Table of Contents
Advertisement
Troubleshooting with Response Codes
Main code
Sub-
code
11: Parameter
00
error
01
03
04
0B
0C
22: Status error
0F
(operating mode
disagreement)
10
11
23: Environment
05
error (no such
Unit)
07
Network Relay Errors
First word
First word
Second word
Second word
Third word
Third word
Probable cause
The parameters in the command data are
incorrect.
The UDP/TCP socket number was not
within the proper range.
The local UDP port number might be set to
0.
A correct memory area code has not been
used or EM Area is not available.
The first word is in an inaccessible area or
the bit number is not 00.
The address set in the command is not
correct.
The response frame is too long.
Parameters are set incorrectly in the com-
mand data.
The same socket service is already in
progress at the specified socket number.
The specified socket is not open.
The internal buffers are full because there
is too much traffic at the local node, pre-
venting data from being sent.
IP address conversion failed.
IP address conversion is set for automatic
conversion only.
For network relay errors using SEND(090) or RECV(098), check the path of
the command using the routing tables and the nature of the error using the
response code to eliminate the cause of the error.
For network relay errors using CMND(490), the location of the relay error is
recorded in the second through third words of the response, as shown below.
1st byte
1st byte
15
15
14
14
13
13
12
12
11
11
Bit
Bit
0
0
15
15
14
14
13
13
12
12
11
11
Bit
Bit
Main response code (MRES)
Main response code (MRES)
1: Relay Error Flag
1: Relay Error Flag
15
15
14
14
13
13
12
12
11
11
Bit
Bit
Error network address
Error network address
Check the parameters.
Be sure the socket number is between 1 and 8.
Set the Local UDP port number correctly.
Check the command's memory area code in the
Results Storage Area and set the appropriate
code.
Set a first word that is in an accessible area.
The bit number must be 00 for Ethernet Units.
Correct the address in the command data,
being sure that the start address plus the num-
ber of words does not exceed accessible mem-
ory.
Correct the number of data elements or other
parameters in the command data for which the
response is being returned.
Check the command data and correct any
parameters that are incorrect.
Use the socket status flag in PC memory to be
sure that socket service has finished before
starting services again.
Open the socket. For TCP sockets, be sure to
wait until connection is made.
Correct the user application to reduce traffic at
the Ethernet Unit.
Check the IP address and subnet mask in the
System Setup and be sure that settings are cor-
rect.
Check the mode settings in the System Setup.
This error will be generated for the READ IP
ADDRESS TABLE command only.
2nd byte
2nd byte
10
10
9
9
8
8
7
7
6
6
5
5
Command code
Command code
10
10
9
9
8
8
7
7
6
6
5
5
Sub response code (SRES)
Sub response code (SRES)
1: PC Non-fatal Error Flag
1: PC Non-fatal Error Flag
1: PC Fatal Error Flag
1: PC Fatal Error Flag
10
10
9
9
8
8
7
7
6
6
5
5
Error node number
Error node number
Section 10-6
Remedy
4
4
3
3
2
2
1
1
0
0
0
0
0
0
4
4
3
3
2
2
1
1
0
0
4
4
3
3
2
2
1
1
0
0
209
Hide quick links:
Advertisement
Chapters
Table of Contents
Troubleshooting
