HEIDENHAIN TNC 640 (34059x-05) ISO programming - Manual (Page 381)

Dynamic Collision Monitoring (Option #40) 11.2
11
TNC 640 | User's ManualDIN/ISO Programming | 1/2015
381
Collision monitoring in the Program Run operating
modes
In the Positioning with manl.data input, Program run single
block and Program run, full sequence operating modes, the
TNC stops the program run before the block in which two objects
monitored for collision would approach each other within a distance
of less than 5 mm. In this case, the TNC displays an error message
naming the two objects causing collision.
If you have selected a screen layout in which the collision objects
are on the right, then the TNC additionally marks the colliding
objects in red.
The TNC monitors motions blockwise. The TNC
interrupts the program run with a collision warning in
the block that would cause a collision.
Danger of collision!
With M140 MB MAX and collision monitoring
simultaneously possible (option #40 enabled,
kinematics with defined collision objects selected),
tool retraction does not terminate at the border of
the traverse range but before a pending collision.
Detected collisions with this constellation do not
generate an error message, but the TNC continues
the NC program from this position. This may cause
unexpected movements or collisions with the
workpiece.
Only use numerical values with collision monitoring
M140.
Check in the
Program run, single block operating
mode whether the actual distance enables collision-
free continuation of the NC program.
If you require
M140 MB MAX, you must select
kinematics without defined collision objects. Please
note that with kinematics without defined collision
objects, collision monitoring is
not
possible.
Constraints with program run:
For tapping with a floating tap holder only the
basic setting of the floating tap holder is taken
into account with collision monitoring.
The handwheel superimpositioning function
with
M118 in combination with active collision
monitoring is only possible in stopped condition.
The TNC is not able to implement collision
monitoring if functions or cycles require the
coupling of several axes e.g. with eccentric
turning.
The TNC is not able to implement collision
monitoring if at least one axis is referenced in lag
tracking or not.
Also note the generally valid constraints, see
"Function", page 377