How to Learn PLC Programming at Home (No Hardware)

If you've been searching how to learn PLC programming at home, you've probably hit the same wall everyone hits: half the internet says you need a physical PLC and a R20 000 training rig, the other half points you at video courses that never make you write a rung yourself. The truth sits elsewhere: you can build genuine PLC programming skill at your kitchen table with nothing but a laptop and a browser simulator, and this page gives you the concrete 30-day plan to do it.

Start tonight, free →

The short answer

• Yes, you can learn PLC programming at home. The logic, timers, sequences and fault-finding all run in a browser simulator with the same scan behaviour as real hardware.
• Don't buy a training rig first. R12 000–R25 000 on hardware before you can write a seal-in rung is the classic wasted purchase.
• A realistic plan is 30 days, about an hour a day: contacts and coils in week one, timers and counters in week two, sequences in week three, fault-finding in week four.
• It runs on a basic laptop, on battery, which means load-shedding doesn't get a vote in your study schedule.
• Cost for the first month: about R220 on Basic for the full plan, or R0 if you stay on the free tier and stop after the timers.

Why a training rig is the wrong first purchase

The instinct is understandable. PLCs are physical things, so surely you need one. Search for home PLC kits and you'll find training rigs (a small PLC, some buttons and lamps on a board, maybe an HMI) at R12 000 to R25 000, plus the brand-name software licensing that sometimes sits on top.

Here's what actually happens to most of those rigs. The new owner wires the demo program, runs it, feels great for a weekend, and then stalls, because the rig came with hardware but no syllabus, no graded exercises, and no answer to "what should I build next?" The rig ends up in a cupboard, and the money it cost would have funded eight years of simulator subscription.

The deeper reason it's the wrong first purchase: in your first month, the skill you're building is logic, not wiring. A contact, a coil, a seal-in, a timer — these behave identically in a decent simulator and on a R25 000 rig, because both implement the same IEC 61131-3 scan semantics. The standard itself is published at iec.ch, and the background on how PLCs execute it is well covered in the Wikipedia PLC article. Hardware adds value later, when you're learning wiring and physical fault-finding. It adds nearly nothing to month one except cost and setup friction.

We've written a full comparison of the two routes at PLC training kit vs simulator: what a kit teaches that a simulator can't, and the reverse. The summary: simulator first, hardware later, and by the time "later" arrives you may get hardware time for free at a workshop or on the job.

The 30-day at-home plan

This is the centrepiece of the page. It assumes roughly an hour a day, five or six days a week, on a laptop. Every exercise linked here runs in the browser; the early ones sit on the free tier.

Week 1 — contacts, coils and the seal-in

Start with the alphabet. Read the ladder logic basics tutorial on day one; it covers contacts, coils, the scan cycle and the trap everyone falls into with normally-closed stop buttons. Days two and three, build rungs in the sandbox until placing an XIC contact feels boring. AND two contacts in series, OR them in parallel, predict the output before you run it, then run it and check.

Days four to seven belong to one circuit: the start-stop seal-in. It's the "hello world" of industrial control and the rung interviewers ask for on whiteboards. Build it, run it, then break it on purpose — swap the stop contact type and watch the motor misbehave, remove the seal-in branch and watch the motor die when you release start. By Sunday you should be able to write it from a blank canvas in under two minutes, no reference.

Week 2 — timers and counters

Read timers and counters first; the TON/TOF/RTO distinctions matter more than they look. Then two exercises. The flashing beacon timer teaches the two-timer flasher pattern, the first circuit where the scan cycle stops being theory and starts explaining why your beacon won't flash. Spend three days on it and its variations: change the on-time, the off-time, add a second beacon out of phase.

Then the bottle counting line: a CTU counting product, a reset, and a target count driving an output. Counters look trivial and then bite — what happens when the count target changes mid-batch? When does the done bit drop? Break it, watch it, fix it.

Week 3 — sequences

This is the week the work starts feeling like real plant logic. The traffic light sequence is your first state machine: red, green, amber, timed transitions, one state active at a time. Most self-taught learners write it badly first (a tangle of timers all running at once), and that's fine. Writing it badly and then restructuring it around states is the lesson.

Follow with the car wash sequence, which adds what real sequences have: a start condition, stages that hand over to each other, and an abort path that has to leave everything in a safe state. If week three takes you nine days instead of seven, take the nine. Sequencing is the skill that separates "did a PLC course once" from "can write control logic".

Week 4 — fault-finding and a small project

Fault-finding is the skill employers actually pay for. Read PLC troubleshooting for the systematic half-split method (not guess-and-poke), then put the month together on the silo fill exercise: level sensors, a fill valve, a pump interlock, alarm states. Build it from the spec. When it works, do the most valuable thing on this whole page: sabotage it. Change one contact, walk away for ten minutes, come back and find the fault using only the live bit states. Do that five times. That loop — break, forget, diagnose — is the closest thing to standby-call experience you can get at a kitchen table.

