Omron CP1H / CP1L PLC Common Faults and Solutions

Fault 3: ERR/ALM Is Flashing but the PLC Still Runs

A flashing ERR/ALM is a non-fatal error. The CPU continues to execute, but one function may be unreliable or unavailable.

Read A400 and the log instead of resetting immediately. Common examples are a low battery, invalid PLC Setup value, Option Board error, interrupt-task refresh conflict, built-in analog error, or a user-created FAL(006) alarm.

If A400 contains 4101 to 42FF, the ladder program intentionally generated the alarm. Identify the FAL number in A360 through A391, then find the corresponding FAL(006) instruction and its machine condition. Replacing the PLC will not remove a programmed alarm.

Error 009B: PLC Setup Error

009B means a PLC Setup value is invalid. The internal address of the incorrect setting is stored in A406.

This often appears after a project made for another CPU model or Unit version is transferred. Compare the installed model and Unit version with the project, correct the specific setting, transfer it, and restart only if the setting requires a power cycle.

Option Board Error

An Option Board error occurs when a board is removed while power is supplied or is not correctly detected.

Power down safely, inspect the board and connector, reinstall it fully, and verify the related serial or Ethernet settings. On CP1L, 00D1 and 00D2 identify the affected Option Board slot. CP1H reports the board location on its diagnostic display and flags.

Fault 4: The PLC Is Running but All Outputs Are Off

Check the INH indicator before opening the program.

If INH is lit, the Output OFF Bit A500.15 is ON. This forces all outputs OFF even though RUN remains lit and the ladder program continues. Find out why the bit was turned on before resetting it; it may be controlled deliberately by commissioning logic, an HMI maintenance command, or a fault routine.

If INH is not lit, check:

• Output power and common wiring
• Load supply voltage
• Output fuse and overcurrent damage
• Physical output indicator versus the monitored CIO bit
• Duplicate instructions writing to the same output bit
• Forced status in CX-Programmer
• PLC mode and fatal/non-fatal errors

If the output indicator is ON but the device does not operate, focus on the field side: load power, common, fuse, wiring, terminal contact, and the load itself.

If the output indicator never turns ON while the monitored bit appears to be commanded, search for another instruction that writes the same output, check task order, and verify that the physical output address matches the CPU and expansion layout.

Fault 5: One Input or a Group of Inputs Is Unstable

Start with the input indicator and the monitored CIO bit.

If neither changes, check the sensor supply, common terminal, field voltage, polarity, and input wiring. If the indicator changes but the PLC bit does not, verify the address and whether the terminal belongs to a special input function such as a high-speed counter, interrupt, or quick-response input.

Intermittent inputs often come from:

• Low or unstable external voltage
• Loose common or terminal screws
• Noise from contactors, solenoids, inverters, or poorly routed motor cables
• A sensor pulse shorter than the configured input response time
• Damaged terminal-block contacts
• An entire 8- or 16-point common group losing its reference

Use appropriate surge suppression, grounding, shielding, and cable separation. Do not hide electrical noise with a long software filter until the signal and machine timing have been checked.

Fault 6: An Output Will Not Turn Off

Compare the output LED with the actual terminal voltage.

If the output LED remains ON, look for a second output instruction, a latched command, forced status, or a task-order problem in the program.

If the LED is OFF but the load remains energized, inspect leakage current, transistor residual voltage, incorrect common wiring, a welded relay contact, or an external bypass path. A small load can remain partially energized by leakage current; the correct external load or approved dummy-resistor arrangement may be required.

For relay outputs, contact wear and welding are realistic failure modes. For transistor outputs, an output short or excessive inrush can damage the channel. Correct the external cause before installing a replacement CPU or output Unit.

Fault 7: Expansion I/O Is Missing or Causes Error 80C0

80C0, 80CA, 80CE, and 80CF are I/O bus errors. They indicate that the CPU cannot exchange data correctly with connected Units.

With power OFF:

1. Inspect every CP-series Expansion Unit connection and CP1W-CN811 cable where used.
2. Check for bent pins, loose latches, mechanical stress, or a Unit that was added during maintenance.
3. Confirm the expansion count and allocated input/output words are within the exact CPU’s limits.
4. On CP1H systems using CP1W-EXT01 and CJ-series Units, inspect the CJ Unit Adapter and required CJ-series End Cover.
5. Check the Unit-specific status and error flags before replacing it.

CP1H supports up to seven CP-series Expansion Units or Expansion I/O Units within the word-allocation restrictions, and up to two compatible CJ-series Special I/O or CPU Bus Units through the CJ Unit Adapter. CP1L limits vary by body size: many M-type CPUs accept up to three CP-series expansion Units, while applicable L-type CPUs accept one. Use the exact model table rather than counting free connector space.

80E1 means the configured Unit or word limit has been exceeded. On CP1H, 80E0 can also appear when an unsupported CJ-series Basic I/O Unit or I/O Control Unit is mounted. 80E9 identifies duplicate Unit numbers among connected CJ-series CPU Bus or Special I/O Units.

