E-Mon Multi-Mon energy monitor

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale
v1_voltage	13952	U32LE	0.1
v2_voltage	13954	U32LE	0.1
v3_voltage	13956	U32LE	0.1
i1_current	13958	U32LE	0.01
i2_current	13960	U32LE	0.01
i3_current	13962	U32LE	0.01
kw_l1	13964	U32LE	0.001
kw_l2	13966	U32LE	0.001
kw_l3	13968	U32LE	0.001
kvar_l1	13970	U32LE	0.001
kvar_l2	13972	U32LE	0.001
kvar_l3	13974	U32LE	0.001
kva_l1	13976	U32LE	0.001
kva_l2	13978	U32LE	0.001
kva_l3	13980	U32LE	0.001
power_factor_l1	13982	U32LE	0.001
power_factor_l2	13984	U32LE	0.001
power_factor_l3	13986	U32LE	0.001
total_kw	14336	U32LE	0.001
total_kvar	14338	U32LE	0.001
total_kva	14340	U32LE	0.001
total_pf	14342	U32LE	0.001
frequency	14466	U32LE	0.01
kwh_import	14720	U32LE	0.1
kwh_export	14722	U32LE	0.1
kvarh_import	14728	U32LE	0.1
kvarh_export	14730	U32LE	0.1
kvah_total	14736	U32LE	0.1

link settings as documented (unverified): RTU/ASCII/TCP; baud 300/600/1200/2400/4800/9600/19200/38400/57600/115200; unit ID 1; FC 03,04,06,16,08; Broadcast mode using address 0 is not supported.

bench facts as documented (unverified)

wiring notes	Communication interface options: RS-232, RS-422, RS-485, Infrared, Dial-Up Modem, RF Modem, Ethernet, GSM/GPRS
broadcast	not supported
model register	46084
serial register	46080
firmware register	46100
doc revision	BG0548 Rev. A1

⚠ disputed: frequency @ 14466 — disputed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 3.1, which shows the 1-Second Auxiliary Values block starting at 14464, where offset +2,3 (14466-14467) is 'In (neutral) Current' and offset +4,5 (14468-14469) is 'Frequency'

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

confirmed: baud_rates [300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] — confirmed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 3.7
confirmed: framing ['RTU', 'ASCII', 'TCP'] — confirmed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 2.1
confirmed: broadcast_supported: false — confirmed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 2.2
confirmed: identification registers (serial @ 46080, model @ 46084, firmware @ 46100) — confirmed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 3.1
confirmed: register map (v1_voltage @ 13952, total_kw @ 14336, kwh_import @ 14720, kvah_total @ 14736) — confirmed by E-Mon Multi-Mon MODBUS Reference Guide BG0548 Section 3.1

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.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.