What are the four PLC fault families?

A useful first classification is wiring faults (open circuits, shorts, transposed terminals), configuration faults (wrong tag address, incorrect I/O card slot, scaling error), logic faults (wrong contact type, missing interlock, incorrect coil address), and intermittent faults (noise, heat, vibration or loose connections). The observed mismatch between field state, card LED, software tag, rung and output determines which family to investigate first.

What is the half-split troubleshooting method?

Half-split applies binary search to a control circuit. Instead of probing each component from one end, you measure at the midpoint of the circuit. If voltage is present at the midpoint, the fault is in the second half; if absent, it is in the first half. Each measurement halves the remaining search window. In a 16-component circuit, four measurements find any fault — versus up to 16 sequential tests.

What does a multimeter measure in a PLC fault diagnosis?

In live circuit diagnosis, the multimeter measures DC voltage (24 V control supply) or AC voltage (110 V or 230 V control) at terminals to confirm or eliminate each circuit segment. Continuity mode is used only on de-energised circuits to check for open cables, broken wires, or failed contacts. Never use continuity mode on a live circuit — it gives incorrect readings and risks a short. For sensors, measure the supply pin, then the signal pin, and compare to the PLC input LED.

How do I troubleshoot a PLC input that reads wrong?

Start at the I/O card LED. If the LED state matches the tag state in the ladder, the card is reading the field correctly — the fault is either in the field (LED off when it should be on = wiring or device fault) or in the logic (LED is right, tag is right, rung is still false = logic fault). If the LED and the tag disagree, the fault is in the software — wrong tag address, wrong I/O card slot assignment, or scaling configuration. That LED/tag comparison is the fastest split between field and software faults.

What PLC fault scenarios does the simulator include?

The fault library covers logic faults (wrong contact type, missing seal-in), configuration faults (address mismatch), runtime faults (stuck input, counter overflow, timer not resetting), scan-order faults, and field-circuit faults such as broken sensor supplies, polarity errors, relay contact swaps, shorts and broken returns. Availability varies by plan and entitlement; guided exercises use objective checks rather than exposing the answer first.

How do I troubleshoot a motor that does not start?

Identify which zone the fault is in before touching anything. Zone 1 — contactor coil circuit: measure voltage at A1–A2 on the contactor while the PLC output is ON. If zero volts, work back toward the supply fuse and overload relay NC contact (95–96). Zone 2 — overload relay: check the trip indicator; measure through the 95–96 contact. Zone 3 — control circuit: compare voltage at the PLC output card terminal to the voltage at contactor A1. Zone 4 — field wiring: check voltage on T1/T2/T3 while the contactor is closed. See the motor starter troubleshooting post for the full sequence.

Does simulated fault practice help with real hardware?

Yes — with an honest caveat. The simulator builds the diagnostic reasoning: the habit of following a method, the mental model of the control circuit, and the pattern recognition of fault types. Those transfer directly to real hardware. What a browser cannot replicate is safe probe technique on live terminals, the physical feel of a loose connection, or the experience of responding when something unexpected happens. Use the simulator to build the reasoning; use real hardware to build the hands-on reflex.

PLC Simulator

Fault Diagnosis

PLC Troubleshooting — Trace the Output Back to the Fault

Start at the failed machine output and move backward through command, permissives, PLC state, I/O and field devices. The seven-step method turns random checking into a bounded diagnosis you can practise on live faults.

Start a fault scenario Start free

Join 6500+ learners practicing PLC programming

First fault scenarios and wiring labs are free. Create a free account to save your progress.

PLC troubleshooting — 7-step method, four fault families, inputs to field

Where faults live

The four fault families

Before any diagnosis, identify the first observed mismatch. A field device, card LED, software tag, rung state and output command form an evidence chain; the first disagreement determines the fault family and next check.

PLC fault families — wiring, config, logic, intermittent, with symptoms, first checks, and tools — The four fault families and the first check for each.

Wiring fault

Symptom: Input never changes state despite field device operating
First check: Supply voltage at device; continuity back to I/O card
Tool: Multimeter
Trained by: Wiring fault labs: fault-01 through fault-08

Configuration fault

