Size:
19.68 Mb
Download

Message Communications Errors Section 7-6

7-6

Message Communications Errors

 

 

 

 

The following table shows the main errors that may occur when messages are

 

sent or received. Refer to SECTION 14 Troubleshooting and Error Processing

 

for corrective measures and details on errors that are recorded in error log but

 

not indicated by the LED indicators.

 

 

 

 

 

 

 

 

 

 

Error

 

Indicators

 

Error code

 

 

 

 

 

(Hex)

 

 

MS

NS

7-segment

 

 

 

 

 

 

 

display

 

 

 

 

 

(See note.)

 

 

 

 

 

 

Routing table error

Flashing red

No change

HC

021A

 

 

 

 

 

IP address duplication error

No change

Lit red

F0

0211

 

 

 

 

 

CPU Unit service monitoring error

Flashing red

No change

HE

0002

 

 

 

 

 

Other CPU error

Not lit

H7

0006

 

 

 

 

 

 

Too many retries, cannot send

 

 

 

0103

 

 

 

 

 

Node address setting error, cannot send

 

 

 

0105

 

 

 

 

 

Remote node not part of network, cannot send

 

 

 

0107

 

 

 

 

 

No Unit with specified unit address, cannot send

 

 

 

0108

 

 

 

 

 

CPU Unit error occurred, cannot send

 

 

 

010B

 

 

 

 

 

Destination address not set in routing tables, cannot send

 

 

 

010D

 

 

 

 

 

Routing tables not registered, cannot send

 

 

 

010E

 

 

 

 

 

Routing tables error occurred, cannot send

 

 

 

010F

 

 

 

 

 

Too many relay connections, cannot send

 

 

 

0110

 

 

 

 

 

Maximum command length exceeded, cannot send

No change

No change

No change

0111

 

 

 

 

 

Header error; cannot send

 

 

 

0112

 

 

 

 

 

Reception buffer full, packet discarded

 

 

 

0117

 

 

 

 

 

Invalid packet discarded

 

 

 

0118

 

 

 

 

 

Local node busy, cannot send

 

 

 

0119

 

 

 

 

 

Unexpected routing error

 

 

 

0120

 

 

 

 

 

Service not supported in present mode, packet discarded

 

 

 

0122

 

 

 

 

 

Transmission buffer full, packet discarded

 

 

 

0123

 

 

 

 

 

Maximum frame length exceeded, routing impossible

 

 

 

0124

 

 

 

 

 

Packet discarded due to response time-out

 

 

 

0125

 

 

 

 

 

 

Note The7-segmentdisplay alternately displays the error and the node address of the node where the error occurred.

195

Message Communications Errors

Section 7-6

196

SECTION 8

FINS Communications

This section provides information on communicating on EtherNet/IP Systems and interconnected networks using FINS commands. The information provided in the section deals only with FINS communications in reference to EtherNet/IP Units or built-inEtherNet/IP ports.

FINS commands issued from a PLC are sent via the SEND(090), RECV(098), and CMND(490) instructions programmed into the user ladder-diagramprogram. Although an outline of these instructions is provided in this section, refer to theCS/ CJ-series Programmable Controllers Programming Manual (W340) for further details on programming these instructions.

8-1 Overview of FINS Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

198

 

8-1-1 Communications On an Ethernet Network. . . . . . . . . . . . . . . . . . . .

198

 

8-1-2 Using the FINS/UDP and FINS/TCP Methods . . . . . . . . . . . . . . . .

199

 

8-1-3 FINS Communications Service Specifications. . . . . . . . . . . . . . . . .

199

8-2

FINS/UDP Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

200

 

8-2-1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

200

8-3

FINS/TCP Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

202

 

8-3-1

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

202

8-4

Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207

 

8-4-1

Routing Table Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

207

 

8-4-2 Connecting and Using a Peripheral Device for the PLC . . . . . . . . .

208

 

8-4-3 Routing Table Setting Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . .

209

8-5

Using FINS Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

211

 

8-5-1

