0xxx alarms

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

0010 [30]

Description:
YCP21 board was not able to recognize YSF21 board when the control power turned ON.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the YSF21 board.

0020 [1]

Description:
No response was sent from the YCP21 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 in maintenance mode, 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:
(1) 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:
(1) Check the following settings.

• The optional board setting in maintenance mode

0020 [22]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [23]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [24]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [25]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [26]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [27]

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

Remedy:
(1) Check the following settings.

• Optional board setting in maintenance mode

0020 [30]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• The PCI connector of YCP02 board

0020 [50]

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

Remedy:
(1) Check the following settings.

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

0020 [51]

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

Remedy:
(1) Check the following settings.

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

0020 [52]

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

Remedy:
(1) Check the following settings.

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

0020 [53]

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

Remedy:
(1) Check the following settings.

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

0020 [54]

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

Remedy:
(1) Check the following settings.

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

0020 [55]

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

Remedy:
(1) Check the following settings.

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

0020 [56]

Description:
No response was sent from the servo board #7.

Remedy:
(1) Check the following settings.

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

0020 [57]

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

Remedy:
(1) Check the following settings.

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

0020 [60]

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

Remedy:
(1) Check the following settings.

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

0020 [61]

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

Remedy:
(1) Check the following settings.

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

0020 [62]

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

Remedy:
(1) Check the following settings.

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

0020 [63]

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

Remedy:
(1) Check the following settings.

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

0020 [64]

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

Remedy:
(1) Check the following settings.

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

0020 [65]

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

Remedy:
(1) Check the following settings.

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

0020 [66]

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

Remedy:
(1) Check the following settings.

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

0020 [67]

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

Remedy:
(1) Check the following settings.

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

0021 [50]

Description:
The communications CPU for the servo board #1 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [51]

Description:
The communications CPU for the servo board #2 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [52]

Description:
The communications CPU for the servo board #3 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [53]

Description:
The communications CPU for the servo board #4 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [54]

Description:
The communications CPU for the servo board #5 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [55]

Description:
The communications CPU for the servo board #6 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [56]

Description:
The communications CPU for the servo board #7 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0021 [57]

Description:
The communications CPU for the servo board #8 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0022

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0023 [60]

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

Remedy:
(1) Check the following settings.

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

0023 [61]

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

Remedy:
(1) Check the following settings.

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

0023 [62]

Description:
The communication CPU for the communication convert board #3 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0023 [63]

Description:
The communication CPU for the communication convert board #4 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0023 [64]

Description:
The communication CPU for the communication convert board #5 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0023 [65]

Description:
The communication CPU for the communication convert board #6 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0023 [66]

Description:
The communication CPU for the communication convert board #7 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0023 [67]

Description:
The communication CPU for the communication convert board #8 detected an error when the control power turned ON.

Remedy:
(1) Check the following settings.

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

0030 [1]

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [10]

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 in maintenance mode, 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 in maintenance mode, 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 in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [22]

Description:
The system program of optional board #3 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [23]

Description:
The system program of optional board #4 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [24]

Description:
The system program of optional board #5 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [25]

Description:
The system program of optional board #6 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [26]

Description:
The system program of optional board #7 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [27]

Description:
The system program of optional board #8 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [30]

Description:
The system program of YSF21 board is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [50]

Description:
The system program of servo board #1 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [51]

Description:
The system program of servo board #2 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [52]

Description:
The system program of servo board #3 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [53]

Description:
The system program of servo board #4 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [54]

Description:
The system program of servo board #5 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [55]

Description:
The system program of servo board #6 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [56]

Description:
The system program of servo board #7 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [57]

Description:
The system program of servo board #8 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [60]

Description:
The system program of functional safety board #1 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [61]

Description:
The system program of functional safety board #2 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [62]

Description:
The system program of functional safety board #3 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [63]

Description:
The system program of functional safety board #4 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [64]

Description:
The system program of functional safety board #5 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [65]

Description:
The system program of functional safety board #6 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [66]

Description:
The system program of functional safety board #7 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0030 [67]

