Scanlab RTC 5 PC Interface Board, Инструкция по установке и эксплуатации

Страница: 568 / 622

RTC
®
5 PC Interface Board
Rev. 1.9 e
12 Troubleshooting
568
innovators for industry
Additionally, the following commands can be helpful
for troubleshooting:
• With get_error and get_last_error , nearly any
command can be checked for proper execution
(see
chapter 6.8 "Error Handling", page 87 ).
• With set_verify , you can verify that all
downloads (commands, tables) were performed
error-free (see
section "Download Verification" on
page 88 ).
• With get_value or get_values , you can query
specific values returned from the scan-system.
With
set_trigger / set_trigger4 and
get_waveform , you can record an entire series of
returned values (see section "Status Monitoring
and Diagnostics" on page 127 ; for i DRIVE
®
scan
systems also see chapter 8.1, page 152 ).
• With set_wait and get_wait_status , you can
check if program branches (conditional jumps)
executed as intended.
• With get_overrun , you can check if overruns of
the 10 µ s clock period occurred (see section
"Clock Overruns" on page 126 ).
• With get_status or get_out_pointer , you can
determine which command number the program
is currently executing (e.g. for “infinite loops“ due
to a circular argument in the program flow).
• get_startstop_info provides information about
the laser signals and possible transmission errors
to and from the attached scan system.
If specific outputs from a port have no effect, then
check if the user application is performing directly
consecutive accesses of that same port. Because so-
called short list commands (see
page 217 ) are typi-
cally used for this, one command might overwrite the
other’s output value within the same 10
µ
s clock
period. In this situation, separate both short
commands with a (normal) list command, e.g.
list_nop or list_continue .
If the execution time (measured via
save_and_restart_timer
and
get_time
) doesn’t
correspond with your calculation, check if your appli-
cation contains so-called short list commands, which
generally don’t require their own clock period for
execution. Another possibility is that additional
scanner delays were automatically inserted to
prevent (improper) overlap of LaserOn and LaserOff
(see
section "Automatic Delay Adjustments" on
page 107 ).
If the problems persist, please contact SCANLAB.