YASKAWA GA500 Maintenance & Troubleshooting page 43

Industrial ac microdrive
Table of Contents

Advertisement

Code
Name
Note:
• The drive detects this error if the difference between the detected speed and the speed reference is more than the setting of F1-10 for longer than F1-11.
• Do a Fault Reset to clear the fault.
• If the drive detects this error, the drive will operate the motor as specified by the stopping method set in F1-04 [Speed Deviation Detection Select].
Code
Name
dv7
Polarity Judge Timeout
Note:
• The drive detects this error if it cannot detect polarity in a pre-set length of time.
• Do a Fault Reset to clear the fault.
Code
Name
EEPROM Memory DWEZ Data
dWF1
Error
Note:
• The drive detects this error if there is an error in the DriveWorksEZ program that was saved to EEPROM.
• Do a Fault Reset to clear the fault.
Code
Name
dWF2
DriveWorksEZ Fault 2
Note:
Do a Fault Reset to clear the fault.
Code
Name
dWF3
DriveWorksEZ Fault 3
Note:
Do a Fault Reset to clear the fault.
Code
Name
dWFL
DriveWorksEZ Fault
Note:
Do a Fault Reset to clear the fault.
Code
Name
E5
MECHATROLINK Watchdog Timer
Err
Note:
• Do a Fault Reset to clear the fault.
• If the drive detects this fault, it will operate the motor as specified by the stop method set in F6-25 [MECHATROLINK Watchdog Error Sel].
Code
Name
EF0
Option Card External Fault
Note:
• The drive detects this fault if the alarm function on the external device side is operating.
• Do a Fault Reset to clear the fault.
• If the drive detects this fault, it will operate the motor as specified by the stop method set in F6-03 [Comm External Fault (EF0) Select].
YASKAWA TOEPYAIGA5001A GA500 DRIVE MAINTENANCE & TROUBLESHOOTING
Causes
The load is locked up.
The holding brake is stopping the motor.
Causes
There is a disconnection in the motor coil winding.
The screws on the drive output terminals are loose.
Causes
There is an error in the EEPROM peripheral circuit.
There is a problem with the EEPROM data.
Causes
There was a fault in the DriveWorksEZ program.
Causes
There was a fault in the DriveWorksEZ program.
Causes
There was a fault in the DriveWorksEZ program.
Causes
The drive detected a watchdog circuit exception while
it received data from the controller.
Causes
The communication option received an external fault
from the controller.
A programming error occurred on the controller side.
Possible Solutions
Examine the machine.
Release the holding brake.
Possible Solutions
Measure the motor line-to-line resistance and replace the motor if a
coil is disconnected.
Tighten the terminal screws to the correct tightening torque.
Possible Solutions
• Re-energize the drive.
• If the fault stays, replace the control board or the drive. For
information about replacing the control board, contact Yaskawa
or your nearest sales representative.
Set A1-03 = 2220, 3330 [Initialize Parameters = 2-Wire
Initialization, 3-Wire Initialization] to initialize the drive, then
upload the DriveWorksEZ project to the drive again.
Possible Solutions
Examine the DriveWorksEZ program and remove the cause of the
fault. This is not a drive fault.
Possible Solutions
Examine the DriveWorksEZ program and remove the cause of the
fault. This is not a drive fault.
Possible Solutions
Examine the DriveWorksEZ program and remove the cause of the
fault. This is not a drive fault.
Possible Solutions
Examine the MECHATROLINK cable connection. If this error
occurs frequently, examine the wiring and decrease the effects of
electrical interference as specified by these manuals:
• MECHATROLINK-II Installation Guide (MECHATROLINK
Members Association, manual number MMATDEP011)
• MECHATROLINK-III Installation Manual (MECHATROLINK
Members Association, publication number MMATDEP018)
Possible Solutions
1.
Find the device that caused the external fault and remove the
cause.
2.
Clear the external fault input from the controller.
Examine the operation of the controller program.
2.4 Fault
2
43

Advertisement

Table of Contents
loading

Table of Contents