CX-Programmer (CX-Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

211

 

8-5-2

FinsGateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

215

8-6 Communicating between OMRON PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . .

220

 

8-6-1

Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . .

220

 

8-6-2 PLC Communications Data Areas . . . . . . . . . . . . . . . . . . . . . . . . . .

221

 

8-6-3 Using SEND(090), RECV(098), and CMND(490) . . . . . . . . . . . . .

222

 

8-6-4

Writing Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

226

 

8-6-5

Program Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

230

8-7 Precautions on High Traffic in FINS Communications . . . . . . . . . . . . . . . . .

232

197

Overview of FINS Communications

Section 8-1

8-1Overview of FINS Communications

8-1-1Communications On an Ethernet Network

The EtherNet/IP Units and built-inEtherNet/IP ports support the FINS communications service, which can be used simultaneously with the CIP communications service.

FINS communications data is sent and received as UDP/IP packets or TCP/IP packets.

PLC

or host computer

EtherNet/IP Unit

Packet (FINS command)

Ethernet (EtherNet/IP)

Packet (FINS response)

EtherNet/IP Unit

PLC

In the FINS communications service, both an IP address for IP (the Internet layer) and a FINS node address for FINS (the application layer) are used for the remote device. Also, 9600 is used as the default setting for the local UDP or TCP port number (i.e., the transport layer) for identifying the application layer, i.e., the FINS communications service. (Another number can be set for the FINS/UDP port from the Setup Tab Page in the Unit Setup.)

For details on pairing FINS node addresses with IP addresses and UDP/TCP port numbers, refer to 5-2 IP Addresses in FINS Communications.

Application Layer

Transport Layer

Internet Layer

Physical Layer

FINS

 

 

Node Number

UDP

TCP

UDP Port No.

TCP Port No.

IP

 

 

IP Address

Ethernet

 

 

Ethernet Address

The FINS communications service is a communications method based on UDP/IP, and it is supported by most OMRON Ethernet-relatedproducts. (In this manual it is called the FINS/UDP method.) In addition to supporting the FINS/UDP method, theCJ2H-CPU@@-EIP,CJ2M-CPU3@,CS1W-EIP21,andCJ1W-EIP21support FINS communications using TCP/IP. (In this manual, this is called the FINS/TCP method.)

198

Overview of FINS Communications

Section 8-1

8-1-2Using the FINS/UDP and FINS/TCP Methods

It is recommended that FINS/UDP and FINS/TCP be used as follows:

When remote devices do not support the FINS/TCP method:

Use the FINS/UDP method for FINS communications with those devices.

When FINS nodes are connected on the same Ethernet segment: Use the FINS/UDP method between those nodes.

Note FINS/UDP offers a slight advantage in performance.

When FINS nodes are connected over multiple IP network layers: Use the FINS/TCP method between those nodes.

Note FINS/TCP offers superior communications quality.

When the quality of connections is unreliable, as with wireless LAN: Use the FINS/TCP method between those nodes.

Note FINS/TCP offers superior communications quality.

8-1-3

FINS Communications Service Specifications

 

 

 

 

 

Item

 

Specifications

 

 

 

Number of nodes

254

 

 

 

 

Message length

2,012 bytes max.

 

 

 

 

Number of buffers

192

 

 

 

 

Protocol name

FINS/UDP method

FINS/TCP method

 

 

 

Protocol used

UDP/IP

TCP/IP

 

 

 

Number of connections

---

16

 

 

 

Port number

9600 (default)

9600 (default)

 

 

Can be changed.

Can be changed.

 

 

 

Protection

No

Yes (Specification of client IP addresses when Unit is used as a

 

 

 

server)

 

 

 

 

Other

 

Items set for each UDP

Items set for each connection

 

 

port

• Server/client specification

 

 

• Broadcast

 

 

• Remote IP address specification

 

 

• IP Address Conversion

When client: Specify the IP address of the remote Unit (server).

 

 

 

 

 

 

When server: Specify IP addresses of clients permitted to con-

 

 

 

nect.

 

 

 

• Automatic FINS node address allocation:

 

 

 

Specify automatic allocation of client FINS node addresses.

 

 

 

Keep-alive:

 

 

 

Specify whether remote node keep-aliveis to be used.

 

 

 

TCP/IP Setting

 

 

 

• Remote node keep-alivetime

 

 

 

Internal table

This a table of correspondences for remote FINS node addresses, remote IP addresses, TCP/

 

 

UDP, and remote port numbers. It is created automatically when power is turned ON to the

 

 

PLC or when the Ethernet Unit is restarted, and it is automatically changed when a connection

 

 

is established by means of the FINS/TCP method or when a FINS command received.

The following functions are enabled by using this table.

IP address conversion using the FINS/UDP method

Automatic FINS node address conversion after a connection is established using the FINS/ TCP method

Automatic client FINS node address allocation using the FINS/TCP method

Simultaneous connection of multiple FINS applications

199

FINS/UDP Method Section 8-2

8-2

FINS/UDP Method

 

 

 

 

8-2-1

Overview

 

 

 

 

 

 

 

 

 

 

FINS/UDP Features

The FINS/UDP method is a FINS communications method that uses the UDP/

 

 

IP protocol. UDP/IP is a connectionless communications protocol. When a

 

 

message is sent from one node to another, the two nodes have an equal rela-

 

 

tionship and there is no clear connection. If using TCP is like making a tele-

 

 

phone call, then UDP is more like delivering a memo by hand. Although the

 

 

UDP protocol is fast, data communications are less reliable than with TCP.

 

 

In particular, when sending large amounts of data involving significant routing,

 

 

the user must program measures, such as retries, into applications in order to

 

 

improve reliability.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node

 

 

Node

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Data transmission 1

 

 

 

 

 

 

 

 

 

 

Data transmission 2

 

 

 

 

 

 

 

 

 

 

Data transmission 3

 

 

 

 

 

 

 

 

Data is sent in one direction, with no

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

confirmation of whether the data was

 

 

 

 

 

 

 

 

received. Because there are few procedures

 

 

 

 

 

 

 

 

involved, data can be sent at high speed but

 

 

 

 

 

 

 

 

with less reliability than with TCP.

 

 

 

 

The FINS/UDP method has the following features:

Because FINS/UDP is a connectionless protocol, there is no limit to the number of corrections.

FINS/UDP can be used for broadcasting.

When data is sent via an IP network with multiple layers (such as the Internet), communications reliability drops.

FINS/UDP Frame Format The following diagram shows the structure of a UDP packet used for sending and receiving data on an Ethernet network.

Ethernet Ver. 2

IP

UDP

FINS frame

FCS

 

 

 

 

 

UDP packet

As the diagram shows, a nested structure is used with the FINS/UDP method, i.e., Ethernet Ver. 2, IP frame, UDP frame, and FINS frame. A UDP data section (FINS frame) that exceeds 1,472 bytes is split into packets for transmission. The split UDP data is then joined automatically at the UDP/IP protocol layer. There is normally no need to pay attention at the application layer to this split, but it may not be possible to send 1,472-byteUDP packets over an IP network with multiple layers. When using the FINS communications service in a system such as this, select the FINS/TCP method.

200

FINS/UDP Method

Section 8-2

UDP Port Numbers for FINS/UDP

The UDP port number is the number for UDP to identify the application layer (i.e., the FINS communications service in this case). When communications are executed by UDP/IP, this port number must be allocated to the communications service.

The default setting for the UDP port number (i.e., the UDP port number of the EtherNet/IP Unit or built-inEtherNet/IP port) is 9600. To set another number, set the number on the FINS/UDP Tab Page of theCX-ProgrammersEdit Parameters Dialog Box.

At the EtherNet/IP Unit or built-inEtherNet/IP port, a UDP/IP frame received with a FINS/UDP port number is recognized as a FINS frame.

Procedure for Using FINS/UDP

1,2,3... 1. Make the basic settings.

Refer to Initial Settingsin 3-1-1 Procedures.

2.Keep the CX-Programmerconnected online,right-clickthe EtherNet/IP Unit orbuilt-inEtherNet/IP port in the PLC IO Table Dialog Box, and selectEdit - Unit Setup. Set the following in the CPU Bus Unit Setup Area from the FINS/UDP Tab Page of the Edit Parameters Dialog Box.

IP Address Conversion

FINS/UDP Port No. (Default: 9600)

IP Address List (Set only when the conversion method is set to IP address table.)

Dynamic Change of remote IP addresses

3.Select Transfer to PLC from the PLC Menu and click theYes Button. The setting data will be transferred to the CPU Bus Unit System Setup Area in the CPU Unit.

4.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.

5.Create a ladder program that includes the SEND(090), RECV(098), and CMND(490) instructions.

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.

201

FINS/TCP Method

Section 8-3

8-3FINS/TCP Method

8-3-1Overview

FINS/TCP Features

The FINS/TCP method is a FINS communications method that uses the TCP/ IP protocol. TCP/IP is a connection-typecommunications protocol. Before a message is sent from one node to another, it is necessary to establish a virtual circuit, i.e., a connection. Once a connection has been established, communications 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.

When FINS/TCP is used, it must be determined which node is the server and which nodes are the clients.

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 communications between two PLCs, either one can be set as the client and the other as the server.

Node

 

 

Node

 

(Client)

 

 

(Server)

 

 

 

 

 

 

 

 

 

 

Request to establish a connection

 

 

Connection

 

 

 

 

 

 

 

Notification of establishing

 

 

established

 

 

 

 

 

 

connection

 

 

 

 

 

 

Acknowledgement

 

 

 

 

 

 

Data transmission 1

 

 

 

 

 

Acknowledgement

 

 

 

 

 

 

 

 

 

 

 

 

An acknowledgement is received whenever a connection is established or data is sent, so transmissions are more reliable but somewhat slower.

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 processing 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-specifiedIP addresses).

