verified connector library

SUTO iTEC S111 power sensor

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
voltage_current_phase_sequence_state220U161
phase_a_current1000F32BE1A
phase_b_current1002F32BE1A
phase_c_current1004F32BE1A
average_current1006F32BE1A
phase_n_current1008F32BE1A
phase_a_voltage1010F32BE1V
phase_b_voltage1012F32BE1V
phase_c_voltage1014F32BE1V
average_phase_voltage1016F32BE1V
zero_sequence_voltage1018F32BE1V
line_voltage_ab1020F32BE1V
line_voltage_bc1022F32BE1V
line_voltage_ca1024F32BE1V
average_line_voltage1026F32BE1V
phase_a_active_power1028F32BE1kW
phase_b_active_power1030F32BE1kW
phase_c_active_power1032F32BE1kW
total_active_power1034F32BE1kW
phase_a_reactive_power1036F32BE1kVAR
phase_b_reactive_power1038F32BE1kVAR
phase_c_reactive_power1040F32BE1kVAR
total_reactive_power1042F32BE1kVAR
phase_a_apparent_power1044F32BE1kVA
phase_b_apparent_power1046F32BE1kVA
phase_c_apparent_power1048F32BE1kVA
total_apparent_power1050F32BE1kVA
phase_a_power_factor1052F32BE1
phase_b_power_factor1054F32BE1
phase_c_power_factor1056F32BE1
total_power_factor1058F32BE1
phase_a_frequency1068F32BE1Hz
phase_b_frequency1070F32BE1Hz
phase_c_frequency1072F32BE1Hz
total_frequency1074F32BE1Hz
phase_a_positive_active_energy2600U32BE1kWh
phase_b_positive_active_energy2602U32BE1kWh
phase_c_positive_active_energy2604U32BE1kWh
total_positive_active_energy2606U32BE1kWh
phase_a_reverse_active_energy2608U32BE1kWh
phase_b_reverse_active_energy2610U32BE1kWh
phase_c_reverse_active_energy2612U32BE1kWh
total_reverse_active_energy2614U32BE1kWh
phase_a_positive_reactive_energy2616U32BE1kVARh
phase_b_positive_reactive_energy2618U32BE1kVARh
phase_c_positive_reactive_energy2620U32BE1kVARh
total_positive_reactive_energy2622U32BE1kVARh
phase_a_reverse_reactive_energy2624U32BE1kVARh
phase_b_reverse_reactive_energy2626U32BE1kVARh
phase_c_reverse_reactive_energy2628U32BE1kVARh
total_reverse_reactive_energy2630U32BE1kVARh
phase_a_apparent_energy2632U32BE1kVAh
phase_b_apparent_energy2634U32BE1kVAh
phase_c_apparent_energy2636U32BE1kVAh
total_apparent_energy2638U32BE1kVAh
current_negative_sequence_unbalancedness7000F32BE1
current_zero_sequence_unbalancedness7002F32BE1
voltage_negative_sequence_unbalancedness7004F32BE1
voltage_zero_sequence_unbalancedness7006F32BE1
current_k_factor_phase_a8000F32BE1
current_k_factor_phase_b8002F32BE1
current_k_factor_phase_c8004F32BE1
angle_phase_a_voltage8100F32BE1
angle_phase_b_voltage8102F32BE1
angle_phase_c_voltage8104F32BE1
angle_phase_a_current8106F32BE1
angle_phase_b_current8108F32BE1
angle_phase_c_current8110F32BE1
angle_voltage_current_phase_a8112F32BE1
angle_voltage_current_phase_b8114F32BE1
angle_voltage_current_phase_c8116F32BE1

link settings as documented (unverified): RTU; default 9600 8N1; unit ID 1; FC 03,16; Parameters need to be set via the meter interface before performing Modbus/RTU communication.

bench facts as documented (unverified)
terminalsA, B
connectorRJ12
wiring notesRS-485 communication port
max registers/read125
model register60
serial register70
firmware register72
doc revision2025-2

generated by gemini:gemini-3.5-flash · harvested from https://www.suto-itec.com/wp-content/uploads/2025/05/S111_Modbus-register-table_EN_V2025-2.pdf (SUTO iTEC); 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.