PLC Simulator
PLC field notesbeginner

PLC Programming for Absolute Beginners (2026 Roadmap)

A gentle, non-jargon guide to PLC programming for people with no electrical background. Covers the scan cycle, your first rung, the five things that will confuse you, and a four-week starter plan that you can follow in a browser without installing anything.

PLC Simulation Software9 min read

PLC programming for absolute beginners

If you landed here by searching plc programming for beginners, you probably have one of three backgrounds: you're a student whose course just started PLC material; you're a maintenance tech who wants to understand the code your plant runs on; or you're a career-switcher who read that industrial automation pays well. All three work.

This post is the gentle on-ramp. No jargon without explanation, no vendor-specific distractions, and by the end you'll know what a PLC is, why the scan cycle matters, and what your first rung looks like.

What a PLC is (in one sentence)

A PLC — Programmable Logic Controller — is a small, ruggedised computer that reads sensor inputs, runs a control program, and switches outputs on or off, sixty-ish times a second, indefinitely. It lives on factory floors, in water plants, inside elevators, and almost any machine you'd describe as "automated." Our plain-English what-is-a-PLC post has the longer explainer.

Everything below assumes that sentence and expands on it.

The four things to learn first

Your first month — one thing per week

One topic per week is the right pace for beginners. Faster and you skip context; slower and you lose momentum.

Week 1 — the scan cycle

The single mental model every PLC behavior derives from. Three steps, repeated sixty times a second:

  1. Read every input into an image table
  2. Solve the ladder program top to bottom
  3. Write every output from the solve back to physical pins

Do the reading in our scan-cycle explainer. Write down one thing you didn't understand. Come back to it at the end of Week 1 — usually it's clear by then.

Week 2 — your first rung

The first rung you will ever write

The start/stop rung. Five symbols. Two vertical rails, two contacts, one coil, and a seal-in. This is the rung you'll write a thousand times in your career. Learn it until you can sketch it on a napkin without looking.

  • Start — normally-open contact. TRUE when operator presses the button.
  • Stop — normally-closed contact. TRUE when the button is NOT pressed. (This wiring convention is the thing beginners find most confusing — see below.)
  • Run — the output coil. Turns the motor on.
  • The Run seal-in — parallel contact that keeps Run energised after the operator releases Start.

Practice in our Motor Start/Stop scenario. It's free. It takes about 25 minutes if you're new.

Week 3 — timers

Every real program uses timers. Three flavours:

  • TON (Timer On-Delay) — start counting when input goes high, pulse the output high after the preset elapses.
  • TOF (Timer Off-Delay) — keep the output high for the preset after the input goes low.
  • TP (Timer Pulse) — emit a fixed-length pulse on the rising edge.

Our timers deep-dive walks through each with waveform diagrams. Plan to read it twice.

Week 4 — sequencing

A traffic light has six phases. Fluorescent bulbs need pre-warm, run, post-cool. Pumps alternate lead-lag. Sequencing is how you structure multi-step operations without writing spaghetti ladder.

The core pattern: one integer variable named PHASE, one rung per transition rule. If you understand that sentence by the end of Week 4, you're ready for real work.

Practice in Traffic Light and CIP Sequence Controller (the second one is Basic tier).

The five confusions that trip up beginners