Symptom: Input changes but PLC ignores it, or wrong engineering-unit value
First check: Tag address, I/O card slot assignment, scaling block
Tool: Software monitor
Trained by: Fault scenarios: fault-03 (wrong address)

Logic fault

Symptom: Rung stays false even when all inputs appear correct
First check: Contact types (XIC/XIO), interlock conditions, coil address
Tool: Ladder monitor
Trained by: Fault scenarios: fault-01 (NO/NC swap), fault-02 (missing seal-in)

Intermittent fault

Symptom: Fault clears itself; reappears under load, heat, or vibration
First check: Connector seating, shielding, data logging over time
Tool: Multimeter + data log
Trained by: Fault scenarios: fault-08 (intermittent edge-case)

Evidence before replacement

See how each observation narrows the PLC fault window

These examples move from a visible machine symptom to a bounded cause, including input and output splits, scan-order behaviour, intermittent evidence and the verification step after the repair.

PLC troubleshooting workflow tracing a stopped conveyor motor through output, ladder logic, input and field overload trip to the root cause — 01Start from the failed load and trace the evidence backward. Here the output is correctly withheld because the overload-trip input blocks the run permissive.

PLC input fault comparison using proximity sensor state, input card LED, software tag and ladder rung to separate field, configuration and logic faults — 02Comparing the physical event, card LED, tag value and rung state splits one vague “input problem” into three different diagnostic paths.

PLC output troubleshooting matrix comparing output tag, module LED, control voltage and contactor state — 03For output faults, each mismatch narrows the boundary: command logic, module path, field wiring or actuator. Do not replace the load before locating the break.

PLC scan-order fault diagram comparing an internal bit read before write with corrected rung order and showing a one-scan output delay — 04The same Boolean logic can behave differently when rung order changes. A read-before-write pattern can leave an output one scan behind the intended state.

Intermittent PLC sensor fault trend correlating vibration spikes, input dropouts and motor stops before verifying a loose connector — 05Trends reveal repeatable correlations, but correlation is only a lead. Inspect and reproduce the suspected connection fault before declaring root cause.

Post-fix PLC troubleshooting verification checklist with forces cleared, full conveyor cycle passed, no new alarms and maintenance log saved — 06A repair is not finished when the symptom disappears. Clear forces, test the full cycle, look for new alarms and record the confirmed cause and corrective action.

The method

The 7-step PLC troubleshooting method

Every step eliminates a portion of the fault window. The direction is always inputs to field: define the symptom, confirm power, read the ladder, check the I/O card, trace the wiring, check the output, verify the fix.

7-step PLC troubleshooting method flowchart — inputs to logic to outputs to field — The seven steps from symptom to verified fix.

Define the symptom precisely

Write it down before touching anything. "Motor does not start" is a symptom. "I think the proximity sensor is bad" is a hypothesis. Keep them separate — you need the symptom clear before you form hypotheses.

Inputs → Logic → Outputs → Field is the direction of travel.

Confirm power — PLC running, I/O powered, no fault lights

Confirm PLC RUN LED, I/O card power LEDs, and supply voltage at the distribution point. A PLC in fault mode or a card with a blown supply fuse mimics logic and wiring faults.

Read the ladder — find the output that should be ON

Open the online ladder monitor and find the output coil for the device that is not operating. Walk the rung from left rail to right. Which contact is false when it should be true? That contact is your target.

Check inputs at the I/O card

For the blocking contact, check the input LED on the physical card. LED off = field fault (go to Step 6). LED on but tag false = configuration fault (wrong address or card slot). LED matches tag but rung still false = logic fault in the rung itself.

The LED/tag comparison is the fastest field-vs-software split.

Half-split the field wiring

Measure voltage at the I/O card terminal. If correct: trace toward the device, measuring at the midpoint of the remaining run. If zero: trace back toward the supply. Each measurement halves the fault window.

Check the output card and field actuator

Output LED lit but actuator not responding: break in wiring between card and actuator, or actuator fault. Output LED not lit but tag is true: output card fuse blown or card failure. Measure voltage at the actuator terminals while output is commanded ON.

Apply the fix and verify — no new symptoms

Make the minimum change needed. Clear all test forces. Cycle the machine through a full operational sequence. Confirm the original symptom is gone and no new symptoms appear. Document root cause and fix in the maintenance log.

