Watlow® EZ-Zone® PM
ProcessView+ for the Watlow EZ-Zone PM
The EZ-Zone PM is a panel-mount controller, and it turns up in ovens and furnaces more often than in the boxed environmental chambers the F4T tends to sit in. It is also the only controller besides the F4T on which ProcessView+ offers autotune — and the only one it can reach through a gateway rather than addressing directly.
Not sure this is what you have? A compact panel-mount controller in the EZ-Zone family, branded EZ-ZONE on the bezel. Check compatibility.
On this controller
What ProcessView+ can do with a EZ-Zone PM
- Profile control — download, read, start, stop, pause, resume
- Data logging and SQL Server mirroring
- QA reports with per-step tolerance bands
- AMS 2750 uniformity surveys and system accuracy tests
- 21 CFR Part 11 audit trail and signatures
- Autotune Shared only with the F4T
- RUI gateway addressing EZ-Zone PM only
Not available on this controller
- PID Sets
- Analog inputs
- Alarms 5–8 Alarms 1–4 are available
- Open-loop detection
- Variables / remote control
Nothing is withheld. ProcessView+ reads the controller type at startup and shows only what that controller exposes — so these menus do not appear rather than appearing and failing.
- Profile names are limited to 10 characters and are read-only in the editor — they come from the controller.
The gateway path, which nothing else has
A PM does not have to be addressed directly. ProcessView+ can reach one through an RUI gateway, and this is the only supported controller for which that is true — the software’s own Add Controller menu names it explicitly: Add New PM Controller or RUI Gateway Online.
The practical consequence is invisible once it is configured, and worth understanding before it is. A gateway shifts where each value lives in the controller’s register map. ProcessView+ carries a per-controller register offset and applies it to every read and write — process values, profile steps, alarms, the lot. You configure the offset once when you add the controller; nothing downstream needs to know a gateway is in the path.
That is what makes an EZ-Zone PM behind a gateway behave, from the software’s point of view, exactly like one addressed directly. Same logging, same reports, same compliance record.
Autotune, and no PID Sets
The PM shares autotune with the F4T and with nothing else. What it does not have is PID Sets — which the F4T and the legacy F4 both do. If your process relies on switching tuning parameter sets by step, that is the gap to know about.
Also missing, and for the same reason as on an F4: analog inputs, alarms 5–8, open-loop detection, and variables. The software reads the controller type at startup and shows only what the controller exposes.
Profile names come from the controller
On an F4T you name a profile in the software. On a PM the profile name field is read-only — the name is whatever the controller holds — and it is limited to 10 characters.
This is worth knowing when you plan a naming scheme across a mixed site. A PM’s profile names are set on the controller, so the software will show you what is there rather than let you rename it from the PC.
Furnaces, and why AMS 2750 matters here
PMs are common in heat-treating equipment, which is where AMS 2750 lives. The uniformity survey and system accuracy test features are not controller-gated in any way — they read recorded sensor data from the logging session — so a furnace running a PM produces the same survey report, with the same hot and cold spot, spread and maximum deviation against class tolerance, as any other supported controller.
See it against your own chamber
The free trial runs against a built-in virtual controller, so you can drive profiles, log data and generate a QA report before connecting anything.
Watlow and EZ-Zone PM are trademarks of Watlow Electric Manufacturing Company. GVE Inc. is not affiliated with, endorsed by, or sponsored by Watlow Electric Manufacturing Company. ProcessView+ is independent software that communicates with these controllers over standard Modbus.