RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
186
innovators for industry
8.7.5 Deactivating Processing-on-
the-fly Corrections
All Processing-on-the-fly corrections can be deacti-
vated (simultaneously for both directions) via the
command
, which also allows the new
output position to be defined.
Notes
• If Processing-on-the-fly correction is not explicitly
deactivated, then it will also be active during
execution of subsequent lists, but not in the
pause between two lists
(1)
.
• Processing-on-the-fly correction enabled via
,
,
will also get deactivated if the same command is
called again but this time with invalid parameter
values. This could lead to a jump to an
unintended output position (also refer to the
command descriptions).
• If Processing-on-the-fly was activated via
won’t
deactivate it and
vice versa. The same applies to
and
. Other than that, every Processing-
on-the-fly command automatically deactivates
any Processing-on-the-fly correction activated by
another Processing-on-the-fly command (also see
section "Overview" on page 178
). Here, a hard
jump to a new output position might occur.
• Processing-on-the-fly correction activated by
also gets
deactivated if you call
with
Mode
= 0. Here, a hard
jump to an uncorrected output position might
occur.
• Processing-on-the-fly correction activated via
also gets
deactivated if you call the command for config-
uring online positioning (see
hard jump to a new output position might occur.
• To avoid hard jumps, you should only use
to deactivate Processing-on-the-fly
correction.
• Processing-on-the-fly correction that was
activated via
should be
• When a command for deactivating Processing-
on-the-fly correction is called, then the deacti-
vation (as of version OUT 515) only occurs after
expiration of the scanner delay (hence the full
scanner delay will execute with Processing-on-
the-fly correction). In older versions, deactivation
would already occur before the scanner delay.
• If Processing-on-the-fly was activated via
, then the
command deactivates Processing-on-
the-fly correction, but it doesn’t deactivate
copying to internal memory locations (just like
with
set_mcbsp_in(5)
). To afterward also
deactivate copying to internal memory locations,
you can use
set_mcbsp_in(0)
or
set_mcbsp_in_list(0)
.
• Processing-on-the-fly correction will also get
deactivated (for both spacial directions simulta-
neously) via
stop.
(1)
does not deactivate Processing-on-the-fly
correction. On the other hand, the correction does not affect
the control commands
.