Learn
Practice
Assess
Record
Advance
Industrial maintenance troubleshooting
Anyone can guess a failed photoeye. Faultpath asks why you believe it is the photoeye — which checks you ran, in what order, what each one ruled out, whether the line was locked out before your hands went in, and whether you proved the repair.
Learn to diagnose, not memorize. In Assess mode a correct answer with no evidence behind it is reported as unsupported, and swapping parts until the machine runs scores below reasoning to the same fix.
No account · Nothing to install · Progress saved in this browser
Line 4 case conveyor
00:00
E-STOP CIRCUIT OPEN — CONVEYOR L4
Active alarm
Line 4 conveyor will not start. Operator says it stopped on its own and the start button does nothing.
37 things you could check. Each one costs time, and nothing reads until you go and read it.
Five stages, in the order you use them
01 · Learn
What normally fails, what a reading means, and the order to check things in — from lockout to PLC I/O.
02 · Practice
A machine with a hidden fault. You choose every check, each one costs time, and the evidence comes from the machine's state — not from a script.
03 · Assess
Assess mode judges each dimension separately, and safety is a gate nothing else on the run can buy back. Your profile turns runs into habits a single run cannot show.
Preview: 13 of 13 scenarios are not yet validated as an employment or qualification assessment, so a result describes what happened in a run.
04 · Record
Log the real faults you diagnose at work, in the same structure a debrief uses. It is the one thing here you cannot regenerate by playing again, and it exports as Markdown.
05 · Advance
Turn logged faults into the answers a technical interviewer probes for. It never writes the answer for you — it names what a strong answer touches and what your draft missed.
Alarms name symptoms, not causes. The lessons teach what a reading means, what normally fails, and what a machine is actually telling you.
The simulator hides a fault in a machine model. Every check costs time, every reading comes from the machine's state, and unsafe work is reachable — so avoiding it means something.
The debrief sets your path beside one good route and names the evidence you never collected. Then the next fault is one click away: fault, diagnose, debrief, next.