ABB M4M network analyzer

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.

cross-referenced (XPF (Quantum Bit Solutions))

Imported from a third-party source and NOT verified by us — not even structure-checked. An unverified claim, shown so you can find the device; trust it no more than the source it came from.

point	address (0-based)	type	scale	unit
energy_trend_data_block_1_0	33551	U16	1	kWh
max_min_demand_data_block_1_0	36737	U16	1	kW
alarm_number	35935	U16	1
entry_number	32768	U16	1
i_o_port_1	35851	U16	1
energy_trend_data_block_1_1	33552	U16	1	kWh
energy_trend_data_block_1_2	33553	U16	1	kWh
energy_trend_data_block_1_3	33554	U16	1	kWh
energy_trend_data_block_1_4	33555	U16	1	kWh
energy_trend_data_block_1_5	33556	U16	1	kWh
energy_trend_data_block_1_6	33557	U16	1	kWh
energy_trend_data_block_1_7	33558	U16	1	kWh

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.