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

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

RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
218
innovators for industry
Notes
• Where applicable, the total execution time of
normal and variable list commands equals the
sum of the command execution time and the
execution time of the process initiated by the
command. A subsequent list command will only
run after this total execution time has completed.
Example: the total execution time of the normal
list command
mark_abs is 10 µ s (command
execution time) + the execution time of the
marking process. The latter is dependent on the
settings of such parameters as marking length,
marking speed, and delays etc.
Undelayed and Delayed Short List
Commands (as of Version OUT 515)
Most short list commands (e.g. list_jump_pos ,
list_call , sub_call or list_return ) (with all software
versions) execute before the next list command and
prior to a possible scanner delay (jump, mark or
polygon delay). These commands are called “unde-
layed short list commands” in the corresponding
command descriptions (in
chapter 10.2 ).
However (as of version OUT 515), some short list
commands only execute after the respective scanner
delay (i.e. directly before the next command). Such
commands are called “delayed short list commands”
in the corresponding command descriptions. These
include commands that immediately affect output or
laser power (e.g.
set_rot_center_list ,
set_wobbel_mode , write_da_x_list ,
set_laser_pulses , set_standby_list ,
set_mark_speed , set_encoder_speed ) or
commands that affect data acquisition or time
measurement (e.g.
set_trigger or
save_and_restart_timer ).
If such (now delayed) commands were to execute
with older software versions, then laser power, for
example, would change at the end of a marking
command (during a still-active mark or polygon
delay) instead of at the beginning of the next marking
command.
set_trigger and save_and_restart_timer
would erroneously take into account the delay of a
preceding command instead of the delay of the
subsequent command.
For several short list commands in a row, even a
“delayed short list command” will only execute
delayed if no further “delayed short list commands”
directly follow (i.e. if it’s the last one in that sequence
of commands or if an “undelayed short list
command” directly follows)
(1)
. For several “delayed
short list commands“ in a row, all short list
commands at the beginning of such a sequence will
execute undelayed (i.e. even before a scanner delay).
So if several short list commands are placed between
two marking commands within a polyline, then the
most important “delayed” commands (e.g. the
commands that change laser power) should
therefore be placed at the end (i.e. directly before the
next marking command) or directly before an “unde-
layed short list command”. Alternatively, you can also
explicitly initiate processing of the scanner delay (e.g.
via
list_nop
), so that all subsequent short list
commands in fact always execute “delayed”.
If a normal list command succeeds more than two
short list commands, then all short list commands
(even “delayed” short list commands) will execute
immediately (“undelayed”) and the normal list
command will execute delayed by a 10 µs clock
period.
List Multi-Commands
A list multi-command has multiple components that
accordingly occupy multiple list buffer positions. The
initial components are always undelayed short list
commands. The final component is always a short,
normal or variable list command. All components
immediately execute successively. Any still-pending
delayed short list commands will execute first. The
RTC
®
5 command set currently only contains two-
component list multi-commands (e.g.
wait_for_encoder_in_range or set_pixel_line_3d ).
(1) This applies as of RTC5OUT.out Version 518. For versions 515-
517 or lower, a “delayed short list command” among several
short list commands in a row will only execute delayed if it is at
the end of that sequence of commands.