verified connector library

GE Multilin 369 motor management relay

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
motor_status512U161
motor_thermal_capacity_used513U161%
estimated_time_to_trip_on_overload514I161s
restart_attempts515U161
restart_total_delay516U161sec.
restart_in_progress517U161
uvr_power_loss_time518U160.10.1 s
motor_speed_status519U161
cause_of_last_trip544U161
phase_a_pre_trip_current550U161A
phase_b_pre_trip_current552U161A
phase_c_pre_trip_current554U161A
motor_load_pre_trip556U160.01FLA
current_unbalance_pre_trip557U161%
ground_current_pre_trip558U160.1A
phase_a_current768U161
phase_b_current770U161
phase_c_current772U161
average_phase_current774U161
motor_load776U160.01
current_unbalance777U161
unbalanced_biased_motor_load778U160.01
ground_current779U160.1
overall_hottest_stator_rtd_owner796U161
overall_hottest_stator_rtd_number797U161
overall_hottest_stator_rtd_temperature798I161
local_hottest_stator_rtd_number799U161
local_hottest_stator_rtd_temperature800I161
local_rtd_1_temperature801I161
local_rtd_2_temperature802I161
local_rtd_3_temperature803I161
local_rtd_4_temperature804I161
local_rtd_5_temperature805I161
local_rtd_6_temperature806I161
local_rtd_7_temperature807I161
local_rtd_8_temperature808I161
local_rtd_9_temperature809I161
local_rtd_10_temperature810I161
local_rtd_11_temperature811I161
local_rtd_12_temperature812I161
vab864U161
vbc865U161
vca866U161
average_line_voltage867U161
van868U161
vbn869U161
vcn870U161
average_phase_voltage871U161
system_frequency872U160.01
power_factor880I160.01
real_power881I161
real_power_hp883U161
reactive_power884I161
apparent_power886U161
positive_megawatthours887U161
positive_megavarhours889U161
negative_megavarhours891U161
positive_kilowatthours893U161
positive_kilovarhours895U161
negative_kilovarhours897U161
current_demand912U161
real_power_demand914U161
reactive_power_demand916U161
apparent_power_demand918U161
peak_current_demand919U161
peak_real_power_demand921U161
peak_reactive_power_demand923U161
peak_apparent_power_demand925U161
number_of_motor_starts1136U161
number_of_emergency_restarts1137U161
motor_running_hours1184U161

link settings as documented (unverified): RTU; baud 1200/2400/4800/9600/19200; unit ID 254; FC 03,04,05,06,07,08,16; Modbus is a single master, multiple slave protocol. Up to 32 slaves can be daisy-chained together on a single communication channel.

bench facts as documented (unverified)
terminalsone of three 2-wire RS485 ports from the rear terminal connector, the RS232 from the front panel connector, a fibre optic connection
A/B polarityEach '+' terminal of every 369 must be connected together for the system to operate.
terminationThe terminating network should consist of a 120 ohm resistor in series with a 1 nF ceramic capacitor when used with Belden 9841 RS485 wire.
connectorrear terminal connector, front panel connector, RJ45 connector
shield/groundShielded wire should always be used to minimize noise.
max registers/read125
inter-frame delay3 ms
broadcastsupported
model register0x0000
serial register0x0020
firmware register0x0002
certificationsCE, UL, ISO9001:2000
doc revision3.4x

generated by gemini:gemini-3.5-flash · harvested from https://www.gegridsolutions.com/products/support/369/gek-113493c.pdf (GE Grid Solutions); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-11 · recorded 2026-06-11

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.