Function Manual
54 01/2017
The following table shows the effect of individual interface signals (from PLC to axis) on gantry axes:
Axis/spindle disable DB380x.DBX0001.3 On all axes in gantry
No effect
Position measuring system 1
On all axes in gantry grouping
Delete distance to go (axial)
On all axes in gantry grouping
Hardware limit switch minus/plus DB380x.DBX1000.0
Axial alarm: Brake request on all axes in gantry
2. Hardware limit switch minus/plus DB380x.DBX1000.2
Axial Axial
Select drive parameter set DB380x.DBX4001.0
Axial Axial
Either the "Follow-up" state (IS of one gantry axis = 1) or the "Stop" state (IS of all gantry axes = 0) is activated for all gantry
axes, depending on interface signal:
DB380x.DBX0001.4 (follow-up mode)
b) Axial interface signals from axis to PLC (NCK → PLC)
Each of the axial, axis-to-PLC interface signals for the synchronized axis and the leading axis is always set on an axis-
specific basis and output to the PLC.
When the leading axis is being traversed, the interface signals are also set for the synchronized axis:
DB390x.DBX0004.6/.7 (traverse command minus/plus)
Miscellaneous points regarding gantry axes
Manual travel
It is not possible to traverse a synchronized axis directly by hand in "JOG" mode. Traverse commands entered via the
traversing keys of the synchronized axis are ignored internally in the control. Rotation of the handwheel for the synchronized
axis has no effect either.
An overriding motion by means of the handwheel can only be applied to the leading axis in coupled axis mode. In this case,
the synchronized axes traverse in synchronism with the leading axis.
Programming in part program
Only the leading axis of a gantry axis grouping may be programmed in the part program. An alarm is generated while
programming a synchronized axis, even when a gantry axis grouping is separated.
The PRESET function can only be applied to the leading axis. All axes in the gantry grouping are reevaluated internally in
the control when PRESET is activated. The gantry axis then loses their reference and synchronization:
DB390x.DBX5005.5 = 0 (gantry grouping is synchronized)
In an active gantry grouping, the following MD parameterization is ignored for the synchronized axes:
MD30450 IS_CONCURRENT_POS_AX=1 (reset default: neutral axis/channel axis)
The state of the leading axis is assumed. The user is informed about the inappropriate configuration with display alarm 4300.
To Next Page
Loading...
Need help?
General
