YASKAWA MOTOMAN FS100 Maintenance Manual
Anúncio
Anúncio
FS100
MAINTENANCE MANUAL
Upon receipt of the product and prior to initial operation, read these instructions thoroughly, and retain for future reference.
MOTOMAN INSTRUCTIONS
MOTOMAN-
INSTRUCTIONS
FS100 INSTRUCTIONS
FS100 OPERATOR’S MANUAL
FS100 MAINTENANCE MANUAL
YASKAWA ELECTRIC CORPORATION
MANUAL NO. RE-CHO-A111 5
FS100
MANDATORY
• This manual explains maintenance procedures of the FS100 system. Read this manual carefully and be sure to understand its contents before handling the FS100.
• General items related to safety are listed in Chapter 1: Safety of the
FS100 INSTRUCTIONS. To ensure correct and safe operation, carefully read the FS100 Instructions before reading this manual.
CAUTION
• Some drawings in this manual are shown with the protective covers or shields removed for clarity. Be sure all covers and shields are replaced before operating this product.
• The drawings and photos in this manual are representative examples and differences may exist between them and the delivered product.
• YASKAWA may modify this model without notice when necessary due to product improvements, modifications, or changes in specifications. If such modification is made, the manual number will also be revised.
• If your copy of the manual is damaged or lost, contact a YASKAWA representative to order a new copy. The representatives are listed on the back cover. Be sure to tell the representative the manual number listed on the front cover.
• YASKAWA is not responsible for incidents arising from unauthorized modification of its products. Unauthorized modification voids your product’s warranty.
ii
FS100
Notes for Safe Operation
Read this manual carefully before installation, operation, maintenance, or inspection of the FS100 .
In this manual, the Notes for Safe Operation are classified as “DANGER”,
“WARNING”, “CAUTION”, “MANDATORY”, or “PROHIBITED”.
DANGER
WARNING
CAUTION
Indicates an imminent hazardous situation which, if not avoided, could result in death or serious injury to personnel.
Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury to personnel.
Indicates a potentially hazardous situation which, if not avoided, could result in minor or moderate injury to personnel and damage to equipment.
It may also be used to alert against unsafe practices.
MANDATORY
Always be sure to follow explicitly the items listed under this heading.
PROHIBITED
Must never be performed.
Even items described as “CAUTION” may result in a serious accident in some situations.
At any rate, be sure to follow these important items.
NOTE
To ensure safe and efficient operation at all times, be sure to follow all instructions, even if not designated as “DAN-
GER”, “WARNING” and “CAUTION” . iii
FS100
WARNING
• Before operating the manipulator, check that servo power is turned
OFF when the emergency stop button on the programming pendant is pressed.
When the servo power is turned OFF, the SERVO ON LED on the programing pendant is turned OFF.
Injury or damage to machinery may result if the emergency stop circuit cannot stop the manipulator during an emergency. The manipulator should not be used if the emergency stop button does not function.
Fig. : Emergency Stop Button
• In the case of not using the programming pendant, be sure to supply the emergency stop button on the equipment. Then before operating the manipulator, check to be sure that the servo power is turned OFF by pressing the emergency stop button.
Connect the external emergency stop button to the 5-6 pin and 16-
17 pin of the robot system signal connector (CN2).
• Upon shipment of the FS100, this signal is connected by a jumper cable in the dummy connector. To use the signal, make sure to supply a new connector, and then input it.
If the signal is input with the jumper cable connected, it does not function, which may result in personal injury or equipment damage.
• Once the emergency stop button is released, clear the cell of all items which could interfere with the operation of the manipulator.
Then turn the servo power ON.
Injury may result from unintentional or unexpected manipulator motion.
Fig. : Release of Emergency Stop Button
TURN
• Observe the following precautions when performing teaching operations within the manipulator’s operating range:
– Be sure to use a lockout device to the safeguarding when going inside. Also, display the sign that the operation is being performed inside the safeguarding and make sure no one closes the safeguarding.
– View the manipulator from the front whenever possible.
– Always follow the predetermined operating procedure.
– Ensure that you have a safe place to retreat in case of emergency.
Improper or unintended manipulator operation may result in injury.
iv
FS100
WARNING
• Confirm that no person is present in the manipulator’s operating range and that you are in a safe location before:
– Turning ON the power for the FS100.
– Moving the manipulator with the programming pendant.
– Running the system in the check mode.
– Performing automatic operations.
Injury may result if anyone enters the manipulator’s operating range during operation. Always press an emergency stop button immediately if there are problems.
The emergency stop button is located on the programing pendant.
CAUTION
• Perform the following inspection procedures prior to teaching the manipulator. If problems are found, correct them immediately, and be sure that all other necessary tasks have been performed.
– Check for problems in manipulator movement.
– Check for damage to the insulation and sheathing of external wires.
• Return the programming pendant to a safe place after use.
If the programming pendant is inadvertently left on the manipulator, on a fixture, or on the floor, the manipulator or a tool may collide with the programming pendant during manipulator movement, which may result in personal injury or equipment damage.
• Read and understand the Explanation of Warning Labels in the
FS100 Instructions before operating the manipulator.
Definition of Terms Used Often in This Manual
The MOTOMAN is the YASKAWA industrial robot product.
The MOTOMAN usually consists of the manipulator, the FS100 controller, manipulator cables, the FS100 programming pendant (optional), and the
FS100 programming pendant dummy connector (optional).
In this manual, the equipment is designated as follows:
Equipment
FS100 controller
FS100 programming pendant
Cable between the manipulator and the controller
FS100 programming pendant dummy connector
Manual Designation
FS100
Programming pendant
Manipulator Cable
Programming pendant dummy connector v
FS100
Descriptions of the programming pendant keys, buttons, and displays are shown as follows:
Equipment
Programming
Pendant
PC Keyboard
Manual Designation
Character Keys The keys which have characters printed on them are denoted with [ ]. ex. [ENTER]
Symbol Keys The keys which have a symbol printed on them are not denoted with [ ] but depicted with a small picture.
Axis Keys
Numeric Keys
Keys pressed simultaneously ex. PAGE key
GO BACK
PAGE
The Cursor is an exception, and a picture is not shown.
“Axis Keys” and “Numeric Keys” are generic names for the keys for axis operation and number input.
When two keys are to be pressed simultaneously, the keys are shown with a
“+” sign between them, ex. SHIFT key SHIFT +COORD key
TOOL SEL
COORD
Mode Key
Button
Displays
Three kinds of modes that can be selected by the mode key are denoted as follows:
REMOTE, PLAY, or TEACH
Three buttons on the upper side of the programming pendant are denoted as follows:
HOLD button
START button
EMERGENCY STOP button
The menu displayed in the programming pendant is denoted with { }. ex. {JOB}
The name of the key is denoted ex. Ctrl key on the keyboard
Description of the Operation Procedure
In the explanation of the operation procedure, the expression "Select • • • " means that the cursor is moved to the object item and the SELECT key is pressed, or that the item is directly selected by touching the screen.
Registered Trademark
In this manual, names of companies, corporations, or products are trademarks, registered trademarks, or brand names for each company or corporation. The indications of (R) and
TM
are omitted.
vi
FS100
Explanation of Warning Labels
DANGER
• The label described below is attached to the manipulator.
Observe the precautions on the warning labels.
Failure to observe this caution may result in injury or damage to equipment.
Fig. : Warning Labels
WARNING Label A:
WARNING
Moving parts may cause injury
WARNING Label B:
WARNING
Do not enter robot work area.
• The following warning labels are attached to FS100.
Observe the precautions on the warning labels.
Failure to observe this warning may result in injury or damage to equipment.
Fig. : Location of Warning Labels
Heavy Object Warning NP
Top View
Front View
Electric Shock Warning NP
Electric Shock Warning NP vii
FS100
...................................................................................................................................... 1-2
...................................................................................................................................... 1-3
viii
FS100
7.4.2 Procedure for the Second Home Position Setting (Check Point) ....................... 7-18
8.3.6.1 Direct Search on the Universal/Specified Input/Output Window ............. 8-9
8.3.7.1 Direct Search on the Universal/Specified Input/Output Window ........... 8-12
8.3.8.1 Direct Modification on the Universal/Specified Input/Output Window ... 8-14
ix
FS100
8.4.2 Individual Window of the System Monitoring Time Display ................................ 8-17
x
FS100
11.2 7-Segment LED Indicator on the Main CPU Circuit Board (CPU201R)......................... 11-3
11.2.1 Status of 7-Segment LED Indicator at Error Occurrence ................................. 11-4
11.2.2 Status of 7-Segment LED Indicator at Control Power Start-up (one digit) ....... 11-5
11.2.3 Status of 7-Segment LED Indicator at Hardware Error Occurrence................. 11-5
11.2.4 Status of 7-Segment LED Indicator at Alarm Occurrence ................................ 11-6
11.4.1 LED Indicator at Alarm Occurrence in the Main CPU and SERVO Control Board
xi
FS100
1 Equipment Configuration
1.1
Arrangement of Units and Circuit Boards
1 Equipment Configuration
Converter unit
CSTR-COB02AA
1.1
Arrangement of Units and Circuit Boards
Fig. 1-1: Arrangement of Units and Circuit Boards
Mounting base unit
CSTR-MBB08AAA
PWM amplifier module
CSTR-SDB AAA ***
Major axes control circuit board
CSTR-IFBM3LA
I/O relay circuit board
CSTRFBBCA8R03CAA
Power relay circuit board
JEPMC-PSD3007R-E
Control circuit board
JEPMC-CP3201R-E
(abbreviated as CPU-201R)
Top view
(without top cover)
User I/O circuit board for Japan and North America: JAPMC-IO2308R-E
(abbreviated as LIO-08R) for Europe: JAPMC-IO2309R-E
(abbreviated as LIO-09R)
Machine safety circuit board
JAPMC-SF2300R-E
(abbreviated as SF2300R)
1-1
FS100
1 Equipment Configuration
1.2
Power Flow
1.2
Power Flow
Three phase
220/200VAC
50Hz/60Hz
1
CN1
QF1
CIRCUIT
PROTECTOR
Noise filter
Z1
COOLING
FAN
COOLING
FAN
FAN
FAN
MC1
POWER
RELAY
CV1
CN304
(Control power supply)
CN303
(Main circuit)
CAPACITOR
UNIT (CRBCC)
CN203
DC280V
CN302
(CSTR-COB02AA)
(Condensor input)
(5V output)
CN308
CONVERTER
CN306
(24V4 output)
REGENERATIVE
RESISTOR
CN301
(PN)
(24V output)
CN307
CN310
(24V3 output)
CN305 CN309
P.P(OPTION)
X81
F1 (250V 0.6A)
24V (to PP)
(Power supply for control unit)
CN3
JAPMC-CP3201-E
CN4(USB)
CN1(RS232C)
CN6(MIII)
CPU201
CN10(BAT)
CN3(Ethernet)
CN2(Ethernet)
(MIII)CN5
CN3 LIO08
IO for the user (1)
IO for the user (2)
Safety
CN5(OT1,OT2)
(+24V3)CN6
CN2(PPESP,DSW)
CN1(PBESP) (HWBB,EDM)CN4
CN3
(SAFF,ONEN,EXESP)
(ESPOUT,DSWOUT)
CNTR-01
217IF-02
+24V4
(Brake power supply)
PN
DC280V
16.5V
CN54
(PN)
CSTR-MBB
CN53
(Gate power supply)
CN55
CN52 CN120
(Control (FBB control) power supply)
CN56 (Safety) CN8
CN110
CN101
CN111
CN101
CN112
CN101
AMP1
CN102
CN51
AMP2
CN102
CN51
AMP3
CN102
CN51
CN100
Motor power
CN101
CN102
FBB
(Brake release) CN210
CN209 (Relay IO)
CN211
(External IO)
CN201
(Control power supply)
CN206 (Manipulator IO)
CN208 (PP IO)
CN202
CN203
CN207
(PG signal)
(Brake output (24V))
CN204
(External axis PG signal)
CN205
(Brake power supply)
CN200 (FBB control)
(External axis PG signal)
MANIPULATOR
S-AXIS MOTOR
POWER
L-AXIS MOTOR
Brake
POWER
U-AXIS MOTOR
Brake
POWER
CN115
CN101
AMP6
CN102
CN51
CN105
X21 Brake output
Motor power
T-AXIS MOTOR
Brake
POWER
CN6A
IFM
CN50 CN51
Main circuit board
CSTR-MBBCB
Mounting base board
CSTR-MBBCA
1-2
FS100
1 Equipment Configuration
1.3
Signal Flow
1.3
Signal Flow
MC1
POWER
RELAY
Feed back signal
Control signal
Power supply turning
ON signal
P.P(OPTION)
X81
Ethernet (to PP)
Safety signal
CN3
JAPMC-CP3201-E
CN4(USB)
CN1(RS232C)
CN6(MIII)
CPU201
CN10(BAT)
CN3(Ethernet)
CN2(Ethernet)
(MIII)CN5
CN3 LIO08
IO for the user (1)
IO for the user (2)
Safety
CN5(OT1,OT2) (+24V3)CN6
CN2(PPESP,DSW)
CN1(PBESP) (HWBB,EDM)CN4
CN3
(SAFF,ONEN,EXESP)
(ESPOUT,DSWOUT)
CNTR-01
CV1
(Control
CN304 CN303 power supply) (Main circuit)
CN301
(PN)
(24V output)
CN307
CN310
(24V3 output)
CONVERTER
CN302
(CSTR-COB02AA)
(Condensor input)
CN308
(5V output)
CN306
(Control power supply)(Servo control)
(24V4 output)
CN305 CN309
FBB
CN209 (Relay IO)
CN211
(External IO)
CN201
(Control power supply)
(ManipulatorIO) CN206
(PG signal) CN203
CN207
CN208 (PP IO)
CN202
CN204
(External axis PG signal)
CN205
(Break power supply)
CN200 (FBB control)
(External axis PG signal)
Encoder signal
FBA control signal
(Encoder signal)
217IF-02
Movement block signal (redundant)
CN54
(PN)
CN53 CN52 CN120
CSTR-MBB
CN55 CN56 (Safety) CN8
CN101
CN101
CN101
AMP1
CN102
CN51
AMP2
CN102
CN51
AMP3
CN102
CN51
CN100
CN101
CN102
MANIPULATOR
S-AXIS MOTOR
ENCODER
L-AXIS MOTOR
ENCODER
U-AXIS MOTOR
ENCODER
CN115
CN101
AMP6
CN102
CN51
CN105
T-AXIS MOTOR
ENCODER
Encoder sigal
X11 Overtravel sigal
MechatroLink III
CN6A
IFM
CN50 CN51
(Main circuit board)
CSTR-MBBCB
(Mounting base board)
CSTR-MBBCA
(Overtravel sigal)
5V (OUT)
SHOCK.LAMP
(OPTION)
OT
24V (IN)
1-3
FS100
2 Security System
2.1
Protection Through Security Mode Settings
2 Security System
2.1.1
Security Mode
2.1
Protection Through Security Mode Settings
The FS100 modes setting are protected by a security system. The system allows operation and modification of settings according to operator clearance. Be sure operators have the correct level of training for each level to which they are granted access.
There are three security modes. Editing mode and management mode require a user ID. The user ID consists of numbers and letters, and contains no less than 4 and no more than 8 characters. (Significant numbers and signs: ”0 to 9”, “-”, “.”.
Table 2-1: Security Mode Descriptions
Security Mode
Operation Mode
Explanation
This mode allows basic operation of the robot (stopping, starting, etc.) for people operating the robot work on the line.
Editing Mode
Management
Mode
This mode allows the operator to teach and edit jobs and robot settings.
This mode allows those authorized to set up and maintain robot system: parameters, system time and modifying user
IDs.
2-1
FS100
2 Security System
2.1
Protection Through Security Mode Settings
Table 2-2: Menu & Security Mode (Sheet 1 of 3)
Main Menu Sub Menu
JOB
VARIABLE
JOB
SELECT JOB
CREATE NEW JOB
1)
MASTER JOB
JOB CAPACITY
CYCLE
BYTE
INTEGER
DOUBLE
REAL
STRING
POSITION (ROBOT)
POSITION (BASE)
POSITION (ST)
LOCAL VARIABLE
1)
IN/OUT EXTERNAL INPUT
EXTERNAL OUTPUT
UNIVERSAL INPUT
UNIVERSAL OUTPUT
SPECIFIC INPUT
SPECIFIC OUTPUT
RIN
CPRIN
REGISTER
AUXILIARY RELAY
CONTROL INPUT
PSEUDO INPUT SIG
NETWORK INPUT
NETWORK OUTPUT
ANALOG OUTPUT
SV POWER STATUS
TERMIMAL
LADDER PROGRAM
I/O ALARM
I/O MESSAGE
1) Displayed in the teach mode only.
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Allowed Security Mode
DISPLAY EDIT
Operation Edit
Operation
Edit
Operation
Operation -
Operation
Edit
Edit
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Operation
Edit
Edit
Edit
Edit
Edit
Edit
Edit
Operation
Operation
Operation
Operation -
-
-
-
Management Management
Management Management
Management Management
-
Edit
Edit
Edit
-
-
Operation
Operation
-
-
Management
-
-
-
Management
2-2
FS100
2 Security System
2.1
Protection Through Security Mode Settings
Table 2-2: Menu & Security Mode (Sheet 2 of 3)
Main Menu
ROBOT
Sub Menu Allowed Security Mode
DISPLAY EDIT
Operation CURRENT POSITION
COMMAND POSITION
SERVO MONITOR
WORK HOME POS
SECOND HOME POS
DROP AMOUNT
POWER ON/OFF POS
Operation
Management -
-
Operation
Operation
Edit
Edit
Management Management
Operation -
Edit Edit
Management Management
TOOL
INTERFERENCE
SHOCK SENS LEVEL
USER COORDINATE
HOME POSITION
Operation
Edit
Edit
Edit
Management Management
MANIPULATOR TYPE
ANALOG MONITOR
OVERRUN&S-SENSOR
1)
LIMIT RELEASE
ARM CONTROL
1)
1)
Management
Management
Edit
-
Management
Edit
Edit Edit
Management Management
SHIFT VALUE Operation
HAND VIBRATION CONTROL Operation
-
Management
SYSTEM INFO VERSION
MONITORING TIME
ALARM HISTORY
I/O MSG HISTORY
NETWORK SERVICE
FD/CF
USER DEFINITION MENU
SECURITY
LOAD
SAVE
VERIFY
DELETE
DEVICE
FOLDER
1) Displayed in the teach mode only.
Operation
Operation
Operation
Operation
Management -
Operation
Operation
Edit
Operation
Operation
Operation
Operation
Edit
-
-
-
-
-
Management
Management
Management
Operation
Operation
Operation
Management
2-3
FS100
2 Security System
2.1
Protection Through Security Mode Settings
Table 2-2: Menu & Security Mode (Sheet 3 of 3)
Main Menu
PARAMETER
SETUP
DISPLAY
SETUP
GENERAL
Sub Menu
S1E
S2E
S3E
S4E
S5E
S1CxG
S2C
S3C
S4C
A1P
A2P
RS
S6E
S7E
S8E
TEACHING COND.
Allowed Security Mode
DISPLAY EDIT
Management Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management
Management Management
Management Management
Management Management
Management Management
Management Management
Management Management
Edit Edit
OPERATE COND.
OPERATE ENABLE
FUNCTION ENABLE
JOG COND.
Management Management
Management Management
Management Management
Management Management
PLAYBACK COND.
FUNCTION COND.
Management Management
Management Management
DISPLAYING COLOR COND.
Management Management
DATE/TIME Management Management
GRP COMBINATION
RESERVE JOB NAME
USER ID
SET SPEED
KEY ALLOCATION
JOG KEY ALLOC.
RES. START (CNCT)
AUTO BACK SET
Management Management
Edit Edit
Edit Edit
Management Management
Management Management
Edit Management
Management Management
Management Management
WRONG DATA LOG Edit
ENERGY SAVING FUNCTION Edit
ENCODER MAINTENANE
CHANGE FONT
Edit
Operation
CHANGE BUTTON
INITIALIZE LAYOUT
Operation
Operation
CHANGE WINDOW PATTERN Operation
GENERAL DIAG.
Operation
Management
Management
Management
Operation
Operation
Operation
Operation
Edit
2-4
FS100
2 Security System
2.1
Protection Through Security Mode Settings
2.1.1.1
Changing the Security Mode
1. Select {SYSTEM INFO} under the main menu.
– The sub menu appears.
2. Select {SECURITY}.
– The selection window of security mode appears.
3. Press [SELECT] and select "SECURITY MODE".
2-5
FS100
2 Security System
2.1
Protection Through Security Mode Settings
4. Input the user ID.
– The user ID input window appears.
SUPPLE
-MENT
At the factory, the following below user ID number is preset.
• Editing Mode:[00000000]
Management Mode:[99999999]
5. Press [ENTER].
– The input user ID is compared with the user ID of the selected security mode. When the correct user ID is entered, the security mode is changed.
2-6
FS100
2 Security System
2.1
Protection Through Security Mode Settings
2.1.2
User ID
User ID is requested when Editing Mode or Management Mode is operated.
User ID must be between 4 characters and 8, and they must be numbers and symbols. (“0 to 9”,“-” and “.”)
2.1.2.1
Changing a User ID
In order to change the user ID, the FS100 must be in Editing Mode or
Management Mode. Higher security modes can make changes the user
ID of to lower security modes.
1. Select {SETUP} under the main menu.
– The sub menu appears.
2. Select {USER ID}.
– The USER ID window appears.
2-7
FS100
2 Security System
2.1
Protection Through Security Mode Settings
3. Select the desired ID.
– The character input line appears, and the message "Input current ID no. (4 to 8 digits)" is shown.
4. Input current ID and press [ENTER].
– When the correct user ID is entered, a new ID is requested to be input. "Input new ID no.(4 to 8 digits)" appears.
5. Input new ID and press [ENTER].
– User ID is changed.
2-8
FS100
3 Maintenance and Inspections
3.1
Daily Inspections
3 Maintenance and Inspections
Operator’s manual for daily inspection and parts replacement are explained in this section. Be sure to read and understand this instruction before operating the FS100.
To ensure correct and safe operation, carefully read the FS100
INSTRUCTIONS (RE-CTO-A218).
WARNING
• Maintenance and inspections should be carried out by the qualified worker.
Failure to observe this caution may result in electric shock or injury.
3.1
Daily Inspections
WARNING
• Do not touch the cooling fan or other equipment while the power is turned ON.
Failure to observe this caution may result in electric shock or injury.
3-1
FS100
3 Maintenance and Inspections
3.1
Daily Inspections
Carry out the following inspections.
Inspection
Equipment
Inspection Item Method Inspection
Interval
As required
Comments
FS100 Controller exterior
Power supply cable
Check for damages and cracks
Check for damages or connections.
Check visually
Check visually As required
Check for damages and loose connectors
Check for damages and loose connectors
Manipulator cable
(between the FS100 and the manipulator)
Cover mounting screws
Cooling fan
Check for damages or connections.
Check for defect or loose of the screws
Check the operation
Check visually
Use screw driver
Check visually
As required
As required
As required
Check for damages and loose connectors
Tighten loose screws
When the power is turned ON
When the SERVO is turned ON
Emergency stop button
1)
(programming pendant)
Enable switch
(programming pendant)
Check the operation
Check the operation
By activating the button
By activating the switch
Before the manipulator operation
Before the manipulator operation
During the teach mode
Battery
(for the system)
Message indication
Check LED lights
Check visually As required Before blocking the power supply
1 Be sure to confirm that the SERVO can be turned OFF by pressing the external emergency button when the programming pendant is not used.
The external emergency button is prepared by the user.
3-2
FS100
3 Maintenance and Inspections
3.2
Cooling Fan Inspections
3.2
Cooling Fan Inspections
Inspect the cooling fans as required. A defective fan can cause the FS100 to malfunction because of excessive high temperatures inside.
The interior circulation fan and cooling fan normally operate while the power is turned ON. Check if the fans are operating correctly by visual inspection and by feeling air moving into the air inlet and from the outlet.
Air intake
Air outlet
Air outlet
(Backside View)
Cooling fan installing direction
Air outlet Air intake Air intake
Air outlet
Air outlet
(Top View)
Cooling wind direction
3-3
FS100
3 Maintenance and Inspections
3.3
Emergency Stop Button Inspections
3.3
Emergency Stop Button Inspections
The emergency stop button is located on the programming pendant.
Before operating the manipulator, confirm that the SERVO power is ON/
OFF by pressing the emergency stop button after the SERVO is ON.
• Be sure to confirm that the SERVO can be turned OFF by pressing the external emergency button when the programming pendant is not used.
The external emergency button is prepared by the user.
3.4
Enable Switch Inspections
The programing pendant is equipped with a three-position enable switch.
Perform the following operations to confirm that the enable switch is firmly operated.
(1) Set the Mode key on the programming pendant to "TEACH".
Mode key with a switch
REMOTE
PLAY
TEACH
(2) Press [SERVO ON READY] on the programming pendant. Then
[SERVO ON] lamp blinks.
SERVO ON
(3) When the enable switch is grasped lightly, the servo power is turned ON.
When the enable switch is grasped firmly or released, the servo power is turned OFF.
NOTE
If the [SERVO ON] lamp does not blink in previous operation (2), check the following:
• The emergency stop button on the programming pendant is pressed.
• The emergency stop signal is externally input.
If the [SERVO ON] lamp does not blink in previous operation (3), check the following:
• If a major alarm is occurring.
3-4
FS100
3 Maintenance and Inspections
3.5
Battery Inspections
3.5
Battery Inspections
The FS100 has a battery that backs up the important program files for user data in the CMOS memory.
A battery alarm is indicated when a battery is weakened to be replaced.
Also, a message "Memory battery weak" appears on the programming pendant display.
Refer to chapter 5.3 “Battery Replacement” at page 5-4
for the battery replacement.
When the programming pendant is not used, be sure to confirm, from the
LED audit window on the FS100 front door, that the battery alarm LED of the CPU unit (CPU-201R) is not lit up.
Also, the battery alarm status can be confirmed by “battery alarm” of a system input.
3-5
4 Preparation before Replacing Parts
FS100
4 Preparation before Replacing Parts
WARNING
• Before operating the manipulator, check that servo power is turned
OFF when the emergency stop button on the programming pendant is pressed.
When the servo power is turned OFF, the SERVO ON LED on the programing pendant is turned OFF.
Injury or damage to machinery may result if the emergency stop circuit cannot stop the manipulator during an emergency. The manipulator should not be used if the emergency stop button does not function.
• In the case of not using the programming pendant, be sure to supply the emergency stop button on the equipment. Then before operating the manipulator, check to be sure that the servo power is turned OFF by pressing the emergency stop button.
Connect the external emergency stop button to the 5-6 pin and 16-
17 pin of the robot system signal connector (CN2).
• Upon shipment of the FS100, this signal is connected by a jumper cable in the dummy connector. To use the signal, make sure to supply a new connector, and then input it.
If the signal is input with the jumper cable connected, it does not function, which may result in personal injury or equipment damage.
• Observe the following precautions when performing teaching operations within the manipulator’s operating range:
– Be sure to use a lockout device to the safeguarding when going inside. Also, display the sign that the operation is being performed inside the safeguarding and make sure no one closes the safeguarding.
– View the manipulator from the front whenever possible.
– Always follow the predetermined operating procedure.
– Ensure that you have a safe place to retreat in case of emergency.
Improper or unintended manipulator operation may result in injury.
• Confirm that no person is present in the manipulator’s operating range and that you are in a safe location before:
– Turning ON the power for the FS100.
– Moving the manipulator with the programming pendant.
Injury may result if anyone enters the manipulator’s operating range during operation. Always press an emergency stop button immediately if there are problems.
The emergency stop button is located on the programing pendant.
4-1
FS100
4 Preparation before Replacing Parts
CAUTION
• Perform the following inspection procedures prior to conducting manipulator teaching. If problems are found, repare them immediaterly, and be sure that all other necessary processing has been performed.
– Check for problems in manipulator movement.
– Check for damage to the insulation and sheathing of external wires.
• Return the programming pendant to a safe place after use.
If the programming pendant is inadvertently left on the manipulator, on a fixture, or on the floor, the manipulator or a tool may collide with the programming pendant during manipulator movement, which may result in personal injury or equipment damage.
The following flowchart shows the operations for replacing parts.
Start
Creating a check program : Chapter 4
Replacing parts
: Chapter 5
Home position calibration
Position deviation check using the check program
: Chapter 6
No
OK?
Yes
End
This chapter describes how to create a check program as a preparation for replacing parts. The check program is a program to check the position deviation. If positions are deviated, home position calibration is required.
For the calibration, this program data is used to correct the home position data. In the following cases particularly, the home position calibration using the check program is needed. Be sure to create a check program
referring to chapter 4.1 “Creating a Check Program” at page 4-3
.
• Change in the combination of the manipulator and FS100
• Replacement of the motor or absolute encoder
• Clearing stored memory (by replacement of main CPU board, weak battery, etc.)
• Home position deviation caused by hitting the manipulator against a workpiece, etc.
4-2
FS100
4 Preparation before Replacing Parts
4.1
Creating a Check Program
4.1
Creating a Check Program
To check position deviation whenever necessary, create a program in which a check point is taught (the job for the check point). In the job for the check point, teach two points; one as a check point and the other as the point to approach the check point. This program checks for any deviation between the tool tip position and the check point.
Fig. 4-1: <Enlarged View>
4-3
FS100
5 Replacing Parts
5 Replacing Parts
5.1
Fuse Replacement
WARNING
• To prevent anyone inadvertently turning ON the power supply
(including a pressurized air), put up a warning sign such as "DO
NOT TURN ON THE POWER" before the maintenance, inspection, or wiring operation.
WARNING
• Maintenance and inspections should be carried out by the qualified worker.
Failure to observe this caution may result in electric shock or injury.
5.1
Fuse Replacement
Following fuses
1)
are mounted in the FS100.
Fuse name Where to mount Type Manufacturer
I/O power supply fuse
(F1: left side of the following figure)
Front side of the FS100 0312.600, 250V, 0.6A
6.3 dia. x 32 mm, fast-blow type
Littel Fuse Ltd.
Fuse for regenerative resistor fan protection
2)
(F2: right side of the following figure)
Front side of the FS100 250V, 1A
5 dia. x 20 mm
1 A fuse is delivered with the FS100 before shipment for replacement.
2 Fuse for regenerative resistor fan protection is mounted on the FS100 for HP20Fonlly.
Littel Fuse Ltd.
5-1
FS100
5 Replacing Parts
5.1
Fuse Replacement
F1 F2
Locations of the fuse
If the fuse seems to be blown, check its conduction. If it is blown, replace it with the same type of fuse (supplied).
NOTE If the fuse seems to be blown, be sure to investigate its cause, or blown again after the replacement.
5-2
FS100
5 Replacing Parts
5.2
Interior Circulation Fan Replacement
5.2
Interior Circulation Fan Replacement
Only interior cooling fan EV2 and EV3 can be replaced.
NOTE
Turn OFF the power before replacing the fan.
Replacement Procedures
1. Disconnect plug codes connected to the fan.
(Remove the ground wirings screwed to the fan, too)
2. Remove the screws (3 places) fixing the fan and the fan guard.
3. Uninstall the fan from the FS100.
4. Install the new fan to the FS100.
(When installing the fan, be carefull to its installing direction so that the air is drewn inside the FS100.)
5. Tighten the screws (3 places) to fix the fan and the fan guard.
6. Connect all the disconnected plug codes and the ground wirings.
(Connect the plug code securely so that there is no space between the plug code and the fan. Also, connect the ground wirings firmly.)
Cooling fan (EV3)
Cooling fan (EV2)
Air outlet
Interior Circulation Fan for Replacement
5-3
FS100
5 Replacing Parts
5.3
Battery Replacement
5.3
Battery Replacement
The battery must be replaced as soon as the battery alarm occurred.
Please be sure to replace it within 1 hour after the power is turned OFF.
(When the programming pendant is used, a message to ask battery replacement appears on its window.
Also, the timing can be confirmed by the lighting-up of the battery alarm
LED on the CPU unit (CPU-201R) or the battery alarm of the specified output.)
WARNING
• To perform this operation, it is required to open the top plate of the
FS100 while the power is turned ON.
Do NOT open the plate to perform the operation within five minutes after turning OFF the FS100 power supply and primary power source.
• Do NOT touch units or terminal parts within five minutes after turning OFF the FS100 power supply.
Failure to observe this warning may result in electric shocks.
• Close the top plate as soon as the maintenance work such as the inspection or maintenance, etc. is completed.
Failure to observe this warning may result in electric shocks.
WARNING
• To prevent anyone inadvertently turning ON the power supply during maintenace operation, put up a warning sign such as “DO
NOT TURN ON THE POWER” at the primary power supply (knife switch, wiring circuit breaker, etc.) .
Failure to observe this warning may result in electric shocks or injury.
5-4
FS100
5 Replacing Parts
5.3
Battery Replacement
Replacement Procedure
1. Uninstall the top plate and loosen the strap which is fixing the battery.
Battery fixing strap
2. Disconnect the connector from the battery extension lead wire and remove the battery.
Extension lead wire connector
3. Connect the new battery to the battery extension lead wire.
5-5
FS100
5 Replacing Parts
5.3
Battery Replacement
4. Fix the battery with the strap.
Fasten the strap till the third hole of it.
When fixing the battery, put the black lead wire toward inner side of the
FS100.
Inner side of the controller
Black lead wire
5-6
Fasten the strap till the third hole
FS100
5 Replacing Parts
5.3
Battery Replacement
Inner side of the controller
Wrong example
Do not fix the battery lead parallel to the inner side of the controller.
Fix the battery lead wire to the inner side of the controller.
The battery might fall off due to the vivration, etc., if the lead wire is fixed parallel to the controller.
NOTE
Although the CMOS memory is backed up by super capacitor, the battery must be replaced as soon as the message
"Memory battery weak" appears.
The job data and other data may be lost if the message
"Memory battery weak" appears and the breaker is turned
OFF for more than 1 hours.
5-7
FS100
6 Recommended Spare Parts
6.1
List of Accessories
6 Recommended Spare Parts
6.1
List of Accessories
Accessories of FS100 are as follows.
No.
1
2
3
Name Type Manufacturer
Power supply connector
Waterproof cable clamp
Dummy connector for safety signal short circuit
I/O power supply protection fuse
CE05-6A18-10SD-
D-BSS
DDK
CE3057-10A-1-D DDK
HB1370101-1
0312.600MXP
Yaskawa Electric
Corporation
Littel
1
1
1
Qty.
Qty. per unit
1 1
1
1
1
Accessory No.1
Accessory No.3
Accessory No.2
6-1
FS100
6 Recommended Spare Parts
6.2
Recommended Spare Parts
6.2
Recommended Spare Parts
The spare parts are ranked as follows.
CAUTION
• It is recommended to use the parts and components in the following table as spare parts for the FS100.
Product performance cannot be guaranteed when using spare parts from any company other than Yaskawa.
• Rank A: Expendable and frequently replaced parts.
• Rank B: Parts for which replacement may be necessary as a result
of frequent operation.
• Rank C: Drive unit.
Table 6-1: Spare Parts for the FS100
Rank
A
A
C
Parts
No.
1
2
3
Name
Battery
Type
BR-1/2AA 3.0V
Manufacturer
Qty.
Qty. per unit
Remark
Panasonic 1 1 When the battery alarm occurred
I/O power supply protection fuse
Cooling fan
(EV2, EV3)
0312.600MXP
Littel 1
3610PS-23T-B30-A00 MINEBEA 2
1
2 After 6 years or
36000h, whichever is earlier.
6-2
7 Operations After Replacing Parts
FS100
7 Operations After Replacing Parts
WARNING
• Before operating the manipulator, check that servo power is turned
OFF when the emergency stop button on the programming pendant is pressed.
Injury or damage to machinery may result if the emergency stop circuit cannot stop the manipulator during an emergency. The manipulator should not be used if the emergency stop button does not function.
• In the case of not using the programming pendant, be sure to supply the emergency stop button on the equipment. Then before operating the manipulator, check to be sure that the servo power is turned OFF by pressing the emergency stop button.
Connect the external emergency stop button to the 5-6 pin and 16-
17 pin of the robot system signal connector (CN2).
• Upon shipment of the FS100, this signal is connected by a jumper cable in the dummy connector. To use the signal, make sure to supply a new connector, and then input it.
If the signal is input with the jumper cable connected, it does not function, which may result in personal injury or equipment damage.
• Observe the following precautions when performing teaching operations within the manipulator’s operating range:
– Be sure to use a lockout device to the safeguarding when going inside. Also, display the sign that the operation is being performed inside the safeguarding and make sure no one closes the safeguarding.
– View the manipulator from the front whenever possible.
– Always follow the predetermined operating procedure.
– Ensure that you have a safe place to retreat in case of emergency.
Improper or unintended manipulator operation may result in injury.
• Confirm that no person is present in the manipulator’s operating range and that you are in a safe location before:
– Turning ON the power for the FS100.
– Moving the manipulator with the programming pendant.
Injury may result if anyone enters the working envelope of the manipulator during operation. Always press an emergency stop button immediately if there are problems.
Emergency stop buttons is located at the upper right of the programming pendant.
7-1
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
CAUTION
• Perform the following inspection procedures prior to conducting manipulator teaching. If problems are found, repare them immediaterly, and be sure that all other necessary processing has been performed.
– Check for problems in manipulator movement.
– Check for damage to the insulation and sheathing of external wires.
• Return the programming pendant to a safe place after use.
If the programming pendant is inadvertently left on the manipulator, on a fixture, or on the floor, the manipulator or a tool may collide with the programming pendant during manipulator movement, which may result in personal injury or equipment damage.
7.1
Home Position Calibration
7.1.1
Home Position Calibration
NOTE
Teaching and playback are not possible before home position calibration is complete.
In a system with two or more manipulators, the home position of all the manipulators must be calibrated before starting teaching or playback.
Set the security mode to the management mode to perform home position calibration.
Home position calibration is an operation in which the home position and absolute encoder position coincide. Although this operation is performed prior to shipment at the factory, the following cases require this operation to be performed again.
• Change in the combination of the manipulator and FS100
• Replacement of the motor or absolute encoder
• Clearing stored memory (by replacement of main CPU board, weak battery, etc.)
• Home position deviation caused by hitting the manipulator against a workpiece, etc.
7-2
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
To calibrate the home position, use the axis keys to calibrate the mark for the home position on each axis so that the manipulator can take its posture for the home position. There are two operations for home position calibration:
• All the axes can be moved at the same time
• Axes can be moved individually
If the absolute data of the home position is already known, set the absolute data again after completing home position registration.
SUPPLE
-MENT
Home Position
The home position is the position with the pulse value "0" for
“Manipulator Home Position” at page 7-10 .
7-3
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
7.1.2
Calibrating Operation
7.1.2.1
Registering All Axes at One Time
1. Select {ROBOT} under the main menu.
2. Select {HOME POSITION}.
– The HOME POSITIONING window appears.
3. Select {DISPLAY} under the menu, or select "PAGE" to display the selection window for the control group,
GO BACK
PAGE or press page key .
– The pull-down menu appears.
4. Select the desired control group.
7-4
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
5. Select {EDIT} under the menu.
– The pull-down menu appears.
6. Select {SELECT ALL AXES}.
– The confirmation dialog box appears.
7. Select “YES”.
– Displayed position data of all axes are registered as home position.
When “NO” is selected, the registration will be canceled.
7-5
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
7.1.2.2
Registering Individual Axes
1. Select {ROBOT} under the main menu.
2. Select {HOME POSITION}.
3. Select the desired control group.
– Perform steps 3 and 4 which have been described in
“Registering All Axes at One Time” at page 7-4 to
select the desired control group.
4. Select the axis to be registered.
– The confirmation dialog box appears.
5. Select "YES".
– Displayed position data of the axis are registered as home position.
When “NO” is selected, the registration will be canceled.
7-6
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
7.1.2.3
Changing the Absolute Data
To change the absolute data of the axis when home position calibration is completed, perform the following:
1. Select {ROBOT} under the main menu.
2. Select {HOME POSITION}.
3. Select the desired control group.
– Perform steps 3 and 4 which have been described in "Registering All
Axes at One Time" to select the desired control group
4. Select the absolute data to be registered.
– The number can now be entered.
5. Enter the absolute data using the numeric keys.
6. Press [ENTER].
– Absolute data are modified.
7-7
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
7.1.2.4
Clearing Absolute Data
1. Select {ROBOT} under the main menu.
2. Select {HOME POSITION}.
– Perform steps 2, 3, and 4 which have been described in "Registering
All Axes at One Time" to display the HOME POSITIONING window and select the desired control group.
3. Select {DATA} under the menu.
– The pull-down menu appears.
4. Select {CLEAR ALL DATA}.
– The confirmation dialog box appears.
7-8
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
5. Select "YES".
– The all absolute data are cleared. When "NO" is selected, the operation will be canceled.
7-9
FS100
7 Operations After Replacing Parts
7.1
Home Position Calibration
7.1.3
Manipulator Home Position
With the MOTOMAN-HP20F, the home position is as follows.
B-axis center line angle against
U-axis center line (-90
°
)
U-axis angle against horizontal line on the ground (-0
°)
L-axis angle against vertical line to the ground (-0
°
)
NOTE
Other manipulator models have different positions. Always consult the documentation for the correct manipulator model.
7-10
FS100
7 Operations After Replacing Parts
7.2
Position Deviation Check Using the Check Program
7.2
Position Deviation Check Using the Check Program
Use the check program to check if positions are deviated with the following procedure.
1. Call up the check program in which the check point is taught (the job for) and operate the manipulator at low speed.
2. Check the tool tip position.
– If it points the check point exactly as shown in the following figure, there is no deviation from the positions. Proceed to chapter 7.4
“Setting the Second Home Position (Check Point)” at page 7-14 .
– If not, there is a deviation. When the motor or encoder, etc. was replaced, move the corresponding axis only, when the stored memory was cleared or the manipulator was hit against a workpiece, move all axes, to the check point by joint motion. Then, proceed to
“Home Position Data Correction” at page 7-13 .
7-11
FS100
7 Operations After Replacing Parts
7.3
Checking of the Check Program
7.3
Checking of the Check Program
7.3.1
Motion of the Check Program
Call up the check program in which the check point is taught (the job for avoiding the position deviation) and operate the manipulator at low speed.
7.3.2
Checking of the Check Program
Check the deviation in to the check point. If the tool tip position is deviated, there is a deviation.
When the motor or encoder, etc. was replaced, move the corresponding axis only, when the stored memory was cleared or the manipulator was hit against a workpiece, move all axes, to the check point by joint motion.
7-12
FS100
7 Operations After Replacing Parts
7.3
Checking of the Check Program
7.3.3
Home Position Data Correction
When there is a deviation from the positions, correct the home position data with the following procedure.
1. Check the values of the following pulses.
– If there is no deviation, the following two values coincide. Then, proceed to chapter 7.4 “Setting the Second Home Position (Check
Point)” at page 7-14 .
– If there is a deviation, execute the following procedures to correct it.
(1) Command position pulse of the check point which was taught in advance
Displaying the Command Position Pulse
I) Select {ROBOT} under the main menu.
II) Select {COMMAND POSITION}.
(2) Current position pulse where the manipulator (tool tip) was moved to the check point after performing the check program
Displaying the Current Position Pulse
I) Select {ROBOT} under the main menu.
II) Select {CURRENT POSITION}.
2. Calculate the difference between the command position pulse and the current position pulse.
The difference pulse = Command position pulse − Current position
pulse
3. On the HOME POSITIONING window, add the difference pulse value to the absolute data of the axis whose motor or encoder, etc. was replaced.
4. Modify the home position data by following the procedures described in
“Changing the Absolute Data” at page 7-7 in
chapter 6.1.2.
5. Confirm that the command position pulse and the current position pulse coincide.
– The home position data have been corrected.
– Proceed to chapter 7.4 “Setting the Second Home Position (Check
Point)” at page 7-14 .
7-13
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
7.4
Setting the Second Home Position (Check Point)
WARNING
• Be aware of safety hazards when performing the position confirmation of the second home position (check point).
Abnormality of the PG system may be a cause for alarm. The manipulator may operate in an unexpected manner, and there is a risk of damage to equipment or injury to personnel.
• Before operating the manipulator, check that the SERVO ON lamp goes out when the emergency stop button on the programming pendant is pressed.
Injury or damage to machinery may result if the manipulator cannot be stopped in case of an emergency.
• In the case of not using the programming pendant, be sure to supply the emergency stop button on the equipment. Then before operating the manipulator, check to be sure that the servo power is turned OFF by pressing the emergency stop button.
Connect the external emergency stop button to the 5-6 pin and 16-
17 pin of the robot system signal connector (CN2).
• Upon shipment of the FS100, this signal is connected by a jumper cable in the dummy connector. To use the signal, make sure to supply a new connector, and then input it.
If the signal is input with the jumper cable connected, it does not function, which may result in personal injury or equipment damage.
• Observe the following precautions when performing teaching operations within the manipulator’s operating range:
– Be sure to use a lockout device to the safeguarding when going inside. Also, display the sign that the operation is being performed inside the safeguarding and make sure no one closes the safeguarding.
– View the manipulator from the front whenever possible.
– Always follow the predetermined operating procedure.
– Ensure that you have a safe place to retreat in case of emergency.
Improper or unintended manipulator operation may result in injury.
• Prior to performing the following operations, be sure that no one is in the manipulator’s operating range, and be sure that you are in a safe place when:
– Turning ON the FS100 power.
– Moving the manipulator with the programming pendant.
Injury may result from contact with the manipulator if persons enter the manipulator’s operating range.
Always press the emergency stop button immediately if there are problems.
Emergency stop button is attached on the programming pendant.
7-14
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
CAUTION
• Perform the following inspection procedures prior to teaching the manipulator. If problems are found, correct them immediately, and be sure that all other necessary tasks have been performed.
– Check for problems in manipulator movement.
– Check for damage to the insulation and sheathing of external wires.
• Return the programming pendant to a safe place after use.
If the programming pendant is inadvertently left on the manipulator, on a fixture, or on the floor, the manipulator or a tool may collide with the programming pendant during manipulator movement, which may result in personal injury or equipment damage.
7-15
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
7.4.1
Purpose of Position Check Operation
If the absolute number of rotation detected at power supply ON does not match the data stored in the absolute encoder the last time the power supply was turned OFF, an alarm is issued when the FS100 power is turned ON.
There are two possible causes of this alarm:
• Error in the PG system
• The manipulator was moved after the power supply was turned OFF.
If there is an error with the PG system, the manipulator may stall when playback is started. If the absolute data allowable range error alarm has occurred, playback and test runs will not function and the position must be checked.
"OUT OF RANGE (ABSO DATA)" alarm occurs
Reset alarm
Turn ON servo power
Procedure After Alarm Occurs
1, Position confirmation operation
2,
Compare second home position (check point)* pulses with current position pulses
OK
NG
Alarm occurs again
3, Correct defective axis
Replace PG system
Home position calibration
Position checking point
Playback possible
7-16
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
1.
Position Check
After the "OUT OF RANGE (ABSO DATA)" alarm occurs, move to the second home position using the axis keys and perform the position confirmation. Playback, test runs, and FWD operation will not function unless "CONFIRM POSITION" is performed.
2.
Pulse Difference Check
The pulse number at the second home position is compared with that at the current position. If the difference is within the allowable range, playback is enabled. If not, the alarm occurs again.
• The allowable range pulse is the number of pulses per rotation of the motor (PPR data).
• The initial value of the second home position is the home position
(where all axes are at pulse 0). The second home position can be
changed. For details, refer to chapter 7.4.2
“Procedure for the Second Home Position Setting (Check Point)” at page 7-18 .
3.
Alarm Occurrence
If the alarm occurs again, there may be an error in the PG system. Check the system. After adjusting the erroneous axis, calibrate the home position of the axis, then check the position again.
NOTE
• Home position calibration of all the axes at the same time enables playback operations without having to check the position.
• S ometimes in a system with a manipulator that has no brake, it is possible to enable playback without position checking after the alarm occurs. However, as a rule, always perform
“COMFIRM POSITION”.
Under the above special conditions, the manipulator moves as follows:
After starting, the manipulator moves at low speed (1/10 of the maximum speed) to the step indicated by the cursor.
If it is stopped and restarted during this motion, the low speed setting is retained until the step at cursor is reached.
Regardless of cycle setting, the manipulator stops after the cursor step is reached.
Starting the manipulator again then moves it at the programmed speed and cycle of the job.
7-17
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
7.4.2
Procedure for the Second Home Position Setting (Check Point)
Apart from the "home position" of the manipulator, the second home position can be set up as a check point for absolute data. Use the following steps to set the specified point.
If two or more manipulators or stations are controlled by one FS100, the second home position must be set for each manipulator or station.
1. Select {ROBOT} under the main menu.
2. Select {SECOND HOME POS}.
– The SECOND HOME POS window appears.
The message “Available to move to and modify specified point” is shown.
3. Press the page key
GO BACK
PAGE ,or select "PAGE" to display the selection window for the control group.
– The group axes by which the second home position is set is selected when there are two or more group axes.
4. Press the axis keys.
– Move the manipulator to the new second home position.
5. Press [MODIFY] and [ENTER].
– The second home position is changed.
7-18
7
FS100
7.4.3
Procedure after the Alarm
Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
WARNING
• Be aware of safety hazards when performing the position confirmation of the specified point.
Abnormality of the PG system may be cause for alarm. The manipulator may operate in an unexpected manner, and there is a risk of damage to equipment or injury to personnel.
If the "OUT OF RANGE (ABSO DATA)" alarm occurs, perform the followings
• Reset the alarm
• Turn Servo power ON and confirm the second home position. After the confirmation, if the PG system is found to be the cause of the alarm, perform the necessary operation, such as replacing the PG, etc.
The robot current position data when turning main power supply OFF and
ON can be confirmed in “POWER ON/OFF POS" window.
SUPPLE
-MENT
chapter 8.7 “Position Data When Power is
Turned ON/OFF” at page 8-23
for details on the
“POWER ON/OFF POS" window.
1. Select {ROBOT} under the main menu.
2. Select {SECOND HOME POS}.
– The SECOND HOME POS window appears.
7-19
FS100
7 Operations After Replacing Parts
7.4
Setting the Second Home Position (Check Point)
3. Press the page key
GO BACK
PAGE .
or select "PAGE" to display the selection window for the control group.
– The group axes by which the second home position is set is selected when there are two or more group axes.
4. Press [FWD].
– TCP moves to the second home position. The robot moving speed is set as selected manual speed.
5. Select {DATA} under the menu.
6. Select {CONFIRM POSITION}.
– The message “Home position checked” is shown.
Pulse data of the second home position and current pulse data are compared. If the compared error is in allowed range, playback operation can be done.
If the error is beyond the allowed range, the alarm occurs again.
7-20
FS100
8 System Diagnosis
8.1
System Version
8 System Diagnosis
8.1
System Version
It is possible to check the system CPU version information as follows.
1. Select {SYSTEM INFO} under the main menu.
2. Select {VERSION}.
– The VERSION window appears.
8.2
Manipulator Model
1. Select {ROBOT} under the main menu.
2. Select {MANIPULATOR TYPE}.
– The ROBOT AXIS CONFIG window appears.
8-1
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3
Input/Output Status
8.3.1
Universal Input
The status of input signal which is referred to by input instruction of a job can be confirmed.
8.3.1.1
Universal Input Window
1. Select {IN/OUT} under the main menu.
2. Select {UNIVERSAL INPUT}.
– The UNIVERSAL INPUT window appears.
8.3.1.2
Universal Input Simple Window
1. Select {IN/OUT} under the main menu.
2. Select {UNIVERSAL INPUT}.
– The UNIVERSAL INPUT window appears.
3. Select {SIMPLE} from the pull-down menu of {DISPLAY}.
– The UNIVERSAL INPUT simple window appears.
8-2
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.2
Universal Output
The status of the output signal set by the output instruction can be confirmed and modified.
8.3.2.1
Universal Output Window
1. Select {IN/OUT} under the main menu.
2. Select {UNIVERSAL OUTPUT}.
– The UNIVERSAL OUTPUT window appears.
8.3.2.2
Universal Output Simple Window
1. Select {IN/OUT} under the main menu.
2. Select {UNIVERSAL OUTPUT}.
– The UNIVERSAL OUTPUT window appears.
3. Select {SIMPLE} from the pull-down menu of {DISPLAY}.
– The UNIVERSAL OUTPUT simple window appears.
8-3
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.2.3
Modifying the Output Status
The status of universal output signal can be changed by the operation below.
1. Select the desired output signal number.
– Select the status of the desired output signal, “ ” or “ ” in the
UNIVERSAL OUTPUT window.
2. Press INTER LOCK key
INTER
LOCK + [SELECT].
– The status is changed. ( : ON status, : OFF status)
NOTE The status of universal output signal can be changed only when the mode is set to the teach mode.
8-4
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.3
Specific Input
8.3.3.1
Specified Input Window
1. Select {IN/OUT} under the main menu.
2. Select {SPECIFIED INPUT}.
– The SPECIFIED INPUT window appears.
8.3.3.2
Specific Input Simple Window
1. Select {IN/OUT} under the main menu.
2. Select {SPECIFIED INPUT}.
– The SPECIFIED INPUT window appears.
3. Select {SIMPLE} from the pull-down menu of {DISPLAY}.
– The SPECIFIC INPUT simple window appears.
8-5
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.4
Specific Output
8.3.4.1
Specified Output Window
1. Select {IN/OUT} under the main menu.
2. Select {SPECIFIED OUTPUT}.
– The SPECIFIED OUTPUT window appears.
8.3.4.2
Specific Output Simple Window
1. Select {IN/OUT} under the main menu.
2. Select {SPECIFIED OUTPUT}.
– The SPECIFIED OUTPUT window appears.
3. Select {SIMPLE} from the pull-down menu of {DISPLAY}.
– The SPECIFIC OUTPUT simple window appears.
8-6
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.5
RIN Input
8.3.5.1
RIN Input Window
1. Select {IN/OUT} under the main menu.
2. Select {RIN}.
– The RIN window appears.
8-7
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.6
Signal Number Search
A search can be made for a signal number of a universal input, universal output, system input, and system output.
Signal number
A search for the signal number can be made in the following two ways.
• Direct search on the UNIVERSAL/SPECIFIED INPUT/OUTPUT window
• Search from the menu
8-8
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.6.1
Direct Search on the Universal/Specified Input/Output Window
1. Move the cursor to a signal number in the UNIVERSAL/SPECIFIED
INPUT/OUTPUT window, and press [SELECT].
– Numeric values can now be entered.
2. Enter the signal number to be searched.
– Type the signal number in the number input line.
3. Press [ENTER] to start the search.
– The page where the signal number exists appears.
8-9
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.6.2
Search from the Menu
1. Select {EDIT} under the menu in the UNIVERSAL/SPECIFIED INPUT/
OUTPUT window.
– The pull-down menu appears.
2. Select {SEARCH SIGNAL NO.}.
– Numeric values can now be entered.
3. Enter the signal number to be searched.
– Type the signal number in the number input line.
4. Press [ENTER] to start the search.
– The page where the signal number exists appears.
8-10
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.7
Relay Number Search
A search can be made for a relay number of a universal input, universal output, system input, and system output.
Relay number
A search for the relay number can be made in the following two ways.
• Direct search on the UNIVERSAL/SPECIFIED INPUT/OUTPUT window
• Search from the menu
8-11
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.7.1
Direct Search on the Universal/Specified Input/Output Window
1. Move the cursor to a relay number in the UNIVERSAL/SPECIFIED
INPUT/OUTPUT window, and press [SELECT].
– Numeric values can now be entered.
2. Enter the relay number to be searched.
– Type the relay number in the number input line.
3. Press [ENTER] to start the search.
– The page where the relay number exists appears.
8-12
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.7.2
Search from the Menu
1. Select {EDIT} under the menu in the UNIVERSAL/SPECIFIED INPUT/
OUTPUT window.
– The pull-down menu appears.
2. Select {SEARCH RELAY SIGNAL NO.}.
– Numeric values can now be entered.
3. Enter the relay number to be searched.
– Type the relay number in the number input line.
4. Press [ENTER] to start the search.
– The page where the relay number exists appears.
8-13
FS100
8 System Diagnosis
8.3
Input/Output Status
8.3.8
Modification of the Signal Name
The name of the universal input or output signal can be modified.
Signal name
The name can be modified in the following two ways.
• Direct modification on the UNIVERSAL/SPECIFIED INPUT/OUTPUT window.
• Modification from the menu
8.3.8.1
Direct Modification on the Universal/Specified Input/Output Window
1. Move the cursor to the signal name to be modified in the UNIVERSAL/
SPECIFIED INPUT/OUTPUT window, and press [SELECT].
– The window for character input appears.
2. Enter the signal name.
3. Press [ENTER].
– New signal name is registered.
8-14
FS100
8
8.3
System Diagnosis
Input/Output Status
8.3.8.2
Modification from the Menu
1. Move the cursor to the signal name to be modified in the UNIVERSAL/
SPECIFIED INPUT/OUTPUT window.
2. Select {EDIT} under the menu.
– The pull-down menu appears.
3. Select {RENAME}.
– The window for character input appears.
4. Enter the signal name.
5. Press [ENTER].
– New signal name is registered.
8-15
FS100
8 System Diagnosis
8.4
System Monitoring Time Display
8.4
System Monitoring Time Display
8.4.1
System Monitoring Time Display Window
The status of system operation, e.g. power ON time, can be checked.
1. Select {SYSTEM INFO}.
2. Select {MONITORING TIME}.
– The SYS MONITORING TIME window appears.
1
2
3
4
5
1.
CONTROL POWER TIME
Displays the cumulative time that the main power supply has been
ON.
2.
SERVO POWER TIME
Displays the cumulative time that the servo power supply has been ON.
3.
PLAYBACK TIME
Displays the cumulative time during which playback was executed.
4.
MOVING TIME
Displays the cumulative time that the manipulator was in motion.
5.
OPERATING TIME
Displays the cumulative time spent in operation.
8-16
FS100
8 System Diagnosis
8.4
System Monitoring Time Display
8.4.2
Individual Window of the System Monitoring Time Display
If the page key
GO BACK
PAGE is pressed, or "PAGE" is selected to display the selection window for the system monitoring time display, the servo power time, playback time, moving time, and each-application operating time by each control group are individually displayed.
NOTE
The total time of each control group here is not always the same as the time in the SYS MONITORING TIME window because these windows show time as seen from the individual control group.
8-17
FS100
8 System Diagnosis
8.4
System Monitoring Time Display
8.4.3
Clearing the System Monitoring Time Display
The moving time and operating time can be cleared and set back to 0 by following procedure. These operations can be performed in the SYS
MONITORING TIME window, or in the individual windows.
1. Select the time to be cleared.
– The confirmation dialog box appears.
2. Select “YES”.
– The cumulative time value at the cursor line is reset to 0, and a new time measurement begins.
8-18
FS100
8 System Diagnosis
8.5
Alarm History
8.5
Alarm History
8.5.1
Alarm History Window
The alarm history can be confirmed in the alarm history window. There are five types of alarm history windows: the "MAJOR ALARM" window, the
"MINOR ALARM" window, the "USER ALARM (SYSTEM)" window, the
"USER ALARM (USER)" window, and the "OFF-LINE ALARM" window.
Each window shows the alarm code and the date and time.
1. Select {SYSTEM INFO} under the main menu.
2. Select {ALARM HISTORY}.
– The alarm history window appears.
3. Press the page key
GO BACK
PAGE to change the window, or select "PAGE" to display the selection window for the alarm windows.
– Each time the page key
GO BACK
PAGE is pressed, the window changes
"MAJOR ALARM" "MINOR ALARM" "USER
ALARM(SYSTEM)” "USER ALARM(USER)" "OFF-LINE
ALARM".
8-19
FS100
8 System Diagnosis
8.5
Alarm History
8.5.2
Clearing the Alarm History
The history of the minor alarms and the user alarms (system and user) can be cleared.
1. Display the alarm history window to be cleared.
2. Select {DATA} under the menu.
– The pull-down menu "CLEAR HISTORY" appears.
3. Select {CLEAR HISTORY}.
– The confirmation dialog box appears.
4. Select “YES”.
– The alarm history displayed is reset.
8-20
FS100
8 System Diagnosis
8.6
I/O Message History
8.6
I/O Message History
8.6.1
I/O Message History Window
The I/O message history can be confirmed in the I/O MESSAGE
HISTORY window.
The I/O MESSAGE HISTORY window shows the date and time, job name, line number, and step number of the I/O message that appeared on the window.
1. Select {SYSTEM INFO} under the main menu.
2. Select {I/O MSG HISTORY}
– The I/O MESSAGE HISTORY window appears.
8.6.1.1
Search
Press [SELECT], and numeric values can now be entered. Input the history number, and press [ENTER]. The search for the input history number begins, and the I/O message that appeared on the window is displayed.
Use the following operation to search for the I/O message history.
1. Select {EDIT} under the menu.
2. Select {SEARCH}.
– The character input line appears.
3. Enter the history No.
4. Press [ENTER].
– The search for the input history number begins, and the I/O message is displayed.
8-21
FS100
8 System Diagnosis
8.6
I/O Message History
8.6.2
Clearing the I/O Message History
Use the following operation to clear the I/O message history.
1. Select {DATA} under the menu.
2. Select {CLEAR HISTORY}.
– The confirmation dialog box appears.
3. Select “YES”.
– The displayed I/O message history is cleared.
8-22
FS100
8 System Diagnosis
8.7
Position Data When Power is Turned ON/OFF
8.7
Position Data When Power is Turned ON/OFF
8.7.1
Power ON/OFF Position Window
The Power ON/OFF position window shows the position of the manipulator when power was turned OFF the last time, the current position of the manipulator when power was later turned ON, and the amount of difference between the two positions. When alarm 4107, "OUT
OF RANGE (ABSO DATA)" occurs, the error value of the faulty axes can be verified in this window.
1. Select {ROBOT} under the main menu.
2. Select {POWER ON/OFF POS}.
– The POWER ON/OFF POSITION window appears.
8-23
FS100
8 System Diagnosis
8.8
Current Position
8.8
Current Position
8.8.1
Current Position Window
1. Select {ROBOT} under the main menu.
2. Select {CURRENT POSITION} under the sub menu.
– The CURRENT POSITION window appears.
3. Select the types of coordinates to be displayed.
– The pull-down menu appears.
4. Select the desired coordinate system.
– The type of coordinates being displayed is changed.
8-24
FS100
8 System Diagnosis
8.9
Servo Monitoring
8.9
Servo Monitoring
8.9.1
Servo Monitor Window
The servo monitor window shows the servo-related data of each axis.
Monitor Items
FEEDBACK PULSE
ERROR PULSE
SPEED DEVIATION
SPEED INST
FEEDBACK SPEED
TORQUE SPEC
MAX. TORQUE
ENCODER ROTATE SUM
IN 1 TURN POSITION
MOTOR ABSOLUTE
ENCODER TEMPERATURE
Description
Feedback position (actual position) of each axis
“0” at the home position
Difference between the command position and the feedback position of each axis
Difference between the command speed and the feedback speed of each axis
Speed reference of each axis
Feedback speed (actual speed) of each axis
Torque reference of each axis
Keeps the maximum value of the torque reference of each axis.
“0” when the maximum torque is cleared or the control power supply is turned ON or OFF
Accumulated number of encoder rotation when the control power supply of each axis is turned ON
Position after one rotation of the encoder when the control power supply of each axis is turned ON
Absolute value of the motor is calculated by adding the position in one rotation to the sum of the accumulated rotations when the control power supply of each axis is turned ON.
Encoder tenperature of each axis
8-25
FS100
8
8.9
System Diagnosis
Servo Monitoring
8.9.1.1
Changing the Monitor Items
1. Set the security mode to the management mode.
2. Select {ROBOT} under the main menu.
3. Select {SERVO MONITOR}.
– The SERVO MONITOR window appears.
4. Select {DISPLAY} under the menu.
– The pull-down menu appears.
MONITOR ITEM 1 is the data on the left, and MONITOR ITEM 2 is the data on the right
8-26
FS100
8 System Diagnosis
8.9
Servo Monitoring
5. Select MONITOR ITEM 1 or 2, and view the sub-menu choices by the cursor key .
– The sub-menu choices appear.
6. Select a menu.
– The type of monitor-related information is changed.
8-27
FS100
8 System Diagnosis
8.9
Servo Monitoring
8.9.1.2
Clearing Maximum Torque Data
The data for the maximum torque can be cleared when the maximum torque-related information is being displayed.
1. Select {DATA} under the menu.
– The clear max torque window appears
2. Select {MAX. TORQUE}.
– The maximum torque data is cleared.
8-28
FS100
9 Alarm
9 Alarm
9.1
Outline of Alarm
9.1
Outline of Alarm
When an alarm of level 0 to 3 (major alarm) occurs, the servo power supply is turned OFF.
Table 9-1: Alarm Code Classification
Alarm Code Alarm Level
0
1 to
3
4 to
8
9
Level 0 (Major alarm)
(Off line alarm: Initial diagnosis/ Hardware diagnosis alarm)
Level 1 to 3
(Major alarm)
Level 4 to 8
(Minor alarm)
Level 9 (Minor alarm)
(I/O alarm)
Alarm Reset Method
It is not possible to reset by
"RESET" under the ALARM window or the system input signal
(Alarm reset). Turn OFF the main power supply and correct the cause of the alarm. Then turn ON the main power supply again.
It is not possible to reset by
"RESET" under the ALARM window or the system input signal
(Alarm reset). Turn OFF the main power supply and correct the cause of the alarm. Then turn ON the main power supply again.
After correcting the cause, it is possible to reset by "RESET" under the ALARM window or the system input signal (Alarm reset).
After correcting the cause for which the system input signal for the system or user alarm request turns ON, it is possible to reset by
"RESET" under the ALARM window or the system input signal
(Alarm reset).
9-1
FS100
9 Alarm
9.2
Alarm Display
9.2
Alarm Display
9.2.1
Displaying and Releasing Alarm
If an alarm occurs during operation, the manipulator stops immediately and the ALARM window appears on the programming pendant indicating that the machine was stopped by an alarm.
Alarm number
Alarm message
Sub data
If more than one alarm occurs simultaneously, all the alarms are displayed.
Scroll the viewing area with the cursor to view the alarm that is not currently displayed on the viewing area.
The following operations are available in the alarm status: window change, mode change, alarm reset, and emergency stop. If the window is changed to another window during alarm occurrence, the ALARM window can be shown again by selecting {SYSTEM INFO} under the main menu and then selecting {ALARM}.
9.2.1.1
Releasing Alarms
Alarms are classified by minor and major alarms.
• Minor Alarms
Select "RESET" on the ALARM window to release alarms.
Or, turn ON the system signal "ALARM RESET" when using an external input signal (system input).
• Major Alarms
If a severe alarm such as hardware failure occurs, servo power is automatically shut OFF and the manipulator stops. Turn OFF the main power supply, remove the cause of the alarm, and then turn ON the power supply again.
9-2
FS100
9 Alarm
9.2
Alarm Display
9.2.2
Special Alarm Display
(1) Sub Data
Sub data such as data for the axis where the alarm occurred, may
also be displayed for some alarms.
• Decimal data
Without signs: 0 to 65535
With signs: -32768 to 32767
• Binary data
The alarm occurrence data becomes “1”.
With 8 bits: 0000_0001
With 16 bits: 00000001_00000001
• Axis data
The axis where the alarm occurred is highlighted.
With robot axis: Robots 1 to 2 [ S L U R B T ]
With base axis: Base 1 to 2
[ 1 2]
With station axis: Stations 1 to 3 [ 1 2 3 ]
• XYZ coordinate data
The coordinates where the alarm occurred are highlighted.
[ X Y Z ]
[ X Y Z Tx Ty Tz ]
• 123 data
The data for which the alarm occurred is highlighted.
[ 1 2 3 ]
• Control group data
The control group where the alarm occurred is highlighted.
[ R1 R2 S1 S2 S3 ]
(2) Multiple SERVO Control Board System
In a system using more than one SERVO control board, the number of
the SERVO control board where the alarm occurred is also displayed.
The SERVO control board number is determined by its S2 switch.
SV#1: SERVO control board 1
SV#2: SERVO control board 2
9-3
FS100
9 Alarm
9.2
Alarm Display
(3) Independent Control Function (Optional)
In the independent control function (multi-task job), the tasks that were
being done when the alarm occurred are also displayed.
TASK#0: Master-task job
TASK#1: Sub-task1 job (SUB1)
TASK#2: Sub-task2 job (SUB2)
TASK#3: Sub-task3 job (SUB3)
TASK#4: Sub-task4 job (SUB4)
TASK#5: Sub-task5 job (SUB5)
9-4
FS100
9 Alarm
9.3
Display of Alarm Details
9.3
Display of Alarm Details
Alarm details displaying function indicates the alarm contents breakdown on the alarm window.
Press [Select] after moving the cursor to the subject alarm on the alarm window to display its “content”, “cause” and “measure”.
Skip displaying the alarm window to directly display this breakdown window is possible by specifying the parameter when an alarm occurs.
9.3.1
Parameter
S2C406 Alarm Details Direct Display 0: Invalid / 1: Valid
9.3.2
Display of Alarm Detail Window
Alarm No.
Page
Alarm explanation
Alarm title
Same as alarm
window data.
(Ordinary window)
Alarm content
{Right/Left} button
Cause
Measure
{Return} button {Retset} button {Page} button
Page
Displays the page number of the alarm whose detail window is currently displayed
/ the total alarm number occurred coincidentally.
Alarm No.
Displays the alarm number with decimal 4 digit.
Sub data
Displays the sub code number defined to each alarm.
Alarm content
Displays the content of the alarm.
9-5
FS100
9 Alarm
9.3
Display of Alarm Details
{Right/Left} button
This button appears when there can be several “cause”s and “measure”s to one alarm. Press this to right/left ward to alternate the “cause” and the
“measure”.
Cause
Displays the cause of an alarm.
Measure
Displays the recovery method from the alarming state.
{Reset}button
Press this button to reset the alarm.
{Page} button
Press this button to display the page number inputting area.
This area appears when several alarms occur at a time.
9-6
FS100
9
9.3
Alarm
Display of Alarm Details
9.3.3
Transition of Alarm Detail Window
Alarm
Standard
ALARM DETAIL window
While direct display setting is set
(S2C406=1)
Move the Cursor (up and down) to select the alarm number to display each ALARM DETAIL window .
[Select]
{RETURN} button or [CANCEL]
When direct display is set, it would not return to the above window
SHIFT SHIFT key PAGE key
GO BACK
PAGE PAGE key
GO BACK
PAGE
{PAGE} button
Press {Left} button
on the window or
Move Cursor to the left
{RESET} button {RESET} button
Press {Right} button
on the window or
Move Cursor to the right
Window before alarm occurs
In case an unresettable alarm occured, the
ALARM window (or its ALARM DETAIL window) appears.
9-7
FS100
9 Alarm
9.4
Alarm Message List
9.4
Alarm Message List
CAUTION
• Before handling the main CPU board (CPU-201R) for any remedies, personnel must be appropriately skilled in maintenance mode operation.
• CPU-201R is saving important file data for the user program through its battery backup operation. Contact your Yaskawa representatives when measures for CPU-201R alarms are considered to be needed. Careless operation may delete registered data.
9-8
Alarm
Number
Alarm Name
ERROR
Sub
Code
Meaning
50
51
Cause
No response was sent from the
Main CPU board when the control power turned ON.
Software operation error occurred
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
No response was sent from the servo board #1 when the control power turned ON.
In this case, the FS100 may make wrong judgement that a signal such as external hold signal is input. However, it is caused by the communication error with Servo control board #1. Therefore, execute the following measure.
Setting error
Connection failure
No response was sent from the
Servo control board #2 when the control power turned ON.
Servo control board failure
Main CPU board failure
Setting error
Connection failure
Servo control board failure
(1)Turn the power OFF then back ON
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1) Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
ERROR (SERVO)
30 ROM ERROR
Sub
Code
Meaning
51
1
Cause Remedy
The communications CPU for the
Servo control board #1 detected an error when the control power turned ON.
The communications CPU for the
Servo control board #2 detected an error when the control power turned ON.
The CPU-201R system program is damaged.
converter unit failure
Main CPU board failure
Setting error
Connection failure
Servo control board failure
Main CPU board failure
Setting error
Connection failure
Servo control board failure
Main CPU board failure
Software operation error occurred
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
ERROR
(I/O MODULE)
Sub
Code
50
51
1
Meaning
The system program of Servo control board #1 is damaged.
The system program of Servo control board #2 is damaged.
The IO module board connected with 0th serial bus exists.
An error was detected in communications with the I/O module board connected with 1st serial bus when the control power turned ON.
Cause
Software operation error occurred
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Main CPU board failure
Setting error
Connection failure
Board failure
(I/O module)
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
2
3
Meaning Cause
An error was detected in communications with the I/O module board connected with 2nd serial bus when the control power turned ON.
Setting error
Connection failure
Board failure
(I/O module)
Main CPU board failure
An error was detected in communications with the I/O module board connected with 3rd serial bus when the control power turned ON.
Setting error
Connection failure
Board failure
(I/O module)
Main CPU board failure
Remedy
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
4
Meaning Cause
An error was detected in communications with the I/O module board connected with 4th serial bus when the control power turned ON.
Setting error
Connection failure
5
Remedy
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
Board failure (I/O module)
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
An error was detected in communications with the I/O module board connected with 5th serial bus when the control power turned ON.
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
6
Meaning Cause
An error was detected in communications with the I/O module board connected with 6th serial bus when the control power turned ON.
Setting error
Connection failure
7
Remedy
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
An error was detected in communications with the I/O module board connected with 7th serial bus when the control power turned ON.
Board failure (I/O module)
Main CPU board failure
Setting error
Connection failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
Board failure(I/O module)
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
100 COMMUNICATION 1
ERROR (servo#1)
Sub
Code
8
Meaning Cause
An error was detected in communications with the I/O module board connected with 8th serial bus when the control power turned ON.
Setting error
Connection failure
2
Remedy
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
Board failure (I/O module)
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
The error was detected during the check of the serial communication watchdog data.
Counter value received from
Servo control board is invalid.
Setting error
Connection failure
The error was detected during the check of the number of the serial communications.
Counter value received from
Servo control board is OFF by one cycle.
Servo control board failure
Main CPU board failure
Setting error
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
101 COMMUNICATION 1
ERROR (servo#2)
Sub
Code
Meaning
2
Cause Remedy
Connection failure
Servo control board failure
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
The error was detected during the check of the serial communication watchdog data.
Counter value received from
Servo control board is invalid.
Setting error
Connection failure
Servo control board failure
Converter unit failure
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
The error was detected during the check of the number of the serial communications.
Counter value received from
Servo control board is OFF by one cycle.
Setting error
Connection failure
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
(PARAMETER FILE)
Sub
Code
0
1
2
3
4
Meaning Cause
Converter unit failure
Main CPU board failure
The RC parameter is damaged.
Data error
Main CPU board failure
The RO parameter is damaged.
Data error
Main CPU board failure
The SV parameter is damaged.
Data error
Main CPU board failure
The SVM parameter is damaged.
Data error
Main CPU board failure
The SC parameter is damaged.
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
5
Meaning
The SD parameter is damaged.
Cause
Data error
6
7
8
9
10
Main CPU board failure
The CIO parameter is damaged.
Data error
Main CPU board failure
The FD parameter is damaged.
Data error
Main CPU board failure
The AP parameter is damaged.
Data error
Main CPU board failure
The RS parameter is damaged.
Data error
Main CPU board failure
The SE parameter is damaged.
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
(SYSTEM CONFIG-
DATA)
(JOB MNG DATA)
Sub
Code
11
Meaning Cause
The SVC parameter is damaged.
Data error
Main CPU board failure
12
13
14
15
0
The AMC parameter is damaged.
Data error
Main CPU board failure
The SVP parameter is damaged.
Data error
Main CPU board failure
The MF parameter is damaged.
Data error
Main CPU board failure
The SVS parameter is damaged.
Data error
Main CPU board failure
The system configuration information data are damaged.
Main CPU board failure
The management data of job files are damaged.
Data error
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
Alarm
Number
Alarm Name
(LADDER PRG FILE)
(NETWORK SETUP)
Sub
Code
1
2
3
Meaning
The job files are damaged.
Cause
Main CPU board failure
Data error
Main CPU board failure
The management data of position data files are damaged.
Data error
Main CPU board failure
Memory and play back file is damaged.
Data error
Main CPU board failure
The CIO ladder file is damaged.
Data error
The network setting file is damaged.
Main CPU board failure
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the job file in maintenance mode, and then load the data (job, variable data, Robot calibration data) saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then set the network again.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
(SYSTEM CONFIG-
DATA)
(OVERRUN INPUT SET)
(CMOS MEMORY)
Sub
Code
2
4
5
7
8
0
Meaning
CIO parameter error.
Cause
Setting error
Main CPU board failure
Axis-related parameter error.
Setting error
Main CPU board failure
Sensor-use parameter error.
Setting error
Main CPU board failure
The set optional functions are different from those of the mounted optional board.
Setting error
Main CPU board failure
IO type error (combination impossible to coexist).
Setting error
Main CPU board failure
Sub Code: Control group
Parameter specification and OT signal information are wrong
The CMOS memory version is different from its initial setting.
Setting error
Setting error
Main CPU board failure
Remedy
(1)Check the following settings.
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Control group settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The optional board setting in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The optional board setting in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Connection settings (OT) in maintenance mode
(1)Check the following settings.
·Set the security mode to MANAGEMENT MODE.
·Data rebuild in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
320 VERIFY ERROR
(I/O MODULE)
Sub
Code
1
1
2
Meaning Cause
The CRC data in CMOS memory and the CRC data calculated by the system software are inconsistent.
Setting error
Main CPU board failure
The I/O module connected to the serial bus #1 is different from the function of the set I/O module.
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
The I/O module connected to the serial bus #2 is different from the function of the set I/O module.
Setting error
Connection failure
Board failure (I/O module)
Remedy
(1)Check the following settings.
·Set the security mode to MANAGEMENT MODE.
·Data rebuild in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
Alarm
Number
Alarm Name
Sub
Code
Meaning
3
4
Cause Remedy
The I/O module connected to the serial bus #3 is different from the function of the set I/O module.
The I/O module connected to the serial bus #4 is different from the function of the set I/O module.
Main CPU board failure
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
5
6
7
Meaning
The I/O module connected to the serial bus #6 is different from the function of the set I/O module.
The I/O module connected to the serial bus #7 is different from the function of the set I/O module.
Cause
The I/O module connected to the serial bus #5 is different from the function of the set I/O module.
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
Setting error
Connection failure
Board failure(I/O module)
Main CPU board failure
Setting error
Remedy
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
Alarm
Number
Alarm Name
(APPLICATION)
(SEGMENT CLOCK)
Sub
Code
Meaning
8
Cause Remedy
The I/O module connected to the serial bus #8 is different from the function of the set I/O module.
Illegal instruction cycle is set.
Connection failure
Board failure(I/O module)
Main CPU board failure
Setting error
Connection failure
Board failure (I/O module)
Main CPU board failure
Main CPU board failure
Setting error
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·The rotary switch setting which specifies slot numbers of each I/O module
·I/O module settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·Terminator
·24V power of the corresponding IO module.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
·Corresponding IO module
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Instruction execution cycle
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
400 PARAMETER
TRANSMISSION ERROR
Sub
Code
50
410
51
MODE CHANGE ERROR 50
Meaning
An error occurred during the parameter/file transfer to the 1st
Servo control board.
Setting error
An error occurred during the parameter/file transfer to the 2nd
Servo control board.
An error occurred during startup sequence processing with the servo CPU of 1st Servo control board, and the system did not startup normally.
Cause
Connection failure
Servo control board failure
Main CPU board failure
Setting error
Connection failure
Servo control board failure
Main CPU board failure
Setting error
Connection failure
Servo control board failure
Remedy
(1)Check the following settings.
·Control group settings in maintenance mode
·The Servo control board rotary switch setting (0) of the corresponding node number (SV#1)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Control group settings in maintenance mode
·The Servo control board rotary switch setting (1) of the corresponding node number (SV#2)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Control group settings in maintenance mode
·The Servo control board rotary switch setting (0) of the corresponding node number (SV#1)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
500
520
Alarm Name
SEGMENT PROC NOT
READY
UNMATCH
AXIS LIMIT OVER
Sub
Code
Meaning
51
51
0
Cause Remedy
An error occurred during startup sequence processing with the servo CPU of 2nd Servo control board, and the system did not startup normally.
Main CPU board failure
Setting error
Connection failure
Servo control board failure
Main CPU board failure
Setting error
Main CPU board failure
1st Servo control board's interface version is not corresponding to
Main CPU board
Main CPU board failure
2nd Servo control board's interface version is not corresponding to Main CPU board.
Main CPU board failure
Setting error
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Control group settings in maintenance mode
·The Servo control board rotary switch setting (1) of the corresponding node number (SV#2)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Check the following settings.
·Control group settings in maintenance mode
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
ERROR
ERROR
Sub
Code
2
3
4
5
Meaning Cause
Data error
Main CPU board failure
An error was found in the relay
No. specification.
Data error
Main CPU board failure
An error was found in the register
No. specification.
Data error
Main CPU board failure
An incorrect instruction was set.
Data error
Main CPU board failure
Data error Output register is used redundantly.
Main CPU board failure
Output relay is used redundantly.
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
6
7
8
9
10
11
Meaning
Unconnected relay exists.
Cause
Data error
Main CPU board failure
The STR instructions are overused.
Data error
Main CPU board failure
The AND-STR instructions are overused.
Data error
Main CPU board failure
A syntax error was found in the
CNT instruction.
Data error
Main CPU board failure
The head of the block starts with an instruction other than the STR instruction.
Data error
Main CPU board failure
Excessive machine codes Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
Sub
Code
12
Meaning Cause
The last instruction is not the END instruction.
Data error
Main CPU board failure
13
14
15
16
17
An error was found in the PART instruction.
Data error
Main CPU board failure
An error was found in the GOUT instruction.
Data error
Main CPU board failure
The No. of operand is incorrect.
Data error
Main CPU board failure
The constant value is incorrect.
Data error
Main CPU board failure
The step capacity exceeds the memory capacity.
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
Alarm
Number
Alarm Name
WEAK
ERROR
Sub
Code
18
19
20
21
Meaning
The number of operation instructions exceed the permissible value.
Cause
Data error
Main CPU board failure
A syntax error was found in the
CNT instruction or TMR instruction.
Data error
Main CPU board failure
A syntax error was found in the
JMP-LABEL instructions.
Data error
Main CPU board failure
The label of JMP destination does not exist.
Data error
Main CPU board failure
Main CPU board battery is weakening.
Connection failure
Connection failure
Sub Code: Option board. Number
× 100 factor
factor:
1 ROM ERR
2 RAM ERR
3 CPU ERR
4 SHARED MEMORY ERR
5 CNTR ASIC ERR
CNTR01R board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Confirm that the battery is appropriately connected to the main CPU board.
(1)Replace the battery in accordance with the instructions in FS100
MAINTENANCE MANUAL.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
Alarm
Number
822
Alarm Name
ERROR
Sub
Code
Meaning
CNTR01R WDG ERROR 100
Cause
Sub Code: Option board.
Number×100 factor
factor:
1 WDG TIMEOVER
2 ADDRESS ERR(READ)
EXCEPTION
3 ADDRESS ERR(WRITE)
EXCEPTION
4 UNJUST INST
EXCEPTION
5 UNJUST SLOT
EXCEPTION
A Watchdog err was detected in the Option #1 board.
CNTR01R board failure
CNTR01R board failure
200
300
400
500
600
700
800
A Watchdog err was detected in the Option #2 board.
CNTR01R board failure
A Watchdog err was detected in the Option #3 board.
CNTR01R board failure
A Watchdog err was detected in the Option #4 board.
CNTR01R board failure
A Watchdog err was detected in the Option #5 board.
CNTR01R board failure
A Watchdog err was detected in the Option #6 board.
CNTR01R board failure
A Watchdog err was detected in the Option #7 board.
CNTR01R board failure
A Watchdog err was detected in the Option #8 board.
CNTR01R board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CNTR01R board. Save the CMOS.BIN before replacing the board to be safe.
Alarm
Number
Alarm Name
(CPU-201R)
920 BUS ERROR
(CPU-201R)
(servo#1)
(servo#2)
1000
(Main CPU)
ROM ERROR
(Main CPU)
1001 ROM ERROR
(SERVO)
Sub
Code
1
Meaning Cause
An error was detected in the CPU. Main CPU board failure
1
1
10
Remedy
The JL chip does not operate normally.
An error was detected in the CPU of servo board #1.
Connection failure
An error was detected in the CPU of servo board #2.
Power Lost Signal Error
Main CPU board failure
Servo control board failure
Main CPU board failure
Connection failure
Servo control board failure
Main CPU board failure
Main CPU board failure
Software operation error occurred
1*:A checksum error occurred in the board or the EEPROM.
(*: axis No.)
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the controller. Save the CMOS.BIN before replacement to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1020
Alarm Name
MotoPlus application load error
1
2
Sub
Code
20
Meaning
21
22
23
24
25
26
Cause
The SRDY signal did not turn ON after the WRITE ENABLE command was written. (EEPROM
WRITE ENABLE error)
Servo control board failure
The SRDY signal did not turn ON after the WRITE PROTECT command was written. (EEPROM
WRITE PROTECT error)
Servo control board failure
The SRDY signal did not turn ON after the ERASE command was written. (EEPROM ERASE error)
Servo control board failure
The SRDY signal did not turn ON after the CLEAR command was written. (EEPROM CLEAR error)
Servo control board failure
The SRDY signal did not turn ON after data were written.
(EEPROM writing error)
Servo control board failure
The SRDY signal did not turn ON after data were read.
(EEPROM reading error)
Servo control board failure
The written data were rejected at verification.
(EEPROM verify error)
Servo control board failure
Num of the Application files is over the limit.
Insufficient memory space
Setting error
Setting error
Remedy
3
4
MotoPlus application folder cannot be found.
Memory size required by
Application is over the limit
(2Mbyte).
Setting error
Setting error
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Set the number of application file "*.OUT" to be within the defined value. (Delete unnecessary files from the MotoPlus menu of the maintenance mode.)
Memory to work MotoPlus application is insufficient under the combination of current system configuration and its optional function. IIf the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your
Yaskawa representative about occurrence status (operating procedure).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller and load the MotoPlus application which was loaded to the previous controller.
Check that if the object file name is too long or inappropriate letters are used.
Alarm
Number
Alarm Name
Sub
Code
5
6
7
8
9
Meaning Cause
Undefined symbols are included in the application.
Load failure (other)
Setting error
Setting error
API library initialization failure Setting error
User root task not included
User root task generation failure
Setting error
Setting error
10 RAM-Disk generation failure Setting error
1030 MEMORY ERROR
(PARAMETER FILE)
0
11
12
13
MotoPlus application process generation failure application file "*.VXE" in the controller exceeded the specified value
Failure to install the driver to communicate between MotoPlus application and the system.
Setting error
Setting error
Setting error
RCD, RCxG parameter error Data error
Main CPU board failure
Remedy
Check that symbols such as undefined functions or constants, which are provided from the system side, are included in the application program.
(1)Check the definition of static variable in the MotoPlus application program is correct or not.
(2)Check the MotoPlus application programs so that they are set within the specified values.
(3)Check that the object files are appropriately created.
Memory to work MotoPlus application is insufficient under the combination of current system configuration and its optional function. If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Confirm that mpUsRoot() is described in the application program.
Memory to work MotoPlus application is insufficient under the combination of current system configuration and its optional function. IIf the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your
Yaskawa representative about occurrence status (operating procedure).
Memory to work MotoPlus application is insufficient under the combination of current system configuration and its optional function. If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Check that the object file is appropriately created.
Set the number of application file "*.VXE" to be within the defined value. (Delete unnecessary files from the MotoPlus menu of the maintenance mode.)
Memory to work MotoPlus application is insufficient under the combination of current system configuration and its optional function. If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
1
2
3
4
5
Meaning
ROxG parameter error
SVD, SVxG parameter error
Main CPU board failure
Data error
SVMxG parameter error
Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error S1CxG, S2C, S3C, S4C parameter error
Main CPU board failure
S1D, S2D, S3D, S4D parameter error
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
6
7
8
9
Meaning
CIO parameter error
FD parameter error
Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
A1P, A2P, …, A8P parameter error
Data error
RS parameter error
Main CPU board failure
Data error
10
Main CPU board failure
S1E, S2E, …, S8E parameter error
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
11
Meaning
SVCxB parameter error
12 AMCxG parameter error
13 SVPxG parameter error
14 MFxG parameter error
15 SVSxG parameter error
Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
1031 MEMORY ERROR
(MOTION1)
Sub
Code
16
Meaning
RExG parameter error
Cause
Data error
2
3
4
0
1
8
9
5
7
34
Main CPU board failure
"GET FILE" instruction, "SET
FILE" instruction execution target file
Home position calibration file
Data error
Data error
Tool file
User coordinates file
Robot calibration file
Data error
Data error
Data error
Tool calibration file Data error
Home position correction data file Data error
Conveyor calibration file
Arm and tool interference prevention file
Conveyor condition file
Data error
Data error
Data error
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate parameter file in maintenance mode, and then load the parameter file saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Alarm
Number
Alarm Name
53
62
47
48
43
45
36
42
64
67
69
Sub
Code
35
Meaning
Press characteristics file
Cause
Data error
Servo float condition file
Anticipation OT# output file
Anticipation OG# output file
Form cut file
Data error
Data error
Data error
Data error
Linear servo float condition file Data error
Macro definition file
Job registration table
Data error
Data error
Linear scale condition file Data error
Conveyor condition auxiliary file Data error
Pelletizing condition file Data error
Mastering registration position Data error
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, initialize the appropriate data in maintenance mode, and then load the data saved in the external memory device.
Alarm
Number
1050
Alarm Name
SET-UP PROCESS
ERROR (SYSCON)
1051 SET-UP PROCESS
ERROR (MOTION)
Sub
Code
1
2
1
2
3
Meaning
Motion instruction setup incomplete
Online error
Cause
Main CPU board failure
Software operation error occurred
Main CPU board failure
Software operation error occurred
Unable to properly activate the servo control
Servo control board failure
Software operation error occurred
The position data of when the power supply was turned OFF cannot be transmitted to the servo control section
Servo control board failure
Software operation error occurred
The servo control section cannot receive the position data of when the power supply was turned OFF
Servo control board failure
Software operation error occurred
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
Alarm
Number
Alarm Name
Sub
Code
7
8
9
10
11
Meaning
Unable to send a request to prepare a feedback pulse
Unable to prepare a feedback pulse
Unable to send a request to initialize the arithmetic section
(ARITH)
Unable to initialize ARITH
Unable to send a request to prepare the current position
Cause
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Main CPU board failure
Software operation error occurred
Main CPU board failure
Software operation error occurred
Main CPU board failure
Software operation error occurred
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
Alarm
Number
1053
1100
1101
1102
1103
1104
Alarm Name
SYSTEM ERROR
(EVENT)
SYSTEM ERROR
SYSTEM ERROR
(MAN-MACHINE
MECHA)
SYSTEM ERROR
(MAN-MACHINE APPLI)
SYSTEM ERROR
(EVENT)
SYSTEM ERROR
(CIO)
Sub
Code
12
Meaning
Unable to prepare the current position
Cause
Main CPU board failure
Software operation error occurred
Sub Code
1 to 8: Signifies the internal software error at event process.
Software operation error occurred
Sub Code
C, B, F : Sub code of unknown alarm
Software operation error occurred
RAM software data error
Sub Code
0 to 6: Internal control error in software
Software operation error occurred
Sub Code
0 to 526: Internal control error in software
Software operation error occurred
Software operation error occurred
Sub Code
1000_0000: I/O module setting error
Connection failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables or connectors.
·IO module cable of the corresponding slot.
·24V power of the corresponding IO module.
Alarm
Number
Alarm Name
1105 SYSTEM ERROR
(SERVO)
Sub
Code
Meaning
15
21
30
37
47
Cause Remedy
Communication period with the motion part is inappropriate.
A task request was sent to an axis in the alarm status.
The linear servo float does not support the manipulator type specified in the RC parameter at calculation for servo-float-related parameters.
The manipulator (B-axis) passed the singular point while the linear servo float was ON.
The alarm number is illegal.
Setting error
Main CPU board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Setting error
Software operation error occurred
(1)Turn the power OFF then back ON.
(2)If the error occurs again, set the I/O module again in maintenance mode.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the YCP01 board. Save the CMOS.BIN before replace the board to be safe. Replace the YCP01 board, and then remove the CF from the failure YCP01 board to insert it into the new YCP01.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Check the following settings.
Correct the job so that the manipulator (B-axis) does not pass the singular point while the linear servo float is ON.
(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).
Alarm
Number
Alarm Name
Sub
Code
49
115
128
135
136
137
Meaning
Parameter modified while the servo float is ON.
500
μ s non real process execution sequence error
The dynamics calculation process did not complete within the time set on the scheduling table.
General08ms process dose not complete within the time set by the scheduling table.
Dynamics arithmetic process dose not complete within the time set by the scheduling table.
500
μ s non real process dose not complete within the time set by the scheduling table.
Cause
Setting error
Software operation error occurred
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
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).
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
Alarm
Number
Alarm Name
Sub
Code
Meaning
138
140
151
160
200
303
Cause Remedy
Real time process dose not complete within the time set by the scheduling table.
External interruption occurred.
The averaging time is not an even number. (times)
Software operation error occurred
Servo control board failure
The interface with the microprogram dose not complete within the time set by the scheduling table.
Software operation error occurred
Servo control board failure
The notch filter doesn't become effective after shifting to PLAY mode.
The difference between the base torque and the target torque exceeded the threshold in the jig robot bending correction.
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Software operation error occurred
Software operation error occurred
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
500
Meaning
Inconsistency of FP register.
Cause Remedy
1000
1001
1002
1003
1004
1005
1006
The check item number of SVD parameter is unmatched.
The check item number of SV parameter is unmatched.
The check item number of SVM parameter is unmatched.
The check item number of SVP parameter is unmatched.
The check item number of AMC parameter is unmatched.
The check item number of MFG parameter is unmatched.
The check item number of MFA parameter is unmatched.
Servo control board failure
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
1200
1204
1220
Alarm Name
HIGH TEMPERATURE
(IN CNTL BOX)
COMMUNICATION
ERROR
(OPTION MODULE)
LAN COMMUNICATION
PARAMETER ERROR
1
Sub
Code
1007
Meaning
4000
7200
7500
Cause Remedy
The check item number of SVC parameter is unmatched.
Software operation error occurred
Execution of the motion command does not complete within the specified time. (The last three digits expresses the command code.)
Software operation error occurred
Software operation error occurred
Interpolation cycle is shorter than the set value.
(The last digit expresses the physical axis of the alarm occurrence.)
Setting error of the NSRCH instruction direct-in number.
Setting error
The temperature rises in the controller
Connection failure
(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).
(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).
(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).
More than 4 direct in numbers are specified at time under the NSRCH instruction. Confirm its direct-in setting value.
Turn the power OFF then back ON after cooling down inside of the controller.
The communication error slot
(Serial-bus-connected Option module communication station
No.) is displayed by the bit.
0: correct / 1: incorrect
Module failure
(converter)
Connection failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting state of the following cables.
·The power cables of the cooling fan inside of the converter unit.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the connecting or inserting state of the followings.
·Option modules of the corresponding slot.
·Option module cables of the corresponding slot.
Incorrect setting of the IP address which is used in the Ethernet function.
IO module failure
Power supply broken
Main CPU board broken
Setting error
Replace the I/O module of the corresponding station number.
Replace the 24V power supply supplied to the I/O module of the corresponding station number.
Save the CMOS.BIN file.
Replace the Main CPU board, and then load the saved CMOS.BIN file.
(1)Check the following settings.
·IP address setting of network in maintenance mode
Alarm
Number
1221
Alarm Name
ETHERNET INITIAL
PROCESS ERROR
Sub
Code
2
Meaning
3
4
70
75
1
Cause
Incorrect setting of the subnet mask which is used in the
Ethernet function.
Incorrect setting of the default gateway which is used in the
Ethernet function.
Incorrect setting of the host address which is used in the
Ethernet function.
Setting error
Setting error
Setting error
Incorrect setting of the host name which is used in the Ethernet function.
Setting error
Setting error Incorrect setting of the domain which is used in the Ethernet function.
An error occurred in the device initialization process of the
Ethernet function.
Software operation error occurred
2
Main CPU board failure
Setting error
3
An error occurred in the IP address setting process of the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the subnet mask setting process of the
Ethernet function.
Setting error
Software operation error occurred
Remedy
(1)Check the following settings.
·Subnet mask of network in maintenance mode
(1)Check the following settings.
·Default gateway of network in maintenance mode
(1)Check the following settings.
·Server (host) of network in maintenance mode
(1)Check the following settings.
·Host name of network in maintenance mode
(1)Check the following settings.
·Domain name of network in maintenance mode
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·IP address setting of network in maintenance mode
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·Subnet mask of network in maintenance mode
(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).
Alarm
Number
Alarm Name
Sub
Code
Meaning
4
Cause
Main CPU board failure
An error occurred in the default gateway setting process of the
Ethernet function.
Setting error
Software operation error occurred
5
6
20
21
An error occurred in the host name setting process of the
Ethernet function.
Main CPU board failure
Setting error
Software operation error occurred
An error occurred in the MAC address getting process of the
Ethernet function.
Main CPU board failure
Software operation error occurred
An error occurred in the Web server task creating process of the Ethernet function.
Main CPU board failure
Software operation error occurred
An error occurred in the FTP server task creating process of the Ethernet function.
Main CPU board failure
Software operation error occurred
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·Default gateway of network in maintenance mode
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·Server (host) of network in maintenance mode
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
Alarm
Number
Alarm Name
1301 COMMUNICATION
ERROR (SERVO)
Sub
Code
Meaning
22
Cause
Main CPU board failure
An error occurred in the FTP client task creating process of the
Ethernet function.
Software operation error occurred
Main CPU board failure
30
50
51
0
An error occurred in the semaphore generation process for access exclusion of the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the Web server task management ID getting process of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the FTP server task management ID getting process of the Ethernet function.
Software operation error occurred
Main CPU board failure
Communication status error Connection failure
Remedy
Module failure (converter)
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
1
2
3
Meaning
Watchdog timer error
JL0101 alarm
Communication status error
Cause Remedy
Main CPU board failure
Connection failure
Module failure (converter)
Servo control board failure
Main CPU board failure
Connection failure
Module failure (converter)
Servo control board failure
Main CPU board failure
Connection failure
Module failure (converter)
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1303
Alarm Name
ARITHMETIC ERROR
(SERVO)
Sub
Code
Meaning
4
Cause Remedy
Data consistency error
Main CPU board failure
Connection failure
Module failure
(converter)
Servo control board failure
Main CPU board failure
Software operation error occurred
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Check the following settings.
Reexamine the tool file setting.
(Check the units of mass and center of gravity, positive/negative signs.)
The data [X____] indicates the generation process.
10000: Observer control
20000: High-precision path control
30000: Dynamics
40000: Disturbance observer control
50000: Dislocation detect
The data [_YYY_] indicates the alarm contents.
The data [____Z] indicates the physical axis number.
Tool file setting error
Software operation error occurred
(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).
Alarm
Number
Alarm Name
1306 AMPLIFIER TYPE
MISMATCH
1307 ENCODER TYPE
MISMATCH
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Motor load error
Setting error
Connection failure
Module failure (amplifier)
Servo control board failure
Setting error
Connection failure
Module failure (encoder)
Servo control board failure
Software operation error occurred
(1)Check the followings.
Overload is applied to the manipulator. Correct the tools, the work pieces, and the drive condition.
(1)Check the following settings.
·Check the current capacity of the amplifier before/after replacement by the model described in board.
·When the external axis is mounted, check if there is no difference between the amplifier selected at configuration and practically mounted one.
Reference parameter: from SVPxG232
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·Check the motor type before and after the replacement.
·When the external axis is mounted, check if there is no difference between the motor selected at configuration and the motor that is actually mounted.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
Alarm
Number
1308
1311
1325
Alarm Name
CONVERTER TYPE
MISMATCH
A/D DETECTION
ERROR (CONVERTER)
COMMUNICATION
ERROR (ENCODER)
Sub
Code
Meaning
Sub Code: Signifies the converter physical number in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause
Sub Code: Signifies the converter in which the alarm occurred
Setting error
Connection failure
Module failure (converter)
Servo control board failure
Software operation error occurred
Module failure (converter)
Connection failure
Module failure (encoder)
Servo control board failure
Remedy
(1)Check the following settings.
·Check the current capacity of the amplifier before/after replacement by the model described in board.
·When the external axis is mounted, check if there is no difference between the amplifier selected at configuration and practically mounted one.
Reference parameter: from SVCxB025
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1326
Alarm Name
DEFECTIVE ENCODER
ABSOLUTE DATA
Sub
Code
1327 ENCODER OVER
SPEED
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause
Connection failure
Module failure (encoder)
Servo control board failure
External environment
Connection failure
Encoder failure
Servo control board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder.
(1)Check the following settings.
Replace the defective motor (encoder).
·Check the position after the alarm.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·Check the grounding condition of Manipulator.
·Check whether it is installed into the strong magnetic field.
·Check the position after the alarm.
(1)Turn the power OFF then back ON.
(2)Turn the servo OFF where the axis does not fall off while turning ON the servo.
(3)Replace the battery of the alarm occurring axis if the alarm and encoder back-up error occur again.
(4)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder
Replace the defective motor (encoder).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1328
Alarm Name
DEFECTIVE ENCODER
Sub
Code
1329
1330
1349
1352
DEFECTIVE SERIAL
ENCODER COMMAND
MICRO PROGRAM
TRANSMIT ERROR
POWER LOST
DETECTION
(SERVO)
SERIAL ENCODER
CORRECTION ERROR
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause
Connection failure
Module failure (encoder)
Servo control board failure
Connection failure
Module failure (encoder)
Servo control board failure
Servo control board failure
Instant power failure
Sub Code: Signifies the axis in which the alarm occurred
Connection failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check if the primary power supply voltage is dropping.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder.
Alarm
Number
Alarm Name
1355 SERIAL ENC
MULTITURN LIMIT
ERROR
1400 ENCODER ERROR
(CONVEYOR)
Sub
Code
Meaning
1
Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
An error occurred at conveyor encoder 1.
Connection failure
Module failure
(encoder)
Servo control board failure
Connection failure
Connection failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connection and insertion of the following cables and connectors.
{Robot axis}
·Cable between encoders
·EAXA-CN508
{External axis}
·Cable between encoders
·EAXB-CN0534,535,536
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connecting or inserting state of the following cables.
{Robot axis}
·Cables between the controller and the encoder.
{External axis}
·Cables between the controller and the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, check the connection and insertion of the following cables and connectors.
{Robot axis}
·Cable between encoders
·EAXA-CN508
{External axis}
·Cable between encoders
·EAXB-CN0534,535,536
Module failure
(encoder)
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the encoder.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Cable (defect), Module failure
(encoder)
Replace the encoder cable or encoder of the conveyor encoder 1.
1401
1402
1403
1404
1405
1406
1407
1512
Alarm
Number
1513
Alarm Name
CANNOT CHANGE
CONVEYOR MODE
WORK IN/NOT DATA
CNT. LMT. OVER
WORK IN/NOT SHIFT
DATA POS LMT.
WORK ID. DATA CNT.
LMT. OVER
WORK ID. SHIFT DATA
POS LMT.
START SHIFT DATA
CNT. LMT. OVER
START SHIFT DATA POS
LMT.
POWER SUPPLY FAN
ERROR
(SERVO)
POWER SUPPLY
OVERHEAT
(SERVO)
Sub
Code
2
Meaning
3
An error occurred at conveyor encoder 2.
An error occurred at conveyor encoder 3.
Cause Remedy
Cable (defect), Module failure
(encoder)
Replace the encoder cable or encoder of the conveyor encoder 2.
Cable (defect), Module failure
(encoder)
Replace the encoder cable or encoder of the conveyor encoder 3.
Input error
Work status error
Do not switch "Encoder / Virtual encoder" with the general signal while performing the conveyor synchronized function.
Check the work in/not shift data and actual the work status within the shift area.
Work status error
Work status error
Work status error
Check the work in/not shift data and actual the work status within the shift area.
Check the work in/not shift data and actual the work status within the shift area.
Check the work in/not shift data and actual the work status within the shift area.
Work status error
Work status error
Check the work in/not shift data and actual the work status within the shift area.
Check the work in/not shift data and actual the work status within the shift area.
Connection failure
Module failure
(converter)
Air inlet and exhaust
The temperature rises in the controller
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check that the air inlet or outlet is not blocked.
Turn the power OFF then back ON after cooling the controller.
Connection failure
Module failure
(converter)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1514
1547
1650
Alarm Name
OVERHEAT
(AMPLIFIER)
CURRENT FEEDBACK
ERROR
FILE TRANSFER DATA
ERROR (SV)
1
Sub
Code
Meaning Cause Remedy
•
The data [XXX_] indicates the
alarm contents.
•
2000:Error in current detection
value
•
The data [___Y] indicates the
physical axis number.
The temperature of amplifier rose.
Connection failure
Turn the power OFF then back ON after cooling the amplifier.
Servo control board failure
Connection failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check if a ground fault has not occurred in the U-, V-, and W-phase of motor power line, or short circuit has not occurred between these phases.
Connection failure
Module failure
(amplifier)
Module failure
(motor)
Servo control board failure
An error occurred when the last data was not received during the first data communication at execution of motion command.
Software operation error occurred
Servo control board failure
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the motor.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1651
1652
1653
Alarm Name
FILE TRANSFER DATA
SIZE ERRORERROR
(SV)
1
2
DB ON ERROR (SERVO)
BASE BLOCK SIGNAL
ERROR
(SERVO)
Sub
Code
Meaning
2
3
Cause Remedy
An error occurred when the first data was not received during on the way data communication at execution of motion command.
Main CPU board failure
Servo control board failure
An error occurred when the first data was not received during the last data communication at execution of motion command.
Servo control board failure
The data size for the file transfer does not agree with the received buffer size.
Buffer size over
Servo control board failure
Servo control board failure
Servo control board failure
Software operation error occurred
Servo control board failure
Software operation error occurred
Module failure (amplifier)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1654
Alarm Name
PG POWER ON
MULTIPLE REQ (SV)
1655
1656
1657
CONVERTER
COMMAND ERROR (SV)
AXIS ENDLESS INFO
NOT GENERATED(SV)
AXIS ENDLESS
SPECIFIC. ERROR
(SV)
Sub
Code
1
2
3
Meaning Cause
Setting error
Software operation error occurred
Setting error
The home position detecting function was used for the axis for which the axis endless function was enabled.
The home position detecting function cannot be used for the axis which the axis endless function was enabled.
The servo float function was used for the axis for which the axis endless function was enabled.
The servo float function cannot be used for the axis which the axis endless function was enabled.
Setting error
Setting error
The encoders manufactured by
Tamagawa Seiki Co., Ltd. was used for the axis for which the axis endless function was enabled.
The encoders manufactured by
Tamagawa Seiki Co., Ltd. cannot be used for the axis which the axis endless function was enabled.
Setting 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).
(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).
Check the JOB.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Disable either the axis endless function or the home position detection function of corresponding axis.
Disable either the axis endless function or the servo float function of corresponding axis.
Disable the corresponding axis endless function.
Alarm
Number
1658
1664
Alarm Name
REDUCTION STOP
SPECIFIC. ERROR
(SV)
MICRO PRG EXECUTE
TIME OVER(SV)
Sub
Code
4
Meaning
1
2
Cause
The general servo function was used for the axis for which the axis endless function was enabled.
The general servo function cannot be used for the axis which the axis endless function was enabled.
Setting error
The servo float function was used for the axis for which the deceleration stop function was enabled.
The servo float function cannot be used for the axis which the deceleration stop function was enabled.
Setting error
The specified axis speed control function was executed for the axis which the deceleration stop function was enabled.
Specified axis speed control function cannot be used for the axis which the deceleration stop function was enabled.
Setting error
Sub code: specifies the axis that alarm occurred.
Servo control board failure
1665
1666
1667
MICRO PROGRAM
SYNC. ERROR (SV)
FILE RECEIVE
INCOMPLETE (SERVO)
RESOLUTION
CONVERSE CONST
ERROR
(SV)
Remedy
Disable the corresponding axis endless function.
Check the JOB.
Check the JOB.
Sub code: specifies the axis that alarm occurred.
Servo control board failure
Sub code: specifies the axis that alarm occurred.
Servo control board failure
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1674
Alarm Name
CTRL LAW SWITCHING
ORDER ERROR (SV)
Sub
Code
1684
1685
1686
1831
1832
INSTANT POWER
FAILURE
(TRQ)(SV)
INSTANT POWER
FAILURE
(TIME)(SV)
POS.DEVITATION
SATURATING ERROR
(SV)
HWBB FB ERROR
(PLD2)
ESP_OUT FB ERROR
(PLD1)
Meaning Cause
Sub code: specifies the axis that alarm occurred.
Servo control board failure
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check if the primary power supply voltage is dropping.
The instant power failure occurred and then the torque was saturated.
Voltage failure
The instant power failure occurred for longer than the certain time period.
Power failure
Voltage failure
Power failure
Setting error
Check if the instant power failure has occurred.
Check if the primary power supply voltage is dropping.
Check if the instant power failure has occurred.
Check the settings for manipulator motion condition (influence by external force, load condition).
Connection failure
Connection failure
Module failure (motor)
Servo control board failure
Check if a ground fault has not occurred in the U-, V-, and W-phase of motor power line, or short circuit has not occurred between these phases.
Check the connection of motor power line.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the motor.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Module failure
(amplifier)
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
1833
Alarm Name
ESP_OUT FB ERROR
(PLD2)
Sub
Code
Meaning
1834
1835
1836
M-SAFETY WATCHDOG
ERROR (PLD1)
M-SAFETY WATCHDOG
ERROR (PLD2)
M-SAFETY WATCHDOG
ERROR (PLD3)
1837 M-SAFETY 24V POWER
SUPPLY ERROR
1838 M-SAFETY DC 24V
FUSE BROKEN
Cause Remedy
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Main CPU board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Software operation error occurred
Connection failure
(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).
(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).
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Ground fault or a short circuit (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Blown fuse (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Ground fault or a short circuit (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
1839 M-SAFETY 5V POWER
SUPPLY ERROR
1840
1841
M-SAFETY 3.3V LOW
VOLTAGE
COMMUNICATION
ERROR
(LOOP BACK)
4000 MEMORY ERROR
(TOOL FILE)
4001 MEMORY ERROR
(USER COORD FILE)
Sub
Code
Meaning
Sub Code: Tool number
Sub Code: User coordinate number
Cause Remedy
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Blown fuse (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Machine safety board failure (1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Connection failure
Servo control board failure
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Servo control board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4002
Alarm Name
MEMORY ERROR
(SV MON SIGNAL FILE)
Sub
Code
4004 MEMORY ERROR
(HOME POS FILE)
4005 MEMORY ERROR
(SECOND HOME POS)
4012 MEMORY ERROR
(LINK SERVOFLOAT)
4013 MEMORY ERROR
(LINEAR SERVOFLOAT)
Meaning Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Sub Code: Condition file number Data error
Main CPU board failure
Sub Code: Condition file number Data error
Main CPU board failure
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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4014
Alarm Name
MEMORY ERROR
(ROBOT CALIB FILE)
Sub
Code
Meaning
Sub Code: Page number
4018 MEMORY ERROR
(LADDER PRG FILE)
4020 MEMORY ERROR
(OPERATION ORIGIN)
4021 MEMORY ERROR
(CONVEYOR COND
FILE)
4022 MEMORY ERROR
(PAINT SPECIAL FILE)
4023 MEMORY ERROR
(PAINT COND FILE)
Sub Code: Page number
Sub Code: Page number
Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
Alarm
Number
Alarm Name
4025 MEMORY ERROR
(INTERRUPT JOB FILE)
4028 MEMORY ERROR
(SENSOR MON COND
FILE)
4034 MEMORY ERROR
(ANTICIPATION OT FILE)
4035 MEMORY ERROR
(ANTICIPATION OG
FILE)
4039 MEMORY ERROR
(FORM CUT FILE)
Sub
Code
Meaning
Sub Code: File number
Cause
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Remedy
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4040
Alarm Name
MEMORY ERROR
(SHOCK LEVEL FILE)
4042 MEMORY ERROR
(VISION FILE)
4043 MEMORY ERROR
(VISION CALIBRATION)
4046 MEMORY ERROR
(CONVEYOR CALIB
FILE)
4047 MEMORY ERROR
(MACRO DEFINITION
FILE)
4050 MEMORY ERROR
(AXIS I/O ALLOC FILE)
Sub
Code
Meaning
Sub Code: File number
Sub Code: Page number
Sub Code: Page number
Sub Code: File number
Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
Alarm
Number
Alarm Name
4051 MEMORY ERROR
(GUN COND. AUX. FILE)
4052 MEMORY ERROR
(TOOL INTERFERENCE)
Sub Code: File number
4063 MEMORY ERROR
(CONVEYOR COND
SUPP.)
4065 MEMORY ERROR
(I/F PANEL FILE)
4072 MEMORY ERROR
(LASER TRACKING
TRACK START FILE)
Sub
Code
Meaning
Sub Code: File number
Sub Code: File number
Cause
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Data error
Main CPU board failure
Remedy
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4074
Alarm Name
MEMORY ERROR
(LASER TRACKING
TRACK SET FILE)
4075 MEMORY ERROR
(CONDITION
FILE OF
CORRESPONDING TO
LASER TRACKING GAP)
4099 DC 24V POWER
SUPPLY FAILURE
4103 PARALLEL START
INSTRUCTION ERROR
1
2
3
Sub
Code
4
Meaning Cause
Data error
Main CPU board failure
Data error
Main CPU board failure
Power supply failure
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.
Setting error
Group axis being used:
The job operated by another sub task uses the same group axis.
Setting error
Multiple start of same job:
The job that was tried to be started was executed by another sub task.
Unregistered master job:
Although the master job was not registered, an attempt was made to execute PSTART SUB (job name omitted).
Setting error
Setting error
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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·The subtask is completed by the PWAIT instruction.
(1)Check the following settings.
·The job to be started
·The execution timing for start command
(1)Check the following settings.
·The same job is not used in the another task
(1)Check the following settings.
·The master job of the subtask is registered
Alarm
Number
Alarm Name
Sub
Code
5
Meaning
6
7
8
9
Cause
Synchronization instruction error:
When restarted by PSTART, synchronization instruction status of the sub task under interruption was different from the status to restart.
Stopped by an alarm:
An attempt was made to start the sub task which is stopped by an alarm.
Setting error
Setting error
Synchronization task specification of SYNC instruction omit error
Setting error
The task is specified by synchronization task of SYNC instruction.
I/O jog being executed
Setting error
Setting error
10 Separate group axis being used Setting error
11 The servo power supply is OFF.
Setting error
4104
4105
WRONG EXECUTION
OF LOAD INST
WRONG EXECUTION
OF SAVE INST
12
16
17
Twin synchronous task ID error
PSTART instruction is the old specification.
Setting error
Setting error
PWAIT instruction is the old specification.
Setting error
Sub Code1 to 245: Signifies the data transmission error.
Sub Code1 to 245: Signifies the data transmission error.
Setting error
Setting error
Remedy
(1)Check the following settings.
·The job to be started
·The execution timing for start command
(1)Check the following settings.
·Alarm occurrence status
(1)Check the following settings.
·Synchronization task specification of SYNC instruction
(1)Check the following settings.
·Synchronization task specification of SYNC instruction
(1)Check the following settings.
·I/O jog executing status
Complete the I/O jog executing status, and then restart.
(1)Check the following settings.
·Usage status of separation use axis
Complete the use of separation use axis, and then restart.
(1)Check the following settings.
·Servo power
Turn ON servo power.
(1)Check the following settings.
·Twin synchronous task specification of SYNC instruction
(1)Check the following settings.
·The specifications of PSTART instruction
Register the PSTART instruction as new specification.
(1)Check the following settings.
·The specifications of PWAIT instruction
Register the PWAIT instruction as new specification.
* Refer to the instruction manual for Data Transmission Function for details.
* Refer to the instruction manual for Data Transmission Function for details.
Alarm
Number
4106
Alarm Name
4107
WRONG EXECUTION
OF DELETE INST
OUT OF RANGE
(ABSO DATA)
Sub
Code
Meaning Cause
Sub Code1 to 245: Signifies the data transmission error.
Sub Code: Signifies the axis in which the alarm occurred
Setting error
Setting error
4112 DATA SENDING ERROR 1 Retry over of NAK Communication error
4113 DATA RECEIVING
ERROR
1
2
2
3
3
Retry over for timeout in timer A Communication error
Retry over for mutual response error
Communication error
Reception timeout (timer A) Communication error
Reception timeout (timer B)
Heading length is too short.
Communication error
Setting error
4 Heading length is too long.
Setting error
5 The header No. error Setting error
6 The text length exceeded 256 characters.
Setting error
Remedy
* Refer to the instruction manual for Data Transmission Function for details.
(1)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).
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(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.
(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.
(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.
(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.
Alarm
Number
Alarm Name
Sub
Code
7
Meaning
Illegal data received
Cause
Setting error
4114 TRANSMISSION
HARDWARE ERROR
1
2
3
4115
4116
TRANSMISSION
SYSTEM BLOCK
TRANSMISSION
SYSTEM ERROR
Overrun error
Parity error
Framing error
Communication error
Communication error
Communication error
4
5
1
Transmission timeout (timer A)
Transmission timeout (timer B)
Communication error
Communication error
Received EOT while waiting ACK. Communication error
2
3
4
1
100
Received EOT while waiting ENQ. Communication error
Received EOT before last block reception.
Communication error
Received codes other than EOT after last block reception.
Communication error
Transmission data contents error Communication error
Trans error or protocol error Communication 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.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the communication setting and communication wiring is correct.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
(1)Reset the alarm.
(2)If the alarm occurs again, check the setting of communication or transmission side data is correctly set.
Alarm
Number
4117
Alarm Name
BRAKE POWER ERROR
Sub
Code
Meaning
Sub Code: XY
X : Servo control board(SV#X)
Y : Power-ON unit(TU#Y)
Cause
Connection failure
Fuse failure
4119 FAN ERROR
(IN CONTROL BOX)
4121 COOLING FAN1 ERROR
4122 COOLING FAN2 ERROR
4124 WRONG EXECUTION
OF VISION INST
1
2
3
Sub Code 1 to 4: Signifies the
Converter unit No. in which the alarm occurred
Cooling fan failure
Sub Code: Signifies the Servo control board No. in which the alarm occurred
Sub Code: Signifies the Servo control board No. in which the alarm occurred
The specified file number is incorrect.
Cooling fan failure
Cooling fan failure
Setting error
The specified file set value is incorrect.
Setting error
Calibration could not be executed. Setting error
4 The communication port for the vision system could not be initialized.
Setting error
Connection failure
Remedy
(1)Reset the alarm.
(2)If the alarm occurs again, check the brake connection if there is a ground fault or short circuit.
(1)Reset the alarm.
(2)If the alarm occurs again, turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Replace the cooling fan of manipulator.
Check the wiring from a manipulator to a servo control board.
* Move the manipulator to the safe position in the teach mode.
Replace the cooling fan of manipulator.
Check the wiring from a manipulator to a servo control board.
* Move the manipulator to the safe position in the teach mode.
(1)Check the following settings.
·File No.
Specify the correct file number.
(1)Check the following settings.
·File set value
Specify the set value.
(1)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.
Set the user variable number in the calibration file.
(1)Check the following settings.
·The Parameter for communication port
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection of the following cables.
·Cable between vision system and FS100 system
Alarm
Number
Alarm Name
6
7
8
9
10
11
12
Sub
Code
5
Meaning
Time-out occurred during data transmission.
Cause
Setting error
Connection failure
Time-out occurred during data reception.
Setting error
Connection failure
The data received from the vision system is incorrect.
Setting error
Connection failure
The pixel coordinates value was not able to be converted into the robot coordinates.
Setting error
Failed to read or write the position type variable (P variable).
Setting error
Use memory is lacking and the area could not be obtained.
Software operation error occurred
The setting value of measurement item (FT) is incorrect.
The data for the vision execution command is incorrect.
Software operation error occurred
Remedy
(1)Check the following settings.
·The communication setting of vision system
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection of the following cables.
·Cable between vision system and FS100 system
(1)Check the following settings.
·The communication setting of vision system
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection of the following cables.
·Cable between vision system and FS100 system
(1)Check the following settings.
·The communication setting of vision system
·The detection setting of vision system
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection of the following cables.
·Cable between vision system and FS100 system
(1)Check the following settings.
·The communication setting of vision system
·Calibration file for use
(1)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.
(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).
Correct the setting value of a measurement item.
(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).
Alarm
Number
4126
Alarm Name
CANNOT EXECUTE
AUTO PMT
1
Sub
Code
48
2
3
4
5
6
7
Meaning
The number of waiting commands sent by Vision sensor exceeded the limit.
Software operation error occurred
System error
PBOX cannot be edited.
The source job is not exist.
Cause
Software operation error occurred
Setting error
The source job cannot be edited.
Setting error
The converted job cannot be edited.
Setting error
The memory area for job area is insufficient.
Software operation error occurred
Setting error
The memory area for position data of the job is insufficient.
Software operation error occurred
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).
(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).
(1)Check the following settings.
·I/O status of the edit prohibit signal
The edit prohibit signal cannot input.
(1)Check the following settings.
·The prohibit status of source job
If the source job is protected from editing, it cannot be edited.
(1)Check the following settings.
·The prohibit status of converted job
If the converted job is protected from editing, it cannot be edited.
(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 job.
(4)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Presence of the specified source job
The job which does not exist cannot be set to the source job.
(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 unuse
(4)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4127
4129
4130
Alarm Name
U-AXIS TIMING BELT
BLOWN
TWIN DRIVE OUT OF
RANGE
(START)
NETWORK
APPLICATION
PROCESS ERROR
1
Sub
Code
8
2
3
4
Meaning
The job under execution is specified as the conversion job.
Cause
Setting error
Sub Code: XY
X : Servo control board(SV#X)
Y : Power-ON unit(TU#Y)
Sub Code: Corresponding master-axes and slave-axes are displayed by the bit.
Belt blown
Setting error
An error occurred when the notification of the APP task reinitialization was processed in the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred when the reinitialization response was received in the Ethernet function.
Software operation error occurred
Main CPU board failure
The incomplete task of re-initialization was unsuccessfully completed in the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred when the semaphore for re-initialization was received in the Ethernet function.
Software operation error occurred
Main CPU board failure
Remedy
(1)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.
Replace the timing belt of the manipulator.
Check the connection between manipulator and Servo control board.
*Move the manipulator to safety place in teach mode.
(1)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 masteraxes and the slave-axes is settled within allowable range.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
Alarm Name
Sub
Code
5
Meaning Cause
An error occurred when the reinitialization mail was sent in the
Ethernet function.
Software operation error occurred
6
7
8
9
30
Main CPU board failure
An error occurred in the exclusive process of the storage area control table of the Ethernet function.
Software operation error occurred
Main CPU board failure
Time-out occurred in the reinitialization response receiving process of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the reinitialization response receiving process of the Ethernet function.
Software operation error occurred
Main CPU board failure
Receiving data size error occurred in the re-initialization response receiving process of the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the Web server task mail receiving process of the Ethernet function.
Software operation error occurred
Main CPU board failure
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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
Alarm Name
Sub
Code
31
Meaning Cause
An error occurred in the FTP server task mail receiving process of the Ethernet function.
Software operation error occurred
32
40
41
42
50
Main CPU board failure
An error occurred in the FTP client task mail receiving process of the Ethernet function.
Software operation error occurred
Main CPU board failure
Illegal e-mail data were received in the Web server task of the
Ethernet function.
Software operation error occurred
Main CPU board failure
Illegal e-mail data were received in the FTP server task of the
Ethernet function.
Software operation error occurred
Main CPU board failure
Illegal e-mail data were received in the FTP client task of the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the data size written to PCI of the Ethernet function.
Software operation error occurred
Main CPU board failure
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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
Alarm Name
Sub
Code
51
Meaning Cause
An error occurred when the request to write PCI data was received in the Ethernet function.
Software operation error occurred
52
53
54
55
100
Main CPU board failure
The request of the undefined transmission was received in the
Ethernet function.
Software operation error occurred
An error occurred in the transmission request of the
Ethernet function.
Main CPU board failure
Software operation error occurred
Main CPU board failure
The transmission request without data was received in the Ethernet function.
Software operation error occurred
Main CPU board failure
The transmission request of illegal data length was received in the
Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in storing process of memory which is used in the Ethernet function.
Software operation error occurred
Main CPU board failure
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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
4131
Alarm Name
Sub
Code
101
Meaning Cause
An error occurred in the buffer for request to write PCI getting process of the Ethernet function.
Software operation error occurred
200
201
UDP PROCESS ERROR 1
2
3
Main CPU board failure
The socket of the Ethernet function was full and was not able to create a socket.
Software operation error occurred
Main CPU board failure
An error occurred in the semaphore of socket control table of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the creation of receiving socket during the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the creation of transmission socket during the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
Illegal data were received in the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
Alarm Name
Sub
Code
4
Meaning Cause
Transmission error occurred in the
UDP process of the Ethernet function.
Software operation error occurred
5
100
101
102
103
Main CPU board failure
The SELECT operation was not successfully completed in the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
The re-initialization notification of illegal data length was received in the UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
The re-initialization notification of illegal data was received in the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
The PCI write process was not successfully completed in the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
The transmission request of illegal data length was received in the
UDP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
4132
4134
Alarm Name
COOLING FAN SET
ABNORMAL
Sub
Code
104
Meaning Cause
The transmission request of illegal data was received in the UDP process of the Ethernet function.
Software operation error occurred
TCP PROCESS ERROR 1
2
3
4
0
Main CPU board failure
The socket table was not successfully created in the TCP process of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in the process of the TCP server initialization of the Ethernet function.
Software operation error occurred
Main CPU board failure
An error occurred in connection detecting process of TCP server of the Ethernet function.
Software operation error occurred
An error occurred in the connection detection checking process of TCP server of the
Ethernet function.
Main CPU board failure
Software operation error occurred
Main CPU board failure
Setting error
4137 WRONG EXECUTION
OF SETUALM INST
1 Alarm code specification error Setting 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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(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).
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)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.
(1)Check the following settings.
·Alarm code
Specify the alarm in the range 8000 to 8999.
Alarm
Number
Alarm Name
4138 WRONG EXECUTION
OF SVON INST
4139 WRONG EXECUTION
OF PRINT INST
Sub
Code
2
Meaning
Task specification error
3
Cause
Setting error
Motion mode specification error Setting error
Connection failure
Setting error
Setting error
4140 WRONG EXECUTION
OF DIALOG INST
1
2
3
4144 FIELDBUS BOARD
STATUS ERROR
DIALOG instruction control error Setting error
Messages and buttons are not registered.
Buttons are not registered.
Setting error
Setting error
In fieldbus board slot is displayed in the sub-code, any board error, communication error (it detects communication error), or Uncommunicating slave (it detects the slave station can not communicate) occurs.
Setting error
Remedy
(1)Check the following settings.
·Task specification
Specify the task in the range 0 to 4 (7 at expansion).
(1)Check the following settings.
·Motion mode specification
Set the motion mode to 0 or 1.
(1)Check the following settings.
·Short-circuit the external servo ON (EXSVON) of MXT terminal block.
(1)Check the following settings.
·The concurrent I/O signal #80031 (servo ON condition1) ON
·The concurrent I/O signal #80033 (servo ON condition2) ON
(1)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.
(1)Check the following settings.
·The tag setting of DIALOG instruction
If no fault is found, delete corresponding DIALOG instruction, and then register again.
(1)Check the following settings.
·The information of DIALOG instruction message and button
(1)Check the following settings.
·The information of DIALOG instruction button
(1)Check the following settings.
・ Check the IO module configuration of the corresponding fieldbus board in maintenance mode.
・ Check the switch settings on the corresponding fieldbus board.
・ Check the settings of the device to communicate with the corresponding fieldbus board.
Alarm
Number
4152
4200
4201
Alarm Name
TIMING BELT BLOWN
SYSTEM ERROR
(FILE DATA)
SYSTEM ERROR
(JOB)
Sub
Code
-1
-3
Meaning Cause
Connection failure
Main CPU board failure
Servo control board number
(SV#) from which an error was detected.
Sub code 01 to 50: Signifies the internal software error
Manipulator timing belt is blown.
Data error
An error occurred during the access to a job in parameter specifications.
Fieldbus board failure
Software operation error occurred
Main CPU board failure
The access to a job could not be performed with the specified job name.
Software operation error occurred
Main CPU board failure
Remedy
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
・ Communication connector and communication cable of the corresponding fieldbus board.
・ Communication connector and communication cable of the device that communicates with corresponding fieldbus board.
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the following board. Save the CMOS.BIN before replace the board to be safe.
・ Corresponding fieldbus board
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace the CPU-201R board.
Move the manipulator in teach mode to the position where there is no torque on the driving belt.
(1) Check the timing belt tension.
(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.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
-5
-6
-7
Sub
Code
-4
Meaning Cause
A job was newly created with the same name of the job already specified in the memory.
Software operation error occurred
Main CPU board failure
-8
-9
A job was newly created with the same name of the job already specified in the memory.
Software operation error occurred
Main CPU board failure
The allowable job registration area (memory) was exceeded.
A job that did not exist in the memory was specified.
Setting error
Software operation error occurred
Main CPU board failure
An attempt was made to change the contents for the job prohibited from being edited.
Setting error
An error occurred during the access to a job in handle value.
Software operation error occurred
Main CPU board failure
-10 An error occurred in job data control system.
Software operation error 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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·Delete unused jobs.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·Release the prohibition.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
Alarm
Number
Alarm Name
Sub
Code
-11
Meaning Cause
Main CPU board failure
An error occurred in sequence number of the accessed job.
Software operation error occurred
Main CPU board failure
-12 An error occurred in step number of the accessed job.
Software operation error occurred
Main CPU board failure
-13 A job specified at job search did not exist in the memory.
Software operation error occurred
Main CPU board failure
-16 Unused handles were lacking when an attempt was made to open a job.
Software operation error occurred
Main CPU board failure
-18
-19
The number of instructions added to a job exceeded 9999.
Setting error
The number of steps added to a job exceeded 999.
Setting error
Remedy
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check the following settings.
·Delete unnecessary instructions and add new instructions again.
(1)Check the following settings.
Delete unnecessary steps and add new steps again.
Alarm
Number
Alarm Name
Sub
Code
-22
-23
-24
-25
-26
Meaning Cause
Job information was not able to be expanded.
Software operation error occurred
Job information was not able to be acquired.
Software operation error occurred
An error occurred in cluster control.
Failed to read the cluster information.
Main CPU board failure
Main CPU board failure
Software operation error occurred
Main CPU board failure
Software operation error occurred
Main CPU board failure
Heap area could not be obtained.
Software operation error occurred
Main CPU board failure
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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4202
Alarm Name
Sub
Code
-90
-91
-92
SYSTEM ERROR (JOB) 1
2
Meaning
The configuration data is damaged.
The FAT area is damaged.
Cause
Software operation error occurred
Main CPU board failure
Software operation error occurred
Main CPU board failure
A job data in the memory was destroyed.
Software operation error occurred
Main CPU board failure
An error occurred in parameter specifications for the access to a job.
Software operation error occurred
Access time exceeded the limit during the access to a job.
Software operation error 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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
3
Meaning Cause
Unapproved characters are used for a job name.
Software operation error occurred
4
5
6
7
8
A job was newly created with the same name of the job already specified in the memory.
Software operation error occurred
A job was newly created with the same name of the job already specified in the memory.
Software operation error occurred
The allowable job registration area (memory) was exceeded.
Software operation error occurred
A job that did not exist in the memory was specified.
Software operation error occurred
An attempt was made to change the contents for the job prohibited from being edited.
Setting error
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 job.
(4)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Setting of EDIT LOCK in JOB header screen
If the job is protected from editing, release the prohibition.
Alarm
Number
Alarm Name
Sub
Code
9
10
11
Meaning Cause
Software operation error occurred
An attempt was made to change the contents for the job prohibited from being edited.
Setting error
Software operation error occurred
An error occurred in job data control system.
Software operation error occurred
An error occurred in sequence number of the accessed job.
Software operation error occurred
Remedy
(1)Reset the alarm.
(2)If you edit this job, release the prohibition.
(3)If the error occurs again, delete the job where the alarm occurred.
(4)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.
(5)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Setting of EDIT LOCK in JOB header screen
If the job is protected from editing, release the prohibition.
(1)Reset the alarm.
(2)If you edit this job, release the prohibition.
(3)If the error occurs again, delete the job where the alarm occurred.
(4)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.
(5)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
12
Meaning Cause
An error occurred in step number of the accessed job.
Software operation error occurred
13
14
16
18
A job specified at job search did not exist in the memory.
Software operation error occurred
There was an instruction that did not exist in a job because of inconsistency of the system software.
Software operation error occurred
Unused handles were lacking when an attempt was made to open a job.
Setting error
Software operation error occurred
The number of instructions added to a job exceeded 9999.
Setting error
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The number of call job stacks
Set the job configuration that decreases the number of call job stacks.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The number of steps in job
Delete unnecessary instructions in job and add new instructions.
Alarm
Number
Alarm Name
Sub
Code
19
20
22
23
Meaning
The accessed job was not opened.
Cause
Software operation error occurred
The number of steps added to a job exceeded 9999.
Setting error
Software operation error occurred
A job was newly created with the same name of the undefined job already specified in the memory.
Software operation error occurred
Failed to expand job information during the access to a job.
Software operation error occurred
Software operation error occurred
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The number of steps in job
Delete unnecessary steps in job and add new steps.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
24
Meaning Cause
An error occurred in the cluster control process of the accessed job.
Software operation error occurred
25
26
90
91
An error occurred when reading the cluster information of the accessed job.
Software operation error occurred
Failed to acquire the necessary memory area during the access to a job.
Software operation error occurred
The configuration information for job data control is damaged.
Software operation error occurred
The FAT information for job data is damaged.
Software operation error occurred
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
4203 SYSTEM ERROR
(POSITION DATA)
Sub
Code
92
99
-1
-3
-6
Meaning
A job data was destroyed.
A job data in the memory was destroyed.
Software operation error occurred
The number of axes for position data is zero.
Software operation error occurred
Unused position data file is destroyed.
Cause
Software operation error occurred
The memory area for position data is lacking at the initialization of the position data control process.
Software operation error occurred
Main CPU board failure
Main CPU board failure
Software operation error occurred
Main CPU board failure
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
-7
-8
-9
-10
-11
Meaning Cause
Unused position data file does not exist.
Software operation error occurred
Main CPU board failure
Position data file is destroyed.
Software operation error occurred
Main CPU board failure
Position data control information is destroyed.
Software operation error occurred
Main CPU board failure
An error occurred in specified position data number.
Software operation error occurred
Main CPU board failure
Position data is not registered.
Software operation error occurred
Main CPU board failure
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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
4204 SYSTEM ERROR
(POSITION DATA)
Sub
Code
-12
-13
-20
1
3
Meaning Cause
An attempt was made to access the undefined position data.
Software operation error occurred
An attempt was made to access the position data for the undefined control group.
Software operation error occurred
Main CPU board failure
Inconsistency of data.
Main CPU board failure
Software operation error occurred
Main CPU board failure
The number of axes for all the control groups is zero at the initialization of the position data control process
Software operation error occurred
The number of axes for position data is zero.
Software operation error 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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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).
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
6
7
8
9
10
Meaning
Unused position data file is destroyed.
Cause
Software operation error occurred
Unused position data file does not exist.
Setting error
Software operation error occurred
Position data file is destroyed.
Software operation error occurred
Position data control information is destroyed.
Software operation error occurred
An error occurred in specified position data number.
Software operation error occurred
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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The number of steps in job (position data)
Delete unnecessary position data in job and add new position data.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
11
12
13
17
20
Meaning
Position data is not registered.
Cause
Setting error
An attempt was made to access the undefined position data.
Software operation error occurred
An error occurred in exceptional control during the position data control process.
Software operation error occurred
Undefined position exists.
Software operation error occurred
An attempt was made to access the position data for the undefined control group.
Software operation error occurred
Software operation error occurred
Remedy
(1)Check the following settings.
·Teaching of alarm occurred point
Teaching the point where alarm occurred.
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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 alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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)f the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4206
Alarm Name
SYSTEM ERROR
(TRANSMISSION)
4207 SYSTEM ERROR
(MOTION)
Sub
Code
Meaning Cause
Sub Code 1 to 4: Signifies the internal software error during data transmission.
Software operation error occurred
1
2
3
4
5
6
7
8
An interrupt undefined in the main command from the system control section occurred.
Software operation error occurred
An interrupt undefined in the sub command from the system control section occurred.
Software operation error occurred
The interrupt command that was sent previously from the system control section is being processed.
An error was detected in the interrupt command data from the system control section.
Software operation error occurred
Software operation error occurred
An undefined command was detected in the sub segment task of MOTION section.
Software operation error occurred
An undefined command was detected in the servo-related processing of MOTION section.
Software operation error occurred
An undefined command was detected in the offline processing task of MOTION section.
Software operation error occurred
An undefined command was detected in the utility task of
MOTION section.
Software operation error occurred
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
10
11
12
14
15
16
18
19
20
Meaning
Task Token is not generated.
Mail-box Token is not generated.
Software operation error occurred
Semaphore Token is not generated.
RMS receiving data error
RMS sending data error
RMS receiving unit error
Task generation error
Mail-box generation error
Semaphore generation error
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
22
23
24
25
30
33
34
35
36
Meaning
TCB area overflow
Stack area overflow
Mail-box area overflow
Semaphore area overflow
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Interrupt main command error Software operation error occurred
Incorrect control group designation
Offline bank semaphore reception error
Software operation error occurred m_gen_area semaphore reception error
Software operation error occurred
Software operation error occurred
Offline HA processing timeout Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
37
38
39
40
45
46
47
48
49
Meaning
S -> M offline processing command type error
Cause
DM_BANK flag error (DM_BANK conversion processing)
Software operation error occurred
Function specification error in the data transmission to the sensor board
Software operation error occurred
Error in designation of application in the request of general-purpose data preset for each application.
Software operation error occurred
Mail-box of sequence task is not ready.
Software operation error occurred
Segment task polling command error
Software operation error occurred
Physical axis number error
Software operation error occurred
Control-group usage undefined Software operation error occurred
Software operation error occurred
The control group impossible to release the brake
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
50
51
52
53
54
55
56
57
Meaning
Sub-segment request FULL
Sub-segment process timeout Software operation error occurred
Data latch request FULL
Data latch process timeout
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
AXIS command request FULL Software operation error occurred
AXIS command process timeout Software operation error occurred
Positioning monitor request FULL Software operation error occurred
Positioning monitor process timeout
Software operation error occurred
Failed AXIS servo OFF command request during category1 emergency stop
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
59
Meaning Cause
AXIS servo OFF command execution system not set during category1 emergency stop
Software operation error occurred
61
62
63
64
66
67
68
69
Conversion primary expression for Power Source command <->
EW command not prepared
Software operation error occurred
Duplicated request error during master control-group tracking
Software operation error occurred
GVM shared resource semaphore error
Software operation error occurred
Job queue DEQUE error
Execution system decision table not set
Software operation error occurred
Unknown mode data (Without
TEACH/PLAY mode data)
Software operation error occurred
Shift-value output timeout of the general-purpose sensor
Software operation error occurred
Interrupt main status set
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
71
Meaning
72
73
75
79
80
81
82
83
No data link added to the command
Inner track zone status error
Cause
System number error at the master side in twin synchronous system
Software operation error occurred
Software operation error occurred
Setting status error of the user coordinates file
Software operation error occurred
Previous path data reference error
Software operation error occurred
Software operation error occurred
Instruction queue and instruction system data area overflow
Software operation error occurred
Offline answer bank flag error Software operation error occurred
Path and trace queue ENQUE
BANK error
Software operation error occurred
Pending and block end request
FULL
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
84
85
86
88
89
90
91
94
Meaning
Base axis file type error
Output buffer SYSCON for automatic test data in use
Cause
Software operation error occurred
Software operation error occurred
Conversion completion status for
AXIS section feedback latch data not established
Software operation error occurred
File C1 through C3 for calibration between manipulators not set
Software operation error occurred
File C1 through C3 for conveyor calibration not set
Software operation error occurred
HA function error
(conv_pos_data())
HA function error
(conv_shift_data())
HA function error
(conv_pulse_to_angle())
Setting error
Setting error
Software operation error occurred
100 Control-group axis configuration information parameter error
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
101
Meaning
Error in the parameter for the table for physical axes
102 Error in the parameter for the table for physical TU
Software operation error occurred
103 Excessive number of control group axes in use
Software operation error occurred
121 Job argument stack overflow
Cause
Software operation error occurred
104 JOG and PLAY maximum speed setting parameter error
Software operation error occurred
Software operation error occurred
122 Job argument stack underflow Software operation error occurred
123
128
129
Designation error of the fetched feedback pulse area at preparation of current value
Software operation error occurred
Timeout for waiting permission to modify the number of averaging times
Software operation error occurred
Object undefined for CLEAR instruction
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
130
Meaning
No space in RT_BANK setting area for correction-amount data
Cause
Software operation error occurred
131
132
133
134
135
Queue operation error for variable write-in history at prereading (at
ENQUE)
Software operation error occurred
Queue operation error for variable write-in history at prereading (at
DEQUE)
Software operation error occurred
Queue operation error for variable write-in history at prereading
(undefined operation)
Software operation error occurred
Queue operation error for variable write-in history at prereading (data length too long)
Software operation error occurred
Queue operation error for scoreboard setting history (at ENQUE)
Software operation error occurred
136 Queue operation error for scoreboard setting history (at DEQUE)
Software operation error occurred
137
138
Queue operation error for scoreboard setting history (undefined operation)
Software operation error occurred
Queue operation error for scoreboard setting history (data length too long)
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
139
Meaning Cause
Queue operation error for instruction execution (at ENQUE)
Software operation error occurred
140 Queue operation error for instruction execution (at DEQUE)
Software operation error occurred
141
142
143
Queue operation error for instruction execution (undefined operation)
Software operation error occurred
Queue operation error for instruction execution (data length too long)
Software operation error occurred
Queue operation error for WORK
ID conveyor (at ENQUE)
Software operation error occurred
144 Queue operation error for WORK
ID conveyor (at DEQUE)
Software operation error occurred
145 Queue operation error for WORK
ID conveyor (undefined operation)
Software operation error occurred
146 Queue operation error for WORK
ID conveyor (data length too long)
Software operation error occurred
147 Queue operation error for WORK
IN/OUT checking conveyor (at
ENQUE)
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
148
Meaning Cause
Queue operation error for WORK
IN/OUT checking conveyor (at
DEQUE)
Software operation error occurred
149
150
151
152
153
154
221
Queue operation error for WORK
IN/OUT checking conveyor
(undefined operation)
Software operation error occurred
Queue operation error for WORK
IN/OUT checking conveyor (data length too long)
Software operation error occurred
Queue operation error for waiting for semaphore for LOCK instruction (at ENQUE)
Software operation error occurred
Queue operation error for waiting for semaphore for LOCK instruction (at DEQUE)
Software operation error occurred
Queue operation error for waiting for semaphore for LOCK instruction (undefined operation)
Software operation error occurred
Queue operation error for waiting for semaphore for LOCK instruction (data length too long)
Software operation error occurred
Transfer data overflow in offline data bank
Software operation error occurred
222 Impossible to execute system exclusive for system job
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
223
Meaning
Event queue number range exceeded
Cause
Software operation error occurred
225
226
227
The number of WORK ID data and the MAX. WORK FIND
COUNT unmatched (MOTION ≠
CV)
The number of WORK IN/OUT data and the MAX. WORK FIND
COUNT unmatched (MOTION ≠
CV)
Excessive number of scheduling for execution of instructions
Software operation error occurred
Software operation error occurred
Software operation error occurred
228 Instruction execution scheduling impossible
Software operation error occurred
229 Illegal 1st-line move instruction at execution of +SMOV instruction
Software operation error occurred
230
232
Impossible to execute the slave circular interpolation and the master circular interpolation at the same time
Illegal index value for a +MOVx instruction
Software operation error occurred
Software operation error occurred
233 No xth-line move instruction exists where the master control group belongs.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
234
Meaning
Marking error for WORK ID conveyor queue (empty queue)
Cause
Software operation error occurred
235 Marking error for WORK IN/OUT conveyor queue (empty queue)
Software operation error occurred
236
237
238
239
Data error 1 at restarting after an emergency stop (actual status and the data status unmatched)
Software operation error occurred
Data error 2 at restarting after an emergency stop (actual status and the data status unmatched)
Software operation error occurred
Data error 3 at restarting after an emergency stop (actual status and the data status unmatched)
Software operation error occurred
Timeout for receiving segment data output request
Software operation error occurred
240
241
The number which designates the setting area of correction amount in RT_BANK exceeded the limit value.
Task error of the function calling source (cv_sync_intr ( ))
Software operation error occurred
Software operation error occurred
244 GETTOOLW manipulator designation error
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
245
Meaning
Overflow of entry number for instruction execution
Cause
Software operation error occurred
246 Data latch processing (function number overflow)
Software operation error occurred
247 Data latch processing (real-time status number overflow)
Software operation error occurred
248
250
Failed to set a timer unit. (No allocation space for timer unit setting)
GETS instruction internal error
Software operation error occurred
Software operation error occurred
251 SETFILE undefined file
252 GETFILE undefined file
Software operation error occurred
Software operation error occurred
253
254
The parameter was destroyed when a GETPRM instruction was executed.
Software operation error occurred
Null pointer assignment detected Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
255
Meaning
Function or other processing parameter error
Cause
Software operation error occurred
260
261
Arithmetic answer is not set at prereading (ADV_HA_ANS.flag
== OFF)
Software operation error occurred
Heap area obtainment failure
(A_BANK)
Software operation error occurred
262 Heap area obtainment failure
(C_BANK)
Software operation error occurred
263 Heap area obtainment failure
(Instruction queue)
Software operation error occurred
264 Heap area obtainment failure
(Path/trace queue)
Software operation error occurred
278 MEASON TRQ instruction control axis specification error
Software operation error occurred
279 Specified MSS system instance is not generated.
Software operation error occurred
280 API ERROR
(HDAS_get_alias_name())
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
500
Meaning
501 SL undefined interrupt command
(sub command)
Software operation error occurred
502 Previous SL interrupt command processing
Software operation error occurred
503 SL interrupt command data error Software operation error occurred
999 Arithmetic section error (segment data all zero timeout)
Software operation error occurred
1001 System task priority arrangement error
Software operation error occurred
1002 VxWorks primitive error
(msgQCreate)
1003 VxWorks primitive error
(msgQSend)
Cause
SL undefined interrupt command
(main command)
Software operation error occurred
1000 System clock (RTC) setting error Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
4208 SYSTEM ERROR
(ARITH)
Sub
Code
1005
1007 VxWorks primitive error
(semTake)
Cause
Software operation error occurred
1100 Failed system job environment configuration
Software operation error occurred
1101 MotoPlus environment setup error Software operation error occurred
1
6
7
8
11
Meaning
VxWorks primitive error
(semBCreate)
Software operation error occurred
Prereading task is not completed.
Software operation error occurred
No previous bank exists.
The answer bank flag is ON.
Software operation error occurred
Software operation error occurred
An error occurred in preparation of current position.
Software operation error occurred
The previous bank's prereading conversion could not correctly be completed.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
12
Meaning
13
14
16
18
20
23
24
A manipulator designation error occurred at JOG operation using the external reference point.
Software operation error occurred
Designation error of cubic interference coordinates
Station/base axis motion command error
Cause
Software operation error occurred
Path control position data error of prereading bank
Software operation error occurred
Software operation error occurred
User coordinates number error Software operation error occurred
Prereading task not completed at master in twin synchronous system
Software operation error occurred
Dynamic model arithmetic error Software operation error occurred
Speed limit control error
(excessive moment of gravity)
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).
(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).
(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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·The allowable braking 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 eachaxes.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
Alarm Name
Sub
Code
25
Meaning Cause
Square root of a negative number Software operation error occurred
26
29
35
41
42
57
59
60
The system number is not set at master in twin synchronous system.
Software operation error occurred
FORMCUT internal control error Software operation error occurred
No master-group is designated at preparation of master-tool user coordinates.
Software operation error occurred
Pulse linked JOG function error Software operation error occurred
Special JOG operation error Software operation error occurred
Arithmetic error occurred when calculating the acceleration and deceleration time (Function acceleration and deceleration control)
Arithmetic error occurred when calculating PL control (Function acceleration and deceleration control)
Arithmetic error occurred when calculating Function acceleration and deceleration dry run.
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
61
Meaning Cause
Arithmetic error occurred when calculating current path of continuous motion stop operation
Software operation error occurred
62
63
64
65
66
67
68
69
Arithmetic error occurred when calculating next path of continuous motion stop operation
Software operation error occurred
Arithmetic error occurred when calculating acceleration time when continuous motion in the prereading processing
Arithmetic error occurred when calculating deceleration time when continuous motion in the prereading processing
Arithmetic error occurred when calculating acceleration and deceleration time when teaching.
Software operation error occurred
Software operation error occurred
Software operation error occurred
Arithmetic error occurred when calculating acceleration and deceleration time for plucking in prereading processing 1
Arithmetic error occurred when calculating acceleration and deceleration time for plucking in prereading processing 2
Arithmetic error occurred when calculating acceleration and deceleration time for plucking in prereading processing 3
Arithmetic error occurred when calculating acceleration and deceleration time for plucking in prereading processing 4
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
70
Meaning
71
72
Cause
Arithmetic error occurred when calculating acceleration and deceleration for PL control plucking in prereading processing
1
Software operation error occurred
Arithmetic error occurred when calculating acceleration and deceleration for PL control plucking in prereading processing
2
Software operation error occurred
Arithmetic error occurred when calculating acceleration and deceleration for plucking
Software operation error occurred
73
74
75
76
77
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing 1
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing 2
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing 3
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing 4
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing 5
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
4209 OFFLINE SYSTEM
ERROR (ARITH)
Sub
Code
85
Meaning
86
Cause
Arithemetic error occurred when acceleration and deceleration for canceling PL control of station were recalculated.
PL during current → Arithmetic error occurred when calculating acceleration time for CONT
Software operation error occurred
Software operation error occurred
87
88
89
65535
Arithmetic error occurred when calculating acceleration and deceleration for PL control in prereading processing
Arithemetic error occurred when acceleration and deceleration for moving to the different conveyer coordinate were calculated.
Software operation error occurred
Software operation error occurred
Operation command group which pre-reading is not completed detection error
Software operation error occurred
For HA debug use Software operation error occurred
100 Data setting error in offline data bank
Software operation error occurred
101 Data setting error in offline answer bank
Software operation error occurred
102 OFF_USER_POS occupation control error
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
103
Meaning
OFF_USER_POS valid control error
Cause
Software operation error occurred
104 Mail-receiving error of offline task Software operation error occurred
105 Offline occupation control error Software operation error occurred
107 OFF_USER_ROT_POS occupation control error
Software operation error occurred
108 OFF_USER_ROT_POS valid control error
Software operation error occurred
109 OFF_CV_CALIB_POS occupation control error
110 OFF_CV_CALIB_POS valid control error
Software operation error occurred
Software operation error occurred
111
112
Incorrect teaching for offline conveyor tracking turntable function
Software operation error occurred
No manipulator is designated for offline conveyor tracking turntable function.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4210
Alarm Name
SYSTEM ERROR
(LOCAL VARIABLE)
Sub
Code
-1
-2
-3
-4
-5
-6
-7
-8
-9
Meaning
Local variable is not used.
Memory area for local variable could not be obtained.
Software operation error occurred
No unused handle value exists when local variable area is created.
An error occurred in exclusive control.
Software operation error occurred
Software operation error occurred
Handle value is invalid for specified local variable.
Handle value is incorrect for specified local variable.
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
An error occurred when memory area for local variable was released.
Software operation error occurred
An error occurred when memory area for local variable was registered.
Software operation error occurred
Local variable control process is not initialized.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4220
4221
4226
Alarm Name
Sub
Code
-10
-11
Meaning Cause
Local variable area shared heap area.
Software operation error occurred
An error occurred in exclusive control.
Software operation error occurred
-12 An error occurred in exclusive control when control of the local variable was processed.
Software operation error occurred
Sub Code: Control group Setting error SERVO POWER OFF
FOR JOB
SERVO POWER OFF
FOR JOB
COMMUNICATION
SERVICE ERROR
1
100
101
102
103
105
Sub Code: Control group Setting error
The communication channel could not be opened/closed at
OPEN/CLOSE instruction execution.
The communication port is already opened.
The communication port is not opened.
No space was found in data sent buffer.
The setting value for the event queue designation parameter is incorrect.
The type of output data is incorrect.
Setting error
Setting error
Setting error
Setting error
Setting error
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).
(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).
(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).
(1)Check the following settings.
·Turn OFF the servo power supply, and then turn ON the servo power supply for the group axis to be operated.
·Turn OFF the servo power supply, and then turn ON the servo power supply for the group axis to be operated.
(1)Check the following settings.
·Setting of the RS (transmission) parameter
(1)Check the following settings.
The serial port setting
(1)Check the following settings.
The serial port setting
(1)Check the following settings.
The serial port setting
(1)Check the following settings.
·RS157···Set to 1 to 4
(1)Check the following settings.
The serial port setting
Alarm
Number
4228
4229
Alarm Name
WRONG DATA
ETHERNET PROCESS
ERROR
1
Sub
Code
2
Meaning Cause
Software operation error occurred
Data error
Remedy
(1)Reset the alarm, and then execute following operation.
·Select a sub menu [WRONG DATA LOG] under main menu [SETUP].
·Execute "RESTORE" by selecting "UTILITY" from the pull-down menu.
*Occurrence date changes to restoration date after it is restored.
·Turn the power ON again and confirm the causes of the wrong data 1 and 2.
Cause 1: Confirm the position of the file.
Cause 2: Register the position of the file again.
*As for the Cause 3, there is no confirming item after the power is turned ON.
(2) If the restoration cannot be completed, execute the followings.
·Execute "RECONFIRM" by selecting "UTILITY" from the pull-down menu.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1) If different axes configuration data is loaded, the system data becomes incorrect status, which causes this alarm. In this case, execute the following operations.
·Select a sub menu [WRONG DATA LOG] under main menu [SETUP].
·Execute "RESTORE" by selecting "UTILITY" from the pull-down menu.
·Load the correct axes configuration.
(2) If the restoration cannot be completed, execute the followings.
·Execute "RECONFIRM" by selecting "UTILITY" from the pull-down menu.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
An error occurred in the acquisition process of the IP address during the IP address monitoring process of the
Ethernet function.
Setting error
Main CPU board failure
An error occurred in the acquisition process of subnet mask during the network service data creation process of the
Ethernet function.
Setting error
Main CPU board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
Alarm
Number
4300
Alarm Name
VERIFY ERROR
(SERVO PARAMETER)
Sub
Code
3
Meaning Cause
An error occurred in the acquisition process of gateway during the network service data creation process of the Ethernet function.
Setting error
Main CPU board failure
4
6
An error occurred in the conversion process of gateway address during the network service data creation process of the Ethernet function.
Setting error
Main CPU board failure
An error occurred in the acquisition process of domain during the network service data creation process of the Ethernet function.
Setting error
Main CPU board failure
8
Remedy
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
An error occurred in the acquisition process of host name during the network service data creation process of the Ethernet function.
Setting error
Main CPU board failure
Setting error
Servo control board failure
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Check the following settings.
·The DHCP server operation (If the DHCP is used)
·The network status (If the DHCP is used)
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller.
(1)Reset the alarm
(2)If the alarm occurs again, check the parameter setting if there were any parameters which were modified before the alarm.
(3)If the alarm occurs again or when it occurs other than above mentioned (2) case, contact your Yaskawa representative.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4302
4303
4304
4305
4307
Alarm Name
BRAKE CIRCUIT
ERROR
CONVERTER READY
SIGNAL ERROR
CONVERTER INPUT
POWER ERROR
CONVERTER CIRCUIT
CHARGE ERROR
SERVO ON DEFECTIVE
SPEED
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Software operation error occurred
Servo control board failure
Connection failure
Module failure (converter)
Servo control board failure
Module failure (converter)
Connection failure
Module failure (converter)
Module failure (Regenerative resistor)
(1)Reset the alarm
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Turn ON the servo power after 5 or more seconds from the alarm occurrence.
Movement of axis when the
SERVO ON process
Mechanical failure
Servo control board failure
Check that the manipulator is not moving when the servo turned ON.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4308
4309
4310
Alarm Name
VOLTAGE DROP
(CONVERTER)
DEFECTIVE ENCODER
INTERNAL DATA
ENCODER OVERHEAT
Sub
Code
Meaning Cause Remedy
Connection failure (1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
{Robot axis}
·Cable between encoders
{External axis}
·Cable between encoders
(3)If the alarm occurs again, replace controller
(1)Reset the alarm
(2)If the alarm occurs again, replace the motor.
Check if the primary power supply voltage is dropping.
Module failure (motor)
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Voltage failure
Connection failure
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Module failure (converter)
Servo control board failure
Connection failure
Module failure (encoder)
Overheated encoder
High ambient temperature
Module failure (encoder)
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
{Robot axis}
·Cable between encoders
{External axis}
·Cable between encoders
(3)If the alarm occurs again, replace controller
(1)Reset the alarm
(2)If the alarm occurs again, replace the encoder.
Turn OFF the power supply for about 10 minutes.
Adjust the ambient temperature to 40°C or less.
(1)Reset the alarm
(2)If the alarm occurs again, replace the encoder.
Alarm
Number
4311
4312
4315
Alarm Name
ENCODER BACK-UP
ERROR
ENCODER BATTERY
ERROR
COLLISION DETECT
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Servo control board failure
Module failure (encoder battery)
Connection failure
Module failure (encoder)
Servo control board failure
Module failure (encoder battery)
Connection failure
Setting error
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
[AL-4314 occurred]
Replace the battery of the axis in which the error occurred.
[AL-1327 occurred]
Replace the battery of the axis in which the alarm occurred. If the home position of the corresponding axis is displays as "***", register the home position.
(1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
{Robot axis}
·Cable between encoders
{External axis}
·Cable between encoders
(1)Reset the alarm
(2)If the alarm occurs again, replace the encoder.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Replace the battery.
(1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·Manipulator cable
Check the following settings.
·The tool information
·The selection tap of the transfer
·The collision detection level
·JOB
·Work
·The speed of JOB
·The acceleration/deceleration speed of ACC and DEC
·Length of the power cables
·Diameter of the power cable
Alarm
Number
4318
Alarm Name
SERIAL ENCODER
CORRECTION LIMIT
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Interference error
Connection failure
Connection failure
Connection failure
Servo control board failure
Module failure (amplifier)
Module failure (motor)
Maintenance failure
Defective speed reducer
Connection failure
Module failure (encoder)
Remove the following interferences.
·The interferences to the jigs of Robot.
·The interferences to the jigs of workpieces.
·If there is no interference between robot and workpieces, set the shock detection level to more than maximum eternal value. Up to 500% of the level is possible.
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·The motor power line
·The encoder line
(1) If the alarm occurs again, check the wiring of phase-U, -V, and -W isn't disconnected.
(2) If disconnected, replace the motor power wire.
(1) Check that the motor brake wire is not disconnected.
(2) If disconnected, replace the motor brake wire.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace the motor.
Measure the density of grease iron powder in the speed reducer and do the maintenance.
Replace the speed reducer or the grease of it.
(1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
{Robot axis}
·Cable between encoders
{External axis}
·Cable between encoders
(1)Reset the alarm.
(2)If the alarm occurs again, replace the encoder.
Alarm
Number
Alarm Name
4320 OVERLOAD
(CONTINUE)
4321 OVERLOAD
(MOMENT)
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Servo control board failure
Setting error
Interference with peripheral devices
Setting error
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·The tools or the mass of the workpieces
Remove interference with the workpiece and peripheral device.
Review the JOB to check if the load factor doesn't exceed 100%.
Servo control board failure
Connection failure
Module failure (motor)
Module failure (converter)
Setting error
Interference error
Setting error
Servo control board failure
Connection failure
Module failure
(motor)
Module failure (converter)
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the following cables.
·The wire harness in the robot.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·The tools or the mass of the workpieces
Remove interference with the workpiece and peripheral device.
Correct the job whether load late does not exceed 100%.
(1)Check that 24V is generated to the brake bolt of the following terminals.
·Motor brake terminal
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the following cables.
·The wire harness in the robot.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4322
Alarm Name
AMPLIFIER OVERLOAD
(CONTINUE)
Sub
Code
4323 AMPLIFIER OVERLOAD
(MOMENT)
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause
Setting error
Interference error
Setting error
Servo control board failure
Connection failure
Module failure (amplifier)
Module failure (converter)
Setting error
Interference error
Setting error
Servo control board failure
Connection failure
Module failure (amplifier)
Module failure (converter)
Remedy
Check the following settings.
·The tools or the mass of the workpieces
Remove interference with the workpiece and peripheral device.
Correct the job whether load late does not exceed 100%.
(1)Check that 24V is generated to the brake bolt of the following terminals.
·Motor brake terminal
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the following cables.
·The wire harness in the robot.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·The tools or the mass of the workpieces
Remove interference with the workpiece and peripheral device.
Correct the job whether load late does not exceed 100%.
(1)Check that 24V is generated to the brake bolt of the following terminals.
·Motor brake terminal
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the following cables.
·The wire harness in the robot.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4324
Alarm Name
CONVERTER
OVERLOAD
4326 OVER SPEED
4327 WRONG MOTOR
ROTATION
4328 SERVO TRACKING
ERROR
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Setting error
Setting error
Module failure (converter)
Servo control board failure
Setting error
Connection failure
Module failure
(motor)
Servo control board failure
Connection failure
Connection failure
Servo control board failure
Setting error
Interference error
Check the settings of the following.
·If the tool or the workpiece used has exceeded the allowable load.
Adjust the job speed.
Adjust the acceleration/deceleration of ACC and DEC instructions.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·Reduction in the motion speed
(1)Reset the alarm.
(2)If the alarm occurs again, check that U-, V- and W-phase are appropriately connected.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·The motor power line
·The encoder line
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·The power cable connection of the manipulator cable.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the settings of the followings.
·Tool file setting
·The tools or the mass of the workpieces
Remove interference with the workpiece and peripheral device.
Alarm
Number
4329
Alarm Name
Sub
Code
Meaning
SAFETY SPEED ERROR
(SERVO)
11
Cause Remedy
The motion speed at the center of the flange exceeded the specified max. speed.
Teaching accelerating/ decelerating speed maximum
Connection failure
Adjust the acceleration/deceleration of ACC and DEC instructions.
Module failure
(brake)
Module failure (amplifier)
Module failure
(motor)
Servo control board failure
Module failure (converter)
Setting error
(1)Reset the alarm.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·The motor power line
·The encoder line
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·Reduction in the motion speed
Setting error
Connection failure
Module failure
(motor)
Servo control board failure
(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).
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
Sub
Code
12
21
22
Meaning
The motion speed at the center of the control point exceeded the specified max. speed.
The motion speed at the center of the control point exceeded the specified max. speed.
Cause
The motion speed at the center of the flange exceeded the specified max. speed.
Setting error
Setting error
Connection failure
Module failure (motor)
Servo control board failure
Software operation error occurred
Software operation error occurred
Connection failure
Module failure (motor)
Servo control board failure
Setting error
Setting error
Remedy
Check the following settings.
·Reduction in the motion speed
(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).
(1)Reset the alarm.
(2)If the alarm occurs again, check that U-, V- and W-phase are appropriately connected.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·Reduction in the motion speed
(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).
(1)Reset the alarm.
(2)If the alarm occurs again, check that U-, V- and W-phase are appropriately connected.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·Reduction in the motion speed
(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).
Alarm
Number
Alarm Name
4334 OVERVOLTAGE
(CONVERTER)
4336 OPEN PHASE
(CONVERTER)
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Sub Code: Signifies the physical
No. of converter in which the alarm occurred
Connection failure
Module failure (motor)
Servo control board failure
Connection failure
Setting error
Voltage failure
Module failure (Regenerative resistor)
Module failure (converter)
Servo control board failure
Connection failure
Voltage failure
Module failure (converter)
Servo control board failure
(1)Reset the alarm.
(2)If the alarm occurs again, check that U-, V- and W-phase are appropriately connected.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the following settings.
·The tools or the mass of the workpieces
Modify the primary breaker voltage to the specified voltage 200V(+10% to
15%).
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Modify the primary breaker voltage to the specified voltage 200V(+10% to
15%).
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4337
4338
4341
Alarm Name
OVERCURRENT
(AMP)
REGENERATIVE
TROUBLE
(CONVERTER)
DISLOCATION DETECT
Sub
Code
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause Remedy
Connection failure
Connection failure
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the following cables.
·Manipulator cable
·Supply cable
Module failure (amplifier)
Module failure (motor)
Servo control board failure
Connection failure
Module failure (Regenerative resistor)
Module failure (converter)
Servo control board failure
Overloading
Interference error
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace the motor.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check that the load does not exceed the allowable limit.
Remove the following interferences.
·The interferences to the jigs of Robot.
·The interferences to the jigs of workpieces.
Parts damage
Software operation error occurred
Check the following parts.
·damage of spring
·damage of bushing
Check the following settings.
·The tool information
Alarm
Number
4344
Alarm Name
4345
4346
4347
4348
4349
4350
4351
LINEAR SERVOFLOAT
TRACKING ERROR
LNK SERVOFLOAT
EXECUTE ERROR
LNK SERVOFLOAT TRQ
LIMIT ERROR
LNR SERVOFLOAT TRQ
LIMIT ERROR
LNR SERVOFLOAT
COORD TYPE ERROR
LNR SERVOFLOAT
TOOL POSE ERROR
LNR SERVOFLOAT
EXECUTE ERROR
DRIVE BELT SNAP
DETECT
Sub
Code
Meaning
Sub Code: Signifies the axis in which the alarm occurred
4352 TWIN DRIVE OVER
DEVIATION
Cause
Software operation error occurred
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
Connection failure
Sub Code: Signifies the axis in which the alarm occurred
Driving belt failure
Connection failure
Cable (failure)
(motor power cable)
Cable (failure)
(motor brake cable)
Servo control board failure
Module failure (amplifier)
Module failure (motor)
Remedy
Confirm the job settings so that excess load would not be applied to the axis in the linear servo float.
Confirm the job settings so that excess load would not be applied to the axis in the linear servo float.
Check the limit torque of the link servo float condition file.
Check the limit torque of the link servo float condition file.
Check the setting file of the job and the linear servo float.
Check the setting file of the job and the linear servo float.
Check the settings for jobs.
Check that the driving belt is not broken.
Check the driving belt.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Check U-, V- and W-phase of the motor power cable disconnection.
(2)If disconnection is found, replace the motor power cable.
(1) Check that the motor brake wire is not disconnected.
(2) If disconnected, replace the motor brake wire.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
4353
Alarm Name
DEFECTIVE TAUGHT
POINT
(ENDLESS)
Sub
Code
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Cause
Setting error
Servo control board failure
4355 Setting error
Remedy
Check the following settings.
·Setting of the command soft (JOB)
·MRESET instruction to corresponding axis
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Check the settings for jobs.
4400
EXTERNAL PRES
DETECT
(SERVOFLOAT)
NOT READY (ARITH) 1
4401 SEQUENCE TASK
CONTR ERROR
2
3
4
5
1
2
The arithmetic process for motion control did not complete within regulated time. No motion command was prepared.
Software operation error occurred
The arithmetic processing section is not ready for JOG operation.
Software operation error occurred
The arithmetic processing section is not ready for the playback operation.
Software operation error occurred
The prereading processing in the arithmetic processing section has not completed.
Software operation error occurred
The arithmetic processing section is not ready for the timer follow-up of the conveyor tracking function.
Software operation error occurred
Unused A_BANK does not exist in the prereading processing of move instruction.
Software operation error occurred
Unused bank priority does not exist in the prereading processing of move instruction.
Software operation error occurred
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
5
6
7
20
21
22
23
24
26
Meaning
A_BANK pointer is not set.
Cause
Software operation error occurred
A_BANK conversion could not be performed.
Software operation error occurred
The specified A_BANK number does not exist.
Software operation error occurred
An error occurred when system number (MSS) was obtained.
Software operation error occurred
An error occurred in RMS960 system call.
Software operation error occurred
Undefined interrupt command was received.
Software operation error occurred
Job start condition is not defined.
Software operation error occurred
An error occurred in instruction prefetch queue operation.
Software operation error occurred
Intermediate code is not defined.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
29
Meaning Cause
Instruction prereading processing has not been completed normally.
Software operation error occurred
30
31
32
33
38
39
41
45
An error occurred in job data change.
Software operation error occurred
The specified sequence number at job execution start is incorrect.
Software operation error occurred
The added area for interruption command is incorrect.
Software operation error occurred
System number (MSS) for interruption command is incorrect.
Software operation error occurred
An error occurred at start of twin synchronous operation.
Software operation error occurred
An error occurred when SYNC specification was reset.
Software operation error occurred
An error occurred in occupation control group setting in MOTION section.
Software operation error occurred
An error occurred in path/trace control.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
47
Meaning Cause
An error occurred when waiting for a completion of main system task (job) in SYNC specification.
Software operation error occurred
48
49
80
An attempt was made to execute an instruction that could not be executed at line sequence execution.
An error occurred when during the instruction data acquisition process.
Software operation error occurred
Software operation error occurred
An exceptional error occurred in job execution process.
Software operation error occurred
100
101
102
Main processing command is incorrect in prereading processing.
Subprocessing command is incorrect in prereading processing.
Software operation error occurred
Software operation error occurred
Prereading processing has not been completed at job execution.
Software operation error occurred
103 A_BANK conversion has not been completed.
Software operation error occurred
104 System number (MSS) is incorrect in prereading processing.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4402
4404
4406
Alarm Name
UNDEFINED COMMAND
(ARITH)
ARITHMETIC ERROR 8
GROUP AXIS CONTROL
ERROR
1
10
11
Sub
Code
105
Meaning
An error occurred in instruction prefetch queue operation in prereading processing.
106
2
3
Cause
Software operation error occurred
An error occurred at IES switching in prereading processing.
Software operation error occurred
Slave designation error
Slave interpolation error
Software operation error occurred
Interpolation such as linear and circular interpolation cannot be performed with this manipulator.
Setting error
The setting of the form data for
Flip/No Flip is not "B-axis Angle".
An attempt was made to pass the
B-axis zero degree position
(singular area).
Designation error for master and slave
Setting error
Setting error
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(1)Reset the alarm, and then try again.
(2)Check the following settings.
·the base-axis position must be registered for the system with base-axis
MOVL P00001 BP00001
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Change the step (move instruction), where the alarm occurred, to MOVJ.
(1)Check the following settings.
·Set "1" to "S2C658: Type data detail settings".
(1)Check the following settings.
·Check the teaching position of the job so that the manipulator does not pass the B-axis zero degree position (singular area).
(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).
(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).
(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).
Alarm
Number
4407
4409
Alarm Name
TWO STEPS SAME
POSITION
(CIRC)
TWO STEPS SAME
POSITION
(3 STEPS)
Sub
Code
4
6
7
8
9
10
11
12
Meaning
No designation of master axis
Cause
Software operation error occurred
Master-axis designation error for
JOG motion
Software operation error occurred
Slave-axis designation error for
JOG motion
Software operation error occurred
Occupation control error Software operation error occurred
Designation error of occupation control for JOG motion
Software operation error occurred
Designation error of occupation control for Bank position
Software operation error occurred
Designation error of occupation control group for tracking motion
Software operation error occurred
No master and slave designated for tracking motion
Software operation error occurred
Setting error
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·Check the settings for teaching position of circular interpolation steps so that each point is different.
(1)Check the following settings.
·Check the settings for three taught points to create an user coordinate system so that each point is different.
Alarm
Number
4414
Alarm Name
EXCESSIVE SEGMENT
(LOW/HIGH)
Sub
Code
Meaning Cause
Sub Code: Control group and axis Setting error
4416 Sub Code: Control group and axis Setting error
4418
4420
4422
4424
PULSE LIMIT
(MIN./MAX.)
CUBE LIMIT
(MIN./MAX.)
SPECIAL SOFTLIMIT
(MIN./MAX.)
MECHANICAL
INTERFERENCE
(MIN./MAX.)
SPECIAL MECHANICAL
INTRF(MIN./MAX.)
Sub Code: Control group and
XYZ
Setting error
Sub Code: Control group and axis Setting error
Sub Code: Control group and axis Setting error
Sub Code: Control group and axis Setting error
4426 PULSE MECHANICAL
LIMIT(MIN./MAX.)
Sub Code: Control group and axis Setting error
Remedy
(1)Reduce the speed in the step where the alarm occurred.
(2)Change the move instruction to joint interpolation (MOVJ).
* Be careful to the peripheral interference since its movement changes.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(2) If the manipulator is stopped near the interference area by servo OFF, it may interfere with the interference area.
In this case, execute the following operations to disable the special mechanical interference check and move each part out of the interference area.
- Change the mode to "TEACH"
- To display LIMIT RELEASE window, select the main menu [ROBOT] and then
[LIMIT RELEASE]
- Change the setting for ALL LIMIT RELEASE from "INVALID" to "VALID" by
[SELECT] key
- Move each part out of the interference area
- Change the setting for ALL LIMIT RELEASE from "VALID" to "INVALID" by
[SELECT] key
NOTE) Be sure to check the operation direction since the above operations enable manipulator's parts to interfere with each other.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
Alarm
Number
4428
Alarm Name
SEGMENT CONTROL
ERROR
4429 WRONG SPECIFIED
CONTROL GROUP
1
Sub
Code
1
2
3
4
5
8
9
10
Meaning
RT-buffer control command error Software operation error occurred
Segment-receiving control command error
No bank priority
Cause
Software operation error occurred
Software operation error occurred
Answer error at MOVE simulating Software operation error occurred
The value of bank_refresh_flag(x) exceeded its limit.
Software operation error occurred
RT-buffer tracking option error Software operation error occurred
The segment was received although the previous segment had not been sent.
Software operation error occurred
Segment creation is requested before segment-receiving is completed.
Control group not designated
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
2
3
4
5
6
7
8
10
11
Meaning
Slave control-group error
Master control-group error
Cause
Software operation error occurred
Software operation error occurred
Master and Slave control-group error
Software operation error occurred
Control-group error for a job file Software operation error occurred
Control-group error for a user coordinate file
Software operation error occurred
Control-group error for a calibration file between manipulators
Control-group error for a tool calibration file
Software operation error occurred
Software operation error occurred
Control-group error for prereading-calculation start point
(for adv_st_pos)
Software operation error occurred
Control-group error for the current-value preset position
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4430
Alarm Name
18
19
CPU COMMUNICATION
ERROR
1
Sub
Code
12
Meaning Cause
Control-group error for the conveyor prereading-calculation start point
Software operation error occurred
13 Occupation control-group error Software operation error occurred
2
3
4
5
Control-group error for the prereading-calculation start point
(for dm_st_pos)
Software operation error occurred
Control-group error for prereading-calculation start point
(for dm_st_pos)
Software operation error occurred
Software operation error occurred
Interrupt processing error between MOTION section and system control section
Interrupt processing error between MOTION section and
SL#1
Software operation error occurred
Software operation error occurred
Interrupt processing error between MOTION section and
SL#2
Interrupt processing error between MOTION section and
SL#3
Interrupt processing error between MOTION section and
SL#4
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4431
4432
Alarm Name
JHM ERROR
INSTRUCTION
INTERPRETER ERROR
1
Sub
Code
6
Meaning
7
1
2
3
Cause
Interrupt processing error between MOTION section and
CV#1
Interrupt processing error between MOTION section and
CV#2
Software operation error occurred
Software operation error occurred
An error occurred in JMS system call when an attempt was made to open a job.
Software operation error occurred
No space was found in job handle value storage area when an attempt was made to open a job.
Software operation error occurred
No job handle was found.
Software operation error occurred
4
5
6
3
Job control proprietary is incorrect.
Software operation error occurred
Job control proprietary could not be changed.
Software operation error occurred
An error occurred in exclusive control.
Software operation error occurred
The intermediate code of the instruction that is to be executed is incorrect.
Software operation error occurred
Destination (variable) tag arrangement is incorrect.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
4
5
6
8
9
10
11
12
14
Meaning
Tag data type is incorrect.
Box number is incorrect.
An error occurred in block separation processing of intermediate code.
Box number definition is duplicated.
Undefined instruction was found at block separation of intermediate code.
Software operation error occurred
IPRM is not set.
Software operation error occurred
An error occurred in tag data search process.
Software operation error occurred
An error occurred move instruction search process.
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Variable information does not exist.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
16
17
18
19
20
22
23
24
25
Meaning Cause
An error occurred at position file data reading.
Software operation error occurred
Variable data type is not defined.
Software operation error occurred
An instruction is included with incorrect intermediate code in expression instruction.
The syntax in expression instruction is incorrect.
Software operation error occurred
Software operation error occurred
The tag data length is zero when tag data is read.
Software operation error occurred
The object to be processed was secret variable in position file control process, so it could not be processed.
Software operation error occurred
The object to be processed was position type variable in position file control process, so it could not be processed.
Software operation error occurred
Job argument settings do not match when a variable is given and/or taken between jobs.
Software operation error occurred
An attempt was made to perform undefined operation at four-rule operation instruction.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4433
Alarm Name
Sub
Code
26
27
UNDEFINED GLOBAL
VARIABLE
0
Meaning Cause
Arithmetic stack used for expression operation exceeded.
Software operation error occurred
Arithmetic stack used for expression operation is empty.
Software operation error occurred
28
29
254
Operation items are lacking in expression operation and operation processing cannot be performed.
Sub instruction which has EXEC process exceeded the maximum number.
Software operation error occurred
Software operation error occurred
Access mechanism for old parameters is used.
Software operation error occurred
255 An exceptional error occurred.
Software operation error occurred
1
2
The set data for byte type variable area is incorrect.
Software operation error occurred
The set data for integer type variable area is incorrect.
Software operation error occurred
The set data for double-precision integer-type variable area is incorrect.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4435
Alarm Name
UNDEFINED LOCAL-
VARIABLE
6
7
4
5
2
3
0
1
Sub
Code
3
Meaning Cause
The set data for real type variable area is incorrect.
Software operation error occurred
4
5
6
7
The set data for character-string type variable area is incorrect.
Software operation error occurred
The set data for robot-axis position-type variable area is incorrect.
The set data for base-axis position-type variable (S1D parameter) area is incorrect.
Software operation error occurred
Software operation error occurred
The set data for station-axis position-type variable (S1D parameter) area is incorrect.
Software operation error occurred
The byte type variable is not defined.
The integer type variable is not defined.
Setting error
Setting error
The double-precision integer-type variable is not defined.
Setting error
The real-number type variable is not defined.
The character-string type variable is not defined.
Setting error
Setting error
Setting error The robot-axis position-type variable is not defined.
The base-axis position-type variable is not defined.
Setting error
The station-axis position-type variable is not defined.
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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
(1)Check the following settings.
·Set the number of local variables to be used in the job header.
Alarm
Number
4436
Alarm Name
LESS THAN 3 STEPS
(CIRCULAR)
4438 UNDEFINED JOB
4439
4440
4441
4444
4445
UNDEFINED LABEL
UNDEFINED RETURN
JOB
LACK OF LOCAL-
VARIABLE AREA
UNSUCCESSFUL FINE
POSITIONING
DATA PRESET ERROR 1
Sub
Code
2
3
4
Meaning Cause
Setting error
Setting error
Setting error
Setting error
Setting error
Sub Code: Bit specification of axis where error occurred
Effect of external force
The token for prereading processing could not be obtained.
Software operation error occurred
The prereading processing has not been completed within the time, and the waiting time for completion exceeded the limit.
The prereading operation processing has not been completed within the time, and the waiting time for completion exceeded the limit.
An error occurred in prereading operation process.
Software operation error occurred
Software operation error occurred
Software operation error occurred
Remedy
(1)Check the following settings.
·Perform teaching so that circulation interpolation steps are continuous three points or more.
(1)Check the following settings.
·Check if the CALL/JUMP destination job is registered. If the job is not registered, delete the JUMP instruction where an alarm occurred.
(1)Check the following settings.
·Check if the JUMP destination label is registered. If the label is not registered, delete the JUMP instruction where alarm occurred.
(1)Check the following settings.
·If there is an illegal RET instruction in the start job, delete the RET instruction.
·Check if RET instruction is not executed under the condition that there is no job in the job call stack. In that case, execute it from
(1)Check the following settings.
·Reduce the number of local variables to be used.
(1)Check the following settings.
·Move the manipulator by the axis operation, etc. to remove the external force of axis where alarm occurred.
(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).
(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).
(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).
(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).
Alarm
Number
4446
Alarm Name
Sub
Code
5
Meaning Cause
A_BANK conversion has not been completed.
Software operation error occurred
255 An exceptional error occurred in job execution process.
Software operation error occurred
OVER VARIABLE LIMIT 0
1
2
3
4
5
6
7
8
The variable value exceeded the limit.
Setting error
The value for the binary (0/1) data type variable exceeded the limit.
Setting error
The value for the signed 1-byte data type variable is less than the minimum value.
Setting error
The value for the unsigned 1-byte data type variable is less than the minimum value.
Setting error
The value for the signed 2-byte data type variable is less than the minimum value.
Setting error
The value for the unsigned 2-byte data type variable is less than the minimum value.
Setting error
The value for the signed 4-byte data type variable is less than the minimum value.
Setting error
The value for the unsigned 4-byte data type variable is less than the minimum value.
Setting error
The value for the real-number 4byte data type variable is less than the minimum value.
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).
(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).
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
Alarm
Number
4447
4449
4450
Alarm Name
DEFECTIVE TAUGHT
POINT(CIRC)
UNMATCHED POSN
VAR DATA TYPE
FILE NO. ERROR 1
2
Sub
Code
14
Meaning
32770
32771
32772
32773
32774
32775
32776
32782
Cause
The value for the character-string type variable is less than the minimum value.
The value for the signed 1-byte data type variable exceeded the maximum value.
Setting error
Setting error
The value for the unsigned 1-byte data type variable exceeded the maximum value.
Setting error
The value for the signed 2-byte data type variable exceeded the maximum value.
The value for the unsigned 2-byte data type variable exceeded the maximum value.
Setting error
Setting error
The value for the signed 4-byte data type variable exceeded the maximum value.
The value for the unsigned 4-byte data type variable exceeded the maximum value.
Setting error
Setting error
The value for the real-number 4byte data type variable exceeded the maximum value.
Setting error
The value for the character-string type variable exceeded the maximum value.
Setting error
Setting error
An error occurred in tool file number check.
An error occurred in user coordinate file number check.
Setting error
Setting error
Setting error
Remedy
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for variable, and then correct the job to fall within the input range of the tag.
(1)Check the following settings.
·Check the settings for three teaching points so that circular interpolation steps do not lie in a straight line.
(1)Check the following settings.
·Match the data type of position type variable.
(1)Check the following settings.
·Confirm that the specified tool file number is 0 to 63.
(1)Check the following settings.
·Confirm that the specified user coordinate file number is 1 to 63.
Alarm
Number
4451
4452
Alarm Name
UNDEFINED
REFERENCE POINT
STACK MORE THAN 10
(JOB CALL)
Sub
Code
3
Meaning
4
5
9
10
12
13
15
Cause
An error occurred in calibration file number check between the manipulators.
An error occurred in tool calibration file number check.
An error occurred in reference point number check.
An error occurred in conveyor characteristic file number check.
An error occurred in press characteristic file number check.
An error occurred in conveyor calibration file number check.
An error occurred in argument number check.
An error occurred while checking the link (linear) servo float condition file number.
Sub Code: Reference point number in binary
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
4453
4459
OVER VARIABLE NO.
The variable number is out of range.
Sub Code: The variable number which an attempt was made to use
Setting error
Setting error
4460
4463
EXCESSIVE
INSTRUCTION
EQUATION
ZERO DIVIDED
OCCURRENCE
PARITY ERROR
Setting error
Setting error
Remedy
(1)Check the following settings.
·Confirm that the specified robot calibration file number is 1 to 32.
(1)Check the following settings.
·Confirm that the specified tool file number is 0 to 63.
(1)Check the following settings.
·Confirm that the specified robot calibration file number is 1 to 8.
(1)Check the following settings.
·Confirm that the specified conveyor condition file number is 1 to 6.
(1)Check the following settings.
·Confirm that the specified press characteristic file number is 0 to 3.
(1)Check the following settings.
·Confirm that the specified conveyor calibration file number is 1 to 6.
(1)Check the following settings.
·Confirm that the argument number is 1 to 16.
(1)Check the following settings.
·Confirm that the link (linear) servo float condition file number is within the range of 1 to 8.
(1)Check the following settings.
·Set the reference point.
(1)Check the following settings.
·Change the job configuration so that the number of nests for CALL instruction is twelve or less.
(1)Check the following settings.
·Correct the job using the variable number within the range.
(1)Check the following settings.
·Separate the operation expression, shorten the expression, and then check the settings for the job.
(1)Check the following settings.
·Do not divide by zero.
(1)Check the following settings.
·Check the settings for the parity data of the user I/O group.
Alarm
Number
4464
4465
4466
Alarm Name
OVER BCD RANGE
OVER BINARY RANGE
(PARITY CHECK)
OFFLINE UNDEFINED
COMMAND (ARITH)
0
Sub
Code
Meaning Cause
Setting error
Setting error
An undefined command was issued to the offline position-data preparation section.
Software operation error occurred
4467
4468
USER COORD STEP
NOT ENOUGH
ROBOT CALIBRATION
DATA ERROR
1
2
Setting error
The calibration between manipulators cannot be executed for this model.
The master group and the slave group are set to the same group.
Setting error
Software operation error occurred
3
4
5
6
7
Incorrect designation of the control group for master group
Software operation error occurred
Incorrect designation of the control group for slave group
Software operation error occurred
Incorrect designation of the occupation control group for calibration data
Incorrect designation of the enabling control group for calibration data
Software operation error occurred
Software operation error occurred
Among three points in the mastergroup's calibration data, two or three points are on the same point.
Setting error
Remedy
(1)Check the following settings.
·Correct the BCD data so that it is within the limit.
(1)Check the following settings.
·Correct the binary data so that it is within the limit.
(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).
(1)Check the following settings.
·Correct the JOB that the number of steps will be three or more.
(1)Check the following settings.
·Do not use a coordinated motion with this manipulator.
(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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·Teach the data for calibration so that each point is different.
Alarm
Number
4469
4470
4471
Alarm Name
ROBOT CALIBRATION
FRAME ERROR
1
2
3
4
5
ROBOT CARIB STEP
NOT ENOUGH
ROBOT CALIBRATION
DATA ERROR
1
Sub
Code
8
Meaning
9
Cause
Among three points in the slavegroup's calibration data, two or three points are on the same point.
Setting error
The number of the teaching points for calibration data is insufficient.
Software operation error occurred
2
Remedy
(1)Check the following settings.
·Teach the data for calibration so that each point is different.
The calibration between manipulators cannot be executed for this model.
The master group and the slave group are set to the same group.
Incorrect designation of the control group for master group
Incorrect designation of the control group for slave group
Calibration data setting error
Incorrect number of teaching points for tool calibration
Incorrect designation of the occupation control group for calibration data
Setting error
Setting error
Software operation error occurred
Software operation error occurred
Software operation error occurred
Setting error
Software operation error occurred
Software operation error occurred
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·The calibration function between manipulators cannot be used for this model.
(1)Check the following settings.
·Set the different groups for the master group and the slave group.
(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).
(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).
(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).
(1)Check the following settings.
·Check the settings for number of the job steps
(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).
(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).
Alarm
Number
4473
4474
4475
4476
4477
Alarm Name
ARITHMETIC ALARM
RESET ERROR
WRONG CONTROL
GROUP AXIS
CANNOT EXECUTE JOB
(NO ROBOT)
CANNOT EDIT (EDIT
LOCK JOB)
0
1
2
SELECT ERROR
(APPLICATION)
Sub
Code
3
Meaning
Incorrect designation of the enabling control group for calibration data
4
Cause
Software operation error occurred
Incorrect designation of the control group for calibration data
Software operation error occurred
Software operation error occurred
Sub Code:The related controlgroup
Setting error
Setting error
An attempt was made to change the tag data.
An attempt was made to change the speed tag data.
An attempt was made to change the board thickness tag data.
Sub Code: Application number
Setting error
Setting error
Setting error
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).
(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).
(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).
(1)Check the following settings.
·Make the setting in advance so that the control group of the CALL/JUMP designation job is included in that of the CALL/JUMP source job.
·Don't start the job which including control group under already operation by
"PSTART.
(1)Check the following settings.
·Add the robot axis to the control-group of the job.
·A robot which executed SKILLSND is not defined as using MotoPlus sensor related API. Check the combination of the robot and MotoPlus application. If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Release the prohibition.
(1)Check the following settings.
·Release the prohibition.
(1)Check the following settings.
·Release the prohibition.
(1)Check the following settings.
·Set the application to a specified robot by the application selection of maintenance mode.
Alarm
Number
4478
Alarm Name
MM TASK NO
RESPONSE (MotoPlus)
Sub
Code
4479
4480
4485
4487
4490
MotoPlus MM TASK
WATCH DOG ERROR
SELECT ERROR
(SENSOR 1)
WRONG SELECTION
(SENSOR)
WRONG MECH
PARAMETER FILE
DEFECTIVE TAUGHT
POINT
(ENDLESS)
1
2
3
4
Meaning
Sub Code:Sensor number
After the Endless rotation completed, an attempt was made to execute an interpolation instruction such as MOVL and
MOVC before executing an
MRESET instruction.
Setting error
The base axis is set as an
Endless rotation axis. The
Endless function cannot be used with the base axis.
An attempt was made to execute the Endless function although the endless axis was not designated.
Setting error
Setting error
The Endless axis exceeded the maximum pulse value
(±536870911).
Setting error
Cause
Software operation error occurred
Software operation error occurred
Setting error
Software operation error occurred
Software operation error occurred
Remedy
(1)Turn the power OFF then back ON.
(2)If the alarm occurs again, replace controller and load the MotoPlus application which was loaded to the previous controller.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your contact your Yaskawa representative about occurrence status
(operating procedure).
Check if there is high priority task of MotoPlus application running long time.
Especially, check if there may be the process which waits for a special condition without executing mpTaskDelay in loop process. If such process exists, suitable remedy should be taken such as inserting mpTaskDelay, etc.
(1)Check the following settings.
·Select the option function for the specified robot in the option function selection of maintenance mode.
(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).
(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).
(1)Check the following settings.
·To perform an interpolation motion such as MOVL and MOVC after an Endless rotation, execute an MRESET instruction beforehand.
(1)Check the following settings.
·Check the parameter setting that designates the Endless rotation axis.
(1)Check the following settings.
·Check the parameter setting that designates the Endless rotation axis.
(1)Check the following settings.
·Set the rotation amount so that the Endless axis does not exceed the maximum pulse value.
Alarm
Number
4491
Alarm Name
CORRECTIONAL
DIRECTION ERROR
4492
4493
POSITION
CORRECTION ERROR
1
OVER TOOL FILE NO.
Sub
Code
1
Meaning
2
3
4
5
2
Cause
Control-group designation error for correcting-direction preparation
Software operation error occurred
Designation error for the correcting-direction coordinates
Software operation error occurred
When "any direction" is set for the correcting direction, the correction coordinates is not prepared.
Setting error
When "any direction" is set for the correcting direction, the reference points (REFP) are taught on the same point.
Setting error
Designation error for the coordinated motion control axis at the reference point
Setting error
Data unmatched between the correction amount data and the job data:
The information about the control groups designated for the series of jobs, which is added to the correction amount data, does not include the valid control-group for the job.
Software operation error occurred
Data unmatched between the correction amount data and the job data:
The valid control-group information that is added to the correction amount data disagrees with the valid control-group for the job.
Software operation error occurred
Software operation error 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).
(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).
(1)Check the following settings.
·Check the settings for the correcting direction with the reference point (REFP).
(1)Check the following settings.
·Check the settings for the reference points (REFP) so that each point is different.
(1)Check the following settings.
·Match the control group designation of the wall point and weaving execution.
(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).
(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).
(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).
Alarm
Number
4495
Alarm Name
UNDEFINED ROBOT
CALIBRATION
4496 PARAMETER ERROR
Sub
Code
Meaning Cause
Sub Code: Control group which calibration is not completed
Setting error
1 The setting of the manipulator number is incorrect.
Setting error
2 Zero is set for the resolution.
Setting error
3
4
5
6
7
8
Zero is set in the feedback pulse parameter.
Setting error
The setting of L-axis ball-screw data is incorrect.
Setting error
The setting of U-axis ball-screw data is incorrect.
Setting error
Zero or a negative value is set for
MAXPPS.
Setting error
Zero or a negative value is set for the maximum acceleration speed.
Setting error
Zero or a negative value is set for the maximum deceleration speed.
Setting error
Remedy
(1)Check the following settings.
·Before using the coordinated motion, execute the calibration between manipulators.
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
9
Meaning Cause
Zero or a negative value is set for the play-mode servo averaging time.
Setting error
10
11
12
13
The setting of the manipulator number is incorrect. An undefined type is designated.
Setting error
The incorrect coordinate system is designated for the cubic interference. An undefined coordinate system is set.
Setting error
The designation of the user coordinates number is incorrect.
A number out of the setting range is set.
Setting error
The reduction ratio <= 0 is output.
Setting error
14
15
16
17
Zero or a negative value is set for the spring constant.
Setting error
Zero or a negative value is set for the motor inertia.
Setting error
Zero or a negative value is set for the speed calculation constant.
Setting error
Dividing number setting error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
18
Meaning Cause
The setting of allowable torque for the speed reducer is incorrect.
Setting error
19
21
22
33
35
36
The setting of allowable torque for the motor is incorrect.
Setting error
Zero or a negative value is set for the balancer.
Setting error
The angle of hexagon set for the
CUT instruction is out of the range
"0 degree < angle < 60 degrees".
Setting error
Zero is set for the response time constant.
Setting error
Zero is set for the averaging time constant.
Setting error
Torque limit ratio data error Setting error
39
41
The setting in the optimized acceleration/deceleration designation parameter is incorrect.
The dynamics-model calculation at the optimized acceleration/ deceleration is invalid.
Setting error
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
42
Meaning
Zero is set for the inertia of dynamics fixed model.
43
44
45
46
47
48
49
50
Cause
Setting error
Designation error for dynamicsmodel calculation type
Setting error
The optimized acceleration/ deceleration control of speed limit function is disabled.
Setting error
The axis designation parameter for the speed limit function is not set.
Setting error
The setting in the mode designation parameter for the speed limit function is incorrect.
Setting error
Zero or negative value is set in the allowable braking torque parameter for the speed limit function.
Zero or a negative value is set in the speed adjustment ratio parameter for the speed limit function.
Setting error
Setting error
Zero or a negative value is set in the torque limit adjustment ratio parameter for the acceleration/ deceleration tuning.
Zero or a negative value is set in the parameter that sets the shortest acceleration/deceleration time for when the excessive torque is applied at the optimized acceleration/deceleration.
Setting error
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
51
Meaning
Zero is set for the dimension information "a3" for the SKR manipulator.
53
54
56
85
86
87
92
93
Cause
Setting error
The parameter setting for the
Cartesian manipulator X-axis data is incorrect.
Setting error
The parameter setting for the
Cartesian manipulator Y-axis data is incorrect.
Setting error
Zero or a negative value is set in the FORMCUT maximum acceleration/deceleration time parameter.
The setting of wrist axis angle for tube-incorporated wrist type manipulators or three-roll wrist type manipulators is incorrect.
Setting error
Setting error
The special link JOG operation cannot be used with this manipulator.
Setting error
The setting in the parameter for special angle limit check designation is incorrect.
Setting error
A negative value is set in the roundness parameter for the pathpriority control.
Setting error
The link parameter for the cutting device is not set.
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
95
Meaning Cause
The real-time bending correction function is enabled for a controlgroup other than robot axis.
Setting error
96
97
103
Zero is set for the dimension information "a2" for the Arc Cell
Torch Arm type manipulators.
Setting error
Zero is set for the deceleration ratio for double T-axis unit of the
V-shaped double T-axis manipulator.
"
α
" is replaced with "0" in SKR1-5 type robot.
Setting error
Setting error
118 Wrong value in set for backlash correction function.
Setting error
121 Incorrect parameter setting to inertia speed control function.
Setting error
122
123
124
Incorrect acceleration/ deceleration time setting at tool mass acceleration/deceleration speed correction function.
Incorrect coefficient/item settings at tool mass acceleration/ deceleration speed correction function.
No tool mas as the minimum acceleration/deceleration time at tool mass acceleration/ deceleration speed correction function.
Setting error
Setting error
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
125
Meaning
Incorrect speed setting at tool mass acceleration/deceleration speed correction function.
Cause
Setting error
126
127
129
130
131
Incorrect coefficient/item settings at tool mass acceleration/ deceleration speed control function.
No tool mass as the maximum acceleration/deceleration time at tool mass acceleration/ deceleration speed control function.
An error in the standard arithmetical axis number setting for approximation model.
Setting error
Setting error
Setting error
An error in the standard expanding point number setting for approximation model.
Setting error
An error in the radius setting for approximation model.
Setting error
132 setting error of arithmetical axis number in D-H method.
Setting error
133
135 setting error of choosing no / wrong connection base arithmetical axis number in D-H method.
Base axis control point → Robot coordinate system offset setting prohibited
Setting error
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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
136
Meaning
Pulse linked JOG function specification error
Cause
Setting error
137 Dual drive control specification error
Setting error
4497 DEFECTIVE TAUGHT
POINT (CALIB)
1
2
138
139
3
4
5
6
7
Notch filter supported acceleration and deceleration tuning: Notch filter function setting error
Setting error
Notch filter supported acceleration and deceleration tuning: Notch filter (z2) setting error
Some of the teaching points for master-group are on the same point.
Some of the teaching points for slave-group are on the same point.
Setting error
Setting error
Setting error
The 2nd-axis positions of C3, C4, and C5 of station axes are not the same.
Setting error
The 1st-axis positions of C1, C2, and C3 of station axes are not the same.
Setting error
The 2nd-axis positions of C1, C2, and C3 of station axes are the same.
Setting error
Setting error The 1st-axis rotation direction of
C3, C4, and C5 of station axes are not the same.
The 1st-axis (elevation axis) positions of C1, C2, and C3 of station axes are not the same.
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).
(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).
(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).
(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).
(1)Check the following settings.
·Perform the teaching again so that the teaching points are different from one another.
(1)Check the following settings.
·Perform the teaching again so that the teaching points are different from one another.
(1)Check the following settings.
·Perform the teaching again so that the 2ndaxis positions of C3, C4, and C5 of the station axes are the same.
(1)Check the following settings.
·Perform the teaching again so that the 1staxis positions of C1, C2, and C3 of station axes are the same.
(1)Check the following settings.
·Perform the teaching again so that the teaching positions are different from one another.
(1)Check the following settings.
·Perform the teaching again so that the 1staxis rotation direction of C3, C4, and
C5 of station axes are the same.
(1)Check the following settings.
·Perform the teaching again so that the 1staxis (elevation axis) positions of C1,
C2, and C3 of station axes are the same.
Alarm
Number
4498
4499
4500
4501
Alarm Name
CANNOT EXECUTE JOB
(NO GRP AXIS)
UNDEFINED POSITION
VARIABLE
UNDEFINED USER
FRAME
OUT OF RANGE
(PARALLEL PROCESS)
Sub
Code
8
Meaning Cause
The 1st-axis (elevation axis) positions of C3, C4, and C5 of station axes are not the same.
An attempt was made to execute an instruction that could not be executed in a job without control group.
Sub Code: The variable number
Setting error
Setting error
Setting error
Sub Code: User coordinate number
Sub Code: Task number
Setting error
Software operation error occurred
4502
4507
4508
SL BOARD ON-LINE
ERROR
REFP POS ERROR
(SEARCH MOTION)
SPECIFIED ERROR
(COORDINATE)
0
1
2
The option board was detected not to operate normally at power
ON.
Software operation error occurred
Setting error
The specified coordinate system does not exist.
Designation error of the master tool coordinate system. This coordinate system cannot be used.
Designation error of the tool coordinate system. This coordinate system cannot be used.
Setting error
Setting error
Setting error
Remedy
(1)Check the following settings.
·Perform the teaching again so that the 1staxis (elevation axis) positions of C3,
C4, and C5 of station axes are the same.
(1)Check the following settings.
·Check the settings for the job instruction with control group.
(1)Check the following settings.
·Check the settings for the position type variable.
(1)Check the following settings.
·Check the settings for the user coordinate.
(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).
(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).
(1)Check the following settings.
·Perform the teaching again so that the search start point and the motion target point are not the same.
·Increase the distance between the search start point and the motion target point.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
Alarm
Number
4509
4510
4511
4512
4513
Alarm Name
MFRAME ERROR
CANNOT EXECUTE
INSTRUCTION (SQRT)
OUT OF RANGE
(DROP-VALUE)
TWO STEPS SAME LINE
(3 STEPS)
EXCESSIVE SEGMENT
(SAFETY 1): LOW/HIGH
Sub
Code
3
Meaning
4
6
10
11
1
Cause
Designation error of the direction of travel coordinate system (for a shared function). This coordinate system cannot be used.
Designation error of the any direction coordinate system (for a shared function). This coordinate system cannot be used.
Designation error of the conveyor coordinate system. This coordinate system cannot be used.
Setting error
Setting error
Setting error
Designation error of the cylindrical coordinate system. This coordinate system cannot be used.
Setting error
Designation error of the coordinate system for the external reference point. This coordinate system cannot be used.
The master-tool user coordinates could not be prepared.
Setting error
Setting error
Setting error
Sub Code: Control group exceeding the allowable value
Setting error
Setting error
Sub Code: Control group and axis Setting error
Remedy
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Check the settings for the coordinate system which can be used.
(1)Check the following settings.
·Execute the MFRAME instruction in coordinated job when you make the master tool user coordinate.
(1)Check the following settings.
·Check the job settings so that the second argument of SQRT instruction does not become negative.
(1)Check the following settings.
·Confirm the load setting to the robot.
(1)Check the following settings.
·Check the settings so that the teaching points are not aligned in a straight line.
(1)Check the following settings.
·Reduce the speed of the step where the alarm occurred.
·Change the move instruction to joint interpolation (MOVJ).
* Be careful to the peripheral interference since its movement changes.
Alarm
Number
4515
Alarm Name
EXCESSIVE SEGMENT
(SAFETY 2): LOW/HIGH
Sub
Code
4517
4518
4521
4522
SEARCH MONITOR SET
ERROR (SERVO)
SEARCH MON
RELEASE ERROR
(SERVO)
WRONG JOB TYPE
TAG DATA CHANGE
PROCESS ERROR
0
1
2
Meaning Cause
Sub Code: Control group and axis Setting error
Sub Code: The related controlgroup
Software operation error occurred
Sub Code: The related controlgroup
Software operation error occurred
Remedy
(1)Check the following settings.
·Reduce the speed of the step where the alarm occurred.
·Change the move instruction to joint interpolation (MOVJ).
* Be careful to the peripheral interference since its movement changes.
(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).
(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).
(1)Check the following settings.
·Check the settings for the job to be started.
Sub Code
0000_0001: A robot job was started from the concurrent job at
CALL/JUMP instruction execution.
0000_1001: A concurrent job was started from the robot job at
CALL/JUMP instruction execution.
1000_0001: A system job was started from the robot job at
CALL/JUMP instruction execution.
An attempt was made to change the contents of variable tag data.
Setting error
Setting error
An attempt was made to change the tag data for the job prohibited from being edited.
Setting error
An error occurred at instruction read-in.
Software operation error occurred
(1)Check the following settings.
·The variable tag cannot be changed. Correct the job so as not to use the variable tag.
(1)Check the following settings.
·Release the prohibition.
(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).
Alarm
Number
4524
4525
4527
4528
4529
Alarm Name
CANNOT EXECUTE
INST (COUCUR JOB)
CANNOT EXECUTE
SPECIFIED JOB
1
2
UNDEFINED PORT
NO.(AOUT)
SYNTAX ERROR
TWIN COORDINATED
ERROR
1
2
Sub
Code
3
4
5
7
3
1
Meaning
The tag is not registered.
Cause
Software operation error occurred
The tag data was variable specification.
Setting error
The value which it was made to change exceeded the limit of tag data.
An error occurred at tag data change.
Setting error
Software operation error occurred
Setting error
An interrupt job (user setting) is started up during the back operation.
An interrupt macro job is started up during the back operation.
Setting error
Setting error
An interrupt job (inside the system) is started up during the back operation.
Setting error
Setting error
A syntax error was found in the IF sentence.
Software operation error occurred
A job without control group was started by SYNC instruction.
A job only with robot axes was started by SYNC instruction.
Setting error
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).
(1)Check the following settings.
·The variable tag cannot be changed. Correct the job so as not to use the variable tag.
(1)Check the following settings.
·Check the contents of changing data.
(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).
(1)Check the following settings.
·Delete an instruction that cannot be executed such as move instruction in the concurrent job.
(1)Check the following settings.
·Check the job so that the interrupt job will not start-up during the back operation.
(1)Check the following settings.
·Check the job so that the interrupt macro job will not start-up during the back operation.
(1)Check the following settings.
·Check the job so that the interrupt job will not start-up during the back operation.
(1)Check the following settings.
·Check the settings for the specified analog output port number.
(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).
(1)Check the following settings.
·Check the control group setting of the job to be started by SYNC.
(1)Check the following settings.
·Check the control group setting of the job to be started by SYNC.
Alarm
Number
4530
Alarm Name
8
CONVEYOR TRACKING
ERROR
1
2
Sub
Code
3
Meaning
4
5
Cause
A job only with master control group axes was started by SYNC instruction.
At full synchronization, the completion timings of move instructions for the master and the slave disagreed.
Setting error
Software operation error occurred
At full synchronization, no operation request from the master was sent.
Software operation error occurred
6
7
At full synchronization, the execution timings of move instructions for the master and the slave disagreed.
The twin synchronous ID number is incorrect.
Software operation error occurred
Software operation error occurred
3
4
An attempt was made to execute triple synchronization when specified Sub-master for the master was different.
The base axis specification is other than 1 or 2 for conveyor characteristic file.
No robot axis in the job for robot axis tracking
Setting error
Setting error
Setting error
No base axis in the job for base axis tracking
Setting error
The conveyor board number and conveyor characteristic file number used are incorrect.
Setting error
Remedy
(1)Check the following settings.
·Check the control group setting of the job to be started by SYNC.
(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).
(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).
(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).
(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).
(1)Check the following settings.
·Match the system number specification of the master between the job to be started by SYNC.
(1)Check the following settings.
·Set the base axis specification of conveyor characteristic file to either 0, 1, or 2.
(1)Check the following settings.
·Correct the job setting so that the robot axis tracking is executed in the job where robot axis exists.
(1)Check the following settings.
·Correct the job settings so that the base axis tracking is executed in the job where base axis exists.
(1)Check the following settings.
·Check the specification of conveyor condition file number for use.
Alarm
Number
4531
4532
4533
Alarm Name
UNDEFINED
CONVEYOR COND FILE
CONVEYOR SPEED
DOWN
ARITHMETIC ERROR
(CV TRACKING)
1
Sub
Code
5
Meaning
There was no conveyor start position data at prereading processing.
10
Cause
Software operation error occurred
No base axis in the job for arc tracking
Sub Code: Conveyor characteristic file number
Sub Code: Conveyor number
Setting error
Setting error
Setting error
Designation error of the conveyor tracking control-group
Software operation error occurred
2
3
4
5
6
7
Designation error of the user coordinates for the conveyor tracking
Software operation error occurred
An attempt was made to use the conveyor tracking function with the slave manipulator at coordinate motion.
Zero is set for the resolution for the turn-table synchronization.
Base axis tracking application error at the control whose conveyor coordinates are different.
Turn table tracking application error at the control whose conveyor coordinates are different.
Interpolation error of the control whose conveyor coordinates are different.
Setting error
Setting error
Setting error
Setting error
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).
(1)Check the following settings.
·Correct the job setting so that the arc tracking is executed in the job where robot axis exists.
(1)Check the following settings.
·Set "Use state" of conveyor characteristic file to "1: Use".
(1)Check the following settings.
·Correct the "Conveyor Lowest Speed" set in the conveyor characteristic file.
(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).
(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).
(1)Check the following settings.
·The conveyor tracking cannot be executed to the slave manipulator of the coordinate system. Correct the job so that the conveyor tracking perform by the robot unit or without coordinated motion.
(1)Check the following settings.
·Check the settings for the resolution.
(1)Check the following settings.
·Set the tracking system to "robot axis tracking".
·Do not operate between different conveyors while it is set to "base-axis tracking".
(1)Check the following settings.
·Do not operate between different conveyors while it is set to turn table synchronization.
(1)Check the following settings.
·Teach interpolation method to SYMOVL when operating between different conveyors.
Alarm
Number
4534
Alarm Name
TORQUE
INTERFERENCE
4535 TARGET VARIABLE
TYPE UNMATCHED
0
1
2
Sub
Code
Meaning
3
4
4538
4539
ROBOT AXIS TRACKING
INVALID
CORNER R CONTROL
ERROR
0
1
2
3
4
Cause
Setting error
An attempt was made to obtain the byte type system variable by the other type variable.
An attempt was made to obtain the integer type system variable by the other type variable.
Setting error
Setting error
An attempt was made to obtain the double-precision integer-type system variable by the other type variable.
An attempt was made to obtain the real-number type system variable by the other type variable.
Setting error
Setting error
An attempt was made to obtain the character-string type system variable by the other type variable.
Setting error
"SYMOVJ" instruction is executed at robot-axis tracking.
Setting error
The Corner-R motion cannot be used for coordinated motion.
An attempt was made to execute the Corner-R motion for the same point.
Setting error
Setting error
The Corner-R zone is taught on a straight line.
Setting error
The start position or end position for the Corner-R motion could not be calculated inside the start zone or the end zone.
Setting error
Remedy
(1)Check the following settings.
·Correctly set the weight information in the tool file. ( Are the weight: W and the number set to the load value of either Xg, Yg or Zg)
·Reduce the speed in the step where the alarm occurred.
(1)Check the following settings.
·Obtain as the byte type variable.
(1)Check the following settings.
·Obtain as the integer type variable.
(1)Check the following settings.
·Obtain as the double-precision integer-type variable.
(1)Check the following settings.
·Obtain as the real-number type variable.
(1)Check the following settings.
·Obtain as the character-string type variable.
(1)Check the following settings.
·Do not use "SYMOVJ" instruction in robot axis tracking.
(1)Check the following settings.
·Do not use the Corner-R motion for coordinated motion.
(1)Check the following settings.
·Check the settings for the teaching so that the start step and end step are not on the same point.
(1)Check the following settings.
·Check the settings for teaching so that the Corner-R zone is not on a strait line.
(1)Check the following settings.
·Make the setting for the Corner-R radius small.
·Make the moving amount of the Corner-R start step long.
·Make the moving amount of the Corner-R start end long.
Alarm
Number
4540
4541
Alarm Name
JOB QUE EMPTY
ERROR
INVALID INPUT STRING
(VAL)
1
Sub
Code
5
Meaning
6
8
17
18
20
Cause
The Corner-R motion cannot be used for coordinated motion
(with master manipulators).
Setting error
The Corner-R motion cannot be used for MOVC, MOVS, and
EIMOVC instructions.
Different tool numbers are set in a
Corner-R zone (for the Corner-R middle step and end step).
Setting error
Setting error
The Corner-R motion is disabled during conveyor tracking.
Setting error
Arithmetic error occurred when calculating the acceleration and deceleration time for the Corner-R operation
The Corner-R motion is disabled to start during continuous motion.
Setting error
Setting error
4542
4543
4544
MRESET ERROR
STACK LESS THAN 0
(JOB CALL)
MID$ INST ERROR
1
1
Setting error
There was no character string representing a constant in character string to be extracted at
VAL instruction execution.
Setting error
An MRESET instruction was executed while no endless axis was designated.
At job return, an attempt was made to fetch a data from an empty job call stack or to stack a data in the job call stack that is full.
The first character of character string to be extracted is null at
MID$ instruction execution.
Setting error
Software operation error occurred
Setting error
Remedy
(1)Check the following settings.
·Do not use the Corner-R motion for master manipulators at coordinated motion.
(1)Check the following settings.
·Use a MOVL instruction when using the Corner-R motion.
(1)Check the following settings.
·Use the same tool number in a Corner-R zone.
(1)Check the following settings.
·Do not perform the conveyor tracking when using the Corner-R motion.
(1)Check the following settings.
·Do not perform the conveyor tracking when using the Corner-R motion.
(1)Check the following settings.
·Make the setting for the Corner-R radius small.
·set Timer or PL=0 to a previous line.
(1)Check the following settings.
·Use "CALL QUE" under the condition that the job data is set to the job queue.
(1)Check the following settings.
·Check the settings for the data of the character string to be extracted.
(1)Check the following settings.
·Set the endless axis.
(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).
(1)Check the following settings.
·Check the settings for the data of the character string to be extracted.
Alarm
Number
4546
4547
4548
4549
4550
4565
Alarm Name
CANNOT EXCUTE
SYSTEM JOB
PRIMITIVE ERROR
CANNOT OPERATE
SPECIFIED EVENT
NOT EXECUTION OF
INIEVNT
CANNOT EXECUTE
INST (USER JOB)
SOFTWARE UNMATCH 1
Sub
Code
2
Meaning
The extraction start position exceeds the character string length at MID$ instruction execution.
Sub Code: System number
3
5
6
Cause
Setting error
Remedy
(1)Check the following settings.
·Check the settings for the data of the character string to be extracted.
Sub Code: Error code
Sub Code: System number
Sub Code: System number
Sub Code: System number
The multi-layer welding function is not used.
The TURBO function is not used.
Software operation error occurred
The conveyor/press synchronization function is not used.
Software operation error occurred
Software operation error occurred
Software operation error occurred
Setting error
Setting error
Software operation error occurred
Software operation error occurred
The shared motion function is not used.
Software operation error occurred
(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).
(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).
(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).
(1)Check the following settings.
·Execute an INIEVNT instruction before executing an event related instruction.
(1)Check the following settings.
·This instruction cannot be executed in the system job. Correct the job so that the instruction is executed in the user job.
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
7
Meaning Cause
The layer motion function is not used.
Software operation error occurred
8
9
10
11
12
14
15
16
The general sensor function is not used.
Software operation error occurred
The servo float function is not used.
Software operation error occurred
The laser cutting function (with small circle cutter) is not used.
Software operation error occurred
The motor gun function (for spot welding application) is not used.
Software operation error occurred
The speed control function
(VCON/VCOF) is not used.
Software operation error occurred
The laser cutting function (for form cutting operation) is not used.
The series communication function between the systems
(PSEND/PRECV) is not used.
Software operation error occurred
Software operation error occurred
The motion extension function is not used.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4566
Alarm Name
Sub
Code
17
Meaning Cause
The bending function is not used.
Software operation error occurred
18
19
20
USER FRAME MAKING
ERROR
1
255 An attempt was made to execute an undefined instruction.
Software operation error occurred
2
3
5
The ME-NET function is not used.
Software operation error occurred
The MEMO-PLAY function is not used.
Software operation error occurred
The 3D-SHIFT function is not used.
Software operation error occurred
The teaching points are incorrect.
Software operation error occurred
The teaching points for usercoordinate turning are incorrect.
Setting error
The robot axis is not specified for the control group of the job to prepare the user coordinates.
Software operation error occurred
Position data error Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·Among three taught points in the teaching position. Teach the three points again so that they do not lie in the straight line.
(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).
(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).
Alarm
Number
4567
4568
4569
4571
4579
4581
4585
4591
Alarm Name
CANNOT MONITOR
DISTANCE
UNDEFINED PRESS
COND DATA FILE
UNDEFINED PRESS
RESOLUTION DATA
SERVO FLOAT MODE
RELEASE ERROR
ANTICIPATION
CONTROL ERROR
DEFECTIVE
ANTICIPATION OT FILE
1
2
SERVO PG ON ERROR
SPEED CTRL MODE
SET ERROR
(SERVO)
Sub
Code
6
Meaning Cause
Setting error of the slave group for user coordinate conversion
Software operation error occurred
1
2
Setting error
Sub Code: Press characteristic file number
Sub Code: Press characteristic file number
Setting error
Setting error
Software operation error occurred
No availability in anticipation control
Setting error
The anticipation data exceeded the maximum length.
Software operation error occurred
Incorrect setting of OT output number for anticipation output file
Incorrect setting of OG output number for anticipation output file
Setting error
Setting error
Connection failure
Software operation error 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).
(1)Check the following settings.
·Change the interpolation instruction to MOVL/MOVC.
·Change the setting so that the arc retry or restart operation does not perform.
(1)Check the following settings.
·Set the status of press characteristic file to be used in the job to "Used State".
(1)Check the following settings.
·Set the press resolution data to be used in the job.
(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).
(1)Check the following settings.
·Maximum simultaneous execution number of anticipation control is five.
Correct the settings for the job so that it is within five.
(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).
(1)Check the following settings.
·Check the setting value of OT output number.
(1)Check the following settings.
·Check the setting value of OG output number.
(1)Reset the alarm, and then try again.
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
·Each axes encoder cable
(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).
Alarm
Number
4592
Alarm Name
SPEED CTRL MODE
CANCEL ERROR(SV)
4595 CAN'T DO FIXED FORM
CUT MOTION
1
Sub
Code
2
3
4
Meaning Cause
Software operation error 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).
(1)Check the following settings.
·Setting of the radius data
The setting for radius is incorrect.
(1) For a circle, it is incorrectly set as: radius <= 0, or radius < minimum radius value, or radius > maximum radius value.
(2) For an ellipse, it is incorrectly set as: radius <= 0 or radius < minimum radius value/2, or radius
> (maximum radius/2 - width/2) value.
Setting error
The setting for width is incorrect.
(1) For a rectangle, it is incorrectly set as: width < 1.0, width > sqrt
(maximum diameter2 - height2), or width > maximum diameter.
(2) It is incorrectly set as: width <
0, width > maximum diameter -2 * radius.
Setting error
The setting for height is incorrect.
(1) For a rectangle, it is incorrectly set as: height > maximum diameter, height < minimum diameter/2, or height > sqrt
(maximum diameter
2
- width
2
).
Setting error
The setting for the corner radius is incorrect.
(1) For a rectangle, it is incorrectly set as: corner radius > width/2 or corner radius > height/2.
Setting error
(1)Check the following settings.
·Setting of the width data
(1)Check the following settings.
·Setting of the height data
(1)Check the following settings.
·Setting of the corner radius
Alarm
Number
Alarm Name
4596 FORMCUT ERROR
Sub
Code
5
Meaning
6
7
8
9
10
11
1
Cause
The setting for overlap is incorrect.
(1) For a rectangle, it is incorrectly set as overlap > width/2.
(2) For a circle, it is incorrectly set as overlap > ABS (2
π
* radius).
(3) For an ellipse, it is incorrectly set as overlap > π * radius +ABS
(width/2).
The setting for the cutting speed is incorrect. It is set as the cutting speed > maximum linear speed.
Setting error
Setting error
Coordinated motion cannot be used with the Form Cutting motion.
Setting error
Zero or a negative value is set in the minimum diameter parameter
(S1CxG063) for the Form Cutting motion.
Zero or a negative value is set in the maximum diameter parameter
(S1CxG064) for the Form Cutting motion.
Setting error
Setting error
Although "PLACEMENT" or
"AUTO" is set for the start point designation on the FORM CUT
SETTING window, the FORMAPR instruction was not executed.
Setting error
Setting error The Cut file setting of the
FORMAPR instruction is different from that of the FORMCUT instruction.
An attempt was made to reexecute the FORMCUT instruction after interrupting it.
Execute condition failure
Remedy
(1)Check the following settings.
·Setting of the overlap data
(1)Check the following settings.
·Setting of the cutting speed
(1)Check the following settings.
·Do not use the coordinated motion.
(1)Check the following settings.
·The setting of the minimum diameter parameter (S1CxG063) for the Form
Cutting motion.
(1)Check the following settings.
·The setting of the maximum diameter parameter (S1CxG064) for the Form
Cutting motion.
(1)Check the following settings.
·Execute the FORMAPR instruction.
(1)Check the following settings.
·The Cut file settings of FORMAPR and FORMCUT instructions must be same.
(1)Check the following settings.
·Re-execute the move instruction executed before the FORMCUT instruction, and then execute the FORMCUT instruction again.
Alarm
Number
4597
Alarm Name
OFFLINE POSITION
DATA CONVERT ERROR
Sub
Code
1
Meaning Cause
Incorrect information of reference position data for offline position data conversion
Software operation error occurred
3 Incorrect reference-point data for offline position data conversion
Software operation error occurred
4
5
6
7
8
9
10
The standard position data for offline position data conversion could not correctly be calculated.
Setting error
Incorrect pulse incremental value for offline position data conversion
Software operation error occurred
The position data could not correctly be added by the pulse incremental value at the offline position data conversion.
Incorrect Cartesian incremental value for offline position data conversion
Software operation error occurred
Software operation error occurred
The position data could not correctly be added by the
Cartesian incremental value at the offline position data conversion.
Setting error
The position conversion could not be done in the designated coordinate system at the offline position data conversion.
Software operation error occurred
Incorrect incremental value of angle for offline position data conversion
Software operation error 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).
(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).
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(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).
(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).
(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).
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(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).
(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).
Alarm
Number
4599
4604
Alarm Name
SERVO COMMAND
ERROR
SPECIFIED ERROR
(ABSO RECOVER AXIS)
Sub
Code
11
Meaning
14
Cause
The position data could not correctly be added by the incremental value of angle at the offline position data conversion.
The reverse shift value could not correctly be calculated at the offline position data conversion.
Software operation error occurred
Software operation error occurred
15
17
19
20
22
The reverse shift value could not correctly be calculated at the offline position data conversion.
Software operation error occurred
The shift value could not correctly be added at the offline position data conversion.
Software operation error occurred
The positions for the mirror shift function could not correctly be calculated at the offline position data conversion.
The positions could not correctly be converted for the mirror shift function at the offline position data conversion.
Software operation error occurred
Setting error
Incorrect designation of coordinates for a new mirror-shift conversion function at the offline position data conversion
An attempt was made to issue the command while the servo control processing has not completed.
Sub Code: Servo CPU bit number
Software operation error occurred
Software operation error occurred
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).
(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).
(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).
(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).
(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).
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(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).
(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).
(1)Check the following settings.
·Registration for the home position correction data.
Alarm
Number
4605
4606
4607
4608
4611
4612
Alarm Name
SETTOOL ERROR
LACK OF GLOBAL
VARIABLE AREA
WRONG EXECUTION
OF MACRO INST
1
2
3
WRONG EXECUTION
OF GETARG INST
1
2
3
OVER OPTON INST
EXECUTION LIMIT
TSYNC ERROR
Sub
Code
1
Meaning Cause
The difference between the current tool constant and a new set value exceeded the allowable range (parameter set value).
Setting error
Software operation error occurred
5
6
The execution macro job is not set.
Setting error
The interrupt macro job is not set.
Setting error
An attempt was made to start the job that could not be started by the macro instruction.
Setting error
An error occurred in the operation process of job call stack when the execution of macro instruction was cancelled.
Software operation error occurred
Incorrect macro number Software operation error occurred
The job argument is not set.
Setting error
No number of the specified job argument
The data types of job argument disagreed.
Setting error
Setting error
Setting error
Sub code: the number of synchronizations of the first executed TSYNC
Setting error
Remedy
(1)Check the following settings.
·Correct the job so that the setting value of tag is allowable value.
·Set the allowance amount of the tool data automatic setting function maximum deviation (S3C1192) to large value.
(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).
(1)Check the following settings.
·Check the settings for execution macro job.
(1)Check the following settings.
·Check the settings for interrupt macro job.
(1)Check the following settings.
·Check the settings for macro job.
(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).
(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).
(1)Check the following settings.
·Check the settings for jobs.
(1)Check the following settings.
·Check the settings for jobs.
(1)Check the following settings.
·Check the settings for jobs.
(1)Check the following settings.
·Check the settings for the OPTON instruction. OPTON instruction can use only the function to five simultaneously.
(1)Check the following settings.
·Check the settings for the number of synchronizations of the TSYNC instruction.
Alarm
Number
4615
Alarm Name
I/O AXIS OPERATING
4619
4620
UNDEFINED JOB
ENTRY TABLE
ARM (TOOL)
INTERFERENCE
4622 SELF-INTERFERENCE
Sub
Code
Meaning
An attempt was made to command a job whose control group was in I/O axis motion.
Cause
Setting error
Sub Code:Designated registration number
Sub Code: Interfering control group and axis & interfered control group and axis.
Setting error
Setting error
Sub Code:Control group & interfering axis number & interfered axis number.
Setting error
4623 WRONG EXECUTION
OF GETPOS INST
1 An attempt was made to obtain the step that used a local position type variable. (The step with local position type variable cannot be fetched. Example: MOVJ LP000
VJ=25.00)
Setting error
Remedy
(1)Check the following settings.
·Does not the I/O axis motion executed for the control group that executing the job?
·Does not the job executed for the control group that operating by the I/O axis motion?
The control group where the I/O axis is operating
(1)Check the following settings.
·Check the settings for the job registration table.
(1)Check the following settings.
·Modify the teaching so that the robots indicated by the sub code would not interfere each other.
·Confirm the tool mode (tool interference file) of the robots indicated by the sub code would not interfere each other.
·Confirm the calibration between the robots is set correctly.
(1)Check the following settings.
·Modify the teaching so that the robots indicated by the sub code would not interfere each other
·Confirm the tool mode (tool interference file) of the robots indicated by the sub code would not interfere each other
(2) If the manipulator is stopped near the interference area by servo OFF, it may interfere with the interference area.
In this case, execute the following operations to disable the self interference check and move each part out of the interference area.
- Change the mode to "TEACH"
- To display LIMIT RELEASE window, select the main menu [ROBOT] and then
[LIMIT RELEASE]
- Change the setting for SELF INTERFERENCE RELEASE from "INVALID" to
"VALID" by [SELECT] key
- Move each part out of the interference area
- Change the setting for SELF INTERFERENCE RELEASE from "VALID" to
"INVALID" by [SELECT] key
NOTE) Be sure to check the operation direction since the above operations enable manipulator's parts to interfere with each other.
(1)Check the following settings.
·Check the settings for the GETPOS instruction.
Alarm
Number
4628
4629
4632
4635
Alarm Name
WRITE VARIABLE NO.
MULTI SETTING
GROUP CHANGE
ERROR
1
2
UNDEFINED LNR
SCALE FILE
CANNOT EXECUTE
COMMON JOB
3
4
5
Sub
Code
2
Meaning
3
Cause
An attempt was made to obtain the step that used a local position type variable. (The step with local position type variable cannot be fetched. Example: MOVJ LP000
VJ=25.00)
The specified step did not exist.
Setting error
Setting error
6
7
8
Sub Code: Duplicated variable number
The group change parameter was invalid.
Setting error
Setting error
The GRPCHG instruction was executed while the external axis motor was servo ON.
The GRPCHG instruction was executed in unchuck status.
Setting error
Setting error
The group identification signal was not received.
Setting error
The specified control group number and the group identification number were unmatched.
The encoder PG power supply was OFF when the GRPCHG was
ON.
Setting error
Setting error
Setting error The encoder PG power supply was ON when the GRPCHG was
OFF.
The control group that corresponded to the received group identification signal did not exist.
Sub Code: Linear scale characteristic file number
Setting error
Setting error
Sub Code: The related controlgroup
Setting error
Remedy
(1)Check the following settings.
·Check the settings for the GETPOS instruction.
(1)Check the following settings.
·Check the settings for the GETPOS instruction.
(1)Check the following settings.
·Check the settings for the written destination variable numbers.
(1)Check the following settings.
·Validate the group change parameter.
(1)Check the following settings.
·Execute the GRPCHG instruction when the external axis motor was servo
OFF.
(1)Check the following settings.
·Execute the GRPCHG instruction in chuck status.
(1)Check the following settings.
·Check the settings for group identification signal.
(1)Check the following settings.
·Check the settings for the specified control group number.
(1)Check the following settings.
·Turn ON the encoder PG power supply when GRPCHG is ON.
(1)Check the following settings.
·Turn OFF the encoder PG power supply when GRPCHG is OFF.
(1)Check the following settings.
·Check the settings for group identification signal.
(1)Check the following settings.
·Complete the settings for the linear scale condition file.
(1)Check the following settings.
·Check the settings for control group specified by the CALL instruction.
Alarm
Number
4637
Alarm Name
TRACK CHG WORK IN/
NOT NOT FOUND
Sub
Code
4638
4639
TRACKING CHG WORK
ID NOT FOUND
SYMOVJ INST
EXECUTE ERROR
2
3
4640
4641
4649
4650
WRONG EXECUTION
OF PSTART INST
CANNOT EXECUTE JOB
(SEPARATE GRP)
PARTIAL OPERATION
AREA INTERFERENCE
TRQ CLEAR ERROR
4
1
2
3
Meaning
Sub Code: Conveyor characteristic file number
Sub Code: Conveyor characteristic file number
Cause
Setting error
Setting error
The conveyor moving amount is not specified for the SYMOVJ motion.
Setting error
An error occurred in the preparation process of the manipulator motion start position for the SYMOVJ motion.
An error occurred in the preparation process of the manipulator motion end position for the SYMOVJ motion.
Software operation error occurred
Software operation error occurred
No axis data of control group to be disconnected
Setting error
An attempt was made to disconnect a control group other than the occupation control group during prereading processing.
Setting error
An attempt was made to disconnect a control group other than the occupation control group when executing a PSTART instruction.
Setting error
Sub Code: The disconnected control group used by a move instruction
Setting error
Sub Code: Interference control group number & interference axis
& interference area number.
Setting error
Software operation error occurred
4651 PALLETIZING EXECUTE
ERROR
1 The setting of the pelletizing condition configuration file is incomplete.
Setting error
Remedy
(1)Check the following settings.
·Check the workpiece presence/absence and data settings for the synchronization section.
(1)Check the following settings.
·Check the workpiece presence/absence and data settings for the synchronization section.
(1)Check the following settings.
·Set the conveyor moving amount for the SYMOVJ motion.
(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).
(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).
(1)Check the following settings.
·Check the settings for PSTART instruction.
(1)Check the following settings.
·Check the settings for PSTART instruction.
(1)Check the following settings.
·Check the settings for PSTART instruction.
(1)Check the following settings.
·Correct the teaching so that the control group disconnected by itself is not to operate for move instruction of own system.
(1)Check the following settings.
·Check the teaching position setting of manipulators.
(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).
(1)Check the following settings.
·Set the pelletizing condition setting file to “Completed”.
Alarm
Number
4652
Alarm Name
TRQ MEASURE MODE
SET ERROR(SV)
Sub
Code
4
Meaning
5
6
7
8
Cause
Pelletize completion universal output number range exceeds the limit.
Setting error
During the pelletize start instruction execution, the pelletize start instruction is executed again
(double execution).
Setting error
The value of the pelletizing number present value output register (or I variable) is more than the total number output register (or I variable).
Setting error
Pelletize completion universal output signal is turned ON at pelletize start instruction execution.
Pelletize end instruction is not registered.
Setting error
Setting error
Software operation error occurred
4653 TRQ MEASURE MODE
CANCEL ERROR(SV)
Software operation error occurred
4654
4655
4656
WRONG EXECUTION
OF SETREG INST
1
WRONG EXECUTION
OF GETREG INST
1
WRONG EXECUTION
OF SETPRM INST
1
2
An attempt was made to change the value of the register currently used by TMR/CNT.
Setting error
An attempt was made to acquire the value of the register not existing.
Software operation error occurred
An attempt was made to change a parameter other than the cuberelated parameter.
Setting error
The SETPRM instruction was executed while another system was in execution.
Setting error
Remedy
(1)Check the following settings.
·Change the pelletize completion universal output signal number of the pelletizing condition setting file in the user output signal point of contact number.
(1)Check the following settings.
·Delete the pelletize start instruction in the pelletize section.
(1)Check the following settings.
·Check if the pelletizing number of current position output register (or I variable) and total number of output register (or I variable) is not changed by another function.
(1)Check the following settings.
·Reset the pelletize completion universal output signal.
(1)Check the following settings.
·Register the pelletizing end instruction.
(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).
(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).
(1)Check the following settings.
·The SETREGM instruction cannot change the register values used in TMR/
CNT. Correct the setting of tag that specifies register number of SETREG instruction.
(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).
(1)Check the following settings.
·The SETPRM instruction cannot change the parameter values other than the parameter related to the cube. Correct the setting of tag that specifies parameter number of SETPRM instruction.
(1)Check the following settings.
·The SETPRM instruction cannot execute while another system is operating.
Correct the job.
Alarm
Number
4670
Alarm Name
4671
4672
INSUFFICIENT NUM OF
SAMPLE DATA
SAMPLE BUFFER OVER
FLOW
BASIC SPEED
UNREACHED
Sub
Code
4673
4676
MAX TRQ
UNDETECTED
BROKEN FAN FUSE
4677 IMPOSSIBLE LINEAR
MOTION
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause
Setting error
Setting error
Setting error
Sub Code: Signifies the axis in which the alarm occurred
Setting error
Sub Code: Signifies the YSU unit number in which the alarm occurred
Connection failure
Fuse failure
Sub Code: Control group and axis Setting error
4681 OVER SPEED
(MainCPU)
4682 MOTION RANGE LIMIT
INTERFERENCE
4683 AXIS MOTION RANGE
LIMIT OVER(MIN./MAX.)
4684 INTERPOLATION
INVALID
Sub Code: Control group and axis Setting error
Sub Code: Manipulator number Setting error
Sub Code: Control group and axis Setting error
Sub Code: Control group Setting error
Remedy
Lengthen the measurement section.
Shorten the measurement section.
Increase the speed specification value of a measurement job or set a small value for BASICV.
Or set a small value for BASICT, or lengthen the measurement section.
Set a large value for the BASICT, and then check again.
(1)Reset the alarm.
(2)If the alarm occurs again, check if there is a ground fault or short circuit in the fan power line.
(After cancellation of the short-circuit and ground fault) Replace the fuse.
(1)Check the following settings.
·If the sub code display is L- and U-axes, perform the teaching again to make the form (arm folded direction) of L- and U-axes same at start point and end point.
·If the sub code display is S- and L-axes, perform the teaching again to make the form (arm folded direction) of S- and L-axes same at start point and end point.
·Change the teaching move instruction to MOVJ instruction. *Be carefull to the interefernces with peripheral environment, because the robot changes its motion.
(1)Check the following settings.
·Reduce the speed of the step where the alarm occurred.
·Change the move instruction to joint interpolation (MOVJ).
* Be careful to the peripheral interference since its movement changes.
(1)Check the following settings.
·Modify the teaching position or widen the operation area so that the robot would not interfere with the operation area.
·Confirm the setting of the robot tool mode (tool interference file) which the control group is indicated.
(1)Check the following settings.
·Modify the teaching position or widen the operation area so that the robot would not interfere with the operation area.
·Confirm the setting of the operation area which the control group is indicated by the sub code.
(1)Check the following settings.
·At the cartesian jog operation, switch to each-axes jog operations, and then change the orientation of manipulator.
·Change the teaching position and orientation.
Alarm
Number
4696
4697
Alarm Name
TURN TABLE
CALIBRATION ERROR
Sub
Code
1
Meaning
2
3
OFFLINE ARM BEND
POS CONVERT ERROR
1
Cause
There was the same point in three points where the calibration had been executed.
Setting error
Setting error The three points where the calibration had been executed lie in a straight line.
The three points where the calibration had been executed lie in a straight line.
Setting error
Incorrect information of standard position data for offline arm bend position data conversion
Software operation error occurred
3
4
5
6
7
8
9
Incorrect reference-point data offline arm bend position data conversion
Software operation error occurred
The position data could not be converted correctly/conversely for the standard position data at the offline arm bend position data conversion.
Setting error
Incorrect pulse incremental value for offline arm bend position data conversion
The position data could not be converted correctly for the pulse incremental value at the offline arm bend position data conversion.
Setting error
Setting error
Incorrect Cartesian incremental value for offline arm bend position data conversion
Setting error
The position data could not be converted correctly for the
Cartesian incremental value at the offline arm bend position data conversion.
Setting error
The position conversion could not be done in the conversion data for offline arm bend position data conversion.
Setting error
Remedy
(1)Check the following settings.
·Correct the calibration position so that each point is different.
(1)Check the following settings.
·Check the calibration position so that the three taught points are not aligned in a straight line.
(1)Check the following settings.
·Check the calibration position so that the three taught points are not aligned in a straight line.
(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).
(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).
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
Alarm
Number
4698
Alarm Name
SHIFT VALUE MAKING
ERROR
1
Sub
Code
10
Meaning
11
14
15
17
19
20
22
Cause
Incorrect incremental value of angle for offline arm bend position data conversion
Setting error
The position data could not be converted correctly for the incremental value of angle at the offline arm bend position data conversion.
Setting error
The reverse shift value creation at the offline position data conversion failure
Setting error
Setting error The reverse shift value adding failure at the offline position data conversion
The shift value adding failure at the offline position data conversion
Setting error
Mirror shift correctly/conversely conversion for the offline position data conversion error
Setting error
Mirror shift position conversion for the offline position data conversion error
Setting error
Coordinate specification error in the new mirror shift conversion for the offline position data conversion
Reference position and target position occupation control-group error
Setting error
Software operation error occurred
2 Reference position and target position enabling control-group error
Software operation error occurred
3 The position data type is not applicable.
Software operation error occurred
4 Coordinated control-group error Software operation error occurred
Remedy
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(1)Check the following settings.
·The variable position may be out of the robot motion range. Check if the variable position is within the robot motion range.
(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).
(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).
(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).
(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).
Alarm
Number
4715
Alarm Name
CIP MESSAGE SERVER
FUNC ERROR
1
Sub
Code
5
2
3
4
5
10
20
30
Meaning
Library initialize error.
Detect undefined error.
Cause
User coordinates number on the specified tag side error
Software operation error occurred
Failed in the generation of the CIP server task.
Software operation error occurred
Failed in the ID take of the CIP server task.
Software operation error occurred
Failed in the generation of the class entry table.
Software operation error occurred
Failed in the generation of the access process.
Software operation error occurred
Detect sever function started processing.
Software operation error occurred
Detect request error.
Software operation error occurred
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
4716 BINARY ETHERNET
SERVER FUNC ERR
1
Sub
Code
31
32
33
40
41
50
2
Meaning
Detect memory error.
Detect mail send error.
Detect CIP answer error.
Detect CIP server task mail receive error.
Detect CIP server task request data error.
Software operation error occurred
Detect CIP server task send error. Software operation error occurred
IP address duplicated.
Cause
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
IP address setting error
Detect message library initialize error.
Software operation error occurred
Failed in the generation of the RC connect management task.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(1)Reset the alarm, and then try again.
(2)The IP address is duplicated with the FS100 controller. Confirm the IP address of the communication target.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
3
4
Meaning
1042 Received data area overflow.
Software operation error occurred
1043 Failed in the request error.
1044 Failed in the request error.
Cause
Failed in the generation of the RC server task.
Software operation error occurred
Failed in the generation of the file server task.
Software operation error occurred
1040 Failed in the request take of the
RC connect management task.
Software operation error occurred
1041 Failed in the endian conversion.
Software operation error occurred
Software operation error occurred
Software operation error occurred
1059 In a RC connect management task,undefine error detected.
Software operation error occurred
1060 Failed in the ID take of the RC server task.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
1061
Meaning
1062 In a RC server task, request mail data error detected.
Software operation error occurred
1063 Answer data area overflow.
1064 In a RC server task, receive data area overflow.
Software operation error occurred
1079 In a RC server task, undefined error detected.
Software operation error occurred
1080 In a file server task, mail receive error detected.
Software operation error occurred
1081 In a file server task, request mail data error detected.
Software operation error occurred
1082 IP address duplicated.
Cause
Failed in the mail take of the RC server task.
Software operation error occurred
Software operation error occurred
IP address setting error
In a file server task, request error occurred.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(1)Reset the alarm, and then try again.
(2)The IP address is duplicated with the FS100 controller. Confirm the IP address of the communication target.
(3)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(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).
Alarm
Number
Alarm Name
Sub
Code
1083
Meaning
Failed in the endian conversion.
Cause
Software operation error occurred
1084 In a file server task, receive data area overflow.
Software operation error occurred
2045 In a RC connect management task , send error detected.
Software operation error occurred
2046 Failed in the endian conversion.
Software operation error occurred
2065 Detect RC server task send error.
Software operation error occurred
2066 Failed in the endian conversion.
Software operation error occurred
2085 Detect file server task send error.
Software operation error occurred
2086 Failed in the endian conversion.
Software operation error occurred
2087 In a file server task, answer data error detected.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
4718 BINARY ETHERNET
CLIENT FUNC ERR
1
Sub
Code
2088
Meaning
Failed in the endian conversion.
Cause
Software operation error occurred
2089 In a file server task, answer data area overflow.
Software operation error occurred
2098 Failed in the status error occurred. Software operation error occurred
2099 In a file server task, undefined error detected.
Software operation error occurred
3090 In a file sever task, file close error. Software operation error occurred
2
3
4
Detect message library initialize error.
Software operation error occurred
Failed in the generation of the file function task.
Software operation error occurred
Failed in the generation of the RC function task.
Software operation error occurred
Detect I/F data error.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
10
Meaning
Detect undefined error.
Cause
Software operation error occurred
110 In a file task, undefined error detected.
Software operation error occurred
510 In a RC task, undefined error detected.
Software operation error occurred
511 In a RC task, request command error detected.
Software operation error occurred
512 In RC task, there is not the class entry of the request command.
Software operation error occurred
513 In RC task, there is not the service entry of the request command.
Software operation error occurred
1130 In a high speed Ethernet task, request mail error detected.
Software operation error occurred
1131 In a high speed Ethernet task, request command error detected.
Software operation error occurred
1132 In a file task, mail receive error occurred.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
2140
Meaning
In a file task, file reading error occurred.
Cause
Software operation error occurred
2141 In a file task, file writing error occurred.
Software operation error occurred
3150 In a file task, request send error occurred.
Software operation error occurred
3151 Failed in the endian conversion.
Software operation error occurred
3160 In a file task, reply packet clear error occurred.
Software operation error occurred
3161 Failed in the take of the reply packet data error.
Software operation error occurred
3162 Failed in the endian conversion.
Software operation error occurred
3163 In a file task, time out occurred.
Software operation error occurred
3164 In a file task, receive data area overflow occurred.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
3165
Meaning
In a file task, received data unmatched.
5533 In a RC task, interface data writing error occurred.
Cause
Software operation error occurred
3166 In a file task, receive data size overflow occurred.
Software operation error occurred
3167 In a file task, received data size set to zero occurred.
Software operation error occurred
3168 In a file task, reply head error occurred.
Software operation error occurred
3169 In a file task, reply status error occurred.
Software operation error occurred
5530 In a RC task, interface request error occurred.
Software operation error occurred
5531 In a RC task, interface answer error occurred.
Software operation error occurred
5532 In a RC task, interface data area overflow occurred.
Software operation error occurred
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
6540
Meaning
In a RC task, time out occurred.
Cause
Software operation error occurred
6541 Detect data error.
6542 Detect exclusive process error.
Software operation error occurred
6543 Detect time out.
6544 Setting error
Detect data error.
Software operation error occurred
Software operation error occurred
Setting error
Software operation error occurred
6545 Detect exclusive process error.
Software operation error occurred
7550 In a RC task, request send error occurred.
Software operation error occurred
7551 Failed in the endian conversion.
Software operation error 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).
(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).
(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).
(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).
(1)Reset the alarm, and confirm whether the following parameter is set to zero.
・ S2C541
・ S2C542
(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).
(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).
(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).
(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).
Alarm
Number
Alarm Name
Sub
Code
7560
Meaning
7561 In a RC task, reply take error detected.
Software operation error occurred
7563 Detect time out.
7565 In a RC task, received data unmatched.
Cause
In a RC task, reply packet error detected.
Software operation error occurred
7562 Failed in the endian conversion.
Software operation error occurred
Software operation error occurred
7564 In a RC task, receive data area overflow detected.
Software operation error occurred
Software operation error occurred
7566 In a RC task, received data size over.
Software operation error occurred
7567 In a RC task, receive data size zero detected.
Software operation error occurred
7568 In a RC task, reply head error detected.
Software operation error 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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
(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).
Alarm
Number
4730
4731
4822
4823
4825
Alarm Name
MOTION RANGE LIMIT
OVER
DEST MOTION RANGE
LIMIT OVER
HARD WIRE BASE
BLOCK ERROR
HARD WIRE BASE
ENABLE ERROR
BASE ENABLE ERROR
Sub
Code
7569
Meaning
In a RC task, reply status error detected.
Sub Code: Control group
Sub Code: Control group
Cause
Software operation error occurred
Setting error
Setting error
Connection failure
Servo control board failure
Software operation error occurred
Connection failure
Servo control board failure
Software operation error occurred
Connection failure
Servo control board failure
Software operation error 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).
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is within the motion range.
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4826
Alarm Name
POWER RELAY ERROR
Sub
Code
Meaning
4830 PP E-STOP SIGNAL
ERROR
4831 PANEL E-STOP SIGNAL
ERROR
4832 EXT E-STOP SIGNAL
ERROR
Cause Remedy
Connection failure
Servo control board failure
Power relay failure
Connection failure
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
programming pendant failure (1)Reset the alarm.
(2)Still the alarm occurs again after confirming the connection or insertion status, execute the following operation.
·Replacement of the programming pendant
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Connection failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Connection failure (1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the connection cable
Hardware failure (1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the external emergency stop button or the corresponding parts.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4833
Alarm Name
ENABLE SW SIGNAL
ERROR
4834 SAFTY PLUG SIGNAL
ERROR
4836 OVERRUN SIGNAL
ERROR (OT1)
Sub
Code
Meaning
Sub Code: Control group
Cause Remedy
Enable signal unmatched error
Connection failure
(1)Reset the alarm.
(2)Check the followings.
·There are two point of contact enable switch, and only one might be turned ON by how to squeeze. Moreover, only one might be turned ON when putting it on the place where it is not a plane on the knee etc.
(1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the programming pendant programming pendant failure (1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of programming pendant
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Connection failure (1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of connection cable
Hardware failure
Hardware failure
(1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the switch used for safeguarding signal or the corresponding parts.
(1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the switch used for protection stop signal or the corresponding parts.
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Enable signal unmatched error
Connection failure
(1)Reset the alarm.
(2)If the alarm occurs again, confirm the followings.
·Select "OVERRUN & S-SENSOR"from "ROBOT" menu to display OVERRUN
& S-SENSOR window. The alarm can be released on this window.
(1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the connection cable
Alarm
Number
Alarm Name
4837 OVERRUN SIGNEAL
ERROR (OT2)
4838 OVERRUN DETECT
4839 MODE SIGNAL CUT
Sub
Code
Meaning
Sub Code: Control group
Sub Code: Control group
Cause Remedy
Hardware failure (1)Reset the alarm.
(2)If the alarm occurs after the replacement of the machine safety module, execute the following operation.
·Replacement of the limit switch or corresponding parts.
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Enable signal unmatched error
(1)Reset the alarm.
(2)If the alarm occurs again, confirm the followings.
·Select "OVERRUN & S-SENSOR"from "ROBOT" menu to display OVERRUN
& S-SENSOR window. The alarm can be released on this window.
Connection failure
Hardware failure
(1)Reset the alarm.
(2)If the alarm occurs again, confirm the following.
·Replacement of the connection cable
(1)Reset the alarm.
(2)If the alarm occurs after the replacement of the machine safety module, execute the following operation.
·Replacement of the limit switch or corresponding parts.
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Overrun limit switch released (1)Reset the alarm.
(2)If the alarm occurs again, confirm the followings.
·Select "OVERRUN & S-SENSOR"from "ROBOT" menu to display OVERRUN
& S-SENSOR window. The alarm can be released on this window.
Connection failure (1)Reset the alarm.
(2)If the alarm occurs again, confirm the following.
·Replacement of the connection cable
Hardware failure (1)Reset the alarm.
(2)If the alarm occurs after the replacement of the machine safety board, execute the following operation.
·Replacement of the limit switch or corresponding parts.
Machine safety board failure (1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Dummy connector not inserted
Insert the dummy connector.
Alarm
Number
4840
4901
4902
4903
4904
Alarm Name
INTERLOCK
CONNECTOR IS USED
CUBE/AXIS
INTERFERENCE
CUBE INTERFERENCE
(CONTROL POINT
MONITOR)
CUBE INTERFERENCE
(WHOLE MONITOR)
CUBE INTERFERENCE
AREA SETTING ERROR
0
Sub
Code
Meaning Cause Remedy
Sub Code: Servo control board from which errors are detected.
0000_0001 SV#1
0000_0010 SV#2
Connection failure (1)Reset the alarm.
(2)If the alarm occurs after above mentioned operation, execute the following operation.
·Confirm the looseness of the connectors connecting the programming pendant and the cable.
·Replace the programming pendant cable.
programming pendant failure (1)Reset the alarm.
(2)If the alarm occurs again, execute the following operation.
·Replacement of the programming pendant
Servo control board failure
Insert connector
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)Disconnect the connector for releasing the manual brake
1
Sub Code; Group, axis, and interference area number
Servo control board failure
Setting error
Sub Code: Control group & Area number
Setting error
Sub Code: Control group &
Interference axis & Area number
Setting error
Maximum number of the cube interference area exceeds the allowable range.
Setting error
The number of cube interference area whose monitoring part is
"whole" exceeds the limit.
Setting error
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is out of interference area.
·Change the settings for interference area.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is out of interference area.
·Change the settings for interference area.
(1)Check the following settings.
·Perform the teaching again to correct positions for manipulators so that the step where the alarm occurred is out of interference area.
·Change the settings for interference area.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
.
Reduce the number of cube interference area whose monitoring part is "whole"
Alarm
Number
4940
4941
4942
4943
4944
4945
Alarm Name
MOTION COMMAND
CODE ERROR (SV)
CANNOT EXECUTE
MOTION CMD (SV)
AVERAGING TIME
CHANGE ERROR (SV)
AVERAGING TIME
ERROR (SERVO)
POSITION LOOP GAIN
ERROR (SV)
MOTION COMMAND
DATA ERROR (SV)
Sub
Code
2
3
Meaning Cause
Detect the cube whose interference area are extremely big or small.
Setting error
Detect the cube interference area whose monitoring part is set to
"whole" despite the invalid status of cube arm interference check function.
Setting error
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Remedy
(1)Among the cube interference areas already values are entered, modify as follows.
1.Change the extremely big values to smaller ones.
2.Change the extremely small values to bigger ones.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs just after loading the cube interference area setting function, execute the following measures.
1.Among the cube interference areas to be loaded, change the monitoring part setting from "whole" to "control point.
2.Load the changed cube interference area again.
3.If tha alarm occurs again after loading the area, confirm its setting 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).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4946
4947
4948
4953
4955
4956
4957
4958
Alarm Name
PG POWER ON
INCOMPLETE (SV)
SERVO ON MULTIPLE
REQUEST (SV)
ENCODER ALARM
(SERVO)
ENCODER COUNTER
DIFF. ERROR(SV)
AVERAGING DATA
ERROR (SERVO)
AVERAGING SUM
ERROR (SERVO)
AVERAGING STATUS
ERROR (SERVO)
HIGH RESOLUTION
PRM UNDEFINED(SV)
Sub
Code
Meaning Cause Remedy
Sub Code: Signifies the axis in which the alarm occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
Connection failure
Servo control board failure
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm
(2)If the alarm occurs again, check the connection and inserting state of the following cables and connectors.
{Robot axis}
·Cable between encoders
{External axis}
·Cable between encoders
(1)Reset the alarm.
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Alarm
Number
4960
4961
4962
4963
4964
4965
4972
Alarm Name
BELT SNAP DETECT
PRM ERROR (SV)
SERIAL ENC OSCILL
DETECTED (SV)
BRAKE LOCK ERROR
(SERVO)
BRAKE RELEASE
ERROR (SERVO)
CONST.SPD MEASURE
MULTI REQ (SV)
DIN SIGNAL SPECIFIC.
ERROR (SV)
CONVTR REGENERATE
OVERLOAD(SV)
Sub
Code
Meaning
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Sub Code: Signifies the axis in which the alarm occurred
Cause Remedy
Setting error
Software operation error occurred
Software operation error occurred
Software operation error occurred
Software operation error occurred
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
(1)Reset the alarm.
(2)If the alarm occurs again, save the CMOS.BIN in maintenance mode, and then contact your Yaskawa representative about occurrence status (operating procedure).
Confirm the DIN signal settings.
Setting error
Primary power supply failure Correct the converter primary power supply.
Setting error
Connection failure
Module failure (Regenerative resistor)
Module failure (converter)
Check the following settings.
·The tool information
·JOB
·Work
·The speed of JOB
·The acceleration/deceleration speed of ACC and DEC
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Alarm
Number
Alarm Name
4980
4981
4982
4973
4983
4984
POSITION ERROR
(COLLISION DETECT)
DESTINATION PULSE
LIMIT
DEST PULSE
MECHANICAL LIMIT
DEST MECHANICAL
INTRF
DEST MECHANICAL
INTRF
DESTINATION SELF-
INTERFERENCE
Sub
Code
Meaning Cause Remedy
Servo control board failure
Setting error
Setting error
Setting error
Setting error
Setting error
Setting error
(1)Reset the alarm
(2)If the alarm occurs again, replace controller. Save the CMOS.BIN before replace controller to be safe.
Confirm the settings of the followings.
·The tool information
·Work
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
(1)Check the following settings.
·Check the position setting for the step (move instruction) where the alarm occurred.
FS100
10 Error
10 Error
10.1 Error Message
10.1
Error Message
Error warns the operator not to advance to the next operation caused by a wrong operation or the access method when using the programming pendant or an external equipment (computer, PLC, etc.).
When an error occurs, confirm the content of the error then release the error.
To release the error, perform either of the following operations:
• Press [CANCEL] on programming pendant.
• Input alarm/error reset signal (system input).
NOTE
An error is different from an alarm because it does not stop the robot even if it occurred while the robot was operated
(during playback).
When two or more errors occur, appears in the message display area.
Activate the message display area and press [SELECT] to view the list of current errors.
10-1
280
290
300
310
230
240
250
260
320
330
340
200
210
211
212
220
160
170
180
190
120
130
140
150
80
90
100
110
32
40
50
60
70
20
30
31
FS100
10 Error
10.1 Error Message
10.1.1
System and General Operation
Error No.
10
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Data Error Message
Turn OFF servo power and perform corrective action
Contents
It cannot be operated while servo power supply is ON.
Depress TEACH Out of specified operation mode
Illegal setting for number of variables Parameter setting error
Illegal setting for number of variablenames
Illegal setting for number of SUB task.
Undefined robot position variables Position variable cannot be used.
Depress MODIFY
Undefined points (ORG, XX, XY)
Program and current tool different
Not registered user coordinates basic 3 points
(ORG, XX, XY)
The tool number registered with teaching position data does not match the tool number selected at the programing pendant.
Same position in the 3 points
Set robot exactly to taught position
On overrun recovery status
Turn ON servo power
Set to PLAY mode
No start using external signal
No start using P.P.
TEACH-LOCK mode ON
ENABLE LED ON
Servo OFF signal ON
TEACH mode select signal ON
Set variable number
Defined group axis
Undefined coordinated robots
Cannot register between stations
Cannot register at this combination
Taught by other robot
While releasing soft limit
Undefined robot
Defined condition No.
Undefined file
Lack of number of I/O points
Cannot set same No.
Undefined user frame
Cannot register Master JOB
Cannot operate CHECK-RUN
Cannot operate MACHINE LOCK
Cannot operate Master JOB
10-2
FS100
690
700
710
720
560
590
640
650
660
670
680
600
610
620
630
390
400
410
420
430
440
450
460
470
480
490
500
510
520
530
540
550
Error No.
350
360
370
380
383
10 Error
10.1 Error Message
Data Error Message Contents
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
XXX
-
-
-
-
-
-
-
-
Cannot initialize
Teach point not specified
No SYNCRO operation
Position not checked
Select joint coordinate system and perform forward operation
Second home position was not checked.
Can specify servo OFF by safety relay
Wrong specification of measure interval
Time could not be measured
Incorrect number of taught points
Time could not be measured for TRT function.
The number of the taught points for tool calibration is incorrect.
Register start reserved JOB
Clear data to teach at the tool because other tool is set
Wrong JOB for measuring
Excess time for measuring
Calibrated at another file
Calibrated at another robot combination
Cannot calibrate at this combination
Undefined robot calibration data
Undefined axis
Cannot select two coordinated combination
Start reservation mode
Not start reservation mode
Start reserved JOB change prohibit is set
Cannot teach position while soft limit released
Register group axis combination [SYNCHRO] was pressed for coordinated job which was not registered as group.
Out of setting data range
Cannot use the user coordinate
Select JOB (robot)
Not completed to load original tool file
Not specified Tool File
Incorrect measured data
Wrong data type of position variable
Enter path number
Defined data
File no.
Illegal path number
Wrong CMOS memory board type
Canceled pelletizing shift value
Defined name
10-3
FS100
723
724
810
820
830
840
850
860
870
880
890
730
750
760
770
790
900
910
920
930
960
971
Error No.
721
722
10 Error
10.1 Error Message
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Data Error Message
It is already registered for IN/OUT signal name.
It is already registered for Variable name.
It is already registered for Local variable name.
The existing names cannot be overwritten
Undefined Name Position file
This name cannot be defined
Error in start condition set
During robot or station operation
FWD/BWD don't work in the handle operation
Servo power supply is limited
Modification range over
Cannot move while modifying speed
Unregistered key
Cannot register instruction
Please release key registration mode
This key cannot be allocated
Same relay cannot be set
This key has already been registered.
Cannot register them once
Relay No. not set
Cannot be registered because job control group not same
Cannot modify this setting
Undefined conveyor calibration data
I/O axis mode requesting
ERRCPU signal error
Contents
10-4
FS100
10.1.2
Editing
Error No.
1010
1020
1030
1050
1060
1070
1080
1090 -
-
-
-
-
-
-
-
Data
10 Error
10.1 Error Message
Error Message
EDIT LOCK mode
Enter correct value
Unauthorized ID No.
Enter correct date
Enter correct clock
Enter an ID number in 4-8 figures
Negative value can’t be set
Enter correct value(START-END signal no)
Contents
10-5
Error No.
2010
2020
2030
2040
2050
2060
2070
2080
2090
2100
2110
2111
2111
2130
2140
2150
2160
2170
2180
2190
2200
2210
2220
2230
2240
2250
2260
2270
2280
FS100
10.1.3
Job Defined Data
10 Error
10.1 Error Message
2290
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
4
5
2
3
*
1
-
-
Data Error Message Contents
Incorrect character
Name not entered
Undefined JOB name
Defined JOB name
Address not found
Select master
Set robot exactly to taught position
Press INSERT or MODIFY
Only modifying move instruction possible
JOB cannot be edited.
Over soft limit
Over soft limit. Adjust center position or pulse width.
Cannot insert/alter/delete with servo
OFF
Only modifying move instruction possible
Must press ENABLE to modify
Inserting is not possible from this point
Cannot modify or delete this position
Press INSERT to record same step as previous step
Cannot insert data
Cannot delete data
Cannot modify data
Illegal data setting
Display edit instruction
Illegal instruction equation
Excessive instruction equation
Unmatched number of parentheses in equation
Wrong group axis selection
Cannot insert any more instruction in
JOB
JOB memory is full
Lack of position file memories
Lack of JOB registering memories
Lack of instruction file memories
Lack of memory pool
Lack of pass condition file for multi layer
Undefined master JOB
10-6
2300
2310
2430
2450
2460
2470
2480
2490
2500
2501
2510
2520
2530
2540
2550
2380
2390
2400
2410
2420
2320
2330
2350
2340
2360
2370
FS100
Error No.
2291
2292
2293
10 Error
10.1 Error Message
Data Error Message
* Undefined SUB Master JOB
Contents
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
3
4
1
2
-
5
-
*
4
5
1
2
3
-
-
-
-
-
-
*
XXX
Undefined MASTER START JOB
Undefined SUB START JOB
Cannot teach JOB without group-axis specification
Same label exists
Cannot create coordinated JOB
Cannot edit coordinated instruction
Pasted data not found
Editing data not found
Cannot create editing area
Cannot cut/copy NOP and END instructions
Wrong JOB selection
Wrong group axis selection
Cannot move in cut & paste editing
When variable is used for speed setting, perform a line-edit
When variable is used for teach setting, perform a line-edit
Reverse data not found
Relative JOB not permitted
Specified JOB is already converted
Wrong JOB type
Wrong JOB coordinates setting
Execute FWD/BWD operation once
Cannot convert the JOB
Cannot convert positions as macro arguments
Cannot correct position in the JOB
Enter JOB name
Illegal step number
Enter step number
Duplicated step number
Sub-master 1
Sub-master 2
Sub-master 3
Sub-master 4
Sub-master 5
Sub-master 1
Sub-master 2
Sub-master 3
Sub-master 4
Sub-master 5
Line no.
10-7
FS100
Error No.
2551
2560
2570
2580
2590
2600
2610
2620
2630
2640
2650
2660
2670
2690
2710
2720
2730
2740
2750
2760
2761
2780
2790
10 Error
10.1 Error Message
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Data Error Message
Duplicated line number
Cannot correct steps of position variables and REFP
The step does not contain speed
The step dose not contain PL/CONT
Soft limit range over
Cannot teach position in concurrent
JOB
Wrong JOB kind
Cannot correct play speed in the JOB
Conveyor position not reset
Incorrect JOB name
Defined JOB name
Register MOVL after circular block
Undefined target JOB
Defined same kind JOB
Relative job can’t be shifted with pulse type
Cannot correct position variables
Cannot use robot macro JOB
Cannot use concurrent macro JOB
Cannot use JOB with group-axis specification
Cannot insert/modify/delete for group axis detachment
Cannot insert/modify/delete for axis detachment
Arithmetic error
Step exceeding operation range.
Contents
10-8
FS100
10 Error
10.1 Error Message
10.1.4
External Memory Equipment
Error No.
3021
3022
3040
3050
3060
3070
3080
3090
3100
3110
3120
3130
3140
3150
3150
3160
3170
3180
-
3
4
1
2
-
*
-
4
2
3
*
1
-
-
8
9
2
3
*
1
-
4
-
7
5
6
6
7
4
5
1
2
3
-
-*
-
-
-
-
-
Data Error Message
CompactFlash not inserted into
CompactFlash slot(PP)
USB media not inserted
File not saved on the media
File saved on the media
Out of memory on the media
Number of files on the media
I/O error on the media
Transmission error with the media
Total checksum error
Syntax error
HEX code error
Verify error
Wrong pseudo instruction
Concurrent I/O record error
Cannot load illegal system data
Condition file data error
Concurrent I/O data transmission error
Contents
Framing error
Overrun error
Parity error
Data code error
Data read error
Data write error
Data time out
Serial I/O error
Error other than described above
Specification error of data decode
Specification error of EOF record
Record type error
Total check error of record
Format error
Ladder program is too long
Exceed the range of the data
Specification error of channel No.
Specification error of relay No.
Timer value error
Specification error of timer No
Format error
Specified file No. is omitted
Specified tool No. is omitted
User file is not registered.
10-9
FS100
Error No.
3190
3200
3210
3220
10 Error
10.1 Error Message
4
5
6
7
2
3
10
11
8
9
*
1
Data Error Message
Error in JOB data record
Contents
12
13
5
6
3
4
*
2
-
NOP or END instruction not found
Position No. storage area not found
Syntax error in instruction data
Record on the number of position data (NPOS) is wrong for the format.
Record on the user coordinate No. (USER) is wrong for the format.
Record on the tool No. (TOOL) is wrong for the format.
Record on the position data section is wrong for the format.
Record on the robot type of XYZ data (RCONF) is wrong for the format.
Date (DATE) record is wrong for the format.
Comment (COMM) record is wrong for the format.
Record on the JOB attribute data (ATTR) is wrong for the format.
Control group (GROUP) record is wrong for the format.
Local variable (LVARS) record is wrong for the format.
JOB argument (JARGS) record is wrong for the format.
Record on the teaching coordinates for relative job (FRAME) is wrong for the format.
Position data coordinates do not match relative job coordinates.
Interior control error
Undefined instruction/tag
Instruction/tag shortage
Disuse instruction/tag
Sub instruction
10-10
FS100
Error No.
3220
3230
10 Error
10.1 Error Message
Data Error Message
19
20
21
22
15
16
17
18
11
12
13
14
7
8
9
10
28
29
30
35
23
24
25
26
27
36
37
40
41
38
39
46
47
48
49
42
43
44
45
-
58
Syntax not matched
10-11
Contents
No instruction
Invalid instruction
Invalid tag
Invalid character
Undefined intermediate code
Intermediate code shortage
Syntax stack overflow
Syntax stack underflow
Array type tag uncompleted Tag [ARRAY]
Element type tag uncompleted Tag [ELEMENT]
Macro JOB unregistered
Input format error
Data size over
MIN value over
MAX value over
Operation expression error
Job call argument setting error
Macro job call argument setting error
Position vector setting error
System error
Soft key designate error
Numerical input buffer overflow
Real type data precision error
Element format error
BOOL TYPE data error
CHAR data error
BYTETYPE, BINARY / HEXADECIMAL BYTE
TYPE data error
INTEGER TYPE, DECIMAL WORD TYPE data error
BINARY/HEXADECIMAL WORD TYPE data error
DOUBLE PRECISION INTEGER TYPE,
DECIMAL DWORD TYPE data error
BINARY/HEXADECIMAL WORD TYPE data error
REAL TYPE data error
LADDER SPECIAL TYPE data error
JCL text
Invalid text
LABEL NAME data error
JOB NAME data error
STRING data error
COMMENT data error
Invalid instruction/tag detection
3470
3480
3490
3500
3501
3510
3520
3530
3540
3550
3551
3560
3570
3580
3581
FS100
Error No.
3360
3370
3380
3390
3400
3410
3420
3430
3440
3450
3240
3250
3260
3270
3290
3300
3310
3350
3460
10 Error
10.1 Error Message
-
-
-
-
-
-
2
*
1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Data Error Message Contents
Undefined application
Cannot load this file
Excess input data
Cannot verify this file
Serial port not defined
Serial port being used
Protocol being used
Not enough memory
Invalid folder
Incorrect folder name
Drive not ready
File not found
File already exists on the media
Out of memory on the media
Max number of files has been reached
I/O error on the drive
Wrong media type
Cannot load macro JOB at current security mode
Load in management mode.
Cannot backup the media
Insufficient Compact Flash memory.
Not accessible to Compact Flash.
Database not found
Database access error
Same database exists
Check the media insertion
Check the media insertion
Cannot delete folder. Check attribute and inside file
Same folder exists
Cannot load at current security mode
CMOS not compatible
Under automatic backup operation.
Operate after the backup is completed.
Under automatic backup operation.
Operate "SORT FILE" after the backup is completed.
Failed in sorting backup file
Actuator data transmission error
Under backup file access. Operate after the access is completed.
Under backup file access. Operate
"SORT FILE" after the access is completed.
10-12
FS100
Error No.
3600
3610
3620
10 Error
10.1 Error Message
-
-
-
Data Error Message system configuration data not matched
Excessive path
Excess folders
Contents
10-13
4050
4060
4070
4080
4090
4100
4110
4120
4130
4140
4150
FS100
10.1.5
Concurrent I/O
10 Error
10.1 Error Message
4160
4170
4180
4190
4200
4210
4220
4230
Error No.
4010
4020
4030
4040
Data Error Message Contents
-
-
-
-
-
-
*
*
XXX
XXX
*
-
-
-
-
XXX
*
-
XXX
XXX
*
XXX
*
XXX
*
XXX
*
*
Illegal relay No.
Line no.
Illegal block No.
Illegal instruction
Relay/register No. duplicated in OUT/
GOUT or arithmetic instruction
Line no.
Multiple outputs are instructed to the relay or register.
Line no.
The relay is not used
Line no.
Excess STR-[-NOT] instructions
Line no.
Excess AND [OR] STR instructions
Line no.
Syntax error in CRT instructions
Enter STR [-NOT] at head of block
Line no.
Need STR [-NOT]
Line no.
Relay No. duplicated in TMR and CNT
Excessive ladder scan-time
Concurrent I/O memory is full
END instruction not found
Wrong ladder program
Wrong use of GSTR, GOUT commands
Exceeds memory capacity (10000 steps)
END instruction not found
Position and number of PART instruction are wrong.
GSTR and GOUT is not used together.
Line no.
-
-
-
XXX
Cannot edit system section
Cannot modify/delete
Depress INSERT/MODIFY/DELETE keys
Ladder program not found
Cannot specify system variables($)
Cannot edit line
Excess TMR/CNT or arithmetic instructions
Syntax error in TMR/CNT instructions
More than 100 TMR, CNT or arithmetic instruction used
10-14
FS100
10.1.6
Maintenance Mode
10 Error
10.1 Error Message
8070
8071
8072
8073
8074
8075
8076
8080
8205
8206
8210
Error No.
8010
8011
8020
8030
8033
8034
8035
8040
8041
8042
8050
8051
8060
8211
8212
8213
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Data Error Message
Too many axes
Choose the input of overrun
Too many I/O points
Too many boards (DEVICENET)
Too many boards
Too many channels
Invalid configuration
Memory error (ControlNet output condition)
Memory error (UNIWIRE
CONNECT DAT
Memory error(IP Network
Configuration data)
Robot model is not registered
Select model
Cannot get UNIWIRE connection data
DHCP is already set to use for another item
DNS is already set to use for another item
DHCP is not set to use
DNS is not set to use
Device Information not found
Unable to accept same type of boards simultaneously
Ethernet is being used by other function.
Non support function
ENABLE Unit over
FLASH access error
IO module configuration is not modified
OPTION, BOARD or MODULE
SETUP is not completed.
Cannot change setting (Function conflict
Check EXTERNAL IO setup
Contents
10-15
FS100
10.2.1
Message
10.2.1.1
Fatal Error
10 Error
10.2 Particular Error Message
10.2
Particular Error Message
Apart from ordinary alarms or errors, some may display an error box message on the programming pendant. This message is displayed, when the system of the programming pendant becomes unauthorized.
This message is displayed when the fatal error occurs.
The message is “Fatal application Error” although the content of the message box varies depending on the occurence status.
The programming pendant becomes either of following states
1. The window becomes inoperable.
2. The window disappears and blue background appears.
10-16
FS100
10 Error
10.2 Particular Error Message
10.2.1.2
Application Transaction Error
This message is displayed when the system or the software of the programming pendant becomes unauthorized due to unexpected transaction or failure in softaware transaction, etc.
The message in the message box varies depending on the occurence status.
10.2.1.3
Other Errors
Followings are the messages possible to occure.
Message syntax error
Meaning
There is an unauthorized part in internal processing discription.
expression too complex(stack overflow) Internal stack has overflowed.
function nesting depth exceeded Nesting of internal processing is unauthorized.
bad radix divide by 0
The cardinal number used is unauthorized.
Memory is running out.
out of memory register is not available
Memoriy is insufficient.
argument list does not match a function The internal processing of the pendant program is unauthorized.
Specified an unavailable system data.
The programming pendant becomes either of following states
1. The window becomes inoperable.
2. Press {OK} button to disappear the message box and it becomes operable.
Other errors than mentioned above, some can trigger the message box.
10-17
FS100
10 Error
10.2 Particular Error Message
10.2.2
When the Error is Indicated
10.2.2.1
Fatal Error
Prgramming pendant becomes inoperable when this message appears.
Please restart the system.
10.2.2.2
Application Transaction Error
It is possible to keep the operation after pressing {OK} button to disappear the message box. However, in this case, the system might be instable.
Please restart the system if the window becomes inoperable.
10.2.2.3
Other Errors
Most of the cases when an error occurs, it is possible to keep the operation after pressing {OK} button to disappear the message box.
Please restart the system if the window becomes inoperable.
Sometimes the message appears due to a specific operation although unstable state of the programming pendant is the main cause of the error in most cases.
If the pendant becomes inoperable after the message due to a specific operation invariably, please report the displayed message to your
Yaskaswa representative.
10-18
11 LED Indicator on Each Circuit Board
FS100
11 LED Indicator on Each Circuit Board
Before the check of LED indicator
In principle, the door must not be opened to prevent electric shock while power is ON. However, open the door with extreme care only if it is required to check the LED display on each circuit board for maintenance.
WARNING
• To perform this operation, it is required to open the door of the control box while power is ON.
• A heavy current (AC200V) flows inside the control box. Do not touch the internal unit.
Failure to observe this warning may result in electric shock.
• Close the door as soon as the maintenance work such as LED check is completed.
Failure to observe this warning may result in electric shock.
WARNING
• Close the door as soon as the maintenance work is completed.
Failure to observe this warning may result in electric shock.
11-1
FS100
11 LED Indicator on Each Circuit Board
11.1 6 LED-Spot Indicator on the Main CPU Circuit Board (CPU201R)
11.1
6 LED-Spot Indicator on the Main CPU Circuit Board
(CPU201R)
CPU201R board shows its operation status with 6 LED-spot indicator.
Indication
SV-ON
RUN
ALM-1
ALM-2
BAT
ERR
LED Color
Green
Green
Red
Red
Red
Red
Board Status when LED is lit
While the SERVO power is turned ON.
While in operation
Occurrence of a major error
Occurrence of a minor error
Battery alarm
Error
6 LED-Spot Indicator
11-2
FS100
11 LED Indicator on Each Circuit Board
11.2 7-Segment LED Indicator on the Main CPU Circuit Board
(CPU201R)
11.2
7-Segment LED Indicator on the Main CPU Circuit Board
(CPU201R)
CPU201R board indicates its start-up status and error causes with 7segment LED indicator.
Status
Immediately after the power is turned ON
7-Segment LED Indicator
All 7-SEG indicators light up.
(‘8’ + ‘.’ light up.)
During the start-up process Count up from ‘0’ toward ‘d’ or ‘P’
Online normal start-up ‘d’ + ‘.’ blink every one second
Maintenance mode start-up ‘F’ + ‘.’ blink every one second
PP/SWP unconnected ‘P’ + ‘.’ blink every one second
ERR The error cause and the address where the error has occurred are indicated.
7-Seg LED indicator
Error indication spec.:
Repeat of [-]
→
[F]
→
[0]
→
[2]
→
[0]
→
[0]
→
(Error Cause)
Error indicati [,]
→
[-]
→
[0]
→
[0]
→
[0]
→
[0]
→
[F]
→
[F]
→
[0]
→
[4]
(Address of occurrence)
11-3
FS100
11 LED Indicator on Each Circuit Board
11.2 7-Segment LED Indicator on the Main CPU Circuit Board
(CPU201R)
11.2.1
Status of 7-Segment LED Indicator at Error Occurrence
Error cause indication
F0a00
F0c00
F0d00
F0e00
F0f00
F1000
F1100
F1200
F1300
F1400
F0200
F0300
F0400
F0600
F0700
F0800
F0900
F0930
Meaning
Machine Check
Data Storage
Instruction Storage
Alignment
Program
Floating Point Unavailable
Watchdog Timer Error (no address indication)
CPU Hung Up Error (no address indication)
Auxiliary Processor Unavailable
Fixed Interval Timer
Watchdog Timer
Data TLB Error
Instruction TLB Error
Debug Exception
CPU Signal Process Engine
Floating Point Data
Floating Point Data Round
Performance Monitor
11-4
FS100
11 LED Indicator on Each Circuit Board
11.2 7-Segment LED Indicator on the Main CPU Circuit Board
(CPU201R)
11.2.2
Status of 7-Segment LED Indicator at Control Power Start-up (one digit) d
E b
C
F
P
9
A
7
8
3
4
5
Error Status
1 The system program has started.
2 Starts verifying the existence of other circuit boards.
(Verifies the start-up of the booting program.)
6
Starts the system program transmission.
Sends the request of the system program start-up.
Starts verifying the existence of other circuit boards.
(Verifies the start-up of the system program.)
Acquires hardware information, etc. of other circuit boards.
(Verifies the IO board status, SERVO IF, and so on.)
Starts the CMOS data transmission.
Sends the pre-online request.
Waits for MIII communication synchronization.
Sends the start-up request of on-line system.
The on-line system has started. (Starts up the initialization task.)
Processes of the system setup completion. (Servo ON enabled)
Alarm occurs at the system setup.
The maintenance mode is starting up.
The system setup PP/SWP unconnected.
11.2.3
Status of 7-Segment LED Indicator at Hardware Error Occurrence
When the hardware error is detected during the operation, the error is indicated with 4-digit numbers with the letter [H] at its head.
Indication spec.:
Repeat of [ H ]
→
[0]
→
[0]
→
[0]
→
[1]
→
[.]
Alarm No.
H0001
H0002
H0003
H0004
H0005
MAC address eorror
Power lost error when start-up
Watchdog error when start-up
Interrupt clear impossible
Initialization of SERVO communication error
Turn the power supply OFF and ON again when the above mentiond numbered error is indicated by the 7-Segment.
Replacement of the controller is requied if the the error occurs again.
11-5
FS100
11 LED Indicator on Each Circuit Board
11.2 7-Segment LED Indicator on the Main CPU Circuit Board
(CPU201R)
11.2.4
Status of 7-Segment LED Indicator at Alarm Occurrence
Only when the PP is not connected the FS100, the alarm number is indicated with 4-digit numbers with the letter [A] at its head.
If more than one alarm occurred, the first alarm numbers indicated.
Note that the number of the major alarm is indicated if major and minor alarms occurred at a time.
Indication spec.: when Alarm 1200 is occurred
Repeat of [ - ]
→
[A]
→
[1]
→
[2]
→
[0]
→
[0]
11-6
FS100
11 LED Indicator on Each Circuit Board
11.3 7 SEG-LED Indicator on Machine Safety Board (SF2300)
11.3
7 SEG-LED Indicator on Machine Safety Board (SF2300)
SF2300 board indicates its operation status with LED indicator.
Indication
PWR
ALM
HWBB1
HWBB2
LED Color
Green
Red
Green
Green
Board Status when LED is lit
When the control power is turned ON.
Error is being detected
CH1 side HWBB is in operation
CH2 side HWBB is in operation
PWR
HWBB1
ALM
HWBB2
CN4
CN5
CN6
CN1
CN2
CN3
PBESP
PPESP
DSW
SAFF
ONEN
EXESP
ESPOUT
DSWOUT
HWBB1
EDM1
HWBB2
EDM2
OT1
OT2
+24V
11-7
FS100
11 LED Indicator on Each Circuit Board
11.4 7 SEG-LED Indicator on SERVO Control Board (IFM)
11.4
7 SEG-LED Indicator on SERVO Control Board (IFM)
IFM board indicates its start-up status and error causes with 6 LED-spot indicator.
Status
Immediately after the power is turned ON
6 LED-spot Indicator
“ERR” is lit
During the start-up process Green LED are lit in sequentially.
Online normal start-up
Alarm occurrence in the main CPU and SERVO control board communication system
Normal alarms other than alarms described above
Fatal alarm occurrence
“LNK2” blinks every one second
The error cause is indicated.
“ERR” is lit.
The error cause and the address where the error has occurred are indicated.
11.4.1
LED Indicator at Alarm Occurrence in the Main CPU and SERVO Control Board Communication
System
Small-sized RC
SERVO CPU Board
LED Status
Blink RDY
CN
LNK1
Blink
Blink
Blink
Blink
RDY
CN
LNK1
RDY
CN
LNK1
RDY
Blink
Blink
CN
LNK1
Status
ERR
CMERR
LNK2
ON
MIII send incompletion
Receive WDG inconsistency
ERR
CMERR
LNK2
ON
MIII status error
ERR
CMERR
LNK2
ON
Power lost detected by way of JL077
ERR
CMERR
LNK2
ON
“Blink”: light up for 3 second then light OFF for 1 second.
11-8
FS100
11 LED Indicator on Each Circuit Board
11.4 7 SEG-LED Indicator on SERVO Control Board (IFM)
11.4.2
LED Indicator During the Start-up Process
LED Status
OFF RDY
OFF
OFF
CN
LNK1
OFF
OFF
OFF
RDY
CN
LNK1
ON
OFF
OFF
RDY
CN
LNK1
ON
ON
OFF
RDY
CN
LNK1
ON
ON
ON
RDY
CN
LNK1
ON
ON
ON
RDY
CN
LNK1
RDY
CN
LNK1
RDY
CN
LNK1
ERR
CMERR
LNK2
ON
OFF
OFF
Meaning
Power supply is turned ON
Starts up boot program
ERR
CMERR
LNK2
OFF
OFF
OFF
ERR
CMERR
LNK2
OFF
OFF
OFF
Starts up boot system
(Completes initialization)
ERR
CMERR
LNK2
OFF
OFF
OFF
Completes the preparation for receiving the system program
ERR
CMERR
LNK2
OFF
OFF
OFF
Starts up the system program has
(Starts up each hardware initialization)
ERR
CMERR
LNK2
OFF
OFF
ON
Starts up the SERVO system
(Starts up each SERVO part initialization)
ERR
CMERR
LNK2
OFF
OFF
ON
Starts up pre-online processes
(LNK2 blinks at 0.3 sec intervals)
ERR
CMERR
LNK2
OFF
OFF
ON
FS100 setup competed
(SERVO ON enabled)
(LNK2 blinks at 1 sec intervals)
11-9
FS100 Index
A absolute data allowable range error alarm
.............................................. 7-16
ALARM HISTORY ..................................................................................
Alarm History Window
.......................................................................... 8-19
alarm level ............................................................................................
AlarmHistory
........................................................................................ 8-19
ANALOG MONITOR
ARM CONTROL
..............................................................................
....................................................................................
axis data ...............................................................................................
B
Battery inspections .................................................................................
binary data ............................................................................................
C
Changing the Absolute Data ...................................................................
changing the monitor items
Clearing Absolute Data
................................................................... 8-26
...........................................................................
clearing the alarm history
...................................................................... 8-20
clearing the I/O message history
........................................................... 8-22
Clearing the System Monitoring Time Display
......................................... 8-18
COMMAND POSITION ..........................................................................
control group data cooling fan
..................................................................................
............................................................................................
CREATE NEW JOB ...............................................................................
Creating a Check Program ......................................................................
CURRENT POSITION ............................................................................
Current Position
................................................................................... 8-24
Current Position Window
...................................................................... 8-24
D
DATE/TIME decimal data
...........................................................................................
..........................................................................................
DELETE ................................................................................................
DEVICE ................................................................................................
displaying and releasing alarm
DROP AMOUNT
................................................................
....................................................................................
E editing mode ..........................................................................................
emergency stop button inspections
Enable switch inspections
..........................................................
.......................................................................
ENCODER ROTATE SUM
.................................................................... 8-25
Error message list
................................................................................ 10-1
ERROR PULSE
................................................................................... 8-25
Index-1
FS100 Index
F
FD/CF
FEEDBACK PULSE .............................................................................
FEEDBACK SPEED ............................................................................
FS100 controller
.................................................................................... 3-2
G
GRP COMBINATION
............................................................................. 2-4
H
HOME POSITION
.................................................................................. 2-3
home position
........................................................................................ 7-3
home position calibration
........................................................................ 7-2
I
I/O message history .............................................................................
I/O message history window .................................................................
I/O MSG HISTORY
................................................................................ 2-3
IN 1 TURN POSITION .........................................................................
IN/OUT
Independent control function (optional)
.................................................... 9-4
Individual Window of the System Monitoring Time Display .......................
Input/Output Status
................................................................................ 8-2
INTERFERENCE
................................................................................... 2-3
J
JOB
JOB CAPACITY
.................................................................................... 2-2
K
KEY ALLOCATION
................................................................................ 2-4
L
LIMIT RELEASE
.................................................................................... 2-3
LOAD
Index-2
FS100 Index
M major alarm ...........................................................................................
managememt mode ...............................................................................
manipulator home position
.................................................................... 7-10
manipulator model .................................................................................
MANIPULATOR TYPE ...........................................................................
MASTER JOB
MAX. TORQUE
.......................................................................................
................................................................................... 8-25
minor alarm mode key
...........................................................................................
..............................................................................................
Modification of the Signal Name modifying the output status
............................................................ 8-14
.....................................................................
MONITORING TIME
MOTOR ABSOLUTE
..............................................................................
............................................................................ 8-25
Multiple SERVOPACK system ................................................................
O
OPERATE COND ..................................................................................
operation mode ......................................................................................
outline of alarm ......................................................................................
OVERRUN&S-SENSOR .........................................................................
P
PARAMETER ........................................................................................
position data when power is turned ON/OFF
.......................................... 8-23
position deviation check using the check program
................................... 7-11
power flow .............................................................................................
POWER ON/OFF POS ...........................................................................
power ON/OFF position window
............................................................ 8-23
R regular inspections replacing parts
.................................................................................
.......................................................................................
RES. START (CNCT) .............................................................................
RESERVE JOB NAME ...........................................................................
RIN input ...............................................................................................
RIN input window ...................................................................................
ROBOT .................................................................................................
S
SAVE ....................................................................................................
SECOND HOME POS ............................................................................
security mode ........................................................................................
security system ......................................................................................
SELECT JOB ........................................................................................
SERVO MONITOR ................................................................................
servo monitor window
........................................................................... 8-25
Index-3
FS100 Index servo monitoring ..................................................................................
SERVO ON
........................................................................................... 3-4
SERVO ON READY
............................................................................... 3-4
SET SPEED
.......................................................................................... 2-4
SETUP
signal flow
............................................................................................. 1-3
Specific Input Simple Window
Specific Input Window
................................................................. 8-5
............................................................................ 8-5
Specific Output
...................................................................................... 8-6
Specific Output Simple Window
.............................................................. 8-6
Specific Output Window
SPEED DEVIATION
......................................................................... 8-6
............................................................................
SPEED INST .......................................................................................
system diagnosis
................................................................................... 8-1
SYSTEM INFO
...................................................................................... 2-3
System Input
......................................................................................... 8-5
System Monitoring Time Display ...........................................................
System Monitoring Time Display Window ...............................................
system version
...................................................................................... 8-1
T
TEACHING COND
................................................................................. 2-4
TOOL
TORQUE SPEC ..................................................................................
U
Universal Input
...................................................................................... 8-2
Universal Input Simple Window
............................................................... 8-2
Universal Input Window
.......................................................................... 8-2
Universal Output Simple Window
............................................................ 8-3
Universal Output Window
USER COORDINATE
....................................................................... 8-3
............................................................................ 2-3
user ID ..........................................................................................
V
VARIABLE
VERIFY
............................................................................................ 2-2
................................................................................................ 2-3
VERSION
............................................................................................. 2-3
W
WORK HOME POS
............................................................................... 2-3
X
XYZ coordinate data
.............................................................................. 9-3
Index-4
FS100
MAINTENANCE MANUAL
HEAD OFFICE
2-1 Kurosakishiroishi, Yahatanishi-ku, Kitakyushu 806-0004, Japan
Phone +81-93-645-7703 Fax +81-93-645-7802
YASKAWA America Inc. (Motoman Robotics Division)
100 Automation Way, Miamisburg, OH 45342, U.S.A.
Phone +1-937-847-6200 Fax +1-937-847-6277
YASKAWA Europe GmbH Robotics Divsion )
Yaskawastrasse 1, 85391 Allershausen, Germany
Phone +49-8166-90-100 Fax +49-8166-90-103
YASKAWA Nordic AB
Bredbandet 1 vån. 3 varvsholmen 392 30 Kalmar, Sweden
Phone +46-480-417-800 Fax +46-480-417-999
YASKAWA Electric (China) Co., Ltd.
22/F One Corporate Avenue No.222, Hubin Road, Huangpu District, Shanghai 200021, China
Phone +86-21-5385-2200 Fax 㧗 86-21-5385-3299
YASKAWA SHOUGANG ROBOT Co. Ltd.
No7 Yongchang North Road, Beijing E&T Development Area China 100176
Phone +86-10-6788-2858 Fax +86-10-6788-2878
YASKAWA India Private Ltd. (Robotics Division)
#426, Udyog Vihar, Phase- IV, Gurgaon, Haryana, India
Phone +91-124-475-8500 Fax +91-124-475-8542
YASKAWA Electric Korea Co., Ltd
9F, Kyobo Securities Bldg., 26-4, Yeouido-dong, Yeongdeungpo-gu, Seoul 150-737, Korea
Phone +82-2-784-7844 Fax +82-2-784-8495
YASKAWA Electric Taiwan Corporation
12F, No.207, Sec. 3, Beishin Rd., Shindian District, New Taipei City 23143, Taiwan
Phone +886-2-8913-1333 Fax +886-2-8913-1513
YASKAWA Electric (Singapore) PTE Ltd.
151 Lorong Chuan, #04-02A, New Tech Park, Singapore 556741
Phone +65-6282-3003 Fax +65-6289-3003
YASKAWA Electric (Thailand) Co., Ltd.
252/125-126 27th Floor, Tower B Muang Thai-Phatra Complex Building,
Rachadaphisek Road 㧘 Huaykwang, Bangkok 10320, Thailand
Phone +66-2693-2200 Fax +66-2693-4200
PT. YASKAWA Electric Indonesia
Menara Anugrah Lantai 1, Kantor Taman E.3.3, JI Mega Kuningan Lot 8.6-8.7, Kawasan
Mega Kuningan, Jakarta, Indonesia
Phone +62-21-57941845 Fax +62-21-57941843
Specifications are subject to change without notice for ongoing product modifications and improvements.
YASKAWA ELECTRIC CORPORATION
C
MANUAL NO. RE-CHO-A111 5
Printed in Japan August 2014 11-09
Download
Anúncio