IMDHMIControls LibraryShop main store

How-to

How to build ladder logic practice projects in STEP 7

PLC programming Published 6 min read

Short answer

Get STEP 7 ladder practice projects from the vendor's own support portal and from the samples the installer already placed on your PC, not from a copy of a book's bundled disk. Then rebuild three circuits yourself: a start/stop latch with overload interlock, an on-delay timer sequence, and an up/down counter.

On this page
  1. Where the practice projects live
  2. Build order: six steps
  3. The instructions the three rebuilds use
  4. Worked example: the start-stop latch with start at I0.0 and coil at Q4.0
  5. Where to go after the three rebuilds
  6. Questions asked

Most ladder logic practice projects for STEP 7 are already published by the vendor: demo projects on its support portal, plus the sample projects the installer copies onto your engineering PC. If a used textbook's example disk never arrived, skip the hunt for a copy of it — the downloads have documented, current replacements, and every circuit on that disk is short enough to rebuild by hand anyway. Ladder diagram is one of the programming languages IEC 61131-3 defines, and three circuits use most of what the language offers: a start/stop latch with an overload interlock, an on-delay timer sequence, and an up/down counter. If you are starting the whole subject from zero, pair this with how to learn PLC, SCADA and DAQ from scratch, then come back and rebuild.

Where the practice projects live #

The vendor publishes what that missing disk held, and the entries are stable identifiers in the Siemens Industry Online Support portal. Entry ID 40263542 is the Getting Started manual for STEP 7 Basic; entry ID 44037848 holds the download for the demo projects in Getting Started of STEP 7 Basic V10.5. They belong to that release, so open them in the engineering environment it targets rather than assuming forward compatibility.

Your own installation ships samples too. A classic STEP 7 install with SIMATIC Manager copies example projects to C:\Program Files\Siemens\Automation\STEP7\EXAMPLES; open that project folder from SIMATIC Manager the way you would open any project. For S7-300 and S7-400 material specifically, entry ID 23330722 collects STEP 7 example programs and documentation, including conveyor control, a mixing tank and a traffic light project, plus organization-block templates.

Build order: six steps #

  1. Open one vendor sample and read it end to end. Take it from the portal entries or the installed examples folder listed above, and page through its blocks without editing anything.

  2. Write each network as a Boolean expression beside it — contacts are AND and OR terms, a coil is the assignment. If you cannot write the expression, you are not ready to rebuild the network.

  3. Rebuild project 1, the start/stop latch with an overload interlock, to the specification and logic worked through in full in the section below.

  4. Rebuild project 2, an on-delay timer sequence: one output follows the command immediately, and a second switches on only after a preset time elapses with the command still held. Use the S_ODT on-delay timer box with the preset at its TV input; pick an illustrative 5 s, then change the preset without touching the logic. It passes when the second output stays off until the time expires and resets whenever the command drops early.

  5. Rebuild project 3, an up/down counter: S_CU on the arrivals, S_CD on the departures, and the S and R inputs to set or clear the count. The count value runs from 0 to 999; compare it against a limit you choose, say 10, and drive an alarm coil from the comparison. It passes when each edge moves the count exactly once, not once per scan.

  6. Prove every rebuild before starting the next: compile, run against a simulated CPU — S7-PLCSIM, where your STEP 7 package and license include it — or watch online status on real hardware, and test every input combination, including stop pressed and a signal wire open.

The instructions the three rebuilds use #

Older textbooks and listings print ladder elements as Statement List mnemonics, one letter pair per contact or coil. The sample projects draw the graphical elements, the listings use the letters, and the rebuilds need both spellings:

Element Mnemonic What it does
Normally open contact A passes power when the bit is 1
Normally closed contact AN passes power when the bit is 0
Output coil = writes the rung result to the bit
Set / reset coils S / R latches a bit on or off
On-delay timer box S_ODT output turns on after the preset at TV elapses with the input held
Up counter box S_CU increments on each rising edge at CU
Down counter box S_CD decrements on each rising edge at CD

The three practice circuits need nothing beyond these seven elements.

Worked example: the start-stop latch with start at I0.0 and coil at Q4.0 #

Inputs. The addresses are illustrative, in the classic S7 byte.bit scheme — I is a process-image input, Q a process-image output — the style the vendor's example projects use; assign your own addresses and put the names in the symbol table, where the run coil here is Motor1_Run. Every signal is binary: its unit is its state, 1 on and 0 off, and the states come from the field wiring, not from the program.

  • I0.0, start pushbutton, momentary: 1 only while pressed.
  • I0.1, stop pushbutton with a normally closed field contact: 1 at rest, 0 when pressed or when its signal wire breaks.
  • I0.2, auxiliary contact on the motor overload relay: 1 while the relay is healthy, 0 once it trips.
  • Q4.0, contactor coil: 1 runs the motor.

