Omega Platinum CN/DP Pt-series controller

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
current_input_value	528	F32BE	1
smart_sensor_value	534	F32BE	1
input_digital	542	U16	1
current_setpoint_1	544	F32BE	1
current_setpoint_2	546	F32BE	1
control_setpoint	548	F32BE	1
peak_value	550	F32BE	1
valley_value	552	F32BE	1
pid_output	554	F32BE	1	%
current_input_valid	556	U16	1
alarm_state	557	U16	1
ramp_soak_state	558	U16	1
output_1_state	560	U16	1
output_2_state	561	U16	1
output_3_state	562	U16	1
output_4_state	563	U16	1
output_5_state	564	U16	1
output_6_state	565	U16	1
output_7_state	566	U16	1
output_8_state	567	U16	1
ramp_soak_remaining_time	626	U32BE	1
smart_sensor_reading_1	658	F32BE	1
smart_sensor_reading_2	660	F32BE	1
smart_sensor_reading_3	662	F32BE	1
smart_sensor_reading_4	664	F32BE	1

link settings as documented (unverified): RTU/ASCII/TCP; baud 300/600/1200/2400/4800/9600/19200/38400/57600/115200; FC 03,06,07,08,16,11; The Platinum Modbus interface imposes a maximum of 64 bytes for the total transaction.

bench facts as documented (unverified)

connector	USB, RS232, RS485
max registers/read	23
broadcast	supported
protocol notes	Modbus traffic should allow a minimum of 500 msec following a write to non-volatile memory. Standard memory accesses should be limited to 10 transactions / second.
model register	512
firmware register	514
certifications	CE, cULus
doc revision	M5458/0716

generated by gemini:gemini-3.5-flash · harvested from https://assets.omega.com/manuals/M5458.pdf (Omega Engineering); 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.