RTC
®
5 PC Interface Board
Rev. 1.9 e
7 Basic Functions for Scan Head and Laser Control
123
innovators for industry
Notes
• If no correction table has been loaded into the
RTC
®
5’s memory, then the RTC
®
5 will transmit
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 files should be loaded at the begin-
ning of an application program, before or after
loading the program file (via
(1)
. They should absolutely be loaded
and assigned prior to first-time starting of a list or
issuance of a control command (e.g.
) 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
only assigns a
correction table to the primary scan head), then
the other scan head connector will transmit no
signals.
• As of version DLL 521, OUT 521,
automatically calls
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
is called prior
to loading a program file via
, then the automatic call of
. And
though
assigns a correc-
tion table – as with
select_cor_table(1,0)
– it
won’t trigger scanner motion to the corrected
position. Therefore, immediately after the
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
desired image field correction becomes active
only after a subsequent
,
, jump or marking com-
mand.
– If
is called
after
, then the call of
parameter values (
HeadA
= 1,
HeadB
= 0) or – if
was
called in the meantime – with the parameters
used there. If you require a different assign-
ment, then you must call
or
(again) using the appro-
priate parameter values. As of version DLL 527,
OUT 529, the command only returns to the
application, after the
-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
Notes on versions older than DLL 521, OUT 521:
• Here
does not call
. Here, the command
should be
called directly after loading a correction table (or after a
subsequent
command) to ensure
that the current position, in accordance with the most
recently loaded correction table, will be attained
immediately via a smooth transition (with
jump_speed
) instead of via a hard jump initiated by
the subsequent jump or marking command. If you
don’t explicitly call
or
, then some boards might also
output unexpected initialization-related galvanometer
scanner positions.
• With such older versions,
or
must also absolutely be called
after loading if
is used to replace
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
(though initialization assigns a
table as via
select_cor_table(1,0
), it doesn’t
trigger scanner motion to the corrected output
position). On the other hand, calling
or
is not obligatory, if a 2D
correction table is replaced with another 2D correction
table. But even in this case,
or
should be called to avoid hard
jumps.
(1)
deletes correction tables number 3 and 4.
