Mitsubishi MELSEC-Q Series User Manual page 524

14
COMMUNICATIONS BETWEEN CPU MODULES
[Error details]
[Program example]
(5) Precautions
14
- 7 14.2 Event Notification
In any of the following cases, an operation error occurs, the error flag (SM0) of the
programmable controller CPU turns ON, and the error code is stored into SD0.
Table14.7 Error codes related to S(P).GINT instruction
*1
Error code
The target CPU start I/O No.
2110
(CPU "Empty" setting) CPU or a CPU module not mounted.
2114
The target CPU start I/O No.
The target CPU start I/O No.
2117
supported by the S(P).GINT instruction.
The target CPU start I/O No.
4100
3DF or 3E4
H
* 1: 0000 (Normal)
H
Sequence program that will cause an interrupt for the C Controller module of CPU No. 2
X0
Figure 14.5 Program example using S(P).GINT instruction
(a) When interrupt event has already been notified at execution of
QBF_WaitEvent function
When an interrupt event has already been notified from the programmable
controller CPU or C Controller module (another CPU) at execution of the
QBF_WaitEvent function, the user program is restored from the interrupt event
waiting status as soon as the QBF_WaitEvent function is executed.
When multiple interrupt events have been notified with the same interrupt event
number at execution of the QBF_WaitEvent function, the user program processes
them as a single interrupt event notification.
(b) When event notification is used by multiple user programs
Do not set the same CPU No. and same interrupt event No. in multiple user
programs.
If such setting is made, it will be uncertain which user program will receive the
interrupt event.
Error factor
16(n1) specified a reserved
16(n1) specified the host CPU.
16(n1) specified a module not
16(n1) specified any of 0 to
.
H
SM391
Normally completed program
SM391
Program that will cause interrupt again
S.GINT H3E1 K0
Corrective
action
Check and
correct the
sequence
program.