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.
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 |
|---|---|---|---|---|
| modbus_status_register | 0 | U16 | 1 | |
| tank_1_status | 1 | U32BE | 1 | |
| tank_1_total_height | 3 | U32BE | 0.1 | 0.1 in or 1 mm |
| tank_1_gross_volume | 5 | U32BE | 1 | GL or LT |
| tank_1_net_volume | 7 | U32BE | 1 | GL or LT |
| tank_1_percent_volume | 9 | U32BE | 0.1 | 0.1 % |
| tank_1_product_temperature | 11 | U32BE | 0.1 | 0.1 °F or 0.1 °C |
| tank_1_water_height | 13 | U32BE | 0.1 | 0.1 in or 1 mm |
| tank_1_ullage | 15 | U32BE | 1 | GL or LT |
| tank_2_status | 17 | U32BE | 1 | |
| tank_2_total_height | 19 | U32BE | 0.1 | |
| tank_2_gross_volume | 21 | U32BE | 1 | |
| tank_2_net_volume | 23 | U32BE | 1 | |
| tank_2_percent_volume | 25 | U32BE | 0.1 | |
| tank_2_product_temperature | 27 | U32BE | 0.1 | |
| tank_2_water_height | 29 | U32BE | 0.1 | |
| tank_2_ullage | 31 | U32BE | 1 | |
| tank_3_status | 33 | U32BE | 1 | |
| tank_3_total_height | 35 | U32BE | 0.1 | |
| tank_3_gross_volume | 37 | U32BE | 1 | |
| tank_3_net_volume | 39 | U32BE | 1 | |
| tank_3_percent_volume | 41 | U32BE | 0.1 | |
| tank_3_product_temperature | 43 | U32BE | 0.1 | |
| tank_3_water_height | 45 | U32BE | 0.1 | |
| tank_3_ullage | 47 | U32BE | 1 | |
| tank_4_status | 49 | U32BE | 1 | |
| tank_4_total_height | 51 | U32BE | 0.1 | |
| tank_4_gross_volume | 53 | U32BE | 1 | |
| tank_4_net_volume | 55 | U32BE | 1 | |
| tank_4_percent_volume | 57 | U32BE | 0.1 | |
| tank_4_product_temperature | 59 | U32BE | 0.1 | |
| tank_4_water_height | 61 | U32BE | 0.1 | |
| tank_4_ullage | 63 | U32BE | 1 | |
| sensors_1_4_status | 193 | U16 | 1 | |
| sensors_5_8_status | 194 | U16 | 1 | |
| sensors_9_12_status | 195 | U16 | 1 | |
| sensors_13_16_status | 196 | U16 | 1 | |
| contact_closures_1_4_status | 203 | U16 | 1 | |
| contact_closures_5_8_status | 204 | U16 | 1 | |
| contact_closures_9_12_status | 205 | U16 | 1 | |
| contact_closures_13_16_status | 206 | U16 | 1 |
⚠ WARNING! Turn power OFF before installing or removing any circuit cards. — Starkest reads only; we never write a control register.
| terminals | Plug-In Terminal Block with Wire Entries |
| A/B polarity | Input: Ch. A (+), Ch. B (-), Shield; Output: Ch. A (+), Ch. B (-), Shield |
| termination | 120-ohm resistor. This is accomplished by setting the LINE TERMINATION switch to 'ON' |
| connector | Plug-in terminal block TB1 |
| isolation | Available in Non-Isolated and Isolated versions depending on P/N |
| shield/ground | SHD |
| wiring notes | Maximum Cable Length: 4000 Feet/1200 Meters total to end of run |
| max registers/read | 64 |
| response timeout | 400 ms |
| sentinel values | the MODBUS processor will force all tank data to full positive scale except ullage, which will be forced to zero |
| protocol notes | Typically, the entire MODBUS register set is updated every 0.8 to 1.2 seconds, and the MSR communications status bit is set to '1' after 10 seconds of failed TMS/LC2000 communications. |
| identification notes | Microprocessor/Firmware (labelled with firmware version in format PMxxxS |
| doc revision | MODBUS RTU Instruction Manual - 2021-09-21.docx |
| firmware applicability | LC2000 ALL, TMS1000 V1x.xx.04, TMS2000 V2x.99.9A/V2x.00.05/V2x.01.xx, TMS2000W V4x.00.xx/V4x.01.xx, TMS3000 V3x.99.9A/V3x.00.05/V3x.01.xx, TMS4000 ALL, TMS4000W ALL |
⚠ disputed: termination: 120-ohm resistor. This is accomplished by setting the LINE TERMINATION switch to 'ON' — disputed by field reports indicating that the switch labeling is counterintuitive: 'OFF' enables the resistor and 'ON' disables it [3.3.9]
Each rung states what it proved and what it did not. Gray until proven; green is earned by hardware only.
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.