Diagnose wiring faults, logic errors, runtime failures, and scan-order bugs — all in a free browser PLC simulator with a live auto-grader. No $500 course, no hardware panel, no install.
Join 800+ learners practicing PLC programming
First fault scenarios are free. Create a free account to save your progress.

Why this exists
Traditional PLC troubleshooting training is sold as hardware panels costing $5,000+, or as CD-ROM/DVD courses from providers like Bin95, Koldwater, and Amatrol that have not materially updated their content in a decade. Both assume you have a classroom, an instructor, and a budget. We are the browser alternative: free, auto-graded, and accessible on any device.
| Product | Price | Access | Auto-grader |
|---|---|---|---|
| Amatrol T5553 fault panel | $5,000–8,000 | Physical hardware | No |
| Bin95 PLC troubleshooting | $200–400 | Windows software | No |
| Koldwater training kit | $300–600 | Hardware + DVD | No |
| TPC Training Systems | $1,000+ | LMS / classroom | Limited |
| This simulator (free tier) | Free | Any browser, any OS | Yes |
| This simulator (Pro) | Subscription | Any browser, any OS | Yes — full track |
What is inside
An open circuit in the field wiring, a shorted sensor, transposed terminals, or a disconnected 24 V supply. The ladder looks correct but the input never changes state — the field device is the problem, not the program.
The wiring is fine but the ladder logic itself is wrong — a contact type is incorrect, an interlock is missing, or a coil references the wrong address.
The program compiled and the wiring is correct, but something fails during execution: a sensor sends a constant signal, a card fault freezes an output, or a data value is out of expected range.
The PLC scan is deterministic and top-to-bottom within a rung/network. A coil written on rung 5 will not be seen by an XIC on rung 3 in the same scan. Scan-order bugs cause intermittent or off-by-one behaviour that is hard to spot without knowing the rule.
The method
Experienced technicians do not poke randomly. They follow a repeatable diagnostic method that moves from symptom to root cause in the fewest steps. Every fault scenario in our simulator is designed to reinforce this method.
What does the machine NOT do? Write it down exactly. "Motor does not start" is a symptom. "I think the sensor is bad" is a hypothesis — save that for step 3.
Find the output coil that controls the symptom device. Look at every contact in its rung. Is the rung false? Which contact is blocking power flow?
If the output coil is true but the actuator is not moving, force the output and see if the actuator responds. If it does: the problem is in the ladder or a field input. If it does not: you have a field wiring or hardware fault.
Walk rung by rung backwards from the false coil. Each false contact is a candidate. Check its field device, its wiring, and its address. Stop when you find the rung with a false input that should logically be true.
Make the minimum change needed to resolve the root cause. Clear any forces. Cycle the machine through a full test. Confirm the original symptom is gone and no new symptoms appear.
How it works
Each scenario opens with a running machine and a symptom description. You use the in-browser ladder monitor and I/O panel to diagnose the fault, apply the fix, and submit. The auto-grader checks your solution and tells you exactly what was wrong.
A running machine simulation with a fault already injected. The symptom is described in one sentence.
Toggle inputs, watch rungs energise or stay dark, force outputs to test field hardware. No Rockwell software needed.
The auto-grader checks whether you found the root cause and applied the correct fix. Full explanation on completion.
Who this is for
You already understand field wiring and motor control. The browser fault simulator bridges the gap to reading ladder logic and using the five-step method on a PLC system.
No factory floor access? No $5,000 hardware kit? Twelve fault scenarios in a browser are better preparation than zero hands-on practice — and you can do them at 2 AM.
Maintenance and controls tech interviews typically include a verbal fault walkthrough ("the conveyor stops randomly — how do you diagnose it?"). Practising 12 faults gives you a clear, confident answer.
Design engineers who understand fault diagnosis are rare and valuable. The four fault types here align directly with what maintenance teams deal with on deployed systems you designed.
Keep exploring
No $500 course. No hardware panel. No install. Free to start.