IAI RA Series, Инструкция по эксплуатации

Страница: 179 / 186

8. T
roubleshooting
171
Phenomenon Cause/Action
Error No. 4BE “Synchronizing Slave Axis
Operation Complete Error” occurs
[Content and cause]
The slave axis operation program finished during the
synchronizing operation. It also occurs when the slave axis
operation got cancelled due to an error occurrence except for
axis-related during the synchronizing operation. In case that
the master axis and slave axes are operated in different
programs, only slave axis operation program cannot be
finished during the synchronizing operation.
[Countermeasure]
Finish the synchronizing operation before finishing the
program. In order to finish the program from the PC software or
a teaching pendant, cancel all the operations or finish from the
master axis operation program.
Error No. 531 “Slave Operation
Parameter Error” occurs
[Content and cause]
There is an error in a parameter setting related to the standard
driver control.
[Countermeasure]
Check the following parameters.
• Extension Motion Control Each Axis Parameter No. 18
As a cause of this error, following things can be considered.
• There is an axis that cannot be indicated for the standard
driver control
(Rotary shortcut control select, linear axis infinite stroke
mode, synchronizing, ZR unit, SCARA axis, etc.)
• Duplication exists in axis indication subject for control
• The axis subject for control is invalid
Error No. 5A4 “Extension Motion Control
Fieldbus Parameter Error” occurs
[Content and cause]
There is an error in the parameter setting for the extension
motion control.
Following can be considered as a cause.
1) The setting in Extension Motion Control Each Axis
Parameter No. 4 “Slave Address” is inappropriate (setting
out of range, duplicated indication of address, etc.)
[Countermeasure]
Revise the parameter setting referring to the axis number that
the error has occurred.
Error No. 5A5 “Extension Motion Control
Fieldbus Reception Error” occurs
[Content and cause]
XSEL has detected the reception error (data not received, CRC
error, etc.). Followings can be considered as a cause.
1) Communication error due to noise or cable line breakage /
connection error
2) Slave driver is not in a condition available for communication
(such as power shutoff).
3) Malfunction of hardware
[Countermeasure]
Refer to “Process in Trouble Occurrence”, and check the
countermeasure for cable line breakage, connector drop-off,
slave driver power supply condition and noise.
ME0364-2B