RTC
®
5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
166
transferred to internal memory locations 1 and 2.
The RTC
®
5 will identify the data type by
examining the coding bit #31 (bit #31 = 0 for
offset values, bit #31 = 1 for rotation correction
values).
Signed 31 bits are effectively available for trans-
ferring offset values. 31 bits without sign are
available for rotation correction values.
• x, y and rot
If you activate all three options together, then the
two offset correction values must be combined
and supplied as one 32-bit value alternatingly
supplied with the rotation correction value as a
second 32-bit value. The McBSP input values will
likewise be alternatingly transferred to internal
memory locations 1 and 2.
The RTC
®
5 will identify the data type by
examining the coding bit #31 (Bit #31 = 0 for
offset values, Bit #31 = 1 for rotation correction
values).
Signed 15 bits are effectively available for trans-
ferring offset values (whereby X values reside in
the lower 16 bits and Y values in the upper
16 bits). 31 bits without sign are available for
rotation correction values.
• The last two cases designate the data type via
coding bit #31. Though this makes the order of
transmission irrelevant, always both data types
nevertheless must be transmitted (preferably
always alternatingly). If a request is made via
apply_mcbsp (or apply_mcbsp_list) when two
values of the same data type exist in both
memory locations, then the most recently trans-
ferred value will always be used. If two identical
Bit #31 codings are present, then the last transfer
should have already ended at the time of the
request.
• matrix
With this option activated, matrix coefficients are
then transferable as 32-bit signed values. The
indices are encoded in the data word (see
command description). McBSP input values get
transferred to internal memory location 1.
Notes
• You can use online positioning in conjunction
with an encoder-controlled Processing-on-the-fly
application, but not in conjunction with a
Processing-on-the-fly application controlled via
McBSP signals:
– When you use the commands for configuring
online positioning, then Processing-on-the-fly
correction activated via set_fly_x_pos,
set_fly_y_pos, set_fly_rot_pos,
set_mcbsp_in, set_mcbsp_in_list,
set_multi_mcbsp_in or
set_multi_mcbsp_in_list will get automati-
cally deactivated. Subsequently, McBSP input
values will be copied to internal memory loca-
tions 1 and possibly 2 (see above) and are then
available for online positioning, but no longer
for a Processing-on-the-fly application.
– In reverse, set_fly_x_pos, set_fly_y_pos,
set_fly_rot_pos, set_mcbsp_in,
set_mcbsp_in_list, set_multi_mcbsp_in or
set_multi_mcbsp_in_list will deactivate a pre-
viously activated online positioning. Subse-
quently, McBSP input values will then be copied
possibly instead of or additionally to the inter-
nal memory location 0 and/or 3 and are then
available for the Processing-on-the-fly applica-
tion, but no longer for online positioning.
– If you switch off online positioning via
set_mcbsp_x, set_mcbsp_y or
set_mcbsp_rot, then the data will continue to
be copied to internal memory locations 1 or 1
and 2 (as long as data is transmitted), but it will
no longer be applied (apply_mcbsp has no
effect).
To Next Page
Loading...