Broadcasting cannot be used.

TCP/IP has various retry procedures, and this tends to lower its performance 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.

202

FINS/TCP Method

Section 8-3

FINS/TCP Frame Format

TCP Port Number for FINS/TCP

FINS/TCP Connection

Numbers

After a FINS/TCP connection (connection number, remote IP address) has been set in the FINS/TCP Tab Page of the Network Configurator’s Edit Parameters Dialog Box, it can be dynamically changed from the ladder program using a FINS command (i.e., FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST).

The following diagram shows the structure of a TCP packet sent over an Ethernet network.

Ethernet Ver. 2

IP

TCP

FINS/TCP header

FINS frame

FCS

 

 

 

 

 

 

TCP packet

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 setting of 1,024 bytes in the EtherNet/IP Unit or built-inEtherNet/IP port, 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/IP Unit orbuilt-inEtherNet/IP port and FinsGateway (Ver. 2003 or higher) the appropriate frames are separated out automatically, so there is normally no need to be pay attention to it at the application layer.

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 communications service.

The default setting for the TCP port number (i.e., the TCP port number of the EtherNet/IP Unit or built-inEtherNet/IP port) is 9600. To set another number, make the setting for the FINS/TCP port on the FINS/TCP Tab Page of the CXProgrammer’s Edit Parameters Dialog Box.

