Endress+Hauser Promag W 10 flowmeter

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
scan_list_register_0	5000	U16	1
scan_list_register_1	5001	U16	1
scan_list_register_2	5002	U16	1
scan_list_register_3	5003	U16	1
scan_list_register_4	5004	U16	1
scan_list_register_5	5005	U16	1
scan_list_register_6	5006	U16	1
scan_list_register_7	5007	U16	1
scan_list_register_8	5008	U16	1
scan_list_register_9	5009	U16	1
scan_list_register_10	5010	U16	1
scan_list_register_11	5011	U16	1
scan_list_register_12	5012	U16	1
scan_list_register_13	5013	U16	1
scan_list_register_14	5014	U16	1
scan_list_register_15	5015	U16	1
value_of_scan_list_register_0	5050	F32BE	1
value_of_scan_list_register_1	5052	F32BE	1
value_of_scan_list_register_2	5054	F32BE	1
value_of_scan_list_register_3	5056	F32BE	1
value_of_scan_list_register_4	5058	F32BE	1
value_of_scan_list_register_5	5060	F32BE	1
value_of_scan_list_register_6	5062	F32BE	1
value_of_scan_list_register_7	5064	F32BE	1
value_of_scan_list_register_8	5066	F32BE	1
value_of_scan_list_register_9	5068	F32BE	1
value_of_scan_list_register_10	5070	F32BE	1
value_of_scan_list_register_11	5072	F32BE	1
value_of_scan_list_register_12	5074	F32BE	1
value_of_scan_list_register_13	5076	F32BE	1
value_of_scan_list_register_14	5078	F32BE	1
value_of_scan_list_register_15	5080	F32BE	1

link settings as documented (unverified): RTU; baud 1200/2400/4800/9600/19200/38400/57600/115200; FC 03,04,06,08,16,23; Response times: Direct data access: typically 25 to 50 ms, Auto-scan buffer: typically 3 to 5 ms.

⚠ Components carry voltage! Incorrect work performed on the electrical connections can result in an electric shock. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	Spring terminals, suitable for strands and strands with ferrules. Conductor cross-section 0.2 to 2.5 mm2 (24 to 12 AWG).
termination	Not integrated
connector	Cable gland: M20 x 1.5 for cable diameter 6 to 12 mm. Thread for cable entry: NPT 1/2", G 1/2", G 1/2" Ex d, M20.
isolation	The outputs are galvanically isolated from one another and from earth.
shield/ground	Connect the cable shields to the inner ground terminal. Ground cable requirements: Copper wire: at least 6 mm2.
max registers/read	125
broadcast	supported
protocol notes	A maximum of 125 consecutive Modbus registers can be read with 1 telegram. A maximum of 120 consecutive Modbus registers can be written with 1 telegram. Response time of the device to the telegram of the Modbus master: typically 3 to 5 ms.
power	Option D: DC 24 V (-20 to +30%); Option E: AC 100 to 240 V (-15 to +10%, 50/60 Hz); Option I: DC 24 V / AC 100 to 240 V; Option M: DC 24 V / AC 100 to 240 V. Power consumption: max. 10 W.
environment	Operating temperature for cables: -20 to +80 °C (-4 to +176 °F).
accuracy	Volume flow: ±0.5 % o.r. ± 1 mm/s. Repeatability: Volume flow Max. ±0.1 % o.r. ± 0.5 mm/s.
certifications	CE mark, C-Tick, ISO 17025, ISO 20456:2017
doc revision	BA02073D/06/EN/01.21
firmware applicability	01.00.zz

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

The register map summary contains off-by-one errors for the scan list configuration and value registers. The scan list configuration registers are mapped to Modbus addresses 5001 to 5016 (not 5000 to 5015), and the values of the scan list registers are mapped to Modbus addresses 5051 to 5082 (not 5050 to 5081). [source]
confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] and RTU framing — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 95
confirmed: Modbus function codes [3, 4, 6, 8, 16, 23] — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 58
confirmed: Direct data access response time (typically 25 to 50 ms) and Auto-scan buffer response time (typically 3 to 5 ms) — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 58
confirmed: Volume flow accuracy (±0.5 % o.r. ± 1 mm/s) and repeatability (Max. ±0.1 % o.r. ± 0.5 mm/s) — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 101
confirmed: Certifications (CE mark, C-Tick, ISO 17025, ISO 20456:2017) — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 101
confirmed: Operating temperature for cables (-20 to +80 °C) — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 100
confirmed: Spring terminals supporting conductor cross-section 0.2 to 2.5 mm2 (24 to 12 AWG) — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 97
confirmed: Power supply options (Option D, E, I, M) and max power consumption of 10 W — confirmed by Operating Instructions BA02073D/06/EN/01.21, page 43

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.