PLC I/O module faulted / showing module error
An I/O module shows a fault LED or the controller reports a module error — a whole block of inputs/outputs is dead or unreliable, not just one channel.
Safety first
A faulted output module can leave outputs in an unknown state. Confirm what those outputs control and make the area safe before working. Follow site procedures for controller work.
Isolate, lock out / tag out, and prove dead before working unless a live test is specifically required, authorised, and carried out under proper supervision. Always follow local regulations, your site procedures, and the equipment manufacturer's documentation.
Full detail — causes, the why, and common mistakes.
Likely causes
Ranked from most to least likely.
- 1
Module field supply / fuse lost
Most likelyThe module's field power or its fuse has gone, killing a whole block of I/O.
- 2
Module not seated / backplane connection
#2A module not fully seated, or a backplane/connector fault, drops the whole module.
- 3
Configuration mismatch
#3The configured module doesn't match the installed one (after a swap), so the controller flags an error.
- 4
Field fault tripping the module's protection
#4A short or overload on the field side trips the module's protection and faults it.
- 5
Failed module
Least likelyThe module itself has failed.
Reports are saved on this device to reflect what you actually find.
Testing sequence
Work through one test at a time. Expected reading and what each result means.
Read the exact module fault on the controller and check the module's own status LEDs.
A clear fault description and status indication.
The fault points you to a cause group — proceed accordingly.
If ambiguous, start with field supply and seating.
View all expected readings at once
Fault-finding flowchart
The same logic as a decision tree.
- 1start
I/O module faulted
→ step 2 - 2decision
Is the module's field supply/fuse good and is it seated?
Yes→ step 3No→ step 4 - 3decision
Does config match and is the field side fault-free?
Yes→ step 5No→ step 6 - 4result
Restore field supply/fuse or reseat the module.
- 5result
Suspect a failed module — replace per procedure.
- 6result
Correct configuration / clear the field fault.
Common mistakes apprentices make
- Replacing a module before checking its field supply/fuse.
- Not fully seating a module after maintenance.
- Config mismatch after fitting a slightly different module.
- Missing a field short that keeps tripping the module.
When to stop & escalate
Module replacement and configuration changes follow site controller procedures with backups. A repeating field fault should be found before re-energising the module.
If you're past your competence, authorisation, or the safe limits of the job — stop and hand it on. There's no fault worth getting hurt over.
Related faults
PLC input not reading despite a signal present
A field device is clearly providing a signal, but the PLC input bit/LED doesn't come on — the program never sees the input, so logic that depends on it won't run.
PLC output LED is on but the device doesn't work
The PLC output indicator says the output is energised, but the connected device (valve, contactor, lamp, motor starter) does nothing. The program thinks everything is fine.
PLC communication fault (network / remote I/O)
The PLC has lost communication with a device, remote I/O, HMI, or network — comms-fault indication, missing data, or remote I/O dropping out.