Omron CJ - ETN21
Omron CJ - ETN21
Omron CJ - ETN21
3. Make the routing table settings and transfer them to each PLC. (See note.)
Set the routing tables with CX-Integrator, and transfer it to each PLC.
4. Create a ladder program that includes the SEND(090), RECV(098), and CMND(490) instructions.
118
FINS/TCP Method Section 6-3
6-3 FINS/TCP Method
6-3-1 Overview
FINS/TCP Features
The FINS/TCP method is a FINS communications method that uses the TCP/
IP protocol. TCP/IP is a connection-type communications protocol. Before a
message is sent from one node to another, it is necessary to establish a vir-
tual circuit, i.e., a connection. Once a connection has been established, com-
munications are quite reliable. The arrival of data that is sent via the
connection is confirmed by an acknowledgement (ACK) response, and retries
are executed automatically as required.
The FINS/TCP method has been newly added to the CS1W-ETN21 and
CJ1W-ETN21 Ethernet Units.When FINS/TCP is used, it must be determined
which node is the server and which is the client.
For communications between a personal computer and a PLC, the computer
should normally be set as the client and the PLC as the server. For communi-
cations between two PLCs, either one can be set as the client and the other
as the server.
Compared to the FINS/UDP method, the FINS/TCP method has the following
characteristics.
Data transmission is more reliable, due to factors such as retry process-
ing at the TCP/IP layer. The FINS/TCP method is thus better suited to
dealing with communications errors in an IP network that spans several
layers.
Remote clients can be restricted by means of settings at the server (i.e.,
the server can be protected from access by non-specified IP addresses).
Broadcasting cannot be used.
TCP/IP has various retry procedures, and this tends to lower its perfor-
mance in comparison with UDP/IP.
There is a limit to the number of connections that can be made (i.e., 16
connections maximum), and any given node can communicate only with
up to 16 other nodes at a time.
Node
(Client)
Data transmission 1
Request to establish a connection
Node
(Server)
Connection established
Acknowledgement
Acknowledgement
An acknowledgement is received whenever a
connection is established or data is sent, so
transmissions are more reliable but somewhat slower.
119
FINS/TCP Method Section 6-3
Once a FINS/TCP connection (connection number, remote IP address)
has been set in the Unit Setup, it can be dynamically changed from the
ladder program using a FINS command (i.e., FINS/TCP CONNECTION
REMOTE NODE CHANGE REQUEST).
FINS/TCP Frame Format The following diagram shows the structure of a TCP packet sent over an
Ethernet network.
As the diagram shows, a nested structure is used with the FINS/TCP method,
i.e., Ethernet Ver. 2, IP frame, TCP frame, FINS/TCP header frame, and FINS
frame. A TCP data section (FINS/TCP header + FINS frame) that exceeds the
segment size (default: 1,024 bytes, with automatic adjustment for optimum
values between the nodes) is split into TCP packets for transmission. The split
TCP data is then joined automatically at the remote node's TCP/IP protocol
layer. The TCP/IP protocol layer, however, cannot determine where the data
has been split, so the TCP data sections from multiple packets are all joined
together. Therefore, when using the FINS/TCP method, FINS/TCP headers
must be added at the beginning of FINS frames in order to serve as FINS
frame delimiters. The length of the data in the following FINS frame is stored
in the header, allowing the frame to be separated out by the remote node.
With the Ethernet Unit and FinsGateway Ver. 2003 the appropriate frames are
separated out automatically, so there is normally no need to be pay attention
to it at the application layer.
TCP Port Number for
FINS/TCP
The TCP port number is the number for TCP to identify the application layer
(i.e., the FINS communications service in this case). When communications
are executed using TCP/IP, this port number must be allocated for the com-
munications service.
The default setting for the FINS/TCP local TCP port number (i.e., the Ethernet
Unit's TCP port number) is 9600. To set another number, make the setting for
the FINS/TCP port using the Setup Tab in the Unit Setup.
The FINS/TCP port number set in the Unit Setup is used by the FINS/TCP
server's TCP socket. The FINS/TCP client's TCP socket uses any TCP port
number that can be used at that node. (With the Ethernet Unit and FinsGate-
way Ver. 2003, an unused TCP port is automatically detected and utilized.)
At the Ethernet Unit, a TCP/IP frame that is received is recognized as a FINS
frame, according to the remote TCP port number in the frame.
FINS/TCP Connection
Numbers
FINS/TCP allows up to 16 FINS/TCP connections to be established simulta-
neously, and these 16 connections are managed at the Ethernet Unit by con-
nection numbers. When setting connections by means of the FINS/TCP
settings in the CX-Programmer's Unit Setup, set them individually using these
connection numbers.
Ethernet Ver. 2 IP TCP FINS frame FCS FINS/TCP header
TCP packet
120
FINS/TCP Method Section 6-3
FINS/TCP Connection Status (Word n+23)
While a connection with a remote node is established, the bit corresponding to
the FINS/TCP connection status turns ON in the section of the CPU Bus Unit
words allocated in the CIO Area. The bit turns OFF if the connection is termi-
nated by a communications error or a FINS command (i.e., FINS/TCP CON-
NECTION REMOTE NODE CHANGE REQUEST).
FINS/TCP
Communications
Procedure
With FINS/TCP, FINS node addresses are exchanged immediately after a
connection is established. This makes it possible to determine the FINS node
addresses to which the 16 connection numbers, and to manage them in an
internal table.
After a connection has been established as a FINS/TCP server, it is termi-
nated in the following ways.
When the connection is closed by the client.
When a FINS command to close the connection (FINS/TCP CONNEC-
TION REMOTE NODE CHANGE REQUEST) is sent by the client.
When there is no response from the client when the keep-alive function is
in effect.
After a connection has been established as a FINS/TCP client, it can be termi-
nated in the following ways.
If the connection is closed by the server.
If there is no response from the client when the keep-alive function is in
effect.
15 14 13 12 11 10 09 07 06 05 04 03 02 01 00
n+23
*: Bit 15 corresponds to connection No. 16, bit 00 to connection No. 1, etc.
08
Connection request (CS)
FINS node number A sent
Ethernet Unit
(Server)
Passive open
Connection established
Local node No. sent
FINS frame sent
Personal computer
(Client)
Active open
Local node No. sent
Connection established
Remote node No. received
FINS node number B sent
FINS node numbers exchanged
Connection established
Normal data communications
Remote node No. received
FINS frame sent
Full duplex communications
Example:
IP address C
FINS node number A
Example:
IP address S
FINS node number B
121
FINS/TCP Method Section 6-3
Even if the connection is closed at the FINS/TCP client, requests continue to
be made to the FINS/TCP server every few seconds to open a connection.
Note After the Ethernet Unit is powered up or restarted, the IP address for the con-
nection used as the FINS/TCP client is the remote IP address set under the
FINS/TCP Tab in the Unit Setup.
To dynamically change the remote IP address (i.e., during CPU Unit opera-
tion), execute the CMND(490) instruction in the ladder program and send a
FINS command (FINS/TCP CONNECTION REMOTE NODE CHANGE
REQUEST; command code: 27 30 hexadecimal) to the Ethernet Unit.
Procedure for Using FINS/TCP
Note Routing tables are required in the following situations:
When communicating with a PLC or computer on another network (e.g.,
remote programming or monitoring using FINS messages or a CX-Pro-
grammer)
When multiple Communications Units are mounted to a single PLC (i.e.,
CPU Unit)
When routing tables are used for one or more other nodes on the same
network
It is not necessary to set routing tables if one Communications Unit is
mounted to the PLC and the nodes are connected as one network.
1. Make the basic settings.
Refer to Section 2 Startup Procedure in the Operation Manual Construction of Net-
works.
3. Make the routing table settings and transfer them to each PLC. (See note.)
Set the routing tables with CX-Integrator, and transfer it to each PLC.
4. Create a ladder program that includes the SEND(090), RECV(098), and CMND(490)
instructions.
122
Creating Routing Tables Section 6-4
6-4 Creating Routing Tables
When the FINS communications service is used, routing tables must be cre-
ated in advance. Routing tables are required in the following circumstances.
When communicating with a PLC or computer on another network (e.g.,
remote programming or monitoring using FINS messages or a CX-Pro-
grammer)
When multiple Communications Units are mounted to a single PLC (i.e.,
CPU Unit).
When routing tables are used for one or more other nodes on the same
network.
It is not necessary to set routing tables if one Communications Unit is
mounted to the PLC and the nodes are connected as one network. The rout-
ing tables are required not only for nodes communicating via the FINS com-
munications service but also for all relay nodes on the network.
6-4-1 Routing Table Overview
The routing tables describe the transmission path for FINS messages when
the FINS communications are used. It consists of two tables: A local network
table and a relay network table.
Local Network Table The local network table is a table describing the correspondences among unit
numbers of the Communications Units and Boards mounted to each node.
Note 1. The unit number is set (0 to F: 1 to 15) by the rotary switch on the front of
the Ethernet Unit.
2. The network address is the number of the network (1 to 127) to which the
Communications Unit or Board is connected. It is set when the local net-
work table is created.
Relay Network Table A relay table is a table that shows the nodes to which data should be sent first
in order to send data to a network that is not connected to the local node. It
shows the correspondence between the address of the final destination net-
work, and the network address and node address of the first relay point of the
path to reach there. When internetwork communications are carried out, the
end network can be reached by following the relay points.
Example
Unit #04
Unit #05
Unit #06
Unit #07
Network #1
Network #2
Network #3
Network #4
Local Network Table
Local network
address
Unit number
1
2
3
4
04
05
06
07
123
Creating Routing Tables Section 6-4
The following example shows routing tables for sending data from PLC #1 (the
local node: network address 1, node address 1) to PLC #4 (the destination
node: network address 3, node address 2).
Note In the above example, the routing tables required for a message to reach PLC
#4 from PLC #1 are shown. Additional settings would be required in the rout-
ing tables for a message to reach PLC #1 from PLC #4. Refer to 6-4-3 Rout-
ing Table Setting Examples for routing table setting examples.
6-4-2 Connecting and Using a Peripheral Device for the PLC
Routing tables must be created by a CX-Integrator connected to the PLC.
(They cannot be created using a Programming Console.) For details on how
to connect and use the CX-Integrator, refer to the CX-Integrator Operation
Manual (W445). (CX-Integrator is automatically installed when CX-One is
installed.)
Note 1. When routing tables are transferred from the CX-Integrator to the PLC, the
CPU Bus Unit is reset so that the routing tables that have been created can
be read and enabled. Before transferring the routing tables, make sure that
the devices in the system will not be adversely affected by resetting the
CPU Bus Unit.
2. To transfer routing tables for multiple nodes to a PLC in one batch, connect
the CX-Integrator to a PLC with only one Communications Unit mounted.
Routing tables cannot be transferred to other nodes from a PLC with mul-
tiple Communications Units mounted.
3. Routing tables can only be transferred as a batch to multiple nodes within
the same network as the PLC to which the CX-Integrator is connected.
3
2 1 3
3 1 1
2 0
3
3 2 2
PLC #1 (local node)
Node #1
Network #1
Node #2
PLC #2 (relay node)
PLC #3
(relay node)
Node #2
Unit #0
PLC #4 (destination node)
Node #3
Node #1
Network #2 Network #3
Node #2
Node #1
Unit #1
PLC #1
relay network table
PLC #2
relay network table
PLC #3
local network table
End network
End
network
Relay
network
Relay
node
Local
network
address
Unit
number
To go to network #3,
first go to node #3 at
network #1.
To go to network #3,
first go to node #2 at
network #2.
(To go to network #3
according to the local
network table, go
through unit
number 1 of the local
CPU Rack.)
(The network is the same,
so go to node #2 at network #3.)
End
network
Relay
network
Relay
node
124
Creating Routing Tables Section 6-4
6-4-3 Routing Table Setting Examples
Example 1: Local Network Table for a PLC With Multiple Units Mounted
This example shows the local network table settings for a PLC to which multi-
ple CPU Bus Units are mounted.
Example 2: Three Interconnected Networks
This example shows the relay network table settings for three different inter-
connected networks.
In the table for PLC #3, for example, if network #A is taken as the end net-
work, then network #B becomes the relay network and node #c becomes the
relay node. If network #C is taken as the end network, then network #B still
becomes the relay network and node #e becomes the relay node.
A
B
a
b
No.
1
2
P
S
C
P
U
C
L
K
E
T
N
Ethernet network
(Network #A)
Controller Link network
(Network #B)
Unit #a Unit #b
PS: Power Supply Unit
CPU: CPU Unit
ETN: Ethernet Unit
CLK: Controller Link Unit
Local Network Table
Local
network
CPU Bus
Unit
1
2
B
C
A
A
b
b
1 C B e
1
2
A
C
B
B
c
e
1
2
A
B
C
C
f
f
1 A B c
Relay Network Table
No.
End
network
Relay
network
Node
PLC #1
Node #a
Network #A
PLC #2
Node #b
Node #c
Node #d
PLC #3
Network #B
Network #C
Node #e
PLC #4
Node #f
Node #g
PLC #5
125
Creating Routing Tables Section 6-4
Example 3: All Nodes
This example uses the following configuration to show the routing tables for all
nodes.
PLC
5
PLC
1
E
T
N
PLC
2
C
L
K
E
T
N
PLC
3
E
T
N
S
L
K
C
PLC
4
C
PLC
6
PLC
7
L
K
L
K
S
L
K
S
L
K
Unit #5
Node #6
Network #10
Unit #4
Node #5
Network #30
Unit #0
Node #1
Unit #1
Node #2
Unit #5
Node #5
Unit #6
Node #10
Network #20
Unit #3
Node #4
Unit #2
Node #3
Unit #7
Node #15
No.
1
2
3
No.
1
2
3
010 05 020 010 004
030 010 005
No.
1
2
3
No.
1
2
3
010 03 030 010 005
No.
1
2
3
No.
1
2
3
010 04 020 010 004
No.
1
2
3
No.
1
2
3
020 00 010 020 003
030 020 003
No.
1
2
3
No.
1
2
3
020 01 010 020 003
030 020 003
No.
1
2
3
No.
1
2
3
030 05 010 030 015
020 030 015
No.
1
2
3
No.
1
2
3
030 06 010 030 015
020 030 015
020 02
030 07
PLC #1 Routing Table
(Local network table) (Relay network table)
Local
network
CPU Bus
Unit No.
End
network
Relay
network
Relay
node
PLC #2 Routing Table
PLC #3 Routing Table
PLC #4 Routing Table
PLC #5 Routing Table
PLC #6 Routing Table
PLC #7 Routing Table
(Relay network table)
(Relay network table)
(Relay network table)
(Relay network table)
End
network
Relay
network
Relay
node
End
network
Relay
network
Relay
node
End
network
Relay
network
Relay
node
End
network
Relay
network
Relay
node
(Local network table)
(Local network table)
(Local network table)
(Local network table)
(Local network table)
(Local network table)
Local
network
CPU Bus
Unit No.
Local
network
CPU Bus
Unit No.
Local
network
CPU Bus
Unit No.
Local
network
CPU Bus
Unit No.
Local
network
CPU Bus
Unit No.
Local
network
CPU Bus
Unit No.
End
network
Relay
network
Relay
node
End
network
Relay
network
Relay
node
(Relay network table)
(Relay network table)
126
Using FINS Applications Section 6-5
6-5 Using FINS Applications
6-5-1 CX-Programmer (CX-Server)
The following examples show how to connect online from a CX-Programmer
on an Ethernet network to a PLC on the Ethernet network.
System Configuration Example 1: No Routing
In this example, an online connection is made by FINS/UDP to a PLC on an
Ethernet network (PLC1 in the diagram below) from a CX-Programmer/CX-
Integrator connected to the Ethernet network.
Conditions
FINS/UDP method
IP address conversion: Automatic generation method (dynamic)
CX-Programmer's Change PLC Dialog Box
CX-Programmer/CX-Integrator
Ethernet (Network address: None)
Ethernet port
Target: PLC1
Ethernet Unit
IP address: 192.168.250.1
FINS/UDP method
Node number: 1
IP address conversion: Automatic
generation method (dynamic)
Ethernet Unit node number: 2
Ethernet Unit IP address: 192.168.250.2
Settings for target PLC (PLC1)'s Change PLC Dialog Box Setting
PLC name PLC1
Network classification Ethernet
Network Tab FINS transmission source address 0
FINS destination Network number 0
Node address 2
Frame length 2,000 bytes
Response monitor time 2 seconds
Driver Tab Workstation node address 1
Automatic generation method Not selected
IP address 192.168.250.2
(Ethernet Unit IP
address)
Port number 9600
127
Using FINS Applications Section 6-5
CX-Programmer's Unit Setup
Setup Tab
Example: Inputs to the CX-Programmer's Setup Window
Example: Change PLC Settings
Item Setting
Broadcast All ones (4.3BSD)
FINS/UDP port Default (9600)
IP address 0.0.0.0 (Use default IP address.)
Subnet mask 0.0.0.0
IP address conversion Automatic generation method (dynamic)
Baud rate Automatic detection
IP router table None
128
Using FINS Applications Section 6-5
Example: Network Settings (Network Tab)
Note When FinsGateway is selected as the network type, make sure that the frame
length is set to 2,000 bytes max.
Example: Network Settings (Driver Tab)
129
Using FINS Applications Section 6-5
System Configuration Example 2: Using Routing Tables
In this example, an online connection is made via the Ethernet to a PLC on a
Controller Link network (PLC 3 below) from a CX-Programmer/CX-Integrator
connected to the Ethernet network.
Conditions
FINS/UDP method
IP address conversion: Automatic generation method (dynamic)
CX-Programmer's Change PLC Dialog Box
CX-Programmer's Unit Setup
Setup Tab
Same as for System Configuration Example 1.
Routing Table Settings and Transfer to Each PLC
Set the routing tables with CX-Integrator, and transfer them.
1. Using CX-Integrator, connect online, and select Routing table Settings.
Then create FINS local routing tables (a local network table and a relay
network table).
Example: PLC 1 Routing Table Settings
Settings for target PLC (PLC3)'s Change PLC Dialog Box Setting
PLC name PLC3
Network classification Ethernet
Network Tab FINS destination FINS transmission
source address
1
Network number 2
Node address 3
Frame length 2,000 bytes
Response monitor time 2 seconds
Driver Tab Workstation node address 1
Automatic generation method Not selected
IP address 192.168.250.2
(Ethernet Unit IP
address)
Port number 9600
CX-Programmer/CX-Integrator
Ethernet port
Node address: 1
IP address: 192.168.250.1
Ethernet (network address 1)
Routing
according to
routing table
Controller
Link Unit
Ethernet Unit
IP address conversion: Automatic generation method (dynamic)
Gateway between networks
PLC1
Controller Link Unit
Target PLC
Controller Link Unit
Node address 2 Node address 3
Controller Link (network address 2)
PLC2
PLC3
Ethernet Unit node address: 2
Ethernet Unit IP address: 192.168.250.2
Ethernet Unit unit number: 0
Controller Link Unit node address: 1
Controller Link Unit unit number: 1
Routing to final network address 2
requires relaying through node
address 2 of relay network address
1 (Ethernet Unit).
130
Using FINS Applications Section 6-5
Local Network Table
Relay Network Table
None
Example: PLC 2 and PLC 3 Routing Table Settings
Local Network Table
Relay Network Table
In order to relay from PLC2/3 to the final network number 1, it is necessary
to relay via node address 1 (i.e., the Controller Link Unit) on relay network
number 2.
2. Save the routing table file (File - Save local routing table file).
3. Select New from the Project Menu, and save with a file name. Then select
Add Device from the Project Menu. For each PLC, register a PLC with a
direct serial connection (node address: 0), and select it.
4. With CX-Integrator, select Open from the PLC Menu.
5. Select Routing table Setup, read the saved file, and select Options
Transfer to PLC. Click Yes to transfer the routing tables to the connected
PLCs.
6-5-2 FinsGateway
FinsGateway Ver. 2003 must be used to communicate using FINS/TCP
between applications serving as communications drivers and CS1W-ETN21
or CJ1W-ETN21 Ethernet Units.
FinsGateway Ver. 3.@ or lower versions can be used, however, when commu-
nicating by the FINS/UDP method only.
Overview of Setup Methods
1. Starting FinsGateway Settings
Select FinsGateway FinsGateway Setup to start the FinsGateway Setup.
2. ETN_UNIT Driver Setup
1. Double-click on ETN_UNIT in the settings for the network and Unit. The fol-
lowing ETN_UNIT Properties Window will be displayed.
Unit number Local network number
0 1
1 2
Unit number Local network number
0 2
Final network number Relay network number Relay node address
1 2 1
131
Using FINS Applications Section 6-5
Network Tab
Communication Unit Tab
Network number Set the network number for the personal computer
(Ethernet port).
Local node address Set the personal computer (Ethernet port) node
address (1 to 254) on the Ethernet network.
Communication unit number Set the unit number in decimal (16 to 31) for the per-
sonal computer (Ethernet port).
UDP port number Set the local UDP port number for the personal com-
puter (Ethernet port). The default is 9600.
Priority Network Card If multiple Network Cards are mounted at the personal
computer, select the Network Card that is to be given
priority.
FINS - IP address conver-
sion
Set the IP address conversion method.
132
Using FINS Applications Section 6-5
UDP Nodes Tab: Automatic Generation Method (Dynamic or Passive)
UDP Nodes Tab: IP Address Table Method or Combined Method
Click the Add Button, and then set the IP address table in the following Ether-
net Node Definition Dialog Box.
133
Using FINS Applications Section 6-5
TCP Nodes Tab
Click the Add Button, and then set the IP address table in the following Ether-
net Node Definition Dialog Box.
Node address: Set the remote FINS node address.
IP address: Set the remote IP address.
134
Using FINS Applications Section 6-5
3. Starting FinsGateway ETN_UNIT Service
Select ETN_UNIT from Services under the Basic Tab in the FinsGateway
Setup Window, and then click the Start Button.
System Configuration Example 3: Connecting the CX-Programmer Online
Using the FINS/TCP Method
In this example, an online connection is made by FINS/TCP to a PLC on an
Ethernet network (PLC1 in the diagram below) from a CX-Programmer/CX-
Integrator connected to the Ethernet network.
Conditions
FINS/TCP method
CX-Programmer's Change PLC Dialog Box
Node address: Set the remote FINS node address.
IP address: Set the remote IP address.
Destination port number: Set the FINS/TCP port number for the remote node.
Normally the PLC's default setting of 9600 should be
specified.
Keep-alive setting: Sets the keep-alive function. Normally this should be
selected.
CX-Programmer/CX-Integrator
Ethernet (Network number: none)
Ethernet port
Target: PLC1
Ethernet Unit
Node number: 1
IP address: 192.168.250.1
FinsGateWay Version 2003
IP address conversion: Automatic generation method (dynamic)
Ethernet Unit node number: 2
Ethernet Unit IP address: 192.168.250.2
FINS/TCP method
Settings for target PLC (PLC1)'s Change PLC Dialog Box Setting
PLC name PLC1
Network classification FinsGateway
Network Tab FINS destination Network number 0
Node address 2
Frame length 2,000 bytes
Response monitor time 2 seconds
135
Communicating between OMRON PLCs Section 6-6
CX-Programmer's Unit Setup
Setup Tab
FINS/TCP Tab
Not set. (All defaults are used.)
FinsGateway ETN_UNIT Setup
TCP Nodes Tab: Ethernet Node Definition Dialog Box
6-6 Communicating between OMRON PLCs
FINS commands can be sent from the users ladder-diagram program in the
PLC by using the SEND(090), RECV(098), and CMND(490) instructions.
SEND(090): Writes I/O data from the local node to another node.
RECV(098): Reads I/O data from another node to the local node.
CMND(490): Issues FINS commands for controlling operations such as send-
ing and receiving I/O memory data to and from other nodes, reading informa-
tion regarding other nodes, and so on.
6-6-1 Communications Specifications
The following table shows the specifications for PLC communications using
the SEND(090), RECV(098), and CMND(490) instructions.
Item Setting
Broadcast All ones (4.3BSD)
FINS/TCP port Default (9600)
IP address 0.0.0.0 (Use default IP address.)
Subnet mask 0.0.0.0
Baud rate Automatic detection
IP router tables None
Item Setting
Node address 2
IP address 192.168.250.2
Destination port number 9600
Keep-alive setting Selected (yes)
Item Specifications
Destination 1:1 SEND(090), RECV(098), CMND(490) instructions
1:N SEND(090), CMND(490) instructions (broadcasting)
Data length SEND(090):
990 words (1,980 bytes) max.; broadcasting: 727 words (1,454
bytes)
RECV(098):
990 words (1,980 bytes) max.
CMND(490):
1,990 bytes max.; broadcasting: 1,462 bytes (after FINS com-
mand code)
136
Communicating between OMRON PLCs Section 6-6
Note 1. The maximum data length is limited to 512 bytes for data exchange be-
tween the PLC and SYSMAC LINK Systems or the PLC and SYSMAC
BUS/2 Remote I/O Systems.
2. When broadcasting, do not require a response.
Use the FINS/UDP method for broadcasting.
6-6-2 PLC Communications Data Areas
The following table shows the I/O data areas involved when SEND(090) and
RECV(098) are used.
Note 1. Data cannot be written to words A000 to A447 in the Auxiliary Area.
2. A maximum of 13 banks in the EM Area can be used. For details regarding
the EM Area, refer to the operation manual for the PLC that is used.
Data contents The following data is sent and received with the execution of
each instruction.
SEND(090):
Sends request for remote node to receive data, and receives
response data.
RECV(098):
Sends request for remote node to send data, and receives
response data.
CMND(490):
Sends any FINS command and receives response data.
Communications
port number
Ports 0 to 7 (Eight transmissions can occur simultaneously.)
Response moni-
tor time
0000:
2 s (default)
0001 to FFFF:
0.1 to 6,553.5 s in 0.1-s increments (specified by user)
Number of retries 0 to 15 retries
Item Specifications
Area Range
CIO Area CIO 0000 to CIO 6143
Work Area W000 to W511
Holding Area H000 to H511
Auxiliary Area A000 to A959 (See note 1.)
Timer Area TIM0000 to 4095
Counter Area CNT0000 to 4095
DM Area D00000 to D32767
EM Area E00000 to E32767 (See note 2.)
137
Communicating between OMRON PLCs Section 6-6
6-6-3 Using SEND(090), RECV(098), and CMND(490)
Make the settings shown below when using the SEND(090), RECV(098), and
CMND(490) instructions in the users ladder-diagram program in the PC.
SEND(090) The SEND(090) instruction sends the data in n number of words, starting from
the beginning word S at the local node, to the words starting from the begin-
ning word D at the remote destination node (node address N).
Note The message service does not guarantee that a message will reach the desti-
nation node. A message may be lost during transmission due to factors such
as noise. To prevent this from occurring when using message services, it is
common to set up retry processing at the node from which instructions are
issued. With the SEND(090), RECV(098), and CMND(490) instructions, retry
processing is executed automatically by specifying the number of retries, so
specify a number other than 0.
S
15 0
n
D
15 0
Local node
Number
of words
(n)
Destination node number N
(@)SEND(90)
S
D
C
C+1 0 0
C
15 11 8 7 0
C+2
15 11 8 7 0
15 0
C+3 0 0
C+4
15 10 8 7 3 0
S: Local node beginning word
D: Destination beginning word
C: First word of control data (below)
Number of words (n)
0001 to 03DE (Hex): 1 to 990 words
Destination network number
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Destination node number N
00 to FE (Hex): 0 to 254
The same data can be broadcast to all nodes on the network by
setting the destination node number to FF (Hex).
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
138
Communicating between OMRON PLCs Section 6-6
RECV(098) With the RECV(098) instruction, the data in m number of words, starting from
the beginning word S at the remote node (node address M) is received at the
words starting from the beginning word D at the local node.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to fac-
tors such as noise. In order to prevent this from occurring when using mes-
sage services, it is common to set up retry processing at the node from which
instructions are issued. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the num-
ber of retries, so specify a number other than 0.
D
m
15 0 15 0
S
Local node
Number
of words
(m)
Remote node number N
C+1 0 0
C+3 0 0
C+4
C
15 11 8 7 0
C+2
15 11 8 7 0
15 10 8 7 3 0 15 0
(@)RECV(98)
S
D
C
S: Remote node beginning word
D: Local beginning word
C: First word of control data (below)
Number of reception words (m)
0001 to 03DE (Hex): 1 to 990 words
Destination network number
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination Unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Remote node number M (send source)
00 to FE (Hex): 0 to 254
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
139
Communicating between OMRON PLCs Section 6-6
CMND(490) The CMND(490) instruction sends n bytes of command data, starting from the
beginning word S at the local node, to the node at node address N. the data in
m number of words, starting from the beginning word S at the remote node
(node address M) is received at the words starting from the beginning word D
at the local node.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to fac-
tors such as noise. In order to prevent this from occurring when using mes-
sage services, it is common to set up retry processing at the node from which
instructions are issued. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the num-
ber of retries, so specify a number other than 0.
S
15 0
(S1)
+
n
2
D
(D1)
+
m
2
Local node Destination node number N
Command
Response
Interpretation
Execution
Com-
mand
data: n
bytes
Re-
sponse
data: m
bytes
(@)CMND(490)
S
D
C
C+1
C
15 0
15 0
C+3
15 8 7 0
C+2 0 0
15 11 8 7 0
C+4 0 0
C+5
15 10 8 7 3 0
15 10 8 7 3 0
S: Beginning command storage word
D: Beginning response storage word
C: First word of control data (below)
Number of bytes of command data (n)
0000 to 07C6 (Hex): 1 to 1,990 bytes
Number of bytes of response data (m)
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination Unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Destination node number N
00 to FE (Hex): 0 to 254
The same data can be broadcast to all nodes on the network by
setting the destination node number to FF (Hex).
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0000 to 07C6 (Hex): 1 to 1,990 bytes
Destination network number
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
140
Communicating between OMRON PLCs Section 6-6
Commands Addressed to CS/CJ-series CPU Units
The following table provides a list of FINS commands that can be processed
by a CS/CJ-series CPU Unit. For details, refer to the CS/CJ-series Program-
mable Controllers Communications Commands Reference Manual (W342).
For details on FINS commands that can be processed by the Ethernet Unit,
refer to SECTION 7 FINS Commands Addressed to Ethernet Units.
Usage Command
code
Name Function
MR SR
I/O memory area
access
01 01 MEMORY AREA READ Reads the contents of consecutive I/O
memory area words.
01 02 MEMORY AREA WRITE Writes the contents of consecutive I/O
memory area words.
01 03 MEMORY AREA FILL Writes the same data to the specified
range of I/O memory area words.
01 04 MULTIPLE MEMORY AREA READ Reads the contents of specified non-
consecutive I/O memory area words.
01 05 MEMORY AREA TRANSFER Copies the contents of consecutive I/O
memory area words to another I/O
memory area.
Parameter area
access
02 01 PARAMETER AREA READ Reads the contents of consecutive
parameter area words.
02 02 PARAMETER AREA WRITE Writes the contents of consecutive
parameter area words.
02 03 PARAMETER AREA FILL (CLEAR) Writes the same data to the specified
range of parameter area words.
Program area
access
03 06 PROGRAM AREA READ Reads the UM (User Memory) area.
03 07 PROGRAM AREA WRITE Writes to the UM (User Memory) area.
03 08 PROGRAM AREA CLEAR Clears the UM (User Memory) area.
Operating mode
changes
04 01 RUN Changes the CPU Units operating
mode to RUN or MONITOR.
04 02 STOP Changes the CPU Units operating
mode to PROGRAM.
Machine configura-
tion reading
05 01 CPU UNIT DATA READ Reads CPU Unit data.
05 02 CONNECTION DATA READ Reads the model numbers of the device
corresponding to addresses.
Status reading 06 01 CPU UNIT STATUS READ Reads the status of the CPU Unit.
06 20 CYCLE TIME READ Reads the maximum, minimum, and
average cycle time.
Time data access 07 01 CLOCK READ Reads the present year, month, date,
minute, second, and day of the week.
07 02 CLOCK WRITE Changes the present year, month, date,
minute, second, or day of the week.
Message display 09 20 MESSAGE READ/CLEAR Reads and clears messages, and reads
FAL/FALS messages.
Access rights 0C 01 ACCESS RIGHT ACQUIRE Acquires the access right as long as no
other device holds it.
0C 02 ACCESS RIGHT FORCED ACQUIRE Acquires the access right even if
another device already holds it.
0C 03 ACCESS RIGHT RELEASE Releases the access right that has been
acquired.
Error log 21 01 ERROR CLEAR Clears errors or error messages.
21 02 ERROR LOG READ Reads the error log.
21 03 ERROR LOG POINTER CLEAR Clears the error log pointer.
141
Communicating between OMRON PLCs Section 6-6
6-6-4 Writing Programs
Programs incorporating the SEND(090), RECV(098), and CMND(490)
instructions are generally created using the Communications Port Enabled
Flag and the Communications Port Error Flag as input conditions. CS/CJ-
series CPU Units have eight communications ports. Only one instruction can
be executed at any given port at one time, however, so the program must not
overlap the use of any of the ports. A program example is provided below.
File memory 22 01 FILE NAME READ Reads file memory data.
22 02 SINGLE FILE READ Reads a specified length of file data
from a specified position within a single
file.
22 03 SINGLE FILE WRITE Writes a specified length of file data
from a specified position within a single
file.
22 04 FILE MEMORY FORMAT Formats (initializes) the file memory.
22 05 FILE DELETE Deletes specified files stored in the file
memory.
22 07 FILE COPY Copies files from one file memory to
another file memory in the same sys-
tem.
22 08 FILE NAME CHANGE Changes a file name.
22 0A MEMORY AREAFILE TRANSFER Transfers or compares data between the
I/O memory area and the file memory.
22 0B PARAMETER AREAFILE TRANSFER Transfers or compares data between the
parameter area and the file memory.
22 0C PROGRAM AREAFILE TRANSFER Transfers or compares data between the
UM (User Memory) area and the file
memory.
22 15 CREATE/DELETE DIRECTORY Creates or deletes a directory.
Debugging 23 01 FORCED SET/RESET Force-sets or force-resets bits, or
releases force-set status.
23 02 FORCED SET/RESET CANCEL Cancels all bits that have been force-set
or force-reset.
Usage Command
code
Name Function
MR SR
There are eight communications ports, so up to eight
communications instructions can be executed at a time. The
number of messages that can be sent or received with a
single CPU Bus Unit ser-vice, though, is not more than two
each for the CPU Unit to the Ethernet Unit and for the
Ethernet Unit to the CPU Unit.
Communications port
Ethernet Unit
CPU Unit
Instruction 1
Instruction 2
Instruction 3
Instruction 4
Instruction 5
Instruction 6
Instruction 7
Instruction 8
142
Communicating between OMRON PLCs Section 6-6
The execution status of the SEND(090), RECV(098), and CMND(490) instruc-
tions is always reflected by the communications flags (i.e., the Communica-
tions Port Enabled Flag and the Communications Port Error Flag). The CS/
CJ-series CPU Units communications flags are allocated in the Auxiliary Area
as shown in the following table.
Note With CS/CJ-series PLCs, communications ports 0 to 7 are also used for exe-
cuting the PCMR(260) (PROTOCOL MACRO) instruction, so these flags are
used in common for SEND(090), RECV(098), CMND(490), and PCMR(260).
While PCMR(260) is being executed, SEND(090), RECV(098), and
CMND(490) cannot be executed at the same communications port.
A
A
A
A
C
Execution
condition
Communications
Port Enabled Flag
KEEP(011) A
Reset B
Input A remains ON from start to completion of commu-
nications instruction.
Operand,
control data
created with
@MOV and
@XFER.
Creates operand and control data in a given
area.
Communications
Port Enabled Flag
DIFU(013) B
Executes communications instructions.
Communications
Port Error Flag
Reset D
Communications
Port Enabled Flag
KEEP(011) C
Creates reset input. (Turns reset B ON
after execution of communications in-
struction.)
Exclusive control so execution is not simultaneous.
Use exclusive control so that no other communica-
tions instructions are started before execution of the
above communications instruction is complete.
(Continued in same way.)
Execution
condition
Communications
instructions
@SEND
@RECV
@CMND
Send Error Flag display
(Retry can be executed.)
Flag name Address Contents
Word Bits
Communications Port
Enabled Flag
A202 Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
OFF: Execution enabled
(being executed)
ON: Execution disabled
(not being executed)
Communications Port
Error Flag
A219 Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
0: Normal completion
1: Abnormal completion
143
Communicating between OMRON PLCs Section 6-6
Communications Port
Completion Codes
The status of a SEND(090), RECV(098), and CMND(490) instruction after
execution is reflected as a communications port completion code, in one word
(two bytes) of data as shown in the following table. (The value is 0000 during
instruction execution.) The recorded status is saved until execution of the next
instruction.
The meanings of the communications port completion codes are the same as
those for FINS commands and responses. When CMND(490) is used, how-
ever, even if a FINS command has an abnormal completion, it will not be
reflected in the communications port completion code. For details, refer to
Communications Port Error Flag and Completion Codes for CMND(490)
below.
Bits 08 to 15 in the communications port completion code correspond to the
first byte of the response code, and bits 00 to 07 correspond to the second
byte. For details, refer to 8-5 Troubleshooting with Response Codes.
Communications Port Error Flag and Completion Codes CMND(490)
Errors that occur when CMND(490) is used generate a Communications Port
Error Flag and are recorded in a communications port completion code only in
the following cases:
When a response timeout error has occurred.
When the number of communications data bytes exceeds the maximum
value for the Unit (i.e., 2,000 bytes for the Ethernet Unit).
When the actual number of response bytes is greater than the number of
reception bytes that has been set. (The response is not stored in this
case.)
Errors other than these are recorded in the response codes of the responses
stored from the beginning response storage word onwards. Be careful of
these, because there are no Communications Port Error Flags and they are
not recorded in a communications port completion code.
Timing of Communications Flag Changes
The Communications Port Enabled Flag remains OFF during communica-
tions and turns ON when they are completed (regardless of whether or
not an error occurs).
The Communications Port Error Flag retains its status until the next trans-
mission or reception.
The Communications Port Error Flag turns OFF with the execution of the
next communications instruction even if there was an abnormal comple-
tion.
Word Contents
A203 Communications Port 0 Completion Code
A204 Communications Port 1 Completion Code
A205 Communications Port 2 Completion Code
A206 Communications Port 3 Completion Code
A207 Communications Port 4 Completion Code
A208 Communications Port 5 Completion Code
A209 Communications Port 6 Completion Code
A210 Communications Port 7 Completion Code
144
Communicating between OMRON PLCs Section 6-6
1
0
1
0
0000 0000 0000
Example
Communications Port Enabled Flag
Communications instruction:
SEND(090), RECV(098), CMND(490)
Communications Port Error Flag
Communications Port Completion Code
Instruction 1
being executed.
Instruction 2
being executed.
Instruction 3
being executed.
0000 (Normal completion)
0000 (Normal completion)
Completion 0202
(Unit address setting error)
145
Communicating between OMRON PLCs Section 6-6
6-6-5 Program Example
When the Communications Port Enabled Flag for port 7
is ON, and RECV(098) is not being executed, the send
execution program will start when execution condition
CIO 000000 turns ON.
Input CIO 120000 remains ON from the start of
SEND(090) execution until completion.
Control Data Creation
Contents Meaning
Number of send words = 10
Destination network number = 2
Destination node number = 4
Destination unit address = 0
Response required.
Communications port No. used = 7
Number of retries = 5
Response monitor time = 10 s
Send Data Creation
Ten words of data from word CIO 0000 is
stored from D00010 onwards.
Ten words of data from D00010 at the local node is
sent to D00020 onwards at network number 2, node
number 4, unit address 0 (the PLC).
Reset Input Creation
Send Error Display
KEEP
120000
000000 A20207 120002
120001
@MOV(21)
120000
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@XFER(70)
@SEND(90)
DIFU(13)
120000 A20207
121000
120000 A21907
Execution
condition (See note.)
(Continued on next page.)
S
R
(See note.)
00 0A
00 02
04 00
07 05
00 64
D0000
D0001
D0002
D0003
D0004
Word
#000A
D00000
#0002
D00001
#0400
D00002
#0705
D00003
#0064
D00004
#000A
0000
D00010
D00010
D00020
D00000
120001
146
Communicating between OMRON PLCs Section 6-6
Note 1. With CS/CJ-series PLCs, the Communications Port Enabled Flags at bits
0 to 7 in word A202 turn OFF even when the PCMR(260) instruction is be-
ing executed using the ports corresponding to those flags.
2. Before using the sample program as is, confirm that the memory areas
(words and bits) used in the sample program are not already being used in
the user program o r by Special I/O Units.
When the Communications Port Enabled Flag for port 7
is ON, and SEND(090) is not being executed, the trans-
mission execution program will start when execution
condition CIO 000001 turns ON.
Input CIO 120002 remains ON from the start of
RECV(098) execution until completion.
Control Data Creation
Word
Number of reception words = 16
Source network number = 3
Source node number = 32
Source unit address = 0
Response required.
Communications port No. used = 7
Number of retries = 5
Response monitor time = Default
A total of 16 words of data beginning from word A100
at network number 3, node number 32, unit address 0
(the PLC) is received at word CIO 2000 onwards of the
local node.
Reset Input Creation
Reception Error Display
Reception Data Processing
If there is no reception processing completion error, the
16 words of data received from word CIO 2000 on-
wards is stored at D00040 onwards.
KEEP
120002
000001 A20207 120000
120003
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@RECV(98)
DIFU(13)
120002 A20207
121001
120002 A21907
Execution
condition
(See note.)
(Continued from previous page.)
120002
@XFER(70)
120002 120003 A21907
(See note.)
S
R
Contents Meaning
00 10
00 03
20 00
07 05
00 00
D0005
D0006
D0007
D0008
D0009
D00040
120003
D00005
2000
A100
D00009
#0000
D00008
#0705
D00007
#2000
D00006
#0003
D00005
#0010
2000
#0016
147
Communicating between OMRON PLCs Section 6-6
6-6-6 Transmission Delays
The methods of computing the maximum time required from execution of the
SEND(090), RECV(098), and CMND(490) instructions until processing is
completed are described in this section.
SEND(090)
The transmission delay for the SEND(090) instruction can be calculated using
the following equation, which is illustrated in the following diagram.
CPU Bus Unit Service Cycle (Local Node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit:
For details, refer to the CPU Unit operation manual.
Max. delay = CPU Bus Unit service cycle (local node)
+CPU Bus Unit service processing time (local node)
+Transmission processing time
+Transmission Delays
+Reception processing time
+CPU Bus Unit service cycle (remote node)
+CPU Bus Unit service processing time (remote node)
Maximum transmission delay
CPU Bus Unit
service cycle (local node)
CPU Bus Unit service
processing time (local node)
CPU Bus Unit
service cycle (remote node)
CPU Bus Unit service
processing time (remote node)
Transmission processing time
Reception processing time
Transmission Delays
CPU data set
processing time (remote node)
SEND(090) executed
in user program
CPU execution mode Processing time considerations
Normal Mode CPU Unit cycle time
Priority peripheral ser-
vicing
Parallel processing with
synchronous memory
access
Parallel processing with
asynchronous memory
access
0.2 ms + peripheral servicing time (1 ms max. of peripheral
servicing time for each Special I/O Unit, CPU Bus Unit,
peripheral port, RS-232C port, and Inner Board)
148
Communicating between OMRON PLCs Section 6-6
CPU Bus Unit Service Processing Time (Local Node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit:
For details, refer to the CPU Unit operation manual.
Transmission Processing Time
Number of words sent x 0.002 + 0.550 ms
Transmission Delay
The transmission delay time will be as given below, depending on the baud
rate set for the Ethernet Unit. (There may be additional delays depending on
devices, such as hubs, in the network configuration.)
Reception Processing Time
Number of words sent 0.003 + 0.704 ms
CPU Bus Unit Service Cycle (Remote Node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
CPU execution mode Processing time considerations
Normal Mode Set time for peripheral servicing
(Default: 4% of CPU Unit cycle time) Priority peripheral servicing
Parallel processing with synchro-
nous memory access
Parallel processing with asynchro-
nous memory access
1 ms max.
Baud rate Delay time
100Base-TX Number of words sent 0.0013 + 0.0118 ms
10Base-T Number of words sent 0.0019 + 0.0157 ms
CPU processing
mode settings
Processing time considerations
Normal Mode CPU Unit cycle time
Priority peripheral ser-
vicing
Ethernet Unit is given
priority.
Time slice instruction execution
time
Ethernet Unit is not
given priority.
CPU Unit cycle time
Parallel processing with
synchronous memory
access
CPU Unit cycle time
Parallel processing with
asynchronous memory
access
0.2 ms + peripheral servicing time (1 ms max. of peripheral
servicing time for each Special I/O Unit, CPU Bus Unit,
peripheral port, RS-232C port, or Inner Board)
149
Communicating between OMRON PLCs Section 6-6
CPU Bus Unit Service Processing Time (Remote Node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
Note The actual operating environment can cause transmission delays larger than
those calculated with the methods given here. Among the causes of longer
delays are the following: traffic on the network, window sizes at network
nodes, traffic through the Ethernet Unit (e.g., socket servicing, FTP server
communications, etc.), and the system configuration.
Example Calculations
The following example shows calculations for sending 256 words between two
PLC nodes using SEND(090). Calculations are shown in the following table.
Conditions
Local node CPU cycle time: 10 ms
Local node CPU execution mode: Normal
Local node CPU uniform peripheral servicing time: Default (4%)
Remote node CPU cycle time: 5 ms
Remote node CPU execution mode: Normal
Remote node CPU peripheral servicing time: Default (4%)
Baud rate: 100Base-TX
CPU processing mode
settings
Processing time considerations
Normal Mode Set peripheral servicing time
Default: 4% of CPU Unit cycle time
Priority peripheral servicing Ethernet Unit is given
priority.
Time slice peripheral servicing
execution time
Ethernet Unit is not
given priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle
time)
Parallel processing with syn-
chronous memory access
Set peripheral servicing time
(Default: 4% of CPU Unit cycle time)
Parallel processing with
asynchronous memory
access
1 ms max.
Item Calculation
CPU Bus Unit service cycle (local node) 10 ms
CPU Bus Unit service processing time
(local node)
0.4 ms
Transmission processing time 256 0.002 + 0.550 = 1.062 1.1 ms
Transmission delay 256 0.0013 + 0.0118 = 0.3446
0.3 ms
Reception processing time 256 0.003 + 0.704 = 1.472 1.5 ms
CPU Bus Unit service cycle (remote node) 5 ms
CPU Bus Unit service processing time
(remote node)
0.2 ms
Total 10 + 0.4 + 1.1 + 0.3 + 1.5 + 5 + 0.2 =
18.5 ms
150
Communicating between OMRON PLCs Section 6-6
RECV(098)
The transmission delay for the RECV(098) instruction can be calculated using
the equation illustrated in the following diagram.
CPU Bus Unit Service Cycle (Local Node 1)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit:
For details, refer to the CPU Unit operation manual.
Maximum transmis-
sion delay time
CPU Bus Unit Service Cycle (local node 1)
+ CPU Bus Unit service processing time (local node
1)
+ Transmission processing time (command)
+ Transmission delay (command)
+ Reception processing time (command)
+ CPU Bus Unit Service Cycle (remote node)
+ CPU Bus Unit service processing time (remote
node)
+ Transmission processing time (response)
+ Transmission Delays (response)
+ Reception processing time (response)
+ CPU Bus Unit Service Cycle (local node 2)
+ CPU Bus Unit service processing time (local node
2)
CPU Bus Unit
service processing time (local node)
CPU Bus Unit
Service Cycle (local node)
Transmission
processing time (command)
Reception processing
time (command)
CPU Bus Unit
Service Cycle (remote node)
CPU Bus Unit
service processing time (remote node)
Reception
processing time (response)
Transmission
processing time (response)
Maximum transmission delay
Transmission Delays
(command)
Transmission Delays
(response)
CPU Bus Unit
Service Cycle (local node 2)
RECV(098) executed in user program
CPU Bus Unit
service processing time
(local node 2)
CPU data set
processing time
CPU processing mode
settings
Processing time considerations
Normal Mode CPU Unit cycle time
Priority peripheral servicing
Parallel processing with syn-
chronous memory access
0.2 ms + peripheral servicing time (1 ms max. of peripheral ser-
vicing time for each Special I/O Unit, CPU Bus Unit, peripheral
port, RS-232C port, or Inner Board)
Parallel processing with
asynchronous memory
access
151
Communicating between OMRON PLCs Section 6-6
CPU Bus Unit Service Processing Time (Local Node 1)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit:
For details, refer to the CPU Unit operation manual.
Transmission processing time (command)
Transmission Delay (Command)
The transmission delay time will be as follows, depending on the baud rate set
for the Ethernet Unit. (There may be additional delays depending on devices
such as hubs in the network configuration.)
Reception processing time (command)
CPU Bus Unit Service Cycle (Remote Node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
CPU processing mode
settings
Processing time considerations
Normal Mode Set peripheral servicing time
(Default: 4% of CPU Unit cycle time)
Priority peripheral servicing
Parallel processing with syn-
chronous memory access
1 ms max.
Parallel processing with
asynchronous memory
access
Command 0.550 ms
Response Number of words sent 0.002 + 0.550 ms
Baud rate Delay time
100Base-TX Command 0.0118 ms
Response Number of words sent 0.0013 + 0.0118 ms
10Base-T Command 0.0157 ms
Response Number of words sent 0.0019 + 0.0157 ms
Command 0.704ms
Response Number of words sent 0.003 + 0.704 ms
CPU processing mode
settings
Processing time considerations
Normal Mode CPU Unit cycle time
Priority peripheral servicing Ethernet Unit is
given priority.
Time slice instruction execution time
Ethernet Unit is not
given priority.
CPU Unit cycle time
Parallel processing with syn-
chronous memory access
CPU Unit cycle time
Parallel processing with
asynchronous memory
access
0.2 ms + peripheral servicing time (1 ms max. of peripheral ser-
vicing time for each Special I/O Unit, CPU Bus Unit, peripheral
port, RS-232C port, or Inner Board)
152
Communicating between OMRON PLCs Section 6-6
CPU Bus Unit service processing time (remote node)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
CPU Bus Unit Service Cycle (Local Node 2)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
CPU Bus Unit Service Processing Time (Local Node 2)
The processing time will be as follows, depending on the CPU processing
mode settings at the CPU Unit.
For details, refer to the CPU Unit operation manual.
Note The actual operating environment can cause transmission delays larger than
those calculated with the methods given here. Among the causes of longer
delays are the following: traffic on the network, window sizes at network
CPU processing mode
settings
Processing time considerations
Normal Mode 4% of CPU Unit cycle time
Priority peripheral servicing Ethernet Unit is
given priority.
Time slice peripheral servicing execution
time
Ethernet Unit is not
given priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle time)
Parallel processing with syn-
chronous memory access
4% of CPU Unit cycle time
Parallel processing with
asynchronous memory
access
1 ms max.
CPU processing mode
settings
Processing time considerations
Normal Mode CPU Unit cycle time
Priority peripheral servicing Ethernet Unit is
given priority.
Time slice instruction execution time
Ethernet Unit is not
given priority.
CPU Unit cycle time
Parallel processing with syn-
chronous memory access
CPU Unit cycle time
Parallel processing with
asynchronous memory
access
0.2 ms + peripheral servicing time (1 ms max. of peripheral ser-
vicing time for each Special I/O Unit, CPU Bus Unit, peripheral
port, RS-232C port, or Inner Board)
CPU processing mode
settings
Processing time considerations
Normal Mode 4% of CPU Unit cycle time
Priority peripheral servicing Ethernet Unit is
given priority.
Time slice peripheral servicing execution
time
Ethernet Unit is not
given priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle time)
Parallel processing with syn-
chronous memory access
4% of CPU Unit cycle time
Parallel processing with
asynchronous memory
access
1 ms max.
153
Precautions on High Traffic in FINS Communications Section 6-7
nodes, traffic through the Ethernet Unit (e.g., socket servicing, FTP server
communications, etc.), and the system configuration.
Example Calculations
The following example shows calculations for receiving 256 words between
two PLC nodes using RECV(098). Calculations are shown in the following
table:
Conditions
Local node CPU cycle time: 10 ms
Local node CPU processing mode: Normal
Local node CPU uniform peripheral servicing time: Default (4%)
Remote node CPU cycle time: 15 ms
Remote node CPU processing mode: Normal
Remote node CPU uniform peripheral servicing time: Default (4%)
Baud rate: 100Base-TX
6-7 Precautions on High Traffic in FINS Communications
When applications are constructed using FINS communications services,
communications errors (from multiple response timeouts) may occasionally
occur due to high traffic, depending on the system configuration and the appli-
cation programs. This section describes precautions for systems with high
traffic in FINS communications.
Conditions for High Traffic
High traffic may occur if FINS messages from multiple communicating nodes
are concentrated at a single Ethernet Unit. The Ethernet Unit and the CPU
Unit may have insufficient processing capacity for the volume of FINS mes-
sages (commands) that are coming from the network.
Item Calculations
CPU Bus Unit service cycle (local node 1) 10 ms
CPU Bus Unit service processing time (local node 1) 0.4 ms
Transmission processing time (command) 0.550 ms 0.5 ms
Transmission delay (command) 0.0118 ms 0.1 ms
Reception processing time (command) 0.704 ms 0.7 ms
CPU Bus Unit service cycle (remote node) 15 ms
CPU Bus Unit service processing time (remote node) 0.6 ms
Transmission processing time (response) 256 0.002 + 0.550 = 1.062 1.1 ms
Transmission delay (response) 256 0.0013 + 0.0118 = 0.3446 0.3 ms
Reception processing time (response) 256 0.003 + 0.704 = 1.472 1.5 ms
CPU Bus Unit service cycle (local node 2) 10 ms
CPU Bus Unit service processing time (local node 2) 0.4 ms
Total 10 + 0.4 + 0.5 + 0.1 + 0.7 + 15 + 0.6 + 1.1 + 0.3
+ 1.5 + 10 + 0.4 = 40.6 ms
154
Precautions on High Traffic in FINS Communications Section 6-7
For example, suppose that approximately 20 ms are required to process a sin-
gle FINS frame (i.e., 20 ms from the time that the command is received at the
Ethernet Unit until a response is sent). If 100 or more FINS frames (com-
mands) are received at once from multiple communicating nodes, it will take
approximately 2 seconds to send a response to the last command. If a time-
out is set at the remote node for 2 seconds or less, then a timeout will be gen-
erated. A retry will begin due to the timeout, and the traffic to the Ethernet Unit
will thus be increased even further, until ultimately the responses to all the
nodes will be too slow. At this point, the system is overloaded.
Avoiding Errors due to High Traffic
To avoid high traffic from FINS communications, the communications load
must be kept down to a reasonable level. To accomplish this, follow the proce-
dure below.
1. Specify the node where FINS frames seem to be concentrated.
2. Referring to 6-6-6 Transmission Delays, estimate the total processing time
for all of the FINS frames processed at that node.
3. Set the timeout value for all of the SEND(090), RECV(098), and
CMND(490) FINS commands at all the remote nodes to at least 1.5 times
the total processing time for all of the FINS frames.
4. As much as possible, implement communications traffic testing up to the
point of actual system operation. If any problem occurs, adjust the traffic.
5. If a commercially-available protocol analyzer can be used, then the actual
FINS frame processing time (i.e., the time from when a command is re-
ceived at the Ethernet Unit until a response is sent) can be measured un-
der high traffic conditions and the communications traffic can be further
adjusted as required.
155
SECTION 7
FINS Commands Addressed to Ethernet Units
This section describes the FINS commands that can be sent to an Ethernet Unit and the responses that are returned by the
Ethernet Unit.
7-1 Command Codes and Response Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
7-1-1 Command Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
7-1-2 Response Code List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
7-2 Socket Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7-2-1 Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
7-2-2 PLC Memory Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
7-3 Command/Response Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
7-3-1 RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
7-3-2 CONTROLLER DATA READ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
7-3-3 CONTROLLER STATUS READ. . . . . . . . . . . . . . . . . . . . . . . . . . . 161
7-3-4 INTERNODE ECHO TEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
7-3-5 BROADCAST TEST RESULTS READ . . . . . . . . . . . . . . . . . . . . . 164
7-3-6 BROADCAST DATA SEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
7-3-7 ERROR LOG READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
7-3-8 ERROR LOG CLEAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
7-3-9 UDP OPEN REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
7-3-10 UDP RECEIVE REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
7-3-11 UDP SEND REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
7-3-12 UDP CLOSE REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
7-3-13 PASSIVE TCP OPEN REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . 172
7-3-14 ACTIVE TCP OPEN REQUEST. . . . . . . . . . . . . . . . . . . . . . . . . . . 174
7-3-15 TCP RECEIVE REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
7-3-16 TCP SEND REQUEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
7-3-17 TCP CLOSE REQUEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
7-3-18 PING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
7-3-19 FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST 182
7-3-20 FINS/TCP CONNECTION STATUS READ. . . . . . . . . . . . . . . . . . 183
7-3-21 IP ADDRESS TABLE WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
7-3-22 IP ADDRESS WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7-3-23 IP ADDRESS TABLE READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
7-3-24 IP ROUTER TABLE READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
7-3-25 PROTOCOL STATUS READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
7-3-26 MEMORY STATUS READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7-3-27 SOCKET STATUS READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7-3-28 ADDRESS INFORMATION READ . . . . . . . . . . . . . . . . . . . . . . . . 196
7-3-29 IP ADDRESS READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
156
Command Codes and Response Codes Section 7-1
7-1 Command Codes and Response Codes
7-1-1 Command Code List
The command codes listed in the following table can be sent to an Ethernet
Unit.
7-1-2 Response Code List
Response codes are 2-byte codes which indicate the results of command
execution. They are returned in the response following the command code.
The first byte of a response code is the MRES (main response code), which
categorizes the results of command execution. The second byte is the SRES
(sub-response code) which specifies the results.
Command code Name Page
MRC SRC
04 03 RESET 159
05 01 CONTROLLER DATA READ 160
06 01 CONTROLLER STATUS READ 161
08 01 INTERNODE ECHO TEST 163
02 BROADCAST TEST RESULTS READ 164
03 BROADCAST DATA SEND 164
21 02 ERROR LOG READ 165
03 ERROR LOG CLEAR 166
27 01 UDP OPEN REQUEST 167
02 UDP RECEIVE REQUEST 168
03 UDP SEND REQUEST 169
04 UDP CLOSE REQUEST 171
10 PASSIVE TCP OPEN REQUEST 172
11 ACTIVE TCP OPEN REQUEST 174
12 TCP RECEIVE REQUEST 177
13 TCP SEND REQUEST 178
14 TCP CLOSE REQUEST 180
20 PING 181
30 FINS/TCP CONNECTION REMOTE
NODE CHANGE REQUEST
182
31 FINS/TCP CONNECTION STATUS
READ
183
50 IP ADDRESS TABLE WRITE 184
57 IP ADDRESS WRITE (CJ Series only) 185
60 IP ADDRESS TABLE READ 186
61 IP ROUTER TABLE READ 187
62 PROTOCOL STATUS READ 189
63 MEMORY STATUS READ 193
64 SOCKET STATUS READ 195
65 ADDRESS INFORMATION READ 196
67 IP ADDRESS READ 197
Command
code
Response
code
MRC: Main request code
SRC: Sub-request code
MRES: Main response code
SRES: Sub-response code
MRC SRC MRES SRES
157
Socket Applications Section 7-2
The MRES codes are shown in the following table along with the results they
indicate. Refer to 8-5 Troubleshooting with Response Codes for details on
response codes including the SRES.
7-2 Socket Applications
The format of the following FINS commands partially differs when the sockets
are used.
7-2-1 Format
The basic format of these commands is shown in the diagram below.
Command Code Specifies the requested process.
Socket Option For the TCP OPEN REQUEST (ACTIVE or PASSIVE), specifies whether or
not the keep-alive function is to be used. For all other commands it is dis-
abled. (Set to 0).
Socket Number Specifies the socket number for which the process is requested, from 1 to 8.
Results Storage Area Specifies the area to store the results of the requested process.
MRES Execution results
00 Normal completion
01 Local node error
02 Remote node error
03 Unit error (controller error)
04 Service not supported
05 Routing error
10 Command format error
11 Parameter error
22 Status error
23 Operating environment error
25 Unit error
Command code Name Page
MRC SRC
27 01 UDP OPEN REQUEST 167
02 UDP RECEIVE REQUEST 168
03 UDP SEND REQUEST 169
04 UDP CLOSE REQUEST 171
10 PASSIVE TCP OPEN REQUEST 172
11 ACTIVE TCP OPEN REQUEST 174
12 TCP RECEIVE REQUEST 177
13 TCP SEND REQUEST 178
14 TCP CLOSE REQUEST 180
Command
code
0 1 2 3 4 5 6 7 8 9 10 11 12
Socket option
Socket number
Results storage area Parameters
Number of bytes from
the beginning of the frame
158
Socket Applications Section 7-2
Parameters Specifies the parameters for the command code. Parameters depend on the
command being executed; for details, refer to the following pages.
7-2-2 PLC Memory Areas
The memory areas of the PLC that can be specified for results storage when
executing commands from the PC are listed in the table below. The Variable
type is set in the first byte of the results storage area. The remaining three
bytes contain the address for communications.
Addresses in the Addresses for communications column are not the same as
the actual memory addresses.
Note The variable types (area designations) given in parentheses can also be
used, allowing CV-series or CVM1 programs to be more easily corrected for
use with CS/CJ-series PLCs.
Word and Bit Addresses Three bytes of data are used to express data memory addresses of PLCs.
The most significant two bytes give the word address and the least significant
byte gives the bit number between 00 and 15.
The word address combined with the bit number expresses the bit address.
The bit number is always 00 because Ethernet Units can handle only word
data, i.e., individual bits cannot be addressed.
Word addresses for specific memory area words can be calculated by con-
verting the normal decimal word address to hexadecimal and adding it to the
first word in the Addresses for communications column in the above table. For
example, the address for communications for D00200 would be 0000 (from
above table) plus C8 (decimal 200 converted to hexadecimal), or 00C8.
Memory
area
Data type Word addresses Addresses for
communications
Variable
type
Bytes
Bit Areas Current
value of
word
CIO CIO 0000 to CIO 6143 000000 to 17FF00 B0 (80)* 2
HR H000 to H511 000000 to 01FF00 B2
A A448 to A959 01C000 to 03BF00 B3
DM Area DM D00000 to D32767 000000 to 7FFF00 82 2
EM Area Bank 0 E0_E00000 to E0_E32767 000000 to 7FFF00 A0 (90)* 2
Bank 1 E1_E00000 to E1_E32767 000000 to 7FFF00 A1 (91)*
Bank 2 E2_E00000 to E2_E32767 000000 to 7FFF00 A2 (92)*
Bank 3 E3_E00000 to E3_E32767 000000 to 7FFF00 A3 (93)*
Bank 4 E4_E00000 to E4_E32767 000000 to 7FFF00 A4 (94)*
Bank 5 E5_E00000 to E5_E32767 000000 to 7FFF00 A5 (95)*
Bank 6 E6_E00000 to E6_E32767 000000 to 7FFF00 A6 (96)*
Bank 7 E7_E00000 to E7_E32767 000000 to 7FFF00 A7 (97)*
Bank 8 E8_E00000 to E8_E32767 000000 to 7FFF00 A8 2
Bank 9 E9_E00000 to E9_E32767 000000 to 7FFF00 A9 2
Bank A EA_E00000 to EA_E32767 000000 to 7FFF00 AA 2
Bank B EB_E00000 to EB_E32767 000000 to 7FFF00 AB 2
Bank C EC_E00000 to EC_E32767 000000 to 7FFF00 AC 2
Current bank E00000 to E32767 000000 to 7FFF00 98 2
Specifies the bit position between 00 and 0F (0 to 15) for bit data.
Specifies the address of the corresponding word.
Variable type
159
Command/Response Reference Section 7-3
7-3 Command/Response Reference
This section describes the FINS commands that can be sent to Ethernet Units
and the responses to each command.
The command, response, and (where applicable) the results storage blocks
are given with the commands in graphic form as shown in the following dia-
gram. If the data is fixed, it is included in the blocks. If the data is variable, it is
described following the blocks. Each box represents 1 byte; every two boxes
represents 1 word. The following diagram shows 2 bytes, or 1 word.
The results storage format is the format used to store transfer results and data
for socket services requested with command codes 2701 to 2714.
Response codes applicable to the command are described at the end of the
command description. If any UNIX error codes are generated, these are also
described. Refer to your UNIX error symbol definition file /usr/include/sys/
errno.h for details. UNIX errors are returned in the results storage area.
Note Except for special cases, all send/receive data is in hexadecimal format.
7-3-1 RESET
Reset the Ethernet Unit.
Command Block
Response Block
Precautions
No response will be returned if the command ends normally. A response will
be returned only if an error occurs.
In some cases, send requests (SEND(192)/RECV(193) instructions) made
from the PLC to the Ethernet Unit just before execution of the RESET com-
mand may not be executed.
Except for the FINS communications service sockets, all open sockets (for
sockets services, FTP server, or mail transmission) are closed immediately
before resetting.
Response Codes
Two bytes
04 03
Command code
Response
code
04 03
Command
code
Response code Description
1001 Command too large
160
Command/Response Reference Section 7-3
7-3-2 CONTROLLER DATA READ
Reads the following data from the Ethernet model, version, IP address, sub-
net mask, FINS UDP port number, mode settings, Ethernet address.
Command Block
Response Block
Parameters
Model, Version
(Response)
The Ethernet Unit mode and version are returned as ASCII characters occu-
pying 20 bytes each (i.e., 20 characters each). If all bytes are not used, the
remaining bytes will be all spaces (ASCII 20 Hex).
Example Model: CS1W-ETN21, CJ1W-ETN21
Version: V1.20
IP Address, Subnet Mask
(Response)
The Ethernet Units IP address and subnet mask are returned as 4 bytes
each.
FINS UDP Port Number
(Response)
The Ethernet Units UDP port number for FINS is returned as 2 bytes.
Mode Setting (Response) The mode setting in the system setup is returned.
Broadcast Address Setting
0: Broadcast with host number set to all ones (4.3BSD specifications)
1: Broadcast with host number set to all zeroes (4.2BSD specifications)
IP Address Conversion Method Setting
00, 01: Automatic generation method
10: IP address table reference method
11: Combined method (IP address table reference + automatic generation)
FINS/UDP Port Number Setting
0: Default (9600)
1: Unit Setup value
05 01
Command code
05 01 20 byte 20 byte 4 byte
Subnet
mask
4 byte
FINS UDP
port number
Mode
setting
6 byte
Ethernet address Response
code
Command
code
Model Version IP address
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Bit
Broadcast address setting
IP address conversion method
UDP port No. setting for FINS
0
System setup format
0 0
TCP port No. setting for FINS/TCP
Transmission speed setting
SNTP server specification method
SMTP server specification method
POP server specification method
161
Command/Response Reference Section 7-3
FFINS/TCP Port Number Setting
0: Default (9600)
1: Unit Setup value
Baud Rate setting
0: Automatic detection
1: 10Base-T
SNTP Server Specification Method
0: IP address
1: Host name
SMTP Server Specification Method
0: IP address
1: Host name
POP Server Specification Method
0: IP address
1: Host name
System Setup Format
Ethernet Address
(Response)
The Ethernet address of the Ethernet Unit is returned. The Ethernet address
is the address marked on the label on the side of the Ethernet Unit.
Response Codes
7-3-3 CONTROLLER STATUS READ
Reads the controller status.
Command Block
Response Block
Bit address Format classification
15 14 13 12
0 0 0 0 ETN11 mode
0 0 0 1 ETN21 mode
Other Reserved
Response code Description
0000 Normal
1001 Command too large
06 01
Command code
06 01 4 byte 4 byte
Total number
of
packets sent
4 byte
Total number
of
errors sent
4 byte
Total number
of
send collisions
4 byte
Response
code
Command
code
2 byte
Error flags Total number
of
packets received
Total number
of
receive errors
162
Command/Response Reference Section 7-3
Parameters
Error Flags (Response) Indicates the operating status and errors that occurred when the Ethernet Unit
was started.
The cause of each error is listed below.
IP Address Error
All bits for the network number or host number are set to 0 or 1.
IP Address Table Error
More than 32 records exist in the IP address table.
IP Router Table Error
More than 8 records exist in an IP router table.
DNS Server Error
There is an error in the IP address setting for the DNS server.
A timeout was generated in communications with the DNS server.
Routing Table Error
Local network table contains 0 or more than 16 records.
Relay network table contains more than 20 records.
SNTP Server error
There is an error in the setting for the SNTP server host specification (i.e.,
the IP address or the host name).
A timeout was generated in communications with the SNTP server.
SMTP Server error
There is an error in the setting for the SMTP server host specification (i.e.,
the IP address or the host name).
A timeout was generated in communications with the SMTP server.
The time for verification from the POP server elapsed (when POP before
SMTP was set).
POP Server Error
There is an error in the setting for the POP server host specification (i.e.,
the IP address or the host name).
An error occurred in the POP server verification (i.e., a user name or
password setting error).
A timeout was generated in communications with the POP server.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
Bit 02: IP address error
Bit 03: IP address table error
Bit 04: IP router table error
Bit 06: Routing table error
Bit 14: Address disagreement
Bit 15: EEPROM error
Bit 05: DNS server error
Bit 11: SNTP server error
Bit 12: SMTP server error
Bit 13: POP server error
163
Command/Response Reference Section 7-3
Address Disagreement
The address conversion method was set for automatic generation, but the
node address and the last byte of the local IP address do not agree, or other
host sections are 0.
EEPROM Error
An error occurred in the EEPROM memory in the Ethernet Unit.
Total Number of Packets
Received (Response)
The total number of packets received by the Ethernet Unit is returned.
Total Number of Receive
Errors (Response)
The total number of errors detected while the Ethernet Unit was receiving is
returned. The types of error detected are short packet errors, alignment
errors, CRC errors, frame length errors (received frame: 1,515 bytes or more),
and communications controller overflow errors.
Total Number of Packets
Sent (Response)
The total number of packets sent by the Ethernet Unit is returned.
Total Number of Errors
Sent (Response)
The total number of packet errors detected while the Ethernet Unit was send-
ing is returned.
Total Number of Send
Collisions (Response)
The number of packets damaged by 16 collisions with data from other nodes
during Ethernet Unit transmissions.
Precautions
Counting of the total number of packets received, total number of receive
errors, total number of packets sent, total number of errors sent, and total
number of send collisions is discontinued when the counted value reaches the
maximum value.
Response Codes
7-3-4 INTERNODE ECHO TEST
Runs the echo test between specified nodes.
Command Block
Response Block
Response code Description
0000 Normal
1001 Command too large
08 01
Command
code
1,998 bytes max.
Test data
08 01
Response
code
Command
code
1,998 bytes max.
Test data
164
Command/Response Reference Section 7-3
Parameters
Test Data (Command,
Response)
This command specifies the data to be sent to the specified nodes. Up to
1,998 bytes can be specified. The response sends back data identical to the
data specified in the command. An abnormality is assumed if the data
returned in the response differs from the test data sent.
Precautions
The test destination node is the destination node specified in the CMND(194)
instruction operands.
Always specify the unit address of the Ethernet Unit in the CMND(194)
instruction.
Response Codes
7-3-5 BROADCAST TEST RESULTS READ
Reads the results (number of times data received) of the broadcast test.
Command Block
Response Block
Parameters
Times Received
(Response)
The number of times the data has been received normally during the broad-
cast send test is returned as a hexadecimal number. The number of times
received is cleared each time the result is read.
Response Codes
7-3-6 BROADCAST DATA SEND
Sends test data simultaneously to all nodes on the network.
Response code Description
0000 Normal
1001 Command too large
1002 Command too small (No test data)
08 02
Command
code
08 02
Times
received
Response
code
Command
code
Response code Description
0000 Normal
1001 Command too large
165
Command/Response Reference Section 7-3
Command Block
Parameters
Test Data (Command) This command specifies the data to be sent to the specified nodes. Up to
1,460 bytes can be specified.
Precautions
No response is made to this command.
When using this command, set the FINS header parameters (or the control
data for the CMND(194) instruction) as follows:
Destination node address: FF (broadcast data)
Destination unit address: FE (Ethernet Unit)
Response/no response flag: 1 (no response)
7-3-7 ERROR LOG READ
Reads the error log.
Command Block
Response Block
Parameters
Beginning Record Number
(Command)
The first record to be read. The first record number can be specified in the
range between 0000 and 003F (0 to 63 decimal) where 0000 is the oldest
record.
Number of Records
(Command, Response)
The number of records to read is specified between 0001 and 0040 (1 to 64
decimal) in the command. The response returns the actual number of records
read.
Maximum Number of
Stored Records
(Response)
The maximum number of records that can be stored in the error log. Care is
required as the error log differs according to the type of PC or CPU Bus Unit.
In an Ethernet Unit, the maximum number of stored records is fixed at 40 (64
decimal).
Number of Stored
Records (Response)
The number of records stored at the time the command is executed is
returned.
08 03
Command
code
1,460 bytes max.
Test data
21 02
Beginning
record
number
Number
of
records
Command
code
21 02
Maximum
number
of stored
records
Number
of stored
records
Number
of
records
10 bytes 10 bytes
Error log data Response
code
Command
code
Error log data
166
Command/Response Reference Section 7-3
Error Log Data
(Response)
The specified number of error log records from the beginning record number
is returned sequentially. The total number of bytes in the error log is calculated
as the number of records x 10 bytes/record. Each error log record thus com-
prises 10 bytes, configured as follows:
Error Code, Detailed Information
Details of the error stored in the record. Refer to 8-3-1 Error Log Error Codes
for details.
Minute, Second, Day, Hour, Year, Month
Indicate the time at which the error stored in the record occurred.
Precautions
If the error log contains fewer records than the number specified in the num-
ber of records parameter, all records stored in the error log at the time the
command is executed will be returned and the command executed will end
normally.
Response Codes
7-3-8 ERROR LOG CLEAR
Clears the number of records stored in the Ethernet Unit error log.
Command Block
Response Block
Response Codes
Error code Detailed
information
1st byte 10th byte
Minutes Second Day Hour Year Month
Response code Description
0000 Normal
1001 Command too large
1002 Command too small
1103 Beginning record number is out of range
110C The number of read records is 0.
21 03
Command code
21 03
Response
code
Command
code
Response code Description
0000 Normal
1001 Command too large
167
Command/Response Reference Section 7-3
7-3-9 UDP OPEN REQUEST
Requests processing to open a socket.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
UDP Socket Number
(Command)
The UDP socket number to be opened specified as 1 byte between 1 and 8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Local UDP Port Number
(Command)
The UDP port number for communications with the socket is specified as 2
bytes (0 cannot be specified). Packets received at this port are distributed to
the socket specified in the UDP socket number, and send packets are distrib-
uted from the UDP socket to this port.
The following ports for the Ethernet Unit's communications services cannot be
specified.
UDP port No. used for FINS (Default: 9600)
UDP port No. used for DNS server access (Default: 53)
UDP port No. used for SNTP server access (Default: 123)
Response Codes
Socket option
Local UDP
port number
Command code
UDP socket number
27 01
Results storage area
Response
code
Command
code
27 01
Results storage
response code
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
168
Command/Response Reference Section 7-3
Results Storage Area Response Codes
7-3-10 UDP RECEIVE REQUEST
Requests that data be sent from a UDP socket.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
UDP Socket Number
(Command)
The UDP socket number to receive data specified as 1 byte between 1 and 8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
1002 Command too small
1100 UDP socket number is out of range.
Local UDP port number is 0.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F Specified socket is already open or is being closed.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
003E Internal buffer cannot be reserved due to high receive load
(ENOBUFS).
0049 Duplicate UDP port number (EADDRINUSE).
Response code Description
Number
of reception
bytes
Timeout
value
Socket option
27 02
Command
code
UDP socket number
Results storage area
Response
code
Command
code
27 02
Source IP address Response
code
Source UDP
port number
Number of
reception
bytes
Received data
Received bytes
169
Command/Response Reference Section 7-3
Number of Reception
Bytes (Command, Results
Storage Area)
The maximum number of bytes of data to be received is given in the com-
mand. The number of bytes of data received will be stored in the results stor-
age area. Up to 1,984 bytes can be specified.
Timeout Value (Command) The maximum control time between receiving the receive request and storing
the result. If this set time limit is exceeded, the code for a timeout error will be
set as the results storage response code. The value is set in units of 0.1 s.
The timeout time will be unlimited if the value is set to 0.
Source IP Address
(Results Storage Area)
The IP address of the node sending data is stored in hexadecimal.
Source UDP Port Number
(Results Storage Area)
The port number of the node sending data.
Received Data (Results
Storage Area)
The data sent from the remote node.
Precautions
If a packet is received which contains more bytes than the number specified in
Number of reception bytes specified in the command, the specified number of
bytes will be stored and the remainder of the bytes will be discarded.
Response Codes
Results Storage Area Response Codes
7-3-11 UDP SEND REQUEST
Requests that data be received by a UDP socket.
Response code Description
0000 Normal
0105 IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 UDP socket number or number of reception bytes is out of
range.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F The specified socket is currently receiving data.
2210 The specified socket is not open.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
003E Internal buffer cannot be reserved due to high reception load
(ENOBUFS).
0066 Internal memory cannot be allocated; cannot execute service.
0080 A receive request timeout error occurred.
0081 The specified socket was closed while receiving data.
170
Command/Response Reference Section 7-3
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
UDP Socket Number
(Command)
The UDP socket number to send the data specified as 1 byte between 1 and
8.
Results Storage Area
(Command)
The area in which the result of the command execution is stored. The first byte
specifies the memory area and data type (variable type). The 2nd to 4th bytes
specify the beginning address of the results storage area. Refer to page 158
for details about the variable types and addresses that can be specified.
Destination IP Address
(Command)
The IP address of the node to which data is being sent is specified in hexa-
decimal.
Destination UDP Port
Number (Command)
The UDP port number of the node to which data is being sent.
Number of Bytes Sent
(Command, Results
Storage Area)
The number of bytes in the data sent by this command. Up to 1,984 bytes can
be specified, or up to 1,472 bytes can be specified if the broadcast address is
specified as the send destination. The results storage area stores the actual
number of bytes sent.
Send Data (Command) Specifies the data sent to the remote node.
Response Codes
Destination
UDP
port number
Number of
bytes sent
Destination IP address
Command
code
Socket option
UDP socket number
27 03
Results storage area
1984 bytes max.
Send data
Response
code
Command
code
27 03
Number of
bytes sent
Response
code
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1003 The number of bytes sent does not match the sent data
length.
171
Command/Response Reference Section 7-3
Results Storage Area Response Codes
7-3-12 UDP CLOSE REQUEST
Requests processing to close a socket.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
UDP Socket Number
(Command)
The UDP socket number to be closed specified as 1 byte between 1 and 8.
1100 UDP socket number or number of bytes sent is out of range.
The destination IP address is 0.
Local UDP port number is 0.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F Specified socket is currently sending.
2210 The specified socket is not open.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
003E Internal buffer cannot be reserved due to high reception load
(ENOBUFS).
0042 The send destination IP address is a broadcast address and
the number of bytes sent exceeds 1,472. (EMSGSIZE)
004C Incorrect network number.
Incorrect destination IP address (EADDRNOTAVAIL).
004E Incorrect destination IP address (ENETUNREACH).
No network number in IP router table.
Router incorrectly set.
0051 Router incorrectly specified.
Incorrect destination IP address (EHOSTUNREACH).
Response code Description
Command
code
Socket option
UDP socket number
27 04
Results storage area
Response
code
Command
code
27 04
Response code
172
Command/Response Reference Section 7-3
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Response Codes
Results Storage Area Response Codes
7-3-13 PASSIVE TCP OPEN REQUEST
Requests processing to open a TCP socket. The socket will wait to be con-
nected to another node.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option is specified in one byte.
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 UDP socket number is out of range.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
2210 Specified socket is not open.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
Local
TCP port
number
Timeout
value
Remote IP address Remote TCP
port number
Command
code
Socket option
TCP socket number
27 10
Results storage area
Response
code
Command
code
27 10
Remote IP address Remote
port number
Response
code
173
Command/Response Reference Section 7-3
TCP Socket Number
(Command)
The TCP socket number to be opened specified as 1 byte between 1 and 8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Local TCP Port Number
(Command)
The TCP port number for communications with the socket is specified as 2
bytes (0 cannot be specified).
The following ports used for the Ethernet Unit's communications services can-
not be specified.
TCP port No. used for FTP server (Default: 20, 21)
TCP port No. used for DNS server access (Default: 53)
TCP port No. used for SMTP server access (Default: 25)
TCP port No. used for POP server access (Default: 110)
TCP port No. used for HTTP server (Default: 80)
Timeout Value (Command) The maximum control time between receiving the open request and storing
the result. If this set time limit is exceeded, the code for a timeout error will be
set as the results storage response code. The value is set in units of 0.1 s.
The timeout time is unlimited if the value is set to 0.
Remote IP Address
(Command, Results
Storage Area)
Specify the remote nodes IP address. If all zeroes are set, no remote node is
specified and connection is awaited from any node. If any other value is set,
connection is awaited from the specified remote node. The IP address of the
connected remote node will be stored in the results storage area.
Remote Port Number
(Command, Results
Storage Area)
Specify the remote TCP port number with this command. If all zeroes are set,
no remote TCP port number is specified. If any other value is set, it specifies
the TCP port number of the remote node. The TCP port number of the con-
nected remote node will be stored in the results storage area.
Precautions
Processing varies as shown in the table below according to the specified com-
bination of remote IP address and remote TCP port number.
7 0 Bits
Keep-alive specification
0: Keep-alive disabled
1: Keep-alive enabled
Remote IP address Remote TCP port Description
0 0 All connection requests received
0 Not 0 Received only when port number
matches.
Not 0 0 Received only when IP address
matches.
Not 0 Not 0 Received only when IP address and
port number matches.
174
Command/Response Reference Section 7-3
Response Codes
Results Storage Area Response Codes
Note These errors occur only in large multilayered networks.
7-3-14 ACTIVE TCP OPEN REQUEST
Requests processing to open a TCP socket. The socket will be connected to
another node.
Command Block
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 TCP socket number is out of range.
Local TCP port number is 0.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F The specified socket (connection) is already open or is cur-
rently being opened.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
003E Internal buffer cannot be reserved due to high reception load
(ENOBUFS).
0042 (see note) An error occurred (EMSGSIZE).
0045 A communication error occurred with the remote node
(ECONNABORTED).
0049 Duplicated port numbers (EADDRINUSE).
004A (see note) An error occurred (ECONNREFUSED).
004B (see note) A communication error occurred with the remote node
(ECONNRESET).
004E (see note) A parameter error occurred at the remote IP address (ENE-
TUNREACH).
0051 (see note) A parameter error occurred at the remote IP address (EHOS-
TUNREACH).
0053 A communication error occurred with the remote node
(ETIMEDOUT). No remote exists.
0066 Internal memory cannot be allocated; cannot execute service.
0080 An open request timeout error occurred.
0081 Socket was closed during opening procedure.
0082 Connection could not be established with the specified
remote.
Local TCP
port number
Results storage area Remote IP
address
Remote TCP
port number
Command
code
Socket option
TCP socket number
27 11
175
Command/Response Reference Section 7-3
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option is specified in one byte.
TCP Socket Number
(Command)
The TCP socket number to be opened specified as 1 byte between 1 and 8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Local TCP Port Number
(Command, Results
Storage Area)
The TCP port number for communications with the socket is specified as 2
bytes. An available TCP port number is automatically assigned if 0 is speci-
fied.
The TCP port numbers allocated to the open socket are stored in the Results
Storage Area.
The following ports used for the Ethernet Unit's communications services can-
not be specified.
TCP port No. used for FTP server (Default: 20, 21)
TCP port No. used for DNS server access (Default: 53)
TCP port No. used for SMTP server access (Default: 25)
TCP port No. used for POP server access (Default: 110)
TCP port No. used for HTTP server (Default: 80)
Remote IP Address
(Command)
Specify the remote nodes IP address (must be non-zero) in hexadecimal.
Remote Port Number
(Command)
Specify the remote TCP port number (must be non-zero).
Response
code
Command
code
27 11
Local port
number
Response
code
7 0 Bits
Keep-alive specification
0: Keep-alive disabled
1: Keep-alive enabled
176
Command/Response Reference Section 7-3
Response Codes
Results Storage Area Response Codes
Note These errors occur only in large multilayered networks.
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 TCP socket number is out of range.
Remote IP address or the remote TCP port number is 0.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F The specified socket (connection) is already open or is being
opened.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
000D A parameter error occurred at the remote IP address
(EACCES).
003E Internal buffer cannot be reserved due to high receive load
(ENOBUFS).
0042 (see note) An error occurred (EMSGSIZE).
0044 Received ICMP data (ENOPROTOOPT).
0045 Local socket closed (ECONNABORTED).
0049 Duplicated port numbers (EADDRINUSE).
004A An error occurred (ECONNREFUSED).
Passive remote is not available.
004B (see note) A communication error occurred with the remote node
(ECONNRESET).
004C A parameter error occurred at the remote IP address (EAD-
DRNOTAVAIL).
A parameter was specified incorrectly.
An attempt was made to actively open local TCP port.
004E A parameter error occurred at the remote IP address
(ENETUNREACH). No network number in IP router table or
incorrect router setting.
0051 A parameter error occurred at the remote IP address
(EHOSTUNREACH). Incorrect router setting.
0053 A communication error occurred with the remote node
(ETIMEDOUT). No remote exists.
0081 Socket was closed during opening procedure.
177
Command/Response Reference Section 7-3
7-3-15 TCP RECEIVE REQUEST
Requests that data be sent from a TCP socket.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
TCP Socket Number
(Command)
The TCP socket number to receive data specified as 1 byte between 1 and 8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Number of Reception
Bytes (Command, Results
Storage Area)
The maximum number of bytes of data to be received is given in the com-
mand. The number of bytes of data received will be stored in the results stor-
age area. Up to 1,984 bytes can be specified.
Timeout Value (Command) The maximum control time between receiving the receive request and storing
the result. If this set time limit is exceeded, the code for a timeout error will be
set as the results storage response code. The value is set in units of 0.1 s.
The timeout time is unlimited if the value is set to 0.
Received Data (Results
Storage Area)
Stores the received data.
Number of
reception bytes
Results storage area Timeout
value
Command
code
Socket option
TCP socket number
27 12
Response
code
Command
code
27 12
Number of
reception bytes
Response
code
Received bytes
Received data
178
Command/Response Reference Section 7-3
Response Codes
Results Storage Area Response Codes
Note These errors occur only in large multilayered networks.
7-3-16 TCP SEND REQUEST
Requests that data be received at a TCP socket.
Command Block
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 TCP socket number or number of reception bytes is out of
range.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F The specified socket is receiving data.
2210 No connection could be established to the specified socket.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
003E Internal buffer cannot be reserved due to high receive load
(ENOBUFS).
0042 (see note) Received ICMP data (EMSGSIZE).
0044 (see note) Received ICMP data (ENOPROTOOPT).
0045 (see note) A communication error occurred with the remote node
(ECONNABORTED).
004B A communication error occurred with the remote node
(ECONNRESET).
004E (see note) Incorrect destination IP address (ENETUNREACH).
No network number in IP router table.
Router incorrectly set.
004F (see note) Received ICMP data (EHOSTDOWN).
0051 (see note) Received ICMP data (EHOSTUNREACH).
Router incorrectly set.
0053 A communications error occurred with the remote node
(ETIMEDOUT).
0066 Internal memory cannot be allocated; cannot execute service.
0080 A receive request timeout error occurred.
0081 Socket was closed while receiving.
Number of
bytes sent
Results storage area Command
code
Socket option
TCP socket number
27 13
Data sent
1,984 bytes max.
179
Command/Response Reference Section 7-3
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
TCP Socket Number
(Command)
The TCP socket number to send the data specified as 1 byte between 1 and
8.
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Number of Bytes Sent
(Command, Results
Storage Area)
The number of bytes in the data sent specified between 0 and 1,984. The
results storage area stores the actual number of bytes sent.
Data Sent (Command) Specifies the data to be sent.
Response Codes
27 13
Command
code
Response
code
Number of
bytes sent
Response
code
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1003 The number of bytes sent does not match the amount of data.
1100 The TCP socket number or number of bytes sent is out of
range.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
220F The specified socket is sending data.
2210 No connection could be established to the specified socket.
2211 High traffic at Unit; cannot execute service.
180
Command/Response Reference Section 7-3
Results Storage Area Response Codes
Note These errors occur only in large multilayered networks.
7-3-17 TCP CLOSE REQUEST
Requests processing to close a TCP socket. Other processing being carried
out is forcibly ended and a code is recorded in the results storage area.
Command Block
Response Block
Results Storage Format
Parameters
Socket Option (Command) The socket option specified as 1 byte. The setting is not valid for this com-
mand. Set to 0.
TCP Socket Number
(Command)
The TCP socket number to be closed specified as 1 byte between 1 and 8.
Response code Description
0000 Normal
0020 Connection to the remote socket was broken during transmis-
sion (EPIPE).
003E Internal buffer cannot be reserved due to high receive load
(ENOBUFS).
0042 (see note) An error occurred (EMSGSIZE).
0044 (see note) Received ICMP data (ENOPROTOOPT).
0045 (see note) A communication error occurred with the remote node
(ECONNABORTED).
004B (see note) A communication error occurred with the remote node
(ECONNRESET).
004E (see note) A parameter error occurred at the remote IP address
(ENETUNREACH).
004F (see note) Received ICMP data (EHOSTDOWN).
0051 (see note) A parameter error occurred at the remote IP address
(EHOSTUNREACH).
0053 (see note) A communication error occurred with the remote node
(ETIMEDOUT).
0081 The specified socket was closed during transmission.
Results storage area
Command
code
Socket option
TCP socket number
27 14
Response
code
Command
code
27 14
Response code
181
Command/Response Reference Section 7-3
Results Storage Area
(Command)
The area in which the results of the command execution are stored. The first
byte specifies the memory area and data type (variable type). The 2nd to 4th
bytes specify the beginning address of the results storage area. Refer to
page 158 for details about the variable types and addresses that can be spec-
ified.
Precautions
Any other processing, such as sending or receiving data, being carried out
when this close command is executed will be forcibly ended and a code will be
stored in the results storage area to indicate that this processing was forcibly
ended.
Response Codes
Results Storage Area Response Codes
7-3-18 PING
Equivalent processing to the UNIX computer PING command (see below).
Command Block
Response Block
Parameters
Destination IP Address
(Command)
The IP address (in hexadecimal) of the destination node for the PING com-
mand echo request packet.
Timeout Value (Command) The wait time for the echo reply packet. The value is set in seconds. The time-
out time is set at 20 seconds if the value is specified as 0. If the echo reply
packet is not received within the set time limit, the code for a timeout error will
be set as the results storage response code.
Response code Description
0000 Normal
0105 Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 The TCP socket number is out of range.
1101 The variable type for the results storage area is out of range.
1103 Non-zero bit address specified for the results storage area.
2210 No connection could be established to the specified socket.
2211 High traffic at Unit; cannot execute service.
Response code Description
0000 Normal
Destination IP address Timeout
value
Command
code
27 20
Response
code
Command
code
27 20
182
Command/Response Reference Section 7-3
Remarks
PING Command
The PING command runs the echoback test using the ICMP protocol. When
the PING command is executed, an echo request packet is sent to the remote
node ICMP. Correct communications are confirmed when the returned
response packet is received normally. The echo reply packet is automatically
returned by the remote node ICMP.
Response Codes
7-3-19 FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST
Requests a remote node change for the FINS/TCP connection.
The default destination IP address in a connection in which the Ethernet Unit
is used as a client is the destination IP address set under the FINS/TCP Tab
in the Unit Setup. By sending this command to the Ethernet Unit, the destina-
tion IP address for the specified connection can be changed to another IP
address.
Remote node changes can be made only for connection numbers specified as
FINS/TCP clients in the Unit Setup.
Command Block
Response Block
Parameters
FINS/TCP Connection No.
(Command)
Specifies, in two bytes, the FINS/TCP connection number (1 to 16) for which
the change is to be made.
Remote IP Address
(Command)
Specifies the remote nodes IP address (must be non-zero) in hexadecimal.
Remote Port Number
(Command)
Specifies the remote TCP port number (must be non-zero) with this com-
mand.
Response code Description
0000 Normal (echo reply received from the remote node)
0205 Timeout error
1001 Command too large
1002 Command too small
1100 Zero destination address
220F PING command currently being executed
2211 High traffic at Unit; cannot execute service.
27 30
FINS/TCP
connection No.
Command
code
Remote IP
address
Remote TCP
port number
27 30
Response
code
Command
code
183
Command/Response Reference Section 7-3
Response Codes
7-3-20 FINS/TCP CONNECTION STATUS READ
Reads the FINS/TCP connection status.
Command Block
Response Block
Parameters
FIFINS/TCP Connection
No. (Command,
Response)
Command: Specifies, in two bytes, the FINS/TCP connection number (1 to
16) for which the status is to be read.
Response: Specifies the FINS/TCP connection number (1 to 16) for which the
status was read.
Connection Service
(Response)
Specifies the service that is being used for the FINS/TCP connection as a
number.
0003: FINS/TCP server
0004: FINS/TCP client
Local IP Address
(Response)
Specifies the IP address for the local node in hexadecimal.
Local TCP Port Number
(Response)
Specifies the TCP port number for the local node.
Remote IP Address
(Response)
Specifies the IP address for the remote node in hexadecimal.
Response code Description
0000 Normal
0105 Node address setting error
Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 Connection number not set from 1 to 16
Remote IP address set to 0
Remote TCP port number set to 0
2230 Connection already established with specified remote node
2231 Specified connection number not set as FINS/TCP client in
Unit Setup
2232 Remote node change processing for specified connection
number aborted because change request received during pro-
cessing
27 31
FINS/TCP
connection No.
Command
code
Connection
service
TCP transition
27 31
Command
code
Local TCP
port number
Remote IP
address
Remote TCP
port number
Response
code
Local IP address FINS/TCP
connection
No.
184
Command/Response Reference Section 7-3
Remote TCP Port Number
(Response)
Specifies the TCP port number for the remote node.
TCP Transitions
(Response)
Specifies the TCP connection status using the following numbers.
For details on TCP status changes, refer to Appendix C TCP Status Transi-
tions.
Response Codes
7-3-21 IP ADDRESS TABLE WRITE
Writes the IP address table.
Command Block
Response Block
Parameters
Number of Records
(Command)
The number of records to write is specified in hexadecimal between 0000 and
0020 (0 to 32 decimal) in the command. If this value is set to 0, the IP address
table will be cleared so that no records are registered.
Number Status Meaning
00000000 CLOSED Connection closed.
00000001 LISTEN Waiting for connection.
00000002 SYN SENT SYN sent in active status.
00000003 SYN RECEIVED SYN received and sent.
00000004 ESTABLISHED Already established.
00000005 CLOSE WAIT FIN received and waiting for completion.
00000006 FIN WAIT 1 Completed and FIN sent.
00000007 CLOSING Completed and exchanged FIN. Awaiting ACK.
00000008 LAST ACK FIN sent and completed. Awaiting ACK.
00000009 FIN WAIT 2 Completed and ACK received. Awaiting FIN.
0000000A TIME WAIT After closing, pauses twice the maximum seg-
ment life (2MSL).
Response code Description
0000 Normal
0105 Node address setting error
Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 Connection number not set from 1 to 16
Number
of records
IP address
table records
Command
code
27 50
IP address
table records
6 bytes 6 bytes
Command
code
Response
code
27 50
185
Command/Response Reference Section 7-3
IP Address Table Records
(Command)
Specify the IP address table records. The number of records specified must
be provided. The total number of bytes in the IP address table records is cal-
culated as the number of records 6 bytes/record. The configuration of the
6 bytes of data in each record is as shown in the following diagram.
FINS Node Address
Node address for communications via the FINS command (hexadecimal).
IP Address
IP address used by TCP/IP protocol (hexadecimal).
Precautions
The new I/O address table records will not be effective until the PC is
restarted or the Ethernet Unit is reset.
An error response will be returned if the IP address conversion method in the
system mode settings is set for automatic generation.
Response Codes
7-3-22 IP ADDRESS WRITE
Write the local IP address and the subnet mask in the CPU Bus Unit System
Setup.
Command Block
Response Block
FINS node
number
1
00
IP address
6 bytes
Response code Description
0000 Normal (echo reply received from the remote node)
1001 Command too large
1002 Command too small
1003 The number of records specified does not match the sent data
length.
110C The number of records is not between 0 and 32.
The FINS node address is not between 1 and 126
The IP address is 0.
2307 IP address conversion method is set for automatic generation.
27 57
Subnet mask IP address Command
code
27 57
Command
code
Response
code
186
Command/Response Reference Section 7-3
Parameters
IP Address (Command) Specify the local IP address of the Ethernet Unit using 4 pairs of hexadecimal
numbers in the range 00.00.00.00 to FF.FF.FF.FF (0.0.0.0. to
255.255.255.255 decimal). If 0.0.0.0 is specified, the local IP address set in
the allocated words in the DM Area is enabled.
Example: 150.31.2.83
Subnet Mask (Command) Specify the local IP address of the Ethernet Unit using 4 pairs of hexadecimal
numbers in the range 00.00.00.00 to FF.FF.FF.FF (0.0.0.0. to
255.255.255.255 decimal).
Example: 255.255.255.255
Response Codes
Precautions
The local IP address and subnet mask set using this mask are written to the
CPU Bus Unit System Setup for the Ethernet Unit.
The new local IP address and subnet mask settings will not be effective until
the PC is restarted or the Ethernet Unit is reset.
7-3-23 IP ADDRESS TABLE READ
Reads the IP address table.
Command Block
Response Block
Parameters
Number of Records
(Command, Response)
The number of records to read is specified between 0000 and 0020 (0 to 32
decimal) in the command. If this value is set to 0, the number of stored
records is returned but the IP address table records are not returned. The
response returns the actual number of records read.
96 53 1F 02
FF 00 FF FF
Response code Description
0000 Normal
1001 Command too large
1002 Command too small
Number of
records
Command
code
27 60
Maximum
number
of stored
records
Number
of stored
records
Number
of records
IP address
table records
Response
code
Command
code
27 60
IP address
table records
6 bytes 6 bytes
187
Command/Response Reference Section 7-3
Maximum Number of
Stored Records
(Response)
The maximum number of records that can be stored in the IP address table is
returned. The maximum number of stored records is fixed at 0020 (32
records).
Number of Stored
Records (Response)
The number of IP address table records stored at the time the command is
executed is returned as a hexadecimal number.
IP Address Table Records
(Response)
The number of IP address table records specified in the number of records
parameter is returned. The total number of bytes in the IP address table
records is calculated as the number of records 6 bytes/record. The configu-
ration of the 6 bytes of data in each record is as shown in the following dia-
gram.
FINS Node Address
Node address for communications via the FINS command (in hexadecimal).
IP Address
IP number used by TCP/IP protocol (in hexadecimal).
Precautions
If the IP address table contains fewer records than the number specified in the
number of records parameter, all the records contained in the IP address table
when the command is executed will be returned and the command execution
will end normally.
An error response will be returned if the IP address conversion method in the
system mode settings is set to the automatic generation method.
Response Codes
7-3-24 IP ROUTER TABLE READ
Reads the IP router table.
Command Block
FINS node
number
1
00
IP address
6 bytes
Response code Description
0000 Normal
1001 Command too large
1002 Command too small
2307 IP address conversion method is set to the automatic genera-
tion method.
Number
of records
Command
code
27 61
188
Command/Response Reference Section 7-3
Response Block
Parameters
Number of Records
(Command, Response)
The number of records to read is specified between 0000 and 0008 (0 to 8
decimal) in the command. If this value is set to 0, the number of stored
records will be returned but the IP router table records will not be returned.
The response returns the actual number of records read.
Maximum Number of
Stored Records
(Response)
The maximum number of records that can be stored in the IP router table is
returned. The maximum number of stored records is fixed at 0008 (8 records).
Number of Stored
Records (Response)
The number of IP router table records stored at the time the command is exe-
cuted is returned in hexadecimal.
IP Router table Records
(Response)
The number of IP router table records specified in the number of records
parameter is returned. The total number of bytes in the IP router table records
is calculated as the number of records 8 bytes/record. The configuration of
the 8 bytes of data in each record is shown below.
IP Network Address
The network ID from the IP address in hexadecimal. The network ID part cor-
responding to the address class (determined by the leftmost 3 bits) set here,
is enabled. (Refer to page 49.)
Router IP Address
The IP address (in hexadecimal) of a router connected to a network specified
with IP addresses.
Precautions
If the IP router table contains fewer records than the number specified in the
number of records parameter, all the records contained in the IP router table
when the command is executed will be returned and the command execution
will end normally.
Response Codes
Maximum
number
of stored
records
Number
of stored
records
Number
of records
IP router
table records
Response
code
Command
code
27 61
IP router
table records
8 bytes 8 bytes
IP Network address
(Network ID)
Router IP address
1 8 bytes
Response code Description
0000 Normal
1001 Command too large
1002 Command too small
189
Command/Response Reference Section 7-3
7-3-25 PROTOCOL STATUS READ
Reads the Ethernet Unit protocol status.
Command Block
Response Block
Parameters
IP Status (Response) Twelve types of IP status information occupying 4 bytes each are returned in
the following sequence. Each value is returned as an 8-digit hexadecimal
value.
1,2,3... 1. Total number of IP packets received.
2. The number of IP packets discarded due to an error with the checksum in
the packet header.
3. The number of IP packets discarded because the received packet was
larger than the overall packet length value in the packet header.
4. The number of IP packets discarded because the minimum size of the IP
header data could not be stored in the first short buffer (See note.) when
an attempt was made to store the packet. Refer to 7-3-26 MEMORY STA-
TUS READ and Appendix B Buffer Configuration.
5. The number of packets discarded for one of the following reasons:
The IP header length value in the IP header was smaller than the
smallest size of the IP header.
The size of the first short buffer (See note.) was smaller than the IP
header length value in the IP header when storing the packet.
6. The number of IP packets discarded because the IP header length was
larger than the overall packet length value in the packet header.
7. The number of fragmented packets received.
8. The number of received fragmented IP packets discarded because a
queue for reassembly could not be secured.
9. The number of fragmented IP packets discarded because they could not
be reassembled within 12 seconds after being received.
10. Always 0.
11. The number of packets addressed to other networks that have been dis-
carded.
12. Always 0.
Note Refer to 7-3-26 MEMORY STATUS READ for details on the short buffer.
27 62
Command
code
27 62
IP status ICMP status TCP status UDP status Response
code
Command
code
48 bytes 184 bytes 184 bytes 12 bytes
190
Command/Response Reference Section 7-3
ICMP Status (Response) Ten types (46 items) of ICMP status information occupying 4 bytes each are
returned in the following sequence. Each value is returned as an 8-digit hexa-
decimal value.
1,2,3... 1. The number of times the ICMP error routine was called. The ICMP error
routine uses ICMP packets to inform the source about errors. The routine
is called when an illegal packet is received (error in IP option processing
or error in relay processing) or if the object port does not exist when using
UDP.
2. Always 0.
3. Always 0.
4. Total number of outputs of each packet type during ICMP output. The 19
statistical values are returned in the order shown below. Contents are de-
fined for 13 types only; all other types contain 0. Only #0, #3, #14, #16, and
#18 are counted by the Ethernet Unit.
5. The number of received ICMP packets discarded because the type-indica-
tion code was out of range.
6. The number of received ICMP packets discarded because the overall
packet length value in the packet header was smaller than the minimum
ICMP packet length.
7. The number of received ICMP packets discarded because of an incorrect
checksum value in the packet header.
8. The number of received ICMP packets discarded because the ICMP head-
er length value in the packet header did not match the lengths of individual
header types.
9. The number of responses returned to received ICMP packets requiring a
response.
10. Total number of inputs of each packet type during ICMP input. The 19 sta-
tistical values are returned in the order shown below. Contents are defined
for 13 types only; all other types contain 0.
Type number Description
#0 Echo reply
#1, #2 Undefined, always 0
#3 Destination unreachable
#4 Source quench
#5 Routing redirect
#6, #7 Undefined, always 0
#8 Echo
#9, #10 Undefined, always 0
#11 Time exceeded
#12 Parameter problem
#13 Time stamp
#14 Time stamp reply
#15 Information request
#16 Information request reply
#17 Address mask request
#18 Address mask reply
#0 #1 #2 #3 #4 #5 #15 #16 #17 #18
4 bytes
191
Command/Response Reference Section 7-3
TCP Status (Response) Three types (46 items) of TCP status information occupying 4 bytes each are
returned in the following sequence. Each value is returned as an 8-digit hexa-
decimal value.
1) Connection Information (60 Bytes)
Fifteen items are returned in the following sequence:
1,2,3... 1. The number of times active connections were correctly established.
2. The number of times a SYN packet was received while waiting to establish
a passive connection.
3. The number of times active or passive connections were correctly estab-
lished.
4. The number of times an established connection was cut off.
5. The number of times the connection wait status was cut off.
6. The number of times protocol control blocks or other actively allocated
structures were released.
7. The number of segments for the round-trip time (time from segment trans-
mission to ACK).
8. The number of times the round-trip time was changed.
9. The number of times a delayed acknowledgement (ACK) was sent. If the
order of the received segments is reversed, ACK is sent with a packet of
data separate from ACK (response to input data, etc.) or is immediately
sent with the ACK for other data.
10. The number of times the connection was cut off because no ACK was re-
turned after several resend attempts.
11. The number of times no ACK was returned within the resend timer set time.
(The resend timer sets the maximum time limit between the data being out-
put and ACK being returned.)
Type number Description
#0 Echo reply
#1, #2 Undefined, always 0
#3 Destination unreachable
#4 Source quench
#5 Routing redirect
#6, #7 Undefined, always 0
#8 Echo
#9, #10 Undefined, always 0
#11 Time exceeded
#12 Parameter problem
#13 Time stamp
#14 Time stamp reply
#15 Information request
#16 Information request reply
#17 Address mask request
#18 Address mask reply
#0 #1 #2 #3 #4 #5 #15 #16 #17 #18
4 bytes
192
Command/Response Reference Section 7-3
12. The number of times no window advertisement is received within the time
set on the duration timer. (The duration timer sets the maximum time limit
for a window advertisement to be received if the transmission window is
smaller than necessary and the resend timer is not set. If no window ad-
vertisement is received within the time limit, the number of segments per-
mitted by the transmission window are sent. If the transmission window is
set to 0, a window probe (1 octet of data) is sent before the timer restarts.)
13. The number of times no segment was sent or received within the time set
on the hold timer.
14. The number of times the hold packet is resent. (Always 0.)
15. The number of times the hold packet is sent without response before the
connection is cut off.
2) Send Information (40 Bytes)
Ten information items are returned in the following sequence:
1,2,3... 1. The total number of packets sent.
2. The number of data packets sent.
3. The number of data bytes sent.
4. The number of data packets resent.
5. The number of data bytes resent.
6. The number of ACK packets sent.
7. The number of window probes (1 octet of data) sent.
8. The number of emergency data packets sent. (Always 0.)
9. The number of window advertisement packets sent.
10. The number of control packets (SYN, FIN, RST) sent.
3) Receive Information
Twenty-one information items are returned in the following sequence:
1,2,3... 1. The total number of packets received.
2. The number of packets received continuously.
3. The number of bytes received continuously.
4. The number of received packets discarded due to an incorrect checksum.
5. The number of packets discarded because the TCP header was smaller
than the minimum size for a TCP header or was larger than the IP packet.
6. The number of packets discarded because the TCP header and IP header
could not be stored in the first short buffer.
7. The number of resent packets received.
8. The number of bytes in the resend packets.
9. The number of duplicated resend packets received.
10. The number of bytes in the duplicated resend packets received.
11. The number of out-of-range data packets received. (Always 0.)
12. The number of bytes in the out-of-range data packets received. (Always 0.)
13. The number of packets where the data was larger than the window.
14. The number of bytes in the packets where the data was larger than the win-
dow.
15. The number of packets received after closing.
16. The number of window probe packets received.
17. The number of resent ACK packets received.
193
Command/Response Reference Section 7-3
18. The number of ACK packets received with no data set.
19. The number of ACK packets received.
20. The number of ACK packets received for received transmission acknowl-
edgements (ACK).
21. The number of window advertisement packets received.
UDP Status (Response) Three items of UDP information occupying 4 bytes each are returned in the
following sequence. Each value is returned as an 8-digit hexadecimal value.
1,2,3... 1. The number of packets discarded because the size of the first short buffer
was smaller than the minimum size (28) of the IP header and UDP header
when the packet was stored.
2. The number of packets discarded due to an incorrect checksum in the UDP
header.
3. The number of packets discarded because the IP overall length in the IP
header was shorter than the UDP overall length in the UDP header.
Precautions
All the above values are set to 0 if network operation stops due to incorrect
settings in the system setup.
Counting will be stopped when a count reaches the maximum value. The
maximum values are as follows:
IP, ICMP, or UDP status: 7FFFFFFF (2,147,483,647 decimal)
TC status: FFFFFFFF (4,294,967,295 decimal)
Response Codes
7-3-26 MEMORY STATUS READ
Reads the status of the Ethernet Units network memory. The network mem-
ory contains 248K bytes that are used as required as for communications
buffers for communications servicing. The network memory consists of 1,472
short buffers (128 bytes each) and 64 long buffers (1,024 bytes each). Refer
to Appendix B Buffer Configuration.
Command Block
Response Block
Response code Description
0000 Normal
1001 Command too large
27 63
Command
code
Memory status Response
code
Command
code
27 63 92 bytes
194
Command/Response Reference Section 7-3
Parameters
Memory Status
(Response)
A total of 23 data items in six areas are returned in the following order. Each
item consists of 4 bytes.
1,2,3... 1. Short Buffer Application: Two items are returned (8 bytes).
a. The number of short buffers currently being used.
b. The number of short buffers in the system (fixed at 1,472 decimal).
2. Short Buffer Application by Type: Thirteen items are returned (52 bytes).
a. The number of short buffers used for storing communications data
b. The number of short buffers used for protocol headers (TCP, UDP, IP,
ICMP, ARP)
c. The number of short buffers used in socket structures
d. The number of short buffers used as protocol control blocks
e. The number of short buffers used for routing tables
f. Not used (always 0)
g. Not used (always 0)
h. The number of short buffers used for IP fragment re-assembly queue
headers
i. The number of short buffers used for storing socket addresses
j. Not used (always 0)
k. The number of short buffers used for storing socket options
l. The number of short buffers used for storing access rights
m. The number of short buffers used for storing interface addresses
3. Long Buffer Application: Two items are returned (8 bytes).
a. The number of long buffers currently being used.
b. The number of long buffers in the system (fixed at 64 decimal).
4. Not Used: Always 0. (4 bytes)
5. Network Memory Application: Two items are returned.
a. The number of bytes used (in K bytes)
b. The percentage used
6. Memory Exhaustion Log (12 bytes)
Counts for the following values indicate a high load on the Ethernet Unit.
These high loads may be caused by problems in communications, partic-
ularly FINS communications and UDP sockets. If these values are consis-
tently high, check your applications.
a. The number of times an attempt was made to secure a short buffer
without WAIT when there were no short buffers available.
b. The number of times an attempt was made to secure a short buffer
with WAIT when there were no short buffers available.
c. The number of times an attempt was made to release and secure a
short buffer already being used by another socket when there were no
short buffers available.
Precautions
All the above values are set to 0 if Ethernet communications functions are
stopped due to improper settings in the system setup.
These values are cleared when the Ethernet Unit is started or reset. Values
will be counted only until the maximum values are reached.
195
Command/Response Reference Section 7-3
Response Codes
7-3-27 SOCKET STATUS READ
Reads the Ethernet Unit network socket status.
Command Block
Response Block
Parameters
Socket Status (Response) Returns eight types of information in records of 32 bytes each. A maximum of
62 records can be returned. The format of each record is shown below.
Protocol (4 bytes)
The protocol used for the socket is returned as a number.
00 00 00 06: TCP; 00 00 00 11: UDP
Receive Queue (4 bytes)
The number of bytes in the reception queue.
Send Queue (4 bytes)
The number of bytes in the send queue.
Local IP Address (4 bytes)
The local IP address allocated to the socket.
Local Port Number (4 bytes)
The local port number allocated to the socket.
Remote IP Address (4 bytes)
The remote IP address allocated to the socket.
Remote Port Number (4 bytes)
The remote port number allocated to the socket.
Response code Description
0000 Normal
1001 Command too large
27 64
Command
code
27 64
Socket status Response
code
Command
code
32 bytes 32 bytes
Socket status
196
Command/Response Reference Section 7-3
TCP Transitions (4 bytes)
The TCP connection status is returned as one of the numbers shown in the
following table. Refer to Appendix C TCP Status Transitions for a diagram of
transitions.
Precautions
All the above values are set to 0 if Ethernet communications functions are
stopped due to improper settings in the system setup.
Response Codes
7-3-28 ADDRESS INFORMATION READ
Reads FINS node addresses and IP addresses
Command Block
Response Block
Parameters
Number of Addresses (Response)
The number of pairs of FINS node addresses and IP addresses being
returned. The Ethernet Unit is always 0001 (1 decimal).
Address Information
Pairs of FINS node addresses and IP addresses. Each pair requires 6 bytes
and has the following configuration.
Number Stage Status
00 00 00 00 CLOSED Closed.
00 00 00 01 LISTEN Waiting for connection.
00 00 00 02 SYN SENT SYN sent in active status.
00 00 00 03 SYN RECEIVED SYN received and sent.
00 00 00 04 ESTABLISHED Already established.
00 00 00 05 CLOSE WAIT Received FIN, waiting to close.
00 00 00 06 FIN WAIT 1 Completed and FIN sent.
00 00 00 07 CLOSING Completed and exchanged FIN. Awaiting ACK.
00 00 00 08 LAST ACK FIN sent and completed. Awaiting ACK.
00 00 00 09 FIN WAIT 2 Close completed and ACK received. Awaiting FIN.
00 00 00 0A TIME WAIT After closing, pauses twice the maximum segment
life (2MSL).
Response code Description
0000 Normal
1001 Command too large
27 65
Command
code
27 65
Number
of addresses
Address
information
Response
code
Command
code
6 bytes
197
Command/Response Reference Section 7-3
FINS Node Address
Node address set on the Ethernet Unit (hexadecimal).
IP Address
IP address set on the Ethernet Unit (hexadecimal).
Response Codes
7-3-29 IP ADDRESS READ
Reads the local IP address and subnet mask in the CPU Bus Unit System
Setup and the FINS node address. The values read with this command, how-
ever, are not necessarily the settings actually used for operation. The settings
that are actually used for operation can be confirmed using CONTROLLER
DATA READ (page 160) and ADDRESS INFORMATION READ (page 196).
This command is supported for CJ-series Ethernet Units only.
Command Block
Response Block
Parameters
Number of Addresses (Response)
The number of sets of FINS node addresses, IP addresses, and subnet
masks being returned. The Ethernet Unit is always 0001 (1 decimal).
FINS Node Address (Response)
Node address set on the Ethernet Unit (hexadecimal).
IP Address (Response)
The local IP address set in the CPU Bus Unit System Setup for the Ethernet
Unit is returned in order starting from the leftmost bytes in hexadecimal. If the
local IP address set in the allocated words in the DM Area is enabled, 0.0.0.0
is returned.
FINS node
number
1
00
IP address
6 bytes
Response code Description
0000 Normal
1001 Command too large
27 67
Command
code
Number of
addresses
Response
code
Command
code FINS
node number
27 67 00
IP address Subnet mask
198
Command/Response Reference Section 7-3
Subnet Mask (Response)
The subnet mask set in the CPU Bus Unit System Setup for the Ethernet Unit
is returned in order starting from the leftmost bytes in hexadecimal.
Response Codes
Response code Description
0000 Normal
1001 Command too large
199
SECTION 8
Troubleshooting
This section describes information and procedures that can be used to troubleshoot problems that sometimes occur with
Ethernet Unit and Ethernet communications.
The Ethernet Unit makes up part of a network. Repair a defective Ethernet Unit as soon as possible as it can have a negative
effect on the entire network. We recommend that customers keep one or more spare Ethernet Units to allow immediate
recovery of the network.
8-1 Troubleshooting with Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8-2 Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
8-3 Error Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
8-3-1 Error Log Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
8-4 Troubleshooting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8-4-1 Startup Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
8-4-2 FINS Communications Problems
(SEND(090)/RECV(098)/CMND(490)) . . . . . . . . . . . . . . . . . . . . . 210
8-4-3 UDP Socket Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
8-4-4 TCP Socket Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
8-4-5 FTP Service Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
8-4-6 Network Connection Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
8-5 Troubleshooting with Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
8-6 Results Storage Area Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
200
Troubleshooting with Indicators Section 8-1
8-1 Troubleshooting with Indicators
The indicators on the Ethernet Unit can be used to troubleshoot some error.
The probable cause and correction for errors that can be determined from the
LINK, HOST, RUN, ERC, and ERH indicators are listed in the following table.
RUN ERC ERH LNK HOST Probably cause Correction
Not lit Not lit Not lit --- --- Power is not being supplied to the CPU
Unit or the power supply voltage is too
low.
Supply power.
Make sure that the correct voltage is
being supplied.
The Ethernet Unit is faulty. Replace the Ethernet Unit.
The CPU Unit or Backplane is faulty. Replace the CPU Unit or the Back-
plane.
The mounting screws on the Ethernet
Unit are loose (CS Series) or the sliders
are not properly locked into place (CJ
Series).
Tighten the mounting screws to the
specified torque (CS Series) or lock
the sliders into place (CJ Series).
Not lit Lit Not lit --- --- The node address is set outside the cor-
rect range on the rotary switches.
Set the node address to between 01
and FE Hex.
The Ethernet Unit is faulty. Restart the PLC. If the problem per-
sists, replace the Ethernet Unit.
Not lit Not lit Lit --- --- The unit number on the Ethernet Unit is
not set correctly on the rotary switch.
Correct the unit number setting.
The I/O tables are not registered in the
CPU Unit.
Register the I/O tables.
The same unit number is being used on
another Unit as well.
Correct the unit number.
The CPU Unit is faulty. Restart the CPU Unit. If the problem
persists, replace the CPU Unit.
Lit --- --- Not lit --- There is no communications link with the
hub.
If power is not turned ON to the hub,
turn it ON.
If there is crossed cable between the
Ethernet Unit and the hub, use
straight cable.
Lit --- Lit --- --- There is a mistake in the Unit Setup or
routing tables.
Read the error history and correct
the data that is causing the error. If
the problem persists, replace the
CPU Unit.
Memory in the CPU Unit is faulty. Restart the CPU Unit. If the problem
persists, replace the CPU Unit.
The CPU Unit is faulty. Restart the CPU Unit. If the problem
persists, replace the CPU Unit.
Lit There is a mistake in the settings for a
server (DNS, SMTP, POP3, or SNTP) in
the Unit Setup.
Read the error status and history
and correct the data that is causing
the error. If the problem persists,
replace the CPU Unit.
Not lit --- Lit An error occurred in communications with
the server.
Inspect the communications path
(Ethernet Unit, cable connections,
hub, router, server), and correct the
situation that is causing the error.
Lit Lit --- --- --- An error occurred in EEPROM. Restart the PLC. If the problem per-
sists, replace the Ethernet Unit.
201
Error Status Section 8-2
8-2 Error Status
The Ethernet Unit will output error status to the following word in the CIO Area
of the CPU Unit. This information can be used in troubleshooting errors.
Word = CIO 1500 + (25 x unit number) +18
Error Status (Ethernet Unit
to CPU Unit)
The status of errors that occur at the Ethernet Unit is reflected as shown in the
following diagram.
Lit --- Flash-
ing
--- --- The IP address is set incorrectly. Correct the IP address. Do not set
any of the following IP addresses.
Host IDs that are all 0 or all 1.
Network IDs that are all 0 or all 1.
Subnetwork IDs that are all 1.
Addresses beginning with 127 (7F
Hex).
The node address set on the rotary
switch on the front of the Unit does not
agree with the host ID in the IP address.
This probably can occur when the
address conversion method is set for
automatic address generation.
Make sure that the node address
and the last byte of the IP address
are the same and set other host IDs
to 0.
Change the address conversion
method.
Flash-
ing
--- --- --- --- The Unit operation mode change function
is in effect.
Set the node address correctly.
RUN ERC ERH LNK HOST Probably cause Correction
Bit Error Status Manipulated by Unit operation
0 to 1 (Not used.) --- --- ---
2 IP address setting error ON Unit ON if any of the following conditions apply to the IP
address.
All bits in the host ID are 0 or 1.
All bits in the network ID are 0 or 1.
All bits in the subnet ID are 1.
The IP address begins with 127 (0x7F).
OFF Unit OFF when the IP address is normal.
3 IP address table error ON Unit On if the IP address table information is incorrect.
OFF Unit OFF when the IP address table is normal.
4 IP router table error ON Unit ON if the IP router table information is incorrect.
OFF Unit OFF when the IP address table is normal.
Bit 02: IP address setting error
Bit 03: IP address table error
Bit 04: IP router table error
Bit 06: Routing table error
Bit 11: SNTP server error
Bit 12: SMTP server error
Bit 13: POP server error
Bit 14: Address disagreement
n+18
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Bit 05: DNS server error
Bit 15: EEPROM error
202
Error Log Section 8-3
8-3 Error Log
The Ethernet Unit provides an error log that records errors that have occurred
during Ethernet Unit operation. The contents of the error log can be read or
cleared from a Programming Device, such as the CX-Programmer, or it can
be read or cleared using FINS commands from a workstation or computer.
(See 7-3-7 ERROR LOG READ and 7-3-8 ERROR LOG CLEAR).
Logged Errors The following errors are recorded in the error log.
Errors in network operation
Errors in data transfers
Error in the CPU Unit
5 DNS server error ON Unit ON when the following errors occur during DNS server
operation:
An illegal server IP address is set.
A timeout occurs during communications with the
server.
OFF Unit OFF when DNS server operation is normal.
6 Routing table error ON Unit ON if the routing table information is incorrect.
OFF Unit OFF when the routing table is normal.
7 to 10 (Not used.) --- --- ---
11 SNTP server error ON Unit ON when the following errors occur during SNTP server
operation:
An illegal server IP address or host name is set.
A timeout occurs during communications with the
server.
OFF Unit OFF when SNTP server operation is normal.
12 SMTP server error ON Unit ON when the following errors occur during SMTP server
operation:
An illegal server IP address or host name is set.
A timeout occurs during communications with the
server.
The verification time from the server has expired (when
POP before SMTP is set).
OFF Unit OFF when SMTP server operation is normal.
13 POP server error ON Unit ON when the following errors occur during POP server
operation:
An illegal server IP address or host name is set.
A server verification error (user name or password)
occurs.
A timeout occurs during communications with the
server.
OFF Unit OFF when use of the POP server is normal.
14 Address disagreement ON Unit ON if the remote IP address is set to automatic genera-
tion but the local IP address host number and FINS
node address do not agree.
OFF Unit OFF under all other circumstances.
15 EEPROM error ON Unit ON if an error has occurred in the EEPROM memory.
OFF Unit OFF when the EEPROM memory is normal.
Bit Error Status Manipulated by Unit operation
203
Error Log Section 8-3
Error Log Table Each error is recorded as one record in an error log table. Up to 64 records
can be saved. If more than 64 errors occur, the oldest errors will be deleted
from the error log and the most recent error will be recorded.
The following information is recorded in the error log table.
Main error code (See table later in this section.)
Detailed error code (See table later in this section.)
Time stamp (from the clock in the CPU Unit)
Error Log Location When an error is detected, the error codes and time stamp are recorded in the
error log in RAM inside the Ethernet Unit. Serious errors are also recorded in
EEPROM. The maximum number of errors that can be saved to EEPROM is
64 for the CS Series and 32 for the CJ Series. The errors recorded in
EEPROM will be saved even if the Unit is restarted or power is turned OFF.
When the Ethernet Unit is started, the contents of the error log in EEPROM is
copied to RAM.
When a FINS command is used to read the error log, the log held in RAM is
read. When a FINS command is used to clear the error log, the logs held in
both RAM and EEPROM are cleared.
FINS Commands for Error
Logs
The following FINS commands can be used to read or clear the error log.
Refer to SECTION 7 FINS Commands Addressed to Ethernet Units.
8-3-1 Error Log Error Codes
The error codes are described in the following table. The detailed error code
will provide detailed information on an error.
Command
code
Function
MRC SRC
21 02 ERROR LOG READ
03 ERROR LOG CLEAR
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
0001 Watchdog timer error in CPU Unit 00 00 Replace the CPU Unit. Saved
0002 CPU Unit service monitor error Monitor time (ms) Check the operating environment. Saved
0006 Other CPU error Bit 11: Unit not in Registered
I/O Tables
Other bits are reserved for
system use.
Create the I/O tables. Saved
000F CPU Unit initialization error 00 00 Replace the CPU Unit. Saved
0010 Insufficient System Setup Area 00 00 Reduce the number of CPU Bus
Units.
Saved
0011 Event timed out MRC SRC Replace the CPU Unit. Saved
0012 CPU Unit memory error 01: Read
error
02: Write
error
03: Routing
table
04: Setup
error
05: CPU Bus
Unit Words
(CIO/DM)
01: Recreate the data specified by
the 2nd byte of the detailed error
code.
02: Clear memory using proce-
dure in the PLC operation manual.
Saved
0013 CPU Unit protected 00 00 Remove protection from CPU Unit
memory.
Saved
204
Error Log Section 8-3
0103 Resend count exceeded (send
failed)
Commands
Bit 15: OFF
Bits 08 to 14: SNA
Bits 00 to 07: SA1
Responses
Bit 15: ON
Bits 08 to 14: DNA
Bits 00 to 07: DA1
Check transceiver at remote node. ---
0105 Node address setting error (send
failed)
Set the IP address correctly. ---
0107 Remote node not in network (send
failed)
Check the connection to the
remote node.
---
0108 No Unit with specified unit
address (send failed)
Check the unit address at the
remote node.
---
010B CPU Unit error (send failed) Troubleshoot the error in the CPU
Unit using the PLC operation
manual.
---
010D Destination address not in routing
tables (send failed)
Set the destination address in the
routing tables.
---
010E No routing table entry (send
failed)
Set the local node, remote node,
and relay nodes in the routing
tables.
---
010F Routing table error (send failed) Create the routing tables correctly. ---
0110 Too many relay points (send
failed)
Reconstruct the network or cor-
rect the routing tables so that
commands are sent to within a 3-
level network range.
---
0111 Command too long (send failed) Check the command format and
set the correct command data.
---
0112 Header error (send failed) Check the command format and
set the correct command data.
---
0117 Internal buffers full; packet dis-
carded
Change the network so that traffic
is not concentrated.
---
0118 Illegal packet discarded Check for nodes sending illegal
packets.
---
0119 Local node busy (send failed) Change the network so that traffic
is not concentrated.
---
0120 Unexpected routing error Check the routing tables. ---
0121 No setting in IP address table;
packet discarded
Set the remote node in the IP
address table.
---
0122 Service not supported in current
mode; packet discarded
Select the IP address table or
both methods for the address con-
version method.
---
0123 Internal send buffer full; packet
discarded
Change the network so that traffic
is not concentrated.
---
0124 Maximum frame size exceeded;
routing failed
Reduce the size of events. ---
021A Logic error in setting table 00 01: Data link
table
02: Network
parameters
03: Routing
tables
04: Unit
Setup
05: CPU Bus
Unit Words
(CIO/DM)
Recreate the data specified by the
2nd byte of the detailed error
code.
Saved
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
205
Error Log Section 8-3
0300 Parameter error; packet discarded Commands
Bit 15: OFF
Bits 08 to 14: SNA
Bits 00 to 07: SA1
Responses
Bit 15: ON
Bits 08 to 14: DNA
Bits 00 to 07: DA1
Check the command format and
set the correct command data.
---
03C0 FINS/TCP setting error 01 to 10:
Connection
number
01: Automati-
cally allo-
cated FINS
node address
duplication
02: Destina-
tion IP
address error
03: Destina-
tion port
number error
Refer to 1-5-1 FINS Communica-
tions Service in this manual and
the Operation Manual, Construc-
tion of Applications: SECTION 7
and set the FINS/TCP settings
correctly.
---
03C1 Server setting error 00: DNS
01: SMTP
02: POP3
03: SNTP
01: IP
address
02: Host
name
03: Port num-
ber
04: Other
parameters
Set the server settings correctly
based on the information in the
detailed error code.
---
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
206
Error Log Section 8-3
03C2 FINS/TCP packet discarded 01 to 10:
Connection
number
02:
Reopened
because
remote node
closed
03:
Reopened
because of
reception
error
04:
Reopened
because of
transmission
error
05:
Reopened
because RST
received from
remote node
06:
Reopened
because of
no keep-alive
response
Have the FINS/TCP connection
status checked when a
SEND(090), RECV(098), or
CMND(490) instruction is exe-
cuted in the ladder program.
---
07: Illegal
FINS/TCP
procedure
Refer to Operation Manual, Con-
struction of Applications: SEC-
TION 7, and correct the remote
node (application on a personal
computer).
---
08: Insuffi-
cient mem-
ory during
server pro-
cessing
09: Insuffi-
cient mem-
ory during
client pro-
cessing
0A: Insuffi-
cient mem-
ory during
node switch-
ing
There is too much load (traffic) on
the Ethernet Unit. Correct the sys-
tem so that traffic is not concen-
trated.
---
03C3 FINS/UDP packet discarded 00 01 to FE:
Transmission
source node
address
The automatic generation (static)
method was used as the IP
address conversion method, so
remote IP address information in
internal memory could not be
changed.
---
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
207
Error Log Section 8-3
03C4 Server connection error 00: DNS
01: SMTP
02: POP3
03: SNTP
01: Specified
host does not
exist
02: No ser-
vice at speci-
fied host
03: Timeout
04: Closed
unilaterally by
host
05: Cannot
connect
because
account infor-
mation does
not match
06: Host
name resolu-
tion error
07: Transmis-
sion error
08: Recep-
tion error
09: Other
error
Take either of the following mea-
sures.
Correct the settings for each
server.
Inspect the communications path
(Ethernet Unit, cable connec-
tions, hub, router, server), and
correct the situation that is caus-
ing the error.
---
03C5 Mail communications error F101: Mail too large
F102: Mail received from
non-specified address
F103: Mail subject error
F104: Non-specified com-
mand received
F106: Mail format (header)
error
F107: Mail format (body)
error
F201: Parameter error
F301: Decoding error
F302: File attachment error
(filename error, data format
error, I/O memory write size
error)
F303: No attached file
F304: Non-specified file
attachment received
F305: File attachment too
large
Other: FINS error response
code
Refer to the Operation Manual,
Construction of Applications: Cre-
ating FINS Applications, and cor-
rect the remote node (i.e., the
application on the personal com-
puter).
---
03C6 Clock data write error 0001: Clock data could not
be refreshed because of a
CPU Unit error.
Clear the CPU Unit error. ---
0002: Clock data could not
be refreshed because the
CPU Unit could not write
clock data in that operation
mode.
Refer to the Operation Manual,
Construction of Applications:
Automatic Clock Adjustment
Function, and check the operat-
ing conditions.
---
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
208
Error Log Section 8-3
Note (1) The time information in the CPU Unit is used in the CPU Bus Units.
(2) If the time information cannot be read from the CPU Unit, the time stamp
in the error log will be all zeros. This can occur due to CPU Unit startup
error, unit number errors, CPU error, and model number errors. If the time
is read out from a Programming Device, the time will be shown as all ze-
ros in the year 2000.
(3) The battery must be installed in the CS/CJ-series CPU Unit, the power
turned ON, and then the time set before the clock in the CPU Unit can be
used. The time will not be set correctly in the error log unless the clock
time is set correctly.
(4) An error record is not created in EEPROM when a CPU Bus Unit memory
error occurs.
0601 CPU Bus Unit error Arbitrary Restart the CPU Unit. If the prob-
lem persists, replace the Ethernet
Unit.
Saved
0602 CPU Bus Unit memory error 01: Read
error
02: Write
error
06: Error log Restart the CPU Unit. If the prob-
lem persists, replace the Ethernet
Unit.
Saved
(except
for error
log)
Error
code
Meaning Detailed error code Correction EE-
PROM
1st byte 2nd byte
209
Troubleshooting Procedures Section 8-4
8-4 Troubleshooting Procedures
The following procedures can be used to troubleshoot various problems in
system operation.
8-4-1 Startup Problems
RUN indicator lit?
Replace the Ethernet Unit.
Y
N
ERH indicator lit?
Y
N
ERC indicator lit?
N
Y
Power supplied
to CPU Unit?
Y
N
Ethernet Unit
loose on Rack?
N
Y
Do the RUN and ERH
indicators not light if another
CPU Unit is mounted
to the Rack?
N
Y
Is the same node
number used by another
Unit?
Y
N
Startup Problems occurred.
Make sure that sufficient
power is supplied to the
CPU Unit.
Make sure that Unit is firmly
mounted and tighten the
mounting screws firmly or
lock the sliders into place.
Replace the CPU Unit that
didn't work.
Create the I/O tables in
the CPU Unit.
Set the node numbers so that each one is used only once.
N
Y
N
Y
Y
N
Go to Network Connection Problems
ERH indicator not lit?
N
Y
N
Y
Set the unit numbers correctly.
Replace the Ethernet Unit.
Y
N
Is the node
address set between
01 and FE Hex?
Is the same unit
number used by another
CPU Bus Unit?
Has a CPU Unit error
occurred in the CPU Unit?
Restart the CPU Unit. If the error persists, replace the CPU
Unit.
Set the Unit Setup and routing tables
correctly.
ERH indicator not
flashing?
Is the IP address correct?
Correct the IP address in the System Setup, and read out the
controller status using the READ CONTROLLER STATUS
command in FINS communications and correct any problems
indicated.
Make sure that the node number and the last byte of the IP address are the same and set
other host IDs to 0, or change the address conversion method to use and IP address table
or combined methods.
Set the node
address to
between 01 and
FE Hex.
210
Troubleshooting Procedures Section 8-4
8-4-2 FINS Communications Problems (SEND(090)/RECV(098)/
CMND(490))
Go to Network
Connection Problems
N
Y
Y
N
N
Y
N
Y
Set both nodes to the same FINS network address.
N
N
N
Y
Y
Y N
Y
Y
FINS Communications Problems occurred.
Is the control data
for the instruction set
incorrectly?
Make sure that the FINS network address is not set to 0
for the Ethernet Unit and check the network address,
node number and unit address.
Is a CMND(194)
instruction being addressed
to the local node, e.g. for
socket services?
Are different UDP port
numbers set for FINS
communications for both
the local node and the
remote node?
Are the local and remote
nodes both on the same
network, i.e. do they have the
same network number in their
IP addresses?
Set the same port number for both nodes.
Is the IP address
of the remote node missing from
the IP address table?
IP routing must be used if the net ID of the IP address of the
local node and remote node. Set the IP address of the remote
node in the local IP address table. (Note: Use of the IP address
table must be set in the mode settings for the IP address table to
be effective.)
Set the IP address of the remote
node in the IP address table or use
automatic address conversion.
Is the IP address
of the remote node
missing from the IP
router table?
Set the network number of the remote node in the IP
router table.
Are the FINS network
addresses of the local and
remote nodes different?
Are you attempting
a broadcast transmission?
Do not attempt to broadcast to a node with a different
network number. You can broadcast only to nodes on the
same IP network.
Are you attempting to
communicate with a PLC on
another network?
Are the routing
tables set improperly?
Y
Set routing tables at the local node, target node, and any
relay nodes.
(Note: The automatic generation setting cannot be used alone.)
E N D
Refer to 8-5 Troubleshooting
with Response Codes and
remove any causes of the
problem discovered there
before proceeding with this
procedure.
211
Troubleshooting Procedures Section 8-4
8-4-3 UDP Socket Problems
General Problems
Opening and Closing
Problems
Refer to General Problems above.
Y
N
Y
N
General Problems
Is the response
code a value other than
0000?
Is the response
code in the results storage
area a value other than
0000?
Go to Network Connection
Problems.
E N D
Go through the procedure in 8-4-2
FINS Communications Problems
(SEND(090)/RECV(098)/
CMND(490)) before starting this
procedure.
Go to 8-5 Troubleshooting with Response
Codes.
Go to 8-6 Results Storage Area Response Codes.
(There will be no response code in the results storage
area if Socket Service Request Switches are being
used.)
212
Troubleshooting Procedures Section 8-4
Reception Problems
Y
N N
N
N
N
Y
Y
Y
Y
Reception Problems occurred.
Is reception
processing
finishing?
Is the remote
node not processing to
send data?
Adjust the remote node to process send data.
Read controller status
using the FINS command
READ CONTROLLER
STATUS.
Read memory status
using the FINS command
READ MEMORY STATUS.
Is the network
memory being used more
than 80%?
There may be too much load on the Ethernet
Unit. If the memory exhaustion records show
counts, UDP data may be corrupted. Check
your applications.
Read protocol status using
the FINS command READ
PROTOCOL STATUS.
Are any of
the first three items in the
status being counted?
The UDP protocol of the remote node may not
be compatible with that of the Ethernet Unit.
Use another communications service.
Check the remote node for transmission problems using the
next procedure. If nothing is uncovered, go to Network
Connection Problems.
Return to the procedure
for general problems.
Have any reception
errors occurred?
There may be noise affecting the network.
Increase the number of retries or take
measures against noise as described in 2-4
Network Installation.
213
Troubleshooting Procedures Section 8-4
Transmission Problems
N
Y
N
Y
Y
N
Is send
processing not
finishing?
Return to the procedure
for general problems.
Transmission Problems occurred.
Read protocol status using the
FINS command READ
PROTOCOL STATUS.
Have any failures
to reach the destination
been counted in the ICMP
status?
The UDP socket specified by the
destination UDP port number in the
send parameters is not opening at
the remote node.
Read controller status using
the FINS command READ
CONTROLLER STATUS.
There may be too much traffic on the
network and UDP packets may be
getting corrupted. Use TCP sockets or
adjust the network to reduce
excessive traffic.
Check the reception status
on the remote node.
Return to the procedure for
general problems.
Have any send
errors occurred?
214
Troubleshooting Procedures Section 8-4
8-4-4 TCP Socket Problems
General Problems
Y
N
N
Y
N
Y
General Problems
Is the response code
in the results storage
area a value other than
0000?
Read controller status using the
FINS command READ
CONTROLLER STATUS.
Is the response code a
value other than 0000?
Have any send
collisions occurred?
There may be too much traffic going on the
network. Reduce network traffic.
Go to Network Connection
Problems.
E N D
Go through the procedure in 8-4-2
FINS Communications Problems
(SEND(090)/RECV(098)/
CMND(490)) before starting this
procedure.
Go to 8-5 Troubleshooting with Response
Codes.
Go to 8-6 Results Storage Area
Response Codes. (There will be no
response code in the results storage area
if Socket Service Request Switches are
being used.)
215
Troubleshooting Procedures Section 8-4
Opening Problems
Closing Problems Refer to General Problems on page 214.
Y
Y
N
N
N
Y
Y
N
Opening Problems occurred.
Are you attempting
an active open?
Is the passive open
not finishing?
Use an active open at the
remote node.
Is the response
code in the results storage
area a value other
than 0049?
Read socket status using
the FINS command READ
SOCKET STATUS.
Does the port
number being used exist
at the local node?
Make sure that the same port number is not being used
simultaneously by more than one process, including FTP services.
Sockets can remain in ESTABLISHED or some later status even if
closed; be sure to close ports from both sides of the connection.
A socket can remain open in TIME WAIT status for up to one minute
on the side that closes the socket first; we recommend that the
active-side port number be set to 0 and that you close the socket
from the active side. If you are using the Socket Service Request
Switches, check the response code to see if it is 0049 Hex.
Return to General
Problems.
216
Troubleshooting Procedures Section 8-4
Reception Problems
Transmission Problems
N
Y
N
Y
N
Y
Y
Y
N
N
Reception problems occurred.
Is reception processing
not finishing?
Is the remote
node not processing
to send data?
Adjust the remote node to process send data.
Read memory status using
the FINS command READ
MEMORY STATUS.
Is the network
memory being used
more than 80%?
There may be too much load on the Ethernet
Unit. If the memory exhaustion records show
counts, processing may be slow. Check your
applications.
Return to the procedure
for general problems.
Is the response
code in the results storage
area a value other
than 0000?
(If you are using the Socket Service
Request Switches, check the response
code to see if it is other than 0000
Hex.) Is the number of
bytes received in the
results storage
area 0?
The remote node's TCP socket has closed.
Close the local socket.
N
Y
Y
N
Transmission problem occurred.
Is send processing
finishing?
Return to the procedure for
general problems.
Read socket status using
the FINS command READ
SOCKET STATUS.
Is there the maximum
number of bytes in the send
queue (4,096 bytes)?
Make sure that reception processing is
being performed at the remote node.
217
Troubleshooting Procedures Section 8-4
8-4-5 FTP Service Problems
Connection Problems
Y
N
N
Y
N
N
Y
END
N
N
Y
Y
Y
Y
What type of Memory
Card is it?
Memory Card
N
Convert to EM File Memory in the PLC System Setup.
N
Y
END
N
Y
Y
Connection problem occurred.
Are you unable
to connect to the
Ethernet Unit's FTP
server?
Is the FTP indicator lit?
The FTP server is connected to another client.
Wait until the client has finished.
Are the parameter
settings in the host
computer incorrect?
Correct the computer settings. Refer to the
documentation for your computer.
Go to Network Connection Problems.
Are you unable to
log in?
Check the login name and password settings.
Can you display
the "EM" directory using ls
from the host
computer?
Have specified
banks of the EM Area been
converted to EM File
Memory?
Has the EM File
Memory been initialized?
Replace the CPU Unit.
Initialize the EM File Memory from the CX-
Programmer or other Programming Device.
Can you display
the MEMCARD directory
using ls from the host
computer?
Is a Memory Card
not inserted in the
PLC?
Insert a Memory Card.
Is the Memory Card
faulty?
Initialize the Memory Card. If the problem persists,
replace the Memory Card if necessary.
EM File
Memory
218
Troubleshooting Procedures Section 8-4
File Transfer Problems
Y
N
N
Y
END
Y
N
N
Y
N
N
1
1
N
Y
Y
Y
File transfer problem occurred.
Are you not connected to
the FTP server?
Return to the previous procedure.
Is the current
directory MEMCARD or EM?
Make MEMCARD or EM the current directory (execute
cd /MEMCARD or cd /EM).
Can you
execute get?
Is the file you are
attempting to get not actually
on the Memory Card?
Designate a file actually in the file system.
Return to Startup Problems.
Can you
execute put?
Is there insufficient
free space available
in the file system?
Delete unneeded files or use a different Memory Card.
Is the data in the
file transferred with put or
get normal (i.e., not
corrupted)?
Use the type command and change the file data type to
binary before executing put or get.
219
Troubleshooting Procedures Section 8-4
8-4-6 Network Connection Problems
Is the LNK indicator
lit?
Did all nodes
fail to respond to ping
command?
Is the twisted-pair
cable secured?
E N D
Firmly secure the cable.
Power may not be being supplied to the hub.
Y
N
Y
N
N
Did a particular
node fail to respond to
ping command?
The remote node may not support ICMP.
Y
N
Is the remote
node functioning as an
FTP client?
Y
N
Y
Only SD indicator
is flashing.
Connect by FTP.
Is the twisted-pair
cable between the Ethernet Unit
and the hub straight
cable?
Use straight cable.
N
Y
Network connection problem occurred.
Go through the procedure in
Startup Problems before
starting this procedure.
Execute the ping
command for all nodes
connected to the network.
Replace first the twisted-pair cable, then the hub,
and then the Ethernet Unit, in order.
The twisted-pair cable for that node may be
disconnected.
Execute FINS PROTOCOL
STATUS READ.
If the following parameters are counted, the corresponding
communications services may not be possible with the remote
node.
[IP status] (2) (3) (5) (6) (All communications services)
[ICMP status] (5) (6) (7) (8) (ping)
[TCP status] (3) reception status (4) (5) (6) (FTP, TCP sockets)
[UDP status] (1) (2) (3) (FINS communications, UDP socket)
If the following parameters are counted, the load at the Ethernet
Unit may be too high. Adjust the user applications.
[IP status] (4) (8) (9)
220
Troubleshooting Procedures Section 8-4
Mail Not being Sent
S T A R T
N
Y
Is the ERH indicator
flashing?
Y
N
Y
N N
Is the HOST indicator
lit?
Is the user mail
transmission status
"7"?
Y
Is the user mail
transmission status
"0"?
Y
N
N
Does destination
mail address exist?
N
Y
Is required
information missing from
the mail?
Y
N
Did required
mail content fail
to be obtained?
Y
N
The mail transmission function cannot be used because no IP
address or host name is set for the SMTP server.
Using the CX-Programmer, make the SMTP settings in the
System Setup. If the host name is used for the server settings,
then the DNS tab settings must be made too.
Is the HOST indicator
flashing?
Y
There is a mistake in the Unit Setup. Correct the mistake.
The SMTP server address is wrong (set to 255.255.255.255
or 127.*.*.*).
The SMTP server host name is wrong.
The local mail address is wrong.
The destination mail address is wrong.
Referring to the error log, correct the communications path.
The SMTP server address is wrong.
The IP router table is wrong.
There is a communications error or a mistake in the
communications path settings.
If POP before SMTP is required for the SMTP server
connection, SMTP (POP before SMTP) and POP must be
set in the Unit Setup.
There is a mistake in the Unit Setup. Correct the mistake.
The SMTP server address is wrong (set to 0.0.0.0).
The mail transmission settings in the Unit Setup are wrong
(not set).
There is a mistake in the send conditions in the Unit Setup's
mail transmission settings. Correct the mistake.
The Mail Send Switch never turns ON after a start (power
ON) or restart.
The interval timer is not set, or is set to an interval longer
than intended.
The send conditions are not set.
Is the user mail
transmission status
"6"?
Y
Correct the communications path.
The SMTP server address is wrong.
The IP router table is wrong.
There is a communications error or a mistake in the
communications path settings.
The mail address set in the Unit Setup is wrong. Correct the
mistake.
Note: Set the destination mail address correctly. If it is incorrect,
mail will stay at the SMTP server.
Correct the information in the mail transmission settings in
the Unit Setup.
Make the settings for the required user data, error log
data, status data, and file attachments.
Clear the following errors.
If a user-created mail address is wrong, then correct it.
There may be too much of a load (traffic) at the Ethernet
Unit. Adjust the applications.
E N D
N
Is the SMTP,
POP3, or
DNS error status
bit ON?
221
Troubleshooting Procedures Section 8-4
Mail Not being Received
S T A R T
N
Y
Is the ERH indicator
flashing?
Y
N
Y
N N
Is the HOST indicator
lit?
Are there responses
to remote mail commands?
Y
Is the user mail
transmission status
"0"?
Y
N
The mail reception function (and response mail transmission)
cannot be used because no IP address or host name is set for
the POP3/SMTP server.
Using the CX-Programmer, make the SMTP and POP settings
in the System Setup. If the host name is used for the server
settings, then the DNS tab settings must be made too.
Is the HOST indicator
flashing?
Y
There is a mistake in the Unit Setup. Correct the mistake.
The SMTP server address is wrong (set to 255.255.255.255
or 127.*.*.*).
The SMTP server host name is wrong.
The local mail address is wrong.
Referring to the error log, correct the communications path.
The SMTP server address is wrong.
The IP router table is wrong.
There is a communications error or a mistake in the
communications path settings.
The POP3 server and account information (user name,
password, mail address) do not match.
Correct the communications path.
Are the mailer settings correct?
Are the settings correct for the POP3 and SMTP servers in
the communications path?
Are the Unit Setup and the mail addresses set for the
servers correct?
Are the destination mail addresses for remote mail
commands correct?
Has the network administrator set protection for mail
addresses as a firewall?
From the response code (response status), refer to the section
on receiving mail in the Operation Manual, Construction of
Applications and remove the cause of the error.
E N D
N
Is the SMTP,
POP3, or
DNS error status
bit ON?
222
Troubleshooting Procedures Section 8-4
Clock Not being Automatically Adjusted
S T A R T
N
Y
Is the SNTP error
status bit ON?
Is the ERH indicator
flashing?
Y
N
Y
N N
Is the HOST indicator
lit?
Is 03C6 stored in
the Ethernet Unit's
error log?
Y
N
The automatic clock adjustment function cannot be used
because no IP address or host name is set for the SNTP
server.
Using the CX-Programmer, make the SNTP settings in the
System Setup. If the host name is used for the server settings,
then the DNS tab settings must be made too.
Is the HOST indicator
flashing?
Y
There is a mistake in the Unit Setup. Correct the mistake.
The SNTP server address is wrong (set to 255.255.255.255
or 127.*.*.*).
The SNTP server host name is wrong.
Referring to the error log, correct the communications path.
The SNTP server address is wrong.
The IP router table is wrong.
There is a communications error or a mistake in the
communications path settings.
Clock information cannot be changed because a bus error
occurred between the PLC and the Ethernet Unit.
Turn OFF the power and restart the PLC.
If the problem occurs again, replace the PLC, Backplane, or
Ethernet Unit.
E N D
Is the SNTP error
status bit ON?
N
Y
For some CPU Unit models and lots, there are operation
modes in which clock information cannot be changed.
For the following model and lot numbers, clock information
cannot be changed while using RUN Mode or Monitor Mode
in asynchronous mode.
CS1G/H-CPU@@H (Lot Nos.: 030430 and earlier)
CJ1H/G-CPU@@H (All lots)
223
Troubleshooting with Response Codes Section 8-5
8-5 Troubleshooting with Response Codes
You can troubleshoot the errors in FINS communications from the response
codes when the SEND(090), RECV(098), or CMND(490) instructions have
been used. For the storage areas of the response codes refer to information
on page 141 under 6-6-4 Writing Programs.
The table below lists response codes (main and sub-codes) returned after
execution of FINS commands, the probable cause of errors, and recom-
mended remedies. The response codes provided here are for the Ethernet
Unit. Refer to the FINS Command Reference Manual (W227) or the operation
manuals for the relevant Unit for further information on response codes.
The 6th, 7th, and 15th bits of the response codes have specific functions. The
6th bit will be ON when a non-fatal error has occurred in the PC at the remote
node; the 7th bit will be ON when a fatal error has occurred in the PC at the
remote node; and the 15th bit will be ON when a network relay error has
occurred. Refer to information given after the following table for more informa-
tion on relay errors.
7 Bit 6 5 4 3 2 1 0
1: PLC non-fatal error flag 1: PLC fatal error flag
1: Relay error flag
First byte
7 6 5 4 3 2 1 0
Second byte
Main response code (MRES) Sub-response code (SRES)
Main code Sub-code Check point Probable cause Remedy
00: Normal
completion
00 --- --- ---
01: Local
node error
03: Local node
send error
--- Send error in local node was
caused by lack of available
space in internal buffers.
Reduce the load (traffic) on the
Ethernet Unit. Check your user
applications.
05: Node address
setting error
Local IP address The network cannot be
accessed because the IP
address setting is not correct.
Correct the local IP address.
07: Local node
busy, cannot
send
System load The internal buffers are full
because there is too much traf-
fic at the local node, preventing
data from being sent.
Correct the user application to
reduce traffic at the Ethernet
Unit.
02: Remote
node error
01: Remote node
not in network
IP address table,
IP router table
IP address of remote node not
set correctly in IP address table
or IP router table.
Set IP address of remote node
into IP address table and, if inter-
network transmission is required,
into the IP router table.
02: No such Unit Control data in
instruction
No node with the specified unit
address.
Check the remote nodes unit
address and make sure the cor-
rect one is being used in the con-
trol data.
05: Response
timeout
Response to
CONTROLLER
STATUS READ
and PROTOCOL
STATUS READ
FINS command
Message packet was corrupted
by transmission error.
Check the protocol and controller
status by reading them with FINS
commands. Increase the num-
ber of transmit retry attempts.
Control data in
instruction
Response time-out, response
watchdog timer interval too
short.
Increase the value for the
response monitor time in the
control data.
Read error log The transmission frame may
be corrupted or the internal
reception buffer full.
Read out the error log and cor-
rect as required.
224
Troubleshooting with Response Codes Section 8-5
03: Communi-
cations con-
troller error
01: Communica-
tions controller
error
ERC indicator on
the Controller
Error occurred in the communi-
cations controller, ERC indica-
tor is lit.
Take corrective action, referring
to troubleshooting procedures in
this section.
02: CPU Unit
error
Remote CPU Unit
indicators
CPU Unit error occurred in the
PLC at the remote node.
Check CPU Unit indicators at the
remote node and clear the error
in the CPU Unit (refer to the PCs
operation manuals)
04: Unit number
setting error
Unit number Unit number setting error Make sure the unit number is
within the specified range and
that the same unit number is not
used twice in the same network.
04: Not exe-
cutable
(Service not
supported.)
01: Unsupported
command
Command code An undefined command has
been used.
Check the command code and
be sure the command is sup-
ported by the Unit to which you
are sending it.
FINS header
frame length
A short frame (4 bytes) is being
used for the FINS header
frame.
Check the FINS header frame
length. The Ethernet Unit does
not support short headers.
05: Routing
error
01: Routing table
setting error
Routing tables Remote node is not set in the
routing tables.
Set the destination address in
the routing tables.
02: Routing
tables not regis-
tered
Routing tables Routing tables arent registered
completely.
Set routing tables at the local
node, remote node, and any
relay nodes.
03: Routing table
error
Routing tables Routing table error Set the routing tables correctly.
04: Too many
relays
Network configu-
ration
The maximum number of relay
nodes (2) was exceeded in the
command.
Redesign the network or recon-
sider the routing table to reduce
the number of relay nodes in the
command. Communications are
possible on three network levels,
including the local network.
10: Com-
mand format
error
01: Command
too long
Command data The command is longer than
the max. permissible length.
Check the command format of
the command and set it correctly.
Be sure broadcast transmissions
dont exceed 1,473 bytes.
02: Command
too short
Command data The command is shorter than
min. permissible length.
Check the command format of
the command and set it correctly.
03: Element-data
mismatch
Command data The designated number of data
items differs from the actual
number in the command data.
Check the number of items and
the data, and make sure that
they agree.
05: Header
parameter error
Command data Data for another node on the
same network was received
from the network.
Check the header parameters in
the command data and be sure
the correct command format is
being used.
An attempt was made to send
response data for a broadcast
address.
Main code Sub-code Check point Probable cause Remedy
225
Troubleshooting with Response Codes Section 8-5
11: Parame-
ter error
00: Parameter
error
Parameters in
command data
The parameters in the com-
mand data are incorrect.
The UDP/TCP socket number
was not within the proper
range.
The local UDP port number
might be set to 0.
Check the parameters.
Be sure the socket number is
between 1 and 8.
Set the Local UDP port number
correctly.
01: No area
specification
Memory area
code in command
data
A correct memory area code
has not been used or EM Area
is not available.
Check the commands memory
area code in the Results Storage
Area and set the appropriate
code.
03: Address
specification out
of range
First word
address in com-
mand data
The first word is in an inacces-
sible area or the bit number is
not 00.
Set a first word that is in an
accessible area. The bit number
must be 00 for Ethernet Units.
04: Address
range exceeded
Command data The address set in the com-
mand is not correct.
Correct the address in the com-
mand data, being sure that the
start address plus the number of
words does not exceed accessi-
ble memory.
0B: Response
too long
Command data The response frame is too
long.
Correct the number of data ele-
ments or other parameters in the
command data for which the
response is being returned.
0C: Parameter
error
Parameters in
command data
Parameters are set incorrectly
in the command data.
Check the command data and
correct any parameters that are
incorrect.
21: Cannot
write
08: Cannot
change
IP address con-
version method
With respect to a FINS node
address that could not be
dynamically changed, a FINS
message was received from an
IP address that differed from
the Unit Setup.
Referring to SECTION 5 Deter-
mining IP Addresses, correct the
relationships between IP
addresses and FINS node
addresses.
Main code Sub-code Check point Probable cause Remedy
226
Troubleshooting with Response Codes Section 8-5
22: Status
error (operat-
ing mode dis-
agreement)
0F: Service in
progress, cannot
perform operation
Socket status
area
The same socket service is
already in progress at the
specified socket number.
Use the socket status flag in PC
memory to be sure that socket
service has finished before start-
ing services again.
10: Socket not
open
Socket status
area
The specified socket is not
open.
Open the socket. For TCP sock-
ets, be sure to wait until connec-
tion is made.
11: Local node
busy, cannot
send
System load The internal buffers are full
because there is too much traf-
fic at the local node, preventing
data from being sent.
Correct the user application to
reduce traffic at the Ethernet
Unit.
20 Unit settings The socket is not open for Sys-
tem Settings.
Correct the settings for the Unit
Setup, the FINS/TCP connection
number, the remote IP address,
and the remote port number.
21 The socket is not open
because of the remote node
conversion command for the
FINS/TCP connection.
22 The socket is reopening
because the connection to the
remote node has closed.
23 The socket is reopening
because of a reception error.
24 The socket is reopening
because of a transmission
error.
25 The socket is reopening
because RST received in
response to keep-alive.
26: FINS/TCP not
connected
The socket is reopening
because of no keep-alive
response.
30: Connection
not establish
Command data A connection is already estab-
lished with the specified
remote node.
Correct the settings for the FINS/
TCP connection number, the
remote IP address, and the
remote port number.
31: Connection
cannot be
changed
Unit settings and
command data
The specified connection num-
ber is not set as a FINS/TCP
client in the Unit Setup.
Correct the settings for the Unit
Setup, the FINS/TCP connection
number, the remote IP address,
and the remote port number.
32: Service
stopped, cannot
perform operation
Command data While a remote node change
was being processed for the
specified connection number, a
request for a change was
received and the processing
was stopped.
Correct the settings for the FINS/
TCP connection number, the
remote IP address, and the
remote port number.
23: Environ-
ment error (no
such Unit)
05: Parameter
error
Unit settings IP address conversion failed. Check the IP address and subnet
mask in the System Setup and
be sure that settings are correct.
07: Configuration
error
IP address con-
version in Unit
settings
IP address conversion is set for
automatic conversion only.
Check the mode settings in the
System Setup. This error will be
generated for the READ IP
ADDRESS TABLE command
only.
Main code Sub-code Check point Probable cause Remedy
227
Results Storage Area Response Codes Section 8-6
Network Relay Errors 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.
8-6 Results Storage Area Response Codes
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.
7 Bit 6 5 4 3 2 1 0
1
First byte
Command code
7 6 5 4 3 2 1 0
Second byte
First word
7 6 5 4 3 2 1 0
1: PLC non-fatal error flag
1: PLC fatal error flag
Relay error flag
1
7 6 5 4 3 2 1 0
S-b-response code (SRES) Second word Main response code (MRES)
7 6 5 4 3 2 1 0
1
7 6 5 4 3 2 1 0
Error node address Third word Error network address
Response
code
UNIX error
message
Description Probable remedy
0003 ESRCH No such process Close the local socket and try reopening it.
0006 ENXIO No such device or address
0009 EBADF Bad file number (incorrect socket
specification)
000D EACCES Permission denied
(Broadcast address specified for
remote IP address for active TCP
open)
Check the IP address of the remote node and
try to reconnect.
000E EFAULT Bad address (copy failed between
kernel and user area)
Close the local socket and try reopening it.
0011 EEXIST File exists
0016 EINVAL Invalid argument (socket library
argument error)
0018 EMFILE Too many open files (More than 32
sockets)
0020 EPIPE Broken pipe (remote node closed
socket)
Close the local socket.
003C EPROTONO-
SUPPORT
Protocol not supported (protocol
other than UDP, TCP, or RAW speci-
fied)
Close the local socket and try reopening it.
003D EPROTOTYPE Protocol wrong type for socket
003E ENOBUFS No buffer space available There is too much load (traffic) on the Ethernet
Unit. Check your user applications.
228
Results Storage Area Response Codes Section 8-6
003F EISCONN Socket is already connected (con-
nection attempted to open socket)
Close the local socket and try reopening it.
0040 ENOTCONN Socket is not connected (send
attempted to closed socket)
0041 EALREADY Operation already in progress (con-
nection attempted to existing non-
block connection)
0042 EMSGSIZE Message too long Check the length of send data.
UDP or TCP: 1 to 1,982 bytes
UDP broadcasts: 1 to 1,472 bytes
0043 EDESTADDRREQ Destination address required (desti-
nation address not specified)
Close the local socket and try reopening it.
0044 ENOPROTOOPT Protocol not available (unsupported
option specified)
0045 ECONNABORTED Software caused connection abort
(another task closed socket)
0046 EINPROGRESS Operation now in progress (non-
block connection ended during pro-
cessing)
0047 ENOTSOCK Socket operation on non-socket
0048 EOPNOTSUPP Operation not supported on socket
0049 EADDRINUSE Address already in use (UDP or
TCP open request sent for port
already in use)
Check the port number.
TCP ports can remain unusable for 1 min after
closing.
004A ECONNREFUSED Connection refused (TCP socket
(active open) processing refused by
remote node)
Passively open a remote TCP socket, checking
the remote IP address and remote TCP port
number.
004B ECONNRESET Connection reset by peer (TCP
socket closed by remote node)
Close the local socket and try reconnecting.
004C EADDRNOTAVAIL Cant assign requested address
(mistake in remote IP address)
Check the setting of the remote IP address and
try reconnecting.
004D EAFNOSUPPORT Address family not supported by
protocol family
Close the local socket and try reopening it.
004E ENETUNREACH Network is unreachable Set the path to the remote node in the IP router
table.
004F EHOSTDOWN Host is down Check the remote host and communications
path.
0050 EWOULDBLOCK Operation would block Close the local socket and try reopening it.
0051 EHOSTUNREACH No route to host The specified node does not exist on the desig-
nated IP network segment. Check the commu-
nications path.
0053 ETIMEDOUT Connection timed out (TCP timed
out)
Check the remote host and communications
path.
0063 ESELABORT Used for internal Ethernet Unit pro-
cessing
Close the local socket and try reopening it.
0066 (None) Internal memory cannot be allocated
for processing; the service cannot
be provided.
Traffic is too high at the Ethernet Unit. Correct
the user application to reduce traffic at the
Ethernet Unit.
0080 (None) Timed out for passive TCP open
request
Either the remote node is not executing an
active TCP open or there is a block on the net-
work.
Response
code
UNIX error
message
Description Probable remedy
229
Results Storage Area Response Codes Section 8-6
0081 (None) Closed by close command during
socket servicing
No action is necessarily called for.
0082 (None) Connection with remote node not
achieved for passive TCP open
request
The remote IP address and TCP port number
settings differ from those of the remote socket
(active side).
Response
code
UNIX error
message
Description Probable remedy
230
Results Storage Area Response Codes Section 8-6
231
Appendix A
Ethernet Network Parameters
Parameter Value Description
TCP send buffer 4,096 bytes Maximum capacity of the TCP send buffer
TCP receive buffer 4,096 bytes Maximum capacity of the TCP receive buffer
UDP send buffer 9,000 bytes Maximum capacity of the UDP send buffer
UDP receive buffer 9,016 bytes Maximum capacity of the UDP receive buffer
FINS receive buffer 16,383 bytes Maximum capacity of the FINS receive buffer
RAW send buffer 2,048 bytes Maximum capacity of the RAW send buffer
RAW receive buffer 2,048 bytes Maximum capacity of the RAW receive buffer
Hold timer 75 s (12 min max.) The hold timer is used for active open processing of TCP sockets.
An ETIMEDOUT error will occur if connection is not completed within
75 s.
Resend timer Initial value: 1 s
Maximum value: 64 s
The resend timer is used to monitor completion of reception of arrival
confirmations when transferring data via socket services, including FTP
server and mail transfer TCP sockets. If the timer setting is exceeded
before arrival confirmation is received, data is resent. Resends are per-
formed from the first timeout (1 s) through the 12th timeout (64 s).
An ETIMEDOUT error will occur after the 12th timeout.
Continue timer Initial value: 5 s
Maximum value: 60 s
The continue timer starts if preparations have been completed to send
data but the send window is too small (either 0 or too small) to send the
data and the remote node has not requested that communications be
restarted. Confirmation of the window size is requested from the remote
node when the continue timer times out. The initial value of the timer is
5 s and confirmation processing will continue consecutively with increas-
ingly longer times until the maximum time of 60 s is reached.
2MSL timer 60 s The 2MSL timer starts at the TCP socket that first closes the socket and
will run for 60 s in the TIME_WAIT status.
IP reassemble timer 12 s A fragmented IP packet is discarded if it cannot be reassembled within 12
seconds.
ARP timer 20 min/3 min If a complete ARP table entry (with an Ethernet address) is not referred
to for 20 minutes, it is removed from the table.
An incomplete ARP table entry (no response yet returned to the ARP
request) is removed from the table after 3 minutes.
Window size
(initial value of maxi-
mum window size)
4,096 bytes The initial value of the maximum capacity used to control the conver-
gence of TCP sockets. Actually, the node negotiates with the remote
node and uses the smaller of the values for the two nodes. The window
size will fluctuate with the available space in the TCP reception buffers of
the remote node when processing communications.
Fragment size 1,500 bytes Data packets are fragmented into 1,500-byte IP packets. UDP data is
separated into 1,472-byte fragments before sending.
Segment size 1,024 bytes TCP data is separated into 1,024-byte units, unless the segments are dif-
ferent, in which case it will be separated into 536-byte units.
TTL (Time to Live) 30 Decremented each time an IP router is passed.
233
Appendix B
Buffer Configuration
Network memory (248K bytes)
Communications
controller
IP packet
output queue
(50 max. x
1,500 bytes)
UDP socket send
request buffers
(8 x 9,000 max.)
TCP socket send
request buffers (8
x 4,096 max.)
FTP service
send buffer
(4,096 bytes)
FINS send
buffer (9,000
bytes max.)
FINS reception
buffer (16,383
bytes max.)
FTP service
reception buffer
(4,096 bytes)
TCP socket
reception
request buffers
(8 x 4,096 max.)
UDP socket
reception
request buffers
(8 x 9,016 max.)
IP packet input
queue
(50 max. x
1,500 bytes)
Network
(See note 2.)
(See note 2.)
(See note 1.)
(See note 1.)
FINS processing
buffers (192 x
2,020 bytes)
C
P
U
U
n
i
t
234
Buffer Configuration Appendix B
Network Memory
Most of the buffers used for communications servicing by the Ethernet Unit are administered in a buffer config-
uration called network memory. Network memory consists of 248K bytes of memory divided into short and long
buffers. The use of short and long buffers is determined by the status of the various services when the Ethernet
Unit is running. The capacity of all buffers cannot be used due to limits in the mounted memory capacity. The
status of the short and long buffers can be accessed by execution the FINS command MEMORY STATUS
READ (2763).
Note 1. The status of UDP and TCP socket reception request buffers can be accessed by executing the FINS
command SOCKET STATUS READ (2764).
2. The status of UDP and TCP socket send request buffers can be accessed by executing the FINS
command SOCKET STATUS READ (2764).
235
Appendix C
TCP Status Transitions
The TCP socket status can be confirmed using the socket status data returned for the FINS command
SOCKET STATUS READ (2764).
Status Meaning
CLOSED Connection closed.
LISTEN Waiting for connection.
SYN SENT SYN sent in active status.
SYN RECEIVED SYN received and sent.
ESTABLISHED Already established.
CLOSE WAIT FIN received and waiting for completion.
FIN WAIT 1 Completed and FIN sent.
CLOSING Completed and exchanged FIN. Awaiting ACK.
LAST ACK FIN sent and completed. Awaiting ACK.
FIN WAIT 2 Completed and ACK received. Awaiting FIN.
TIME WAIT After closing, pauses twice the maximum segment life (2MSL).
rcv FIN
snd ACK
CLOSE
rcv ACK of FIN
rcv ACK of SYN
CLOSED
LISTEN
SYN
RECEIVED
SYN
SENT
ESTABLISHED
CLOSING
CLOSED
WAIT
CLOSED
snd SYN, ACK
Passive OPEN
CLOSE
ACTIVE OPEN
snd SYN
snd SYN
SEND
CLOSE
rcv SYN
snd ACK
rcv SYN, ACK
snd ACK
snd FIN
CLOSE
snd ACK
rcv FIN
rcv ACK of FIN
snd FIN
rcv FIN
rcv ACK of FIN
Timeout=2MSL
LAST-ACK
CLOSE
snd FIN
TIME WAIT
FIN
WAIT-1
FIN WAIT-2
rcv SYN
snd ACK
237
Appendix D
ASCII Characters
Bits 1 to 4 Bits 5 to 7
Binary 0000 0001 0010 0011 0100 0101 0110 0111
Hex 0 1 2 3 4 5 6 7
0000 0 NUL DLE Space 0 @ P p
0001 1 SOH DC1 ! 1 A Q a q
0010 2 STX DC2 2 B R b r
0011 3 ETX DC3 # 3 C S c s
0100 4 EOT DC4 $ 4 D T d t
0101 5 ENQ NAK % 5 E U e u
0110 6 ACK SYN & 6 F V f v
0111 7 BEL ETB 7 G W g w
1000 8 BS CAN ( 8 H X h x
1001 9 HT EM ) 9 I Y i y
1010 A LF SUB * : J Z j z
1011 B VT ESC + ; K [ k {
1100 C FF FS , < L \ l |
1101 D CR GS - = M ] m }
1110 E SO RS . > N ^ n ~
1111 F SI US / ? O _ o DEL
239
Appendix E
Maintenance
The Ethernet Unit makes up part of a network. Repair a defective Ethernet Unit as soon as possible as it can
have a negative effect on the entire network. We recommend that customers keep one or more spare Ethernet
Units to allow immediate recovery of the network.
Replacing an Ethernet Unit
Observe the following precautions when replacing the Ethernet Unit.
Always turn OFF the power supply before replacing the Ethernet Unit.
Check that the spare Ethernet Unit is operating normally before replacing a defective Unit with it.
When returning a defective Unit for repairs, provide as much written information as possible on the symp-
toms of the problem.
If a problem occurs with poor contacts, wipe the contacts with a clean cloth soaked with industrial alcohol.
Carefully remove any lint remaining on the contacts before replacing the Unit.
Settings after Replacing an Ethernet Unit
After replacing an Ethernet Unit, set the following to the same settings as were used on the previous Unit.
Unit number
Node address
Settings after Replacing a CPU
The EEPROM in the PCs CPU holds the information listed below. This information must be stored in any new
CPU used to replace a defective one.
Routing tables
System Setup for the Ethernet Unit
241
Appendix F
Inspections
Carry out regular inspections to ensure the Ethernet Unit is functioning perfectly.
Items
Most of the parts that make up an Ethernet Unit are semiconductor components. None of the parts in the Unit
will wear out after a specific lifetime, but some parts may deteriorate due to extreme operating condition.
Therefore, it is important to inspect the Unit regularly.
Inspection Interval
Normally inspect once or twice per year. Choose the inspection period according to the severity of the operat-
ing conditions. New installation should be inspected more frequently until they are judged to be stable.
Inspection Items
Correct any of the items in the table below not conforming to the specified standard.
Tools Required for Inspection
The following tools are needed to inspect the Ethernet Unit:
Standard Tools
Flat-blade and Phillips screwdrivers
Tester or digital voltmeter
Industrial alcohol and a clean cloth
Tools Required Under Special Circumstances
Synchroscope
Pen oscilloscope
Thermometer and hygrometer
Item Details Standard
Environment Temperature around Unit 0 to 55C
Humidity around Unit 10% to 90% (with no condensation)
Accumulated dust No accumulated dust
Mounting Ethernet Unit firmly attached No looseness
Transceiver cable connector fully pushed in No looseness
Condition of transceiver cable No visible abnormality
Twisted-pair cable connector fully pushed in No looseness
Condition of twisted-pair cable No visible abnormality
243
Appendix G
Ethernet Unit Web Function
Web Function
Ethernet Units with Unit Ver. 1.3 or later can use a Web browser from a personal computer or other device to
easily make the Ethernet Units system settings and monitor statuses.
Web Function List
The information displayed on the window from the Web browser for the Ethernet Unit is as follows:
Unit Setup Functions
Menu item Parameter item Corresponding CX-Programmer function
Settings CX-Programmers Ethernet Unit Setup window
IP address and Protocols ---
System ---
IP address Unit Setup window- Setup Tab - IP Address
Net mask Unit Setup window- Setup Tab - Sub-net Mask
FINS/UDP Port Unit Setup window- Setup Tab - FINS/UDP Port
FINS/TCP Port Unit Setup window- Setup Tab - FINS/TCP Port
Address conversion mode Unit Setup window- Setup Tab - Conversion
Auto (Dynamic) Unit Setup window- Setup Tab - Auto (dynamic)
Auto (Static) Unit Setup window- Setup Tab - Auto (Static)
Manual Unit Setup window- Setup Tab - Table used
Auto & Manual Unit Setup window- Setup Tab - Mixed
Destination IP address is changed
dynamically
Unit Setup window- Setup Tab - Destination IP Address (Change Dynamically)
Destination IP address is Not changed
dynamically
Unit Setup window- Setup Tab - Destination IP Address (Change Dynamically)
ETN11 compatible mode None
Broadcast option Unit Setup window- Setup Tab - Broadcast
Baud rate Unit Setup window- Setup Tab - Baud Rate
TCP/IP keep-alive Unit Setup window- Setup Tab - TCP/IP keep-alive
FINS/TCP Protected Unit Setup window- FINS/TCP Tab - Use IP address to protect
SMTP Server (Host name or IP
address)
Unit Setup window- SMTP Tab - Server specification type
POP Server (Host name or IP
address)
Unit Setup window- POP Tab - Server specification type
SNTP Server (Host name or IP
address)
Unit Setup window- Auto Adjust Time Tab - Server specification type
FTP Unit Setup window- Setup Tab
Login name Unit Setup window- Setup Tab - FTP (Login)
Password Unit Setup window- Setup Tab - FTP (Password)
Port No. Unit Setup window- Setup Tab - FTP (Port No.)
DNS Unit Setup window- DNS Tab
IP address of DNS server Unit Setup window- DNS Tab - IP Address
Port No. Unit Setup window- DNS Tab - Port No.
Retry timer Unit Setup window- DNS Tab - Retry timer
SMTP Unit Setup window- SMTP Tab
IP Address (or Host name) Unit Setup window- SMTP Tab - IP Address or Host name
Port No. Unit Setup window- SMTP Tab - Port No.
Local mail address Unit Setup window- SMTP Tab - Local mail address
Option (Use POP before SMTP) Unit Setup window- SMTP Tab - Use POP before SMTP
244
Ethernet Unit Web Function Appendix G
POP Unit Setup window- POP Tab
IP Address (or Host name) Unit Setup window- POP Tab - IP Address or Host name
Port No. Unit Setup window- POP Tab - Port No.
Mail account Unit Setup window- POP Tab - Account Name
Mail password Unit Setup window- POP Tab - Mail password
Server access interval time Unit Setup window- POP Tab - Server access interval time
SNTP Unit Setup window- Auto Adjust Time Tab
IP Address (or Host name) Unit Setup window- Auto Adjust Time Tab - IP Address or Host name
Port No. Unit Setup window- Auto Adjust Time Tab - Port No.
Auto Adjust Time Unit Setup window- Auto Adjust Time Tab - Auto Adjust Time
Adjust Time Unit Setup window- Auto Adjust Time Tab - Adjust Time
Retry timer Unit Setup window- Auto Adjust Time Tab - Retry timer
Option
(Get the time info. from the SNTP
server)
Unit Setup window- Auto Adjust Time Tab - Get the time information from the SNTP
server
HTTP Unit Setup window- HTTP Tab
WEB Password Unit Setup window- HTTP Tab - Password
WEB Password (Confirm) None (for confirmation of Web password)
Port No. Unit Setup window- HTTP Tab - Port No.
Option (Use Web Function) Unit Setup window- HTTP Tab - Use Web Function
IP address/router table Unit Setup window- Setup Tab
IP address table Unit Setup window- Setup Tab - IP Address Table
IP router table Unit Setup window- Setup Tab - IP Router Table
FINS/TCP Unit Setup window- FINS/TCP Tab
Connection (1-8) Unit Setup window- FINS/TCP Tab - No. (1 to 8)
FINS/TCP server / client Unit Setup window- FINS/TCP Tab - FINS/TCP Mode
IP Address Unit Setup window- FINS/TCP Tab - IP Address
Auto-allocated FINS node Unit Setup window- FINS/TCP Tab - Auto allocated FINS node
keep-alive Unit Setup window- FINS/TCP Tab - keep-alive
Connection 9-16 Unit Setup window- FINS/TCP Tab - No. (9 to 16)
Send Mail ---
Mail address Unit Setup window- Mail Address Tab
Mail address 1 Unit Setup window- Mail Address Tab - Mail address 1
Mail address 2 Unit Setup window- Mail Address Tab - Mail address 2
Send Mail Unit Setup window- Send Mail Tab
Trigger No. Unit Setup window- Send Mail Tab - Trigger No.
Trigger option Unit Setup window- Send Mail Tab - Trigger No.
Not Use Unit Setup window- Send Mail Tab - Send mail upon trigger
Software switch Unit Setup window- Send Mail Tab - Software switch
Word value change Unit Setup window- Send Mail Tab - Word value change
Bit value change Unit Setup window- Send Mail Tab - Bit value change
ETN condition change Unit Setup window- Send Mail Tab - ETN condition (at error storage)
CPU condition change Unit Setup window- Send Mail Tab - CPU condition
Periodic timer Unit Setup window- Send Mail Tab - Periodic timer
Mail address Unit Setup window- Send Mail Tab - Mail address
Interval time Unit Setup window- Send Mail Tab - Interval time
Include data ---
Send user data Unit Setup window- Send Mail Tab - Send user data
Area Unit Setup window- Send Mail Tab - User defined mail address
Send Error Log information Unit Setup window- Send Mail Tab - Send Error Log informat.
Send Status information Unit Setup window- Send Mail Tab - Send status information
Send file data / IO memory data Unit Setup window- Send Mail Tab - Send file data / IO memory data
File data Unit Setup window- Send Mail Tab - File data
IO data (IOM) Unit Setup window- Send Mail Tab - I/O data (.IOM)
IO data (TXT) Unit Setup window- Send Mail Tab - I/O data (.TXT)
IO data (CSV) Unit Setup window- Send Mail Tab - I/O data (.CSV)
File name Unit Setup window- Send Mail Tab - Attached file name
Area Unit Setup window- Send Mail Tab - I/O memory data
Menu item Parameter item Corresponding CX-Programmer function
245
Ethernet Unit Web Function Appendix G
Status Monitor
Web Function Password
To prevent unauthorized access to the Ethernet Unit from a Web browser, password entry is required to enable
display and setting of the parameters. Even if the password has not been set, the default password ETHER-
NET must be entered. To change this password, set a new password in the HTTP Tab of the CX-Program-
mers Unit Setup, or use the Web function and select Settings - IP address and Protocols - HTTP.
Note 1. Setting a new Web function password as soon as possible is recommended to prevent unauthorized
access.
2. The Web function can also be disabled by setting in the Web function option.
Using the Web Function (Setting Password)
The Ethernet Units Web window is displayed by accessing the following URL from the Web browser.
URL: http://(Ethernet Units IP address)/0
Use the following procedure to set the Units system settings (HTTP password setting in this example) using
Internet Explorer version 6.0 and the Ethernet Units Web function.
Receive Mail Unit Setup window- Receive Mail Tab
Mail Address Protection Setting Unit Setup window- Receive Mail Tab - Protect using mail address
Attached File Enable Settings Unit Setup window- Receive Mail Tab - Receive file with specified extension only
Command Enable Setting Unit Setup window- Receive Mail Tab - Receive specified commands only
Menu item Corresponding CX-Programmer function
Status View ---
Unit information FINS(0501): CONTROLLER DATA READ
Unit status FINS(0601): CONTROLLER STATUS READ
Protocol status ---
IP status FINS(2762): PROTOCOL STATUS READ, IP status
ICMP status FINS(2762): PROTOCOL STATUS READ, ICMP status
TCP status FINS(2762): PROTOCOL STATUS READ, TCP status
UDP status FINS(2762): PROTOCOL STATUS READ, UDP status
Memory status FINS(2763): MEMORY STATUS READ
Socket status FINS(2764): SOCKET STATUS READ
Fins status Ethernet Units internal node table
Mail log RECEIVE MAIL: READ MAIL LOG
Error log FINS(2102): READ ERROR LOG
Send mail status Mail send status 1 to 8
Menu item Parameter item Corresponding CX-Programmer function
246
Ethernet Unit Web Function Appendix G
1. Connect to the Ethernet Unit from the Web browser.
In this example, the URL is specified as http://192.168.250.1/0 using the Ethernet Units default IP address.
2. Select Settings from the menu on the left side of the window to display the Settings Menu.
3. Select 1. IP address and Protocols - System to display the Login Password field on the right of the window.
247
Ethernet Unit Web Function Appendix G
4. Input the default password (ETHERNET all in upper case) and click the Login Button.
When login is successful, the following setting window will be displayed.
5. Select HTTP from the menu to display the HTTP setting items.
The following window shows the default settings.
248
Ethernet Unit Web Function Appendix G
6. Make the required settings (i.e., the password in this example).
To prevent incorrect password entry, set the same password in the WEB Password field and WEB Password
(Confirm) field.
7. After entering the correct password, click the Set Button followed by the Regist Button.
The Set Button is used to transfer the entered values from the personal computer, and temporarily register
them in the Ethernet Unit.
The Regist Button stores the set values that have been temporarily registered in the Ethernet to the flash mem-
ory (non-volatile memory) of the CPU Unit. The Ethernet Unit reads the unit settings from flash memory (non-
volatile memory) when the power is turned ON or the Unit is restarted. Therefore, when making the unit set-
tings using the Web function, always click the Set Button before the Regist Button. Otherwise the entered set
values will not be used. The Set Button and Regist Button are provided on the window for each setting item.
Note To prevent unauthorized Web access, the Web function can be disabled. Select HTTP - Option and
deselect the Use Web Function option. Click the Set Button followed by the Regist Button. This setting
is enabled by turning ON the power to the Ethernet Unit again or restarting the Unit. This setting can be
cancelled only through the CX-Programmer Unit Setup (version 5.0 or higher).
8. The functions of the other button are as follows:
Cancel Button
Use this button to cancel the entered value and display the value that was previously set with the Set But-
ton again. If the Set Button has not been clicked, the value that was read from the CPU Units flash mem-
ory (non-volatile memory) when the Ethernet Unit was started will be displayed.
Reload Button
Use this button read and display the values saved in the CPU Units flash memory (non-volatile memory).
9. To enable the unit settings that have been registered in the CPU Units flash memory (non-volatile memory,
turn the power to the PLC system OFF and ON again, or restart the Ethernet Unit.
249
Index
Numerics
100M indicator, 26
A
Account Name field, 68
applications precautions, xxiii
ARP communications, 16
ASCII characters, 237
Attached file name field, 71
Auto Adjust Time Tab, 51, 74
Auto allocated FINS node field, 65
automatic, 8
automatic clock adjustment, 8, 10, 22, 51
Auxiliary Area, 136
B
baud rate
CJ-series, 14
CS-series, 13
setting, 49
Baud Rate field, 63
Bit value change field, 71
bits
addresses, 90, 158
error status, 83, 201
service status, 82
status of UDP/TCP sockets, 80
BROADCAST DATA SEND, 164
Broadcast field, 62
broadcast setting, 48
broadcast test
command, 164
reading results, 164
BROADCAST TEST RESULTS READ, 164
buffers, 193, 231
configuration, 233
C
C200H-PRO27-E, 40
cables
communications, xxv
connections, 38
installation, 37
precautions, 35
twisted-pair, 11
CJ-series, 14
CS-series, 13
cascade connections, 36
CJ-series, 14
CS-series, 13
ChangeMode command, 6, 73
CIO Area, 136
allocations, 78
CJ1W-ETN11
comparison, 27
compatibility, 53
clock
automatic adjustment, 8, 10, 22, 51
Close Request Switch, 85
Closing Flag, 80
CMND(490) instruction, 8, 17, 19, 139
commands
FINS commands, 156
remote, 6
ChangeMode, 6
ErrorLogClear, 6
ErrorLogRead, 6
FileDelete, 6
FileList, 6
FileRead, 6
FileWrite, 6
FinsSend, 6
IOMRead, 6
IOMWrite, 6
MailLogClear, 6
MailLogRead, 6
PARAMBackup, 6
Test, 6
UMBackup, 6
Communication Unit Tab, 131
communications cables, xxv
Communications Port Enabled Flags, 90, 141
Communications Port Error Flags, 141
connectors
recommended models, 35
Contact Output Units
installation, 37
interference with Ethernet, 37
250
Index
precautions, 37
CONTROLLER DATA READ, 160
Controller Link, 10
CONTROLLER STATUS READ, 161
Conversion field, 62
Counter Area, 136
CPU Bus Unit Error Flag, 90
CPU Bus Unit Error, Unit Number Flags, 91
CPU Bus Unit Initializing Flags, 90
CPU Bus Unit Number Duplication Flags, 90
CPU Bus Unit Restart Bits, 91
CPU Bus Unit Setting Error Flag, 90
CPU Bus Unit Setting Error, Unit Number Flags, 91
CPU Bus Unit System Setup Area, 11
format, 53
CPU Bus Units
flags, 90
Restart Bits, 91
CPU condition field, 71
CQM1-PRO01-E, 40
crimp terminals, xxiv
CS1W-CN114, 40
CS1W-CN224, 40
CS1W-CN624, 40
CS1W-ETN01
compatibility, 53
CS1W-ETN11
comparison, 27
compatibility, 53
CS1W-KS001-E, 40
CSV extension, 73
current consumption
CJ-series, 14
CS-series, 13
Custom 1 to 3 field, 73
CX-Integrator, 12, 40
creating routing tables, 123
CX-Programmer, 40
connecting to PLC, 2, 126
from personal computer, 3
through multiple segments, 3
using wireless LAN, 3
within same segment, 2
Ethernet Unit Setup, 41
D
data areas
FINS communications, 158
Data Received Flag, 8, 80
dedicated control bits, 18
DHCP client, 9
dimensions, 15
CJ-series, 14
CS-series, 14
DM Area, 136
allocations, 86
DNS client, 22
DNS client function, 10
DNS communications, 17
DNS server, 10, 22
DNS Tab, 50, 66
Driver Tab, 126
E
EC Directives, xxv
echo response packet, 52
electromagnetic fields, xxiii
EM Area, 136
EM File Memory, 7
E-mail
attaching files, 9
mail receive function, 6, 9, 21
mail send function, 5, 20
receiving at PLC, 6
sending data, 5
sending equipment status, 5
EMC Directives, xxv
EMI countermeasures, 37
EMI Standard, xxv
EMS Standard, xxv
ERC indicator, 26
troubleshooting, 200
ERH indicator, 26
troubleshooting, 200
ERROR LOG CLEAR, 166
ERROR LOG READ, 165
ErrorLogClear command, 6, 73
ErrorLogRead command, 6, 73
errors
alignment, 163
Index
251
controller status, 161
error codes, 203
error log, 202
clearing, 166
reading, 165
error status, 201
flags
FINS communications, 162
response codes, 223
short packets, 163
status, 83, 201
unit numbers, 91
UNIX error messages, 227
Ethernet communications, 16
addresses
reading from Unit, 160
exchanging data between PLCs, 4
parameters, 231
Ethernet Connector, 23, 38
Ethernet Unit Setup, 41
Ethernet Units
mounting, 33
reading status, 193
replacing, 239
resetting, 159
ETN condition field, 71
ETN11 mode, 53
converting from ETN21 mode, 59
converting to ETN21 mode, 58
ETN21 mode
converting from ETN11 mode, 58
converting to ETN11 mode, 59
F
FileDelete, 6
FileDelete command, 73
FileList command, 6, 73
FileRead command, 6, 73
FileWrite command, 6, 73
FINS communications, 9, 17
commands, 156, 159
format, 157
from PLCs, 135
sending, 135
socket services, 157
data contents, 136
data length, 135
destination, 135
echo test, 52
memory areas, 158
node addresses, 9
overview, 17
port numbers, 136
response codes, 156, 223
response monitor time, 136
responses, 159
retries, 136
socket numbers, 157
specifications, 115, 135
TCP/IP, 3, 9
testing, 181
troubleshooting, 210
UDP/IP, 2, 9
FINS node addresses
automatic allocation, 9
FINS/TCP, 3, 115, 118
communications, 120
connection numbers, 119
connection status, 120
features, 118
frame format, 119
procedure, 121
TCP port number, 119
FINS/TCP Mode field, 65
FINS/TCP Port field, 62
FINS/TCP Tab, 64
FINS/UDP, 2, 50, 115, 116
frame format, 116
procedure, 117
UDP port numbers, 117
FINS/UDP Port field, 62
FinsGateway, 12, 130
FinsSend command, 6, 73
flags
Closing Flag, 80
Communications Port Enabled Flags, 90
Communications Port Error Flags, 90
CPU Bus Unit Error Flag, 90
CPU Bus Unit Error Unit Number Flags, 91
CPU Bus Unit Initializing Flags, 90
CPU Bus Unit Number Duplication Flags, 90
CPU Bus Unit Setting Error Flag, 90
CPU Bus Unit Setting Error Unit Number Flags, 91
Data Received Flag, 8, 80
Error Flags, 162
FTP Status Flag, 82
Opening Flag, 80
Receiving Flag, 80
252
Index
Results Storage Error Flag, 80
Sending Flag, 80
TCP/UDP Open Flag, 80
FTP communications, 17
FTP indicator, 26
FTP server, 7, 9, 20, 50
troubleshooting, 217
FTP Status Flag, 82
H
Holding Area, 136
HOST indicator, 26
Host name field, 67, 68, 74
HTTP Tab, 75
hub, 11, 35
connections
cascade, 36
stack, 36
installation, 37
precautions, 36
I
I/O allocations, 136
CIO Area, 78
DM Area, 86
I/O tables
creating, 39
ICMP communications, 16
status, 190
indicators, 25
troubleshooting, 200
inspections, 241
installation
cables
connections, 38
Contact Output Units, 37
location, xxiii
precautions, 34
interlock circuits, xxiv
INTERNODE ECHO TEST, 163
internode test, 10
command, 163
Interval time field, 71, 72
IOM extension, 73
IOMRead command, 6, 73
IOMWrite command, 6, 73
IP Address field, 62, 65, 68, 74
IP Address Table field, 63
IP ADDRESS TABLE READ, 186
IP addresses
allocating, 94
configuration, 94
dynamic, 9
setting, 46
IP communications, 16
IP addresses
reading from Units, 160
reading tables, 186
IP router tables
reading, 187
status, 189
IP Router Table field, 63
IP ROUTER TABLE READ, 187
IP router tables, 49
K
keep-alive field, 65
keep-alive setting, 19, 49
L
limit circuits, xxiv
LNK indicator, 26
Local mail address field, 67
locking devices
precautions, xxiv
Login field, 63
Low Voltage Directive, xxvi
M
mail
status, 87
Mail Address 1 field, 69
Mail Address 2 field, 69
Mail address field, 71, 72
Mail Address Tab, 51, 69
Mail password field, 68
mail receive function, 6, 9, 21
mail send function, 5, 20
Mail Send Switch, 5, 20
mail triggers, 5
Index
253
MailLogClear command, 6, 73
MailLogRead command, 6, 73
main response code, 156
See also MRES
maintenance, 239
media access method
CJ-series, 14
CS-series, 13
memory areas
See also data areas
Memory Card, 7
MEMORY STATUS READ, 193
mode settings
reading from Unit, 160
modulation method
CJ-series, 14
CS-series, 13
mounting
Racks, 33
MRES, 157
N
Network Tab, 126, 131
networks
network memory, 193, 234
No. field, 64
node addresses
manipulating rotary switches, 58
setting, 31, 32
Node Number Switches, 23
noise, xxiii
Contact Output Units, 37
O
OBJ extension, 73
online editing, xxii
Opening Flag, 80
operating environment
ambient humidity
CJ-series, 14
CS-series, 14
ambient temperature
CJ-series, 14
CS-series, 14
precautions, xxiii
P
PARAMBackup command, 6, 73
Password field, 63
PCMR(260) instruction, 142
PING, 10, 52, 181
application examples, 53
echo test, 52
POP server, 22
POP Tab, 51, 68
POP3 communications, 17
POP3 server, 6
Port No. field, 63, 66, 68, 74
port numbers
UDP port
reading from Unit, 160
power supply, xxiii
precautions, xxiv
precautions, xxi
applications, xxiii
Contact Output Units, 37
general, xxii
inspections, 241
installation, 33, 34
operating environment, xxiii
power supply, xxiv
replacing Units, 239
safety, xxii
wiring, 38
Programming Console, 40
Programming Devices
connecting, 39
CX-Net, 40
CX-Programmer, 40
Programming Console, 40
Protect using mail address field, 72
PROTOCOL STATUS READ, 189
protocols, 16
ARP, 16
DNS, 17
FINS, 17
FTP, 17
ICMP, 16
IP, 16
POP3, 17
reading status, 189
SMTP, 17
SNTP, 17
TCP, 17
254
Index
TCP/IP, 8
UDP, 17
UDP/IP, 8
R
Racks
mounting Ethernet Units, 33
radioactivity, xxiii
RD indicator, 26
Receive file with specified extension only field, 73
Receive Mail Tab, 51, 72
Receive Request Switch, 85
Receiving Flag, 80
RECV(098) instruction, 17, 138
relay tables, 122
RESET, 159
response codes, 223
FINS commands, 156
UNIX error messages, 227
Results Storage Area, 157
response codes, 227
Results Storage Error Flag, 80
Retry timer field, 66
Routing Table Area, 12
routing tables
creating, 122
local network table, 122
relay network table, 122
setting examples, 124
RUN indicator, 26
troubleshooting, 200
S
safety precautions, xxii
SD indicator, 26
Send Error Log information field, 71
Send file data/I/O memory data field, 71
Send Mail Tab, 51, 70
Send mail upon trigger field, 70
Send Request Switch, 85
Send status information field, 71
Send user data field, 71
SEND(090) instruction, 17, 137
transmission delay, 147
Sending Flag, 80
Server access interval time field, 68
Server specification type field, 67, 68, 74
servers
specifying, 22
service status, 82
Setup Tab, 50, 62
shock resistance
CJ-series, 14
CS-series, 13
short-circuits
precautions, xxiv
signals
precautions, xxiv
SMTP communications, 17
SMTP server, 5, 22
SMTP Tab, 51, 67
SNTP communications, 17
SNTP server, 10, 22
socket option, 157
Socket Service Request Switches, 84
socket services, 18, 50
creating communications applications, 7
FINS communications, 157
Parameter Areas, 88, 227
socket option, 157
Socket Service Request Switches, 84
TCP/IP, 8
troubleshooting, 227
UDP/IP, 8
SOCKET STATUS READ, 195, 235
sockets
closing
TCP, 180
UDP, 171
numbers, 157
opening
TCP, 172, 174
UDP, 167
reading status, 195
receiving data
TCP, 177
UDP, 168
sending data
TCP, 178
UDP, 169
status, 80
TCP sockets
status, 88, 235
troubleshooting, 214
Index
255
testing communications, 181
UDP sockets
troubleshooting, 211
software
configuration, 16
Software switch field, 71
specifications
Ethernet Units
CJ-series, 14
CS-series, 13
FINS communications, 135
SRES, 157
stack connections, 36
startup
procedure, 30
static electricity, xxiii
precautions, xxv
status
reading memory status, 193
reading protocol status, 189
reading socket status, 195
STD extension, 73
storage temperature
CJ-series, 14
CS-series, 14
Sub-net Mask field, 62
subnet masks, 48, 95
reading from Unit, 160
sub-response code, 156
See also SRES
switches
Socket Service Request Switches, 84
SYSMAC BUS/2, 136
SYSMAC LINK, 136
system configuration, 11
examples, 126
T
TCP Active Open Request Switch, 85
TCP CLOSE REQUEST, 180
TCP communications, 17
sockets
interface, 19
status, 235
troubleshooting, 214
status, 191
TCP indicator, 26
TCP Nodes Tab, 133
TCP OPEN REQUEST (ACTIVE), 174
TCP OPEN REQUEST (PASSIVE), 172
TCP Passive Open Request Switch, 85
TCP RECEIVE REQUEST, 177
TCP SEND REQUEST, 178
TCP/IP, 3, 8, 115
creating communications applications, 7
TCP/IP keep-alive, 49
TCP/UDP Open Flag, 80
terminal blocks, xxiii
Test command, 6, 73
Timer Area, 136
timers, 231
transmission
delays, 147
distance
CJ-series, 14
CS-series, 13
media
CJ-series, 14
CS-series, 13
path
CJ-series, 14
CS-series, 13
Trigger No. field, 70
troubleshooting
FINS communications, 210
FTP server, 217
procedures, 209
socket services, 227
startup, 209
TCP sockets, 214
UDP sockets, 211
UNIX error messages, 227
using indicators, 200
using response codes, 223
twisted-pair cables, 11
precautions, 35
recommended models, 35
TXT extension, 73
U
UDP CLOSE REQUEST, 171
UDP communications, 17
sockets
troubleshooting, 211
256
Index
UDP Nodes Tab, 132
UDP OPEN REQUEST, 167
UDP Open Request Switch, 85
UDP RECEIVE REQUEST, 168
UDP SEND REQUEST, 169
UDP/IP, 2, 8, 115
creating communications applications, 7
UDP/TCP sockets
status bits, 80
UMBackup command, 6, 73
Unit Number Switch, 23
unit numbers
setting, 31, 32
UNIX error messages, 227
Use IP address to protect field, 64
Use POP before SMTP field, 67
V
vibration resistance
CJ-series, 14
CS-series, 13
Visual BASIC, 12
Visual C++, 12
W
weight
CJ-series, 14
CS-series, 14
wiring
cables, 38
precautions, 38
word addresses, 90, 158
Word value change field, 71
Work Area, 136
257
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
The following table outlines the changes made to the manual during each revision. Page numbers refer to the
previous version.
Revision code Date Revised content
1 July 2003 Original production
02 March 2004 Information was added for new functions available with new versions of the CX-Programmer
and Ethernet Unit, including the Web function, described in new sub-section 2-8 and Appendix
G. The following revisions were also made.
Page xiv: Added information on unit versions.
Page 3: Added information for CX-Programmer version 4.0 or higher.
Page 7: Corrected or to and in paragraph on automatic clock adjustment.
Pages 8 and 9: Added information on Ethernet Units with Unit Ver. 1.3 or later.
Page 12: Added information on CX-Programmer version 4.0 or higher.
Page 17: Changed note
Page 25: Corrected information for ERH indicator.
Page 26: Added information on upgrade to unit version.
Page 28: Corrected 00.00.00.00 to 0.0.0.0 in Note 1.
Page 31: Corrected 1.2 to 0.9 and 0.8 to 0.4 in Note.
Page 40: Changed screen.
Page 41: Changed screen, corrected Right-click to Click in steps 6 and 7, and added new
sub-section on the Web function.
Page 43: Changed screen.
Page 45: Added settings to tables.
Page 47: Added table of settings for HTTP Tab, and swapped response and request in dia-
gram.
Pages 50 and 58: Changed screen.
Page 59: Added item to table and notes.
Page 60: Corrected 00.00.00.00 to 0.0.0.0 in table.
Page 71: Added information on HTTP Server Setup and changed screen.
Page 84: Changed 07CD hex to 07C0 hex
Page 85: Corrected 00.00.00.00 to 0.0.0.0 and corrected information for setting local IP
address.
Page 96: Added information on prohibiting dynamic conversion of remote IP addresses.
Pages 100 and 101: Corrected table headings.
Page 124: Added note.
Page 125: Corrected Controller Unit to Controller Link Unit in diagram.
Page 126: Corrected Ethernet Unit to Controller Link Unit in information on relay network
tables, and corrected 2 to 1 for the relay node address.
Pages 141 and 142: Changed PC to PLC.
Page 197: Removed (CJ Series only) from table.
Page 221: Added error codes to table.
Page 229: Added table on TCP status information.
Cat. No. W420-E1-04
Revision code
258
Revision History
03 June 2005 Information was added for new versions of the Ethernet Unit and minor corrections were also
made, including the following changes.
Page v: Added information on general precautions notation.
Page vii: Removed table.
Page xiii: Added information on warranty and liability.
Page 28: Added table.
Page 36: Changed cable in diagram.
Pages 45 and 247: Replaced diagram.
Pages 85 and 120: Changed n+24 to n+23.
Page 101: Added information on ETN11-compatible mode.
Page 123: Added note.
Page 243: Changed and added new parameter item.
04 January 2006 The following changes were made throughout the manual: added CJ1G-CPU@@P, changed
"CX-Net" to "CX-Integrator", and changed "CX-Programmer" to "CX-One".
Page xv: Removed manuals and added others and changed details for manuals W446 and
W336.
Pages xxiv and xxv: Added precautions.
Page 30: Changed the reference for creating I/O tables.
Page 40: Removed model number for the CX-Programmer and added information on relevant
manuals.
Page 41: Added information on unit version restrictions.
Pages 74 and 75: Changed "SMTP" to "SNTP".
Page 100: Removed "to be included in".
Pages 103 and 121: Changed the reference for FINS node address settings.
Page 166: Changed the reference for error code details.
Page 188: Changed the reference page for IP network addresses.
Page 205 and 206: Changed the reference for FINS settings.
Revision code Date Revised content
OMRON Corporation
Control Devices Division H.Q.
Shiokoji Horikawa, Shimogyo-ku,
Kyoto, 600-8530 Japan
Tel: (81)75-344-7109/Fax: (81)75-344-7149
Regional Headquarters
OMRON EUROPE B.V.
Wegalaan 67-69, NL-2132 JD Hoofddorp
The Netherlands
Tel: (31)2356-81-300/Fax: (31)2356-81-388
OMRON ELECTRONICS LLC
1 East Commerce Drive, Schaumburg, IL 60173
U.S.A.
Tel: (1)847-843-7900/Fax: (1)847-843-8568
OMRON ASIA PACIFIC PTE. LTD.
83 Clemenceau Avenue,
#11-01, UE Square,
Singapore 239920
Tel: (65)6835-3011/Fax: (65)6835-2711
OMRON (CHINA) CO., LTD.
Room 2211, Bank of China Tower,
200 Yin Cheng Zhong Road,
PuDong New Area, Shanghai, 200120 China
Tel: (86)21-5037-2222/Fax: (86)21-5037-2200
Authorized Distributor:
Cat. No. W420-E1-04 Note: Specifications subject to change without notice
Printed in Japan
This manual is printed on 100% recycled paper.