PLC troubleshooting faults usually trace back to ten causes: power supply problems, loose terminals, failed field devices, output module damage, communication errors, a CPU in stop or fault mode, battery or memory loss, forced bits, noise and earthing, and overheating. Check them in that order, because the first four account for most failures and take the least time to prove.
What you receive: if you need a hand on a live fault, send the PLC model, the fault lights and a description and we respond remotely the same day. Request a quotation
By Eng. Junaid Ali, KSA Industrial Automation Company. Published October 2026.
Work on live panels only if you are competent and authorised. Isolate and lock out the circuit before touching terminals, and follow your plant permit-to-work rules.
What are the 10 most common PLC troubleshooting faults?
The table gives each fault with its typical symptom and the first check. The order reflects how quickly each can be tested.
| # | Fault | Typical symptom | First check |
|---|---|---|---|
| 1 | Power supply problem | PLC dead or restarting | Measure 24 V DC at the PLC terminals under load |
| 2 | Loose or corroded terminal | Intermittent input or output | Inspect and re-tighten after isolation |
| 3 | Failed sensor or switch | Input stuck on or off | Check the input LED with the device operated |
| 4 | Output module or relay damage | Output LED on, load off | Measure voltage at the load terminal, check fuse |
| 5 | Communication error | Device offline on the HMI | Check cable, address, device name, duplicate IP |
| 6 | CPU in stop or fault | Run light off, fault light on | Read the diagnostic buffer or fault log |
| 7 | Battery or memory loss | Program lost after power cycle | Check battery status and backup storage |
| 8 | Forced input or output | Signal ignores the field | Look for forces in the online view |
| 9 | Noise and earthing | Random trips, noisy analogue values | Check shield earthing and cable routing |
| 10 | Overheating | Faults at hot hours | Check cabinet temperature, filters and fans |
How do you troubleshoot a PLC step by step?
- Ask what changed: a modification, a repair, a storm, a power dip.
- Look at the LEDs on the CPU, power supply and modules before connecting anything.
- Measure supply voltages at the PLC, not at the source.
- Go online and read the diagnostic buffer or fault log with timestamps.
- Compare the live state with the I/O list: input LED, field device, wiring.
- Test one hypothesis at a time and record the result.
- After the repair, run the affected sequence and back up the program.
Which faults need a closer look?
Three faults are often misread. A CPU in stop is frequently the result, not the cause: a watchdog or cycle-time fault, an array-index error or a missing module can stop it. Read the log before you restart it. Communication errors are often a duplicate address or a changed device name after a module replacement, not a cable fault. Forced bits left after maintenance are common and dangerous, because the program appears to ignore the field; a forced output can hold a valve open.
For Allen-Bradley controllers the equivalent tools are the major and minor fault logs in Studio 5000. For Siemens, the diagnostic buffer in TIA Portal shows the event, the module and the time. For Schneider Modicon, the status words and the EcoStruxure diagnostics play the same role. The logic of fault finding is the same on all three.
Worked example: a motor will not start
This is an example to show the method; your plant will differ. A pump motor does not start from the HMI. The PLC is in Run, and no fault light is on.
| Step | Observation | Conclusion |
|---|---|---|
| Check HMI | Start command shows sent | Command reaches the PLC |
| Check output LED | Q 4.0 lit | Program is calling for the start |
| Measure at contactor coil | 0 V | Break between the output and the coil |
| Check output fuse | Blown; fuse rated 2 A | Output side protected the module |
| Check coil resistance | 12 Ω; at 24 V, 24 ÷ 12 = 2 A | Coil draws 2 A, which is the fuse rating |
The coil draws exactly the fuse rating, so any inrush blows it. The fix is a correctly rated fuse and an interposing relay, not a bigger fuse on the module output. The test took six steps, no software changes and about twenty minutes.
When should you call for help on PLC troubleshooting faults?
Call when the fault repeats after a repair, when the log points to a CPU or module failure, when the program must be restored or changed, or when production is at risk and you lack spares. Keep the PLC model, firmware, fault code, time of failure and what changed to hand.
KSA Industrial Automation Company gives remote support the same day and attends site within one working day in the Eastern Province. Our PLC troubleshooting and emergency support service is the route for call-outs and support contracts. For repeat failures on an ageing system, a PLC retrofit and upgrade removes the cause. Changes to the logic itself belong with PLC programming services.
Common questions about PLC troubleshooting faults
How do you troubleshoot a PLC?
Start with power, then the status lights, then the diagnostic log, and then the I/O against the field device. Change one thing at a time and write each result down. Most faults are found in the first three checks without changing any program.
What causes a PLC to fault?
Common triggers are a program error such as a divide by zero or array overrun, an exceeded watchdog or scan time, a missing or failed module, a power dip and a battery or memory fault. The fault log names the cause.
What is PLC maintenance?
PLC maintenance is the planned care that prevents faults: backing up programs, checking supply voltages, cleaning filters, tightening terminals, testing batteries and reviewing logs. A short quarterly routine finds problems before they stop production.
How do I troubleshoot an Allen-Bradley PLC?
Read the fault codes in Studio 5000 under controller properties, and check the I/O tree for modules in fault. Verify the key switch position and the module LEDs. Then follow the same power, wiring and device checks as for any PLC.
What does PLC troubleshooting cost?
Cost depends on the response time needed, the controller platform, access to the site, the spares required and whether the work is a single call-out or a support contract. A proposal sets out the options and the response terms.
Facing PLC troubleshooting faults on a live plant? Send the PLC model, fault lights and a short description and receive a response within one working day. Email: inquiry@ksaindustrialautomation.com | Request a quotation