4xxx alarms

Listing the DX200 error codes in the range from 4000 to 4999. These are minor alarms.

4000

Description:
Sub Code: Tool number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the tool file in maintenance mode, and then load the tool file saved in the external memory device.

4001

Description:
Sub Code: User coordinate number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the user coordinates file in maintenance mode, and then load the user coordinates file saved in the external memory device.

4002

Content:
An error was detected at memory check. The memory for the servo monitor signal file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the servo monitor signal file in maintenance mode, and then load the servo monitor signal file saved in the external memory device.

4003

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the weaving condition file in maintenance mode, and then load the weaving condition file saved in the external memory device.

4004

Content:
An error was detected at memory check. The memory for the home positioning file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the home positioning file in maintenance mode, and then load the home positioning file saved in the external memory device.

4005

Content:
An error was detected at memory check. The memory for the second home position file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the second home positioning file in maintenance mode, and then load the second home positioning file saved in the external memory device.

4006

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the arc welding Power Source condition file in maintenance mode, and then load the arc welding Power Source condition file saved in the external memory device.

4007

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the arc start condition file in maintenance mode, and then load the arc start condition file saved in the external memory device.

4008

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the arc end condition file in maintenance mode, and then load the arc end condition file saved in the external memory device.

4009

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the arc auxiliary condition file in maintenance mode, and then load the arc auxiliary condition file saved in the external memory device.

4010

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the COM-ARC condition file in maintenance mode, and then load the COM-ARC condition file saved in the external memory device.

4011 [230]

Description:
The memory for the gun detail setting file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the gun detail setting file in maintenance mode, and then load the gun detail setting file saved in the external memory device.

4011 [231]

Description:
The memory for the spot management file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the spot management file in maintenance mode, and then load the spot management file saved in the external memory device.

4011 [232]

Description:
The memory for the spot welder I/F file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the spot welder I/F file in maintenance mode, and then load the spot welder I/F file saved in the external memory device.

4011 [233]

Description:
The memory for the manual press condition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the manual press condition file in maintenance mode, and then load the manual press condition file saved in the external memory device.

4011 [240]

Description:
The memory for the wear detection base position file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the wear detection base position file in maintenance mode, and then load the wear detection base position file saved in the external memory device.

4011 [243]

Description:
The memory for the learning control I/O allocation file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the learning control I/O allocation file in maintenance mode, and then load the learning control I/O allocation file saved in the external memory device.

4011 [261]

Description:
The memory for the IOSPDCTRL setup file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the IOSPDCTRL setup file in maintenance mode, and then load the IOSPDCTRL setup file saved in the external memory device.

4012

Description:
Sub Code: Condition file number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the link servo float condition file in maintenance mode, and then load the link servo float condition file saved in the external memory device.

4013

Description:
Sub Code: Condition file number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the linear servo float condition file in maintenance mode, and then load the linear servo float condition file saved in the external memory device.

4014

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the file for calibration between manipulators in maintenance mode, and then load the file for calibration between manipulators saved in the external memory device.

4017

Content:
An error was detected at memory check. The memory for the Power Source user definition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the Power Source user definition file in maintenance mode, and then load the Power Source user definition file saved in the external memory device.

4018

Content:
An error was detected at memory check. The memory for the ladder program file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the ladder program file in maintenance mode, and then load the ladder program file saved in the external memory device.

4019

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the cutting condition file in maintenance mode, and then load the cutting condition file saved in the external memory device.

4020

Content:
An error was detected at memory check. The memory for the work home position file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the work home position file in maintenance mode, and then load the work home position file saved in the external memory device.

4021

Content:
An error was detected at memory check. The memory for the conveyor condition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the conveyor condition file in maintenance mode, and then load the conveyor condition file saved in the external memory device.

4022

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the paint special file in maintenance mode, and then load the paint special file saved in the external memory device.

4023

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the paint condition file in maintenance mode, and then load the paint condition file saved in the external memory device.

4024

Content:
An error was detected at memory check. The memory for the wrist weaving amplitude file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the wrist weaving amplitude file in maintenance mode, and then load the wrist weaving amplitude file saved in the external memory device.

4025

Content:
An error was detected at memory check. The memory for the interrupt job file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the interrupt job file in maintenance mode, and then load the interrupt job file saved in the external memory device.

4028

Content:
An error was detected at memory check. The memory for the sensor monitoring condition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the sensor monitoring condition file in maintenance mode, and then load the sensor monitoring condition file saved in the external memory device.

4030

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the press condition file in maintenance mode, and then load the press condition file saved in the external memory device.

4031

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the gun condition file in maintenance mode, and then load the gun condition file saved in the external memory device.

4032

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the spot welding gun condition file in maintenance mode, and then load the spot welding gun condition file saved in the external memory device.

4033

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the gun pressure file in maintenance mode, and then load the gun pressure file saved in the external memory device.

4034

Content:
An error was detected at memory check. The memory for the anticipation outputs (OT) file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the anticipation output (OT) file in maintenance mode, and then load the anticipation output (OT) file saved in the external memory device.

4035

Content:
An error was detected at memory check. The memory for the anticipation outputs (OG) file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the anticipation output (OG) file in maintenance mode, and then load the anticipation output (OG) file saved in the external memory device.

4036

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the wear amount file in maintenance mode, and then load the wear amount file saved in the external memory device.

4037

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the FULL/SHORT OPEN position setting file in maintenance mode, and then load the FULL/SHORT OPEN position setting file saved in the external memory device.

4038

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the dry-spotting pressure file in maintenance mode, and then load the dry-spotting pressure file saved in the external memory device.

4039

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the form cut file in maintenance mode, and then load the form cut file saved in the external memory device.

4040

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the shock level file in maintenance mode, and then load the shock level file saved in the external memory device.

4041

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the spot I/O allocation file in maintenance mode, and then load the spot I/O allocation file saved in the external memory device.

4042

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the vision condition file in maintenance mode, and then load the vision condition file saved in the external memory device.

4043

Description:
Sub Code: Page number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the vision calibration file in maintenance mode, and then load the vision calibration file saved in the external memory device.

4044

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the welding pulse condition file in maintenance mode, and then load the welding pulse condition file saved in the external memory device.

4045

Content:
An error was detected at memory check. The memory for the welding pulse selection file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the welding pulse selection file in maintenance mode, and then load the welding pulse selection file saved in the external memory device.

4046

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the conveyor calibration file in maintenance mode, and then load the conveyor calibration file saved in the external memory device.

4047

Content:
An error was detected at memory check. The memory for the macro definition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the macro definition file in maintenance mode, and then load the macro definition file saved in the external memory device.

4048

Content:
An error was detected at memory check. The memory for the sealer gun characteristics file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the sealer gun characteristics file in maintenance mode, and then load the sealer gun characteristics file saved in the external memory device.

4049

Content:
An error was detected at memory check. The memory for the painting amount correction file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the painting amount correction file in maintenance mode, and then load the painting amount correction file saved in the external memory device.

4050

Content:
An error was detected at memory check. The memory for the axis motion I/O allocation file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the axis motion I/O allocation file in maintenance mode, and then load the axis motion I/O allocation file saved in the external memory device.

4051

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the gun characteristics auxiliary file in maintenance mode, and then load the gun characteristics auxiliary file saved in the external memory device.

4052

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the tool interference file in maintenance mode, and then load the tool interference file saved in the external memory device.

4053

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the painting system setting file in maintenance mode, and then load the painting system setting file saved in the external memory device.

4054

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the painting device characteristics file in maintenance mode, and then load the painting device characteristics file saved in the external memory device.

4055

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the painting CCV file in maintenance mode, and then load the painting CCV file saved in the external memory device.

4056

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the painting filling file in maintenance mode, and then load the painting filling file saved in the external memory device.

4057

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the EVB gun condition file in maintenance mode, and then load the EVB gun condition file saved in the external memory device.

4058

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the EVB turbine condition file in maintenance mode, and then load the EVB turbine condition file saved in the external memory device.

4059

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the EVB paint condition file in maintenance mode, and then load the EVB paint condition file saved in the external memory device.

4060

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the clearance file in maintenance mode, and then load the clearance file saved in the external memory device.

4061

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the gauging sensor condition file in maintenance mode, and then load the gauging sensor condition file saved in the external memory device.

4062

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the linear scale condition file in maintenance mode, and then load the linear scale condition file saved in the external memory device.

4063

Description:
Sub Code: File number

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the conveyor condition auxiliary file in maintenance mode, and then load the conveyor condition auxiliary file saved in the external memory device.

4064

Content:
An error was detected at memory check. The memory for the weaving synchronizing welding condition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the weaving synchronizing welding condition file in maintenance mode, and then load the weaving synchronizing welding condition file saved in the external memory device.

4065

Content:
An error was detected at memory check. The memory for the I/F panel file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the I/F panel file in maintenance mode, and then load the I/F panel file saved in the external memory device.

4069