After day 30 you won't be employable yet, and anyone who says a month does it is lying. What you'll have: real reading and writing fluency in ladder, a working fault-finding method, and the proof that you like the work enough to continue. The path from there runs through the rest of the curriculum and, eventually, one short hands-on wiring workshop — the only part of this trade a home setup genuinely can't deliver.

A few habits make the plan stick, learned from watching at-home learners succeed and stall. Keep a paper notebook next to the laptop and sketch each circuit by hand before you build it — drawing a rung forces you to think in rungs, and it's exactly what you'll do on a whiteboard in interviews. Name your tags properly from day one: StartPB, StopPB, MotorRun, never Input1 and Output3. Sloppy naming is the single most visible tell of a self-taught beginner, and it costs nothing to avoid. And end every session by breaking something on purpose and fixing it. Ten minutes of deliberate fault-injection per day compounds into the diagnostic instinct that four weeks of only-building never produces.

The load-shedding advantage nobody mentions

A practical South African point. Classroom courses and physical training rigs both assume mains power and, for classrooms, that you can get somewhere. A browser simulator needs a laptop battery and a phone hotspot at most (sessions are light on data, rungs and bit states rather than streaming video), so you can practise at the kitchen table straight through an outage window. Stage 4 doesn't get a vote in whether you practise tonight.

That sounds like a small thing until you're three weeks into a habit. The single biggest predictor of whether at-home learners finish is whether daily practice survives interruptions, and in SA, power interruptions are the scheduled kind. A study plan that dies whenever the lights do is a plan you'll abandon by week two. One that runs on a charged laptop through a two-hour window is one you'll actually keep — and a one-hour exercise fits a load-shedding block almost exactly, which is grimly convenient.

What it costs

The whole 30-day plan above, priced honestly:

Option	Price	In rand (approx.)
Simulator — Free tier	$0	R0 — sandbox + first six lessons covers week 1 and the timer half of week 2
Simulator — Basic	$12/month	~R220/month — full curriculum; needed for the counters, sequences and fault-finding weeks
Simulator — Pro	$29/month	~R540/month — adds cert packs and portfolio export
Simulator — Teams	$199/seat/year (min 5 seats)	~R3 700/seat/year — training centres and employers
Home training rig	R12 000 – R25 000	hardware, no syllabus, no grading
SA classroom course	R4 100 – R17 595	one to five days away from home

Worst case for the full month at home: about R220. The rig costs fifty times that and the classroom week up to eighty times, and neither fits around a job the way an hour a night does. Current tiers are on the pricing page; for how the classroom market prices itself, see PLC course prices in South Africa.

Common questions

Can you learn PLC programming at home?

Yes — the programming itself, fully. Ladder logic, timers, counters, sequencing and logic-level fault-finding all run in a browser simulator with the same scan behaviour as hardware. What you can't learn at home is physical wiring and panel work; plan one short hands-on workshop for that after the logic is solid, not before.

Do I need a PLC to practise on?

No, and buying one first is the most common money mistake in self-taught PLC learning. A simulator gives you unlimited practice on the logic for R0–R220 a month; a R20 000 rig gives you the same logic plus wiring practice you're not ready to use yet. Get hardware time later — at a workshop, or on the job.

How long does it take to learn PLC programming?

Basics in about a month at an hour a day, as the plan above lays out. Competent enough to be useful, with solid sequences, real fault-finding reflexes and a portfolio, takes most part-time learners six to nine months. The 30 days isn't the destination; it's the proof you'll get there.

How hard is it to learn PLC at home without a teacher?

Harder than the course adverts admit, and the gap isn't the notation. On a site, an artisan glances at your rung and says "your stop contact's the wrong type" in four seconds; at the kitchen table, nobody does, and a beginner can stare at their own broken logic for an hour without seeing it. Two things stand in for the mentor: the grader, which runs your code against test scenarios and fails you with reasons, and the deliberate fault-injection habit from week four. The other honest hard part is consistency, which is why this page prescribes a small daily habit rather than weekend marathons.

What computer do I need?

Any laptop that runs a modern browser — the simulator has no installation and no licence dongle, and a mid-range machine from five years ago is fine. That's a deliberately low bar: the brand-name engineering suites you'll meet later on the job want strong Windows machines, but you don't need one to learn.

Write your first rung tonight →

What we don't claim

We're not SAQA-registered and not MerSETA-accredited, and finishing this 30-day plan earns you skill and a completion record, not an NQF-listed qualification. We don't claim a month at home makes you employable — it makes you fluent in the basics, which is a different and honestly-stated thing. We don't claim a simulator replaces every hour on real hardware: wiring, panel-building and live plant fault-finding still have to happen on physical equipment, later and ideally on someone else's budget. And since the simulator in this plan is our own paid product (with a genuinely free tier), weigh this page knowing we benefit if you subscribe — then test the claim the cheap way, on the free tier, before spending anything.