0xxx alarms

Listing the YRC1000micro error codes in the range from 0000 to 0999. These are major alarms.

0010

Description:
Not able to recognize ACP31 board when the control power turned ON. SubCode:Subcode shows the error part of ACP31 board. (There is possibility of combination of follow boards) 0000_0001 : ACP31#1 0000_0010 : ACP31#2

Remedy:
Check the following settings. Not found the ACP31 board (RSW=0).

• The Upper side of ACP31 board rotary switch setting (0)
• The rotary switch setting is overlapped to the other ACP31 board rotary switch setting. Check the rotary switch setting.

0011

Description:
ACP31 board was not able to recognize ASF30 board when the control power turned ON. SubCode:Subcode shows the error part of ASF30 board. (There is possibility of combination of follow boards) 0000_0001 : ASF30#1 0000_0010 : ASF30#2

Remedy:
Check the following settings.

• There is RSW on the ASF30 board.
• The ASF30 board rotary switch setting (0)

0012 [1]

Description:
ACP31 board was not able to recognize ASF30 board when the control power turned ON.

Remedy:
Check the following settings.

• There is RSW on the ASF30 board.
• The ASF30 board rotary switch setting (0)

0012 [2]

Description:
No response was sent from the ASF30 board when the control power turned ON.

Remedy:
Check the following settings.

• There is RSW on the ASF30 board.
• The ASF30 board rotary switch setting (0)

0012 [3]

Description:
No response was sent from the ASF30 board when the control power turned ON.

Remedy:
Check the following settings.

• There is RSW on the ASF30 board.
• The ASF30 board rotary switch setting (0)

0012 [4]

Description:
No response was sent from the ACP31 board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The rotary switch setting is overlapped to the other Upper side of ACP31 board rotary switch setting. Check the rotary switch setting.

0012 [5]

Description:
No response was sent from the ACP31 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The rotary switch setting is overlapped to the other Upper side of ACP31 board rotary switch setting. Check the rotary switch setting.

0012 [12]

Description:
No response was sent from the ACP31 board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The rotary switch setting is different from the ASF30 board on the ACP31 board rotary switch setting. Check the rotary switch setting.

0012 [13]

Description:
No response was sent from the ACP31 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The rotary switch setting is different from the ASF30 board on the ACP31 board rotary switch setting. Check the rotary switch setting.

0012 [22]

Description:
ACP31 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, replace the controller. Save the CMOS.BIN before replacement to be safe.

0012 [50]

Description:
Not able to recognize ACP31#1 board when the control power turned ON.

Remedy:
Check the following settings.

• Check the Upper side of ACP31 board rotary switch setting. Not found the ACP31 board (RSW=0).
• The rotary switch setting is overlapped to the other ACP31 board rotary switch setting. Check the rotary switch setting.

0012 [51]

Description:
Not able to recognize ACP31#2 board when the control power turned ON.

Remedy:
Check the following settings.

• Check the Upper side of ACP31 board rotary switch setting. Not found the ACP31 board (RSW=1).
• The rotary switch setting is overlapped to the other ACP31 board rotary switch setting. Check the rotary switch setting.
• The rotary switch setting is different from the ASF30 board on the ACP31 board rotary switch setting. Check the rotary switch setting.

0020 [1]

Description:
No response was sent from the ACP31 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).

0020 [20]

Description:
No response was sent from the optional board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Optional board setting in maintenance mode

0020 [21]

Description:
No response was sent from the optional board #2 when the control power turned ON.

Remedy:
Check the following settings.

• The optional board setting in maintenance mode

0020 [30]

Description:
No response was sent from the ASF30 board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (0) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0020 [31]

Description:
No response was sent from the ASF30 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (1) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0020 [32]

Description:
No response was sent from the ASF30 board #3 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (2) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (2) of the corresponding node number (SV#3)

0020 [33]

Description:
No response was sent from the ASF30 board #4 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (3) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (3) of the corresponding node number (SV#4)

0020 [34]

Description:
No response was sent from the ASF30 board #5 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (4) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (4) of the corresponding node number (SV#5)

0020 [35]

Description:
No response was sent from the ASF30 board #6 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (5) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (5) of the corresponding node number (SV#6)

0020 [36]

Description:
No response was sent from the ASF30 board #7 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (6) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (6) of the corresponding node number (SV#7)

0020 [37]

