RTC6 boards
Doc. Rev. 1.0.21 en-US
6 Developing RTC6-User Programs
129
When an RTC6 PCIe Board is acquired by another
user program, some important information
managed by the previous user program only in the
RTC6 DLL is not (automatically) taken over. The
acquiring user program thereby lacks information
related to memory configuration, protected-area
management, or the operational status.
If board acquisition is followed by a board
initialization by load_program_file and all settings
are newly defined anyway, such missing information
would not be relevant.
On the other hand, if the acquiring user program is
supposed to further use the inherited state of the
RTC6 PCIe Board, then it must explicitly query the
missing RTC6 DLL information, receive it from the
previous user program and explicitly re-establish it so
that RTC6 DLL and board remain consistent. In this
regard, observe the following notes.
Notes
• For a correct behavior of the input pointer at the
list borders, the memory configuration currently
set in the RTC6 DLL for the acquiring
user program must be consistent to the current
memory configuration of the acquired board.
get_config_list obtains the current memory
configuration of the board and sets it in the
RTC6 DLL correspondingly.
• The management tables of protected functions
(indexed subroutines, character sets and text
strings) are located on the board.
All protected functions stored on the board
therefore remain callable. On the other hand,
information on where the next protected
function should be loaded is lost. This
information can only be restored by
save_disk/load_disk, see Section ”Index
Management and Defragmentation”, page 115.
An alternative restoration method is not possible.
The intermixed loading of protected functions by
differing applications should therefore be
avoided.
• The input pointer is generally not inherited (the
input pointer location currently saved in the
RTC6 DLL for the acquiring user program is used,
maybe corrected after get_config_list). On the
other hand, output pointers of lists can be
queried after an acquisition by get_status.
• After acquisition and until the next load_… call,
the list status (in regards to LOAD list status and
READY list status) might be incorrect. But for
further execution this is not important, and the
status is newly set after the next load_… call.
• Other settings such as start_loop or laser settings
are not relevant to the RTC6 DLL. Though settings
used by the previous user program can not
generally be queried, new settings can of course
be set as desired.
• Error handling is performed separately for each
board and each user program. When access
rights are exchanged, this data is not included.
To Next Page
Loading...