13 - 10
13.2 Interrupt from Another CPU
13
COMMUNICATIONS BETWEEN CPU MODULES
(f) Program example
In the sequence program below, an interrupt is issued to the C Controller module
that is set as CPU No.2.
(5) Precautions
(a) When an interrupt event has already been notified at execution of the
QBF_WaitEvent function
When an interrupt event has already been notified from a programmable
controller CPU or C Controller module (another CPU) at the time of the
QBF_WaitEvent function execution, the user program is restored from the
interrupt event waiting status at the same time with the QBF_WaitEvent function
execution.
If multiple interrupt events have been notified with the same interrupt event No. at
the time of the QBF_WaitEvent execution, the user program processes them as a
single interrupt event notification.
(b) When using the event notification function in multiple user programs
Do not set the same CPU No. and the same interrupt event No. on more than one
program.
If such settings are specified, which user program will receive the interrupt event
will be uncertain.
For details of the D(P).GINT instruction, refer to the following.
Q173DCPU/Q172DCPU Motion Controller (SV13/SV22) Programming
Manual (Motion SFC)
Figure 13.8 Example of a program using S(P).GINT instruction
S.GINT H3E1 K0
Program for normal completion
Program that will cause interrupt again
SM391
SM391
X0
To Next Page
Loading...
