PLC Troubleshooting: 10 Common Faults and How to Fix Them

Why Troubleshooting Skills Matter

Every PLC will eventually fail. Power surges, communication dropouts, sensor malfunctions, wiring faults, software bugs — the list of things that can go wrong on a factory floor is endless. The difference between a junior technician and a skilled automation engineer is the ability to systematically diagnose and fix these problems under pressure.

When a production line stops, every minute costs money. A pharmaceutical batch might need to be scrapped. An automotive assembly line might miss its shift target. The engineer who can find and fix the problem quickly is worth their weight in gold.

This guide covers the 10 most common PLC faults you will encounter and the systematic approach to fixing each one.

Fault 1: PLC CPU Goes to STOP Mode

Symptoms: CPU status LED turns red/amber. All outputs go to safe state. Production stops.

Common causes:
- Memory overflow (program too large for CPU)
- Hardware watchdog timeout
- Power supply voltage fluctuation
- Corrupt program download

Troubleshooting steps:
1. Check the CPU diagnostic buffer (every PLC logs the reason for going to STOP)
2. On Siemens: TIA Portal > Online > Diagnostics > CPU Messages
3. On Allen Bradley: RSLogix > Controller Properties > Major Faults
4. Address the specific fault code before switching back to RUN
5. Never force the CPU to RUN without understanding why it stopped

Fault 2: Communication Failure Between PLC and HMI

Symptoms: HMI shows "No Connection" or displays stale values. Alarms stop updating.

Common causes:
- Network cable disconnected or damaged
- IP address conflict on the network
- Communication driver mismatch
- Switch or router failure

Troubleshooting steps:
1. Ping the PLC from the HMI station (or from a laptop on the same network)
2. Check physical connections: cables, RJ45 connectors, switch port LEDs
3. Verify IP addresses: PLC and HMI must be on the same subnet
4. Check if other devices can communicate with the PLC (isolate the problem)
5. Restart the communication driver on the HMI if needed

Fault 3: Digital Input Not Responding

Symptoms: PLC program does not detect a sensor signal even though the sensor is working.

Common causes:
- Wiring fault (loose terminal, broken wire)
- Wrong input type (sourcing sensor on sinking input or vice versa)
- Input module failure
- Sensor output voltage below PLC threshold

Troubleshooting steps:
1. Measure voltage at the PLC input terminal with a multimeter
2. Check if the input LED on the PLC module lights up
3. If LED is on but program does not see it: check the input address in the program
4. If LED is off but sensor is working: check wiring between sensor and PLC
5. Try moving the wire to a spare input channel to test the module

Fault 4: Analog Input Reading Incorrect Values

Symptoms: Temperature, pressure, or level readings are wrong, jumping, or showing 0/max value.

Common causes:
- Incorrect scaling in PLC program (raw value to engineering units)
- Wrong input range configured (0-10V vs 4-20mA)
- Broken shield wire causing electrical noise
- Sensor calibration drift
- Loose terminal connection

Troubleshooting steps:
1. Check raw value in the PLC (before scaling). For 4-20mA: 4mA = 0%, 20mA = 100%
2. Measure the actual current/voltage at the PLC terminal with a process calibrator
3. Verify the input range configuration matches the sensor output
4. Check for noise: if the value fluctuates wildly, check cable shielding and routing
5. Re-calibrate the sensor or transmitter if the offset is consistent

Fault 5: Output Not Switching

Symptoms: PLC program shows the output as ON, but the physical device (motor, valve, solenoid) does not activate.

Common causes:
- Output relay contact worn out (common on relay-type outputs after millions of cycles)
- Overloaded output (current exceeds rating)
- External fuse blown
- Contactor coil failure
- Force table overriding the output

Troubleshooting steps:
1. Check if the output LED on the PLC module is ON
2. Measure voltage at the output terminal
3. Check for forced I/O in the PLC program (forces override normal logic)
4. Check external circuit: fuses, contactors, overload relays
5. If the output module has a blown fuse indicator, replace the fuse

