PLC Simulator

For instructors

Programmable logic controller course outline: a 15-week sample

A one-semester introductory programmable logic controller (PLC) course, week by week, with the free simulator lab for each week and where hands-on hardware time fits. It is our suggestion for you to adapt, not a standard.

Week by week

Topics follow the order the standard US PLC textbooks share: overview and hardware, number systems, logic, basic programming, timers, counters, then data instructions and troubleshooting. Each unit gives outcomes, what to teach, the free simulator labs with the behaviours each one checks, a suggested bench session if you have trainers, and a checkpoint idea. Bench lengths and checkpoints are suggestions to change; the lab details come from the labs themselves.

  1. Week 1
  2. Week 2
  3. Week 3
  4. Week 4
  5. Week 5
  6. Week 6
  7. Week 7
  8. Week 8
  9. Week 9
  10. Week 10
  11. Week 11
  12. Week 12
  13. Week 13
  14. Week 14
  15. Week 15

Week 1: What a PLC is, its hardware, safety, and the scan cycle

Students can, by the end of the week

  • Name the CPU, power supply, input and output modules and field devices
  • Explain that a PLC reads inputs, runs the program, then updates outputs, over and over
  • Run a graded program and read the result

In class

A block diagram of a PLC system, a short safety briefing for your lab, and the scan cycle drawn on the board with a switch and a lamp.

Simulator lab (free), about 3 min

Bench, if you have hardware (about 60 min): Tour the trainer: find the CPU, power supply and I/O modules, and trace one input and one output from terminal to device.

Checkpoint: Ask each student to say in two sentences what the PLC does between reading an input and changing an output. Lab 1 passed.

Week 2: Number systems and how inputs and outputs are addressed

Students can, by the end of the week

  • Convert between binary, decimal and hexadecimal for small values
  • Read an I/O address and say which module and point it refers to

In class

Number systems with worked examples, then your controller's addressing scheme with a wiring diagram of the trainer.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 90 min): Wire a switch and a lamp to a point each, find their addresses in your programming software and watch the switch bit change.

Checkpoint: Short quiz: three conversions and two addressing questions taken from your own trainer.

Week 3: Contact logic: AND and OR

Students can, by the end of the week

  • Predict the output of series and parallel contacts from a truth table
  • Explain why two contacts in series are an AND and two in parallel an OR

In class

Series and parallel circuits as relay logic first, then the same circuits as rungs. Fill in truth tables by hand before anyone opens the software.

Simulator lab (free), about 8 min

  • Lab 2. Two switches (AND)
    • Only SWITCH_1 on → LIGHT off
    • Both switches on → LIGHT on
    • Both off → LIGHT off
    • Only SWITCH_2 on → LIGHT off
  • Lab 3. Two switches (OR)
    • SWITCH_2 only → LIGHT on
    • SWITCH_1 only → LIGHT on
    • Both off → LIGHT off
    • Both switches on → LIGHT on

Bench, if you have hardware (about 60 min): Wire two switches and a lamp and build both the AND and the OR program on the controller.

Checkpoint: Hand out the truth-table section of worksheets 2 and 3 as a closed-book quiz, then have students confirm their tables in the labs.

Week 4: Normally closed contacts and stop circuits

Students can, by the end of the week

  • Say what a normally closed contact does when its input is false and when it is true
  • Explain why stop buttons are usually wired normally closed in the field

In class

Normally open and normally closed field devices versus normally open and normally closed instructions. This is the first place students confuse the two.

Simulator lab (free), about 4 min

Bench, if you have hardware (about 60 min): Wire a stop button normally closed, then disconnect its wire and compare what the lamp does with a normally open button.

Checkpoint: Ask: if the stop button's wire comes loose, what does the lamp do, and is that the safe failure? Lab 4 passed.

Week 5: Start/stop circuits and latching

Students can, by the end of the week

  • Explain why a momentary start button needs something to remember it
  • Build a start/stop with a stop that always wins

In class

Lab 5 is built to fail on purpose, so have students try it first and describe the problem before you introduce latching. Then compare SET/RESET with a seal-in rung.

Simulator lab (free), about 14 min

