IMDHMIControls LibraryShop main store

How-to

How to learn Siemens ladder logic programming step by step

PLC programming Published 6 min read

Short answer

Learn Siemens ladder logic as two skills, not one tutorial: read LAD contacts, coils and boxes through the PLC scan cycle, and turn the controlled process into an I/O list plus a stopped, running and faulted operating table before writing networks. Practice each skill one instruction at a time in a simulator or on an isolated training PLC, with manuals for the exact controller and STEP 7 you run.

On this page
  1. Why a tutorial alone stops working
  2. What a contact means: the scan decides
  3. Turn the process into signals and states
  4. The practice sequence
  5. Manuals, books and where they come from
  6. Decisions you can commit to
  7. Questions asked

Learn Siemens ladder logic as two skills, practiced separately. First, read LAD — contacts, coils and box instructions — through the controller's scan cycle, so every network tells you when it executes and which value it sees. Second, turn the controlled process into an input/output list and an operating-state table before you write a single network. Take the manuals for your exact controller family and engineering software from Siemens Industry Online Support, because S7-1200/S7-1500 material in TIA Portal does not transfer to an S7-300/400, and practice each instruction in a simulator or on an isolated training PLC, never on a machine that can move.

Why a tutorial alone stops working #

IEC 61131-3 defines ladder diagram as one of the standard PLC programming languages; Siemens calls its implementation LAD, and in TIA Portal it extends contacts and coils with box instructions for math, timer, counter and move functions. STEP 7 in TIA Portal is the engineering environment where that program is written, configured and diagnosed. Recognizing the symbols is the small half of the skill. Most learners who stall are missing one of four things:

Symptom What is missing What to practice
Instructions make sense, the program never works Execution order and stored state Trace operand values through a full scan
The process description will not become networks Requirements never written as conditions and transitions Build the I/O list and state table first
The logic works until Stop or a fault Stop priority and abnormal states left out Test stop, lost permissive and restart deliberately
The tutorial will not reproduce in your software Controller or package mismatch Match material to your controller family and software

What a contact means: the scan decides #

One scan reads the physical inputs into an input image, executes the networks in order, then copies the output image to the terminals. A contact therefore tests the stored image, not the live terminal, and every network after the first sees the values the earlier networks left behind. Interrupts and direct peripheral reads exist; leave them until cyclic execution is second nature.

A normally open contact passes logic when its operand is 1; a normally closed contact passes when its operand is 0. Those names describe the instruction, not the wiring of the field device — read the input with the device actuated and with it released before you decide which one to use. Contacts in series are AND, branches in parallel are OR, and a coil assigns a Boolean result to its operand.

Order is the rule that bites: if network 3 writes a value that network 7 reads, network 7 sees the new value in the same scan. Two coils on one operand make the last one executed the winner, silently. Commit to one coil per output operand per program, and predict every output on paper before you go online to check.

Turn the process into signals and states #

A permissive is a condition that must hold before an action is allowed; an interlock is a condition that blocks a prohibited action. Write both in process words first, such as level above the low switch, and only then pick instructions. For each signal, record what 1 means and what 0 means; an operand whose meaning is OK is not a defined signal.

Then define three states — stopped, running, faulted — with the output condition in each state and the condition for every transition out of it, including how each state stops and whether restoring a permissive restarts the action. One limit belongs here: emergency stop is a safety function governed by IEC 60204-1 and ISO 13849-1, and a LAD stop branch is operational control only, never that function.

Worked example: a fill pump with a feedback window #

The addresses below are illustrative — a training example, not a wiring drawing.

Signal Example operand 1 means 0 means
Start pushbutton %I0.0 pressed released
Stop pushbutton %I0.1 pressed released
Level permissive %I0.2 level above low switch level at or below the switch
Contactor feedback %I0.3 contactor closed contactor open
Run command %Q0.0 pump commanded on pump commanded off

Four discrete inputs give 2^4 = 16 input combinations. The state table covers all 16 through three states and four transitions instead of 16 special cases:

State Run command Transitions out
Stopped 0 Start pressed and level permissive = 1 → Running
Running 1 Stop pressed or level permissive lost → Stopped; no feedback within 5 s of the run command → Faulted
Faulted 0 Fault cause cleared and reset acknowledged → Stopped

The running network is a seal-in: a Start contact in parallel with a Run contact, in series with the level permissive and a Stop break contact, driving the Run coil. An on-delay timer with a 5 s preset, timed from the run command, watches the feedback. Test it with two numbers: feedback arriving at 4 s stays Running, because 4 s < 5 s; feedback arriving at 6 s is 6 s − 5 s = 1 s past the window and drops the pump to Faulted. Restart rule, decided in advance: a level permissive that returns does not restart the pump — only a new Start does.

