Size:
19.68 Mb
Download

IP Addresses in FINS Communications

Section 5-2

• Ethernet address:

A fixed number is assigned to each EtherNet/IP

 

Unit or built-inEtherNet/IP port and it cannot be

 

changed.

• IP address:

Use the default IP address

 

(192.168.250.FINS_node number), set the

 

address in the allocated DM Area words, or set

 

the address on the TCP/IP Tab Page of the Edit

 

Parameters Dialog Box from the CX-Program-

 

mer.

• FINS/UDP port No.:

Use the default FINS/UDP port number (9600) or

 

set the number on the FINS/UDP Tab Page of

 

the Edit Parameters Dialog Box from the CX-Pro-

 

grammer.

• FINS/TCP port No.:

Use the default FINS/TCP port number (9600) or

 

set the number on the FINS/UDP Tab Page of

 

the Edit Parameters Dialog Box from the CX-Pro-

 

grammer.

• FINS node address:

Set the number using the Node Address Setting

 

Switches (NODE NO.) on the front of the Ether-

 

Net/IP Unit or built-inEtherNet/IP port.

Pairing IP Addresses with FINS Node Addresses at Local Nodes

A particular IP address is allocated to each communications node, including EtherNet/IP Units and built-inEtherNet/IP ports. The IP address must be paired with the FINS node address (1 to 254) by one of the following methods.

Automatic Generation Method (Dynamic/Static)

Set the relationship between the IP address and the FINS node address setting in the EtherNet/IP Unit or built-inEtherNet/IP port according to the following equation. If the setting does not conform to this equation, a setting error will be generated and the MS Indicator will flash red.

FINS node address = IP address host number

IP Address Table Method and Combined Method

Sending FINS Messages from EtherNet/IP Units or Built-inEtherNet/IP Ports

With these methods, the IP address and the FINS node address setting in the EtherNet/IP Unit or built-inEtherNet/IP port have no particular relationship. Set both the FINS node address and the IP address so that they are not duplicated in the network.

When the EtherNet/IP Unit or built-inEtherNet/IP port sends a FINS message, it is necessary to determine the remote node's IP address, UDP port number, and TCP port number. The relationships between all addresses, such as remote FINS node addresses and IP addresses, are managed by an internal table at the EtherNet/IP Unit orbuilt-inEtherNet/IP port.

Remote FINS node

Remote IP address

Connection

Remote port

address

(Example)

 

number (Example)

 

 

 

 

1

192.168.250.1

UDP

9600

 

 

 

 

2

192.168.250.2

UDP

9600

 

 

 

 

to

 

 

 

 

 

 

 

254

192.168.250.254

UDP

9600

 

 

 

 

When the EtherNet/IP Unit or built-inEtherNet/IP port is turned ON or restarted, the internal table is generated automatically from the various settings that have been made. Depending on the setting method used, data such as remote IP addresses may be changed dynamically. (Dynamic changes can be prohibited.)

95

IP Addresses in FINS Communications

Section 5-2

 

 

 

FINS header

FINS data

 

 

 

Remote node

 

 

 

 

 

 

 

 

 

 

Internal table

Remote port

 

 

 

 

 

 

 

Remote FINS

Remote IP

 

 

 

 

 

 

 

 

node number

address (Example) Connection

number

 

 

 

Application level

FINS

 

 

(Example)

 

 

 

 

 

1

192.168.250.1

UDP

9600

 

 

 

Node number

2

192.168.250.2

UDP

9600

 

 

 

 

 

!

 

 

 

 

 

 

 

 

 

 

!

 

 

 

 

 

 

 

 

 

 

!

 

 

 

 

 

 

Transport level

UDP

 

TCP TCP port

254

192.168.250.254

UDP

9600

 

 

 

UDP port

 

 

 

 

 

 

 

Application level

FINS

 

 

 

 

 

number

number

Node number

 

Internet level

IP

 

 

 

 

 

 

 

IP address

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Transport level

 

 

 

UDP port

 

TCP port

Physical level

Ethernet

 

 

 

UDP

TCP

 

 

Ethernet address

 

 

number

number

 

 

 

 

Internet level

 

IP

 

 

IP address

 

The remote node's IP address, UDP/TCP

 

 

 

 

 

 

 

 

Physical level

 

Ethernet

 

 

 

method, UDP port number, and TCP port

 

 

Ethernet address

 

number are calculated from the node

 

 

 

 

 

 

number in the FINS message, and an

 

 

 

 

 

 

 

 

Ethernet frame is generated.

 

 

 

Ethernet V2

IP

UDP

FINS header

FINS data

5-2-2Pairing Addresses in Internal Tables

FINS/UDP Communications Methods

Automatic Generation (Dynamic)

When the EtherNet/IP Unit or built-inEtherNet/IP port is turned ON or restarted, the following values are set for addresses in the internal table.

• Remote IP address:

Local IP address network number + remote

 

FINS node address

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

With the dynamic method, data in an internal table that has been generated can be dynamically converted according to FINS messages received from remote nodes. This is enabled when the remote node is a device such as a personal computer and IP addresses are dynamically changed by a method such as DHCP.

EtherNet/IP Unit

CPU Unit

Personal computer

 

Remote FINS node number

 

 

Must be fixed.

Change

Local FINS node number

registration

 

Local FINS node number

Automatic generation

(dynamic setting)

Can be changed.

Internal table

 

Local IP address

Remote IP address

Local IP address

 

IP address FINS command

Ethernet (EtherNet/IP)

 

IP addressFINS response

For the remote IP address, a response is returned to the changed IP address.

96

IP Addresses in FINS Communications

Section 5-2

Automatic Generation (Static)

