Mitsubishi Electric MELSEC iQ-F Series User Manual page 122

Error code Error name
C059H Ethernet communication
error
C05BH Ethernet communication
error
C05CH Ethernet communication
error
C05EH Ethernet communication
error
C05FH Ethernet communication
error
C060H Ethernet communication
error
C061H Ethernet communication
error
C06FH Ethernet communication
error
C0D8H Ethernet communication
error
C0DEH Ethernet communication
error
C101H Ethernet communication
error
C11CH E-mail function
C120H E-mail function
C124H E-mail function
C126H E-mail function
C131H E-mail function
C13DH E-mail function
10 TROUBLESHOOTING
120
10.6 List of Error Codes
Error details and causes
• Error in command or subcommand
specification.
• There is a command or subcommand that
cannot be used by the Ethernet module.
Ethernet module cannot read or write from/to
specified device.
Error in request contents. (Reading or writing
by bit unit for word device, etc.)
The communication time between the
Ethernet module and PLC CPU exceeds the
Ethernet monitor timer setting.
There is a request that cannot be executed for
the target CPU module.
Error in request contents. (Error in
specification of data for bit device, etc.)
Request data length does not match the
number of data in the character section (part
of text).
When the communication data code is set to
"Binary", a request message of ASCII is
received. (Error history of this error code is
registered but no error response returns.)
The number of the specified blocks exceeds
the range.
Socket communication receive message fails.
No response can be received from the DNS
server.
No e-mail address is found.
The SMTP server could not be open.
The response from the SMTP server is timed
out.
The SMTP server could not be closed.
The SMTP server was running, but an error
response was received.
SMTP server authentication error
Action
• Reconsider request contents.
• Send command or subcommand that can be used by the
Ethernet module.
Reconsider device to read or write.
Correct request content, and send data to Ethernet module again.
(Subcommand correction, etc.)
• Increase the monitor timer setting.
• Check the connection between the CPU and Ethernet module.
• Correct network number, request station number, request
destination module I/O number, or request destination module
station number.
• Correct contents of write request and/or read request.
Correct request content, and send data to Ethernet module again.
(Data correction, etc.)
After reexamining and correcting the content of the text or the
request data length in the header, resend the message to the
Ethernet module.
• Sent a request message which is adapted to the setting of the
communication data code.
• Change to the communication data code which is adapted to
the request message.
Correct the specified value of for the number of blocks.
• Check the operation of the external device or switching hub.
• Since there may be congestion of packets on the line, send
data after a certain period of time.
• Check if the connection cable is disconnected.
• Check that there is no connection failure with the switching hub.
• Execute the communication status test, and if the test was
completed with an error, take the corrective action.
• Execute the module communication test, and check that there
is no failure in the module.
• Check the DNS server address.
• Run a PING command to check whether the DNS server can be
communicated.
• Check that the own station IP address and the DNS server IP
address are in the same class. (If the class differs, check the
router settings.)
• Check if the e-mail settings in the parameter settings are
correct.
• If the e-mail server and the Ethernet module are connected via
a router, check whether the router settings are correct.
• Send a test e-mail to an address that is ensured to receive the
e-mail. If the e-mail is received successfully, check again that
the domain name after "@" is correct.
• Check that the SMTP server port number is 25.
• Run a PING command to check whether the SMTP server can
be communicated.
• If TLS connection is specified, check if the certificate is
appropriate.
• Check if there is a problem with environments such as network
cables.
• Check that there is no error with the SMTP server.
• Check for any excessive network load.
• Check that there is no error with the SMTP server.
• Check for any excessive network load.
• Check whether the specified user name is registered with the
server.
• Send the e-mail again after a certain period of time.
• Check that the SMTP login ID and password are correct.
• Check the SMTP server status.