User`s guide

instruction at a time. For information on the V+ program debugger, see The Program
Debugger on page 85.)
Execution of program tasks other than #0 is generally the same as for task #0. The following
points highlight the differences:
l The task number must be explicitly included in all the monitor commands and program
instructions that affect program execution, including EXECUTE, ABORT, PROCEED,
RETRY, SSTEP, and XSTEP. (However, when the V+ program debugger is being used,
the task being accessed by the debugger becomes the default task for all these
commands.)
l If the program is going to control the robot, it must explicitly ATTACH the robot before
executing any instructions that control the robot.
l If task 0 is not executing concurrently, the V+ monitor prompt continues to be a dot
(.). Also, the prompt is displayed after the task-initiating EXECUTE command is
processed.
NOTE: If you want program execution to be delayed briefly to allow time for the dot
prompt to be output (for example, to prevent it from occurring during output from the
program), have your program execute two WAIT instructions with no parameter.
l The TRACE feature does not apply to tasks other than #0.
NOTE: To use TRACE with a program that is intended to execute in a task other than #0,
execute the program as task #0. (This consideration does not apply when using the V+
program debugger, which can access any program task.)
See the section Scheduling of Program Execution Tasks on page 48 for details on task
scheduling.
Executing Programs
V+Language User's Guide, v17.0
Page 38