Size:
19.68 Mb
Download

Setting Tag Data Links

Section 6-2

• Differences Found in the Device Type

Click the OK Button or the Close Button.

5.If multiple nodes have been selected, the following message will be displayed. Click the Yes Button.

The comparison results will be displayed in order of the selected nodes.

6-2-13Starting and Stopping Tag Data Links

Automatically Starting Tag Data Links

Tag data links will start operating automatically immediately after the tag data link parameters are downloaded from the Network Configurator. (They will also start automatically when the power to the PLC is turned ON or the CPU Unit is restarted.)

Starting and Stopping All Tag Data Links on the Network

Using the Network

All tag data links on the network can be started and stopped by selecting I/O

Configurator

Connection - Start/Stop from the Network Menu.

Starting and Stopping Tag Data Links for Individual Devices

Using the Network

Configurator

You can start and stop tag data links for individual devices using the following buttons in the Monitor Device Dialog Box. This applies only to tag data links for which the device is the originator. Access the Monitor Device Dialog Box by selecting Monitor from the Device Menu.

175

Setting Tag Data Links

Section 6-2

Start Connection Button:

Starts all connections for which the device is the originator.

Stop Connection Button:

Stops all connections for which the device is the originator.

Note Connections will be cut off if any of the following errors occurs in the CPU Unit that is the originator while tag data links are active.

Fatal CPU Unit error

I/O refresh error

CPU Unit WDT error

I/O bus error

6-2-14Clearing the Device Parameters

The device parameters saved in the EtherNet/IP Units in the EtherNet/IP network can be cleared (returned to their default settings). The following procedure shows how to clear the device parameters. For details on connecting to the network from the Network Configurator, refer to 6-2-9 Connecting the Network Configurator to the Network.

1,2,3... 1. Connect the Network Configurator to the network.

2.Select the icon of the EtherNet/IP Unit in which you want to clear the device parameters. In the following example, 2 nodes are selected: 192.168.250.1 and 192.168.250.2. To select multiple nodes, press and hold the Shift Key while selecting additional icons.

176

Setting Tag Data Links

Section 6-2

3. Select Device - Reset. The following dialog box will be displayed.

Clicking the Yes Button:

The following dialog box will be displayed.

Select one of the following options and click the OK Button.

Emulate cycling power

Restarts the Unit.

Return to the out-of-boxconfiguration, and then emulate cycling power

Returns the Unit to its factory default settings, and restarts the Unit.

Clicking the No Button:

The device parameters are not cleared or reset.

6-2-15Saving the Network Configuration File

Device parameters set in the Network Configurator, or device parameters uploaded from the network can be saved as a network configuration file.

1,2,3... 1. SelectFile - Save As. The following dialog box will be displayed.

The File name Field will containUntitled.nvf as the default file name.

2. Input the file name, and click the Save Button.

177

Setting Tag Data Links

Section 6-2

The network configuration file save operation is complete.

3.When the network configuration is changed later, the existing network con-

figuration file can be overwritten by selecting File - Save or clicking theButton.

4.You can select the Select target network Check Box in theOption Area to save a network configuration file with only the required networks.

Select the check boxes of the networks to save and click the OK Button.

6-2-16Reading a Network Configuration File

A previously saved network configuration file can be read into the Network

Configurator.

178

Setting Tag Data Links

Section 6-2

1,2,3... 1. SelectFile - Open or click theButton. The following dialog box will be displayed.

If the network configuration file that you want to read is not displayed, change to (Look in) another folder.

2.When you click and select the network configuration file that you want to read, that file name will be displayed in the File name Field.

3.Click the Open Button to read the network configuration file.

4.The Network Configurator’s Title Bar will display the name of the file that was read.

179

Setting Tag Data Links

Section 6-2

5. Select any of the options as necessary. The options are listed below.

Option

Function

 

 

Select target network

Allows you to select specific networks from the net-

 

work configuration and open them.

 

 

Add to current document

Allows you to add the networks from the network

 

configuration file being opened to the current config-

 

uration file.

Note The save format will vary depending on the Network Configurator version. Configuration files (*.ncf) created using the Network Configurator for EtherNet/IP (version 2 or higher) can be imported (opened) by selectingExternal Data - Import from the File Menu.