Verify before you close the job.

Half-split: binary search through the fault window

Instead of probing from one end sequentially, measure at the midpoint of the circuit. Voltage present: fault is in the second half. Zero volts: fault is in the first half. Repeat — each measurement halves the remaining window. The PLC I/O boundary (card terminal vs field terminal) is the natural midpoint for most control circuits.

16 components, 4 measurements maximum — versus 16 sequential tests.

The diagnostic toolkit

A visual map of the fault-diagnosis method

Every fault is found in the same direction — symptom, inputs, logic, outputs, field. These diagrams are the mental models the method runs on: the decision flow, the I/O LED comparison, the field terminal, and the scan order that hides scan-order bugs.

The decision flow — symptom to inputs to logic to outputs to field.

Input I/O — the LED-vs-tag comparison that splits field faults from software faults.

The field terminal — where you half-split the circuit to trace a wiring fault.

Reading the rung — find the false contact that should be true.

The scan cycle — the rule behind one-scan delays and scan-order faults.

Motor starter zones — coil, overload, PLC output: isolate a no-start zone by zone.

Honest scope

What needs a real meter

The fault scenarios and wiring labs build diagnostic reasoning — the method, the mental model of the circuit, and pattern recognition of fault types. That transfers directly to real hardware. What a browser cannot replicate:

→Developing safe probe placement habits on live 24 VDC and 230 V AC terminals
→Recognising the physical signs of a burnt contact, corroded terminal, or cracked insulation
→The physical feel of a loose connector versus a tight one — caught before it causes a fault
→Correctly identifying polarity, phase, and common returns by sight in a real wiring arrangement
→Responding safely when something unexpected happens during live probing

Use the simulator to build the reasoning. Arrive at a real panel having already diagnosed sixteen simulated faults and you will be measurably faster than someone coming in cold.

What is inside

Logic-fault scenarios plus practical wiring fault labs

Each scenario injects a specific fault into a running machine simulation. Each wiring lab puts a fault in a field circuit and asks you to trace it with the virtual multimeter. Every one is auto-graded.

PLC troubleshooting training catalogue with logic, runtime, scan-order and practical wiring fault exercises — The full training catalogue — fault injection scenarios and wiring labs mapped to fault families.

Fault scenarios

Wiring fault labs

Go deeper

Detailed guides

Guide

PLC Fault Finding: 7 Steps from Symptom to Root Cause

Complete coverage of the 7-step method, multimeter discipline sequence, half-split technique, and how to approach all four fault families including intermittent faults.

Read the guide →

Guide

Motor Starter Troubleshooting: Contactor, Overload, and Control Circuit Faults

The three fault zones in a DOL motor starter — coil circuit, overload relay, and PLC output side — with the correct measurement sequence and overload trip diagnosis checklist.

Read the guide →

Keep exploring

Related practice

PLC troubleshooting simulator — the full browser fault simulator: 12 fault scenarios, live grader, no hardware required.
Fault scenario track — start with the first free fault scenario in the curriculum.
Motor starter wiring lab — practise the full DOL control circuit from PLC output card to contactor coil with injected faults.
Contactor chattering diagnostic guide — separate unstable commands, low coil voltage, control-circuit drop and mechanical failure.
PLC commissioning checklist — prove power, every I/O point, sequences, fault recovery and handover evidence.
Relay vs contactor — current ratings, contact types, and when to use each.
Motor starter vs contactor — overload relay, trip class, and why a bare contactor is not a motor starter.
PLC interview prep — timed interview-style scenarios including fault diagnosis walkthrough questions.

Questions

PLC troubleshooting FAQ

A systematic PLC troubleshooting method works from symptom to root cause using a fixed sequence of steps: define the symptom, confirm power, read the ladder, check inputs at the I/O card, trace field wiring, check output card and actuator, apply and verify fix. Each step eliminates a portion of the fault window. The alternative — random probing — takes longer and sometimes misses the root cause entirely.

Diagnose your first PLC fault in the next two minutes.

Free browser simulator. Auto-graded. No hardware panel, no $500 course, no install.

Start a fault scenario Start free

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.