Hager ECR/ECx energy meter range

Register map(s) for this device, each at the trust rung it earned. Addresses are 0-based as on the wire. Word order and scaling are confirmed at the hardware-verified rung and at no rung below it.

interop-verified

Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.

point	address (0-based)	type	scale	unit
voltage_l1_n	45056	U16	0.01	V/100
voltage_l2_n	45057	U16	0.01	V/100
voltage_l3_n	45058	U16	0.01	V/100
voltage_l1_l2	45059	U16	0.01	V/100
voltage_l2_l3	45060	U16	0.01	V/100
voltage_l3_l1	45061	U16	0.01	V/100
frequency	45062	U16	0.01	Hz/100
current_l1	45065	U32BE	0.001	mA
current_l2	45067	U32BE	0.001	mA
current_l3	45069	U32BE	0.001	mA
current_neutral	45071	U32BE	0.001	mA
active_power_total	45073	U32BE	0.01	±kW/100
reactive_power_total	45075	U32BE	0.01	±kvar/100
apparent_power_total	45077	U32BE	0.01	kVA/100
power_factor_total_iec	45079	I16	0.001	0.001
power_factor_total_ieee	45080	I16	0.001	0.001
active_power_l1	45081	U32BE	0.01	±kW/100
active_power_l2	45083	U32BE	0.01	±kW/100
active_power_l3	45085	U32BE	0.01	±kW/100
reactive_power_l1	45087	U32BE	0.01	±kvar/100
reactive_power_l2	45089	U32BE	0.01	±kvar/100
reactive_power_l3	45091	U32BE	0.01	±kvar/100
apparent_power_l1	45093	U32BE	0.01	kVA/100
apparent_power_l2	45095	U32BE	0.01	kVA/100
apparent_power_l3	45097	U32BE	0.01	kVA/100
power_factor_l1_iec	45099	I16	0.001	0.001
power_factor_l2_iec	45100	I16	0.001	0.001
power_factor_l3_iec	45101	I16	0.001	0.001
power_factor_l1_ieee	45102	I16	0.001	0.001
power_factor_l2_ieee	45103	I16	0.001	0.001
power_factor_l3_ieee	45104	I16	0.001	0.001
active_energy_import_total	45152	U32BE	1	kWh
reactive_energy_import_total	45154	U32BE	1	kvarh
active_energy_export_total	45156	U32BE	1	kWh
reactive_energy_export_total	45158	U32BE	1	kvarh
partial_active_energy_import_total	45160	U32BE	1	kWh
partial_active_energy_export_total	45162	U32BE	1	kWh
active_energy_import_total_wh	45164	U32BE	1	Wh
active_energy_export_total_wh	45166	U32BE	1	Wh
active_energy_import_l1	45440	U32BE	1	kWh
active_energy_import_l2	45442	U32BE	1	kWh
active_energy_import_l3	45444	U32BE	1	kWh
active_energy_export_l1	45446	U32BE	1	kWh
active_energy_export_l2	45448	U32BE	1	kWh
active_energy_export_l3	45450	U32BE	1	kWh
reactive_energy_import_l1	45452	U32BE	1	kvarh
reactive_energy_import_l2	45454	U32BE	1	kvarh
reactive_energy_import_l3	45456	U32BE	1	kvarh
reactive_energy_export_l1	45458	U32BE	1	kvarh
reactive_energy_export_l2	45460	U32BE	1	kvarh
reactive_energy_export_l3	45462	U32BE	1	kvarh

link settings as documented (unverified): RTU; baud 1200/2400/4800/9600/19200/38400; FC 03,06,43,67

bench facts as documented (unverified)

terminals	screw terminals
connector	RJ-45 or screw terminals
wiring notes	Agardio models use RJ-45 connection instead of screw terminals
model register	4162
serial register	4196
firmware register	4128
FC 43 device ID	supported
doc revision	1.14
firmware applicability	2.0

field reports — community-sourced, unverified (checked 2026-06-11)

Users frequently encounter Modbus Illegal Data Address (02) exceptions when querying register 45056 (0xB000) because the vendor documentation lists 0-based decimal addresses (e.g., 45056) which are mistaken for 1-based Modbus reference numbers (which would map to protocol address 5055 or 45055). [source]
confirmed: comms.baud_rates: [1200, 2400, 4800, 9600, 19200, 38400] — confirmed by Hager Modbus table Summary rev. 1.14
confirmed: comms.function_codes: [3, 6, 43, 67] — confirmed by Hager Modbus table Summary rev. 1.14
confirmed: facts.identification: fc43_device_id=true, firmware_register=4128, model_register=4162, serial_register=4196 — confirmed by Hager Modbus table Summary rev. 1.14
confirmed: facts.physical: Agardio models use RJ-45 connection instead of screw terminals — confirmed by Hager Modbus table Summary rev. 1.14
confirmed: register_map: voltage_l1_n @ 45056, active_energy_import_total @ 45152, active_energy_import_l1 @ 45440 — confirmed by Hager Modbus table Summary rev. 1.14

The trust ladder

Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
interop-verified — Read + decoded cleanly over a real network vs an independent third-party Modbus test server (transport and framing; reads are remapped into the server's register window, so the map's own addresses are NOT exercised). Does NOT prove word order/scaling against the actual device.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

If your device isn't here, upload its register map. Generation is free, and the connector keeps the rung it earns under testing.

To prove a connector against your own device, order hardware verification. If it doesn't verify, you don't pay.

Platform builders can license the verified library: machine-readable maps, the firmware matrix, API access.