Description:
The system program of functional safety board #8 is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0031

Description:
The explosion-proof PP boot ROM is not applicable to DX200.

Remedy:
Contact your Yaskawa representative to replace the explosion-proof programming pendant with the one in which the applicable boot ROM (ver2.00) is installed.

0060 [0]

Description:
The IO module board connected with 0th serial bus exists.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the YSF21 board.

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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO module for the details of the setting.

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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO module for the details of the setting.

0060 [15]

Description:
EtherNet/IP(CPU Board) processing could not be started normally when the control power turned ON.

Remedy:
Check the following settings. (1) EtherNet/IP(CPU Board) setting in maintenance mode (In particular, the IP address, subnet mask, default gateway are set correctly, and DHCP is not used) (2) IO module setting in maintenance mode (3) IP address setting of devices connected to the network (the same IP address does not exist).

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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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 EAXA21 board is invalid.

Remedy:
(1) Check the following settings.

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

0100 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 EAXA21 board is invalid.

Remedy:
(1) Check the following settings.

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

0101 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0102 [1]

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

Remedy:
(1) Check the following settings.

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

0102 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0103 [1]

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

Remedy:
(1) Check the following settings.

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

0103 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0104 [1]

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

Remedy:
(1) Check the following settings.

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

0104 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0105 [1]

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

Remedy:
(1) Check the following settings.

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

0105 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0106 [1]

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

Remedy:
(1) Check the following settings.

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

0106 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0107 [1]

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

Remedy:
(1) Check the following settings.

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

0107 [2]

Description:
The error was detected during the check of the number of the serial communications. Counter value received from EAXA21 board is off by one cycle.

Remedy:
(1) Check the following settings.

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

0110

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 1st Functional Safety board.

Remedy:
(1) Check the following settings.

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

0111

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 2nd Functional Safety board.

Remedy:
(1) Check the following settings.

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

0112

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 3rd Functional Safety board.

Remedy:
(1) Check the following settings.

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

0113

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 4th Functional Safety board.

Remedy:
(1) Check the following settings.

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

0114

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 5th Functional Safety board.

Remedy:
(1) Check the following settings.

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

0115

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 6th Functional Safety board.

Remedy:
(1) Check the following settings.

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

0116

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 7th Functional Safety board.

Remedy:
(1) Check the following settings.

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

0117

Content:
The serial communications between YCP21 board and Functional Safety board in the DX200 is softwarily monitored by each board. This alarm occurs if YCP21detects an error in the serial communication between YCP21 board and 8th Functional Safety board.

Remedy:
(1) Check the following settings.

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

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 YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

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.

0240 [0]

Description:
The DeviceNet allocation file 1 is damaged.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0240 [1]

Description:
The DeviceNet allocation file 2 is damaged.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0270

Description:
The system software version is inconsistent with the version when the internal storage data is set or the CompactFlash on the YCP21 board is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0280

Content:
The DX200 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 DX200 detects an error in the check sum.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then set the IO module.

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:
(1) Check the following settings.

• I/O module settings in maintenance mode

0300 [4]

Description:
Axis-related parameter error.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode

0300 [5]

Description:
Sensor-use parameter error.

Remedy:
(1) 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:
(1) Check the following settings.

• The optional board setting in maintenance mode

0300 [8]

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

Remedy:
(1) Check the following settings.

• I/O module settings in maintenance mode

0300 [10]

Description:
Functional Safety board save data error

Remedy:
(1) Select the following menu.

