RTC6 boards
Doc. Rev. 1.0.21 en-US
10 RTC6 Commands
642
Normal List
Command
set_fly_2_axes
Function “Fly Extension” Command: Activates a 2-Axes-Processing-on-the-fly application.
Restriction If the Option Processing-on-the-fly is not enabled, then set_fly_2_axes terminates the
Processing-on-the-fly process (even though it could not have been activated).
Call
set_fly_2_axes( Axis1, Mode1, Scale1, Axis2, Mode2, Scale2 )
Parameters
Axis1
Axis from Table 3, page 259.
Allowed values:
1
…
3
(linear axis only).
As an unsigned 32-bit value.
Mode1
Mode from Table 4, page 261.
As an unsigned 32-bit value.
Scale1
Scaling factor.
As a 64-bit IEEE floating point value.
Allowed value range:
• 1/256 |
Scale1
| 16.000,0 with linear axis (
1
,
2
or
3
)
Scale1
can be + or –. Only the absolute value is restricted.
Scale1
is ignored for
Mode1
= ( 8/12/16 ).
Axis2
Like
Axis1
.
Mode2
Like
Mode1
.
Scale2
Like
Scale1
.
Comments • Being an “Fly Extension” Command, set_fly_2_axes must not be used mixed with
“Classic“ Processing-on-the-fly commands (see Footnote, page 242).
• See Chapter 8.6 ”Processing-on-the-fly”, page 242 and Section
”“Fly Extension” Commands”, page 259.
• With
Mode
( 1…4 ), set_fly_2_axes requires two 10 µs clock cycles for execution.
• set_fly_2_axes overwrites a previous definition for the same Axes (even individually).
As 2 linear axes, set_fly_2_axes can be combined with a third linear axis, but not with
a Rotary axis. Any still-active rotation-fly application (
set_fly_1_axis( Axis =4
)) is
automatically deactivated and vice versa. It is recommended to explicitly switch off
incompatible Processing-on-the-fly corrections beforehand, for example, see
fly_return_2_axes.
•
Axis1
and
Axis2
need to be different linear axes and must not be rotary axes.
•
Mode1
and
Mode2
can be the same. If they use the same Encoder, a different
scaling factor can be specified by
Mode1
/
Mode2
= 1 / 3 or 2 / 4.
• With an unallowed parameter value, set_fly_2_axes is replaced by a list_nop
(
get_last_error ret
urn code
RTC6_PARAM_ERROR
).