Bench, if you have hardware (about 90 min): Build the latched start/stop on the trainer and test it with the stop pressed at the same time as start.

Checkpoint: Peer test: each student tries to break a neighbour's program from the I/O panel and writes down what they found. Labs 5 to 7 passed.

Week 6: Review and first practical

Students can, by the end of the week

  • Write, download and demonstrate a start/stop from a written specification

In class

Review of weeks 1 to 5 using the worksheets as a revision set.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 90 min): Practical: from a one-paragraph specification, wire, program, download and demonstrate a start/stop with a lamp.

Checkpoint: Exam 1 on weeks 1 to 5, plus the practical marked against the same behaviours the labs check.

Week 7: On-delay timers

Students can, by the end of the week

  • Say what a timer's preset, elapsed time and done bit are
  • Predict what happens when the input is released before the preset

In class

Timing diagrams. Have students draw the diagram before building: input on, done bit on after the preset, and what a released input does to the timer.

Simulator lab (free), about 12 min

Bench, if you have hardware (about 90 min): Add a timed shutoff to the week 5 circuit, then time it with a stopwatch against the preset.

Checkpoint: Timing-diagram quiz: given an input waveform, draw the done bit. Labs 8 and 9 passed.

Week 8: Off-delay and retentive timers (no lab here)

Students can, by the end of the week

  • Choose between on-delay, off-delay and retentive timers for a described job

In class

Your textbook's timer chapter. The free labs only cover the on-delay timer, so this week is lecture and bench.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 90 min): Build one off-delay and one retentive timer example on the trainer and compare them with the on-delay.

Checkpoint: Short quiz on timer selection: three described jobs, name the timer type and justify it.

Week 9: Counters

Students can, by the end of the week

  • Explain that a counter counts a change of state, not a level
  • Use a done bit and a reset to count batches

In class

Counting edges versus levels with a photo-eye that stays blocked for half a second. Then batch counting with a reset.

Simulator lab (free), about 23 min

  • Lab 10. Count to five (CTU)
    • Five BOX_EYE pulses → CARTON_FULL on
    • Four BOX_EYE pulses → CARTON_FULL still off
    • CNT_RESET after a full carton → lamp off, next carton counts from zero
  • Lab 11. Count five boxes and stop (CTU)
    • Tap START → MOTOR on, CARTON_FULL off
    • Five BOX_EYE pulses → CARTON_FULL on, MOTOR off
    • Three BOX_EYE pulses → MOTOR still on, CARTON_FULL off
    • CNT_RESET after full carton → lamp off, conveyor can restart

Bench, if you have hardware (about 60 min): Count pushbutton presses on the trainer and drive an output at the preset, with a reset button.

Checkpoint: Ask: a box blocks the photo-eye for half a second. How many counts should that be, and why? Labs 10 and 11 passed.

Week 10: Small project: a timed, counted conveyor

Students can, by the end of the week

  • Combine start/stop, a warning delay, a counter and a stop condition from a written specification

In class

Project week: lab 12 is the specification. Students list the conditions for MOTOR to run before they build.

Simulator lab (free), about 12 min

  • Lab 12. Carton line (mini-project)
    • START → MOTOR off for 0.5 s, then on after the delay
    • STOP while running → MOTOR off and stays off
    • STOP during the 2 s wait → MOTOR never starts
    • Five boxes → CARTON_FULL on, MOTOR off
    • Three boxes → MOTOR still on, CARTON_FULL off
    • CNT_RESET after a full carton → lamp off, START runs again

Bench, if you have hardware (about 90 min): Rebuild the carton line on the trainer if it has a timer and a counter, with pushbuttons standing in for the photo-eye.

Checkpoint: Project handed in with the condition list and a screenshot of the passed lab. Marked on whether STOP works at every point, including during the delay.

Week 11: Motor control: ways to stop, and remembering a fault

Students can, by the end of the week

  • Separate stop sources (stop button, emergency stop, overload) in a program
  • Latch a fault and clear it only with a deliberate reset

In class

Motor starter circuit with an overload contact. Walk through what should happen when each stop source clears.