• {File}-{Initialize},{Functional 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:
(1) 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:
(1) Check the following settings.

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

0300 [13]

Description:
Torque monitoring function can not be used under this setting.

Remedy:
(1) Check the following setting.

• The number of EAXA01 bord(Max 1 board).
• The number of axes(Max 8 axes).

0300 [14]

Description:
POWER REGENERATIVE FUNCTION Parameter Setting error.

Remedy:
(1) 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:
(1) 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:
(1) 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:
(1) 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 [18]

Description:
The communication setting written to the EtherNet/IP board (AB3607) and the communication setting recorded in the robot controller do not match.

Remedy:
(1) Reconfigure the EtherNet/IP board (AB3607). (2) Please reconfirm the setting contents of AB3607.

• IP addresses are not duplicated
• The sum of the IO sizes does not exceed the upper limit value
• The IO input range is less than the communication data size

0300 [20]

Description:
Machine Safety board save data error

Remedy:
(1) Select the following menu.

• {File}-{Initialize},{Machine 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}

0301

Description:
Sub Code: Control group

Parameter specification and OT signal information are wrong

Remedy:
(1) Check the following settings.

• Connection settings (OT) in maintenance mode

0302 [0]

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

Remedy:
(1) Check the following settings.

• Connection settings function safety in maintenance mode

0310

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

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:
(1) Check the following settings.

• The YIO board type connected to YSF22.
• 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO 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:
(1) 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 IO module for the details of the setting.

0320 [15]

Description:
The EtherNet/IP(CPU Board) settings and the function registered in the IO module are different.

Remedy:
Check the following settings. (1) EtherNet/IP(CPU Board) setting in maintenance mode (2) IO module setting in maintenance mode For details on the setting method, refer to the OPTIONS INSTRUCTIONS EtherNet/IP COMMUNICATION FUNCTION(FOR STANDARD LAN PORT).

0320 [16]

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

Remedy:
(1) 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 IO module for the details of the setting.

0320 [17]

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

Remedy:
(1) 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 IO module for the details of the setting.

0320 [18]

Description:
The I/O module connected to the 3rd PCI bus is different from the function of the set I/O module.

Remedy:
(1) 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 IO module for the details of the setting.

0320 [19]

Description:
The I/O module connected to the 4th PCI bus is different from the function of the set I/O module.

Remedy:
(1) 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 IO module for the details of the setting.

0330

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0340

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0350 [0]

Description:
The station No. specified by the DeviceNet allocation file1 is incorrect (the station No. is out of the allowable range, or the specified station board is not the DeviceNet master).

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0350 [1]

Description:
The MAC_ID specified by the DeviceNet allocation file1 is not consistent with the MAC_ID of the specified station board.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0350 [2]

Description:
Inconsistency was detected in the scan list of the DeviceNet allocation file1.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0350 [10]

Description:
The station No. specified by the DeviceNet allocation file2 is incorrect (the station No. is out of the allowable range, or the specified station board is not the DeviceNet master).

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0350 [11]

Description:
The MAC_ID specified by the DeviceNet allocation file2 is not consistent with the MAC_ID of the specified station board.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0350 [12]

Description:
Inconsistency was detected in the scan list of the DeviceNet allocation file2.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0370

Description:
The designation in the parameter is different from the connected welding timer.

Remedy:
Check the specified setting of the welding timer. If the welding timer is set to NADEX, make sure it is one of the following: A) The EM item of the corresponding slave station is enabled in the master setting of the Molex DeviceNet board (SST-DN4). B) The Nadex timer interface board (JARCR-XFB01B-2, -3, -4) is connected.

0390

Description:
Illegal instruction cycle is set.

Remedy:
(1) Check the following settings.

• Instruction execution cycle

0400 [30]

Description:
An error occurred during the parameter/file transfer to the YSF21 board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• The PCI connector of YSF21 board
• The PCI connector of YIF01 board

0400 [50]

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

Remedy:
(1) Check the following settings.

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

0400 [51]

Description:
An error occurred during the parameter/file transfer to the 2nd servo board.

Remedy:
(1) Check the following settings.

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

0400 [52]

Description:
An error occurred during the parameter/file transfer to the 3rd servo board.

Remedy:
(1) Check the following settings.

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

0400 [53]

Description:
An error occurred during the parameter/file transfer to the 4th servo board.

Remedy:
(1) Check the following settings.

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

0400 [54]

Description:
An error occurred during the parameter/file transfer to the 5th servo board.

Remedy:
(1) Check the following settings.

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

0400 [55]

Description:
An error occurred during the parameter/file transfer to the 6th servo board.