Description:
No response was sent from the ASF30 board #8 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ASF30 board rotary switch setting (7) of the corresponding node number
• The Upper side of ACP31 board rotary switch setting (7) of the corresponding node number (SV#8)

0020 [50]

Description:
No response was sent from the ACP31 board #1 when the control power turned ON. At this time, the YRC1000micro may judge it as signal input such as external hold wrong. However, it is caused by the communication error with ACP31 board #1. Therefore, execute the following measures first of all.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0020 [51]

Description:
No response was sent from the ACP31 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0020 [60]

Description:
No response was sent from the ASF04 board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode

0020 [61]

Description:
No response was sent from the ASF04 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode

0021 [50]

Description:
The Main CPU detected an communication error for the ACP31 board #1 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0021 [51]

Description:
The Main CPU detected an communication error for the ACP31 board #2 when the control power turned ON.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0030 [1]

Description:
The system program of ACP31 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).

0030 [20]

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).

0030 [21]

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).

0030 [30]

Description:
The system program of ASF30 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).

0030 [31]

Description:
The system program of ASF30 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).

0030 [32]

Description:
The system program of ASF30 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).

0030 [33]

Description:
The system program of ASF30 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).

0030 [34]

Description:
The system program of ASF30 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).

0030 [35]

Description:
The system program of ASF30 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).

0030 [36]

Description:
The system program of ASF30 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).

0030 [37]

Description:
The system program of ASF30 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).

0030 [50]

Description:
The system program of ACP31 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).

0030 [51]

Description:
The system program of ACP31 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).

0060 [0]

Description:
The I/O module board connected with 0th serial bus exists.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0060 [1]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [2]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [3]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [4]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [5]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [6]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode

0060 [7]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [8]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [9]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [10]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [11]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [12]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [13]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [14]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [15]

Description:
An error was detected in communications with the I/O module board connected with 15th serial bus when the control power turned ON.

Remedy:
Check the following settings.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [16]

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.

• PCI slot number in which each PCI board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [17]

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.

• PCI slot number in which each PCI board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [18]

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.

• PCI slot number in which each PCI board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0060 [19]

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.

• PCI slot number in which each PCI board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0100 [1]

Description:
The error was detected during the check of the serial communication watchdog data. Counter value received from ACP31 board is invalid.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0101 [1]

Description:
The error was detected during the check of the serial communication watchdog data. Counter value received from ACP31 board is invalid.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The Upper side of ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0110

Content:
The PCIe communications between ACP31 board and Safety board in the YRC1000micro is softwarily monitored by each board. This alarm occurs if ACP31 cannot detect reply from Safety board within the specified time.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0200 [0]

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.

0200 [1]

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.

0200 [2]

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.

0200 [3]

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.

0200 [4]

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.

0200 [5]

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.

0200 [6]

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.

0200 [7]

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.

0200 [8]

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.

0200 [9]

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.

0200 [10]

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.

0200 [11]

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.

0200 [12]

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.

0200 [13]

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.

0200 [14]

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.

0200 [15]

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.

0200 [125]

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.

0200 [126]

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.

0210

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 controller. Save the CMOS.BIN before replacement to be safe.

0220 [0]

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.

0220 [1]

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.

0220 [2]

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.

0220 [3]

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.

0230

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.

0270

Description:
The system software version is inconsistent with the version when the internal storage data is set or the SD Card on the ACP31 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).

0280

Content:
The YRC1000micro 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 YRC1000micro 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 I/O module.

0290

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.

0300 [2]

Description:
CIO parameter error.

Remedy:
Check the following settings.

• I/O module settings in maintenance mode

0300 [4]

Description:
Axis-related parameter error.

Remedy:
Check the following settings.

• Control group settings in maintenance mode

0300 [5]

Description:
Sensor-use parameter error.

Remedy:
Check the following settings.

• The optional board setting in maintenance mode

0300 [7]

Description:
The set optional functions are different from those of the mounted optional board.

Remedy:
Check the following settings.

• The optional board setting in maintenance mode

0300 [8]

Description:
IO type error (combination impossible to coexist).

Remedy:
Check the following settings.

• I/O module settings in maintenance mode

0300 [10]

Description:
Safety board save data error

Remedy:
(1) Select the following menu.

• [File]-[Initialize],[Safety Board FLASH Reset] in maintenance mode. (2) Turn the power OFF then back ON.

0300 [11]

