How to Learn PLC Programming: 2026 Roadmap (Self-Taught Path)
Complete roadmap for learning PLC programming in 2026. Realistic 6-month self-taught path covering tools, scenarios, vendors, certifications, and how to land your first PLC programmer role.
If you're searching "how to learn PLC programming", you almost certainly fall into one of three groups: an electrician moving into controls, a software engineer crossing into operational technology, or a student / career-changer entering automation from scratch. The roadmap is similar for all three but with different starting points and emphasis. This guide gives a realistic 6-month self-taught path from zero to "ready to apply for junior PLC programmer roles" — built around tools that are free or under $200 total spend.
Where to Start Depends on Your Background
Before the roadmap, identify your starting position:
If You're an Electrician Moving Into Controls
Strengths: physical wiring, schematic reading, motor control concepts, safe work practices.
Gaps: programming logic, abstract thinking about scan cycles, software tooling, version control.
Adjustment: skip month 1's electrical-fundamentals review (you already know it). Spend extra time on Structured Text and state machines (months 3-4) — these are the parts that don't have an electrical analogue.
If You're a Software Engineer Moving Into OT
Strengths: programming logic, debugging, abstractions, version control, testing mindset.
Gaps: physical-world thinking, safety mindset, scan-cycle determinism, vendor-specific tooling, electrical wiring basics.
Adjustment: skip Structured Text introduction (it's Pascal-like; you'll be fluent in days). Spend extra time on the wiring + safety side (months 5-6). Read our PLC coding guide for software engineers.
If You're a Career-Changer or Student From Zero
Strengths: open-minded, time-flexible, no bad habits to unlearn.
Gaps: literally everything — electrical, programming, industrial vocabulary, vendor ecosystems.
Adjustment: don't skip anything. Take month 1 seriously and build the mental model before writing code.
Month 1: Foundations (No Code Yet)
The biggest mistake beginners make is jumping straight into Studio 5000 or TIA Portal without the mental model. Spend three weeks reading and watching, no laptop programming.
Read:
- What is PLC Programming complete guide — start here
- Beginner's Guide to PLC Programming — pillar page covering the conceptual base
- PLC Programming Basics
- Is a PLC a computer?
Watch (free):
- PLC Professor's intro playlist on YouTube
- RealPars's free fundamentals videos
- Tim Wilborne's beginner content
Internalise these mental models:
- The scan cycle: read inputs → execute logic → write outputs → repeat, every 10-100 ms
- Inputs only update at scan start; outputs only update at scan end
- Timers tick on the scan clock, not real-time
- The PLC runs forever, not from main() to exit
- Industrial I/O is 24 V DC, not 5 V or 3.3 V
Output of month 1: you can explain to a friend how a PLC differs from a regular computer, and what the scan cycle is. Don't move on until you can.
Month 2: First Hands-On Practice (Browser Simulator)
Now you write code. Don't buy hardware yet. Use a browser-based PLC simulator with scored scenarios.
Tools (free):
- Browser PLC simulator (free tier, 3 scenarios after free signup)
- Codesys Development System (free Windows IDE with built-in SoftPLC)
- OpenPLC Editor (free, runs on any OS)
Do these scenarios in this order:
- Motor Start/Stop — three-wire seal-in. The "hello world" of PLC programming. Full tutorial here.
- Traffic Light — pure sequencing with timers (TON, TOF, TP). Builds intuition for time-based control.
- Conveyor Sort — sensors trigger pushers / diverters. Builds intuition for sensor-driven sequencing.
Output of month 2: you've written 3 scored ladder programs and watched them run. You understand seal-in, basic timers, and sensor-driven decisions.
Month 3: Structured Text and State Machines
Ladder is enough for binary logic. Real machines need math, loops, string handling, and complex state — which is where Structured Text starts to dominate.
Read:
Practice:
- Rewrite your motor start/stop in Structured Text (use the same browser simulator).
- Build a 4-state state machine: Idle → Filling → Mixing → Discharge → Idle, with timers between states. The batch mixer scenario on plcsimulationsoftware.com is exactly this pattern.
- Build a PID temperature controller in Structured Text. The PID temperature scenario provides the platform; the PID tuning guide provides the theory.
Output of month 3: you can write Structured Text fluently for math-heavy or state-machine-heavy problems. You can choose between ladder and ST per problem.
Month 4: Vendor Specialisation
You can't ship a PLC project without picking a vendor — Siemens, Rockwell, Codesys-based, etc. Pick one based on your target job market.
Decision tree:
- US/Canada manufacturing → Allen-Bradley (Rockwell). Tool: Connected Components Workbench (free for Micro800) initially; Studio 5000 later via employer.
- Europe / global process → Siemens. Tool: TIA Portal (paid; €300/yr Basic for LOGO! and S7-1200) or browser simulator with Siemens dialect for free.
- Vendor-neutral, machine-builder OEM, IoT-curious → Codesys-based (Beckhoff TwinCAT, WAGO, Schneider). Tool: Codesys IDE (free).
Read your chosen vendor's tutorial:
Practice:
- Rebuild your motor start/stop in your chosen vendor's IDE.
- Recreate one machine scenario you've done in the simulator on the actual vendor toolchain.
- Note the vendor-specific differences: tag-based vs address-based, IDE conventions, library names.
Output of month 4: fluent in one vendor's IDE and conventions. Can read code from a real-world plant in that vendor's ecosystem.
Month 5: Real Hardware
You don't strictly need real hardware to get hired, but it dramatically accelerates learning and gives you something to show in interviews.
Two paths:
Path A: Raspberry Pi + OpenPLC (~$80 total)
- Buy a Raspberry Pi 4 (4 GB), a 24V industrial DIN-rail PSU, a few optocoupler-isolated input modules, a relay output module, push buttons and LEDs.
- Install OpenPLC runtime on the Pi.
- Wire up a small machine — three buttons, two lights, a small motor with a relay.
- Deploy your motor start/stop scenario from your laptop to the Pi.
- See our Arduino and Raspberry Pi PLC guide for the full build.
Path B: AutomationDirect Click Trainer (~$200)
- The Click "starter kit" with C0-00DD1-D CPU + I/O modules + power supply.
- Free Click Programming Software.
- Wire real industrial inputs and outputs.
- More representative of a real production small-PLC environment.
Output of month 5: you've built a real machine — wires, relays, lights, buttons — and your code makes it work. This single experience separates "watched videos" from "did it".
Month 6: Portfolio + Apply
You're ready to be hired. Spend month 6 packaging what you've built and getting it in front of employers.
Portfolio:
- Document 5 substantive scenarios: motor start/stop with E-stop and overload, traffic light, conveyor sort, batch mixer state machine, PID temperature loop.
- For each, document: requirements, design (ladder + ST as appropriate), test results, screenshots.
- Most browser PLC simulators export PDF portfolios. Use one. Send the PDF as your interview leave-behind.
Network:
- LinkedIn: connect with controls engineers, automation integrators, and PLC programmers in your target region.
- Local trade groups: ISA chapters, IEEE Industry Applications Society, regional automation meetups.
- Trade shows if accessible: Automate, SPS, Pack Expo.
Apply:
- Junior controls engineer
- PLC programmer (entry)
- Automation technician
- Maintenance technician (controls focus)
- Field service engineer (vendor)
- Apprentice / trainee positions at integrators
Be ready for a 1-3 month job-search timeline. Most hires happen through referral or industry contacts; cold applications to large companies have low conversion. Smaller integrators and OEM machine-builders are more receptive to self-taught candidates with strong portfolios.
What to Avoid While Learning
Don't buy a paid course before getting hands-on. RealPars, PLC Academy, and Udemy courses are nice-to-have, not need-to-have. Free YouTube + browser simulator + this site's tutorials cover the same ground for $0. Buy paid content as supplement, not as primary path.
Don't buy a vendor PLC IDE licence as a self-taught learner. TIA Portal, Studio 5000 — these are $300-$8,000/yr per seat. Wait until employed; the employer pays.
Don't skip the scan cycle mental model. Engineers who didn't internalise it produce code that "works" in simulation and fails on real hardware. Take the time.
Don't ignore safety. Even in simulation, build E-stops and interlocks into every scenario. The reflex matters.
Don't get stuck on vendor specifics in month 4. Pick one vendor, spend a month, move on. You'll learn the second vendor when you're employed.
Realistic Timeline
The 6-month roadmap assumes ~10 hours/week of focused effort. At 5 hours/week it's 12 months. At 20 hours/week it's 3 months. Adjust expectations to your actual hours.
Most self-taught engineers don't hit "ready to apply" until month 6-9 because life happens. That's fine. The path is the same; the calendar slows or accelerates.
Key Takeaways
- A realistic self-taught path takes 6 months at 10 hours/week.
- Total cost: $0-$200 (optional Pi or Click hardware in month 5).
- Don't pay for vendor licences while learning; the employer pays once you're hired.
- Don't pay for courses upfront; free YouTube + browser simulator + tutorials cover the ground.
- Six months sequenced as: foundations → practice → sophistication → vendor → hardware → portfolio.
- Internalise the scan cycle in month 1. Pick one vendor in month 4. Build a real machine in month 5. Apply in month 6.
