EasyManua.ls Logo

Scanlab RTC 5 PC Interface Board - 8.7.8 Encoder Resets

Scanlab RTC 5 PC Interface Board
622 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
189
innovators for industry
tation via a wait_for_encoder_in_range
command, then the galvanometer scanners will
already be at the correct location after the inter-
mediate motion (here, no jump is required after
the interruption).
With set_fly_2d, clipping might occur if the
Processing-on-the-fly-corrected coordinate values
exceed the real image field during a long interme-
diate motion. To avoid this, it might make sense
to switch off Processing-on-the-fly correction
before the motion (e.g. via fly_return – see
chapter 8.7.5, page 186; the galvanometer
scanners will then remain stationary). To switch
correction back on after the intermediate motion,
you can use the command activate_fly_2d
instead of set_fly_2d (or activate_fly_xy instead
of set_fly_x and set_fly_y). These commands
don’t reset the encoders, but instead recalculate
the last Processing-on-the-fly-uncorrected coordi-
nate values so that the Processing-on-the-fly-
corrected output matches the current output. If
resuming correction via these commands results
in an error (e.g. because the current recalculated
coordinate values would now exceed the 24-bit
virtual image field), then an error bit will get set
that is queryable via get_marking_info (bit # 9
= 1). If, during list processing, it’s necessary to
immediately respond to this error, then you can
call the list command if_not_activated to
possibly jump to an error-handling routine.
8.7.8 Encoder Resets
Many encoder-based Processing-on-the-fly applica-
tions (e.g. a conveyor belt continuously traveling in
the same direction) need to occasionally reset the
encoders (e.g. after an interruption via
wait_for_encoder, before a new marking sequence
etc.). For this, you can integrate Processing-on-the-fly
reactivations into your lists via set_fly_x, set_fly_y,
set_fly_rot or set_fly_2d.
In contrary, encoder-based Processing-on-the-fly
applications for continuous marking (e.g. using an XY
stage) should usually retain the relation between
encoder values and absolute positions of the XY
translation stage. For this purpose, you should use
the set_fly_2d command to activate Processing-on-
the-fly correction. Before a long interruption (via
wait_for_encoder etc.), you can then deactivate
Processing-on-the-fly correction with fly_return. And
after the interruption you could use the command
activate_fly_2d to resume correction (also see
chapter 8.7.4 "Compensation of 2D Motions",
page 184 and chapter 8.7.7 "Synchronization of
Processing-on-the-fly Applications", page 188).
Processing-on-the-fly correction can also be resumed
with activate_fly_xy, but some functions will no
longer be available, particularly those necessary for
the relation between current encoder values and
absolute XY stage positions (see the section "2D
Encoder Compensation for XY Stages" on page 184).

Table of Contents

Related product manuals