Selection guide
Counting HMI device connections for an extrusion machine upgrade
Short answer
Seven controllers — one CompactLogix, four temperature controllers and two pressure controllers — need seven HMI device connections when wired directly, and the connection entitlement, not the loop count, decides the platform. Current Ignition Edge documentation includes unlimited device connections for included drivers, so the direct architecture fits; CompactLogix can instead aggregate the six process controllers into one connection.
On this page
Count device connections, not temperature zones. This extruder upgrade puts seven controllers in front of the HMI — one CompactLogix replacing the SLC 5/05, four Mini-8 temperature controllers and two pressure controllers — and each is a separate device connection when the panel talks to it directly. Current Ignition Edge documentation comes with unlimited device connections for the drivers included with it, so the seven-connection architecture fits a licensed Edge once the driver list covers every controller; if the panel cannot reach all seven, CompactLogix can aggregate the six process controllers into one connection at the price of PLC-side communications engineering.
Count devices, not loops #
A device connection is one communications endpoint in the HMI project: one configured driver pointed at one controller. The four Mini-8 units carry the machine's temperature zones between them and still count as four connections, because loop count and connection count are different quantities. Adding a drive or a second PLC adds a connection; consolidating loops inside a controller you already connect to does not. The inventory for this machine:
| Controller | What it regulates | HMI device connections |
|---|---|---|
| CompactLogix, replacing the SLC 5/05 | Machine sequence and I/O | 1 |
| Mini-8 temperature controllers, 4 units | 36 temperature zones, 11 of them heat/cool | 4 |
| Eurotherm pressure controllers, 2 units | 2 pressure loops | 2 |
| Total | 38 loops | 7 |
Reconcile the 36 zones against the channels actually configured in the four Mini-8 units before building the tag list; the connection count is unaffected, the tag map is not. Keep the second licensing axis in mind as well: some platforms price by tag count rather than connections. Current InTouch documentation describes unlimited tag count support, while other SCADA products still tier by tags — on those, the 38 loops and not the 7 connections drive the license size.
What the Edge connection terms say #
Licensing discussions consistently report two device connections for an unlicensed Edge install, with additional connections sold per device — under that older scheme this machine needed 7 − 2 = 5 purchased connections, which is where the "it will not work" verdict came from. The documented position has since moved: the current Ignition user manual describes Ignition Edge IIoT with unlimited tags and device connections for the drivers included with it. On those terms the direct architecture needs no per-connection purchase.
The operative words are included drivers. The connection count stops being the gate and the driver list becomes it: confirm the protocol each controller actually speaks — EtherNet/IP to the CompactLogix, a serial or TCP protocol on the process controllers — and that an included driver serves it, then have the quotation show the exact Edge edition with that driver set. Because per-connection licensing was sold in the recent past, read the entitlement line on the quote rather than assuming current terms.
One placement question comes before any of that: whether the machine needs Edge at the machine at all. If the screens can run as a client to an existing full Ignition server, the Edge connection terms never apply at the operator station — the case laid out in running an Ignition Vision client as a machine HMI without Edge.
Three architectures, one connection count #
| Architecture | HMI device connections | Where the 38 loops run | Work you own |
|---|---|---|---|
| Direct connections | 7 | Mini-8 and pressure controllers | Driver coverage, connection entitlement |
| PLC-mediated | 1, to CompactLogix | Mini-8 and pressure controllers | Controller comms, tag mapping, stale-data diagnostics |
| Centralized control | 1, to CompactLogix | CompactLogix | Loop I/O, heat/cool logic, SSR outputs, commissioning |
Whether the operator interface is an operator panel or a PC runtime is a separate fork, argued in headless HMI server versus operator panel selection, and it applies to all three rows. The previous machine ran the direct arrangement on a Red Lion panel sold under Eurotherm branding; that proves the architecture is sound, not that any specific new panel model can repeat it.
Letting CompactLogix aggregate the controllers #
In the middle row, CompactLogix polls the six process controllers and republishes their data, so the HMI holds one connection to the PLC — over EtherNet/IP, the link covered in connecting a CompactLogix PLC to an HMI over EtherNet/IP. The HMI's driver problem disappears and the engineering moves into the PLC: a communication path to each controller, a mapped tag set for setpoints, process values and alarm words, and freshness logic that turns a silent controller into an operator-visible fault instead of frozen numbers. That split of supervisory and regulation duties is the divide described in how an HMI and a PLC divide the work in a control system. Take this row when the panel's drivers or its entitlement cannot reach seven devices — not by default, because you are trading a licensing line item for communications code you maintain.
Moving the loops into the PLC #
A more capable CPU makes centralization worth evaluating; it does not execute 38 loops by itself. The 11 heat/cool zones in particular are not interchangeable PID blocks: each needs the right sensor input, a heating output, a cooling output, correct output direction and a defined transition between heating and cooling, and the two pressure loops need their own actuator assessment. Build the loop schedule first — zone, sensor, controller channel, heating output, cooling output, actuator, setpoint, alarms — and record the installed controllers' tuning, output limits and sensor-failure responses before anything is unwired.
The heater outputs follow the pattern the machine already uses: the Mini-8 zones drive SSR inputs from 24 VDC PWM outputs, with Crydom CKRD4830 relays on the co-extruder zones. The PLC repeats that with its own 24 VDC outputs into zero-crossing SSRs and PWM counted in AC half-cycles. At 60 Hz one cycle is 16.67 ms, so a half-cycle is 16.67 / 2 = 8.33 ms; counting half-cycles across a 10 s window gives 10,000 / 8.33 ≈ 1200 steps of duty resolution, 1:1200. The same 10 s window at 50 Hz, on 10 ms half-cycles, gives 1000 steps. Stagger the zones' on-times so 36 heaters do not draw together, and write the counting logic yourself — there is no stock block for it.
Relay outputs are excluded twice over: contacts will not survive the switching rate, and cycle-rate PWM defeats the point of a solid-state stage. For the relay itself, SSR versus EMR cycle rate and load type is the deciding comparison. Check the chosen output module's documented off-state leakage against the SSR input's turn-off threshold before standardizing, because a solid-state module can leak enough to hold a relay partly on. And SSRs normally fail short: heater overtemperature protection belongs to an independent limit device, never to the PWM output.
The decision #
Four cases, one machine:
- Distributed controllers, PC HMI at the machine: buy the licensed Edge runtime and connect all seven devices directly — unlimited device connections for included drivers on current documented terms — after confirming the driver list and the edition on the quotation. The runtime at the machine runs on industrial panel PCs.
- Operator panel instead: select the model by its documented driver and connection support for all seven devices, and pair it with the right engineering software as which HMI software works with which HMI panel hardware requires. The Red Lion precedent says the architecture works; it promises nothing about a new model.
- Panel that cannot reach seven devices: let CompactLogix aggregate into one connection and budget the controller communications, mapping and stale-data diagnostics as PLC scope.
- Centralize the loops: one connection and one tag namespace on the HMI, against 38 loops of I/O, SSR outputs, heat/cool logic and commissioning on the PLC side. Take it as a control-architecture decision, never as a workaround for connection licensing.
Questions asked
Do the 36 temperature zones mean 36 HMI device connections?
No. A device connection is one communications endpoint, so each Mini-8 counts once no matter how many zones it regulates: four units, four connections. Zones show up in the tag database instead, and on platforms that license by tag count it is tags, not connections, that set the tier. Adding zones to an existing controller changes the tag count and leaves the connection count alone.
How many device connections does Ignition Edge include?
An unlicensed Edge install is limited to two devices, and per-connection add-ons were sold under the older scheme. The current Ignition user manual documents Ignition Edge IIoT with unlimited tags and device connections for included drivers, so a seven-device extruder fits without add-ons on current terms, provided every controller's protocol is served by an included driver. Read the entitlement line on the quotation, because the terms changed within the last few years.
Can CompactLogix lower the connection count without replacing the controllers?
Yes. The PLC polls the six process controllers and republishes mapped tags, so the HMI needs a single connection to CompactLogix. The cost is PLC-side scope: a communication path per controller, the tag mapping, and diagnostics that flag stale data, because the HMI can no longer see a failed temperature controller directly, only what the PLC passes through.
What duty resolution does half-cycle PWM give on heater outputs?
At 60 Hz a half-cycle is 8.33 ms, and counting half-cycles across a 10 s window gives 10,000 / 8.33, roughly 1200 steps, a 1:1200 resolution. On a 50 Hz supply the half-cycle is 10 ms and the same window gives 1000 steps. Lengthen the window for finer resolution at the cost of slower output response, and stagger zones so heaters do not switch together.
Does moving the loops into the PLC change the HMI selection?
It simplifies the HMI to one connection and one tag namespace, which usually shrinks the screen project. It does not shrink the job: 38 loops of input modules, SSR outputs, heat/cool logic and commissioning move into the PLC budget. Treat centralization as a control-architecture change in its own right, not as a way around connection licensing.