The FINS/TCP port number set in the FINS Configuration Tab Page 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/IP Unit or built-inEtherNet/IP port and FinsGateway (Ver. 2003 or higher), an unused TCP port is automatically detected and utilized.)

At the EtherNet/IP Unit or built-inEtherNet/IP port, 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 allows up to 16 FINS/TCP connections to be established simultaneously, and these 16 connections are managed at the EtherNet/IP Unit or built-inEtherNet/IP port by connection numbers. When setting FINS/TCP connection settings in the FINS/TCP Tab Page of the Network Configurator’s Edit Parameters Dialog Box, set them individually using these connection numbers.

203

FINS/TCP Method

Section 8-3

FINS/TCP Connection Status (Word n+24)

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 terminated by a communications error or a FINS command (i.e., FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST).

 

15

14

13

12

11

10

09

08

07

06

05

04

03

02

01

00

 

 

n+24

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

*: Bit 15 corresponds to connection No. 16, bit 00 to connection No. 1, etc.

Note

The starting word of the FINS/TCP Connection Status Area is different in the

 

CS1W-ETN21andCJ1W-ETN21Ethernet Units; it is n+23 in the Ethernet

 

Units. If a ladder program using FINS/TCP communications was created for

 

Ethernet Units, and is being reused for EtherNet/IP Units and built-inEther-

 

Net/IP ports, change the word starting word address for this area from n+23 to

 

n+24.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS/TCP

With FINS/TCP, FINS node addresses are exchanged immediately after a

Communications

connection is established. This makes it possible to determine the FINS node

Procedure

addresses to which the 16 connection numbers, and to manage them in an

 

internal table.

Personal computer

 

Ethernet/IP Unit

(Client)

 

(Server)

 

 

 

 

 

Example:

 

Example:

IP address C

 

IP address S

FINS node number A

 

FINS node number B

 

 

 

 

 

 

 

 

 

 

 

 

 

