Sigenergy Sigen PV Max (pv)
The Sigenergy Sigen PV Max is a string PV inverter for residential and small commercial solar installations, available in SP and TP series power classes. This ModbusCloud template targets the Sigen PV Max over Modbus TCP and reads the inverter's AC output power at register 30035. Supported across the Sigen Hybrid and SigenStore EC product family, the template gives installers and asset managers a live power reading from the inverter via the ModbusCloud Gateway, enabling continuous solar yield monitoring without manual data collection.
- Protocol
- Modbus TCP
- Connection
- Ethernet, Modbus TCP
- Registers
- 1, read only
- Brand
- Sigenergy
- Compatible models
- Sigen Hybrid · Sigen PV Max · SigenStore EC
- Last updated
Registers (1)
1 read, 0 write
| Name | Unit | Access | Address (Hidden until you enter your email) | Function (hidden) | Type (hidden) |
|---|---|---|---|---|---|
| power | W | 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 AC output power to verify the Sigen PV Max is producing at expected levels.
- Track daily power curves to detect soiling, shading, or clipping events on specific string inputs.
- Alert on sustained zero-power readings during daylight hours to identify inverter faults early.
- Compare output power across multiple Sigen PV Max units on the same site to spot underperforming inverters.
- Report monthly generation trends to building owners using ModbusCloud historical data exports.
Installation
Enable Modbus TCP on the Sigen PV Max by opening the mySigen App, navigating to the device settings panel, and turning on the Modbus TCP Server Enable toggle, then saving the change.
Connect the Sigen PV Max to the same local network as the ModbusCloud Gateway using a wired Ethernet connection or the inverter's built-in WLAN interface, and confirm port 502 is reachable.
In the ModbusCloud portal, add the Gateway, import the Sigenergy Sigen PV Max (pv) template, and assign the correct Modbus slave unit ID matching the inverter's configured address.
Spot-check register 30035 in the portal's live register view and confirm a plausible watt value is returned before saving the device configuration.
Things to watch for
Modbus TCP is enabled but no data appears in the portal. Why?
Confirm that both the inverter and the ModbusCloud Gateway are on the same local network segment and that TCP port 502 is not blocked by a firewall or VLAN boundary. Also verify the unit ID in the portal matches the slave address configured in the mySigen App, which defaults to 1 for individual inverters.
Register 30035 returns zero even during sunlight hours. What is wrong?
A zero reading during active daylight can indicate that Modbus TCP was not saved correctly after enabling it, or that the inverter is in standby due to a grid fault. Reconnect to the mySigen App, confirm the Modbus TCP Server Enable toggle is still on, and check the inverter's running state in the app.
The power value looks unexpectedly large or negative. Is the scaling correct?
Register 30035 is a signed 32-bit integer spanning two consecutive Modbus registers. Ensure your Modbus client reads both registers as a single int32 value in big-endian (Sigenergy standard) byte order. Reading only one 16-bit word or swapping byte order will produce incorrect results.
Which slave address should I use for plant-level versus inverter-level queries?
Individual inverter registers, including register 30035, are read at the inverter's own slave address (commonly 1). Plant-level aggregate registers use slave address 0 or 247. Using address 247 for a single-inverter query will return plant totals, not the individual Sigen PV Max reading.
Want to see how it works?
