Omron CJ-series CJ2 CPU Unit

This is a non-fatal error indicating a problem with a Basic I/O Unit. The POWER and RUN indicators will be lit, while the ERR/ALM indicator will be flashing. Additional error details, including the slot and rack number of the faulty unit, are available in memory area A408. This error prevents normal operation of the affected I/O unit.

This non-fatal error occurs when the 'Detect Duplicated Refresh Errors' setting in the PLC Setup is 'Detect', and I/O refresh instructions (IORF(097), FIORF(225), IORD(222), IOWR(223)) in a cyclic task compete with the same instructions in an interrupt task for the same Special I/O Unit. It also occurs if an I/O refresh instruction is executed in an interrupt task while I/O is already being refreshed, potentially causing data inconsistencies.

An error has occurred in a Basic I/O Unit, indicated by A402.12 and A408. This suggests a potential hardware issue or component failure within the unit, such as a blown fuse, leading to a loss of I/O functionality.

There is a setting error in the PLC Setup parameters, indicated by A402.10. This signifies that one or more configuration values are invalid, preventing the CPU Unit from operating according to its intended setup.

An Option Board error has occurred, indicated by A315.13 and A402.00. This typically happens if the Option Board was removed while the system was operating, if the board itself has failed, or if the connector mating is poor, leading to a loss of its specific functionality.

Writing to the built-in flash memory failed, indicated by A315.15. This non-fatal error means that critical backup data may not have been correctly saved, and proper operation may not be possible the next time power is restored after a power interruption due to loss of retained data.

An error occurred in the memory where network tags are stored, indicated by A315.12. This can affect communication and data exchange involving network tags, potentially leading to incorrect data or communication failures.

An error occurred in the memory specifically used for online editing operations, indicated by A315.04 and A402.00. This condition implies that online program modifications might be compromised, or that normal operation may not be possible upon the next power restoration after an interruption.

This non-fatal error occurs when the PLC Setup is configured to detect battery errors, and the CPU Unit's backup battery is either missing or its voltage has dropped below an acceptable threshold, indicated by A402.04. This can lead to loss of retained data or time upon power cycle.

An error occurred during data exchange between the CPU Unit and a CPU Bus Unit, indicated by A402.07 and A417. This signifies a communication failure or an internal issue specific to one of the CPU Bus Units (unit numbers 0 to F).

An error occurred during data exchange between the CPU Unit and a Special I/O Unit, indicated by A402.06 and A418 to A423. This signifies a communication failure or an internal fault within one of the Special I/O Units (unit numbers 0 to 95).

An installed CPU Bus Unit does not match the CPU Bus Unit registered in the I/O tables. This error indicates a mismatch between the physical hardware and the configured settings. Flag A402.03 and Auxiliary Area A427 indicate the error and the problem unit number respectively.

An installed Special I/O Unit does not match the Special I/O Unit registered in the I/O tables. This indicates a mismatch between the physical hardware and the configured settings, potentially involving synchronous unit operation. Flag A402.02 and Auxiliary Area A428 to A433 indicate the error and the problem unit number respectively.

The Function Advance Logic (FAL) instruction number 006 has been executed in the program. This indicates a user-defined error condition has been met. The specific FAL number (001 to 511) is stored in Auxiliary Area A400 (leftmost digit 4, rightmost 3 digits 101 to 2FF hex) and flags A360 to A391.

The PLC's scan cycle time has exceeded the maximum cycle time (watch cycle time) configured in the PLC Setup. This indicates the program or I/O operations are taking too long to complete within the allowed timeframe. Flag A401.08 indicates this error.

An error has occurred in the communication bus line between the CPU and I/O Units, or the End Cover is not correctly connected to the CPU Rack or an Expansion Rack. This is a fatal error, indicated by flag A401.14. Auxiliary Area A404 contains the error slot number (00 to 09, with '0F hex' for undetermined slot, '0B hex' for built-in EtherNet/IP port bus error) and rack number (00 to 03, with '0E hex' for missing End Cover).

The connected I/O Units do not match the registered I/O tables, or the number of connected Units differs from the number registered. This is a fatal error, indicated by flag A401.10. Auxiliary Area A405.08 specifically turns ON if an Interrupt Input Unit is in the wrong position or registered incorrectly.

