Lesson 20: Machine Controls | Slides | Material Handling Academy

MATERIAL HANDLING ACADEMY

Part V. Lesson 20. Machine Controls.

DRIVING QUESTION How does a decision become motion the machine can execute safely?

PART V | LESSON 20: MACHINE CONTROLS

The Decision Is Made

Upstream, the system already knows what the carton is and where it sits, and a layer above already decided where it goes. None of that moves a single roller. Between the decision and the motion sits the machine controls layer: the PLC, the drives, the driver cards, and a safety system that can override all of them.

Now something has to move. And it has to be safe.

PART V | LESSON 20: MACHINE CONTROLS

Decision to Motion

PLC

Holds the logic and issues the commands. On its own it decides; it doesn't turn anything.

→

The Drives

A VFD sets and ramps belt speed. A starter switches a fixed-speed motor. An MDR card drives an E24 zone.

→

Motion

A turning belt, a firing divert, a held zone. The HMI is where a person meets it all.

The self-contained EZLogic zones handle their own accumulation without the PLC touching every zone.

PART V | LESSON 20: MACHINE CONTROLS

Open control panel showing the PLC, a VFD, and an MDR driver card on a control rail, with a separate safety PLC and safety-rated I/O on their own safety rail below a divider, an HMI on the panel door, and a gold Aux I/O module bridging the panel out to a self-contained EZ zone with its zone controller and photoeye. — The execution chain in hardware. The safety system sits on its own rail; the Aux I/O bridges the panel to a zone that otherwise runs itself.

PART V | LESSON 20: MACHINE CONTROLS

DESIGN PRINCIPLE The PLC owns what crosses zones. The zone owns what happens inside it.

Keep that boundary clean and the program stays small. Blur it and the PLC ends up micromanaging every roller, which is exactly what the EZ zones were built to spare it.

PART V | LESSON 20: MACHINE CONTROLS

Aux I/O, Implemented

The Aux I/O module plugs into a zone's transducer port on one end and the PLC panel on the other. That gives the PLC two things on a self-contained EZ conveyor: it can command that zone to hold or release, and it can read whether a package is present.

If the PLC needs to talk to the zone or listen to the zone, it needs an Aux I/O.

Map every point on paper during design. Found at commissioning, a missing Aux I/O is a panel modification at the worst possible time.

PART V | LESSON 20: MACHINE CONTROLS

Safety Controls

E-stops, light curtains, and interlocks run on a separate safety-rated controller and safety-rated I/O, not the standard PLC. Three ideas carry the layer.

Zoning: a trip in one zone stops that zone and its hazard, not the whole plant. A jam in one aisle shouldn't dark the building.
Reset logic: a tripped zone doesn't restart on its own. It needs a deliberate, located reset by a person.
Safe-state: the designed behavior on a trip, spelled out ahead of time, so a stop is predictable instead of a scramble.

PART V | LESSON 20: MACHINE CONTROLS

WHYA zone's release logic decides what happens on a disconnect, and that's a safety and product-integrity call, not a preference. Signal-to-stop holds product on a lost signal. Signal-to-release dumps it.

WHENOn every accumulation zone whose release the PLC commands. Decided during controls design and confirmed before commissioning, never left to chance.

WHEREAt every Aux I/O-equipped zone, and above all the end-of-conveyor zones feeding an induction or a sorter, where a runaway release meets moving equipment.

NOT WHENDon't leave a zone set signal-to-release just because it was the default on the last job. If that Aux I/O ever gets unplugged, and on a live system it will, the zone releases everything it's holding.

FAILURE IF IGNOREDA tech pulls an Aux I/O to trace a fault, and a zone set signal-to-release lets go of a full queue into a running induction. Best case a pileup. Worst case someone's standing there.

PART V | LESSON 20: MACHINE CONTROLS

Standards Discipline

Tagging conventions: every device and signal carries a consistent, structured name, so the PLC program, the drawing, and the HMI all call the same thing the same thing.
Alarm philosophy: alarms are designed, not accumulated. Each one is prioritized and actionable, and one fault doesn't bury the screen.
State-machine design: equipment lives in defined states, stopped, running, faulted, e-stopped, with defined transitions between them.

PART V | LESSON 20: MACHINE CONTROLS

Riverside

DESIGN PRINCIPLE Specify it now, or it gets set to a default at startup.

Walk the layout and write down every zone that needs an Aux I/O: the end-of-conveyor zones feeding the sorter induction, the merge-entry zones, any zone the PLC has to hold. Confirm every accumulation zone is set signal-to-stop. Then start the setpoints list: belt speeds by section, the VFD ramp rate at the decline, the PLC delays at the transfers, the release mode on each zone, and the fail-safe default, stated.

Next: What keeps the system powered, connected, and defended?