Rockwell Automation 8520 9/Series CNC Lathe User Manual

Page 760

Advertising
background image

Chapter 30

Using a 9/Series Dual--Processing System

30-20

Activating Interference Checking

The interference boundaries for each process are entered into the

interference checking tables. These tables relate the boundaries to specific

tool or offset geometries. The system installer selects the number of

boundaries that are available (from 1-32) for each process.

Each process can have a different interference boundary number active at

the same time. Activating an interference boundary for only one process is

not sufficient to activate interference checking. Each process must have an

active, valid interference boundary.

The system installer determines how the different interference boundaries

are activated for each process through PAL. Refer to your system

installer’s documentation for details on activating these boundaries.

Before interference checking can be activated, all axes that make up a

boundary must be homed.

Important: Your system installer has the option to determine with PAL

when interference checking will become active. Interference checking is

available in:

manual mode
automatic and MDI modes
manual, automatic, and MDI modes

Refer to your system installer’s documentation for details.

Once interference checking is turned on, it remains active in that mode

(Auto, MDI, or Manual) until turned off through the system installer’s

PAL. This includes when no program is active, a control reset is

performed, or even when the control is in E-Stop (unless PAL has been

specifically written to do so). Interference checking can also be active in

mechanical handle feed mode (servo off).

Interference checking is not performed on the part program during

QuickCheck mode. Interference checking is still active in QuickCheck;

however, since axis motion is not usually present during QuickCheck,

programmed collisions are not detected.

Important: Shared axes can only be defined in an interference zone in one

process. If the system installer defines the same shared axis to be in an

interference zone for both processes the control generates an error.

Advertising