YASKAWA MP2000 Series Troubleshooting Manual page 40

3.3 Message Communication Error
3.3.1 Checking the Error Status and Transmission Status
( 2 ) When other than 0: No error is Displayed in the Error Status Field
Check the overview of the error details by referring to the Error Status field. The list of error statuses that frequently
occur is given below.
Note: The Error Status field shows the latest error history. The error information is retained even after recover-
ing from the error and starting normal communication.
[ a ] When the TCP protocol is selected
Error Status Field
2: Local Port Number
Error
4: Connection Error
(M-SND)
5: Connection Error
(M-RCV)
7: Data Transmit Error
(TCP)
9: Data Receive Error
(TCP)
12: Data Change Error
[ b ] When the UDP protocol is selected
Error Status Field
12: Data Change Error
3-8
Details
The port number whose TCP connec-
tion has been broken was bound.
Local port number setting
error
A command was issued by another mes-
sage function to the same remote device
simultaneously before the connection
had been established.
TCP connection error The TCP connection request from the
(When using the message Machine Controller was rejected by the
transmission function) remote device.
An error has occurred on the Machine
TCP connection error
Controller side while processing the
(When using the message
TCP connection request from the
receive function)
remote device.
The remote device is not connected or
Data transmission error
the power to the remote device is OFF.
A TCP connection break request has
Data reception error
been received from the remote device.
There was a data format error in the pro-
Protocol conversion error
tocol.
Details
There was a data format error in the pro-
Protocol conversion error
tocol.
Cause
Review the application so that the exe-
cute command is issued more than one
minute after the execution of the abort
command has completed in the message
function at the Machine Controller side.
Review the program so that more than
one message function will not be exe-
cuted for one connection.
Check that the network settings of the
remote device are set to open the port
for communicating with the Machine
Controller.
(Settings to be checked: the port number
for communicating with the Machine
Controller, TCP/UDP selection, etc.)
Check that the network settings of the
remote device are correctly set for the
port for communicating with the
Machine Controller.
Check that the power to the remote
device is turned ON and that it is con-
nected with the Machine Controller by
Ethernet cables.
If this is a request for an unexpected
connection break, review the connection
closing sequence at the remote device.
Match the settings for the protocol type
and code (BIN/RTU/ASCII) between
the remote device and the Machine
Controller.
Cause
Match the settings for the protocol type
and code (BIN/RTU/ASCII) between
the remote device and the Machine
Controller.
Remedy
Remedy