With the static method as well, the following values are set for addresses in the internal table when the EtherNet/IP Unit or built-inEtherNet/IP port is turned ON or restarted.

• Remote IP address:

Local IP address network number + remote

 

FINS node address

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

With the static method, however, data in an internal table that has been generated is not freely changed.

 

 

EtherNet/IP Unit

CPU Unit

Personal computer

 

 

Remote FINS node number

 

 

 

 

Must be fixed.

 

Local FINS node number

 

 

 

Local FINS node number

 

Automatic generation

 

(static setting)

 

Must be fixed.

 

Internal table

 

 

Local IP address

 

Remote IP address

Local IP address

 

 

IP address FINS command

Ethernet (EtherNet/IP)

 

IP addressFINS response

IP Address Table Method With this method, FINS node addresses are converted to IP addresses based on a preset correspondence table (IP address table).

The IP address table is set on the FINS/UDP Tab Page of the Edit Parameters Dialog Box of the CX-Programmer.Nodes can be registered even if they are in different segments and have different network IDs

The internal table will be as follows:

FINS Node Address Registered to IP Address Table The following address is registered to the internal table.

• Remote IP address:

IP address registered to IP address table

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

FINS Node Address Not Registered to IP Address Table The following address is registered to the internal table.

• Remote IP address:

0.0.0.0

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

With the IP address table method, records of FINS nodes registered to the IP address table are not changed dynamically. When the Unit is turned ON or restarted, the IP addresses of remote FINS nodes registered with an IP address of 0.0.0.0 can be changed dynamically according to FINS messages received from remote nodes. This can be used effectively when the remote node is a device such as a personal computer and IP addresses are dynamically changed by a method such as DHCP.

97

IP Addresses in FINS Communications

 

 

 

Section 5-2

 

Example

 

 

 

 

 

When FINS Command is Sent

 

 

 

 

FINS node number

 

 

 

 

 

 

IP address table

 

 

 

FINS node

IP address

 

 

 

number

 

 

 

Node number in

 

 

 

 

18

 

153.214.0.62

 

 

IP address table

 

 

 

20

 

153.214.0.129

IP address 153.214.0.129

 

 

 

 

 

23

 

153.218.51.8

FINS command sent

 

When FINS Command is Received

 

 

 

FINS node number

 

 

 

 

 

Node number not

 

Internal table

 

 

in IP address table

25

 

153.218.51.10

IP address 153.218.51.10

 

 

 

 

Changed

 

 

 

FINS response returned

Combined Method

The combined method combines the IP address table method and the auto-

 

matic generation method (dynamic).

 

First the IP address table is referenced. Then, if the applicable FINS node address is found, the corresponding IP address is read. If the FINS node address is not found, the IP address is calculated using the automatic generation method (dynamic).

The internal table will be as follows:

FINS Node Address Registered to IP Address Table The following address is registered to the internal table.

• Remote IP address:

IP address registered in IP address table

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

FINS Node Address Not Registered to IP Address Table The following address is registered to the internal table.

• Remote IP address:

Local IP address network number + FINS

 

node address

• Remote UDP port number: UDP port number set for local Unit

• Connection method:

FINS/UDP

With the combined method, records of FINS nodes registered to the IP address table are not dynamically changed. When the Unit is turned ON or restarted and the IP address of a remote FINS node is not registered in the IP table, the IP address can be changed dynamically according to FINS messages received from the remote node. This can be used effectively when the remote node is a device such as a personal computer and IP addresses are dynamically changed by a method such as DHCP.

98

IP Addresses in FINS Communications

 

 

 

Section 5-2

Example

 

 

 

 

When FINS Command is Sent

 

 

 

FINS node number

 

 

 

 

 

IP address table

 

 

FINS node

IP address

 

 

Node number in number

 

 

153.214.0.62

 

 

IP address table

18

 

IP address

20

153.214.0.129

IP address

 

method

 

23

153.218.51.8

FINS command

 

 

sent

 

 

 

 

 

Node number not

Network number: xx.xx.00.00

 

 

in IP address table

 

 

 

 

+

IP address

 

Automatic

FINS node number: xx

 

(See note.)

 

generation

 

 

FINS command

 

method

 

 

sent

Automatic

 

 

 

 

When FINS Command is Received

 

generation

FINS node number

 

 

 

method

 

 

 

(dynamic)

Node number

 

 

 

Internal table

 

 

not in IP

 

 

 

 

 

 

address table

25

153.218.51.10

IP address

 

Changed

153.218.51.10

 

 

FINS response

 

returned

Prohibiting Dynamically

Changing Remote IP

Addresses

Using the ETN11compatible Mode

Note When an internal table IP address has been changed with the reception of a FINS command, this is sent to the IP address in the internal table.

With EtherNet/IP Units and built-inEtherNet/IP ports, it is possible to prohibit (protect against) dynamic changes to remote IP addresses by each method (automatic generation, IP address table, or combined method). Use the CXProgrammer to make this setting.

When dynamically changing remote (destination) IP addresses is prohibited, the internal table for each method is maintained in the same state it had when the power was turned ON or restarted. Therefore, protection can be provided against access using FINS/UDP from personal computers or other devices that have dynamically changing IP addresses. To prohibit dynamic changes, clear the selection of the Dynamic change the target IP addresses Option on the FINS/UDP Tab Page in the Edit Parameters Dialog Box of theCX-Pro-grammer.