Remedy:
(1) Check the following settings.

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

0400 [56]

Description:
An error occurred during the parameter/file transfer to the 7th servo board.

Remedy:
(1) Check the following settings.

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

0400 [57]

Description:
An error occurred during the parameter/file transfer to the 8th servo board.

Remedy:
(1) Check the following settings.

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

0400 [60]

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

Remedy:
(1) Check the following settings.

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

0400 [61]

Description:
An error occurred during the parameter/file transfer to the 2nd functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [62]

Description:
An error occurred during the parameter/file transfer to the 3rd functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [63]

Description:
An error occurred during the parameter/file transfer to the 4th functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [64]

Description:
An error occurred during the parameter/file transfer to the 5th functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [65]

Description:
An error occurred during the parameter/file transfer to the 6th functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [66]

Description:
An error occurred during the parameter/file transfer to the 7th functional safety board.

Remedy:
(1) Check the following settings.

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

0400 [67]

Description:
An error occurred during the parameter/file transfer to the 8th functional safety board.

Remedy:
(1) Check the following settings.

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

0410 [30]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• The PCI connector of YSF21 board
• The PCI connector of YIF01 board

0410 [50]

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

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode
• The EAXA21 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 servo board, and the system did not startup normally.

Remedy:
(1) Check the following settings.

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

0410 [60]

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

Remedy:
(1) Check the following settings.

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

0410 [61]

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

Remedy:
(1) Check the following settings.

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

0410 [62]

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

Remedy:
(1) Check the following settings.

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

0410 [63]

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

Remedy:
(1) Check the following settings.

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

0410 [64]

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

Remedy:
(1) Check the following settings.

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

0410 [65]

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

Remedy:
(1) Check the following settings.

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

0410 [66]

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

Remedy:
(1) Check the following settings.

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

0410 [67]

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

Remedy:
(1) Check the following settings.

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

0420 [1]

Description:
The DeviceNet allocation file1 could not be transmitted to the specified station.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

0420 [2]

Description:
The DeviceNet allocation file2 could not be transmitted to the specified station.

Remedy:
(1) Check the following settings. [XFB01 board]

• The settings of the objective DeviceNet allocation file
• The I/O module settings of the objective DeviceNet board in maintenance mode
• The DeviceNet allocation of the I/O module in maintenance mode

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:
(1) Check the following settings.

• Instruction execution cycle

0510 [20]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [21]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [30]

Description:
YSF21 board’s boot interface version is not corresponding to YCP21.

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

0510 [50]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [51]

Description:
2nd servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [52]

Description:
3rd servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [53]

Description:
4th servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [54]

Description:
5th servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [55]

Description:
6th servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [56]

Description:
7th servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [57]

Description:
8th servo board’s interface version is not corresponding to YCP21.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0510 [60]

Description:
The software version of the functional safety board connected to the 1st servo board is unmatched.

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

0510 [61]

Description:
The software version of the functional safety board connected to the 2nd servo board is unmatched.

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

0510 [62]

Description:
The software version of the functional safety board connected to the 3rd servo board is unmatched.

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

0510 [63]

Description:
The software version of the functional safety board connected to the 4th servo board is unmatched.

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

0510 [64]

Description:
The software version of the functional safety board connected to the 5th servo board is unmatched.

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

0510 [65]

Description:
The software version of the functional safety board connected to the 6th servo board is unmatched.

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

0510 [66]

Description:
The software version of the functional safety board connected to the 7th servo board is unmatched.

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

0510 [67]

Description:
The software version of the functional safety board connected to the 8th servo board is unmatched.

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

0510 [70]

Description:
The software version of the YSF21 board is unmatched.

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

0510 [71]

Description:
The software version of the YSF21 board connected to the 2nd servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [72]

Description:
The software version of the YSF21 board connected to the 3rd servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [73]

Description:
The software version of the YSF21 board connected to the 4th servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [74]

Description:
The software version of the YSF21 board connected to the 5th servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [75]

Description:
The software version of the YSF21 board connected to the 6th servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [76]

