Correction Via Mcbsp Interface With Additional Mcbsp Input; Correction Via Mcbsp Interface With Enhanced Mcbsp Input; Compensation Of Rotary Movements; Correction Via Encoder Counter - Scanlab RTC 5 PC Interface Board Installation And Operation Manual

Correction via McBSP Interface with
Additional McBSP Input
To activate Processing-on-the-fly correction for linear
motions using McBSP input values (as an alternative
to set_fly_x_pos or set_fly_y_pos), you can also call
set_mcbsp_in or set_mcbsp_in_list
These commands offer the advantage of using the
McBSP interface to input additional desired signals
that shouldn't be subjected to Processing-on-the-fly
correction even when it is activated. For this, all
McBSP input values must be coded via bit#31.
• Bit#31 = 0: The input value gets copied to
internal memory location 0 and is applied for
Processing-on-the-fly correction.
• Bit#31 = 1: The input value gets copied to
internal memory location 3 but is not applied for
Processing-on-the-fly correction.
Notes
• All input values always get copied alternatingly to
internal memory locations 1 and 2 and subse-
quently, in accordance with their bit#31 coding,
to internal memory locations 0 and 3. But after
deactivation of correction via set_mcbsp_in(0) or
set_mcbsp_in_list(0), they only get copied to
memory locations 1 and 2.
• You can query the data currently stored at
internal memory locations 0 - 3 via read_mcbsp.
• You can specify a scaling factor via
or set_mcbsp_in_list (as with
set_fly_y_pos). For two-dimensional correction,
the scaling factor applies to both axes simulta-
neously. Calibration for determining the scaling
factor is the same as for
set_fly_y_pos (see above).
• For transferring one-dimensional correction
values, 31 bits with sign are available (bit#31 is
reserved as the coding bit). In contrast, only 15
bits with sign are available per axis for trans-
ferring two-dimensional correction values,
whereby the X value lies in the lower 16 bits and
the Y value in the upper 16 bits of the value at the
McBSP interface. For a description of the
interface, see page 52.
®
RTC 5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
(Mode = 1...3).
set_mcbsp_in
set_fly_x_pos and
set_fly_x_pos and
Correction via McBSP Interface with
Enhanced McBSP Input
As an alternative to the previous chapter's methods,
you can also activate Processing-on-the-fly correction
of linear motion with set_multi_mcbsp_in
set_multi_mcbsp_in_list.
These commands have an advantage over
set_mcbsp_in or set_mcbsp_in_list
offer Processing-on-the-fly correction not only in the
X and Y directions, but also in the Z direction and
with laser power variation. Furthermore, up to four
additional signals can be transmitted for usage as
you wish.
Each 10 µs, data asynchronously transmitted to
McBSP memory locations 0 through 3 gets sorted and
copied to an additional internal memory location.
From there it is available for final usage and can be
read-out using read_multi_mcbsp.
8.7.3 Compensation of Rotary
Movements
Before activating Processing-on-the-fly correction for
rotary XY movement, you must define the rotation
center via set_rot_center or set_rot_center_list. The
rotation center may also be situated outside the
image field. The Processing-on-the-fly correction
itself can be activated via the list command
set_fly_rot or alternatively via
set_mcbsp_in or set_mcbsp_in_list
Processing-on-the-fly correction can be stopped via
the command fly_return (see the corresponding
notes on page 186).
Notes
• You can't combine Processing-on-the-fly rotation
correction with other Processing-on-the-fly
corrections (see section "Overview" on page
• Simultaneous Processing-on-the-fly rotation
correction for both scan head connectors is only
practical if both attached scan heads are aligned
to exactly the same rotation center.

Correction via Encoder Counter

If an incremental encoder is used to detect the
angular position of the parts to be processed, the
encoder must be connected to the ENCODER X input
(also see page 215).
or
in that they
set_fly_rot_pos or via
(Mode = 4).
178).
181