RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
838
Normal List
Command
wait_for_1_axis
Function “Fly Extension” Command: Waits until the value for the specified Mode has been exceeded
or underrun.
Call
wait_for_1_axis( Value, Mode, WaitMode, LaserMode )
Parameters
Value
Value to be waited for.
As a signed 32-bit value.
Mode
Mode from Table 4, page 261.
As an unsigned 32-bit value.
WaitMode
< 0: Undercutting.
= 0: Equal.
> 0: Overrun.
The galvanometer scanner follow the object movement.
WaitMode
+16: The galvanometer scanner stop.
As a signed 32-bit value.
LaserMode
= 0: The laser remains unchanged.
> 0: The laser is switched off after a LaserOff Delay.
As an unsigned 32-bit value.
Comments • Being an “Fly Extension” Command, wait_for_1_axis must not be used mixed with
“Classic“ Processing-on-the-fly commands (see Footnote, page 242).
• See Chapter 8.6 ”Processing-on-the-fly”, page 242 and Section
”“Fly Extension” Commands”, page 259.
• Depending on the set Mode, it can be waited for an encoder value or (any) McBSP
value. In case of McBSP, a corresponding Processing-on-the-fly correction should be
enabled. Make sure that the data is transferred in the correct format.
• With
wait_for_1_axis
and
wait_for_2_axes
, Mode 1…4 must not be specified. Instead,
Mode 17…20 is to be used. Mode 17…18 is to be used with an scan system with
SCANahead control, if waiting is yet to occur within
PreviewTime
. Outside of this, Mode
19…20 can be used. Mode 17…18 and Mode 19…20 are identical with
intelliSCAN systems.
•
LaserMode
= 0: like before.
•
LaserMode
> 0: Laser is switched off after a LaserOff Delay.
•
WaitMode
is like
Mode
of wait_for_encoder_mode.
•
WaitMode
and
WaitMode
+16 differentiate the galvanometer scanner movement, not
set_fly_2d and set_fly_x/set_fly_y.
• wait_for_encoder with automatic positions-dependent selection of direction is not
supported.
• With an unallowed parameter value, wait_for_1_axis is replaced by a list_nop
(get_last_error return code
RTC6_PARAM_ERROR
).
To Next Page
Loading...