Fault 8: Battery Error 00F7 or Lost Retained Data

00F7 is a non-fatal Battery Error. It occurs when battery-error detection is enabled and the battery is missing, disconnected, or low.

The PLC may keep running, but Holding Area values, retained DM data, counter values, and the clock can be at risk after power is removed. Upload the project and important retained values before maintenance.

Use the battery specified for the exact CPU and follow the replacement timing in its operation manual. Battery-free operation is possible only when the application is designed for it and battery-error detection is intentionally disabled. Confirm what happens to retained values and the clock after power loss before choosing that option.

If data is lost despite a good battery, check whether the program initializes DM values at startup, whether flash DM initial values are being restored, and whether a Memory Cassette startup transfer is overwriting the current data.

Fault 9: CX-Programmer Cannot Connect by USB

The built-in USB port is a programming peripheral port, not a general serial COM port.

Use this sequence:

1. Confirm the PLC POWER indicator is ON.
2. Use a known-good USB A-to-B cable and a different PC USB port.
3. Check Windows Device Manager for the Omron SYSMAC PLC device.
4. If the device is unknown or has a warning icon, reinstall the Omron USB driver supplied with CX-One/CX-Programmer.
5. In CX-Programmer, select the correct CP1H or CP1L CPU and choose USB as the network type.
6. Take CX-Programmer offline before unplugging and reconnecting the USB cable.

Only one CP-series PLC can be connected to one computer by this USB method at a time. Omron also specifies a maximum 5 m cable for the peripheral USB connection.

If Device Manager never detects a device after the powered PLC, cable, USB port, and driver have been verified, the PLC’s USB interface may be damaged. Before replacing the CPU, try a valid serial or Ethernet path where the installed hardware supports one.

A very long PLC cycle can also cause CX-Programmer response timeouts. In that case, increasing the software response-monitoring time may restore diagnostics, but the high cycle time still requires investigation.

Fault 10: RS-232C or RS-422A/485 Communication Fails

Do not begin by changing baud rates at both ends. First record the existing settings and identify the installed Option Board: CP1W-CIF01, CP1W-CIF11, or CP1W-CIF12-V1.

Then compare:

• Protocol selection: Host Link, NT Link, no-protocol, Modbus-RTU Easy Master, or another configured mode
• Baud rate, data bits, parity, and stop bits
• Unit number and host address
• RS-232C pinout or RS-422A/485 polarity
• Two-wire versus four-wire arrangement
• Termination and biasing where required
• Cable shield and signal-ground practice
• PLC Setup port number and the actual physical Option Board slot

If COMM or port activity is visible but no valid data is exchanged, a format, node, command, or application-program mismatch is more likely than an open cable. If there is no activity at all, check the transmit command, port assignment, cabling, and whether another service already owns the port.

Power OFF before reseating or replacing the Option Board.

Fault 11: CP1L-EL/EM Ethernet Will Not Connect

The built-in Ethernet port on CP1L-EL/EM supports FINS/UDP, FINS/TCP, TCP/UDP socket services, DNS, and SNTP functions. It is not the same function as an EtherNet/IP port with cyclic tag data links.

Troubleshoot from the physical layer upward.

1. Check Link and the PC Adapter

Confirm LNK/ACT activity, the switch-port link indicator, and a known-good Ethernet cable. Select the correct PC network adapter when Wi-Fi, VPN, virtual-machine, and USB Ethernet interfaces coexist.

2. Check IP Address and Subnet

Verify that the PLC and engineering PC have unique addresses in a compatible subnet. Ping is a useful basic test, but a successful ping does not prove that FINS node conversion, routing, or port settings are correct.

3. Check FINS Settings

For FINS/UDP, verify the FINS/UDP port and the selected IP-address conversion method. The default FINS/UDP port is 9600, and the available conversion methods include automatic dynamic, automatic static, IP address table, and combined methods.

For FINS/TCP, verify the TCP connection setup. Error 03C0 identifies a FINS/TCP setup problem. Routing tables are required when communicating across other networks or when the system design uses them.

4. Check Configuration Tables

Error 021A means the routing table, IP address table, or IP router table has a logical error. A313 identifies the table category. Correct and transfer the related setup instead of rewriting all Ethernet parameters.

5. Check Server-Specific Errors

03C1 is a DNS/SNTP server setup error. 03C4 means the configured server could not be reached. Check gateway, routing, server address or host name, DNS resolution, firewall policy, and physical reachability.

The built-in Ethernet error record at A40 through A44 stores the code, detail, and occurrence time for an Ethernet communication error. Codes such as 0105 for node-address setting, 010D for a destination missing from routing tables, 0121 for a missing IP address-table entry, 03C3 for a discarded FINS/UDP packet, and 03C2 for a discarded FINS/TCP packet provide a more specific direction than “Ethernet not working.”