Scanlab RTC6 PCIe Board - Jump Mode; Functional Principle

RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
217
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”.
This requires the scan system to be equipped with a
Jump tuning, see also Section ”Requirements and
Activation”, page 218.
Functional Principle
In the default setting (after load_program_file),
both Jump Commands and Mark Commands are
executed in vector mode:
• The jump length gets subdivided into individually
executable Microsteps in accordance with the
current jump speed. If the scan system is only
equipped with a Jump tuning, then the
Microsteps execute using this tuning.
• A Jump Delay defined by set_scanner_delays is
executed before a subsequent list command.
In contrast, when Jump Mode is enabled and
activated by set_jump_mode or
set_jump_mode_list, every 2D jump (see below) is
executed as follows:
• The entire jump length of the 2D jump is
controlled as a “Hard Jump” over a time
dimensioned jump of 10 µ duration. The target
position is executed without Microstepping.
• The jump executes with a Jump tuning.
set_jump_mode can be used to designate which
Jump tuning to use. If a different tuning has been
set before the jump, then the RTC6 PCIe Board
automatically switches at the beginning of the
jump to the tuning specified by set_jump_mode.
• At the end of the 2D jump, the RTC6 PCIe Board
automatically switches to a Vector tuning (if the
scan system is equipped with one and if a
corresponding setting has been made by
set_jump_mode).
• At the end of the 2D jump, a jump-length-
dependent Jump Delay occurs. This Jump Delay
can be specified for the corresponding
jump length by load_jump_table_offset or
set_jump_table, see also Section ”Jump-Length-
Dependent Jump Delays”, page 218. Here, an
external Jump Delay specified by
set_scanner_delays is not taken into account.
Notes
• Jump Mode works exclusively on
– jump_abs, jump_rel, goto_xy (not on the
corresponding 3D, para or timed commands)
– home jumps and home returns (see
home_position)
• If a 2D jump occurs where the
jump length limit
( Length p
arameter) specified by set_jump_mode
is not reached or exceeded on at least one of the
two axes, then the jump executes in vector mode
even if Jump Mode has been enabled and
activated. This allows exploitation of the fact that
short jumps can in some circumstances execute
faster by 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 cycle. 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 (by
set_jump_mode or set_jump_mode_list), then
subsequent jumps again execute in vector mode
(split-up into Microsteps and without further
servo autoswitching). Here, the Vector tuning is
used that has been most recently set at the end of
Jump Mode, unless deactivation has been
followed by selection of a different tuning by
control_command. Moreover, the most recently
set jump speed is again used and jumps are
followed by the Jump Delay specified by
set_scanner_delays.