6-2-17Checking Connections

Check the consistency of connection parameters for network configuration files with device parameters set using the Network Configurator and device parameters uploaded from the network.

1.Select Check Connections in the Network Menu. The following dialog box will be displayed if parameters are normal.

The following dialog box will be displayed if there are parameter errors.

Check the displayed details and review the settings.

If an inconsistency occurs, open the originator's Edit Device Parameter Dialog Box and click the Connection Tab. The inconsistent connection will

be displayed with a icon (instead of the normalicon). To change the connection setting and select a different target variable, select the connection as shown below and click theEdit Button.

180

Setting Tag Data Links

Section 6-2

Icon (When normal:

)

6-2-18Changing Devices

Devices that are registered in a network configuration with the Network Configurator can be changed. Select Change Device from the Device Menu to display a list of the devices that can be changed to. Select the desired device.

A device can be changed only when there is complete or upward compatibility with the device being changed to.

Device Changes

Device after change

CJ1W-

CS1W-

CJ1W-

CS1W-

CJ1W-

CJ2B-

CJ2M-EIP21

 

 

EIP21

EIP21

EIP21

EIP21

EIP (CJ2)

EIP21

 

 

 

 

 

 

 

 

 

 

Device before change

Revi-

1.01

1.01

2.01

2.01

2.01

2.01

2.01

 

sion

 

 

 

 

 

 

 

CJ1W-EIP21

1.01

---

OK

OK

OK

OK

OK

OK if there are

 

 

 

 

 

 

 

 

less than 33 tags

CS1W-EIP21

1.01

OK

---

OK

OK

OK

OK

OK if there are

 

 

 

 

 

 

 

 

less than 33 tags

CJ1W-EIP21

2.01

No

No

---

OK

OK

OK

OK if there are

 

 

 

 

 

 

 

 

less than 33 tags

CS1W-EIP21

2.01

No

No

OK

---

OK

OK

OK if there are

 

 

 

 

 

 

 

 

less than 33 tags

CJ1W-EIP(CJ2)

2.01

No

No

OK if no vari-

OK if no vari-

---

OK

OK if there are

 

 

 

 

ables in tags

ables in tags

 

 

less than 33 tags

CJ2B-EIP21

2.01

No

No

OK if no vari-

OK if no vari-

OK

---

OK if there are

 

 

 

 

ables in tags

ables in tags

 

 

less than 33 tags

CJ2M-EIP21

2.01

No

No

OK if no vari-

OK if no vari-

OK

OK

---

 

 

 

 

ables in tags

ables in tags

 

 

 

6-2-19Displaying Device Status

Device status is displayed using the following icons in Maintenance Mode. To enter maintenance mode, select Large Icons - Maintenance Mode from the View Menu.

181

Setting Tag Data Links

Section 6-2

Icon

Status

 

 

(gray)

Offline

 

 

 

 

Default (no configuration)

(turquoise edge)

 

 

 

(green)

Idle (CPU Unit of PLC is in PROGRAM mode.)

 

 

(blue)

Communications normal (CPU Unit of PLC is in RUN or MONI-

TOR mode.)

 

 

 

(yellow)

Warning (A non-fatalerror has occurred in the CPU Unit of the

 

PLC.)

(red)

Alarm (A fatal error has occurred in the CPU Unit of the PLC.)

 

 

 

182

Ladder Programming with Tag Data Links

Section 6-3

6-3Ladder Programming with Tag Data Links

6-3-1Ladder Programming Related to Tag Data Links

If data in the ladder program is linked by tag data links, add conditions 1 to 4 in the ladder program for that data. If you want to use target node PLC flags as input conditions, add conditions 5 and 6.

For details on the various flags, refer to 4-2 CIO Area Allocations.

Conditions showing the EtherNet/IP Unit’s Tag Data Links are enabled:

1.The Unit Error Occurred Flag (n+10, bit 00) is OFF,

2.and the Online Flag (n+11, bit 00) is ON,

3.and the Tag Data Link Operating Flag (n+11, bit 01) is ON.

Conditions showing that connections are established with the target device, and tag data links are operating:

4.The corresponding Normal Target Node Flag (in words n+20 to n+23) is ON.