Fault 6: PLC Program Running But Logic Not Working as Expected

Symptoms: The program is in RUN mode but the machine does not behave correctly. Sequences are wrong, timers are not timing, or conditions are not being met.

Common causes:
- Logic error in the program (wrong AND/OR conditions)
- Timer or counter preset values incorrect
- Data type mismatch (INT vs REAL)
- Subroutine not being called
- Incorrect program version deployed

Troubleshooting steps:
1. Go online with the PLC and monitor the program logic in real-time
2. Trace the logic path: which conditions are TRUE and which are FALSE?
3. Check variable values: are timers counting? Are counters incrementing?
4. Compare the online program with the project file (has someone made changes?)
5. Use cross-reference tools to find where a variable is written and read

Fault 7: Profinet/EtherNet-IP Device Drops Off Network

Symptoms: Remote I/O module, drive, or instrument loses communication intermittently.

Common causes:
- Electromagnetic interference (EMI) from VFDs or welding equipment
- Industrial Ethernet cable not rated for the environment (use Cat 6A shielded)
- Switch overloaded or not managed
- IP address conflict
- Firmware mismatch between PLC and device

Troubleshooting steps:
1. Check the device diagnostic page in the PLC
2. Monitor network traffic for errors (CRC errors, frame drops)
3. Check cable routing: keep Ethernet cables away from power cables
4. Use a managed switch with port diagnostics
5. Update device firmware to match PLC compatibility requirements

Fault 8: VFD (Variable Frequency Drive) Fault Code

Symptoms: Motor stops running. VFD display shows a fault code.

Common causes:
- Overcurrent (mechanical overload on the motor)
- Overvoltage (regenerative braking without a brake resistor)
- Ground fault (motor winding insulation breakdown)
- Overtemperature (insufficient cooling or ambient temperature too high)
- Communication timeout (if VFD is controlled via PLC)

Troubleshooting steps:
1. Read the specific fault code from the VFD display or via PLC diagnostics
2. Check the motor: is it free to rotate? Is the mechanical load normal?
3. Check drive cooling: fan running? Air filters clean? Ambient temperature?
4. For communication faults: check the cable and PLC communication settings
5. Reset the fault only after addressing the root cause

Fault 9: Safety System Tripped

Symptoms: Machine stops in safe state. Safety relay or safety PLC has tripped. Cannot restart.

Common causes:
- Emergency stop button pressed (check all e-stop stations)
- Light curtain interrupted
- Safety door interlock opened
- Safety relay wiring fault
- Safety PLC diagnostic fault

Troubleshooting steps:
1. NEVER bypass safety systems to restart the machine
2. Check all e-stop buttons (some may be hidden or in remote locations)
3. Check safety relay diagnostics LEDs for the specific fault channel
4. For safety PLCs: connect online and read the diagnostic buffer
5. Reset the safety system only after confirming the cause and ensuring it is safe

Fault 10: Power Supply Failure

Symptoms: Entire PLC rack loses power. All LEDs off. Multiple devices affected.

Common causes:
- Mains power failure or fluctuation
- PLC power supply overloaded (too many modules drawing current)
- Power supply unit failure (electrolytic capacitor ageing)
- Loose power supply terminals
- UPS battery exhausted

Troubleshooting steps:
1. Check mains power at the panel incoming terminals
2. Measure the 24VDC output of the PLC power supply
3. Calculate total current draw vs power supply rating (leave 20% headroom)
4. Check for hot spots at terminal connections (indicates loose connection)
5. If the power supply is failed, replace with the same model and rating

Building Troubleshooting Skills

Troubleshooting cannot be learned from textbooks alone. It requires hands-on experience with real faults on real equipment. At EDWartens, the AEP program includes dedicated troubleshooting modules where you work with intentionally faulted systems — learning to diagnose and fix problems under realistic conditions.

This practical experience is what separates EDWartens graduates from those who only have classroom training. When you face your first PLC fault on the job, you will have already solved dozens of similar problems during your training.

Explore the AEP program or contact us to start building real troubleshooting skills.