The practice sequence #

  1. Create an offline project for the controller you will actually be paid to program, and settle the software side by reading what STEP 7 is in a PLC project and which one you need; tutorial, controller and engineering package must agree.
  2. Wire one contact to one coil in logic. Predict the coil state for both input values, then monitor and confirm.
  3. Add series and parallel conditions until you can write the level permissive as a series condition without looking it up.
  4. Build the seal-in with Stop in series so stop wins over the seal, and write the restart rule beside the network.
  5. Add one on-delay timer and test its reset behavior before you add any second timed function.
  6. Implement the state table above; force the stop, the lost level and the late feedback, and watch each transition fire.
  7. Keep a test log — forced inputs, expected state, observed state — for every run; the log is what turns practice into evidence.
  8. Repeat the whole sequence on a second, different process. Ladder logic practice projects in STEP 7 gives you graded exercises. When your scope grows past the PLC, learning PLC, SCADA and DAQ from scratch covers the visualization and data side.

Manuals, books and where they come from #

Search Siemens Industry Online Support by your exact controller entry and software version: the programming manual for your STEP 7, the controller manual for your CPU, and the LAD reference for your generation are all downloadable there, and the instruction help sits inside the engineering tool. Scale your expectations — the S7-1200 controller manual in its 2014 edition runs 864 pages and the Programming with STEP 7 manual runs 668, so these are references you search by task, not books you read end to end.

Structured exercise books built around the S7-1200 with LAD work well as sources of graded practice. Get the engineering software itself from Siemens or its authorized distributors under its license. If your bench is an older S7-300 trainer, S7-300 student project ideas for a training lab line up bench exercises with that hardware generation.

Decisions you can commit to #

Question Decision
S7-1200 tutorial on an S7-300 bench? No. Use the LAD material for your controller generation; the families are not interchangeable.
Simulator or hardware first? Simulator until every paper prediction matches, then an isolated training PLC for wiring and feedback. Never a machine that can move.
Restart after a lost permissive? Require a new Start. Write the rule in the state table before the network exists.
Stop versus the seal-in? Stop breaks the seal: put it in series with the seal-in branch.
When are you done? When the I/O list, the paper prediction and the abnormal-state tests all pass on two different processes.

Questions asked

Is a simulator enough to learn Siemens LAD, or do I need a training PLC?

A simulator is enough for the scan cycle, seal-in circuits, timers and state tables, because those live in logic, not wiring. Real hardware adds what it cannot: 24 V field wiring, contact bounce, the choice between normally open and normally closed devices, and a contactor's true feedback timing. Do the full practice sequence in the simulator first, then move to an isolated training PLC before you work on a machine.

Why does my sealed-in output drop out when I release the Start button?

Three usual causes. The seal-in branch may not parallel the Start contact with the output's own operand, so nothing holds the rung. A permissive or stop contact in series may open when the button releases. Or a later network assigns the same coil again, and in LAD the last assignment in the scan wins. Check that the output operand drives exactly one coil and that the parallel branch uses that same operand.

Does ladder logic learned on another brand transfer to Siemens?

The reasoning transfers completely: Boolean conditions, seal-in circuits, permissives, interlocks and state thinking are the same in any ladder dialect. The surroundings do not: Siemens operand addressing, block structure, the LAD box instructions, and the download and online modes exist only in STEP 7. Learn the concepts wherever you like, but finish your practice on the Siemens software you will be paid to use.

How do I know when I have learned enough to write real machine logic?

Use milestones, not weeks. You write an I/O list with true and false meanings without help. You predict every output on paper before going online. Your state table survives the stop, lost-permissive and late-feedback tests without edits. And you can explain why a value written in an early network reads differently in a later one. When all four hold on two different processes, you are ready for supervised work on a real machine.

Where do I get the manuals and the engineering software?

Search Siemens Industry Online Support by your exact controller and software version: the programming manual, the controller manual and the LAD reference for your generation are downloadable there at no charge. The engineering software comes from Siemens or its authorized distributors under its own license, and where a trial or simulation license is offered, that is the legitimate way to practice before you have hardware.

Keep reading

  • How-to

    Build a siren pulse count sequence in S7-1200 ladder logic

    Use a positive-edge request to load a target of 3, 2, or 1 pulses, then run a four-state ladder sequence — idle, start, stop, count — that drives Q6.2 (START) and Q6.1 (STOP) from separate states so the two SIMOCODE Pro V commands never overlap. With a 2.0 s on-time and a 1.0 s gap, the three patterns finish in 11.0 s, 7.0 s, and 3.0 s.

    PLC programming

  • How-to

    How to build ladder logic practice projects in STEP 7

    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.

    PLC programming

  • How-to

    Sequencer valve control with a table-driven PLC program

    Write the sequence as data, not as rungs: one output command word per state in the binary file, a pointer word selecting it through an indirect MOV, and a second table of limit-switch patterns that proves each state before the pointer advances. A timer alone never advances a wash step; the feedback word must equal the commanded pattern or the step is a fault.

    PLC programming