The location of the Normal Target Node Flags depends on the layout setting. For details on the layout settings, refer to 4-2-2 Details of the Allocated CIO Area Words.

Note With revision 2 or higher, the Normal Target Node Flag will turn ON only after the data for all connections for the target device has been refreshed in the CPU Unit. With revision 1, the Normal Target Node Flag will turn ON after the data for only one connection for the target device has been refreshed in the CPU Unit.

Example of Programming to Detect Normal Status

Condition showing that the Target Node PLC is operating (OMRON PLCs only):

5.The corresponding Target Node PLC Operating Flag (in words n+2 to n+5) is ON.

Condition showing the Target Node PLC’s fatal or non-fatalerror status (OMRON PLCs only):

6.The corresponding Target Node PLC Error Flag (in words n+6 to n+9) is OFF.

When you want to use the Target Node PLC Error Flag, the PLC status must be included in the tag sets for both the originator and target. Include the PLC status by using the Network Configurator to select the Include Options in the Edit Tag Set Dialog Boxes. For details, refer to6-3-2 Status Flags Related to Tag Data Links.

The following programming can be used to confirm that normal communications are being performed for each target node. If the PLC status is included in the tag data, the status of the PLC can also be detected.

183

Ladder Programming with Tag Data Links

Section 6-3

Programming to Detect Errors: Example 1

Programming to Detect Errors: Example 2

Programming for Revision 2 or Higher

Tag Data Link

Normal Target Node

PLC Operating

PLC Error

Operating

Flag 1

Flag 1

Flag 1

 

 

 

 

 

 

 

 

 

 

 

 

Node 1 Data Link

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Normal Operation Flag

 

 

 

 

 

 

 

 

 

 

 

 

n+11 bit 01

n+20 bit 01

n+2 bit 01

n+6 bit 01

 

 

 

Normal Target Node

PLC Operating

PLC Error

 

 

 

Flag 2

Flag 2

Flag 2

 

 

 

 

 

 

 

 

 

 

 

 

Node 2 Data Link

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Normal Operation Flag

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

n+20 bit 02

n+2 bit 02

n+6 bit 02

 

 

 

 

 

 

 

 

 

 

 

 

 

Programming for Revision 1 and Revision 2

Tag Data Link

All Tag Data Links

Operating

Operating

n+11 bit 01

n+12 bit 14

 

 

PLC Operating

PLC Error

 

Flag 1

Flag 1

 

n+2 bit 01

n+6 bit 01

 

PLC Operating

PLC Error

 

Flag 2

Flag 2

 

n+2 bit 02

n+6 bit 02

Normal Operation Flag

Node 1 Data Link

Normal Operation Flag

Node 2 Data Link

Normal Operation Flag

The following programming can be used to check for errors for each target node. This programming is used to detect errors only after the data links for all nodes have started normally.

Programming for Revision 2 or Higher

Tag Data Link

Normal Target Node

 

 

 

 

 

Operating

Flag 1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node 1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Error output

n+11 bit 01

n+20 bit 01

 

 

 

 

 

 

 

 

Normal Target Node

Node 1

 

 

 

 

Flag 1

Error output

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

n+20 bit 01

 

 

 

 

 

 

 

 

Normal Target Node

 

 

 

 

 

 

 

 

Flag 2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Node 2

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Error output

 

 

 

n+20 bit 02

 

 

 

 

 

 

 

 

Normal Target Node

Node 2

 

 

 

 

Flag 2

Error output

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

n+20 bit 02

The following programming can be used to detect tag data link errors at the local node.

184

Ladder Programming with Tag Data Links

 

Section 6-3

Programming for Revision 1 or Higher

 

 

 

 

 

Tag Data Link

Unit Error

 

 

 

 

 

 

 

 

 

 

Operating

Occurred

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DIFD

 

 

 

 

 

 

 

 

 

10000

 

 

 

n+11 bit 01

n+10 bit 00

 

 

 

 

 

 

 

 

 

 

 

 

 

Unit Error

 

 

 

 

 

 

 

 

Occurred

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

DIFU

 

 

 

 

 

 

 

 

 

 

10000

 

 

 

 

 

 

n+10 bit 00

 

 

 

 

 

10000

Release Flag

 

 

 

 

 

 

 

 

 

 

 

 

 