With EtherNet/IP Units and built-inEtherNet/IP ports, operating specifications can be made compatible with theCS1W-ETN11/CJ1W-ETN11for all methods (automatic generation (dynamic), I/O address table, or combined). (Dynamic changes, however, are prohibited for the destination IP address in ETN11compatible mode.) While inETN11-compatiblemode, the following operations will be performed the same as they are for theCS1W-ETN11/CJ1W-ETN11for FINS/UDP command data sent from a UDP port number other than the local FINS/UDP port number (default: 9600) set ion the FINS/UDP Tab Page.

If the command data is addressed to an Ethernet Unit, a FINS response will be sent to the source UDP port number.

If the command data is for any other Unit, such as the CPU Unit, a FINS response will be sent to the UDP port number set as the FINS/UDP port number.

99

IP Addresses in FINS Communications

Section 5-2

Note If theETN11-compatiblemode is used, the internal table will retain the same content from when it was created after the EtherNet/IP Unit was turned ON or restarted. This feature provides protection from access via FINS/UDP from computers that dynamically change their IP address.

FINS/TCP Communications Method

Pairing in the FINS/TCP

With the FINS/TCP method, communications are first established for each

Method

connection, and then remote FINS node addresses are mutually converted.

 

(See note.) After the FINS node address is converted, FINS message com-

 

munications are executed.

 

In this way, remote FINS node addresses and remote IP addresses are paired

 

for each connection. Therefore, with the FINS/TCP method, there is no need

 

to set IP address conversions (i.e., pairing FINS node addresses with IP

 

addresses) as with FINS/UDP. On the other hand, it is necessary to set the

 

remote IP address for each connection in the FINS/TCP Tab Page of the Net-

 

work Configurator’s Edit Parameters Dialog Box.

Note

The internal table is changed after connections are established.

Internal Processing

The EtherNet/IP Unit or built-inEtherNet/IP port executes the following pro-

 

cessing when the FINS/TCP method is used.

 

Local Device: FINS/TCP Client

1,2,3... 1. Connections are established in TCP/IP protocol with the remote IP addresses set for FINS/TCP connections in the FINS/TCP Tab Page of theCX-Programmer’sEdit Parameters Dialog Box.

2.The remote node (i.e., the server) is notified of the FINS node address for the local device.

3.Notification is received from the remote node (i.e., the server) of the remote node's FINS node address.

4.The EtherNet/IP Unit or built-inEtherNet/IP port changes the internal table (FINS node address, IP address, and TCP port number).

5.FINS messages can then be sent and received.

100

IP Addresses in FINS Communications

Section 5-2

Local Device: FINS/TCP Server

1,2,3... 1. A request to open a connection is received in TCP/IP protocol from the remote device (i.e., the client, either a personal computer, an EtherNet/IP Unit orbuilt-inEtherNet/IP port), and the connection is established.

2.Notification is received from the remote node (i.e., the client) of the remote node's FINS node address.

3.The local device provides notification of the local FINS node address.

4.The EtherNet/IP Unit or built-inEtherNet/IP port changes the internal node correspondence table (FINS node address, IP address, and TCP port number).

5.FINS messages can then be sent and received.

Personal computer or

 

EtherNet/IP Unit (server) CPU Unit

EtherNet/IP Unit (client)

 

 

 

 

(1) The connection is established.

Local FINS node number B

Local FINS node number A

 

 

 

 

(2) The local device (such as a personal

Local IP address S

Local IP address T

computer) sends notification that its

 

 

FINS node number is A.

 

 

IP address FINS node number transmission

Ethernet (EtherNet/IP)

 

 

 

IP address FINS node number transmission

 

The FINS node number is converted for each connection number.

(3)The EtherNet/IP Unit sends notification that its FINS node number is B.

(4)The internal node correspondence table is changed.

(5)It then becomes possible to send and receive FINS messages.

Setting FINS/TCP

Connections

The procedure for setting FINS/TCP connections involves the items described below. The settings are made individually for each connection (numbers 1 to 16) on the FINS/TCP Tab Page of the Edit Parameters Dialog Box of the CXProgrammer.

Local Device: Server

1,2,3... 1. Set the server.

2.Set IP addresses for the devices to be connected.

If the option for protection of IP addresses is selected, set the IP addresses for clients where connections are permitted. (This step can be omitted.)

3.Automatic FINS node address allocation:

If the client (generally a personal computer) supports FINS/TCP, and if it is to be used without setting a FINS node address, the value set here (from 239 to 254) can be allocated to the client. The default settings should normally be used.

Local Device: Client

1,2,3... 1. Set the client.

101

IP Addresses in FINS Communications

Section 5-2

2.Set IP addresses for the devices to be connected.

Set the IP address for the remote EtherNet/IP Unit or built-inEtherNet/IP port (i.e., the server) connected by FINS/TCP.

This setting must be made if this EtherNet/IP Unit will be used as a FINS/ TCP client.

5-2-3Application Examples

Responding to Computers with Changed IP Addresses

FINS/UDP

Communications Method

With FINS/UDP, whether using the automatic conversion method (dynamic), the IP address table method, or the combined method, remote FINS node addresses and remote IP addresses in the internal table are changed after FINS messages are received. Therefore, even when a FINS command has been received from a personal computer (a DHCP client computer) for which the IP address is dynamically changed, a response can still be sent back to the computer (the DHCP client computer) from which the command originated.

Personal computer (client)

IP address changed

(acquired from DHCP server when connected)

 

 

 

 

 

 

 

 

 

 

FINS command sent

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

IP address

FINS command

 

 

 

Ethernet (EtherNet/IP)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

EtherNet/IP Unit

 

 

 

 

 

 

 

 

IP address

FINS response

 

 

 

 

 

 

Response sent back to

 

 

 

 

 

(with fixed IP address)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

changed IP address

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS/TCP

Communications Method

