Solax X3-MIC G2 (pv)
The Solax X3-MIC G2 is a three-phase string inverter for residential and small commercial PV installations, available from 3 kW to 15 kW. This ModbusCloud template connects over Modbus TCP via the Solax PocketWiFi or PocketLAN dongle and reads AC output power, cumulative energy yield, and per-phase voltages and currents for all three phases. With this data in your portal you can verify generation performance, detect phase imbalances, and maintain a continuous production record without relying on Solax Cloud.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 8, read only
- Brand
- Solax
- Compatible models
- X3-MIC G2 · X3-PRO G2 · Q.VOLT P5T-X · Q.VOLT P17T-X
- Last updated
Registers (8)
8 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | Wh | Read | |||
| currents_a | A | Read | |||
| currents_b | A | Read | |||
| currents_c | A | Read | |||
| voltages_a | V | Read | |||
| voltages_b | V | Read | |||
| voltages_c | V | Read |
Loading registers…
Send your device list
If a device is not in the library yet, we build the template for free as soon as we have the register data.
Use cases
- Monitor total AC output power in real time to verify the Solax X3-MIC G2 is producing at expected capacity.
- Track cumulative energy yield over time to generate accurate production reports for building owners or grid feed-in billing.
- Alert on per-phase voltage deviations across phases A, B, and C to detect grid disturbances or wiring faults early.
- Compare phase currents on all three phases to identify unbalanced loading or a failed string connection.
- Verify inverter output after firmware updates by checking that power and voltage readings return to baseline values.
Installation
Ensure a Solax PocketWiFi 3.0 (or newer) dongle is installed on the inverter and connected to the same LAN as the ModbusCloud Gateway; earlier dongle versions do not expose Modbus TCP on port 502.
Note the dongle's IP address from your router's DHCP table or assign a static IP, then confirm reachability on TCP port 502 from the same network segment.
In your ModbusCloud portal, add a new device, select the Solax X3-MIC G2 (pv) template, enter the dongle's IP address, set port 502, and use the default Modbus unit ID of 1.
Save the configuration, then open the live register view and spot-check the voltages_a register to confirm a plausible grid voltage value and verify communication is active.
Things to watch for
All registers return zero or no response after adding the device.
The Solax X3-MIC G2 does not expose Modbus TCP natively. Communication requires a PocketWiFi 3.0 or newer dongle acting as a TCP-to-RTU bridge. Older PocketWiFi versions and PocketLAN dongles do not provide Modbus access. Confirm the dongle firmware version and that it is connected to the LAN, then retry on port 502.
Power reads a plausible value but energy always shows zero.
The energy register (address 1059) is a uint32 spanning two consecutive 16-bit input registers. If the gateway polls only one register word, the 32-bit value is incomplete and resolves to zero. Verify that your polling configuration requests two consecutive registers starting at address 1059 and that the byte order is big-endian, which is standard for Solax Modbus.
Phase voltages or currents on one phase read zero intermittently.
Solax MIC G2 inverters expose phase data only while actively generating AC power. At night or during a protection trip the inverter stops responding to Modbus queries on those registers. Check the inverter LCD for any fault code and verify PV string voltage is sufficient for the inverter to start. The zero reading is expected behaviour outside generating hours.
The gateway connects but data updates stop after a few minutes.
Modbus is designed for a single master. If SolaxCloud monitoring or another integration is simultaneously polling the dongle, data collisions cause the dongle to block subsequent connections. Disable competing cloud polling or use a TCP multiplexer to serialise queries. Also keep the polling interval at 15 seconds or more, as the dongle drops requests when queried too rapidly.
-917%2Fcover.png&w=3840&q=75)
Want to see how it works?