Passive open

 

 

Connection request (C→S)

 

 

Active open

 

 

 

 

 

 

 

 

 

 

Connection established

 

Connection established

 

 

FINS node number A sent

 

 

Local node No. sent

Remote node No. received

 

 

 

FINS node number B sent

 

 

Remote node No. received

Local node No. sent

 

FINS frame sent

 

FINS frame sent

 

 

Full duplex communications

Connection established

FINS node numbers exchanged

Normal data communications

After a connection has been established as a FINS/TCP server, it is terminated in the following ways.

When the connection is closed by the client.

When a FINS command to close the connection (FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST) is sent by the client.

When there is no response from the client when the keep-alivefunction is in effect.

204

FINS/TCP Method

Section 8-3

After a connection has been established as a FINS/TCP client, it can be terminated in the following ways.

If the connection is closed by the server.

If there is no response from the client when the keep-alivefunction is in effect.

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/IP Unit orbuilt-inEtherNet/IP port is powered up or restarted, the IP address for the connection used as the FINS/TCP client is the remote IP address that was set in the FINS/TCP Tab Page of theCX-Pro-grammer’s Edit Parameters Dialog Box. To dynamically change the remote IP address (i.e., during CPU Unit operation), 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/IP Unit orbuilt-inEtherNet/IP port.

Procedure for Using FINS/TCP

1,2,3... 1. Make the basic settings.

Refer to Initial Settingsin 3-1-1 Procedures.

2.Make the following settings on the FINS/TCP Tab Page of the CX-Pro-grammer's Edit Parameters Dialog Box.

FINS/TCP port (default: 9600)

Server/Client: Specifies whether the connection will operate in FINS/ TCP server mode or client mode.

Target IP address for client: Specifies the IP address of the target FINS/TCP server.

Target IP address for server: Specifies allowed client IP addresses when protection is enabled.

Automatically allocated FINS node address for server: Specifies the address to allocate when automatically allocating a FINS node address to the target FINS/TCP client.

Keep-alive:Specified whether to use thekeep-alivefunction.

Note Normally this function is used and the option is selected.

Enable protect via IP address:

Note Select this option only when protecting as the server.

3.Select Transfer to PLC from the PLC Menu and click theYes Button. The setting data will be transferred to the CPU Bus Unit System Setup Area in the CPU Unit.

4.Make the routing table settings and transfer them to each PLC. (See note 1.)

Set the routing tables with CX-Integrator,and transfer it to each PLC.

5.Create a ladder program that includes the SEND(090), RECV(098), and CMND(490) instructions.

Note (1) 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-Programmer)

When multiple Communications Units are mounted to a single PLC (i.e., CPU Unit)

205

FINS/TCP Method

Section 8-3

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.

(2)If EtherNet/IP is selected for CX-Programmercommunications, FINS message communications and remote programming/monitoring from theCX-Programmerwill be possible as long as CIP routing is possible for the entire communications path. Routing tables do not need to be set. If FINS messages are sent from a PLC, however, then routing tables must be set.

206

Routing Tables

Section 8-4

8-4Routing Tables

When the FINS communications service is used, routing tables must be created 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.

 

 

8-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.

 

 

Example

 

 

 

 

 

 

 

 

 

 

 

 

Unit #04

 

 

 

 

 

 

 

 

 

 

 

 

Unit #05

 

 

 

 

 

 

 

 

 

 

 

 

Unit #06

 

 

 

 

 

 

 

 

 

 

 

 

Unit #07

Local Network Table

 

 

 

 

 

 

 

 

 

 

 

 

Local network

Unit number

 

 

 

 

 

 

 

 

 

 

 

 

 

address

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1

04

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2

05

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3

06

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #1

4

07

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #4

 

 

 

 

Note

1. The unit number is set (0 to F: 1 to 15) using the rotary switch on the front

 

 

 

of the EtherNet/IP Unit (built-inport).

 

 

 

 

 

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 network, 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.

207

Routing Tables

Section 8-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).

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #3

 

Node #2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit #0

PLC #4 (destination node)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(relay node)

 

 

 

 

 

 

 

 

 

 

PLC #2 (relay node)

 

Node #1

 

 

 

PLC #1 (local node)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node #3

 

Unit #1

 

 

 

 

 

 

 

 