Description:
Ex. AXIS INDIVIDUAL CONTROL Parameter Setting error (EX.TU# out of a range ).

Remedy:
Check the following settings.

• [Option function] - [Ex. AXIS INDIVIDUAL CONTROL(SDA) ] settings in maintenance mode

0300 [12]

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.

• [Option function] - [Ex. AXIS INDIVIDUAL CONTROL(SDA) ] settings in maintenance mode

0300 [13]

Description:
PFL board save data error

Remedy:
(1) Select the following menu.

• [File]-[Initialize],[PFL Board FLASH Reset] in maintenance mode. (2) Turn the power OFF then back ON.

0300 [14]

Description:
POWER REGENERATIVE FUNCTION Parameter Setting error.

Remedy:
Check the following settings.

• [Option function] - [POWER REGENERATIVE FUNCTION] settings in maintenance mode

0300 [15]

Description:
Parameter setting error of the robot detachment function or axes detachment function.

Remedy:
Check the following settings.

• [OPTION FUNCTION] - [ROBOT DETACHMENT] settings in maintenance mode, Reset the detachment group setting.
• [OPTION FUNCTION] - [AXES DETACHMENT] settings in maintenance mode, Reset the detachment axis setting.

0300 [16]

Description:
The fast cycle DeviceNet communication can not be available under this setting

Remedy:
Check the fast cycle DeviceNet communication setting.

• The Channel number for the fast cycle communication(Max channel number is 2).
• The Communication IO number for the fast cycle communication(Max IO number is 64Byte).

0300 [17]

Description:
The fast cycle DeviceNet communication can not be available under this setting

Remedy:
Check the fast cycle DeviceNet communication setting.

• The Channel number for the fast cycle communication(Only 1channel is available).
• The Communication IO number for the fast cycle communication(Max IO number is 16Byte).

0300 [20]

Description:
Machine Safety board save data error

Remedy:
(1) Select the following menu.

• [File]-[Initialize],[Safety Board FLASH Reset] (2) Turn the power OFF then back ON. (3) If the alarm occurs again, select the following menu.
• [File]-[Initialize]-[I/O Data],[YSF LOGIC FILE]

0300 [31]

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).

0300 [32]

Description:
The fieldbus type of set optional function is not consistent with the fieldbus type of option board.

Remedy:
Check the following settings.

• Fieldbus type setting of target INpact board in maintenance mode

0300 [40]

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.

• The number of Servo Control Board(Only 1 board is available).

0300 [42]

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).

0301

Description:
Sub Code: Control group

Parameter specification and OT signal information are wrong

Remedy:
Check the following settings.

• Connection settings (OT) in maintenance mode

0302 [0]

Content:
The YRC1000micro verifies if the parameter specification is the special hardware setting. This alarm occurs if the YRC1000micro detects an error in the verification process.

Remedy:
Check the following settings.

• Connection settings function safety in maintenance mode

0310

Description:
The CMOS memory capacity is different from its initial setting.

Remedy:
(0) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0320 [0]

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.

• The AIO board type connected to ASF30.
• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [1]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [2]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [3]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [4]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [5]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [6]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [7]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [8]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [9]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [10]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [11]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [12]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [13]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [14]

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.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [15]

Description:
The I/O module connected to the serial bus #15 is different from the function of the set I/O module.

Remedy:
Check the following settings.

• The rotary switch setting which specifies slot numbers of each I/O module
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [16]

Description:
The I/O module connected to the 1st PCI express bus is different from the function of the set I/O module.

Remedy:
Check the following settings.

• PCI express slot number in which each PCI express board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0320 [17]

Description:
The I/O module connected to the 2nd PCI express bus is different from the function of the set I/O module.

Remedy:
Check the following settings.

• PCI express slot number in which each PCI express board is mounted
• I/O module settings in maintenance mode Please refer to the manual of each I/O module for the details of the setting

0330

Content:
The YRC1000micro verifies that the application parameters are correctly set during a startup process. This alarm occurs if the YRC1000micro detects an error in the verification process.

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).

0340

Content:
The YRC1000micro verifies that the sensor parameters are correctly set during a startup process. This alarm occurs if the YRC1000micro detects an error in the verification process.

Remedy:
(0) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0390

Description:
Illegal instruction cycle is set.

Remedy:
Check the following settings.

• Instruction execution cycle

0400 [30]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #1.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0400 [31]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #2.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0400 [32]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #3.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (2) of the corresponding node number (SV#3)

0400 [33]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #4.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (3) of the corresponding node number (SV#4)

0400 [34]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #5.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (4) of the corresponding node number (SV#5)

