ABB M1M 96 power meter

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
active_energy_import	20482	U32BE	0.01
active_energy_export	20486	U32BE	0.01
reactive_energy_import	20494	U32BE	0.01
reactive_energy_export	20498	U32BE	0.01
apparent_energy_import	20506	U32BE	0.01
three_phase_system_voltage	23296	U32BE	0.1	V
phase_voltage_l1	23298	U32BE	0.1	V
phase_voltage_l2	23300	U32BE	0.1	V
phase_voltage_l3	23302	U32BE	0.1	V
line_voltage_l1_l2	23304	U32BE	0.1	V
line_voltage_l3_l2	23306	U32BE	0.1	V
line_voltage_l1_l3	23308	U32BE	0.1	V
three_phase_system_current	23310	U32BE	0.01	A
current_l1	23312	U32BE	0.01	A
current_l2	23314	U32BE	0.01	A
current_l3	23316	U32BE	0.01	A
current_n	23318	U32BE	0.01	A
active_power_total	23322	U32BE	0.01	W
active_power_l1	23324	U32BE	0.01	W
active_power_l2	23326	U32BE	0.01	W
active_power_l3	23328	U32BE	0.01	W
reactive_power_total	23330	U32BE	0.01	VAR
reactive_power_l1	23332	U32BE	0.01	VAR
reactive_power_l2	23334	U32BE	0.01	VAR
reactive_power_l3	23336	U32BE	0.01	VAR
apparent_power_total	23338	U32BE	0.01	VAR
apparent_power_l1	23340	U32BE	0.01	VA
apparent_power_l2	23342	U32BE	0.01	VA
apparent_power_l3	23344	U32BE	0.01	VA
frequency	23346	U16	0.01	Hz
power_total_angle	23347	I16	0.1	°
power_angle_l1	23348	I16	0.1	°
power_angle_l2	23349	I16	0.1	°
power_angle_l3	23350	I16	0.1	°
voltage_angle_l1	23351	I16	0.1	°
voltage_angle_l2	23352	I16	0.1	°
voltage_angle_l3	23353	I16	0.1	°
current_angle_l1	23357	I16	0.1	°
current_angle_l2	23358	I16	0.1	°
current_angle_l3	23359	I16	0.1	°
power_factor_total	23360	I16	0.001
power_factor_l1	23361	I16	0.001
power_factor_l2	23362	I16	0.001
power_factor_l3	23363	I16	0.001
cosphi_total	23368	I16	0.001
cosphi_l1	23369	I16	0.001
cosphi_l2	23370	I16	0.001
cosphi_l3	23371	I16	0.001
phase_voltage_harmonics_l1_thd	23808	U16	0.1	%
phase_voltage_harmonics_l2_thd	23936	U16	0.1	%
phase_voltage_harmonics_l3_thd	24064	U16	0.1	%
current_harmonics_l1_thd	24576	U16	0.1	%
current_harmonics_l2_thd	24704	U16	0.1	%
current_harmonics_l3_thd	24832	U16	0.1	%
unbalance_phase_voltage	25088	U32BE	0.1	%
unbalance_line_voltage	25090	U32BE	0.1	%
unbalance_current	25092	U32BE	0.1	%
digital_output_1_status	25344	U16	1
digital_output_2_status	25345	U16	1
digital_input_1_2_status	25352	U32BE	1
digital_input_3_4_status	25354	U32BE	1

link settings as documented (unverified): RTU/TCP; baud 9600/19200/38400/57600/115200; FC 03,16

bench facts as documented (unverified)

terminals	3-pole plug contact
A/B polarity	polarity dependent
termination	120 Ohm resistors at both ends of the line
connector	3-pole plug contact, RJ45
shield/ground	shield should be connected to ground in one end
max registers/read	125
broadcast	supported
protocol notes	When using function code 16 (10H), all registers of the same function must be written consecutively.
model register	8966
serial register	8900
firmware register	8908
doc revision	9AKK108467A2704 [1.3]

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

When reading multi-register values (such as 64-bit energy values spanning 4 registers), the registers must be read together in a single request. Attempting to read them one by one or partially will result in incorrect data (e.g., returning 0 or 25565) or an Illegal Data Value exception. [source]
confirmed: comms defaults (baud rates 9600 to 115200, Modbus RTU/TCP, function codes 3 and 16) — confirmed by ABB M1M 20 User Manual and M1M Modbus Communication Manual
confirmed: identification registers (serial @ 8900, firmware @ 8908, model/product name @ 8966) — confirmed by ABB M1M 30 Modbus Register Map and M1M Modbus map V1.2
confirmed: physical properties (3-pole terminal for RTU, RJ45 for TCP, polarity dependent, 120 Ohm termination, shield grounded at one end) — confirmed by ABB M1M 20 User Manual and M1M Modbus Communication Manual
confirmed: quirks (broadcast supported, max read registers 125, consecutive write requirement for FC16) — confirmed by ABB M1M Modbus Communication Manual (9AKK108467A2704)

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.