IAI RA Series, Instruction Manual

Page: 175 / 186

8. T
roubleshooting
167
8. Troubleshooting
8.1. Notes Related to Generally for Errors
• Refer to the instruction manual of each controller for contents of each error, countermeasures and
general troubleshooting of controllers.
• In order to check the conditions of the RC controller (alarm list, parameters, etc.), it is necessary
to prepare an RC teaching tool. Also, if switching the RC controller over to MANU Mode while in a
condition that the connection is established with the XSEL, an error such as Error No. 4B0
“Extension Motion Control Fieldbus Slave Station Command Detection” could occur.
• Changing a parameter on RC Controller after the connection is established with XSEL may cause
an error on XSEL side or cause mismatches to the recognition of parameters between XSEL and
RC Controller. Make sure to reboot the power to XSEL and RC Controller after a change is made
to a parameter on RC Controller.
• If an error related to an axis is occurred on an extension motion control axis, the value of
“extension motion control axis 1000” is shown as the axis number in the error list.
[Example] Error Occurred No. “1005” • • • Error occurred on Extension Motion Control Axis
No. 5
Considering above, check the axis with an error occurred.
(*However, when the axis use method is the standard driver control, some errors show the control
device number (1 to 8).)
• If errors occur in movement axes in commands where the execution is completed during axis
movements, such as commands to start electronic CAM and other synchronization movements,
positioning commands enabling position complete band, etc., step No. where errors occurred,
which are displayed in the error list, become the step No. of commands that commanded axis
movements, not step No. being executed when errors occurred.
When connecting a teaching tool to the RC controller, make sure to conduct the
following procedures before connecting.
• Stop all the programs of XSEL
• Turn the servo off on all the axes
ME0364-2B