With FINS/TCP, FINS node addresses and IP addresses in the internal table are changed with each connection that is established. Therefore, even when a FINS command has been received from a personal computer (a DHCP client computer) for which the IP address is dynamically changed, a response can still be sent back to the computer (the DHCP client computer) from which the command originated.

Personal computer (client)

IP address changed

(acquired from DHCP server when connected)

 

 

 

 

 

 

 

 

 

 

FINS command sent

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

IP address

FINS command

 

 

 

 

Ethernet (EtherNet/IP)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

EtherNet/IP Unit

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

IP address

FINS response

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(FINS/TCP server; with

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

fixed IP address)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Response sent back to changed IP address

Note Automatic IP Address Setting by DHCP Service

DHCP service is a method whereby a DHCP server collectively manages all of the IP address in a network.

Nodes that are functioning as clients acquire IP addresses from the DHCP

102

IP Addresses in FINS Communications

Section 5-2

server whenever the system is started. Therefore, at a personal computer using the DHCP service, IP addresses may be different with each system startup.

DHCP service is mainly used for automatic settings in devices such as personal computers that are used for client applications. Nodes used for server applications, such as mail servers, are normally allocated fixed IP addresses. EtherNet/IP Units and built-inEtherNet/IP ports in PLC systems are also allocated fixed IP addresses.

Simultaneously Running Multiple Applications on a Personal Computer

FINS/UDP

Communications Method

In communications involving previous models, multiple communications applications were configured on personal computers according to data accessing uses, and the fact that no more than one UDP port number for FINS communications could be used on any given computer created a problem. This EtherNet/IP Unit provides a practical solution with an internal table that pairs remote nodes (applications) with FINS node addresses, enabling dynamic changes.

FINS nodes are allocated individually for each application on the computer, and the respective FINS/UDP port numbers that are used are also allocated individually. When FINS/UDP FINS commands are sent from individual applications to the EtherNet/IP Unit or built-inEtherNet/IP port, the respective remote IP addresses and remote port numbers in the internal table are dynamically changed.

FINS/TCP

Communications Method

With this method as well, FINS nodes are allocated individually for each application on the computer, and the respective FINS/TCP port numbers that are used are also allocated individually. Each application is positioned with a FINS/TCP client, and requests the opening of a connection with the FINS/ TCP server of the EtherNet/IP Unit or built-inEtherNet/IP port. When the connection is established, the respective remote IP address and remote port number in the internal table are dynamically changed.

5-2-4Related Products and Communications/Setting Methods

Models Supporting

Automatic Generation

Method (Dynamic)

Product

Model/Series/

Supports automatic

 

 

Version

generation method

 

 

 

(dynamic)?

CS-seriesEthernet

100BASE-TX

CS1W-ETN21

Yes

Unit

 

 

 

10BASE-5

CS1W-ETN01

No: Set by automatic

 

 

 

 

generation method or

 

10BASE-T

CS1W-ETN11

 

combined method. Com-

 

 

 

 

 

 

munications are not pos-

 

 

 

sible with personal

 

 

 

computers with variable

 

 

 

IP addresses.

 

 

 

 

CJ-seriesEthernet

100BASE-TX

CJ1W-ETN21

Yes

Unit

 

 

 

10BASE-T

CJ1W-ETN11

No: Set by automatic

 

 

 

 

generation method or

CV/CVM1-series

10BASE-5

CV500-ETN01

combined method. Com-

Ethernet Unit

 

 

 

 

munications are not pos-

 

 

 

FinsGateway

 

Version 4.xx or

sible with personal

 

 

lower

 

 

computers with variable

 

 

 

 

 

 

IP addresses.

 

 

 

 

 

 

Version 2003 or

Yes

 

 

higher

 

 

 

 

 

103

IP Addresses in FINS Communications

 

 

Section 5-2

 

 

 

 

 

 

Product

Model/Series/

Supports automatic

 

 

 

Version

generation method

 

 

 

 

(dynamic)?

 

 

 

 

 

 

Programmable Terminal

NS Series

No: Set manually so that

 

 

 

 

automatic settings can be

 

Open Network Controller (ONC)

---

 

used with the automatic

 

 

 

 

 

 

 

 

generation method.

 

 

 

 

 

Models Supporting

 

 

 

Automatic Generation

 

 

 

Method (Static)

 

 

 

 

 

 

 

 

 

Product

Model/Series/

Supports automatic

 

 

 

Version

generation method

 

 

 

 

(static)?

 

CS-seriesEthernet

100BASE-TX

CS1W-ETN21

Yes

 

Unit

 

 

 

 

10BASE-5

CS1W-ETN01

Yes: Simply called “auto-

 

 

 

 

 

 

matic generation

 

 

10BASE-T

CS1W-ETN11

 

 

method.”

 

 

 

 

 

 

 

 

 

 

CJ-seriesEthernet

100BASE-TX

CJ1W-ETN21

Yes

 

Unit

 

 

 

 

10BASE-T

CJ1W-ETN11

Yes: Simply called “auto-

 

 

 

 

 

 

matic generation

 

CV/CVM1-series

10BASE-5

CV500-ETN01

 

method.”

 

Ethernet Unit

 

 

 

 

 

 

 

 

 

 

 

 

FinsGateway

 

Version 4.xx or

 

 

 

 

lower

 

 

 

 

 

 

 

 

 

Version 2003 or

Yes

 

 

 

higher

 

 

 

 

 

 

Programmable Terminal

NS Series

No: Set manually so that

 

 

 

 

automatic settings can be

 

Open Network Controller (ONC)

---

 

used with the automatic

 

 

 

 

 

 

 

 

generation method.

 

 

 

 

 

