Preliminary fault localization (rapidly pinpointing the fault scope)
1.Observe the status of the PLC indicator lights: focus on checking the power light (POWER), running light (RUN), and fault light (ERROR/Fault). If the power light is not on, prioritize troubleshooting the power supply line (voltage, loose wiring); if the running light is off/flashing, it is highly likely that there is a program fault or CPU module abnormality; if the fault light is on, it is necessary to read the fault code in conjunction with the programming software.
2.Distinguish between fault types: These are categorized into hardware faults (PLC modules, I/O interfaces, wiring, power supply) and software faults (program logic errors, parameter setting errors, program loss). A preliminary judgment can be made through “power off and restart” (if the fault disappears after restarting, it is mostly a temporary software anomaly; if the fault persists after restarting, it is mostly a hardware fault).
3.Auxiliary positioning based on on-site phenomena: If the associated equipment (such as motors, sensors) does not respond, first check the wiring between the PLC output interface and the equipment; if the equipment behaves abnormally (such as malfunction or no action), prioritize checking the program logic or input signals (sensors, buttons).
Troubleshooting and resolution by type
1. Hardware failure (the most common, accounting for about 60%)
(1) Power failure: Check whether the PLC power supply voltage (AC220V or DC24V) is stable, and whether the wiring terminals are loose or oxidized; if the power module is severely heated and emits an odor, replace the power module directly; if the external power supply fluctuates, install a voltage regulator.
(2) I/O module fault: Use a multimeter to check the voltage of the input/output interface. If there is no signal at the input interface (such as no response after connecting the sensor), check the sensor, wiring, or input module. If there is no signal at the output interface, check the output module, relay, or wiring. If the module indicator light is abnormal (such as constantly on/off), it is highly likely that the module is damaged and needs to be replaced.
(3)Wiring fault: Focus on inspecting the wiring between the PLC and external devices (sensors, actuators, buttons), and troubleshoot issues such as looseness, short circuits, and reversed connections. Especially in high-frequency vibration scenarios (such as production lines), it is necessary to regularly tighten the wiring terminals.
2. Software malfunctions (accounting for approximately 30%)
- Program logic fault: Read the program through programming software (such as Siemens STEP7, Mitsubishi GX Works2) to troubleshoot issues such as logic conflicts, timer/counter setting errors, and improper use of instructions. The “monitoring mode” can be used to view variable status in real time, locate the incorrect logic, make modifications, download to the PLC, and restart the test.
- Program loss/corruption: If the program is lost after the PLC is powered off, check the battery module (backup power supply) and replace the battery if it is low on power. If the program is corrupted, import the backup program and download it to the PLC again. It is recommended to regularly back up the program to avoid failure to recover after a malfunction.
- Parameter setting fault: Check the internal parameters of the PLC (such as communication parameters, I/O address allocation, and high-speed counter parameters). If the parameter settings are incorrect, leading to poor equipment coordination and abnormal signals, the parameters need to be reset according to the equipment manual.
