Mitsubishi PLC Error Codes: The Field Guide

A Mitsubishi FX or MELSEC Q series CPU flashing an error LED at 2 AM is not a theoretical problem. It stops production. Mitsubishi PLC error codes are the first diagnostic layer every technician needs to read correctly before anything else happens on that floor. This guide covers what the codes mean, how they map to real hardware and software faults, and what your next move should be.

How Mitsubishi PLC Error Codes Work

Mitsubishi PLCs report faults through a combination of LED indicators, special register values, and error history stored in the CPU. On MELSEC Q and iQ-R series hardware, you read these through GX Works2 or GX Works3 via the diagnostics window. On FX series units, the front-panel LED pattern combined with D8000/D8001 special data registers is your starting point.

The CPU stores a self-diagnostic error code as a four-digit decimal value in D8060 to D8069 (FX series) or in SD0 to SD25 (MELSEC Q/iQ-R). The code range tells you whether you are looking at a hardware fault, a parameter mismatch, a program execution error, or a network communication failure.

Read the error code before you touch anything. The CPU has already done your diagnostic work. Your job is to interpret it correctly." � Panel Shop Lead, Automotive Tier 1 Supplier

FX Series Error Codes

D8060 to D8069: Special Register Map

The FX2N, FX3U, and FX5U CPUs store fault data in dedicated special data registers. D8060 holds the most recent error code. D8061 stores the address of the instruction that caused the fault. This matters when a program error triggers mid-scan.

Common FX error codes to know on sight:

• 6000: Battery voltage drop. The RTC and program retention backup battery is low. Plan replacement before next shutdown window.
• 6101: Program memory error. Check for corrupted ladder logic, particularly after a power interruption during a write operation.
• 6102: Parameter error. Typically a mismatch between the CPU's I/O configuration and what is physically installed.
• 6200: WDT (watchdog timer) error. The scan time exceeded the configured watchdog limit. Review scan load, particularly any long FOR-NEXT loops.
• 6401: I/O bus error. A connected expansion module is not responding. Check ribbon cable seating and module slot addressing.

LED Patterns on FX Units

The POWER, RUN, and ERROR LEDs on FX hardware give you a first-pass diagnosis before you connect a laptop. ERROR flashing with RUN lit typically indicates a non-fatal warning. ERROR solid with RUN off indicates a fatal CPU halt. Record the flash pattern before reset; it disappears once power cycles.

MELSEC Q and iQ-R Error Codes

SD0 to SD25: System Device Registers

On MELSEC Q and iQ-R platforms, the diagnostic register block runs from SD0 through SD25. SD0 holds the latest error code. SD1 contains the network error history pointer. SD8 holds the annunciator number if an F-coil fault relay has been triggered in the program.

GX Works2 Diagnostics (PLC Diagnostics tab) populates these registers in a readable format. You will see the error code, the step number, and a plain-language description. Do not skip this window. It contains more context than any single register read.

Common Q/iQ-R Error Code Ranges

Reading Error Codes via GX Works

GX Works2 Diagnostics Procedure

Connect to the CPU via USB or Ethernet. Open Diagnostics from the top menu. Select PLC Diagnostics. The error code, step number, and timestamp populate automatically. Write down the step address before clearing. That address links directly to the offending rung in the program.

If the PLC is in STOP mode and will not go to RUN, the error is almost always in the 1000�4999 range. Clear the error, verify the program, and attempt RUN manually. If it halts again immediately, the fault is persistent hardware or a corrupted parameter block.

Special Relay M8060 on FX Series

FX units use special relays M8060 to M8069 in parallel with the D8060 data registers. M8065 turns on when there is a program syntax error. M8067 turns on during WDT overflow. These relays can be monitored in the ladder program itself for automated fault logging to an HMI screen without requiring a separate diagnostics session.

Troubleshooting Scenario: WDT Fault on a Packaging Line