Description:
The software version of the YSF21 board connected to the 7th servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0510 [77]

Description:
The software version of the YSF21 board connected to the 8th servo board is unmatched.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the following communication cables.

• Communication cable between YSF25 board (CN250/251) and YSF21 board (CN203) (3) If the alarm occurs again, check the YSF21 board version and then consult your Yaskawa representative.

0520 [0]

Content:
The number of axes exceeds the permissible value.

Remedy:
(1) Check the following settings.

• Control group settings in maintenance mode

0600

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0601

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0602

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0603

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0604

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0605

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0606

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0607

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0608

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0609

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0610

Content:
An error occurred at the MADER timer.

Remedy:
Refer to the instruction manual for the MEDAR function.

0700

Content:
The DX200 verifies that the EX IO file are correctly set during a startup process. This alarm occurs if the DX200 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 set the IO module.

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.

0730 [0]

Description:
Welder power serial I/F task cannot be created.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0730 [1]

Description:
Incorrect values are set for the communication frame number with the welder power.

Remedy:
(1) Check the following setting.

• The number of communication frames for Welder power serial communication (RS262)

0730 [2]

Description:
Incorrect values are set for the number of the sending bytes per frame with the welder power.

Remedy:
(1) Check the following setting.

• The number of the sending bytes for Welder power serial communication (RS262)

0730 [3]

Description:
Incorrect values are set for the number of the receiving bytes per frame with the welder power.

Remedy:
(1) Check the following setting.

• The number of the receiving bytes for Welder power serial communication (RS262)

0730 [10]

Description:
The binary semaphore to start up event for Welder power serial I/F task cannot be created.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0730 [11]

Description:
The event resource for Welder power serial I/F task cannot be created

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0730 [12]

Description:
The completion notification mail of Welder power serial I/F task cannot be created.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0730 [13]

Description:
Welder power serial I/F task cannot be created.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0750

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0751

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0752

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0753

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0754

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0755

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0756

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0757

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0758

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0759

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0760

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0761

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0762

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0763

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0764

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0765

Description:
The YCP21 system program is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

0770 [1]

Description:
Safety slave and standard master are used simultaneously in one channel of the DeviceNet board.

Remedy:
(1) Check the following settings. ¥Select [SYSTEM] - [SETUP] - [OPTION BOARD] settings in maintenance mode. Display the slot(channel) that is configured with DeviceNet Safety, set to slave mode.

0770 [2]

Description:
Board that can not be used with DeviceNet Safety is set.

Remedy:
(1) Check the following settings. ¥ Insert the SST-DN4-PCU board to the PCI slot to be used in the DeviceNet Safety. Select [SYSTEM] - [SETUP] - [OPTION BOARD] settings in maintenance mode, set the DeviceNet Safety.

0771 [10000]

Description:
The error was detected by the safety fieldbus proccess (YCP21). Subcode shows the error part of software.

