RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
258
Notes on Usage
• For general information on Processing-on-the-fly
correction and determining scaling factors, see
Chapter 8.6 ”Processing-on-the-fly”, page 242.
• When activating “FlyZ correction” by set_fly_z,
you can specify which of the two encoder
counters should be used. Because set_fly_x
already uses encoder counter “Encoder0” and
set_fly_y uses encoder counter “Encoder1”
(set_fly_rot uses “Encoder0”), you might need to
use one of the two encoders twice.
• “FlyZ correction” can be applied together with
set_fly_x/set_fly_y/set_fly_rot.
• “FlyZ correction” can be also be used alone (only
encoder-based z variation).
• Activated “FlyZ correction” can be deactivated by
fly_return_z or fly_return. As a result, all
Processing-on-the-fly corrections for all three
spatial directions are simultaneously deactivated.
You can supply a command parameter for a new
output position (only the x and y coordinates for
fly_return, in addition the z coordinate for
fly_return_z).
• Activated “FlyZ correction” can also be
deactivated by set_fly_z in conjunction with an
invalid parameter (for example,
set_fly_z( ScaleZ=0 )
).
– If only z correction has been activated here,
then a jump to an uncorrected output position
might occur.
– If Processing-on-the-fly corrections were also
activated for other spatial directions (by
set_fly_x/set_fly_y/set_fly_rot), then these do
not get deactivated here (and no jump to an
uncorrected output position occurs).
• If correction for all three spatial directions is
activated by set_fly_x, set_fly_y and set_fly_z,
then a subsequent
set_fly_x( ScaleX=0 )
only
deactivates X correction without affecting Y and
Z correction (likewise for
set_fly_y(ScaleY=0)
).
But if only z correction (by set_fly_z) or
2D correction (by set_fly_z and set_fly_x or
set_fly_y) is activated, then a subsequent
set_fly_x, set_fly_y or set_fly_rot with invalid
parameter value (for example,
set_fly_x( ScaleX=0
)
) also deactivates
z c
orrection. In the latter case, a jump to a
(partially) uncorrected output position might
occur.
• set_fly_z deactivates a Processing-on-the-fly
correction with positional values via McBSP.
• Conversely, Processing-on-the-fly correction
activated by set_fly_z gets deactivated by such a
correction. Here, a “Hard Jump” to a new output
position might occur.
• To avoid “Hard Jumps”, use only fly_return_z to
deactivate Processing-on-the-fly correction.
• get_marking_info also provides information on
possible range exceedances during “FlyZ
correction” (Bit #22…Bit #25).
• set_fly_limits_z, if_fly_z_overflow and
if_not_fly_z_overflow are available for defining
a customer-specific monitoring range for “FlyZ
correction” and for corresponding conditional
command execution, see Chapter 9.3.2
”Conditional Command Execution”, page 295.
You can use clear_fly_overflow and
clear_fly_overflow_ctrl to reset the error bits
(Bit #24…Bit #25 from get_marking_info) for
customer-specific monitoring of FlyZ
applications.
• A 3D Processing-on-the-fly correction with
positional values via McBSP can be activated by
set_multi_mcbsp_in and
set_multi_mcbsp_in_list.
To Next Page
Loading...