Content:
An error was detected at memory check. The memory for the palletizing condition file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the palletize condition file in maintenance mode, and then load the palletize condition file saved in the external memory device.

4070

Content:
An error was detected at memory check. The memory for the laser tracking welding start file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the laser tracking welding start file in maintenance mode, and then load the laser tracking welding start file saved in the external memory device.

4071

Content:
An error was detected at memory check. The memory for the laser tracking welding end file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the laser tracking welding end file in maintenance mode, and then load the laser tracking welding end file saved in the external memory device.

4072

Content:
An error was detected at memory check. The memory for the laser tracking track start file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the laser tracking track start file in maintenance mode, and then load the laser tracking track start file saved in the external memory device.

4073

Content:
An error was detected at memory check. The memory for the laser tracking welding set file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the laser tracking welding set file in maintenance mode, and then load the laser tracking welding set file saved in the external memory device.

4074

Content:
An error was detected at memory check. The memory for the laser tracking track set file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the laser tracking track set file in maintenance mode, and then load the laser tracking track set file saved in the external memory device.

4075

Content:
An error was detected at memory check. The memory for the condition file of corresponding to laser tracking gap is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the condition file of corresponding to laser tracking gap in maintenance mode, and then load the condition file of corresponding to laser tracking gap saved in the external memory device.

4076

Content:
An error was detected at memory check. The memory for the memory play file for laser tracking DC is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the memory play file for laser tracking DC in maintenance mode, and then load the memory play file for laser tracking DC saved in the external memory device.

4080

Content:
An error was detected at memory check. The memory for the mutual wait set file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the mutual wait set file in maintenance mode, and then load the mutual wait set file saved in the external memory device.

4081

Content:
An error was detected at memory check. The memory for the interference predict file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the mutual wait set file in maintenance mode, and then load the interference predict file saved in the external memory device.

4082

Content:
DX200 has detected the possibility of interference between manipulators.

Remedy:
(1) Reset the alarm. (2) Pull the manipulators away each other. (3) If this alarm occurred during test run or playback operation, change the teaching points.

4083

Description:
SubCode 0000_0000_0000_0010:DX200 received an error response from the interference predict server. 0001_0000_0000_0001:No response for the interference check start request was returned from the intererence predict server. 0001_0000_0000_0010:No response for the current position acquisition request was returned from the interference predict server. 0001_0000_0000_0011:DX200 received an error response for the interference check start request from the interference predict server.

Remedy:
(1) Reset the alarm. (2) Check the connection between interference predict server and DX200.

4084

Description:
SubCode 0000_0000_0000_0001:No response was returned from the mutual wait target. 0000_0000_0000_0010:An error occurred in the communication with the mutual wait target during the execution of FN591. 0000_0000_0000_0011:An error occurred in the communication with the mutual wait target during the execution of FN591. 0000_0000_0000_0100:FN591 execution cancel was received even though FN591 execution notice hadn’t been received from the mutual wait target.
0000_0000_0000_0101:FN591 execution cancel error from the mutual wait target was received. 0000_0000_0001_0000:The mutual wait manipulator No. of the FN591 is abnormal. 0000_0000_0010_0000:FN591 was doubly executed. 0000_0000_0011_0000:FN591 execution notice from the mutual wait target was received doubly. 0000_0000_0100_0000:FN591 execution notice error from the mutual wait target was received.

Remedy:
SubCode 0000_0000_0000_0001 0000_0000_0000_0010 0000_0000_0000_0011 0000_0000_0000_0100 0000_0000_0000_0101 0000_0000_0011_0000 0000_0000_0100_0000 (1) Reset the alarm. (2) Check the communication connection with the mutual wait target.

4085

Content:
An error was detected at memory check. The memory for the interference history file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the mutual wait set file in maintenance mode, and then load the interference history file saved in the external memory device.

4086

Content:
An error was detected at memory check. The memory for the ysf set file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the ysf set file in maintenance mode, and then load the ysf set file saved in the external memory device.

4087

Content:
An error was detected at memory check. The memory for the ysf timer file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the ysf timer file in maintenance mode, and then load the ysf timer file saved in the external memory device.

4088

Content:
An error was detected at memory check. The memory for the ysf logic file is damaged.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the ysf logic file in maintenance mode, and then load the ysf logic file saved in the external memory device.

4096

Description:
Purging signal P3-N3 is abnormal. Sub code:Robot which has detected error.

Remedy:
(1) Cycle the power. (2) If the alarm occurs again, check if there is no cable failure (broken line, short circuit) between the pressure unit and the barrier unit in the controller. (3) Check the connection/insertion status of the following connector and also check if there is no failure (such as short circuit) in the cable connected to the following connector.

• YIS21 board-CN661

4098

Description:
Sub Code:Gun No.

Remedy:
Check the setting of pressure.

4099

Content:
An error was detected in the voltage value of the YPS power,

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, turn the power OFF then back ON. (3) If the alarm occurs again, replace the following unit.

• YPS21 unit

4100 [1]

Description:
Sub Code 0001: OT(Robot)

Remedy:
Overrun limit switch is released. Select “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the limit switch. After that, perform avoidance movement by jog operation.

4101

Description:
Sub Code 0001:OT1 0010:OT2 0100:OT3 1000:OT4

Remedy:
Overrun limit switch is released. Select “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the limit switch. After that, perform avoidance movement by jog operation.

4102

Content:
The system parameters are modified. An attempt was made to turn ON the servo power supply after having modified the system parameters.

Remedy:
(1) Reset the alarm. (2) Turn the power OFF then back ON before turning ON the servo power supply.

4103 [1]

Description:
Sub task being executed: Although a job is being executed by instructed sub task, an attempt was made to execute another job by the sub task.

Remedy:
(1) Reset the alarm. (2) Check if other JOB has been already executed in the same task which is used in the PSTART. If same task need to be executed in series, add PWAIT to confirm if the previous task end.

4103 [2]

Description:
Group axis being used: The job operated by another sub task uses the same group axis.

Remedy:
(1) Reset the alarm. (2) Check if the control group of the JOB which is used in the PSTART has been already executed in other task. If the same group need to be executed in series, add PWAIT to confirm if the other task end.

4103 [3]

Description:
Multiple start of same job: The job that was tried to be started was executed by another sub task.

Remedy:
(1) Reset the alarm. (2) Check if the JOB which is used in the PSTART has been already executed in other task. If the same job need to be executed in series, add PWAIT to confirm if the other task end.

4103 [4]

Description:
Unregistered master job: Although the master job was not registered, an attempt was made to execute PSTART SUB (job name omitted).

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The master job of the subtask is registered

4103 [5]

Description:
Synchronization instruction error: When restarted by PSTART, synchronization instruction status of the sub task under interruption was different from the status to restart.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The job to be started
• The execution timing for start command

4103 [6]

Description:
Stopped by an alarm: An attempt was made to start the sub task which is stopped by an alarm.

Remedy:
(1) Check the following settings.

• Alarm occurrence status

4103 [7]

Description:
Synchronization task specification of SYNC instruction omit error

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• Synchronization task specification of SYNC instruction

4103 [8]

Description:
The task is specified by synchronization task of SYNC instruction.

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• Synchronization task specification of SYNC instruction It is not possible to set the same task to the SYNC as the sub task of PSTART instruction.

4103 [9]

Description:
I/O jog being executed

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• I/O jog executing status Complete the I/O jog execution, and then restart.

4103 [10]

Description:
Separate group axis being used

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• I/O jog executing status Complete the I/O jog executing status, and then restart.

4103 [11]

Description:
The servo power supply is OFF.

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• Servo power Turn ON servo power.

4103 [12]

Description:
Twin synchronous task ID error

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• Twin synchronous task specification of SYNC instruction

4103 [16]

Description:
PSTART instruction is the old specification.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The specifications of PSTART instruction Register the PSTART instruction as new specification.

4103 [17]

Description:
PWAIT instruction is the old specification.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The specifications of PWAIT instruction Register the PWAIT instruction as new specification.

4103 [18]

Description:
Sub task to be set PSTART has been already executed.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The subtask is completed by the PWAIT instruction.
• The execution timing for start command

4103 [19]

Description:
An attempt was made to start up the control group where IO speed control is activaed by a job.

Remedy:
(1) Reset the alarm. (2) Check the status of IOSPDCTRL operation setting. The control group of which setting status is “VALID” cannot be started up by a job. (3) Modify the job so as not to start up the control group in which IO speed control is activaed.

4104

Description:
Sub Code1 to 245: Signifies the data transmission error.

Remedy:
* Refer to the instruction manual for Data Transmission Function for details.

4105

Description:
Sub Code1 to 245: Signifies the data transmission error.

Remedy:
* Refer to the instruction manual for Data Transmission Function for details.

4106

Description:
Sub Code1 to 245: Signifies the data transmission error.

Remedy:
* Refer to the instruction manual for Data Transmission Function for details.

4107

