RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
186
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 fly_return, 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
set_fly_x, set_fly_y, set_fly_2d, set_fly_rot,
set_fly_x_pos, set_fly_y_pos or set_fly_rot_pos
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
set_fly_x, then set_fly_y won’t deactivate it and
vice versa. The same applies to set_fly_x_pos and
set_fly_y_pos. 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
set_mcbsp_in or set_mcbsp_in_list also gets
deactivated if you call set_mcbsp_in or
set_mcbsp_in_list with
Mode
= 0. Here, a hard
jump to an uncorrected output position might
occur.
• Processing-on-the-fly correction activated via
set_fly_x_pos, set_fly_y_pos, set_fly_rot_pos,
set_mcbsp_in or set_mcbsp_in_list also gets
deactivated if you call the command for config-
uring online positioning (see page 166). Here, a
hard jump to a new output position might occur.
• To avoid hard jumps, you should only use
fly_return to deactivate Processing-on-the-fly
correction.
• Processing-on-the-fly correction that was
activated via set_multi_mcbsp_in should be
terminated via fly_return_z.
• 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
set_mcbsp_in or set_mcbsp_in_list, then the
fly_return 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_execution or an external list
stop.
(1) set_end_of_list does not deactivate Processing-on-the-fly
correction. On the other hand, the correction does not affect
the control commands goto_xy and goto_xyz.
To Next Page
Loading...