verified connector library

Onicon System-10 BTU meter (needs MOD interface card)

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.

pointaddress (0-based)typescaleunit
meter_operating_mode_indicator1000U161
mode_status_indicator1001U161
energy_rate_btu_hr1002F32BE1Btu/Hr
energy_rate_kw1004F32BE1kW
energy_rate_tons1006F32BE1Tons
volume_rate_gpm1008F32BE1GPM
volume_rate_gph1010F32BE1GPH
volume_rate_mgd1012F32BE1MGD
volume_rate_l_s1014F32BE1L/S
volume_rate_l_m1016F32BE1L/M
volume_rate_l_h1018F32BE1L/H
volume_rate_m3_hr1020F32BE1M³/Hr
volume_rate_ft3_s1070F32BE1Ft³/S
volume_rate_ft3_m1072F32BE1Ft³/M
mass_rate_lb_hr1022F32BE1Lb/Hr
mass_rate_kg_hr1024F32BE1Kg/Hr
supply_temp_f1026F32BE1°F
return_temp_f1028F32BE1°F
supply_temp_c1030F32BE1°C
return_temp_c1032F32BE1°C
energy_total_mode_1_btu1034F32BE1Btu
energy_total_mode_2_btu1036F32BE1Btu
energy_total_mode_1_tonhr1038F32BE1TonHr
energy_total_mode_2_tonhr1040F32BE1TonHr
energy_total_mode_1_kwhr1042F32BE1kWHr
energy_total_mode_2_kwhr1044F32BE1kWHr
volume_total_mode_1_gal1046F32BE1Gal
volume_total_mode_2_gal1048F32BE1Gal
volume_total_mode_1_liters1050F32BE1Liters
volume_total_mode_2_liters1052F32BE1Liters
volume_total_mode_1_m31054F32BE1
volume_total_mode_2_m31056F32BE1
volume_total_mode_1_ft31078F32BE1Ft³
volume_total_mode_2_ft31080F32BE1Ft³
mass_total_lbs1058F32BE1Lbs
mass_total_kg1060F32BE1kg
auxiliary_input_total_di31062F32BE1
supply_temp_f_int21U160.01°F
return_temp_f_int22U160.01°F
supply_temp_c_int23I160.01°C
return_temp_c_int24I160.01°C

link settings as documented (unverified): RTU/TCP; default 9600 8N1; unit ID 17; FC 03,06,16,17; RS485 transceiver is 2-wire, half-duplex. TCP/IP transceiver is 10Base T, 10Mbps, RJ45 connection.

bench facts as documented (unverified)
terminalsTerminal T1 for RS485, Terminal T2 for Aux Pulse Input (Di3)
A/B polarityRS485 network cable connections are polarity sensitive (+ to + and - to -)
terminationJumper selectable 120 Ohm resistor
connectorRJ45 for TCP/IP, screw terminals for RS485
shield/groundIncoming and outgoing RS485 cable shield wires should be connected together, but must not be connected to the Btu meter.
protocol notesResetting totals requires writing a 1 to a register, which takes longer to accomplish than reading registers and can lead to timeout issues.
power24 VAC input
doc revision07-18
field reports — community-sourced, unverified (checked 2026-06-11)
  • confirmed: Baud rates [1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200] and default baud 9600 — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Default unit ID 17 (represented as 017) — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Framing RTU and TCP, and supported function codes 3, 6, 16, 17 — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: RS485 transceiver is 2-wire half-duplex, and TCP/IP is 10Base T, 10Mbps, RJ45 — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Parity N and Stop bits 1 — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Shield ground wires must be connected together but not to the Btu meter — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Terminal T1 for RS485 and Terminal T2 for Aux Pulse Input (Di3) — confirmed by System-10-MOD Network Interface Installation Guide
  • confirmed: Jumper selectable 120 Ohm termination resistor — confirmed by System-10-MOD Network Interface Installation Guide

The trust ladder

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.