A MELSEC Q03UDECPU on a case packing line began faulting with error code 5100 (WDT overflow) every three to four hours during high-cycle runs. The fault was intermittent and did not appear during slower trial runs or maintenance cycles.

Initial assumption: A FOR-NEXT loop in the vision inspection subroutine was running unchecked. Monitoring the scan time via SD520 showed normal peaks of 4.2 ms on standard cycles. During the fault windows, SD520 spiked to 18 ms, which exceeded the 10 ms WDT limit configured in the CPU parameters.

The root cause was a third-party Ethernet module polling a barcode database server over a congested network segment. The response delay caused the communication instruction to stall the scan. Solution was to move the database query to a separate low-speed task block with its own interrupt timer, reducing the main task scan load.

The WDT fault was not a CPU problem. It was a network architecture problem. The error code told us the scan was too long. The diagnostics register told us where in the scan it was happening. � Controls Engineer, Food & Beverage OEM

CC-Link and MELSECNET Fault Codes

Network-layer errors on CC-Link and MELSECNET are reported through the network module's own diagnostics buffer and through SD1 to SD25 on the master CPU. A station offline event on CC-Link appears as error code 7000 on the master. The B-series device area assigned to that station will show all zeros until the station reconnects.

CC-Link error code 7010 indicates a data link error on a specific station address. Pull the station number from the network diagnostics buffer, not just the master CPU error register. The master code gives you the fault category. The module-level buffer gives you the affected node.

Verify cable termination resistance before assuming a failed slave module. Both ends of a CC-Link trunk require 110-ohm termination. A missing resistor on a new installation or after a cable extension causes intermittent station drops that produce exactly this error pattern.

Error History and Preventive Monitoring

Using SD Error History Registers

MELSEC iQ-R CPUs store up to 16 previous error events in SD380 to SD399. Each error entry includes the code, timestamp, and step address. This history survives a power cycle if the backup battery is functional. Before any PLC service call, pull this history. Recurring codes at the same step address confirm a persistent fault. Random codes across multiple step addresses suggest a power quality issue or EMC interference.

Mapping Errors to Maintenance Intervals

Battery low warnings (code 6000 on FX, 6010 on Q series) are predictable. Mitsubishi rates backup batteries at three to five years under typical operating conditions. A site running 24/7 in an enclosure above 40 degrees Celsius will see shorter life. Track the first battery warning and schedule replacement within 30 days.

I/O module error codes that repeat after reset without any wiring change often indicate a failing input card. Optocoupler degradation on high-cycle digital inputs is a known wear mechanism, particularly on older FX extension blocks running at 24V DC input frequency above 10 Hz continuously.

Sourcing Replacement Modules After a Fault

When an error code confirms a failed hardware module, lead time is the immediate constraint. Mitsubishi MELSEC Q and iQ-R modules are available through authorized distributors, but older FX2N expansion blocks and discontinued QX/QY I/O modules require verification against current stock, not just catalog checks.

Before ordering any replacement module based on an error code diagnosis, cross-reference the exact model number on the module housing against the current Mitsubishi parts catalog. A QX40 and a QX40-S1 are not interchangeable despite similar part numbers. The S1 suffix indicates sink/source input flexibility that changes the wiring configuration.

Counterfeit Mitsubishi modules exist in the market, particularly for high-volume FX series components. Purchase only through authorized distribution channels and verify the holographic certification label on the packaging before installation. A counterfeit module will not produce the same error code behavior as a genuine part, which compromises your fault diagnosis going forward.

Need Help Sourcing Mitsubishi PLC Components?

If an error code diagnosis has led you to a replacement module or CPU, Techno Control Corp stocks Mitsubishi MELSEC and FX series components and can verify part number compatibility before your order ships. Our technical team works from actual datasheets, not catalog assumptions.

Contact us directly for sourcing support, lead time checks, or component cross-referencing. If you are commissioning a new system and want to review your I/O architecture or network configuration before it hits the floor, we can help with that too.