Description:
Sub Code: Signifies the axis in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Move the manipulator or station to the zero position by the axis operation and check the home position alignment marks (the arrow).

4109

Description:
0000_0000_0000_0001: Detector circuit error. 0000_0000_0000_0010: Fuse blown (YIO board) 0000_0000_0000_0011: External 24V power supply error.

Remedy:
(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 and connection of the followings.

• CN303 of YIO board
• Fuse (blown) of YIO board
• The communications cable for the I/O module

4110

Content:
This alarm occurs if the shock sensor signal is detected.

Remedy:
Shock sensor is activated. Select “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the sensor. After that, perform avoidance movement by jog operation.

4112 [1]

Description:
Retry over of NAK

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4112 [2]

Description:
Retry over for timeout in timer A

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4112 [3]

Description:
Retry over for mutual response error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4113 [1]

Description:
Reception timeout (timer A)

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4113 [2]

Description:
Reception timeout (timer B)

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4113 [3]

Description:
Heading length is too short.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, send EOT code to release the data link and then check that the sending side data is correctly set. (3) Check that the communication setting is correct.

4113 [4]

Description:
Heading length is too long.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, send EOT code to release the data link and then check that the sending side data is correctly set. (3) Check that the communication setting is correct.

4113 [5]

Description:
The header No. error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, send EOT code to release the data link and then check that the sending side data is correctly set. (3) Check that the communication setting is correct.

4113 [6]

Description:
The text length exceeded 256 characters.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, send EOT code to release the data link and then check that the sending side data is correctly set. (3) Check that the communication setting is correct.

4113 [7]

Description:
Illegal data received

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, send EOT code to release the data link and then check that the sending side data is correctly set. (3) Check that the communication setting is correct.

4114 [1]

Description:
Overrun error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4114 [2]

Description:
Parity error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4114 [3]

Description:
Framing error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4114 [4]

Description:
Transmission timeout (timer A)

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4114 [5]

Description:
Transmission timeout (timer B)

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4115 [1]

Description:
Received EOT while waiting ACK.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4115 [2]

Description:
Received EOT while waiting ENQ.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4115 [3]

Description:
Received EOT before last block reception.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4115 [4]

Description:
Received codes other than EOT after last block reception.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4116 [1]

Description:
Transmission data contents error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4116 [100]

Description:
Trans error or protocol error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4117 [1]

Description:
The EAXA21 / EAXB21 board # 1generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [6]

Description:
The EAXA21 / EAXB21 board # 6generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [7]

Description:
The EAXA21 / EAXB21 board # 7generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4117 [8]

Description:
The EAXA21 / EAXB21 board # 8generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.

4118 [1]

Description:
The EAXA21 / EAXB21 board # 1generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [6]

Description:
The EAXA21 / EAXB21 board # 6 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [7]

Description:
The EAXA21 / EAXB21 board # 7 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4118 [8]

Description:
The EAXA21 / EAXB21 board # 8 generates an alarm.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check fan power line if there is a ground fault or short circuit.

4119

Description:
Sub Code 1 to 4: Signifies the YSF21 board No. in which the alarm occurred

Remedy:
Replace the YPS21 unit.

4121

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) Replace the cooling fan of manipulator. Check the wiring from a manipulator to a servo board.

• Move the manipulator to the safe position in the teach mode.

4122

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) Replace the cooling fan of manipulator. Check the wiring from a manipulator to a servo board.

• Move the manipulator to the safe position in the teach mode.

4123

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
Replace the cooling fan of manipulator. Check the wiring from a manipulator to a servo board.

• Move the manipulator to the safe position in the teach mode.

4124 [1]

Description:
The specified file number is incorrect.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• File No. Specify the correct file number.

4124 [2]

Description:
The specified file set value is incorrect.

Remedy:
(1) Check the following settings.

• File set value Specify the set value.

4124 [3]

Description:
Calibration could not be executed.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The robot coordinate data or the pixel coordinate data used for the calibration
• The user variable number in the calibration file Set the robot coordinate data and the pixel coordinate data used for the calibration to the user variable. Correctly set the user variable number in the calibration file.

4124 [4]

Description:
The communication port for the vision system could not be initialized.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The Parameter for vision communication port. (3) Set the correct parameters for the communication port.

4124 [5]

Description:
Time-out occurred during data transmission.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The communication setting of vision system

4124 [6]

Description:
Time-out occurred during data reception.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The communication setting of vision system

4124 [7]

Description:
The data received from the vision system is incorrect.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The communication setting of vision system
• The detection setting of vision system

4124 [8]

Description:
The pixel coordinates value was not able to be converted into the robot coordinates.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The communication setting of vision system
• Calibration file for use

4124 [9]

Description:
Failed to read or write the position type variable (P variable).

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Usage status of the specified position type variable Don’t use the specified positional type variable at the same time in other jobs.

4124 [10]

Description:
Use memory is lacking and the area could not be obtained.

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

4124 [11]

Description:
The setting value of measurement item (FT) is incorrect.

Remedy:
(1) Reset the alarm. (2) Correct the setting value of a measurement item.

4124 [12]

Description:
The data for the vision execution command is incorrect.

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

4124 [48]

Description:
The number of waiting commands sent by Vision sensor exceeded the limit.

Remedy:
(1) Reset the alarm, and then try again. (2) Check the command sent by Vision sensor (3) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4125 [1]

Description:
File access error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4125 [2]

Description:
File data error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or file data is correctly set.

4125 [3]

Description:
Calibration execution error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4125 [4]

Description:
YCP21 port initialize error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or YCP21 port is correctly set.

4125 [5]

Description:
Time-out occurred during data transmission.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4125 [6]

Description:
Time-out occurred during data reception.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4125 [7]

Description:
Receive data error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the communication setting and communication wiring is correct.

4125 [8]

Description:
Coordinate conversion error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4125 [9]

Description:
Position type variable access error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4125 [10]

Description:
Failed to store the area.

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

4125 [11]

Description:
Measurement item setting error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4125 [12]

Description:
Tag setting error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4125 [48]

Description:
Wait status table FULL

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check the setting of communication or transmission side data is correctly set.

4126 [1]

Description:
System error

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

4126 [2]

Description:
PBOX cannot be edited.

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• I/O status of the edit prohibit signal The edit prohibit signal cannot input.

4126 [3]

Description:
The source job cannot be edited.

Remedy:
(1) Reset the alarm. (2) Check the following setting.

• The prohibit status of source job If the source job is protected from editing, it cannot be edited.

4126 [4]

Description:
The converted job cannot be edited.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The prohibit status of converted job If the converted job is protected from editing, it cannot be edited.

4126 [5]

Description:
The memory area for job area is insufficient.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete unused jobs. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. In that case, delete the unused jobs. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4126 [6]

Description:
The source job is not exist.

Remedy:
(1) Check the following settings.

• Presence of the specified source job The job which does not exist cannot be set to the source job.

4126 [7]

Description:
The memory area for position data of the job is insufficient.

Remedy:
(1) Reset the alarm. (2) when the error occurs again, if there is an unnecessary teaching position, delete it. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. In that case, delete the unused jobs. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4126 [8]

Description:
The job under execution is specified as the conversion job.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Execution status of the source job
• Execution status of the converted job The job under execution is specified for the source / converted job. Execute conversion operation after ending the job execution.

4127

