Paper Machinery Control System: PLC and HMI FAQ
How do you size a PLC for a paper cup machine?
Size it from I/O count with spare capacity, scan time against the fastest control loop, and motion axes against the number of synchronized drives. Take the axis count first, because motion usually sets the platform class before discrete I/O does. Leave at least 20% spare I/O and one spare axis. A machine that runs at its controller's limit cannot take the next feature the plant asks for, and its replacement cycle arrives before the capital is paid off.
Why does scan time matter more than the average cycle?
Because a control loop that overruns its period produces intermittent faults that look mechanical and trace back to the controller only after a long hunt. Specify scan time against the fastest loop the machine runs, not the average, and keep a margin between the program's worst-case execution and the loop period. When the margin disappears, symptoms appear as jitter, missed triggers, and phantom jam faults rather than as a clean controller error.
How should PLC and safety controller responsibilities differ?
The PLC runs production logic; the safety function runs on a separate or safety-rated path that must bring the machine to a safe state independently. Mixing them on one standard controller fails the safety assessment. Specify a safety controller or safety-rated I/O under ISO 13849, and validate stop-time performance separately from the production program. Bolting a safety function onto standard logic late in a project forces a controller change and a re-validation.
What makes a good HMI on a cup line?
A good HMI shows the line state and the next required action, not a replica of the electrical drawing. Group alarms by cause, show the recovery step with each alarm, and place operating controls where the operator actually stands. Lock recipe and clearance parameters against accidental change, and show the staged changeover checklist on screen. An interface that forces an operator to interpret raw codes under production pressure is where changeover mistakes and hidden micro-stops begin.
What belongs in the data layer above the machine?
Four things: a fieldbus matched to the controller family for drives and remote I/O, an isolated machine network for controller-to-HMI traffic, a read-only plant link that sends production data to MES, and version-controlled recipe distribution to the line. The data layer is where improvement work lives — reject counts, cycle time, and downtime reasons come from the controller rather than a clipboard, which is what makes an OEE board trustworthy.
What is the right commissioning sequence for a new machine?
Point-to-point I/O verification first, then safety functions with validated stop times, then axis-by-axis jog, then a dry automatic cycle with no stock, then a production trial at speed, and recipe and data setup last. Commissioning out of order is what produces the late rewrite. Error-proof the interface so a wrong recipe or an unlocked setting cannot run — the cheapest control improvement is often the one that makes the wrong action impossible. Sources: ISO 13849, UL Solutions control panel certification, ENERGY STAR motor and drive guidance, Lean Enterprise Institute.