verified connector library

Red Lion PAX2A panel meter

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.

pointaddress (0-based)typescaleunit
input_relative_value0U32BE1
maximum_value2U32BE1
minimum_value4U32BE1
total_value6U32BE1
setpoint_1_value8U32BE1
setpoint_2_value10U32BE1
setpoint_3_value12U32BE1
setpoint_4_value14U32BE1
setpoint_1_band_dev_value16U32BE1
setpoint_2_band_dev_value18U32BE1
setpoint_3_band_dev_value20U32BE1
setpoint_4_band_dev_value22U32BE1
setpoint_output_register24U161
manual_mode_register25U161
reset_output_register26U161
analog_output_register27U161
input_absolute_value28U32BE1
input_offset_value30U32BE1

link settings as documented (unverified): RTU/ASCII; default 38400 8N?; unit ID 247; Type factory setting is Modbus ASCII (2). Data bits factory setting is 8 bits (1).

bench facts as documented (unverified)
max registers/read32
protocol notesMaximum 32 register writes and 32 register reads.
model register41001
firmware register41001
identification notesSlave ID register 41001-41010 contains model 'RLC-PAX2A' and version number.
doc revision4/15/13 LP0931A

generated by gemini:gemini-3.5-flash · harvested from https://files.valinonline.com/userfiles/ct/documents/red-lion-controls/red-lion-pax2a-register-table.pdf (Red Lion); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; 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.

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.