Local node

 

 

 

 

 

 

 

 

 

Error output

 

Local node

 

 

 

 

 

 

 

 

 

Error output

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Example of Programming

The following type of programming can be used to process data only when the

to Process Data

data links are operating normally.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Additional part

Normal Operation

Flag

 

 

Normal Operation

 

Flag

The parts of the ladder program that use the data link area for the relevant node are processed only when the corresponding Normal Operation Flag is ON.

Interlocks (IL and ILC instructions) and jumps (JMP and JME instructions) can also be used to process data only when the data links are operating normally as shown below.

Node A Data Link

Normal Operation Flag

IL

Node A data processing

ILC

Node B Data Link

Normal Operation Flag

IL

Node B data processing

ILC

Node C Data Link

Normal Operation Flag

IL

Node C data processing

ILC

185

Ladder Programming with Tag Data Links

Section 6-3

Note Even if an error occurs in communications with a target device, the input data from the target device will remain stored in words allocated in memory to the local node. To prevent malfunctions, write the ladder program so that input data processing will not be performed when the Unit Error Occurred Flag (word n+10 bit 00) is ON.

6-3-2Status Flags Related to Tag Data Links

The status of the tag data links is reflected in the following words.

Name (allocated area)

Contents

 

 

Target Node PLC Operating Flag

Each flag indicates the operating status of the

Information

corresponding target node PLC of connections

Layout set to default settings:

in which the EtherNet/IP Unit is the originator.

The flag corresponding to the target node’s tar-

Words n+2 to n+5

get ID will be ON when the PLC Operating Flags

Layout set to user settings:

for all connections with that target node indicate

Words n+32 to n+47

that the PLC is operating.

Note Corresponds to the PLC

Each node address’s flag location (i.e., target ID)

status’s PLC Operating

can be changed from the Network Configurator.

Flag.

The PLC status flags are enabled when the PLC

 

 

status is included in the communications data for

 

both the originator and target.

 

The data in this table is refreshed when neces-

 

sary.

 

 

Target Node PLC Error Flag Infor-

Each flag indicates the error status (logical OR

mation

of non-fataland fatal errors) of the corresponding

Layout set to default settings:

target node PLC of connections in which the Eth-

erNet/IP Unit is the originator. The flag corre-

Words n+6 to n+9

sponding to the target node’s target ID will be

Layout set to user settings:

ON if even one error is indicated in any of the

Words n+48 to n+63

connections with that target node.

Note Corresponds to the PLC

Each node address’s flag location (i.e., target ID)

status’s PLC Error Flag.

can be changed from the Network Configurator.

 

 

The PLC status flags are enabled when the PLC

 

status is included in the communications data for

 

both the originator and target.

 

The data in this table is refreshed when neces-

 

sary.

 

 

Normal Target Node Flag Table

Each flag indicates the connection status of the

Layout set to default settings:

corresponding target node PLC of connections

in which the EtherNet/IP Unit is the originator.

Words n+20 to n+23

The flag corresponding to the target node’s tar-

Layout set to user settings:

get ID will be ON when connections are estab-

Words n+16 to n+31

lished for all connections with that target node

Note Does not correspond to the

indicate that the PLC is operating.

PLC status.

Each node address’s flag location (i.e., target ID)

 

 

can be changed from the Network Configurator.

 

The data in this table is refreshed when neces-

 

sary.

186

SECTION 7

Message Communications Functions

This section describes message communications using FINS messages and explicit messages.

7-1

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

188

7-2

FINS Message Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

190

7-3

Explicit Message Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

192

7-4

Message Communications Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . .

193

7-5 Message Communications Error Indications . . . . . . . . . . . . . . . . . . . . . . . . .

194

7-6

Message Communications Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

195

187

Overview

Section 7-1

7-1Overview

The message communications functions send command/response messages between nodes on the Ethernet network. The messages can be sent between a computer and PLC, between two PLCs, between an OMRON PLC and a master made by another company, or between slaves. The messages can be used to send/receive data; read time data, error logs, and other data; or control operation, e.g., by force-setting/resettingbits.

There are two types of messages: FINS messages and explicit messages.

Item

 

 

FINS messages

 

 

Explicit messages

 

 

 

 

 

 

 

 

 

Outline

Message communications for

