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

Register map(s) for this device, with a note of how far each has been checked. Addresses are 0-based, as on the wire. Scale and byte order are confirmed only at the hardware-verified rung.

coherence-checked

Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.

point	address (0-based)	type	scale
phase_current_i1	275	U16	0.1
phase_current_i2	276	U16	0.1
phase_current_i3	277	U16	0.1
residual_current_i0_sum	278	U16	0.1
residual_current_measured	279	U16	0.1
average_phase_current_im1	280	U16	0.1
average_phase_current_im2	281	U16	0.1
average_phase_current_im3	282	U16	0.1
peak_demand_phase_current_im1	283	U16	0.1
peak_demand_phase_current_im2	284	U16	0.1
peak_demand_phase_current_im3	285	U16	0.1
phase_to_phase_voltage_u21	286	U16	1
phase_to_phase_voltage_u32	287	U16	1
phase_to_phase_voltage_u13	288	U16	1
phase_to_neutral_voltage_v1	289	U16	1
phase_to_neutral_voltage_v2	290	U16	1
phase_to_neutral_voltage_v3	291	U16	1
residual_voltage_v0	292	U16	1
positive_sequence_voltage_vd	293	U16	1
negative_sequence_voltage_vi	294	U16	1
frequency	295	U16	0.01
active_power_p	296	I16	1
reactive_power_q	297	I16	1
apparent_power_s	298	I16	1
peak_demand_active_power_pm	299	I16	1
peak_demand_reactive_power_qm	300	I16	1
power_factor	301	I16	0.01
positive_active_energy_ea	302	U32BE	100
negative_active_energy_ea	304	U32BE	100
positive_reactive_energy_er	306	U32BE	100
negative_reactive_energy_er	308	U32BE	100
thermal_capacity_used	356	U16	1
temperature_1	364	I16	1
temperature_2	365	I16	1
temperature_3	366	I16	1
temperature_4	367	I16	1
temperature_5	368	I16	1
temperature_6	369	I16	1
temperature_7	370	I16	1
temperature_8	371	I16	1

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)

terminals	Screw terminals on ACE949-2 / ACE959 / ACE969
A/B polarity	L+, L-
termination	Jumper for RS 485 network line-end impedance matching with load resistor (Rc = 150 Ohm)
connector	RJ45 socket to connect the interface to the base unit with a CCA612 cord
isolation	Galvanic isolation between RS 232 and RS 485 interfaces: 1000 Vrms, 50 Hz, 1 min
shield/ground	The interfaces are fitted with clamps to hold the network cable and recover shielding
response timeout	15 ms
broadcast	supported
FC 43 device ID	supported
power	External, 12 V DC or 24 V DC ±10% (or 24 to 250 V DC / 110 to 240 V AC for ACE969)
environment	Operating temperature: -25°C to +70°C
doc revision	06/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.

generated — A prompt produced it. Unproven — anyone can regenerate this.
structure-verified — Decode path is structurally sound (addresses, widths, finite values). Does NOT prove word order or scaling.
coherence-checked — Round-trips through a real Modbus stack with no overlapping addresses and a word-order-sensitive codec — the map is internally coherent and wire-decodable. Does NOT prove byte-order or scaling match a real device: the emulator is seeded from the map's own types, so a uniformly wrong byte-order still round-trips. Only hardware-verified confirms byte-order/scale on the wire.
hardware-verified (software-key) x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

Device not here? Upload its manual and get a checked map back. It's free.

Want it confirmed against your own device? Order hardware verification. If it doesn't check out, you don't pay.

Building on a lot of devices? License the library — machine-readable maps, the firmware matrix, and API access.