Models Supporting IP

 

 

 

Address Table Method

 

 

 

 

 

 

 

 

Product

Model/Series/

Supports IP address

 

 

 

Version

table method?

 

 

 

 

 

 

CS-seriesEthernet

100BASE-TX

CS1W-ETN21

Yes

 

Unit

 

 

 

 

10BASE-5

CS1W-ETN01

 

 

 

 

 

 

 

 

 

 

 

10BASE-T

CS1W-ETN11

 

 

 

 

 

 

 

CJ-seriesEthernet

100BASE-TX

CJ1W-ETN21

 

 

Unit

 

 

 

 

10BASE-T

CJ1W-ETN11

 

 

 

 

 

 

 

 

 

 

CV/CVM1-series

10BASE-5

CV500-ETN01

 

 

Ethernet Unit

 

 

 

 

 

 

 

 

 

FinsGateway

 

Version 4.xx or

 

 

 

 

lower

 

 

 

 

 

 

 

 

 

Version 2003 or

 

 

 

 

higher

 

 

 

 

 

 

Programmable Terminal

NS Series

No: Set manually. FINS

 

 

 

 

communications are not

 

Open Network Controller (ONC)

---

 

possible with personal

 

 

 

 

 

 

 

 

computers set automati-

 

 

 

 

cally by DHCP.

104

IP Addresses in FINS Communications

 

 

 

 

 

 

Section 5-2

Models that Can Use the

 

 

 

 

 

 

 

 

 

 

Combined Method

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Product

 

 

Model/Series/

Supports combined

 

 

 

 

 

 

 

 

 

 

Version

method?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CS-seriesEthernet

100BASE-TX

 

CS1W-ETN21

Yes

 

 

 

 

Unit

 

 

 

 

 

 

 

 

 

 

 

 

10BASE-5

 

CS1W-ETN01

No

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

10BASE-T

 

CS1W-ETN11

No

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CJ-seriesEthernet

100BASE-TX

 

CJ1W-ETN21

Yes

 

 

 

 

Unit

 

 

 

 

 

 

 

 

 

 

 

 

10BASE-T

 

CJ1W-ETN11

No

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CV/CVM1-series

10BASE-5

 

CV500-ETN01

No

 

 

 

 

Ethernet Unit

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FinsGateway

 

 

 

 

Version 4.xx or

No

 

 

 

 

 

 

 

 

 

 

lower

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Version 2003 or

Yes

 

 

 

 

 

 

 

 

 

 

higher

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Programmable Terminal

 

 

NS Series

No: Set manually. FINS

 

 

 

 

 

 

 

 

 

 

 

communications are not

 

 

 

Open Network Controller (ONC)

 

---

 

 

 

 

 

 

possible with personal

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

computers set automati-

 

 

 

 

 

 

 

 

 

 

 

cally by DHCP.

 

 

 

 

 

 

 

 

 

 

 

5-2-5

Pairing IP Addresses and FINS Node Addresses

 

 

 

 

 

The following table shows the methods for pairing IP address and FINS node

 

 

 

addresses, and the relation between fixed and variable address, for both

 

 

 

FINS/UDP and FINS/TCP.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Communi-

 

Method of pairing

IP address determination

Client (personal

Server (PLC)

cations

 

of IP addresses

 

 

 

 

computer of PLC)

 

 

method

 

and FINS node

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS node

IP address

FINS node

IP address

 

 

addresses

 

 

 

 

 

 

 

 

 

 

address

 

address

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS/UDP

 

By pairing FINS

IP address

 

Automatic gen-

Fixed

 

Fixed

Fixed

Fixed

 

 

node addresses with

conversion

 

eration method

 

 

 

 

 

 

 

 

IP addresses in

 

 

(static)

 

 

 

 

 

 

 

 

 

Ethernet

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Automatic gen-

Fixed

 

Fixed or

Fixed

Fixed

 

 

 

 

 

 

 

 

 

 

 

eration method

 

 

 

variable

 

 

 

 

 

 

 

(dynamic)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

IP address table

Fixed

 

Fixed or

Fixed

Fixed

 

 

 

 

 

method

 

 

 

 

variable

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Combined

Fixed

 

Fixed or

Fixed

Fixed

 

 

 

 

 

method

 

 

 

 

variable

 

 

 

 

 

 

 

 

 

 

 

 

 

FINS/TCP

 

By automatic conver-

Automatic

 

Connection

Fixed or

 

Fixed or

Fixed

Fixed

 

 

sion of FINS node

 

 

method (auto-

can be allo-

variable

 

 

 

 

addresses at Ether-

 

 

matic FINS

cated auto-

 

 

 

 

 

Net/IP Unit and

 

 

node address

matically

 

 

 

 

 

 

remote node (and

 

 

conversion)

when not

 

 

 

 

 

then sending and

 

 

 

 

determined.

 

 

 

 

 

receiving data)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

105

Private and Global Addresses

Section 5-3

5-3Private and Global Addresses

5-3-1Private and Global Addresses

There are two kinds of IP addresses, private and global.

• Global addresses: These are IP addresses that connect directly to the Internet. Allocated by application to NIC, each address is unique in the world, and as many as 4.3 million can be allocated worldwide.

• Private addresses: These are IP addresses for Intranet (LAN) use, and cannot connect directly to the Internet. Frames that include private IP addresses are restricted by the router from being sent outside the LAN.

Generally, as shown below, global addresses in the intranet are allocated only to IP routers (such as broadband routers) interfacing with the Internet. All other nodes in the intranet, including the EtherNet/IP Unit or built-inEtherNet/ IP port, are allocated private addresses.

Intranet

 

 

Personal computer,

 