Description:
Sub Code: XY X : Servo board(SV#X) Y : Power-ON unit (TU#Y)

Remedy:
(1) Reset the alarm. (2) Replace the timing belt of the manipulator. Check the connection between manipulator and servo board.

• Move the manipulator to safety place in teach mode.

4128 [1]

Description:
Monitor ON was executed in Monitor ON.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Arc monitor ON status Arc monitor ON cannot be executed during arc monitor ON.

4128 [10]

Description:
Analog CH specification or register specification is not exist.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Analog CH specification
• Register specification Analog CH specification or register specification is required.

4128 [11]

Description:
The number of samplings exceeds the set value.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The number of samplings The number of sampling is too much. Confirm the monitor ON/OFF status.

4129

Description:
Sub Code: Corresponding master-axes and slave-axes are displayed by the bit.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Pulse error of the master-axes and the slave-axes Switch to independent movement mode so that the pulse error of the master-axes and the slave-axes is settled within allowable range.

4130 [1]

Description:
An error occurred when the notification of the APP task re-initialization was processed in the Ethernet function.

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

4130 [2]

Description:
An error occurred when the re-initialization response was received in the Ethernet function.

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

4130 [3]

Description:
The incomplete task of re-initialization was unsuccessfully completed in the Ethernet function.

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

4130 [4]

Description:
An error occurred when the semaphore for re-initialization was received in the Ethernet function.

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

4130 [5]

Description:
An error occurred when the re-initialization mail was sent in the Ethernet function.

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

4130 [6]

Description:
An error occurred in the exclusive process of the storage area control table of the Ethernet function.

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

4130 [7]

Description:
Time-out occurred in the re-initialization response receiving process of the Ethernet function.

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

4130 [8]

Description:
An error occurred in the re-initialization response receiving process of the Ethernet function.

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

4130 [9]

Description:
Receiving data size error occurred in the re-initialization response receiving process of the Ethernet function.

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

4130 [30]

Description:
An error occurred in the Web server task mail receiving process of the Ethernet function.

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

4130 [31]

Description:
An error occurred in the FTP server task mail receiving process of the Ethernet function.

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

4130 [32]

Description:
An error occurred in the FTP client task mail receiving process of the Ethernet function.

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

4130 [40]

Description:
Illegal e-mail data were received in the Web server task of the Ethernet function.

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

4130 [41]

Description:
Illegal e-mail data were received in the FTP server task of the Ethernet function.

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

4130 [42]

Description:
Illegal e-mail data were received in the FTP client task of the Ethernet function.

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

4130 [50]

Description:
An error occurred in the data size written to PCI of the Ethernet function.

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

4130 [51]

Description:
An error occurred when the request to write PCI data was received in the Ethernet function.

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

4130 [52]

Description:
The request of the undefined transmission was received in the Ethernet function.

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

4130 [53]

Description:
An error occurred in the transmission request of the Ethernet function.

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

4130 [54]

Description:
The transmission request without data was received in the Ethernet function.

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

4130 [55]

Description:
The transmission request of illegal data length was received in the Ethernet function.

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

4130 [60]

Description:
Illegal mail data ware received in the DNS task of the Ethernet function.

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

4130 [61]

Description:
Illegal mail data was transmitted in the DNS task of the Ethernet function.

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

4130 [100]

Description:
An error occurred in storing process of memory which is used in the Ethernet function.

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

4130 [101]

Description:
An error occurred in the buffer for request to write PCI getting process of the Ethernet function.

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

4130 [200]

Description:
The socket of the Ethernet function was full and was not able to create a socket.

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

4130 [201]

Description:
An error occurred in the semaphore of socket control table of the Ethernet function.

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

4131 [1]

Description:
An error occurred in the creation of receiving socket during the UDP process of the Ethernet function.

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

4131 [2]

Description:
An error occurred in the creation of transmission socket during the UDP process of the Ethernet function.

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

4131 [3]

Description:
Illegal data were received in the UDP process of the Ethernet function.

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

4131 [4]

Description:
Transmission error occurred in the UDP process of the Ethernet function.

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

4131 [5]

Description:
The SELECT operation was not successfully completed in the UDP process of the Ethernet function.

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

4131 [100]

Description:
The re-initialization notification of illegal data length was received in the UDP process of the Ethernet function.

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

4131 [101]

Description:
The re-initialization notification of illegal data was received in the UDP process of the Ethernet function.

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

4131 [102]

Description:
The PCI write process was not successfully completed in the UDP process of the Ethernet function.

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

4131 [103]

Description:
The transmission request of illegal data length was received in the UDP process of the Ethernet function.

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

4131 [104]

Description:
The transmission request of illegal data was received in the UDP process of the Ethernet function.

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

4132 [1]

Description:
The socket table was not successfully created in the TCP process of the Ethernet function.

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

4132 [2]

Description:
An error occurred in the process of the TCP server initialization of the Ethernet function.

Remedy:
(1) Make sure that there is no communication device with the same IP address in the network. (2) If DHCP is enabled, make sure that the correct IP address is leased from the DHCP server.

4132 [3]

Description:
An error occurred in connection detecting process of TCP server of the Ethernet function.

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

4132 [4]

Description:
An error occurred in the connection detection checking process of TCP server of the Ethernet function.

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

4134 [0]

Content:
Cooling fan setting parameter disabled

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Confirm parameter SVS and S2C for the cooling fan.
• Open the front panel to refer to the parameter list on the back.

4135 [0]

Content:
TOYOPUC is in stopped state.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Use the PCwin, etc. to run the TOYOPUC.

4136 [0]

Description:
The PCI bus state of the TOYOPUC turns to “ER”.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• OFF/ON status of the remote
• OFF/ON status of the power supply Turn OFF and back ON the remote or power supply.

4137 [1]

Description:
Alarm code specification error

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Alarm code Specify the alarm in the range 8000 to 8999.

4137 [2]

Description:
Task specification error

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Task specification Specify the task in the range 0 to 15.

4137 [3]

Description:
Motion mode specification error

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Motion mode specification Set the motion mode to 0 or 1.

4137 [4]

Description:
Alarm num error

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

4138

Content:
An error occurred at SVON instruction execution.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• Short-circuit the external servo ON (EXSVON) of MXT terminal block.

4139

Content:
An error occurred at PRINT instruction execution.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The setting of the PRINT output conversion spec (character string specification) If there is no problem in the setting, delete the corresponding PRINT instruction and register again.

4140 [1]

Description:
DIALOG instruction control error

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The tag setting of DIALOG instruction If no fault is found, delete corresponding DIALOG instruction, and then register again.

4140 [2]

Description:
Messages and buttons are not registered.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The information of DIALOG instruction message and button

4140 [3]

Description:
Buttons are not registered.

Remedy:
(1) Reset the alarm. (2) Check the following settings.

• The information of DIALOG instruction button

4141 [1]

Description:
The error on setting of time difference value occurred in the SNTP process of the Ethernet function.

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

4141 [2]

Description:
The error on setting of time-out value occurred in the SNTP process of the Ethernet function.

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

4141 [3]

Description:
The error on setting of reference interval value occurred in the SNTP process of the Ethernet function.

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

4141 [4]

Description:
The IP address error occurred in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• The IP address of the SNTP server
• The DHCP server operation (If the DHCP is used)
• The network status (If the DHCP is used)

4141 [5]

Description:
Time-out occurred in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• The SNTP server operation
• The network status

4141 [6]

Description:
The server time is not synchronized in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• The SNTP server operation
• The network status

4141 [7]

Description:
The SNTP process of the Ethernet function is not compliant with the version that the server sent.

Remedy:
Use the server compliant with the SNTP version 3.

4141 [8]

Description:
Illegal parameters were found in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• SNTP setting

4141 [9]

Description:
The SNTP process of the Ethernet function was not successfully completed.

Remedy:
(1) Check the following settings.

• SNTP setting

4141 [10]

Description:
The name resolution error occurred in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• The IP address of the SNTP server
• The DHCP server operation *If the DHCP is used
• The network status *If the DHCP is used

4141 [11]

Description:
The error on getting of server address occurred in the SNTP process of the Ethernet function.

Remedy:
(1) Check the following settings.

• The DHCP server operation
• The network status

4141 [12]

Description:
The server setting is incorrect in the SNTP process of the Ethernet function (for future use).

Remedy:
(1) Check the following settings.

• SNTP setting

4144 [0]

Description:
FN591 was executed 11 or more times in a row.

Remedy:
(1) Reset the alarm. (2) Don’t set FN593 11 or more times in a row. Review the teaching.

4145 [0]

Description:
There is invalid relay number in the SYSTEM LADDER.

Remedy:
(1) Save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4145 [1]

Description:
There is invalid relay number in the USER LADDER.

Remedy:
(1) Set the security to management mode and compile the ladder program. If any error occurs, modify the invalid relay number to complete the compiling. Valid range General Input:00010 to 05127 General Output:10010 to 15127 External Input:20010 to 25127 External Output:30010 to 35127 Specific Input:40010 to 41607 Specific Output:50010 to 53007 I/F Panel Input:60010 to 60647 Auxiliary Relay:70010 to 79997 Control Input:80010 to 81287 Pseudo Input:82010 to 82207 Network Input:27010 to 29567 Network output:37010 to 39567

4146 [1]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [2]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [3]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [4]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [5]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [6]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [7]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4146 [8]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4147

Content:
An error occurred during the editing operation of the user coordinates file.

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, initialize the user coordinates file in maintenance mode, and then load the user coordinates file saved in the external memory device.

4148

Description:
Trace level value is abnormal.

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

4149 [0]

Description:
Trace data is abnormal.

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

4149 [1]

Description:
Time stamp value is abnormal.

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

4149 [2]

Description:
Trace level value is abnormal.

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

4149 [3]

Description:
Abnormal variable is specified.

Remedy:
(1) Check the following setting;

• TRACE instruction.

4149 [4]

Description:
Exceeded the maximum trace number.

Remedy:
Execute TRACESAVE or TRACERST.

4150

Description:
The overrun limit switch of the control group that corresponds to the indicated sub code was released.

Remedy:
Overrun limit switch is released. Select “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the limit switch.

4151

Description:
The overrun limit switch of the control group that corresponds to the indicated sub code was released.

Remedy:
Overrun limit switch is released. Select “OVERRUN&SHOCK SENSOR” under sub menu “ROBOT” to reset the limit switch.

4152 [1]

Description:
The EAXA21 / EAXB21 board # 1 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [6]

Description:
The EAXA21 / EAXB21 board # 6 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [7]

Description:
The EAXA21 / EAXB21 board # 7 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4152 [8]

Description:
The EAXA21 / EAXB21 board # 8 generates an alarm.

Remedy:
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension. (2) Check the wiring between manipulator and the machine safety unit (YSF22 board).

4153 [1]

Description:
The EAXA21 / EAXB21 board # 1 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [6]

Description:
The EAXA21 / EAXB21 board # 6 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [7]

Description:
The EAXA21 / EAXB21 board # 7 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4153 [8]

Description:
The EAXA21 / EAXB21 board # 8 generates an alarm.

Remedy:
Refer to the instruction manuals for the cooling unit in use.

4154 [1]

Description:
The EAXA21 / EAXB21 board # 1 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [6]

Description:
The EAXA21 / EAXB21 board # 6 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [7]

Description:
The EAXA21 / EAXB21 board # 7 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4154 [8]

Description:
The EAXA21 / EAXB21 board # 8 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [1]

Description:
The EAXA21 / EAXB21 board # 1 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [2]

Description:
The EAXA21 / EAXB21 board # 2 generates an alarm.

Remedy:
(1) Reset the alarm.

4155 [3]

Description:
The EAXA21 / EAXB21 board # 3 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [4]

Description:
The EAXA21 / EAXB21 board # 4 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [5]

Description:
The EAXA21 / EAXB21 board # 5 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [6]

Description:
The EAXA21 / EAXB21 board # 6 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [7]

Description:
The EAXA21 / EAXB21 board # 7 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4155 [8]

Description:
The EAXA21 / EAXB21 board # 8 generates an alarm.

Remedy:
(1) Reset the alarm. (2) Check the connection and insertion of the cable and connector for the cooling fan.

4156

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) Replace the cooling fan of manipulator. Check the wiring from a manipulator to a servo board.

