Scanlab RTC6 PCIe Board - Page 226

RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
226
innovators for industry
• Before the total transformation is applied to the
current position, the Signals for “Laser Active”
Operation are switched off with at_once = 0…2.
They remain unchanged with at_once = 3.
• With at_once = 1 or 3, all settings (only)
accumulated until then are processed
immediately and simultaneously. In the process,
the scan system axes are moved from the current
position to the corrected position at the defined
jump speed. Consequently, this can require some
clock cycles.
This needs to be observed especially when
RTC6 PCIe Boards are master/slave synchronized
and are supposed to execute different
jump lengths. With this use case, the coordinate
transformations should be executed prior the
synchronized start with at_once = 1 and their end
should be waited for.
Any Scanner Delays are not initialized. The
INTERNAL-BUSY list execution status is set while
the jump to the corrected position is executed.
• With at_once = 2, the accumulated settings only
become effective upon execution of the next
jump_abs, jump_rel, goto_xy or goto_xyz (but
not other Jump Commands such as
jump_abs_3d or jump_rel_3d) unless afterwards
another call triggers immediate execution.
Correction of the current output position then
occurs together with the specified coordinate
jump. This eliminates unnecessary
galvanometer scanner motions (incl. delays).
Example: The following command sequence
produces a first jump to (0, 0), followed by – if
at_once = 1 or at_once = 3 – a second jump from
(0, 0) to (1000, 500) and a third from (1000, 500)
to (0, 500). But if at_once = 2, then only a second
jump occurs from (0, 0) to (0, 500).
jump_abs( 0, 0 );
set_offset_list( 1000, 500, at_once );
jump_abs( -1000, 0 );
Notes on data recording:
– The galvanometer scanner movement of
jump_abs or jump_rel at the beginning of the
list can be recorded with set_trigger (signal
type 7, 8, 9), if no coordinate transformation
with at_once = 2 has been applied before.
– In case of movements after a coordinate
transformation (for example, by set_offset_list
with at_once = 2) the “sample values”
(set_trigger signal type 7, 8, 9) are immediately
set to the target coordinates and remain
unchanged for the duration of the movement.
The movement recorded here does not appear
like Microstepping
(1)
has been performed, but
rather like a Hard Jump. The real
galvanometer scanner movement can be
recorded with set_trigger, signal type 25 and
26 (transformed control values).
– In case of movements caused by coordinate
transformation in a list (for example, by
set_offset_list with at_once = 1), the “sample
values” (set_trigger signal type 7, 8, 9) remain
unchanged for the duration of the movement.
The real galvanometer scanner movement can
be recorded with set_trigger, signal type 25
and 26 (transformed control values).
• Settings via control commands by at_once = 0
are only saved as long as no list is running.
When the execution is started or the list is already
running, the settings take effect immediately
before the next list command.
Settings via list commands with at_once = 0 are
only saved until they are retrieved elsewhere
( at_once > 0 or by a control command).
• If no correction table
is assigned to the
corr
esponding scan head connector, then the
new settings for the coordinate transformations
are only stored on the RTC6 PCIe Board. They take
effect when a correction table is assigned.
(1) See Chapter 7.1.2 ”Microstepping”, page 140.