Scanlab RTC6 PCIe Board - Notes on How to Use Fly Extension Commands

RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
260
innovators for industry
Notes on How to Use
“Fly Extension” Commands
• set_fly_1_axis( Axis, Mode, Scale ) replaces
one of the “Classic“
Processing-on-the-fly commands:
– set_fly_x
– set_fly_y
– set_fly_z
– set_fly_rot
– set_fly_x_pos
– set_fly_y_pos
– set_fly_rot_pos
• set_fly_2_axes combines the activation of any 2
linear axes and replaces for example, even
set_fly_2d.
• fly_return_1_axis, fly_return_2_axes and
fly_return_3_axes extend the functionality of the
“Classic“ Processing-on-the-fly commands
fly_return and fly_return_z.
• activate_fly_2_axes replaces the “Classic“
Processing-on-the-fly commands
– activate_fly_2d
– activate_fly_2d_encoder
– activate_fly_xy
– activate_fly_xy_encoder
• wait_for_1_axis can “wait” for any encoder
value or a value transmitted by McBSP, thus
substituting wait_
for_encoder_mode and
wait_for_mcbsp.
• wait_for_2_axes stands for
wait_for_encoder_in_range and
wait_for_encoder_in_range_mode and are able
to wait for McBSP values in addition.
• The laser control (switch off the laser or leave it
unchanged) can be set individually at
wait_for_1_axis (wait_for_2_axes) with
parameter LaserMode ( LaserMode ).
• The galvanometer scanner movement (stand still
ore move along) can be specified with
wait_for_1_axis (wait_for_2_axes) by
parameter WaitMode ( WaitMode ). Thus, it is no
longer bound to set_fly_2d and
set_fly_x/set_fly_y.
• “Fly Extension” Commands are also compatible
with McBSP transmissions from set_mcbsp_in
and set_multi_mcbsp_in. The
Processing-on-the-fly corrections can be
subsequently overwritten, for example, by
Encoder-based corrections. However, the
McBSP transmission to the memory locations
themselves cannot be changed.
• “Fly Extension” Commands are – like “Classic“
Processing-on-the-fly commands
(1)
– not
compatible with an Online Positioning.
• “Fly Extension” Commands are able to “wait” for
McBSP values, see Table 4.
• Modes and Encoders supported with
“Fly Extension” Commands are shown in Table 4.
(1) See Footnote on page 259.