Monitoring Processing-On-The-Fly Corrections; Customer-Defined Monitoring Area And Conditional Command Execution (As Of Version Dll 525, Out 527) - Scanlab RTC 5 PC Interface Board Installation And Operation Manual

8.7.9 Monitoring Processing-on-the-
fly Corrections
If a Processing-on-the-fly application program is not
optimized for the motion of the workpiece or scan
system or if considerable unintended change of
workpiece or scan system speed occurs during a
Processing-on-the-fly operation, then the image
field's boundaries might be reached. Because the
RTC®5 clips coordinate values at the boundaries to
prevent unallowable values, this could cause some
parts of the to-be-marked pattern to not be scanned.
To allow user programs to monitor Processing-on-
the-fly applications, the RTC
(#0...3) if the image field boundaries are exceeded
(and coordinate values get clipped). You can query
these internal error bits via get_marking_info.
To avoid boundary exceedance, you should
repeatedly call get_marking_info
normal operation of your Processing-on-the-fly appli-
cation and modify your user program accordingly.
Notes
• Error bits #0...3 can also be used for determining
which edge of the image field was exceeded.
Each boundary exceedance results in setting of
the corresponding error bit.
• Error bits #0...3 are reset during initialization (via
load_program_file) and by the command
get_marking_info. get_marking_info
returns information about errors that occurred
since the last initialization or the last call of
get_marking_info.
®
• The RTC 5 sets an error bit if boundary
exceedance is detected when calculating the
output value from the specified coordinate values
following application of Processing-on-the-fly
correction. Any coordinate transformations,
image field corrections and compensating gain
and offset corrections applied during calculation
of output values after Processing-on-the-fly
correction (see page 126) will not be taken into
account here. During the adjustment phase of a
®
RTC 5 PC Interface Board
Rev. 1.9 e
8 Advanced Functions for Scan Head and Laser Control
®
5 sets internal error bits
during test runs or
therefore
Processing-on-the-fly correction, you must
therefore always ensure that coordinate points
approaching the image field boundaries will be
checked for applicable limits.
• Error bit #9 indicates if the 24-bit virtual image
field range was exceeded during resumption of
Processing-on-the-fly correction via
activate_fly_2d or activate_fly_xy
chapter 8.7.7, page 188).
Customer-Defined Monitoring Area and
Conditional Command Execution (as of
Version DLL 525, OUT 527)
For Processing-on-the-fly applications, the RTC
also checks for exceedance of a second value range
whose boundaries can be specified via set_fly_limits.
Such exceedances likewise result in setting internal
error bits that can be queried via
(error bits#4...7).
Moreover, the conditional commands
if_fly_x_overflow, if_fly_y_overflow,
if_not_fly_x_overflow or if_not_fly_y_overflow
allow execution of any list command to be made
dependent upon whether boundary exceedance in a
customer-defined monitoring area occurred or not.
The conditional commands have no effect if the
condition (on error bits#4...7) specified as a
command parameter is fulfilled (or not fulfilled).
Otherwise, they result in skipping the next list
command.
Notes
• Boundary exceedance of a customer-defined
monitoring area doesn't necessarily result in
clipping of the output coordinate values. Clipping
(and setting error bits #0...3) only occurs if the
maximum image field (–524288 ... 524287 bit)
would be exceeded (the customer-defined
monitoring area is typically smaller).
• Error bits #4...7 are reset during initialization (via
load_program_file), but not by the command
get_marking_info. Individual error bits will, if
applicable, get implicitly reset by the conditional
commands and can also be explicitly reset via the
command clear_fly_overflow
description).
• Error bits #4...7 (as do error bits #0...3) take into
account neither coordinate transformations,
image field corrections, compensating gain nor
offset corrections.
(see
®
5
get_marking_info
(see command
190