Fuji PXR temperature controller

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 only confirmed at the hardware-verified rung.

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
process_value	1000	I16	1	°C/°F
current_set_value	1001	I16	1	°C/°F
current_deviation	1002	I16	1	°C/°F
manipulated_value_1	1003	I16	0.01	%
manipulated_value_2	1004	I16	0.01	%
heater_current	1009	I16	0.1	A
sv_controlled_on_face_panel	1002	I16	1	°C/°F
proportional_band	1005	U16	0.1	%
integral_time	1006	U16	0.1	s
derivative_time	1007	U16	0.1	s
cooling_proportional_band_coefficient	1009	U16	0.1	A
dead_band	1010	I16	0.01	s
heater_burnout_alarm_set_value	1038	U16	0.1	A

link settings as documented (unverified): RTU; default 9600 8O1; unit ID 1; FC 01,02,03,04,05,06,16; Transmission speed, data length, and stop bit are fixed.

⚠ For avoiding electric shock and malfunctions, do not turn on the power supply until all wiring have been completed. — Starkest reads only; we never write a control register.

bench facts as documented (unverified)

terminals	7 (+), 8 (-)
A/B polarity	7 is +, 8 is -
termination	Both ends of the cable should be terminated with terminating resistors 100 ohm 1/2W
connector	Terminal block
isolation	Functional isolation between transmission circuit and others (withstand voltage: 500V AC)
shield/ground	The shield wire of the cable should be grounded at one place on the master station unit side.
wiring notes	Recommended cable: UL2464, UL2448, etc. Recommended noise filter: ZRAC2203-11/TDK
max registers/read	60
broadcast	not supported
protocol notes	While the data is being written in non-volatile memory after write via communication, the next write is attempted and will result in no response.
FC 43 device ID	not supported
doc revision	INP-TN512642a-E

generated by gemini:gemini-3.5-flash · harvested from https://www.instrumart.com/assets/PXR%20MODBUS%20Protocol.pdf (Fuji Electric); manual-faithful — the document's claims, panel risk: ELEVATED — panel is not confident; proved interop-verified on 2026-06-10 · recorded 2026-06-10

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.

Have a device that isn't here? Upload its register map — generation is free, and the connector earns its rung by being proven, not claimed.

Need it proven on your own device? Hardware verification — if it doesn't verify, you don't pay.

Building a platform? License the verified library — machine-readable maps, firmware matrix, API access.