Node #1

 

 

 

Node #2

 

 

 

 

 

 

 

 

 

 

 

 

 

Node #2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node #1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #1

 

Network #2

Network #3

 

 

 

PLC #1

 

 

 

PLC #2

 

 

 

PLC #3

 

End network

relay network table

 

relay network table

local network table

 

 

 

 

End Relay

Relay

 

End Relay

Relay

Local

 

Unit

 

 

 

 

 

network

 

 

 

 

 

network network

node

 

network network

node

address

 

number

 

 

 

2 1 3

3 1 3

To go to network #3, first go to node #3 at network #1.

3 2 2

To go to network #3, first go to node #2 at network #2.

2 0

3 1

(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.)

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 routing tables for a message to reach PLC #1 from PLC #4. Refer to8-4-3 Routing Table Setting Examples for routing table setting examples.

8-4-2Connecting and Using a Peripheral Device for the PLC

Routing tables must be created by a CX-Integratorconnected to the PLC. (They cannot be created using a Programming Console.) For details on how to connect and use theCX-Integrator,refer to theCX-Integrator Operation Manual (W445).(CX-Integratoris automatically installed whenCX-Oneis installed.)

Note 1. When routing tables are transferred from theCX-Integratorto the PLC, all of the CPU Bus Unit are reset so that the routing tables that have been created can be read and enabled. Before transferring the routing tables, confirm that there will be no problems in the system when the CPU Bus Units are reset.

2.To transfer routing tables for multiple nodes to a PLC in one batch, connect the CX-Integratorto a PLC with only one Communications Unit mounted. Routing tables cannot be transferred to other nodes from a PLC with multiple 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-Integratoris connected.

208

Routing Tables

Section 8-4

8-4-3Routing 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 multiple CPU Bus Units are mounted.

Ethernet (EtherNet/IP) network

Controller Link network

