RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
432
Normal
List Command
set_fly_y_pos
Function activates Processing-on-the-fly correction for compensation of a linear workpiece or scan
system movement in the Y direction (based on position values transferred to the RTC
®
5 via
the McBSP interface); thereby sets the corresponding scaling factor.
Restriction If the Processing-on-the-fly option is not enabled, then the command terminates the
Processing-on-the-fly process (even though it couldn’t have been activated).
Call
set_fly_y_pos( ScaleY )
Parameter
Scale
scaling factor for the Y direction in (RTC
®
5)bits/(McBSP)bit
(as a 64-bit IEEE floating point value);
allowed range: 1/256 |
ScaleY
| 16000.0
Comments • For Processing-on-the-fly correction and determination of the scaling factor, see
"Processing-on-the-fly (Optional)", page 177.
• If unallowed parameter values are supplied (e.g. for
ScaleY
= 0), then set_fly_y_pos
will not activate a Processing-on-the-fly correction or will deactivate a Processing-on-
the-fly correction previously activated via set_fly_y_pos (but will not deactivate any
other Processing-on-the-fly correction). The latter case leads to a jump (at jump speed)
to the endpoint of the most recently executed vector or arc command (without
“set_fly_y_pos“ Processing-on-the-fly correction).
• The various Processing-on-the-fly corrections can’t be arbitrarily combined (see the
page 178).
• For deactivating Processing-on-the-fly correction, see page 186.
• For one-dimensional correction (when only set_fly_y_pos is used), the McBSP interface
provides a (signed) 32-bit value. In contrast, only a (signed) 16-bit value per axis is
supplied for two-dimensional correction (set_fly_x_pos and set_fly_y_pos). Here,
set_fly_x_pos uses the McBSP interface’s lower 16 bits for the X value and
set_fly_y_pos uses its upper 16-bits for the Y value.
• The McBSP interface can’t be simultaneously used for both Processing-on-the-fly appli-
cations and online positioning (see page 166).
• The McBSP interface always ignores the first FrameSync signal after a
load_program_file or mcbsp_init, so available data will not be transmitted (see
page 53).
RTC
®
4
RTC
®
5 new command
In RTC
®
4 compatibility mode, the RTC
®
5 multiplies the specified scaling factor by 16 (the
permissible range of values is correspondingly reduced).
Version info Last change with version OUT 515
References fly_return, set_fly_x_pos, read_mcbsp, set_fly_x, set_fly_y
To Next Page
Loading...