The five things that will confuse you (and shouldn't)

1. Why Stop is wired normally-closed

On a real machine, the Stop button is wired as a normally-closed circuit. When the button is pressed, the circuit breaks. In ladder logic that means your Stop input is FALSE when pressed.

You draw Stop as [ ] (normally-open contact), which evaluates TRUE when the input is TRUE — i.e., when the button is NOT pressed.

If the wire gets cut or the button fails, the input goes FALSE, the rung goes FALSE, the motor stops. That's safe failure — which is the entire point.

2. Why outputs are one scan late

If Input goes high on scan 100, the output image table reflects that at the start of scan 101. Which means the output is energised at the end of scan 101, physical output switches mid-scan 102. For most purposes: 100 ms lag, invisible. For high-speed scans or tight timing: design around it.

3. Why SET/RESET behave differently from a plain coil

A plain coil reads the rung every scan and writes the result. TRUE on this scan, FALSE if the rung goes FALSE next scan.

A SET coil writes TRUE once and leaves the bit high forever, even if the rung goes FALSE. It only comes back FALSE when a separate RESET fires. This is called "latching."

Use latches for phase transitions and fault states where you want the bit to stay on until acknowledged. Avoid them everywhere else — they create hidden state that's painful to debug.

4. Why TON is not a function you call

In most programming languages a delay is a function call: sleep(1000). In ladder logic, TON is a block instance that lives inside a function block. It has state (the current accumulated time) that persists across scans. You don't "call" it; you energise its IN input, and over many scans its Q output eventually goes TRUE.

This is the biggest mental shift for programmers coming from software. PLCs don't block. Everything is evaluated every scan.

5. Why seal-in latches are the most important rung

Because almost every machine has at least one thing that needs to stay on after an operator lets go of a momentary button. Start/stop with seal-in is the universal pattern for that. Every variation — two-hand control, interlocked forward/reverse, cycle start for batch processes — is a seal-in with additions.

Get Week 2 right and everything downstream is easier.

What you do NOT need to worry about yet

  • Vendor dialects. IEC 61131-3 is the lingua franca. Worry about Allen-Bradley vs Siemens differences in month 3, not month 1.
  • PID loops. Analog control is Week 6+ material. Skip for now.
  • SCADA / HMI. Different discipline. See our PLC+SCADA training post when you're ready.
  • Structured text. Learn ladder first. ST is easier to pick up when you already think in scan-cycle terms. See our ladder-vs-ST post.
  • Safety PLCs. Specialist domain. Later.

FAQ

Is PLC programming hard to learn for beginners?

The first month is harder than you'd expect (scan-cycle thinking is unfamiliar). The second month is easier than you'd expect (the patterns repeat). By month three you'll look back and find Week 1 obvious.

What's the best language for a beginner?

Ladder logic. It's the most visual, the most common in industry, and it forces you to think in scan cycles from day one. Our ladder vs structured text post compares them.

Do beginners need to buy a PLC?

No. A browser simulator can teach the transferable scan-cycle and logic semantics. Run one guided first program without an account, then use the free tier with no card or trial clock.

What should a beginner start with?

Motor Start/Stop is the canonical first scenario — five symbols, seal-in pattern, deep content. Traffic Light second. Then follow the 12-week course.

Is PLC programming a good career for beginners?

Yes, still. Demand is rising because of reshoring and retirement. Mid-level PLC programmers earn USD 80,000–120,000 in North America and Europe. Our how to become a PLC programmer post goes deep on the career math.

Where to start right now

  1. Sign up free.
  2. Open Motor Start/Stop.
  3. Use the hints panel when you get stuck. Don't copy the solution — the hints are enough.
  4. When the tests pass, read our basic PLC programming post.

Twenty-five minutes to a passing first program. That's where the learning starts.

ShareX / TwitterLinkedIn

From reading to running logic

Practice this yourself in the simulator

Start with guided PLC practice in your browser. No install and no credit card required.

Start practising free

Continue learning

Related field notes

All articles
wiring
fault finding

How to Learn PLC Panel Wiring & Fault-Finding Online (2026 Guide)

A practical guide for learners who want to practice industrial control panel wiring and physical-fault diagnosis without a hardware bench. What you can learn online, what you can't, and how to structure deliberate practice.

14 min read
online
training

Online PLC Training in 2026: What Actually Works (And What's a Waste of Money)

A buyer's guide to online PLC training — video courses, subscription academies, graded simulators, and free alternatives. Which formats build real skill, which signal well on a CV, and which are paid YouTube. Includes recommended paths for students, career switchers, and working engineers.

10 min read
beginner
basics

Basic PLC Programming: The 20 Rungs You Will Use for the Rest of Your Career

Basic PLC programming is a surprisingly small set of patterns — maybe twenty rungs — that appear in almost every real program. Learn them in the right order, in the browser, with automated tests, and you will never have to re-learn the fundamentals.

11 min read

Competency and practice field guide

PLC programming for beginners guide: practice plan

Direct answer

The learner can explain the scan, map one input and output, build stop-priority logic, add time or count state and diagnose a changed case.

Written for first-time PLC learners who need a coherent practical sequence rather than an unstructured list of instructions and software links.

a diverse adult automation class using browser workstations and safe low-energy PLC training equipment with instructor feedback while studying beginner PLC learning from I/O truth to tested machine behavior
System map / 02

NODE 01observable

Scope

Learning objective, electrical state, physical input and output, process image, scan model, Boolean requirement, instruction state, machine result and feedback.

NODE 02observable

Signal path

Field stimulus through input tag, program evaluation, final output owner, modeled actuator and independently observed result.

NODE 03observable

Baseline practice

A start-stop or switch-output program behaves predictably over repeated scans from a clean reset.

NODE 04observable

Edge cases

Simultaneous commands, held input, one-scan event, timer boundary, counter edge, stop demand, power return and retained state.

NODE 05observable

Fault practice

An input truth, address, contact sense, branch, output ownership, state, timing or feedback mismatch.

NODE 06observable

Transfer to the job

The behavior recreated in the chosen official software and supervised hardware exercise.

Answer surface / 07

What should a PLC beginner learn first?

Learn the complete path from a field condition to input state, scan evaluation, output command and physical feedback before collecting advanced instructions.

Can I learn PLC programming without hardware?

You can build logic and diagnostic reasoning in a simulator, then transfer the exercises into official software and supervised physical I/O practice.