Remedy:
In the case of DeviceNet Safety, please check the following. (1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the SST-DN4-PCU board. Save the CMOS.BIN before replace the board to be safe. Replace the SST-DN4-PCU board, and then load the CMOS.BIN saved before alarm occurred.

0772

Description:
Safety reset request was received from the safety PLC in communication.

Remedy:
Turn the power OFF then back ON.

0790

Description:
The YIF01 battery is exhausted.

Remedy:
(1) Check if the battery is correctly connected to CN110/BAT on the YIF01 board.

0800

Description:
The management area (FAT) of Compact Flash in YCP21 board is damaged.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0801

Content:
The DX200 saves a part of data needed for system operations on the Compact Flash in the YCP21 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 CompactFlash 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 YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

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 DX200 saves a part of data needed for system operations on the Compact Flash in the YCP21 board. This alarm occurs if it cannot access to the YCP21correctly. Usually, this alarm occurs accAL-0800 and AL-0801 occurs simultaneously. Since this alarm occurs due to CompactFlash 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 YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

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 YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0804

Content:
In the DX200 software version DN1.70.00A(*)-00 or later, the structure of the variable data area was modified. Therefore, if you upgrade the DX200 software from older version, you have to rebuild the variable data area.

Remedy:
Select the following menu in maintenance mode and execute [DATA REBUILD] opetration.

• [SYSTEM]-[DATA REBUILD] Even if you perform the above operation, the variable data won’t be deleted.

0810 [1]

Description:
An error was found in the input/output direction data of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [3]

Description:
In the output side setting of allocation configuration data, the specified R-register start No. for the TOYOPUC exceeds the R-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [4]

Description:
In the output side setting of allocation configuration data, the set number to use the input side R-register of the TOYOPUC exceeds the R-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [5]

Description:
In the output side setting of allocation configuration data, the set number to use the M-register of concurrent I/O exceeds the M-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [8]

Description:
An error was found in the type set for output direction of allocation configuration data.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [9]

Description:
An error was found in the type set for input direction of allocation configuration data.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [10]

Description:
An error was found in the type specified for system data of allocation configuration data.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [12]

Description:
An error was found in the specified number of registers which are used by the system data “CURR.POS. (PULSE)” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [14]

Description:
An error was found in the specified number of registers which are used by the system data “CURR.POS. (XYZ)” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [16]

Description:
An error was found in the specified number of registers which are used by the system data “WELDING INFO.” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [18]

Description:
An error was found in the specified number of registers which are used by the system data “TASK INFO.” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [20]

Description:
An error was found in the specified number of registers which are used by the system data “EXECUTE PROGRAM INFO.” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [22]

Description:
An error was found in the specified number of registers which are used by the system data “INST. MESSAGE” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [23]

Description:
An error was found in the specified number of registers for “Alarm/Error/Message” in the system data of Allocation setting information.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [30]

Description:
In the input side setting of allocation configuration data, the specified R-register start No. for the TOYOPUC exceeds the R-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [31]

Description:
In the input side setting of allocation configuration data, the set number to use the input side R-register of the TOYOPUC exceeds the R-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [32]

Description:
In the input side setting of allocation configuration data, the set number to use the M-register of concurrent I/O exceeds the M-register limit.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [34]

Description:
An error was found in the specified number of registers which are used by the system data “standard time setting data” of allocation configuration.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [41]

Description:
In the output side setting of allocation configuration data, some of the TOYOPUC’s R-registers are specified redundantly.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [42]

Description:
In the output side setting of allocation configuration data, some of the M-registers of concurrent I/O are specified redundantly.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [44]

Description:
In the input side setting of allocation configuration data, some of the TOYOPUC’s R-registers are specified redundantly.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

0810 [45]

Description:
In the input side setting of allocation configuration data, some of the M-registers of concurrent I/O are specified redundantly.

Remedy:
(1) Check the following settings.

• Allocation configuration for the TOYOPUC

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 YIF01 board.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0901

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

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0902

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

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0903

Description:
A Watchdog timeout was detected in the YCP02 #3 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0904

Description:
A Watchdog timeout was detected in the YCP02 #4 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0905

Description:
A Watchdog timeout was detected in the YCP02 #5 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0906

Description:
A Watchdog timeout was detected in the YCP02 #6 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0907

Description:
A Watchdog timeout was detected in the YCP02 #7 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0908

Description:
A Watchdog timeout was detected in the YCP02 #8 board.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0909 [0]

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

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

• YSF21 board

0909 [1]

Content:
The DX200 can safely stop the system with a watchdog function when an error occurred. This alarm occurs if a watchdog timeout is detected in the YSF21 board (CPU2).

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

• YSF21 board

0910

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0911

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0912

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0913

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0914

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0915

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0916

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0917

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0918

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0919 [0]

Content:
An error was detected in the CPU1 of the YSF21board.

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

• YSF21 board

0919 [1]

Content:
An error was detected in the CPU2 of the YSF21board.

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

• YSF21 board

0920 [1]

Description:
The JL chip does not operate normally.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YCP21 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP21 board, and then remove the CF from the failure YCP21 board to insert it into the new YCP21 board.

0931

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0932

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0933

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0934

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0935

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0936

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0937

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0938

Description:
An error was detected in the CPU.

Remedy:
(1) Check the following settings.

• Optional board in maintenance mode

0940

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

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

• EAXA21 board

0941

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

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

• EAXA21 board

0942

Description:
A Watchdog timeout was detected in the EAXA#3 board.

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

• EAXA21 board

0943

Description:
A Watchdog timeout was detected in the EAXA#4 board.

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

• EAXA21 board

0944

Description:
A Watchdog timeout was detected in the EAXA#5 board.

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

• EAXA21 board

0945

Description:
A Watchdog timeout was detected in the EAXA#6 board.

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

• EAXA21 board

0946

Description:
A Watchdog timeout was detected in the EAXA#7 board.

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

• EAXA21 board

0947

Description:
A Watchdog timeout was detected in the EAXA#8 board.

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

• EAXA21 board

0950

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0951

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0952

Description:
An error was detected in the CPU of servo board #3.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0953

Description:
An error was detected in the CPU of servo board #4.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0954

Description:
An error was detected in the CPU of servo board #5.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0955

Description:
An error was detected in the CPU of servo board #6.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0956

Description:
An error was detected in the CPU of servo board #7.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0957

Description:
An error was detected in the CPU of servo board #8.

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following cables and connectors.

• The cable of EAXA21 board CN509
• The cable of EAXA21 board connector CN515/516
• The PCI connector of the YIF01 board
• The cable of YIF01 board connector CN113

0970 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0970 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0971 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0971 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0972 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0972 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0973 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0973 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0974 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0974 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0975 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0975 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0976 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0976 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0977 [0]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0977 [1]

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

Remedy:
(1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection and insertion of the following connector.

• CN509 cable of EAXA21 board
• The cable of EAXA21 board connector CN515/516
• CNBXconnector of EAXA21board and YSF25 board
• The PCI connector of YIF01board
• The cable of YIF01 board connector CN113

0980

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

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

0981

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

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

0982

Description:
A Watchdog timeout was detected in the functional safety board #3.

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

0983

Description:
A Watchdog timeout was detected in the functional safety board #4.

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

0984

Description:
A Watchdog timeout was detected in the functional safety board #5.

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

0985

Description:
A Watchdog timeout was detected in the functional safety board #6.

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

0986

Description:
A Watchdog timeout was detected in the functional safety board #7.

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

0987

Description:
A Watchdog timeout was detected in the functional safety board #8.

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

0990 [1]

Description:
YCP21board detect the Controller power off signal (Power lost signal) of YIF01 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:
YCP21board detect the WATCHDOG TIMER ERROR of YIF01 board when the control power turned ON.

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

0990 [3]

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

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

0990 [4]

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

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

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 YIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the YIF01 board, and then load the CMOS.BIN saved before alarm occurred.

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 YIF01 board. Save the CMOS.BIN before replace the board to be safe. Replace the YIF01 board, and then load the CMOS.BIN saved before alarm occurred.

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, check the connection and insertion of the following cables and connectors.

• The cable of YPS01 unit connector CN158/159
• The CN5 connector of the YBB21 back board.
• Cable replace between the YPS01 unit and the YBB21 back board.

0991 [1]

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

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

• YCP02 board

0992 [1]

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

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

• YCP02 board

0993 [1]

Description:
An error was detected in the CPU of the optional YCP02 #3.

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

• YCP02 board

0994 [1]

Description:
An error was detected in the CPU of the optional YCP02 #4.

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

• YCP02 board

0995 [1]

Description:
An error was detected in the CPU of the optional YCP02 #5.

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

• YCP02 board

0996 [1]

Description:
An error was detected in the CPU of the optional YCP02 #6.

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

• YCP02 board

0997 [1]

Description:
An error was detected in the CPU of the optional YCP02 #7.

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

• YCP02 board

0998 [1]

Description:
An error was detected in the CPU of the optional YCP02 #8.

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

• YCP02 board

0999

Content:
An unknown alarm was detected.

Remedy:
If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).