Operation when an interrupt is generated
Operation when an interrupt is generated is explained below.
■If an interrupt cause occurs when interrupt is disabled (DI)
The interrupt that was generated is stored, and the stored interrupt program is executed the moment that the status changes
to interrupt enabled. An interrupt is stored only once even if the same interrupt is generated multiple times. Note, however,
that all interrupts cause are discarded when interrupt disable is specified by the IMASK and SIMASK instructions.
Main routine program
Interrupt Program
Not executed because the interrupt program
execution is in disabled status (DI).
■When an interrupt cause is generated by a PAUSE status
The interrupt program is executed the moment that the CPU module changes to the RUN status and the status changes to
interrupt enabled. An interrupt is stored only once when the same interrupt is generated multiple times before the CPU
module changes to the RUN status.
Interrupt occurrence
Main routine program
Interrupt Program
Not executed because the CPU module
is in the STOP status.
■If an interrupt factor occurs during link refresh
Suspends link refresh and executes the interrupt program. Even though station unit block guarantee is enabled for cyclic data
during refresh of such links as CC-Link IE Field Network, if the interrupt program uses a device specified as the refresh target,
station unit block guarantee for cyclic data is not available.
Interrupt factor
Execution of the interrupt
program
Execution of link refresh
(1) Suspends link refresh and executes the interrupt program.
1 PROGRAM EXECUTION
34
1.5 Program Type
Interrupt occurrence
PAUSE→ RUN
10 ms
Enable Interrupt (EI)
Execution
Executed as soon as the interrupt program
execution status changes to enabled.
Enable Interrupt (EI)
Execution
Executed as soon as PAUSE → RUN and
the interrupt program execution status
changes to enabled.
10 ms
10 ms
(1)
10 ms