Rockwell Automation 8520-MUM 9/Series CNC Mill Operation and Programming Manual Documentation Set - Manual (Page 762)

Program Interrupt
Chapter 29
29-4
When using system interrupts, take into consideration:
The system installer can determine in AMP if a signal to execute an
interrupt program is delayed until the end of a currently executing
block, or if the interrupt is executed immediately when the signal is
received.
The system installer can determine in AMP whether an interrupt
program request is recognized when an interrupt switch is turned on, or
only when the switch makes the transition from off to on. This is to
help prevent the accidental execution of an interrupt program if a switch
is inadvertently left on when a program begins execution.
Interrupt programs should normally be disabled during thread cutting.
The execution of an interrupt program during a threading pass may
cause undesired results.
The system installer has the option of writing PAL to allow the use of 4
interrupt signals (4 switches). One of these signals may call a type 1
interrupt; the other three call a type 2 interrupt.
Before an interrupt signal is recognized by the control it must first have
been enabled by programming a M96 followed by the correct L word
for that signal.
Interrupt programs may only be executed when the control is in the
automatic mode. Interrupt requests that occur during MDI or manual
modes are ignored.
Cutter compensation is temporarily cancelled during the execution of an
interrupt program. It is reactivated upon completion of the interrupt
program. No entry or exit move from compensation is performed.
Interrupts that are requested when the control is in E-STOP are ignored
regardless of whether the interrupt is enabled or not.
Interrupts can only be executed when the control is in the
<CYCLE START> state. If a request for an interrupt is made when the
control is in <CYCLE STOP> or cycle suspend the interrupt request is
still recognized. The interrupt program will be executed when a
<CYCLE START> state becomes active again.
29.2
Interrupt Request
Considerations