One or more system limits regarding I/O points, interrupt inputs, Pulse I/O Modules, or Expansion Racks have been exceeded, or resources are allocated to more than one Unit. This is a fatal error, indicated by flag A401.11, with Auxiliary Area A407.13 to A407.15 providing specific details about which limit was exceeded.

The same number has been allocated to more than one CPU Bus Unit or Special I/O Unit. This is a fatal error, indicated by flag A401.13. Auxiliary Area A410 and A411 to A416 will indicate the duplicated unit numbers for CPU Bus Units and Special I/O Units respectively.

An Expansion Rack's starting word address exceeds CIO 0901, preventing the CPU from correctly addressing the I/O for the rack. The corresponding bit in A409.00 to A409.03 (Racks 0 to 3) will be turned ON, indicating the affected rack.

A general program error has occurred within the CJ2 CPU Unit, indicating incorrect program logic or an unrecoverable runtime issue. The program will stop, and the address at which the stop occurred will be output to A298 and A299. Specific sub-error flags (A295.xx) provide more detailed diagnostic information.

A fatal error has occurred in the CPU's memory, indicated by A401.15. A bit in A403 will turn ON to show the location of the error, such as checksum errors in user program memory, PLC Setup, registered I/O tables, routing tables, or CPU Bus Unit Setup. This can be caused by power interruptions during data storage or corrupted settings, preventing the PLC from operating correctly.

The user program that was transferred includes functions that are not supported by the current unit version of the CPU Unit, indicated by A401.05 and A293. This incompatibility prevents the program from executing correctly and leads to a fatal error.

The CPU Unit failed to correctly read the contents of the Memory Card when power was turned ON, indicated by A401.03. This can occur if required files for automatic transfer are missing or if a program including network symbols was transferred to an incompatible CPU version (CJ2H-CPU6 unit version 1.5 or earlier, or CJ2M-CPU1 unit version 2.1 or earlier).

The FALS(007) instruction has been executed in the program, indicated by A401.06, signifying a user-defined fatal error condition. The specific error code in A400 will range from 0xC101 to 0xC2FF, where the last three hexadecimal digits correspond to a user-defined FAL number from 001 to 511.

A memory error has occurred in the CPU Unit, or a checksum error has been detected during the PLC's cyclic checksum verification. This is a fatal error, indicated by flag A401.15. The specific memory area affected is detailed by individual bits in Auxiliary Area A403. The CPU Unit attempts automatic recovery from flash memory for certain areas like user program memory and PLC Setup; if unsuccessful, operation stops.

Incorrect data values were provided in an operand during an attempt to execute an instruction, causing the ER Flag to turn ON. The PLC Setup is configured to stop operation for instruction errors, halting the CPU and contributing to a fatal program error (0x80F0). The Program Error Position (A298/A299) indicates where the error occurred.

An indirect DM/EM BCD error has occurred, causing the AER Flag to turn ON, and the PLC Setup is set to stop operation for an instruction error. This means an indirect address or the word holding it is not in BCD format when BCD mode is specified for DM/EM access, contributing to a fatal program error (0x80F0). The error address is output to A298/A299.

An attempt was made to access memory in an unauthorized manner, and the PLC Setup is configured to stop operation on an instruction error, leading to a fatal program error (0x80F0). This includes reading/writing parameter areas, writing to non-installed memory, writing to an EM bank configured as EM file memory, writing to a read-only area, or using an indirect DM/EM address not in BCD when BCD mode is specified. The error address is output to A298/A299.

The program is missing an END(001) instruction at the conclusion of the task specified in A294. This indicates an incomplete program structure, preventing proper task execution and leading to a fatal program error (0x80F0).

A task error has occurred, meaning there is no executable cyclic task or no task corresponds to an interrupt that was input. This is particularly critical if the 'Stop CPU on Instruction Error' parameter in the PLC Setup is set to 'Stop', leading to a fatal program error (0x80F0).

Too many differentiated instructions have been inserted or deleted during an online editing session, leading to an unstable program state. This condition prevents proper execution and contributes to a fatal program error (0x80F0).

The program contains an instruction that the CPU Unit cannot execute, indicating either a corrupt program transfer or an instruction not supported by the CPU's firmware version. This prevents the program from running correctly and contributes to a fatal program error (0x80F0).

The user program memory (UM) has been exceeded, indicating that the program is too large for the allocated memory space. This prevents the PLC from loading or executing the full program, contributing to a fatal program error (0x80F0).