Hager Hager XEM with EMC flow R2 (grid)

Installation

1. 1Confirm the Hager XEM470 is connected to the local LAN via its Ethernet port and has a valid IP address assigned, either by DHCP or static configuration via the embedded web interface.
2. 2Connect the ModbusCloud Gateway to the same LAN segment as the XEM470 and verify network reachability between the two devices on TCP port 502.
3. 3In the ModbusCloud portal, add a new device, import the Hager XEM470 EMC flow R2 (grid) template, and enter the XEM470's IP address and Modbus unit ID (default is 1 unless changed in the device configuration).
4. 4Trigger a manual poll in the portal and verify that registers 4099 to 4102 return plausible values: phase currents should reflect the actual load, and active power should show a signed watt reading matching grid flow direction.

Things to watch for

01

All four registers return zero or no response. What is wrong?

Verify the XEM470 has an active LAN connection and that TCP port 502 is reachable from the ModbusCloud Gateway. Check that the unit ID configured in the portal matches the device's Modbus slave address. Also confirm the XEM470 firmware is up to date, as earlier versions had limited Modbus TCP support.

02

Phase current values look wrong or wildly high. Why?

The currents registers (4099 to 4101) are uint16 and the XEM470 applies a scaling factor internally. If your portal displays raw counts without applying the correct divisor documented in the Hager Modbus table, readings will appear inflated. Cross-check the scaling for your firmware revision against the official Hager Modbus register document.

03

The active power register shows a constant value and does not update. What should I check?

Register 4102 is an int32 spanning two consecutive 16-bit holding registers. Confirm the ModbusCloud Gateway is reading two registers starting at address 4102 with FC3, and that big-endian word order is used. A single-register read or swapped word order will produce a stuck or garbage value.

04

The gateway connects but values jump between correct readings and large negative numbers.

The power register is a signed int32. Negative values indicate grid export (energy flowing back to the grid) and are normal during PV surplus. If the sign oscillates unexpectedly, check that no other Modbus master is polling the device simultaneously, as concurrent masters on TCP can cause incomplete reads and data corruption.

Registers (4)

4 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 ECA180D One-phase energy meter

Hager

Modbus RTU

Monitors single-phase energy consumption via Modbus RTU

8 registers30

Hager Hager XEM with EMC flow R2 (battery)

Hager

Modbus TCP

2 registers

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