Siemens SIRIUS 3RW5 soft starter (needs 3RW5 Modbus module)

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	unit
phase_current_l1_rms_float	2497	F32BE	1	A
phase_current_l2_rms_float	2499	F32BE	1	A
phase_current_l3_rms_float	2501	F32BE	1	A
phase_current_avg_rms_float	2503	F32BE	1	A
active_power_float	2631	F32BE	1	W
active_energy_import_total_float	2657	F32BE	1	Wh
remaining_motor_cooling_time	34819	U16	0.1	s
motor_temperature_rise	34821	U16	1
line_voltage_u_l1_l2	34828	U16	0.1	V
line_voltage_u_l2_l3	34829	U16	0.1
line_voltage_u_l3_l1	34830	U16	0.1
phase_current_l1_rms	34831	U32BE	0.01	A
phase_current_l2_rms	34833	U32BE	0.01
phase_current_l3_rms	34835	U32BE	0.01
active_power	34841	U32BE	0.0001	kW
device_operating_hours	35843	U32BE	1	s
motor_starts_cw	35845	U32BE	1
motor_starts_ccw	35847	U32BE	1
motor_overload_trips	35849	U16	1
motor_operating_hours	35855	U32BE	1

link settings as documented (unverified): RTU/TCP; default 19200 8E1; unit ID 126; FC 01,02,03,04,05,06,15,16,23; Supports automatic setting of port configuration and baud rate.

bench facts as documented (unverified)

terminals	6-pin terminal connection for Modbus RTU, RJ45 socket for Modbus TCP
A/B polarity	Com (GND, SC), -/A (D0, D-, RXD/TXD-N), +/B (D1, D+, RXD/TXD-P)
termination	Built-in 120-Ohm terminating resistor activated via jumper between Ter and +/B
shield/ground	Connect cable shield to system ground with low impedance
wiring notes	Line polarization via built-in 560-Ohm resistor pair activated by jumper between PU and PD
max registers/read	125
response timeout	5000 ms
broadcast	supported
protocol notes	Access monitoring time factory setting is 5 seconds (configurable to 5 or 10 seconds). Up to 2000 bits can be read per telegram.
model register	199
serial register	209
firmware register	218
identification notes	I&M0 device identification registers are read-only via FC03 and FC04. FC43 is explicitly not supported.
FC 43 device ID	not supported
doc revision	03/2020 A5E43676481002A/RS-AC/003

field reports — community-sourced, unverified (checked 2026-06-11)

confirmed: comms.default_unit_id: 126 — confirmed by Siemens Equipment Manual (03/2020, A5E43676481002A/RS-AC/003)
confirmed: physical.notes: Line polarization via built-in 560-Ohm resistor pair activated by jumper between PU and PD — confirmed by Siemens Equipment Manual
confirmed: register_map: phase_current_l1_rms @ 34831 (0x880F) — confirmed by Siemens Equipment Manual
confirmed: register_map: line_voltage_u_l1_l2 @ 34828 (0x880C) — confirmed by Siemens Equipment Manual

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.