Omron SYSMAC CJ Series, Operation Manual

Page: 366 / 371

Troubleshooting Errors Section 6-3
354
6-3-12 BASIC Program Error
/i
6-3-13 Axis Error
/i
Problem Solution
BASIC program stopped working during
operation due to runtime error (bit 0 of the
SYSTEM_ERROR system parameter is
high, see section 4-2-230 for more details
on this parameter).
Using BASIC command RUN_ERROR
determine the error type that caused
runtime error. Using BASIC command
ERROR_LINE find a line in the BASIC
program which caused runtime
error.Modify found line causing an error to
prevent it from happening in the future
(see section 4-2-210 for more details on
RUN_ERROR and section 4-2-95 for
more details on ERROR_LINE BASIC
commands).
BASIC program cannot be run due to
compilation or syntax error. Use Trajexia Studio Software to edit and
compile BASIC programs. Editor of the
software will automatically highlight
locations of possible compile errors and
provide all necessary debugging
information while compiling the program.
Problem Solution
Not all physically present axes are
initialised. Some of them are virtual
(ATYPE = 0) or have illegal axis number -1
assigned. Wrong setting of the SERVO_PERIOD
system parameter for a given number of
MECHATROLINK-II stations and
axes.Correct the
SERVO_PERIOD value
and restart the unit (see section 4-2-218
for more information on valid
SERVO_PERIOD value depending on
number of connected stations).
Present axis has illegal axis number (-1)
assigned to it, Encoder Interface axis is in
error. Confliction axis number for
MECHATROLINK-II axis and Encoder
Interface axis. This can happen if a new
MECHATROLINK-II axis is added to the
system and the MECHATROLINK-II bus
is reinitialized using BASIC command
MECHATROLINK(0, 0) , but the unit is not
restarted.After adding new
MECHATROLINK-II axis to the system,
restart the unit.