List Execution Status - Scanlab RTC 5 PC Interface Board Installation And Operation Manual

set_start_list_pos(ListNo, Pos ) and execute via
execute_list_pos(ListNo, Pos). If no other list
has been active at this moment, then list ListNo
has the status USED afterward.
• When interpreting the status values returned by
read_status, always take into account the
programmed loading or execution processes of
the lists (see command description).
®
RTC 5 PC Interface Board
Rev. 1.9 e
6 Developing User Applications

6.4.3 List Execution Status

The provided list status values are supplemented by
three additional status values that indicate whether
one of the two lists is currently being executed
(BUSY), if its execution is currently interrupted
®
(PAUSED) or if the RTC 5 is busy with executing
control commands beyond list execution (INTERNAL-
BUSY). These status values can be queried via the
get_status (page 281) command.
• The BUSY status is set when a list is currently being
processed or when a list has been halted via the
control commands pause_list
contrast, the BUSY status is not set if a list has
been paused via the list command
will then be again set via a subsequent
release_wait command).
• The PAUSED status is set when a list has been
halted via pause_list, stop_list
reset via a subsequent restart_list
release_wait command (also see
Lists for Synchronization of Processing", page
• The INTERNAL-BUSY status is set when the RTC
is busy with executing a control command, which
needs more than 10 µs for executing a scan move-
ment (e.g. goto_xy or possibly set_offset) or
while a home jump or home return is executed
(with set_wait, set_end_of_list
if the home jump mode has been previously acti-
vated via home_position
home_position_xyz). The INTERNAL-BUSY status
and the BUSY status cannot be set at the same
time.
Notes
• The BUSY status is also available as the BUSY OUT
signal at the 15-pin D-SUB LASER connector (see
figure 10 on page 46), and the EXTENSION 1
connector (see figure 15 on page
the MARKING ON THE FLY connector (see
figure 18 on page 51).
• Some control commands are ignored (not
executed), when the BUSY status and/or
INTERNAL-BUSY status are set (e.g. auto_cal,
goto_xy, load_correction_file) or – with set
INTERNAL-BUSY status – are only executed with
delay after the INTERNAL-BUSY status has been
reset again (e.g. execute_list_pos, set_offset).
or stop_list. In
set_wait (and
or set_wait. It is
or
"Interrupting
74).
®
5
or release_wait,
or
49) as well as
73