Virtual Image Field With Processing-On-The-Fly; Synchronizing Processing-On-The-Fly Applications - Scanlab RTC6 PCIe Board Installation And Operation Manual

8.6.6 Virtual Image Field with
Processing-on-the-fly
With Processing-on-the-fly applications, the full value
range (29-bit) of the virtual
see Chapter 7.3.3 "Virtual Image Field", page 169
load and process command lists with objects that are
up to 512 times larger than the real 20-bit
Field.
With 1D Processing-on-the-fly applications (for
example, workpieces on a conveyor belt), objects can
only exceed the real Image Field
parallel to the Processing-on-the-fly direction.
With 2D Processing-on-the-fly applications (for
example, with an xy positioning stage), the to-be-
marked objects of a command list may be distributed
across the entire virtual Image
If an entire marking task consists of several partial
markings ("tiles") whose extent does not exceed the
real Image Field, the Processing-on-the-fly
functionality can also only be used to move the
partial marking to be marked into the real
and then process it there.
Coordinate values which are still outside the real
image after Processing-on-the-fly correction are
clipped to the boundary values of the real
Here, the get_marking_info
automatically, see Chapter 8.6.9 "Monitoring
Processing-on-the-fly Corrections", page
If there is a risk of the real 20-bit
exceeded during list execution, specifically a
forwarding motion of the conveyor belt or
xy positioning stage should be executed. The
forwarding motion can be waited for with
wait_for_encoder, wait_for_encoder_mode,
wait_for_encoder_in_range
interrupting the list execution until certain encoder
values or McBSP values are reached, see
Chapter 8.6.7 "Synchronizing Processing-on-the-fly
Applications", page 252.
The appropriate break up of the entire marking task
and synchronization with the 1D or
2D Processing-on-the-fly movement is the task of the
user program.
RTC6 boards
Doc. Rev. 1.0.21 en-US
8 Advanced Functions for Scan Head Control and Laser Control
Image Field can be used,
to
Image
in the very dimension
Field.
Image Field
Image Field
error bits get set
255.
Image Field being
or wait_for_mcbsp by
8.6.7 Synchronizing
Processing-on-the-fly
Applications
Processing of command lists can be started by either
a RTC6 command or an external start signal, see
Chapter 6.4.4 "Starting and Stopping Lists",
page 109.
If the command list is not to be started immediately
with the start signal, then an appropriate delay may
be implemented as follows:
• When transferring positions via the
McBSP interface – by a
beginning of the command list.
• When transferring positions via encoder counters
– by a set_fly_x/set_fly_y,
set_fly_rot (to reset the counter(s)) and a
wait_for_encoder_mode
subsequent
wait_for_encoder_in_range
the command list.
wait_for_encoder_in_range
2D encoder-based Processing-on-the-fly
wait_for_encoder_in_range
applications.
until both encoders are within the specified range
at the same time and thus does not depend on
the actual Trajectory that used to reach this
(1)
range
When transferring positions via encoder
counters, a track delay can be configured (even
independently of an active
Processing-on-the-fly Session) to delay the
execution of the actual start relative to the
triggering start signal or RTC6 command, see
Section "External Start", page
wait_for_encoder
(1) If you would use
wait_for_encoder_mode
call these commands individually and consecutively for
each encoder. Here, simultaneous fulfillment of both
encoder criteria would depend on the xy
stage
motion's explicit Trajectory
to define and reproduce an appropriate
before loading the lists.
wait_for_mcbsp at the
set_fly_2d or
or
at the beginning of
is useful for
waits
290.
or
instead, you would need to
positioning
and you would need
Trajectory even
252