• Move the manipulator to the safe position in the teach mode.

4157

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) Replace the cooling fan of manipulator. Check the wiring from a manipulator to a servo board.

• Move the manipulator to the safe position in the teach mode.

4160

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
(1) Check the fuse(F1) in the YFL21 board is not disconnected.

4161

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4162

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4163

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4164

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4165

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4166

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4167

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4168

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Replace the power supply

4169

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the following setteing. (1) DC24V output from I/O expansion board is correct. (2) FU1 or FU2 fuse in I/O expansion board is not blown. (3) A short circuit or ground fault has not occurred in IN/OUT line of I/O expansion board.

4170

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Replace the power supply

4171

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Confirm whether YFL22 board is being used. (1) when being unused, confirm following setting.

• A jumper of CN3 of YFL21 board be connected between 1-2. (2) when using, please confirm following setting.
• A jumper of CN3 of YFL21 board be connected between 2-3.

4172

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the status of circuit protector.

4173

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Replace the fuse(F2) in the YFL21 board.

4174

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the set value of the point which corresponds with an instruction manual of the power supply.

4175

Description:
Sub Code: Signifies the YFL21 board number in which the alarm occurred.

Remedy:
Check the set value of the point which corresponds with an instruction manual of the power supply.

4183

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F11) in the YFL22 board.

4184

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F12) in the YFL22 board.

4185

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F13) in the YFL22 board.

4186

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F14) in the YFL22 board.

4187

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F15) in the YFL22 board.

4188

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F16) in the YFL22 board.

4189

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F17) in the YFL22 board.

4190

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F18) in the YFL22 board.

4191

Description:
Sub Code: Signifies the YFL22 board number in which the alarm occurred.

Remedy:
Replace the fuse(F19) in the YFL22 board.

4192 [0]

Description:
TRACE file generation error

Remedy:
(1) Reset the alarm. (2) Check the connection status of the USB in the DX200 controller and its available memory.

4192 [1]

Description:
TRACE file open error

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

4192 [2]

Description:
TRACE file writing error

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

4192 [3]

Description:
TRACE file close error

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

4192 [4]

Description:
TRACE file number error

Remedy:
Delete the trace files generated today from the USB on the DX200 controller.

4192 [5]

Description:
TRACE file index error

Remedy:
Review the name of the trace files generated today in the USB on the DX200 controller.

4195 [1]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [2]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [3]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [4]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [5]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [6]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [7]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4195 [8]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Check the following settings.

• Turn ON the circuit protector.

4196

Description:
Sub Code: 1000 +channel*100 +factor: 0 send complete error 1 receive time out 2 receive break letter 3 framing error 4 parity error 5 over run error 6 revceive length error 7 no STX control letter 8 no ETB control letter 9 BCC error 10 sequence number error 11 sensor detection error

Remedy:
(1) After checking the following two tems, turn the power OFF then back ON.

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

4200

Description:
Sub code 01 to 50: Signifies the internal software error

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, turn the controller power OFF and then ON to check the operation. (3) If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.

4201 [-1]

Description:
An error occurred during the access to a job in parameter specifications.

Remedy:
Reset the alarm, and then try again.

4201 [-2]

Description:
Access time exceeded the limit during the access to a job.

Remedy:
Reset the alarm, and then try again.

4201 [-3]

Description:
The access to a job could not be performed with the specified job name.

Remedy:
Reset the alarm, and then try again.

4201 [-4]

Description:
A job was newly created with the same name of the job already specified in the memory.

Remedy:
Reset the alarm, and then try again.

4201 [-5]

Description:
A job was newly created with the same name of the job already specified in the memory.

Remedy:
Reset the alarm, and then try again.

4201 [-6]

Description:
The allowable job registration area (memory) was exceeded.

Remedy:
(1) Check the following settings.

• Delete unused jobs.

4201 [-7]

Description:
A job that did not exist in the memory was specified.

Remedy:
Reset the alarm, and then try again.

4201 [-8]

Description:
An attempt was made to change the contents for the job prohibited from being edited.

Remedy:
(1) Check the following settings.

• Release the prohibition.

4201 [-9]

Description:
An error occurred during the access to a job in handle value.

Remedy:
Reset the alarm, and then try again.

4201 [-10]

Description:
An error occurred in job data control system.

Remedy:
Reset the alarm, and then try again.

4201 [-11]

Description:
An error occurred in sequence number of the accessed job.

Remedy:
Reset the alarm, and then try again.

4201 [-12]

Description:
An error occurred in step number of the accessed job.

Remedy:
Reset the alarm, and then try again.

4201 [-13]

Description:
A job specified at job search did not exist in the memory.

Remedy:
Reset the alarm, and then try again.

4201 [-14]

Description:
There was an instruction that did not exist in a job because of inconsistency of the system software.

Remedy:
Reset the alarm, and then try again.

4201 [-16]

Description:
Unused handles were lacking when an attempt was made to open a job.

Remedy:
Reset the alarm, and then try again.

4201 [-18]

Description:
The number of instructions added to a job exceeded 9999.

Remedy:
(1) Check the following settings.

• Delete unnecessary instructions and add new instructions again.

4201 [-19]

Description:
The number of steps added to a job exceeded 9999.

Remedy:
(1) Check the following settings. Delete unnecessary steps and add new steps again.

4201 [-22]

Description:
Job information was not able to be expanded.

Remedy:
Reset the alarm, and then try again.

4201 [-23]

Description:
Job information was not able to be acquired.

Remedy:
Reset the alarm, and then try again.

4201 [-24]

Description:
An error occurred in cluster control.

Remedy:
Reset the alarm, and then try again.

4201 [-25]

Description:
Failed to read the cluster information.

Remedy:
Reset the alarm, and then try again.

4201 [-26]

Description:
Heap area could not be obtained.

Remedy:
Reset the alarm, and then try again.

4201 [-27]

Description:
The target for change is the line where editing is prohibited or the comment-out line.

Remedy:
(1) Reset the alarm, and then try again. (2) If the alarm occurs again, deactivate the prohibit setting for the target line or delete the comment-out line.

4201 [-28]

Description:
A false change in the marker job was attempted.

Remedy:
Reset the alarm, and then try again.

4201 [-90]

Description:
The configuration data is damaged.

Remedy:
Reset the alarm, and then try again.

4201 [-91]

Description:
The FAT area is damaged.

Remedy:
Reset the alarm, and then try again.

4201 [-92]

Description:
A job data in the memory was destroyed.

Remedy:
Reset the alarm, and then try again.

4202 [1]

Description:
An error occurred in parameter specifications for the access to a job .

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [2]

Description:
Access time exceeded the limit during the access to a job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [3]

Description:
Unapproved characters are used for a job name.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [4]

Description:
A job was newly created with the same name of the job already specified in the memory.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [5]

Description:
A job was newly created with the same name of the job already specified in the memory.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [6]

Description:
The allowable job registration area (memory) was exceeded.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete unused jobs. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. In that case, delete the unused jobs. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [7]

Description:
A job that did not exist in the memory was specified.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [8]

Description:
An attempt was made to change the contents for the job prohibited from being edited.

Remedy:
(1) Check the following settings.

