Ladder + SCL / Free learning path
Understand the logic.
Prove the result.
Five practical PLC skills, from your first Boolean circuit to tracing a sequence fault. Predict what happens, check your reasoning, then change the conditions.
Permit Start MotorCmd
|----[ ]--------[ ]----------( )----|
Permit = 0 Start = 1
What is MotorCmd?READ → PREDICT → CHECK
A static example. Try the exercise below.
Put the logic to work
Quick PLC programming practice: write a short ST/SCL-style program and use scan-by-scan checks to improve it.
Mechatronics training: teach a virtual robot, connect a simulated sensor and investigate a stopped conveyor.
Choose a different starting point
New to PLCs or need a refresher?
Try the three-minute motor exercise below, then follow modules 1–5 in order. No software setup or account needed.
Already comfortable with basic logic?
Check your understanding of start, stop and seal-in behavior. If you can explain the result, try the independent variant.
Intermediate: try the seal-in check →
Not sure? Start with the first exercise. These recommendations do not set or save an account level.
Will the motor turn on?
A simulated motor needs both a start request and a permit. Here are two ways to write the same rule:
Ladder
--[ Permit ]--[ Start ]--( MotorCmd )SCL
#MotorCmd := #Permit AND #Start;In ladder, contacts in series mean AND. In SCL, AND says the same thing. Each value is either 0 (FALSE) or 1 (TRUE).
Your turn: Permit is 0 and Start is 1. Write MotorCmd’s value and one sentence explaining why. Make the prediction before opening the answer.
Need a hint before checking?
Read the rung from left to right. AND needs a complete path: if either condition is FALSE, the command stays FALSE. Which condition is missing in this case?
Reveal the answer and why
MotorCmd = 0. AND needs both conditions to be TRUE. A start request cannot bypass the permit. Now close this answer and predict what happens with Permit=1, Start=1, then Permit=1, Start=0. Check: 1, then 0.
That is the rhythm here: predict → check the reason → try a changed case. You can work on paper. This page does not execute code, grade you automatically, or save your answers.
The exercise and all five written modules are free, with no account or subscription required. Academy Plus is a separate $20/month recurring membership for guided member fault investigations. Compare free practice and Academy Plus.
Was anything unclear?
If you want to help improve this exercise, email support with the step where you got stuck and what you expected to happen. Feedback is optional. Please leave out workplace details, passwords and private machine data.
A SKILL PATH, NOT A VIDEO PLAYLIST
Build evidence that you understand it.
Each module takes you from a rule to a working explanation. Finish with a trace, a test table, or a fault report you can review, not just a checked box.
FOUNDATION / 01–02
Make the logic predictable.
Trace one scan, test Boolean conditions, and build a start/stop circuit that handles held buttons and loss of permission.
BEHAVIOR / 03–04
Handle time and events.
Distinguish a held signal from a new event. Explain timer resets, sensor chatter, counting and reset priority.
DIAGNOSIS / 05
Prove a whole sequence.
Follow state transitions, isolate a stalled conveyor, and retest stop, restart and repeated-cycle behavior.
The standard for a finished exercise
- Predict: Write the expected input, memory and output values before looking at the explanation.
- Trace: Follow execution in order. Separate the physical situation from the Boolean signal the program sees.
- Challenge: Test the normal case, a missing condition, held inputs, and the return to normal.
- Explain: State why the result is correct and what the example does not cover.
Use the written modules on paper or in your own simulator. The browser workshop is a separate bounded training engine; these TIA-style examples are not importable or commissioning-ready programs.
Your next five skills
A clear path. One circuit at a time.
Take these in order. Each has one worked example, a prediction, optional guidance, an independent variant, and explanatory answers. Plan around 15–30 minutes for each core lesson, then 20–35 minutes for its applied lab. The final sequence capstone takes roughly 60–90 minutes. These are planning estimates, not deadlines.
01 · Scan cycles and Boolean logic
Predict which value a later network reads. Translate series, parallel and negated contacts.
02 · Start, stop and seal-in
Build memory that still obeys a normal stop. Catch the bypass and held-start traps.
03 · Timers that reset correctly
Trace a TON through a chattering sensor. Call it consistently and explain elapsed time.
04 · Edges and part counting
Count arriving parts, not scans. Reason about rising edges, reset and preset behavior.
05 · Sequence and troubleshoot
Build a three-state simulated conveyor sequence. Prove transitions and find scan-order bugs.
Before using TIA Portal: notation and setup
Know what the examples assume.
- LAD notation:
[ X ]conducts when X is TRUE;[/ X ]when X is FALSE;( Y )writes the result to Y every scan. Series is AND, parallel branches are OR. These are software tests, not a physical wiring drawing. - SCL means Siemens Structured Control Language. It is Siemens’ Structured Text implementation. Examples use TIA Portal-style FB variables prefixed with
#,:=for assignment, andTRUE/FALSEfor Boolean values. Declare the listed interface and Static variables before using a body excerpt. - Use one implementation at a time: LAD and SCL are alternatives; do not execute both against the same timer, counter, or edge instance in one scan.
- Memory: use FB Static or suitable DB storage for Run, State, timer/counter instances and edge history. They must survive calls. Temp variables do not provide that memory; persistence across calls is different from retention through power loss.
- Execution: assume one call per cyclic scan, top-to-bottom program execution and ordinary process-image I/O. Later instructions can read memory written earlier in that scan. Actual PLC scheduling, interrupts and direct peripheral access can change I/O timing.
- Practice tool choice: start with paper traces. The browser workshop offers its own ladder and Structured Text subset. Its supported instructions and tag names may differ from TIA Portal. Do not assume Siemens FB calls below will paste or run there unchanged. Use a matching TIA Portal simulation project for vendor-specific compilation and tests.
Plan a short review over the next week
Check what stayed with you.
Record the module, today’s date, your confidence before checking, the mistake you corrected, and your next review date in a notebook. No progress or reminder is saved by this page.
| When | Do this without the worked solution | Check your evidence |
|---|---|---|
| After the module | Rebuild the independent variant in both languages. | Explain each test case, including stop/reset. |
| Tomorrow | Answer the module’s three recall prompts. | Mark correct, uncertain, or incorrect before revealing. |
| About 3 days later | Mix one task from two different modules. | Choose the right pattern yourself. |
| About 1 week later | Solve the final mixed challenge again. | Compare your trace and explain any correction. |
Adjust the gap to your performance and the date you need the skill. If recall is difficult, use a shorter gap. If it is easy and accurate, extend it. The goal is durable recall and transfer, not a streak.
Why this practice works: evidence and references
Evidence-informed, with honest limits.
Retrieval practice and spacing have substantial research support. Worked examples with gradually reduced guidance and corrective feedback also inform this design. The studies below tested other learning tasks and populations; they do not prove that this website improves PLC job performance. Our lesson sequence and review dates are applications of those findings, not a clinically or industrially validated training protocol.
- Roediger & Karpicke (2006), Test-enhanced learning. Delayed recall improved after retrieval practice in prose-learning experiments. Here: predict and explain before revealing.
- Cepeda et al. (2008), Spacing effects in learning. The effective study gap depended on the later retention interval. Here: revisit the skill over days instead of one long reread.
- Renkl, Atkinson & Große (2004), How fading worked solution steps works. Experiments studied gradual removal of worked steps. Here: complete example → missing steps → independent variant.
- Butler & Roediger (2008), Feedback and multiple-choice testing. Corrective feedback improved delayed performance and reduced errors in that setting. Here: check the reasoning and correct the underlying misconception.
- Institute of Education Sciences practice guide (2007). Synthesizes recommendations on spacing, worked examples, retrieval and explanatory questions.
Technical reference: Siemens cyclic OB execution; TON; CTU; block interface and storage. Match your CPU and TIA version when using instruction help.
Already using the app? This practice path adds deeper exercises to the existing eight workshop lessons. Your workshop stays available.