0400 [35]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #6.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (5) of the corresponding node number (SV#6)

0400 [36]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #7.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (6) of the corresponding node number (SV#7)

0400 [37]

Description:
An error occurred during the parameter/file transfer to the ASF30 board #8.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (7) of the corresponding node number (SV#8)

0400 [50]

Description:
An error occurred during the parameter/file transfer to the 1st ACP31 board.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0410 [30]

Description:
An error occurred during startup sequence processing with the ASF30 board #1, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0410 [31]

Description:
An error occurred during startup sequence processing with the ASF30 board #2, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0410 [32]

Description:
An error occurred during startup sequence processing with the ASF30 board #3, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (2) of the corresponding node number (SV#3)

0410 [33]

Description:
An error occurred during startup sequence processing with the ASF30 board #4, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (3) of the corresponding node number (SV#4)

0410 [34]

Description:
An error occurred during startup sequence processing with the ASF30 board #5, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (4) of the corresponding node number (SV#5)

0410 [35]

Description:
An error occurred during startup sequence processing with the ASF30 board #6, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (5) of the corresponding node number (SV#6)

0410 [36]

Description:
An error occurred during startup sequence processing with the ASF30 board #7, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (6) of the corresponding node number (SV#7)

0410 [37]

Description:
An error occurred during startup sequence processing with the ASF30 board #8, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (7) of the corresponding node number (SV#8)

0410 [50]

Description:
An error occurred during startup sequence processing with the servo CPU of 1st ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (0) of the corresponding node number (SV#1)

0410 [51]

Description:
An error occurred during startup sequence processing with the servo CPU of 2nd ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (1) of the corresponding node number (SV#2)

0410 [52]

Description:
An error occurred during startup sequence processing with the servo CPU of 3rd ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (2) of the corresponding node number (SV#3)

0410 [53]

Description:
An error occurred during startup sequence processing with the servo CPU of 4th ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (3) of the corresponding node number (SV#4)

0410 [54]

Description:
An error occurred during startup sequence processing with the servo CPU of 5th ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (4) of the corresponding node number (SV#5)

0410 [55]

Description:
An error occurred during startup sequence processing with the servo CPU of 6th ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (5) of the corresponding node number (SV#6)

0410 [56]

Description:
An error occurred during startup sequence processing with the servo CPU of 7th ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (6) of the corresponding node number (SV#7)

0410 [57]

Description:
An error occurred during startup sequence processing with the servo CPU of 8th ACP31 board, and the system did not startup normally.

Remedy:
Check the following settings.

• Control group settings in maintenance mode
• The ACP31 board rotary switch setting (7) of the corresponding node number (SV#8)

0500

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.

• Instruction execution cycle

0510 [20]

Description:
1st option board’s interface version is not corresponding to ACP31.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0510 [21]

Description:
2nd option board’s interface version is not corresponding to ACP31.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0510 [30]

Description:
ASF30 board connected to the 1st servo boad’s software version is not corresponding to ACP31.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the ASF30 board version and then consult your YASKAWA representative.

0510 [50]

Description:
1st servo board’s interface version is not corresponding to ACP31.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the ACP31 board version and then consult your YASKAWA representative.

0520 [0]

Content:
The number of axes exceeds the permissible value.

Remedy:
Check the following settings.

• Control group settings in maintenance mode

0700

Content:
The YRC1000 micro 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.

0710

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.

0720 [1]

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.

0720 [2]

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.

0720 [3]

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.

0720 [4]

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.

0720 [5]

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.

0720 [6]

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.

0720 [7]

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.

0720 [8]

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.

0720 [9]

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.

0720 [10]

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.

0720 [11]

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.

0720 [12]

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.

0720 [13]

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.

0720 [14]

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.

0720 [15]

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.

0720 [16]

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.

0720 [17]

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.

0720 [18]

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.

0720 [19]

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.

0720 [20]

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.

0720 [21]

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.

0780 [00003A01]

Description:
NT112B board does not exist.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A02]

Description:
The set value of the slot number exceeds the range.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A03]

Description:
The set value of the channel number exceeds the range.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A04]

Description:
The set value of the priority exceeds the range.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A05]

Description:
Master / slave mode is out of range.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A07]

Description:
The set value of the operation mode exceeds the range.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A08]

Description:
The target board does not exist.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A0F]

Description:
Driver is not loaded.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003A13]

Description:
Creating a interrupt handler is failed.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00003AFF]

