RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
567
Variable
List Command
park_return
Function Moves the output point (of the laser focus) away from a park position along a 2D vector
at jump speed to the specified position (absolute coordinate values) within the 2D Image
Field.
Restriction If the Option Processing-on-the-fly is not enabled, then park_return functions as a normal
Jump Command. If the laser focus is not currently in a park position, then park_return is
a short list command with no effect (see below).
Call
park_return( Mode, X, Y )
Parameters
Mode
As an unsigned 32-bit value.
= 0:
X
and
Y
are ignored (see comments).
> 0:
X
and
Y
are interpreted as return jump coordinates (see comments).
X
Absolute x coordinate of the jump vector end point in the virtual Image Field.
In bits.
As a signed 32-bit value.
Allowed value range: [–268,435,456…+268,435,455].
Out-of-range values are clipped to the boundary values.
Y
Like
X
(analogously).
Comments • park_return is intended for encoder-based set_fly_2d or set_fly_x/set_fly_y
Processing-on-the-fly applications where the laser focus should leave a safe parking
area previously reached by park_position after an intermediate forwarding motion
(following list interruption by wait_for_encoder etc.), see Chapter 8.6.7
”Synchronizing Processing-on-the-fly Applications”, page 252. See also comments at
park_position.
• If a set_fly_2d or set_fly_x/set_fly_y Processing-on-the-fly mode has been switched
off by a prior park_position(
Mode =
0 ) call, then park_return switches the same
Processing-on-the-fly mode back on. Other Processing-on-the-fly modes are not
switched back on.
• If the park position has been attained by park_position, then park_return(
Mode =
0 )
returns the galvanometer scanners to the most recent valid position before
park_position has been called, whereas park
_return(
Mode =
1 ) m
oves them to the
position specified with the command. When calculating the new position, the RTC6
takes the current Processing-on-the-fly correction into account. But if clipping to the
boundaries of the virtual Image Field occurs (for example, due to a too long forwarding
motion during a list interruption by wait_for_encoder), then the Processing-on-the-fly
mode is not reactivated (see also activate_fly_2d and activate_fly_xy) and the jump
executes without Processing-on-the-fly correction.
To Next Page
Loading...