Listing the YRC1000 error codes in the range from 0000 to 0999. These are major alarms.
YAS5.02
Listing the YRC1000 error codes in the range from 0000 to 0999. These are major alarms.
YAS5.02
Description:
ACP01 board was not able to recognize SDCA01 board when the control power turned ON.
SubCode:Subcode shows the error part of SDCA01 board. (There is possibility of combination of follow boards)
0000_0001 : SDCA01#1
0000_0010 : SDCA01#2
0000_0100 : SDCA01#3
0000_1000 : SDCA01#4
0001_0000 : SDCA01#5
0010_0000 : SDCA01#6
0100_0000 : SDCA01#7
1000_0000 : SDCA01#8
Remedy:
Check the following settings.
Not found the ASF01 board (RSW=0).
Description:
ACP01 board was not able to recognize ASF01 board when the control power turned ON.
SubCode:Subcode shows the error part of ASF01 board. (There is possibility of combination of follow boards)
0000_0001 : ASF01#1
0000_0010 : ASF01#2
0000_0100 : ASF01#3
0000_1000 : ASF01#4
0001_0000 : ASF01#5
0010_0000 : ASF01#6
0100_0000 : ASF01#7
1000_0000 : ASF01#8
Remedy:
Check the following settings.
Not found the ASF01 board (RSW=0).
Description:
ACP01 board was not able to recognize ASF01 board when the control power turned ON.
Remedy:
Check the following settings.
Not found the ASF01 board (RSW=0).
Description:
No response was sent from the ASF01 board when the control power turned ON.
Remedy:
Check the following settings.
Not found the ASF01 board (RSW=0).
Description:
No response was sent from the ASF01 board when the control power turned ON.
Remedy:
Check the following settings.
Not found the ASF01 board (RSW=0).
Description:
No response was sent from the SDCA01 board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #7 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #7 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize AIF01 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
ACP01 board was not able to recognize ASF04 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
ACP01 board was not able to recognize SDCA01#1 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#2 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#3 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#4 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#5 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#6 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#7 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
ACP01 board was not able to recognize SDCA01#8 board when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ACP01 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
No response was sent from the optional board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #7 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the optional board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #7 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF01 board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #1 when the control power turned ON.
At this time, the YRC1000 may judge it as signal input such as external hold wrong. However, it is caused by the communication error with SDCA01 board #1. Therefore, execute the following measures first of all.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #7.
Remedy:
Check the following settings.
Description:
No response was sent from the SDCA01 board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF04 board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
No response was sent from the ASF04 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #1 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #2 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #3 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #4 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #5 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #6 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #7 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The Main CPU detected an communication error for the SDCA01 board #8 when the control power turned ON.
Remedy:
Check the following settings.
Description:
The ACP01 system program is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #1 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #2 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #3 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #4 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #5 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #6 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #7 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of optional board #8 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #1 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #2 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #3 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #4 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #5 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #6 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #7 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of ASF01 board #8 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #1 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #2 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #3 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #4 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #5 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #6 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #7 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The system program of SDCA01 board #8 is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Description:
An error was detected in the initialization with MIII of ASF01 when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
The IO module board connected with 0th serial bus exists.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the ASF01 board.
Description:
An error was detected in communications with the I/O module board connected with 1st serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 2nd serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 3rd serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 4th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 5th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 6th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 7th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 8th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 9th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 10th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 11th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 12th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 13th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 14th serial bus when the control power turned ON.
Remedy:
Check the following settings.
Description:
EtherNet/IP(CPU Board) processing could not be started normally when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 1st PCI connector when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 2nd PCI when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 3rd PCI when the control power turned ON.
Remedy:
Check the following settings.
Description:
An error was detected in communications with the I/O module board connected with 4th PCI when the control power turned ON.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Counter value received from SDCA01 board is invalid.
Remedy:
Check the following settings.
Description:
The error was detected during the check of the serial communication watchdog data.
Watchdog data cannot be received from SDCA01 board.
Remedy:
Check the following settings.
Content:
The serial communications between ACP01 board and Safety board in the YRC1000 is monitored by each board.
This alarm occurs if ACP01detects an error in the serial communication between ACP01 board and 1st Safety board.
Remedy:
Check the following settings.
Description:
The RC parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The RO parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SV parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SVM parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SC parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SD parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The CIO parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The FD parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The AP parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The RS parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SE parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SVC parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The AMC parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SVP parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The MF parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The SVS parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
RE parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
FMS parameter is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The system configuration information data are damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
The management data of job files are damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
Description:
The job files are damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
Description:
The management data of position data files are damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
Description:
Memory and play back file is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The CIO ladder file is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The DeviceNet allocation file 1 is damaged.
Remedy:
Check the following settings.
[XFB01 board]
Description:
The DeviceNet allocation file 2 is damaged.
Remedy:
Check the following settings.
[XFB01 board]
Description:
The system software version is inconsistent with the version when the internal storage data is set or the SD Card on the ACP01 board is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).
Content:
The YRC1000 holds the information of EX IO function setting in the EX IO ALLOC FILE, and performs a check sum during the startup process to ensure that these files are properly retained. This alarm occurs if the YRC1000 detects an error in the check sum.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then set the IO module.
Description:
The network setting file is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then set the network again.
Description:
CIO parameter error.
Remedy:
Check the following settings.
Description:
Axis-related parameter error.
Remedy:
Check the following settings.
Description:
Sensor-use parameter error.
Remedy:
Check the following settings.
Description:
The set optional functions are different from those of the mounted optional board.
Remedy:
Check the following settings.
Description:
IO type error (combination impossible to coexist).
Remedy:
Check the following settings.
Description:
Safety board save data error
Remedy:
(1) Select the following menu.
Description:
Ex. AXIS INDIVIDUAL CONTROL Parameter Setting error (EX.TU# out of a range ).
Remedy:
Check the following settings.
Description:
Ex. AXIS INDIVIDUAL CONTROL Parameter Setting error (Difference in an Ex. AXIS INDIVIDUAL CONTROL Parameter and Physics TU# parameter).
Remedy:
Check the following settings.
Description:
PFL board save data error
Remedy:
(1) Select the following menu.
Description:
POWER REGENERATIVE FUNCTION
Parameter Setting error.
Remedy:
Check the following settings.
Description:
Parameter setting error of the robot detachment function or axes detachment function.
Remedy:
Check the following settings.
Description:
The fast cycle DeviceNet communication can not be available under this setting
Remedy:
Check the fast cycle DeviceNet communication setting.
Description:
The fast cycle DeviceNet communication can not be available under this setting
Remedy:
Check the fast cycle DeviceNet communication setting.
Description:
The communication setting written to the EtherNet/IP board (AB3607) and the communication setting recorded in the robot controller do not match.
Remedy:
(1) Reconfigure the EtherNet/IP board (AB3607).
(2) Please reconfirm the setting contents of AB3607.
Description:
Low priority DeviceNet communication cannot be used.
Remedy:
Cannot be used simultaneously with the fast cycle DeviceNet communication of SST-DN4.
Description:
Machine Safety board save data error
Remedy:
(1) Select the following menu.
Description:
The combination of the software version and the version of driver for INPACT board (HMSAB.DRV) is incorrect.
Remedy:
Please try the software update.
In order to know the correct software version, contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The fieldbus type of set optional function is not consistent with the fieldbus type of option board.
Remedy:
Check the following settings.
Description:
The combination of the software version and the version of driver for HMS board (HMSAB.DRV) is incorrect.
Remedy:
Please try the software update.
In order to know the correct software version, contact your YASKAWA representative about occurrence status (operating procedure).
Description:
The instance number set in EtherNet/IP communication is the same as the instance number used in EtherNet/IP Safety communication.
Remedy:
Set an instance number (INPUT INSTANCE / OUTPUT INSTANCE / CONFIGURATION INSTANCE) other than the following for EtherNet/IP(CPU board) instance number.
768 to 776, 896 to 904, 1024 to 1032
Description:
In the EtherNet/IP(CPU Board) EX. ADAPTER settings, the same instance number is used for multiple adapters.
Remedy:
When using EtherNet/IP (CPU Board) in the EX.ADAPTER setting, do not duplicate the instance number used in the adapters.
Description:
There is an error in the LAN interface settings used for EtherNet/IP (CPU Board).
Remedy:
Check the LAN interface settings used for EtherNet/IP (CPU Board).
Description:
An error occurred in the IP address setting process of the LAN interface used for EtherNet/IP (CPU Board).
Remedy:
Check the following settings.
(1) IP address setting of LAN interface in maintenance mode.
(In particular, IP address, subnet mask, default gateway are set correctly, and DHCP is not used)
(2) IP address setting of devices connected to the network (the same IP address does not exist).
Description:
An error occurred in the CC-Link IE Field setting.
Remedy:
Check the CC-Link IE Field settings.
(Do not set remote register to disable when the IO size is set to 0 bytes. )
Description:
The data output function for Self-Diagnosis System can not be available under this setting
Remedy:
Check the data output function setting for Self-Diagnosis System.
Description:
There is an error in the LAN interface settings used for MODBUS/TCP (CPU Board).
Remedy:
Check the LAN interface settings used for MODBUS/TCP (CPU Board).
Description:
Sub Code: Control group
Parameter specification and OT signal information are wrong
Remedy:
Check the following settings.
Content:
The YRC1000 verifies if the parameter specification is the special hardware setting.
This alarm occurs if the YRC1000 detects an error in the verification process.
Remedy:
Check the following settings.
Description:
The CMOS memory capacity is different from its initial setting.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
The I/O module connected to the PCI express bus is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #1 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #2 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #3 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #4 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #5 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #6 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #7 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #8 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #9 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #10 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #11 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #12 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #13 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the serial bus #14 is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The EtherNet/IP(CPU Board) settings and the function registered in the IO module are different.
Remedy:
Check the following settings.
Description:
The I/O module connected to the 1st PCI bus is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the 2nd PCI bus is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the 3rd PCI bus is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The I/O module connected to the 4th PCI bus is different from the function of the set I/O module.
Remedy:
Check the following settings.
Description:
The settings of the option board connected to the first PCI bus and the settings managed by the system software are different.
Remedy:
Check the following settings.
-Turn off the power and insert / remove the optional board.
-After starting maintenance mode select the option board and check the settings.
Description:
The settings of the option board connected to the first PCI bus and the settings managed by the system software are different.
Remedy:
Check the following settings.
-Turn off the power and insert / remove the optional board.
-After starting maintenance mode select the option board and check the settings.
Content:
The YRC1000 verifies that the application parameters are correctly set during a startup process. This alarm occurs if the YRC1000 detects an error in the verification process.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Content:
The YRC1000 verifies that the sensor parameters are correctly set during a startup process. This alarm occurs if the YRC1000 detects an error in the verification process.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
The station No. specified by the DeviceNet allocation file1 is incorrect (the station No. is out of the allowable range, or the specified station board is not the DeviceNet master).
Remedy:
Check the following settings.
[XFB01 board]
Description:
The MAC_ID specified by the DeviceNet allocation file1 is not consistent with the MAC_ID of the specified station board.
Remedy:
Check the following settings.
[XFB01 board]
Description:
Inconsistency was detected in the scan list of the DeviceNet allocation file1.
Remedy:
Check the following settings.
[XFB01 board]
Description:
The station No. specified by the DeviceNet allocation file2 is incorrect (the station No. is out of the allowable range, or the specified station board is not the DeviceNet master).
Remedy:
Check the following settings.
[XFB01 board]
Description:
The MAC_ID specified by the DeviceNet allocation file2 is not consistent with the MAC_ID of the specified station board.
Remedy:
Check the following settings.
[XFB01 board]
Description:
Inconsistency was detected in the scan list of the DeviceNet allocation file2.
Remedy:
Check the following settings.
[XFB01 board]
Description:
The designation in the parameter is different from the connected welding timer.
Remedy:
Check the following settings.
Description:
Illegal instruction cycle is set.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ACP02 board.
Remedy:
(1) Turn on the power again.
(2) If the alarm recurs, check the insertion status of the ACP02 board.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #1.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #2.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #3.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #4.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #5.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #6.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #7.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the ASF01 board #8.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 1st servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 2nd servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 3rd servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 4th servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 5th servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 6th servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 7th servo board.
Remedy:
Check the following settings.
Description:
An error occurred during the parameter/file transfer to the 8th servo board.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #1, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #2, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #3, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #4, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #5, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #6, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #7, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the ASF01 board #8, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 1st servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 2nd servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 3rd servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 4th servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 5th servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 6th servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 7th servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
An error occurred during startup sequence processing with the servo CPU of 8th servo board, and the system did not startup normally.
Remedy:
Check the following settings.
Description:
The DeviceNet allocation file1 could not be transmitted to the specified station.
Remedy:
Check the following settings.
[XFB01 board]
Description:
The DeviceNet allocation file2 could not be transmitted to the specified station.
Remedy:
Check the following settings.
[XFB01 board]
Content:
To properly operate the manipulator, it is required to complete the processing of operation instructions within the specified time. This alarm occurs if the processing of operation instructions is not completed within the specified time.
Remedy:
Check the following settings.
Description:
1st option board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
2nd option board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
ASF01 board connected to the 1st servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 2nd servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 3rd servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 4th servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 5th servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 6th servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 7th servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
ASF01 board connected to the 8th servo board’s software version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the ASF01 board version and then consult your YASKAWA representative.
Description:
1st servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
2nd servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
3rd servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
4th servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
5th servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
6th servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
7th servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Description:
8th servo board’s interface version is not corresponding to ACP01.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the SDCA01 board version and then consult your YASKAWA representative.
Content:
The number of axes exceeds the permissible value.
Remedy:
Check the following settings.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
An error occurred at the MADER timer.
Remedy:
Refer to the instruction manual for the MEDAR function.
Content:
The YRC1000 verifies that the EX IO file are correctly set during a startup process. This alarm occurs if the YRC1000 detects an error in the verification process.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Content:
The ladder program could not be initialized successfully.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
An error was found in the relay No. specification.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
An error was found in the register No. specification.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
An incorrect instruction was set.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
Output register is used redundantly.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
Output relay is used redundantly.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
Unconnected relay exists.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The STR instructions are overused.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The AND-STR instructions are overused.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
A syntax error was found in the CNT instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The head of the block starts with an instruction other than the STR instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
Excessive machine codes
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The last instruction is not the END instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
An error was found in the PART instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
An error was found in the GOUT instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The No. of operand is incorrect.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The constant value is incorrect.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The step capacity exceeds the memory capacity.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The number of operation instructions exceed the permissible value.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
A syntax error was found in the CNT instruction or TMR instruction.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
A syntax error was found in the JMP-LABEL instructions.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
The label of JMP destination does not exist.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Description:
Welder power serial I/F task cannot be created.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
Incorrect values are set for the communication frame number with the welder power.
Remedy:
Check the following setting.
Description:
Incorrect values are set for the number of the sending bytes per frame with the welder power.
Remedy:
Check the following setting.
Description:
Incorrect values are set for the number of the receiving bytes per frame with the welder power.
Remedy:
Check the following setting.
Description:
The binary semaphore to start up event for Welder power serial I/F task cannot be created.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
The event resource for Welder power serial I/F task cannot be created.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
The completion notification mail of Welder power serial I/F task cannot be created.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
Welder power serial I/F task cannot be created.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
Safety slave and standard master are used simultaneously in one channel of the DeviceNet board.
Remedy:
Check the following settings.
Select [SYSTEM] - [SETUP] - [OPTION BOARD] settings in maintenance mode. Display the slot(channel) that is configured with DeviceNet Safety, set to slave mode.
Description:
Board that can not be used with DeviceNet Safety is set.
Remedy:
Check the following settings.
Insert the SST-DN4-PCIE board to the slot to be used in the DeviceNet Safety. Select [SYSTEM] - [SETUP] - [OPTION BOARD] settings in maintenance mode, set the DeviceNet Safety.
Description:
The error was detected by the safety fieldbus process (ACP01). Subcode shows the error part of software.
Remedy:
In the case of DeviceNet Safety, please check the following.
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SST-DN4-PCIE board. Save the CMOS.BIN before replace the board to be safe. Replace the SST-DN4-PCIE board, and then load the CMOS.BIN saved before alarm occurred.
Description:
Safety reset request was received from the safety PLC in communication.
Remedy:
Turn the power OFF then back ON.
Description:
The AIF01 battery is exhausted.
Remedy:
Check if the battery is correctly connected to CN110/BAT on the AIF01 board.
Description:
The management area (FAT) of SD Card in ACP01 board is damaged.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Content:
The YRC1000 saves a part of data needed for system operations on the SD Card in the ACP01 board.
The data is read out when the controller power is turned ON.
This alarm occurs if this data reading cannot be done correctly.
Since this alarm occurs due to SD Card access failure, it is not recorded in the alarm history.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
PANELBOX.LOG file broken
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, select the following menu.
Description:
MAINTE.LOG file broken
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, select the following menu.
Content:
The YRC1000 saves a part of data needed for system operations on the SD Card in the ACP01 board. This alarm occurs if it cannot access to the ACP01correctly.
Usually, this alarm occurs accAL-0800 and AL-0801 occurs simultaneously.
Since this alarm occurs due to SD Card access failure, it is not recorded in the alarm history.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
An error occurred during the parameter of Manipulator Model (mecha.rom) loading.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
An error was found in the input/output direction data of allocation configuration.
Remedy:
Check the following settings.
Description:
In the output side setting of allocation configuration data, the specified
R-register start No. for the TOYOPUC exceeds the R-register limit.
Remedy:
Check the following settings.
Description:
In the output side setting of allocation configuration data, the set number to use the input side R-register of the TOYOPUC exceeds the R-register limit.
Remedy:
Check the following settings.
Description:
In the output side setting of allocation configuration data, the set number to use the M-register of concurrent I/O exceeds the M-register limit.
Remedy:
Check the following settings.
Description:
An error was found in the type set for output direction of allocation configuration data.
Remedy:
Check the following settings.
Description:
An error was found in the type set for input direction of allocation configuration data.
Remedy:
Check the following settings.
Description:
An error was found in the type specified for system data of allocation configuration data.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “CURR.POS. (PULSE)” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “CURR.POS. (XYZ)” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “WELDING INFO.” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “TASK INFO.” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “EXECUTE PROGRAM INFO.” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “INST. MESSAGE” of allocation configuration.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers for “Alarm/Error/Message” in the system data of Allocation setting information.
Remedy:
Check the following settings.
Description:
In the input side setting of allocation configuration data, the specified R-register start No. for the TOYOPUC exceeds the R-register limit.
Remedy:
Check the following settings.
Description:
In the input side setting of allocation configuration data, the set number to use the input side R-register of the TOYOPUC exceeds the R-register limit.
Remedy:
Check the following settings.
Description:
In the input side setting of allocation configuration data, the set number to use the M-register of concurrent I/O exceeds the M-register limit.
Remedy:
Check the following settings.
Description:
An error was found in the specified number of registers which are used by the system data “standard time setting data” of allocation configuration.
Remedy:
Check the following settings.
Description:
In the output side setting of allocation configuration data, some of the TOYOPUC’s R-registers are specified redundantly.
Remedy:
Check the following settings.
Description:
In the output side setting of allocation configuration data, some of the M-registers of concurrent I/O are specified redundantly.
Remedy:
Check the following settings.
Description:
In the input side setting of allocation configuration data, some of the TOYOPUC’s R-registers are specified redundantly.
Remedy:
Check the following settings.
Description:
In the input side setting of allocation configuration data, some of the M-registers of concurrent I/O are specified redundantly.
Remedy:
Check the following settings.
Description:
Sub Code:
1000
+channel*100
+factor:
0 send complete error
1 receive time out
2 receive break letter
3 framing error
4 parity error
5 over run error
6 receive length error
7 no STX control letter
8 no ETB control letter
9 BCC error
10 sequence number error
11 sensor detection error
Remedy:
(1) After checking the following two tems, turn the power OFF then back ON.
Description:
A Watchdog timeout was detected in the AIF01 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
A Watchdog timeout was detected in the ACP02 #1 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #2 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #3 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #4 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #5 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #6 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #7 board.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ACP02 #8 board.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
0-255:error code detected by ACP01
1000-: internal error of software
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ACP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the ACP01 board, and then remove the SD card from the failure ACP01 board to insert it into the new ACP01 board.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the ASF01#1 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#1 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#2 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#2 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#3 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#3 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#4 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#4 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#5 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#5 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#6 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#6 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#7 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#7 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#8 board (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the ASF01#8 board (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
An error was detected in the CPU.
Remedy:
Check the following settings.
Description:
A Watchdog timeout was detected in the SDCA01#1 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#2 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#3 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#4 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#5 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#6 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#7 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the SDCA01#8 board.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of servo board #1.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #2.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #3.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #4.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #5.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #6.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #7.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of servo board #8.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of ASF01 board #1 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #1 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #2 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #2 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #3 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #3 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #4 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #4 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #5 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #5 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #6 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #6 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #7 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #7 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #8 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #8 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #1 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #1 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #2 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #2 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #3 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #3 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #4 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #4 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #5 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #5 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #6 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #6 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #7 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #7 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #8 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
An error was detected in the CPU of ASF01 board #8 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following connector.
Description:
A Watchdog timeout was detected in the Safety board #1 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #1 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #2 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #2 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #3 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #3 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #4 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #4 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #5 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #5 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #6 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #6 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #7 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #7 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #8 (CPU1).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
A Watchdog timeout was detected in the Safety board #8 (CPU2).
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
ACP01board detect the Controller power off signal (Power lost signal) of AIF01 board when the control power turned ON. This alarm may occur, when the control power turned OFF before an online screen is displayed by a programming pendant.
Remedy:
Turn the power OFF after the online window appears on the programming pendant.
Description:
ACP01board detect the WATCHDOG TIMER ERROR of AIF01 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the AIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the AIF01 board, and then load the CMOS.BIN saved before alarm occurred.
Description:
ACP01board detect the Servo IF Initialize error of AIF01 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the AIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the AIF01 board, and then load the CMOS.BIN saved before alarm occurred.
Description:
ACP01board detect the IO IF Initialize error of AIF01 board when the control power turned ON.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the AIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the AIF01 board, and then load the CMOS.BIN saved before alarm occurred.
Description:
Processing time error of the IO processing
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the AIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the AIF01 board, and then load the CMOS.BIN saved before alarm occurred.
Description:
Processing time error of the SV communication.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the AIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the AIF01 board, and then load the CMOS.BIN saved before alarm occurred.
Description:
It was detected that AC power supply became less than the specified voltage.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.
Description:
An error was detected in the CPU of the optional ACP02 #1.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #2.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #3.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #4.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #5.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #6.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #7.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the CPU of the optional ACP02 #8.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #1.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #2.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #3.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #4.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #5.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #6.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #7.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of the optional ACP02 board #8.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #1.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #2.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #3.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #4.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #5.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #6.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #7.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of ASF01 board #8.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, replace the ASF01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #1.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #2.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #3.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #4.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #5.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #6.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #7.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.
Description:
An error was detected in the PCI-e Communication of SDCA01 board #8.
Remedy:
(1) Turn the power OFF then back ON.
(2) If the alarm occurs again, check the connection and insertion of the SDCA01 board. Save the CMOS.BIN before replace the board to be safe.