Standard ODVA message communi-

 

OMRON products that use the

cations using the CIP protocol.

 

FINS protocol.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Remote

• Computer with an Ethernet inter-

• Computer with an Ethernet inter-

device

face

face

 

• OMRON PLCs (with a CS/CJ-

• Another company’s masters or

 

series EtherNet/IP Unit, built-in

slaves.

 

EtherNet/IP port, or Ethernet

• OMRON PLCs (with a CS/CJ-

 

Unit)

series EtherNet/IP Unit or built-in

 

 

 

 

EtherNet/IP port)

 

 

 

 

 

 

 

 

 

Features

• Send and receive the various

• Supports message communica-

 

FINS commands to provide an

tions with other companies’ Ether-

 

even greater range of services

Net/IP devices.

 

than the CIP UCMM messages.

 

 

 

 

 

 

CS/CJ Series

 

• Provide transparency in mes-

 

CS1W-EIP21

 

sage communications with other

 

CJ1W-EIP21

 

OMRON networks, such as Con-

 

troller Link, SYSMAC LINK, and

CJ2H-CPU@@-EIP

 

Ethernet.

CJ2M-CPU3@

 

(CS1/CJ1 CPU Units with unit

 

 

 

 

 

 

version 2.0 or later or CJ2 CPU

 

 

 

 

 

 

Units: Up to 8 levels, CPU Units

 

 

 

 

 

 

with unit version earlier than 2.0:

 

 

 

 

 

 

Up to 3 levels)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Send

 

 

 

 

 

 

 

 

 

 

 

FINS communications function

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Receive

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Message communications functions

Send

Explicit message

communications function Receive

188

 

Overview

 

Section 7-1

Overall Structure

 

 

 

CPU Unit

 

EtherNet/IP Unit

 

 

 

 

 

 

 

 

 

CMND(490)

 

FINS

 

 

 

instruction

 

 

 

 

FINS message

message

 

 

 

 

 

 

 

 

 

function

 

 

 

 

 

 

 

CMND(490)

 

 

 

 

instruction

 

Explicit

 

 

(2810 Hex)

FINS Explicit message

 

 

 

 

message

 

 

 

 

function

OMRON special message communications

FINS message

Ethernet (EtherNet/IP) network

EtherNet/IP message communications

Explicit message

Note With the EtherNet/IP Unit orbuilt-inEtherNet/IP port, message communications are possible even if the I/O link function is disabled.

189

FINS Message Communications Section 7-2

7-2

FINS Message Communications

 

 

 

 

 

 

Messages containing FINS commands can be exchanged over the Ethernet

 

 

 

network between nodes that support FINS messages.

 

 

Note FINS message communications can be executed without any particular

 

 

 

restrictions over the Ethernet network with OMRON Ethernet Units (CS1W-

 

 

 

ETN21 or CJ1W-ETN21),computers(CX-Oneor Fins Gateway applications),

 

 

 

and NS-seriesProgrammable Terminals.

 

 

 

 

 

 

 

Type of FINS message

 

Data send/receive commands

 

Any kind of FINS command

 

 

 

 

 

 

 

Network

 

SEND/RECV instructions

 

CMND(490) instructions

communications

 

 

 

 

 

 

instructions

 

 

 

 

 

 

 

 

 

 

 

 

 

PLC to PLC (both must

 

CS/CJ-seriesPLCCS/CJ-seriesPLC

 

CS/CJ-seriesPLCCS/CJ-seriesPLC

be CS/CJ-seriesPLCs

 

 

 

 

 

 

 

 

with a CS/CJ-seriesEth-

 

 

 

 

 

Command to

erNet/IP Unit, built-in

 

 

 

 

 

EtherNet/IP Unit

EtherNet/IP port, or

 

 

 

 

 

 

 

 

 

 

Command

Ethernet Units) (See

 

 

 

 

 

 

note 1.)

 

 

 

 

 

 

Note Inter-networkcom-

 

 

 

 

CS/CJ-seriesPLC

 

munications are

 

 

 

 

 

 

 

 

 

 

 

 

possible with

 

 

 

 

 

Command to

 

Ethernet networks

 

 

 

 

 

CPU Unit

 

or other networks,

 

 

 

 

Command

 

