When a production line goes down, the pressure to get it running again is immense. Effective PLC troubleshooting is a critical skill that separates experienced automation engineers from novices. A systematic approach can dramatically reduce downtime and prevent recurring faults.
The Systematic Approach
Never start troubleshooting by randomly changing things. Follow a structured methodology:
Step 1: Gather information
- Talk to the operator: What happened? What was the machine doing? Were there any unusual sounds, smells, or behaviours?
- Check the HMI/SCADA for active alarms and fault messages
- Review the alarm history for patterns or recurring faults
Step 2: Observe the system
- Look at the PLC status LEDs (RUN, STOP, ERROR, BUS FAULT)
- Check for obvious physical damage, loose wiring, or disconnected cables
- Observe the state of outputs (are motors running? are valves in the correct position?)
Step 3: Analyse the programme
- Go online with the PLC using TIA Portal or the appropriate programming software
- Monitor the programme logic in real time to see which conditions are met and which are not
- Use the cross-reference function to trace signals from inputs through logic to outputs
Step 4: Isolate the fault
- Determine whether the fault is in the input (sensor, wiring), the programme (logic error), or the output (actuator, wiring, power)
- Use force functions cautiously (and only with proper authorisation) to test individual circuits
Step 5: Repair and verify
- Fix the identified fault
- Test the repair thoroughly before returning the machine to production
- Document the fault, cause, and corrective action
Common PLC Faults and Their Causes
PLC in STOP mode:
- Programme error (division by zero, array index out of bounds)
- Hardware fault (defective module, power supply failure)
- Memory card error or programme corruption
Input not registering:
- Faulty sensor or wiring
- Incorrect input module configuration (voltage type, filter settings)
- Input module hardware failure
Output not activating:
- Fuse blown on output module or external circuit
- Relay or transistor failure on output module
- Incorrect programme logic or interlock not satisfied
Communication failure:
- Network cable disconnected or damaged
- IP address conflict or incorrect network configuration
- Switch or network component failure
Using Diagnostic Tools
Modern PLCs provide powerful diagnostic tools:
- Online monitoring: Watch programme execution in real time
- Watch tables: Monitor specific variables and force values for testing
- Trace functions: Record variable changes over time for intermittent faults
- Web server: Access PLC diagnostics from any web browser without programming software
- Diagnostic buffer: Review the chronological list of PLC events and faults
Documentation Is Key
Always document your troubleshooting findings:
- Record the fault symptoms, root cause, and corrective action
- Update maintenance logs and asset management systems
- Share findings with the engineering team to prevent recurrence
Develop Your Skills at EDWartens UK
Our PLC maintenance and troubleshooting courses at EDWartens UK use fault-injection scenarios on real hardware to build practical diagnostic skills. Students learn to systematically identify and resolve faults under realistic time pressure, preparing them for the demands of industrial maintenance roles.