Kostal Plenticore Ess

Installation

1. 1Enable Modbus TCP on the Kostal Plenticore via the inverter web interface or display menu under the Modbus/SunSpec communication section; note the default port is 1502 and the default Unit ID is 71.
2. 2Connect the Kostal Plenticore to the same LAN segment as the ModbusCloud Gateway using a standard Ethernet cable to the RJ45 port on the Smart Communication Board.
3. 3In your ModbusCloud portal, add a new gateway, import the Kostal Plenticore Ess template, set the host address to the inverter IP, port to 1502, and Unit ID to 71.
4. 4Spot-check register 210 (state of charge) and register 152 (frequency) in the live data view to confirm values are plausible before enabling any alerts or write operations.

Things to watch for

01

All float registers return garbage or enormous values. Why?

The Kostal Plenticore defaults to Little-Endian (CDAB) byte order for float registers. If your client or the ModbusCloud Gateway is configured for Big-Endian (ABCD), every float32 value will be nonsensical. In the inverter web interface, go to the Modbus/SunSpec settings and verify or change the byte order to match your client configuration.

02

Modbus TCP connects but the inverter state register reads zero constantly.

Register 56 returns 0 when the inverter is in the Off state, which is correct. However, if other registers are also zero during daylight, Modbus TCP may not actually be enabled. Confirm the Modbus TCP toggle is active in the inverter communication settings, not just that a network connection is present on port 1502.

03

Writing set_active_power has no effect. What is required first?

External battery control via Modbus must be explicitly enabled by a qualified installer in the inverter settings under the battery management section, selecting the Modbus TCP option. Without this, write commands are accepted by the TCP stack but ignored by the inverter. Also note that write register values are not stored persistently; they reset after any inverter power cycle or reboot.

04

Is it safe to write large values to the active power setpoint register?

Use caution: the set_active_power register directly controls battery charge and discharge behavior. Sending setpoints outside the inverter operational limits or conflicting with max_charge_power or max_discharge_power can cause protection trips. Always write setpoints incrementally and monitor active_power and soc in real time. Consult the Kostal Modbus interface documentation and your installer before deploying automated write logic.

Registers (17)

16 read / 1 write

More Kostal templates

Kostal Inverter

Kostal

Modbus RTU

Reads values from Kostal inverters via RS485 Modbus connection.

0 registers189

Kostal Modbus-TCP and Battery

Kostal

Modbus TCP

Reads energy yield, consumption, and battery data from Kostal inverters via Modbus TCP.

12 registers325

Kostal Plenticore Hybrid, incl. grid charging of the house battery (battery)

Kostal

Modbus TCP

2 registers

Kostal Smart Energy Meter KSEM

Kostal

Modbus TCP

Reads energy data from Kostal Smart Energy Meter via Modbus TCP

3 registers61

Kostal Plenticore Hybrid (battery)

Kostal

Modbus TCP

1 registers

Kostal Smart Energy Meter (via inverter) (grid)

Kostal

Modbus TCP

1 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

Sigenergy SigenStore EC (grid)

Sigenergy

Modbus TCP

5 registers1

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

Fronius - Modbus TCP

Fronius

Modbus TCP

Monitors Fronius Symo and Primo inverters via Modbus TCP

15 registers597