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.
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_value | 1302 | F32BE | 1 | |
| sv_value | 1304 | F32BE | 1 | |
| tv_value | 1306 | F32BE | 1 | |
| qv_value | 1308 | F32BE | 1 | |
| pv_units_code | 104 | U16 | 1 | |
| sv_units_code | 108 | U16 | 1 | |
| tv_units_code | 112 | U16 | 1 | |
| qv_units_code | 116 | U16 | 1 | |
| blocking_distance | 3100 | F32BE | 1 | Level Units |
| level_unit_code | 2140 | U16 | 1 | |
| level_offset | 3102 | F32BE | 1 | Level Units |
| sensitivity | 3131 | U16 | 1 | |
| level_threshold_amplitude | 3134 | U16 | 1 | |
| interface_threshold_amplitude | 3135 | U16 | 1 |
| terminals | RS-485 terminal block (TB2) with Receive/Transmit Data+ A and Receive/Transmit Data- B. TB2 is also used for RS-232 when DIP switches 3 and 4 are set to RS-232 mode. |
| A/B polarity | A connects to '-' position, B connects to '+' position |
| termination | 120 Ohm resistor between the two RS-485 terminal block positions |
| wiring notes | Supports up to five attached HART devices (one in the same housing, up to four external). |
| inter-frame delay | 8 ms |
| protocol notes | HMA typically responds within about 8 milliseconds. Unkey Delay on master should be less than 7 milliseconds. |
| model register | 1002 |
| serial register | 1213 |
| firmware register | 1205 |
| power | 9 to 30 VDC @ 200mA |
| doc revision | BULLETIN: 41-621.0, March 2015 |
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.