VARTA pulse neo (battery)

Installation

1. 1Connect the VARTA pulse neo to your local network via its RJ45 Ethernet port and confirm the device has a stable IP address assigned by your router or DHCP server.
2. 2In the ModbusCloud portal, add a new ModbusCloud Gateway, enter the VARTA unit's IP address and port 502, and set the Modbus unit ID to 255 as recommended in the VARTA Modbus documentation.
3. 3Import the VARTA pulse neo template from the ModbusCloud template library and assign it to the gateway you just configured, leaving register addresses at their defaults.
4. 4Trigger a manual poll in the portal and spot-check that register 1066 returns a signed watt value and register 1068 returns a percentage between 0 and 100 to confirm the connection is working.

Things to watch for

01

Why does the portal report only one active Modbus connection at a time?

The VARTA Modbus TCP server accepts only one client session simultaneously. If another system such as a home automation controller is already polling the device, the ModbusCloud Gateway will be refused. Disconnect or proxy the competing client before connecting the Gateway.

02

Register 1066 returns garbage or negative values unexpectedly. What is wrong?

Register 1066 is a signed int16. A negative value means the battery is discharging, which is correct behavior. If the magnitude looks wrong, confirm your polling tool is decoding the register as int16 (signed), not uint16 (unsigned). Using uint16 will produce large incorrect positive values during discharge.

03

The gateway connects but stops receiving data after a few minutes.

The VARTA Modbus server is sensitive to poll frequency. Keep the request interval at one second or slower, as documented by VARTA. A too-rapid polling loop can cause the server to drop or reset the TCP connection. Adding a short delay between requests resolves most dropout issues.

04

Is it safe to write to register 1074 to control discharge?

Use register 1074 with caution. Writing 0 halts discharge immediately. The register controls maximum discharge power and is not fully documented in all official VARTA Modbus revisions. Test with the battery in a non-critical state first. Incorrect values can interfere with normal energy management and may affect warranty conditions. Always restore normal operation values after testing.

More VARTA templates

VARTA Energy Storage

VARTA

Modbus TCP

Monitors VARTA energy storage systems via Modbus TCP.

9 registers258

VARTA element (battery)

VARTA

Modbus TCP

3 registers

VARTA pulse (grid)

VARTA

Modbus TCP

1 registers

VARTA pulse (pv)

VARTA

Modbus TCP

1 registers

VARTA element (pv)

VARTA

Modbus TCP

1 registers

VARTA pulse neo (grid)

VARTA

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