Watlow EZ-ZONE PM 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
analog_input_1_process_value	360	F32LE	1	°F
analog_input_1_error_status	362	U16	1
analog_input_2_process_value	440	F32LE	1	°F
analog_input_2_error_status	442	U16	1
digital_output_5_output_state	1012	U16	1
digital_input_5_event_status	1328	U16	1
digital_output_6_output_state	1042	U16	1
digital_input_6_event_status	1348	U16	1
limit_low_set_point	684	F32LE	1	°F
limit_high_set_point	686	F32LE	1	°F
limit_state	690	U16	1
monitor_control_mode_active	1882	U16	1
monitor_heat_power	1904	F32LE	1	%
monitor_cool_power	1906	F32LE	1	%
monitor_closed_loop_active_set_point	2172	F32LE	1	°F
monitor_open_loop_active_set_point	2174	F32LE	1
monitor_alarm_1_state	1496	U16	1
monitor_alarm_2_state	1546	U16	1
monitor_alarm_3_state	1596	U16	1
monitor_alarm_4_state	1646	U16	1
monitor_ambient_temperature_input_1	366	F32LE	1
monitor_ambient_temperature_input_2	446	F32LE	1
monitor_control_loop_output_power	1908	F32LE	1	%
loop_closed_loop_set_point	2160	F32LE	1	°F

link settings as documented (unverified): RTU/TCP; default 9600 8N1; unit ID 1; FC 03,05,06,16; Default serial data format is 9600 baud, 8 data bits, no parity, 1 stop bit. Modbus RTU is typically deployed over serial connections, Modbus TCP over Ethernet.

bench facts as documented (unverified)

terminals	Slot C (A to CA, B to CB, GND to CC)
A/B polarity	A to CA, B to CB
connector	Slot C
wiring notes	EIA-485 converter connects to slot C.
response timeout	1000 ms
inter-frame delay	0 ms
protocol notes	Excessive writes to the PM may cause premature EEPROM failure. EEPROM is rated for 1,000,000 writes. By default, settings made through the network are not saved to nonvolatile memory.
model register	0
firmware register	2
identification notes	Hardware ID is at register 0, Firmware ID is at register 2, Software Revision is at register 4.
doc revision	0600-0056-0000 Rev. B, November 2007

generated by gemini:gemini-3.5-flash · harvested from https://www.thermoelectric.com/2016/manuals/tc-3400/TC-3400%20comms.pdf (Watlow); 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.