such as Controller

 

 

 

 

 

 

 

 

 

 

 

 

Link. (See note 2.)

 

 

 

 

 

 

 

 

 

 

 

 

 

Data length (excluding

 

SEND instruction: 990 words: RECV

 

CMND instruction: 1,990 bytes max.

command code)

 

instruction: 990 words.

 

 

 

 

 

 

 

 

 

 

 

 

Note 1. When two or more Communications Units (including the EtherNet/IP Units andbuilt-inEtherNet/IP ports) are mounted to aCS/CJ-seriesPLC and FINS messages are being used, the EtherNet/IP Units andbuilt-inEtherNet/IP ports must be registered in theCS/CJ-seriesPLC’s local network routing table. The commands will not be sent if the Unit is not registered in the routing tables.

2.When a CS/CJ-seriesEtherNet/IP Unit orbuilt-inEtherNet/IP port is connected to an Ethernet network, message communications can be conducted between networks, including other Ethernet networks as well as other networks such as Controller Link and SYSMAC LINK. Up to eight levels of networks can be crossed, provided that routing tables (containing local network tables and relay network tables) have been registered in the CPU Units of each PLC on the network.

3.A Programming Device connected to the CPU Unit of a PLC connected to the network can be used to program and monitor another PLC that is on the network. Up to eight levels of networks can be crossed for CS1/CJ1series CPU Units with unit version 2.0 or later, CJ2 CPU Units, and CXProgrammer version 4.0 or higher.

190

FINS Message Communications

Section 7-2

Up to 8 network levels, including the EtherNet/IP network, can be crossed.

Controller Link Unit

Controller Link Unit CS/CJ-seriesEtherNet/IP Unit

CS/CJ-seriesCPU Unit

Remote I/O communications

Controller Link

CS/CJ-seriesEtherNet/IP Unit

 

Ethernet (EtherNet/IP)

 

CS/CJ-seriesEtherNet/IP Unit

 

Ethernet (EtherNet/IP)

Note FINS commands sent and received by theCS/CJ-seriesEtherNet/IP Unit include commands addressed to theCS/CJ-seriesCPU Unit and commands addressed to theCS/CJ-seriesEtherNet/IP Unit.

191

Explicit Message Communications Section 7-3

7-3

Explicit Message Communications

 

 

 

Explicit messages defined in EtherNet/IP can be used to send service

 

 

requests to other companies’ EtherNet/IP masters/slaves and OMRON PLCs

 

 

with CS/CJ-seriesEtherNet/IP Units andbuilt-inEtherNet/IP ports.

 

 

Note Specific FINS commands (commands 2810 and 2801) are used to send

 

 

explicit messages.

 

 

 

 

Explicit message

Sending

Receiving

 

 

 

Network communi-

CIP UCMM messages can be sent to an EtherNet/IP

Automatically responds to explicit mes-

cations instruction

Unit or built-inEtherNet/IP port by a CMND(490)

sages from other devices.

 

 

instruction containing FINS command code 2810

 

 

 

Hex.

 

 

 

 

Functions supported

• Masters/slaves made by other manufacturers:

• Masters made by other manufacturers

in remote devices

Supported services determine supported functions.

• PLC with a CS/CJ-seriesEtherNet/IP Unit

 

 

• PLC with a CS/CJ-seriesEtherNet/IP Unit orbuilt-in

or built-inEtherNet/IP port: Supports the

 

 

EtherNet/IP port:

reading/writing of the local CPU Unit’s sta-

 

 

Supports the reading/writing of a remote CPU Unit’s

tus information and I/O memory data.

 

 

status information and I/O memory data.

 

 

 

 

 

Note TheCS/CJ-seriesEtherNet/IP Units andbuilt-inEtherNet/IP ports (CS1WEIP21,CJ1W-EIP21,CJ2H-CPU@@-EIP,orCJ2M-CPU3@)contain a PLC Object, so that other devices can read/write the I/O memory of the CPU Unit with thebuilt-inEtherNet/IP port or the CPU Unit to which the EtherNet/IP Unit is mounted.

192

Message Communications Specifications Section 7-4

7-4

Message Communications Specifications

 

 

 

 

 

 

CPU Unit function

 

CS/CJ Series

 

 

 

Unit model number

 

