Delta AH500 series Hardware Manual page 209

AH5 00 Hardw are Manu al
Error
Description
code
The remote device refuses the
16#6214
connection.
16#6215 The socket is not opened.
16#6217 The socket is opened.
The data has been sent
16#6218
through the socket.
The data has been received
16#6219
through the socket.
16#621A The socket is closed.
The remote device in the Ether
16#6303
Link aborts the connection.
The connection in the Ether
16#6304
Link is busy.
The remote device in the Ether
16#6309 Link does not respond after the
timeout period.
The number of TCP
connections reaches the upper
16#6400 limit, or the flag which is related
to the sending of the data is not
set to ON.
The remote device aborts the
16#6401
connection.
There is no response from the
16#6402 remote device after the timeout
period.
The remote IP address used in
16#6403
the applied instruction is illegal.
The Modbus function code not
16#6404
supported is received.
The number of data which will
be received is not consistent
16#6405
with the actual length of the
data.
The network number which
16#6600 receives the command
exceeds the range.
The network is undefined in the
16#6601
network configuration
parameter.
The number of routing
16#6604 connections reaches the upper
limit.
The unexpected packet is
16#6605
received.
9 - 1 4
Remedy
Make sure that the remote device operates
normally.
Check whether operational sequence in the
program is correct.
Check whether operational sequence in the
program is correct.
Check whether operational sequence in the
program is correct.
Check whether operational sequence in the
program is correct.
Check whether operational sequence in the
program is correct.
1. Check the connection and the status of the
remote device.
2. Check whether the remote device supports the
Ether Link.
1. Check whether the number of connections in
the Ether Link exceeds the system load.
2. Retry the connection in the Ether Link later.
1. Check whether the CPU module in the Ether
Link operates normally.
2. Check whether the CPU modules are connected
normally.
1. Check whether the flag which is related to the
sending of the data in the program is modified.
2. Retry the setting of the flag and the sending of
the packet.
Check whether the remote device support the
Modbus port (502).
Check whether the remote device operate
normally.
Check whether the program is correct.
Check the command transmitted from the remote
device.
Check the command transmitted from the remote
device.
Check the command transmitted from the remote
device.
Check the network configuration in NWCONFIG,
and download it again.
Resend the packet later. ((This error does not
cause the PLC to stop running. Users can perform
the corresponding remedy by means of the related
flag in the program.)
Check the command transmitted from the remote
device.