IAI RA Series, Instruction Manual

Page: 177 / 186

8. T
roubleshooting
169
Phenomenon Cause/Action
Alarm reset cannot be conducted on RC
axis
Cause:
Countermeasure:
1) An error with higher level than cold start
has been occurred on the RC controller.
2) The operation mode of the RC controller
prohibits launching PIO.
1) If an error with higher level than cold
start has been occurred, remove the
cause of the error and turn off and on
the power to the RC controller.
2) Switch the operation mode of the RC
controller to PIO startup permitted
(AUTO Mode).
Error No. 452 “Slave Driver Alarm
Detection” occurs
Cause:
Countermeasure:
There was an error occurred on the RC
controller.
Connect a teaching tool to the RC
controller and take a counteraction to the
alarm code currently occurred.
* Refer to the “latest” alarm code occurred
on the RC controller displayed in Info.1 in
the error list.
(Also, the value for Info. 1 may become 0
depends on the condition of the RC
controller.)
However, as there is a concern that
several alarms are generated at the
same time in the actual case, it is
recommended basically to connect a
teaching tool to the RC controller to
check the alarms.
Especially when an alarm such as the
absolute battery related alarm is
occurred in the RC controller startup,
without absolute reset on the RC
controller, there is a concern that the
coordinates can be determined with the
home position in wrong.
Error No. 4B0 “Extension Motion Control
Fieldbus Slave Station Command Error
Detection” occurs.
[Content and cause]
The MECHATROLINK Command Error has been detected in
the slave station.
[Countermeasure]
Confirm that there is no other error occurred in the axis where
this error occurred using the error list.
1) This error occurred together with an Error No. 5A6
“Extension Motion Control Fieldbus Command
Completion Time Out Error” at the start-up.
→ Refer to the Countermeasure for the Error No. 5A6.
2) This error occurred together with an Error No. 452 “Slave
Driver Alarm Detection”.
→ Refer to the Countermeasure for the Error No. 452.
When any of the above two items is not applied, check the
following points.
• Check whether or not the slave has been in the AUTO
mode.
• Check whether or not the power is supplied to the
slave-axis driving source.
[Additional Description]
This error might occur, if the slave axis servo is turned ON
immediately after the XSEL start-up (when the automatic start
program is executed in the AUTO mode). In such case, delay
the axis start-up about 3 seconds after the XSEL start-up
completion, using the TIMW command, to avoid the error.
ME0364-2B