5 Programming and Testing: Service Routines
5 Programming and Testing: Service Routines
5 Programming and Testing: Service Routines
Service routines
Service routines perform a number of common services. Which service routines
are available depends on your system setup and available options. Please refer
to your plant or cell documentation for more information.
Prerequisites
Service routines can only be started in manual reduced speed mode or in manual
full speed mode.
The program must be stopped and there has to be a program pointer.
It is not possible to call a routine when in synchronized mode.
If the service routine contains parts that must be carried out in automatic mode,
then the program pointer must not be moved manually before starting the service
routine. The program pointer should be where the program flow was stopped.
WARNING
CAUTION
Note that once a service routine has started, aborting it might not resume the
system to its previous state, as the routine may have moved the robot arm.
Action
2 On the Debug menu tap Call Routine.
en0400000884
3 The Call Service Routine dialog lists all predefined service routines.
The same dialog can however be used to run any routine in the task scope. Select All
Routines on the View menu to see all available routines.
en0400000885
Action
5 Press the Start button on the FlexPendant and follow the instructions displayed on
the FlexPendant.
After execution of the routine the task is stopped and the program pointer is returned
to where it was before the service routine started.
CAUTION
Press Cancel Call Rout if you need to interrupt the routine before it has finished
executing. Before resuming normal program flow, however, you must see to it
that the robot is correctly positioned. If the interrupted routine has moved it, you
will need to take actions to return the robot to its position. See Returning the
robot to the path on page 242 for further information.
WARNING
Limitations
Besides service routines, Call Routine applies to all routines with the following
criteria:
• Must be a procedure with empty parameter list. This means not a function
and not a trap routine.
• Must be in the task scope, not local. If the procedure is local in a module the
scope is restricted to that module, and the procedure is not visible from the
task level.
• Must be in a loaded module, not installed. (Check the system parameter
Installed in the type Automatic Loading of Modules in the Controller topic.)
Related information
Battery shutdown service routine on page 216.
LoadIdentify, load identification service routine on page 219.
Service Information System, ServiceInfo service routine on page 218.
Calibration Pendulum, CalPendulum service routine on page 217.