Scanlab RTC6 PCIe Board - Requirements and Activation; Jump-Length-Dependent Jump Delays

RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
218
innovators for industry
Requirements and Activation
The following are required for enabling and
activating Jump Mode:
• At least one of the two scan head connectors
must have been assigned a correction table.
• At least one of the two scan head connectors
must be connected to an intelliSCAN, intellicube,
intelliWELD or intelliDRILL scan system.
• As of scan system firmware  2078.
• The attached scan system must be equipped with
at least one Jump tuning. In contrast, a
Vector tuning is not absolutely required.
• The tuning numbers specified by
set_jump_mode must match those stored on the
board.
• The tunings specified by set_jump_mode must
be of the proper type – Vector tuning or
Jump tuning – (the Tuning type is stored in the
scan system firmware) and must be suitable for
rapid switching.
Before Jump Mode can be activated by
set_jump_mode_list, it must have been successfully
enabled at least once by set_jump_mode (see
command description).
The set_jump_mode control command (but not the
set_jump_mode_list list command) performs an
appropriate check if Jump Mode has been not
already enabled.
Jump-Length-Dependent Jump Delays
When executing a “Hard Jump”, it takes the
scan head some time to reach the specified position.
The RTC6 PCIe Board takes this delay (also called step
response) into account by appending a Jump Delay at
the end of the jump.
Point-by-point laser processing does not need to take
other Scanner Delays into account and you can
generally set Laser Delays to 0.
The specific step response behavior of the respective
scan system (step response time vs. jump length) can
be stored on the RTC6 PCIe Board in a user-specific
Jump Delay table. With Jump Mode enabled, the
RTC6 PCIe Board uses the specified Jump Delay table
to determine the appropriate Jump Delay value for
each 2D jump in accordance with the jump’s longer
edge (that is, either the x or y component of the
jump).
You can determine the step response behavior
experimentally and then load it onto the board as a
table of values using load_jump_table_offset.
Alternatively, the Jump Delay table can also be
automatically determined by
load_jump_table_offset (parameter Name = NULL).
Additionally, the currently loaded Jump Delay table
can be retrieved as a binary table by get_jump_table
and reloaded onto the board by se
t_jump_table.
The
step response time (at least for longer jumps)
typically scales with the squareroot of the
jump length, and load_program_file accordingly
initializes the internal jump table – with an end value
of 10.24 ms for a jump length of 2
20
bits.
When the Jump Delay table has been loaded and a
new RTC6DAT.dat file is created by create_dat_file,
then this table is automatically loaded upon the next
load_program_file.