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 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
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

⚠ disputed: terminals: "7 (+), 8 (-)" and polarity: "7 is +, 8 is -" — disputed by the official manual [3.4.1]. This terminal allocation is only correct for the PXR4 model. The PXR3 uses terminals 15 (+) and 14 (-), while the PXR5 and PXR9 use terminals 1 (+) and 2 (-).

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

The Process Value (PV) at register 31001 (relative address 1000) is located in the read-only Input Register space (3xxxx) and must be read using Modbus Function Code 04H. Attempting to read it using Function Code 03H (Read Holding Registers) is a common integration pitfall that will result in a Modbus exception response. [source]
During the non-volatile memory write-in (FIX) process triggered by writing 1 to register 40001/41001, the controller will not respond to any incoming Modbus commands for approximately 5 seconds. [source]
confirmed: Document revision INP-TN512642a-E matches the Fuji Electric Micro Controller X (PXR) RS-485 Modbus Communication Manual [1.2.3].
confirmed: Default communication settings are 9600 bps, 8 data bits, 1 stop bit, and Odd parity (CoM = 0), with a default station number (unit ID) of 1.
confirmed: Modbus RTU communication is prohibited if the station number is set to 0, meaning broadcast is not supported.

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.