Simulator lab (free), about 18 min

  • Motor lab 1. Three ways to stop
    • START → MOTOR and RUN_LAMP on
    • STOP → MOTOR and RUN_LAMP off
    • ESTOP stops the motor, and it stays off after ESTOP clears
    • THERMAL_OL stops the motor, and it stays off after the overload clears
    • START does nothing while ESTOP is active
    • START does nothing while THERMAL_OL is active
  • Motor lab 2. Remember the trip
    • ESTOP while running → motor off, FAULT_LAMP on
    • ESTOP released → FAULT_LAMP stays on, motor stays off
    • RESET while THERMAL_OL is still active → fault stays on
    • Cause cleared, then RESET → FAULT_LAMP off, motor still off
    • START while the fault is latched → motor stays off
    • After a reset, START runs the motor again
    • RESET while ESTOP is still active → fault stays on

Bench, if you have hardware (about 90 min): Wire a motor starter circuit with an overload contact and test each stop source in turn.

Checkpoint: Ask: after the emergency stop is released, should the motor restart by itself? Motor labs 1 and 2 passed.

Week 12: A motor start/stop with fault monitoring

Students can, by the end of the week

  • Detect a contactor that did not drop out using its auxiliary feedback
  • Explain why a reset must never restart the motor by itself

In class

Contactor auxiliary contacts and feedback supervision. This is the longest free lab, so give it a full session.

Simulator lab (free), about 30 min

  • Motor lab 3. Motor Start/Stop & Fault Monitoring
    • Start energises contactor and run lamp, stop drops both
    • Start pulse seals in via latch
    • E-stop latches fault, clears only via stop-pb
    • Thermal overload latches fault, needs reset + stop-pb to clear
    • Stuck auxiliary feedback latches fault

Bench, if you have hardware (about 90 min): Run the same start, stop, fault and reset behaviours on the trainer.

Checkpoint: Graded as the second practical: students demonstrate each fault case to you on the simulator, then on hardware if you have it.

Week 13: Comparison, math and data instructions (no lab here)

Students can, by the end of the week

  • Compare and scale a value in a program

In class

Your textbook's data and math chapters. None of the 12 free labs uses these instructions.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 90 min): Compare an input value to a setpoint and scale it on the trainer.

Checkpoint: Quiz with two short problems from your textbook's review questions.

Week 14: Troubleshooting (no lab among the 12 free labs)

Students can, by the end of the week

  • Find a wiring fault and a program fault with a meter and the online view

In class

A fault-finding method: check power, then inputs, then the program, then outputs.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 120 min): Plant faults in the trainer wiring and in a program and have students find them against the clock.

Checkpoint: Troubleshooting practical: each student finds and fixes two planted faults.

Week 15: Review and final practical

Students can, by the end of the week

  • Demonstrate a complete small program on hardware

In class

Revision using the worksheets and the lab list.

Simulator lab (free)

No simulator lab this week

Bench, if you have hardware (about 120 min): Final practical on hardware: a start/stop with a timer and a counter from a written specification.

Checkpoint: Final exam and practical.

How much student time the labs take

The 12 beginner labs add up to about 76 minutes on our estimates for a first attempt. So a week's labs are short homework, not a lab session. That is why the outline leaves lecture and bench time for the topics a simulator cannot cover: wiring, module installation, downloading to a controller, and troubleshooting a real fault.

Each lab is graded on what the simulated machine does, so any correct program passes. Students can retry as often as they like, and in a class you can see who has finished (see for instructors).

What this outline does not cover

  • Sequencers, shift registers, program control, math and data instructions, networks and analog: no lab among the 12 free labs.
  • Brand-specific software, addressing and wiring: practise those on your own hardware and vendor software.
  • Accreditation: the course is yours; we give no qualification for completing the labs.

Using a textbook? See the textbook companion. Want paper practice? See the ladder logic worksheets. Questions: paul@plcsimulationsoftware.com.

FAQ

Course outline questions.

No. It is a sample we wrote for instructors to adapt. It is not a college outline, a state standard or an accredited curriculum, and completing the labs gives no qualification. Your institution owns its own outline and assessment.