Troubleshooting Mitsubishi PLCs: Understanding Common Faults
Created on 04.09
Mitsubishi PLCs—whether the compact FX series or the modular Q series—are renowned for their durability and reliability in industrial environments. However, like any electronic control system, they are not immune to failure. When a PLC goes down, production stops. Understanding the most common faults and their telltale signs is essential for any maintenance technician.
PLC faults can generally be divided into two categories: hardware failures and software/program errors. The key to rapid diagnosis often lies in observing the LED indicators on the front panel.
1. Power Supply Failure (POWER Indicator OFF)
Symptoms: The green POWER LED on the CPU unit does not illuminate.
Common Causes:
- Loose or incorrect power wiring
- Blown internal fuse (often due to a power surge)
- Overload on the built-in 24V DC output (too many sensors drawing power)
- Failed power supply module
Troubleshooting: Disconnect all loads from the 24V DC terminals. If the POWER LED lights up, the issue is an external overload. If it remains off, the internal power supply or fuse is likely damaged.
2. Battery Failure (BATT Indicator RED)
Symptoms: The red BATT LED is lit (or flashing on some models).
Common Cause: The internal lithium battery has reached the end of its life (typically 3-5 years). Once the battery voltage drops, the PLC risks losing its program and the contents of its retentive memory (data registers, latched relays).
Action: Replace the battery immediately with the PLC powered on to prevent program loss. If the BATT light remains lit after replacement, the CPU board may have a circuit failure.
3. CPU / Program Errors (ERROR Indicator)
The ERROR LED is the most critical indicator. Its behavior tells you the nature of the problem:
Indicator State | Fault Type | Common Causes |
ERROR ON (Solid) | Hardware Failure | RAM error, CPU circuit failure, watchdog timer (WDT) hardware fault, I/O bus error. The CPU cannot start. |
ERROR FLASHING | Program Error | Syntax errors in ladder logic, incorrect instruction usage, timer/counter without a set value, duplicated I/O numbers, or parameters exceeding memory limits. |
ERROR FLASHING | Watchdog Timer Timeout | Scan time exceeds the preset watchdog time (typically 200ms). This often occurs due to infinite loops in the program or excessive use of interrupt routines. |
Key Diagnostic Codes: When the ERROR LED flashes, technicians should read the error code from the PLC (using GX Works software or by checking special registers D8004 and D8060–D8069). Common codes include 6401 (parameter error), 6501 (instruction error), and 6101 (RAM error).
4. Communication Failures
Symptoms: The PLC cannot communicate with the HMI (touch screen), SCADA system, or programming software. The communication LEDs (SD/RD) remain dark.
Common Causes:
- Incorrect communication protocol, baud rate, or station number settings
- Loose or broken communication cables
- Electromagnetic interference (EMI) from nearby inverters or high-power equipment
- Failed communication module (e.g., FX-485BD, Ethernet module)
Solution: Verify configuration parameters match on both devices. Check cable shielding and ensure communication lines are separated from high-voltage power cables.
5. I/O Module Failures
Symptoms: Specific inputs are not being detected, or outputs are not energizing the field devices (solenoids, contactors, indicator lights).
Common Causes:
- Input Side: Damaged sensors (proximity switches, photoelectric sensors), loose terminal screws, or blown fuses on input modules.
- Output Side: Relay output contacts that are welded shut or burnt out due to inductive load surges (common in older FX relay-output models). Transistor outputs may fail due to short circuits.
Note: A frequent mistake is using a relay output to drive a solenoid without a surge suppressor. Over time, the arcing destroys the relay contact, causing the output to fail permanently.
6. Environmental and External Factors
Surprisingly, the PLC itself is often the *least* likely component to fail. The majority of "PLC faults" are actually external:
- Conductive Dust: Metal dust or carbon buildup inside the control panel can create shorts between terminals.
- Temperature: High ambient temperatures (above the PLC's rated 55°C) can degrade electrolytic capacitors in the power supply.
- Vibration: Loose terminal blocks or mounting screws can cause intermittent connections.
- Electromagnetic Interference: Improper grounding can cause erratic behavior, such as phantom inputs or communication dropouts.
Diagnostic Best Practices
When responding to a Mitsubishi PLC fault, follow this sequence:
1. Observe the LEDs: Is it POWER, RUN, ERROR, or BATT? This narrows the scope immediately.
2. Connect the Software: Use GX Works2 (for FX/Q series) or GX Works3 (for iQ-R/FX5) to go online. Read the error history—this often tells you exactly what happened and when.
3. Check the Peripherals: Verify that the emergency stops are pulled, the power supply is stable, and that external sensors are functioning. A shorted 24V sensor often takes down the entire PLC's 24V power rail.
4. Review Recent Changes: Did a technician just modify the ladder logic? Was a new motor installed near the control panel? Recent changes are the most common source of new faults.
Mitsubishi PLCs are engineered for longevity, but no component lasts forever. While power supply failures and battery depletion are inevitable over time, many "faults" are actually caused by external wiring issues, sensor failures, or electromagnetic interference.
A systematic approach—starting with the LED indicators, moving to software diagnostics, and finally inspecting external components—will minimize downtime. Regular maintenance, including cleaning, terminal tightening, and proactive battery replacement, remains the most effective strategy for keeping Mitsubishi PLCs running reliably for years.
JOIN OUR MAILING LIST
AND NEVER MISS AN UPDATE
电话
WhatsApp