Ginlong Ginlong Solis Hybrid Inverter (S Series) (pv) Modbus RTU template

Ginlong Solis Hybrid Inverter (S Series) (pv)

The Ginlong Solis Hybrid Inverter (S Series) is a residential and light-commercial hybrid PV inverter that combines solar generation with battery storage. This ModbusCloud template reads two key PV production registers over Modbus RTU via RS485: total DC output power (register 33057) and cumulative total energy generation (register 33029). Together these give installers and asset managers a clear picture of live generation and lifetime yield, enabling performance verification and long-term yield reporting directly from the ModbusCloud portal.

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

NameUnitAccessAddress (Hidden until you enter your email)Function (hidden)Type (hidden)
powerWRead
energykWhRead

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.

Number of installations (optional)

Use cases

  • Monitor real-time DC output power to verify the Solis S Series inverter is producing at expected capacity.
  • Track cumulative energy generation over time to confirm yield against the original PV system design.
  • Alert on sustained drops in total DC output power during peak irradiance hours to flag shading or faults.
  • Compare daily and seasonal energy totals across multiple Solis S Series sites from one portal overview.
  • Report lifetime kWh generation figures to building owners or grid operators for subsidy and compliance records.

Installation

  1. Enable Modbus RTU on the Solis S Series inverter by navigating to the communication or advanced settings menu on the inverter display, setting the slave address (default 01) and baud rate to 9600.

  2. Connect the ModbusCloud Gateway to the inverter's RS485 COM port using a twisted-pair cable, wiring RS485-A to A and RS485-B to B, with a common ground reference where required.

  3. In the ModbusCloud portal, add your Gateway, import the Ginlong Solis Hybrid Inverter (S Series) (pv) template, and assign the correct Modbus unit ID matching the slave address set on the inverter.

  4. Verify the connection by checking that the portal displays live values for the power and energy registers; a non-zero power reading during daylight confirms successful communication.

Things to watch for

Why does the portal show zero for power during the day?

The inverter's Modbus interface only responds when the LCD is powered, which requires DC voltage from the PV panels. If irradiance is too low or panels are shaded, the inverter may be in standby and will not respond to Modbus polls. Wait until the inverter is in normal operation before expecting live readings.

Energy and power values look wildly incorrect. What is wrong?

Both registers are 32-bit unsigned integers (uint32) spanning two consecutive 16-bit Modbus registers. The Solis S Series uses big-endian byte order, high word first. If your reading tool assembles the words in the wrong order, you will get a garbage value. Confirm your Modbus master is reading two registers starting at the base address and combining them high-word-first.

The Gateway times out on every poll. What should I check?

Verify the RS485 wiring: A to A and B to B, with no polarity reversal. Check that the baud rate is 9600, parity is None, 8 data bits, and 1 stop bit. Confirm the unit ID in the portal matches the slave address on the inverter display. A proprietary Exceedconn connector is required on the inverter's COM port; a standard RJ45 plug will not make reliable contact.

Polling works but values freeze after a few minutes. Why?

The Solis S Series Modbus stack can become unresponsive if the bus is polled too aggressively. Use a polling interval of at least 30 to 60 seconds. Also note that running the manufacturer's WiFi datalogger on the same RS485 bus simultaneously can cause bus contention, resulting in dropped responses or frozen values. Disconnect the datalogger from the COM port or use a bus-sharing adapter.

Want to see how it works?

Electrician working in an open distribution board