Lesson 20: Machine Controls, Instructor Session Plan

This is the implementation lesson for the machine controls layer. It's where the Aux I/O concept from Lesson 13 becomes wiring, and where safety-controls architecture and controls-standards discipline get taught for the first time. The one thing every student must leave with: the machine controls layer is specified now, in writing, or it gets set to defaults at startup and the system underperforms. If they treat ramp rates, release modes, and Aux I/O points as things to figure out during commissioning, the lesson didn't land. Part V is the depth part; teach the detail, don't reduce it to a summary.

Run of Show (60-minute baseline)

Segment	Min	What happens
The decision is made, now something has to move	5	Open cold on the hook. Don't frame it. Ask the room: between the routing decision and a carton actually moving, what has to exist? Let them list the pieces before you name the layer. That gap is the whole lesson.
The execution chain	11	Walk PLC, VFD, motor starter, MDR driver card. Put the control-panel sketch on the board. Land the division of labor: the PLC owns what crosses zones, the zone owns what happens inside it. Stress that the VFD ramp rate is a setpoint carried in from Part IV, not a knob turned at startup.
Aux I/O and the mapping drill	14	The heart of the session. Put a real layout on the board and run the Aux I/O mapping drill as a class. Students call out each point and defend why the PLC has to talk to or listen to that zone. Then flip to setpoints.
Safety PLC: zoning, reset, safe-state	12	Separate safety-rated controller and I/O, safety-rated devices, not standard switches. Teach zoning, reset logic, and safe-state. Tie it to the fail-safe default: signal-to-stop. Run the Stop and Think as a two-minute debate.
Controls standards discipline	10	Tagging, alarm philosophy, state machines. The maintainability layer. Make the 2 a.m. alarm concrete: a tech reads it and has to find the device on the drawing without a decoder ring.
Riverside machine-controls list	8	Students name every Riverside Aux I/O point and start the setpoints list. Collect the lists. Read two or three aloud and have the room defend or challenge each point.
Total	60	Baseline session. Expand with the stretch option below for a 90-minute block.

KEY TEACHING MOMENT

Put a real layout on the board and run the Aux I/O mapping drill as a class. Students call out each point and defend why the PLC has to talk to or listen to that zone. Do not accept "because it's an EZ zone" as an answer; make them name the reason, an end-of-conveyor feed, a PLC-commanded hold, a presence report, a merge entry.

Then flip to setpoints and say it plainly: every VFD ramp rate, every PLC transfer delay, every zone release mode is an installation-drawing element, not a commissioning detail. A student who leaves the machine controls to be "figured out during startup" has misunderstood the layer. The setpoints get specified now, in the design package, or they get defaulted at startup and the system runs slower and rougher than it was designed to.

WATCH-FORS

Three failures show up in this lesson. Catch them early and drive each one back to the same standard: the machine controls layer is specified now, in writing.

Students who treat Aux I/O as trivia because they already met it in Lesson 13. It was a concept then; here it's a wiring and panel-mapping requirement. Make them map real points, not recite the definition.
Students who conflate the safety PLC with the standard PLC. Separate the two on the board every time. The safety functions run on a separate safety-rated controller and safety-rated I/O, not as extra logic on the machine PLC.
Students who leave release modes and ramp rates unspecified "for commissioning." That's how a system gets defaulted at startup. If they can't state the fail-safe default and the ramp rate, the design isn't done.

RIVERSIDE FACILITATION

Run the Aux I/O walk on the Riverside layout and have students defend every point: the end-of-conveyor zones feeding the sorter induction, the merge-entry zones, and any zone the PLC has to hold. Then debate the safe default out loud, signal-to-stop versus signal-to-release on the induction feed, with the maintenance-of-one reality in the room. Michael keeps this system running alone; a zone that dumps a queue when he pulls a connector is his problem at the worst possible time.

Then have them start the setpoints list: belt speeds by section carried in, 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. Collect the lists. The students who write a complete, dated list are building the instinct you want.

CHECKPOINT ANSWER KEY (INSTRUCTOR ONLY)

These are judgment answers. Grade the reasoning, not a matching string. Push for the defense of each point.

Aux I/O mapping and the safe default. The end-of-line zone feeding the sorter induction needs an Aux I/O: it feeds a non-EZ device, and the PLC has to hold product, know when a carton is waiting, and sequence the release. The three pack-station lanes need one wherever the PLC has to hold or read the zone, a hold pending pack readiness, or a presence report. The footswitch lane is the exception that still uses the module: the footswitch wires straight into the Aux I/O, configured locally in the zone controller to pause the zone while the operator loads, no PLC needed. The rule to hear back: if the PLC has to talk to or listen to the zone, it needs an Aux I/O. Safe default on the induction-feed zone: signal-to-stop, so a disconnect holds product instead of dumping a full queue into a running induction. (Slug release is the Lesson 13 release pattern, a separate setting from the fail-safe default; credit the distinction.)
Safety zoning, safety-rated devices, and reset. Zoning buys availability without giving up safety: an e-stop or trip stops only the affected zone and its hazard, so a fault in one aisle doesn't dark the whole building. The customer's building-wide dark-stop makes every minor fault a full-plant outage and tempts operators to defeat it, and it adds no safety over a properly zoned system. Safety-rated devices and a safety-rated controller and I/O are engineered and diagnosed for the safety function; a standard switch on an interlock isn't a safety device and is the first thing questioned in an incident investigation, so cheap switches trade away the integrity of the function. Reset: a tripped zone must not restart on its own; it requires a deliberate, located manual reset by a person, at or near the zone and separate from a general start, so nothing surges back while someone's hands are in the machine. Don't let the answer name a specific guarding regulation or standard; that's Lesson 27. Keep it to the controls architecture.

INSTRUCTOR ONLY | DO NOT SHARE WITH STUDENTS

The Aux I/O list and the setpoints list the students start in this lesson are the machine-controls page of the capstone controls package. The setpoints seed the installation drawing in Lesson 28. A student who keeps a complete, dated setpoints list from here forward arrives at the capstone with this deliverable most of the way built.

Never tell them that. Reinforce the documentation habit as what a professional does, the same way you have since Lesson 1, and leave the payoff for them to discover. The reveal lands hardest for the students who kept the list without being told why.