Ginlong Solis Storage Inverter (S Series) (pv)
The Ginlong Solis Storage Inverter (S Series) is a hybrid PV inverter designed for residential and light-commercial solar-plus-storage installations. This Modbus RTU template reads two core photovoltaic registers from the ESINV register map: instantaneous DC PV output power (address 33057) and cumulative total energy generation (address 33029). Both registers use function code 4 and 32-bit unsigned integer encoding. Connecting via the ModbusCloud Gateway gives installers a continuous view of PV production performance across the Solis Hybrid Inverter (S Series), Solis Storage Inverter (S Series), and AXIhycon 12-15H.
- Protocol
- Modbus RTU
- Connection
- RS485
- Registers
- 2, read only
- Brand
- Ginlong
- Compatible models
- Solis Hybrid Inverter (S Series) · Solis Storage Inverter (S Series) · AXIhycon 12-15H
- Last updated
Registers (2)
2 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | Read | |||
| energy | kWh | 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 real-time DC PV output power to verify the inverter is producing at expected levels during daylight hours.
- Track cumulative total energy generation over time to confirm yield against the original system design estimate.
- Alert on sustained near-zero power readings during daylight to detect PV string faults or inverter shutdowns early.
- Compare daily production trends across multiple sites running Solis S Series inverters in your ModbusCloud portal.
- Report monthly energy generation totals from the cumulative register to support maintenance invoicing or performance guarantees.
Installation
Enable Modbus RTU on the inverter by navigating to the communication or advanced settings menu on the inverter display, and confirm the RS485 slave address (default is typically 1) and baud rate (9600 bps, 8N1).
Wire the RS485 A and B terminals of the inverter COM port to the corresponding A and B terminals on the ModbusCloud Gateway, using a twisted-pair cable with a 120-ohm termination resistor at each end of the bus.
In the ModbusCloud portal, add the Gateway, import the Ginlong Solis Storage Inverter (S Series) (pv) template, and set the unit ID to match the slave address configured on the inverter.
Verify the connection by spot-checking the power register (33057): during daylight hours the value should reflect active PV generation in watts; a zero or error reading at midday indicates a wiring or address mismatch.
Things to watch for
Why does the power register always read zero or a nonsense value?
Register 33057 is a 32-bit unsigned integer spanning two consecutive 16-bit input registers. If your Modbus master reads only one register or reverses the word order, you will get an incorrect or zero result. Confirm that your polling request reads 2 registers starting at 33057 and that word order is big-endian (high word first), as documented in the Ginlong ESINV protocol.
The energy register (33029) value looks far too large. What is wrong?
Address 33029 is also a 32-bit unsigned integer (two 16-bit words). The raw value is in kilowatt-hours with no scaling factor. If the two words are swapped (little-endian word order), the resulting number will be implausibly large. Ensure the template and your gateway are set to big-endian 32-bit word order.
The gateway connects but no register values appear after import. What should I check?
The most common cause is a slave address mismatch. The default Solis RS485 address is 1, but it can be changed in the inverter menu. Confirm the unit ID in the ModbusCloud portal matches exactly. Also verify serial settings: 9600 bps, 8 data bits, 1 stop bit, no parity. A wrong parity setting causes silent timeouts rather than explicit errors.
Polling works but values drop out intermittently. Why?
The Ginlong Solis RS485 stack can be overloaded by excessively frequent polling. Use a polling interval of at least 15 to 30 seconds. Also ensure no other device (such as the manufacturer datalogger or a Wi-Fi stick) is simultaneously acting as Modbus master on the same RS485 bus, as bus contention causes frame collisions and dropped responses.
More Ginlong templates
Want to see how it works?
