verified connector library

Setra Power Patrol power 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
vin1_l1_n104F32BE1V
vin1_l2_n106F32BE1V
vin1_l3_n108F32BE1V
vin1_l1_l2110F32BE1V
vin1_l2_l3112F32BE1V
vin1_l3_l1114F32BE1V
vin1_freq128F32BE1hertz
vin2_l1_n152F32BE1V
vin2_l2_n154F32BE1V
vin2_l3_n156F32BE1V
vin2_l1_l2158F32BE1V
vin2_l2_l3160F32BE1V
vin2_l3_l1162F32BE1V
vin2_freq176F32BE1hertz
total_kwh324F32BE1kWh
total_kwh_plus326F32BE1kWh
total_kwh_minus328F32BE1kWh
total_kvarh330F32BE1kvarh
total_amperage352F32BE1A
total_kw354F32BE1kW
total_kvar356F32BE1kvar
total_kva358F32BE1kVA
total_apf360F32BE1power-factor
total_dpf362F32BE1power-factor
phase_l1_kwh404F32BE1kWh
phase_l1_amps430F32BE1A
phase_l1_kw432F32BE1kW
phase_l1_kvar434F32BE1kvar
phase_l1_kva436F32BE1kVA
phase_l1_apf438F32BE1power-factor
phase_l2_kwh464F32BE1kWh
phase_l2_amps490F32BE1A
phase_l2_kw492F32BE1kW
phase_l2_kvar494F32BE1kvar
phase_l2_kva496F32BE1kVA
phase_l2_apf498F32BE1power-factor
phase_l3_kwh524F32BE1kWh
phase_l3_amps550F32BE1A
phase_l3_kw552F32BE1kW
phase_l3_kvar554F32BE1kvar
phase_l3_kva556F32BE1kVA
phase_l3_apf558F32BE1power-factor

link settings as documented (unverified): RTU/TCP; Data Format: Big-Endian (high byte first, or most significant byte first)

bench facts as documented (unverified)
model register30042
serial register30050
firmware register30058
doc revisionSS-SPM-MODBUS_G
field reports — community-sourced, unverified (checked 2026-06-11)
  • confirmed: comms framing: RTU, TCP — confirmed by Setra Power Patrol product documentation and BACnet PICS [1.3.9]
  • confirmed: Data Format: Big-Endian (high byte first, or most significant byte first) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: doc_revision: SS-SPM-MODBUS_G — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: identification registers (firmware: 30058, model: 30042, serial: 30050) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: vin1 voltage and frequency registers (vin1_l1_n @ 104, vin1_l2_n @ 106, vin1_l3_n @ 108, vin1_l1_l2 @ 110, vin1_l2_l3 @ 112, vin1_l3_l1 @ 114, vin1_freq @ 128) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: vin2 voltage and frequency registers (vin2_l1_n @ 152, vin2_l2_n @ 154, vin2_l3_n @ 156, vin2_l1_l2 @ 158, vin2_l2_l3 @ 160, vin2_l3_l1 @ 162, vin2_freq @ 176) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: total energy and power registers (total_kwh @ 324, total_kwh_plus @ 326, total_kwh_minus @ 328, total_kvarh @ 330, total_amperage @ 352, total_kw @ 354, total_kvar @ 356, total_kva @ 358, total_apf @ 360, total_dpf @ 362) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)
  • confirmed: phase L1 registers (phase_l1_kwh @ 404, phase_l1_amps @ 430, phase_l1_kw @ 432, phase_l1_kvar @ 434, phase_l1_kva @ 436, phase_l1_apf @ 438) — confirmed by Setra Power Meter Modbus Register Master List (SS-SPM-MODBUS_G)

generated by gemini:gemini-3.5-flash · harvested from https://www.setra.com/hubfs/modbus-register-list.pdf (Setra); 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.