Shimaden SR23 controller (needs comms option)

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.

point	address (0-based)	type	scale	unit
pv_value	256	I16	1
execution_sv_value	257	I16	1
control_output_1	258	I16	0.1	%
control_output_2	259	I16	0.1	%
operation_flag	260	U16	1
event_output_flag	261	U16	1
execution_sv_no	262	U16	1
execution_pid_no	263	U16	1
remote_input_value	264	I16	1
hb_current_value	265	U16	0.1	A
hl_current_value	266	U16	0.1	A
di_input_state_flag	267	U16	1
ch1_pv_measuring_range	640	I16	1
ch2_pv_measuring_range	641	I16	1
sv_no_1	768	I16	1
sv_no_2	769	I16	1
sv_no_3	770	I16	1
sv_no_4	771	I16	1
sv_no_5	772	I16	1
sv_no_6	773	I16	1
sv_no_7	774	I16	1
sv_no_8	775	I16	1
sv_no_9	776	I16	1
sv_no_10	777	I16	1

link settings as documented (unverified): RTU/ASCII; default 9600 8E1; unit ID 1; FC 03,06; Supports both SHIMADEN standard protocol and MODBUS communication protocol.

⚠ To prevent uncontrollable situations such as host program runaway, communication between the SR23 and the host can be forcibly terminated by holding down the ENT and STEP keys simultaneously for at least three seconds. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	RS-232C: SD(3), RD(2), SG(5) on host to RD(14), SD(13), SG(12) on controller. RS-485: +(13), -(14), SG(12)
A/B polarity	Mark state: - terminal < + terminal, Space state: - terminal > + terminal
termination	Attach a terminator of about 1/2W 120Ω to the endmost terminal (between + and - terminals)
shield/ground	FG
wiring notes	RS-232C max distance 15m, RS-485 max distance 500m. RS-485 supports up to 31 devices.
broadcast	supported
sentinel values	Sc.HH/Cj.HH/b = 7FFFH, Sc.LL/Cj.LL = 8000H, HBL/HLA display = 7FFFH, HB current value when output is OFF and HL current value when output is ON = 7FFEH
protocol notes	In tri-state control, a delay of about 1 msec (max) after end of transmission of the end bit of the end character up to the return from high impedance is generated. It sometimes takes about 400 ms to process commands in the case of the write command.
model register	0040
identification notes	Series codes 1 to 4 are located at registers 0040H to 0043H (64 to 67).
doc revision	MSR23-E04-B, Feb. 2015

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

confirmed: comms defaults (baud rates [2400, 4800, 9600, 19200], default baud 9600, default unit ID 1, framing [RTU, ASCII], parity E, stop bits 1, function codes [3, 6]) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B
confirmed: control_warning (forcibly terminating communication by holding down ENT and STEP keys for at least 3 seconds) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B
confirmed: identification (model register 0040H to 0043H for series codes 1 to 4) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B
confirmed: physical (RS-232C max distance 15m, RS-485 max distance 500m, RS-485 supports up to 31 devices, polarity, terminals, and 120 ohm termination) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B
confirmed: quirks (broadcast support, tri-state delay of about 1 msec max, write command processing delay up to 400 ms, and sentinels like 7FFFH, 8000H, 7FFEH) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B
confirmed: register map summary (pv_value @ 256, execution_sv_value @ 257, control_output_1 @ 258, control_output_2 @ 259, operation_flag @ 260, event_output_flag @ 261, execution_sv_no @ 262, execution_pid_no @ 263, remote_input_value @ 264, hb_current_value @ 265, hl_current_value @ 266, di_input_state_flag @ 267, ch1_pv_measuring_range @ 640, ch2_pv_measuring_range @ 641, sv_no_1 @ 768 to sv_no_10 @ 777) — confirmed by the SR23 Series Digital Controller Instruction Manual (Detailed version) MSR23-E04-B

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.
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.
simulator-verified — Decoded correctly against a protocol emulator seeded with known-true values — catches word-order/scaling errors vs the emulator, not the physical device.
hardware-verified x1 — Matched a real device with operator-attested readings as ground truth — the only rung that confirms word order + scaling on the wire.

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.