(Network #A)

(Network #B)

E C C P

I L P S

P K U

Unit #a Unit #b

Local Network Table

No.

Local

CPU Bus

 

network

Unit

1

A

a

2

B

b

 

 

 

Example 2: Three Interconnected Networks

PS: Power Supply Unit

CPU: CPU Unit

EIP: EtherNet/IP Unit

CLK: Controller Link Unit

This example shows the relay network table settings for three different interconnected networks.

Relay Network Table

 

 

 

 

No.

End

Relay

Node

 

 

 

 

network

network

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #1

 

 

 

 

 

 

 

1

B

A

b

 

 

Node #a

 

2

C

A

b

Network #A

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #2

 

 

 

 

 

 

 

Node #b

 

1

C

B

e

 

 

 

 

 

Node #c

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #3

 

 

 

 

 

 

 

1

A

B

c

Network #B

 

Node #d

 

2

C

B

e

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #4

 

 

 

 

 

 

 

Node #e

 

1

A

B

c

 

 

 

Network #C

 

Node #f

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #5

 

 

 

 

 

 

1

A

C

f

 

 

 

 

 

Node #g

 

2

B

C

f

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In the table for PLC #3, for example, if network #A is taken as the end network, 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.

209

Routing Tables

Section 8-4

Example 3: All Nodes

This example uses the following configuration to show the routing tables for all nodes.

 

 

 

 

 

 

 

Unit #5

E

PLC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node #6

I

1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

P

 

 

 

 

 

 

 

 

Network #10

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit #3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit #4

 

 

 

 

Node #4

C

E

PLC

 

 

 

 

 

E

S

 

PLC

 

Node #5

 

 

 

 

L

I

 

 

 

 

 

I

L

 

 

 

 

Unit #7

 

 

 

 

Unit #2

K

P

2

 

 

 

 

 

P

K

 

3

 

 

 

 

 

 

 

Node #3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node #15

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #20

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Network #30

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

C

 

PLC

 

 

 

C

PLC

 

 

S

 

PLC

 

S

PLC

 

 

 

 

L

 

 

 

 

L

 

 

L

 

 

L

 

 

 

 

 

4

 

 

 

5

 

 

 

 

 

 

 

6

 

 

7

 

 

 

 

 

K

 

 

 

 

K

 

 

 

 

K

 

 

 

 

 

K

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit #0

 

Unit #1

Unit #5

 

Unit #6

 

 

 

Node #1

 

Node #2

Node #5

 

Node #10

 

PLC #1 Routing Table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(Local network table)

 

 

 

 

(Relay network table)

 

 

No.

Local

CPU Bus

 

 

 

 

 

End

 

 

 

Relay

Relay

 

 

 

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

 

 

 

 

No. network

network

node

 

 

 

 

 

 

 

 

 

 

1

010

 

 

05

 

 

 

 

 

1

020

 

 

 

 

010

 

004

 

 

2

 

 

 

 

 

 

 

 

 

 

 

2

030

 

 

 

 

010

 

005

 

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #2 Routing Table

 

 

 

 

(Relay network table)

 

(Local network table)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

End

 

 

 

Relay

Relay

 

 

No.

Local

CPU Bus

 

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

 

No. network

network

node

 

 

 

 

 

 

 

1

010

 

 

03

 

 

 

 

 

1

030

 

 

 

 

010

 

005

 

 

2

020

 

 

02

 

 

 

 

 

2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #3 Routing Table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(Local network table)

 

 

 

 

(Relay network table)

 

 

 

 

 

 

 

 

 

 

End

 

 

 

Relay

Relay

 

No.

Local

CPU Bus

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

No. network

network

node

 

 

 

 

1

010

 

 

04

 

 

 

 

 

1

020

 

 

 

 

010

 

004

 

2

030

 

 

07

 

 

 

 

 

2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #4 Routing Table

 

 

 

(Relay network table)

 

(Local network table)

 

 

 

 

 

No.

Local

CPU Bus

 

 

 

 

 

End

 

 

 

Relay

Relay

 

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

No. network

network

node

 

 

 

 

1

020

 

 

00

 

 

 

 

 

1

010

 

 

 

 

020

 

003

 

2

 

 

 

 

 

 

 

 

 

 

 

2

030

 

 

 

 

020

 

003

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #5 Routing Table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(Local network table)

 

 

 

 

(Relay network table)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

No.

Local

CPU Bus

 

 

 

 

 

End

 

 

 

Relay

Relay

 

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

No. network

network

node

 

 

 

 

1

020

 

 

01

 

 

 

 

 

1

010

 

 

 

 

020

 

003

 

2

 

 

 

 

 

 

 

 

 

 

 

2

030

 

 

 

 

020

 

003

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #6 Routing Table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(Local network table)

 

 

 

 

(Relay network table)

 

No.

Local

CPU Bus

 

 

 

 

 

End

 

 

 

Relay

Relay

 

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

No. network

network

node

 

 

 

 

1

030

 

 

05

 

 

 

 

 

1

010

 

 

 

 

030

 

015

 

2

 

 

 

 

 

 

 

 

 

 

 

2

020

 

 

 

 

030

 

015

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC #7 Routing Table

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(Local network table)

 

 

 

 

(Relay network table)

 

 

 

 

 

 

 

 

 

End

 

 

 

Relay

Relay

 

No.

Local

CPU Bus

 

 

 

 

 

 

 

 

 

network

Unit No.

 

 

No. network

network

node

 

 

 

 

1

030

 

 

06

 

 

 

 

 

1

010

 

 

 

 

030

 

015

 

2

 

 

 

 

 

 

 

 

 

 

 

2

020

 

 

 

 

030

 

015

 

3

 

 

 

 

 

 

 

 

 

 

 

3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

210

Using FINS Applications

Section 8-5

8-5Using FINS Applications

8-5-1CX-Programmer(CX-Server)

The following examples show how to connect online from a CX-Programmeron 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 (Dynamic) generation method

CX-Programmer/CX-Integrator

 

 

 

 

 

Node number: 1

EtherNet/IP Unit

 

 

 

 

 

 

 

 

 

 

IP address: 192.168.250.1

 

 

 

 

 

IP address conversion: Automatic

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

generation method (dynamic)

 

 

 

 

 

 

 

Ethernet port

Ethernet or EtherNet/IP (Network address: None)

FINS/UDP method

EtherNet/IP Unit node number: 2 EtherNet/IP Unit IP address: 192.168.250.2

Target: PLC1

CX-Programmer'sChange PLC Dialog Box

Settings for target PLC (PLC1)'s Change PLC Dialog Box

Setting

 

 

 

 

PLC name

 

 

PLC1

 

 

 

 

Network classification

 

 

Ethernet

 

 

 

 

Network Tab Page

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 Page

Workstation node address

1

 

 

 

 

Automatic generation method

Not selected

 

 

 

 

 

IP address

 

192.168.250.2 (Eth-

 

 

 

erNet/IP Unit or

 

 

 

built-inEtherNet/IP

 

 

 

port IP address)

 

 

 

 

 

Port number

 

9600

 

 

 

 

CX-Programmer'sFINS/UDP Tab Page in Edit Parameters Dialog Box

Item

Setting

 

 

FINS/UDP Port

Default (9600)

 

 

IP Address Conversion

Automatic (Dynamic) generation method

 

 

IP Router Table

None

 

 

211

Using FINS Applications

Section 8-5

Example: Inputs to the CX-Programmer'sSetup Window

Example: Change PLC Settings

Example: Network Settings (Network Tab Page)

Note When FinsGateway is selected as the network type, make sure that the frame length is set to 2,000 bytes max.

212

Using FINS Applications

Section 8-5

Example: Network Settings (Driver Tab Page)

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-Integratorconnected to the Ethernet network.

Conditions

FINS/UDP method

IP address conversion: Automatic generation method (dynamic)

CX-Programmer/CX-IntegratorController

Link Unit

Node address: 1

IP address: 192.168.250.1

EtherNet/IP Unit

IP address conversion: Automatic generation method (dynamic)

Gateway between networks

 

PLC1

EtherNet/IP Unit node address: 2

 

EtherNet/IP Unit IP address: 192.168.250.2

Ethernet port

EtherNet/IP Unit unit number: 0

 

Controller Link Unit node address: 1

 

Controller Link Unit unit number: 1

Controller Link Unit

Target PLC

Controller Link Unit

Ethernet or EtherNet/IP

 

 

(network address 1)

PLC2

 

PLC3

 

 

Routing

 

 

according to

 

 

routing table

Node address 2

Node address 3

 

Routing to final network address 2

 

 

 

Controller Link (network address 2)

requires relaying through node

 

 

 

address 2 of relay network address

 

 

 

1 (EtherNet/IP Unit).

 

 

 

CX-Programmer'sChange PLC Dialog Box

Settings for target PLC (PLC3)'s Change PLC Dialog Box

Setting

 

 

 

 

PLC name

 

 

PLC3

 

 

Network classification

Ethernet

 

 

 

 

Network Tab

FINS destination

FINS transmission

1

Page

 

source address

 

 

 

 

 

 

 

Network number

2

 

 

 

 

 

 

Node address

3

 

 

 

 

 

Frame length

2,000 bytes

 

 

 

 

Response monitor time

2 seconds

 

 

 

 

213

Using FINS Applications

Section 8-5

 

 

 

 

 

Settings for target PLC (PLC3)'s Change PLC Dialog Box

Setting

 

 

 

 

Driver Tab Page

Workstation node address

1

 

 

 

 

 

 

Automatic generation method

Not selected

 

 

 

 

 

 

IP address

192.168.250.2 (Eth-

 

 

 

erNet/IP Unit or

 

 

 

built-inEtherNet/IP

 

 

 

port IP address)

 

 

 

 

 

 

Port number

9600

 

 

 

 

CX-Programmer'sFINS/UDP Tab Page in Edit Parameters Dialog Box

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 selectRouting table Settings. Then create FINS local routing tables (a local network table and a relay network table).

Example: PLC 1 Routing Table Settings

Local Network Table

Unit number

Local network number

 

 

0

1

 

 

1

2

 

 

Relay Network Table None

Example: PLC 2 and PLC 3 Routing Table Settings

Local Network Table

Unit number

Local network number

 

 

0

2

 

 

• 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.

 

Final network number

Relay network number

Relay node address

 

 

 

 

 

1

2

1

 

 

 

 

2.

Save the routing table file (File - Save local routing table file).

3.

Next, to connect online, select Communication Settings from the Net-

 

work Menu. For each PLC, register a PLC with a direct serial connection

 

(node address: 0), and select it.

 

4.

With the CX-Integrator,selectWork Online from the Network Menu.

5.

Select Tools - Start Routing table, read the saved file, and selectOp-

 

tions - Transfer to PLC. Click Yes to transfer the routing tables to the con-

 

nected PLC.

 

 

214