Scanlab RTC 5 PC Interface Board, Installation And Operation Manual

Page: 392 / 622

RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
392
innovators for industry
Ctrl Command release_rtc
Function releases the specified RTC
®
5 for use by other applications (user programs)
Call
NoOfReleasedCard = release_rtc( CardNo )
Parameter
CardNo
(DLL-internal) number of the RTC
®
5 board as an unsigned 32-bit value
Result The returned (unsigned 32-bit) value is
CardNo
if the application was still in possession of
access rights for this board. Otherwise, 0 is returned.
Comments • After the application releases a board with release_rtc , it no longer has access rights
for this board. The board can then be subsequently acquired by the same or another
application via
acquire_rtc (page 227) or init_rtc5_dll (page 306) .
• If a board released via release_rtc was the active board, then (other than multi-board
commands) only those non-multi-board commands not requiring explicit access rights
will be subsequently available. Another board will not be automatically selected as the
active board. Activation of another board (for which access rights are assigned to the
application) can be achieved via the
select_rtc , page 403 command.
• The release_rtc command does not cause a reset of the RTC
®
5 board. Board resets can
only be initiated via the command load_program_file , page 340 .
• The release_rtc command is also available without explicit access rights for a particular
RTC
®
5 board, but the command then has no effect (return value 0).
• The release_rtc command also has no effect (return value 0) if
CardNo
exceeds the
number of RTC
®
5 boards found during initialization (see rtc5_count_cards , page 396 )
or if
CardNo
= 0 (real boards begin at 1).
• release_rtc is not available as a multi-board command.
RTC
®
4

RTC
®
5 new command
References acquire_rtc , init_rtc5_dll
Ctrl Command release_wait
Function resumes execution of a list that was interrupted by a set_wait command
Call
release_wait()
Comments • The command release_wait is only executed if the RTC
®
5 is actually in a wait state
(hence if a wait marker was previously reached and execution was halted; the PAUSED
status is then set, the BUSY status is
not set). Otherwise, the command is ignored
( get_last_error return code
RTC5_BUSY
).
• release_wait resets the PAUSED status and newly sets the BUSY status (both queriable
with get_status , also see "List Execution Status", page 73 ).
• The command release_wait resets to zero the wait_word that receives the wait marker
number during an interrupt.
• If a home jump (defined with home_position or home_position_xyz ) was executed via
set_wait , then release_wait will lead to a corresponding home return (the INTERNAL-
BUSY status is set while the home return is executed).
• The wait status can be queried via get_wait_status .
RTC
®
4

RTC
®
5 essentially unchanged functionality, however:
the RTC
®
5 also provides a PAUSED status that will be set with set_wait and reset with
release_wait .
References set_wait , get_wait_status , restart_list