Results Storage Area Response Codes - Omron CS Series Operation Manual

Results Storage Area Response Codes

Network Relay Errors
8-5

Results Storage Area Response Codes

Response UNIX error
code message
0003 ESRCH
0006 ENXIO
0009 EBADF
000D EACCES
000E EFAULT
0011 EEXIST
0016 EINVAL
0018 EMFILE
0020 EPIPE
003C EPROTONO-
SUPPORT
003D EPROTOTYPE
003E ENOBUFS
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.
Bit 7 6
1
First word
7 6
1
Second word Main response code (MRES)
Relay error flag
7 6
1
Third word Error network address
The response codes stored in the Results Storage Area can be used to trou-
bleshoot socket service problems. Refer to Socket Services Parameter Area 1
to 8 (Ethernet Unit to CPU Unit) on page 88 for the location of the response
codes stored in the Results Storage Area.
The UNIX socket service error messages corresponding to the response
codes are given in the following table. Refer to the documentation for the
devices involved when communicating between an Ethernet Unit and other
devices.
Description
No such process
No such device or address
Bad file number (incorrect socket
specification)
Permission denied
(Broadcast address specified for
remote IP address for active TCP
open)
Bad address (copy failed between
kernel and user area)
File exists
Invalid argument (socket library
argument error)
Too many open files (More than 32
sockets)
Broken pipe (remote node closed
socket)
Protocol not supported (protocol
other than UDP, TCP, or RAW speci-
fied)
Protocol wrong type for socket
No buffer space available
First byte Second byte
5 4 3 2 1 0 7 6 5 4
Command code
5 4 3 2 1 0 7 6 5 4
S-b-response code (SRES)
1: PLC non-fatal error flag
1: PLC fatal error flag
5 4 3 2 1 0 7 6 5 4
Error node address
Probable remedy
Close the local socket and try reopening it.
Check the IP address of the remote node and
try to reconnect.
Close the local socket and try reopening it.
Close the local socket.
Close the local socket and try reopening it.
There is too much load (traffic) on the Ethernet
Unit. Check your user applications.
Section 8-5
3 2 1 0
3 2 1 0
3 2 1 0
231