RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
157
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.
• The software version of the attached scan
system(s) must be 2078 or higher.
• The attached scan system must be equipped with
at least one jump tuning. In contrast, a vector
tuning isn’t absolutely required.
• The tuning numbers specified via
set_jump_mode must match those stored on the
board.
• The tunings specified via set_jump_mode must
be of the proper type – vector tuning or jump
tuning – (the tuning type is stored as info in the
scan system’s firmware) and must be suitable for
rapid switching.
Before jump mode can be activated via
set_jump_mode_list, it must have been successfully
enabled at least once via 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 wasn’t already enabled.
Jump-Length-Dependent Jump Delays
When executing a hard jump, it takes the scanner
some time to reach the specified position. The RTC
®
5
takes this delay (also called step response) into
account by appending a jump delay at the end of the
jump that appropriately postpones further program
execution (point-by-point laser processing doesn’t
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 RTC
®
5 in a user-specific jump delay
table. With jump mode enabled, the RTC
®
5 uses the
specified jump delay table to determine the appro-
priate jump delay value for each 2D jump in accor-
dance with the jump’s longer edge (i.e. either the x
or y component of the jump).
You can determine the step response behavior exper-
imentally and then load it onto the board as a table
of values using the load_jump_table_offset
command. Alternatively, the jump delay table can
also be automatically determined via
load_jump_table_offset (parameter
Name
= 0).
Additionally, the currently loaded jump delay table
can be retrieved as a binary table via get_jump_table
and reloaded onto the board via set_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.
To Next Page
Loading...