Raritan PX2/PX3 PDU

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
register_set_version	0	U16	1
number_of_inlets	1	U16	1
number_of_overcurrent_protectors	2	U16	1
number_of_outlets	3	U16	1
number_of_transfer_switches	4	U16	1
peripheral_sensor_1_type	2048	U16	1
peripheral_sensor_1_state	2049	U16	1
peripheral_sensor_1_reading	2050	F32BE	1
transfer_switch_active_inlet	8193	U16	1
transfer_switch_preferred_inlet	8194	U16	1
transfer_switch_phase_sync_angle	8200	F32BE	1	degrees
inlet_1_rms_voltage	12296	F32BE	1	V
inlet_1_rms_current	12298	F32BE	1	A
inlet_1_active_power	12306	F32BE	1	W
inlet_1_apparent_power	12308	F32BE	1	VA
inlet_1_power_factor	12310	F32BE	1
inlet_1_line_frequency	12322	F32BE	1	Hz
ocp_1_rms_current	16394	F32BE	1
outlet_1_rms_voltage	32776	F32BE	1
outlet_1_rms_current	32778	F32BE	1
outlet_1_active_power	32786	F32BE	1
outlet_1_apparent_power	32788	F32BE	1
outlet_1_power_factor	32790	F32BE	1
outlet_1_line_frequency	32802	F32BE	1

link settings as documented (unverified): TCP; FC 01,03,05,06,15,16,22,43; The Modbus service can be enabled in the Network Services section of the Device Settings menu in the web UI.

bench facts as documented (unverified)

protocol notes	Data types which span multiple 16-bit registers are big-endian.
FC 43 device ID	supported

generated by gemini:gemini-3.5-flash · harvested from https://cdn.raritan.com/download/px3/version-3.6.1/PDU_Modbus_3.6.1_46982.pdf (Raritan); 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.