CX-Programmer,etc.

 

Ethernet (EtherNet/IP)

Firewall

PLC

IP router

Private address

 

 

Private address

Internet

Not output to Internet

Global address

 

(required)

Intranet

Not output to Internet

Global address

IP router

Private address

Private address Personal computer,

CX-Programmer,etc.

Firewall

Ethernet (EtherNet/IP)

 

 

 

 

 

 

PLC

 

 

 

 

PLC

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Communications Services That Require Global Addresses for EtherNet/IP Units and built-inEtherNet/IP ports

Private address

Private address

A global address is required for the IP addresses of the EtherNet/IP Units and built-inEtherNet/IP port when the following communications services are used over the Internet.

FINS communications services

Explicit message communications services

106

Private and Global Addresses

Section 5-3

5-3-2Using a Private Address for the EtherNet/IP Unit

Intranet

IP router

Firewall

Intranet

Firewall

IP router

FINS/TCP client computer with CX-Programmer,etc.

or

CIP client computer with Network Configurator, etc.

Ethernet (EtherNet/IP)

Communications in intranet

PLC

EtherNet/IP Unit: Private address

Internet

FINS/TCP client computer with CX-Programmer,etc. or

CIP client computer with Network Configurator, etc.

FINS communications, Explicit messages

FINS communications, Explicit messages

Communications in Intranet

Ethernet (EtherNet/IP)

PLC

PLC

Communications

 

in Intranet

 

EtherNet/IP Unit: Private address

EtherNet/IP Unit: Private address

Conditions for Using Communications Applications

When the EtherNet/IP Unit or built-inEtherNet/IP port has a private address, communications applications can be used under the following conditions:

FINS Communications Service

The FINS communications service can be executed on the intranet between EtherNet/IP Units and built-inEtherNet/IP ports with private addresses only.

A device such as a personal computer (with a FINS application, including the CX-Programmer)cannot connect online and communicate over the Internet with an EtherNet/IP Unit orbuilt-inEtherNet/IP port that has a private address. FINS communications are also not possible over the Internet between EtherNet/IP Units and orbuilt-inEtherNet/IP ports with private addresses.

Either FINS/TCP or FINS/UDP can be used for the FINS communications service.

With FINS/UDP, all of the EtherNet/IP Unit or built-inEtherNet/IP port IP address conversion methods can be used.

107

Private and Global Addresses

Section 5-3

With FINS/UDP, when the IP address (private address) of a computer serving as a DHCP client is changed, the IP address conversion method of the EtherNet/IP Unit or built-inEtherNet/IP port will be the automatic generation method (dynamic), the combined method, or the IP address table method. When FINS/TCP is used, IP addresses can be changed automatically.

Explicit Message Communications Service

The explicit message communications service can be executed on the intranet between EtherNet/IP Units and built-inEtherNet/IP ports with private addresses only.

A device such as a personal computer (CIP applications including the Network Configurator) cannot connect online and communicate over the Internet with an EtherNet/IP Unit or built-inEtherNet/IP port that has a private address. Explicit message communications are also not possible over the Internet between EtherNet/IP Units andbuilt-inEtherNet/IP ports with private addresses.

Note Network Security and Firewalls

Setting up an intranet through a global address involves network security considerations. Before doing so, be sure to consult with a network specialist and consider installing a firewall.

Once a firewall has been set up by a communications technician, on the other hand, there may be some applications that cannot be used. Be sure to check first with the communications technician.

108

Private and Global Addresses

Section 5-3

5-3-3EtherNet/IP Unit with a Global Address

Communications over Internet

Intranet

FINS/TCP client computer with CX-Programmer,etc. or

CIP client computer with

Network Configurator, etc. Ethernet (EtherNet/IP)

Firewall

IP router

Private address

 

Internet

Not output to Internet

Global address

 

(required)

Not output to Internet

Intranet

Global address

IP router

Private address

Private address

Firewall

Ethernet (EtherNet/IP)

 

 

 

 

 

 

 

PLC

Communications

 

 

 

 

 

 

 

 

 

 

 

 

in intranet

 

 

 

 

 

 

 

 

 

 

 

 

 

EtherNet/IP Unit: Global address

Conditions for Using Communications Applications

Communications applications can be used over the Internet under the following conditions:

FINS Communications Service

A device such as a personal computer (a FINS application, including the CX-Programmer)can connect online and communicate over the Internet with an EtherNet/IP Unit orbuilt-inEtherNet/IP port that has a global address.

FINS/TCP is recommended as the FINS communications service method.

FINS/TCP is more reliable than FINS/UDP in terms of communications errors involving IP routers.

The IP address table method is used as the IP address conversion method of the EtherNet/IP Unit or built-inEtherNet/IP port.

The TCP port number to be used for FINS/TCP cannot be used if prohibited by a firewall in the communications path.

Explicit Message Communications Service

A device such as a personal computer (a CIP application including the Network Configurator) can connect online and communicate over the Internet with an EtherNet/IP Unit or built-inEtherNet/IP port that has a global address.

109

Private and Global Addresses

Section 5-3

If the TCP port number (44818) or UDP port number (44818) that is used for EtherNet/IP cannot be used if prohibited by a firewall in the communications path.

Note Network Security and Firewalls

Setting a global IP address for an EtherNet/IP Unit or built-inEtherNet/IP port involves network security considerations. It is recommended that the user contract with a communications company for a dedicated line, rather than using a general line such as a broadband line. Also, be sure to consult with a network specialist and consider security measures such as a firewall.

Once a firewall has been set up by a communications technician, on the other hand, there may be some applications that cannot be used. Be sure to check first with the communications technician.

110

SECTION 6