Rule. The coil stays energized while start is pressed or the coil is already on, and while the stop circuit and the overload are both healthy.

Arithmetic. Q4.0 = (I0.0 OR Q4.0) AND I0.1 AND I0.2, evaluated case by case:

  • Motor at rest, start pressed: (1 OR 0) AND 1 AND 1 = 1, coil on.
  • Start released: (0 OR 1) AND 1 AND 1 = 1, the seal-in branch holds the coil.
  • Stop pressed: (0 OR 1) AND 0 AND 1 = 0, coil drops and the seal-in is broken.
  • Stop signal wire broken: I0.1 reads 0, so the AND chain gives 0 with nobody touching anything.
  • Overload tripped: (0 OR 1) AND 1 AND 0 = 0, coil drops.

Result. One network in OB1, the block the CPU scans cyclically: a branch of I0.0 in parallel with Q4.0, in series with I0.1 and I0.2, feeding the Q4.0 coil, every contact examined normally open because each input's healthy state is 1. As a listing: A I0.0, O Q4.0, A I0.1, A I0.2, = Q4.0.

Decision. The rebuild passes only when all three failure tests behave: releasing start keeps the coil on, pressing stop drops it, and opening the stop signal wire drops it too. If a listing instead examines the stop with a normally closed contact (AN I0.1), its field button is normally open — and a broken stop wire then leaves the input at 0, the rung conducting, the motor startable. Check the at-rest state of every input before trusting a copied circuit; that mismatch is the most common bug carried out of old example printouts.

One safety note: IEC 60204-1 requires machinery stop and emergency-stop functions to work independently of programmable logic, so this latch is control, not protection — the emergency stop and the overload trip stay wired to devices that break power directly.

Where to go after the three rebuilds #

The vendor's application examples take over from the samples. Entry ID 109817184 documents how application examples are organized and found. Entry ID 109476781 is the Sample Library for Instructions, examples for individual TIA Portal STEP 7 instructions. Entry ID 109810699 publishes the SIMATIC Process Function Library V4.0 with its TIA Portal application examples, and the template download for HMI design sits under entry ID 91174767. Work each one the way you worked the first three: read the description, rebuild the logic yourself in ladder, then open the vendor's blocks and compare. The differences between your version and theirs are the lesson, and they are why rebuilding teaches more than watching a sample run.

Questions asked

Do the demo projects from entry ID 44037848 open in TIA Portal?

They are built for STEP 7 Basic V10.5, the release the Getting Started manual they accompany targets, so open them in that engineering environment rather than assuming forward compatibility. For TIA Portal work the documented source is the Sample Library for Instructions, entry ID 109476781. Sample projects generally open in the version they were written for; moving a classic SIMATIC Manager project forward uses the software's migration path and is never a plain file copy.

Do I need a real CPU to run the rebuilds?

No. Where your STEP 7 package and license include the S7-PLCSIM simulation component, run the finished project against a simulated CPU and toggle each input by hand to test every combination; which packages include it depends on the license, so check your installation. Without simulation you can still build and compile everything offline and prove the logic on paper before you ever connect a CPU.

Why does my counter stop at 999?

The S5 counters used in classic STEP 7 ladder, such as the S_CU up counter and the S_CD down counter, hold the count value as a three-digit BCD number, so the range is 0 to 999. To track more than 999 events, increment a normal data word with an add instruction and compare that word instead of driving one counter past its range.

May I share the projects I rebuild?

Read the license text that comes with any sample or library you download from the vendor's portal before reposting it anywhere; vendor samples are not always yours to redistribute. Projects you rebuild yourself, written network by network from a written description with your own symbols and addresses, are your own work, and those you can share as you choose.

Keep reading

  • How-to

    How to learn PLC, SCADA and DAQ from scratch

    Learn the three as one project, not three courses: pick one route, wire one real input, program a three-state sequence, exchange one Modbus register, bind SCADA tags and store a timestamped value. Pass the five checkpoint tests on the way; simulation alone never exercises terminals, polarity or reconnection.

    SCADA and data logging

  • Troubleshooting

    Why HMI values show question marks: PLC comms timeouts

    Yes — a running PLC program can cause intermittent HMI timeouts by consuming nearly all controller execution time, and clean Ethernet counters do not clear it: utilization measures bytes, not the cost of servicing requests. Work controller load first: Task Monitor above 90% on the dropping units against 7–15% on healthy ones, then message pacing, packet-rebuild address forms, read grouping, and power last.

    PLC programming