Dwyer APM/MPM/PPM sensor

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	unit
pv_rate_display_value	0	F32BE	1	User defined
alarm_and_relay_status	2	U16	1	None
digital_inputs_and_outputs_status	3	U16	1	None
maximum_display_value	4	F32BE	1
minimum_display_value	6	F32BE	1
total_value	8	F32BE	1
grand_total_value	10	F32BE	1
total_overflow_value	12	F32BE	1
total_non_overflow_value	14	F32BE	1
grand_total_overflow_value	16	F32BE	1
grand_total_non_overflow_value	18	F32BE	1
pv_rate_display_value_long	20	U32BE	1
maximum_display_value_long	24	U32BE	1
minimum_display_value_long	26	U32BE	1
total_value_long	28	U32BE	1
grand_total_value_long	30	U32BE	1
total_overflow_value_int	32	I16	1
total_non_overflow_value_long	33	U32BE	1
grand_total_overflow_value_int	35	I16	1
grand_total_non_overflow_value_long	36	U32BE	1
pv2_display_value	182	F32BE	1
pv2_display_value_long	184	U32BE	1
pv1_percent_display_value	186	I16	1
analog_output_value	400	U16	1	uA

link settings as documented (unverified): RTU; default 2400 8E?; unit ID 247; FC 03,04,06,16; All 4x Registers are mirrored into 3x register space, and are therefore capable of being read by Modbus function 04 (Read Input Registers).

⚠ As is typical with most instruments, the addition of serial communications carries an inherent risk; it allows a remote operator to change the operation and/or characteristics of the device being digitally communicated with. Inappropriate communication could have serious consequences in meter or system operation. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

protocol notes	Writing a value that is outside the parameters range will force it to be limited to the closest value within the range.
model register	49901
firmware register	49905
identification notes	Product Identifier is at 49901-49904, Firmware Version is at 49905-49908.
doc revision	LIMModbus2DW_A.doc 10/10

generated by gemini:gemini-3.5-flash · harvested from https://assets.dwyeromega.com/manuals-do/APMMPM_Modbus%C2%AE_Register_Tables.pdf (Dwyer); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; 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.