Tag Data Link Functions

This section describes tag data link functions and related Network Configurator operations.

 

6-1 Overview of Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112

6-1-1

Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112

6-1-2

Overview of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113

6-1-3

Tag Data Link Functions and Specifications . . . . . . . . . . . . . . . . . .

115

6-1-4

Data Link Data Areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

116

6-2 Setting Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

121

6-2-1

Starting the Network Configurator . . . . . . . . . . . . . . . . . . . . . . . . . .

121

6-2-2

Tag Data Link Setting Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

6-2-3

Registering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

125

6-2-4

Creating Tags and Tag Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

126

6-2-5

Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

141

6-2-6

Setting Tags Using Data Link Tool. . . . . . . . . . . . . . . . . . . . . . . . . .

150

6-2-7

Creating Connections Using the Wizard . . . . . . . . . . . . . . . . . . . . .

156

6-2-8

Creating Connections by Device Dragging and Dropping . . . . . . . .

159

6-2-9

Connecting the Network Configurator to the Network . . . . . . . . . .

161

6-2-10

Downloading Tag Data Link Parameters . . . . . . . . . . . . . . . . . . . . .

168

6-2-11

Uploading Tag Data Link Parameters. . . . . . . . . . . . . . . . . . . . . . . .

171

6-2-12

Verifying the Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

172

6-2-13

Starting and Stopping Tag Data Links . . . . . . . . . . . . . . . . . . . . . . .

175

6-2-14

Clearing the Device Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .

176

6-2-15

Saving the Network Configuration File . . . . . . . . . . . . . . . . . . . . . .

177

6-2-16

Reading a Network Configuration File. . . . . . . . . . . . . . . . . . . . . . .

178

6-2-17

Checking Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

180

6-2-18

Changing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

181

6-2-19

Displaying Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

181

6-3 Ladder Programming with Tag Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . .

183

6-3-1

Ladder Programming Related to Tag Data Links . . . . . . . . . . . . . . .

183

6-3-2

Status Flags Related to Tag Data Links . . . . . . . . . . . . . . . . . . . . . .

186

111

Overview of Tag Data Links

Section 6-1

6-1Overview of Tag Data Links

6-1-1Tag Data Links

Tag data links enable cyclic data exchanges on an EtherNet/IP network between PLCs or between PLCs and another device. I/O memory addresses (e.g., in the CIO or DM Area) and symbols can be assigned to tags. The settings for tag data links are made using the Network Configurator. Refer to 6-2 Setting Tag Data Links for information on how to make the settings.

Note Symbols can be used in tags only for theCJ2H-CPU6@-EIPand CJ2MCPU3@. If you are using aCJ1W-EIP21orCS1W-EIP21EtherNet/IP Unit that is mounted to aCJ2H-CPU6@or any CPU Unit other than theCJ2H-CPU6@-EIP, use I/O memory addresses to set the tag data links.

With tag data links, one node requests the opening of a communications line called a connection to exchange data with another node. The node that requests opening the connection is called the originator, and the node that receives the request is called the target.

CPU Unit

 

EtherNet/IP Unit

 

 

EtherNet/IP Unit

 

CPU Unit

 

 

Inputs

 

 

Outputs

 

 

 

 

Tag set name: ABC

 

Connection

 

 

 

 

 

 

 

Tag set name: OUT1

 

 

DM00100

 

 

 

 

 

Var-Out1(DM0)

I/O refreshed.

DM00100

 

 

Var-Out1

 

 

 

 

 

 

 

Input tags

 

 

 

Var-In(WR200)

 

Var-In

Output tags

Var-Out2

I/O refreshed.

Var-Out2(DM100)

 

DM20000

 

 

Var-Out3

 

 

 

 

 

 

DM20000

Originator

 

Var-Out3(DM200)

 

Target

 

 

 

 

 

Outputs

Inputs

DM00200

DM00200

 

Connection

Var-Out(WR300)

Tag set name: XYZ

Tag set name: IN1

WR300

DM20100

I/O refreshed.

 

 

DM00200

 

DM20100

DM00200

Output tags

Input tags

I/O refreshed.

 

Var-Out

WR300

 

 

 

 

 

 

 

 

DM20100

 

 

DM20100

 

 

PLC status

PLC status

 

Target

Originator

Ethernet (EtherNet/IP)

For communications between PLCs, the connection information is set in the EtherNet/IP Unit or built-inEtherNet/IP port of the PLC that receives data (i.e., the originator).

Note For communications between a PLC and an I/O device, the connection information is set in the EtherNet/IP Unit orbuilt-inEtherNet/IP port that is the originator. If an I/O device is used, the Network Configurator must have an EDS file installed that includes connection information for the I/O device. Refer toAppendix F EDS File Management for the installation procedure.

The output words and input words for each node for which data is exchanged must be set in the connection information. These words are called the output tag set and input tag set. A tag set must specify at least one tag. The size of the data for data exchange is the total size of the tags included in the tag set. The size of the output tag set and the size of the input tag set must match.

In this manual, set connection information is called tag data link parameters.

The following section describes how to set tag data links using the Network

Configurator.

112

Overview of Tag Data Links

Section 6-1

6-1-2Overview of Operation

Setting and Downloading Tag Data Link Parameters

 

The tag data link parameters (e.g., connection information) that are described

 

below are created using the Network Configurator, and then the parameters

 

are downloaded to all originator devices on the EtherNet/IP network.

 

Make the following settings using the Network Configurator if tag data link

 

functionality is used with the CJ2B-EIP21built-inEtherNet/IP port on the

 

CJ2H, CJ2M-EIP21built-inEtherNet/IP port on the CJ2M,CS1W-EIP21,or

 

