RTC6 boards
Doc. Rev. 1.0.21 en-US
6 Developing RTC6-User Programs
131
Some control commands (for example, init_rtc6_dll,
load_correction_file or load_program_file)
additionally return a special error code as the result
value that is not buffered and must therefore be
immediately evaluated or discarded by the
user program.
6.8.1 Download Verification
Verification of RTC6 communication is vital
particularly in medical applications. For this purpose,
you can activate download verification separately for
each board by set_verify.
However, this automatically results in extended
download times.
If download verification is activated and an error is
found, then the error code
RTC6_VERIFY_ERROR
is set,
which can be queried by get_last_error or get_error.
Certain operations might immediately be aborted
and the board would then no longer be functional
(for example, if load_program_file has been
aborted).
With download verification activated, the following
checks are performed (also note the comments in the
command description of set_verify):
(1) Loading of list commands
For list-command downloads, each download is
read back and compared (for equality) against
the sent command. Here, only transfer to the
RTC6 PCIe Board itself is checked; automatic
parameter adjustments (for example, clipping)
are not taken into account.
(2) Loading of control commands
For control commands, the corresponding
parameters are read back and compared for
equality against the sent parameters. Automatic
parameter adjustments are not taken into
account.
(3) load_program_file
For sending of load_program_file, the following
is checked:
–
RTC6DAT.dat
is tested by a checksum for file
correctness and PCI-transfer correctness.
–
RTC6RBF.rbf
is only checked by a bitwise
transfer handshake. No other checking is
possible.
– Each loaded section of
RTC6OUT.out
is
immediately read back for checking. If an error
is detected, then the loading process aborts.
To Next Page
Loading...