• Setting of EDIT LOCK in JOB header screen If the job is protected from editing, release the prohibition.

4202 [9]

Description:
An attempt was made to change the contents for the job prohibited from being edited.

Remedy:
(1) Check the following settings.

• Setting of EDIT LOCK in JOB header screen If the job is protected from editing, release the prohibition.

4202 [10]

Description:
An error occurred in job data control system.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [11]

Description:
An error occurred in sequence number of the accessed job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [12]

Description:
An error occurred in step number of the accessed job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [13]

Description:
A job specified at job search did not exist in the memory.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [14]

Description:
There was an instruction that did not exist in a job because of inconsistency of the system software.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [16]

Description:
Unused handles were lacking when an attempt was made to open a job.

Remedy:
(1) Check the following settings.

• The number of call job stacks Set the job configuration that decreases the number of call job stacks.

4202 [18]

Description:
The number of instructions added to a job exceeded 9999.

Remedy:
(1) Check the following settings.

• The number of steps in job Delete unnecessary instructions in job and add new instructions.

4202 [19]

Description:
The number of steps added to a job exceeded 9999.

Remedy:
(1) Check the following settings.

• The number of steps in job Delete unnecessary steps in job and add new steps.

4202 [20]

Description:
A job was newly created with the same name of the undefined job already specified in the memory.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [22]

Description:
Failed to expand job information during the access to a job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [23]

Description:
The accessed job was not opened.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [24]

Description:
An error occurred in the cluster control process of the accessed job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [25]

Description:
An error occurred when reading the cluster information of the accessed job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [26]

Description:
Failed to acquire the necessary memory area during the access to a job.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [27]

Description:
An attempt was made to change the contents for the line prohibited from being edited or the commented-out line.

Remedy:
(1) Reset the alarm. (2) Cancel the LINE EDIT LOCK/COMMENT OUT settings of target lines in JOB CONTENTS screen.

4202 [28]

Description:
A false change in the marker job was attempted.

Remedy:
(1) Reset the alarm. (2) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (3) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [90]

Description:
The configuration information for job data control is damaged.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [91]

Description:
The FAT information for job data is damaged.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [92]

Description:
A job data was destroyed.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4202 [99]

Description:
A job data in the memory was destroyed.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4203 [-1]

Description:
The memory area for position data is lacking at the initialization of the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-2]

Description:
The number of axes for all the control groups is zero at the initialization of the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-3]

Description:
The number of axes for position data is zero.

Remedy:
Reset the alarm, and then try again.

4203 [-4]

Description:
The number of stored position data exceeded the maximum stored data at the initialization of the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-5]

Description:
The memory size of the position data exceeded the maximum memory size at the initialization of the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-6]

Description:
Unused position data file is destroyed.

Remedy:
Reset the alarm, and then try again.

4203 [-7]

Description:
Unused position data file does not exist.

Remedy:
Reset the alarm, and then try again.

4203 [-8]

Description:
Position data file is destroyed.

Remedy:
Reset the alarm, and then try again.

4203 [-9]

Description:
Position data control information is destroyed.

Remedy:
Reset the alarm, and then try again.

4203 [-10]

Description:
An error occurred in specified position data number.

Remedy:
Reset the alarm, and then try again.

4203 [-11]

Description:
Position data is not registered.

Remedy:
Reset the alarm, and then try again.

4203 [-12]

Description:
An attempt was made to access the undefined position data.

Remedy:
Reset the alarm, and then try again.

4203 [-13]

Description:
An attempt was made to access the position data for the undefined control group.

Remedy:
Reset the alarm, and then try again.

4203 [-14]

Description:
Position data control is not initialized.

Remedy:
Reset the alarm, and then try again.

4203 [-15]

Description:
The number of axes for the control groups exceeded the limit.

Remedy:
Reset the alarm, and then try again.

4203 [-16]

Description:
An error occurred in exclusive control during the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-17]

Description:
An error occurred in exceptional control during the position data control process.

Remedy:
Reset the alarm, and then try again.

4203 [-20]

Description:
Inconsistency of data.

Remedy:
Reset the alarm, and then try again.

4204 [1]

Description:
The number of axes for all the control groups is zero at the initialization of the position data control process

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [2]

Description:
The number of axes for all the control groups is zero at the initialization of the position data control process

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [3]

Description:
The number of axes for position data is zero.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [4]

Description:
The number of stored position data exceeded the maximum stored data at the initialization of the position data control process.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [5]

Description:
The memory size of the position data exceeded the maximum memory size at the initialization of the position data control process.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [6]

Description:
Unused position data file is destroyed.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [7]

Description:
Unused position data file does not exist.

Remedy:
(1) Check the following settings.

• The number of steps in job (position data) Delete unnecessary position data in job and add new position data.

4204 [8]

Description:
Position data file is destroyed.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [9]

Description:
Position data control information is destroyed.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [10]

Description:
An error occurred in specified position data number.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [11]

Description:
Position data is not registered.

Remedy:
(1) Check the following settings.

• Teaching of alarm occurred point Teaching the point where alarm occurred.

4204 [12]

Description:
An attempt was made to access the undefined position data.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [13]

Description:
An attempt was made to access the position data for the undefined control group.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [14]

Description:
Position data control is not initialized.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [15]

Description:
The number of axes for the control groups exceeded the limit.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [16]

Description:
An error occurred in exclusive control during the position data control process.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [17]

Description:
An error occurred in exceptional control during the position data control process.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4204 [20]

Description:
Undefined position exists.

Remedy:
(1) Reset the alarm. (2) If the error occurs again, delete the job where the alarm occurred. (3) If the error occurs again after the previous measures were executed, initialize the job file in the maintenance mode, and then load the saved job file. (4) If the error occurs again though the previous measures were executed, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4205 [1]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [2]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [3]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [4]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [5]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [6]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [7]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4205 [8]

Description:
Sub Code 1to 8: Signifies the EAXA/EAXB board No. in which the alarm occurred

Remedy:
(1) Reset the alarm. (2) If the alarm occurs again, check circuit protector for motor cooling fans in the controller is doing trip. (3) Check motor cooling fan power line if there is a ground fault or short circuit.

4206

Description:
Sub Code 1 to 4: Signifies the internal software error during data transmission.

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

4207 [1]

Description:
An interrupt undefined in the main command from the system control section occurred.

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

4207 [2]

Description:
An interrupt undefined in the sub command from the system control section occurred.

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

4207 [3]

Description:
The interrupt command that was sent previously from the system control section is being processed.

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

4207 [4]

Description:
An error was detected in the interrupt command data from the system control section.

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

4207 [5]

Description:
An undefined command was detected in the sub segment task of MOTION section.

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

4207 [6]

Description:
An undefined command was detected in the servo-related processing of MOTION section.

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

4207 [7]

Description:
An undefined command was detected in the offline processing task of MOTION section.

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

4207 [8]

Description:
An undefined command was detected in the utility task of MOTION section.

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

4207 [10]

Description:
Task Token is not generated.

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

4207 [11]

Description:
Mail-box Token is not generated.

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

4207 [12]

Description:
Semaphore Token is not generated.

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

4207 [14]

Description:
RMS receiving data error

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

4207 [15]

Description:
RMS sending data error

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

4207 [16]

Description:
RMS receiving unit error

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

4207 [18]

Description:
Task generation error

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

4207 [19]

Description:
Mail-box generation error

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

4207 [20]

Description:
Semaphore generation error

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

4207 [22]

Description:
TCB area overflow

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

4207 [23]

Description:
Stack area overflow

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

4207 [24]

Description:
Mail-box area overflow

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

4207 [25]

Description:
Semaphore area overflow

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

4207 [30]

Description:
Interrupt main command error

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

4207 [33]

Description:
Incorrect control group designation

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

4207 [34]

Description:
Offline bank semaphore reception error

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

4207 [35]

Description:
m_gen_area semaphore reception error

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

4207 [36]

Description:
Offline HA processing timeout

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

4207 [37]

Description:
DM_BANK flag error (DM_BANK conversion processing)

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

4207 [38]

Description:
S -> M offline processing command type error

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

4207 [39]

Description:
Function specification error in the data transmission to the sensor board

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

4207 [40]

Description:
Error in designation of application in the request of general-purpose data preset for each application.

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

4207 [45]

Description:
Mail-box of sequence task is not ready.

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

4207 [46]

Description:
Control-group usage undefined

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

4207 [47]

Description:
Segment task polling command error

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

4207 [48]

Description:
Physical axis number error

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

4207 [49]

Description:
The control group impossible to release the brake

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

4207 [50]

Description:
Sub-segment request FULL

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

4207 [51]

Description:
Sub-segment process timeout

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

4207 [52]

Description:
Data latch request FULL

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

4207 [53]

Description:
Data latch process timeout

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

4207 [54]

Description:
AXIS command request FULL

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

4207 [55]

Description:
AXIS command process timeout

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

4207 [56]

Description:
Positioning monitor request FULL

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

4207 [57]

