8.6.3 3D Marking Commands
®
The RTC
5's command set includes the following 3D
vector and timed 3D vector commands:
•
goto_xyz
• jump_abs_3d,
timed_jump_abs_3d
• jump_rel_3d,
timed_jump_rel_3d
• mark_abs_3d,
timed_mark_abs_3d
• mark_rel_3d,
timed_mark_rel_3d
®
In addition the RTC
5 command set provides the
following 3D arc commands which allow spiral
marking:
• arc_abs_3d,
arc_rel_3d
Except for the additional motion in the third
dimension, these commands function identically to
the corresponding 2D marking commands:
• The specified vectors or arcs will be microvec-
torized (with the same output period as with 2D
commands, see
page
96).
• As with 2D commands, jump and marking speeds
can be specified via
set_jump_speed
set_mark_speed
(see
page
vector commands, for timed 3D vector
commands, the speeds will be automatically
determined based on the specified jump or
marking duration.
• 3D image field correction will be applied in accor-
dance with the 3D correction table assigned via
select_cor_table
or
select_cor_table_list
page
120).
• For jump and mark commands, the laser control
signals will be switched on and off while taking
delay settings into account (see
®
The RTC
5 simultaneously calculates output values
for the galvanometer scanners of the scan system and
the corresponding focal lengths (or focal intercepts)
and output values for the Z-axis. Here, the RTC
appropriate data from the assigned 3D correction
table. SCANLAB individually calculates each
correction table based on the optical configuration of
the specific 3-axis system and all available optical
system data (such as mirror geometry, calibration,
objective specifications and Z-axis optics specifica-
tions). Each correction table is stored in a correction
file named (*.CT5) in the RTC
(also see
load_correction_file, page
®
RTC
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
and
93). As for timed 2D
(see
page
99).
®
5 uses
®
5 software package
328).
®
In RTC
5 mode, the X and Y vector coordinates of a
vector must be specified as signed 20-bit numbers
(i.e. as numbers between – 524288 and +524287),
however the Z coordinates in a 3D system must be
signed 16-bit numbers (i.e. numbers between
– 32768 and +32767). Therefore, the calibration
factor (the ratio of a point coordinate in bits and the
actual position of the point in millimeters) is 16 times
smaller in the Z direction than in the X and Y direc-
tions:
K
= K
z
xy
In contrast, the following should be used for RTC
compatibility mode (as with the RTC
K
= K
= K
= K
/ 16.
x
y
z
xy
®
®
The RTC
5 (in RTC
5 mode as well as in RTC
compatibility mode) automatically upscales Z coor-
dinate values internally to 20-bit values, so that the
three dimensions of space can be handled equiva-
lently in terms of jump or marking speed values.
Notes
• If vector-defined laser control is activated via
set_vector_control, then para-mark and para-
jump commands (para_jump_abs_3d,
timed_para_jump_abs_3d, para_jump_rel_3d,
timed_para_jump_rel_3d, para_mark_abs_3d,
timed_para_mark_abs_3d, para_mark_rel_3d,
timed_para_mark_rel_3d) can also be used.
These commands simultaneously vary a signal
parameter linearly along the mark or jump vector
(see
page
147). With (Ctrl = 7), for example, the
focus shift (i.e. an offset to the calculated focal
length) will vary (as with
set_defocus_list).
• The size of the usable image field and the
maximum focus shift in the Z direction (height of
the usable working volume) can be obtained
from the "Readme.txt" file supplied with the 3D
correction file or from the user manual of the
3-axis scan system or the varioSCAN ("Technical
Specifications" chapter).
• If a Z axis serves the purpose of maintaining the
laser focus in a particular plane, then 2D vector
commands can be used, too (after the desired Z
position was set via a 3D vector command). 2D
vector commands have no effect on the Z
position, but regulate the focal length – if the 3D
option is enabled and a 3D correction table was
assigned – so that the laser beam maintains
focused in the same plane.
/ 16.
®
4
®
4):
®
4
set_defocus
or
172
Need help?
Do you have a question about the RTC 5 PC Interface Board and is the answer not in the manual?