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

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

RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
156
innovators for industry
8.1.5 Jump Mode
For applications such as drilling holes with defined
spacing (whereby laser processing is actually point-
by-point rather than along lines and curves), you can
optimize process times by activating the so-called
jump mode. For this, the scan system must be
equipped with a jump tuning (also see
section
"Requirements and Activation" on page 157 ).
Functional Principle
In the default setting (after load_program_file ),
both jump commands and marking commands
execute in vector mode:
• The jump length gets subdivided into individually
executable microvectors in accordance with the
current jump speed. If the scan system is only
equipped with a jump tuning, then the
microvectors will execute using this tuning.
• A subsequent list command will be preceded by a
jump delay specified via set_scanner_delays .
In contrast, when jump mode is enabled and acti-
vated via the
set_jump_mode or
set_jump_mode_list
command, every 2D jump (see
below) will execute as follows :
• The 2D jump’s entire jump length will execute as
a so-called hard jump via a timed jump with a
10
µ s execution time, i.e. the target position gets
instantaneously outputted without microvector-
ization.
• The jump will execute with a jump tuning (the
scan system must be equipped with one).
set_jump_mode can be used to designate which
jump tuning to use. If a different tuning was set
before the jump, then the RTC
®
5 will automati-
cally switch at the beginning of the jump to the
tuning specified via
set_jump_mode .
• At the end of the 2D jump, the RTC
®
5 automati-
cally switches to a vector tuning (if the scan
system is equipped with one and if a corre-
sponding setting was made via
set_jump_mode ).
• At the end of the 2D jump, a jump-length-
dependent jump delay will occur. This jump delay
can be specified for the corresponding jump
length via
load_jump_table_offset or
set_jump_table (also see "Jump-Length-
Dependent Jump Delays", page 157 ). Here, an
external jump delay specified via
set_scanner_delays is not taken into account.
Notes
• Jump mode works exclusively on
– jump_abs , jump_rel , goto_xy ( not on the cor-
responding 3D, para or timed commands)
– home jumps and home returns (see
home_position )
• If a 2D jump occurs where the jump length limit
(
Length
parameter) specified via
set_jump_mode is not reached or exceeded on
at least one of the two axes, then the jump will
execute in vector mode even if jump mode was
enabled and activated. This allows exploitation of
the fact that
short jumps can in some circum-
stances execute faster via vector tuning than with
jump tuning. But if no vector tuning is installed or
none specified, then you should set the
Length
parameter to 0.
• Each switch between different tunings (servos)
requires an additional 10 µ s clock period. For
applications such as pure drilling, this can be
avoided by not specifying a vector tuning to
switch back to when you call
set_jump_mode .
• When you deactivate or disable jump mode (via
set_jump_mode or set_jump_mode_list ), then
subsequent jumps will again execute in vector
mode (microvectorized and without further servo
autoswitching). Here, the vector tuning will be
used that was most recently set at the end of
jump mode, unless deactivation was followed by
selection of a different tuning via
control_command . Moreover, the most recently
set jump speed will again be used and jumps will
be followed by the jump delay specified via
set_scanner_delays .