EasyManua.ls Logo

Scanlab RTC6 PCIe Board - Page 230

Scanlab RTC6 PCIe Board
1004 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
230
innovators for industry
x and 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 are
likewise alternatingly transferred to internal
memory locations 1 and 2.
The RTC6 identifies 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
transferring 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 by
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 by
apply_mcbsp (or apply_mcbsp_list) when two
values of the same data type exist in both
memory locations, then the most recently
transferred value is always 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 signed 32-bit 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 “Local 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 by McBSP signals:
When you use the commands for configuring
“Local Online Positioning“, then
Processing-on-the-fly correction activated by
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 gets automatically
deactivated. Subsequently, McBSP input values
are copied to internal memory locations 1 and
2 (see above) and are then available for
“Local Online Positioning“.
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 de
activate a
previously activated “Local Online Positioning“.
Subsequently, McBSP input values are then
transferred to the internal memory locations 0
to 3 depending on the command and are then
available for the Processing-on-the-fly
application.
If you switch off (intentionally or with an invalid
scaling factor) “Local Online Positioning“ by
set_mcbsp_x, set_mcbsp_y or
set_mcbsp_rot, then the data is continued to
be copied to internal memory locations 1 or 1
and 2 (as long as data is transmitted), but it is
no longer applied (apply_mcbsp has no
effect).

Table of Contents