Description:
System error is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00002001]

Description:
Creating a task is failed.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0780 [00002002]

Description:
Creating an event (semaphore) is failed.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [FFFFFFFF]

Description:
There are slave stations with incomplete transmission delay time calculation.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [FFFFFFFE]

Description:
An error was detected with the error status of the ASIC.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [FFFFFFFD]

Description:
An error occurred in the SRAM read / write check.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001000]

Description:
Invalid user parameter is set.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001004]

Description:
Request size is over.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001005]

Description:
Invalid HostIF pointer is set.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001006]

Description:
RAM size is over.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000100B]

Description:
Sequence is incorrect.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000100C]

Description:
The setting of the slave axis number is abnormal.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000100D]

Description:
IO map size is abnormal.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000101E]

Description:
Station number is invalid.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000101F]

Description:
Request size is invalid.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001020]

Description:
Size is invalid.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001021]

Description:
FTYPE is invalid.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001030]

Description:
Message abort is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001031]

Description:
Message overflow is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001032]

Description:
Message data was sent during the request.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001033]

Description:
Request message size is abnormal.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001034]

Description:
Message data was received during the request.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001037]

Description:
Message underflow is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00001038]

Description:
Message split over is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00002010]

Description:
ASIC reset error is occurred.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00002029]

Description:
Global frame is unreceived.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003001]

Description:
MODE register setting request is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003002]

Description:
User parameter setting request is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003008]

Description:
Synchronous communication start request is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003009]

Description:
Asynchronous communication start request is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000301A]

Description:
Response buffer switch is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [0000301C]

Description:
Command buffer switch is unfinished.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003035]

Description:
Abort message is occued.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0781 [00003036]

Description:
Busy message is occued.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000001]

Description:
Inexact exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000002]

Description:
Overflow exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000003]

Description:
Underflow exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000004]

Description:
Invalid division exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000005]

Description:
Zero division exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000006]

Description:
Flush-to-zero exception is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000007]

Description:
Undefined instruction is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000008]

Description:
Prefetch abort is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [00000009]

Description:
Supervisor instruction is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0782 [0000000A]

Description:
Data abort is occued in NT112B board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the NT112B board. Save the CMOS.BIN before replace the board to be safe. Replace the NT112B board, and then load the CMOS.BIN saved before alarm occurred.

0790

Description:
The ACP31 battery is exhausted.

Remedy:
Check if the battery is correctly connected to the ACP31 board.

0800

Description:
The management area (FAT) of SD Card in ACP31 board is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0801

Content:
The YRC1000 micro saves a part of data needed for system operations on the SD Card in the ACP31 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 controller. Save the CMOS.BIN before replacement to be safe.

0801 [3000]

Description:
PANELBOX.LOG file broken

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, select the following menu.

• [SYSTEM]-[DATA REBUILD]

0802

Content:
The YRC1000 micro saves a part of data needed for system operations on the SD Card in the ACP31 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 controller. Save the CMOS.BIN before replacement to be safe.

0803

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 controller. Save the CMOS.BIN before replacement to be safe.

0805

Description:
Sub Code: Internal error code

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, initialize the MotoPlus temporary file in maintenance mode.

0831

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 revceive 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.

