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 | 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 |
⚠ disputed: Baud rates of 300, 600, and 38400 are supported — disputed by Section 6.6.3.2 of the Omega Platinum Series Temperature & Process Controllers User Manual (M5451) and Section 10.2 of the Platinum Series Datasheet, which state that the supported baud rates are 1200, 2400, 4800, 9600, 19200, 57600, and 115200
field reports — community-sourced, unverified (checked 2026-06-11)
- The vendor manual (M5458/0716) contains a typo in the 'Index' column for the Smart Sensor Readings. It lists the decimal indices as 658, 659, 660, and 661, but because these are 32-bit floats (occupying 2 registers each), the actual decimal indices corresponding to the hex addresses (0x0292, 0x0294, 0x0296, 0x0298) are 658, 660, 662, and 664. [source]
- For RTU formatted packets, Modbus requires specific inter-frame character timing to determine framing. This timing is not available over a generic virtual comm channel across USB, which collects serial data into 64-byte packets for transmission based on the USB end-point buffer size. The USB Modbus RTU interface relies on the USB channel collecting data into 64-byte packets. [source]
- The default LabVIEW Modbus driver provided by Omega assumes a setting of 8 data bits and 1 stop bit for Modbus RTU, which can cause communication failures if the device is configured with 2 stop bits. [source]
- Users attempting to communicate with the Omega Platinum Series Meter through micro-USB using the provided LabVIEW driver example often encounter a timeout error 6101 due to serial port configuration issues. [source]
- confirmed: Framing options of RTU, ASCII, and TCP are supported — confirmed by Section 1.1 of the Omega Platinum Modbus Interface manual (M5458/0716)
- confirmed: Supported Modbus function codes are 3, 6, 7, 8, 16, and 11 — confirmed by Section 2.1 of the Omega Platinum Modbus Interface manual (M5458/0716)
- confirmed: The Modbus interface imposes a maximum transaction limit of 64 bytes — confirmed by Section 2.0 of the Omega Platinum Modbus Interface manual (M5458/0716)
- confirmed: Device identification registers are 512 (Device ID) and 514 (Version Number) — confirmed by Section 3.0 of the Omega Platinum Modbus Interface manual (M5458/0716)
- confirmed: Quirks such as broadcast support on address 0, a maximum of 23 read registers for RTU/TCP, and timing constraints (500 ms delay after non-volatile writes, max 10 transactions/sec) — confirmed by Section 2.0 and 3.0 of the Omega Platinum Modbus Interface manual (M5458/0716)
- confirmed: Register map summary addresses (e.g., current_input_value @ 528, smart_sensor_value @ 534, input_digital @ 542, current_setpoint_1 @ 544, current_setpoint_2 @ 546, control_setpoint @ 548, peak_value @ 550, valley_value @ 552, pid_output @ 554, current_input_valid @ 556, alarm_state @ 557, ramp_soak_state @ 558, output_1_state @ 560, output_2_state @ 561, output_3_state @ 562, output_4_state @ 563, output_5_state @ 564, output_6_state @ 565, output_7_state @ 566, output_8_state @ 567, ramp_soak_remaining_time @ 626) — confirmed by Section 3.0 of the Omega Platinum Modbus Interface manual (M5458/0716)