Yaskawa Alarm Codes 4700 – 4799
Yaskawa Alarm Codes 4700 – 4799
4700 | SYSTEM ERROR 2 (RSC1) | SUB-Code Internal control error in software | Software operation error occurred | (1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | ||||||||||||||||||||||||||||||||||
4701 | MEMORY ALLOCA- TION ERROR | Software operation error occurred | (1) Turn the power OFF then back ON. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4703 | F-SAFE OPERA- TION MODE ER- ROR | Data error | (1)Change the teach mode. (2)Reset the alarm, and then try again. (3) If the alarm occurs again, set to home position. | |||||||||||||||||||||||||||||||||||
YSF25 board failure | (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 unit to be safe. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4707 | TIMING CONTROL ERROR | 1 | Control data error oc- curred at prereading. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||
2 | Control data error oc- curred. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | Index number of the target does not exist. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4 | Bank number of the target does not exist. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5 | Control data size over. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
6 | Control index over- flow. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7 | The control-group of surveillance does not exist. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
8 | Instruction index overflow. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
9 | An error occurred when calculate a feedback position. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
10 | The control-group of the target which su- pervises a position does not exist. (Func- tion the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
11 | Waiting time exceed- ed the limit. (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
12 | Watching information settings incomplete (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
13 | Delay control impos- sible (Function the timing control) | Setting error | (1) Check the following settings. Please change the settings so as not to delay control. | |||||||||||||||||||||||||||||||||||
14 | Execution control re- quest settings incom- plete (Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
15 | Instruction that can not coexist with FPL/ +DOUT/+PULSE was used | Setting error | (1)Check the following settings. ·FPL/DOUT/+PULSE and NWAIT can not be used at the same time for SYMOVL instruction. Correct the JOB. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||
16 | Monitor error oc- curred.(Function the timing control) | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
17 | Executed step desig- nation error | Setting error | (1) Check the following settings. ·Please review a JOB so that prereading processing of timing control is completed before an operation start of the control object step. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4708 | MOTOR GUN AUTO TUNING IN- COMPLETE | SUB-Code: Gun number | Setting error | Please complete the setting of MOTOR GUN AUTO TUNING FILE as the following operations. 1. choose [SPOT WELDING] ->[MOTOR GUN AUTO TUNING]. 2. change the mode to PLAYBACK, then push [EXECUTE]. 3. select [REGIST], after the setting of MOTOR GUN AUTO TUNING FILE completes. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4709 | WELD COMPLETE SIGNAL OFF | SUB-Code: Welder number | Setting error | (1) Reset the alarm, and then try again. NOTE) When trying the JOB again, the robot returns to the previ- ous welding point where the spot welding wasn’t completed nor- mally and welds again there. (2) If the alarm occurs again, check the following setting of the tim- er. ∙Decrease the offset time of opening the gun. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4710 | WELDER ERROR | Welding power failure | It will be automatically reset after 10 seconds. Then, start again. | |||||||||||||||||||||||||||||||||||
Welding power failure | Turn the primary power of welding power OFF then back ON | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4711 | 24V FUSE BLOWN (EW-BOARD) | Parts failure | Replace the fuse on the YEW board. | |||||||||||||||||||||||||||||||||||
Board failure | Replace the YEW board of the corresponding station. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4712 | 24V DETECT CIR ERR (EW-BOARD)” | Board failure | Replace the YEW board of the corresponding station. | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4713 | EXT 24V POWER ERR (EW-BOARD) | Connection failure | Check if the 24V line that is input for YEW board is correctly wired. | |||||||||||||||||||||||||||||||||||
Unit failure | Replace the unit that supplies with the external 24V power. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4714 | 18V LINE BROKEN (EW-BOARD) | YEW01 board failure | Replace the YEW board of the corresponding station. | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4715 | CIP MESSAGE SERVER FUNC ER- ROR | 1 | Failed in the genera- tion of the CIP server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||
2 | Failed in the ID take of the CIP server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | Failed in the genera- tion of the class entry table. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4 | Library initialize error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5 | Failed in the genera- tion of the access pro- cess. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
10 | Detect undefined er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
20 | Detect sever function started processing. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
30 | Detect request error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
31 | Detect memory error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
32 | Detect mail send er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
33 | Detect CIP answer er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
40 | Detect CIP server task mail receive er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
41 | Detect CIP server task request data er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
50 | Detect CIP server task send error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4716 | BINARY ETHER- NET SERVER FUNC ERR | 1 | IP address duplicat- ed. | IP address setting er- ror | (1) Reset the alarm, and then try again. (2) The IP address is duplicated with the robot controller. Confirm the IP address of the communication target. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||
Detect message li- brary initialize error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | ||||||||||||||||||||||||||||||||||||
2 | Failed in the genera- tion of the RC connect management task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | Failed in the genera- tion of the RC server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4 | Failed in the genera- tion of the file server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1040 | Failed in the request take of the RC con- nect management task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1041 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1042 | Received data area overflow. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1043 | Failed in the request error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1044 | Failed in the request error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1059 | In a RC connect man- agement task, unde- fined error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
1060 | Failed in the ID take of the RC server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1061 | Failed in the mail take of the RC server task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1062 | In a RC server task, request mail data er- ror detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1063 | Answer data area overflow. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1064 | In a RC server task, receive data area overflow. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1079 | In a RC server task, undefined error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1080 | In a file server task, mail receive error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1081 | In a file server task, request mail data er- ror detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
1082 | IP address duplicat- ed. | IP address setting er- ror | (1) Reset the alarm, and then try again. (2) The IP address is duplicated with the robot controller. Confirm the IP address of the communication target. (3) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
In a file server task, request error oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | ||||||||||||||||||||||||||||||||||||
1083 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1084 | In a file server task, receive data area overflow. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2045 | In a RC connect man- agement task, send error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2046 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2065 | Detect RC server task send error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
2066 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2085 | Detect file server task send error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2086 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2087 | In a file server task, answer data error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2088 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2089 | In a file server task, answer data area overflow. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2098 | Failed in the status er- ror occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2099 | In a file server task, undefined error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3090 | In a file sever task, file close error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4718 | BINARY ETHER- NET CLIENT FUNC ERR | 1 | Detect message li- brary initialize error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||
2 | Failed in the genera- tion of the file function task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3 | Failed in the genera- tion of the RC function task. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4 | Detect I/F data error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
10 | Detect undefined er- ror. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
110 | In a file task, unde- fined error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
510 | In a RC task, unde- fined error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
511 | In a RC task, request command error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
512 | In RC task, there is not the class entry of the request com- mand. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
513 | In RC task, there is not the service entry of the request com- mand. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1130 | In a high speed Ether- net task, request mail error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1131 | In a high speed Ether- net task, request command error de- tected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
1132 | In a file task, mail re- ceive error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2140 | In a file task, file read- ing error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
2141 | In a file task, file writ- ing error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3150 | In a file task, request send error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3151 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3160 | In a file task, reply packet clear error oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3161 | Failed in the take of the reply packet data error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3162 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3163 | In a file task, time out occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3164 | In a file task, receive data area overflow occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3165 | In a file task, received data unmatched. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3166 | In a file task, receive data size overflow oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3167 | In a file task, received data size set to zero occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3168 | In a file task, reply head error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3169 | In a file task, reply status error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5530 | In a RC task, interface request error oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5531 | In a RC task, interface answer error oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5532 | In a RC task, interface data area overflow occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
5533 | In a RC task, interface data writing error oc- curred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
6540 | In a RC task, time out occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
6541 | Detect data error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
6542 | Detect exclusive pro- cess error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
6543 | Detect time out. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
6544 | Setting error | Setting error | (1) Reset the alarm, and confirm whether the following parameter is set to zero. ∙S2C541 ∙S2C542 | |||||||||||||||||||||||||||||||||||
Detect data error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | ||||||||||||||||||||||||||||||||||||
6545 | Detect exclusive pro- cess error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7550 | In a RC task, request send error occurred. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
7551 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7560 | In a RC task, reply packet error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7561 | In a RC task, reply take error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7562 | Failed in the endian conversion. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7563 | Detect time out. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7564 | In a RC task, receive data area overflow detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7565 | In a RC task, received data unmatched. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7566 | In a RC task, received data size over. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
7567 | In a RC task, receive data size zero detect- ed. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7568 | In a RC task, reply head error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
7569 | In a RC task, reply status error detected. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4719 | VIB SUPPRES- SION FLT TIME OUT | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4721 | IMPROPER TOOL FILE SETTING | SUB-Code: Control group number & tool data & tool number. | Setting error | (1) Reset the alarm. (2) Check the following settings. ∙Select a sub menu [TOOL] under main menu [ROBOT]. ∙Select the coordinate window of the number specified by SUB- Code (tool number). ∙Set „0“ to the coordinate data specified by SUB-Code (tool data). | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4725 | SETTM ERROR | 1 | TM variable number exceeded the limit. | Setting error | (1) Check the following settings. ·Check the TM variable number used in the JOB, and then correct the JOB to fall within the range of TM variable number(0-59). | |||||||||||||||||||||||||||||||||
2 | Same TM variable set up as „LOCAL“ was used in different tasks. | Setting error | (1) Check the following settings. ·Correct the job not to use the same TM variable set up as „LO- CAL“ in different tasks. | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | The I/O signal num- ber set up in the „SETTM SETUP FILE“ cannot be car- ried out. | Setting error | (1) Check the following settings. ·Check the I/O signal number set in the „SETTM SETUP FILE“, and then correct it within the effective setting range. | |||||||||||||||||||||||||||||||||||
4727 | GETCVSFT ER- ROR | 1 | Conveyor condition support file (WORK ID shift) is not set. | Setting error | (1) Check the following settings. ·Set „USED STATUS“ of conveyor condition support file (WORK ID shift) to „1: Use.“ | |||||||||||||||||||||||||||||||||
2 | Conveyor condition support file (WORK IN/OUT shift) is not set. | Setting error | (1) Check the following settings. ·Set „USED STATUS“ of conveyor condition support file (WORK IN/OUT shift) to “1: Use.” | |||||||||||||||||||||||||||||||||||
3 | Conveyor condition file is not set. | Setting error | (1)Check the following settings. ·Set „USED STATUS“ of conveyor condition file to „1: Use.“ | |||||||||||||||||||||||||||||||||||
4 | Conveyor condition support file (Start shift) is not set. | Setting error | (1)Check the following settings. ·Set „USED STATUS“ of conveyor condition support file (Start shift) to „1: Use.“ | |||||||||||||||||||||||||||||||||||
5 | „WORK ID signal“ of the conveyor condi- tion support file (WORK ID shift) is not set | Setting error | (1) Check the following settings.·Set „WORK ID signal“ of Con- veyor condition support file (WORK ID shift) | |||||||||||||||||||||||||||||||||||
6 | „WORK IN/OUT sig- nal“ of the conveyor condition support file (WORK IN/OUT shift) is not set | Setting error | (1) Check the following settings. ·Set „WORK IN/OUT signal“ of conveyor condition support file (WORK IN/OUT shift) | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4728 | CONVEYOR SYN- CHRONIZATION (SHIFT FUNCTION) ERROR | 1 | “WORK ID signal” of the Conveyor condi- tion support file (WORK ID shift) is not set | Setting error | (1) Check the following settings. ·Set „WORK ID signal“ of conveyor condition support file (WORK ID shift) | |||||||||||||||||||||||||||||||||
2 | “WORK IN/OUT sig- nal” of the conveyor condition support file (WORK IN/OUT shift) is not set | Setting error | (1) Check the following settings. ·Set „WORK IN/OUT signal“ of conveyor condition support file (WORK IN/OUT shift) | |||||||||||||||||||||||||||||||||||
4729 | 1 | The file number is wrong. An attempt was made to record again the file being recorded by IB- GNSTART instruc- tion. | Setting error | (1) Check the following settings. ·Set a number of the file in IBGNSTART instruction, so that the file being recorded does not repeat. | ||||||||||||||||||||||||||||||||||
2 | The number of robot in the JOB is wrong. An attempt was made to record the file in the JOB including robots more than two. | Setting error | (1) Check the following settings. ·Correct the JOB, so that IBGNSTART instruction is used in the JOB of one robot. | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | The number of exter- nal axis (STATION or BASE) in the JOB is wrong. An attempt was made to record the file in the JOB including exter- nal axis (STATION or BASE) more than two. | Setting error | (1) Check the following settings. ·Correct the JOB, so that IBGNSTART instruction is used in the JOB of one external axis (STATION or BASE). | |||||||||||||||||||||||||||||||||||
4 | IBGNEND instruction is not registered. | Setting error | (1) Check the following settings. ·Register IBGNEND instruction in the same JOB after the line where IBGNSTART instruction was registered. | |||||||||||||||||||||||||||||||||||
5 | IBGNEND signal is not turned OFF be- fore a specified time at the time of IBGN- START instruction ex- ecuted. | Setting error | (1)Check the following settings. ·Turn off IBGNEND signal by executing mpNoticeIBGNRecor- dRefEnd() in the MotoPlus application before IBGNSTART in- struction is executed. | |||||||||||||||||||||||||||||||||||
6 | The setting of the playback file is not completed at the time of IBGNSTART PLAYBACK=ON in- struction executed. | Setting error | (1)Check the following settings. ·Complete the setting of the playback file by executing mpNoti- ceIBGNPlaybackSetEnd() in the MotoPlus application before IB- GNSTART PLAYBACK=ON instruction is executed. | |||||||||||||||||||||||||||||||||||
7 | JOB name in the play- back file is wrong at the time of IBGN- START PLAY- BACK=ON instruction executed. | Setting error | (1) Check the following settings. ·Set the JOB name in which IBGNSTART PLAYBACK=ON in- struction is executed in the playback file. | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
8 | The setting of interpo- lation clock in the playback file is wrong at the time of IBGN- START PLAY- BACK=ON instruction executed. | Setting error | (1) Check the following settings. ·Set the interpolation clock acquired in the record file in the play- back file. | |||||||||||||||||||||||||||||||||||
9 | The start/end step number in the play- back file is wrong at the time of IBGN- START PLAY- BACK=ON instruction executed. | Setting error | (1) Check the following settings. ·Set the start/end step number of the JOB in which the record file was made in the playback file. | |||||||||||||||||||||||||||||||||||
10 | IBGNSTART PLAY- BACK=ON instruction was executed in a for- ward direction, before a robot arrives at the start step of the play- back | Setting error | (1) Check the following settings. ·Execute IBGNSTART PLAYBACK=ON instruction in a forward direction, after a robot arrives at the start step of the playback file in a backward direction, when IBGNSTART PLAYBACK=ON in- struction was executed in a backward direction. | |||||||||||||||||||||||||||||||||||
11 | An error occurred when IBGNSTART PLAYBACK=ON in- struction was execut- ed in a backward direction. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4730 | CANNOT EXE- CUTE BRAKE SLIP DETECT | 1 | Brake slip detection was commanded to be executed while an- other optional func- tion was in execution. | Software operation error occurred | (1) Reset the alarm, and then try again. (2)If another optional function was commanded to be executed, cannot execute brake slip detection.Correct the JOB. | |||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
2 | Brake slip detection could not be executed in the specified axis. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
3 | Holding torque data which is calculated by the brake slip detec- tion is incorrect. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
4 | Detection torque data which is calculated by the brake slip detec- | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative | |||||||||||||||||||||||||||||||||||
5 | The torque value for the brake slip detec- tion device is not set. | Software operation error occurred | (1) Reset the alarm. (2)Check the following settings. ∙Check torque value | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
6 | Holding torque data which is calculated by the brake slip detec- tion exceeds the limit. | Software operation error occurred | (1) Reset the alarm. (2)Check the following settings. ∙Check torque value | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
7 | The parameter of the pulse operation ex- ceeds the limit. | Software operation error occurred | (1) Reset the alarm. (2)Check the following settings. ∙Pulse operation (S1CxG512 to 519) | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
8 | The parameter of the error detection value parameter is incor- | Software operation error occurred | (1) Reset the alarm. (2)Check the following settings. ∙Error detection value(S1CxG520 to 527) | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4733 | WRIST MOTION ERROR (SINGULAR POINT) | An attempt was made to pass the B-axis zero degree position (singular area). | Setting error | (1) Check the following settings. ∙Check the teaching position of the JOB so that the robot does not pass the B-axis zero degree position (singular area). | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4734 | FIGURE CONVER- SION IMPOSSIBLE | The setting of the form data for Flip/No Flip is not „B-axis An- gle“. | Setting error | (1) Check the following settings. ∙Set „1“ to „S2C658: Type data detail settings“. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4735 | SENSOR-LESS LEARNING CTRL ERROR | 1 | Learning control table setting error. | Software operation error occurred | (1) Reset the alarm, and then try again. (2)If another optional function was commanded to be executed, cannot execute brake slip detection. Correct the JOB. | |||||||||||||||||||||||||||||||||
2 | Learning control table ID is incorrect. | Software operation error occurred | (1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN in MAINTE- NANCE mode, and then contact your YASKAWA representative about occurrence status (operating procedure). | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
3 | Multiple task execu- tion error | Setting error | (1) Check the following settings. ∙The Learning control cannot execute the same time by multiple tasks. Correct the JOB. | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4736 | USER GROUP IO ERROR | 1 | Setting of „START“ in the user group I/O setting file is 0. | Setting error | (1) Check the following settings. ·Set a value of 1-4096 at „START“ in the user group I/O setting file. | |||||||||||||||||||||||||||||||||
2 | Setting of „LENGTH“ in the user group I/O setting file is abnor- mal. | Setting error | (1) Check the following settings. ·Set a value of 1-32 at „LENGTH“ in the user group I/O setting file. | |||||||||||||||||||||||||||||||||||
3 | The number of I/O signals in the defini- tion of the user group I/O is out of a range. | Setting error | (1)Check the following settings. ·Set „START“ or „LENGTH“ in the user group I/O setting file, so that the number of I/O signals in the definition of the user group I/ O is within a range. | |||||||||||||||||||||||||||||||||||
4 | A number of the user group I/O is abnor- mal. | Setting error | (1)Check the following settings. ·Set a number of the user group I/O to 1-64 used in the JOB. | |||||||||||||||||||||||||||||||||||
4737 | MOTION RANGE LIMIT OVER | SUB-Code: Control group | Setting error | (1) Check the following settings. ·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range. (2) Check the following setting in case of the robot with the special range of motion. ·Check the weight information in the tool file. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4738 | DEST MOTION RANGE LIMIT OVER | SUB-Code: Control group | Setting error | (1) Check the following settings. ·Check the position setting for the step (move instruction) where the alarm occurred. (2) Check the following setting in case of the robot with the special range of motion. ·Check the weight information in the tool file. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4739 | USER ANALOG IO ERROR | 1 | Setting of „START“ in the user analog I/O setting file is 0. | Setting error | (1) Check the following settings. ·Set a value of 1-4096 at „START“ in the user analog I/O setting file. | |||||||||||||||||||||||||||||||||
2 | The number of I/O signals in the defini- tion of the user analog I/O is out of a range. | Setting error | (1) Check the following settings. ·Set „START“ or „LENGTH“ in the user analog I/O setting file, so that the number of I/O signals in the definition of the user analog I/O is within a range. | |||||||||||||||||||||||||||||||||||
3 | The number of the user analog I/O set- ting file is abnormal. | Setting error | (1) Check the following settings. ·Set the number of the user analog I/O setting file to 1-16 used in the JOB. | |||||||||||||||||||||||||||||||||||
4740 | M-SAF OVERRUN DETECT | Overrun limit switch control group that is displayed in the SUB- Code has tripped. | Fuse failure | (1) Turn the power OFF then back ON. (2) If the alarm occurs again, check the connection of the fuse of YSF22 board and then turn the power ON again. | ||||||||||||||||||||||||||||||||||
Overrun limit switch released | (1) Reset the alarm. (2) If the alarm occurs again, overrun limit switch is released. Se- lect „OVERRUN&SHOCK SENSOR“ under sub menu „ROBOT“ to reset the limit switch. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Connection failure | (1) Reset the alarm. (2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ·Check the electrical connection of slack and cable of connection between the control group in whom the overrun limit switch oper- ated, YFC22 board (CN219) or YFC22 board (CN219) and YSF22 board (CN219), and a connector. ·Check the connection and inserting state of the following manip- ulator cables (Between robot and robot controller) and connec- tors. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2)(2) If the alarm occurs again, Replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a sys- tem where a plurality of YSF22 boards are connected, replace the board, which is connected to the control group on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Overrun limit switch failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the limit switch or an equiv- alent switch. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4741 | M-SAF PPESP SIG. ERROR | Emergency stop sig- nal of programming pendant was un- matched longer than a certain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN218 ∙Replace the cable of the programming pendant. ∙Check connectors of the connected outside devices of EMER- GENCY STOP signal of programming pendant line. | ||||||||||||||||||||||||||||||||||
Programming pen- dant failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the programming pendant. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Fuse failure | {Controller for painting use( Explosion-proof programming pen- dant spec)} (1) Reset the alarm. (2) If the alarm occurs again, replace the fuse(FU10, FU11) in the painting module. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4742 | M-SAF PBESP SIG. ERROR | Emergency stop sig- nal of the panel box was unmatched for a certain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN218 ∙Check connectors of the connected outside devices of EMER- GENCY STOP signal line. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Hardware failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the emergency stop switch of the panel box. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a sys- tem where a plurality of YSF22 boards are connected, replace the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4743 | M-SAF EXESP SIG. ERROR | External emergency stop signal was un- matched for a certain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check connectors of the connected outside devices of EXTER- NAL EMERGENCY STOP signal line. | ||||||||||||||||||||||||||||||||||
Hardware failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the external emergency stop switch. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4744 | M-SAF PP ENABLE SW SIG. ERROR | The enable switch signal of PP was un- matched for a certain time. | Programing pendant illegal operation | There are two contact points for an enable switch, and only one point may be turned on by how to squeeze it or when putting it on the place where it is not a plane such as on the knee etc. Check how to squeeze or put the programming pendant on flat. | ||||||||||||||||||||||||||||||||||
Programming pen- dant failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the programming pendant. | |||||||||||||||||||||||||||||||||||||
Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙Replace the cable of the programming pendant. ∙YSF22-CN218 | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Fuse failure | {Controller for painting use (Explosion-proof programming pen- dant spec)} (1) Reset the alarm. (2) If the alarm occurs again, replace the fuse(FU14, FU15) in the painting module. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4745 | M-SAF EX ENABLE SW SIG. ERROR | External Enable sig- nal was unmatched for a certain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check connectors of the connected outside devices of EXTER- NAL ENABLE SWITCH signal line. | ||||||||||||||||||||||||||||||||||
Hardware failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the external enable switch. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4746 | M-SAF SAFETY FENCE SIG. ER- ROR | Safety fence signal is unmatched for a cer- tain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check connectors of the connected outside devices of SAFETY FENCE signal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4747 | M-SAF OVERRUN SIG. ERROR | The meaning of each SUB-Code is as fol- lows: 1:OT1 2:OT2 3:OT3 4:OT4 | Overrun limit switch released | (1) Reset the alarm. (2) If the alarm occurs again, overrun limit switch is released. Se- lect “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the limit switch. | ||||||||||||||||||||||||||||||||||
Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, please insert and conduction state of the cable and connector of the control group to which the over- run limit switch has tripped. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Overrun limit switch failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the limit switch or an equiv- alent switch. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board, which is connected to the control group on which | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4748 | M-SAF ON_EN- ABLE SIG. ERROR | The meaning of each SUB-Code is as fol- lows: 1:ON_ENABLE1 2:ON_ENABLE2 3:ON_ENABLE3 4:ON_ENABLE4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check ON_ENABLE signal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board, which is connected to the ON_ENABLE signal on | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4749 | M-SAF FULL SPEED SIG. ER- ROR | Full speed test signal was unmatched for a certain time. | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check connectors of the connected outside devices of FST sig- nal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the YFC22 board which is connected to the first YSF22 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4750 | M-SAF GENERAL INPUT SIG. ERROR | The meaning of each SUB-Code is as fol- lows: 1:GSIN1 2:GSIN2 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙YSF22-YFC22 cable ∙Check connectors of the connected outside devices of GSIN sig- nal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the GSIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4751 | YSF24 GENERAL INPUT SIG. ERROR | The meaning of each SUB-Code is as fol- lows: 1:XIN1 2:XIN2 3:XIN3 4:XIN4 5:XIN5 6:XIN6 7:XIN7 8:XIN8 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC24 ∙YSF22-YFC24 cable ∙Check connectors of the connected outside devices of XIN signal line. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF24 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF24 board. In a system where a plurality of YSF24 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YFC24 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC24 board. In a system where a plurality of YFC24 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4752 | M-SAF PPESP DI- AG. ERROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4753 | M-SAF PBESP DI- AG. ERROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4754 | M-SAF EXESP DI- AG. ERROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4755 | M-SAF PP ENABLE SW DIAG. ERROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4756 | M-SAF EX ENABLE SW DIAG. ERROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4757 | M-SAF SAFETY GUARD DIAG. ER- ROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4758 | M-SAF OVERRUN DIAG. ERROR | An error is detected by YSF21 board. The error is occurred in the signal that is in- verted representa- tion. CPU1 1:OT1 CPU1 2:OT2 CPU1 3:OT3 CPU1 4:OT4 CPU2 1:OT1 CPU2 2:OT2 CPU2 3:OT3 CPU2 4:OT4 | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board, which is connected to the overrun signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4759 | M-SAF ON_EN- ABLE DIAG. ER- ROR | An error is detected by YSF21 board. The meaning of each SUB-Code is as fol- lows: CPU1 1:ON_EN- ABLE1 CPU1 2:ON_EN- ABLE2 CPU1 3:ON_EN- ABLE3 CPU1 4:ON_EN- ABLE4 CPU2 1:ON_EN- ABLE1 CPU2 2:ON_EN- ABLE2 CPU2 3:ON_EN- ABLE3 CPU2 4:ON_EN- ABLE4 | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board, which is connected to the ON_ENABLE signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4760 | M-SAF FULL SPEED DIAG. ER- ROR | SUB-Code indicates the process that the software of CPU1 or CPU2 detected an er- ror. | YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | ||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the YSF22 board which is connected to the first EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4761 | M-SAF GENERAL INPUT DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:GSIN1 CPU1 2:GSIN2 CPU2 1:GSIN1 CPU2 2:GSIN2 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC24 ∙YSF22-YFC24 cable ∙Check connectors of the connected outside devices of GSIN sig- nal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4762 | YSF24 GENERAL INPUT DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:XIN1 CPU1 2:XIN2 CPU1 3:XIN3 CPU1 4:XIN4 CPU1 5:XIN5 CPU1 6:XIN6 CPU1 7:XIN7 CPU1 8:XIN8 CPU2 1:XIN1 CPU2 2:XIN2 CPU2 3:XIN3 CPU2 4:XIN4 CPU2 5:XIN5 CPU2 6:XIN6 CPU2 7:XIN7 CPU2 8:XIN8 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC24 ∙YSF22-YFC24 cable ∙Check connectors of the connected outside devices of XIN signal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF24 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF24 board. In a system where a plurality of YSF24 boards are connected, re- place the board, which is connected to the XIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4763 | M-SAF CONTACT FB DIAG. ERR (CPU1) | The meaning of each SUB-Code is as fol- lows: 1:KMMB1 2:KMMB2 3:KMMB3 4:KMMB4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN217 ∙YPU-CN607 ∙Cable continuity between YSF22 board and YPU unit. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YPU unit failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YPU unit. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4764 | M-SAF STO FB DI- AG. ERROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:EDM1 CPU1 2:EDM2 CPU1 3:EDM3 CPU1 4:EDM4 CPU2 1:EDM1 CPU2 2:EDM2 CPU2 3:EDM3 CPU2 4:EDM4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ·EAXA21-CN521/EAXB21-CN522,CN523,CN524 ∙YSF22-CN217 ∙Cable continuity between YSF22 board and EAXA21 board. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
EAXA21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4765 | M-SAF BRAKE FB DIAG. ERROR | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN214 ·Cable continuity between YSF22 board(CN214) and EAXA21 board(CN511). ·Cable continuity between EAXA21 board(CN513) and YBK21 board(CN405). | |||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YBK21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YBK21 board. In a system where a plurality of YBK21 boards are connected, re- place the board, which is connected to the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4766 | M-SAF CONTACT OFF FB DIAG. ER- ROR | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ·YSF22-CN217 ·YPU-CN607, CN610 ·Cable continuity between YSF22 board(CN217) and YPU unit(CN607). | |||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YPU unit failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YPU unit. In a system where a plurality of YPU units are connected, replace the board, which is connected to the unit on which the alarm oc- curred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4767 | M-SAF GENERAL OUT FB DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:GSEDM1 CPU1 2:GSEDM2 CPU2 1:GSEDM1 CPU2 2:GSEDM2 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22 CN219 ∙YSF22-YFC22 ∙Check connectors of the connected outside devices of GSEDM signal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the GSIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4768 | YSF24 GENERAL OUT FB DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:XEDM1 CPU1 2:XEDM2 CPU1 3:XEDM3 CPU1 4:XEDM4 CPU1 5:XEDM5 CPU1 6:XEDM6 CPU1 7:XEDM7 CPU1 8:XEDM8 CPU2 1:XEDM1 CPU2 2:XEDM2 CPU2 3:XEDM3 CPU2 4:XEDM4 CPU2 5:XEDM5 CPU2 6:XEDM6 CPU2 7:XEDM7 CPU2 8:XEDM8 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC24 ∙YSF22-YFC24 cable ∙Check connectors of the connected outside devices of XEDM signal line. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF24 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF24 board. In a system where a plurality of YSF24 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4769 | M-SAF CONTAC- TOR DIAG. ERROR | The meaning of each sub code is as fol- lows: CPU1 1: SFRON1 CPU1 2: SFRON2 CPU1 3: SFRON3 CPU1 4: SFRON4 CPU2 1: SFRON1 CPU2 2: SFRON2 CPU2 3: SFRON3 CPU2 4: SFRON4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN217 ∙YPU-CN607 ∙Cable continuity between YSF22 board and YPU unit. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YPU unit failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YPU unit. In a system where a plurality of YPU units are connected, replace the unit, which is connected to the unit on which the alarm oc- curred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4770 | M-SAF STO DIAG. ERROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:STO1 CPU1 2:STO2 CPU1 3:STO3 CPU1 4:STO4 CPU2 1:STO1 CPU2 2:STO2 CPU2 3:STO3 CPU2 4:STO4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN217 ∙Cable continuity between YSF22 board and EAXA21 board. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
EAXA21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the EAXA21 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4771 | M-SAF GENERAL OUTPUT DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:GSOUT1 CPU1 2:GSOUT2 CPU2 1:GSOUT1 CPU2 2:GSOUT2 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC22 ∙Cable continuity between YSF22 board and YFC22 board. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. In a system where a plurality of YFC22 boards are connected, re- place the board, which is connected to the GSIN signal on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4772 | YSF24 GENERAL OUTPUT DIAG. ER- ROR | The meaning of each SUB-Code is as fol- lows: CPU1 1:XOUT1 CPU1 2:XOUT2 CPU1 3:XOUT3 CPU1 4:XOUT4 CPU1 5:XOUT5 CPU1 6:XOUT6 CPU1 7:XOUT7 CPU1 8:XOUT8 CPU2 1:XOUT1 CPU2 2:XOUT2 CPU2 3:XOUT3 CPU2 4:XOUT4 CPU2 5:XOUT5 CPU2 6:XOUT6 CPU2 7:XOUT7 CPU2 8:XOUT8 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YFC24 ∙Cable continuity between YSF22 board and YFC24 board. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YSF24 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF24 board. In a system where a plurality of YSF24 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4773 | M-SAF CONTACT FB DIAG. ERR (CPU2) | The meaning of each SUB-Code is as fol- lows: 1:KMMB1 2:KMMB2 3:KMMB3 4:KMMB4 | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. ∙YSF22-CN217 ∙YPU-CN607 ∙Cable continuity between YSF22 board and YPU unit. | ||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF21 board. | |||||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. In a system where a plurality of YSF22 boards are connected, re- place the board on which the alarm occurred. | |||||||||||||||||||||||||||||||||||||
YPU unit failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YPU unit. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4776 | M-SAF YSF LOGIC FILE SIGNAL ERR | 0 | Start-up, in reading information from the FlashROM of YSF21 board, YSF21 board has detected an un- defined signal. | Setting error | (1)Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||
YSF21 board failure | (1)Please start in “MAINTENANCE mode”. (2)Display the screen of the “file”-“initialization”, please run the “Machine safety FLASH ROM reset”. (3)Turn the power OFF then back ON. (4)If the alarm occurs again, replace the YSF22 board. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
1 | In the receiving infor- mation on safe logic circuit information, YSF21 board has de- tected an undefined signal. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4777 | TRANSMISSION ERROR(M-SAF FILE) | 1 | Safe logic circuit infor- mation transmission error was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
2 | Timer delay informa- tion transmission er- ror was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer”. When a value is inaccurate, please set up the right value and per- form “writing”. | |||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
3 | M-safety signal alloc information transmis- sion error was detect- ed. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4 | Safety signal board alloc information transmission error was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
253 | M-safety command reception time out was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
254 | Safe logic circuit infor- mation write error was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
255 | Safe logic circuit infor- mation cancel error was detected. | Setting error | (1) Please display the screen of the “safety function” – “safe logic circuit”, and check the value of a “signal”, “logic”, and a “timer.” When a value is inaccurate, please set up the right value and per- form “writing.” | |||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4778 | 24V VOLTAGE ER- ROR(SERVO I/O) | Connection failure | (1) Reset the alarm. (2) If the alarm occurs again, check the connection and inserting state of the following cables and connectors. Check the insertion, connection, Short circuit , ground or 24V power line (DIRECTIN signals) fault of the followings. ∙YFC22-81,82,92,93: +24V2U3 ∙YSF22-CN219 ∙Cable between YSF22 board and the YFC22 board | |||||||||||||||||||||||||||||||||||
YSF22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YSF22 board. | |||||||||||||||||||||||||||||||||||||
YFC22 board failure | (1) Reset the alarm. (2) If the alarm occurs again, replace the YFC22 board. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4780 | F-SAFE AXIS RANGE LIMIT INTF | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check the axis range limit condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to interfere limit range setting. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4781 | AXIS RANGE LIMIT INTF | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check the axis range limit condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to interfere limit range setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4782 | F-SAFE AXIS SPEED MONITOR ERROR | SUB-Code: Signifies the file number, con- trol group, axis and error type in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the axis speed monitor condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to over with limit speed setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4783 | F-SAFE ROBOT RANGE LIMIT INTF | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check robot range limit condition file that is indicated in the SUB- Code is set correctly. ∙Modify the teaching so as not to interfere limit area setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4784 | ROBOT RANGE LIMIT INTF | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check the robot range limit condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to interfere limit area setting. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4785 | F-SAFE SPEED LIMIT ERROR | SUB-Code: Signifies the file number, con- trol group and error type in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the speed limit condition file that is indicated in the SUB- Code is set correctly. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4786 | F-SAFE TEACH SAFETY SPEED ERROR | SUB-Code: Signifies the control group and error type in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the speed limit condition file that is indicated in the SUB- Code is set correctly. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4787 | F-SAFE ROBOT STOP MONITOR ERROR | SUB-Code: Signifies the file number and control group in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the speed limit condition file that is indicated in the SUB- Code is set correctly. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4788 | F-SAFE STATION STOP MONITOR ERR | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check the speed limit condition file that is indicated in the SUB- Code is set correctly. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4789 | F-SAFE TOOL CHANGE MONI- TOR ERR | SUB-Code: Signifies the file number, con- trol group and error type in which the alarm occurred. Error type means: 1:All tool change monitoring condition files is invalid. 2:It detects a mis- match of monitoring tool number and the selection tool file number. 3:Multiple tool change monitoring condition files is enabled. | Setting error | (1) Check the following settings. ∙Check the tool change monitor condition file that is indicated in the SUB-Code is set correctly. ∙Check whether only one tool change monitor condition file en- able. ∙Please coincide the tool file number chosen as the robot of the control group displayed in SUB-Code, and a tool change monitor condition file. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4790 | F-SAFE TOOL ANGL MONITOR ERR | SUB-Code: Signifies the file number and control group in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the tool angle monitor condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to over limit angle setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4791 | F-SAFE AXIS STOP MONITOR ERROR | SUB-Code: Signifies the file number, con- trol group and axis in which the alarm oc- curred. | Setting error | (1) Check the following settings. ∙Check the axis speed monitor condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to over with limit speed setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4792 | TOOL ANGL MONI- TOR ERR | SUB-Code: Signifies the file number and control group in which the alarm occurred. | Setting error | (1) Check the following settings. ∙Check the tool angle monitor condition file that is indicated in the SUB-Code is set correctly. ∙Modify the teaching so as not to over limit angle setting. | ||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4794 | F-SAFE MONITOR EXECUTE TIME OVER | Setting error | (1) Reset the alarm. (2) If the alarm occurs again, reduce the number of robot range limit condition files validated at the same time. | |||||||||||||||||||||||||||||||||||
YSF25 board failure | (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. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4795 | F-SAFE CANNOT OPERATE TEMP DSBL | Setting error | (1)Change the teach mode. (2)Reset the alarm, and then try again. | |||||||||||||||||||||||||||||||||||
YSF25 board failure | (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. | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4796 | F-SAFE DATA CRC UNMATCH | SUB-Code: Signifies the file kind in which the alarm occurred. | Data error | (1) Reset the alarm, and then try again. (2)Check whether the data which it is going to load is surely saved as data of functional safety. | ||||||||||||||||||||||||||||||||||
YSF25 board failure | (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. | |||||||||||||||||||||||||||||||||||||
YIF01 board failure | (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. | |||||||||||||||||||||||||||||||||||||
Other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
4797 | F-SAFE RANGE CONBINATION ERR | Software operation error occurred | Reset the alarm, and then try again. | |||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). | |||||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4798 | F-SAFE SIGNAL SET ERR(SFB) | SUB-Code: Code [X _ _ _ ] indi- cates the abnormal content. 1000: Input/output signal number in con- dition file is abnormal. 4000: Safety fieldbus input signal that is not available is set in con- dition file. 5000: Safety fieldbus output signal that is not available is set in condition file. 6000: File valid condi- tion data is abnormal. Code [ _ Y _ _ ] indi- cates the type of con- dition file abnormality occurs. 100: Axis range limit function | Data error | (1) Check the configuration of condition file abnormality occurs. (2) Reset the alarm, and then try again. | ||||||||||||||||||||||||||||||||||
Alarm No. | Alarm Name | SUB- Code | Meaning | Cause | Remedy | |||||||||||||||||||||||||||||||||
4798 | F-SAFE SIGNAL SET ERR(SFB) | Code [ _ Y _ _ ] indi- cates the type of con- dition file abnormality occurs. 100: Axis range limit function 200: Axis speed mon- itor function 300: Speed limit func- tion 400: Robot range limit function 500: Tool angle moni- tor function 600: Tool change monitor function Code [ _ _ Z Z] indi- cates the number of condition file abnor- mality occurs. | Data error | (1) Check the configuration of condition file abnormality occurs. (2) Reset the alarm, and then try again. | ||||||||||||||||||||||||||||||||||
YSF25 board failure | (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. | |||||||||||||||||||||||||||||||||||||
YSF21 board failure | (1) Turn the power OFF then back ON. (2) If the alarm occurs again, replace the YSF21 board. Save the CMOS.BIN before replace the board to be safe. | |||||||||||||||||||||||||||||||||||||
other | If the alarm occurs again, save the CMOS.BIN in MAINTENANCE mode, and then contact your YASKAWA representative about oc- currence status (operating procedure). |