Autonics TK series PID controller (RS485 models)

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	1000	I16	1	℃/℉/-
decimal_point_location	1001	U16	1
indicator_unit	1002	U16	1
sv_setting_value_read	1003	I16	1	℃/℉/-
heating_side_mv_read	1004	U16	0.1	%
cooling_side_mv_read	1005	U16	0.1	%
indicator_status_word	1006	U16	1
heater_current_value_monitoring	1007	U16	0.1
sv_set_value	0	I16	1	℃/℉/-
heating_mv	1	U16	0.1	%
cooling_mv	2	U16	0.1	%
auto_manual_control	3	U16	1
control_output_run_stop	50	U16	1
multi_sv_number	51	U16	1
heater_current_monitoring	52	U16	0.1	A
alarm_output_1_low_limit	53	I16	1	℃/℉/-
alarm_output_1_high_limit	54	I16	1	℃/℉/-
alarm_output_2_low_limit	55	I16	1	℃/℉/-
alarm_output_2_high_limit	56	I16	1	℃/℉/-
sv_0	57	I16	1	℃/℉/-
sv_1	58	I16	1	℃/℉/-
sv_2	59	I16	1	℃/℉/-
sv_3	60	I16	1	℃/℉/-
alarm_output_3_low_limit	61	I16	1	℃/℉/-
alarm_output_3_high_limit	62	I16	1	℃/℉/-

link settings as documented (unverified): RTU; default 9600 8N2; unit ID 1; FC 01,02,03,04,05,06,16

bench facts as documented (unverified)

terminals	AWG 20 (0.50mm²) screw bolt on terminal block
A/B polarity	Please wire properly after checking the terminal polarity when connecting temperature sensor.
response timeout	20 ms
broadcast	not supported
model register	300105
serial register	300101
firmware register	300103
doc revision	MCT-TKC1-V01.7-1701EN

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

confirmed: comms defaults (baud_rates: [2400, 4800, 9600, 19200, 38400], default_baud: 9600, default_unit_id: 1, framing: ['RTU'], parity: 'N', stop_bits: 2) — confirmed by Autonics TK Series User Manual for Communication (MCT-TKC1-V01.7-1701EN) and plc247.com integration guide
confirmed: identification registers (firmware_register: 300103, model_register: 300105, serial_register: 300101) — confirmed by Autonics TK Series User Manual for Communication (MCT-TKC1-V01.7-1701EN) Read Input Registers (Func 04) table
confirmed: physical wiring and terminals (AWG 20 screw bolt on terminal block, check polarity when connecting temperature sensor) — confirmed by Autonics TK Series User Manual for Communication (MCT-TKC1-V01.7-1701EN) safety precautions and wiring specifications
confirmed: quirks (broadcast not supported, response timeout default 20ms) — confirmed by Autonics TK Series User Manual for Communication (MCT-TKC1-V01.7-1701EN) and plc247.com integration guide
confirmed: register map summary (pv @ 1000, decimal_point_location @ 1001, sv_set_value @ 0, heating_mv @ 1, cooling_mv @ 2, auto_manual_control @ 3) — confirmed by Autonics TK Series User Manual for Communication (MCT-TKC1-V01.7-1701EN) Modbus Mapping Table

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.