Hager Hager XEM with EMC flow R2 (battery)

Installation

1. 1Confirm the XEM470 EMC is connected to the local LAN via its Ethernet port and that Modbus TCP access is enabled under the communication or Modbus section of the device configuration.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the XEM470 and verify IP reachability between the two devices, for example by pinging the XEM470 address from a laptop on the same subnet.
3. 3In the ModbusCloud portal, add the Gateway, import the Hager XEM with EMC flow R2 (battery) template, and assign the correct IP address and unit ID for your XEM470 installation.
4. 4Spot-check both registers in the portal live-data view: the power register at address 4138 should show a signed watt value reflecting current battery activity, and the soc register at address 4146 should show a percentage between 0 and 100.

Things to watch for

01

The portal connects but both registers return zero or no data. Why?

Confirm that Modbus TCP is explicitly enabled in the XEM470 configuration and that no firewall or VLAN is blocking port 502 between the ModbusCloud Gateway and the XEM470. Some firmware versions disable the Modbus TCP server by default; check the device's communication settings and re-enable it if needed.

02

The power register reads an unexpected large negative or positive value. What is wrong?

Address 4138 returns a signed int32 value. If your Modbus client is treating it as an unsigned 32-bit integer, large positive values will appear instead of negative ones during charging. Verify that the data type is configured as int32 in the template, which it is by default.

03

The state of charge value jumps erratically between reads. How do I fix this?

Address 4146 returns a uint16 value. If you see erratic jumps, confirm the function code is 3 (read holding registers) and that only one Modbus master is polling the XEM470 at a time. Multiple simultaneous masters can cause garbled responses on some firmware revisions.

04

Can I rely on the power and soc registers for billing or settlement purposes?

These registers provide operational monitoring data for energy management purposes. They are not MID-certified measurement values. For billing or settlement, use the dedicated MID-certified energy meters in the Hager flow installation. Read-only access here carries no write risk, but always verify your legal metering requirements with the relevant authority.

Registers (2)

2 read / 0 write

More Hager templates

Hager ECR310D Three-phase energy meter

Hager

Modbus TCP

Monitors three-phase energy consumption and production via Modbus RTU.

11 registers61

Hager Hager XEM with EMC flow R2 (pv)

Hager

Modbus TCP

1 registers

Hager ECA380D Three-phase energy meter

Hager

Modbus RTU

Monitors three-phase energy consumption and power quality via Modbus RTU.

25 registers54

Hager Hager XEM with EMC flow R2 (grid)

Hager

Modbus TCP

4 registers

Hager ECA180D One-phase energy meter

Hager

Modbus RTU

Monitors single-phase energy consumption via Modbus RTU

8 registers30

Hager ECR380D

Hager

Modbus RTU

61 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