Troubleshooting / PLC / controls

PLC / Controls Troubleshooting

The most common PLC / controls problems on the plant floor, with the likely causes and the fix for each. Part of the OEE Lab troubleshooting directory.

Not your exact symptom?

Describe it in the symptom finder and search the whole directory.

Open the symptom finder

Problems on this page:

PLC fault / stop (fault LED)Network / comms dropoutHMI blank or frozenInput or output not workingRetentive data or program lossIntermittent or random stopsAnalog signal noise or driftWrong program version in the PLC

PLC fault / stop (fault LED)

Hits OEE: Availability

Symptoms: PLC in fault/stop, machine dead, fault indicator on the CPU or a module.

I/O module fault
Read the fault code; reseat or replace the flagged module.
Power supply issue
Check PLC power and backplane voltage.
Watchdog / scan fault
Review the diagnostic buffer; clear the fault and investigate the logic/cause.
Field device short on an output
Find the shorted actuator/wiring on the faulted output.

Prevention: Read diagnostics first, protect outputs, keep firmware/backups current.

Network / comms dropout

Hits OEE: Availability

Symptoms: Devices drop offline intermittently, comms-loss faults, HMI freezes.

Cable or connector fault
Inspect/replace the suspect ethernet/fieldbus cable and connectors.
Electrical noise
Route comms away from VFD/power cables; ensure proper shielding/grounding.
Duplicate IP / addressing
Check for duplicate addresses on the network.
Failing switch or port
Swap the switch/port; check for errors on managed switches.

Prevention: Cable management, segregation from power, managed-switch monitoring.

HMI blank or frozen

Hits OEE: Availability

Symptoms: Operator panel dark or unresponsive; machine runs but no control/visibility.

Power or comms to PLC lost
Check HMI power and the PLC link; reseat the cable.
Application crash / memory
Restart the panel; check for a faulted runtime or full memory.
Failed backlight or panel
Test backlight; replace the panel if dead.

Prevention: Stable power, comms monitoring, firmware/app backups.

Input or output not working

Hits OEE: Availability

Symptoms: A field device does not read or actuate although the logic looks correct.

Field wiring or device fault
Check the device, wiring and that the I/O LED follows the signal.
Blown output fuse or module fault
Test the module fuse; swap or replace a failed I/O module.
Forced or overridden I/O
Check for forces left on in the program and remove them.

Prevention: I/O checks, fuse management, force discipline after maintenance.

Retentive data or program loss

Hits OEE: Availability

Symptoms: Recipe or counter values lost, or the program is corrupt after a power cycle.

Dead backup battery or failed memory
Replace the PLC battery; reload from the verified backup.
No current program backup
Restore the latest archive; establish a backup routine.
Power quality or improper shutdown
Fix supply issues; use controlled shutdowns and a UPS.

Prevention: Battery replacement schedule, regular program backups, clean power.

Intermittent or random stops

Hits OEE: Availability

Symptoms: The line stops sporadically with no clear fault or only a vague message.

Loose connection or intermittent sensor
Wiggle-test wiring; monitor suspect inputs over time.
Timing or race condition in logic
Review recent program changes and timing assumptions.
Heat or noise affecting the controller
Check panel cooling and grounding.

Prevention: Connection integrity, change control, panel-environment checks.

Analog signal noise or drift

Hits OEE: Quality

Symptoms: Analog readings jump or drift, false alarms, poor control.

Grounding or shielding fault
Use a single-point shield ground; separate from power wiring.
Sensor or wiring fault
Check the transmitter, wiring and loop power.
Scaling or calibration error
Verify the analog scaling and calibrate.

Prevention: Proper shielding/grounding, loop checks, calibration.

Wrong program version in the PLC

Hits OEE: Quality

Symptoms: A fixed problem comes back, or the machine behaves differently after a CPU swap or restore.

Online changes not saved to the master copy
Save every online change to the master project.
Backup restored from an old file
Keep dated backups in one known place.
No change log
Log every change with the date, the person and the reason.

Prevention: Version control or a change log for PLC programs.

Guidance only. Always follow lockout/tagout and your site's safe-work procedures, and verify against OEM manuals before acting.

Alarm codes: Mitsubishi FX PLC error codes · Allen-Bradley MicroLogix fault codes

Related equipment guides: VFD drive · servo drive · electric motor · switchgear · UPS system · motor control centre · flow meter · pressure transmitter · level sensor · load cell · temperature sensor · proximity sensor · safety light curtain · barcode scanner · stepper motor · HMI panel

Stop the same fault coming back

Recurring PLC / controls stops usually trace to a cause you cannot see by hand. The partner we recommend is Fabrico: it tracks OEE and downtime live from PLCs, IoT sensors or AI cameras; where cameras are fitted, the video of a stop sits next to its machine data so the cause can be reviewed; and a technician opens the work order from the stop in the same system. Data is hosted in the AWS EU region, and Fabrico and the company behind it hold ISO/IEC 27001, ISO/IEC 20000-1 and ISO 9001.

Book a Fabrico demo
The directory stays free.

Related tools: full troubleshooting directory · OEE calculator · downtime cost · MTBF / MTTR · glossary

Methods that cut recurring stops: the six big losses · root cause analysis · preventive vs predictive maintenance · TPM · SMED & changeover