RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
391
Comments • When interpreting the status values returned by read_status, always take into account
the programmed loading or execution processes of the lists. Under some circum-
stances, the status values can be misleading, as illustrated by the following examples:
– Even during a loading process, a list’s LOAD status can already have been reset and
its READY status set if – after loading of a set_end_of_list command into a list – fur-
ther list commands are loaded into the same list.
– The status values remain unchanged if a set_end_of_list command is overwritten
with another command (READY is not reset).
– If – during a loading process– a set_end_of_list command is processed at the same
time in the same list, then the list is regarded as already processed (USED status set),
even though it will still be newly loaded (USED was then initially reset).
– Even if a completely loaded command list (incl. set_end_of_list) has been stored, a
list’s READY status can be reset if the input pointer was newly set (e.g. via
set_input_pointer) into the list. Then a list’s USED status can be reset too, even
though a completely loaded and already processed command list is stored.
– For jumps from one list area to another (“List 1” <-> “List 2”, e.g. via
list_jump_pos) during execution, the USED status values of both lists (unlike their
BUSY status values) remain unchanged and are therefore not meaningful.
• If the list status is queried during processing of a subroutine in the protected buffer area
(“List 3”), then the status will be returned of the list (“List 1” or “List 2”) in which the
output pointer most recently resided (typically from where the subroutine was origi-
nally called).
• If list execution is interrupted (via pause_list, stop_list or set_wait), then the above-
mentioned status values will remain unchanged.
• The list execution statuses BUSY and PAUSED (see "List Execution Status", page 73) can
be queried via get_status (page 281).
• To read the status signals from the scan heads, use the command get_head_status
(page 266).
RTC
®
4
RTC
®
5 essentially unchanged functionality, however:
the RTC
®
5 also provides a USED status
References get_status, get_head_status
Ctrl Command read_user_data
Function queries the status information currently returned from the scan system via the user data
bit.
Comments • Up to now, this command has no effect, but it is reserved for future use according to
chapter 7.3.6 "Status Monitoring and Diagnostics", page 127 and chapter 8.1.2
"Configuring Status Return Behavior", page 153.
References send_user_data
Ctrl Command read_status
To Next Page
Loading...
