E-Mon PowerSmart+ 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
v1_voltage	13952	F32LE	1
v2_voltage	13954	F32LE	1
v3_voltage	13956	F32LE	1
i1_current	13958	F32LE	1
i2_current	13960	F32LE	1
i3_current	13962	F32LE	1
kw_l1	13964	F32LE	1
kw_l2	13966	F32LE	1
kw_l3	13968	F32LE	1
kvar_l1	13970	F32LE	1
kvar_l2	13972	F32LE	1
kvar_l3	13974	F32LE	1
kva_l1	13976	F32LE	1
kva_l2	13978	F32LE	1
kva_l3	13980	F32LE	1
pf_l1	13982	F32LE	1
pf_l2	13984	F32LE	1
pf_l3	13986	F32LE	1
total_kw	14336	F32LE	1
total_kvar	14338	F32LE	1
total_kva	14340	F32LE	1
total_pf	14342	F32LE	1
average_voltage_ln	14356	F32LE	1
average_voltage_ll	14358	F32LE	1
average_current	14360	F32LE	1
neutral_current	14466	F32LE	1
frequency	14468	F32LE	1
voltage_unbalance	14470	F32LE	1
current_unbalance	14472	F32LE	1
kwh_import	14720	F32LE	1
kwh_export	14722	F32LE	1
kvarh_import	14728	F32LE	1
kvarh_export	14730	F32LE	1
kvah_total	14736	F32LE	1

link settings as documented (unverified): RTU; baud 300/600/1200/2400/4800/9600/19200/38400/57600/115200; FC 03,04,06,16,08

bench facts as documented (unverified)

wiring notes	COM1 supports RS-485. COM2 supports RS-232, RS-422, RS-485, RF, Ethernet, and Profibus.
broadcast	not supported
model register	46082
serial register	46080
firmware register	46100
doc revision	BG0542 Rev. A1

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

confirmed: Baud rates [300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] — confirmed by BG0542 Rev. A1, Section 3.7 (Device Setup Registers, offset +3 BPS)
confirmed: Modbus function codes [3, 4, 6, 16, 8] — confirmed by BG0542 Rev. A1, Section 2.3 (Table 2-2 Modbus Function Codes)
confirmed: Device identification registers (serial @ 46080, model @ 46082, firmware @ 46100) — confirmed by BG0542 Rev. A1, Section 3.7 (Device Identification block)
confirmed: COM1 and COM2 physical port capabilities — confirmed by BG0542 Rev. A1, Section 3.7 (COM1/COM2 port options)
confirmed: Broadcast mode not supported — confirmed by BG0542 Rev. A1, Section 2.2 (Address Field)
confirmed: Register map addresses (v1_voltage @ 13952, total_kw @ 14336, kwh_import @ 14720) — confirmed by BG0542 Rev. A1, Section 2.7 (Data Formats) and Section 3

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.