plcsimulationsoftware.com/plc-lab-manual — every lab runs and grades itself in the browser. Free for students; instructor pack (answer keys + curriculum map) via plcsimulationsoftware.com/for-teams.
For educators → PLC Lab Manual
12 complete labs — from a first graded rung to a traffic-light capstone — each with an objective, a numbered procedure, and auto-graded pass criteria. Every lab runs in the browser on a free account. No trainer kits, no software installs, no marking pile.
2026 edition · Last updated 10 July 2026
The short answer
A PLC lab manual should progress from digital I/O basics (contacts and coils) through AND/OR logic, normally-closed stop circuits, latching and seal-in, on-delay timers and counters, to an integrated capstone — with each lab stating an objective, a numbered procedure, and explicit pass criteria a student can verify.
That is exactly what this manual is. The 12 labs below follow that arc one-to-one, and every lab maps to a free, auto-graded scenario in our browser simulator — so the “expected result” section of each lab is not a paragraph the student compares by eye, it is a set of test cases the platform runs against their program. Each lab is also a real industrial pattern rather than an abstract exercise: two-hand interlocks, dual start stations, the 3-wire motor seal-in, conveyor batching, a traffic-light sequencer. If you are searching for PLC real-world examples to structure a course around, that is what these are.
The manual is written for instructors at colleges, universities and training centres, but it works equally well for self-guided learners — every procedure step is addressed to the student. It complements, rather than replaces, hardware time: see our honest comparison of PLC training equipment options and why many programmes now run a simulator instead of trainer kits for the programming module, keeping a smaller bench for wiring and commissioning.
“A lab manual is only as good as its answer key. Ours is executable — the grader checks every student's program against the same pass criteria printed on the page.”
Course planning
The labs are sequenced so each one uses only concepts from earlier labs, with two deliberate difficulty walls — the SET/RESET latch pair (Lab 7) and the motor practical (Lab 11) — placed where our grading data says students need the most time. A one-lab-per-week pace fits a standard 13-week semester with room for orientation and a two-week capstone:
| Week | Session | Graded deliverable |
|---|---|---|
| 1 | Orientation: accounts, simulator tour, the scan cycle — then Lab 1 in the same session | Lab 1 passed (2 test cases) |
| 2 | Lab 2 — AND logic and interlocks | Lab 2 passed (3 test cases) |
| 3 | Lab 3 — OR logic and parallel branches | Lab 3 passed (3 test cases) |
| 4 | Lab 4 — NC contacts and stop circuits | Lab 4 passed (2 test cases) |
| 5 | Lab 5 — start/stop without a latch (designed failure + discussion) | Lab 5 passed (3 test cases) |
| 6 | Lab 6 — the SET latch | Lab 6 passed (2 test cases) |
| 7 | Lab 7 — SET/RESET latch pair (hardest concept week — budget the full session) | Lab 7 passed (3 test cases) |
| 8 | Lab 8 — TON on-delay timers and function blocks | Lab 8 passed (3 test cases) |
| 9 | Lab 9 — conveyor stop delay (latch + timer integration) | Lab 9 passed (3 test cases) |
| 10 | Lab 10 — CTU counters and the carton-fill pattern | Lab 10 passed (4 test cases) |
| 11 | Lab 11 — motor starter with faults (practical exam, double period) | Lab 11 passed (5 test cases) |
| 12 | Lab 12 part 1 — traffic light capstone (staged scenarios for scaffolding) | Capstone in progress |
| 13 | Lab 12 part 2 — capstone completion, review, certificate of completion | Lab 12 passed (2 test cases) |
Running a shorter block course? Labs 1–4 compress comfortably into two sessions; keep full sessions for Labs 7, 8 and 11. For a full curriculum-mapping treatment (outcomes, assessment weighting, accreditation language), see the PLC curriculum guide for educators.
In a traditional PLC lab, checking work means walking bench to bench pressing buttons — or trusting a screenshot. Here, every lab ends with a graded run: the platform executes the scenario's test cases against the student's program in a simulated machine and reports each case pass/fail with the exact signal that mismatched. Most labs grade in under a second, so students iterate in a tight loop instead of queueing for you. Across the 10,272 graded attempts on our platform to date, the most common failure message is simply an output that never energised — the kind of error students can find themselves when the feedback is instant.
There is no equipment list. The simulator is a PLC virtual lab that runs entirely in the browser — laptops, Chromebooks, lab desktops, students' own machines at home. No installs, no licences per seat of vendor software, no admin rights. All 12 scenarios in this manual are on the free tier, so students complete the whole manual on free accounts. You can also point students at the free ladder logic simulator page for self-paced practice between sessions.
For instructors
This page prints cleanly as the student handout — press and the navigation and CTAs disappear. The instructor pack adds the parts that should not be in students' hands: worked answer keys for all 12 labs, a curriculum map with learning outcomes for accreditation paperwork, and cohort dashboards that show you every student's graded attempts.
Prefer email? hello@plcsimulationsoftware.com — tell us your cohort size and programme and we'll send the pack details.
The manual
Each lab states its objective, prerequisites, a numbered procedure the student follows in the simulator, the auto-graded pass criteria (the scenario's real test cases, verbatim), and instructor notes with pass-rate statistics from our platform's graded-attempt data — so you know in advance where cohorts struggle.
15–20 min
Concepts: NO contact, output coil, the scan cycle
Write and test a one-rung program: when input SWITCH is ON, output LIGHT is ON; when SWITCH is OFF, LIGHT is OFF. Students learn that a contact reads an input, a coil writes an output, and power flows left to right.
None. This is the first session — a free account and a browser are the only requirements.
The grader runs these test cases against the student's program. All must pass:
This is the easiest lab in the manual: 80% of graded attempts pass (2,116 of 2,634 in our platform data). Use it to get every student one green run in the first session — that early win matters more than the content.
The most common failure is a misspelled or unassigned tag: the grader reports "LIGHT = false, expected true" because the coil is driving a tag the test never reads. Teach students to check tag names against the I/O table before debugging logic.
Scenario: beginner-01-switch-light
Run this lab: plcsimulationsoftware.com/scenarios/beginner-01-switch-light
20–25 min
Concepts: Series contacts as AND, interlocks
Program a rung where LIGHT turns on only when SWITCH_1 AND SWITCH_2 are both ON. Students learn that contacts in series read as AND — the pattern behind every interlock (guard closed AND start pressed).
Lab 1.
The grader runs these test cases against the student's program. All must pass:
Pass rate drops to 51% here (444 of 868 graded attempts) — the first real filter. The usual mistake is placing the contacts on a parallel branch (OR) instead of in series; the "Only SWITCH_1 on → LIGHT off" case exists precisely to catch it.
Frame it industrially before students touch the editor: a motor that starts only when the guard is closed AND the start button is pressed. Students who anchor series = "all conditions required" stop guessing.
Scenario: beginner-02-and
Run this lab: plcsimulationsoftware.com/scenarios/beginner-02-and
20–25 min
Concepts: Parallel branches as OR, multiple start stations
Program a rung where LIGHT turns on when SWITCH_1 OR SWITCH_2 is ON. Students learn that parallel contacts read as OR — how two start buttons on opposite sides of a machine are wired.
Labs 1–2.
The grader runs these test cases against the student's program. All must pass:
Pass rate 51% (259 of 503 graded attempts) — nearly identical to the AND lab, and the mirror-image mistake: contacts in series when a branch was needed. The two single-switch cases fail together when that happens, which makes the diagnosis easy to teach.
A good five-minute extension for fast finishers: combine Labs 2 and 3 into (SWITCH_1 OR SWITCH_2) AND a third condition on paper, and ask where the branch has to close.
Scenario: beginner-03-or
Run this lab: plcsimulationsoftware.com/scenarios/beginner-03-or
20–25 min
Concepts: Normally-closed contacts, fail-safe stop wiring
Use a normally-closed (NC) contact so LIGHT is on by default and pressing STOP_BUTTON turns it off. Students learn the contact type behind every real stop circuit: idle = circuit complete, pressed = circuit broken.
Labs 1–3.
The grader runs these test cases against the student's program. All must pass:
Pass rate 53% (194 of 368 graded attempts). The classic error is using an NO contact — the lamp then does the exact opposite of the brief, and the "STOP released → LIGHT on" case fails.
This is the right moment for the examine-if-closed conversation: the contact symbol describes the logic condition, not the physical button. Students who conflate the two will struggle again in Lab 7 — invest the ten minutes here.
Scenario: beginner-04-nc
Run this lab: plcsimulationsoftware.com/scenarios/beginner-04-nc
25–30 min
Concepts: Combining NO + NC, discovering why latching exists
Combine an NO START with an NC STOP in series: hold START and the LIGHT is on, release it and the LIGHT drops out. The point of the lab is to feel the problem — nobody holds a start button all day — before Lab 6 fixes it.
Labs 1–4.
The grader runs these test cases against the student's program. All must pass:
Pass rate 61% (210 of 345 graded attempts). Students who overthink it add a latch they have not been taught yet — and then fail the "Release START → LIGHT off" case. That failure is a teaching gift: the grader is checking the naive circuit on purpose.
Close the session with the cliffhanger, not the answer: "next week we make it stay on." The discovery framing measurably improves engagement with Lab 6.
Scenario: beginner-05-start-stop-no-latch
Run this lab: plcsimulationsoftware.com/scenarios/beginner-05-start-stop-no-latch
20–25 min
Concepts: SET (S=) coils, retained state
Use a SET coil so a momentary START pulse turns LIGHT on and it stays on after the button is released — the way real machines start: tap the button, the motor runs.
Labs 1–5 (Lab 5 supplies the motivation).
The grader runs these test cases against the student's program. All must pass:
Pass rate 69% (218 of 318 graded attempts) — the highest of the latching labs, because it is one rung with one new element. Let it be a confidence builder between the Lab 5 discovery and the Lab 7 filter.
The "Idle → LIGHT off" case catches students who drive the coil unconditionally. It looks trivial; it is the first time the grader checks what the program does when the operator does nothing.
Scenario: beginner-06-latch-start
Run this lab: plcsimulationsoftware.com/scenarios/beginner-06-latch-start
35–45 min
Concepts: RESET (R=) coils, two-rung latching, the NC-on-reset trap
Add a stop to the latch: pulse START and LIGHT latches on; pulse STOP and it resets off; pulse START again and it returns. Two rungs — one SET, one RESET — the pattern behind nearly every industrial start/stop circuit.
Labs 1–6.
The grader runs these test cases against the student's program. All must pass:
Expect a wall: only 23% of graded attempts pass (148 of 631) — the second-hardest lab in this manual. The dominant error is putting an NC contact on the reset rung, carried over from Lab 5. An NC /STOP is true every scan the button is NOT pressed, so it resets the latch continuously and the lamp never latches.
That mistake surfaces as "LIGHT = false, expected true" — the single most common failure message across our whole platform (2,171 of 3,715 failed attempts end that way). Put the NO-vs-NC-on-reset question on the board before students run anything.
Budget a full session and expect multiple graded attempts per student; in our data most students who eventually pass a scenario need more than one run at this stage of the course.
Scenario: beginner-07-latch-stop
Run this lab: plcsimulationsoftware.com/scenarios/beginner-07-latch-stop
35–45 min
Concepts: Function blocks, TON instances, preset vs elapsed time, the .Q done bit
Use an on-delay timer: after SWITCH closes, wait 2 seconds, then turn LIGHT on. Release the switch early and the timer resets and the light never comes on. Students meet their first function block and its .Q output.
Labs 1–7.
The grader runs these test cases against the student's program. All must pass:
Pass rate 25% (98 of 397 graded attempts). Two mistakes dominate: writing PT := 2 (seconds) instead of 2000 (milliseconds), and wiring LIGHT straight from SWITCH so it ignores the timer entirely — the 500 ms case exists to kill that shortcut.
This is also where students first see a program that is not a pure rung: declaration, call, then a rung reading .Q. Walk through why the call happens every scan — it prevents a whole family of "my timer never runs" questions in Labs 9–11.
Scenario: beginner-08-ton-delay
Run this lab: plcsimulationsoftware.com/scenarios/beginner-08-ton-delay
45–60 min
Concepts: Integrating SET/RESET with a TON, auto-shutoff sequencing
Tap START and the conveyor MOTOR latches on; after 3 seconds a timer shuts it off automatically. Three rungs — SET on START, a TON enabled by MOTOR, RESET on the timer done bit — the first true multi-rung sequence.
Labs 1–8 (this lab integrates Labs 7 and 8).
The grader runs these test cases against the student's program. All must pass:
Pass rate 43% (96 of 222 graded attempts) — better than Labs 7 and 8 individually, because students who survived those two have the pieces; the work here is composition. The common failure is omitting the reset rung, which fails only the 3.5 s case.
Ask students to predict the timing diagram on paper before running. The mid-cycle test case (motor still on at 1.5 s) rewards the ones who actually reasoned about time rather than toggling until green.
Scenario: beginner-09-conveyor-stop-delay
Run this lab: plcsimulationsoftware.com/scenarios/beginner-09-conveyor-stop-delay
50–60 min
Concepts: CTU function blocks, rising edges, gating a restart
A conveyor fills a carton: each box that trips the BOX_EYE photo-eye counts up; after five boxes the MOTOR stops and CARTON_FULL lights; CNT_RESET clears the count for the next carton. A real packaging-line pattern, end to end.
Labs 1–9.
The grader runs these test cases against the student's program. All must pass:
Pass rate 28% (52 of 189 graded attempts). The subtle failure is the restart gate: without /BOX_CNT.Q in the start rung, a full carton can be restarted without resetting — only the fourth test case catches it, so students see three greens and one stubborn red. That is a realistic commissioning experience; say so.
CU is edge-triggered: students who hold BOX_EYE closed and expect the count to climb get exactly one count. It is worth demonstrating live before they ask.
Scenario: beginner-10-counter
Run this lab: plcsimulationsoftware.com/scenarios/beginner-10-counter
90 min (double period)
Concepts: Seal-in, E-stop and thermal-overload fault latching, feedback supervision
Build the classic 3-wire motor starter: the contactor seals in on a momentary start, drops on stop, latches a fault on E-stop or thermal overload that only an explicit stop-press can clear, and detects a welded contactor via the auxiliary feedback contact.
Labs 1–10. This lab uses everything: latching, NC logic, and a TON (a 500 ms delay before declaring the stuck-feedback fault).
The grader runs these test cases against the student's program. All must pass:
This is the hardest graded lab in the manual: an 18.7% pass rate (127 of 679 graded attempts) in our platform data. Treat it as the practical exam and schedule a double period — students who pass it cold have genuinely learned the material.
The concept that separates passers from non-passers is fault-latch semantics: releasing an E-stop must NOT restart anything or clear the fault. Students consistently reset the fault from the E-stop input itself; the third test case fails them for it, exactly as a safety auditor would.
Partial credit is easy to award by hand if your course needs it: the five test cases are independently reported, and the first two (start/stop and seal-in) map to the traditional 3-wire circuit taught with hardware trainers.
Scenario: motor-start-stop
Run this lab: plcsimulationsoftware.com/scenarios/motor-start-stop
2 sessions
Concepts: Timed sequencing, phase state, safety interlocks — everything combined
Build a 4-way traffic light controller: NS and EW phases alternate, each green runs 10 s, yellow 3 s, with a 1-second all-red clearance so the two directions are never green together. Sequence logic, timing and safety in one real control problem.
Labs 1–11. For cohorts that need scaffolding, the simulator also has a free staged version of this exact problem — four smaller scenarios (single lamp → manual colors → timed sequence → auto cycle) that break the capstone into graded steps.
The grader runs these test cases against the student's program. All must pass:
Pass rate 45% (175 of 387 graded attempts) — higher than the motor lab because students attempt it after everything else, and many iterate over several sessions. Grading takes ~8–9 seconds per run (the grader simulates full light cycles in accelerated time), so warn students the spinner is normal.
The "Never both green simultaneously" case is the one to talk about afterwards: it is a property test, not a step test. It fails programs that happen to cycle correctly but have no structural guarantee against conflicting greens — the difference between code that works and code that is safe.
Struggling students should be routed to the staged traffic-light scenarios (also free) and can return to the capstone after stage 4; strong students can be asked to add a pedestrian-crossing phase on paper as an extension exercise.
Scenario: traffic-light
Run this lab: plcsimulationsoftware.com/scenarios/traffic-light
Beyond PLC courses
Mechatronics programmes need the same controls module this manual delivers, and the format — objective, procedure, expected result — is the classic mechatronics lab experiments structure, so the 12 labs drop into a mechatronics course as the PLC block without adaptation. Labs 9–12 in particular (conveyor timing, part counting, motor supervision, sequenced lights) are the electromechanical-integration experiments most mechatronics syllabi ask for.
One honest scope note: if your syllabus calls for a mechatronics and IoT lab manual, this covers the mechatronics/controls half — PLC programming, timing, sequencing and interlocks — not IoT networking or cloud connectivity. For the broader platform fit (robotics and HMI modules alongside PLC), see mechatronics training software.
Related planning resources: PLC training equipment guide, PLC trainer kit alternatives, and the curriculum guide for educators.
All 12 labs are free-tier scenarios. Pilot with one class, then add the instructor pack and cohort dashboards when you scale.