• the connection status
• the sensor type (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your YASKAWA representative about occurrence status (operating procedure)

0900

Description:
A Watchdog timeout was detected in the ACP31 board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0910

Description:
An error was detected in the CPU. 0-255:error code detected by ACP30 1000-: internal error of software

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0920 [0]

Description:
A Watchdog timeout was detected in the ASF30#1 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0920 [1]

Description:
A Watchdog timeout was detected in the ASF30#1 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0921 [0]

Description:
A Watchdog timeout was detected in the ASF30#2 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0921 [1]

Description:
A Watchdog timeout was detected in the ASF30#2 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0922 [0]

Description:
A Watchdog timeout was detected in the ASF30#3 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0922 [1]

Description:
A Watchdog timeout was detected in the ASF30#3 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0923 [0]

Description:
A Watchdog timeout was detected in the ASF30#4 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0923 [1]

Description:
A Watchdog timeout was detected in the ASF30#4 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0924 [0]

Description:
A Watchdog timeout was detected in the ASF30#5 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0924 [1]

Description:
A Watchdog timeout was detected in the ASF30#5 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0925 [0]

Description:
A Watchdog timeout was detected in the ASF30#6 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0925 [1]

Description:
A Watchdog timeout was detected in the ASF30#6 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0926 [0]

Description:
A Watchdog timeout was detected in the ASF30#7 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0926 [1]

Description:
A Watchdog timeout was detected in the ASF30#7 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0927 [0]

Description:
A Watchdog timeout was detected in the ASF30#8 board (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0927 [1]

Description:
A Watchdog timeout was detected in the ASF30#8 board (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0940

Description:
A Watchdog timeout was detected in the ACP31#1 board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0941

Description:
A Watchdog timeout was detected in the ACP31#2 board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0950

Description:
An error was detected in the CPU of ACP31 #1.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0951

Description:
An error was detected in the CPU of ACP31 #2.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0960 [0]

Description:
An error was detected in the CPU of ASF30 board #1 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0960 [1]

Description:
An error was detected in the CPU of ASF30 board #1 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0961 [0]

Description:
An error was detected in the CPU of ASF30 board #2 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0961 [1]

Description:
An error was detected in the CPU of ASF30 board #2 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0962 [0]

Description:
An error was detected in the CPU of ASF30 board #3 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0962 [1]

Description:
An error was detected in the CPU of ASF30 board #3 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0963 [0]

Description:
An error was detected in the CPU of ASF30 board #4 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0963 [1]

Description:
An error was detected in the CPU of ASF30 board #4 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0964 [0]

Description:
An error was detected in the CPU of ASF30 board #5 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0964 [1]

Description:
An error was detected in the CPU of ASF30 board #5 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0965 [0]

Description:
An error was detected in the CPU of ASF30 board #6 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0965 [1]

Description:
An error was detected in the CPU of ASF30 board #6 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0966 [0]

Description:
An error was detected in the CPU of ASF30 board #7 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0966 [1]

Description:
An error was detected in the CPU of ASF30 board #7 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0967 [0]

Description:
An error was detected in the CPU of ASF30 board #8 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0967 [1]

Description:
An error was detected in the CPU of ASF30 board #8 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0970 [0]

Description:
An error was detected in the CPU of ASF30 board #1 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0970 [1]

Description:
An error was detected in the CPU of ASF30 board #1 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0971 [0]

Description:
An error was detected in the CPU of ASF30 board #2 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0971 [1]

Description:
An error was detected in the CPU of ASF30 board #2 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0972 [0]

Description:
An error was detected in the CPU of ASF30 board #3 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0972 [1]

Description:
An error was detected in the CPU of ASF30 board #3 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0973 [0]

Description:
An error was detected in the CPU of ASF30 board #4 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0973 [1]

Description:
An error was detected in the CPU of ASF30 board #4 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0974 [0]

Description:
An error was detected in the CPU of ASF30 board #5 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0974 [1]

Description:
An error was detected in the CPU of ASF30 board #5 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0975 [0]

Description:
An error was detected in the CPU of ASF30 board #6 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0975 [1]

Description:
An error was detected in the CPU of ASF30 board #6 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0976 [0]

Description:
An error was detected in the CPU of ASF30 board #7 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0976 [1]

Description:
An error was detected in the CPU of ASF30 board #7 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0977 [0]

Description:
An error was detected in the CPU of ASF30 board #8 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0977 [1]

Description:
An error was detected in the CPU of ASF30 board #8 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0980 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #1 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0980 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #1 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0981 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #2 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0981 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #2 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0982 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #3 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0982 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #3 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0983 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #4 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0983 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #4 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0984 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #5 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0984 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #5 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0985 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #6 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0985 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #6 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0986 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #7 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0986 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #7 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0987 [0]

Description:
A Watchdog timeout was detected in the ASF30 board #8 (CPU1).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0987 [1]

Description:
A Watchdog timeout was detected in the ASF30 board #8 (CPU2).

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0990 [1]

Description:
ACP30 board detect the Controller power off signal (Power lost signal) of ACP31 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.

0990 [2]

Description:
ACP30 board detect the WATCHDOG TIMER ERROR of ACP31 board when the control power turned ON.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0990 [3]

Description:
ACP30board detect the Servo IF Initialize error of ACP31 board when the control power turned ON.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0990 [4]

Description:
ACP30 board detect the IO IF Initialize error of ACP31 board when the control power turned ON.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0990 [5]

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 controller. Save the CMOS.BIN before replacement to be safe.

0990 [6]

Description:
Processing time error of the SV comminucation,

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.

0990 [7]

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, replace the controller. Save the CMOS.BIN before replacement to be safe.