Lovato DMG700 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 only confirmed at the hardware-verified rung.

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
l1_phase_voltage	2	U32BE	0.01
l2_phase_voltage	4	U32BE	0.01
l3_phase_voltage	6	U32BE	0.01
l1_current	8	U32BE	0.0001
l2_current	10	U32BE	0.0001
l3_current	12	U32BE	0.0001
neutral_current	108	U32BE	0.0001
l1_l2_voltage	14	U32BE	0.01
l2_l3_voltage	16	U32BE	0.01
l3_l1_voltage	18	U32BE	0.01
l1_active_power	20	U32BE	0.01
l2_active_power	22	U32BE	0.01
l3_active_power	24	U32BE	0.01
l1_reactive_power	26	U32BE	0.01
l2_reactive_power	28	U32BE	0.01
l3_reactive_power	30	U32BE	0.01
l1_apparent_power	32	U32BE	0.01
l2_apparent_power	34	U32BE	0.01
l3_apparent_power	36	U32BE	0.01
l1_power_factor	38	U32BE	0.0001
l2_power_factor	40	U32BE	0.0001
l3_power_factor	42	U32BE	0.0001
frequency	50	U32BE	0.001
eqv_phase_voltage	52	U32BE	0.01
eqv_phase_to_phase_voltage	54	U32BE	0.01
eqv_current	56	U32BE	0.0001
eqv_active_power	58	U32BE	0.01
eqv_reactive_power	60	U32BE	0.01
eqv_apparent_power	62	U32BE	0.01
eqv_power_factor	64	U32BE	0.0001
total_imported_active_energy	6688	U32BE	0.01
total_exported_active_energy	6690	U32BE	0.01
total_imported_reactive_energy	6692	U32BE	0.01
total_exported_reactive_energy	6694	U32BE	0.01
total_apparent_energy	6696	U32BE	0.01

link settings as documented (unverified): RTU/ASCII/TCP; default 9600 8N1; unit ID 1; FC 03,04,06,07,16,17,23; Supports Modbus RTU and ASCII on RS-485, and Modbus TCP on expansion modules.

bench facts as documented (unverified)

max registers/read	80
identification notes	Function 17 (Report Slave ID) returns device type (e.g., AAh for DMG700), software revision, hardware revision, and parameter revision.
FC 43 device ID	not supported
doc revision	Doc. I317IGB02_22.doc

generated by gemini:gemini-3.5-flash · harvested from https://docs.rs-online.com/a1cf/A700000011374977.pdf (Lovato); manual-faithful — the document's claims, panel risk: LOW — panel concurs, no field disagreements; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.