Detailed description
2.1 Axes
Basic logic functions: Axes, coordinate systems, frames (K2)
32 Function Manual, 11/2006, 6FC5397-0BP10-2BA0
Note
The gaps count as axes with reference to the number of channel axes and their indices.
If the following machine data is used to try to define a channel axis gap with the geo axis,
then the attempt is rejected without an alarm:
MD20050 $MC_AXCONF_GEOAX_ASIGN_TAB (assignment of geometry axis to channel
axis)
Using channel axes in
MD24120ff. $MC_TRAFO_GEOAX_ASSIGN_TAB1...
and
MD24110ff. $MC_TRAFO_AXES_IN1...8
to which no machine axes are assigned (gap) through
MD20070 $MC_AXCONF_MACHAX_USED (machine axis number valid in the channel)
,
triggers alarms 4346 or 4347.
2.1.12 Link axes
Significance
Link axes are axes, which are physically connected to another NCU and whose position is
controlled from this NCU. Link axes can be assigned dynamically to channels of a different
NCU. From the perspective of a particular NCU, link axes are non-local axes.
The axis container concept is used for the dynamic modification of the assignment to an
NCU. Axis replacement with GET and RELEASE from the part program is not available for link
axes across NCU boundaries.
Requirements:
• The participating NCUs, NCU1 and NCU2, must be connected by means of high-speed
communication via the link module.
References:
/PHD/Configuring Manual NCU 571-573.2; Link Module
• The axis must be configured appropriately by machine data.
• The link axis option must be installed.
To Next Page
Loading...
Need help?
General
