Write a small PLC program, run the checks and inspect the first scan that differs from the target behavior. Quick Practice is for a short coding session without opening the full machine builder.
Open Quick PracticeEight small tasks, one skill at a time
The practice editor uses a bounded Structured Text/SCL-style teaching language. Start with Boolean assignments and progress to memory and timing:
- AND: require both inputs before commanding a motor.
- NOT: run only while the sensor is clear and the normal-stop condition permits it.
- OR: accept either request without letting either bypass the stop condition.
- Seal-in: retain a run request after Start is released.
- Selection: choose between two virtual outputs.
- Rising edge: generate a one-scan pulse instead of a continuous signal.
- Counting: count presses rather than the scans during a held press.
- TON: wait for a steady sensor and reset correctly when its input drops.
A worked example: the missing parentheses
Suppose either Start or AtSensor may request Motor, but StopOK must be TRUE for either request. StopOK is a normal process condition here, not a safety input.
Motor := StopOK AND (Start OR AtSensor);Read the grouped request first: Start OR AtSensor. Then require StopOK as well. If StopOK is FALSE, Motor must remain FALSE even when AtSensor is TRUE.
Your prediction: Start = FALSE, AtSensor = TRUE and StopOK = FALSE. What should Motor be, and which input prevents it from running?
Check the answer
Motor is FALSE. The request group is TRUE because AtSensor is TRUE, but the outer AND also requires StopOK. A program that writes Motor as (StopOK AND Start) OR AtSensor would incorrectly allow the sensor request to bypass that normal-stop condition.
Use the failed scan as evidence
A program can look reasonable and still fail when an input is held or changes back. The checks exercise changing and held inputs, not only one successful cycle. A failing result shows the relevant input values and the expected versus actual result. Equivalent solutions can pass; you do not need to reproduce one exact line of text.
- Read the task and its tag descriptions before typing.
- Write the smallest complete solution and run the checks.
- Find the first mismatch. Explain which expression produced it.
- Change one idea, then run all checks again.
- After a pass, edit or reset the task and try a different valid solution.
Hints are available when needed. Reset restores the starter; Undo can recover the reset code. Each task keeps its draft locally in the browser, not as an account-synced project. Editing a passing program requires a new check.
Write your first quick program → · Review scan-cycle basics
What this editor does and does not represent
This is an educational runtime, not the full Siemens SCL compiler or a substitute for TIA Portal. Tag declarations and available instructions are defined by each task. The TON exercise uses explicit simulated scan durations: its first enabled scan starts at ET = 0, later enabled scans add time, and a FALSE input resets the timer. No output is sent to real equipment.
For controller-specific execution details, consult Siemens’ S7-1200 V20 scan-cycle documentation. Our timer lesson adds a written trace you can compare with the practice task.