Sigenergy SigenStore EC (pv)

Installation

1. 1Enable Modbus TCP on the SigenStore EC: open the mySigen app, navigate to the device settings panel, turn on the 'Modbus TCP Server Enable' switch, and save. Confirm port 502 is reachable on the inverter's IP address.
2. 2Connect the SigenStore EC and the ModbusCloud Gateway to the same local network, either via Ethernet or Wi-Fi, ensuring no firewall blocks TCP port 502 between the two devices.
3. 3In your ModbusCloud portal, add the Gateway, then import the Sigenergy SigenStore EC (pv) template. Set the unit ID to 1 for a single-inverter plant, or to the slave address assigned in the mySigen app if you have multiple devices.
4. 4Verify the connection by checking the live value for register 30035 (power) in the portal. A non-zero positive reading during daylight confirms Modbus TCP communication is working correctly.

Things to watch for

01

Register 30035 always reads zero even during full sun. Why?

This register reports PV power from panels connected directly to the Sigenergy inverter only. If you have third-party inverters connected via the Smart Port or AC coupling, their generation is not included here. Check the mySigen app to see the total PV figure and compare. Firmware updates have also been known to temporarily affect this register's behaviour.

02

The portal connects to the inverter but no value appears for power.

First confirm that Modbus TCP Server Enable is switched on in the mySigen app and that port 502 is open (use a telnet or port-scan test from the Gateway's network). Next verify the unit ID matches the slave address set in the app. Sigenergy uses unit ID 247 as the plant address for read operations with acknowledgement.

03

I get garbage or wildly incorrect values from register 30035.

The register is typed as int32, which spans two consecutive 16-bit Modbus registers read with function code 3. If your client reads only one word (16-bit) or applies a wrong decode type (for example, uint16 or int16), the result will be incorrect. Confirm the template's int32 data type is active and that no manual override is in place.

04

Is it safe to poll register 30035 frequently?

Register 30035 is read-only, so polling carries no risk of changing inverter behaviour or setpoints. A polling interval of 5 to 30 seconds is typical for energy monitoring. Avoid intervals below 1 second, as excessive Modbus traffic can cause the inverter's TCP server to drop connections.

Registers (1)

1 read / 0 write

More Sigenergy templates

Sigenergy SigenStore EC (grid)

Sigenergy

Modbus TCP

5 registers1

Sigenergy Sigen PV Max (battery)

Sigenergy

Modbus TCP

4 registers

Sigenergy Sigen Hybrid (pv)

Sigenergy

Modbus TCP

1 registers

Sigenergy SigenStor Plant

Sigenergy

Modbus TCP

Monitors SigenStor energy storage system via Modbus TCP

4 registers54

Sigenergy SigenStor Slave

Sigenergy

Modbus TCP

Monitors energy flow and battery data from SigenStor inverters via Modbus TCP.

6 registers45

Sigenergy Sigen PV Max (grid)

Sigenergy

Modbus TCP

5 registers

More TCP templates

Algodue Energy meter UEM80-2D E

Algodue Elettronica S.r.l.

Modbus TCP

Measures single-phase energy consumption and production via Modbus TCP.

12 registers46

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597

Fronius GEN24

Fronius

Modbus TCP

Monitors and controls Fronius GEN24 inverters and PV batteries via SunSpec Modbus TCP

0 registers762

HUAWEI SUN2000 Inverter & LUNA2000 battery

Huawei

Modbus TCP

Monitors HUAWEI SUN2000 inverter, LUNA2000 battery, and Smart Power Sensor via Modbus TCP.

4 registers1248

NIBE Nibe S-Series (SG Ready)

NIBE

Modbus TCP

5 registers1

Domekt R 400 V

Komfovent

Modbus TCP

Controls Komfovent Domekt recuperator ventilation via Modbus TCP

25 registers118