RTC
®
5 PC Interface Board
Rev. 1.9 e
10 Commands And Functions
452
innovators for industry
Ctrl Command set_mcbsp_in
Function
activates Processing-on-the-fly correction for compensation of a workpiece or scan system
movement (based on position values transferred to the RTC
®
5 via the McBSP interface);
the McBSP interface can also be used for inputting other desired signals.
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_mcbsp_in( Mode, Scale )
Parameters
Mode
an unsigned 32-bit value, allowed values:
= 0:
Processing-on-the-fly correction will be switched off
= 1:
compensation of linear movement in the X direction
= 2:
compensation of linear movement in the Y direction
= 3:
compensation of linear movement in the X and Y directions
= 4:
compensation of rotary movement
= 5:
Processing-on-the-fly correction will be switched off
•
Mode
= 0 … 5: All McBSP input values will be alternatingly copied to
internal memory locations 1 and 2.
•
Mode
= 1 … 5 (but not for
Mode
= 0): McBSP input values coded with
“Bit#31 = 0” will additionally be copied to internal memory location 0 and
those with “Bit#31 = 1” to internal memory location 3.
•
Mode
= 1 … 4: Values copied to internal memory location 0 will be applied
for Processing-on-the-fly correction.
Scale
scaling factor or rotation resolution as a 64-bit IEEE floating point value:
•
Mode
= 1 … 3: scaling factor in
(RTC
®
5)bits/(McBSP)bit;
allowed range: 1/256
|
Scale
|
16000.0
(if
Mode
= 3,
Scale
applies to both axes)
•
Mode
= 4: number of steps (counts) per revolution;
allowed range: |
Scale
| > 100.0
Comments
• You can query the internal memory locations at any time via
.
• For Processing-on-the-fly correction and determination of the scaling factor, see
"Processing-on-the-fly (Optional)", page 177
.
• The various Processing-on-the-fly corrections can’t be arbitrarily combined (see the
• For deactivating Processing-on-the-fly correction, see
• 15 bits per axis (with sign) are effectively available for two-dimensional correction
(
Mode
= 3), whereby the X value is in the lower 16 bits of the “bit#31 = 0”-coded
McBSP input value and the Y value in the upper 16 bits.
• The McBSP interface can’t be simultaneously used for both Processing-on-the-fly appli-
cations and online positioning (see
).
• The McBSP interface always ignores the first FrameSync signal after a
, so available data will not be transmitted (see
• If
Mode
> 5,
set_mcbsp_in
is
not
executed (
return code:
RTC5_PARAM_ERROR
).
• If an unallowed
Scale
parameter value is supplied (e.g.
Scale
= 0),
set_mcbsp_in
behaves as with
Mode
= 0.
RTC
®
4
RTC
®
5 new command
Version info
Available beginning with version DLL 531, OUT 532