verified connector library

Schneider Sepam series 40 relay (needs ACE949/959 interface)

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
phase_current_i1275U160.1
phase_current_i2276U160.1
phase_current_i3277U160.1
residual_current_i0_sum278U160.1
residual_current_measured279U160.1
average_phase_current_im1280U160.1
average_phase_current_im2281U160.1
average_phase_current_im3282U160.1
peak_demand_phase_current_im1283U160.1
peak_demand_phase_current_im2284U160.1
peak_demand_phase_current_im3285U160.1
phase_to_phase_voltage_u21286U161
phase_to_phase_voltage_u32287U161
phase_to_phase_voltage_u13288U161
phase_to_neutral_voltage_v1289U161
phase_to_neutral_voltage_v2290U161
phase_to_neutral_voltage_v3291U161
residual_voltage_v0292U161
positive_sequence_voltage_vd293U161
negative_sequence_voltage_vi294U161
frequency295U160.01
active_power_p296I161
reactive_power_q297I161
apparent_power_s298I161
peak_demand_active_power_pm299I161
peak_demand_reactive_power_qm300I161
power_factor301I160.01
positive_active_energy_ea302U32BE100
negative_active_energy_ea304U32BE100
positive_reactive_energy_er306U32BE100
negative_reactive_energy_er308U32BE100
thermal_capacity_used356U161
temperature_1364I161
temperature_2365I161
temperature_3366I161
temperature_4367I161
temperature_5368I161
temperature_6369I161
temperature_7370I161
temperature_8371I161

link settings as documented (unverified): RTU; default 19200 8E1; unit ID 1; FC 01,02,03,04,05,06,07,15,16,08,11,43; Modbus TCP is also supported via the ACE850 interface.

bench facts as documented (unverified)
terminalsScrew terminals on ACE949-2 / ACE959 / ACE969
A/B polarityL+, L-
terminationJumper for RS 485 network line-end impedance matching with load resistor (Rc = 150 Ohm)
connectorRJ45 socket to connect the interface to the base unit with a CCA612 cord
isolationGalvanic isolation between RS 232 and RS 485 interfaces: 1000 Vrms, 50 Hz, 1 min
shield/groundThe interfaces are fitted with clamps to hold the network cable and recover shielding
response timeout15 ms
broadcastsupported
FC 43 device IDsupported
powerExternal, 12 V DC or 24 V DC ±10% (or 24 to 250 V DC / 110 to 240 V AC for ACE969)
environmentOperating temperature: -25°C to +70°C
doc revision06/2025
field reports — community-sourced, unverified (checked 2026-06-11)
  • When using the ACE959 (4-wire interface) on a 2-wire RS485 network by jumpering Tx+ to Rx+ and Tx- to Rx-, there is an inversion of polarities inside the ACE959 design. The Tx+/Rx+ (B/B') gathering wire must be connected to the L- terminal of the ACE909-2 converter, and the Tx-/Rx- (A/A') gathering wire must be connected to the L+ terminal. [source]
  • confirmed: Baud rates [4800, 9600, 19200, 38400] and default baud 19200 — confirmed by Schneider Sepam S40 Modbus Communication Guide and S7-1200 integration guides
  • confirmed: Register map addresses (e.g., phase_current_i1 @ 275, phase_current_i2 @ 276, phase_current_i3 @ 277, power_factor @ 301) — confirmed by Schneider Electric Modbus Registers Map and Siemens S7-1200 integration guides
  • confirmed: ACE949-2 physical characteristics (RJ45 socket, CCA612 cord, L+/L- polarity, 150 Ohm termination jumper, and -25°C to +70°C operating temperature) — confirmed by ACE949-2 2-Wire RS485 Network Interface Instruction Bulletin

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.