CJ1W-EIP21.

Tag Settings

Create input (reception) tags and output (send) tags for addresses in the CPU

 

Unit's I/O memory areas or for symbols.

 

The following are the limits for tags that can be created with the CJ2B-EIP21

 

built-inEtherNet/IP port on the CJ2H,CJ2M-EIP21built-inEtherNet/IP port

 

on the CJ2M, CS1W-EIP21,orCJ1W-EIP21.

 

• A maximum of 32 tags can be created per Unit for the CJ2M-EIP21.A

 

maximum of 256 tags can be created per Unit for other CPU Units.

 

• A maximum data size of 40 bytes (20 words) can be used per tag for the

 

CJ2M-EIP21.A maximum data size of 1,444 bytes (722 words) can be

 

used per tag for other CPU Units.

 

With the CJ2H-CPU6@-EIPorCJ2M-CPU3@,you can create tags by import-

 

ing network symbols (i.e., I/O allocation settings) that were created using the

 

CX-Programmerinto the Network Configurator. Output tags can be defined to

 

clear output data to 0 or to hold the output data when PLC outputs are turned

 

OFF.

Setting Tag Sets

Create output tag sets and input tag sets and position them. (Up to eight tag

 

sets can be created). The following are the limits on tag sets that can be cre-

 

ated with the CJ2B-EIP21built-inEtherNet/IP port on the CJ2H,CJ2M-EIP21

 

built-inEtherNet/IP port on the CJ2M,CS1W-EIP21,orCJ1W-EIP21.

 

• A maximum of 32 tag sets can be created per Unit for the CJ2M-EIP21.A

 

maximum of 256 tag sets can be created per Unit for other CPU Units.

 

• A maximum data size of 40 bytes (20 words) can be used per tag set for

 

the CJ2M-EIP21.A maximum data size of 1,444 bytes (722 words) can

 

be used per tag set for other CPU Units.

 

The PLC status can be specified in a tag set to indicate the CPU Unit’s operat-

 

ing status (operating information and error information).

Setting Connections

The target device output tag set and the originator device input tag set are

 

associated as connections. A maximum of 256 connections can be opened

 

per Unit for the CJ2B-EIP21built-inEtherNet/IP port on the CJ2H, CS1W-

 

EIP21, or CJ1W-EIP21.A maximum of 32 connections can be opened per

 

Unit for the CJ2M-EIP21built-inEtherNet/IP port on the CJ2M.

Counting Connections

The number of connections is the total of the number of input tag sets that

 

receive data and the number of nodes that send data for output tag sets.

 

(Refer to the following figure.) One connection is consumed for each connec-

 

tion setting whether the connection is a multicast connection or a unicast

 

(point-to-point)connection.

113

Overview of Tag Data Links

Section 6-1

Setting the Packet Interval (RPI)

Using Multicast and

Unicast Communications

Example of Calculating the Number of Connections

EtherNet/IP Unit or built-inEtherNet/IP port with IP address of 192.168.250.254 in bidirectional connection with 128 nodes

192.168.250.254

Tagset _in1

Tagset _in2

Tagset_in128

Tagset_out25 4

The maximum number of connections for node 192.168.250.254 is 32 for the CJ2M and 256 for other CPU Units.

CN.1

CN.2

CN.129

:

CN.128

CN.130

:

:

CN.256

192.168.250.1

Tagset_out

Tagset_in

192.168.250.2

Tagset_out

Tagset_in

:

:

192.168.250.128

Tagset_out

Tagset_in

Another EtherNet/IP Unit must be mounted to the PLC to increase the maximum number of connections. (Refer to the following figure.)

Example of Calculating the Number of Connections

The maximum number of connections (32 for the CJ2M and 256 for other CPU Units) per Unit would be exceeded if an EtherNet/IP Unit or built-inEtherNet/IP port with an IP address of 192.168.250.254 is used in a bidirectional connection with 129 nodes. In this case, bidirectional communications can be performed with 129 nodes or more by adding an EtherNet/IP Unit with the IP address of, for example, 192.168.250.253 to the same PLC, creating an output tag set in the new EtherNet/IP Unit, and creating connections.

192.168.250.254

 

 

192.168.250.1

Tagset_in1

CN.1

 

Tagset _out

 

 

Tagset_in2

CN.2

CN.1

Tagset_in

 

 

Tagset _in129

:

 

192.168.250.2

 

 

 

CN.129

 

Tagset _out

 

 

CN.2

Tagset _in

192.168.250.253

 

 

 

Tagset _out 253

 

:

:

 

 

 

 

:

:

192.168.250.129

Tagset _out

CN.129

Tagset _in

The packet interval is the data I/O refresh cycle in the Ethernet circuit when performing tag data links, and can be set separately for each connection. The packet interval can be set to between 0.5 and 10,000 ms in units of 0.5 ms for the CJ2B-EIP21(built-inEtherNet/IP port on the CJ2H),CS1W-EIP21,orCJ1W-EIP21.It can be set to between 1 and 10,000 ms in units of 0.5 ms for theCJ2M-EIP21(built-inEtherNet/IP port on the CJ2M). The default setting is 50 ms.

With EtherNet/IP, data is exchanged on the communications line at the packet interval that is set for each connection, regardless of the number of nodes.

A multicast connection or unicast (point-to-point)connection can be selected as the connection type in the tag data link connection settings.

With a multicast connection, you can send an output tag set in one package to multiple nodes and make allocations to the input tag sets.

A unicast connection separately sends one output tag set to each node, and so it sends the same number of packets as the number of input tag sets.

Therefore, using multicast connections can decrease the communications load if one output tag set is sent to multiple nodes.

114