Scanlab RTC 5 PC Interface Board Installation And Operation Manual page 123

Notes
• If no correction table has been loaded into the
®
RTC 5's memory, then the RTC
unintended values to the scan system. If no 2D or
3D correction file for the specific optical configu-
ration is available, then at least a 1to1 (2D or 3D)
correction table should be loaded (see
Correction Tables", page
Correction files should be loaded at the begin-
ning of an application program, before or after
loading the program file (via
(1)
page 340) . They should absolutely be loaded
and assigned prior to first-time starting of a list or
issuance of a control command (e.g.
page 296) that sets the scan system's
galvanometer scanners in motion.
• If only one of the two scan head connectors has
been assigned a 2D correction table (e.g. initial-
ization via load_program_file
correction table to the primary scan head), then
the other scan head connector will transmit no
signals.
• As of version DLL 521, OUT 521,
load_correction_file automatically calls
select_cor_table after loading the correction
table. This results in both assignment of a
correction table and triggering of a jump with
jump_speed (no hard jump) to the corrected
galvanometer scanner position.
– However, if load_correction_file
to loading a program file via
load_program_file, then the automatic call of
select_cor_table will have no effect
though load_program_file
tion table – as with select_cor_table(1,0) – it
won't trigger scanner motion to the corrected
position. Therefore, immediately after the
load_program_file command, the laser focus
will initially be centered in the image field (0|0)
– even if a correction table #1 had been
previously loaded via load_correction_file. The
desired image field correction becomes active
only after a subsequent select_cor_table,
select_cor_table_list, jump or marking com-
mand.
– If load_correction_file
load_program_file, then the call of
select_cor_table will execute with the default
parameter values (HeadA = 1, HeadB = 0) or – if
select_cor_table or select_cor_table_list
(1) load_program_file deletes correction tables number 3 and 4.
®
RTC 5 PC Interface Board
Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control
®
5 will transmit
"1to1
124).
load_program_file,
goto_xy,
only assigns a
is called prior
(1)
. And
assigns a correc-
is called after
was
called in the meantime – with the parameters
used there. If you require a different assign-
ment, then you must call
select_cor_table_list
priate parameter values. As of version DLL 527,
OUT 529, the command only returns to the
application, after the select_cor_table-induced
jump to the corrected galvanometer position
has completed.
®
• RTC 5 correction files differ from those of prior
®
RTC products (with the file extension .ctb) in
terms of size, structure and content. If ct5 and ctb
correction files have the same file name (except
for the different extensions), then they were
calculated for the same optical configuration. For
converting older correction files, see
Correction Files", page 125.
Notes on versions older than DLL 521, OUT 521:
• Here load_correction_file
select_cor_table. Here, the command
select_cor_table or select_cor_table_list
called directly after loading a correction table (or after a
subsequent load_program_file
that the current position, in accordance with the most
recently loaded correction table, will be attained
immediately via a smooth transition (with
) instead of via a hard jump initiated by
jump_speed
the subsequent jump or marking command. If you
don't explicitly call select_cor_table
select_cor_table_list, then some boards might also
output unexpected initialization-related galvanometer
scanner positions.
• With such older versions, select_cor_table
select_cor_table_list must also absolutely be called
after loading if load_correction_file
an already loaded and assigned 2D correction table by
a 3D correction table (or a 3D table by a 2D table or by
another 3D table). Otherwise the newly loaded
correction table will not be fully effective. The same
applies when the correction table is loaded after
load_program_file (though initialization assigns a
table as via
select_cor_table(1,0
trigger scanner motion to the corrected output
position). On the other hand, calling
or select_cor_table_list is not obligatory, if a 2D
correction table is replaced with another 2D correction
table. But even in this case,
select_cor_table_list should be called to avoid hard
jumps.
select_cor_table or
(again) using the appro-
"Converting
does not call
should be
command) to ensure
or
or
is used to replace
), it doesn't
select_cor_table
select_cor_table or
123