Mitsubishi Melsec-Q Series User Manual page 299

(From the previous page)
Unable to perform boot operation from
Note12.3
memory card.
UNIT VERIFY ERR. has occurred.
CONTROL BUS ERR. has occurred.
CPU module does not start.
OPERATION ERROR has occurred at
execution of the S(P).SFCSCOMR and
S(P).SFCTCOMR instructions.
Comments cannot be read at the execution of
the S(P).SFCSCOMR and S(P).SFCTCOMR
instructions.
PARAMETER ERROR has occurred at power
on or reset.
CPU module cannot communicate with
GX Developer.
Ethernet communication is not available other
than by direct connection to GX Developer.
Ethernet communication with the target device
is not available.
Ethernet communication is not available by
direct connection to GX Developer.
Ethernet communication with a CPU module is
slow or unstable.
Error has occurred during MC protocol
communication.
Clock data cannot be set by SNTP.
Data cannot be received on the target device
side after sending upon the send instruction
from the Built-in Ethernet port QCPU by using
the Socket communication function.
Data cannot be received on the Built-in
Ethernet port QCPU side after sending from
the target device side by using the Socket
communication function.
Open process of the Socket communication
function does not complete (SD1282 (Open
completion signal) does not turn on).
Note1
Basic
Note12.3
The Basic model QCPU cannot use the memory card.
When unable to perform boot operation from
Section 12.2.23
the memory card
Section 12.2.24
When "UNIT VERIFY ERR." has occurred
Section 12.2.25
When "CONTROL BUS ERR." has occurred
Section 12.2.26
When the CPU module does not start
When "OPERATION ERROR" has occurred at
Section 12.2.27
execution of the S(P).SFCSCOMR and
S(P).SFCTCOMR instructions
When comments cannot be read at execution of
Section 12.2.28
the S(P).SFCSCOMR and S(P).SFCTCOMR
instructions
When "PARAMETER ERROR" has occurred at
Section 12.2.29
power on or reset
When the CPU module cannot communicate with
Section 12.2.30
GX Developer
When Ethernet communication is not available other
Section 12.2.31
than by direct connection to GX Developer
When Ethernet communication with the target
Section 12.2.32
device is not available
When Ethernet communication is not available by
Section 12.2.33
direct connection to GX Developer
When Ethernet communication with a CPU module
Section 12.2.34
is slow or unstable
When an error has occurred during MC protocol
Section 12.2.35
communication
Section 12.2.36
When clock data cannot be set by SNTP
When unable to receive data on the target device
Section 12.2.37
side by the Socket communication function
When unable to receive data by the Socket
Section 12.2.38
communication function
When open process of the Socket communication
Section 12.2.39
function does not complete
Figure 12.1 Troubleshooting flowchart
CHAPTER12 TROUBLESHOOTING
12 - 4
1
2
3
12
5
6
7
8
Note1