OMRON CPM2C system fault diagnosis and maintenance

Scenario 2: The system cannot run - the RUN indicator light is not on, but the PWR light is on

This phenomenon indicates that the PLC has not entered the running state, and possible reasons include:

Mode switch position error: Check the mode switch on the programmer or CPU unit to ensure it is in the RUN or MONITOR position.

Fatal error exists: Is the ERR/ALM light constantly red? If so, follow the method in scenario three below to troubleshoot fatal errors.

Startup mode setting: The startup mode of CPM2C is determined by the settings of DM 6600. If set to 'start according to programmer mode switch' but the programmer is not connected, the PLC will start in RUN mode. But if set incorrectly, it may always stay in Program mode. Check whether the set values (00, 01, or 02) of DM 6600 match the expected values through the programmer.

Missing program or END instruction: The user program memory is empty, or there is no END (01) instruction at the end of the program. Check the program through the programmer.

Scenario 3: Dealing with fatal errors (ERR/ALM red light constantly on)

This is the most urgent situation on site and requires immediate handling. The process is as follows:

Connect programmer, read error: This is the fastest way to obtain fault information. Common fatal error messages and their countermeasures:

Memory ERR: In this case, it is necessary to check the AR 1308 to AR 1314 flag bits to locate the specific problem.

AR 1308 ON: There are non-existent bit or word addresses in the program. Countermeasure: Check and correct the program.

AR 1310 ON: Read only DM area (DM 6144 to DM 6599) checksum error. Countermeasure: Check and re-enter the setting values for the area.

AR 1314 ON: The designated area data was not preserved after a power outage. Countermeasure: Clear the error, check the data in the hold area (HR, DM, etc.) and rewrite it.

I/O BUS ERR: Abnormal data transfer between CPU and expansion unit. Countermeasure: Check if the connection between the CPU and the first expansion unit is secure, and if the connectors between each expansion unit are loose or dirty. Disconnect the expansion units one by one and power them back on to locate the faulty units.

NO END INST: There is no END (01) instruction at the end of the program. Countermeasure: Write END (01) at the end of the program.

SCAN TIME OVER: The actual program execution cycle exceeds the maximum watchdog time set in DM 6618. Countermeasure: Optimize the program to reduce cycle time, or increase the setting value of DM 6618 appropriately.

Clear fatal errors: After identifying and correcting the cause of the error, it is necessary to switch the PLC to Program mode and then perform error clearing operations through the programmer, or power on the PLC again.

Scenario 4: ERR/ALM light flashing (non fatal error)

This situation usually allows the system to continue running, but the cause must be identified.

**SYS FAIL FAL * *: The user program executed the FAL (06) instruction. Check the FAL number (01-99) in SR 253 and determine the conditions that trigger the user-defined warning based on program logic.

BATTERY ERROR: The low battery detection switch is turned on and the battery voltage is too low. Countermeasure: Immediately prepare to replace the battery (see Part 5).

SCAN TIME OVER: The program cycle exceeds the recommended value of 100ms, but does not exceed the watchdog set value. Countermeasure: Optimize the program or adjust parameters such as input filtering time.

Scenario 5: Specific I/O points not working

When a specific input or output point exhibits abnormal behavior, follow the "isolation method" for troubleshooting:

Check I/O indicator lights: Each I/O point on the CPU unit or expansion unit has a corresponding LED indicator light. When there is a signal input, the input indicator light should light up; When the program sets the output point to ON, the output indicator light should light up. This is the fastest way to determine whether the problem is "external" or "internal".

External circuit inspection:

Input point: If the input indicator light is not on, the problem lies in the periphery. Check the sensor power supply, wiring, and whether the sensor itself is damaged. Measure whether the voltage between the input terminal and the common terminal (COM) is within the rated range (24 VDC).

Output point: If the output indicator light is on but the external device is not functioning, the problem lies in the periphery. Check if the power supply, wiring, and load (such as contactor coils) of the output device are damaged. Measure the voltage between the output terminal and the common terminal.

Mandatory operation and program monitoring:

In MONITOR or PROGRAMM mode, use the programmer to force the suspicious output point to ON/OFF. If the output indicator light changes accordingly, it indicates that the CPU and I/O hardware are normal, and the problem lies in the program logic.

Monitor the relevant logic in the program to see if the input conditions are met and if the status of intermediate relays, timers, and counters is correct.

Part 3: Advanced Diagnostic Techniques - Utilizing PC Settings and Special Instructions