Description:
Positioning monitor process timeout

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

4207 [58]

Description:
Failed AXIS servo OFF command request during category1 emergency stop

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

4207 [59]

Description:
AXIS servo OFF command execution system not set during category1 emergency stop

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

4207 [61]

Description:
Conversion primary expression for Power Source command <-> EW command not prepared

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

4207 [62]

Description:
Duplicated request error during master control-group tracking

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

4207 [63]

Description:
GVM shared resource semaphore error

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

4207 [64]

Description:
Job queue DEQUE error

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

4207 [65]

Description:
Conversion primary expression for painting device command <-> EW command not prepared

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

4207 [66]

Description:
Execution system decision table not set

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

4207 [67]

Description:
Unknown mode data (Without TEACH/PLAY mode data)

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

4207 [68]

Description:
Shift-value output timeout of the general-purpose sensor

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

4207 [69]

Description:
Interrupt main status set

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

4207 [71]

Description:
System number error at the master side in twin synchronous system

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

4207 [72]

Description:
No data link added to the command

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

4207 [73]

Description:
Setting status error of the user coordinates file

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

4207 [75]

Description:
Previous path data reference error

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

4207 [76]

Description:
Target position preparation error in arc-retry shift motion mode

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

4207 [79]

Description:
Inner track zone status error

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

4207 [80]

Description:
Instruction queue and instruction system data area overflow

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

4207 [81]

Description:
Offline answer bank flag error

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

4207 [82]

Description:
Path and trace queue ENQUE BANK error

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

4207 [83]

Description:
Pending and block end request FULL

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

4207 [84]

Description:
Base axis file type error

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

4207 [85]

Description:
Output buffer SYSCON for automatic test data in use

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

4207 [86]

Description:
Conversion completion status for AXIS section feedback latch data not established

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

4207 [88]

Description:
File C1 through C3 for calibration between manipulators not set

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

4207 [89]

Description:
File C1 through C3 for conveyor calibration not set

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

4207 [90]

Description:
HA function error (conv_pos_data())

Remedy:
(1) Check the following settings.

• Correct the job so that the target position data is within the motion range. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4207 [91]

Description:
HA function error (conv_shift_data())

Remedy:
(1) Check the following settings.

• Correct the job so that the target position data is within the motion range. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4207 [94]

Description:
HA function error (conv_pulse_to_angle())

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

4207 [95]

Description:
HA function error (pr_atinf_pos_make())

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

4207 [97]

Description:
HA function error (get_gun_ctrl_ori_angle())

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

4207 [98]

Description:
HA function error (make_conv_frm_data())

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

4207 [99]

Description:
HA function error (calc_dist_pos())

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

4207 [100]

Description:
Control-group axis configuration information parameter error

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

4207 [101]

Description:
Error in the parameter for the table for physical axes

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

4207 [102]

Description:
Error in the parameter for the table for physical TU

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

4207 [103]

Description:
Excessive number of control group axes in use

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

4207 [104]

Description:
JOG and PLAY maximum speed setting parameter error

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

4207 [105]

Description:
Reduction ratio setting parameter error

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

4207 [106]

Description:
feedback PPR setting parameter error

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

4207 [121]

Description:
Job argument stack overflow

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

4207 [122]

Description:
Job argument stack underflow

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

4207 [123]

Description:
Designation error of the fetched feedback pulse area at preparation of current value

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

4207 [128]

Description:
Timeout for waiting permission to modify the number of averaging times

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

4207 [129]

Description:
Object undefined for CLEAR instruction

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

4207 [130]

Description:
No space in RT_BANK setting area for correction-amount data

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

4207 [131]

Description:
Queue operation error for variable write-in history at prereading (at ENQUE)

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

4207 [132]

Description:
Queue operation error for variable write-in history at prereading (at DEQUE)

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

4207 [133]

Description:
Queue operation error for variable write-in history at prereading (undefined operation)

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

4207 [134]

Description:
Queue operation error for variable write-in history at prereading (data length too long)

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

4207 [135]

Description:
Queue operation error for score-board setting history (at ENQUE)

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

4207 [136]

Description:
Queue operation error for score-board setting history (at DEQUE)

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

4207 [137]

Description:
Queue operation error for score-board setting history (undefined operation)

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

4207 [138]

Description:
Queue operation error for score-board setting history (data length too long)

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

4207 [139]

Description:
Queue operation error for instruction execution (at ENQUE)

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

4207 [140]

Description:
Queue operation error for instruction execution (at DEQUE)

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

4207 [141]

Description:
Queue operation error for instruction execution (undefined operation)

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

4207 [142]

Description:
Queue operation error for instruction execution (data length too long)

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

4207 [143]

Description:
Queue operation error for WORK ID conveyor (at ENQUE)

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

4207 [144]

Description:
Queue operation error for WORK ID conveyor (at DEQUE)

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

4207 [145]

Description:
Queue operation error for WORK ID conveyor (undefined operation)

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

4207 [146]

Description:
Queue operation error for WORK ID conveyor (data length too long)

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

4207 [147]

Description:
Queue operation error for WORK IN/OUT checking conveyor (at ENQUE)

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

4207 [148]

Description:
Queue operation error for WORK IN/OUT checking conveyor (at DEQUE)

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

4207 [149]

Description:
Queue operation error for WORK IN/OUT checking conveyor (undefined operation)

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

4207 [150]

Description:
Queue operation error for WORK IN/OUT checking conveyor (data length too long)

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

4207 [151]

Description:
Queue operation error for waiting for semaphore for LOCK instruction (at ENQUE)

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

4207 [152]

Description:
Queue operation error for waiting for semaphore for LOCK instruction (at DEQUE)

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

4207 [153]

Description:
Queue operation error for waiting for semaphore for LOCK instruction (undefined operation)

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

4207 [154]

Description:
Queue operation error for waiting for semaphore for LOCK instruction (data length too long)

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

4207 [161]

Description:
Functional safety command request is full.

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

4207 [162]

Description:
Functional safety command request is latency over.

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

4207 [221]

Description:
Transfer data overflow in offline data bank

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

4207 [222]

Description:
Impossible to execute system exclusive for system job

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

4207 [223]

Description:
Event queue number range exceeded

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

4207 [224]

Description:
No motor-gun control group for ESRCH instruction

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

4207 [225]

Description:
The number of WORK ID data and the MAX. WORK FIND COUNT unmatched (MOTION NOT EQUAL CV)

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

4207 [226]

Description:
The number of WORK IN/OUT data and the MAX. WORK FIND COUNT unmatched (MOTION NOT EQUAL CV)

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

4207 [227]

Description:
Excessive number of scheduling for execution of instructions

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

4207 [228]

Description:
Instruction execution scheduling impossible

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

4207 [229]

Description:
Illegal 1st-line move instruction at execution of +SMOV instruction

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

4207 [230]

Description:
Impossible to execute the slave circular interpolation and the master circular interpolation at the same time

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

4207 [231]

Description:
Impossible to execute the slave spline interpolation and the master spline interpolation at the same time

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

4207 [232]

Description:
Illegal index value for a +MOVx instruction

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

4207 [233]

Description:
No xth-line move instruction exists where the master control group belongs.

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

4207 [234]

Description:
Marking error for WORK ID conveyor queue (empty queue)

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

4207 [235]

Description:
Marking error for WORK IN/OUT conveyor queue (empty queue)

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

4207 [236]

Description:
Data error 1 at restarting after an emergency stop (actual status and the data status unmatched)

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

4207 [237]

Description:
Data error 2 at restarting after an emergency stop (actual status and the data status unmatched)

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

4207 [238]

Description:
Data error 3 at restarting after an emergency stop (actual status and the data status unmatched)

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

4207 [239]

Description:
Timeout for receiving segment data output request

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

4207 [240]

Description:
The number which designates the setting area of correction amount in RT_BANK exceeded the limit value.

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

4207 [241]

Description:
Task error of the function calling source (cv_sync_intr ( ))

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

4207 [242]

Description:
No control group for motor gun for clearance move instruction

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

4207 [243]

Description:
Motor gun condition file number error (including gun pressure file)

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

4207 [244]

Description:
GETTOOLW manipulator designation error

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

4207 [245]

Description:
Overflow of entry number for instruction execution

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

4207 [246]

Description:
Data latch processing (function number overflow)

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

4207 [247]

Description:
Data latch processing (real-time status number overflow)

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

4207 [248]

Description:
Failed to set a timer unit. (No allocation space for timer unit setting)

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

4207 [249]

Description:
Segment data missing (seg_t_req was not received in time.)

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

4207 [250]

Description:
GETS instruction internal error

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

4207 [251]

Description:
SETFILE undefined file

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

4207 [252]

Description:
GETFILE undefined file

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

4207 [253]

Description:
The parameter was destroyed when a GETPRM instruction was executed.

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

4207 [254]

Description:
Null pointer assignment detected

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

4207 [255]

Description:
Function or other processing parameter error

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