CS1W-EIP21,CJ1W-EIP21,CJ2H-CPU@@-EIP,orCJ2M-CPU3@

 

 

 

Communications

Sending/ receiving

SEND and RECV instructions

instructions

data

 

 

 

 

 

 

 

 

FINS commands

CMND(490) instruction

 

 

 

 

 

 

 

There are two kinds of FINS commands: commands addressed to the CPU

 

 

 

Unit, and commands addressed to the CS/CJ-seriesEtherNet/IP Unit or

 

 

 

built-inEtherNet/IP port.

 

 

 

 

 

 

Sending Ether-

CMND(490) instruction

 

 

Net/IP CIP UCMM

 

 

 

 

Sends CIP UCMM messages to other companies’ masters/slaves, or PLCs

 

 

messages

 

 

with a CS/CJ-seriesEtherNet/IP Unit orbuilt-inEtherNet/IP port mounted.

 

 

 

 

 

 

Number of desti-

FINS message com-

1:N communications

nation nodes

munications

 

 

 

 

 

 

 

 

Explicit message

1:N communications

 

 

communications

Send functions:

CIP unconnected (UCMM) communications only

 

 

 

 

 

 

Receive functions: CIP unconnected (UCMM) and CIP connected (Class 3)

 

 

 

 

communications

 

 

 

Transmission data

FINS message com-

• SEND: 990 words (1,980 bytes) max. normally, or 727 words (1,454 bytes)

length (not includ-

munications

max. when broadcasting

ing the command

 

• RECV: 990 words (1,980 bytes) max.

code)

 

 

• CMND: 1,990 bytes max. normally, or 1,462 bytes max. when broadcasting

 

 

 

 

 

 

(data after the FINS command code)

 

 

 

 

 

 

Explicit message

CMND: 492 bytes max.

 

 

communications

 

 

 

 

 

No. of simultaneous instructions

One each for 8 ports (ports 0 to 7)

 

 

 

Refer to 3-25Network Instructionsin the CS/CJ Series Programmable Con-

 

 

 

trollers Instructions Reference Manual (W340) for information on ports (logi-

 

 

 

cal ports).

 

 

 

Response monitoring time

Default setting: 2 s

 

 

 

User setting:

0.1 to 6553.5 s

 

 

 

 

 

Retries

 

 

0 to 15

 

 

 

 

Internetwork con-

Same network type

Supports internetwork communications between Ethernet networks con-

nections

 

 

nected to CS/CJ-seriesEtherNet/IP Units andbuilt-inEtherNet/IP ports (up

 

 

 

to 3 levels).

 

 

 

 

 

 

 

Different network

Supports internetwork communications between the EtherNet/IP network

 

 

type

connected to a CS/CJ-seriesEtherNet/IP Unit orbuilt-inEtherNet/IP port

 

 

 

and other networks such as Controller Link or SYSMAC LINK (up to 3 lev-

 

 

 

els).

 

 

 

 

 

 

193

Message Communications Error Indications

Section 7-5

7-5Message Communications Error Indications

There are two ways to obtain information on communications errors that occur in message communications: checking the EtherNet/IP Unit’s error log or checking its indicators.

1,2,3... 1. Each time a communications error occurs, an error code is placed in an error record in the error log stored in RAM in the EtherNet/IP Unit or CPU Unit with thebuilt-inEtherNet/IP Port. Up to 64 records can be stored in the error log. The time and date that the error occurred are also recorded together.

The error log can be read or cleared from the CPU Unit by sending an FINS command to the EtherNet/IP Unit (Error Log Read/Clear). The contents of the error log can also be monitored from the Configurator.

Code

Code

64 records

Code

FINS command

 

CPU Unit

 

 

 

 

 

Read-out

 

 

 

 

 

 

 

 

 

 

 

 

 

Monitor

 

Configurator

 

 

 

 

2.When a communications error has occurred, details on the error are indicated by the MS and NS indicators and the 7-segmentdisplay on the front panel of the EtherNet/IP Unit or CPU Unit with thebuilt-inEtherNet/IP port. This information can be used for troubleshooting.

Example: Routing table error

Flashing red Not relevant

MS

NS

Communications status 3

15

00

EtherNet/IP CPU

Unit Unit

194