Concealed diagnosis
The assessment view removes the visible fault picker and fault-revealing schematic marks.
Browser-based electrical troubleshooting simulator
Find the hidden fault with circuit evidence.
Operate a real motor-control model, place virtual multimeter probes on named nodes, avoid unsafe test modes and submit the diagnosis. The fault changes the circuit—the answer is not written into the story.
Quick answer: the simulator covers control-supply, stop-chain, coil, contact, overload, phase and interlock faults across DOL, reversing and star-delta circuits. Pro adds concealed cases, scoring and saved records.
Experiential, not slide based
The reading changes because the circuit changed.
Each case starts the same tested motor-control engine with one server-selected fault. Inputs, coils, auxiliary contacts, poles, voltage nodes, current, rpm and protection states remain connected, so one fault creates consistent symptoms across the workbench.
Named probe nodes
Measure control points from 24 V through A1–A2 and three-phase points from L to T.
Live motor state
Contactor commands, phase condition, current, rpm, direction and dangerous overlap update over time.
Saved evidence
Correct attempts save diagnosis count, observations, safety mistakes, time and score.
Visual field guide
Eight diagrams explain the simulator, scoring and evidence.
Each figure answers a separate search question: the troubleshooting process, circuit zones, half-split method, meter modes, fault evidence, scoring, attempt state and saved record.
Method
One repeatable loop for every hidden fault
The workbench rewards a circuit hypothesis and a discriminating measurement—not random component swapping.
Circuit map
Separate the control path from the power path
A healthy coil command does not prove the three-phase path. Each zone has named evidence and a different fault family.
Meter strategy
Use voltage to bracket the open circuit
Measure at a point that divides the remaining suspects. The next test follows from the result.
Meter safety
Choose the energy state before the meter mode
The simulator permits voltage evidence while energised and blocks resistance or continuity on the live model.
Fault library
Seven fault families with distinct evidence
Fuse, stop, coil, pole, overload, phase and interlock failures change the actual circuit model instead of revealing a scripted answer.
Scoring
A transparent 70–100 assessment score
The server owns the final answer and score. Wrong diagnoses remain part of the attempt instead of resetting the exercise.
State machine
A pass exists only after a correct diagnosis
An incorrect submission returns the learner to evidence gathering. A completed attempt is idempotent and cannot be scored twice.
Training evidence
Keep the record that makes practice visible
Individuals see recent attempts; team administrators receive member-level rollups and an exportable evidence trail.
Current case library
Faults that force different measurements.
The library begins with starter circuits because they connect control logic, real components, three-phase power and a measurable load. It does not currently claim general residential wiring, PCB repair, arc-flash calculation or safety certification.
Blown control fuse
No contactor response; line power may still be present.
Best first evidence: Compare 24 V before and after F1.
Open STOP chain
START is ignored despite a healthy supply.
Best first evidence: Trace the first lost voltage through the fail-safe series path.
Open contactor coil
Command voltage reaches A1–A2 but the contactor does not pull in.
Best first evidence: Use live voltage evidence, then isolated continuity.
Welded main contact
Load-side voltage remains after the coil command drops.
Best first evidence: Treat the mismatched coil and pole state as dangerous.
Overload trip
The starter stops and the 95–96 path remains open.
Best first evidence: Identify protection state before attempting a reset.
Missing phase
The contactor closes but the motor will not accelerate normally.
Best first evidence: Compare every line and load phase pair.
Failed interlock
Opposing contactors can overlap during reversal or transition.
Best first evidence: Observe the dangerous state, isolate and diagnose the interlock.
Assessment records
Turn practice into evidence an instructor can review.
A completed simulation saves more than a completion tick. It records whether the learner diagnosed efficiently, gathered meter evidence and avoided an unsafe meter setup. Team rollups expose passes, average and best score per member.
See team trainingCase
The hidden work order and motor-control family
Diagnosis
Correct fault and number of submissions
Evidence
Measurement observations and unsafe setups
Outcome
Elapsed time, 70–100 score and timestamp
Simulation boundary
This browser lab develops circuit reasoning and test-selection habits. It does not prove practical competence, authorize electrical work, select PPE, perform a real absence-of-voltage test or replace employer and jurisdictional procedures.
Same login · separate assessment tier
Start with a hidden motor-control fault.
The assessment is built into the existing PLC Simulator Pro app, while the employer path keeps its own reporting, messaging and team workflow.
Questions
Frequently asked.
It includes hidden faults in DOL, reversing and star-delta motor-control circuits, recognizable starter hardware, live control and three-phase paths, named multimeter test points, voltage and isolated-continuity modes, motor behaviour, scored diagnoses and saved attempt evidence.
Runnable simulator field guide
Electrical fault training simulator: implementation, evidence and troubleshooting
Direct answer
Electrical fault training simulator becomes useful when it connects the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings with source through protection, contacts, coil or load and return with controller and physical feedback where applicable, then proves normal control voltage, continuity in an isolated state and resulting device behavior under normal, boundary, fault and recovery conditions. The objective is a repeatable engineering or learning result, not merely activity inside a page or tool.
This guide is written for electrical and maintenance learners practising schematic interpretation, safe-state decisions, voltage patterns and controlled fault isolation. The intended result is specific: the learner can state expected readings, locate the first electrical disagreement, identify one cause and prove restoration without trial-and-error replacement.
System map / 02
Six concepts that control the result
Treat these as connected checkpoints. Each checkpoint has an expected state, an observable state and a boundary to the next part of the system. That structure prevents a software indication from being mistaken for physical proof.
NODE 01observable
Define the operating contract
the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings. For industrial electrical fault diagnosis, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation.
NODE 02observable
Map the evidence path
source through protection, contacts, coil or load and return with controller and physical feedback where applicable. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected.
NODE 03observable
Prove normal operation
normal control voltage, continuity in an isolated state and resulting device behavior. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability.
NODE 04observable
Exercise a boundary case
open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path.
NODE 05observable
Diagnose a controlled fault
one hidden fault divided at the safest useful measurement boundary. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result.
NODE 06observable
Transfer and hand over
cause removal, bypass removal, stop-path test, normal operation and documented handover. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment.
Procedure / 03
A six-step practice and commissioning workflow
Run the steps in order the first time. Later, the same structure becomes a diagnostic loop: define the expected condition, observe the boundary, interpret the difference and choose one proving action.
- 01
Write the acceptance case
Convert the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings into initial conditions, one stimulus and observable pass criteria.
Evidence: Another person can repeat the case without guessing the intended result.
Avoid: Using page completion or an animation as the acceptance criterion.
- 02
Build the map
Document source through protection, contacts, coil or load and return with controller and physical feedback where applicable and name who owns each state or decision.
Evidence: Every request and result has a source, destination and useful inspection point.
Avoid: Using the same value as command, status and independent feedback.
- 03
Run the baseline
Apply normal control voltage, continuity in an isolated state and resulting device behavior from a clean start and record the expected evidence.
Evidence: Repeated runs produce the same bounded result.
Avoid: Changing several parameters before a baseline exists.
- 04
Challenge assumptions
Test open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback without changing the acceptance contract.
Evidence: Limits, timing and restart behavior reach defined states.
Avoid: Testing only one ideal sequence.
- 05
Isolate one failure
Introduce or analyse one hidden fault divided at the safest useful measurement boundary and locate the first disagreement.
Evidence: The proving action distinguishes the leading hypotheses.
Avoid: Resetting, forcing or replacing before evidence is retained.
- 06
Close the evidence loop
Complete cause removal, bypass removal, stop-path test, normal operation and documented handover and repeat the affected regression cases.
Evidence: A run is complete only when the requested behavior, stop behavior, fault response and recovery are observable from a fresh initial condition.
Avoid: Treating an acknowledged message or one successful rerun as handover.
Diagnostic matrix / 04
Symptoms, proving points and next actions
The table is a reasoning aid, not a parts-replacement chart. Preserve the initial symptom, inspect the named boundary and use the interpretation to choose the next controlled test. Site safety procedures and equipment manuals remain authoritative.
| Observed symptom | Inspect | Interpretation | Next proving action |
|---|---|---|---|
| The expected result is unclear | Requirement, initial state, actor, stimulus, units and pass condition | The operator, programmer and reviewer may be solving different versions of the task. | Rewrite one observable acceptance case before continuing. |
| Internal state changes but the outcome does not | Request, final owner, output or service boundary and independent feedback | A software or interface indication proves intent at one layer, not the complete outcome. | Trace the first boundary after the changing state. |
| Normal case passes but an edge case fails | Limits, timing, simultaneous events, reset and restart assumptions | The implementation contains a hidden assumption exposed by the changed condition. | Add the failed boundary as a permanent regression case. |
| The failure disappears after reset | Original symptom, histories, diagnostics, timestamps and active cause | Reset changed evidence or state without proving the initiating cause. | Reproduce under a controlled condition and preserve pre/post-event data. |
| Simulator and target disagree | Model boundary, software version, task timing, I/O behavior, data types and configuration | A learning model and the intended target do not share one of the recorded assumptions. | Reduce the case and verify against current target documentation. |
| The result cannot be explained | Prediction, observation, proving action, alternative hypotheses and limitations | Activity occurred but the evidence is not yet transferable or reviewable. | Have the learner defend the signal path and repeat a changed case. |
Product evidence / 05
What the browser practice can actually demonstrate
The browser runtime joins editable control state to visible I/O and machine or process behavior, allowing the same initial conditions and stimuli to be replayed.
Where simulation stops
The de-energized browser model cannot authorize live work, set arc-flash boundaries, select PPE or replace employer procedures and supervised physical qualification.
Commissioning notebook / 06
Six cases that turn the concepts into evidence
Use these as written briefs rather than click-through instructions. For every case, state the expected condition before acting, retain the first useful observation and explain why the final result proves the requirement. A different program or component choice can still be correct when it produces the same bounded behavior and evidence.
Case 01
predict → observe → prove
Prove define the operating contract
Engineering context. the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings. For industrial electrical fault diagnosis, record the initial condition, actor, requested change, observable result and stopping condition before selecting a tool or implementation. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Write the acceptance case” stage of the workflow: convert the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings into initial conditions, one stimulus and observable pass criteria. The acceptance record should show this result: another person can repeat the case without guessing the intended result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The expected result is unclear” as one bounded deviation. Inspect requirement, initial state, actor, stimulus, units and pass condition The working interpretation is that the operator, programmer and reviewer may be solving different versions of the task. The next proving action is to rewrite one observable acceptance case before continuing. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using page completion or an animation as the acceptance criterion. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What should I learn first about industrial electrical fault diagnosis? A defensible short answer is: Start with the operating contract and evidence path: the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings, followed by source through protection, contacts, coil or load and return with controller and physical feedback where applicable. Add advanced features only after the baseline is predictable.
Case 02
predict → observe → prove
Prove map the evidence path
Engineering context. source through protection, contacts, coil or load and return with controller and physical feedback where applicable. Separate request, internal state, output or service, physical or user-visible result and independent feedback so each boundary can be inspected. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Build the map” stage of the workflow: document source through protection, contacts, coil or load and return with controller and physical feedback where applicable and name who owns each state or decision. The acceptance record should show this result: every request and result has a source, destination and useful inspection point. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Internal state changes but the outcome does not” as one bounded deviation. Inspect request, final owner, output or service boundary and independent feedback The working interpretation is that a software or interface indication proves intent at one layer, not the complete outcome. The next proving action is to trace the first boundary after the changing state. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is using the same value as command, status and independent feedback. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How do I practise industrial electrical fault diagnosis effectively? A defensible short answer is: Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
Case 03
predict → observe → prove
Prove prove normal operation
Engineering context. normal control voltage, continuity in an isolated state and resulting device behavior. Run more than one cycle from a known state and retain the values, timings or artifacts that demonstrate repeatability. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Run the baseline” stage of the workflow: apply normal control voltage, continuity in an isolated state and resulting device behavior from a clean start and record the expected evidence. The acceptance record should show this result: repeated runs produce the same bounded result. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Normal case passes but an edge case fails” as one bounded deviation. Inspect limits, timing, simultaneous events, reset and restart assumptions The working interpretation is that the implementation contains a hidden assumption exposed by the changed condition. The next proving action is to add the failed boundary as a permanent regression case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is changing several parameters before a baseline exists. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: What counts as proof of competence? A defensible short answer is: A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Case 04
predict → observe → prove
Prove exercise a boundary case
Engineering context. open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback. Choose minimum, maximum, simultaneous, delayed or restart conditions that reveal assumptions hidden by the happy path. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Challenge assumptions” stage of the workflow: test open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback without changing the acceptance contract. The acceptance record should show this result: limits, timing and restart behavior reach defined states. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The failure disappears after reset” as one bounded deviation. Inspect original symptom, histories, diagnostics, timestamps and active cause The working interpretation is that reset changed evidence or state without proving the initiating cause. The next proving action is to reproduce under a controlled condition and preserve pre/post-event data. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is testing only one ideal sequence. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Why test faults and restart behavior? A defensible short answer is: Because one hidden fault divided at the safest useful measurement boundary or open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback can expose assumptions that never appear during ideal startup and steady operation.
Case 05
predict → observe → prove
Prove diagnose a controlled fault
Engineering context. one hidden fault divided at the safest useful measurement boundary. Preserve the first symptom, divide the system at a measurable boundary and change one condition only after predicting the result. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Isolate one failure” stage of the workflow: introduce or analyse one hidden fault divided at the safest useful measurement boundary and locate the first disagreement. The acceptance record should show this result: the proving action distinguishes the leading hypotheses. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “Simulator and target disagree” as one bounded deviation. Inspect model boundary, software version, task timing, I/O behavior, data types and configuration The working interpretation is that a learning model and the intended target do not share one of the recorded assumptions. The next proving action is to reduce the case and verify against current target documentation. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is resetting, forcing or replacing before evidence is retained. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: Can browser practice replace official software or hardware? A defensible short answer is: No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
Case 06
predict → observe → prove
Prove transfer and hand over
Engineering context. cause removal, bypass removal, stop-path test, normal operation and documented handover. Restore normal state, remove temporary changes, repeat affected checks and document which claims remain limited to the learning environment. Begin with a written normal condition and identify which request, state, physical result or communication value will provide independent confirmation. Do not begin by changing the configuration; the initial state is part of the evidence and should remain reproducible.
Controlled setup. Use the “Close the evidence loop” stage of the workflow: complete cause removal, bypass removal, stop-path test, normal operation and documented handover and repeat the affected regression cases. The acceptance record should show this result: a run is complete only when the requested behavior, stop behavior, fault response and recovery are observable from a fresh initial condition. Record initial conditions, the exact stimulus and the observation point so another learner can repeat the case without relying on your memory.
Fault challenge. Introduce or analyse “The result cannot be explained” as one bounded deviation. Inspect prediction, observation, proving action, alternative hypotheses and limitations The working interpretation is that activity occurred but the evidence is not yet transferable or reviewable. The next proving action is to have the learner defend the signal path and repeat a changed case. Change only one condition before observing the result, and preserve timestamps or measurements where timing matters.
Review and recovery. The most common trap here is treating an acknowledged message or one successful rerun as handover. After restoring the cause, repeat the normal case and at least one stop, timeout, disconnect or restart boundary relevant to this topic. Remove temporary forces and bypasses, return the model to a known state and retain the evidence that both operation and recovery are deliberate.
Explain it aloud: How should progress be documented? A defensible short answer is: Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
Answer surface / 07
Questions people ask about Electrical fault training simulator
These concise answers define the operating, training and product boundaries most often missed in broad summaries. The full workflow and diagnostic table above provide the evidence behind them.
What should I learn first about industrial electrical fault diagnosis?
Start with the operating contract and evidence path: the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings, followed by source through protection, contacts, coil or load and return with controller and physical feedback where applicable. Add advanced features only after the baseline is predictable.
How do I practise industrial electrical fault diagnosis effectively?
Use short cases with known initial conditions, a written prediction, one action and an observable result. Then alter a boundary or fault and explain why the evidence changed.
What counts as proof of competence?
A repeatable artifact or system result plus an explanation of the signal path is stronger than time spent, screenshots or a copied answer. Physical competence requires separate supervised evidence.
Why test faults and restart behavior?
Because one hidden fault divided at the safest useful measurement boundary or open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback can expose assumptions that never appear during ideal startup and steady operation.
Can browser practice replace official software or hardware?
No. It can build concepts and diagnostic reasoning. Exact firmware, I/O electrical behavior, networking, safety and commissioning require current official tools, documentation and target equipment.
How should progress be documented?
Keep the requirement, initial state, program or configuration, observed values, fault hypothesis, proving action, recovery result and a concise limitations statement.
What should I do when the answer differs from a guide?
Check assumptions, version, units and initial state first. Reduce the case, compare one boundary at a time and prefer current primary documentation for target-specific behavior.
When is a industrial electrical fault diagnosis exercise finished?
A run is complete only when the requested behavior, stop behavior, fault response and recovery are observable from a fresh initial condition.
Continue the signal path / 08
Related practice and reference pages
Electrical troubleshooting guideContinue from the circuit purpose, energy state, normal sequence, named nodes, approved measurement and expected readings.PLC wiring simulatorContinue from source through protection, contacts, coil or load and return with controller and physical feedback where applicable.Motor-control simulatorContinue from normal control voltage, continuity in an isolated state and resulting device behavior.PLC troubleshooting methodContinue from open conductors, failed contacts, blown protection, wrong reference, phase loss and intermittent feedback.
Primary and first-party references
Troubleshooting learning path
Diagnose from evidence instead of replacing parts
Establish the expected state, isolate the failed signal path, test one hypothesis and prove the repair under the original conditions.