4207 [260]

Description:
Arithmetic answer is not set at prereading (ADV_HA_ANS.flag == OFF)

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

4207 [261]

Description:
Heap area obtainment failure (A_BANK)

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

4207 [262]

Description:
Heap area obtainment failure (C_BANK)

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

4207 [263]

Description:
Heap area obtainment failure (Instruction queue)

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

4207 [264]

Description:
Heap area obtainment failure (Path/trace queue)

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

4207 [265]

Description:
Heap area obtainment failure (IF-Express descriptor)

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

4207 [279]

Description:
Specified MSS system instance is not generated.

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

4207 [280]

Description:
API error(HDAS_get_alias_name())

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

4207 [284]

Description:
GA generation number is over the limit.

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

4207 [285]

Description:
GA gene number is over the limit.

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

4207 [286]

Description:
GA initial generation number setting error

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

4207 [287]

Description:
GA control group error

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

4207 [288]

Description:
Learning control analysis error

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

4207 [290]

Description:
HA function error (get_svspot_ntch_data())

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

4207 [291]

Description:
Paint instruction internal error

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

4207 [292]

Description:
Paint recover control error (Paint Gun parameter error)

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

4207 [293]

Description:
Paint recover control error

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

4207 [294]

Description:
Job completion time over

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

4207 [295]

Description:
Servo simulator averaging time change error

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

4207 [310]

Description:
Synchronized queue operation error for WORK ID conveyor (at ENQUE)

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

4207 [311]

Description:
Synchronized queue operation error for WORK ID conveyor (at DEQUE)

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

4207 [312]

Description:
Synchronized queue operation error for WORK ID conveyor (undefined operation)

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

4207 [313]

Description:
Synchronized queue operation error for WORK ID conveyor (data length too long)

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

4207 [314]

Description:
Synchronized queue operation error for WORK IN/OUT checking conveyor (at ENQUE)

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

4207 [315]

Description:
Synchronized queue operation error for WORK IN/OUT checking conveyor (at DEQUE)

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

4207 [316]

Description:
Synchronized queue operation error for WORK IN/OUT checking conveyor (undefined operation)

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

4207 [317]

Description:
Synchronized queue operation error for WORK IN/OUT checking conveyor (data length too long)

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

4207 [318]

Description:
Synchronized queue operation error for WORK ID conveyor or WORK IN/OUT conveyor (at DEQUE)

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

4207 [319]

Description:
Synchronized queue empty error for WORK ID conveyor (at execution of CVQUE)

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

4207 [320]

Description:
Synchronized queue empty error for WORK IN/OUT conveyor (at execution of CVQUE)

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

4207 [330]

Description:
P-PLC suspend err

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

4207 [331]

Description:
P-PLC suspend err

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

4207 [332]

Description:
P-PLC suspend seq err

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

4207 [333]

Description:
P-PLC suspend seq no err

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

4207 [334]

Description:
P-PLC suspend seq no err

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

4207 [340]

Description:
PSTRIG suspend err

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

4207 [341]

Description:
PSTRIG suspend err

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

4207 [342]

Description:
PSTRIG suspend seq err

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

4207 [371]

Description:
ACK response error

Remedy:
(1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).

4207 [372]

Description:
Polling command release error

Remedy:
(1) Reset the alarm, and then try again. (2) If the alarm occurs again, save the CMOS.BIN, and then contact your YASKAWA representative about occurrence status (operating procedure).

4207 [500]

Description:
SL undefined interrupt command (main command)

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

4207 [501]

Description:
SL undefined interrupt command (sub command)

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

4207 [502]

Description:
Previous SL interrupt command processing

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

4207 [503]

Description:
SL interrupt command data error

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

4207 [999]

Description:
Arithmetic section error (segment data all zero timeout)

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

4207 [1000]

Description:
System clock (RTC) setting error

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

4207 [1001]

Description:
System task priority arrangement error

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

4207 [1002]

Description:
VxWorks primitive error (msgQCreate)

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

4207 [1003]

Description:
VxWorks primitive error (msgQSend)

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

4207 [1005]

Description:
VxWorks primitive error (semBCreate)

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

4207 [1007]

Description:
VxWorks primitive error (semTake)

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

4207 [1008]

Description:
VxWorks primitive error (msgQSend) Message queue is full.

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

4207 [1100]

Description:
Failed system job environment configuration

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

4207 [2000]

Description:
Failed system job environment configuration

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

4208 [1]

Description:
Prereading task is not completed.

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

4208 [5]

Description:
The averaging buffer in the arithmetic section is destroyed.

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

4208 [6]

Description:
No previous bank exists.

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

4208 [7]

Description:
The answer bank flag is ON.

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

4208 [8]

Description:
An error occurred in preparation of current position.

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

4208 [9]

Description:
Mails could not correctly be received in the current task.

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

4208 [10]

Description:
Spline-curve path designation error

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

4208 [11]

Description:
The previous bank’s prereading conversion could not correctly be completed.

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

4208 [12]

Description:
A manipulator designation error occurred at JOG operation using the external reference point.

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

4208 [13]

Description:
Designation error of cubic interference coordinates

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

4208 [14]

Description:
Path control position data error of prereading bank

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

4208 [16]

Description:
Station/base axis motion command error

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

4208 [18]

Description:
User coordinates number error

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

4208 [19]

Description:
Processing error in re-preparation of segment control data

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

4208 [20]

Description:
Prereading task not completed at master in twin synchronous system

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

4208 [23]

Description:
Dynamic model arithmetic error

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

4208 [24]

Description:
Speed limit control error (excessive moment of gravity)

Remedy:
(1) Check the following settings.

• The allowable breaking torque was exceeded only by the gravity moment. Set the gravity value of the tool within payload of the manipulator.
• Teach the manipulator orientation that does not become the overload for each-axes of the manipulator. (2) If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).

4208 [25]

Description:
Square root of a negative number

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

4208 [26]

Description:
The system number is not set at master in twin synchronous system.

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

4208 [29]

Description:
FORMCUT internal control error

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

4208 [30]

Description:
Arm interference check error (radius data referencing mistake)

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

4208 [31]

Description:
Arm interference check error (miscalculation using direct kinematics)

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

4208 [32]

Description:
Arm interference check error (L-axis expansion flag setting error)

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

4208 [33]

Description:
Arm interference check error (check-point re-setting error)

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

4208 [34]

Description:
Impossible to edit the averaging buffer (zero division)

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

4208 [35]

Description:
No master-group is designated at preparation of master-tool user coordinates.

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

4208 [37]

Description:
Gauging function error (command designation error)

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

4208 [38]

Description:
A coordinated motion was attempted using the Following function.

Remedy:
(1) Check the following settings.

• Change the setting so that only the manipulator moves. *The coordinated motion cannot be performed by the Following function.

4208 [39]

Description:
Zero or a negative value is set for the bending speed of the Following function.

Remedy:
(1) Check the following settings.

• Set a positive value for the bending speed.

4208 [40]

Description:
Zero or a negative value is set for the bending stroke of the Following function.

Remedy:
(1) Check the following settings.

• Set a positive value for the bending stroke.

4208 [41]

Description:
Pulse linked JOG function error

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

4208 [42]

Description:
Special JOG operation error

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

4208 [44]

Description:
Segment overless: Segment excessive error

Remedy:
(1) Check the following settings.

• The teaching position cannot hold down the speed by the segment overless function. Reduce the teaching speed of the job.

4208 [45]

Description:
Segment overless: Path calculation repeat error

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

4208 [47]

Description:
Play path control: initialization error

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

4208 [48]

Description:
Play path control: continue process error

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

4208 [49]

Description:
Play path control: Step continuous initialization error

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

4208 [50]

Description:
Play path control: step continuous motion execution process error

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

4208 [54]

Description:
Approximation model internal control error

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

4208 [55]

Description:
Pair coordinate system position calculation function error

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

4208 [56]

Description:
OPT higher acceleration and deceleration control is not allowed when Function acceleration and deceleration control is enabled.

Remedy:
(1) Check the following settings.

• OPT higher acceleration and deceleration control is used.
• Don’t use the OPT higher acceleration and deceleration control.

4208 [57]

Description:
Arithmetic error occurred when calculating the acceleration and deceleration time (Function acceleration and deceleration control)

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

4208 [58]

Description:
Arithmetic error occurred when recalculating the acceleration and deceleration time (Function acceleration and deceleration control)

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

4208 [59]

Description:
Arithmetic error occurred when calculating PL control (Function acceleration and deceleration control)

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

4208 [60]

Description:
Arithmetic error occurred when calculating Function acceleration and deceleration dry run.

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

4208 [61]

Description:
Arithmetic error occurred when calculating current path of continuous motion stop operation

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

4208 [62]

Description:
Arithmetic error occurred when calculating next path of continuous motion stop operation

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

4208 [63]

Description:
Arithmetic error occurred when calculating acceleration time when continuous motion in the prereading processing

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

4208 [64]