Omron Sysmac Cj1W Eip21 Users Manual CS And CJ Series .CS1W (100Base TX) .CJ1W .CJ2H CPU6_ EIP .CJ2M CPU3_ TX/1

CJ2M-CPU3@ to the manual 96fea41f-c557-4a36-922a-fbeb65ac0a13

2015-01-24

: Omron Omron-Sysmac-Cj1W-Eip21-Users-Manual-332556 omron-sysmac-cj1w-eip21-users-manual-332556 omron pdf

Open the PDF directly: View PDF PDF.
Page Count: 464 [warning: Documents this large are best viewed by clicking the View PDF Link!]

OPERATION MANUAL
Cat. No. W465-E1-05
SYSMAC CS and CJ Series
CS1W-EIP21 (100Base-TX)
CJ1W-EIP21 (100Base-TX)
CJ2H-CPU6@-EIP (100Base-TX)
CJ2M-CPU3@ (100Base-TX/10Base-T)
EtherNet/IP Units
CS1W-EIP21 (100Base-TX)
CJ1W-EIP21 (100Base-TX)
CJ2H-CPU6@-EIP (100Base-TX)
CJ2M-CPU3@ (100Base-TX/10Base-T)
EtherNet/IP Units
Operation Manual
Revised February 2010
iv
v
Notice:
OMRON products are manufactured for use according to proper procedures by a qualified operator
and only for the purposes described in this manual.
The following conventions are used to indicate and classify precautions in this manual. Always heed
the information provided with them. Failure to heed precautions can result in injury to people or dam-
age to property.
!DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or
serious injury. Additionally, there may be severe property damage.
!WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or
serious injury. Additionally, there may be severe property damage.
!Caution Indicates a potentially hazardous situation which, if not avoided, may result in minor or
moderate injury, or property damage.
OMRON Product References
All OMRON products are capitalized in this manual. The word “Unit” is also capitalized when it refers to
an OMRON product, regardless of whether or not it appears in the proper name of the product.
The abbreviation “Ch,” which appears in some displays and on some OMRON products, often means
“word” and is abbreviated “Wd” in documentation in this sense.
The abbreviation “PLC” means Programmable Controller. “PC” is used, however, in some Program-
ming Device displays to mean Programmable Controller.
Visual Aids
The following headings appear in the left column of the manual to help you locate different types of
information.
Note Indicates information of particular interest for efficient and convenient opera-
tion of the product.
1,2,3... 1. Indicates lists of one sort or another, such as procedures, checklists, etc.
Trademarks and Copyrights
EtherNet/IP is a registered trademark of the ODVA (Open DeviceNet Vendor Association).
Ethernet is a trademark of the Xerox Corporation.
Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and Windows Vista are registered
trademarks of the Microsoft Corporation.
Other names of systems or products that appear in this document are trademarks or registered trade-
marks of the respective company.
OMRON, 2007
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form, o
r
by any means, mechanical, electronic, photocopying, recording, or otherwise, without the prior written permission o
f
OMRON.
No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is con-
stantly striving to improve its high-quality products, the information contained in this manual is subject to change without
notice. Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON assumes no responsibility
for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in
this publication.
vi
vii
TABLE OF CONTENTS
PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
1 Intended Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
2 General Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
3 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
5 Application Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiv
6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
SECTION 1
Overview of EtherNet/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1-1 EtherNet/IP Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2 Devices Required for Constructing a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-3 Support Software Required to Construct a Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-4 Communications Services Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1-5 Network Configurator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SECTION 2
Unit Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications . . . . . . . . . . . . . . . . . . . . . . 14
2-2 Nomenclature and Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-3 Selecting the Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SECTION 3
Installation and Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . 33
3-1 Overview of Initial Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-2 Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-3 Mounting to a PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-4 Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-5 Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
3-6 Creating I/O Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3-7 Setting the Local IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
3-8 TCP/IP and Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
3-9 Tag Data Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
3-10 Other Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3-11 Communications Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
viii
TABLE OF CONTENTS
SECTION 4
Memory Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4-1 Overview of Memory Allocated to the EtherNet/IP Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4-2 CIO Area Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4-3 DM Area Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-4 User Settings Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-5 Auxiliary Area Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
SECTION 5
Determining IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5-1 IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-2 IP Addresses in FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5-3 Private and Global Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
SECTION 6
Tag Data Link Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
6-1 Overview of Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
6-2 Setting Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
6-3 Ladder Programming with Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
SECTION 7
Message Communications Functions . . . . . . . . . . . . . . . . . . 187
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
SECTION 8
FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
8-1 Overview of FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
8-2 FINS/UDP Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
8-3 FINS/TCP Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
8-4 Routing Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
8-5 Using FINS Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .211
8-6 Communicating between OMRON PLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
8-7 Precautions on High Traffic in FINS Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
SECTION 9
Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
9-1 Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .234
9-2 Receiving Explicit Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
ix
TABLE OF CONTENTS
SECTION 10
Communications Performance and Communications Load 261
10-1 Communications System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .262
10-2 Adjusting the Communications Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
10-3 I/O Response Time in Tag Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
10-4 Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports . . . . . . . . . . . . . . . . . . . . 291
10-5 Message Service Transmission Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
SECTION 11
FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
11-1 Overview and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .302
11-2 FTP Server Function Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .303
11-3 Using the FTP Server Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
11-4 FTP Server Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
11-5 Using FTP Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .308
11-6 Checking FTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
11-7 Using File Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
11-8 FTP File Transfer Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
11-9 Host Computer Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
SECTION 12
Automatic Clock Adjustment Function . . . . . . . . . . . . . . . . 323
12-1 Automatic Clock Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
12-2 Using the Automatic Clock Adjustment Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
12-3 Automatic Clock Adjustment Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
12-4 Automatic Clock Adjustment Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
SECTION 13
Maintenance and Unit Replacement. . . . . . . . . . . . . . . . . . . 331
13-1 Maintenance and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
13-2 Simple Backup Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .333
13-3 Using the Backup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
SECTION 14
Troubleshooting and Error Processing. . . . . . . . . . . . . . . . . 339
14-1 Checking Status with the Network Configurator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
14-2 Using the LED Indicators and Display for Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . 347
14-3 Connection Status Codes and Error Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
14-4 Error Log Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
14-5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
14-6 Troubleshooting with FINS Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
x
TABLE OF CONTENTS
Appendices
A CS/CJ-series Ethernet Unit Function Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
B Ethernet Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
C TCP Status Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .379
D CIP Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
E FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports . . . . . . . . 391
F EDS File Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
G Precautions for Using Windows XP, Vista, or Windows 7 . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
xi
About this Manual:
This manual describes the operation of the CS/CJ-series EtherNet/IP Units and the built-in EtherNet/IP
ports on a CJ2 CPU Unit for constructing applications and includes the sections described below.
Please read this manual carefully and be sure you understand the information provided before
attempting to install or operate the EtherNet/IP Unit or built-in EtherNet/IP port. Be sure to read the
precautions provided in the following section.
Precautions provides general precautions for using the CS/CJ-series EtherNet/IP Units and built-in
EtherNet/IP ports.
Section 1 introduces the functions and protocols used in EtherNet/IP Unit or built-in EtherNet/IP port
communications services.
Section 2 provides the specifications of EtherNet/IP Units and introduces recommended network con-
figuration devices.
Section 3 explains how to install and make the initial settings required for operation of the EtherNet/IP
Unit or built-in EtherNet/IP port.
Section 4 describes the words allocated in the CIO Area and the DM Area for EtherNet/IP Units or
built-in EtherNet/IP ports.
Section 5 explains how to manage and use IP addresses.
Section 6 describes tag data link functions and related Network Configurator operations.
Section 7 describes message communications using FINS messages and explicit messages.
Section 8 provides information on communicating on EtherNet/IP Systems and interconnected net-
works using FINS commands. The information provided in the section deals only with FINS communi-
cations in reference to EtherNet/IP Units or built-in EtherNet/IP ports.
Section 9 describes message communications using FINS commands sent from the ladder program
in the CPU Unit of the PLC.
Section 10 describes the communications performance in an EtherNet/IP network, and shows how to
estimate the I/O response times and transmission delays.
Section 11 describes the functions provided by the FTP server.
Section 12 provides an overview of the automatic clock adjustment function, including details on spec-
ifications, required settings, operations from CX-Programmer, and troubleshooting.
Section 13 describes cleaning, inspection, and Unit replacement procedures, as well as the Simple
Backup Function.
Section 14 describes error processing, periodic maintenance operations, and troubleshooting proce-
dures needed to keep the EtherNet/IP network operating properly. We recommend reading through the
error processing procedures before operation so that operating errors can be identified and corrected
more quickly.
Appendices provide information on EtherNet/IP network parameters, the buffer configuration, TCP
status transitions, ASCII characters, maintenance, and inspections.
xii
Relevant Manuals
The following table lists CS- and CJ-series manuals that contain information relevant to EtherNet/IP
Units or built-in EtherNet/IP ports.
Manual
number Model Name Contents
W465 CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU6@-EIP
CJ2M-CPU3@
EtherNet/IP Units
Operation Manual
(this manual)
Provides information on operating and installing Ether-
Net/IP Units, including details on basic settings, tag data
links, and FINS communications.
Refer to the Communications Commands Reference
Manual (W342) for details on FINS commands that can
be sent to CS-series and CJ-series CPU Units when
using the FINS communications service.
Refer to the Ethernet Units Operation Manual
Construction of Applications (W421) for details on con-
structing host applications that use FINS communica-
tions.
W420 CS1W-ETN21
CJ1W-ETN21 Ethernet Units Oper-
ation Manual
Construction of Net-
works
Provides information on operating and installing
100Base-TX Ethernet Units, including details on basic
settings and FINS communications. Refer to the Commu-
nications Commands Reference Manual (W342) for
details on FINS commands that can be sent to CS-series
and CJ-series CPU Units when using the FINS communi-
cations service.
W421 CS1W-ETN21
CJ1W-ETN21 Ethernet Units Oper-
ation Manual
Construction of
Applications
Provides information on constructing host applications for
100Base-TX Ethernet Units, including functions for send-
ing/receiving mail, socket service, automatic clock adjust-
ment, FTP server functions, and FINS communications.
W343 CS1W-ETN01
CS1W-ETN11
CJ1W-ETN11
Ethernet Units Oper-
ation Manual Describes the installation and operation of the 10Base-5
and 10Base-T Ethernet Units.
W342 CS1G/H-CPU@@H
CS1G/H-CPU@@-V1
CS1W-SCU@@-V1
CS1W-SCB@@-V1
CJ2H-CPU6@-EIP
CJ2H-CPU6@
CJ2M-CPU@@
CJ1G/H-CPU@@H
CJ1G-CPU@@
CJ1M-CPU@@
CJ1W-SCU@@-V1
CP1E-E@@D@-@
CP1E-N@@D@-@
CP1H-X@@@@-@
CP1H-Y@@@@-@@
Communications
Commands Refer-
ence Manual
Describes the C-series (Host Link) and FINS communi-
cations commands used when sending communications
commands to CS-series, CJ-series, CP-series, and SYS-
MAC One NSJ-series CPU Units.
W472 CJ2H-CPU6@-EIP
CJ2H-CPU6@
CJ2M-CPU@@
CJ-series CJ2 CPU
Unit Hardware
User’s Manual
Provides hardware information for the CJ2 CPU Units.
Information is included on features, system configuration,
component names, component functions, installation,
setting procedures, and troubleshooting.
Use together with the CJ-series CJ2 CPU Unit Software
User’s Manual (W473).
W473 CJ2H-CPU6@-EIP
CJ2H-CPU6@
CJ2M-CPU@@
CJ-series CJ2 CPU
Unit Software User’s
Manual
Provides software information for the CJ2 CPU Units.
Information is included on CPU Unit operation, internal
memory, programming, setting procedures, and CPU
Unit functions.
Use together with the CJ-series CJ2 CPU Unit Hardware
User’s Manual (W472).
xiii
W474 CJ2H-CPU6@-EIP
CJ2H-CPU6@
CJ2M-CPU@@
CS1G/H-CPU-@@H
CS1G/H-CPU-@@-V1
CJ1G/H-CPU@@H
CJ1M-CPU@@
CJ1G-CPU@@
NSJ@-@@@@(B)-G5D
NSJ@-@@@@(B)-M3D
Programmable Con-
trollers Instructions
Reference Manual
Describes the ladder diagram programming instructions
supported by CS-series and CJ-series PCs. Use this
manual for CJ2 CPU Units.
W339 CS1G/H-CPU@@H
CS1G/H-CPU-@@V1 Programmable Con-
trollers Operation
Manual
Provides an outline of, and describes the design, installa-
tion, maintenance, and other basic operations for the CS-
series PLCs. Information is also included on features,
system configuration, wiring, I/O memory allocations, and
troubleshooting.
Use together with the Programmable Controllers Pro-
gramming Manual (W394).
W393 CJ1G/H-CPU@@H
CJ1G-CPU@@ Programmable Con-
trollers Operation
Manual
Provides an outline of, and describes the design, installa-
tion, maintenance, and other basic operations for the CJ-
series PLCs. Information is also included on features,
system configuration, wiring, I/O memory allocations, and
troubleshooting.
Use together with the Programmable Controllers Pro-
gramming Manual (W394).
W394 CS1G/H-CPU@@H
CS1G/H-CPU-@@V1
CJ1G/H-CPU@@H
CJ1G-CPU@@
NSJ@-@@@@(B)-G5D
NSJ@-@@@@(B)-M3D
Programmable Con-
trollers Program-
ming Manual
Describes programming, tasks, file memory, and other
functions for the CS-series, CJ-series, and NS-J-series
PLCs.
Use together with the Programmable Controllers Opera-
tion Manual (W339 for CS-series PLCs and W393 for CJ-
series PLCs).
W340 CS1G/H-CPU@@H
CS1G/H-CPU-@@V1
CJ1G/H-CPU@@H
CJ1G-CPU@@
NSJ@-@@@@(B)-G5D
NSJ@-@@@@(B)-M3D
Programmable Con-
trollers Instructions
Reference Manual
Describes the ladder diagram programming instructions
supported by CS-series and CJ-series PCs. Use together
with the Programmable Controllers Operation Manual
(W339 for CS-series PLCs and W393 for CJ-series
PLCs), and the Programmable Controllers Programming
Manual (W394).
W463 CXONE-AL@@C-V4
CXONE-AL@@D-V4 CS-One Setup Man-
ual Describes the setup procedures for the CX-One. Informa-
tion is also provided on the operating environment for the
CX-One.
W446 WS02-CXPC@-V9 CX-Programmer
Operation Manual Provides information on how to use the CX-Programmer,
a Windows-based programming device. Use together
with the Programmable Controllers Operation Manual
(W339 for CS-series PLCs and W393 for CJ-series
PLCs), Programmable Controllers Programming Manual
(W394) and the Programmable Controllers Instructions
Reference Manual (W340) to perform programming.
W464 CXONE-AL@@C-V4/
CXONE-AL@@D-V4 CS/CJ/CP/NSJ-
series CX-Integrator
Ver. 2.@ Operation
Manual
Describes the operating procedures of the CX-Integrator
that can be used to set up and monitor networks.
Manual
number Model Name Contents
!WARNING Failure to read and understand the information provided in this manual may result in per-
sonal injury or death, damage to the product, or product failure. Please read each section
in its entirety and be sure you understand the information provided in the section and
related sections before attempting any of the procedures or operations given.
xiv
xv
Read and Understand this Manual
Please read and understand this manual before using the product. Please consult your OMRON
representative if you have any questions or comments.
Warranty and Limitations of Liability
WARRANTY
OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a
period of one year (or other period if specified) from date of sale by OMRON.
OMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, REGARDING NON-
INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR PARTICULAR PURPOSE OF THE
PRODUCTS. ANY BUYER OR USER ACKNOWLEDGES THAT THE BUYER OR USER ALONE HAS
DETERMINED THAT THE PRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR
INTENDED USE. OMRON DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED.
LIMITATIONS OF LIABILITY
OMRON SHALL NOT BE RESPONSIBLE FOR SPECIAL, INDIRECT, OR CONSEQUENTIAL DAMAGES,
LOSS OF PROFITS OR COMMERCIAL LOSS IN ANY WAY CONNECTED WITH THE PRODUCTS,
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT
LIABILITY.
In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which
liability is asserted.
IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS
REGARDING THE PRODUCTS UNLESS OMRON'S ANALYSIS CONFIRMS THAT THE PRODUCTS
WERE PROPERLY HANDLED, STORED, INSTALLED, AND MAINTAINED AND NOT SUBJECT TO
CONTAMINATION, ABUSE, MISUSE, OR INAPPROPRIATE MODIFICATION OR REPAIR.
xvi
Application Considerations
SUITABILITY FOR USE
OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the
combination of products in the customer's application or use of the products.
At the customer's request, OMRON will provide applicable third party certification documents identifying
ratings and limitations of use that apply to the products. This information by itself is not sufficient for a
complete determination of the suitability of the products in combination with the end product, machine,
system, or other application or use.
The following are some examples of applications for which particular attention must be given. This is not
intended to be an exhaustive list of all possible uses of the products, nor is it intended to imply that the uses
listed may be suitable for the products:
• Outdoor use, uses involving potential chemical contamination or electrical interference, or conditions or
uses not described in this manual.
• Nuclear energy control systems, combustion systems, railroad systems, aviation systems, medical
equipment, amusement machines, vehicles, safety equipment, and installations subject to separate
industry or government regulations.
• Systems, machines, and equipment that could present a risk to life or property.
Please know and observe all prohibitions of use applicable to the products.
NEVER USE THE PRODUCTS FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR
PROPERTY WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE HAS BEEN DESIGNED TO
ADDRESS THE RISKS, AND THAT THE OMRON PRODUCTS ARE PROPERLY RATED AND INSTALLED
FOR THE INTENDED USE WITHIN THE OVERALL EQUIPMENT OR SYSTEM.
PROGRAMMABLE PRODUCTS
OMRON shall not be responsible for the user's programming of a programmable product, or any
consequence thereof.
xvii
Disclaimers
CHANGE IN SPECIFICATIONS
Product specifications and accessories may be changed at any time based on improvements and other
reasons.
It is our practice to change model numbers when published ratings or features are changed, or when
significant construction changes are made. However, some specifications of the products may be changed
without any notice. When in doubt, special model numbers may be assigned to fix or establish key
specifications for your application on your request. Please consult with your OMRON representative at any
time to confirm actual specifications of purchased products.
DIMENSIONS AND WEIGHTS
Dimensions and weights are nominal and are not to be used for manufacturing purposes, even when
tolerances are shown.
PERFORMANCE DATA
Performance data given in this manual is provided as a guide for the user in determining suitability and does
not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must
correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and
Limitations of Liability.
ERRORS AND OMISSIONS
The information in this manual has been carefully checked and is believed to be accurate; however, no
responsibility is assumed for clerical, typographical, or proofreading errors, or omissions.
xviii
xix
Unit Versions of CS/CJ-series
Unit Versions A “unit version” has been introduced to manage Units in the CS/CJ Series
according to differences in functionality accompanying Unit upgrades.
Notation of Unit Versions
on Products The unit version is given to the right of the lot number on the nameplate of the
products for which unit versions are being managed, as shown below.
■CS1W-EIP21/CJ1W-EIP21
■CJ2H-CPU@@-EIP/CJ2M-CPU3@
In this manual, the version of the EtherNet/IP port built into the CJ2H-
CPU@@-EIP/CJ2M-CPU3@ CPU Unit is given as the unit version.
Confirming Unit Versions
with Support Software CX-Programmer version 4.0 can be used to confirm the unit version using the
Unit Manufacturing Information.
Note The unit versions of Pre-Ver.1.0 Units cannot be confirmed in Unit Manufac-
turing Information. The following dialog box is displayed.
In the IO Table Window, right-click and select Unit Manufacturing informa-
tion - CPU Unit.
The following Unit Manufacturing information Dialog Box will be displayed.
CS1W-
UNIT
Lot No. 040401 0000 Ver.1.0
OMRON Corporation MADE IN JAPAN
Product nameplate
Unit version
Example for unit version 1.0
Lot No.
CJ2H-
UNIT
Lot No. 080701 CPU Ver. 1.0 EIP Ver.2.0
OMRON Corporation MADE IN JAPAN
Product nameplate
Indicates that the unit
version of the CPU Unit
is 1.0.
Indicates that the unit
version of the built-in
EtherNet I/P port is 2.0.
xx
Note The unit version will be displayed in the Unit Manufacturing Information Dialog
Box.
Using Unit Version Label The following unit version label is provided with the EtherNet/IP Unit.
This label can be attached to the front of the EtherNet/IP Unit to differentiate
between EtherNet/IP Units with different unit versions.
Unit Versions and CX-Programmer Versions
Use the following versions of the CX-Programmer to make the Unit settings for
the EtherNet/IP Unit.
* The following auto update must be applied to use CX-Programmer version 8.0:
CX-Common Components/CPS Upgrade Software 2008.08 0302
Unit Version Notation In this manual, the unit version of a EtherNet/IP Unit is given as shown in the
following table.
Note Some Support Software products call the EtherNet/IP Unit version the “revi-
sion.” “Revision” is also sometimes used in this manual.
CIP Revisions and
Unit Versions The CIP revisions corresponding to the unit versions of the EtherNet/IP Unit
are given in the following table.
Unit version
Unit version CX-Programmer
Ver. 7.1 or lower Ver. 8.0 Ver. 8.02 or higher
Unit version 1.0 --- OK* OK
Unit version 2.0 --- OK OK
Product nameplate Notation used in this manual Special remarks
Ver. 1.0 or later number
shown to right of the lot
number
Ethernet Unit Ver. 1.0 or later (See note.) Information without reference to specific Unit
Versions applies to all versions of the Unit.
Unit version CIP revision
Version 1.0 Revision 1.01
Version 2.0 Revision 2.01 or 2.02
xxi
PRECAUTIONS
This section provides general precautions for using the CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports.
The information contained in this section is important for the safe and reliable application of EtherNet/IP Units or
built-in EtherNet/IP ports. You must read this section and understand the information contained before attempting
to set up or operate an EtherNet/IP Unit or built-in EtherNet/IP port.
1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
3 Safety Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
4 Operating Environment Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
5 Application Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv
6 Conformance to EC Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
6-1 Applicable Directives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
6-2 Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
xxii
Intended Audience 1
1 Intended Audience
This manual is intended for the following personnel, who must also have
knowledge of electrical systems (an electrical engineer or the equivalent).
• Personnel in charge of installing FA systems.
• Personnel in charge of designing FA systems.
• Personnel in charge of managing FA systems and facilities.
2 General Precautions
The user must operate the product according to the performance specifica-
tions described in the operation manuals.
Before using the product under conditions which are not described in the
manual or applying the product to nuclear control systems, railroad systems,
aviation systems, vehicles, combustion systems, medical equipment, amuse-
ment machines, safety equipment, and other systems, machines, and equip-
ment that may have a serious influence on lives and property if used
improperly, consult your OMRON representative.
Make sure that the ratings and performance characteristics of the product are
sufficient for the systems, machines, and equipment, and be sure to provide
the systems, machines, and equipment with double safety mechanisms.
This manual provides information for programming and operating the Unit. Be
sure to read this manual before attempting to use the Unit and keep this man-
ual close at hand for reference during operation.
!WARNING It is extremely important that a PLC and all PLC Units be used for the speci-
fied purpose and under the specified conditions, especially in applications that
can directly or indirectly affect human life. You must consult with your OMRON
representative before applying a PLC System to the above-mentioned appli-
cations.
3 Safety Precautions
!WARNING Do not attempt to take any Unit apart while the power is being supplied. Doing
so may result in electric shock.
!WARNING Do not touch any of the terminals or terminal blocks while the power is being
supplied. Doing so may result in electric shock.
!WARNING Do not attempt to disassemble, repair, or modify any Units. Any attempt to do
so may result in malfunction, fire, or electric shock.
xxiii
Safety Precautions 3
!WARNING Provide safety measures in external circuits (i.e., not in the Programmable
Controller), including the following items, to ensure safety in the system if an
abnormality occurs due to malfunction of the Programmable Controller or
another external factor affecting the operation of the Programmable Control-
ler. “Programmable Controller” indicates the CPU Unit and all other Units and
is abbreviated “PLC” in this manual.
• Emergency stop circuits, interlock circuits, limit circuits, and similar safety
measures must be provided in external control circuits.
• The PLC will turn OFF all outputs when its self-diagnosis function detects
any error or when a severe failure alarm (FALS) instruction is executed.
As a countermeasure for such errors, external safety measures must be
provided to ensure safety in the system.
• The PLC will turn OFF all outputs when its self-diagnosis function detects
any error or when a severe failure alarm (FALS) instruction is executed.
Unexpected operation, however, may still occur for errors in the I/O con-
trol section, errors in I/O memory, and other errors that cannot be
detected by the self-diagnosis function. As a countermeasure for all such
errors, external safety measures must be provided to ensure safety in the
system.
• Provide measures in the computer system and programming to ensure
safety in the overall system even if errors or malfunctions occur in data
link communications or remote I/O communications.
!Caution Execute online editing only after confirming that no adverse effects will be
caused by extending the cycle time. Otherwise, the input signals may not be
readable.
• Emergency stop circuits, interlock circuits, limit circuits, and similar safety
measures must be provided in external control circuits.
!Caution Fail-safe measures must be taken by the customer to ensure safety in the
event of incorrect, missing, or abnormal signals caused by broken signal lines,
momentary power interruptions, or other causes. Serious accidents may
result from abnormal operation if proper measures are not provided.
!Caution Confirm safety at the destination node before changing or transferring to
another node the contents of a program, the PLC Setup, I/O tables, I/O mem-
ory, or parameters. Changing or transferring any of these without confirming
safety may result in injury.
!Caution Tighten the screws on the terminal block of the AC Power Supply Unit to the
torque specified in the operation manual. The loose screws may result in
burning or malfunction.
xxiv
Operating Environment Precautions 4
4 Operating Environment Precautions
!Caution Do not operate the control system in the following locations:
• Locations subject to direct sunlight.
• Locations subject to temperatures or humidity outside the range specified
in the specifications.
• Locations subject to condensation as the result of severe changes in tem-
perature.
• Locations subject to corrosive or flammable gases.
• Locations subject to dust (especially iron dust) or salts.
• Locations subject to exposure to water, oil, or chemicals.
• Locations subject to shock or vibration.
!Caution Take appropriate and sufficient countermeasures when installing systems in
the following locations:
• Locations subject to static electricity or other forms of noise.
• Locations subject to strong electromagnetic fields.
• Locations subject to possible exposure to radioactivity.
• Locations close to power supplies.
5 Application Precautions
Observe the following precautions when using the EtherNet/IP Unit or built-in
EtherNet/IP port.
!WARNING Always heed these precautions. Failure to abide by the following precautions
could lead to serious or possibly fatal injury.
• Always connect to a ground of 100 Ω or less when installing the Units. Not
connecting to a ground of 100 Ω or less may result in electric shock.
• Always turn OFF the power supply to the CPU Unit and Slaves before
attempting any of the following. Not turning OFF the power supply may
result in malfunction or electric shock.
• Mounting or dismounting Power Supply Units, I/O Units, CPU Units,
Memory Packs, or Master Units.
• Assembling the Units.
• Setting DIP switches or rotary switches.
• Connecting cables or wiring the system.
• Connecting or disconnecting the connectors.
!Caution Failure to abide by the following precautions could lead to faulty operation of
the EtherNet/IP Unit, built-in EtherNet/IP port, or the system, or could damage
the Ethernet Unit. Always heed these precautions.
• Interlock circuits, limit circuits, and similar safety measures in external cir-
cuits (i.e., not in the Programmable Controller) must be provided by the
customer.
xxv
Application Precautions 5
• Always use the power supply voltages specified in the operation manuals.
An incorrect voltage may result in malfunction or burning.
• Take appropriate measures to ensure that the specified power with the
rated voltage and frequency is supplied. Be particularly careful in places
where the power supply is unstable. An incorrect power supply may result
in malfunction.
• Install external breakers and take other safety measures against short-cir-
cuiting in external wiring. Insufficient safety measures
• Make sure that all the Backplane mounting screws, terminal block screws,
and cable connector screws are tightened to the torque specified in the
relevant manuals. Incorrect tightening torque may result in malfunction.
• Leave the label attached to the Unit when wiring. Removing the label may
result in malfunction if foreign matter enters the Unit.
• Remove the label after the completion of wiring to ensure proper heat dis-
sipation. Leaving the label attached may result in malfunction.
• Use crimp terminals for wiring. Do not connect bare stranded wires
directly to terminals. Connection of bare stranded wires may result in
burning.
• Observe the following precautions when wiring the communications
cable.
• Separate the communications cables from the power lines or high-ten-
sion lines.
• Do not bend the communications cables past their natural bending ra-
dius.
• Do not pull on the communications cables.
• Do not place heavy objects on top of the communications cables.
• Always lay communications cable inside ducts.
• Use appropriate communications cables.
• Make sure that the terminal blocks, expansion cable connectors, and
other items with locking devices are locked in place.
• Wire all connections correctly according to instructions in this manual.
• Double-check all wiring and switch settings before turning ON the power
supply. Incorrect wiring may result in burning.
• Mount terminal blocks and connectors only after checking the mounting
location carefully.
• Check the user program (ladder program and other programs) and
parameters for proper execution before actually running it on the Unit. Not
checking the program may result in unexpected operation.
• Confirm that no adverse effect will occur in the system before attempting
any of the following. Not doing so may result in an unexpected operation.
• Changing the operating mode of the PLC.
• Force-setting/force-resetting any bit in memory.
• Changing the present value of any word or any set value in memory.
• After replacing a Unit, resume operation only after transferring to the new
CPU Unit, Special I/O Unit, or CPU Bus Unit the contents of the DM Area,
HR Area, programs, parameters, and other data required for resuming
operation. Not doing so may result in an unexpected operation.
• Before touching a Unit, be sure to first touch a grounded metallic object in
order to discharge any static build-up. Not doing so may result in malfunc-
tion or damage.
xxvi
Conformance to EC Directives 6
• When transporting the Unit, use special packing boxes and protect it from
being exposed to excessive vibration or impacts during transportation.
• CPU Bus Units will be restarted when routing tables are transferred from
a Programming Device to the CPU Unit. Restarting these Units is required
to read and enable the new routing tables. Confirm that the system will
not be adversely affected before allowing the CPU Bus Units to be reset.
• When the settings (IP address or tag data link settings) of the EtherNet/IP
Unit or built-in EtherNet/IP port are transferred from a Programming
Device, all of the destination EtherNet/IP Units or built-in EtherNet/IP
ports (nodes) will be reset in order to enable the transferred settings.
Transfer settings to the EtherNet/IP Units or built-in EtherNet/IP ports only
after verifying that restarting the Units will not cause any problems in the
system.
• If a repeater hub is used for EtherNet/IP tag data links (cyclic communica-
tions), the network's communications load will increase, data collisions
will occur frequently, and stable communications will be impossible.
Always use a switching hub when using tag data links in the network.
• Before resetting a CPU Bus Unit or Special I/O Unit, always verify that
restart the Unit will not cause any problems in the system.
6 Conformance to EC Directives
6-1 Applicable Directives
•EMC Directives
• Low Voltage Directive
6-2 Concepts
EMC Directives
OMRON devices that comply with EC Directives also conform to the related
EMC standards so that they can be more easily built into other devices or the
overall machine. The actual products have been checked for conformity to
EMC standards (see the following note). Whether the products conform to the
standards in the system used by the customer, however, must be checked by
the customer.
EMC-related performance of the OMRON devices that comply with EC Direc-
tives will vary depending on the configuration, wiring, and other conditions of
the equipment or control panel on which the OMRON devices are installed.
The customer must, therefore, perform the final check to confirm that devices
and the overall machine conform to EMC standards.
Note Applicable EMS (Electromagnetic Susceptibility) and EMI (Electromagnetic
Interference) Standards in the EMC (Electromagnetic Compatibility) stan-
dards are as follows:
Low Voltage Directive
Always ensure that devices operating at voltages of 50 to 1,000 V AC and 75
to 1,500 V DC meet the required safety standards for the PLC (EN61131-2).
EtherNet/IP Unit EMS EMI
CS1W-EIP21 EN61000-6-2 EN61000-6-4
(Radiated emission: 10-m
regulations)
CJ1W-EIP21
1
SECTION 1
Overview of EtherNet/IP
This section introduces the functions and protocols used in EtherNet/IP Unit or built-in EtherNet/IP port communications
services.
1-1 EtherNet/IP Unit Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1-2 Devices Required for Constructing a Network . . . . . . . . . . . . . . . . . . . . . . . . 4
1-3 Support Software Required to Construct a Network. . . . . . . . . . . . . . . . . . . . 4
1-4 Communications Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1-5 Network Configurator Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-5-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1-5-2 Network Configurator Requirements . . . . . . . . . . . . . . . . . . . . . . . . 10
1-5-3 Precautions When Using the Network Configurator . . . . . . . . . . . . 11
2
EtherNet/IP Unit Features Section 1-1
1-1 EtherNet/IP Unit Features
EtherNet/IP is an industrial multi-vendor network that uses Ethernet compo-
nents. The EtherNet/IP specifications are open standards managed by the
ODVA (Open DeviceNet Vendor Association), just like DeviceNet.
EtherNet/IP is not just a network between controllers; it is also used as a field
network. Since EtherNet/IP uses standard Ethernet technology, various gen-
eral-purpose Ethernet devices can be used in the network. The EtherNet/IP
Unit and built-in EtherNet/IP port have the following features.
High-speed, High-capacity
Data Exchange through
Data Links
The EtherNet/IP protocol supports implicit communications, which allows
cyclic communications (called tag data links in this manual) with EtherNet/IP
devices. Data can be exchanged at high speed between Controllers and
devices, using high-volume tag sets (up to 640 words for the CJ2M and up to
184,832 words for other CPU Units) between PLCs.
Tag Data Link (Cyclic
Communications) Cycle
Time
Tag data links (cyclic communications) can operate at the cyclic period speci-
fied for each application, regardless of the number of nodes. Data is
exchanged over the network at the refresh cycle set for each connection, so
the communications refresh cycle will not increase even if the number of
nodes is increased, i.e., the synchronicity of the connection’s data is pre-
served.
Since the refresh cycle can be set for each connection, each application can
communicate at its ideal refresh cycle. For example, a processes interlocks
can be transferred at high speed while the production commands and the sta-
tus monitor information are transferred at low speed.
Note The communications load to the nodes must be within the Units’ allowed com-
munications bandwidth.
Communicating with FINS
Messages (FINS/TCP and
FINS/UDP)
Data can be exchanged with other OMRON FA devices using SEND, RECV,
and CMND instructions from the ladder program, because EtherNet/IP sup-
ports OMRON’s standard FINS message communications services.
There are two kinds of message services, using UDP/IP and TCP/IP (called
FINS/UDP and FINS/TCP), allowing flexible data exchange for different appli-
cations.
Note There are no particular restrictions when sending FINS messages to OMRON
Ethernet Units (CS1W-ETN21 or CJ1W-ETN21) in an Ethernet network.
Network Connections with
Controller Link Mutual connections of Controller Link and EtherNet/IP are also supported
(using the FINS communications service). The Controller Link connection
allows a PLC on the Controller Link network to be monitored from a PLC on
the EtherNet/IP network. Conversely, data can be exchanged with a PLC on
the EtherNet/IP network from a PLC on the Controller Link network.
(3) Switching hub
CX-One Support
Software
(2) Twisted-pair cable
100 m
max.
(1) CS1W-EIP21 EtherNet/IP
Unit for CS-series (1) CJ1W-EIP21
EtherNet/IP Unit
CS-series
PLC
CJ-series
PLC
Ethernet (LAN) port
(1) Built-in EtherNet/IP port on
CJ2 CPU Unit
(CJ2H-CPU@@-EIP/
CJ2M-CPU3@)
CJ-series
PLC
EtherNet/IP S
y
stem Confi
g
uration Exam
p
le
3
EtherNet/IP Unit Features Section 1-1
FTP Server A built-in FTP server is provided to enable transferring files in the PLC to and
from a host computer. This enables transferring large amounts of data from a
client without any additional ladder programming.
Automatic PLC Clock
Adjustment The clocks built into PLCs connected to Ethernet can be automatically
adjusted to the time of the clock in the SNTP server. If all of the clocks in the
system are automatically adjusted to the same time, time stamps can be used
to analyze various production histories.
Note A separate SNTP server is necessary to automatically adjust the PLC clocks.
Manage the Network with
an SNMP Manager Internal status information from the EtherNet/IP Unit or built-in EtherNet/IP
port can be passed to network management software that uses an SNMP
manager.
Note A separate SNMP manager is necessary for network management.
Specify Servers with Host
Names DNS client functionality allows you to use host names instead of IP addresses
to specify SNTP servers and SNMP managers. This is useful, for example,
when server IP addresses change for system revisions because the IP
addresses are automatically found when host names are used.
Note (1) A separate DNS server is necessary to use host names with the DNS cli-
ent.
(2) The DNS server is specified directly using its IP address.
Set Classless IP Address
with CIDR A subnet mask can be set to use classless IP addresses, allowing more flexi-
bility in address settings.
Plentiful Troubleshooting
Functions A variety of functions are provided to quickly identify and handle errors.
• Self-diagnosis at power ON
• PING command to check the connection with another node
• Error Log functions record the time of occurrence and other error details
Note The CIP (Common Industrial Protocol) is a shared industrial protocol for the
OSI application layer. The CIP is used in networks such as EtherNet/IP, Con-
trolNet, and DeviceNet. Data can be routed easily between networks that are
based on the CIP, so a transparent network can be easily configured from the
field device level to the host level.
The CIP has the following advantages.
• Destination nodes are specified by a relative path, without fixed routing
tables.
• The CIP uses the producer/consumer model. Nodes in the network are
arranged on the same level and it is possible to communicate with
required devices whenever it is necessary.
The consumer node will receive data sent from a producer node when the
connection ID in the packet indicates that the node requires the data.
Since the producer can send the same data with the same characteristics
in a multicast (either multicast or unicast can be selected), the time
required for the transfer is fixed and not dependent on the number of con-
sumer nodes.
4
Devices Required for Constructing a Network Section 1-2
1-2 Devices Required for Constructing a Network
The basic configuration for an EtherNet/IP System consists of one switching
hub to which nodes are attached in star configuration using twisted-pair cable.
The devices shown in the following table are required to configure a network
with CS1W-EIP21 and CJ1W-EIP21 EtherNet/IP Units or the built-in EtherNet/
IP port in CJ2H-CPU@@-EIP/CJ2M-CPU3@ CPU Units.
Recommended
Switching Hubs For details on recommended devices for constructing a network, refer to 2-3-1
Recommended Network Devices.
Note If a repeater hub is used for EtherNet/IP tag data links (cyclic communica-
tions), the network’s communications load will increase, data collisions will
occur frequently, and stable communications will be impossible. Always use a
switching hub when using tag data links in the network.
1-3 Support Software Required to Construct a Network
This section describes the Support Software that is required to construct an
EtherNet/IP network. Make the tag data link settings and Unit setup settings
for the EtherNet/IP Unit or built-in EtherNet/IP port. Both of these settings are
stored in the EtherNet/IP Unit’s non-volatile memory (See note.). Support
Software is provided for each, as described below.
Note Unlike the Ethernet Units, the EtherNet/IP Unit’s TCP/IP settings are not
stored in the CPU Unit’s CPU Bus Unit System Setup Area. The settings are
stored in the EtherNet/IP Unit itself.
Unit Setup: CX-
Programmer The CX-Programmer is used to set basic parameters, such as the local IP
address of the EtherNet/IP Unit or built-in EtherNet/IP port and the subnet
mask. (The CX-Programmer is included in the CX-One.)
The CX-Programmer can also be used to check if data I/O is being performed
correctly for tag data links.
(3) Switching hub
CX-One Support
Software
(2) Twisted-pair cable
100 m
max.
(1) CS1W-EIP21 EtherNet/IP
Unit for CS-series (1) CJ1W-EIP21
EtherNet/IP Unit
CS-series
PLC
CJ-series
PLC
Ethernet (LAN) port
(1) Built-in EtherNet/IP port on
CJ2 CPU Unit
(CJ2H-CPU@@-EIP/
CJ2M-CPU3@)
CJ-series
PLC
Network device Contents
(1) CS1W-EIP21 EtherNet/IP
Units for CS-series PLCs,
CJ1W-EIP21 EtherNet/IP
Units for CJ-series PLCs,
or built-in EtherNet/IP port
in CJ2H-CPU@@-EIP/
CJ2M-CPU3@ CPU Units
These are Communications Units or built-in ports
that connect a CS-series or CJ-series PLC to an Eth-
erNet/IP network.
(2) Twisted-pair cable The twisted-pair cable connects EtherNet/IP Units or
built-in EtherNet/IP ports to the switching hub, with
an RJ45 Modular Connector at each end.
Use an STP (shielded twisted-pair) cable of category
5, 5c, or higher.
(3) Switching Hub This is a relay device that connects multiple nodes in
a star-shaped LAN.
5
Support Software Required to Construct a Network Section 1-3
Refer to the CX-Programmer Operation Manual (Cat. No. W446) for informa-
tion on the CX-Programmer.
Tag Data Link Settings:
Network Configurator The Network Configurator is used to set the tag data links for the EtherNet/IP
Unit or built-in EtherNet/IP port. (The Network Configurator is included in CX-
One version 3.0 or higher.) The main functions of the Network Configurator
are given below.
1) Setting and Monitoring Tag Data Links (Connections)
The network device configuration and tag data links (connections) can be cre-
ated and edited. After connecting to the network, the device configuration and
tag data link settings can be uploaded and monitored.
2) Multivendor Device Connections
EDS files can be installed and deleted to enable constructing, setting, and
managing networks that contain EtherNet/IP devices from other companies.
The IP addresses of EtherNet/IP devices can also be changed.
For details on the Network Configurator, refer to SECTION 6 Tag Data Link
Functions.
Routing Table Settings:
CX-Integrator Propriety OMRON FINS network system can be constructed from OMRON
Communications Units. When FINS services are used, the CX-Integrator
allows you to set routing tables to define transmission paths. (The CX-Integra-
tor is included in the CX-One.) If FINS services are not used, then routing
tables are not required.
EtherNet/IP Unit
or built-in
EtherNet/IP port
CS/CJ-series CPU Unit
Computer
CX-Programmer Edit Parameters
Dialog Box
Unit settings
(Built-in non-volatile memory)
EtherNet/IP Unit
or built-in EtherNet/IP port
CS/CJ-series CPU Unit
Computer
Network Configurator Edit Device
Parameters
Dialog Box
Tag Data Link Settings
(Built-in non-volatile memory)
Transferred
6
Communications Services Overview Section 1-4
Refer to the CX-Integrator Operation Manual (Cat. No. W464) for information
on the CX-Integrator.
1-4 Communications Services Overview
The following communications services are supported.
CIP (Common Industrial Protocol) Communications Services
1) Tag Data Links (Cyclic Communications)
A program is not required to perform cyclic data exchanges with other devices
in the EtherNet/IP network.
Normally, the tag data links in an EtherNet/IP Unit or built-in EtherNet/IP port
are started by grouping the tags created with the Network Configurator into a
tag set, and establishing a connection with the target device using that group
of tags. One connection is used per group (tag set). Up to 32 connections for
the CJ2M and up to 256 connections for other CPU Units) can be registered.
The following table gives the tag and tag set specifications.
Personal computer
running Windows
CX-Integrator
Routing table
settings
EtherNet/IP Unit or
built-in EtherNet/IP port
CS/CJ-series CPU Unit
Routing Table Area
Tags Tag sets
CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
CJ2M-CPU3@CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
CJ2M-CPU3@
Total size of all tags ≤
184,832 words Total size of all tags ≤ 640
words Maximum size of 1 tag set ≤
722 words
(The maximum size is 721
words when the tag set
includes the PLC status.)
Maximum size of 1 tag set ≤
20 words
(The maximum size is 19
words when the tag set
includes the PLC status.)
Maximum size of 1 tag ≤ 722
words
(The maximum size is 721
words when the tag set
includes the PLC status.)
Maximum size of 1 tag ≤ 20
words
(The maximum size is 19
words when the tag set
includes the PLC status.)
Number of tags per tag set ≤ 8
(7 tags/tag set when the tag set includes the PLC status)
Note Input and output variables cannot be combined.
Number of registrable tags ≤
256 Number of registrable tags ≤
32 Number of registrable tag
sets ≤ 256 Number of registrable tag
sets ≤ 32
7
Communications Services Overview Section 1-4
Note In this example, a connection is established with the originator’s tag list con-
taining tags a to g (inputs), which are grouped in a tag set called SP1_IN, and
the target’s tag list containing tags i and ii (outputs), which are grouped in a
tag set called SP1_OUT.
2) Message Communications (Unconnected Message Service)
User-specified CIP commands can be sent to devices on the EtherNet/IP net-
work. CIP commands, such as those for reading and writing data, can be sent
and their responses received by executing the CMND instruction from the CS/
CJ-series CPU Unit’s user program (without using a connection).
CIP messages (CIP commands and responses) can also be transferred to
another CIP-based network via the EtherNet/IP Unit or built-in EtherNet/IP
port using the CIP routing function for message communications.
In the CS/CJ Series, CIP routing is possible only through two EtherNet/IP
Units or built-in EtherNet/IP port.
Tag Set (Inputs)
Tag g
:
Tag c
Tag b
Tag a
PLC Status
EtherNet/IP
Connection information
• Target IP address
• Target tag set
• Originator tag set
• Packet interval (RPI)
Tag set name: S
P1_IN
Originator
device Target
device
Data flow
Connection
Tag Set (Outputs)
Tag ii
Tag i
PLC Status
Tag set name: S
P1_IN
Ethernet
(EtherNet/IP)
CMND
CIP command
Response
EtherNet/IP Unit
CS/CJ-series CPU Unit
8
Communications Services Overview Section 1-4
FINS
Communications
Service
FINS commands can be sent to or received from other PLCs or computers on
the same Ethernet network by executing SEND(090), RECV(098), or
CMND(490) instructions in the ladder diagram program. This enables various
control operations such as the reading and writing of I/O memory between
PLCs, mode changes, and file memory operations.
Note There are no particular restrictions when sending FINS messages to OMRON
Ethernet Units (CS1W-ETN21 or CJ1W-ETN21) in an Ethernet network.
Various control operations (such as the reading and writing of I/O memory
between PLCs, mode changes, and file memory operations) can be executed
from the host computer by sending the corresponding FINS command with a
UDP/IP or TCP/IP header attached.
For example, it is possible to connect online via Ethernet from FINS communi-
cations applications such as the CX-Programmer, and to perform remote pro-
gramming and monitoring. (See note.)
Note Use CX-Programmer version 4.0 to use TCP/IP. For lower versions of CX-Pro-
grammer, FinsGateway Version 2003 or higher is required to use TCP/IP.
EtherNet/IP
Ethernet
(EtherNet/IP), etc.
EtherNet/IP Unit
EtherNet/IP Unit
CS/CJ-series CPU Unit
Ethernet (EtherNet/IP)
EtherNet/IP Unit Ethernet Unit EtherNet/IP Uni
User program
IP UDP or TCP FINS IP FINS
CS/CJ-series CPU
Unit
UDP or TCP
SEND(090),
RECV(098), or
CMND(490)
instruction
9
Communications Services Overview Section 1-4
The FINS gateway function enables access to PLCs on not only the same
Ethernet network but on various other networks, including SYSMAC LINK and
Controller Link.
Ethernet (EtherNet/IP)
IP FINS
EtherNet/IP Unit
UDP or TCP
CS/CJ-series CPU
Unit
10
Network Configurator Overview Section 1-5
1-5 Network Configurator Overview
1-5-1 Overview
The Network Configurator Ver. 3.0 or higher is a software package designed
for building, setting, and controlling a multi-vendor EtherNet/IP Network using
OMRON's EtherNet/IP. It is included in CX-One version 4.0 or higher. The
Network Configurator provides the following functions for building, setting, and
controlling EtherNet/IP.
Network Control The Network configuration can be created and edited regardless of whether
the Network Configurator is online or offline. The Network configuration can
be read from a file or the network.
Hardware (EDS File)
Control EDS files used by the Network Configurator can be installed and deleted.
1-5-2 Network Configurator Requirements
Item Specification
Operating environment Refer to the CX-One Setup Manual (W463).
CXONE-AL@@C-V4/CXONE-AL@@D-V4
Network
connection
method
CS1/CJ1 CJ2
Serial interface CPU Unit’s Peripheral or RS-232C port CPU Unit’s USB or RS-232C port
Ethernet interface EtherNet/IP Unit’s Ethernet port CPU Unit’s Ethernet port
EtherNet/IP Unit’s Ethernet port
Location on Network A single node address is used (only when directly connected to EtherNet/IP).
Number of Units that can be
connected to Network A single Network Configurator per network (More than one Configurator cannot be
used in the same system.)
Main func-
tions Network control
functions • The network configuration can be created and edited regardless of whether the Net-
work Configurator is online or offline.
• The network configuration can be read from a file or the network.
Hardware control
functions The EDS files used by the Network Configurator can be installed and deleted.
Supported file formats Configurator network configuration files (*.nvf)
Configuration files (*.ncf) created using the Network Configurator for EtherNet/IP
(version 2) can be imported by selecting External Data - Import from the File
Menu.
11
Network Configurator Overview Section 1-5
1-5-3 Precautions When Using the Network Configurator
Only an OMRON EtherNet/IP Unit can be set as the originator for a connec-
tion using the Network Configurator.
• The Network Configurator can be connected to the EtherNet/IP network
through the following ports:
• CS1/CJ1-series CPU Unit’s serial port (peripheral or RS-232C) or
Ethernet port on EtherNet/IP Unit
• CJ2-series CPU Unit’s serial port (USB or RS-232C), Ethernet port on
EtherNet/IP Unit or built-in EtherNet/IP port
• The Network Configurator can be connected directly to the EtherNet/IP
network from the computer’s Ethernet port. When connecting directly to
the EtherNet/IP network, an Ethernet port must be set up in the computer
in advance. In this case, the Network Configurator will be connected to
the EtherNet/IP network as a single node. If there isn’t an unused node
address available, the Network Configurator can’t be connected directly to
the EtherNet/IP network.
12
Network Configurator Overview Section 1-5
13
SECTION 2
Unit Specifications
This section provides the specifications of EtherNet/IP Units and introduces recommended network configuration devices.
2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications . . . . . . . . . . . 14
2-1-1 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-1-2 Unit Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2-1-3 Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2-1-4 Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2-1-5 Software Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2-2 Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-2-1 Nomenclature and Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-2-2 Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2-3 Selecting the Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2-3-1 Recommended Network Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2-3-2 Network Devices Manufactured by OMRON . . . . . . . . . . . . . . . . . 28
2-3-3 Switching Hub Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2-3-4 Switching Hub Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2-3-5 Precautions When Selecting a Switching Hub . . . . . . . . . . . . . . . . . 29
14
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port
Specifications
2-1-1 General Specifications
The general specifications conform to those of the CS-series and CJ-series
PLCs.
2-1-2 Unit Specifications
CS-series EtherNet/IP Units
Note If tag data links are being used, use 100Base-TX. Otherwise, 10Base-T can
be used, but this is not recommended.
Item Specifications
Model number CS1W-EIP21
Type 100Base-TX (See note.)
Applicable PLCs CS-series PLCs
Unit classification CS-series CPU Bus Unit
Mounting location CPU Rack or Expansion Rack
Number of Units that can be
mounted 8 max. (including Expansion Racks)
CPU Unit
words used Allocated CIO Area
words (CPU Bus Unit
words)
25 words/Unit (one unit number’s words)
These words contain control bits and flags, the target node PLC’s operating and
error information, Unit status, communications status, registered/normal target
node information, and FINS/TCP connection status.
Allocated DM Area
words (CPU Bus Unit
words)
100 words/Unit (one unit number’s words)
These words contain the IP address display/setting area
User-set area Any usable data area words
Target node PLC’s operating and error information, and registered/normal target
node information
CPU Bus Unit System
Setup Not used.
Non-volatile memory within Ether-
Net/IP Unit (See note.) The following settings are stored in the EtherNet/IP Unit’s non-volatile memory.
Note Unlike the regular Ethernet Units, the CPU Bus Unit Setup Area in the CPU
Unit is not used for these settings.
1. Unit setup (communications settings for the EtherNet/IP Unit, such as the IP ad-
dress, DNS server settings, host name, baud rate, FINS/UDP settings, and FINS/
TCP settings)
2. Tag data link settings (device parameters)
Transfer
specifica-
tions
Media access method CSMA/CD
Modulation method Baseband
Transmission paths Star form
Baud rate 100 Mbit/s (100Base-TX)
Transmission media Shielded twisted-pair (STP) cable
Categories: 100 Ω at 5, 5e
Transmission distance 100 m (distance between hub and node)
Number of cascade
connections There is no limitation when a switching hub is used.
Current consumption (Unit) 410 mA max. at 5 V DC
Weight 171 g max.
Dimensions 35 × 130 × 101 mm (W × H × D)
Other general specifications Other specifications conform to the general specifications of the CS-series
15
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
CJ-series EtherNet/IP Unit
Note If tag data links are being used, use 100Base-TX. Otherwise, 10Base-T can
be used, but this is not recommended.
Item Specifications
Model number CJ1W-EIP21
Type 100Base-TX (See note.)
Applicable PLCs CJ-series PLCs
Unit classification CJ-series CPU Bus Unit
Mounting location CPU Rack or Expansion Rack
Number of Units that can be
mounted 8 max. (including Expansion Racks)
Note Up to seven EtherNet/IP Units can be connected to a CJ2H-CPU@@-EIP CPU
Unit. Up to two EtherNet/IP Units can be connected to a CJ2M CPU Unit.
CPU Unit
words used Allocated CIO Area
words (CPU Bus
Unit words)
25 words/Unit (one unit number’s words)
These words contain control bits and flags, the target node PLC’s operating and error
information, Unit status, communications status, registered/normal target node infor-
mation, and FINS/TCP connection status.
Allocated DM Area
words (CPU Bus
Unit words)
100 words/Unit (one unit number’s words)
These words contain the IP address display/setting area.
User-set area Any usable data area words
Target node PLC’s operating and error information, and registered/normal target
node information
CPU Bus Unit Sys-
tem Setup Not used.
Non-volatile memory within Ether-
Net/IP Unit (See note.) The following settings are stored in the EtherNet/IP Unit’s non-volatile memory.
Note Unlike the regular Ethernet Units, the CPU Bus Unit Setup Area in the CPU
Unit is not used for these settings.
1. Unit Setup (communications settings for the EtherNet/IP Unit, such as the IP ad-
dress, DNS server settings, host name, baud rate, FINS/UDP settings, and FINS/
TCP settings)
2. Tag data link settings (device parameters)
Transfer
specifica-
tions
Media access
method CSMA/CD
Modulation method Baseband
Transmission paths Star form
Baud rate 100 Mbit/s (100Base-TX)
Transmission media Shielded twisted-pair (STP) cable
Categories: 100 Ω at 5, 5e
Transmission dis-
tance 100 m (distance between hub and node)
Number of cascade
connections There is no limitation when a switching hub is used.
Current consumption (Unit) 410 mA max. at 5 V DC
Weight 94 g max.
Dimensions 31 × 90 × 65 mm (W × H × D)
Other general specifications Other specifications conform to the general specifications of the CJ-series.
16
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
CJ2 CPU Built-in EtherNet/IP Port
Note If tag data links are being used, use 100Base-TX. Otherwise, 10Base-T can
be used, but this is not recommended.
Item Specifications
Model number CJ2H-CPU@@-EIP CJ2M-CPU3@
Type 100Base-TX (See note.)
Unit classification CJ2 CPU Unit built-in port (CJ2 CPU Bus Unit)
CPU Unit
words used Allocated CIO Area
words (CPU Bus
Unit words)
25 words/Unit (one unit number’s words)
These words contain control bits and flags, the target node PLC’s operating and error
information, Unit status, communications status, registered/normal target node infor-
mation, and FINS/TCP connection status.
Allocated DM Area
words (CPU Bus
Unit words)
100 words/Unit (one unit number’s words)
These words contain the IP address display/setting area.
User-set area Any usable data area words
Target node PLC’s operating and error information, and registered/normal target
node information
CPU Bus Unit Sys-
tem Setup Not used.
Non-volatile memory for the CJ2
built-in EtherNet/IP port The following settings are stored in the non-volatile memory for the built-in EtherNet/
IP port.
Note Unlike the regular Ethernet Units, the CPU Bus Unit Setup Area in the CPU
Unit is not used for these settings.
1. Unit Setup (communications settings for the built-in EtherNet/IP port, such as the
IP address, DNS server settings, host name, baud rate, FINS/UDP settings, and
FINS/TCP settings)
2. Tag data link settings (device parameters)
Transfer
specifica-
tions
Media access
method CSMA/CD
Modulation method Baseband
Transmission paths Star form
Baud rate 100 Mbit/s (100Base-TX)
Transmission media Shielded twisted-pair (STP) cable
Categories: 100 Ω at 5, 5e
Transmission dis-
tance 100 m (distance between hub and node)
Number of cascade
connections There is no limitation when a switching hub is used.
Current consumption (Unit) For CJ2 CPU Units, refer to the CJ2 CPU Hardware Operation Manual (W472).
Weight
Dimensions
Other general specifications Other specifications conform to the general specifications of the CJ2 or built-in Ether-
Net/IP port CJ2 CPU Unit.
17
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
2-1-3 Communications Specifications
Item CS1/CJ1 CJ2H CJ2M
CIP
service Tag data
links
(Cyclic
communi-
cations)
Number of connections 256 32
Packet interval (refresh
cycle) 0.5 to 10,000 ms (in 0.5-ms units)
Can be set independently for each connection.
(Data is refreshed over the network at the preset
interval and does not depend on the number of
nodes.)
1 to 10,000 ms (in 0.5-
ms units)
Can be set indepen-
dently for each connec-
tion.
(Data is refreshed over
the network at the pre-
set interval and does
not depend on the
number of nodes.)
Allowed communica-
tions bandwidth per
Unit
6000 pps (See note 1.)
Note Including the heartbeat.
3000 pps (See note 1.)
Note Including the
heartbeat.
Number of tags that
can be registered 256 32
Tag types CIO Area, DM Area, EM Area, Holding Area, Work Area, and network
symbols (See note 8.)
Number of tags per
connection (= 1 tag
set)
8 (7 tags when the tag set contains the PLC status)
Maximum link data size
per node 184,832 words 640 words
Maximum data size per
connection 252 words or 722 words (See note 2.)
Note Data synchronicity is maintained within
each connection.
20 words
Note Data synchronic-
ity is maintained
within each con-
nection.
Number of registrable
tag sets 256
(1 connection = 1 tag set) 32
(1 connection = 1 tag
set)
Maximum size of 1 tag
set 722 words
(The PLC status uses 1 word when the tag set
contains the PLC status.)
20 words
(The PLC status uses 1
word when the tag set
contains the PLC sta-
tus.)
Maximum number of
tags that can be
refreshed per CPU Unit
cycle (See note 3.)
Output/Transmission
(CPU → EtherNet/IP):
19
Input/Reception
(EtherNet/IP → CPU):
20 (See note 4.)
Output/Transmission
(CPU → EtherNet/IP):
256
Input/Reception
(EtherNet/IP → CPU):
256
Output/Transmission
(CPU → EtherNet/IP):
32
Input/Reception
(EtherNet/IP → CPU):
32
Data that can be
refreshed per CPU Unit
cycle (See note 3.)
Output/Transmission
(CPU → EtherNet/IP):
7,405 words
Input/Reception
(EtherNet/IP → CPU):
7,405 words
Output/Transmission
(CPU → EtherNet/IP):
6,432 words
Input/Reception
(EtherNet/IP → CPU):
6,432 words
Output/Transmission
(CPU → EtherNet/IP):
640 words
Input/Reception
(EtherNet/IP → CPU):
640 words
Changing tag data link
parameters during
operation
Supported (See note 5.)
Multicast packet filter
function (See note 6.) Supported
18
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
Note (1) In this case, pps means “packets per second” and indicates the number
of packets that can be processed in one second.
(2) To use 505 to 1,444 bytes as the data size, the system must support the
Large Forward Open standard (an optional CIP specification). The SYS-
MAC CS/CJ-series Units support this standard, but before connecting to
nodes of other companies, confirm that those devices also support it.
(3) If the maximum data size is exceeded, the data refreshing with the CPU
Unit will extend over two or more cycles.
(4) If status layout is selected in the user settings, the maximum number of
tags that can be received is 19 tags.
(5) If parameters are changed in the EtherNet/IP Unit, however, the Ether-
Net/IP Unit will be restarted. When other nodes are communicating with
the affected node, the communications will temporarily time out and au-
tomatically recover later.
(6) Because the EtherNet/IP Unit is equipped with an IGMP client (version
2), unnecessary multicast packets can be filtered by using a switching
hub that supports IGMP snooping.
(7) The EtherNet/IP Unit uses the TCP/UDP port numbers shown in the fol-
lowing table.
(8) Network symbols can be used only with a CJ2H-CPU6@-EIP or CJ2M-
CPU3@ CPU Unit.
CIP
service Explicit
messaging Class 3 (connected) Number of connections: 128
UCMM (unconnected) Number of clients that can communicate at one
time:
32 max.
Number of servers that can communicate at one
time:
32 max.
Number of clients that
can communicate at
one time:
16 max.
Number of servers that
can communicate at
one time:
16 max.
CIP routing CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
CJ2M-CPU3@
FINS service
(See note 7.) FINS/UDP Supported
FINS/TCP 16 connections max.
SNMP Agent SNMPv1, SNMPv2c
MIB MIB-II
EtherNet/IP conformance test Conforms to A5
Ethernet interface 10BASE-T or 100BASE-TX
Auto Negotiation or fixed settings
Item CS1/CJ1 CJ2H CJ2M
Service Protocol Port number Remarks
Tag data links UDP 2222 Fixed value
Class 3, UCMM TCP/UDP 44818
DNS UDP 53
FINS/UDP service UDP 9600 Port numbers in the Unit
Setup can be changed with
the CX-Programmer.
FINS/TCP service TCP 9600
FTP TCP 20, 21
SNTP UDP 123
SNMP UDP 161
SNMP trap UDP 162
19
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
2-1-4 Dimensions
CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
101 mm35 mm
130 mm
NODE
NO.
1
×16
0
0
×16
1
UNIT
NO.
100BASE-TX
10BASE-T
0
EIP21
MS
NS
COMM
100M
10M
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
65 mm
31 mm
UNIT
No.
EIP21
90 mm
NODE
No.
x16
0
x16
1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
MS
NS
100M
10M
COMM
100BASE-TX
10BASE-T
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
90 mm
2.7 mm
2.7 mm 79.8 mm
66.2 mm
65 mm
74.5 mm
20
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1
CJ2M-CPU3@
2-1-5 Software Configuration
76.16 mm
62 mm
2.7 mm
2.7 mm
90 mm
84.5 mm
75 mm
FINS
encapsulization
FINS Cyclic
Interface with CPU Unit
Memory Card/
EM file memory
FTP Automatic
clock adjustment
FINSFINS
UDP
IP ARP IGMP
LAN controller driver
LAN controller
Encapsulation
ICMP
TCP
FINS Service
(FINS/UDP and FINS/TCP) CIP
Tag data link function Explicit messaging
21
Nomenclature and Functions Section 2-2
2-2 Nomenclature and Functions
2-2-1 Nomenclature and Functions
CS1W-EIP21
CJ1W-EIP21
LED Indicators
Unit number
setting switch
Label showing
IP address
Node address
setting switches
Ethernet
connector
Backplane
Connector
NODE
NO.
1
×16
0
0
×16
1
UNIT
NO.
100BASE-TX
10BASE-T
0
EIP21
MS
NS
COMM
100M
10M
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
Unit number
setting switch
Node address
setting switches
LED Indicators
Label showing
IP address
UNIT
No.
EIP21
NODE
No.
x16
0
x16
1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
MS
NS
100M
10M
COMM
100BASE-TX
10BASE-T
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
Ethernet
connector
22
Nomenclature and Functions Section 2-2
Built-in EtherNet/IP Port in CJ2H-CPU@@-EIP
Built-in EtherNet/IP Port in CJ2M-CPU3@
Ethernet Address Notation A specific Ethernet address is allocated to all devices connected to the Ether-
net network. The EtherNet/IP Unit’s address is listed in 12-digit hexadecimal
on the right side of the Unit.
Note (1) The Ethernet Address can also be checked with the CONTROLLER
DATA READ command. For details, refer to Appendix E FINS Commands
Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports.
(2) An IP address label is included with the EtherNet/IP Unit, so the user can
record the user-set IP address and subnet mask on the label, and affix
the label to the front of the Unit. When this label is affixed to the front of
the Unit, it is easy to confirm the Unit’s IP address and subnet mask.
Unit number
setting switch
Node address
setting switches
LED Indicators
Label showing
IP address
Ethernet
connector
Unit number
setting switch
Node address
setting switches
LED Indicators
Label showing
IP address
Ethernet
connector
ETHERNET/IP UNIT
CS1W-EIP21
OMRON Corporation MADE IN JAPAN
Lot No.
@@@@@@@@@@@@
Ethernet Address
Ethernet address
(
12 di
g
its
)
23
Nomenclature and Functions Section 2-2
Indicators A EtherNet/IP Units or built-in EtherNet/IP port is equipped with the following
indicators that indicate the operating status of the node itself and the overall
network.
CS1W-EIP21
CJ1W-EIP21, CJ2H-CPU@@-EIP, and CJ2M-CPU3@
Status Indicators: MS, NS,
COMM, 100M, and 10M The MS (Module Status) indicator indicates the status of the node itself and
the NS (Network Status) indicator indicates the status of the network.
The COMM, 100M, and 10M indicators indicate the status of Ethernet com-
munications.
The MS and NS indicators can be green or red. The COMM, 100M, and 10M
indicators are yellow. These indicators can be lit, flashing, or not lit. The fol-
lowing table shows the meaning of these indicator conditions.
Refer to SECTION 14 Troubleshooting and Error Processing for details on
using these indicators for troubleshooting.
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
Example label
UNIT
No.
EIP21
NODE
No.
x16
0
x16
1
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
0
1
2
3
4
5
6
7
8
9
A
B
C
D
E
F
MS
NS
100M
10M
COMM
100BASE-TX
10BASE-T
IP ADDRESS
SUBNET MASK
192.168.250.1
255.255.255.0
Affix the label on the front of the
EtherNet/IP Unit, between the
node address switches and the
Ethernet connector.
EIP21
MS
NS
COMM
100M
10M
EIP
21
MS
NS
100M
10M
COMM
24
Nomenclature and Functions Section 2-2
Seven-segment Display When the power is turned ON (or the Unit is restarted), all of the segments will
flash twice, the IP address set in the EtherNet/IP Unit or built-in EtherNet/IP
port will be displayed on the 7-segment display just once, from right to left.
Afterwards, the rightmost 8 bits of the IP address is displayed in hexadecimal
during normal operation.
Example 1: Displaying IP Address 192.168.250.10
Indicator Name Color LED status Indicated operating status
MS Module Status Red Lit Fatal error
Flashing Recoverable error
Green Lit Normal
--- Not lit Power supply OFF
NS Network Status Red Lit Fatal error
Flashing Recoverable error
Green Lit Tag data link and message connections established
Flashing Tag data link and message connections not established
--- Not lit Offline or power supply OFF
COMM Communication Yellow Lit Transferring data
Not lit Not transferring data
100M 100 Mbps Yellow Lit 100BASE-TX link established
Not lit 100BASE-TX link not established
10M 10 Mbps Yellow Lit 10BASE-TX link established
Not lit 10BASE-TX link not established
The IP address is displayed in decimal, flowing from right to left.
If the Unit is operating normally, the last digit of the
Unit's IP address is displayed in hexadecimal.
Flashing: The tag data link is stopped.
Lit: The tag data link is operating.
25
Nomenclature and Functions Section 2-2
If an error occurs, the error code will be displayed alternately with the right-
most byte of the affected device’s IP address. For details on error codes, refer
to SECTION 14 Troubleshooting and Error Processing.
Displaying Multiple Error Sources
• A d6 error (failed to establish connection) occurred with IP address
192.168.250.8.
• A d6 error (failed to establish connection) occurred with IP address
192.168.250.9.
• A d5 error (verification error, target nonexistent) occurred with IP address
192.168.250.64.
• A C6 error (multiple switches ON) and EA error (EtherNet/IP expansion
setting error) occurred at the local EtherNet/IP Unit or built-in EtherNet/IP
port, IP address 192.168.250.10.
• There is no particular priority to the order in which the errors are dis-
played. All of the errors are displayed repeatedly in order.
The error code is displayed and then the last digit of the target node's
IP address is displayed in hexadecimal.
Displays errors that occurred
within the Unit.
The last digit of the Unit's IP address
is displayed in hexadecimal.
26
Nomenclature and Functions Section 2-2
Right and Left Dot LEDs
If an error occurred in two or more devices with the same rightmost byte in
their IP addresses, the Right Dot LED will be lit while the devices’ error is
being displayed.
Example: Displaying the Following Errors
• A d6 error (failed to establish connection) occurred with IP address
10.0.1.8.
• A d6 error (failed to establish connection) occurred with IP address
10.0.2.8.
2-2-2 Switch Settings
Unit Number Setting
Switch The Unit Number Setting Switch sets the unit number of the EtherNet/IP Unit
or built-in EtherNet/IP port as a CPU Bus Unit. The unit number determines
which data area words are allocated to the Unit to contain data such as con-
trol bits, flags, status information, and connection information.
Note The unit number is factory-set to 0.
The unit number can be set to any number in the setting range (0 to F), as
long as the same number is not set on another CPU Bus Unit in the same
PLC.
Note (1) Use a small screwdriver to make the setting, and be sure not to damage
the rotary switch.
(2) Always turn OFF the PLC’s power supply before setting the unit number.
(3) The unit number is factory-set to 0.
(4) If the same unit number is set on more than one CPU Bus Unit mounted
in a PLC, a unit number duplication error will occur in the PLC and the
EtherNet/IP Unit or built-in EtherNet/IP port will not be able to start oper-
ating.
Setting method Setting range
One-digit hexadecimal 0 to F
F
E
D
C
B
A
9
8
7
6
5
4
3
2
1
0
27
Nomenclature and Functions Section 2-2
Node Address Setting
Switch The Node Address Setting Switch sets the node address of the EtherNet/IP
Unit or built-in EtherNet/IP port.
Note The node address is factory-set to 01. With the default settings, the values set
on these switches become the last two digits of the local IP address of the Ether-
Net/IP Unit or built-in EtherNet/IP port.
Default IP address = 192.168.250.node address
With the factory-default node address setting of 01, the default IP address is
192.168.250.1.
The node address can be set to any number in the setting range (01 to FE),
as long as the same address is not set on another node in the network.
Note If the node address setting is changed during operation, the MS Indicator will
flash red.
Setting method Setting range
Two-digit hexadecimal 01 to FE
X161X160
F
E
D
C
B
A
9
8
7
6
5
4
3
2
1
0
0
F
E
D
C
B
A
9
8
7
6
5
4
3
2
1
28
Selecting the Network Devices Section 2-3
2-3 Selecting the Network Devices
2-3-1 Recommended Network Devices
The following table shows the devices recommended for use with the Ether-
Net/IP.
Note (1) Always use a switching hub when using tag data links in the network.
(2) If a repeater hub is used for EtherNet/IP tag data links (cyclic communi-
cations), the network’s communications load will increase, data collisions
will occur frequently, and stable communications will be impossible.
2-3-2 Network Devices Manufactured by OMRON
The following network devices are manufactured by OMRON for EtherNet/IP
networks.
2-3-3 Switching Hub Types
Unmanaged Layer 2 (L2)
Switching Hubs These switching hubs use the Ethernet MAC address to switch ports. Ordi-
nary switching hubs have this function. Switching hub functions and settings
cannot be changed.
Managed Layer 2 (L2)
Switching Hubs These switching hubs use the Ethernet address to switch ports. Switching hub
functions and settings can be changed using special software tools for switch-
ing hubs running on a network node. Analytical data can also be collected.
These switching hubs provide more-advanced functions that unmanaged
layer 2 switching hubs.
Part Maker Model number Inquires
Switching
Hub Cisco Systems, Inc. Consult the manufacturer. Cisco Systems, Inc. Main Corpo-
rate HQ
Contec USA, Inc. Consult the manufacturer. CONTEC USA Inc.
Phoenix Contact Consult the manufacturer. Phoenix Contact USA Customer
Service
Twisted-pair
cable 100BASE-TX
Fujikura F-LINK-E 0.5mm × 4P Fujikura America, Inc.
EtherNet/IP compliant cable ---
Connectors
(Modular
plug)
STP Plug
Panduit Corporation MPS588 Panduit Corporation US Headquar-
ters
Boots Tsuko Company MK boot (IV) LB Tsuko Company Japan Headquar-
ters
Name Model Function Number of
ports Error detection
output
Switching Hub W4S1-03B Packet priority control (QoS):
EtherNet/IP control data priority
Failure detection: Broadcast
storm, LSI error detection, 10/
100Base-TX, Auto-Negotiation
3None
W4S1-05B 5 None
W4S1-05C 5 Provided.
29
Selecting the Network Devices Section 2-3
2-3-4 Switching Hub Functions
This section describes the switching hub functions that are important when
using an EtherNet/IP network. When using an EtherNet/IP Unit, set the follow-
ing two functions.
• Multicast filtering
• QoS (Quality of Service) for TCP/UDP port numbers (L4)
Multicast Filtering Multicast filtering transfers multicast packets to the specific nodes only. This
function is implemented in the switching hub as IGMP Snooping or GMRP.
“Specific nodes” are nodes equipped with an IGMP client that have made
transfer requests to the switching hub. (OMRON EtherNet/IP Units are
equipped with an IGMP client.)
When the hub does not use multicast filtering, multicast packets are sent to all
nodes, just like broadcast packets, which increases the traffic in the network.
Settings must be made in the switching hub to enable this function.
There must be enough multicast filters for the network being used.
QoS (Quality of Service)
Function for TCP/UDP
Port Numbers (L4)
This function controls the priority of packet transmissions so that packets can
be sent with higher priority to a particular IP address or TCP (UDP) port. The
TCP and UDP protocols are called transport layer protocols, leading to the
name L4 (layer 4) QoS function.
When tag data links and message communications are executed on the same
network, tag data links can be sent at higher priority to prevent problems such
as transmission delays due to message communications traffic and packet
losses due to buffer overflow. Settings must be made in the switching hub to
enable this function and give higher priority to tag data link packets.
Support for the above two functions is as follows for the different types of
switching hubs.
Note If the Network Configurator is used to set the connection type in the connec-
tion settings to a multicast connection, multicast packets will be used. If the
connection type is set to a point-to-point connection, multicast packets will not
be used.
2-3-5 Precautions When Selecting a Switching Hub
The functions supported by the switching hub may affect tag data link trans-
mission delays and the configuration. In addition, if the switching hub supports
advanced functions, special settings are required for those functions.
Hub Multicast
filtering L4 QoS Remarks
Unmanaged L2 switching hub None None ---
Managed L2 switching hub Provided. Provided. Both functions must
be set with a special
software tool.
OMRON W4S1-series Switching
Hubs None Provided. L4 QoS is set using
a switch. No soft-
ware tool is neces-
sary.
30
Selecting the Network Devices Section 2-3
When selecting a switching hub, it is necessary to consider whether the
switching hub will be selected based on the kind and amount of communica-
tions that will be performed in the network or the kind of switching hub that you
want to use. Refer to the following precautions when selecting a switching
hub.
Refer to 10-2 Adjusting the Communications Load to estimate the communi-
cations load for tag data links.
Selecting the Switching Hub Based on the Types of Network Communications
Executing Tag Data Links
Only We recommend using an L2 switching hub without multicast filtering or an L2
switching hub with multicast filtering.
Using an L2 switching hub with multicast filtering prevents increased traffic
due to unnecessary multicast packets, so the tag data links can operate at
higher speed. If either of the following conditions exists, the amount traffic will
be the same for both kinds of L2 switching hubs (with or without multicast fil-
tering).
• The tag data links are set to share the same data with all nodes in the net-
work. (The multicast packets are transferred to all nodes in the network,
just like a broadcast.)
• The tag data link settings are all one-to-one (unicast) and multicast pack-
ets cannot be used.
If multicast filters are being used, settings must be made in the switching hub.
There must be enough multicast filters for all of the networks being used.
Executing Tag Data Links
and Message
Communications
We recommend using an L2 switching hub with multicast filtering and L4 QoS.
By setting tag data links for higher-priority transmission, it is possible to pre-
vent problems such as transmission delays due to message communications
traffic and packet losses due to buffer overflow. Settings must be made in the
switching hub to enable this function and give higher priority to tag data link
packets.
Special settings must be made in the switching hub when using the multicast
filtering function and L4 QoS function.
Selecting the Switching Hub Based on the Hub’s Supported Functions
L2 Switching Hub without
Multicast Filtering We recommend this kind of switching hub when only tag data links are exe-
cuted and any of the following conditions is met.
• The tag data links are set to share the same data with all nodes in the net-
work. (The multicast packets are transferred to all nodes in the network,
just like a broadcast.)
• The tag data link settings are all one-to-one (unicast) and multicast pack-
ets cannot be used.
• There is little traffic in the tag data links.
No special settings are required for an L2 switching hub without multicast fil-
tering.
L2 Switching Hub with
Multicast Filtering We recommend this kind of switching hub when only tag data links are exe-
cuted and the following condition is met.
• There are many 1:N links (where N represents some number of nodes in
the network) in the tag data link settings, i.e., there are many multicast
packets used, or there is heavy traffic in the tag data links.
Special settings are required for an L2 switching hub with multicast filtering.
There must be enough multicast filters for the network being used.
31
Selecting the Network Devices Section 2-3
L3 Switching Hub with
Multicast Filtering and L4
QoS Functions
We recommend this kind of switching hub when both tag data links and mes-
sage communications are executed.
By setting tag data links for higher-priority transmission, it is possible to pre-
vent problems such as transmission delays due to message communications
traffic and packet losses due to buffer overflow. Settings must be made in the
switching hub to enable this function and give higher priority to tag data link
packets.
Special settings must be made in the switching hub when using the multicast
filtering function and L4 QoS function. There must be enough multicast filters
for the network being used.
Note (1) Ask the switching hub manufacturer for setting procedures for the switch-
ing hub.
(2) Install the switching hub so that its environmental resistance capabilities
are not exceeded. Ask the switching hub manufacturer for information on
the environmental resistance of the switch hub.
32
Selecting the Network Devices Section 2-3
33
SECTION 3
Installation and Initial Setup
This section explains how to install and make the initial settings required for operation of the EtherNet/IP Unit or built-in
EtherNet/IP port.
3-1 Overview of Initial Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-1-1 Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-2 Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-2-1 CS-series EtherNet/IP Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3-2-2 CJ-series EtherNet/IP Units and CJ2 Built-in EtherNet/IP Port. . . . 37
3-3 Mounting to a PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-3-1 Mounting to a CS-series PLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-3-2 Mounting to a CJ-series PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-3-3 Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-3-4 Handling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3-4 Network Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-4-1 Basic Installation Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-4-2 Recommended Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-4-3 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-4-4 Using Contact Outputs (Common to All Units) . . . . . . . . . . . . . . . . 43
3-5 Connecting to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3-5-1 Ethernet Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3-5-2 Connecting the Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3-6 Creating I/O Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3-6-1 I/O Table Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3-6-2 Connecting Programming Devices to the PLC. . . . . . . . . . . . . . . . . 46
3-6-3 Procedure for Creating I/O Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3-7 Setting the Local IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3-8 TCP/IP and Link Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3-8-1 Setting Procedure with the CX-Programmer . . . . . . . . . . . . . . . . . . 52
3-8-2 Making TCP/IP Settings with the Network Configurator . . . . . . . . 55
3-9 Tag Data Link Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-9-1 Network Configurator Setting Procedure . . . . . . . . . . . . . . . . . . . . . 57
3-10 Other Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3-11 Communications Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3-11-1 PING Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3-11-2 EtherNet/IP Unit or Built-in EtherNet/IP Port Operation. . . . . . . . . 65
3-11-3 Host Computer Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
34
Overview of Initial Setup Procedures Section 3-1
3-1 Overview of Initial Setup Procedures
3-1-1 Procedures
Initial Settings
1,2,3... 1. Set the unit number and node address with the switches on the front of the
EtherNet/IP Unit or, for the built-in EtherNet/IP port, on the front of the CPU
Unit.
Refer to 3-2 Switch Settings.
2. Mount the Unit in the CPU Rack.
A maximum of seven EtherNet/IP Units can be connected to a CJ2H-
CPU@@-EIP CPU Unit (making eight EtherNet/IP ports including the built-
in EtherNet/IP port).
A maximum of two EtherNet/IP Units can be connected to a CJ2M-CPU3@
CPU Unit.
Refer to 3-3 Mounting to a PLC.
3. Wire the Ethernet network with twisted-pair cable.
Refer to 3-4 Network Installation and 3-5 Connecting to the Network.
4. Prepare a computer with Support Software installed on it and a serial cable
or an Ethernet cable (twisted-pair cable) to connect to the PLC. These are
required to perform network settings using the Support Software (e.g., Net-
work Configurator, CX-Programmer, and CX-Integrator).
5. Connect the PLC to the computer and create the I/O tables using the CX-
Programmer. I/O tables do not need to be created for the built-in EtherNet/
IP port on the CJ2H-CPU@@-EIP or CJ2M-CPU3@.
Refer to 3-6 Creating I/O Tables.
6. Set the IP address of the EtherNet/IP Unit or built-in EtherNet/IP port using
one of the following methods.
a) Using the Unit without setting the IP address:
• The default IP address is 192.168.250.Node_address.
b) Setting a particular IP address:
• If you want to store the setting in the CPU Unit, set it in the EtherNet/
IP Unit’s allocated DM area within the CPU Unit.
• If you want to store the setting in the Unit, set the IP address in the Edit
Parameters Dialog Box of the I/O Table Dialog Box from the CX-Pro-
grammer, and transfer the setting to the Unit.
Refer to 3-7 Setting the Local IP Address and 3-8 TCP/IP and Link
Settings.
7. When necessary, set the following items in the Edit Parameters Dialog Box
and transfer them: TCP/IP, Ethernet, FINS/UDP, FINS/TCP, FTP, Auto Ad-
just Time, Status Area, SNMP, and SNMP Trap
Refer to 3-10 Other Parameters.
8. When necessary, set the routing tables.
If the FINS communications service is being used and multiple network
Communications Units are mounted in the PLC, set the routing tables from
the CX-Integrator, and transfer the table.
Refer to the CX-Integrator Operation Manual (Cat. No. W464) for the set-
ting procedure.
35
Overview of Initial Setup Procedures Section 3-1
9. Test communications.
Send a PING command to the EtherNet/IP Unit or built-in EtherNet/IP port.
Refer to 3-11 Communications Test.
Settings Required for Tag Data Link Service (Cyclic Communications)
1. Using the EtherNet/IP Datalink Tool in the Network Configurator to Set the Parameters
With this method, there is no flexibility in the settings, but you can easily set
the data link parameters using only memory addresses, and the settings will
conform to Controller Link data link parameters. Refer to 3-9 Tag Data Link
Parameters or SECTION 6 Tag Data Link Functions.
2. Using the Tag Data Link Setting Function in the Network Configurator to Set the Parameters
With this method, you can set the connections that define the tag data links for
each EtherNet/IP node. Tag data links can be set with a high degree of flexibil-
ity using both memory addresses and network variables. Refer to SECTION 6
Tag Data Link Functions for information on how to make these settings.
Settings Required for the Message Communications Service
Execute a CMND(490) instruction in the CS/CJ-series CPU Unit’s user
program.
Refer to SECTION 9 Message Communications.
36
Switch Settings Section 3-2
3-2 Switch Settings
3-2-1 CS-series EtherNet/IP Units
Setting the Unit Number
The unit number is used to identify individual CPU Bus Units when more than
one CPU Bus Unit is mounted to the same PLC. Use a small screwdriver to
make the setting, taking care not to damage the rotary switch. The unit num-
ber is factory-set to 0.
Note (1) Turn OFF the power supply before setting the unit number.
(2) If the unit number is being set for the first time or changed, then I/O tables
must be created for the PLC.
(3) With CS-series and CJ-series PLCs, words are automatically allocated in
the CIO Area and DM Area according to the unit numbers that are set.
For details, refer to SECTION 4 Memory Allocations.
Setting the Node Address
When there are multiple EtherNet/IP Units or Ethernet Units connected to the
Ethernet network for the FINS communications service, the EtherNet/IP Units
are identified by node addresses. Use the node address switches (NODE
NO.) to set the node address between 01 and FE hexadecimal (1 to 254 deci-
mal). Do not set a number that has already been set for another node on the
same network.
The left switch sets the sixteens digit (most significant digit) and the right
switch sets the ones digit (least significant digit). The node address is factory-
set to 01.
Note Turn OFF the power supply before setting the node address.
Relationship to IP
Addresses When IP addresses are generated automatically (either dynamic or passive),
the rightmost byte of the host ID of the IP address is set to the same value as
the node address. (Refer to Section 5 Determining IP Addresses.) If the same
node address value cannot be used, the IP address table method or the com-
bined method must be used for address conversion. (For details, refer to SEC-
TION 5 Determining IP Addresses.)
If the FINS communications service is not being used on the Ethernet net-
work, then it is all right for the same node address to be set on two or more
EtherNet/IP Units. The setting, however, must be made within a range of 01 to
FE. If a value outside of this range is set, the MS indicator will light red, the 7-
segment display will indicate code H4 (node address setting error), and the
EtherNet/IP Unit will stop operating.
UNIT
No.
Setting range:
0 to F
NODE
NO.
× 161× 16
0
Setting range:
01 to FE (1 to 254 decimal)
37
Switch Settings Section 3-2
3-2-2 CJ-series EtherNet/IP Units and CJ2 Built-in EtherNet/IP Port
Setting the Unit Number
The unit number is used to identify individual CPU Bus Units when more than
one CPU Bus Unit is mounted to the same PLC. Use a small screwdriver to
make the setting, taking care not to damage the rotary switch. The unit num-
ber is factory-set to 0.
Note (1) Turn OFF the power supply before setting the unit number.
(2) If the unit number is being set for the first time or changed, then I/O tables
must be created for the PLC.
(3) With CS-series and CJ-series PLCs, dedicated areas are automatically
allocated in the CIO Area and DM Area according to the unit numbers that
are set. For details, refer to SECTION 4 Memory Allocations.
Setting the Node Address
With the FINS communications service, when there are multiple EtherNet/IP
Units connected to the Ethernet network, the EtherNet/IP Units are identified
by node addresses. Use the node address switches to set the node address
between 01 and FE hexadecimal (1 to 254 decimal). Do not set a number that
has already been set for another node on the same network.
The left switch sets the sixteens digit (most significant digit) and the right
switch sets the ones digit (least significant digit). The node address is factory-
set to 01.
Note Turn OFF the power supply before setting the node address.
Relationship to IP
Addresses When IP addresses are generated automatically (either dynamic or passive),
the rightmost byte of the host ID of the IP address of the EtherNet/IP Unit or
built-in EtherNet/IP port is set to the same value as the node address. (Refer
to Section 5 Determining IP Addresses.) If the same node address value can-
not be used, the IP address table method or the combined method must be
used for address conversion. (For details, refer to SECTION 5 Determining IP
Addresses.)
If the FINS communications service is not being used on the Ethernet net-
work, then it is all right for the same node address to be set on two or more
EtherNet/IP Units or built-in EtherNet/IP ports. The setting, however, must be
made within a range of 01 to FE. If a value outside of this range is set, the MS
indicator will light red, the 7-segment display will indicate code H4 (node
address setting error), and the EtherNet/IP Unit or built-in EtherNet/IP port will
stop operating.
UNIT
No.
Setting range:
0 to F
NODE
No.
× 16 0
× 16 1
Setting range:
01 to FE (1 to 254 decimal)
38
Mounting to a PLC Section 3-3
3-3 Mounting to a PLC
3-3-1 Mounting to a CS-series PLC
EtherNet/IP Units can be mounted to any slot in a CS-series CPU Rack or a
CS-series Expansion CPU Rack, but the number of slots to which they can be
mounted depends on the Backplane. Up to four EtherNet/IP Units can be
mounted to a single PLC. If it is mounted in combination with other CPU Bus
Units (e.g., Controller Link Units), the maximum total number of CPU Bus
Units that can be mounted is 8.
Note Tighten PLC Backplane mounting screws to a torque of 0.9 N⋅m, and the
Unit’s screws to a torque of 0.4 N⋅m.
Note The CS1W-EIP21 EtherNet/IP Unit’s maximum current consumption is
410 mA. Be sure that the total current consumption of all the Units connected
to the same CPU Backplane or Expansion Backplane does not exceed the
output capacity of the Power Supply Unit.
3-3-2 Mounting to a CJ-series PLC
EtherNet/IP Units can be mounted in a CJ-series CPU Rack or a CJ-series
Expansion CPU Rack. Connect the EtherNet/IP Unit in any of the positions
shown below using the sliders on the top and bottom of the Unit. Up to seven
EtherNet/IP Units can be mounted for a CJ2H-CPU@@-EIP CPU Unit
(enabling up to eight EtherNet/IP ports if you include the built-in EtherNet/IP
port). Up to two EtherNet/IP Units can be mounted for a CJ2M-CPU3@ CPU
Unit.
If EtherNet/IP Units are mounted in combination with other CPU Bus Units
(e.g., Controller Link Units), the maximum total number of CPU Bus Units that
can be mounted is 16.
CS1W-BI033/BI053/BI083/BI103 CS-series Expansion Backplane
3, 5, 8, or 10 slots
CS1W-BC023/BC033/BC053/BC083/BC103 CPU Backplane
CS-series CPU Rack with
2, 3, 5, 8, or 10 slots
Can be mounted in any slot.
CS1W-BI033/BI053/BI083/BI103 CS-series Expansion Backplane
CS-series Expansion Rack with
3, 5, 8, or 10 slots. Up to eight Units can be mounted
to the slots shown in the diagrams
on the left.
3, 5, 8, or 10 slots
2, 3, 5, 8, or 10 slots
(Expansion Backplane not possible with 2-slot CPU Backplane.)
CPU: CPU Unit
PS: Power Supply Unit
CPU
PS
PS
PS
Can be mounted in any slot.
CS-series Expansion Rack with
3, 5, 8, or 10 slots.
Can be mounted in any slot.
39
Mounting to a PLC Section 3-3
Note The CJ1W-EIP21 EtherNet/IP Unit’s maximum current consumption is
410 mA. Be sure that the total current consumption of all the Units connected
to the same CPU Backplane or Expansion Backplane does not exceed the
output capacity of the Power Supply Unit.
3-3-3 Mounting
Mount the EtherNet/IP Unit to the Backplane using the following procedure.
1,2,3... 1. Hook the claw on the top of the Unit onto the Backplane.
2. Insert the Unit into Backplane connectors and securely tighten the screw
at the bottom of the Unit. Tighten the screws to a torque of 0.4 N·m.
C
P
U
P
SI
C
P
SI
I
P
SI
I
P
SI
I
CPU Rack 10 Units max. End cover
10 Units max. End cover
Expansion Backplane
10 Units max. End cover
Expansion Backplane
10 Units max. End cover
Expansion Backplane
Up to eight EtherNet/IP
Units can be mounted.
PS: Power Supply Unit
CPU: CPU Unit
IC: I/O Control Unit
II: I/O Interface Unit
Claw
Backplane
40
Mounting to a PLC Section 3-3
3. When removing the Unit, first loosen the screw at the bottom of the Unit.
Note When mounting the Unit, provide the clearance shown below to facilitate easy
mounting or dismounting.
3-3-4 Handling Precautions
• Always turn OFF the power supply to the PLC before mounting or dis-
mounting a Unit or connecting or disconnecting cables.
• Provide separate conduits or ducts for the I/O lines to prevent noise from
high-tension lines or power lines.
• Leave the label attached to the Unit when wiring. Removing the label may
result in malfunction if wire clippings or other foreign matter enters the
Unit. Remove the label after the completion of wiring to ensure proper
heat dissipation. Leaving the label attached may result in malfunction.
Fixin
g
screws
Duct
Duct
20 mm min.
20 mm min.
Backplane
Phillips screwdriver
Remove the label after wiring.
UNIT
NO.
16
1
16
0
0
1
0
NODE
NO.
100BASE-TX
10BASE-T
IP ADDRESS
192.168.250.1
SUBNET MASK
255.255.255.0
MS
NS
COMM
100M
10M
EIP21
41
Network Installation Section 3-4
3-4 Network Installation
3-4-1 Basic Installation Precautions
• Take the greatest care when installing the Ethernet System, being sure to
follow ISO 8802-3 specifications. You must obtain a copy of these specifi-
cations and be sure you understand them before attempting to install an
Ethernet System. Unless you are already experienced in installing com-
munications systems, we strongly recommend that you employ a profes-
sional to install your system.
• Do not install Ethernet equipment near sources of noise. If a noisy envi-
ronment is unavoidable, take adequate measures against noise interfer-
ence, such as installing network components in grounded metal cases or
using optical cable in the system.
• When installing an EtherNet/IP network that combines an information sys-
tem with the control system, and the communications load may be heavy
due to tag data links, we recommend configuring the network so that the
load does not affect communications. For example, install the tag data
links in a segment that is separate from the information network.
Note The maximum current consumption of the CS1W-EIP21 and CJ1W-EIP21
EtherNet/IP Units is 410 mA. Be sure that the total current consumption of all
the Units connected to the same CPU Backplane or Expansion Backplane
does not exceed the output capacity of the Power Supply Unit.
3-4-2 Recommended Products
The following table shows the devices recommended for use with the Ether-
Net/IP Unit 2-3 Selecting the Network Devices.
3-4-3 Precautions
Precautions on Laying Twisted-pair Cable
• Noise resistance may be reduced by ground loops, which can occur due
to improper shield connections and grounding. Ground the shield at one
location, as shown in the following diagram.
• Do not connect the shield to the EtherNet/IP Unit’s connector.
• If a cable connects two hubs, connect the shields at only one end.
Hub Hub
Connector Connector Connector
Connector
Connector Connector
GR GR
Connect shield.
Do not connect shield.
STP
(Shield)
STP
(Shield)
STP
(Shield)
EIP
Unit Power
Supply
Unit
GR
terminal
Connector
EIP
Unit Power
Supply
Unit
GR
terminal
42
Network Installation Section 3-4
• Press the cable connector in firmly until it locks into place at both the
switching hub and the EtherNet/IP Unit.
• Do not lay the twisted-pair cable together with high-voltage lines.
• Do not lay the twisted-pair cable near devices that generate noise.
• Do not lay the twisted-pair cable in locations subject to high temperatures
or high humidity.
• Do not lay the twisted-pair cable in locations subject to excessive dirt and
dust or to oil mist or other contaminants.
Switching Hub Installation Environment Precautions
• Do not ground the switching hub in the same location as a drive-system
component such as an inverter.
• Always use a dedicated power supply for the switching hub’s power sup-
ply. Do not use the same power supply used for other equipment, such as
an I/O power supply, motor power supply, or control power supply.
• Before installation, check the switching hub’s environment-resistance
specifications, and use a switching hub appropriate for the ambient condi-
tions. Contact the switching hub manufacturer for details on switching
hub’s environment-resistance specifications.
Switching Hub Connection Methods
Connect two hubs to each other as follows: Connect an MDI port to an MDI-X
port with a straight cable; connect two MDI ports with a cross cable; and
connect two MDI-X ports with a cross cable.
Note It is very difficult to distinguish cross cables and straight cables by appear-
ance. Incorrect cables will cause communications to fail. We recommend
using cascade connections with straight cables whenever possible.
Some switching hubs can automatically distinguish between MDI and MDI-X.
When this kind of switching hub is being used, straight cable can be used
between switching hubs.
Note Adjust the link settings of the EtherNet/IP Unit or built-in EtherNet/IP port to
match the communications settings of the connected switching hub. If the set-
tings do not match, the link will become unstable and prevent normal commu-
nications. The following table shows the allowed settings for each switching
hub communications mode.
MDI-X port
(cross)
Switching
Hub
Switching
Hub
Switching
Hub
Straight cable
Cross cable
Switching
Hub
MDI ports
Switching hub setting EtherNet/IP Unit setting
Auto-
negotiation 10 Mbps (fixed) 100 Mbps (fixed)
Full
duplex Half
duplex Full
duplex Half
duplex
Auto-negotiation Best --- OK --- OK
10 Mbps
(fixed) Full duplex --- OK --- --- ---
Half duplex OK --- OK --- ---
43
Network Installation Section 3-4
Note Best = Recommended; OK = Allowed; --- = Not allowed.
3-4-4 Using Contact Outputs (Common to All Units)
When an EtherNet/IP Unit or built-in EtherNet/IP port and Contact Output Unit
are mounted in the same Rack or connected to the same PLC, communica-
tions errors may occur due to noise generated by the contact outputs. Use
one or more of the following measures when installing Contact Output Units
and EtherNet/IP Units on the same Rack.
Mounting Location
Mount (or connect) any Contact Output Units as far away from the EtherNet/IP
Unit or built-in EtherNet/IP port as possible.
Cable Location
Separate the transceiver cable or twisted-pair cable connecting the EtherNet/
IP Unit as far from the wiring to the Contact Output Units as possible. The
coaxial cable must also be placed as far away from the Contact Output Units
and their wiring as possible.
100 Mbps
(fixed) Full duplex --- --- --- Best ---
Half duplex OK --- --- --- OK
Switching hub setting EtherNet/IP Unit setting
Auto-
negotiation 10 Mbps (fixed) 100 Mbps (fixed)
Full
duplex Half
duplex Full
duplex Half
duplex
Contact Output Unit EtherNet/IP Unit
Contact outputs
To switching hu
b
Contact Output Unit EtherNet/IP Uni
t
Contact outputs
To switchin
g
hub
44
Connecting to the Network Section 3-5
3-5 Connecting to the Network
3-5-1 Ethernet Connectors
The following standards and specifications apply to the connectors for the
Ethernet twisted-pair cable.
• Electrical specifications: Conforming to IEEE802.3 standards.
• Connector structure: RJ45 8-pin Modular Connector
(conforming to ISO 8877)
3-5-2 Connecting the Cable
!Caution Turn OFF the PLC’s power supply before connecting or disconnecting twisted-
pair cable.
!Caution Allow enough space for the bending radius of the twisted-pair cable as shown
in below.
Connector pin Signal name Abbr. Signal direction
1 Transmission data + TD+ Output
2 Transmission data – TD– Output
3 Reception data + RD+ Input
4 Not used. --- ---
5 Not used. --- ---
6 Reception data – RD– Input
7 Not used. --- ---
8 Not used. --- ---
Hood Frame ground FG ---
35 mm
45
Connecting to the Network Section 3-5
1,2,3... 1. Lay the twisted-pair cable.
2. Connect the cable to the switching hub. Be sure to press in the cable until
it locks into place.
3. Connect the twisted-pair cable to the connector on the EtherNet/IP Unit.
Be sure to press the connectors (both the switching hub side and Ethernet
side) until they lock into place.
EtherNet/IP Unit
RJ45 Modular Connector
Example: CS1W-EIP21
46
Creating I/O Tables Section 3-6
3-6 Creating I/O Tables
3-6-1 I/O Table Overview
I/O tables are used to identify Units mounted to the PLC, and to allocate I/O to
them. With CS-series and CJ-series PLCs, whenever there is a change to the
Unit configuration it is necessary to create I/O tables and register the mounted
Units in the CPU Unit.
The I/O tables can be created in the following ways.
• Using the CX-Programmer offline.
• Using the CX-Programmer online to create the I/O table based on the
Units mounted to the PLC.
• Using the Programming Console to create the I/O table based on the
Units mounted to the PLC.
• Using the CPU Unit's automatic I/O allocation at startup. (This method is
available for the CJ Series only.)
3-6-2 Connecting Programming Devices to the PLC
To create the I/O tables, connect a Programming Device (such as a CX-Pro-
grammer or Programming Console) to the PLC.
Applicable Programming Devices
The following Programming Devices can be used with CS/CJ-series PLCs.
Programming Console
Note A Programming Console cannot be used with the CJ2H-CPU@@(-EIP)
and CJ2M-CPU3@ CPU Units. Use the CX-Programmer.
CX-Programmer
For information on how to connect and operate the CX-Programmer, refer to
the CX-Programmer Operation Manual (Cat. No. W446).
Connecting a Programming Console
To connect a Programming Console, attach a CS/CJ-series Key Sheet and
then connect the Console to the CPU Unit’s peripheral port. (It cannot be con-
nected to the RS-232C port.)
3-6-3 Procedure for Creating I/O Tables
Programming Console
This section provides the procedure for creating the I/O tables using a Pro-
gramming Console. For details on using the Programming Console, refer to
the Programming Console’s operation manual.
Note (1) With the CJ Series, it is necessary to create I/O tables only when the user
is allocating I/O manually. With the CS Series, it is always necessary to
create I/O tables.
Model number Key Sheet (required) Recommended cable (required)
C200H-PRO27-E CS1W-KS001-E CS1W-CN224 (cable length: 2.0 m)
CS1W-CN624 (cable length: 6.0 m)
CQM1-PRO01-E CS1W-CN114 (cable length: 0.1 m)
47
Creating I/O Tables Section 3-6
(2) With the CJ2H-CPU@@-EIP and CJ2M-CPU3@ CPU Units, the built-in
EtherNet/IP port is set in the I/O tables by default and cannot be changed.
It is not necessary to register it in the I/O tables.
Use the following procedure to create the I/O tables.
CX-Programmer (Version 8.0 or Higher)
This section describes how to register an EtherNet/IP Unit or built-in EtherNet/
IP port in the I/O tables using the CX-Programmer (version 8.0 or higher).
Refer to the CX-Programmer Operation Manual (Cat. No. W446) for details on
the operating procedures.
This section describes how to register the CJ1W-EIP21 in the I/O tables by
creating the I/O tables on a computer with the CX-Programmer. In this
example, the computer is connected to the PLC using a serial cable. The
CJ1W-EIP21 is connected to a CJ1H-CPU67 CPU Unit.
1,2,3... 1. Start the CX-Programmer, and then select PLC
−
Auto Online
−
Direct
Connection from the menus.
Initial screen
Password
or (Save or clear the CPU Bus Unit System Setup.)
SHIFT
WRITE
CHG
CH
*DM
000000 I/O TBL ?
000000 I/O TBL
WRIT ????
000000CPU BU ST?
0:CLR 1:KEEP
000000 I/O TBL
WRIT OK
48
Creating I/O Tables Section 3-6
2. The Direct Online Dialog Box will be displayed. Select a serial connection,
select the name of the applicable computer serial port, and then press the
Connect Button.
3. If the connection process is successful, the system will be connected on-
line. Here, check the operating mode of the PLC. If the operating mode is
not PROGRAM mode, change the mode by selecting PLC
−
Operating
Mode
−
Program from the menus.
4. Double-click IO Table and Unit Setup Icon in the project workspace in the
CX-Programmer. The PLC IO Table Window will be displayed. Select Op-
tions
−
Create from the menus.
49
Creating I/O Tables Section 3-6
5. The EtherNet/IP Unit will be displayed at the position it is mounted in the
PLC.
Note If it is not displayed, select Options
−
Transfer from PLC from the
menus.
Note Creating I/O tables is not required if the built-in EtherNet/IP port of a CJ2 CPU
Unit is used. It is registered as a built-in port/Inner Board with a model number
of CJ2B-EIP21 for the CJ2H and a model number of CJ2M-EIP21 for the
CJ2M. You cannot delete a built-in port from the I/O tables.
50
Setting the Local IP Address Section 3-7
3-7 Setting the Local IP Address
This section describes the 3 ways to set the local I/O address of an EtherNet/
IP Unit or built-in EtherNet/IP port.
Method 1: Using the default IP address:
The default IP address is 192.168.250.Node_address.
(The node address is set with the rotary switches on the front of
the EtherNet/IP Unit or, for the built-in EtherNet/IP port, on the
front of the CPU Unit.)
→This method can be used to make a temporary or preliminary
connection to the Ethernet. In this case, leave the TCP/IP Con-
figuration and the allocated DM area IP address settings at their
default values (0.0.0.0).
Method 2: Setting an IP address in the CPU Unit’s allocated DM area:
→If you want to set a particular local IP address and store that set-
ting in the CPU Unit, set it in the EtherNet/IP Unit’s allocated DM
area. The IP address can be set from the CX-Programmer, Pro-
gramming Console, or ladder program.
Method 3: Setting the TCP/IP Configuration from the CX-Programmer:
→If you want to set a particular local IP address and store that set-
ting in the EtherNet/IP Unit, set the IP address from the CX-Pro-
grammer.
When FINS communications are being used, it is necessary to show the cor-
respondence between the IP addresses and FINS node addresses. Refer to
SECTION 5 Determining IP Addresses for an explanation of IP addresses as
well as the correspondence between FINS node addresses and IP addresses.
The three setting methods are described in the following paragraphs.
Method 1: Using the Default IP Address (192.168.250.Node_address)
When the EtherNet/IP Unit or built-in EtherNet/IP port is just mounted in the
PLC and the I/O table is created, the EtherNet/IP Unit or built-in EtherNet/IP
port will operate with its default IP address. This default address is enabled
when the local IP address in the allocated DM area and the TCP/IP Configu-
ration are both set to their defaults (0.0.0.0).
The default IP address is 192.168.250.Node_address, where Node_address
is the node address set with the rotary switches on the front of the EtherNet/IP
Unit. This address is also used as the FINS node address.
The following table shows the various settings in the Unit Setup when the IP
address and TCP/IP Configuration are all set to their default values.
Setting Operating status
IP address 192.168.250.Node_address
Subnet mask 255.255.255.0 (class C mask)
Default gateway None (IP routing disabled)
Preferred DNS server None
Alternate DNS server None
Host name None
Domain name None
Baud rate Auto-detect
51
Setting the Local IP Address Section 3-7
Method 2: Setting the Address in the CPU Bus Unit's Allocated DM Area
With this method, an IP address is not set in the TCP/IP Configuration (left at
its default setting), and an IP address is set in the allocated DM Area words
(the IP Address Display/Setting Area in words m+98 and m+99).
The IP address can be written in the two IP Address Display/Setting Area
words using the CX-Programmer or the Programming Console. To enable the
new IP Address setting, the EtherNet/IP Unit or built-in EtherNet/IP port must
be restarted or the PLC’s power must be turned OFF and then ON again.
Beginning word m = D30000 + (100 x unit number)
The following table shows the various Unit Setup when only the IP Address
Display/Setting Area is set, and the other TCP/IP Configuration settings are
left at their default values.
Method 3: Setting the TCP/IP Configuration from the Network
Configurator
This method can be used to set IP addresses from the CX-Programmer.
For details, refer to 3-8 TCP/IP and Link Settings.
If the IP address is set in the TCP/IP Tab Page, that IP address setting will be
displayed in the IP Address Display/Setting Area (words m+98 and m+99) in
the DM Area words allocated to the Unit/port.
1514131211109876543210
m+98 (1) (2) (3) (4)
m+99 (5) (6) (7) (8)
IP Address: (1)(2).(3)(4).(5)(6).(7)(8) (Hex)
Setting Operating status
IP address IP address set in words m+98 and m+99 (IP Address Dis-
play/Setting Area) of the DM Area words allocated to the
EtherNet/IP Unit as a CPU Bus Unit
Subnet mask Determined by class of the IP address
Default gateway None (IP routing disabled)
Preferred DNS server None
Alternate DNS server None
Host name None
Domain name None
Baud rate Auto-detect
52
TCP/IP and Link Settings Section 3-8
3-8 TCP/IP and Link Settings
This section describes the TCP/IP-related settings, such as the local IP
address and subnet mask for the EtherNet/IP Unit or built-in EtherNet/IP port.
Use the CX-Programmer to make these settings. The settings are stored in
non-volatile memory in the Unit.
Note Unlike the Ethernet Units, the TCP/IP settings of the EtherNet/IP Unit and
built-in EtherNet/IP port are not stored in the CPU Unit’s CPU Bus Unit Sys-
tem Setup Area.
3-8-1 Setting Procedure with the CX-Programmer
1,2,3... 1. When the EtherNet/IP Unit is registered in the I/O tables of the CX-Pro-
grammer, the EtherNet/IP Unit and built-in EtherNet/IP port will be dis-
played in the I/O tables. Refer to 3-6 Creating I/O Tables for details.
2. Right-click the EtherNet/IP Unit or built-in EtherNet/IP port in the I/O table
and select Edit - Unit Setup from the menus. The Edit Parameters Dialog
Box will be displayed.
3. Make the necessary settings on the TCP/IP Tab Page of the Edit Parame-
ters Dialog Box. (The IP address is set here.)
53
TCP/IP and Link Settings Section 3-8
4. Place the CX-Programmer online with the PLC and transfer the settings to
the EtherNet/IP Unit or built-in EtherNet/IP port.
5. After transferring the settings, a message will ask if you want to restart the
EtherNet/IP Unit or built-in EtherNet/IP port. The Unit/port must be restart-
ed to enable the settings.
6. Check the 7-segment display for the EtherNet/IP Unit or built-in EtherNet/
IP port.
7. If the 7-segment display is tested again after it goes OFF, and finally
displays the IP address, it indicates that the EtherNet/IP Unit has
recognized the new TCP/IP Configuration settings (the IP address in this
case).
Note (1) The EtherNet/IP Unit or built-in EtherNet/IP port must restart in order to
enable the parameter settings that are transferred to it. Verify that restart-
ing the Unit/port will not cause any problems in the system before restart-
ing it.
(2) If the target node address (IP address) is not set correctly, invalid device
parameters may be set in the wrong PLC, so check the connected PLC
before downloading parameters.
Settings on the TCP/IP Tab Page
Settings for the following items are provided on the TCP/IP Tab Page of the
Edit Parameters Dialog Box in the CX-Programmer.
• IP address
• Subnet mask
• Default gateway
• Broadcasting
• Preferred DNS server
• Alternate DNS server
• Domain name
• IP router table
54
TCP/IP and Link Settings Section 3-8
IP Address
Sets the local IP address of the EtherNet/IP Unit or built-in EtherNet/IP port.
Set the local IP address on the TCP/IP Tab Page when not setting the IP
address in the CPU Unit’s allocated DM Area or using the default IP address
(default IP address = 192.168.250.Node_address).
When the IP address is set on the TCP/IP Tab Page, it will be stored as the IP
address in the DM Area words allocated to the Unit/port as a CPU Bus Unit.
Subnet Mask
For the subnet mask, all bits corresponding to the bits in the IP address used
as the network ID are set to 1, and the bits corresponding to the host number
are set to 0. The EtherNet/IP Unit or built-in EtherNet/IP port supports CIDR
(Classless Inter-Domain Routing). The subnet mask can be set to 192.0.0.0 to
255.255.255.252. (CIDR is supported by unit version 2.0 or later.)
If no subnet mask is set, or if an illegal value is set, the following values will be
used depending on the IP address class.
In normal applications, we recommend setting the subnet mask defined for
the class.
With the default setting (0.0.0.0), a subnet mask corresponding to the IP
address class is used.
The following table shows the various parameters in the Unit Setup when only
the IP address and subnet mask are set and other settings are left at their
default values.
Default Gateway
Sets the default gateway’s IP address.
This setting is not required when the default gateway is not being used.
Broadcasting
Sets the IP address specification method for broadcasting with FINS/UDP.
• All 1’s (4.3BSD): Broadcasting is performed with the host ID set to all 1’s.
• All 0’s (4.2BSD): Broadcasting is performed with the host ID set to all 0’s.
Normally, use the default setting of all 1’s (4.3BSD).
Preferred DNS Server and Alternate DNS Server
When accessing another node from the EtherNet/IP Unit or built-in EtherNet/
IP port using the host name, the DNS server searches for the other node’s IP
address from the other node’s host name to the DNS server. These settings
register the IP addresses of the preferred and alternate DNS servers that will
perform the search. At this time, the EtherNet/IP Unit is not equipped with any
Class Subnet mask
Class A 255.0.0.0
Class B 255.255.0.0
Class C 255.255.255.0
Setting Operating status
Default gateway None (IP routing disabled)
Preferred DNS server None
Alternate DNS server None
Host name None
Domain name None
Broadcasting 4.3 BSD specifications
IP router table None
55
TCP/IP and Link Settings Section 3-8
functions that require a DNS server, so these settings are not used. (The
functionality required to use a DNS server is not provided on EtherNet/IP
Units with unit version 1.0. The DNS server cannot be used with these Units.)
Domain Name
Sets the domain name of the domain to which the EtherNet/IP Unit or built-in
EtherNet/IP port belongs. The EtherNet/IP Unit or built-in EtherNet/IP port
does not use a domain name in actual communications.
IP Router Table
Set the IP router table to route EtherNet/IP communications for specific nodes
through an IP router other than the default gateway.
Settings on the Ethernet Tab Page
The following settings are provided on the Ethernet Tab Page of the Unit
Setup for the EtherNet/IP Unit or built-in EtherNet/IP port.
• Link settings (baud rate and half/full duplex)
Link Setting
Sets the communications baud rate.
Note Adjust the EtherNet/IP Unit’s link settings to match the communications set-
tings of the connected switching hub. If the settings do not match, the link will
become unstable and prevent normal communications. The following table
shows the allowed settings for each switching hub communications mode.
Note Best = Recommended; OK = Allowed; --- = Not allowed.
3-8-2 Making TCP/IP Settings with the Network Configurator
Use the Network Configurator to change IP address settings for any device
other than a CS/CJ-series EtherNet/IP Unit or built-in port. You can also use
the Network Configurator to change IP address settings for a CS/CJ-series
EtherNet/IP Unit or built-in port.
1,2,3... 1. Connect the Network Configurator online.
Refer to 6-2-9 Connecting the Network Configurator to the Network for
details on connecting the Network Configurator to the EtherNet/IP Unit.
Setting Meaning
Auto (default) The baud rate with the switching hub is detected automat-
ically. If possible, the Unit operates in 100Base-T (full
duplex).
10 Mbps, Half Duplex Operates in 10Base-T, half duplex.
10 Mbps, Full Duplex Operates in 10Base-T, full duplex.
100 Mbps, Half Duplex Operates in 100Base-TX, half duplex.
100 Mbps, Full Duplex Operates in 100Base-TX, full duplex.
Switching hub setting EtherNet/IP Unit setting
Auto-
negotiation 10 Mbps (fixed) 100 Mbps (fixed)
Full
duplex Half
duplex Full
duplex Half
duplex
Auto-negotiation Best --- OK --- OK
10 Mbps
(fixed) Full duplex --- OK --- --- ---
Half duplex OK --- OK --- ---
100 Mbps
(fixed) Full duplex --- --- --- Best ---
Half duplex OK --- --- --- OK
56
TCP/IP and Link Settings Section 3-8
2. Select Tools - Setup TCP/IP Configuration to display the following Setup
TCP/IP Configuration Dialog Box, and set the TCP/IP Configuration for the
target device. In the following example, the settings are all at their default
values.
3. Enter the IP address to set and press the Get from the Device Button. The
present setting will be obtained. Change the IP address in the New Con-
figuration Box if required.
4. Press the Set to the Device Button. The IP address will be transferred to
the device. The applicable device is the device specified in the Target IP
Address Box. The device must be reset to enable the transferred setting. If
the device is not reset when the new IP address is transferred, click the Re-
set the Device Button.
When the EtherNet/IP Unit is reset, the IP address will be displayed once
in flowing text on the 7-segment display on the front of the Unit.
Note (1) The transfer function for IP address settings is defined by ODVA specifi-
cations. Target devices that do not support these specifications cannot be
set. When setting the IP address of the target device with the Network
57
Tag Data Link Parameters Section 3-9
Configurator, connect the devices one at a time, and download the TCP/
IP Configuration’s IP address parameters. If TCP/IP parameters are set
for the EtherNet/IP Unit or built-in EtherNet/IP port from the Network Con-
figurator, the EtherNet/IP Unit may automatically be reset and restarted.
Before setting the TCP/IP parameters, make sure that no system prob-
lems will occur when the Unit is restarted. If the Unit does not restart au-
tomatically, click the Reset the Device Button.
(2) If the target node address (IP address) is not set correctly, invalid device
parameters may be set in the wrong PLC, so check the connected PLC
before downloading parameters.
TCP/IP Parameters
The following TCP/IP parameters can be set from the Network Configurator.
• IP address
• Subnet mask
• Default gateway
• Preferred DNS server
• Alternate DNS server
• Domain name
• Link parameters (baud rate and full/half duplex)
3-9 Tag Data Link Parameters
Set the following parameters when using tag data links with an EtherNet/IP
Unit or built-in EtherNet/IP port. The parameter settings are saved in flash
memory in the EtherNet/IP Unit or CPU Unit. (See note.)
Note The CPU Bus Unit Setup Area is not used for tag data link settings for an
EtherNet/IP Unit or built-in EtherNet/IP port. This point is different from the
operation of Ethernet Units.
Refer to SECTION 6 Tag Data Link Functions for details.
3-9-1 Network Configurator Setting Procedure
The methods for setting tag data links using the Network Configurator can be
roughly divided into the following two.
1. Using the EtherNet/IP Datalink Tool in the Network Configurator to Set the Parameters
With this method, there is no flexibility in the settings, but you can easily set
the data link parameters using only memory addresses, and the settings will
conform to Controller Link data link parameters.
2. Using the Tag Data Link Setting Function in the Network Configurator to Set the Parameters
With this method, you can set the connections that comprise the tag data links
for each EtherNet/IP node. Tag data links can be set with a high degree of
flexibility using both memory addresses and network variables. Refer to SEC-
TION 6 Tag Data Link Functions for details on how to perform these settings.
This section presents a setting example using the EtherNet/IP Datalink Tool.
Using the EtherNet/IP Datalink Tool
The method that is described here is used to set memory addresses in tables
to specify data links between EtherNet/IP Units or built-in EtherNet/IP ports
on CS/CJ-series PLCs.
58
Tag Data Link Parameters Section 3-9
The following method can be used to easily set the data links shown in the fol-
lowing figure using a wizard in the EtherNet/IP Datalink Tool.
1,2,3... 1. Start the Network Configurator, select the applicable EtherNet/IP Unit in
the Tree View on the left, and then paste it into the Device Configuration
Pane on the right.
Note If an EtherNet/IP system has already been installed, you can create a similar
device configuration by connecting to the EtherNet/IP network and selecting
Network
−
Upload from the menus.
Refer to 6-2-9 Connecting the Network Configurator to the Network for infor-
mation on connecting.
2. Select Network
−
EtherNet/IP Datalink Tool from the menus to start the
EtherNet/IP Datalink Tool.
#1
#2
#3
#1
#2
#3
#3
#1
#2
#3
#1
#2
#2
#1
#3
#2
#1
#3
EtherNet/IP
W0
W0
D50 D50
Node #1: CJ1H-CPU67H
(IP address: 192.168.250.1) Node #2: CJ1H-CPU67H
(IP address: 192.168.250.2) Node #3: CJ1H-CPU67H
(IP address: 192.168.250.3)
Area 1
W0
50 words
W50
50 words
W100
50 words
Area 2 D50
100 words
D150
100 words
D250
100 words
59
Tag Data Link Parameters Section 3-9
3. Select Datalink
−
Wizard from the menus in the Datalink Tool when it has
started.
4. In the Datalink Wizard Dialog Box, enter 50 words starting from memory
address W000 for area 1 and 100 words starting from D00050 for area 2,
and then press the OK Button.
5. The data link settings will be automatically created in the window of the
EtherNet/IP Datalink Tool. Select File
−
Save to end. The settings will be
saved in the Network Configurator.
60
Tag Data Link Parameters Section 3-9
6. In the Device Configuration Window of the Network Configurator, a
mark will be added to each EtherNet/IP Unit to show that data links have
been set.
7. Connect the Network Configurator to the EtherNet/IP network and select
Network
−
Download from the menus. The data link settings will be down-
loaded to the EtherNet/IP Units, and the data links will operate.
61
Other Parameters Section 3-10
3-10 Other Parameters
In addition to the tag data link parameters, the EtherNet/IP Unit and built-in
EtherNet/IP port also have the following communications and operation
parameters.
• FINS/UDP
•FINS/TCP
•FTP
• Auto Adjust Time
• Status Area
•SNMP
•SNMP Trap
These parameters are set as Unit Setup from the CX-Programmer. The
parameter settings are saved in flash memory in the EtherNet/IP Unit or CPU
Unit. (See note.)
Note The CPU Bus Unit Setup Area is not used for tag data link settings for an
EtherNet/IP Unit or built-in EtherNet/IP port. This point is different from the
operation of Ethernet Units.
Using FINS/UDP
When necessary, set the routing tables using the CX-Integrator.
Tab Page in Edit
Parameters Dialog Box Setting Function
FINS/UDP FINS/UDP Port Specifies the local UDP port number to use in the FINS communi-
cations service. The UDP uses the UDP port number to distinguish
the application layer (FINS communications service in this case).
• Default value (9,600)
• User-set value (1 to 65,535)
Conversion Selects one of the following methods to convert from the FINS
node address to an IP address (FINS/UDP only).
• Automatic generation (dynamic setting)
• Automatic generation (static setting)
• IP address table
• Combined method
IP Address Table Sets the IP address table that defines the relationship between
FINS node addresses and IP addresses.
This table is effective only when FINS/UDP is being used and the
IP address conversion method is set to the IP address table.
Dynamic change the tar-
get IP addresses Selects dynamic change of other FINS/UDP nodes’ IP addresses.
To disable dynamic changes, deselect this option by removing the
check mark.
62
Other Parameters Section 3-10
Using FINS/TCP
When necessary, set the routing tables using the CX-Integrator.
Using FTP
Tab Page in Edit
Parameters Dialog Box Setting Function
FINS/TCP FINS/TCP Port Specifies the local TCP port number to use in the FINS communi-
cations service. The TCP uses the TCP port number to distinguish
the application layer (FINS communications service in this case).
• Default value (9,600)
• User-set value (1 to 65,535)
FINS/TCP Connection
Setup This is the network API used when TCP is used for the FINS com-
munications service. Up to 16 APIs can be used at a time, and they
are identified by connection numbers 1 to 16.
The EtherNet/IP Unit or built-in EtherNet/IP port can thus simulta-
neously execute the FINS communications service by TCP with up
to 16 remote nodes.
Protection Setting Select this check box to refuse connection requests from any IP
address not set as the target IP address when the server/client
setting is set to a server and the target IP address is set to any
value other than 0.0.0.0.
This check box can be selected to prevent inappropriate opera-
tions on the PLC for FINS commands from specific nodes.
Tab Page in Edit
Parameters Dialog Box Setting Function
FTP Not Use FTP or
Use FTP
Specifies whether to use FTP. FTP connections from external
devices will not be possible if Not Use FTP is specified.
Login Sets the login name for FTP connections to the EtherNet/IP Unit
or built-in EtherNet/IP port from external devices
Password Sets the password for FTP connections to the EtherNet/IP Unit or
built-in EtherNet/IP port from external devices.
Port No. Sets the FTP port number of the EtherNet/IP Unit or built-in
EtherNet/IP port.
It is normally not necessary to change this setting.
Two ports are used with the FTP: a control port and a data transfer
port. Only the control port can be set. The data transfer port num-
ber will be one larger than the control port number.
63
Other Parameters Section 3-10
Using the Automatic Time Adjustment
Using the Status Area
Tab Page in Edit
Parameters Dialog Box Setting Function
Auto Adjust Time Not get the time informa-
tion from the SNTP
server or
Get the time information
from the SNTP server
Specifies whether to set the clock in the CPU Unit to the time on
the SNTP server.
The time can be set only in CPU Units with an EtherNet/IP Unit or
a built-in EtherNet/IP port.
Auto Adjust time Sets the time to access the SNTP server to automatically adjust
the CPU Unit clock.
When the specified time arrives, the SNTP server will be accessed
and the clock in the CPU Unit will be set to the time on the SNTP
server.
Server Specification Type Specifies whether to use an IP address or a domain name (i.e.,
host name) to specify the SNTP server to use for automatic time
adjustment.
IP Address Sets the IP address of the SNTP server to use for automatic time
adjustment.
This IP address is valid only when the Server Specification Type is
set to an IP address.
Host Name Sets the host name of the SNTP server to use for automatic time
adjustment.
This IP address is valid only when the Server Specification Type is
set to a host name.
Port No. Sets the port number to use to connect to the SNTP server for
automatic time adjustment. It is normally not necessary to change
this setting.
Retry Timer Sets the time to wait before retrying the connection when connect-
ing to the SNTP server fails.
It is normally not necessary to change this setting.
Adjust Time Sets the time to offset the clock in the CPU Unit when setting the
clock in the CPU Unit to the time obtained from the SNTP server.
To use the time from the SNTP server as is, enter 0 for the Adjust
Time.
Tab Page in Edit
Parameters Dialog Box Setting Function
Status Area Layout Type Specifies whether to use the default setting or a custom setting for
the words allocated to the status area.
Allocation Area Sets the first word in the status area when the Layout Type is set
for a customer setting.
With CS1/CJ1 CPU Units, only an I/O memory address can be set.
With CJ2 or NE1S CPU Units, either an I/O memory address or a
symbol defined in the CPU Unit can be set.
64
Other Parameters Section 3-10
Using SNMP
Using SNMP Trap
Tab Page in Edit
Parameters Dialog Box Setting Function
SNMP Not use SNMP service or
Use SNMP service
Specifies whether to use the SNMP.
If not using the SNMP service is specified, an SNMP manager will
not be able to connected from an external device.
SNMP Port Sets the port number to use when connecting from an SNMP man-
ager.
It is normally not necessary to change this setting.
SNMP Contact Informa-
tion Specifies the contact information as text.
This information can be read from the SNMP manager.
SNMP Location Informa-
tion Specifies the location information as text.
This information can be read from the SNMP manager.
Authentication Check 1/2 Specifies the SNMP managers that can access the PLC.
To restrict access to only specific SNMP managers, specify the
SNMP managers using IP addresses or host names. Community
names can also be specified (e.g., public).
Ether one or two settings can be made.
Tab Page in Edit
Parameters Dialog Box Setting Function
SNMP Trap Not use SNMP Trap ser-
vice or
Use SNMP Trap service
Specifies whether to use the SNMP trap.
If not using the SNMP trap service is specified, SNMP traps cannot
be sent to the SNMP manager.
SNMP Trap Port Sets the port number to use to connect to the SNMP manager.
It is normally not necessary to change this setting.
Trap 1/2 Sets the SNMP manager destinations for SNMP traps.
The SNMP managers can be specified using IP addresses or host
names. Community names can also be specified (e.g., public).
Either one or two trap destinations can be set.
65
Communications Test Section 3-11
3-11 Communications Test
If the basic settings (in particular the IP address and subnet mask) have been
made correctly for the EtherNet/IP Unit or built-in EtherNet/IP port, then it
should be possible to communicate with nodes on the EtherNet/IP network.
This section describes how to use the PING command to test communica-
tions with the EtherNet/IP Unit or built-in EtherNet/IP port.
3-11-1 PING Command
The PING command sends an echo request packet to a remote node and
receives an echo response packet to confirm that the remote node is commu-
nicating correctly. The PING command uses the ICMP echo request and
responses. The echo response packet is automatically returned in the ICMP.
The PING command is normally used to check the connections of remote
nodes when configuring a network. The EtherNet/IP Unit or built-in EtherNet/
IP port supports both the ICMP echo request and reply functions.
If the remote node returns a normal response to the PING command, then the
nodes are physically connected correctly and Ethernet node settings are cor-
rect.
3-11-2 EtherNet/IP Unit or Built-in EtherNet/IP Port Operation
The EtherNet/IP Unit or built-in EtherNet/IP port automatically returns the
echo response packet in response to an echo request packet sent by another
node (host computer, or other EtherNet/IP Unit or built-in EtherNet/IP port).
An echo request packet can be sent to another node by issuing the FINS
command to execute the PING command from the PLC.
3-11-3 Host Computer Operation
The PING command can be executed from the host computer to send an
echo request packet to an EtherNet/IP Unit or built-in EtherNet/IP port. The
following example shows how to use the PING command in the host com-
puter.
Command Method
Input the following command at the host computer’s prompt ($):
$ ping IP_address(host_name)
The destination is specified by its IP address or host name. If the host name is
used, the host name must be defined in the /etc/hosts file.
Note The PING command is not supported by some host computers.
EtherNet/IP Unit
Ethernet
ICMP IP
UDPTCP
Echo response
Echo request
Remote Node
(host computer or EtherNet/IP Unit)
66
Communications Test Section 3-11
Application Example
In this example, a PING command is sent to the node at IP address
130.25.36.8. The “$” in the example represents the host computer prompt.
Normal Execution
Error Occurred
Refer to the OS command reference manual for your computer for details on
using the PING command.
$ ping 130.25.36.8 ← Executes the PING command.
PING 130.25.36.8: 56 data bytes
64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms
64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms
: : : : :
64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms
← Press the Ctrl+C Keys to cancel execution.
---- 130.25.36.8 PING Statistics ----
9 packets transmitted, 9 packets received, 0% packets loss
round-trip (ms) min/avg/max = 0/1/16
$
$
$ png 130.25.36.8 ← Executes the PING command.
PING 130.25.36.8: 56 data bytes
← Press the Ctrl+C Keys to cancel execution.
---- 130.25.36.8 PING Statistics ----
9 packets transmitted, 9 packets received, 0% packets loss
67
SECTION 4
Memory Allocations
This section describes the words allocated in the CIO Area and the DM Area for EtherNet/IP Units or built-in EtherNet/IP
ports.
4-1 Overview of Memory Allocated to the EtherNet/IP Unit . . . . . . . . . . . . . . . . 68
4-2 CIO Area Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4-2-1 Overview of the Allocated CIO Area Words . . . . . . . . . . . . . . . . . . 70
4-2-2 Details of the Allocated CIO Area Words . . . . . . . . . . . . . . . . . . . . 71
4-3 DM Area Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-3-1 Overview of the Allocated DM Area Words . . . . . . . . . . . . . . . . . . 83
4-3-2 Details of the Allocated DM Area Words. . . . . . . . . . . . . . . . . . . . . 83
4-4 User Settings Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-4-1 Overview of the User Settings Area . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-4-2 User Settings Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-5 Auxiliary Area Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-5-1 Read-only Bits/Words. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-5-2 Read/Write Bits (User Settings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
68
Overview of Memory Allocated to the EtherNet/IP Unit Section 4-1
4-1 Overview of Memory Allocated to the EtherNet/IP Unit
The following CPU Unit words are allocated to the EtherNet/IP Unit or built-in
EtherNet/IP port.
• CPU Unit’s allocated CIO Area words
Contains software switch and status information.
• CPU Unit’s allocated DM Area words
Contains the IP Address Display/Setting Area
• CPU Unit’s user settings area
Contains status information. (This area can be used only when the allo-
cated CIO Area words are set to user settings.)
Note The EtherNet/IP Unit or built-in EtherNet/IP port has the following
two data areas in its non-volatile memory. (Unlike the Ethernet
Units, settings are not stored in the CPU Unit’s CPU Bus Unit Sys-
tem Setup Area.)
• Unit Setup: Settings such as the IP address and FINS/UDP set-
tings. The Unit Setup is set from the CX-Programmer.
• Device parameter settings: Settings such as the tag data link set-
ting parameters. The device parameter settings are made from the
Network Configurator.
69
Overview of Memory Allocated to the EtherNet/IP Unit Section 4-1
CPU Unit
● Allocated CIO Area words
(Allocated to the Unit as a CPU Bus Unit.)
100
words
100
words
100
words
EtherNet/IP Unit
100 words
IP Address Display/Setting Area
Unit settings
64
words
64
words
Unit number 0
Unit number 1
Unit number 15
Unit number 0
Unit number 1
Unit number 15
CIO 1500
CIO 1501
CIO 1524
CIO 1525
CIO 1549
CIO 1875
CIO 1899
25 words 25 words
25 words
25 words
Flags and control bits
Target node PLC's operating
and error information, Unit
status, communications
status, registered/normal
target node, and FINS/TCP
connection status
Local memory
Local memory
Local memory
Set in Network Configurator. →
● User Settings Area
● Allocated DM Area words
(Allocated to the Unit as a CPU Bus Unit.)
D30000
D30098
D30099
D30100
D30199
D31500
D31599
Target node PLC's operating
and error information, and
registered/normal target
node
Non-volatile memory in the EtherNet/IP
Unit
Device parameter settings (tag data link
settings)
Network Configurator
Settings such as the IP address of the
EtherNet/IP Unit and FINS/UDP settings.
Refer to 3-8 TCP/IP and Link Settings
and 3-10 Other Parameters for details.
Refer to Section 6 Tag Data Links for
details.
70
CIO Area Allocations Section 4-2
4-2 CIO Area Allocations
4-2-1 Overview of the Allocated CIO Area Words
The various kinds of data are stored in the allocated CIO Area words, which
are identified by the offset from the beginning word (n) allocated to each Unit.
There are two patterns for the layout of the allocated CIO Area words: the
default settings and user settings. The layout can be selected in the Status
Area settings in the Edit Parameters Dialog Box from the CX-Programmer.
To set a customer areas, select User defined for the Layout Type on the Sta-
tus Area Tab Page.
The beginning word n is calculated by the following equation:
Beginning word n = CIO 1500 + (25 × unit number)
Default Settings
Note The reserved words are regularly refreshed with all zeroes.
Unit control bits
(Reserved)
Target Node PLC Operating Information
(4 words only)
Target Node PLC Error Information
(4 words only)
Unit status 1
Unit status 2
Communications status 1
Communications status 2
Communications status 3
(Reserved)
Registered Target Node
(4 words only)
Normal Target Node
(4 words only)
FINS/TCP Connection Status
CPU Unit → EtherNet/IP Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
Offset Bit
Data direction
n
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
n+10
n+11
n+12
n+13
n+14
n+15
n+16
n+17
n+18
n+19
n+20
n+21
n+22
n+23
n+24
15 8 7 0
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
71
CIO Area Allocations Section 4-2
User Settings
Note The reserved words are regularly refreshed with all zeroes.
The functions of the allocated CIO Area words are described in the following
section.
4-2-2 Details of the Allocated CIO Area Words
Unit Control Bits (CPU Unit to EtherNet/IP Unit) (n)
Unit control bits
(Reserved)
Unit status 1
Unit status 2
Communications status 1
Communications status 2
Communications status 3
(Reserved)
FINS/TCP Connection Status
CPU Unit → EtherNet/IP Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
Offset Bit
Data direction
n
n+1
n+2
n+3
n+4
n+5
n+6
n+7
n+8
n+9
n+10
n+11
n+12
n+13
n+14
n+15
n+16
n+17
n+18
n+19
n+20
n+21
n+22
n+23
n+24
15 8 7 0
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Tag Data Link Start Bit
Tag Data Link Stop Bit
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
n
Adjust Clock Bit
Bit Switch Status Manipulated
by Unit operation
0 to 1 (Not used.) --- --- ---
2 Tag Data Link Start
Bit ON User The tag data link starts when this bit
is switched from OFF to ON.
OFF Unit Turned OFF by Unit after the tag
data link starts operating.
72
CIO Area Allocations Section 4-2
Tag Data Link Start Bit
(Bit 2) Start the tag data links by switching this bit from OFF to ON. If the tag data
links are already operating, the signal will be ignored. The tag data link starts
operating automatically after the tag data link parameter settings are down-
loaded from the Network Configurator, the CPU Unit’s power is turned ON, or
the Unit is restarted.
If the tag data links have been stopped by turning the Tag Data Link Stop Bit
(n bit 04) from OFF to ON, the tag data links can be restarted by turning this
Tag Data Link Start Bit (n bit 02) from OFF to ON.
Once the tag data links start, the EtherNet/IP Unit automatically turns OFF the
Tag Data Link Start Bit. Do not force this bit ON or OFF until it is automatically
turned OFF by the Unit.
Tag Data Link Stop Bit
(Bit 4) Stop the tag data links by switching this bit from OFF to ON. Once the tag
data links have been stopped, they will remain stopped until the Unit is
restarted or the Tag Data Link Start Bit is turned ON. (The tag data links will
also start operating automatically when the tag data link parameter settings
are downloaded from the Network Configurator.)
If the tag data links are already stopped, the signal will be ignored.
Message communications can be performed while the tag data links are
stopped.
Once the tag data links have stopped, the EtherNet/IP Unit automatically
turns OFF the Tag Data Link Stop Bit. Do not force this bit ON or OFF until it is
automatically turned OFF by the Unit.
Adjust Clock Bit (Bit 5) Automatically adjust the time on the clock by switching this bit from OFF to
ON. The SNTP server used to adjust the time is set in the Unit Setup.
Once the clock time has been adjusted, the EtherNet/IP Unit automatically
turns OFF the Adjust Clock Bit. Do not force this bit ON or OFF until it is auto-
matically turned OFF by the Unit.
Target Node PLC
Operating Information
(EtherNet/IP Unit to
CPU Unit) (n + 2 to n +
5)
These words show the operating status of the target node PLCs that are con-
nected with the EtherNet/IP Unit as the originator. This status information is
enabled when the PLC status is included in the communications data in both
the originator and target node.
These words show the status of nodes 0 to 63 only. If it is necessary to show
the status of nodes higher than node 63, select “user settings” as the layout
pattern. For details, refer to 4-4 User Settings Area.
The flags are valid only when the corresponding Normal Target Node Flag is
ON. If the corresponding Normal Target Node Flag is OFF, the Target Node
PLC Operating Flag indicates the previous operating status.
3 (Not used.) --- --- ---
4 Tag Data Link Stop
Bit ON User The tag data link stops when this bit
is switched from OFF to ON.
OFF Unit Turned OFF by Unit after the tag
data link stops operating.
5 Adjust Clock Bit ON User The clock time is automatically
adjusted when this bit is switched
from OFF to ON.
OFF Unit Turned OFF by Unit after the clock
time has been adjusted.
6 to 15 (Not used.) --- --- ---
Bit Switch Status Manipulated
by Unit operation
73
CIO Area Allocations Section 4-2
Target Node PLC
Error Information
(EtherNet/IP Unit to
CPU Unit) (n + 6 to n +
9)
These words show the error status (logical OR of fatal and non-fatal errors) of
the target node PLCs that are connected with the EtherNet/IP Unit as the orig-
inator. This status information is enabled when the PLC status is included in
the communications data in both the originator and target node.
These words show the error status of nodes 0 to 63 only. If it is necessary to
show the error status of nodes higher than node 63, select “user settings” as
the layout pattern. For details, refer to 4-4 User Settings Area.
The flags are valid only when the corresponding Normal Target Node Flag is
ON. If the corresponding Normal Target Node Flag is OFF, the Target Node
PLC Error Flag indicates the previous error status.
Unit Status 1
(EtherNet/IP Unit to
CPU Unit) (n + 10)
Bit Name Status Manipulated
by Unit operation
--- Target Node PLC Operat-
ing Flags ON Unit The corresponding PLC
is operating. (The pro-
gram is being executed.)
OFF Unit The PLC is not operating.
n+2
n+3
n+4
n+5
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
Bit Name Status Manipulated
by Unit operation
--- Target Node PLC Error
Flags ON Unit A fatal or non-fatal error
occurred in the corre-
sponding PLC.
OFF Unit No error occurred in the
PLC.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
n+6 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
n+7 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
n+8 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
n+9 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
n+10
Network Error Occurred
Unit Memory Error
Communications Controller Error
Link OFF Error
Status Area Layout Setting Error
Unit Error Occurred
IP Address Duplication Error
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
74
CIO Area Allocations Section 4-2
Bit Name Status Manipulated
by Unit operation
0 Unit Error Occurred ON Unit Indicates that an error
occurred that is related to
EtherNet/IP Unit operation.
This flag is turned ON when
any bit in Unit Status 1 is
ON. (Bits 1 to 15 are logi-
cally ORed.)
OFF Unit Indicates that a Unit error
did not occur. This flag is
turned OFF when the error
is cleared.
1Network Error
Occurred ON Unit One or more network-
related errors occurred.
(The bits in Communica-
tions Status 1 and 3 are log-
ically ORed.)
OFF Unit Indicates that a network
error did not occur. This flag
is turned OFF when the
error is cleared.
2 to 3 (Not used) --- --- ---
4 Unit Memory Error ON Unit Indicates that an error
occurred in accessing the
Unit’s internal non-volatile
memory (device error).
OFF Unit Indicates that a non-volatile
memory error did not occur.
This flag is not cleared even
if it occurs one time. (Flag
remains ON.)
5 Communications
Controller Error ON Unit Indicates that an error
occurred in the communica-
tions controller.
OFF Unit Indicates that a communica-
tions controller error did not
occur. This flag remains ON
until the power supply is
turned OFF and ON again.
6 IP Address Duplica-
tion Error ON Unit An ARP was sent with the
specified IP address, indi-
cating that an IP address
duplication was detected.
An address duplication is
detected if there is an ARP
response. This flag remains
ON until the power supply is
turned OFF and ON again.
(The Ethernet interface will
stop.)
OFF Unit There was no ARP
response.
7 to 8 (Not used) --- --- ---
9 Link OFF Error ON Unit There was an error estab-
lishing a link with the switch-
ing hub.
OFF Unit A link was established nor-
mally with the switching hub.
75
CIO Area Allocations Section 4-2
Unit Status 2
(EtherNet/IP Unit to
CPU Unit) (n + 11)
10 to
13 (Not used) --- --- ---
14 Status Area Layout
Setting Error ON Unit Indicates that there was an
error in the allocated CIO
Area’s layout settings. When
this error occurs, the allo-
cated CIO Area layout is set
to the default pattern.
In the following cases, how-
ever, the allocated CIO Area
layout is set to the user-set
pattern. In this case, the
user-set area will not be
refreshed.
• A non-existent area has
been specified.
OFF Unit There was not an error in
the layout settings.
15 (Not used) --- --- ---
Bit Name Status Manipulated
by Unit operation
Bit Name Status Manipulated
by Unit operation
0 Online ON Unit Indicates that the Unit is
online. (The EtherNet/IP Unit
can perform communications
processing.)
OFF Unit Indicates that the Unit is not
online. This bit is turned OFF
in the following cases.
• IP Address Duplication Error
• Ethernet Communications
Controller Error (hardware
error)
• BOOTP Server Error
Tag Data Link Operating
Operating IP Address Change
Multiple Switches ON Error
Online
User Settings Area Enabled
Error Lo
g
Stored
n+11
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
76
CIO Area Allocations Section 4-2
1 Tag Data Link
Operating ON Unit Indicates that the tag data link
is operating. Turned OFF
when communications stop in
the following cases.
• Hardware error
• IP Address Duplication Error
• BOOTP Server Error
• Basic Ethernet Settings
Error
• Memory Error (MAC
Address Error)
OFF Unit Indicates that the tag data link
is stopped. Turned ON in the
following cases.
• The Unit is set as the origi-
nator and the power supply
was turned ON or the Unit
was restarted.
• The Unit is set as the origi-
nator and the Tag Data Link
Start Bit was turned ON.
2 Operating IP
Address Change ON Unit ON if the node address set-
ting is different from the set-
ting when the power was
turned ON.
OFF Unit OFF if the node address set-
ting is the same as the setting
when the power was turned
ON.
3 to 10 (Not used) --- --- ---
11 User Setting Area
Enabled ON Unit Indicates that the user set-
tings area data is enabled.
ON when “user settings” have
been specified as the layout of
the allocated CIO Area, and
refreshing of the user settings
area has started.
OFF Unit Indicates that the user set-
tings area data is invalid.
The bit is turned OFF in the
following cases, because
communications stop.
• The allocated CIO Area lay-
out is set to default settings.
• The allocated CIO Area lay-
out is set to user settings,
but one of the following prob-
lems occurred.
• A Layout Setting Error
occurred.
12 to
13 (Not used) --- --- ---
14 Multiple Switches
ON Error ON Unit ON when two or more control
bits are ON simultaneously.
(Unused bits are ignored.)
OFF Unit Turned OFF when the next
control bit operation starts.
Bit Name Status Manipulated
by Unit operation
77
CIO Area Allocations Section 4-2
Communications
Status 1
(EtherNet/IP Unit to
CPU Unit) (n + 12)
Word n+12 contains status flags related to the tag data links, as shown in the
following diagram.
15 Error Log Stored ON Unit Indicates that an error record
is registered in the error log.
OFF Unit Indicates that no error records
are registered in the error log.
Also turned OFF when an
error log clear request is
received.
Bit Name Status Manipulated
by Unit operation
Bit Name Status Manipulated
by Unit operation
0 Verification Error ON Unit Indicates that the information
registered for a target node in
the tag data link parameters is
different from the actual node
information.
Main causes:
• The specified target does not
exist.
• The variable name does not
match.
• The connection size is differ-
ent.
• Connection resources are
insufficient.
OFF Unit Indicates that a verification
error has not occurred. Also
turned OFF when a verifica-
tion error is cleared.
1 (Not used) --- --- ---
2 Tag Data Link Error ON Unit Indicates that there were two
or more errors in a connection
as an originator.
This status does not indicate
the following errors.
• Connection as a target
• Connection timeout due to a
Link OFF Error with the
switching hub
OFF Unit Indicates that the errors listed
above did not occur.
3 (Not used) --- --- ---
n+12
Tag Data Link Error
Invalid Communications Paramete
r
All Tag Data Links Operating
Verification Error
Tag Refresh Error
Ta
g
Data Links Operatin
g
Tag Database Error
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
78
CIO Area Allocations Section 4-2
4 Invalid Communi-
cations Parameter ON Unit ON when there was an error
in the validation check of tag
data link parameters stored in
the Unit’s non-volatile mem-
ory, and a checksum error
occurred. (Includes parame-
ters related to basic Ethernet
settings.)
The tag data links will stop.
OFF Unit OFF when the validation
check of parameters in non-
volatile memory was normal.
5 Tag Refresh Error ON Unit ON when a specified data
area or address range is not
supported in tag data links.
OFF Unit OFF when the specified data
areas and addresses are sup-
ported in tag data links.
6 Tag Database
Error ON Unit ON if a tag database error
occurs in the CPU Unit when
a symbol name is used incor-
rectly in a setting for the Eth-
erNet/IP Unit or built-in
EtherNet/IP port (tag data
link, status area allocations
setting, etc.). (CJ2H-CPU6@-
EIP or CJ2M-CPU3@ only)
OFF Unit OFF when a symbol name is
not used in a setting for the
EtherNet/IP Unit or built-in
EtherNet/IP port, when a tag
database error has not
occurred, or when a previous
error has been cleared.
7 to 13 (Not used) --- --- ---
14 All Tag Data Links
Operating ON Unit Indicates that tag data links
are communicating in all con-
nections as the originator.
OFF Unit Indicates that a tag data link
failed in on or more connec-
tions as the originator.
(OFF even if some tag data
links are communicating.)
15 Tag Data Links
Operating ON Unit Indicates that tag data links
are communicating in one or
more connections as the origi-
nator.
OFF Unit Indicates that not even one
tag data link is communicating
in connections as the origina-
tor.
(OFF even if the Unit is com-
municating as a target.)
Bit Name Status Manipulated
by Unit operation
79
CIO Area Allocations Section 4-2
Communications
Status 2
(EtherNet/IP Unit to
CPU Unit) (n + 13)
Word n+13 contains status flags related to the Ethernet, as shown in the fol-
lowing diagram.
Communications
Status 3
(EtherNet/IP Unit to
CPU Unit) (n + 14)
Word n+14 contains status flags related to the Ethernet errors, as shown in
the following diagram.
Bit Name Status Manipulated
by Unit operation
0 FTP Status ON Unit ON when the FTP server is
operating (i.e., when there is
an FTP client connection).
OFF Unit OFF when the FTP is on
standby (i.e., waiting for a cli-
ent connection).
1 to 13 (Not used) --- --- ---
14 Link Status ON Unit ON when a link is established
with the switching hub.
OFF Unit OFF when the link with the
switching hub is stopped.
15 (Not used) --- --- ---
n+13
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Link Status FTP Status
Bit Name Status Manipulated
by Unit operation
0 to 1 (Not used) --- --- ---
2 Basic Ethernet
Settings Error ON Unit One of the following parame-
ters is invalid.
•TCP/IP
Configuration set-
tings
(IP address, subnet mask, or
Link settings)
OFF Unit OFF when the parameters
above are valid.
3 IP Address Table
Error ON Unit ON when the IP address table
information is incorrect.
OFF Unit OFF when the IP address
table information is correct.
n+14
IP Address Table Error
IP Router Table Error
Address Mismatch
Basic Ethernet Settings Error
Non-volatile Memor
y
Error
Routing Table Error
Ethernet Expansion Settings Error
BOOTP Server Error
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
80
CIO Area Allocations Section 4-2
Registered Target
Node Table
(EtherNet/IP Unit to
CPU Unit) (n + 16 to n
+ 19)
Words n+16 to n+19 show the registration status of the target nodes that are
connected with the EtherNet/IP Unit as the originator.
These words show the status of nodes 0 to 63 only. If it is necessary to show
the status of nodes higher than node 63, select “user settings” as the layout
pattern. For details, refer to 4-4 User Settings Area.
4 IP Router Table
Error ON Unit ON when the IP router table
information is incorrect.
OFF Unit OFF when the IP router table
information is correct.
5 (Not used) --- --- ---
6 Routing Table Error ON Unit ON when the routing table
information is incorrect.
OFF Unit OFF when the routing table
information is correct.
7 to 8 (Not used) --- --- ---
9 Ethernet Expan-
sion Settings Error ON Unit One of the following parame-
ters is invalid.
• FINS settings
OFF Unit OFF when the parameters
above are valid.
10 BOOTP Server
Error ON Unit One of the following errors
occurred when using the
BOOTP server.
• The IP address received
from the BOOTP server is
incorrect.
• A communications timeout
occurred with the server.
OFF Unit OFF when the errors listed
above did not occur.
11 to
13 (Not used) --- --- ---
14 Address Mismatch ON Unit ON when the target IP
address conversion method is
set to Automatic generation,
but the local IP address’ host
ID does not match the FINS
node address.
OFF Unit OFF when the values match.
15 Non-volatile Mem-
ory Error ON Unit ON when an error occurred in
the Unit’s internal non-volatile
memory.
OFF Unit OFF when the Unit’s internal
non-volatile memory is oper-
ating normally.
Bit Name Status Manipulated
by Unit operation
81
CIO Area Allocations Section 4-2
Normal Target Node
Table (EtherNet/IP
Unit to CPU Unit)
(n+20 to n+23)
Words n+20 to n+23 show the connection status of the target nodes that are
connected with the EtherNet/IP Unit as the originator. With revision 2 or
higher, the flag turns ON after all data for multiple connections for individual
target devices is refreshed in the CPU Unit. With revision 1, each flag immedi-
ately turns ON when all connections are established.
These words show the status of nodes 0 to 63 only. If it is necessary to show
the status of nodes higher than node 63, select “user settings” as the layout
pattern. For details, refer to 4-4 User Settings Area.
FINS/TCP Connection
Status
(EtherNet/IP Unit to
CPU Unit) (n+24)
Word n+24 shows the status of FINS/TCP connections. For details, refer to
SECTION 8 FINS Communications.
Bit Name Status Manipulated
by Unit operation
--- Registered Target
Node Flags ON Unit Indicates that the node’s tag
data link is registered.
OFF Unit Indicates that the node’s tag
data link is not registered.
n+16
n+17
n+18
n+19
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
Bit Name Status Manipulated
by Unit operation
--- Normal Target Node
Flags ON Unit Revision 1: Flags immediately
turn ON when all connections
are established.
Revision 2 or higher: Flags turn
ON after all data for multiple
connections for the target
device is refreshed in the CPU
Unit.
OFF Unit Indicates that the connection is
not established
n+20
n+21
n+22
n+23
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
Bit Name Status Manipulated
by Unit operation
0 FINS/TCP Connec-
tion 1 ON Unit Turned ON by the Unit when a
connection is established.
OFF Unit Turned OFF by the Unit when
the connection is terminated.
1 FINS/TCP Connec-
tion 2 ON Unit Turned ON by the Unit when a
connection is established.
OFF Unit Turned OFF by the Unit when
the connection is terminated.
:: :: :
01 2 3 4 5 6 7 8 9 1011 12 13 14 15
n+24
82
CIO Area Allocations Section 4-2
14 FINS/TCP Connec-
tion 15 ON Unit Turned ON by the Unit when a
connection is established.
OFF Unit Turned OFF by the Unit when
the connection is terminated.
15 FINS/TCP Connec-
tion 16 ON Unit Turned ON by the Unit when a
connection is established.
OFF Unit Turned OFF by the Unit when
the connection is terminated.
Bit Name Status Manipulated
by Unit operation
83
DM Area Allocations Section 4-3
4-3 DM Area Allocations
4-3-1 Overview of the Allocated DM Area Words
The various kinds of data are stored in the offset positions shown in the fol-
lowing diagram, from the beginning word in the area for each Unit.
The beginning word m is calculated by the following equation:
Beginning word m = D30000 + (100 x unit number)
4-3-2 Details of the Allocated DM Area Words
IP Address Display/Setting Area (m+98 and m+99)
IP address: (1)(2).(3)(4).(5)(6).(7)(8) (Hex)
If the local IP address is set to a value other than 0.0.0.0 in the TCP/IP Config-
uration, this area (words m+98 and m+99) will act as an IP Address Display
Area and the local IP address set in the TCP/IP Configuration will be read and
stored here when the power is turned ON or the Unit restarted.
If the local IP address in the TCP/IP Configuration is set to 0.0.0.0, this value
is read by the EtherNet/IP Unit when the power is turned ON or the Unit
restarted and is used as the local IP address.
If the local IP address in these words and the TCP/IP Configuration are both
set to 0.0.0.0, the default IP address (192.168.250.Node_address) will be
used. For details on the IP address settings, refer to SECTION 5 Determining
IP Addresses.
Note (1) If an IP address other than 00.00.00.00 is set as the local IP address in
the TCP/IP Configuration, the IP Address Display/Setting Area words
(m+98 and m+99) will be overwritten with the TCP/IP Configuration’s IP
Offset Bit Data direction
m
m+97
m+98
m+99
15 08 07 00
(Not used)
IP Address Display/Setting Area Ethernet Unit to CPU Unit or
CPU Unit to Ethernet Unit
1514131211109876543210
m+98 (1) (2) (3) (4)
m+99 (5) (6) (7) (8)
(1)(2).(3)(4).(5)(6).(7)(8) (Hex)
Application Setting device Setting area Remarks
Simple operation (i.e., The TCP/IP
Configuration is left at its default
settings. Only the IP address is
set.)
Programming Con-
sole (CX-Program-
mer can also be
used.)
Allocated words in
the DM Area • The setting in the allocated DM Area
words is enabled only when the IP
address is set to 0.0.0.0 in the TCP/IP
Configuration.
• If the IP address is set to a value other
than 00.00.00.00 in the TCP/IP Con-
figuration, this value is stored in the
allocated words in the DM Area.
Operation with the desired IP
address set in the TCP/IP Configu-
ration.
CX-Programmer
(Unit Setup) Setup TCP/IP Con-
figuration Dialog Box The IP address set in the Setup TCP/IP
Configuration Dialog Box is stored in
the allocated DM Area words.
84
DM Area Allocations Section 4-3
address, even if a non-zero IP address was set in the IP Address Display/
Setting Area words beforehand.
(2) It is not possible to set the following IP addresses. If any of these values
are set, the ERH indicator will flash.
• IP addresses where all network number bits are 0 or 1.
• IP addresses where all host number bits are 0 or 1.
• IP addresses where all subnet number bits are 1.
• IP addresses that start with 127 (7F hexadecimal, e.g., 127.35.21.16).
85
User Settings Area Section 4-4
4-4 User Settings Area
4-4-1 Overview of the User Settings Area
When the layout of the allocated CIO Area words is set to user settings, the
user settings area can be used in addition to the allocated CIO Area words
and allocated DM Area words.
The beginning word of the user settings area can be set in the Status Area
Tab Page in the Edit Parameters Dialog Box of the CX-Programmer.
4-4-2 User Settings Area
The user can allocate any available area to contain the registered target node
information, normal target node information, target node PLC operating infor-
mation, and target node PLC error information.
Registered Target
Node Table
(EtherNet/IP Unit to
CPU Unit)
These flags indicate the registration status of the target nodes, and are valid
only when the EtherNet/IP Unit is the originator of the connection. For details
on the default settings, refer to 4-2-2 Details of the Allocated CIO Area Words.
Offset Bit Data direction
+0
+15
+16
+31
+32
+47
+48
+63
15 08 07 00
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
EtherNet/IP Unit → CPU Unit
Registered target node
(16 words)
Normal target node
(16 words)
Target node PLC's operating information
(16 words)
Target node PLC's error information
(16 words)
Bit Name Status Manipulated
by Unit operation
--- Registered Target
Node Flags ON Unit Indicates that the node’s tag
data link is registered.
OFF Unit Indicates that the node’s tag
data link is not registered.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+0 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+1 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
+2 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
+3 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
+4 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
+5 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
+6 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
+7 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112
+8 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128
+9 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144
+10 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160
+11 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176
+12 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192
+13 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208
+14 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224
+15 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240
86
User Settings Area Section 4-4
Normal Target Node
Table (EtherNet/IP
Unit to CPU Unit)
These flags indicate the connection status of the target nodes. With revision 2
or higher, the flag turns ON after all data for multiple connections for individual
target devices is refreshed in the CPU Unit. With revision 1, each flag immedi-
ately turns ON when all connections are established.
Target Node PLC
Operating Information
(EtherNet/IP Unit to
CPU Unit)
These flags indicate the operating status of the target node PLCs, and are
valid only when the EtherNet/IP Unit is the originator. The flags are valid only
when the corresponding Normal Target Node Flag is ON. If the corresponding
Normal Target Node Flag is OFF, the Target Node PLC Operating Flag indi-
cates the previous operating status.
For details on the default settings, refer to 4-2-2 Details of the Allocated CIO
Area Words.
Bit Name Status Manipulated
by Unit operation
--- Normal Target Node
Flags ON Unit Revision 1: Flags immediately
turn ON when all connections
are established.
Revision 2 or higher: Flags turn
ON after all data for multiple
connections for the target
device is refreshed in the CPU
Unit.
OFF Unit Indicates that all connections
are not established
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+17 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
+18 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
+19 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
+20 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
+21 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
+22 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
+23 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112
+24 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128
+25 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144
+26 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160
+27 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176
+28 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192
+29 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208
+30 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224
+31 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240
87
User Settings Area Section 4-4
Target Node PLC
Error Information
(EtherNet/IP Unit to
CPU Unit)
These flags indicate the error status (logical OR of fatal and non-fatal errors)
of the target node PLCs, and are valid only when the EtherNet/IP Unit is the
originator. The flags are valid only when the corresponding Normal Target
Node Flag is ON. If the corresponding Normal Target Node Flag is OFF, the
Target Node PLC Error Flag indicates the previous error status.
For details on the default settings, refer to 4-2-2 Details of the Allocated CIO
Area Words.
Bit Name Status Manipulated
by Unit operation
--- Target Node PLC
Operating Flags ON Unit The corresponding PLC is oper-
ating. (The program is being exe-
cuted.)
OFF Unit The PLC is not operating.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+32 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+33 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
+34 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
+35 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
+36 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
+37 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
+38 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
+39 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112
+40 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128
+41 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144
+42 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160
+43 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176
+44 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192
+45 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208
+46 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224
+47 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240
Bit Name Status Manipulated
by Unit operation
--- Target Node PLC
Error Flags ON Unit A fatal or non-fatal error occurred
in the corresponding PLC.
OFF Unit No error occurred in the PLC.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+48 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
+49 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
+50 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
+51 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
+52 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64
+53 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80
+54 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96
+55 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112
+56 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128
+57 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144
+58 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160
+59 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176
+60 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192
+61 223 222 221 220 219 218 217 216 215 214 213 212 211 210 209 208
+62 239 238 237 236 235 234 233 232 231 230 229 228 227 226 225 224
+63 255 254 253 252 251 250 249 248 247 246 245 244 243 242 241 240
88
Auxiliary Area Data Section 4-5
4-5 Auxiliary Area Data
The following table and descriptions cover the words and bits in the CPU
Unit’s Auxiliary Area that are related to the EtherNet/IP Unit.
4-5-1 Read-only Bits/Words
Word(s) Bit(s) Name Function Settings
A202 A20200 to
A20207 Communications
Port Enabled Flags Bits A20200 to A20207 turn ON when a network
instruction (SEND, RECV, CMND, or PMCR) can be
executed with the corresponding port number. Bits
00 to 07 correspond to communications ports 0 to 7.
0: Network communi-
cations running
1: No network com-
munications running
A203 to
A210 --- Communications
Port Completion
Codes
These words contain the completion codes for the
corresponding port numbers when network
instructions (SEND, RECV, CMND, or PMCR) have
been executed. Words A203 to A210 correspond to
communications ports 0 to 7.
0000: No error
Not 0000: Error code
A219 A21900 to
A21907 Communications
Port Error Flags Bits A21900 to A21907 turn ON when an error
occurred during execution of a network instruction
(SEND, RECV, CMND, or PMCR). Bits 00 to 07
correspond to communications ports 0 to 7.
0: Normal end
1: Error end
A302 A30200 to
A30215 CPU Bus Unit
Initializing Flags Bits A30200 through A30215 turn ON while the
corresponding CPU Bus Units (Units #0 through
#15, respectively) are initializing. The bits will turn
ON either when power is turned ON or when a CPU
Bus Unit Restart Bit (A50100 to A50115) is turned
ON.
0: Not initializing
1: Initializing (System
will automatically turn
the flag OFF when ini-
tialization has been
completed.)
A402 A40203 CPU Bus Unit Set-
ting Error Flag
(Non-fatal error)
Bit A40203 is turned ON when the CPU Bus Units
actually installed differ from the Units registered in
the I/O tables. The ERR/ALM indicator on the front
of the CPU Unit will flash, but CPU operation will
continue.
The unit number of the CPU Bus Unit involved is
stored in word A427.
0: No setting error
1: Setting error
A40207 CPU Bus Unit Error
Flag
(Non-fatal error)
Bit A40207 is turned ON when an error occurs
during the transmission of data between the CPU
and CPU Bus Units. The ERR/ALM indicator on the
front of the CPU Unit will flash, but CPU operation
will continue. The Unit where the error occurred will
stop.
The unit number of the CPU Bus Unit involved is
stored in word A422.
0: No unit number
error
1: Unit number error
A403 A40300 to
A40308 Memory Error
Location When a memory error occurs, the Memory Error
Flag (A40115) is turned ON and one of the following
flags is turned ON to indicate the memory area
where the error occurred.
A40300: User program
A40304: PLC Setup
A40305: Registered I/O Tables
A40307: Routing Tables
The ERR/ALM indicator on the front of the CPU Unit
will light and CPU operation will stop.
0: Normal
1: Error
A410 A41000 to
A41015 CPU Bus Unit Num-
ber Duplication
Flags
The Duplication Error Flag (A40113) and the
corresponding flag in A410 will be turned ON when
a CPU Bus Unit’s unit number has been
duplicated. Bits 00 to 15 correspond to unit numbers
0 to F.
The ERR/ALM indicator on the front of the CPU Unit
will light and CPU operation will stop.
0: No duplication
1: Duplication
89
Auxiliary Area Data Section 4-5
4-5-2 Read/Write Bits (User Settings)
A417 A41700 to
A41715 CPU Bus Unit Error,
Unit Number Flags When an error occurs in a data exchange between
the CPU Unit and a CPU Bus Unit, the CPU Bus
Unit Error Flag (A40207) and the corresponding flag
in A417 are turned ON. Bits 00 to 15 correspond to
unit numbers 0 to F.
The ERR/ALM indicator on the front of the CPU Unit
will flash, but CPU operation will continue.
0: No error
1: Error
A427 A42700 to
A42715 CPU Bus Unit Set-
ting Error, Unit
Number Flags
When a CPU Bus Unit Setting Error occurs, A40203
and the corresponding flag in A27 are turned ON.
Bits 00 to 15 correspond to unit numbers 0 to F.
The ERR/ALM indicator on the front of the CPU Unit
will flash, but CPU operation will continue.
0: No setting error
1: Setting error
Word Bits Name Description Settings
A501 A50100 to
A50115 CPU Bus Unit
Restart Bits Bits A50100 through A50115 can be turned ON to
reset CPU Bus Units number #0 through #15,
respectively.
Note The CPU Bus Unit Initializing Flags (A30200
to A30215) will turn ON when initialization of
the Units begins and turn OFF when it is com-
pleted.
Note When turning ON the CPU Bus Unit Restart
Bit from a ladder program, use the SET
instruction.
OFF to ON:
Unit restarted.
Automatically turned
OFF by system after
restart processing
has been completed.
Word(s) Bit(s) Name Function Settings
90
Auxiliary Area Data Section 4-5
91
SECTION 5
Determining IP Addresses
This section explains how to manage and use IP addresses.
5-1 IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-1-1 IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-1-2 Allocating IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
5-1-3 EtherNet/IP Unit IP Address Settings. . . . . . . . . . . . . . . . . . . . . . . . 93
5-1-4 Subnet Masks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5-1-5 CIDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5-2 IP Addresses in FINS Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5-2-1 Specifying Nodes in FINS Communications Services. . . . . . . . . . . 94
5-2-2 Pairing Addresses in Internal Tables . . . . . . . . . . . . . . . . . . . . . . . . 96
5-2-3 Application Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5-2-4 Related Products and Communications/Setting Methods. . . . . . . . . 103
5-2-5 Pairing IP Addresses and FINS Node Addresses . . . . . . . . . . . . . . . 105
5-3 Private and Global Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5-3-1 Private and Global Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5-3-2 Using a Private Address for the EtherNet/IP Unit . . . . . . . . . . . . . . 107
5-3-3 EtherNet/IP Unit with a Global Address . . . . . . . . . . . . . . . . . . . . . 109
92
IP Addresses Section 5-1
5-1 IP Addresses
5-1-1 IP Address Configuration
IP addresses are made up of 32 bits of binary data divided into four 8-bit fields
called octets. These four octets provide the network number (net ID) and host
number (host ID). The network number identifies the network, and the host
number identifies the node (or host) on the network.
The network numbers in an IP address are divided into three classes, A, B,
and C, so that the address system can be selected according to the scale of
the network. (Classes D and E are not used.) The configuration of the IP
address for each of these classes is shown in the following diagram.
The number of networks in each class and the number of nodes possible on
the network differ according to the class.
The 32 bits of an IP address are divided into four sections of eight bits each,
and expressed as a punctuated number. IP addresses are represented by the
decimal equivalent of each of the four octets in the 32-bit address, each sepa-
rated by a period. For example, the binary address 10000010 00111010
00010001 00100000 would be represented as 130.58.17.32.
Note The same network number must be set for every node on the same Ethernet
network.
5-1-2 Allocating IP Addresses
IP (Internet Protocol) is a standard communications protocol used throughout
the world, and is designed to enable communications between any Ethernet
nodes regardless of the networks on which they exist. To achieve this, net-
work numbers are allocated by the Network Solutions, InterNIC Registration
Services, to ensure that all Ethernet networks have unique numbers regard-
less of where they exist. The local system administrator is left the responsibil-
ity of allocating unique host numbers locally. You therefore should obtain a
network number from the InterNIC Registration Services to ensure unique-
ness and allow for future network expansions if required.
Bit 31 23 0
0Class A
Bit 31 15 0
0Class B 1
Bit 31 7 0
0Class C 1 1
Bit 31 0
0Class D 1
1
1
Bit 31 0
1Class E 1
1
1
Network number (7 bits) Host number (24 bits)
Network number (14 bits) Host number (16 bits)
Network number (21 bits) Host number (8 bits)
Multicast address (Cannot be used.)
(Cannot be used.)Identification address
Class Number of networks Number of hosts
Class A Small 224−2 max. (16,777,214 max.)
Class B Medium 216−2 max. (65,534 max.)
Class C Large 28−2 max. (254 max.)
93
IP Addresses Section 5-1
5-1-3 EtherNet/IP Unit IP Address Settings
An IP address must be set even for the EtherNet/IP Unit or built-in EtherNet/IP
port before Ethernet communications can proceed. Use one of the following
methods to set the IP address of the EtherNet/IP Unit or built-in EtherNet/IP
port. Either use the default IP address setting, use a Programming Device to
set a particular IP address in the DM Area words (CS/CJ Series only) allo-
cated to the Unit as a CPU Bus Unit, or set a particular IP address in the Eth-
erNet/IP Unit or built-in EtherNet/IP port.
• If you want to connect the EtherNet/IP Unit or built-in EtherNet/IP port
immediately, the default IP address is 192.168.250.Node_address. (The
node address is set with the Node Address Setting Switches on the front
of the EtherNet/IP Unit or CPU Unit.)
• If you want to set a particular IP address and store that local IP address in
the CPU Unit, set it with the CPU Unit’s allocated DM Area words (CS/CJ
Series only).
• If you want to set a particular IP address and store that local IP address in
the EtherNet/IP Unit or CPU UNit, set the IP address in the TCP/IP set-
tings of the Unit Setup from the CX-Programmer.
• If you want to set a particular IP address and obtain the IP address auto-
matically from the BOOTP server, TCP/IP settings of the Unit Setup from
the CX-Programmer. For details, refer to 3-8 TCP/IP and Link Settings.
5-1-4 Subnet Masks
Operation and management of a network can become very difficult if too
many nodes are connected on a single network. In such a case it can be help-
ful to configure the system so that a single network is divided up into several
subnetworks. This can be done by using part of the host number as a subnet
number. Internally the network can be treated as a number of subnetworks,
but from the outside it acts as a single network and uses only a single Net-
work ID.
To establish subnetworks, the Host ID in the IP address is divided into a Sub-
net ID and a Host ID by using a setting called the Subnet Mask. The Subnet
Mask indicates which part of the Host ID is to be used as the Subnet ID. All
bits in the Subnet Mask that correspond to the bits in the IP address used
either as the Network ID or Subnet ID are set to “1,” and the remaining bits,
which correspond to the bits in the IP address actually used for the Host ID,
are set to “0.”
The following example shows the Subnet Mask for an 8-bit Subnet ID used in
a class-B IP address.
Set the same Subnet Mask value for all of the nodes on that subnetwork. If no
subnetworks are used, there is no need to set Subnet Masks. In that case, the
following Subnet Mask values will be used depending on the IP address class.
Class Subnet Mask value
Class A 255.0.0.0
Class B 255.255.0.0
Class C 255.255.255.0
Bit 31 15 0
Class B 1 0
Subnet mask 1111111111111111 1111111100000000 = FF FF FF 00
Network ID (14 bits) Host ID (16 bits)
Network number
Subnet number Host number
94
IP Addresses in FINS Communications Section 5-2
5-1-5 CIDR
CIDR, or classless interdomain routing, is used to assign IP addresses that do
not use classes. IP addresses that use classes are separated into blocks
according to net IDs and host IDs, resulting in inefficient usage of IP address
space.
CIDR does not use classes, so IP address space can be divided as required
to more efficiently use IP address space. For example, using a subnet mask
setting with CIDR enables building a horizontally distributed network exceed-
ing 254 nodes even if a class C address block (e.g., 192, 168...).
CIDR was added for unit version 2.0.
5-2 IP Addresses in FINS Communications
5-2-1 Specifying Nodes in FINS Communications Services
With FINS communications services on an Ethernet network, IP addresses,
UDP port numbers, and TCP port numbers are paired with FINS node
addresses to specify nodes on the network.
Note Use the Node Address Setting Switches (NODE NO.) on the front of the Eth-
erNet/IP Unit or, for the built-in EtherNet/IP port, on the front of the CPU Unit
to set the FINS node address.
Allocating Addresses to EtherNet/IP Units and Built-in EtherNet/IP Ports
FINS Message Reception
for EtherNet/IP Units or
Built-in EtherNet/IP Ports
The IP address, FINS/UDP port number, and FINS/TCP port number set for
the EtherNet/IP Unit or built-in EtherNet/IP port are mainly used when receiv-
ing FINS communications messages.
Subnet mask range
192.0.0.0 to 255.255.255.252
Application level
Transport level
Internet level
Physical level
FINS
UDP
IP
Ethernet
Node number
UDP port
number TCP port
number
TCP
IP address
Ethernet address
Must be allocated.
Automatically allocated
Application level
Transport level
Internet level
Physical level
FINS
UDP
IP
Ethernet
TCP
Node number
UDP port
number TCP port
number
IP address
Ethernet address Receives communications data
conforming to Ethernet address,
IP address, UDP port number,
and FINS node number.
FINS header FINS dataEthernet V2 IP UDP
95
IP Addresses in FINS Communications Section 5-2
• Ethernet address: A fixed number is assigned to each EtherNet/IP
Unit or built-in EtherNet/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-in EtherNet/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-in EtherNet/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 set-
ting in the EtherNet/IP Unit or built-in EtherNet/IP port according to the follow-
ing 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
With these methods, the IP address and the FINS node address setting in the
EtherNet/IP Unit or built-in EtherNet/IP port have no particular relationship.
Set both the FINS node address and the IP address so that they are not dupli-
cated in the network.
Sending FINS Messages
from EtherNet/IP Units or
Built-in EtherNet/IP Ports
When the EtherNet/IP Unit or built-in EtherNet/IP port sends a FINS mes-
sage, 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 or built-in EtherNet/IP port.
When the EtherNet/IP Unit or built-in EtherNet/IP port is turned ON or
restarted, the internal table is generated automatically from the various set-
tings 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.)
Remote FINS node
address Remote IP address
(Example) Connection Remote port
number (Example)
1 192.168.250.1 UDP 9600
2 192.168.250.2 UDP 9600
to
254 192.168.250.254 UDP 9600
96
IP Addresses in FINS Communications Section 5-2
5-2-2 Pairing Addresses in Internal Tables
FINS/UDP Communications Methods
Automatic Generation
(Dynamic) When the EtherNet/IP Unit or built-in EtherNet/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.
1 192.168.250.1 UDP 9600
2 UDP 9600
!
!
!
254 UDP 9600
192.168.250.2
192.168.250.254
FINS header
Remote FINS
node number Remote IP
address (Example) Connection
Remote port
number
(Example)
Internal table
FINS data
Application level
Transport level
Internet level
Physical level
FINS
UDP TCP
IP
Ethernet
Node number
UDP port
number TCP port
number
IP address
Ethernet address
Ethernet V2 IP UDP FINS header FINS data
Remote node
Application level
Transport level
Internet level
Physical level
FINS
UDP TCP
IP
Ethernet
Node number
UDP port
number TCP port
number
IP address
Ethernet address
The remote node's IP address, UDP/TCP
method, UDP port number, and TCP port
number are calculated from the node
number in the FINS message, and an
Ethernet frame is generated.
Personal computer
Local FINS node number
Local IP address
Must be fixed.
Can be changed.
IP address
IP address
FINS command
FINS response
EtherNet/IP Unit
Change
registration
Internal table
Automatic generation
(dynamic setting)
Remote IP address Local IP address
Ethernet (EtherNet/IP)
CPU Unit
Remote FINS node number
Local FINS node number
For the remote IP address,
a response is returned to
the changed IP address.
97
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-in EtherNet/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 gener-
ated is not freely changed.
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 dynami-
cally changed by a method such as DHCP.
Personal computer
Local FINS node number
Local IP address
Must be fixed.
Must be fixed.
IP address
IP address
FINS command
FINS response
EtherNet/IP Unit
Automatic generation
(static setting)
Internal table
Remote IP address Local IP address
CPU Unit
Remote FINS node number
Local FINS node number
Ethernet (EtherNet/IP)
98
IP Addresses in FINS Communications Section 5-2
Example
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 genera-
tion 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 mes-
sages 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.
18
20
23
153.214.0.62
153.214.0.129
153.218.51.8
25 153.218.51.10
When FINS Command is Sent
FINS node number
Node number in
IP address table
IP address table
FINS node
number IP address
IP address 153.214.0.129
FINS command sent
When FINS Command is Received
FINS node number
Node number not
in IP address table
Changed
Internal table
IP address 153.218.51.10
FINS response returned
99
IP Addresses in FINS Communications Section 5-2
Example
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.
Prohibiting Dynamically
Changing Remote IP
Addresses
With EtherNet/IP Units and built-in EtherNet/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 CX-
Programmer 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 the CX-Pro-
grammer.
Using the ETN11-
compatible Mode With EtherNet/IP Units and built-in EtherNet/IP ports, operating specifications
can be made compatible with the CS1W-ETN11/CJ1W-ETN11 for all methods
(automatic generation (dynamic), I/O address table, or combined). (Dynamic
changes, however, are prohibited for the destination IP address in ETN11-
compatible mode.) While in ETN11-compatible mode, the following operations
will be performed the same as they are for the CS1W-ETN11/CJ1W-ETN11
for 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.
When FINS Command is Sent
FINS node number
FINS node number
Node number in
IP address table 18
20
23
153.214.0.62
153.214.0.129
153.218.51.8
25 153.218.51.10
Node number not
in IP address table
Automatic
generation
method
IP address table
FINS node
number
Network number: xx.xx.00.00
IP address
FINS node number: xx
+
IP address
FINS command
sent
IP address
(See note.)
FINS command
sent
When FINS Command is Received
Node number
not in IP
address table
Changed
Internal table
IP address
153.218.51.10
FINS response
returned
Automatic
generation
method
(dynamic)
IP address
method
100
IP Addresses in FINS Communications Section 5-2
Note If the ETN11-compatible mode 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
Method With the FINS/TCP method, communications are first established for each
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-in EtherNet/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 ad-
dresses set for FINS/TCP connections in the FINS/TCP Tab Page of the
CX-Programmer’s Edit 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 re-
mote node's FINS node address.
4. The EtherNet/IP Unit or built-in EtherNet/IP port changes the internal table
(FINS node address, IP address, and TCP port number).
5. FINS messages can then be sent and received.
101
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 re-
mote device (i.e., the client, either a personal computer, an EtherNet/IP
Unit or built-in EtherNet/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-in EtherNet/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.
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 CX-
Programmer.
■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 nor-
mally be used.
■Local Device: Client
1,2,3... 1. Set the client.
Personal computer or
EtherNet/IP Unit (client)
Local FINS node number A
Local IP address T
The FINS node number
is converted for each
connection number.
(1) The connection is established.
(2) The local device (such as a personal
computer) sends notification that its
FINS node number is A.
IP address
IP address
FINS node number transmission
FINS node number transmission
(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.
EtherNet/IP Unit (server) CPU Unit
Local FINS node number B
Local IP address S
Ethernet (EtherNet/IP)
102
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-in EtherNet/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-3 Application 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 origi-
nated.
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.
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
Personal computer (client)
IP address changed
(acquired from DHCP server when connected)
FINS command sent
IP address
IP address
FINS command
FINS response
Ethernet (EtherNet/IP)
Response sent back to
changed IP address
EtherNet/IP Unit
(with fixed IP address)
Personal computer (client)
IP address changed
(acquired from DHCP server when connected)
FINS command sent
IP address
IP address
FINS command
FINS response
Response sent back to
changed IP address
EtherNet/IP Unit
(FINS/TCP server; with
fixed IP address)
Ethernet (EtherNet/IP)
103
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 per-
sonal 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-in EtherNet/IP ports in PLC systems are also allo-
cated fixed IP addresses.
Simultaneously Running Multiple Applications on a Personal Computer
In communications involving previous models, multiple communications appli-
cations were configured on personal computers according to data accessing
uses, and the fact that no more than one UDP port number for FINS commu-
nications could be used on any given computer created a problem. This Eth-
erNet/IP Unit provides a practical solution with an internal table that pairs
remote nodes (applications) with FINS node addresses, enabling dynamic
changes.
FINS/UDP
Communications Method 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 appli-
cations to the EtherNet/IP Unit or built-in EtherNet/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 appli-
cation 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-in EtherNet/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-4 Related Products and Communications/Setting Methods
Models Supporting
Automatic Generation
Method (Dynamic)
Product Model/Series/
Version Supports automatic
generation method
(dynamic)?
CS-series Ethernet
Unit 100BASE-TX CS1W-ETN21 Yes
10BASE-5 CS1W-ETN01 No: Set by automatic
generation method or
combined method. Com-
munications are not pos-
sible with personal
computers with variable
IP addresses.
10BASE-T CS1W-ETN11
CJ-series Ethernet
Unit 100BASE-TX CJ1W-ETN21 Yes
10BASE-T CJ1W-ETN11 No: Set by automatic
generation method or
combined method. Com-
munications are not pos-
sible with personal
computers with variable
IP addresses.
CV/CVM1-series
Ethernet Unit 10BASE-5 CV500-ETN01
FinsGateway Version 4.xx or
lower
Version 2003 or
higher Yes
104
IP Addresses in FINS Communications Section 5-2
Models Supporting
Automatic Generation
Method (Static)
Models Supporting IP
Address Table Method
Programmable Terminal NS Series No: Set manually so that
automatic settings can be
used with the automatic
generation method.
Open Network Controller (ONC) ---
Product Model/Series/
Version Supports automatic
generation method
(dynamic)?
Product Model/Series/
Version Supports automatic
generation method
(static)?
CS-series Ethernet
Unit 100BASE-TX CS1W-ETN21 Yes
10BASE-5 CS1W-ETN01 Yes: Simply called “auto-
matic generation
method.”
10BASE-T CS1W-ETN11
CJ-series Ethernet
Unit 100BASE-TX CJ1W-ETN21 Yes
10BASE-T CJ1W-ETN11 Yes: Simply called “auto-
matic generation
method.”
CV/CVM1-series
Ethernet Unit 10BASE-5 CV500-ETN01
FinsGateway Version 4.xx or
lower
Version 2003 or
higher Yes
Programmable Terminal NS Series No: Set manually so that
automatic settings can be
used with the automatic
generation method.
Open Network Controller (ONC) ---
Product Model/Series/
Version Supports IP address
table method?
CS-series Ethernet
Unit 100BASE-TX CS1W-ETN21 Yes
10BASE-5 CS1W-ETN01
10BASE-T CS1W-ETN11
CJ-series Ethernet
Unit 100BASE-TX CJ1W-ETN21
10BASE-T CJ1W-ETN11
CV/CVM1-series
Ethernet Unit 10BASE-5 CV500-ETN01
FinsGateway Version 4.xx or
lower
Version 2003 or
higher
Programmable Terminal NS Series No: Set manually. FINS
communications are not
possible with personal
computers set automati-
cally by DHCP.
Open Network Controller (ONC) ---
105
IP Addresses in FINS Communications Section 5-2
Models that Can Use the
Combined Method
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.
Product Model/Series/
Version Supports combined
method?
CS-series Ethernet
Unit 100BASE-TX CS1W-ETN21 Yes
10BASE-5 CS1W-ETN01 No
10BASE-T CS1W-ETN11 No
CJ-series Ethernet
Unit 100BASE-TX CJ1W-ETN21 Yes
10BASE-T CJ1W-ETN11 No
CV/CVM1-series
Ethernet Unit 10BASE-5 CV500-ETN01 No
FinsGateway Version 4.xx or
lower No
Version 2003 or
higher Yes
Programmable Terminal NS Series No: Set manually. FINS
communications are not
possible with personal
computers set automati-
cally by DHCP.
Open Network Controller (ONC) ---
Communi-
cations
method
Method of pairing
of IP addresses
and FINS node
addresses
IP address determination Client (personal
computer of PLC) Server (PLC)
FINS node
address IP address FINS node
address IP address
FINS/UDP By pairing FINS
node addresses with
IP addresses in
Ethernet
IP address
conversion Automatic gen-
eration method
(static)
Fixed Fixed Fixed Fixed
Automatic gen-
eration method
(dynamic)
Fixed Fixed or
variable Fixed Fixed
IP address table
method Fixed Fixed or
variable Fixed Fixed
Combined
method Fixed Fixed or
variable Fixed Fixed
FINS/TCP By automatic conver-
sion of FINS node
addresses at Ether-
Net/IP Unit and
remote node (and
then sending and
receiving data)
Automatic Connection
method (auto-
matic FINS
node address
conversion)
Fixed or
can be allo-
cated auto-
matically
when not
determined.
Fixed or
variable Fixed Fixed
106
Private and Global Addresses Section 5-3
5-3 Private and Global Addresses
5-3-1 Private 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-in EtherNet/
IP port, are allocated private addresses.
Communications Services
That Require Global
Addresses for EtherNet/IP
Units and built-in
EtherNet/IP ports
A global address is required for the IP addresses of the EtherNet/IP Units and
built-in EtherNet/IP port when the following communications services are
used over the Internet.
• FINS communications services
• Explicit message communications services
Intranet
Personal computer,
CX-Programmer, etc.
Ethernet (EtherNet/IP)
PLC
Firewall
IP router
Private address
Internet Global address
(required)
Intranet
Private address
IP router Global address
Private address
Firewall
Ethernet (EtherNet/IP)
PLC PLC
Private address Private address
Not output to Internet
Personal computer,
CX-Programmer, etc.
Not output to Internet
Private address
107
Private and Global Addresses Section 5-3
5-3-2 Using a Private Address for the EtherNet/IP Unit
Conditions for Using
Communications
Applications
When the EtherNet/IP Unit or built-in EtherNet/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-in EtherNet/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 or built-in EtherNet/IP port that has a pri-
vate address. FINS communications are also not possible over the Inter-
net between EtherNet/IP Units and or built-in EtherNet/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-in EtherNet/IP port IP
address conversion methods can be used.
Intranet
FINS/TCP client computer
with CX-Programmer, etc.
Firewall
IP router
Ethernet (EtherNet/IP)
PLC
Communications in intranet
EtherNet/IP Unit: Private address
FINS communications,
Explicit messages
FINS communications,
Explicit messages
Internet
Intranet
IP router
Firewall
Communications in Intranet
FINS/TCP client computer
with CX-Programmer, etc.
or
CIP client computer with
Network Configurator, etc.
Ethernet (EtherNet/IP)
PLC PLC
Communications
in Intranet
EtherNet/IP Unit: Private address EtherNet/IP Unit: Private address
or
CIP client computer with
Network Configurator, etc.
108
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-in EtherNet/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-in EtherNet/IP ports with pri-
vate 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-in EtherNet/IP port that has a pri-
vate address. Explicit message communications are also not possible
over the Internet between EtherNet/IP Units and built-in EtherNet/IP ports
with private addresses.
Note Network Security and Firewalls
Setting up an intranet through a global address involves network security con-
siderations. 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.
109
Private and Global Addresses Section 5-3
5-3-3 EtherNet/IP Unit with a Global Address
Conditions for Using
Communications
Applications
Communications applications can be used over the Internet under the follow-
ing 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 or built-in EtherNet/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-in EtherNet/IP port.
• The TCP port number to be used for FINS/TCP cannot be used if prohib-
ited 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-in EtherNet/IP port that has a
global address.
Intranet
FINS/TCP client computer
with CX-Programmer, etc.
or
CIP client computer with
Network Configurator, etc.
Ethernet (EtherNet/IP)
Communications
over Internet Firewall
IP router
Internet Global address
(required)
Intranet
IP router
Firewall
Private address
Global address
Communications
in intranet
Ethernet (EtherNet/IP)
PLC
EtherNet/IP Unit: Global address
Private address
Private address
Not output to Internet
Not output to Internet
110
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 communi-
cations path.
Note Network Security and Firewalls
Setting a global IP address for an EtherNet/IP Unit or built-in EtherNet/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.
111
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
112
Overview of Tag Data Links Section 6-1
6-1 Overview of Tag Data Links
6-1-1 Tag 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 set-
tings 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 the CJ2H-CPU6@-EIP and CJ2M-
CPU3@. If you are using a CJ1W-EIP21 or CS1W-EIP21 EtherNet/IP Unit that
is mounted to a CJ2H-CPU6@ or any CPU Unit other than the CJ2H-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.
For communications between PLCs, the connection information is set in the
EtherNet/IP Unit or built-in EtherNet/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 infor-
mation is set in the EtherNet/IP Unit or built-in EtherNet/IP port that is the orig-
inator. 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 to
Appendix 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.
Input tags
Output tags
Input tags
Output tags
DM00100
Var-In
DM20000
DM00200
Var-Out
DM20100
Var-Out1
Var-Out2
Var-Out3
DM00200
WR300
DM20100
I/O refreshed.
Inputs
Tag set name: ABC
CPU Unit CPU Unit
I/O refreshed.
I/O refreshed.
I/O refreshed.
EtherNet/IP Unit EtherNet/IP Unit
Originator
Originator
Outputs
Tag set name: XYZ
PLC status PLC status
Connection
Connection
Tag set name: OUT1
Outputs
Target
Target
Inputs
Tag set name: IN1
Ethernet (EtherNet/IP)
Var-Out1(DM0)
Var-Out2(DM100)
Var-Out3(DM200)
DM00200
WR300
DM20100
DM00100
Var-In(WR200)
DM20000
DM00200
Var-Out(WR300)
DM20100
113
Overview of Tag Data Links Section 6-1
6-1-2 Overview 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-EIP21 built-in EtherNet/IP port on the
CJ2H, CJ2M-EIP21 built-in EtherNet/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-in EtherNet/IP port on the CJ2H, CJ2M-EIP21 built-in EtherNet/IP port
on the CJ2M, CS1W-EIP21, or CJ1W-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@-EIP or CJ2M-CPU3@, you can create tags by import-
ing network symbols (i.e., I/O allocation settings) that were created using the
CX-Programmer into 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-EIP21 built-in EtherNet/IP port on the CJ2H, CJ2M-EIP21
built-in EtherNet/IP port on the CJ2M, CS1W-EIP21, or CJ1W-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-EIP21 built-in EtherNet/IP port on the CJ2H, CS1W-
EIP21, or CJ1W-EIP21. A maximum of 32 connections can be opened per
Unit for the CJ2M-EIP21 built-in EtherNet/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.
114
Overview of Tag Data Links Section 6-1
Another EtherNet/IP Unit must be mounted to the PLC to increase the maxi-
mum number of connections. (Refer to the following figure.)
Setting the Packet Interval
(RPI) 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-in EtherNet/IP port on the CJ2H), CS1W-EIP21, or
CJ1W-EIP21. It can be set to between 1 and 10,000 ms in units of 0.5 ms for
the CJ2M-EIP21 (built-in EtherNet/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.
Using Multicast and
Unicast Communications 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.
Example of Calculating the Number of Connections
• EtherNet/IP Unit or built-in EtherNet/IP port with IP address of
192.168.250.254 in bidirectional connection with 128 nodes
The maximum number of
connections for node
192.168.250.254 is 32 for
the CJ2M and 256 for other
CPU Units.
192.168.250.254 192.168.250.1
192.168.250.2
192.168.250.128
Tagset_out
Tagset_in
:
:
Tagset _in1
Tagset _in2
Tagset_in128
Tagset_out254
CN.1
CN.2
CN.128
CN.129
CN.130
CN.256
:
:
:
Tagset_out
Tagset_in
Tagset_out
Tagset_in
• 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-in
EtherNet/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.
Example of Calculating the Number of Connections
192.168.250.1
192.168.250.2
192.168.250.129
192.168.250.254
192.168.250.253
Tagset_in1
Tagset_in2
Tagset_in129
Tagset_out253
Tagset _out
Tagset_in
Tagset _out
Tagset _in
Tagset _out
Tagset _i n
CN.1
CN.2
CN.129
CN.1
CN.2
CN.129
:
:
:
:
:
115
Overview of Tag Data Links Section 6-1
If multicast connections are used, however, use a switching hub that has mul-
ticast filtering, unless the tag set is received by all nodes in the network.
If a switching hub that does not have multicast filtering is used, the multicast
packets will be broadcast to the entire network, and so packets will be sent to
nodes that do not require them, which will cause the communications load on
those nodes to increase.
This applies only if one output tag set is sent to multiple nodes using a multi-
cast connection with one packet, the connection type of the connections that
receive the output tag set is multicast, and the connection I/O types, packet
intervals (RPI), and timeout values are all the same.
Note The performance of communications devices is limited to some extent by the
limitations of each product’s specifications. Consequently, there are limits to
the packet interval (RPI) settings. Refer to 10-2 Adjusting the Communica-
tions Load and set an appropriate packet interval (RPI).
Starting and Stopping Tag Data Links
Tag data links are automatically started when the data link parameters are
downloaded from the Network Configurator. Thereafter, tag data links can be
stopped and started for the entire network or individual devices from the Net-
work Configurator. Starting and stopping tag data links for individual devices
must be performed for the originator.
Software switches in allocated words can also be used to start and stop tag
data links for the entire network. Refer to 6-2-13 Starting and Stopping Tag
Data Links for details.
6-1-3 Tag Data Link Functions and Specifications
Item Specification
Communications
type Standard EtherNet/IP implicit communications (connection-
type cyclic communications)
Setting method After setting tags, tag sets, and connections with the Network
Configurator, the tag data link parameters must be down-
loaded to all devices in the EtherNet/IP network.
With a CJ2H-CPU6@-EIP or CJ2M-CPU3@ CPU Unit, a sym-
bol table can be created with the CX- Programmer and then
imported into the Network Configurator to allocate tags.
After the parameters are downloaded, the EtherNet/IP Units
are restarted to start the tag data links.
Tags Applicable CPU Unit data: CIO Area, DM Area, EM Area,
Holding Area, Work Area, and symbols. (See note.)
Number of words per tag: 20 max. (40 bytes) for CJ2M, 722
max. (1,444 bytes) for other CPU Units
Number of tags per Unit: 32 max. for CJ2M, 256 max. for other
CPU UNits
Note With the CJ2H-CPU6@-EIP or CJ2M-CPU3@, network
symbols (I/O allocation settings) created using the CX-
Programmer can be imported into the Network Configu-
rator.
Tag sets Number of tags per tag set: 8 max. (7 max. if PLC status is
included)
Number of words per tag set: 20 max. (40 bytes) for CJ2M,
722 max. (1,444 bytes) for other CPU Units
Number of tag sets per Unit: 32 max. for CJ2M, 256 max. for
other CPU Units
Connections Number of connections per Unit: 32 max. for CJ2M, 256 max.
for other CPU Units
116
Overview of Tag Data Links Section 6-1
System Configuration Conditions for Setting Tags Using Symbols or I/O Memory
Addresses
Local tags for tag data links can be set using I/O memory addresses or net-
work symbols. Support for network symbols, however, depends on the model
of CPU Unit, as shown in the following table.
Communications with the remote node are possible regardless of whether the
remote node tags are set using I/O memory addresses or network symbols.
Note Symbols cannot be set for tags with CJ2H-CPU6@ and CJ2M-CPU1@ CPU
Units.
6-1-4 Data Link Data Areas
Tags A data link between the local I/O memory and a remote I/O memory is called
a tag. A tag can be set using a network symbol name or an I/O memory
address.
Tag Sets When a connection is established, from 1 to 8 tags (including PLC status) is
configured as a tag set. Each tag set represents the data that is linked for a
tag data link connection. Tag data links are thus created by connecting one
tag set to another tag set. A tag set name must be set for each tag set.
Note A connection is used to exchange data as a unit within which data concur-
rency is maintained. Thus, data concurrency is maintained for all the data
exchanged for the tags in one data set.
Example In the following example, input tags a to g at the originator are a tag set
named SP1_IN and output tags i and ii are a tag set named SP1_OUT). A
connection is set between these two tag sets.
Connection type Each connection can be set for 1-to-1 (unicast) or 1-to-N (mul-
ticast) communications. (Default: Multicast)
Packet interval (RPI) 1 to 10,000 ms for CJ2M and 0.5 to 10,000 ms for other CPU
Units (in 0.5-ms units)
The packet interval can be set separately for each connection.
Item Specification
Name in hardware list
of Network
Configurator
CPU Unit EtherNet/IP Unit or
built-in EtherNet/IP port Symbol name
specification I/O memory
address
specification
CJ2B-EIP21 CJ2H-CPU6@-EIP CJ2H-CPU@@-EIP OK OK
CJ2M-EIP21 CJ2M-CPU3@CJ2M-CPU3@OK OK
CJ1W-EIP21(CJ2) CJ2H-CPU6@-EIP
CJ2H-CPU6@
CJ2M-CPU3@
CJ2M-CPU1@
CJ1W-EIP21 OK
(CJ2H-CPU6@-EIP and
CJ2M-CPU3@ only)
(See note.)
OK
CJ1W-EIP21 CJ1 CPU Unit CJ1W-EIP21 --- OK
CS1W-EIP21 CS1 CPU Unit CS1W-EIP21 --- OK
117
Overview of Tag Data Links Section 6-1
There are both input and output tag sets. Each tag set can contain only input
tags or only output tags. The same input tag cannot be included in more than
one input tag set.
Number of Tags in Tag
Sets Each tag set can contain one or more tags.
■Tag Sets with Only One Tag
With basic Network Configurator procedures, each tag set contains only one
tag.
■Tag Sets with Multiple Tags
As shown below, tags can be created in groups. Each tag set can contain up
to 8 tags totaling 20 words for the CJ2M or 722 words for other CPU Units.
Tag ii
Tag i
PLC status
EtherNet/IP
Connection
Tag Set (Input Tags)
Tag set name: SP1_IN
PLC status
Tag a
Tag b
Tag c
Tag g
Originator device Target device
Tag set name: SP1_OUT
Tag Set (Output Tags)
IP address: #
Connection Information
· Target IP address: #
· Originator tag set: SP1_IN
· Target tag set: SP1_OUT
· Packet interval (RPI)
Tag set SP1_IN
(tag a)
EtherNet/IP
I/O memory
CPU Unit
a
b
I/O memory
CPU Unit
c
d
Tag set SP2_IN
(tag d)
Tag set SP1_OUT
(tag c)
Connection
Tag set SP2_OUT
(tag b)
Connection
One tag each
(Each tag is set using a text
string of the network symbol
or I/O memory address.)
118
Overview of Tag Data Links Section 6-1
Note The I/O memory words used in tags in a tag set do not have continuous
addresses. The tags can also be from different I/O memory areas. To enable a
connection, however, each tag set must include only input tags or only output
tags. (Both input and output tags cannot be included in the same tag set.)
Specifications The following table shows the tag and tag set specifications.
PLC Status A characteristic function of the CS1W-EIP21 and CJ1W-EIP21 EtherNet/IP
Units and CJ2 built-in EtherNet/IP ports is the ability to specify the PLC status
as a member of the tag set. This function reads the operating status (operat-
ing and error status) of the CPU Unit of the PLC in which the EtherNet/IP Unit
is mounted, and includes the PLC status as status flags in the data trans-
ferred by the tag data links.
When the PLC status is specified as an output (produce) tag, it is actually
transferred as the tag set’s leading data in the following format.
Tag set SP1_IN
(group of tags a, b, and c)
EtherNet/IP
I/O memory
CPU Unit
a
b
c
d
e
I/O memory
CPU Unit
f
g
h
i
j
Tag set SP1_OUT
Tag set SP2_OUT
(group of tags d, e) Tag set SP2_IN
Connection
One tag each
(Each tag is set using a text
string of the network symbol
or I/O memory address.)
Tags Tag sets
CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
CJ2M-CPU3@CS1W-EIP21
CJ1W-EIP21
CJ2H-CPU@@-EIP
CJ2M-CPU3@
Total size of all tags ≤
184,832 words Total size of all tags ≤ 640
words Maximum size of 1 tag set ≤
722 words
(The maximum size is 721
words when the tag set
includes the PLC status.)
Maximum size of 1 tag set ≤
20 words
(The maximum size is 19
words when the tag set
includes the PLC status.)
Maximum size of 1 tag ≤ 722
words
(The maximum size is 721
words when the tag set
includes the PLC status.)
Maximum size of 1 tag ≤ 20
words
(The maximum size is 19
words when the tag set
includes the PLC status.)
Number of tags per tag set ≤ 8
(7 tags/tag set when the tag set includes the PLC status)
Note Input and output variables cannot be combined.
Number of registrable tags ≤
256 Number of registrable tags ≤
32 Number of registrable tag
sets ≤ 256 Number of registrable tag
sets ≤ 32
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
00 0 0 0 0 0 0 0 0 0 0 0 0
PLC Operating Flag
PLC Error Flag
119
Overview of Tag Data Links Section 6-1
To receive the PLC status, specify the PLC status in an input (consume) tag in
the reception tag set as well. When the PLC status is specified in an input tag,
the PLC status flags will be reflected in the corresponding location in the tag
data link’s Target Node PLC Operating Flags and Target Node PLC Error
Flags. The following example shows the relationship between the Target Node
PLC Operating Flag location and target ID of the target node with
192.168.250.2.
Note The target ID may be duplicated depending on the IP addresses of the target
nodes. In this case, it is necessary to change the target ID with the Network
Configurator. For information on how to change the device number, refer to
step 4 under Registering Devices in the Register Device List on page 141.
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
IP address = 192.168.250.2 → (Last byte = 2) → Target ID = #002
Target Node PLC Operating Flags:
n+2
n+3
n+4
n+5
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32
63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48
EtherNet/IP
I/O memory
CPU Unit
a
b
c
CPU Unit
f
g
h
PLC status (when included)
Target data link status
PLC status
I/O memory
PLC status
Connection
Output tag set Input tag set
PLC status (when included)
120
Overview of Tag Data Links Section 6-1
The following table shows the operation of each the bits when multiple con-
nections are used to communicate with a node, and the PLC status is speci-
fied in all of the connections.
Note When the PLC status is not selected in the input (consume) tags, the PLC sta-
tus information (16-bit data) can be used as reception data.
Name (allocated area) Contents
Target Node PLC Operating Flag
Information
Layout set to default settings:
Words n+2 to n+5
Layout set to user settings:
Words n+32 to n+47
Note Corresponds to the PLC sta-
tus’s PLC Operating Flag.
Each flag indicates the operating status of the
corresponding target node PLC of connections
in which the EtherNet/IP Unit is the originator.
The flag corresponding to the target node’s
target ID will be ON when the PLC Operating
Flags for all connections with that target node
indicate that the PLC is operating.
Each node address’s flag location (i.e., target
ID) can be changed from the Network Configu-
rator.
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-
mation
Layout set to default settings:
Words n+6 to n+9
Layout set to user settings:
Words n+48 to n+63
Note Corresponds to the PLC sta-
tus’s PLC Error Flag.
Each flag indicates the error status (logical OR
of non-fatal and fatal errors) of the correspond-
ing target node PLC of connections in which
the EtherNet/IP Unit is the originator. The flag
corresponding to the target node’s target ID
will be ON if even one error is indicated in any
of the connections with that target node.
Each node address’s flag location (i.e., target
ID) can be changed from the Network Configu-
rator.
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
Layout set to default settings:
Words n+20 to n+23
Layout set to user settings:
Words n+16 to n+31
Note Does not correspond to the
PLC status.
Each flag indicates the connection status of
the corresponding target node PLC of connec-
tions in which the EtherNet/IP Unit is the origi-
nator. The flag corresponding to the target
node’s target ID will be ON when connections
are established for all connections with that
target node indicate that the PLC is operating.
Each node address’s flag location (target ID)
can be changed from the Network Configura-
tor.
The data in this table is refreshed when neces-
sary.
121
Setting Tag Data Links Section 6-2
6-2 Setting Tag Data Links
6-2-1 Starting the Network Configurator
Procedure Tag data links are set by using the Network Configurator. Use the following
procedure to start the Network Configurator.
■Starting from the Windows Start Menu
To start the Network configurator, select OMRON - CX-One - Network Con-
figurator for EtherNet/IP - Network Configurator from the Windows Start
Menu.
■Starting from the IO Table Dialog Box in CX-Programmer
To start the Network configurator, select the Unit in the PLC IO Table Dialog
Box and select either of the options for Start Special Application from the
pop-up menu. Only operation will be started even if Start with Settings Inher-
ited is selected.
122
Setting Tag Data Links Section 6-2
When the Network Configurator starts, the following window will be displayed.
Main Window The Main Window consists of a Hardware List and a Network Configuration
Window, as shown in the following diagram.
Hardware List:
Displays the devices that can
be added to the network.
Network Configuration Window:
Displays the layout and network
configuration of devices that are set
and monitored.
123
Setting Tag Data Links Section 6-2
When two or more networks are being managed, a new Network Configura-
tion Window can be added by selecting Network - Add.
To change the name displayed in the Network Tab Page, select Network -
Property. The name set in the Comment Field of the Network Property Win-
dow can be changed.
124
Setting Tag Data Links Section 6-2
6-2-2 Tag Data Link Setting Procedure
The section describes the procedure for setting tag data links (i.e., connection
information).
For data links between PLCs, the connection information is set only in the
originator, i.e., the node that receives data.
1. Creating a Network Configuration
Register all EtherNet/IP Units or built-in EtherNet/IP ports for which connections will
be created in the EtherNet/IP Network Configuration Window. (Refer to 6-2-3 Reg-
istering Devices.)
Note If a system has already been installed, connect online to the EtherNet/IP net-
work and upload the network configuration. (Refer to 6-2-11 Uploading Tag
Data Link Parameters.)
↓
2. Creating Connections
Set the connections using one of the following methods.
1) Basic Operation
1-1) Create tags and tag sets for all registered devices (EtherNet/IP Unit or built-
in port). (Refer to 6-2-4 Creating Tags and Tag Sets.)
1-2) Create a connection for the originator device (i.e., registered device that
receives data as input data). (Refer to 6-2-5 Connection Settings.)
2) Generating a Connection Using the EtherNet/IP Datalink Tool (Refer to 6-2-5
Connection Settings.)
The EtherNet/IP Datalink Tool is used to create data links between PLCs by
specifying I/O memory addresses in the same manner as for Controller Link.
The following functions can be used with Network Configurator version 3.10 or
higher.
3) Creating Connections Using the Wizard (Refer to 6-2-7 Creating Connections
Using the Wizard.)
Create connections between OMRON PLCs following the instructions. Tags and
tag sets must be set for all devices before starting the Wizard. (Refer to Basic
Operation 1-1.)
Note Select Device - Parameters - Wizard from the menus to start operation.
4) Creating Connections by Dragging and Dropping Registered Devices (Refer to 6-
2-8 Creating Connections by Device Dragging and Dropping.)
When a target device is dragged and dropped to the originator device, the Edit
Connection Dialog Box will be displayed, and a connection can be created.
OMRON EtherNet/IP Units or built-in EtherNet/IP ports are the only originator
devices for which connections can be created in this way.
↓
Downloading Tag Data Link Parameters (Refer to 6-2-10 Downloading Tag Data Link
Parameters.)
↓
Check that tag data links are operating correctly by using the indicators on the Ether-
Net/IP Unit (refer to 14-2 Using the LED Indicators and Display for Troubleshooting for
Troubleshooting) and the Network Configurator monitor function (refer to 14-1 Check-
ing Status with the Network Configurator).
↓
Check that the output tag data is updated in the input tag by using the CX-Program-
mer's Watch Window or PLC memory function.
Note Refer to the CX-Programmer Operation Manual (Cat. No. W446) for the operat-
ing procedures.
125
Setting Tag Data Links Section 6-2
6-2-3 Registering Devices
Register all of the devices required in the equipment (such as EtherNet/IP
Units performing tag data links) as a network configuration.
1,2,3... 1. Register the devices that will participate in the tag data links by dragging
the devices from the Hardware List and dropping them in the Network Con-
figuration Window. (To drag and drop an icon, click and hold the left mouse
button over the icon, move the icon to the destination, and release the
mouse button.)
The icon will be displayed in the Network Configuration Window, as shown
in the following diagram.
Hardware List
Note (1) If the revision is unknown, select the newest revision (i.e., the revision
with the highest number). The following table shows the relation between
the CIP revision and the unit version.
(2) When mounting the CJ1W-EIP21 to a CJ2 CPU Unit, select CJ1W-EIP21
(CJ2) from the Hardware List.
2. Click the right mouse button over the registered device’s icon to display the
pop-up menu, and select Change Node Address.
Drag and drop icons from
the Hardware List.
Name in hardware list CIP revision EtherNet/IP Unit
CJ2B-EIP21 Rev. 2 Built-in EtherNet/IP port on CJ2H
CPU Unit (CJ2H-CPU@@-EIP)
CJ2M-EIP21 Rev. 2 Built-in EtherNet/IP port on CJ2M
CPU Unit (CJ2M-CPU3@)
CJ1W-EIP21 Rev. 1 or 2 CJ1W-EIP21 EtherNet/IP Unit
connected to CJ1 CPU Unit
CS1W-EIP21 Rev. 1 or 2 CS1W-EIP21 EtherNet/IP Unit
connected to CJ1 CPU Unit
CJ1W-EIP21 (CJ2) Rev. 2 CJ1W-EIP21 EtherNet/IP Unit
connected to CJ2 CPU Unit
Unit version CIP revision
Ver. 1.0 Revision 1.01
Ver. 2.0 Revision 2.01 or 2.02
126
Setting Tag Data Links Section 6-2
3. Set the IP address to match the node address (IP address) actually being
used in the device.
4. Repeat steps 1 to 3, and register all of the devices participating in the tag
data links.
6-2-4 Creating Tags and Tag Sets
Specifying I/O
Memory Addresses The tag sets and set member tags required to create connections for a regis-
tered EtherNet/IP Unit must be created. The I/O memory addresses or net-
work symbols that are used in the control programs can be set for the tags.
(Using network symbols is supported only by the CJ2H-CPU6@-EIP21 and
CJ2M-CPU3@.) This section first describes the basic procedure for creating
tags and tag sets for using the Network Configurator's device parameter edit-
ing function.
1. Creating Tags and Tag Sets Using the Network Configurator's Device Pa-
rameter Editing Function
Next, the following two procedures, which can be used to effectively use net-
work symbols in tags, are described.
2. Importing Network Symbols Created with the CX-Programmer to the Net-
work Configurator
3. Importing Network Symbols That Were Registered to Tags with the Net-
work Configurator to the CX-Programmer
1. Creating Tags and Tag Sets Using the Network Configurator's Device Parameter
Editing Function
Note The network symbols described in this section can be used only if you are
using a CJ2H-CPU6@-EIP21 or CJ2M-CPU3@ CPU Unit.
Creating a Tag Set
1,2,3... 1. Double-click the icon of the device (for which a tag set is being created) to
display the Edit Device Parameters Dialog Box. Right-click the icon to dis-
play the pop-up menu, and select Parameter - Edit.
127
Setting Tag Data Links Section 6-2
2. Click the Tag Sets Tab at the top of the Edit Device Parameters Dialog Box.
There are two kinds of tag sets: input (consume) and output (produce).
128
Setting Tag Data Links Section 6-2
Creating and Adding Tags 3. Click the Edit Tags Button. The Edit Tags Dialog Box will be displayed.
Register the input (consume) tags and output (produce) tags separately.
4. Click the In - Consume Tab, and click the New Button. The Edit Tag Dialog
Box will be displayed.
5. In the Name Field, enter the character string for the CPU Unit's I/O memory
address or a network symbol (e.g., 100, W100, D0, Input_signal).
Addresses in the following I/O memory areas can be set.
Note (a) The H, W, D, and E characters can also be input in lower case as
h, w, d, and e.
CPU Unit’s data area Address (Text to input in Name Field.)
CIO Area 0000 to 6143
Holding Area H000 to H511
Work Area W000 to W511
DM Area D00000 to D32767
EM Area Bank 0 hex E0_00000 to E0_32767
···
···
Bank 18
hex E18_00000 to E18_32767
129
Setting Tag Data Links Section 6-2
(b) Be sure to directly enter the CPU Unit's I/O memory address
(e.g., 100, W100, D0) or a network symbol as a character string.
6. Input the size of the tag in the Size Field, in bytes.
7. Click the Regist Button to register the tag.
If an I/O memory address is specified for a tag name, the Edit Tags Dialog
Box will be displayed with the next consecutive address as the tag name
for editing the next tag. Once you have registered the tags, click the Cancel
Button.
8. Click the Out - Produce Tab, and click the New Button. The Edit Tag Dialog
Box will be displayed, like the dialog box for input tags, except for the Over
Load setting. The Over Load setting determines whether outputs are
cleared or continue their previous status when outputs are turned OFF with
the PLC’s Output OFF function. Output inhibit settings are not required for
input (reception) tag sets.
• Follow the output inhibit function: Enabled (default)
Output data is cleared to 0 when a PLC output inhibit occurs.
• Do not follow the output inhibit function: Disabled
Output data maintains its previous status even after a PLC output in-
hibit occurs.
Note When any of the following errors occurs in the originator PLC while tag data
links are in progress, the connection will be forcibly disconnected.
• Fatal CPU Unit error
• I/O refreshing error
• CPU Unit WDT error
• I/O bus error
Select Disable or Enable.
130
Setting Tag Data Links Section 6-2
9. When you are finished registering the required tags, click the OK Button at
the bottom of the Edit Tags Dialog Box.
10. At this point, a confirmation dialog box will be displayed to check whether
the registered tag names will registered without changes as tag sets. A tag
set can contain up to 8 tags, but tag sets will be registered with one tag per
tag set if the tags are registered as tag sets. In this case, the Yes Button is
clicked to register one tag per tag set.
If the No Button is clicked, more tags can be registered at the end of the
tag set. Refer to step 18 for details on adding tags to the end of the tag set.
131
Setting Tag Data Links Section 6-2
Changing and Registering
Tag Sets 11. The following dialog box will be displayed when the tags in the Edit Tags
Dialog Box are registered directly as tag sets.
12. If an input tag has already been registered in an input tag set, and you want
to change its registration to a different input tag set, it is necessary to de-
lete the tag from the tag set in which it was originally registered.
132
Setting Tag Data Links Section 6-2
Open the Edit Device Parameters Dialog Box, select the tag set containing
the tag that you want to delete, and click the Delete Button in the Edit Tag
Dialog Box. (If there are other tags registered in that tag set, it is possible
to delete just one tag by selecting the tag that you want to delete in the Edit
Tag Set Dialog Box and clicking the Button.)
At this point, a confirmation dialog box will be displayed to confirm that you
want to delete the selected tag set and the tags contained in that tag set.
If the No Button is clicked, only the tag set will be deleted. Click the No But-
ton.
133
Setting Tag Data Links Section 6-2
13. In order to edit a registered tag set and add tags, either double-click the tag
set, or select the tag set and click the Edit Button. The Edit Tag Set Dialog
Box will be displayed.
The Tag List on the left side of the dialog box shows the tags that are al-
ready registered, and the Candidate Tag List on the right side of the dialog
box shows the other tags that have not been registered yet. To add a tag,
select it in the Candidate Tag List and click the Button.
14. When the PLC status is being included in the tag set, select the Include
Option at the upper-right corner of the dialog box.
15. If you want to change the tag set’s name, it can be changed in this dialog
box.
16. To save the changes, click the OK Button at the bottom of the Edit Tag Set
Dialog Box.
17. Click the OK Button at the bottom of the Edit Device Parameters Dialog
Box.
134
Setting Tag Data Links Section 6-2
18. If you want to just add new tags and register the tag set, first register the
tags with steps 1 to 9. In this example, input tags D00004 and D00005
have been newly added.
19. When you are finished registering the required tags, click the OK Button at
the bottom of the Edit Tags Dialog Box.
20. At this point, a confirmation dialog box will be displayed to check whether
the registered tag names will be registered without changes as tag sets.
Tags are just being added in this case, so click the No Button. Just the tags
will be registered, without registering the tags as tag sets.
135
Setting Tag Data Links Section 6-2
21. To register the newly added tags in a tag set, either double-click the de-
sired tag set, or select the tag set and click the Edit Button.
The Tag List on the left side of the dialog box shows the tags that are al-
ready registered, and the Candidate Tag List on the right side of the dialog
box shows the other tags that have not been registered yet.
22. Select the tags that you want to add from the Candidate Tag List and click
the Button.
Up to 8 tags can be registered in a tag set, or up to 7 tags can be registered
and two byes will be added to the size if the PLC status is included in the
tag set.
23. To confirm the changes, click the OK Button at the bottom of the Edit Tag
Set Dialog Box.
24. Click the OK Button at the bottom of the Edit Device Parameters Dialog
Box.
136
Setting Tag Data Links Section 6-2
2. Importing Network Symbols Created with the CX-Programmer to the Network
Configurator
If the CJ2H-CPU6@-EIP or CJ2M-CPU3@ is used, you can create network
symbols using the CX-Programmer, import them into the Network Configura-
tor, and then create tags and tag sets. Use the following procedure.
Creating Global Symbols Create global symbol with the Global Symbol Editor of the CX-Programmer
and select Input or Output for the network variable properties. Safe the project
when you are finished.
Any global symbols with Input or Output set for the network variable property
will be imported when the import procedure is performed from the Edit Device
Parameters Dialog Box.
Importing Symbols to the
Network Configurator
1,2,3... 1. Start the CX-Programmer and open the project that was saved.
Note When multiple copies of the CX-Programmer are running at the same time, it
is possible to import only from the CX-Programmer project that was started
first. If the global symbols that are to be imported are stored in multiple CX-
Programmer project files, the projects must be started one by one to import
the symbols.
2. From the devices registered in the Network Configurator, double-click the
icon of the device for which to import the network symbols. The Edit Device
Parameter Dialog Box will be displayed. You can also right-click the icon
and select Device - Parameters - Edit from the pop-up menu.
3. Click the Import Button on the Tag Sets Tab Page of the Edit Device Pa-
rameter Dialog Box.
137
Setting Tag Data Links Section 6-2
A confirmation message will be displayed. Click the Yes Button.
The symbols will be imported as shown below on the Tag Sets Tab Page.
Each symbol will be imported into a different tag set and the device param-
eters will be automatically edited. (The symbol name will be used for the
tag set name.)
138
Setting Tag Data Links Section 6-2
To place more than one input symbol (input tag) imported from the CX-
Programmer into one tag set, you must delete the input tags that were reg-
istered to separate input tag sets.
Select the tag sets for the symbols that are included in the one tag set and
click the Delete Button. A confirmation message will be displayed. Click
the No Button to delete only the tag sets.
To create a new tag set for more than one tag, click the New Button. To
place more than one tag in an existing tag set, double-click the tab set, or
select it and click the Edit Button.
The Edit Tag Set Dialog Box will be displayed. Imported tags that are not
registered in another tag set will be displayed in the Candidate Tag List
Area on the right. Click the Right Arrow Button to add tags individually.
139
Setting Tag Data Links Section 6-2
4. You can change tag set names in this dialog box. To confirm a change, click
the OK Button in the dialog box.
5. Perform steps 1 to 3 for all the devices that will perform tag data links.
3. Importing Network Symbols That Were Registered to Tags with the Network
Configurator to the CX-Programmer
If the CJ2H-CPU6@-EIP or CJ2M-CPU3@ is used, you can specify network
symbols for tags using the Network Configurator. The procedure to import net-
work symbols that were created using the Network Configurator into the CX-
Programmer is described below.
Exporting Tags and Tag Sets with the Network Configurator
1,2,3... 1. Select To/From File - Export to file on the Tag Sets Tab Page in the Edit
Device Parameters Dialog Box to export the tag and tag set information to
a CSV file.
140
Setting Tag Data Links Section 6-2
Importing the Tag and Tag Set CSV File with the CX-Programmer
1,2,3... 1. In the project global symbol table for the CJ2H-CPU6@-EIP or CJ2M-
CPU3@, right-click and select Import Network Variable from the pop-up
menu.
2. You can add a tag as a network symbol by selecting and executing the CSV
file exported using the Network Configurator.
Note The following precautions apply when importing.
• Tags that have a specified I/O memory address cannot be imported.
• Tags are imported as network symbols in a one-dimensional WORD
array. To change the data type, use the Symbol Editor of the CX-Program-
mer.
141
Setting Tag Data Links Section 6-2
6-2-5 Connection Settings
After creating the tag sets, click the Connections Tab at the top of the Edit
Device Parameters Dialog Box, and set the following connection information.
• The target devices with which connections will be opened
• Whether the tag sets are input or output tag sets
• The length of the packet intervals (RPI)
Make the Connections settings in the originator only. The Connections set-
tings are not necessary in the target device.
Note Make the Connections settings after creating tag sets for all of the devices
involved in tag data links.
Connection Settings (Connections Tab)
Registering Devices in the Register Device List
1,2,3... 1. Display the originator device’s Edit Device Parameters Dialog Box by dou-
ble-clicking the device’s icon in the Network Configuration Window, or
right-clicking the device’s icon and selecting Parameter - Edit from the
pop-up menu.
2. Click the Connections Tab at the top of the Edit Device Parameters Dialog
Box. All of the devices registered in the network (except the local node) will
be displayed.
142
Setting Tag Data Links Section 6-2
3. In the Unregister Device List, select the target device that requires connec-
tion settings by clicking the device so its color changes to gray, and click
the Button. The selected target device will be displayed in the Reg-
ister Device List, as shown in the following diagram.
4. Target node IDs are assigned to devices registered in the Register Device
List. This target node ID determines the location in the originator node PLC
of the Target Node PLC Operating Flag, Target Node PLC Error Flag, Reg-
istered Target Node Flag, and Normal Target Node Flag. By default, the
target ID is automatically set to the rightmost 8 bits of the IP address. In
the example above, the target device’s IP address is 192.168.250.2, so the
device number is #002. If a target node ID is duplicated and you want to
change the device number, click the Change Target Node ID Button and
change the target ID.
Editing Settings for
Individual Connections You can edit each connection separately.
Note Refer to the following page for information on how to perform batch editing in
a table format.
143
Setting Tag Data Links Section 6-2
1,2,3... 1. Select the Connection Tab and then click the New Button.
The following Edit Connection Dialog Box will be displayed according to the
type of device that is selected.
Using an OMRON EtherNet/IP Unit or Built-in EtherNet/IP Port as the
Target
Using Other EtherNet/IP Devices as the Target
144
Setting Tag Data Links Section 6-2
The settings are as follows:
2. When the settings have been completed, press the Regist Button.
Connections Settings
(Editing All Connections) The connection settings between the originator and all of the target devices
selected in the Register Device List can be edited together in a table.
1,2,3... 1. Select the Connections Tab, and click the Edit All Button. The following
Edit All Connections Dialog Box will be displayed.
Item Description
Connection I/O Type When creating tag data links for a CS1W-EIP21, CJ1W-EIP21,
CJ2B-EIP21, or CJ2M-EIP21, select Input Only (Tag Type).
When creating tag data links for other target devices, select
the connection I/O type specified in that device’s EDS file.
Use the Input Only (ID type) setting when another company's
node is the originator and does not support connection set-
tings with a Tag type setting.
Connection Type Selects whether the data is sent in multicast or unicast (point-
to-point). The default setting is multicast.
• Multicast connection
Select this type when the same data is shared by multiple
nodes. This setting is usually used.
• Point-to-Point connection
Select this type when the same data is not shared by multiple
nodes. In a unicast connection, other nodes are not bur-
dened with an unnecessary load.
Note Refer to 6-1-2 Overview of Operation for details on
using multicast and unicast connection as well as count-
ing the number of connections.
The Connection Structure Field and the following items will not be displayed if the
Hide Detail Button is pressed.
Packet Interval (RPI) Sets the data update cycle (i.e., the packet interval) of each
connection between the originator and target. The interval can
be set to between 1 and 10,000 ms for the CJ2M and 0.5 and
10,000 ms for other CPU Units in 0.5-ms increments. The
default setting is 50 ms (i.e., data updated once every 50 ms).
Timeout Value Sets the time until a connection times out. The timeout value is
set as a multiple of the packet interval (RPI) and can be set to
4, 8, 16, 32, 64, 128, 256, or 512 times the packet interval. The
default setting is 4 times the packet interval (RPI).
Connection Name Sets a name for the connection. (32 characters max.)
145
Setting Tag Data Links Section 6-2
The following table describes the various settings in the dialog box.
2. When the settings are completed, click the OK Button.
Setting Function
Target Device Selects the target device.
Connection
Name Any name can be given to the connection (up to 32 charac-
ters).
If this field is left blank, a default name will be assigned.
This Connection Name can be used for comments.
Connection I/O
Type When making tag data links in a CS1W-EIP21, CJ1W-EIP21,
CJ2B-EIP21, or CJ2M-EIP21, select Input Only (Tag type).
When making tag data links in other devices, select the con-
nection I/O type specified in that device’s EDS file.
Use the Input Only (ID type) setting when another company’s
node is the originator and does not support connection set-
tings with the Tag type setting.
In/Out The connections I/O is automatically displayed based on the
selected connection.
• Input Only: Just In is displayed.
Target Variable Selects and allocates the target node’s tag set.
• In: Selects the target’s output (produce) tag set.
• Out: Selects the target’s input (consume) tag set.
Originator Vari-
able Selects and allocates the originator node’s tag set.
• In: Selects the originator’s output (produce) tag set.
• Out: Selects the originator’s input (consume) tag set.
Connection
Type Selects whether the data is sent in a multicast or unicast. The
default setting is multicast.
• Multicast connection:
Select when the same data is shared by multiple nodes. This
setting is usually selected.
• Point-to-Point connection:
Select when the same data is not being shared by multiple
nodes. In a unicast transmission, other nodes are not bur-
dened with an unnecessary load.
Note Refer to 6-1-2 Overview of Operation for details on
using multicast and unicast transmissions, and counting
the number of connections.
RPI Sets the packet interval (RPI) of each connection between the
originator and target. The interval can be set between 1 and
10,000 ms for the CJ2M and 0.5 and 10,000 ms for other CPU
Units in 0.5-ms units. The default setting is 50 ms (data
refreshed once every 50 ms).
Timeout Value Sets the time until a connection timeout is detected. The time
out value is set as a multiple of the packet interval (RPI) and
can be set to a 4, 8, 16, 32, 64, 128, 256, or 512 multiple. The
default setting is 4× the packet interval (RPI).
146
Setting Tag Data Links Section 6-2
Confirming the
Connections Settings
1,2,3... 1. An overview of the connections set in the Register Device List is displayed
in the Connections Tab Page.
2. Click the OK Button. The following kind of diagram will be displayed.
3. Repeat the Connections setting procedure until all of the connections have
been set.
Note After completing the settings, always click the OK Button before
closing the Edit Device Parameters Dialog Box and performing an-
other operation. If the Cancel Button is clicked and the dialog box
is closed, the new settings will be discarded.
Indicates the IP address of the
originator where the connection
was set.
147
Setting Tag Data Links Section 6-2
4. If the tag set’s size is changed in either the originator or target after the
connection was set, the size will not match the other node and a parameter
data mismatch will occur. In this case, if the connection settings have been
changed, be sure to check the connections. (Refer to 6-2-17 Checking
Connections.)
Automatically Setting
Connections Tag set names set for devices can be automatically detected to automatically
set connections between input and output tag sets with the same name (or
the same names excluding specified ellipses). Connections are automatically
set under the following conditions.
Example 1: Automatic Connections with the Same Tag Set Names
The following connections would automatically be set if there is an output tag
set named A_Signal at node A and input tag sets named A_Signal at nodes B
and C.
Output tag set names Except for specified ellipses, the output tag set name
must be the same as the input tag set name.
Ellipses can be set for the beginning or end of tag set
names.
Input tag set names Except for specified ellipses, the input tag set name
must be the same as the output tag set name.
Ellipses can be set for the beginning or end of tag set
names.
Connection types The connection type must be Input Only.
Multicast and single cast connection types can be
specified when executing a connection.
RPI The default setting is used.
Timeouts The default setting is used.
Connection
EtherNet/IP
Output tag set: A_Signal
Node A
Input tag set: A_Signal
Node B
Input tag set: A_Signal
Node C
Connection
Excluded characters: None
148
Setting Tag Data Links Section 6-2
Example 2: Automatic Connections with the Ellipses
The following connections would automatically be set if there is an output tag
set named O_Signal at node A and input tag sets named I_Signal at nodes B
and C, and “O_” and “I_” were set as ellipses.
1,2,3... 1. Set the same tag set names for the output and input tag sets for the con-
nection. The tag set names can also include forward and backward el-
lipses.
2. Select Auto Connection from the Network Menu. The connections will be
set automatically.
A dialog box will appear to set forward and backward ellipses for both out-
put (product) and input (consume) tag sets as soon as automatic connec-
tion setting processing has begun.
Input the ellipses and click the OK Button. Automatic setting will be pro-
cessed.
3. If there are tag sets that meet the conditions for automatic connection set-
ting, they will be displayed.
Connection
EtherNet/IP
Node A Node B Node C
Connection
Output tag set: O_Signal Input tag set: I_Signal Input tag set: I_Signal
Excluded characters: O_ and I_
149
Setting Tag Data Links Section 6-2
Click the OK Button to start processing.
4. A device connection structure tree will be displayed when processing has
been completed.
5. Use the device connection structure tree as required to change the RPI
and timeout settings.
Device Connection
Structure Tree Connection settings can be displayed on the network configuration. Select
View Device’s Connection Structure Tree from the Network Menu.
150
Setting Tag Data Links Section 6-2
•The Display the detail of Connection Check Box can be used to switch
between device-level and connection-level displays of tag data link com-
munications.
• An asterisk will be displayed after the device name of the originator set for
the connection.
• The Edit Device Parameters Dialog Box can be displayed by selecting a
connection and clicking the Edit Button. The connections can be edited in
this dialog box.
6-2-6 Setting Tags Using Data Link Tool
Using the EtherNet/IP Datalink Tool enables easily setting data links similar to
those for the Controller Link by using only I/O memory addresses. This
method has the following restrictions.
• Settings can be made only for tag data links between OMRON EtherNet/
IP Units and built-in EtherNet/IP ports.
• Tags must be set using I/O memory addresses.
• A maximum of two tags (area 1 and area 2) can be set in one tag set.
Select Network - EtherNet/IP Datalink Tool from the menus in the Network
Configurator after you have registered all the devices to start the EtherNet/IP
Datalink Tool.
151
Setting Tag Data Links Section 6-2
Node List The following items will be displayed in the Node Area on the left side of the
window.
• IP Address: The IP address of the node.
• Device: The name (model number) of the device at the node.
Note The node list will display the node registered in the Network Configurator.
Nodes cannot be added or deleted from this window.
Data Link Table
Information The data link table of the node selected on the left will be displayed on the
right. Each row specifies word that are allocated for data links for that node.
Each row specifies the node settings for the words (area) where a data link
has been created. You can set only area 1 or both area 1 and area 2.
• IN/OUT: Specifies whether the link inputs data to the node or outputs data
from the node. OUT can be selected only once. Once OUT has been
selected for one row, IN will automatically be selected for other rows. A
asterisk will be displayed if the Over Load function is disabled. (See note.)
Note The Over Load function is used to clear output data when all out-
puts are turned OFF from the CPU Unit of the PLC. This setting is
not necessary for inputs.
(a) Over Load function enabled: Output data will be cleared to all ze-
ros when all outputs from the PLC are turned OFF from the CPU
Unit.
(b) Over Load function disabled: Output data will be maintained even
when all outputs from the PLC are turned OFF from the CPU Unit.
• Area 1, Link CH: The I/O memory address of the first word in link area 1
• Area 1, Size: The number of words in link area 1. (See note.)
• Area 2, Link CH: The I/O memory address of the first word in link area 2
• Area 2, Size: The number of words in link area 2. (See note.)
Note With the Network Configurator, the PLC status will be shown at the
beginning of each area. The PLC status includes the CPU Unit op-
erating status (operating information and error information).
152
Setting Tag Data Links Section 6-2
• Tag Set Name: If the Wizard is used, the names will be automatically
assigned using consecutive IP addresses in the following form for both
input and output tags: TagSet1_192168.250.1. There is no reason to be
concerned with these names. If the Wizard is not used, then names will
not be automatically assigned and they must be entered directly into the
data link table.
• Total Size: The total number of words in areas 1 and 2. This value is auto-
matically displayed after the sizes of areas 1 and 2 are entered.
• Node: For an input tag, this is the IP address of the node that provides the
output. For an output tag, “-” will be entered automatically.
• Target Variable: The target tag set name. For an input tag, this is the
name of the target set that provides the output. For an output tag, “-” will
be entered automatically.
• RPI (ms): The requested packet interval for an input tag. For an output
tag, “-” will be entered automatically.
Setting Procedure The setting procedure is described here along with setting examples.
■Setting Example A
Area 1 memory area = Work Area (W)
Area 1 start address = 0
Area 1 size = 50 words
Area 2 memory area = DM Area (D)
Area 2 start address = 50
Area 2 size = 100 words
■Allocations
1,2,3... 1. Select Wizard from the Data Link Menu. The Datalink Wizard Dialog Box
will be displayed.
Area 1
Node 1
(IP address: 192.168.250.1)
Area 2
#1
#2
#3
#1
#2
#3
#3
#1
#2
Node 3
(IP address: 192.168.250.3)
#3
#1
#2
#2
#1
#3
Node 2
(IP address: 192.168.250.2)
#2
#1
#3
EtherNet/IP
W0
50 words
W50
50 words
W100
50 words
D50
100 words
D150
100 words
D250
100 words
W0
W0
D50 D50
153
Setting Tag Data Links Section 6-2
2. Select the memory area (here, W) in the Memory Field and enter the start-
ing address (here, 0) and number of words (here, 50) in the Start Address
and Size Fields for Area 1.
3. Select the memory area (here, D) in the Memory Field and enter the start-
ing address (here, 50) and number of words (here, 100) in the Start Ad-
dress and Size Fields for Area 2.
4. Select the Enable Over Load Check Box if the Over Load function is nec-
essary.
5. Click the OK Button. The following dialog box will be displayed.
Click the Yes Button to continue creating the data link table, or click the No
Button to cancel the operation.
154
Setting Tag Data Links Section 6-2
If the creating the data link table is continued, the data link table will be cre-
ated with the same size of data link for all registered nodes. Examples are
shown below.
Automatic Allocation Results for Node 1 (IP Address: 192.168.250.1)
Automatic Allocation Results for Node 2 (IP Address: 192.168.250.2)
155
Setting Tag Data Links Section 6-2
Automatic Allocation Results for Node 3 (IP Address: 192.168.250.3)
6. After entering all of the settings in the data link table, select Save from the
File Menu. A consistency check will be performed on the table and the re-
sults will be displayed.
a. Table Inconsistencies
The following Check Result Dialog Box will be displayed. Correct the data
link table according to the displayed information.
To save the check results, click the Copy To Clipboard Button and paste
the results to other file, such as the text pad.
Click the OK Button. The following message will be displayed. Click the OK
Button again to return to the EtherNet/IP Datalink Tool Window.
156
Setting Tag Data Links Section 6-2
b. No Table Inconsistencies
The following message will be displayed. Click the OK Button.
7. Select Exit from the File Menu. The EtherNet/IP Datalink Tool will be exited
and you’ll return to the Network Configurator.
8. Returning to the Network Configurator
Click the icon for each device and check the settings made with the Ether-
Net/IP Datalink Tool in the Edit Device Parameters Dialog Box.
6-2-7 Creating Connections Using the Wizard
You can use the Network Configurator's Wizard to easily create connections
between OMRON PLCs following the instructions provided by the Wizard.
Network Configurator version 3.10 or higher is required to use the Wizard.
Note The Wizard can be used only with the following OMRON EtherNet/IP devices.
Use the following procedure to create connections (i.e., data links) with the
Wizard.
1,2,3... 1. Set tags and tag sets for all devices before starting the Wizard. Refer to 6-
2-4 Creating Tags and Tag Sets for the setting procedure.
2. For tag data links between OMRON PLCs, a connection is created in the
PLC (i.e., the originator device) that receives data as input data.
First, select the registered device for which you want to create a connec-
tion in the Network Configuration Window of the Network Configurator, and
then select Device - Parameters - Wizard from the menus.
Device name Remarks
CJ1W-EIP21 CJ1W-EIP21 mounted to CJ1 CPU Unit
CJ1W-EIP21(CJ2) CJ1W-EIP21 mounted to CJ2 CPU Unit
CJ2B-EIP21 Built-in EtherNet/IP port in CJ2H CPU Unit
CJ2M-EIP21 Built-in EtherNet/IP port in CJ2M CPU Unit
CS1W-EIP21 CJ1W-EIP21 mounted to CS1 CPU Unit
157
Setting Tag Data Links Section 6-2
The following dialog box will be displayed before the Wizard starts.
Click the Yes Button to delete the connections that have been set with OM-
RON PLCs before starting the Wizard.
3. Create the connection following the instructions that are given by the Wiz-
ard after the Wizard starts. (See the following figure.)
4. A list of tag sets is displayed on the right side of the Wizard Dialog Box with
target devices that support receiving input data.
Select the tag sets that you want to receive at the originator device.
The following tables describes the meanings of the icons and check marks
displayed in the tag set list.
Note Tag sets that are used in connections that are already set are not displayed.
Icon Display position Status
All All output tag sets for all devices are selected.
Device All output tag sets for the applicable device are
selected.
Tag set The applicable output tag sets are selected. These
are the tag sets that will be set in the connection.
All All or some output tag sets for some devices are
selected.
Device Some output tag sets for applicable devices are
selected.
All All output tag sets for all devices are not selected.
Device All output tag sets for applicable devices are not
selected.
Tag set The applicable output tag sets are not selected.
The connections for this tag set will be deleted.
Device No applicable tag sets.
158
Setting Tag Data Links Section 6-2
The following display will appear when you click the Show Detail Button.
The specified values for detailed parameters will be displayed. Change the
values as required. The connection name cannot be set. They are automati-
cally created using the following rule.
default_N (where N is a 3-digit number (001, 002, etc.) starting from 1)
5. Click the Next Button to switch to the table in the following Wizard Dialog
Box. Follow the instructions to select and input from the list box the input
tag set of the originator device that receives the output tag set of the target
device.
• The blank area in the Input Tag Set Column is the connection that you are
creating.
• The rows in which there are input tag sets are connections that are
already set.
• To prevent duplicate settings, input tag sets that have been used are not
displayed in the list box for input tag sets.
• If there is no applicable input tag set, you can edit a tag set or create a
new one by using the Edit Tag Sets Button and Edit Tag Button.
6. Once the input tag set settings have been completed, click the Finish But-
ton. You can check the set connection by selecting Network - View Devic-
es Connection Structure Tree from the menus.
• The Wizard can be ended even if the input tag set includes a blank row. In
that case, a connection is not created for the blank row.
• You can delete a connection by deleting the input tag sets that were previ-
ously set.
159
Setting Tag Data Links Section 6-2
6-2-8 Creating Connections by Device Dragging and Dropping
You can create a connection to the originator by dragging a target device and
dropping it at the originator device. Network Configurator version 3.10 or
higher is required to drag and drop devices to make connections.
Example: Drag the target device at 192.168.250.1 and drop it at the orig-
inator device at 192.168.250.100.
Note The EtherNet/IP originator device (i.e., a device in which connections can be
set) must be one of the following OMRON EtherNet/IP devices.
Use the following procedure to create connections (i.e., data links) by drag-
ging and dropping devices.
1,2,3... 1. Set the tags and tag sets for the target device that will be dragged.
a. Refer to 6-2-4 Creating Tags and Tag Sets for information on creating
the settings if the target is one of the OMRON EtherNet/IP devices giv-
en above.
b. If the target is another EtherNet/IP device, refer to the manual of that
device and perform settings as required.
2. A dialog box as in the following figure for connection allocation will be dis-
played when you drag the target device and drop it at the OMRON Ether-
Net/IP device.
a. Using One of the Above OMRON EtherNet/IP Devices As Target
Select the output tag set from Target Device Area on the right side of
the Edit Connection Dialog Box, and then select the input tag set to re-
ceive the output tag set in the Originator Device Area on the left.
Drag & Drop
Device name Remarks
CJ1W-EIP21 CJ1W-EIP21 mounted to CJ1 CPU Unit
CJ1W-EIP21(CJ2) CJ1W-EIP21 mounted to CJ2 CPU Unit
CJ2B-EIP21 Built-in EtherNet/IP port in CJ2H CPU Unit
CJ2M-EIP21 Built-in EtherNet/IP port in CJ2M CPU Unit
CS1W-EIP21 CJ1W-EIP21 mounted to CS1 CPU Unit
160
Setting Tag Data Links Section 6-2
• If there is no applicable input tag set at the originator, you can create
a new one by using the Edit Tag Sets Button and Edit Tag Button.
b. Using Other EtherNet/IP Devices as Target
The connection I/O type list box in the upper part of the Connection
Settings Dialog Box displays the connection I/O types that can be se-
lected. Select the connection I/O type according to your application.
• The connection I/O types that can be selected depend on the target
device.
• Items that can be selected will depend on the connection I/O type that
is selected.
• Select the output, input, or both output and input tag sets at the target
and specify the corresponding input, output, or both input and output
tag sets at the originator.
• If there is no applicable tag set at the originator, you can create a new
one by using the Edit Tag Sets Button and Edit Tag Button.
The following display will appear when you click the Show Detail But-
ton.
The specified values for detailed parameters will be displayed. Change
the values as required. Connection names are automatically created
using the following rule.
default_N (where N is a 3-digit number (001, 002, etc.) starting from 1)
161
Setting Tag Data Links Section 6-2
Note The following dialog box will be displayed if a target device that does not have
I/O data is dropped.
Before dropping again, refer to the manual of the applicable device and create
the I/O data (i.e., output tag sets) required to create a connection.
3. After you have set all of the connection, click the Regist Button to create
the connection. When creating the connection has been completed, the in-
put tag set and output tag set will be blank. Next, you can continue to cre-
ate connections by selecting the connection I/O type and setting a tag set.
6-2-9 Connecting the Network Configurator to the Network
This section explains how to connect the Network Configurator to the network.
Connecting through
Ethernet
Note The Windows firewall settings must be changed when making this connection
for the first time in Windows XP, Vista, or Windows 7. For details on changing
the firewall settings, refer to Appendix G Precautions for Using Windows XP,
Vista, or Windows 7.
Connect to the EtherNet/IP Unit’s Ethernet port via the Ethernet network.
1,2,3... 1. Select Option - Select Interface - Ethernet I/F.
2. Select Network - Connect.
If there are multiple Ethernet interfaces on the computer, the Select Con-
nect Network Port Dialog Box will be displayed. Select the interface that is
to be connected, and press the OK Button.
The following dialog box will be displayed.
3. Click the OK Button. Select the network to be connected.
162
Setting Tag Data Links Section 6-2
The Network Configurator will connect to the EtherNet/IP network. If the
Network Configurator is connected online properly, On-line will be dis-
played in the status bar at the bottom of the window. The network connec-
tion icon will be displayed in blue in the Network Tab Page in which the
Network Configurator is connected.
The connecting network can be switched by selecting Network - Change
Connect Network.
Connecting through the CPU Unit’s Peripheral or RS-232C Port
Connect to the EtherNet/IP Unit’s Ethernet port via the CPU Unit’s peripheral
port or RS-232C port.
1,2,3... 1. Select Option - Select Interface - CS/CJ1 Serial Port → EIP Unit I/F.
2. Select Network - Connect. The following dialog box will be displayed.
Network connection icon
163
Setting Tag Data Links Section 6-2
3. Input the EtherNet/IP Unit’s unit number in the Unit No. Field, select the
connecting COM port number, and click the OK Button.
Usually, the Baud Rate is left at this setting.
The following dialog box will be displayed.
4. After clicking TCP:2, click the OK Button. The Network Configurator will be
connected to the EtherNet/IP network. If the Network Configurator is con-
nected online properly, On-line will be displayed in the status bar at the bot-
tom of the window.
Connecting through the CPU Unit’s USB or RS-232C Port (CJ2 CPU Units Only)
Connect to the EtherNet/IP Unit’s Ethernet port via the CPU Unit’s USB port
or RS-232C port.
1,2,3... 1. Select Option - Select Interface - CJ2 USB/Serial Port to set the com-
munications interface.
164
Setting Tag Data Links Section 6-2
2. Select Network - Connect. The Setup Interface Dialog Box will be dis-
played.
3. Set the port type to either USB or serial.
4. Set the port to use and then click the OK Button. (Leave the baud rate at
the default setting.)
The following dialog box will be displayed.
5. Select the Backplane Icon and click the Refresh Button.
The CPU Unit, CPU Bus Units, and Special I/O Units connected in the PLC
will be displayed as shown below.
6. Click the + icon to the left of the EtherNet/IP Unit or built-in EtherNet/IP port
(CJ1W-EIP21(CJ2) or CJ2B-EIP21). The TCP ports on the EtherNet/IP
Unit will be displayed as shown below.
165
Setting Tag Data Links Section 6-2
7. Select the port for the EtherNet/IP Unit and then click the OK Button. The
Network Configurator will be connected to the EtherNet/IP network. If the
Network Configurator goes online normally, “On-line” will be displayed in
the status bar at the bottom of the window.
Connecting to an EtherNet/IP Network via an Ethernet Unit
Note (1) Windows firewall settings must be changed when this connection is made
for the first time using Windows XP (SP2 or higher), Vista, or Windows 7.
Refer to Appendix G Precautions for Using Windows XP, Vista, or Win-
dows 7: Using EtherNet/IP with Windows XP, Vista, or Windows 7 for in-
formation on how to make the changes.
(2) Use the CX-Integrator to correctly set the FINS routing tables for the CS/
CJ-series CPU Unit that will be the relay node.
1,2,3... 1. Select Option - Select Interface - Ethernet
→
CS/CJ1 ETN-EIP Unit I/F.
Select the TCP port of the EtherNet/IP Unit.
Network Configurator on
Windows computer
Ethernet Unit
Ethernet
EtherNet/IP Unit
CS/CJ-series
CPU Unit
EtherNet/IP Unit or built-in EtherNet/IP port
CS/CJ-series
CJ2 CPU Unit
EtherNet/IP
166
Setting Tag Data Links Section 6-2
2. Select Network - Connect.
The following Setup Interface Dialog Box will be displayed.
3. Click the Setup Button in the Setup Interface Dialog Box. The Registration
of the connection Dialog Box will be displayed. Enter the network informa-
tion for the connection destination, and then click the Add Button to regis-
ter the settings.
The registration information details are as follows:
a. Registration name
Enter any name.
b. Host (PC) information
Enter information for the computer that has the Network Configurator
installed.
• Network address
Same number as the network address of the Ethernet Unit of the PLC
that will be the relay node.
• Node address
Last value in the computer's IP address (e.g., 1 for 192.168.250.1)
c. Remote Information - EtherNet/IP Unit
Enter the information for the EtherNet/IP Unit of the PLC that will be
the relay node.
• Network address
Network address set in the routing tables
167
Setting Tag Data Links Section 6-2
• Node address
Last value in the IP address of the Unit above (e.g., 3 for
192.168.251.3)
• Unit number of CPU Bus Unit
Unit number of the Unit above
d. Remote Information - Ethernet Unit
Enter the information for the Ethernet Unit of the PLC that will be the
relay node.
4. Once the settings have been registered, the Setup Interface Dialog Box will
be displayed again. Check the registered information that has been en-
tered, and then click the OK Button.
5. The following dialog box will be displayed. Select TCP:2, which represents
the EtherNet/IP port, and then click the OK Button.
The Network Configurator will connect to the EtherNet/IP network, and
“On-line” will be displayed in the status bar at the bottom of the window
when connection has been properly made online.
Note A list of nodes on the EtherNet/IP network you are attempting to connect to
will be displayed when the Refresh Button or the icon ( ) at the left of TCP:2
168
Setting Tag Data Links Section 6-2
is clicked in the dialog box above. (Refer to the following figure.)
6-2-10 Downloading Tag Data Link Parameters
To make tag data links, you must download tag data link parameters, such as
tag set settings and connection settings, to all devices in the EtherNet/IP net-
work. When the download operation is executed, the tag data link parameters
will be transferred to the EtherNet/IP Units that require the settings.
The following procedure shows how to download the tag data link parameters.
Refer to 6-2-9 Connecting the Network Configurator to the Network for infor-
mation on how to connect the Network Configurator to the network.
Note • If the target node IP address is not set correctly, invalid device parameters
may be set in the wrong PLC. Check the connected PLC before down-
loading parameters.
• If incorrect tag data link parameters are set, it may cause equipment to
operate unpredictably. Even when the correct tag data link parameters are
set, make sure that there will be no effect on equipment before transfer-
ring the data.
• When network symbols are used in tag settings, a connection error will
result if the symbols are not also set in the CPU Unit. Before downloading
the tag data link parameters, check to confirm that the network symbols
have been set in the CPU Unit. On the Connection and Tag Status Tab
Pages described in 14-1-1 The Network Configurator’s Device Monitor
Function, check whether the network symbol, tag, and connection set-
tings are correct.
• When a communications error occurs, the output status depends on the
specifications of the Unit being used. When a communications error
occurs for a Unit that is used along with output devices, check the operat-
ing specifications and implement safety countermeasures.
• The EtherNet/IP Unit is automatically restarted after the parameters have
been downloaded. This restart is required to enable the tag set and con-
nection information that have been set. Before downloading the parame-
ters, check to confirm that restarting will not cause any problems with the
equipment.
• Do not disconnect the Ethernet cable or reset or turn OFF the power to
the EtherNet/IP Unit while the parameters are being downloaded
• For EtherNet/IP Units or built-in EtherNet/IP ports with revision 2 or later,
the CPU Unit can download tag data link parameters in either RUN mode
or MONITOR mode. (They can also be downloaded in PROGRAM mode.)
• For EtherNet/IP Units with revision 1, tag data link parameters can be
downloaded only when the CPU Unit is in PROGRAM mode.
• Even for Units with revision 2 or later, all CPU Units must be in PRO-
GRAM mode to download the parameters if any Units with revision 1 are
included in the network.
169
Setting Tag Data Links Section 6-2
1,2,3... 1. Connect the Network Configurator online.
2. There are two ways to download the parameters.
• Downloading to All Devices in the Network
Select Network - Download. The following dialog box will be displayed.
• Downloading Individually to Particular Devices
Select the icon of the EtherNet/IP Unit to which you want to download. To
select multiple nodes, press and hold the Shift Key while selecting addi-
tional icons. (In the following example, 2 nodes are selected:
192.168.250.1 and 192.168.250.2.)
After selecting the icons, click the right mouse button over the icon to dis-
play the pop-up menu, and select Parameter - Download.
The following dialog box will be displayed.
3. Click the Yes Button to download the tag data link parameters to the Eth-
erNet/IP Unit.
The following dialog box will be displayed if any of the CPU Units is not in
PROGRAM mode.
• Display When All EtherNet/IP Units and Built-in EtherNet/IP Ports are
Revision 2 or Higher
170
Setting Tag Data Links Section 6-2
If the Download after changed to Program mode Button is clicked, all
CPU Units will be changed to PROGRAM mode and the parameters will
be downloaded. Confirm safety for all controlled equipment if the CPU
Units are changed to PROGRAM mode. The operating mode can be re-
turned to the previous setting after the parameters have been downloaded.
The Download with Current mode Button can be clicked to download
load the parameters even when one or more CPU Units is in RUN or MON-
ITOR mode.
• Display When Even One EtherNet/IP Unit Is Revision 1
When the Download after changed to Program mode Button is clicked,
all CPU Units will be changed to PROGRAM mode and the parameters will
be downloaded. Confirm safety for all controlled equipment if the CPU
Units are changed to PROGRAM mode. The operating mode can be re-
turned to the previous setting after the parameters have been downloaded.
During the download, the following progress monitor will be displayed to
show the progress of the download.
171
Setting Tag Data Links Section 6-2
If the operating mode of one or more CPU Units was changed to download
the parameters, the CPU Units can be returned to the previous operating
mode. If the No Button is clicked, the CPU Units will remain in PROGRAM
mode.
4. The following dialog box will be displayed, indicating that the download was
completed.
6-2-11 Uploading Tag Data Link Parameters
Tag data link parameters (such as the tag set settings and connection set-
tings) can be uploaded from EtherNet/IP Units in the EtherNet/IP network.
The following procedure shows how to upload the parameters. For details on
connecting to the network from the Network Configurator, refer to 6-2-9 Con-
necting the Network Configurator to the Network.
1,2,3... 1. Connect the Network Configurator to the network.
2. There are two ways to upload the parameters.
• Uploading from All Devices in the Network
Select Network - Upload. The following dialog box will be displayed.
• Clicking the Yes Button:
Parameters will be uploaded only from the devices registered in the Net-
work Configuration Window. Parameters will not be uploaded from devices
that are not registered in the Network Configuration Window.
• Clicking the No Button:
• If parameters are being uploaded from all devices in the network, the
parameters will be newly uploaded from all devices. The current net-
work configuration information will be lost.
• If parameters are being uploaded from specified devices only, the up-
load operation will be cancelled and the upload will not be performed.
• Clicking the Cancel Button:
The upload operation will be cancelled and the upload will not be per-
formed.
• Uploading Individually from Particular Devices
172
Setting Tag Data Links Section 6-2
Select the icon of the EtherNet/IP Unit from which you want to upload. To
select multiple nodes, press and hold the Shift Key while selecting addi-
tional icons. (In the following example, 2 nodes are selected:
192.168.250.1 and 192.168.250.2.)
After selecting the icons, click the right mouse button over the icon to dis-
play the pop-up menu, and select Parameter - Upload.
The following confirmation dialog box will be displayed.
Click the Yes Button or No Button.
During the upload, the following progress monitor will be displayed to show
the progress of the upload.
3. The following dialog box will be displayed, indicating that the upload was
completed.
6-2-12 Verifying the Tag Data Links
Tag data link parameters (such as the tag set settings and connection set-
tings) can be compared with the EtherNet/IP Units in the EtherNet/IP network.
The following procedure shows how to compare the parameters. For details
on connecting to the network from the Network Configurator, refer to 6-2-9
Connecting the Network Configurator to the Network.
173
Setting Tag Data Links Section 6-2
Verifying the Network
Configuration Compare the list of registered devices in the Network Configuration Window
with the devices connected on the EtherNet/IP network, and check the IP
addresses and device types. This function cannot be used to verify device
parameters.
1,2,3... 1. Connect the Network Configurator to the network.
2. The following progress monitor will be displayed to show the progress as
data is read from the network and compared.
3. The results of the comparison between the network configuration file and
data from the network are displayed as follows.
• Differences Not Found in the Comparison
• Differences Found in the Comparison
• Differences Found in the Device Type.
174
Setting Tag Data Links Section 6-2
Click the OK Button or the Close Button.
Verifying the Device
Parameters Use the following procedure to compare the device parameters for the devices
selected in the Network Configuration Window with those of the devices con-
nected on the EtherNet/IP network. The IP addresses, device types, and
device parameters are compared.
1,2,3... 1. Connect the Network Configurator to the network.
2. Click the icon of the EtherNet/IP Unit that is to be verified. To select multiple
nodes, hold down the Shift Key while clicking the icons. (In the following ex-
ample, the 192.168.250.1 and 192.168.250.2 nodes are selected.)
With the icons selected, right-click and select Parameter - Verify from the
pop-up menu.
3. The following dialog box will be displayed.
Click the Yes Button or the No Button.
4. One of the following dialog boxes will be displayed.
• Differences Not Found in the Comparison
• Differences Found in the Comparison
175
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 dis-
played. Click the Yes Button.
The comparison results will be displayed in order of the selected nodes.
6-2-13 Starting 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
Configurator All tag data links on the network can be started and stopped by selecting I/O
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.
176
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-14 Clearing the Device Parameters
The device parameters saved in the EtherNet/IP Units in the EtherNet/IP net-
work can be cleared (returned to their default settings). The following proce-
dure 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 Net-
work 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.
177
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-box configuration, 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-15 Saving 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. Select File - Save As. The following dialog box will be displayed.
The File name Field will contain Untitled.nvf as the default file name.
2. Input the file name, and click the Save Button.
178
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 the
Button.
4. You can select the Select target network Check Box in the Option 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-16 Reading a Network Configuration File
A previously saved network configuration file can be read into the Network
Configurator.
179
Setting Tag Data Links Section 6-2
1,2,3... 1. Select File - Open or click the Button. 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.
180
Setting Tag Data Links Section 6-2
5. Select any of the options as necessary. The options are listed below.
Note The save format will vary depending on the Network Configurator version.
Configuration files (*.ncf) created using the Network Configurator for Ether-
Net/IP (version 2 or higher) can be imported (opened) by selecting External
Data - Import from the File Menu.
6-2-17 Checking 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 Di-
alog Box and click the Connection Tab. The inconsistent connection will
be displayed with a icon (instead of the normal icon). To change
the connection setting and select a different target variable, select the con-
nection as shown below and click the Edit Button.
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.
181
Setting Tag Data Links Section 6-2
6-2-18 Changing Devices
Devices that are registered in a network configuration with the Network Con-
figurator 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
6-2-19 Displaying 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.
Icon (When normal: )
Device after change CJ1W-
EIP21 CS1W-
EIP21 CJ1W-
EIP21 CS1W-
EIP21 CJ1W-
EIP (CJ2) CJ2B-
EIP21 CJ2M-EIP21
Device before change Revi-
sion 1.01 1.01 2.01 2.01 2.01 2.01 2.01
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-
ables in tags OK if no vari-
ables in tags --- OK OK if there are
less than 33 tags
CJ2B-EIP21 2.01 No No OK if no vari-
ables in tags OK if no vari-
ables in tags OK --- OK if there are
less than 33 tags
CJ2M-EIP21 2.01 No No OK if no vari-
ables in tags OK if no vari-
ables in tags OK OK ---
182
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-fatal error has occurred in the CPU Unit of the
PLC.)
(red) Alarm (A fatal error has occurred in the CPU Unit of the PLC.)
183
Ladder Programming with Tag Data Links Section 6-3
6-3 Ladder Programming with Tag Data Links
6-3-1 Ladder 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 set-
ting. 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 tar-
get device has been refreshed in the CPU Unit.
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-fatal error 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 Op-
tions in the Edit Tag Set Dialog Boxes. For details, refer to 6-3-2 Status
Flags Related to Tag Data Links.
Example of Programming
to Detect Normal Status The following programming can be used to confirm that normal communica-
tions 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.
184
Ladder Programming with Tag Data Links Section 6-3
Programming for Revision 2 or Higher
Programming for Revision 1 and Revision 2
Programming to Detect
Errors: Example 1 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
Programming to Detect
Errors: Example 2 The following programming can be used to detect tag data link errors at the
local node.
Tag Data Link
Operating
n+11 bit 01
Normal Target Node
Flag 1
n+20 bit 01
PLC Operating
Flag 1
n+2 bit 01
PLC Error
Flag 1
n+6 bit 01
Node 1 Data Link
Normal Operation Flag
Normal Target Node
Flag 2
n+20 bit 02
PLC Operating
Flag 2
n+2 bit 02
PLC Error
Flag 2
n+6 bit 02
Node 2 Data Link
Normal Operation Flag
Tag Data Link
Operating
n+11 bit 01
All Tag Data Links
Operating
n+12 bit 14
Normal Operation Flag
PLC Operating
Flag 1
n+2 bit 01
PLC Error
Flag 1
n+6 bit 01
Node 1 Data Link
Normal Operation Flag
PLC Operating
Flag 2
n+2 bit 02
PLC Error
Flag 2
n+6 bit 02
Node 2 Data Link
Normal Operation Flag
Tag Data Link
Operating
n+11 bit 01
Normal Target Node
Flag 1
n+20 bit 01
Node 1
Error output
Normal Target Node
Flag 1
n+20 bit 01
Node 1
Error output
Normal Target Node
Flag 2
n+20 bit 02
Node 2
Error output
Normal Target Node
Flag 2
n+20 bit 02
Node 2
Error output
185
Ladder Programming with Tag Data Links Section 6-3
Programming for Revision 1 or Higher
Example of Programming
to Process Data The following type of programming can be used to process data only when the
data links are operating normally.
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.
Tag Data Link
Operating
n+11 bit 01
Unit Error
Occurred
n+10 bit 00
Unit Error
Occurred
n+10 bit 00
10000
Local node
Error output
Release Flag
Local node
Error output
DIFD
10000
DIFU
10000
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.
Normal Operation
Flag
Additional part Normal Operation
Flag
Node A data processing
Node A Data Link
Normal Operation Flag
IL
ILC
Node B data processing
Node B Data Link
Normal Operation Flag
IL
ILC
Node C data processing
Node C Data Link
Normal Operation Flag
IL
ILC
186
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-2 Status 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
Information
Layout set to default settings:
Words n+2 to n+5
Layout set to user settings:
Words n+32 to n+47
Note Corresponds to the PLC
status’s PLC Operating
Flag.
Each flag indicates the operating status of the
corresponding target node PLC of connections
in which the EtherNet/IP Unit is the originator.
The flag corresponding to the target node’s tar-
get ID will be ON when the PLC Operating Flags
for all connections with that target node indicate
that the PLC is operating.
Each node address’s flag location (i.e., target ID)
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.
Target Node PLC Error Flag Infor-
mation
Layout set to default settings:
Words n+6 to n+9
Layout set to user settings:
Words n+48 to n+63
Note Corresponds to the PLC
status’s PLC Error Flag.
Each flag indicates the error status (logical OR
of non-fatal and fatal errors) of the corresponding
target node PLC of connections in which the Eth-
erNet/IP Unit is the originator. The flag corre-
sponding to the target node’s target ID will be
ON if even one error is indicated in any of the
connections with that target node.
Each node address’s flag location (i.e., target ID)
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
Layout set to default settings:
Words n+20 to n+23
Layout set to user settings:
Words n+16 to n+31
Note Does not correspond to the
PLC status.
Each flag indicates the connection status of the
corresponding target node PLC of connections
in which the EtherNet/IP Unit is the originator.
The flag corresponding to the target node’s tar-
get ID will be ON when connections are estab-
lished for all connections with that target node
indicate that the PLC is operating.
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.
187
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
188
Overview Section 7-1
7-1 Overview
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 con-
trol operation, e.g., by force-setting/resetting bits.
There are two types of messages: FINS messages and explicit messages.
Item FINS messages Explicit messages
Outline Message communications for
OMRON products that use the
FINS protocol.
Standard ODVA message communi-
cations using the CIP protocol.
Remote
device • Computer with an Ethernet inter-
face
• OMRON PLCs (with a CS/CJ-
series EtherNet/IP Unit, built-in
EtherNet/IP port, or Ethernet
Unit)
• Computer with an Ethernet inter-
face
• Another company’s masters or
slaves.
• OMRON PLCs (with a CS/CJ-
series EtherNet/IP Unit or built-in
EtherNet/IP port)
Features • Send and receive the various
FINS commands to provide an
even greater range of services
than the CIP UCMM messages.
• Provide transparency in mes-
sage communications with other
OMRON networks, such as Con-
troller Link, SYSMAC LINK, and
Ethernet.
(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)
• Supports message communica-
tions with other companies’ Ether-
Net/IP devices.
CS/CJ Series
• CS1W-EIP21
• CJ1W-EIP21
• CJ2H-CPU@@-EIP
• CJ2M-CPU3@
Message communications functions
FINS communications function
Explicit message
communications function
Send
Receive
Send
Receive
189
Overview Section 7-1
Overall Structure
Note With the EtherNet/IP Unit or built-in EtherNet/IP port, message communica-
tions are possible even if the I/O link function is disabled.
CPU Unit
CMND(490)
instruction
CMND(490)
instruction
(2810 Hex)
FINS message
FINS Explicit message
FINS
message
function
Explicit
message
function
FINS message
Explicit message
OMRON special message communication
s
EtherNet/IP message communications
EtherNet/IP Unit
Ethernet (EtherNet/IP) network
190
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-One or Fins Gateway applications),
and NS-series Programmable Terminals.
Note 1. When two or more Communications Units (including the EtherNet/IP Units
and built-in EtherNet/IP ports) are mounted to a CS/CJ-series PLC and
FINS messages are being used, the EtherNet/IP Units and built-in Ether-
Net/IP ports must be registered in the CS/CJ-series PLC’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-series EtherNet/IP Unit or built-in EtherNet/IP port is con-
nected to an Ethernet network, message communications can be conduct-
ed 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/CJ1-
series CPU Units with unit version 2.0 or later, CJ2 CPU Units, and CX-
Programmer version 4.0 or higher.
Type of FINS message Data send/receive commands Any kind of FINS command
Network
communications
instructions
SEND/RECV instructions CMND(490) instructions
PLC to PLC (both must
be CS/CJ-series PLCs
with a CS/CJ-series Eth-
erNet/IP Unit, built-in
EtherNet/IP port, or
Ethernet Units) (See
note 1.)
Note Inter-network com-
munications are
possible with
Ethernet networks
or other networks,
such as Controller
Link. (See note 2.)
Data length (excluding
command code) SEND instruction: 990 words: RECV
instruction: 990 words. CMND instruction: 1,990 bytes max.
CS/CJ-series PLC CS/CJ-series PLC CS/CJ-series PLC CS/CJ-series PLC
Command
CS/CJ-series PLC
Command
Command to
CPU Unit
Command to
EtherNet/IP Unit
191
FINS Message Communications Section 7-2
Note FINS commands sent and received by the CS/CJ-series EtherNet/IP
Unit include commands addressed to the CS/CJ-series CPU Unit
and commands addressed to the CS/CJ-series EtherNet/IP Unit.
Up to 8 network levels, including the EtherNet/IP network, can be crossed.
Controller Link Unit Controller Link Unit
CS/CJ-series EtherNet/IP Unit
CS/CJ-series CPU Unit
Remote I/O communications
Controller Link CS/CJ-series EtherNet/IP Unit
Ethernet (EtherNet/IP)
CS/CJ-series EtherNet/IP Unit
Ethernet (EtherNet/IP)
192
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-series EtherNet/IP Units and built-in EtherNet/IP ports.
Note Specific FINS commands (commands 2810 and 2801) are used to send
explicit messages.
Note The CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports (CS1W-
EIP21, CJ1W-EIP21, CJ2H-CPU@@-EIP, or CJ2M-CPU3@) contain a PLC
Object, so that other devices can read/write the I/O memory of the CPU Unit
with the built-in EtherNet/IP port or the CPU Unit to which the EtherNet/IP Unit
is mounted.
Explicit message Sending Receiving
Network communi-
cations instruction CIP UCMM messages can be sent to an EtherNet/IP
Unit or built-in EtherNet/IP port by a CMND(490)
instruction containing FINS command code 2810
Hex.
Automatically responds to explicit mes-
sages from other devices.
Functions supported
in remote devices • Masters/slaves made by other manufacturers:
Supported services determine supported functions.
• PLC with a CS/CJ-series EtherNet/IP Unit or built-in
EtherNet/IP port:
Supports the reading/writing of a remote CPU Unit’s
status information and I/O memory data.
• Masters made by other manufacturers
• PLC with a CS/CJ-series EtherNet/IP Unit
or built-in EtherNet/IP port: Supports the
reading/writing of the local CPU Unit’s sta-
tus information and I/O memory data.
193
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, or CJ2M-CPU3@
Communications
instructions Sending/ receiving
data SEND and RECV instructions
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-series EtherNet/IP Unit or
built-in EtherNet/IP port.
Sending Ether-
Net/IP CIP UCMM
messages
CMND(490) instruction
Sends CIP UCMM messages to other companies’ masters/slaves, or PLCs
with a CS/CJ-series EtherNet/IP Unit or built-in EtherNet/IP port mounted.
Number of desti-
nation nodes FINS message com-
munications 1:N communications
Explicit message
communications 1:N communications
Send functions: CIP unconnected (UCMM) communications only
Receive functions: CIP unconnected (UCMM) and CIP connected (Class 3)
communications
Transmission data
length (not includ-
ing the command
code)
FINS message com-
munications • SEND: 990 words (1,980 bytes) max. normally, or 727 words (1,454 bytes)
max. when broadcasting
• RECV: 990 words (1,980 bytes) max.
• CMND:1,990 bytes max. normally, or 1,462 bytes max. when broadcasting
(data after the FINS command code)
Explicit message
communications CMND: 492 bytes max.
No. of simultaneous instructions One each for 8 ports (ports 0 to 7)
Refer to 3-25 Network Instructions in 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-
nections Same network type Supports internetwork communications between Ethernet networks con-
nected to CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports (up
to 3 levels).
Different network
type Supports internetwork communications between the EtherNet/IP network
connected to a CS/CJ-series EtherNet/IP Unit or built-in EtherNet/IP port
and other networks such as Controller Link or SYSMAC LINK (up to 3 lev-
els).
194
Message Communications Error Indications Section 7-5
7-5 Message 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 er-
ror record in the error log stored in RAM in the EtherNet/IP Unit or CPU
Unit with the built-in EtherNet/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.
2. When a communications error has occurred, details on the error are indi-
cated by the MS and NS indicators and the 7-segment display on the front
panel of the EtherNet/IP Unit or CPU Unit with the built-in EtherNet/IP port.
This information can be used for troubleshooting.
CPU Unit
Configurator
FINS command
Read-out
Monitor
Code
Code
Code
64 records
Example: Routing table erro
r
Flashing red
Not relevant NS
MS
Communications status 3
15 00
EtherNet/IP
Unit CPU
Unit
195
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.
Note The 7-segment display alternately displays the error and the node address of
the node where the error occurred.
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
No change No change No change
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 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
196
Message Communications Errors Section 7-6
197
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-in EtherNet/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-diagram program. Although an outline of these instructions is provided in this section, refer to the CS/
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
198
Overview of FINS Communications Section 8-1
8-1 Overview of FINS Communications
8-1-1 Communications On an Ethernet Network
The EtherNet/IP Units and built-in EtherNet/IP ports support the FINS com-
munications service, which can be used simultaneously with the CIP commu-
nications service.
FINS communications data is sent and received as UDP/IP packets or TCP/IP
packets.
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.
The FINS communications service is a communications method based on
UDP/IP, and it is supported by most OMRON Ethernet-related products. (In
this manual it is called the FINS/UDP method.) In addition to supporting the
FINS/UDP method, the CJ2H-CPU@@-EIP, CJ2M-CPU3@, CS1W-EIP21,
and CJ1W-EIP21 support FINS communications using TCP/IP. (In this man-
ual, this is called the FINS/TCP method.)
Packet (FINS command)
Ethernet
(EtherNet/IP)
Packet (FINS response)
EtherNet/IP Unit
PLC
PLC
EtherNet/IP Unit or host computer
FINS
UDP TCP
IP
Ethernet
Ethernet Address
Node Number
Application Layer
Transport Layer
Internet Layer
Physical Layer
IP Address
UDP Port No. TCP Port No.
199
Overview of FINS Communications Section 8-1
8-1-2 Using 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)
Can be changed. 9600 (default)
Can be changed.
Protection No Yes (Specification of client IP addresses when Unit is used as a
server)
Other Items set for each UDP
port
• Broadcast
• IP Address Conversion
Items set for each connection
• Server/client specification
• Remote IP address specification
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-alive is to be used.
TCP/IP Setting
• Remote node keep-alive time
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
200
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.
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.
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 sec-
tion (FINS frame) that exceeds 1,472 bytes is split into packets for transmis-
sion. 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-byte UDP 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.
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.
Ethernet Ver. 2 IP UDP FINS frame FCS
UDP packet
201
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 communi-
cations service.
The default setting for the UDP port number (i.e., the UDP port number of the
EtherNet/IP Unit or built-in EtherNet/IP port) is 9600. To set another number,
set the number on the FINS/UDP Tab Page of the CX-Programmers Edit
Parameters Dialog Box.
At the EtherNet/IP Unit or built-in EtherNet/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 Settings in 3-1-1 Procedures.
2. Keep the CX-Programmer connected online, right-click the EtherNet/IP
Unit or built-in EtherNet/IP port in the PLC IO Table Dialog Box, and select
Edit - 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 ad-
dress table.)
• Dynamic Change of remote IP addresses
3. Select Transfer to PLC from the PLC Menu and click the Yes 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.
202
FINS/TCP Method Section 8-3
8-3 FINS/TCP Method
8-3-1 Overview
FINS/TCP Features
The FINS/TCP method is a FINS communications method that uses the TCP/
IP protocol. TCP/IP is a connection-type communications protocol. Before a
message is sent from one node to another, it is necessary to establish a vir-
tual circuit, i.e., a connection. Once a connection has been established, com-
munications are quite reliable. The arrival of data that is sent via the
connection is confirmed by an acknowledgement (ACK) response, and retries
are executed automatically as required.
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 communi-
cations between two PLCs, either one can be set as the client and the other
as the server.
Compared to the FINS/UDP method, the FINS/TCP method has the following
characteristics.
• Data transmission is more reliable, due to factors such as retry process-
ing at the TCP/IP layer. The FINS/TCP method is thus better suited to
dealing with communications errors in an IP network that spans several
layers.
• Remote clients can be restricted by means of settings at the server (i.e.,
the server can be protected from access by non-specified IP addresses).
• Broadcasting cannot be used.
• TCP/IP has various retry procedures, and this tends to lower its perfor-
mance in comparison with UDP/IP.
• There is a limit to the number of connections that can be made (i.e., 16
connections maximum), and any given node can communicate only with
up to 16 other nodes at a time.
Node
(Client)
Data transmission 1
Request to establish a connection
Node
(Server)
Notification of establishing
connection
Acknowledgement
Acknowledgement
An acknowledgement is received whenever a
connection is established or data is sent, so
transmissions are more reliable but somewhat slower.
Connection
established
203
FINS/TCP Method Section 8-3
• 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 lad-
der program using a FINS command (i.e., FINS/TCP CONNECTION
REMOTE NODE CHANGE REQUEST).
FINS/TCP Frame Format The following diagram shows the structure of a TCP packet sent over an
Ethernet network.
As the diagram shows, a nested structure is used with the FINS/TCP method,
i.e., Ethernet Ver. 2, IP frame, TCP frame, FINS/TCP header frame, and FINS
frame. A TCP data section (FINS/TCP header + FINS frame) that exceeds the
segment size (default setting of 1,024 bytes in the EtherNet/IP Unit or built-in
EtherNet/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
or built-in EtherNet/IP port and FinsGateway (Ver. 2003 or higher) the appro-
priate frames are separated out automatically, so there is normally no need to
be pay attention to it at the application layer.
TCP Port Number for
FINS/TCP The TCP port number is the number for TCP to identify the application layer
(i.e., the FINS communications service in this case). When communications
are executed using TCP/IP, this port number must be allocated for the com-
munications service.
The default setting for the TCP port number (i.e., the TCP port number of the
EtherNet/IP Unit or built-in EtherNet/IP port) is 9600. To set another number,
make the setting for the FINS/TCP port on the FINS/TCP Tab Page of the CX-
Programmer’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-in EtherNet/IP port and FinsGateway (Ver. 2003 or higher), an
unused TCP port is automatically detected and utilized.)
At the EtherNet/IP Unit or built-in EtherNet/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 Connection
Numbers FINS/TCP allows up to 16 FINS/TCP connections to be established simulta-
neously, and these 16 connections are managed at the EtherNet/IP Unit or
built-in EtherNet/IP port by connection numbers. When setting FINS/TCP con-
nection settings in the FINS/TCP Tab Page of the Network Configurator’s Edit
Parameters Dialog Box, set them individually using these connection num-
bers.
Ethernet Ver. 2 IP TCP FINS frame FCSFINS/TCP header
TCP packet
204
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 termi-
nated by a communications error or a FINS command (i.e., FINS/TCP CON-
NECTION REMOTE NODE CHANGE REQUEST).
Note The starting word of the FINS/TCP Connection Status Area is different in the
CS1W-ETN21 and CJ1W-ETN21 Ethernet 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-in Ether-
Net/IP ports, change the word starting word address for this area from n+23 to
n+24.
FINS/TCP
Communications
Procedure
With FINS/TCP, FINS node addresses are exchanged immediately after a
connection is established. This makes it possible to determine the FINS node
addresses to which the 16 connection numbers, and to manage them in an
internal table.
After a connection has been established as a FINS/TCP server, it is termi-
nated in the following ways.
• When the connection is closed by the client.
• When a FINS command to close the connection (FINS/TCP CONNEC-
TION REMOTE NODE CHANGE REQUEST) is sent by the client.
• When there is no response from the client when the keep-alive function is
in effect.
15 14 13 12 11 10 09 07 06 05 04 03 02 01 00
n+24
*: Bit 15 corresponds to connection No. 16, bit 00 to connection No. 1, etc.
08
Connection request (C→S)
FINS node number A sent
Ethernet/IP Unit
(Server)
Passive open
Connection established
Local node No. sent
FINS frame sent
Personal computer
(Client)
Active open
Local node No. sent
Connection established
Remote node No. received FINS node number B sent
FINS node numbers exchanged
Connection established
Normal data communications
Remote node No. received
FINS frame sent
Full duplex communications
Example:
IP address C
FINS node number A
Example:
IP address S
FINS node number B
205
FINS/TCP Method Section 8-3
After a connection has been established as a FINS/TCP client, it can be termi-
nated in the following ways.
• If the connection is closed by the server.
• If there is no response from the client when the keep-alive function is in
effect.
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 or built-in EtherNet/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 the CX-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 or built-in EtherNet/IP port.
Procedure for Using FINS/TCP
1,2,3... 1. Make the basic settings.
Refer to Initial Settings in 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 ad-
dress to the target FINS/TCP client.
• Keep-alive: Specified whether to use the keep-alive function.
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 the Yes 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)
206
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-Programmer communications, FINS
message communications and remote programming/monitoring from the
CX-Programmer will 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.
207
Routing Tables Section 8-4
8-4 Routing Tables
When the FINS communications service is used, routing tables must be cre-
ated in advance. Routing tables are required in the following circumstances.
• When communicating with a PLC or computer on another network (e.g.,
remote programming or monitoring using FINS messages or a CX-Pro-
grammer)
• When multiple Communications Units are mounted to a single PLC (i.e.,
CPU Unit).
• When routing tables are used for one or more other nodes on the same
network.
It is not necessary to set routing tables if one Communications Unit is
mounted to the PLC and the nodes are connected as one network. The rout-
ing tables are required not only for nodes communicating via the FINS com-
munications service but also for all relay nodes on the network.
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.
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-in port).
2. The network address is the number of the network (1 to 127) to which the
Communications Unit or Board is connected. It is set when the local net-
work table is created.
Relay Network Table A relay table is a table that shows the nodes to which data should be sent first
in order to send data to a network that is not connected to the local node. It
shows the correspondence between the address of the final destination net-
work, and the network address and node address of the first relay point of the
path to reach there. When internetwork communications are carried out, the
end network can be reached by following the relay points.
Example Unit #04
Unit #05
Unit #06
Unit #07
Network #1
Network #2
Network #3
Network #4
Local Network Table
Local network
address Unit number
1
2
3
4
04
05
06
07
208
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).
Note In the above example, the routing tables required for a message to reach PLC
#4 from PLC #1 are shown. Additional settings would be required in the rout-
ing tables for a message to reach PLC #1 from PLC #4. Refer to 8-4-3 Rout-
ing Table Setting Examples for routing table setting examples.
8-4-2 Connecting and Using a Peripheral Device for the PLC
Routing tables must be created by a CX-Integrator connected to the PLC.
(They cannot be created using a Programming Console.) For details on how
to connect and use the CX-Integrator, refer to the CX-Integrator Operation
Manual (W445). (CX-Integrator is automatically installed when CX-One is
installed.)
Note 1. When routing tables are transferred from the CX-Integrator to the PLC, all
of the CPU Bus Unit are reset so that the routing tables that have been cre-
ated can be read and enabled. Before transferring the routing tables, con-
firm 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-Integrator to a PLC with only one Communications Unit mounted.
Routing tables cannot be transferred to other nodes from a PLC with mul-
tiple Communications Units mounted.
3. Routing tables can only be transferred as a batch to multiple nodes within
the same network as the PLC to which the CX-Integrator is connected.
3
21 3
31 1
20
3
32 2
PLC #1 (local node)
Node #1
Network #1
Node #2
PLC #2 (relay node)
PLC #3
(relay node)
Node #2
Unit #0 PLC #4 (destination node)
Node #3
Node #1
Network #2 Network #3
Node #2
Node #1
Unit #1
PLC #1
relay network table
PLC #2
relay network table PLC #3
local network table
End network
End
network Relay
network Relay
node
Local
network
address Unit
number
To go to network #3,
first go to node #3 at
network #1.
To go to network #3,
first go to node #2 at
network #2. (To go to network #3
according to the local
network table, go
through unit
number 1 of the local
CPU Rack.)
(The network is the same,
so go to node #2 at network #3.)
End
network Relay
network Relay
node
209
Routing Tables Section 8-4
8-4-3 Routing Table Setting Examples
■Example 1: Local Network Table for a PLC With Multiple Units Mounted
This example shows the local network table settings for a PLC to which multi-
ple CPU Bus Units are mounted.
■Example 2: Three Interconnected Networks
This example shows the relay network table settings for three different inter-
connected networks.
In the table for PLC #3, for example, if network #A is taken as the end net-
work, then network #B becomes the relay network and node #c becomes the
relay node. If network #C is taken as the end network, then network #B still
becomes the relay network and node #e becomes the relay node.
A
Ba
b
No.
1
2
P
S
C
P
U
C
L
K
E
I
P
Ethernet (EtherNet/IP) network
(Network #A)
Controller Link network
(Network #B)
Unit #a Unit #b
PS: Power Supply Unit
CPU: CPU Unit
EIP: EtherNet/IP Unit
CLK: Controller Link Unit
Local Network Table
Local
network CPU Bus
Unit
1
2
B
C
A
A
b
b
1C B e
1
2
A
C
B
B
c
e
1
2
A
B
C
C
f
f
1A B c
Relay Network Table
No. End
network Relay
network Node
PLC #1
Node #a
Network #A PLC #2
Node #b
Node #c
Node #d
PLC #3
Network #B
Network #C
Node #e
PLC #4
Node #f
Node #g
PLC #5
210
Routing Tables Section 8-4
■Example 3: All Nodes
This example uses the following configuration to show the routing tables for all
nodes.
PLC
5
PLC
1
E
I
P
PLC
2
C
L
K
E
I
P
PLC
3
E
I
P
S
L
K
CPLC
4
CPLC
6PLC
7
L
KL
K
S
L
K
S
L
K
Unit #5
Node #6 Network #10
Unit #4
Node #5
Network #30
Unit #0
Node #1 Unit #1
Node #2 Unit #5
Node #5 Unit #6
Node #10
Network #20
Unit #3
Node #4
Unit #2
Node #3 Unit #7
Node #15
No.
1
2
3
No.
1
2
3
010 05 020 010 004
030 010 005
No.
1
2
3
No.
1
2
3
010 03 030 010 005
No.
1
2
3
No.
1
2
3
010 04 020 010 004
No.
1
2
3
No.
1
2
3
020 00 010 020 003
030 020 003
No.
1
2
3
No.
1
2
3
020 01 010 020 003
030 020 003
No.
1
2
3
No.
1
2
3
030 05 010 030 015
020 030 015
No.
1
2
3
No.
1
2
3
030 06 010 030 015
020 030 015
020 02
030 07
PLC #1 Routing Table
(Local network table) (Relay network table)
Local
network CPU Bus
Unit No. End
network Relay
network Relay
node
PLC #2 Routing Table
PLC #3 Routing Table
PLC #4 Routing Table
PLC #5 Routing Table
PLC #6 Routing Table
PLC #7 Routing Table
(Relay network table)
(Relay network table)
(Relay network table)
(Relay network table)
End
network Relay
network Relay
node
End
network Relay
network Relay
node
End
network Relay
network Relay
node
End
network Relay
network Relay
node
(Local network table)
(Local network table)
(Local network table)
(Local network table)
(Local network table)
(Local network table)
Local
network CPU Bus
Unit No.
Local
network CPU Bus
Unit No.
Local
network CPU Bus
Unit No.
Local
network CPU Bus
Unit No.
Local
network CPU Bus
Unit No.
Local
network CPU Bus
Unit No.
End
network Relay
network Relay
node
End
network Relay
network Relay
node
(Relay network table)
(Relay network table)
211
Using FINS Applications Section 8-5
8-5 Using FINS Applications
8-5-1 CX-Programmer (CX-Server)
The following examples show how to connect online from a CX-Programmer
on an Ethernet network to a PLC on the Ethernet network.
■System Configuration Example 1: No Routing
In this example, an online connection is made by FINS/UDP to a PLC on an
Ethernet network (PLC1 in the diagram below) from a CX-Programmer/CX-
Integrator connected to the Ethernet network.
Conditions
• FINS/UDP method
• IP Address Conversion: Automatic (Dynamic) generation method
CX-Programmer's Change PLC Dialog Box
CX-Programmer's FINS/UDP Tab Page in Edit Parameters Dialog Box
CX-Programmer/CX-Integrator
Ethernet or EtherNet/IP (Network address: None)
Ethernet port
Target: PLC1
EtherNet/IP Unit
IP address: 192.168.250.1
FINS/UDP method
Node number: 1
IP address conversion: Automatic
generation method (dynamic)
EtherNet/IP Unit node number: 2
EtherNet/IP Unit IP address: 192.168.250.2
Settings for target PLC (PLC1)'s Change PLC Dialog Box Setting
PLC name PLC1
Network classification Ethernet
Network Tab 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-in EtherNet/IP
port IP address)
Port number 9600
Item Setting
FINS/UDP Port Default (9600)
IP Address Conversion Automatic (Dynamic) generation method
IP Router Table None
212
Using FINS Applications Section 8-5
Example: Inputs to the CX-Programmer's Setup 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.
213
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-Integrator
connected to the Ethernet network.
Conditions
• FINS/UDP method
• IP address conversion: Automatic generation method (dynamic)
CX-Programmer's Change PLC Dialog Box
Settings for target PLC (PLC3)'s Change PLC Dialog Box Setting
PLC name PLC3
Network classification Ethernet
Network Tab
Page FINS destination FINS transmission
source address 1
Network number 2
Node address 3
Frame length 2,000 bytes
Response monitor time 2 seconds
CX-Programmer/CX-Integrator
Ethernet port
Node address: 1
IP address: 192.168.250.1
Ethernet or EtherNet/IP
(network address 1)
Routing
according to
routing table
Controller
Link Unit EtherNet/IP Unit
IP address conversion: Automatic generation method (dynamic)
Gateway between networks
PLC1
Controller Link Unit Target PLC Controller Link Unit
Node address 2 Node address 3
Controller Link
(
network address 2
)
PLC2 PLC3
EtherNet/IP Unit node address: 2
EtherNet/IP Unit IP address: 192.168.250.2
EtherNet/IP Unit unit number: 0
Controller Link Unit node address: 1
Controller Link Unit unit number: 1
Routing to final network address 2
requires relaying through node
address 2 of relay network address
1 (EtherNet/IP Unit).
214
Using FINS Applications Section 8-5
CX-Programmer's FINS/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 select Routing table − Settings.
Then create FINS local routing tables (a local network table and a relay
network table).
Example: PLC 1 Routing Table Settings
• Local Network Table
• Relay Network Table
None
Example: PLC 2 and PLC 3 Routing Table Settings
• Local Network Table
• Relay Network Table
In order to relay from PLC2/3 to the final network number 1, it is necessary
to relay via node address 1 (i.e., the Controller Link Unit) on relay network
number 2.
2. Save the routing table file (File - Save local routing table file).
3. 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, select Work Online from the Network Menu.
5. Select Tools - Start Routing table, read the saved file, and select Op-
tions - Transfer to PLC. Click Yes to transfer the routing tables to the con-
nected PLC.
Driver Tab Page Workstation node address 1
Automatic generation method Not selected
IP address 192.168.250.2 (Eth-
erNet/IP Unit or
built-in EtherNet/IP
port IP address)
Port number 9600
Unit number Local network number
01
12
Unit number Local network number
02
Final network number Relay network number Relay node address
121
Settings for target PLC (PLC3)'s Change PLC Dialog Box Setting
215
Using FINS Applications Section 8-5
8-5-2 FinsGateway
FinsGateway Ver. 2003 must be used to communicate using FINS/TCP
between applications serving as communications drivers and CS1W-EIP21,
CJ1W-EIP21, CJ2H-CPU@@-EIP, or CJ2M-CPU3@ EtherNet/IP Units.
FinsGateway Ver. 3.@ or lower versions can be used, however, when commu-
nicating by the FINS/UDP method only.
■Overview of Setup Methods
1. Starting FinsGateway Settings
Select FinsGateway − FinsGateway Setup to start the FinsGateway Setup.
2. ETN_UNIT Driver Setup
1. Double-click on ETN_UNIT in the settings for the network and Unit. The fol-
lowing ETN_UNIT Properties Window will be displayed.
• Network Tab Page
• Network number Set the network number for the personal computer
(Ethernet port).
• Local node address Set the personal computer (Ethernet port) node
address (1 to 254) on the Ethernet network.
• Communication unit number Set the unit number in decimal (16 to 31) for the per-
sonal computer (Ethernet port).
216
Using FINS Applications Section 8-5
• Communication Unit Tab Page
• UDP Nodes Tab Page: Automatic Generation Method (Dynamic or Passive)
• UDP port number Set the local UDP port number for the personal com-
puter (Ethernet port). The default is 9600.
• Priority Network Card If multiple Network Cards are mounted at the personal
computer, select the Network Card that is to be given
priority.
• FINS - IP address conver-
sion Set the IP address conversion method.
217
Using FINS Applications Section 8-5
• UDP Nodes Tab Page: IP Address Table Method or Combined Method
Click the Add Button, and then set the IP address table in the following Ether-
net Node Definition Dialog Box.
• Node address: Set the remote FINS node address.
• IP address: Set the remote IP address.
218
Using FINS Applications Section 8-5
• TCP Nodes Tab Page
Click the Add Button, and then set the IP address table in the following Ether-
net Node Definition Dialog Box.
3. Starting FinsGateway ETN_UNIT Service
Select ETN_UNIT from Services under the Basic Tab in the FinsGateway
Setup Window, and then click the Start Button.
• Node address: Set the remote FINS node address.
• IP address: Set the remote IP address.
• Destination port number: Set the FINS/TCP port number for the remote node.
Normally the PLC's default setting of 9600 should be
specified.
• Keep-alive setting: Sets the keep-alive function. Normally this should be
selected.
219
Using FINS Applications Section 8-5
■ System Configuration Example 3: Connecting the CX-Programmer Online
Using the FINS/TCP Method
In this example, an online connection is made by FINS/TCP to a PLC on an
Ethernet network (PLC1 in the diagram below) from a CX-Programmer/CX-
Integrator connected to the Ethernet network.
Conditions
• FINS/TCP method
CX-Programmer's Change PLC Dialog Box
CX-Programmer's FINS/TCP Tab Page in Edit Parameters Dialog Box
Not set. (All defaults are used.)
FinsGateway ETN_UNIT Setup
TCP Nodes Tab Page: Ethernet Node Definition Dialog Box
CX-Programmer/CX-Integrator
Ethernet or EtherNet/IP (Network number: none)
Ethernet port Target: PLC1
EtherNet/IP Unit
Node number: 1
IP address: 192.168.250.1
FinsGateWay Version 2003
IP address conversion: Automatic generation method (dynamic)
EtherNet/IP Unit node number: 2
EtherNet/IP Unit IP address: 192.168.250.2
FINS/TCP method
Settings for target PLC (PLC1)'s Change PLC Dialog Box Setting
PLC name PLC1
Network classification FinsGateway
Network Tab
Page FINS destination Network number 0
Node address 2
Frame length 2,000 bytes
Response monitor time 2 seconds
Item Setting
FINS/TCP Port Default (9600)
IP Router Table None
Item Setting
Node address 2
IP address 192.168.250.2
Destination port number 9600
Keep-alive setting Selected (yes)
220
Communicating between OMRON PLCs Section 8-6
8-6 Communicating between OMRON PLCs
FINS commands can be sent from the CPU Unit of a PLC by using the
SEND(090), RECV(098), and CMND(490) instructions.
SEND(090): Writes I/O data from the local node to another node.
RECV(098): Reads I/O data from another node to the local node.
CMND(490): Issues FINS commands for controlling operations such as send-
ing and receiving I/O memory data to and from other nodes, reading informa-
tion regarding other nodes, and so on.
8-6-1 Communications Specifications
The following table shows the specifications for PLC communications using
the SEND(090), RECV(098), and CMND(490) instructions.
Note 1. The maximum data length is limited to 512 bytes for data exchange be-
tween the PLC and SYSMAC LINK Systems or the PLC and SYSMAC
BUS/2 Remote I/O Systems.
2. When broadcasting, do not require a response.
Use the FINS/UDP method for broadcasting.
Item Specifications
Destination 1:1 SEND(090), RECV(098), CMND(490) instructions
1:N SEND(090), CMND(490) instructions (broadcasting)
Data length SEND(090):
990 words (1,980 bytes) max.; broadcasting:
727 words (1,454 bytes)
RECV(098):
990 words (1,980 bytes) max.
CMND(490):
1,990 bytes max.; broadcasting: 1,462 bytes (after FINS com-
mand code)
Data contents The following data is sent and received with the execution of
each instruction.
SEND(090):
Sends request for remote node to receive data, and receives
response data.
RECV(098):
Sends request for remote node to send data, and receives
response data.
CMND(490):
Sends any FINS command and receives response data.
Communications
port number Ports 0 to 7 (Eight transmissions can occur simultaneously.)
Response moni-
tor time 0000:
2 s (default)
0001 to FFFF:
0.1 to 6,553.5 s in 0.1-s increments (specified by user)
Number of retries 0 to 15 retries
221
Communicating between OMRON PLCs Section 8-6
8-6-2 PLC Communications Data Areas
The following table shows the I/O data areas involved when SEND(090) and
RECV(098) are used.
Note 1. Data cannot be written to words A000 to A447 in the Auxiliary Area.
2. A maximum of 13 banks in the EM Area can be used for a CS1/CJ1 CPU
Unit. A maximum of 25 banks in the EM Area can be used for a CJ2H CPU
Unit. A maximum of 4 banks in the EM Area can be used for a CJ2M CPU
Unit. For details regarding the EM Area, refer to the operation manual for
the PLC that is used. Refer to the operation manual for your CPU Unit to
confirm EM Area support.
Area Range
CIO Area CIO 0000 to CIO 6143
Work Area W000 to W511
Holding Area H000 to H1535
Auxiliary Area A000 to A959 (See note 1.)
Timer Area TIM0000 to 4095
Counter Area CNT0000 to 4095
DM Area D00000 to D32767
EM Area E00000 to E32767 (See note 2.)
222
Communicating between OMRON PLCs Section 8-6
8-6-3 Using SEND(090), RECV(098), and CMND(490)
Make the settings shown below when using the SEND(090), RECV(098), and
CMND(490) instructions in the user’s ladder-diagram program in the PC.
SEND(090) The SEND(090) instruction sends the data in n number of words, starting from
the beginning word S at the local node, to the words starting from the begin-
ning word D at the remote destination node (node address N).
Note The message service does not guarantee that a message will reach the desti-
nation node. A message may be lost during transmission due to factors such
as noise. To prevent this from occurring when using message services, it is
common to set up retry processing at the node from which instructions are
issued. With the SEND(090), RECV(098), and CMND(490) instructions, retry
processing is executed automatically by specifying the number of retries, so
specify a number other than 0.
S→
15 0
n
D→
15 0
Local node
Number
of words
(n)
Destination node number N
(@)SEND(90)
S
D
C
C+1 0 0
C
15 11 8 7 0
C+2
15 11 8 7 0
15 0
C+3 0 0
C+4
15 10 8 7 3 0
S: Local node beginning word
D: Destination beginning word
C: First word of control data (below)
Number of words (n)
0001 to 03DE (Hex): 1 to 990 words
Destination network number
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Destination node number N
00 to FE (Hex): 0 to 254
The same data can be broadcast to all nodes on the network by
setting the destination node number to FF (Hex).
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
223
Communicating between OMRON PLCs Section 8-6
RECV(098) With the RECV(098) instruction, the data in m number of words, starting from
the beginning word S at the remote node (node address M) is received at the
words starting from the beginning word D at the local node.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to fac-
tors such as noise. In order to prevent this from occurring when using mes-
sage services, it is common to set up retry processing at the node from which
instructions are issued. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the num-
ber of retries, so specify a number other than 0.
D→
m
15 0 15 0
S→
Local node
Number
of words
(m)
Remote node number N
C+1 0 0
C+3 0 0
C+4
C
15 11 8 7 0
C+2
15 11 8 7 0
15 10 8 7 3 0
15 0
(@)RECV(98)
S
D
C
S: Remote node beginning word
D: Local beginning word
C: First word of control data (below)
Number of reception words (m)
0001 to 03DE (Hex): 1 to 990 words
Destination network number
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination Unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Remote node number M (send source)
00 to FE (Hex): 0 to 254
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
224
Communicating between OMRON PLCs Section 8-6
CMND(490) The CMND(490) instruction sends n bytes of command data, starting from the
beginning word S at the local node, to the node at node address N. the data in
m number of words, starting from the beginning word S at the remote node
(node address M) is received at the words starting from the beginning word D
at the local node.
Note The message services function does not guarantee that a message will reach
the destination node. A message may be lost during transmission due to fac-
tors such as noise. In order to prevent this from occurring when using mes-
sage services, it is common to set up retry processing at the node from which
instructions are issued. With the SEND(090), RECV(098), and CMND(490)
instructions, retry processing is executed automatically by specifying the num-
ber of retries, so specify a number other than 0.
S
15 0
(S−1)
+−
n
2
D
(D−1)
+−
m
2
Local node Destination node number N
Command
Response
Interpretation
Execution
Com-
mand
data: n
bytes
Re-
sponse
data: m
bytes
(@)CMND(490)
S
D
C
C+1
C
15 0
15 0
C+3
15 8 7 0
C+2 0 0
15 11 8 7 0
C+4 0 0
C+5
15 10 8 7 3 0
15 10 8 7 3 0
S: Beginning command storage word
D: Beginning response storage word
C: First word of control data (below)
Number of bytes of command data (n)
0000 to 07C6 (Hex): 1 to 1,990 bytes
Number of bytes of response data (m)
00 (Hex): Local network
01 to 7F (Hex): 1 to 127
Destination Unit address
00 (Hex): CPU Unit
10 to 1F: (Hex): Unit #0 to #15
E1 (Hex): Inner Board
FE (Hex): Unit connected to network
Destination node number N
00 to FE (Hex): 0 to 254
The same data can be broadcast to all nodes on the network by
setting the destination node number to FF (Hex).
The range of node addresses is different for networks other than Ethernet.
Number of retries
0 to F (Hex): 0 to 15 retries
Communications port number: 0 to 7
Response
0: Required.
1: Not required.
Response monitor time
0000 (Hex): 2 s
0000 to 07C6 (Hex): 1 to 1,990 bytes
Destination network number
0001 to FFFF (Hex): 0.1 to 6,553.5 s
(in units of 0.1 s)
225
Communicating between OMRON PLCs Section 8-6
Commands Addressed to CS/CJ-series CPU Units
The following table provides a list of FINS commands that can be processed
by a CS/CJ-series CPU Unit. For details, refer to the CS/CJ-series Program-
mable Controllers Communications Commands Reference Manual (W342).
For details on FINS commands that can be processed by the EtherNet/IP Unit
or built-in EtherNet/IP port, refer to Appendix E FINS Commands Addressed
to EtherNet/IP Units or Built-in EtherNet/IP Ports.
Usage Command
code Name Function
MR SR
I/O memory area
access 01 01 MEMORY AREA READ Reads the contents of consecutive I/O
memory area words.
01 02 MEMORY AREA WRITE Writes the contents of consecutive I/O
memory area words.
01 03 MEMORY AREA FILL Writes the same data to the specified
range of I/O memory area words.
01 04 MULTIPLE MEMORY AREA READ Reads the contents of specified non-
consecutive I/O memory area words.
01 05 MEMORY AREA TRANSFER Copies the contents of consecutive I/O
memory area words to another I/O
memory area.
Parameter access
(registered I/O
tables, routing
tables, etc.)
02 01 PARAMETER AREA READ Reads the contents of consecutive
parameter area words.
02 02 PARAMETER AREA WRITE Writes the contents of consecutive
parameter area words.
02 03 PARAMETER AREA FILL (CLEAR) Writes the same data to the specified
range of parameter area words.
Program area
access 03 06 PROGRAM AREA READ Reads the UM (User Memory) area.
03 07 PROGRAM AREA WRITE Writes to the UM (User Memory) area.
03 08 PROGRAM AREA CLEAR Clears the UM (User Memory) area.
Operating mode
changes 04 01 RUN Changes the CPU Unit’s operating
mode to RUN or MONITOR.
04 02 STOP Changes the CPU Unit’s operating
mode to PROGRAM.
Machine configura-
tion reading 05 01 CPU UNIT DATA READ Reads CPU Unit data.
05 02 CONNECTION DATA READ Reads the model numbers of the device
corresponding to addresses.
Status reading 06 01 CPU UNIT STATUS READ Reads the status of the CPU Unit.
06 20 CYCLE TIME READ Reads the maximum, minimum, and
average cycle time.
Time data access 07 01 CLOCK READ Reads the present year, month, date,
minute, second, and day of the week.
07 02 CLOCK WRITE Changes the present year, month, date,
minute, second, or day of the week.
Message display 09 20 MESSAGE READ/CLEAR Reads and clears messages, and reads
FAL/FALS messages.
Access rights 0C 01 ACCESS RIGHT ACQUIRE Acquires the access right as long as no
other device holds it.
0C 02 ACCESS RIGHT FORCED ACQUIRE Acquires the access right even if
another device already holds it.
0C 03 ACCESS RIGHT RELEASE Releases the access right that has been
acquired.
Error log 21 01 ERROR CLEAR Clears errors or error messages.
21 02 ERROR LOG READ Reads the error log.
21 03 ERROR LOG POINTER CLEAR Clears the error log pointer.
226
Communicating between OMRON PLCs Section 8-6
8-6-4 Writing Programs
Programs incorporating the SEND(090), RECV(098), and CMND(490)
instructions are generally created using the Communications Port Enabled
Flag and the Communications Port Error Flag as input conditions. CS/CJ-
series CPU Units have eight communications ports. Only one instruction can
be executed at any given port at one time, however, so the program must not
overlap the use of any of the ports. A program example is provided below.
File memory 22 01 FILE NAME READ Reads file memory data.
22 02 SINGLE FILE READ Reads a specified length of file data
from a specified position within a single
file.
22 03 SINGLE FILE WRITE Writes a specified length of file data
from a specified position within a single
file.
22 04 FILE MEMORY FORMAT Formats (initializes) the file memory.
22 05 FILE DELETE Deletes specified files stored in the file
memory.
22 07 FILE COPY Copies files from one file memory to
another file memory in the same sys-
tem.
22 08 FILE NAME CHANGE Changes a file name.
22 0A MEMORY AREA–FILE TRANSFER Transfers or compares data between the
I/O memory area and the file memory.
22 0B PARAMETER AREA–FILE TRANSFER Transfers or compares data between the
parameter area and the file memory.
22 0C PROGRAM AREA–FILE TRANSFER Transfers or compares data between the
UM (User Memory) area and the file
memory.
22 15 CREATE/DELETE DIRECTORY Creates or deletes a directory.
Debugging 23 01 FORCED SET/RESET Force-sets or force-resets bits, or
releases force-set status.
23 02 FORCED SET/RESET CANCEL Cancels all bits that have been force-set
or force-reset.
Usage Command
code Name Function
MR SR
There are eight communications ports, so up to eight
communications instructions can be executed at a time. The
number of messages that can be sent or received with a
single CPU Bus Unit service, though, is not more than two
each for the CPU Unit to the EtherNet/IP Unit and for the
EtherNet/IP Unit to the CPU Unit.
Communications port
EtherNet/IP Unit CPU Unit
Instruction 1
Instruction 2
Instruction 3
Instruction 4
Instruction 5
Instruction 6
Instruction 7
Instruction 8
227
Communicating between OMRON PLCs Section 8-6
The execution status of the SEND(090), RECV(098), and CMND(490) instruc-
tions is always reflected by the communications flags (i.e., the Communica-
tions Port Enabled Flag and the Communications Port Error Flag). The CS/
CJ-series CPU Unit’s communications flags are allocated in the Auxiliary Area
as shown in the following table.
Note In CS/CJ-series PLCs, communications ports 0 to 7 are also used when exe-
cuting the PCMR(260) (PROTOCOL MACRO), TXDU(256), and RXDU(255)
instructions, so these flags are shared by SEND(090), RECV(098),
CMND(490), PCMR(260), TXDU(256), and RXDU(255).
SEND(090), RECV(098), and CMND(490) cannot be executed at a communi-
cations port if PCMR(260) TXDU(256), or RXDU(255) is being executed at
that port.
A
A
A
A
C
Execution
condition Communications
Port Enabled Flag
KEEP(011) A
Reset B
Input A remains ON from start to completion of commu-
nications instruction.
Operand,
control data
created with
@MOV and
@XFER.
Creates operand and control data in a given
area.
Communications
Port Enabled Flag
DIFU(013) B
Executes communications instructions.
Communications
Port Error Flag
Reset D
Communications
Port Enabled Flag
KEEP(011) C
Creates reset input. (Turns reset B ON
after execution of communications in-
struction.)
Exclusive control so execution is not simultaneous.
Use exclusive control so that no other communica-
tions instructions are started before execution of the
above communications instruction is complete.
(Continued in same way.)
Execution
condition
Communications
instructions
@SEND
@RECV
@CMND
Send Error Flag display
(Retry can be executed.)
Flag name Address Contents
Word Bits
Communications Port
Enabled Flag A202 Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
OFF: Execution enabled
(being executed)
ON: Execution disabled
(not being executed)
Communications Port
Error Flag A219 Bit 7: Port 7
Bit 6: Port 6
Bit 5: Port 5
Bit 4: Port 4
Bit 3: Port 3
Bit 2: Port 2
Bit 1: Port 1
Bit 0: Port 0
0: Normal completion
1: Abnormal completion
228
Communicating between OMRON PLCs Section 8-6
Communications Port
Completion Codes The status of a SEND(090), RECV(098), and CMND(490) instruction after
execution is reflected as a communications port completion code, in one word
(two bytes) of data as shown in the following table. (The value is 0000 during
instruction execution.) The recorded status is saved until execution of the next
instruction.
The meanings of the communications port completion codes are the same as
those for FINS commands and responses. Bits 08 to 15 in the communica-
tions port completion code correspond to the first byte of the response code,
and bits 00 to 07 correspond to the second byte. For details, refer to 14-6
Troubleshooting with FINS Response Codes.
Communications Port Error Flag and Completion Codes CMND(490)
Errors that occur when CMND(490) is used generate a Communications Port
Error Flag and are recorded in a communications port completion code only in
the following cases:
• When a response timeout error has occurred.
• When the number of communications data bytes exceeds the maximum
value for the Unit (i.e., 2,000 bytes for the EtherNet/IP Unit or built-in Eth-
erNet/IP port).
• When the actual number of response bytes is greater than the number of
reception bytes that has been set. (The response is not stored in this
case.)
Errors other than these are recorded in the response codes of the responses
stored from the beginning response storage word onwards. Be careful of
these, because there are no Communications Port Error Flags and they are
not recorded in a communications port completion code.
Timing of Communications Flag Changes
• The Communications Port Enabled Flag remains OFF during communica-
tions and turns ON when they are completed (regardless of whether or
not an error occurs).
• The Communications Port Error Flag retains its status until the next trans-
mission or reception.
• The Communications Port Error Flag turns OFF with the execution of the
next communications instruction even if there was an abnormal comple-
tion.
Word Contents
A203 Communications Port 0 Completion Code
A204 Communications Port 1 Completion Code
A205 Communications Port 2 Completion Code
A206 Communications Port 3 Completion Code
A207 Communications Port 4 Completion Code
A208 Communications Port 5 Completion Code
A209 Communications Port 6 Completion Code
A210 Communications Port 7 Completion Code
229
Communicating between OMRON PLCs Section 8-6
1
0
1
0
0000 0000 0000
Example
Communications Port Enabled Flag
Communications instruction:
SEND(090), RECV(098), CMND(490)
Communications Port Error Flag
Communications Port
Completion Code
Instruction 1
being executed. Instruction 2
being executed.
Instruction 3
being executed.
0000 (Normal completion)
0000 (Normal completion)
Completion 0202
(Unit address setting error)
230
Communicating between OMRON PLCs Section 8-6
8-6-5 Program Example
When the Communications Port Enabled Flag for port 7
is ON, and RECV(098) is not being executed, the send
execution program will start when execution condition
CIO 000000 turns ON.
Input CIO 120000 remains ON from the start of
SEND(090) execution until completion.
Control Data Creation
Contents Meaning
Number of send words = 10
Destination network number = 2
Destination node number = 4
Destination unit address = 0
Response required.
Communications port No. used = 7
Number of retries = 5
Response monitor time = 10 s
Send Data Creation
Ten words of data from word CIO 0000 is
stored from D00010 onwards.
Ten words of data from D00010 at the local node is
sent to D00020 onwards at network number 2, node
number 4, unit address 0 (the PLC).
Reset Input Creation
Send Error Display
KEEP
120000
000000 A20207
(See note 1.) 120002
120001
@MOV(21)
120000
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@XFER(70)
@SEND(90)
DIFU(13)
120000 A20207
121000
120000 A21907
(
Continued on next
p
a
g
e.
)
S
R
(See note 1.)
00 0A
00 02
04 00
07 05
00 64
D0000
D0001
D0002
D0003
D0004
Word
#000A
D00000
#0002
D00001
#0400
D00002
#0705
D00003
#0064
D00004
#000A
0000
D00010
D00010
D00020
D00000
120001
Execution
condition
231
Communicating between OMRON PLCs Section 8-6
Note 1. With CS/CJ-series PLCs, the Communications Port Enabled Flags at bits
0 to 7 in word A202 turn OFF even when the PCMR(260) instruction is be-
ing executed using the ports corresponding to those flags.
2. Before using the sample program as is, confirm that the memory areas
(words and bits) used in the sample program are not already being used in
the user program o r by Special I/O Units.
When the Communications Port Enabled Flag for port 7
is ON, and SEND(090) is not being executed, the trans-
mission execution program will start when execution
condition CIO 000001 turns ON.
Input CIO 120002 remains ON from the start of
RECV(098) execution until completion.
Control Data Creation
Word
Number of reception words = 16
Source network number = 3
Source node number = 32
Source unit address = 0
Response required.
Communications port No. used = 7
Number of retries = 5
Response monitor time = Default
A total of 16 words of data beginning from word A100
at network number 3, node number 32, unit address 0
(the PLC) is received at word CIO 2000 onwards of the
local node.
Reset Input Creation
Reception Error Display
Reception Data Processing
If there is no reception processing completion error, the
16 words of data received from word CIO 2000 on-
wards is stored at D00040 onwards.
KEEP
120002
000001 A20207
(See note 1.) 120000
120003
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@MOV(21)
@RECV(98)
DIFU(13)
120002 A20207
121001
120002 A21907
Execution
condition
(Continued from previous page.)
120002
@XFER(70)
120002 120003 A21907
(See note 1.)
S
R
Contents Meaning
00 10
00 03
20 00
07 05
00 00
D0005
D0006
D0007
D0008
D0009
D00040
120003
D00005
2000
A100
D00009
#0000
D00008
#0705
D00007
#2000
D00006
#0003
D00005
#0010
2000
#0016
232
Precautions on High Traffic in FINS Communications Section 8-7
8-7 Precautions on High Traffic in FINS Communications
When applications are constructed using FINS communications services,
communications errors (from multiple response timeouts) may occasionally
occur due to high traffic, depending on the system configuration and the appli-
cation programs. This section describes precautions for systems with high
traffic in FINS communications.
■Conditions for High Traffic
A heavy communications load may occur at an EtherNet/IP Unit or built-in
EtherNet/IP port if FINS messages and CIP messages from multiple nodes
are concentrated on that EtherNet/IP Unit or built-in EtherNet/IP port. The
EtherNet/IP Unit or built-in EtherNet/IP port and the CPU Unit may have insuf-
ficient processing capacity for the volume of FINS messages (commands)
that are coming from the network.
For example, suppose that approximately 20 ms are required to process a sin-
gle FINS frame (i.e., 20 ms from the time that the command is received at the
EtherNet/IP Unit or built-in EtherNet/IP port until a response is sent). If 100 or
more FINS frames (commands) are received at once from multiple communi-
cating nodes, it will take approximately 2 seconds to send a response to the
last command. If a timeout is set at the remote node for 2 seconds or less,
then a timeout will be generated. A retry will begin due to the timeout, and the
traffic to the EtherNet/IP Unit or built-in EtherNet/IP port will thus be increased
even further, until ultimately the responses to all the nodes will be too slow. At
this point, the system is overloaded.
■Avoiding Errors due to High Traffic
To avoid high traffic from FINS communications, the communications load
must be kept down to a reasonable level. To accomplish this, follow the proce-
dure below.
1. Specify the node where FINS frames seem to be concentrated.
2. Estimate the total processing time for all of the FINS frames processed at
that node. (For details, refer to 10-5-1 Maximum Transmission Delays (Ex-
cluding Delays in the Network).)
3. Set the timeout value for all of the SEND(090), RECV(098), and
CMND(490) FINS commands at all the remote nodes to at least 1.5 times
the total processing time for all of the FINS frames.
4. As much as possible, implement communications traffic testing up to the
point of actual system operation. If any problem occurs, adjust the traffic.
5. If a commercially-available protocol analyzer can be used, then the actual
FINS frame processing time (i.e., the time from when a command is re-
ceived at the EtherNet/IP Unit or built-in EtherNet/IP port until a response
is sent) can be measured under high traffic conditions and the communi-
cations traffic can be further adjusted as required.
233
SECTION 9
Message Communications
This section describes message communications using FINS commands sent from the ladder program in the CPU Unit of
the PLC.
9-1 Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
9-1-1 Sending Explicit Messages Using CMND(490). . . . . . . . . . . . . . . . 243
9-2 Receiving Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
9-2-1 List of PLC Object Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
234
Sending Explicit Messages Section 9-1
9-1 Sending Explicit Messages
CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports can send
explicit messages. Only CIP unconnected message (UCMM) communications
can be used to send explicit messages. Explicit messages can be sent to the
following destinations.
• EtherNet/IP Units made by other manufacturers
• Other PLCs with a CS/CJ-series EtherNet/IP Unit or built-in EtherNet/IP
port
Example
When the destination is another company’s EtherNet/IP node, an explicit mes-
sage can be sent to the EtherNet/IP Unit or built-in EtherNet/IP port using
FINS command code 28 01 or 28 10, through the Connection Manager class’s
Unconnected Send service, as shown in the following diagram.
When sending an explicit message, set the local node’s EtherNet/IP Unit or
built-in EtherNet/IP port as the destination of the FINS command, and not the
actual destination (other company’s EtherNet/IP node). Specify the node
address of the actual destination in the command data of the explicit message
send command.
There are two ways to send an explicit message send command:
1,2,3... 1. CIP UCMM MESSAGE SEND command (28 10)
Messages can be routed through multiple CIP network layers. (Messages
can be routed through 16 network levels. The explicit message send com-
mand may time out if routing is attempted for more than 16 networks.
2. EXPLICIT MESSAGE SEND command for DeviceNet Units (28 01)
This command is compatible with the DeviceNet Unit’s explicit message
send command (28 01) in the ladder program. The message must be sent
CS/CJ-series EtherNet/IP Unit
CS/CJ-series CPU Unit
Explicit messages can be sent
Explicit message
Ethernet (EtherNet/IP)
Other manufacturer's
EtherNet/IP node
CS/CJ-series EtherNet/IP Uni
t
CS/CJ-series
CPU Unit
CPU Unit
CMND
(490)
Explicit
message FINS
header
Note: Use 28 01 for the
FINS command code.
FINS
header Response
EtherNet/IP Unit
FINS
header
FINS
header
Explicit
message
Response
EtherNet/IP
network
Other company's
EtherNet/IP node
235
Sending Explicit Messages Section 9-1
in the same network layer and the remote node’s IP address range is lim-
ited.
The following diagram shows an example of actual node address specifica-
tions.
Note Depending on conditions, the destination slave may not always accept an
explicit message. Always perform retry processing when sending explicit mes-
sages.
PLC's
CPU
Unit
Explicit message
Other company's
EtherNet/IP node
Destination node address:
Local node address: 05
Node 05
Destination unit address:
FE or 12 (Hex)
The node address of the non-OMRON node is set as the
destination node address in the FINS command data.
Command code
Node address of the non-
OMRON node: 06 Hex
Explicit command block
CMND
S
D
CS
S+1
2801
15 8 7 0
15 8 7 0
06
0
C+3 5FE
FINS
command
EtherNet/IP Unit
with unit number 2
236
Sending Explicit Messages Section 9-1
CIP UCMM MESSAGE SEND (28 10)
This command sends an explicit message for CIP routing to another node’s
specified class and receives a response. There are two command formats:
one with a specified route path (path to the target device), and the other with-
out the route path.
Command Block
• Relay Hop Format
The following format includes the route path (routing service data). Specify
the entire routing path in the command’s request path.
• Last Hop Format
The following format does not include the route path.
28 10 52
Command
code Transport
ID Message
monitoring
time
02 20 06 24 01
Service code
Unconnected Send service: 52 Hex
Request path size = 2 words: 02 Hex
Class ID Connection Manager: 06 Hex
8-bit class ID: 20 Hex
8-bit instance ID: 24 Hex
Instance ID: 01 Hex
Priority/Time Tick
Request path
(variable length)
Time Out Ticks
Request path size
Service code
Routing service data
Routing
service data
Route path size
Request data
(variable length) Route path
(variable length)
Message
request size
Last hop
data Routing
service data
00
Padding data
(when necessary)
Request path 502 bytes max.
502 bytes max.
Service code
Request path size
(variable length) Request data
(variable length)
Request path size
2810 Hex
Command
code Transport
ID Message
monitoring time
502 bytes max.
237
Sending Explicit Messages Section 9-1
Response Block
The following normal response is returned to a transmitted CIP UCMM MES-
SAGE SEND command if it was completed normally.
The following response is returned if an error occurs in a transmitted CIP
UCMM MESSAGE SEND command.
The following response is returned if the CIP UCMM MESSAGE SEND com-
mand could not be sent or timed out.
Parameters
Transport ID (command, response):
When multiple CIP UCMM MESSAGE SEND commands are being sent, the
Transport ID identifies the commands. This Transport ID is returned
unchanged in the response.
Message monitoring time (command):
Specifies the monitoring time in 10-ms units, in order to monitor the time from
the point that the EtherNet/IP Unit or built-in EtherNet/IP port extracts the CIP
explicit message from this command until a response is received. The moni-
toring time can be set between 0.01 and 655.35 s.
Service code (command, response):
In the command, this code is the service code defined for EtherNet/IP.
In the response, bit 15 of the service code specified in the command is turned
ON and the resulting value is returned.
Service code (response)
Service response data
(variable length)
Reserved
Reserved
General status
2810 Hex
00
Hex 00
Hex 00
Hex
Command
code Response
code Transport
ID No. of bytes
received
0000 Hex
502 bytes max.
Service code (response)
Additional status
(variable length)
Reserved
Additional status size
General status
2810 Hex
00
Hex
Command
code Response
code Transport
ID No. of bytes
received
Service
response data
(variable length)
0000 Hex
502 bytes max.
(See note.)
Note: There may be additional data depending on
the response code, e.g., for a relay error.
2810 Hex
Command
code Response
code
238
Sending Explicit Messages Section 9-1
In the routing format for rely hops, the first service code (in the routing service
data) is 52 Hex, which is the Unconnected Send service.
Request path size (command):
Specifies the number of words of data that are specified in the request path
field.
In the routing format for relay hops, the first request path size (in the routing
service data) is 02 Hex.
Request path (command):
Specifies the request path (class ID, instance ID, etc.) in bytes. If there is an
odd number of bytes, pad the last byte with a 0 so that the data is in full word
units.
In the routing format for relay hops, the first request path (in the routing ser-
vice data) is 20 06 24 01 Hex (Connection Manager). For details, refer to the
description of the Route Path in Appendix D CIP Message Communications.
Request data (command):
In the command, specify the data determined by the service code.
In the response, the reception data determined by the service code will be
returned.
Priority/Time tick (command):
The timeout time specified by the Priority Time Tick is used as a base value to
specify the actual timeout value. For details, refer to the description of the Pri-
ority/Time Ticks and Time Out Ticks at the end of Appendix D CIP Message
Communications.
Time Out Ticks (command):
Specifies the base value of the timeout time. For details, refer to the descrip-
tion of the Priority/Time Ticks and Time Out Ticks at the end of Appendix D
CIP Message Communications.
Message request size (command):
Specifies the number of bytes of data from the second service code to the
request data. The data size is specified in LSB, MSB order.
For example, if there are 400 bytes, the data size is 0190 hex bytes, which is
entered as 90 01 hex.
Padding data (command):
If the message request size specifies an odd number of bytes, use 00 hex as
padding in the last byte. The padding data is not required if there is an even
number of bytes.
Route path size (command):
Specifies the number of words of data that are specified in the route path field.
Route path (command):
Specifies the path (route path) to the target device. For details, refer to the
description of the Route Path in Appendix D CIP Message Communications.
No. of bytes received (response):
This hexadecimal value is returned to indicate the number of bytes of data
received after the service code (response).
General status (response):
The general status defined in EtherNet/IP is returned. The normal response is
00 hex. For details, refer to the description of the Response Codes in Appen-
dix D CIP Message Communications.
Additional status size (response):
239
Sending Explicit Messages Section 9-1
This hexadecimal value is returned to indicate the number of words of data in
the additional status field.
Additional status (response):
The additional status defined in EtherNet/IP is returned. For details, refer to
the description of the Response Codes in Appendix D CIP Message Commu-
nications.
Service response data (response):
The reception data determined by the service code is returned.
Description
• The CIP UCMM MESSAGE SEND command is used to send an Ether-
Net/IP-defined explicit message to another company’s node and receive a
response.
• Unlike other FINS commands, the destination of a CIP UCMM MESSAGE
SEND command’s control data is the local node’s EtherNet/IP Unit or
built-in EtherNet/IP port, and the actual destination node is specified in
the command’s route path.
• When an EtherNet/IP Unit or built-in EtherNet/IP port receives an explicit
message, it automatically returns a response to the message.
• When specifying the timeout time, the proper values are different for last-
hop and relay-hop methods. With the last-hop method, set the timeout
time for the actual request service processing. With the relay-hop method,
the timeout for the relay path must be added to the timeout time for the
actual request service processing.
In CIP routing, the node/Unit performing the routing subtracts the timeout
time for 1 hop, deletes its own address from the routing information, and
relays the message to the next node/Unit.
Set the following timeout values for command processing.
The maximum number of relay nodes (Units) is 16. If the number is more
than 16, the explicit message send command may time out even if the con-
ditions of network and each node (Unit) are normal. If more than 16 relay
nodes (Units) have been set, a constant time must be specified for the re-
quest service processing timeout time (normally 0000 hex).
• Priority Time Tick and Time Out Ticks =
(5 s × Number of relay nodes/Units) + Request processing timeout
• Message monitoring time ≥ Priority Time Tick and Time Out Ticks
• CMND(490) timeout set value = Message monitoring time
A timeout may occur sooner than the actual set value, depending on the
point where the timeout occurs in the path.
• General status = 01 hex, and Additional status = 0204 hex
A FINS timeout error response (0205 hex) may occur if the CMND(490)
timeout set value or message monitoring time is less than the Priority Time
Tick and Time Out Ticks.
Note 1. For details on the parameters of explicit messages, refer to the EtherNet/
IP and CIP specifications.
2. The Open DeviceNet Vendor Association, Inc. (ODVA) can be contacted at
the following address to obtain copies of the EtherNet/IP and CIP specifi-
cations.
ODVA Headquarters
4220 Varsity Drive, Suite A
240
Sending Explicit Messages Section 9-1
Ann Arbor, Michigan 48108-5006
USA
TEL: 1 734-975-8840
FAX: 1 734-922-0027
Email odva@odva.org
WEB www.odva.org
241
Sending Explicit Messages Section 9-1
EXPLICIT MESSAGE SEND (28 01)
EXPLICIT MESSAGE SEND will send a DeviceNet Unit-compatible explicit
message to the specified class of another node and receive a response.
The other node is specified with the destination node address in the com-
mand. The actual destination IP address is as follows.
Destination IP address = (Local IP address & Subnet mask)
+ Destination node address
Command Block
Response Block
Normal Response
Error Responses
The following response is returned if an error occurs for the explicit message.
The following response is returned if the explicit message cannot be sent or
times out.
Parameters Destination node address (command):
The node address of the destination of the explicit message.
The node address of the local EtherNet/IP Unit or built-in EtherNet/IP port is
specified in the control data for the CMND(490), but the node address of the
actual destination is specified here in the FINS command. The destination
node address cannot be set to 00 hex or FF hex.
Service code (command, response):
A service code defined for EtherNet/IP. In a normal response, bit 15 of the ser-
vice code specified in the command will be turned ON and returned. In an
error response, 94 Hex will always be returned.
0128
Destination node address
Instance ID Service dataClass IDCommand
code
468 bytes max.
Service code
0128
Destination node address
(
remote node
)
No. of bytes
received Service dataResponse
code
Command
code
498 bytes max.
Service code
00 00
0128
Destination node address
(
remote node
)
Service code 94 (Hex)
No. of bytes
received
Response
code
Command
code Error code
00 00 94
0128
Response
code
Command
code
242
Sending Explicit Messages Section 9-1
Class ID (command):
The class ID of the destination of the explicit message.
Instance ID (command):
The instance ID of the destination of the explicit message.
Service data (command, response):
The data defined for the services codes.
No. of bytes received (response):
The number of bytes received from the destination node address (remote
node).
Destination node address (remote node):
The node address of the OMRON Special I/O Slave Unit or Slave manufac-
tured by another company to which the explicit message was sent is returned.
Error code (response):
An error code defined in EtherNet/IP (1-byte general status and 2-byte addi-
tional status) is returned. The data format is DeviceNet-compatible (2 bytes
total), so the returned Error Code is converted to the 1-byte general status
and a 1-byte additional status (high byte only).
Description
• The EXPLICIT MESSAGE SEND command is used to send an EtherNet/
IP-defined explicit message to another company’s node and receive a
response.
• Unlike other FINS commands, the destination of a EXPLICIT MESSAGE
SEND command’s control data is the local node’s EtherNet/IP Unit or
built-in EtherNet/IP port, and the actual destination node is specified in
the command’s route path.
Always specify the local node’s EtherNet/IP Unit or built-in EtherNet/IP port
in the CMND(490) instruction’s control data. An error will occur if another
node’s Master Unit is specified as the destination.
• When an EtherNet/IP Unit or built-in EtherNet/IP port receives an explicit
message, it automatically returns a response to the message.
• A time of 2 s is used for request service processing timeouts.
Set the CMND(490) instruction’s timeout set value to 2 s or longer.
When there is a timeout, the error code will be 0102 hex.
When the CMND(490) instruction’s timeout set value is less than 2 s, a
FINS timeout error response of 0205 hex may occur.
Note 1. For details on the parameters of explicit messages, refer to the EtherNet/
IP specifications.
2. The Open DeviceNet Vendor Association, Inc. (ODVA) can be contacted at
the following address to obtain copies of the EtherNet/IP and CIP specifi-
cations.
ODVA Headquarters
4220 Varsity Drive, Suite A
Ann Arbor, Michigan 48108-5006
USA
TEL: 1 734-975-8840
FAX: 1 734-922-0027
Email odva@odva.org
WEB www.odva.org
243
Sending Explicit Messages Section 9-1
9-1-1 Sending Explicit Messages Using CMND(490)
With a CS/CJ-series EtherNet/IP Unit or built-in EtherNet/IP port, a
CMND(490) in the CPU Unit’s ladder program can send CIP UCMM explicit
messages.
Send the CIP UCMM explicit message’s command data in a FINS command
following the 2810 hex FINS command code.
The CIP UCMM explicit message’s response is received following the
2810 hex FINS command code and the FINS completion code.
The following command is used: [ CMND S D C ]
S: First command word
D: First response word
C: First control data word
Command data is set in order starting with the word specified for the
CMND(490) operand S (first command word) and continuing with words with
higher addresses in I/O memory in the command block format.
Command Format Example: Get_Attribute_All Service to Identity Object
Routing service data
Transport
ID
8-bit instance ID: 24 Hex
Priority/Time Tick
Time Out Ticks
Message
request size
8-bit class ID
Class ID identity object
8-bit instance ID: 24 Hex
Instance ID Ethernet port: 12 Hex
Route path size (13 bytes)
Padding data
Request path
Request path
Routing service data
Routin
g
service data
Last hop data
Route path
size
(8 words)
Service code
Get_Attribute_All service
Request path size (2 words)
Route path
Route path
Request path size = 2 words: 02 Hex
Class ID Connection Manager: 06 Hex
8-bit class ID: 20 Hex
28 10 00 00 05 DC 52 02 20 06 24 01 0A 0C 06 00
01 02 20 01 24 01 08 00 12 0D 31
1
39
9
32
2.
2E 31
1
36
6
38
8
2E
.
32
2
35
5
30
0
2E
.
32
2
00
Service code
Unconnected Send service: 52 Hex
Command
code
Instance ID
244
Sending Explicit Messages Section 9-1
Setting the Command Data for CMND(490)
The response data is set in the same way, starting from the word specified for
CMND(490) operand D (first response word) and continuing with words with
higher addresses in I/O memory in the response block format.
Note Request path data or request data that is in word (2-byte) or double-word (4-
byte) units, such as word data and ERROR CLEAR codes, is specified from
low to high (U) bytes in command block format. For example, to specify word
data 1234 hex, specify 34 hex and then 12 hex. To specify the double word
data 12345678 hex, specify 78 hex, 56 hex, 34 hex, and then 12 hex. The
command blocks are shown in the following diagram.
Similarly, when the additional status data and service response data in the
response block is in word (2-byte) or double-word (4-byte) units, such as word
FINS command code
Transport ID
Message monitoring time
Service code = 52 hex, Request path size = 02 hex
8-bit class ID = 20 hex, Class ID = 06 hex (Connection Manager)
8-bit instance ID = 24 hex (request path), Instance ID = 01 hex
Priority/Time Tick = 0A hex, Time Out Ticks = 0C hex
Message request size
Service code = 01 hex (Get_Attribute_All service), Request path size = 02 hex
8-bit class ID = 20 hex, Class ID = 01 hex (Identity Object)
8-bit instance ID = 24 hex, Instance ID = 01 hex
Route path size = 8 words
Ethernet port = 12 hex (Extended Link Address Size = 1 hex, Ethernet port number = 2 hex), Route path size = 13 bytes
1 9
2 .
1 6
8 .
2 5
0 .
2
Route path IP address
192.168.250.2
Link
path
Bit
28
00
05
52
20
24
0A
06
01
20
24
08
12
31
32
31
38
32
30
32
S+0
S+1
S+2
S+3
S+4
S+5
S+6
S+7
S+8
S+9
S+10
S+11
S+12
S+13
S+14
S+15
S+16
S+17
S+18
S+19
10
00
DC
02
06
01
0C
00
02
01
01
00
0D
39
2E
36
2E
35
2E
00
15 08 07 00
Command Block
Example: 1234 hex Example: 12345678 hex
Service Data Service Data
The format from CMND(490) operand S onwards will be set as follows:
From higher byte From higher byte
Bit Bit
From lower byte
From lower byte
Bit
Bit
Example: 1234 hex Example: 12345678 hex
245
Sending Explicit Messages Section 9-1
data and ERROR CLEAR codes, is also returned in the same order from low
to high bytes in the response block.
Example: Sending Explicit Messages Using CMND(490)
Operation The identity object information (class ID = 01 hex) is read from the other com-
pany’s EtherNet/IP node at IP address 192.168.250.2, using the CIP UCMM
MESSAGE SEND command, 28 10. The command data is stored in the DM
Area starting at DM01000, and the response data is stored in the DM Area
starting at D02000. If the command ends with an error, the end code is stored
in D00006 and command transmission is retried.
Command Details [CMND S D C ]
S = D01000: First command word
D01000 = 2810 hex Command Code
D01001 = 0000 hex Transport ID: 0000 hex
D01002 = 05DC hex Message monitoring time: 15.00 s
D01003 = 5202 hex Slave code: 52 hex (Unconnected Send)
Request path size: 2 words
D01004 = 2006 hex Request path: 20 06 24 01 hex
(Connection Manager)
Class ID: 06 hex
D01005 = 2401 hex Instance ID: 01 hex
Words S+6 to S+19 contain the request data.
D01006 = 0A0C hex Priority/Time_Tick: 0A hex
Time Out Ticks: 0C hex
D01007 = 0600 hex Message request size: 6 bytes
Words S+8 to S+10 contain the request message request.
D01008 = 0102 hex Service: 01 hex (Get_Attribute_All)
Request path size: 2 words
Words S+9 and S+10 contain the request path.
D01009 = 2001 hex 8-bit class ID: 20 hex
Class ID: 01 hex
D01010 = 2401 hex 8-bit instance ID: 24 hex
Instance ID: 01 hex (Identity object)
Words S+11to S+19 contain the root path.
D01011 = 0800 hex Route path size: 8 words
D01012 = 120D hex Extended link address size = 1 hex
Route path size: 13 bytes (characters) = 0D hex
D01013 = 3139 hex IP address: “19”
D01014 = 322E hex IP address: “2.”
D01015 = 3136 hex IP address: “16”
EtherNet/IP node of other manufacturer
EtherNet/IP Unit
with unit number 0
CMND(490)
instruction
PLC's
CPU
Unit
Network address: 01 hex
Node address: 05 hex
Unit address: 10 hex
Explicit
message
246
Sending Explicit Messages Section 9-1
D01016 = 382E hex IP address: “8.”
D01017 = 3235 hex IP address: “25”
D01018 = 302E hex IP address: “0.”
D01019 = 3200 hex IP address: “2”
Padding data: 00 hex
D = D02000: First response word at local node
C = D00000: First control word
D00000 = 0028 hex Number of command bytes: 40 bytes
D00001 = 0064 hex Number of response bytes: 100 bytes
D00002 = 0001 hex Destination network address: 1
D00003 = 0510 hex Destination node address: 5
Destination unit address: FE hex (or 10 hex)
D00004 = 0000 hex Response, communications port 0, no retries
D00005 = 00A0 hex Response monitoring time: 16.0 s
Response D02000 = 2801 hex Command code
D02001 = 0000 hex FINS completion code
D02002 = 0000 hex Transport ID
D02003 = 001D hex Number of bytes received: 29 bytes
D02004 = 8100 hex Service code (response): 81 hex
Reserved: 00 hex
D02005 = 0000 hex General status: 00 hex
Reserved: 00 hex
Words C+6 to C+18 contain the service response data.
D02006: 2F00 hex
D02007: 0C00 hex
D02008: 0C00 hex
D02009: 0101 hex
D020010: 3000 hex
D020011: 5303 hex
D020012: 0011 hex
D020013: 0A43 hex
D020014: 5331 hex
D020015: 572D hex
D020016: 4549 hex
D020017: 5032 hex
D020018: 3100 hex
247
Sending Explicit Messages Section 9-1
Program Example
Sets 0000 in D00000 to D02999.
Shifts the contents of CIO 0000 one bit to the right and
retries in the next cycle (CIO 000000 ON).
Sends 8 bytes of command data to destination node address 06, receives
14 bytes of response data, and stores it in the local node starting at D02000.
(D00000 is control data.)
Shifts the contents of CIO 0000 one bit to the left.
Copies the completion code (network communications error response code)
from A203 to D00006.
Communications
Enabled Flag
First Cycle Flag
Execution
condition
Online Flag
(n+11, bit 00)
Communications
Enabled Flag Network Communication
Execution Error Flag
Moves 0001 into CIO 0000.
000000
A20011
Sets 0028 in D00000. (Number of send data bytes: 40)
BSET #0000 D00000 D02999
MOV #0028 D00000
MOV #0064 D00001
MOV #0001 D00002
MOV #0510 D00003
MOV #0000 D00004
MOV #00A0 D00005
MOV #2810 D1000
MOV #0000 D1001
MOV #5202 D1003
MOV #2006 D1004
MOV #2401 D1005
MOV #0A0C D1006
MOV #0600 D1007
MOV #0102 D1008
MOV #2001 D1009
MOV #2401 D1010
MOV #0800 D1011
MOV #120D D1012
MOV #3139 D1013
MOV #322E D1014
MOV #3136 D1015
MOV #382E D1016
MOV #3235 D1017
MOV #302E D1018
MOV #3200 D1019
MOV #0001 0000
ASL 0000
CMND D01000 D02000 D00000
MOV A203 D00006
ASR 0000
END
000013
000018
000024
000000 A20200
000001 A20200 A21900
151100
Sets 0064 in D00001. (Number of receive data bytes: 100).
Sets 0001 in D00002. (Destination network address: 01).
Sets 0510 in D00003. (Destination node address: 05, destination unit address: 10)
Sets 0000 in D00004.
(Response required, port number 0, number of retries = 0)
Command data
Set the CIP UCMM MESSAGE SEND command's command data
in words D01000 to D01019 in routing data format.
Sets 00A0 in D00005. (Response monitoring time: 16.0 s)
(071)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(021)
(025)
(490)
(021)
(026)
(001)
MOV #05DC D1002
(021)
248
Receiving Explicit Messages Section 9-2
9-2 Receiving Explicit Messages
The CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports are
equipped with a PLC Object that is functionally compatible with CS/CJ-series
DeviceNet Units. The Unit will receive messages addressed to the PLC
Object, process service requests addressed to the CPU Unit, and return
responses. The CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports
support CIP unconnected message (UCMM) communications and CIP con-
nected (Class 3) communications as reception functions.
The following services are provided by the PLC Object.
• CPU Unit status read/write
• CPU Unit I/O memory read/write
• CPU Unit error log read/clear
Explicit messages can be received from the following sources:
• EtherNet/IP nodes made by other manufacturers
• OMRON PLCs with a CS/CJ-series EtherNet/IP Unit or a CPU Unit with a
built-in EtherNet/IP port. (Messages from CS/CJ-series EtherNet/IP Units
and built-in EtherNet/IP ports must be CIP unconnected messages
(UCMM).)*
* Messages from CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP
ports must be CIP unconnected messages (UCMM).
Example
Note For an EtherNet/IP Unit or built-in EtherNet/IP port with version 2.0 or higher,
change the class ID of the PLC Object from 2F hex to C4 hex.
When using a PLC Object with a DeviceNet Unit or EtherNet/IP Unit with ver-
sion 1.0, and converting to EtherNet/IP Unit or built-in EtherNet/IP port with a
version 2.0 or higher, the class ID must be changed according to the commu-
nications application.
CS/CJ-series
CPU Unit
CS/CJ-series
EtherNet/IP Unit CS/CJ-series
CPU Unit Other company's
Ethernet node
Explicit messages
can be sent.
Explicit message
Ethernet (EtherNet/IP)
CS/CJ-series
EtherNet/IP Unit
249
Receiving Explicit Messages Section 9-2
9-2-1 List of PLC Object Services
PLC Objects provide the following services.
Status Read/Write for CPU Units
Services Service
code Class ID Instance ID Request
service data Contents
CPU Unit Informa-
tion Read 0E Hex C4 Hex
(2F Hex)
(See note.)
00 Hex Attribute ID =
64 Hex Reads the operating mode of the
CPU Unit.
Attribute ID =
65 Hex Reads if there is a fatal or non-fatal
error in the CPU Unit.
Attribute ID =
66 Hex Reads CPU Unit model.
CPU Unit Write 10 Hex Attribute ID =
64 Hex,
Attribute Value
Changes the operating mode of the
CPU Unit.
Attribute ID =
65 Hex
Attribute Value
Clears errors.
CPU Unit Status
Read 40 Hex None Reads the detailed status of the CPU
Unit.
Operation status: Stop, run, CPU
standby
Operating modes: PROGRAM, MON-
ITOR, RUN
Fatal error information: Error flags,
including memory errors, I/O bus
errors, system errors
Messages: Message No. when MSB
instruction executed by CPU Unit
Error codes: Error code for the most
serious errors
Error messages: Messages stored in
CPU Unit when FAL/FALS instruction
executed
250
Receiving Explicit Messages Section 9-2
I/O Memory Read/Write for CPU Units
Note With a EtherNet/IP Unit or built-in EtherNet/IP port with unit version 2.0 or
later, the PLC object class ID is C4 hex. (With unit version 1.0, the PLC object
class ID is F2 hex.)
The commands and responses for the explicit messages that can be sent and
received are described on the following pages.
In the following command and response formats, all boxes represent 1 byte
each.
Service Service
code Class ID Instance ID Request
service
data
Contents
Byte Data Read 1C Hex C4 Hex
(2F Hex)
(See note.)
Specifies
area (01 Hex
to 14 Hex)
Address, No.
of read bytes Reads the specified node data in byte units.
The word data is read in order, from high to
low bytes.
Read data: 200 bytes max.
Word Data
Read 1D Hex Address, No.
of read
words
Reads the specified node data in word
units. The word data is read in order, from
high to low bytes.
Read data: 200 bytes max.
Byte Data Write 1E Hex Address,
byte data Writes the specified node data in byte units.
The word data is specified in order, from
high to low bytes.
Write data: 200 bytes max.
Word Data Write 1F Hex Address
word data Writes the specified node data in word
units. The word data is specified in order,
from high to low bytes.
Write data: 200 bytes max.
251
Receiving Explicit Messages Section 9-2
CPU Information Read (Service Code: 0E Hex)
Reads CPU Unit information, including operating mode, fatal/non-fatal errors,
and the CPU Unit model.
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): 0E Hex is specified for commands.
For responses, the highest bit be ON and 8E Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): Always 00 Hex.
Attribute ID (command): The read information is specified by the attribute ID.
The attribute IDs are listed in the following table.
• CPU Operating Mode (when Attribute ID = 64 Hex)
Reads the CPU Unit operating mode.
• CPU Unit Errors (when Attribute ID = 65 Hex)
Reads if there are any fatal or non-fatal errors in the CPU Unit.
• CPU Unit Model (when Attribute ID = 66 Hex)
Reads the CPU Unit model.
Read data (response): The specified information is returned in order.
• CPU Unit operating mode (attribute ID = 64 Hex).
The CPU Unit operating mode is returned in 1-word (2-byte) hexadecimal for-
mat, as follows:
0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;
0004 Hex: RUN mode
00
(*)
0E C4
(2F)
(*)
Class ID Attribute ID
Instance ID
Service Code
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
8E
Service Code
Attribute Value
Attribute ID (Hex) Contents Attribute value size
64 CPU Unit operating mode 1 word (2 bytes)
65 CPU Unit errors 1 word (2 bytes)
66 CPU Unit model 22 bytes
PROGRAM mode
MONITOR mode
RUN mode
252
Receiving Explicit Messages Section 9-2
Note The codes for the above modes are 1-word (2-byte) data and are returned in
low byte first. For example, for PROGRAM mode, the code is returned as 01
Hex followed by 00 Hex.
• CPU Unit Errors (when Attribute ID = 65 Hex)
The CPU Unit fatal/non-fatal error data is returned in 1-word (2-byte) hexa-
decimal format, as follows:
01 Hex: Error; 00 Hex: No error.
• CPU Unit Model (when Attribute ID = 66 Hex)
The CPU Unit model is returned in ASCII.
Size: 2 bytes (Always 1400 Hex) + Model: 20 bytes (fixed). Unused area is
filled with 20 Hex (spaces) and returned.
CPU Unit Write (Service Code: 10 Hex)
This PLC Object service writes CPU Unit information, including the operating
mode and clearing errors.
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): 10 Hex is specified for commands. For
responses, the highest bit will turn ON and 90E Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): Always 00 Hex.
Attribute ID (command): Information to write is specified by the attribute ID.
The attribute IDs are listed in the following table.
1: Error
20 bytes
Byte Byte Byte Byte Byte
Unit name
00
(*)
10 C4
(2F)
(*)
Class ID Attribute ID
Instance ID
Service Code Attribute Value
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
Service Code
90
Attribute ID (Hex) Contents Attribute value size
64 CPU Unit operating mode 1 word (2 bytes)
65 CPU Unit errors 1 word (2 bytes)
253
Receiving Explicit Messages Section 9-2
• CPU Operating Mode (Attribute ID = 64 Hex)
Changes the CPU Unit operating mode.
The Attribute Values are as follows:
0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;
0004 Hex: RUN mode
Note The specified code for the above operating modes are 1-word (2-byte
data, and are specified with the low byte first. For example, for PRO-
GRAM mode, the code is specified as 01 Hex followed by 00 Hex. Ac-
cordingly, the low to high bytes for the above codes are set as high
to low bytes in I/O memory, when setting the codes as data for oper-
and S of CMND(490).
• Clearing CPU Unit Errors (when Attribute ID = 65 Hex)
Clears any fatal or non-fatal errors in the CPU Unit. Sets the error clear
code to Attribute Value. The error clear codes are listed in the following
table.
Note Error clear codes are 1-word (2-byte) data, so the above codes are
specified with the low byte first. The low to high bytes for the above
codes are set as high to low bytes in I/O memory, when setting the
codes as data for operand S of CMND(490). For example, to specify
battery error 00F7 Hex, specify the error code as F7 Hex followed by
00 Hex, as shown in the following diagram.
Error code
(Hex) Data cleared
FFFE Current error (clears the highest priority error)
0008B Interrupt task error
009A Basic I/O error
009B PLC Setup error
02F0 Inner Board non-fatal error
0300 to 035F Special I/O Unit error
00A0 to 00A1 SYSMAC BUS error
0500 to 055F Special I/O Unit settings error
00E7 I/O verification error
When registered and actual I/O tables are different
When disconnecting or connecting I/O Units
00F7 Battery error
0200 to 020F CS/CJ-series CPU Bus Unit error (last 2 digits are binary code for
the Unit No.)
For parity errors generated when data transferred between CS/CJ-
series CPU Bus Unit and CPU Unit
For watchdog timer errors in CS/CJ-series CPU Bus Unit
0400 to 040F CPU Bus settings error (last 2 digits are binary code for the Unit
No.)
System error (FAL): FAL instruction executed
4101 to 42FF
10 65 F7 0000
C4
(2F)
Class ID Attribute ID
Instance ID
Service Code Attribute Value
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
254
Receiving Explicit Messages Section 9-2
CPU Unit Status Read (Service Code: 40 Hex)
This PLC Object service reads status details (operation status, operating
mode, fatal and non-fatal errors, etc.) from the CPU Unit.
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): 40 Hex is specified for commands. For
responses, the highest bit will turn ON and C0 Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): Always 00 Hex.
Read data (response): The read data is given in the following table. The data
is returned after the service code in the order shown in the table (high to low).
•Operation status: Returns the operation status of the CPU Unit in 1-byte
(2-digit) hexadecimal.
The values of bits 3 to 6 are not fixed. Always mask them when address-
ing the status data.
00
(*)
40 C4
(2F)
(*)
Class ID
Instance ID
Service Code
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
C0
Service Code
Detailed status
Operation Status
RUN mode
Fatal error information (L)
Fatal error information (H)
Non-fatal error information (L)
Non-fatal error information (H)
Message exists/does not exist (L)
Message exists/does not exist (H)
Error code (L)
Error code (H)
Error message (16 bytes)
255
Receiving Explicit Messages Section 9-2
•Operating mode: Returns the operating mode of the CPU Unit in 1-byte
(2-digit) hexadecimal.
0001 Hex: PROGRAM mode; 0002 Hex: MONITOR mode;
0004 Hex: RUN mode
•Fatal error information: Returns the fatal error information for the CPU
Unit in 2 bytes (low to high).
•Non-fatal error information: Returns the non-fatal error information for
the CPU Unit in 2 bytes (low to high).
76543210Bit
Unspecified
Flash memory access status (CS1H, CJ1-H, CJ1M, and CS1D only)
0: Memory is not being written.
1: Memory is being written.
Operation status
0: Stopped (User program is not being executed.)
1: Operating (User program is being executed.)
CPU status
0: Normal
1: CPU standb
y
(
waitin
g
for SYSMAC Bus Remote I/O or other event
)
Battery status (CS1H, CJ1-H, CJ1M, and CS1D only)
0: No battery
1: Battery installed
----
1: System error (FALS)
1: Cycle time over
1: Program error
1: I/O setting error
1: No. of I/O points exceeded
1: Inner Board fatal error
1: Number duplicate use error
1: I/O Bus error
1: Memory error
Unspecified (reserved for system use)
1: Special I/O Unit error
1: CPU Bus settings error
1: Battery error
1: SYSMAC BUS error
1: Special I/O Unit
1: CS1-series CPU Bus Unit error
1: Inner Board error
1: I/O verification error
1: PLC system error
1: Unspecified (reserved for system use)
1: Basic I/O Unit error
1: Interrupt task error
1: Unspecified (reserved for system use)
1: S
y
stem error
(
FAL
)
256
Receiving Explicit Messages Section 9-2
•Message Exists/Does Not Exist: When the MSG instruction is executed
by the CPU Unit, the bit corresponding to the message number will turn
ON and be returned in 2 bytes (from low to high bytes).
•Error Code: The highest priority error code of the errors existing when
the command is executed will be returned in 2-byte decimal (from low to
high bytes). If there are no errors, the error code will be 0000.
Note For information on the severity of error codes, refer to the CS1 Series
CPU Unit Operation Manual (W339) or the CJ Series CPU Unit Op-
eration Manual (W393).
•Error Messages: If the above error codes have occurred when FAL/FALS
instructions are executed with registered messages, those messages are
returned in 16-byte ASCII. If there are no registered messages or if the
error codes have not occurred due to execution of FAL/FALS instructions,
the code is returned in ASCII with 20 Hex (space) in 16 bytes.
Byte Data Read (Service Code: 1C Hex)
Byte Data Read reads any I/O memory area data in a CPU Unit. The read
word data is in byte units. The response block data is returned in low-to-high
byte order.
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): 1C Hex is specified for commands.
For responses, the highest bit will turn ON and 9C Hex will be returned.
Message No. 0 (1: exists; 0: does not exist)
Message No. 1 (1: exists; 0: does not exist)
Message No. 2 (1: exists; 0: does not exist)
Message No. 3 (1: exists; 0: does not exist)
Message No. 4 (1: exists; 0: does not exist)
Message No. 5 (1: exists; 0: does not exist)
Message No. 6 (1: exists; 0: does not exist)
Message No. 7 (1: exists; 0: does not exist)
1C C4
(2F)
(*) (*)
Class ID
Address L
Instance ID
Service Code
No. of bytes read
Address H
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
9C
Service Code
Word data H
Word data L
Word data H
Word data L
Read data (200 b
y
tes max.)
257
Receiving Explicit Messages Section 9-2
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): The memory area that will read the data is specified
as shown in the following table.
Address L, Address H (command): The address of the first word from which
to read the data is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is given in 4-digit
hexadecimal.
Address H: The higher 2 digits when the first word address is given in 4-digit
hexadecimal.
No of Read Bytes (command): The number of bytes of read data is specified
in 1-byte (2-digit) hexadecimal. The range is 01 to C8 Hex (1 to 200 decimal).
No. of bytes received (response): The number of bytes received from the
destination node address (remote node) is returned in hexadecimal.
Destination node address (response): The node address of the CS/CJ-
series EtherNet/IP Unit or built-in EtherNet/IP port that returned the response
is returned in hexadecimal.
Read data (response): The specified area, word, and byte data is returned in
order from word H (high byte: bits 8 to 15) to word L (low byte: bits 0 to 7). If
an odd number is specified for the number of read bytes, the last 1 byte of
data will be read to the high word.
Important Points The actual address L, address H, and number of read bytes that can be spec-
ified depends on the model of the CPU Unit, and the data area being read. Do
not exceed the boundary of the data areas for the PLC you are using.
Word Data Read (Service Code: 1D Hex)
Word Data Read reads I/O memory area data in a CPU Unit. The read word
data is in word units. The response block data is returned in low-to-high byte
order.
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Instance ID (Hex) CPU Unit memory area
for read Word range
01 CIO 0000 to 6143
03 DM D00000 to D32767
04 WR W000 to W511
05 HR H000 to H1535
08 to 20 EM, banks 0 to 18 En_00000 to En_32767
(n: 0 to 18)
C4
(2F)
(*) (*)
1D
Service
Code
No. of words read
Class ID
Instance ID
Address L
Address H
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
258
Receiving Explicit Messages Section 9-2
Response Block
Parameters Service code (command, response): ID Hex is specified for commands. For
responses, the highest bit will turn ON and 9D Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): The type of memory area that will read the data is
specified as shown in the following table.
Address L, Address H (command): The address of the first word to read the
data from is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is given in 4-digit
hexadecimal.
Address H: The higher 2 digits when the first word address is given in 4-digit
hexadecimal.
No of Read Words (command): The number of words of read data is speci-
fied in 1-byte (2-digit) hexadecimal. The range is 01 to 64 Hex (1 to 100 deci-
mal).
Read data (response): The specified area, word, and byte data is returned in
order from word L (low byte: bits 0 to 7) to word H (high byte: bits 8 to 15).
Important Points The actual address L, address H, and number of write data bytes that can be
specified depends on the model of the CPU Unit, and the data area being
written. Do not exceed the boundary of the data areas for the PLC you are
using.
Byte Data Write (Service Code: 1E Hex)
Byte Data Write writes data to an I/O memory area in a CPU Unit. The write
word data is in byte units. The command block is specified in high-to-low byte
order, as shown in the following diagram.
9D
Service Code
Word data L
Word data H
Word data L
Word data H
Read data (200 b
y
tes max.)
Instance ID (Hex) CPU Unit memory area
for read Word range
01 CIO 0000 to 6143
03 DM D00000 to D32767
04 WR W000 to W511
05 HR H000 to H1535
08 to 20 EM, banks 0 to 18 En_00000 to En_32767
(n: 0 to 18)
259
Receiving Explicit Messages Section 9-2
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): IE Hex is specified for commands. For
responses, the highest bit will turn ON and 9E Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): The type of memory area to which the data will be
written is specified as shown in the following table.
Address L, Address H (command): The address of the first word to which
the data will be written is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is displayed in 4-
digit hexadecimal.
Address H: The higher 2 digits when the first word address is displayed in 4-
digit hexadecimal.
Write data (response): The specified area and write data is returned in order
from word H (higher byte: bits 8 to 15) to word L (lower byte: bits 0 to 7). For
byte data write, specify an even number.
Important Points The actual address L, address H, and number of write data bytes that can be
specified depends on the model of the CPU Unit, and the data area being
written. Do not exceed the boundary of the data areas for the PLC you are
using.
Word Data Write (Service Code: 1F Hex)
Word Data Write writes data to any I/O memory area in a CPU Unit. The write
word data is in word units. The response block data is returned in low-to-high
byte order.
Word data L
Word data H
Word data L
Write data
(
200 b
y
tes max.
)
Word data H
(*)
C4
(2F)
(*)
1E
Service
Code
Class ID
Instance ID
Address L
Address H
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
Service Code
9E
Instance ID (Hex) CPU Unit memory area
for write Word range
01 CIO 0000 to 6143
03 DM D00000 to D32767
04 WR W000 to W511
05 HR H000 to H1535
08 to 20 EM, banks 0 to 18 En_00000 to En_32767
(n: 0 to 18)
260
Receiving Explicit Messages Section 9-2
Command Block
Note A body format of either 8 bits or 16 bits is possible.
Response Block
Parameters Service code (command, response): IF Hex is specified for commands. For
responses, the highest bit will turn ON and 9F Hex will be returned.
Class ID (command): Always C4 (2F).
The class ID depends on the unit version. The class ID is C4 for unit version
2.0, and 2F for unit version 1.0.
Instance ID (command): The memory area to which the data is written is
specified as shown in the following table.
Address L, Address H (command): The address of the first word to which
the data is written is specified in hexadecimal as shown below.
Address L: The lower 2 digits when the first word address is displayed in 4-
digit hexadecimal.
Address H: The higher 2 digits when the first word address is displayed in 4-
digit hexadecimal.
Write data (response): The specified area and write data is returned in order
from word L (lower byte: bits 0 to 7) to word H (higher byte: bits 8 to 15).
Important Points The actual address L, address H, and number of write data bytes that can be
specified depends on the model of the CPU Unit, and the data area being
written. Do not exceed the boundary of the data areas for the PLC you are
using.
Address L
Address H
Word data H
Word data L
Word data H
Write data (200 b
y
tes max.)
Word data L
(*)
C4
(2F)
(*)
1F
Service
Code
Class ID
Instance ID
The class ID depends on the unit version.
Version 2.0: The class ID is C4.
Version 1.0: The class ID is 2F.
Service Code
9F
Instance ID (Hex) CPU Unit memory area
for write Word range
01 CIO 0000 to 6143
03 DM D00000 to D32767
04 WR W000 to W511
05 HR H000 to H1535
08 to 20 EM, banks 0 to 18 En_00000 to En_32767
(n: 0 to 18)
261
SECTION 10
Communications Performance and Communications Load
This section describes the communications performance in an EtherNet/IP network, and shows how to estimate the I/O
response times and transmission delays.
10-1 Communications System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
10-1-1 Tag Data Link Communications Method . . . . . . . . . . . . . . . . . . . . . 262
10-1-2 Calculating the Number of Connections. . . . . . . . . . . . . . . . . . . . . . 264
10-1-3 Network Transmission Delay Time . . . . . . . . . . . . . . . . . . . . . . . . . 265
10-2 Adjusting the Communications Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
10-2-1 Checking Bandwidth Usage for Tag Data Links . . . . . . . . . . . . . . . 269
10-2-2 Tag Data Link Bandwidth Usage and RPI . . . . . . . . . . . . . . . . . . . . 270
10-2-3 Adjusting Device Bandwidth Usage. . . . . . . . . . . . . . . . . . . . . . . . . 271
10-2-4 Changing the RPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
10-2-5 RPI Setting Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
10-3 I/O Response Time in Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
10-3-1 Timing of Data Transmissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
10-3-2 EtherNet/IP Unit or CJ2H Built-in Port Data Processing Time . . . . 283
10-3-3 Effect on the CPU Unit’s Cycle Time. . . . . . . . . . . . . . . . . . . . . . . . 284
10-3-4 Tag Data Link I/O Response Time Calculation Example. . . . . . . . . 285
10-4 Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports. . . . . . . . . 291
10-4-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
10-4-2 Tag Data Link I/O Response Time . . . . . . . . . . . . . . . . . . . . . . . . . . 292
10-5 Message Service Transmission Delay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
10-5-1 Maximum Transmission Delays (Excluding Delays in the Network) 294
262
Communications System Section 10-1
10-1 Communications System
10-1-1 Tag Data Link Communications Method
Packet Interval (RPI)
Settings In EtherNet/IP tag data links, the data transmission period is set for each con-
nection as the packet interval (RPI). The target device will send data (i.e., out-
put tags) once each packet interval (RPI), regardless of the number of nodes.
Also, the heartbeat frame is sent from the originator to the target for each con-
nection. The target uses the heartbeat to check to see if errors have occurred
in the connection with the originator. The data transmission period of the
heartbeat frame depends on the packet interval (RPI) settings.
■Heartbeat Frame Transmission Period
• Packet interval < 100 ms
The heartbeat frame transmission period is 100 ms.
• Packet interval ≥ 100 ms
The heartbeat frame transmission period is the same as the RPI.
Example
In this example, 2 tag data link connections are set for node 2 (the originator)
and node 1 (the target).
The packet interval (RPI) for output data 1 is set to 10 ms.
The packet interval (RPI) for output data 2 is set to 15 ms.
In this case, output data 1 is sent from node 1 to node 2 every 10 ms, and out-
put data 2 is sent from node 1 to node 2 every 15 ms, as shown in the follow-
ing diagram. Also, data is sent from node 2 (the originator) to node 1 (the
target) with a heartbeat of 100 ms for connection 1 and a heartbeat of 100 ms
for connection 2.
10 ms
10 ms
15 ms
Originator
Target
Connection 1 heartbeat
Connection 2 heartbeat
100-ms interval
100-ms interval
Node 1 Node 2
Output data 1
Output data 2
Output data 1
Output data 2
Output data 1
263
Communications System Section 10-1
Packet Interval (RPI)
and Bandwidth Usage
(PPS)
In a tag data link, the number of packets transferred each second is called the
bandwidth used or PPS (packets per second).
The PPS is calculated from the RPI and heartbeat as follows for each connec-
tion:
The following equation is used to calculate the total number of packets trans-
ferred by each EtherNet/IP Unit or built-in EtherNet/IP port in 1 second.
Note Connections set as target connections must be added, too.
The maximum number of packets that the Unit can transfer in 1 second
(called the allowed Unit bandwidth) is 6,000 pps (CJ2M: 3,000 pps), so set the
connection below this maximum value.
Example
Node 1 has both originator and target connections, with send RPI of 200 ms
and 2 ms, and receive RPI of 1 ms.
Node 2 has originator connections only, with receive RPI of 200 ms, 2 ms, and
5 ms.
Node 3 has target connections only, with send RPI of 5 ms and 1 ms.
Each node’s total PPS is calculated as follows.
• Total PPS of node 1 Unit
= 1,000 / 200 ms + 1,000 / 2 ms + 1,000 / 1 ms (for data)
+1,000 / 200 ms + 1,000 / 100 ms + 1,000 / 100 ms (for heartbeat)
= 1,530 pps
• Total PPS of node 2 Unit
= 1,000 / 200 ms + 1,000 / 2 ms + 1,000 / 5 ms (for data)
+1,000 / 200 ms + 1,000 / 100 ms + 1,000 / 100 ms (for heartbeat)
= 730 pps
• Total PPS of node 3 Unit
= 1,000 / 5 ms + 1,000 / 1 ms (for data)
+1,000 / 100 ms + 1,000 / 100 ms (for heartbeat)
= 1,220 pps
All of the Units are within the allowed Unit bandwidth of 6,000 pps (CJ2M:
3,000 pps), so they can transfer data.
PPS used in a connection (pps)
= (1,000 ÷ RPI (ms)) + (1,000 ÷ Heartbeat transmission period (ms))
Unit’s total PPS = Total PPS of originator connections
+ Total PPS of target connections (See note.)
RPI: 1 ms
HB: 100 ms
O: Originator
T: Target
HB: Heartbeat
O
T
T
O T
O T
O
RPI:5ms
HB:100ms
Node 1
Node 3
RPI: 2 ms
HB: 100 ms
RPI: 200 ms
HB: 200 ms
Node 2
264
Communications System Section 10-1
10-1-2 Calculating the Number of Connections
The maximum number of connections for the Unit is 32 for the CJ2M and 256
for other CPU Units.
The number of connections must be set to 32 or less for the CJ2M and 256 or
less for other CPU Units combining both connections that the Unit opens as
the originator and connections that are opened from an originator with the
Unit as the target.
Example
Node 1 opens two connections as the target with node 2 and one connection
as the originator with node 3. Therefore, the total is three connections. Node 2
opens two connections as the originator with node 1 and one connection as
the target with node 3. Therefore, the total is three connections. Node 3 opens
one connection as the target with node 1 and one connection as the target
with node 2. Therefore, the total is two connections. In either case, the con-
nections can be opened because the maximum number of connections for the
Unit is less than 32 for the CJ2M and less than 256 for other CPU Units.
Also, if multicast is set, one packet will be sent, but the number of connections
will be consumed.
Example
Node 3 sends one multicast packet to node 1 and node 2. At that time, node 3
opens one connection as the target with node 1 and one connection as the
target with node 2 for a total of two connections. Caution is required because
the number of connections consumed is the same as for unicast connections
even when multicast connections are set.
O
TT
O T
O T
O
Node 1
Node 3
O: Originato
r
T: Target
Node 2
T
O T
O
Node 1
Node 3
O: Originato
r
T: Target
Node 2
Multicast
Multicast
265
Communications System Section 10-1
10-1-3 Network Transmission Delay Time
In an EtherNet/IP network, the tag data link packets are sent once each
packet interval (RPI), but several delays occur between the transmission of
packets from each node and the arrival of the packets at the destination
nodes. The following diagram shows the 4 major delay sources.
Total network transmission delay = (1) Send processing delay + (2) Ca-
ble delays + (3) Switching hub delay
+ (4) Receive processing delay
The lengths of these delays depend on many factors, such as the tag data link
connection settings (number of connections and data sizes), number of
nodes, the switching hub being used, and cable lengths. Each delay is
described in detail below.
1. Send Processing
Delay The send processing delay is the delay that occurs within the EtherNet/IP Unit
or built-in EtherNet/IP port when data packets are sent once each packet
interval. This delay varies with the RPI error shown in the following graph, so
the send processing time is the maximum value for each RPI.
2. Cable Delay The cable delay is the time required for the data signal to pass through the
cable and reach the destination. When an STP (shielded twisted-pair) cable of
category 5, 5e, or higher is being used, the maximum cable delay is 545 ns/
100 m. The cable delay represents a very small percentage of the total tag
data link delay.
EtherNet/IP
Unit
Switching hub
(1) Send
processing
delay
(
2
)
Cable dela
y(
2
)
Cable dela
y(
3
)
Switchin
g
hub dela
y
EtherNet/IP
Unit
(4) Receive
processing
delay
Data
Packet interval (RPI) RPI error (±) (%)
0.5 to 1,000 ms 15 − (RPI (ms) ÷ 100)
1,000 ms to 10,000 ms 5% of the RPI
0
2
4
6
8
10
12
14
16
0 1,000 2,000 3,000 4,000 5,000 6,000 7,000 8,000 9,000 10,000
RPI [ms]
RPI error (±)[%]
266
Communications System Section 10-1
3. Switching Hub
Delay The switching hub delay is the delay time between the arrival of the packet at
the switching hub and the output of the packet from the hub’s transmission
port. This delay depends on the total number of connections used for recep-
tion and data sizes used in the tag data links. In addition, this delay depends
on the switching hub maker and model, but the delay can be approximated
with the following table. (For a precise estimate, contact the switching hub
manufacturer.)
The following values are the delays when cascade connections are not being
used. If cascade connections are used, more nodes can be connected, but
the switching hub delays will increase.
4. Receive Processing
Delay The receive processing delay is the delay that occurs within the EtherNet/IP
Unit or built-in EtherNet/IP port from the reception of the data packet at the
Unit until the completion of reception processing in the Unit. This delay
depends on the size of the connections used in the tag data links and the
number of connections. In practice, the delay depends on the number of con-
nections used in tag data links with less than 200 words. If the number of con-
nections is “n”, the maximum delay can be calculated with the following
equation.
Maximum reception processing delay = 1 + (n × 0.043) ms
The size of the connections may cause a delay when the data sizes are
smaller and a large number of packets may be received in a fixed interval,
because the data may wait for receive processing.
Example Calculation
of the Tag Data Link
Delay
This example shows how to calculate the tag data link delay when the follow-
ing tag data link connection settings have been made.
In this case, 17 EtherNet/IP Units or built-in EtherNet/IP ports are being used,
and one Unit is receiving 200 words of data from each of the other Units at a
packet interval (RPI) of 5 ms. Thus, 16 tag data link connections are used.
The length of the cables between the Units is 50 m for all connections.
Send processing delay = 5 ms × (15 − 5/100)% = 0.7475 ms
Cable delay = 545 ns × 50 m/100 = 272.5 ns
Switching hub delay = 0.7 ms
Receive processing delay = 1 + (16 × 0.043) ms = 1.688 ms
Tag data link delay = 0.7475 ms + 0.0002725 ms + 0.7 ms + 1.688 ms
≈ 3.14 ms
Words per connection Number of connections used for reception
16 32 64 128 256
2 words 0.2 ms 0.3 ms 0.5 ms 1.0 ms 1.9 ms
200 words 0.7 ms 1.3 ms 2.5 ms 5.0 ms 10.0 ms
400 words 1.2 ms 2.3 ms 4.6 ms 9.1 ms 18.2 ms
600 words 1.7 ms 3.3 ms 6.6 ms 13.2 ms 26.4 ms
722 words 2.0 ms 4.0 ms 7.9 ms 15.7 ms 31.4 ms
267
Communications System Section 10-1
PLC #1 PLC #2 PLC #3 PLC #17
#17
#3
#2 200 words
200 words
200 words
× 16
5 ms
5 ms
200 words
5 ms
268
Adjusting the Communications Load Section 10-2
10-2 Adjusting the Communications Load
In an Ethernet network using a switching hub, the network bandwidth is not
shared by all of the nodes; independent transmission paths are established
between individual nodes through the switching hub.
A dedicated communications buffer is established in the switching hub for
communications between the nodes and full-duplex communications (simulta-
neous transmission and reception) are performed asynchronously with other
transmission paths. The communications load in other transmission paths
does not affect communications, so packet collisions do not occur and stable,
high-speed communications can be performed.
The switching hub functions shown in the following table determine the perfor-
mance of tag data links.
The following table shows the tag data link settings that can be made for indi-
vidual EtherNet/IP Units as well as the setting ranges.
When the tag data link settings exceed the capabilities of the switching hub
being used, increase the RPI value. Particularly when using a switching hub
that does not support multicast filtering, the settings must be made consider-
ing that multicast packets will be sent even to nodes without connection set-
tings.
In addition, if the required tag data link performance cannot be achieved with
the switching hub’s capabilities, reevaluate the overall network configuration
and correct it by taking steps such as selecting a different switching hub or
splitting the network.
The following sections show how to check the device bandwidth being used
by the tag data links in the designed network, and how to set the appropriate
values.
Note If the Network Configurator is used to set the connection type in the connec-
tion settings to a multicast connection, multicast packets will be used. If the
connection type is set to a point-to-point connection, multicast packets will not
be used.
Item Description
Buffer capacity This is the amount of data that can be buffered when packets
accumulate at the switching hub.
Multicast filtering This function transfers multicast packets to specific nodes
only.
QoS function This function performs priority control on packet transfers.
Item Contents Settings
Network bandwidth Physical Ethernet baud rate 100 Mbps or 10 Mbps
Allowed tag data link
communications band-
width
Maximum number of tag data
link packets that can be pro-
cessed in 1 second (pps: pack-
ets per second)
CJ2M: 3,000 pps max.
Other CPU Units: 6,000
pps max.
Connection resources Number of connections that can
be established CJ2M: 32 max.
Other CPU Units:
256 max.
Packet interval
(RPI: Requested Packet
Interval)
Refresh cycle for tag data CJ2M: 1 to 1,000 ms
Other CPU Units:
0.5 to 10,000 ms
(in 0.5 ms units)
269
Adjusting the Communications Load Section 10-2
10-2-1 Checking Bandwidth Usage for Tag Data Links
The Network Configurator can display the bandwidth actually used for tag
data links at each EtherNet/IP Unit, based on the connections set in the net-
work configuration.
The device bandwidth used by tag data links can be checked by clicking the
Detail Button in the Usage of Device Bandwidth Area at the bottom of the Net-
work Configuration Window.
Item Description
# The IP address of the device.
Comment A description of the device. The comment is displayed below
the device icon. The model number of the device is displayed
by default.
Usage of Capacity The percentage of the allowable communications bandwidth
used for tag data links for the device is displayed.
Bandwidth used ÷ Allowable tag data link bandwidth
The values outside parentheses are for when multicast filtering
is used.
The values inside parentheses are for when multicast filtering
is not used.
Mbit/s The bandwidth used for communications by the device of the
100-Mbps network bandwidth is shown.
The values outside parentheses are for when multicast filtering
is used.
The values inside parentheses are for when multicast filtering
is not used.
Usage of IP Multi-
cast Addresses The number of multicast IP addresses actually used for com-
munications by the device is shown.
270
Adjusting the Communications Load Section 10-2
Checking the Usage of
Capacity and Network
Bandwidth for Tag Data
Links
The percentage of the allowable communications bandwidth for tag data links
for each EtherNet/IP Unit is displayed as the Usage of Capacity and the band-
width used for tag data link communications in the entire network is displayed
as the Mbit/s.
The usage of capacity and used network bandwidth that are displayed in
parentheses are for a switching hub that does not use multicast filtering. In
this case, multicast packets will be sent to even the nodes without connection
settings, so the displayed values will include these packets as well.
These values can be adjusted according to instructions in 10-2-4 Changing
the RPI.
Checking the Total
Number of Multicast IP
Addresses in the Network
When using a switching hub that provides multicast filtering, there must be
enough multicast filters for the network being used. The number of multicast
IP address used in the entire network that is displayed by the Network Config-
urator as the Network Total of Max. Mbit/s is based on connection settings.
Make sure that the number of multicast IP addresses used in the entire net-
work does not exceed the number of multicast filters supported by the switch-
ing hub. If necessary, change to a switching hub with enough multicast filters,
or adjust the usage of capacity and network bandwidth for tag data links (Mbit/
s) values given for a switching hub without multicast filtering (i.e., the values in
parentheses). Adjust these values according to instructions in 10-2-4 Chang-
ing the RPI.
Checking the Total
Maximum Network
Bandwidth
The Network Configurator displays the total maximum bandwidth that can be
used for the entire network as the Network Total of Max. Mbit/s. This value
indicates the maximum bandwidth that can be used on the transmission paths
when switching hubs are cascaded. If the value exceeds the bandwidth of a
cascade connection in the actual network, the maximum bandwidth for part of
the communications path may be exceeded, depending on how the network is
wired.
If this occurs, either calculate the bandwidth usage for each communications
path and be sure that the maximum bandwidth is not exceeded for any cas-
cade connection, or adjust the bandwidth for all cascade connections so that
the total maximum network bandwidth is not exceeded. Adjust the bandwidth
according to instructions in 10-2-4 Changing the RPI.
10-2-2 Tag Data Link Bandwidth Usage and RPI
The usage of capacity can be adjusted using the RPI setting. If the RPI is
made shorter, the usage of capacity will increase. If the RPI is made longer,
the usage of capacity will decrease.
The RPI can be set in any one of the following ways.
• Setting the same interval for all connections
• Setting a particular device’s connection
• Setting a particular connection
When the same RPI is set for all connections, the usage of capacity will basi-
cally increase proportionally as the RPI is made shorter.
Total usage of IP
multicast addresses The number of multicast IP addresses used in the entire net-
work is shown. This value is used to estimate the number of
multicast filters for switching.
Network Total of
Max. Mbit/s The total network bandwidth used for tag data link communica-
tions in the entire network is shown. Tag data links will not
operate normally if 100 Mbps is exceeded for the network
bandwidth.
Item Description
271
Adjusting the Communications Load Section 10-2
Example:
If the RPI is set to 50 ms for all connections and the usage of capacity is
40%, the usage of capacity may increase to 80% when the RPI is reduced
to 25 ms for all connections.
Note Performing message communications or other network operations from the
Network Configurator (such as monitoring or other operations that place a
load on the network) or from the user application when the tag data link band-
width usage of capacity is between 80% and 100% can create an excessive
load on the network and result in timeouts. If timeouts occur, increase one or
all of the RPI settings or reduce the usage of capacity.
10-2-3 Adjusting Device Bandwidth Usage
Switching Hubs without
Multicast Filtering (100-
Mbps Hubs)
• Is the network bandwidth without multicast filtering usage under
100 Mbps for each node? (This appears as “Mbit/s” in the dialog box
shown on page 269.)
→ If any node exceeds 100 Mbps, change the connections settings, such
as the RPI.
• Is the usage of capacity without multicast filtering under 100% for each
node? (This appears as “Usage of Capacity” in the dialog box shown on
page 269.)
→ If any node exceeds 100%, change the connections settings, such as
the RPI.
• Is the total network bandwidth usage under 100 Mbps? (This appears as
“Network Total of Max. Mbit/s” in the dialog box shown on page 269.)
→ If the total bandwidth usage exceeds 100 Mbps, the bandwidth of part
of the transmission path (e.g., a switching hub or media converter) had
been exceeded as the result of how the network was wired (e.g., switch
hub or cascade connection), causing a tag data link to operate abnor-
mally. Check the bandwidth of the transmission path for all cascade con-
nections. If the bandwidth is exceeded, rewire the network or increase the
bandwidth between switching hubs (e.g., to 1 Gbps). If these countermea-
sures are not possible, change the connection settings, e.g., the RPI set-
tings, and adjust the bandwidth for all cascade connections until the total
network bandwidth is not exceeded.
Switching Hubs with
Multicast Filtering (100-
Mbps Hubs)
• Is the network bandwidth usage under 100 Mbps for each node?
→ If any node exceeds 100 Mbps, change the connections settings, such
as the RPI.
• Is the usage of capacity under 100% for each node?
→ If any node exceeds 100%, change the connections settings, such as
the RPI.
• Is the total network bandwidth usage under 100 Mbps? (This appears as
“Network Total of Max. Mbit/s” in the dialog box shown on page 269.)
→ If the total bandwidth usage exceeds 100 Mbps, the bandwidth of part
of the transmission path (e.g., a switching hub or media converter) had
been exceeded as the result of how the network was wired (e.g., switch
hub or cascade connection), causing a tag data link to operate abnor-
mally. Check the bandwidth of the transmission path for all cascade con-
nections. If the bandwidth is exceeded, rewire the network or increase the
bandwidth between switching hubs (e.g., to 1 Gbps). If these countermea-
sures are not possible, change the connection settings, e.g., the RPI set-
tings, and adjust the bandwidth for all cascade connections until the total
network bandwidth is not exceeded.
272
Adjusting the Communications Load Section 10-2
• Is the network bandwidth usage without multicast filtering under 100
Mbps for each node or the usage of capacity without multicast filtering
under 100% for each node? (These appear as “Mbit/s” and “Usage of
Capacity” in the dialog box shown on page 269.)
→ If the total bandwidth usage exceeds 100 Mbps, the bandwidth of part
of the transmission path (e.g., a switching hub or media converter) had
been exceeded as the result of how the network was wired (e.g., switch
hub or cascade connection), causing a tag data link to operate abnor-
mally. Check the bandwidth of the transmission path for all cascade con-
nections. If the bandwidth is exceeded, rewire the network or increase the
bandwidth between switching hubs (e.g., to 1 Gbps). If these countermea-
sures are not possible, change the connection settings, e.g., the RPI set-
tings, and adjust the bandwidth for all cascade connections until the total
network bandwidth is not exceeded.
10-2-4 Changing the RPI
You can check the usage of capacity offline without multicast filtering against
the tag data link's allowable bandwidth by following the procedures in 10-2-1
Checking Bandwidth Usage for Tag Data Links. The usage of capacity without
multicast filtering can be adjusted against the tag data link's allowable band-
width by changing the packet interval (RPI). If the required communications
performance cannot be achieved by changing the settings, reevaluate the net-
work starting with the network configuration.
1,2,3... 1. Make the required settings in the Network Configurator’s Network Config-
uration Window.
2. Click the Detail Button in the Usage of Device Bandwidth Area at the bot-
tom of the Network Configuration Window.
The Usage of Device Bandwidth Dialog Box will be displayed.
273
Adjusting the Communications Load Section 10-2
The Usage of Capacity column will show the percentage of the allowed tag
data link bandwidth being used, and the Mbit/s column will show the net-
work bandwidth being used.
3. The usage of capacity can be adjusted by changing the associated devic-
es’ RPI settings.
The RPI settings can be changed with the following three methods.
Method 1: Same Packet Interval Set for all Connections
The usage of capacity can be adjusted by changing the RPI for all of the
connections at the same time.
a. Click the Set Packet Interval (RPI) Button at the bottom of the Usage
of Device Bandwidth Dialog Box.
b. The Set Packet Interval (RPI) Dialog Box will be displayed. Input a new
RPI value, and click the OK Button.
274
Adjusting the Communications Load Section 10-2
Method 2: Changing a Particular Device’s RPI Setting
The usage of capacity can be adjusted for only a particular device by
changing the packet intervals (RPI) for all of the device’s connections to-
gether. In this case, the usage of capacity will also change for the devices
that are the target devices of the connection which was adjusted.
a. Click the Set Packet Interval (RPI) Button at the bottom of the Usage
of Device Bandwidth Dialog Box.
b. The Set Packet Interval (RPI) Dialog Box will be displayed. In the Tar-
get Device Area, deselect the target devices that are not being adjust-
ed by removing the check marks.
c. Input a new RPI value, and click the OK Button.
Method 3: Changing a Particular Connection’s RPI Setting
The usage of capacity can be adjusted by individually changing the packet
intervals (RPI) setting for a particular connection. In this case, the usage
of capacity will also change for the device that is the target device of the
connection which was adjusted.
275
Adjusting the Communications Load Section 10-2
a. Click the Close Button at the bottom of the Usage of Device Bandwidth
Dialog Box.
b. Double-click the device that is set as the originator of the desired con-
nection. The Edit Device Parameters Dialog Box will be displayed.
c. In the Register Device List, select the connection for which you want
to change the RPI, and click the Edit Button.
d. The device’s Edit Connections Dialog Box will be displayed. Input a
new RPI value, and click the OK Button.
276
Adjusting the Communications Load Section 10-2
4. If the usage of capacity cannot be adjusted to the desired level when the
setting described above has been performed, reconsider the network con-
figuration considering the following points. Refer to 10-2-3 Adjusting De-
vice Bandwidth Usage.
• Reduce the number of nodes and number of connections.
• Split the network.
5. Check the bandwidth usage again.
If the connection settings have been changed, click the Detail Button in the
Usage of Device Bandwidth Area at the bottom of the Network Configura-
tion Window and check bandwidth usage according to the instructions in
10-2-1 Checking Bandwidth Usage for Tag Data Links. It is particularly im-
portant to check the usage of capacity when an individual connection’s RPI
setting was changed without using the Set Packet Interval (RPI) Button at
the bottom of the Usage of Device Bandwidth Dialog Box.
6. Run user tests to verify that there are no problems with the new settings.
10-2-5 RPI Setting Examples
The following examples explain how to calculate the packet intervals (RPI) in
the following network configuration.
277
Adjusting the Communications Load Section 10-2
Example Conditions
Connections
In this example, there are 10 CS1W-EIP21 Units and 10 CJ1W-EIP21 Units
for a total of 20 devices connected in the network. Each device has one 100-
word tag for transmission and nineteen 100-word tags for reception, so that
the Units exchange data mutually.
By default, the packet intervals (RPI) are set to 10 ms for all of the connec-
tions. The devices’ IP addresses range from 192.168.250.1 to
192.168.250.20.
Checking the Device
Bandwidth Usage When the Detail Button is clicked in the Usage of Device Bandwidth Area, it is
apparent that the percentage of the allowed tag data link bandwidth being
used by each device’s tag data link (Usage of Capacity) is 39.67%, as shown
in the following dialog box.
IP address: 192.168.250.1 19 2.168.250.2 192.16 8. 250.3
CS1W-EIP 21 CS1W-EIP21
100 words
100 words
100 words
Transmit
Transmit
Transmit
Transmit
192.168.250.20
CJ1W-EIP21
10 CS1W-EIP21 Units + 10 CJ1W-EIP21 Units = 20 Units total
The RPI is 10 ms (ethernet default) for all connections.
Tag data link area with
100 words × 20 Units
CS1W-EIP 21
100 words
278
Adjusting the Communications Load Section 10-2
Changing the
Settings Method 1: Same Packet Interval Setting for All Connections
The percentage of the allowed tag data link bandwidth being used (Usage of
Capacity) was 39.67% with the RPI set to 10.0 ms for all of the connections,
so the RPI will be set to 5.0 ms, with a target of 80% or less of the allowable
bandwidth.
Click the Set Packet Interval (RPI) Button at the bottom of the Usage of
Device Bandwidth Dialog Box. The Set Packet Interval (RPI) Dialog Box will
be displayed. Input 5.0 ms as the new RPI value, and click the OK Button.
279
Adjusting the Communications Load Section 10-2
If the packet interval for all connections has been set to the same setting, the
dialog box will show that the usage of capacity for the tag data link's allowable
communications bandwidth is 73.00% and the fastest set value is 5.0 ms.
Method 2: Changing the Packet Interval (RPI) of Only Specific Devices
In this example, we want faster tag data links for devices 192.168.250.1 and
192.168.250.10 only. Click the Set Packet Interval (RPI) Button at the bottom
of the Usage of Device Bandwidth Dialog Box to display the Set Packet Inter-
val (RPI) Dialog Box.
In the Target Device Area, deselect all devices other than 192.168.250.1 and
192.168.250.10 by removing the corresponding check marks. Input 5.0 ms as
the new RPI value, and click the OK Button.
The percentage of the allowed tag data link bandwidth being used (Usage of
Capacity) increases to 74.67% for devices 192.168.250.1 and
192.168.250.10, which indicates that the RPI is set to a higher speed for
these devices’ connections.
280
Adjusting the Communications Load Section 10-2
The Usage of Capacity values also indicate that the Usage of Capacity has
increased (from 39.67% to 43.00%) for all of the other devices, which connect
with devices 192.168.250.1 and 192.168.250.10.
In this case, if there is no multicast filter, the value becomes 106.33%. If there
is no multicast filter for a switching hub, communications errors may occur
depending on the communications load of the EtherNet/IP Unit or built-in Eth-
erNet/IP Unit port.
281
Adjusting the Communications Load Section 10-2
Method 3: Changing the Packet Interval (RPI) of Only Specific
Connections
In this example, we want a faster tag data links for just a particular connection
of device 192.168.250.1.
Double-click device 192.168.250.1 in the Network Configuration Window.
Information about the connection with device 192.168.250.20 is registered in
the Register Device List. Double-click this connection to edit the settings.
282
Adjusting the Communications Load Section 10-2
In the Edit Connection Dialog Box, input 1.0 ms as the new RPI value, and
click the OK Button. The tag data link bandwidth being used by device
192.168.250.1 (Usage of Capacity) increases to 54.67%, which indicates that
a RPI is set to a higher speed for this device.
In this case, the tag data link bandwidth being used by device 192.168.250.20
(Usage of Capacity) also increases (from 39.67% to 56.33%).
283
I/O Response Time in Tag Data Links Section 10-3
10-3 I/O Response Time in Tag Data Links
Note This section describes the data processing time for an EtherNet/IP Unit or a
built-in EtherNet/IP port on a CJ2H-CPU6@-EIP CPU Unit. The data process-
ing time for a built-in EtherNet/IP port on the CJ2M-CPU3@ CPU Unit is differ-
ent. For details, refer to 10-4 Tag Data Link Performance for CJ2M Built-in
EtherNet/IP Ports.
10-3-1 Timing of Data Transmissions
The following diagram shows the timing of tag data link transmissions
between the EtherNet/IP Unit or CJ2H built-in port and the CPU Unit.
The data transmission is processed during the I/O refresh period. Send data
is processed with transmission at regular intervals, and received data is pro-
cessed together with the send data when new data has been received from
other nodes. The following diagram shows the timing of data transmissions.
If there is an interrupt for data transmission processing, the CPU Unit’s cycle
time is extended by that interrupt processing time. Refer to 10-3-2 EtherNet/IP
Unit or CJ2H Built-in Port Data Processing Time for details.
10-3-2 EtherNet/IP Unit or CJ2H Built-in Port Data Processing Time
The following formula approximates the time required for the EtherNet/IP Unit
or CJ2H built-in port to process data transmissions with the CPU Unit (i.e., the
data processing time).
CPU Unit processing Basic
pro-
cesses
Program
execution I/O refreshing Peripheral
servicing
Data exchange processing
Basic
pro-
cesses
Data received
EtherNet/IP
Unit processing EtherNet/IP Unit data
processing time
(Refer to 10-3-2.)
CPU Unit’s c
y
cle time
Approximation of the data processing time for an
EtherNet/IP Unit or CJ2H Built-in Port
(0.0008 × Number of data transmission words) + 1.0 ms
284
I/O Response Time in Tag Data Links Section 10-3
The maximum number of tag data link words that can be transferred by one
EtherNet/IP Unit or CJ2H built-in port is 184,832 words. However, if the num-
ber of tag data link words exceeds the number of words that can be
exchanged with the CPU Unit at one time, the data will be divided and trans-
ferred in multiple data exchanges. The following table shows the number of
words that each CPU Unit can exchange at one time.
The number of data exchanges may double as given in the following table
according to the relation with the CPU Unit’s cycle time and the data process-
ing time of the EtherNet/IP Unit or CJ2H built-in port.
Note (1) With CS/CJ-series PLCs, consecutive data area words specified in the
tag set will be transferred together if possible. Up to 19 send data blocks
can be processed in one data transmission; up to 20 receive data blocks
can be processed in one data transmission. If there are more blocks, the
data will be divided and transferred in separate data transmissions.
(2) The preceding data processing time approximation is the standard formu-
la when a higher priority processing event does not occur in peripheral
servicing. For example, if an instruction such as SEND, RECV, or FAL is
executed, the instruction’s processing will have higher priority, so the data
processing time may be longer.
10-3-3 Effect on the CPU Unit’s Cycle Time
The CPU Unit’s cycle time is affected when the EtherNet/IP Unit or CJ2H built-
in port refreshes tag data and status data with the CPU Unit. This effect
depends on the size of the tag data links, and can be approximated with the
values in the following table. When there are multiple EtherNet/IP Units or
CJ2H built-in ports, the effect is cumulative.
CPU Unit Number of words per data transmission
CS/CJ Series Output/Send: About 7,405 words max. (If there are more words,
the data will be divided.)
Input/Receive: About 7,405 words max. (If there are more words,
the data will be divided.)
Note The total amount of send data and receive data that can be
exchanged at one time is about 14,810 words maximum.
SYSMAC CJ2
Series Output/send: About 6,432 words max. (If there are more words, the
data will be separated into multiple transmissions.)
Input/receive: About 6,432 words max. (If there are more words,
the data will be separated into multiple transmissions.)
Note The total amount of send data and receive data that can be
transferred at one time is about 12,864 words maximum.
Condition Number of data transmissions
CPU Unit’s cycle time
> EtherNet/IP Unit or CJ2H built-in port
data processing time
Number of data transmissions
based on the data size
CPU Unit’s cycle time
≤ EtherNet/IP Unit or CJ2H built-in port
data processing time
Number of data transmissions × 2
based on the data size
285
I/O Response Time in Tag Data Links Section 10-3
Note (1) When one of the listed CPU Bus Units is mounted in a CS-series Long-
distance Rack, the I/O refreshing time is extended by the distance to the
Rack in which the Unit is mounted, regardless of the model of the CPU
Unit. The following graph shows the coefficients (2 and 3) required to cal-
culate this effect.
(2) The additional time for CJ2H CPU Units with unit version 1.1 or later will
be as follows if high-speed interrupts are enabled.
0.1 ms + Number of words transferred × 0.87 µs
10-3-4 Tag Data Link I/O Response Time Calculation Example
When using the tag data link functions of the EtherNet/IP Unit or CJ2H built-in
port, there is a time lag between the point when the data link area’s data
changes due to an input at a node and the point when the change is output at
another node’s data link area. This time lag is called the tag data link
I/O response time.
This example shows how to calculate the minimum and maximum I/O
response times in the following configuration for connection 1 opened
between node 1 and node 2.
CPU Unit Effect of EtherNet/IP Unit or
CJ2H built-in port only Total effect when tag data links are being used
CJ2H CPU Rack: 0.1 ms
Expansion Rack: 0.13 ms
CPU Rack: Value from left column + 0.1 ms + No. of words trans-
ferred × 0.33 µs (See note 2.)
Expansion Rack: Value from left column + 0.1 ms + No. of words
transferred × 0.45 µs
CJ2M CPU Rack: 0.14 ms
Expansion Rack: 0.16 ms
CPU Rack: Value from left column + 0.02 ms + No. of words trans-
ferred × 0.78 µs
Expansion Rack: Value from left column + 0.02 ms + No. of words
transferred × 0.92 µs
CJ1 0.25 ms 0.25 ms + 1.5 ms + (Number of words × 1 µs)
CJ1M 0.17 ms 0.17 ms + 0.1 ms + (Number of words × 0.7 µs)
CJ1-H 0.1 ms 0.1 ms + 0.1 ms + (Number of words × 0.7 µs)
CS1 0.2 ms 0.2 ms + 1.5 ms + (Number of words × 1 µs)
CS1-H 0.1 ms 0.1 ms + 0.1 ms + (Number of words × 0.7 µs)
Long-distance
Rack 0.2 ms × Coefficient 2 (0.2 ms × Coefficient 2) + 1.5 ms + (Number of words × 1 µs ×
Coefficient 3)
Coefficient
Distance to Long-distance Rack (m)
286
I/O Response Time in Tag Data Links Section 10-3
The following table gives the items required to find the I/O response time and
values used in calculations for this system configuration.
Maximum Tag Data Link I/O Response Time
You can find the maximum I/O response time from the total of (1) to (6) in the
following figure.
PLC#1
EtherNet/IP
PLC#2 PLC#3
Node 1 Node 2 Node 3
Input switch (external input device)
Input W000.01 W000.01 Output
Output relay (external output device)
Tag Data Link Table
PLC#1 PLC#2 PLC#3
Outputs
RPI = 10 ms
RPI = 10 ms
W000
722 words x 16 connections
Total: 11,552 words
W000
Inputs
Inputs
256 words x 16 connections
Total: 4,096 words
RPI = 100 ms Outputs
Connection 1
Item Value used in calculation example
PLC#1 PLC#2
External I/O device delay time Input device delay:
1.5 ms Output device delay:
2.0 ms
Cable length 50 m
CPU Unit model CJ2H CPU Unit CJ2H CPU Unit
RPI 10 msec ---
Number of receive connections 0 32
CPU Unit cycle time 10 msec 15 msec
Total number tag
data link words Number of send
words 11,552 None
Number of
receive words None 15,648
287
I/O Response Time in Tag Data Links Section 10-3
(1) Node 1 (PLC #1) Input ON Response Time
This is the delay time for the external input device from when the input occurs
until the switch actually turns ON and the time until the input data is stored in
the memory area of the CPU Unit for PLC #1. In this system, the input switch
delay time is 1.5 ms. Also, one CPU cycle time is required until the data is
stored in the memory area of the CPU Unit. Therefore, the input ON response
time is 1.5 ms + 10 ms, or 11.5 ms.
(2) Node 1 (PLC #1) Send Data Processing Time
This is the time until memory data in the CPU Unit is transferred to the Ether-
Net/IP Unit. If the amount of data that can be processed in one data transmis-
sion with the CPU Unit is exceeded, data transmission will be performed over
multiple cycles of the CPU Unit, and so time is calculated for the number of
transmissions times the CPU Unit cycle times. The following table gives the
send data processing times and breakdown for node 1 (PLC #1) in this sys-
tem configuration. Refer to 10-3-2 EtherNet/IP Unit or CJ2H Built-in Port Data
Processing Time for details on the calculation formula for each item.
Output
: I/O processing
: Data exchange
Tag data link I/O response time
(1) Input ON
response
time
(2) Send data
processing
time (3) RPI
(4) Network transmission delay time
(5) Receive data
processing time
(6) Output ON
response time
Input
Calcu-
lation
Calcu-
lation
PLC #1 processing
Send data processing time
Cycle time x 2
Tag data link refresh cycle
Receive data processing time
PLC #2 processing
Input device
Transmission
path
Output
device PLC #1
PLC #2
Cycle time x 4
Item Calculation formula Time
A CPU Unit cycle time
for PLC #1 10 m sec
B Number of transmis-
sions based on the data
size
Number of data transmission words (11,552
words) ÷ 6,432 words (using a CJ2 CPU
Unit)
2
C EtherNet/IP Unit data
processing time 0.0008 × 6,432 + 1.0 (Maximum number of
transmission words per cycle) 6.15 m sec
288
I/O Response Time in Tag Data Links Section 10-3
(3) Packet Interval (RPI)
This is the communications refresh cycle set for each connection using the
Network Configurator. In this system, it is the refresh cycle for connection 1
(10 ms), which includes W000.01.
(4) Network Transmission Delay Time
This is the total of the send processing delay, receive processing delay,
switching hub delay, and cable delay. Refer to 10-1-3 Network Transmission
Delay Time for details on the calculation formula for network delay time. In this
system, it is 5.2 ms.
(5) Node 2 (PLC #2) Receive Data Processing Time
This is the time to transfer the data received by the EtherNet/IP Unit or CJ2H
built-in port to the memory area in the CPU Unit. Receive data is transferred
in the order that it is received, but if the amount of data that can be processed
in one transmission is exceeded, multiple cycles are required to transfer the
data. Also, data transmission is performed only once per CPU Unit cycle.
Therefore, if data transfer has ended in the cycle in which data is received, the
start of transmission for received data will be delayed by one CPU Unit cycle
time.
In this system configuration, data transfer is performed a maximum of three
times based on the data size of node 2 (PLC #2) to transfer received data for
node 1 (PLC #1) and node address 3 (PLC #3). Also, the cycle time of PLC #2
is 15 ms, the effect on the CPU Unit cycle time is 2.3 ms, and the data pro-
cessing time for the EtherNet/IP Unit or CJ2H built-in port is 6.15 ms. The
number of data transmissions is thus calculated as 3. In addition, the number
of data transmissions is calculated as a maximum of 4 (3 + 1) because it is
necessary to consider a delay of one CPU Unit cycle time in transferring
received data.
D Number of data trans-
missions A 10 m sec > C 6.15 m sec
To meet the conditions, the number of trans-
missions is the same as B.
2
To ta l:
(2) Send data process-
ing time
CPU Unit cycle time of A PLC #1 × D Num-
ber of data transmissions 20 m sec
Delay item Calculation formula Max. delay time
A Send processing delay 10 m sec × (15-10 msec/100)% 1.49 msec
B Cable delay 545 nsec + 50 m/100 272.5 nsec
C Switching hub delay 2 msec + Approx. 0.7 msec 2.7 msec
D Receive processing
delay 1 + (0 connection × 0.043) 1.0 msec
To ta l:
(4) Network Transmission
Delay Time
A + B + C + D 5.2 msec
Item Calculation formula Time
A CPU Unit cycle time --- 15 msec
B Number of transmis-
sions based on the data
size
Number of data transmission words (15,648
words) ÷ 6,432 words (using a CJ2 CPU
Unit)
3
C EtherNet/IP Unit data
processing time 0.0008 × 6,432 + 1.0 (Maximum number of
transmission words per cycle) 6.15 msec
Item Calculation formula Time
289
I/O Response Time in Tag Data Links Section 10-3
(6) Output ON response time
This is the delay time for the external output device from when the output bit
turns ON in the memory of the CPU Unit until the output is actually performed.
In this system configuration, the delay time for an output relay is 2.0 ms. Also,
one CPU cycle time is required until the data is stored in the memory area of
the CPU Unit.
The maximum tag data link I/O response time for this system configuration
found from the total of (1) to (6) is 124 ms.
Note The I/O response time may be longer due to noise, or other events.
D Number of data trans-
missions A 10 m sec > C 6.15 m sec
To meet the condition to enable processing
in one data transmission, the number of
transmissions is the same as B plus 1.
(Delay of one CPU Unit cycle time)
4
To ta l:
(5) Receive data process-
ing time
A Cycle time × D Number of data trans-
missions 60 msec
Item Time
A CPU Unit cycle time of PLC #2 15 msec
B Output relay delay time 2.0 msec
To ta l:
(6) Node 2 (PLC #2) output ON response time 17.0 msec
(1) Node 1 (PLC #1) input ON response time 11.5 msec
(2) Node 1 (PLC #1) send data processing time 20 msec
(3) Packet Interval (RPI) 10 msec
(4) Network Transmission Delay Time 5.5 msec
(5) Node 2 (PLC #2) receive data processing time 60 msec
(6) Output ON response time 17 msec
Maximum I/O response performance (total of (1) to (6)) 124 msec
Item Calculation formula Time
290
I/O Response Time in Tag Data Links Section 10-3
Minimum Tag Data Link I/O Response Time
The minimum tag data link I/O response time, which occurs when there are no
processing delays, is calculated as follows.
When the baud rate is 100 Mbps, the transmission time can be calculated with
the following equation. If a network delay does not occur, just this transmis-
sion time is added.
Transmission time =
(Number of send data words × 2 + 74) × 8 × 0.00001 ms
Note The I/O response time may be longer due to noise, or other events.
Output
: I/O processing
: Data exchange
Tag data link I/O response time
(1) Input ON
response
time
(2) Network transmission delay time
(3) Output ON
response time
Input
Calcu-
lation
Calcu-
lation
PLC #1 processing
Tag data link refresh cycle
PLC #2 processing
Input device
Transmission
path
Output
device PLC #1
PLC #2
(1) Node 1
(PLC #1) input ON response time
Input switch delay time 1.5 ms
CPU Unit cycle time of PLC #1 10.0 ms
(2) Transmission time (722 send data words) 0.121 msec
(3) Node 2
(PLC #1) output ON response time CPU Unit cycle time of PLC #2 15.0 ms
Output relay delay time 2.0 ms
Total (tag data link I/O response time) 28.6 ms
291
Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports Section 10-4
10-4 Tag Data Link Performance for CJ2M Built-in EtherNet/IP
Ports
10-4-1 Overview
The built-in EtherNet/IP port on a CJ2M CPU Unit (CJ2M-CPU3@) supports
tag data links for up to 32 connections, with a data size of 20 words per con-
nection. These specifications are different from those of CJ2H built-in ports
and EtherNet/IP Units. The maximum number of words that can be transmit-
ted for tag data links is 640 words. This 640 words is the amount of data that
is processed for one data transmissions between the CPU Unit and the CJ2M
built-in port.
The tag data link specifications of CJ2M built-in ports are provided in the fol-
lowing table. If these specifications are insufficient for the required system
configuration, use a CJ2H built-in port on a CJ2H-CPU6@-EIP CPU Unit or a
CJ1W-EIP21 EtherNet/IP Unit.
Tag Data Link Specifications for CJ2M Built-in EtherNet/IP Ports
Tag Data Link System
Configuration
Example
This example configuration is based on the maximum specifications for CJ2M
built-in ports where all nodes send and receive data to the other nodes. In this
case, the maximum send area for each node in a 17-node configuration is 20
words.
For example, node 1 establishes 16 send connections and 16 receive connec-
tions to the other 16 nodes, for a total of 32 connections. The maximum data
size per connection is 20 words, so the send area in node 1 is 20 words and
the receive areas in node 1 are each 20 words.
CJ2M built-in port
(CJ2M-CPU3@)Reference: CJ2H built-in port
(CJ2H-CPU6@-EIP)
Number of connections 32 256
Packet interval (RPI) 1 to 10,000 ms (in 0.5-ms units) 0.5 to 10,000 ms (in 0.5-ms units)
Allowed communications
bandwidth per Unit (PPS) 3,000 pps 6,000 pps
Number of tags that can be
registered 32 256
Tag types CIO Area, DM Area, EM Area, Holding Area, Work Area, and network symbols
Number of registrable tag sets 32 256
Number of tags per connec-
tion 8 (7 tags when the tag set contains the PLC status)
Maximum size of 1 tag set 20 words
(The PLC status uses 1 word when the tag
set contains the PLC status.)
722 words
(The PLC status uses 1 word when the tag
set contains the PLC status.)
Maximum data size per con-
nection 20 words 722 words
Maximum link data size per
node 640 words 184,832 words
Maximum number of tags that
can be refreshed per CPU Unit
cycle
Output/Transmission
(CPU → EtherNet/IP): 32
Input/Reception (EtherNet/IP → CPU): 32
Output/Transmission
(CPU → EtherNet/IP): 256
Input/Reception (EtherNet/IP → CPU): 256
Data that can be refreshed per
CPU Unit cycle Output/Transmission (CPU → EtherNet/IP):
640 words
Input/Reception (EtherNet/IP → CPU):
640 words
Note The total for output/transmission and
input/reception is 640 words.
Output/Transmission (CPU → EtherNet/IP):
6,432 words
Input/Reception (EtherNet/IP → CPU):
6,432 words
Note The total for output/transmission and
input/reception is 12,864 words.
292
Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports Section 10-4
If the same RPI is set for all connections, 12 ms is the lowest setting that can
be used.
■Calculation Example
(1,000 ÷ 12 [ms] (RPI) + 1,000 ÷ 100 [ms] (heartbeat transmission period)) ×
32 (connections) = 2,987 pps < 3,000 pps
10-4-2 Tag Data Link I/O Response Time
With tag data links, if the data in the data link area for a node changes due to
an input to that node, a certain amount of time is required for the data in data
link area at another node to be updated and output.
The I/O response time for tag data links can be calculated for a CJ2M built-in
port in the same was as it can for a CJ2H built-in port (refer to 10-2-4 Chang-
ing the RPI). Here, formulas to calculate guideline I/O response times are pro-
vided. (Tag data link delays are ignored because the data link size handled by
the built-in CJ2M port is small.)
Maximum I/O Response Time
Input ON delay + Cycle time of sending PLC × 2 + RPI + Cycle time of receiv-
ing PLC × 2 + Output ON delay
Minimum I/O Response Time
Input ON delay + Cycle time of sending PLC + Cycle time of receiving PLC +
Output ON delay
*All nodes use CJ2M built-in ports.
Node 1
Send 20 words
Receive 20 words
Receive 20 words
Send connections = 16
(20 words × 16 = 320 words)
Node 2
Send 20 words
Send 20 words
Send 20 words
Send 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words
Receive 20 words Receive 20 words
Receive 20 words
Node 3 Node 16 Node 17
Receive connections = 16
(20 words × 16 = 320 words)
All connections
Cycle time: 5 ms
Input ON response time:
1.5 ms
Input Output
Data link
EtherNet/IP
Connection
RPI: 12 ms
PLC #1
Node 1 PLC #2
Node 2
20
words 20
words Cycle time: 10 ms
Output ON response
time: 2.0 ms
293
Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports Section 10-4
For example, the maximum and minimum I/O response times would be as fol-
lows for the above system.
Maximum response time:
1.5 ms + 5 ms × 2 + 12 ms + 10 ms × 2 + 2.0 ms = 45.5 ms
Minimum response time:
1.5 ms + 5 ms + 10 ms + 2.0 ms = 18.5 ms
Note If the message service is used at the same time on the CJ2M built-in port, the
tag data link I/O response time will change.
294
Message Service Transmission Delay Section 10-5
10-5 Message Service Transmission Delay
This section explains the maximum transmission delay that can occur
between the execution of a SEND(090), RECV(098), or CMND(490) instruc-
tion in the ladder program until completion of the instruction. This delay does
not include the time required for the tag data link or the execution time of the
ladder program itself.
10-5-1 Maximum Transmission Delays (Excluding Delays in the Network)
Use the following equation to calculate the maximum transmission delay that
can occur between the execution of a SEND(090) or RECV(098) instruction in
the ladder program until completion of the instruction.
SEND(090) Instruction
Maximum transmission delay =
CPU Bus Unit service cycle (local node)
+ CPU Bus Unit service processing time (local node)
+ Send processing
+ Transmission delay
+ Receive processing
+ CPU Bus Unit service cycle (remote node)
+ CPU Bus Unit service processing time (remote node)
CPU Bus Unit Service
Cycle (Local Node) The following table shows the service cycle, which depends on the CPU Unit’s
CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
Execution of SEND(090)
in user program
CPU Bus Unit service cycle
(Local node)
CPU Bus Unit service processing time
(Local node)
Send processing
Transmission delay
Receive processing
CPU Bus Unit service cycle
(Remote node)
CPU Bus Unit service
processing time (Remote node)
CPU data set
processing
Maximum transmission delay
CPU execution mode Processing time details
Normal Mode (See note.) One CPU Unit cycle time
Priority peripheral servicing
Parallel processing with syn-
chronous memory access
Parallel processing with asyn-
chronous memory access 0.2 ms + peripheral servicing time (1 ms max. for
peripheral servicing of each Special I/O Unit, CPU
Bus Unit, peripheral port, RS-232C port, and Inner
Board)
295
Message Service Transmission Delay Section 10-5
For details, refer to the CPU Unit’s Operation Manual.
CPU Bus Unit Service
Processing Time (Local
Node)
The following table shows the CPU Bus Unit service processing time, which
depends on the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
Send Processing (Number of words being transferred × 0.002) + 0.550 ms
Transmission Delay The transmission delay time depends on the baud rate set for the EtherNet/IP
Unit or built-in EtherNet/IP port, as shown in the following table. (There may
be additional delays due to the other devices in the network, such as switch-
ing hubs.)
Receive Processing (Number of words being transferred × 0.003) + 0.704 ms
CPU Bus Unit Service
Cycle (Remote Node) The following table shows the CPU Bus Unit service cycle, which depends on
the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
CPU execution mode Processing time details
Normal Mode (See note.) Set peripheral servicing time
Default: 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Priority peripheral servicing
Parallel processing with syn-
chronous memory access
Parallel processing with asyn-
chronous memory access 1 ms max.
Baud rate Delay time
100Base-TX (Number of words being transferred × 0.0013) + 0.0118 ms
10Base-T (Number of words being transferred × 0.0019) + 0.0157 ms
CPU execution mode Processing time details
Normal Mode (See note.) One CPU Unit cycle time
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice instruction execution
time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
One CPU Unit cycle time
Parallel processing with syn-
chronous memory access One CPU Unit cycle time
Parallel processing with asyn-
chronous memory access 0.2 ms + peripheral servicing time (1 ms max. for
peripheral servicing of each Special I/O Unit, CPU
Bus Unit, peripheral port, RS-232C port, and Inner
Board)
296
Message Service Transmission Delay Section 10-5
CPU Bus Unit Service
Processing Time (Remote
Node)
The following table shows the CPU Bus Unit service processing time, which
depends on the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
Note Depending on the actual operating environment, the transmission time may
be longer than the one calculated with the equations given here. The following
factors can cause longer transmission times: other traffic on the network, win-
dow sizes of network nodes, other traffic at the EtherNet/IP Unit or built-in Eth-
erNet/IP port itself (e.g., simultaneous tag data link communications), and the
system configuration.
Example Calculation In this example, SEND(090) is used to send 256 words of data between two
PLCs. The maximum transmission delay is calculated based on the following
operating conditions.
• Local node’s CPU cycle time: 10 ms
• Local node’s CPU execution mode: Normal
• Local node’s CPU peripheral servicing time: Default (4%)
• Remote node’s CPU cycle time: 5 ms
• Remote node’s CPU execution mode: Normal
• Remote node’s CPU peripheral servicing time: Default (4%)
• Baud rate: 100Base-TX
CPU execution mode Processing time details
Normal Mode (See note.) Set peripheral servicing time
Default: 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice peripheral servicing
execution time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle
time)
Parallel processing with syn-
chronous memory access Set peripheral servicing time
Default: 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Parallel processing with asyn-
chronous memory access 1 ms max.
Item Calculated value
CPU Bus Unit service cycle (local
node) 10 ms
CPU Bus Unit service processing
time (local node) 0.4 ms
Send processing (256 × 0.002) + 0.550 = 1.062 ≅ 1.1 ms
Transmission delay (256 × 0.0013) + 0.0118 = 0.3446 ≅ 0.3 ms
Receive processing (256 × 0.003) + 0.704 = 1.472 ≅ 1.5 ms
CPU Bus Unit service cycle (remote
node) 5 ms
CPU Bus Unit service processing
time (remote node) 0.2 ms
Maximum transmission delay 10 + 0.4 + 1.1 + 0.3 + 1.5 + 5 + 0.2 = 18.5 ms
297
Message Service Transmission Delay Section 10-5
RECV(098) Instruction
Maximum transmission delay =
CPU Bus Unit service cycle (Local node, 1)
+ CPU Bus Unit service processing time (Local node, 1)
+ Send processing (Command)
+ Transmission delay (Command)
+ Receive processing (Command)
+ CPU Bus Unit service cycle (remote node)
+ CPU Bus Unit service processing time (remote node)
+ Send processing (Response)
+ Transmission delay (Response)
+ Receive processing (Response)
+ CPU Bus Unit service cycle (Local node, 2)
+ CPU Bus Unit service processing time (Local node, 2)
CPU Bus Unit Service
Cycle (Local Node, 1) The following table shows the service cycle, which depends on the CPU Unit’s
CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
CPU Bus Unit Service
Processing Time (Local
Node, 1)
The following table shows the CPU Bus Unit service processing time, which
depends on the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
Maximum transmission delay
Execution of RECV(099)
in user program
CPU Bus Unit service cycle
(Local node, 1)
CPU Bus Unit service processing time
(Local node, 1)
Send processing
(Command)
Receive processing
(Command)
Transmission delay
(Command)
CPU Bus Unit service cycle
(Local node, 2)
CPU Bus Unit service
processing time (Local node, 2)
Send processing
(Response)
Transmission delay
(Response)
Transmission delay
(Response)
CPU data set
processing
CPU Bus Unit service processing time
(Remote node)
CPU Bus Unit service cycle
(Remote node)
CPU execution mode Processing time details
Normal Mode (See note.) One CPU Unit cycle time
Priority peripheral servicing
Parallel processing with syn-
chronous memory access 0.2 ms + peripheral servicing time (1 ms max. for
peripheral servicing of each Special I/O Unit, CPU
Bus Unit, peripheral port, RS-232C port, and Inner
Board)
Parallel processing with asyn-
chronous memory access
CPU execution mode Processing time details
Normal Mode (See note.) Set peripheral servicing time
Default: 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Priority peripheral servicing
Parallel processing with syn-
chronous memory access 1 ms max.
Parallel processing with asyn-
chronous memory access
298
Message Service Transmission Delay Section 10-5
For details, refer to the CPU Unit’s Operation Manual.
Send Processing
Transmission Delay The transmission delay time depends on the baud rate set for the EtherNet/IP
Unit or built-in EtherNet/IP port, as shown in the following table. (There may
be additional delays due to the other devices in the network, such as switch-
ing hubs.)
Receive Processing
CPU Bus Unit Service
Cycle (Remote Node) The following table shows the CPU Bus Unit service cycle, which depends on
the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
CPU Bus Unit Service
Processing Time (Remote
Node)
The following table shows the CPU Bus Unit service processing time, which
depends on the CPU Unit’s CPU processing mode setting.
Command 0.550 ms
Response (Number of words being transferred × 0.002) + 0.550 ms
Baud rate Delay time
100Base-TX Command 0.0118 ms
Response (Number of words transferred × 0.0013) + 0.0118 ms
10Base-T Command 0.0157 ms
Response (Number of words transferred × 0.0019) + 0.0157 ms
Command 0.704 ms
Response (Number of words being transferred × 0.003) + 0.704 ms
CPU execution mode Processing time details
Normal Mode (See note.) One CPU Unit cycle time
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice instruction execution
time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
One CPU Unit cycle time
Parallel processing with syn-
chronous memory access One CPU Unit cycle time
Parallel processing with asyn-
chronous memory access 0.2 ms + peripheral servicing time (1 ms max. for
peripheral servicing of each Special I/O Unit, CPU
Bus Unit, peripheral port, RS-232C port, and Inner
Board)
CPU execution mode Processing time details
Normal Mode (See note.) 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice peripheral servicing
execution time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle
time)
299
Message Service Transmission Delay Section 10-5
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
CPU Bus Unit Service
Cycle (Local Node, 2) The following table shows the CPU Bus Unit service cycle, which depends on
the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
CPU Bus Unit Service
Processing Time (Local
Node, 2)
The following table shows the CPU Bus Unit service processing time, which
depends on the CPU Unit’s CPU processing mode setting.
Note CJ2 CPU Units support only Normal Mode.
For details, refer to the CPU Unit’s Operation Manual.
Note Depending on the actual operating environment, the transmission time may
be longer than the one calculated with the equations given here. The following
factors can cause longer transmission times: other traffic on the network, win-
dow sizes of network nodes, other traffic at the EtherNet/IP Unit or built-in Eth-
erNet/IP port itself (e.g., simultaneous tag data link communications), and the
system configuration.
Parallel processing with syn-
chronous memory access 4% of CPU Unit cycle time
Parallel processing with asyn-
chronous memory access 1 ms max.
CPU execution mode Processing time details
CPU execution mode Processing time details
Normal Mode (See note.) One CPU Unit cycle time
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice instruction execution
time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
One CPU Unit cycle time
Parallel processing with syn-
chronous memory access One CPU Unit cycle time
Parallel processing with asyn-
chronous memory access 0.2 ms + peripheral servicing time (1 ms max. for
peripheral servicing of each Special I/O Unit, CPU
Bus Unit, peripheral port, RS-232C port, and Inner
Board)
CPU execution mode Processing time details
Normal Mode (See note.) 4% of CPU Unit cycle time
(10% for CJ2 CPU Units)
Priority peripheral servicing EtherNet/IP Unit or
built-in EtherNet/IP
port is given prior-
ity.
Time slice peripheral servicing
execution time
EtherNet/IP Unit or
built-in EtherNet/IP
port is not given
priority.
Set peripheral servicing time
(Default: 4% of CPU Unit cycle
time)
Parallel processing with syn-
chronous memory access 4% of CPU Unit cycle time
Parallel processing with asyn-
chronous memory access 1 ms max.
300
Message Service Transmission Delay Section 10-5
Example Calculation In this example, RECV(098) is used to receive 256 words of data from another
PLC. The maximum transmission delay is calculated based on the following
operating conditions.
• Local node’s CPU cycle time: 10 ms
• Local node’s CPU execution mode: Normal
• Local node’s CPU peripheral servicing time: Default (4%)
• Remote node’s CPU cycle time: 15 ms
• Remote node’s CPU execution mode: Normal
• Remote node’s CPU peripheral servicing time: Default (4%)
• Baud rate: 100Base-TX
Item Calculated value
CPU Bus Unit service cycle (local
node, 1) 10 ms
CPU Bus Unit service processing
time (local node, 1) 0.4 ms
Send processing (command) 0.550 ms ≅ 0.5 ms
Transmission delay (command) 0.0118 ms ≅ 0.1 ms
Receive processing (command) 0.704 ms ≅ 0.7 ms
CPU Bus Unit service cycle (remote
node) 15 ms
CPU Bus Unit service processing
time (remote node) 0.6 ms
Send processing (command) (256 × 0.002) + 0.550 = 1.062 ≅ 1.1 ms
Transmission delay (command) (256 × 0.0013) + 0.0118 = 0.3446 ≅ 0.3 ms
Receive processing (command) (256 × 0.003) + 0.704 = 1.472 ≅ 1.5 ms
CPU Bus Unit service cycle (local
node, 2) 10 ms
CPU Bus Unit service processing
time (local node, 2) 0.4 ms
Maximum transmission delay 10 + 0.4 + 0.5 + 0.1 + 0.7 + 15 + 0.6 + 1.1 +
0.3 + 1.5 + 10 + 0.4 = 40.6 ms
301
SECTION 11
FTP Server
This section describes the functions provided by the FTP server.
11-1 Overview and Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
11-1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
11-1-2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
11-2 FTP Server Function Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
11-2-1 File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
11-2-2 Connecting to the FTP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
11-3 Using the FTP Server Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
11-3-1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
11-3-2 List of Settings Required for the FTP Server Function . . . . . . . . . . 305
11-3-3 FTP Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
11-4 FTP Server Application Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
11-5 Using FTP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
11-5-1 Table of Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
11-5-2 Using the Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
11-5-3 Error Messages and FTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
11-6 Checking FTP Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
11-6-1 FTP Status Flag. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
11-7 Using File Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
11-7-1 File Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
11-7-2 File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
11-7-3 Initializing File Memory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
11-7-4 I/O Memory Data Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
11-8 FTP File Transfer Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
11-9 Host Computer Application Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
302
Overview and Specifications Section 11-1
11-1 Overview and Specifications
11-1-1 Overview
The EtherNet/IP Unit or built-in EtherNet/IP port has a built-in FTP (File Trans-
fer Protocol) server function, so other computers on the Ethernet can read or
write (upload/download) large files in the EM file memory by executing FTP
commands from the FTP client software.
FTP can be used for EtherNet/IP Units with unit version 2.0.
Note Only one FTP client can connect at the same time.
EtherNet/IP Unit or
built-in EtherNet/IP port
Ethernet
FTP client
Intranet
Large file
Upload
Download
Specify the file and upload or download
using FTP commands such as get and put.
Files in the EM File Memory or the
Memory Card mounted to the CPU
Unit.
303
FTP Server Function Details Section 11-2
11-1-2 Specifications
Note The PLC, however, is unable to read or write files at other nodes using FTP
because the EtherNet/IP Unit or built-in EtherNet/IP port does not support
FTP client functions.
11-2 FTP Server Function Details
11-2-1 File Types
The file system in the CPU Unit that can be accessed by the EtherNet/IP Unit
or built-in EtherNet/IP port includes files in any Memory Card mounted in the
CPU Unit and files in the EM file memory. The directory tree is shown below.
A connection will be initially made to the root directory.
Note 1. The date of the MEMCARD directory displayed for ls or dir commands in
the root directory will be the date of the file system volume label.
2. The login date will be displayed for EM files and for MEMCARD if a volume
label has not been created.
Item Specification
Executable com-
mands open: Connects the specified host FTP server.
user: Specifies user name for the remote FTP server.
ls: Displays the Memory Card file names.
dir: Display the Memory Card file names and details.
rename: Changes a file name.
mkdir: Creates a new directory in the working directory in the remote host.
rmdir: Deletes a new directory from the working directory in the remote host.
cd: Changes the Ethernet Unit work directory to the specified directory.
cdup: Changes the working directory at the remote host to the parent directory.
pwd: Displays the Ethernet Unit work directory.
type: Specifies the data type of transferred files.
get: Transfers the specified file from the Memory Card to the local host.
mget: Transfers multiple files from the Memory Card to the local host.
put: Transfers the specified local file to the Memory Card.
mput: Transfers multiple local files to the Memory Card.
delete: Deletes the specified file from the Memory Card.
mdelete: Deletes multiple files from the Memory Card.
close: Disconnects the FTP server.
bye: Closes the FTP (client).
quit: Closes the FTP (client).
Protection FTP login name consists of 12 letters max. CONFIDENTIAL is the default login name.
Password consists of 8 characters max.
Protocol FTP (port number: 20/TCP, 21/TCP)
Number of connec-
tions 1
/
: root
MEMCARD: Memory card directory
EM: EM file memory director
y
304
FTP Server Function Details Section 11-2
11-2-2 Connecting to the FTP Server
The host computer must connect to the FTP server before the FTP server
functions can be used. The login name and password set in the Unit Setup will
be used when connecting. The default FTP login name is “CONFIDENTIAL”
and no password is required.
The FTP server in the EtherNet/IP Unit or built-in EtherNet/IP port can con-
nect to only one client at a time. If a client attempts to connect when the FTP
server is in use, a message will be returned and connection will be refused.
Note When general-purpose FTP software is used, files can be transferred and
read using a graphical user interface similar to Explorer.
Login Name and Password Setting
The default login name for FTP is “CONFIDENTIAL” and no password is set
for the default login, so login is possible by simply entering “CONFIDENTIAL”
as the login name. A user-set login name and password can also be set in the
User Setup (CPU Bus Unit System Setup).
Login Messages
Setting Restrictions
The following restrictions apply to login names and passwords.
• The login name and password must consist of alphanumeric characters,
hyphens, and/or underscores. They are not case sensitive.
• A login name consists of 12 characters.
• A password consists of 8 characters.
• Always set a password when setting a new login name. The login name
will not be valid unless a password is set for it.
• If a login name is not set or contains illegal characters, the default login
name, CONFIDENTIAL, must be used. No password is required and any
password that is set will be ignored.
FTP File Transfer Mode
FTP has two file transfer modes: ASCII mode and binary mode. Before start-
ing to transfer files, use the type command (specifies the data type of trans-
ferred files) to select the required mode.
Always select binary mode for binary files (extensions .IOM, .STD, or .OBJ) in
the CS/CJ-series file memory and other program files (with extensions such
as .CXP).
Status Message
Normal
connection 220 xxx.xx.xx.xx yyyyyyyyyy FTP server (FTP Ver-
sion z.zz) ready.
xxx.xx.xx.xx: IP address of EtherNet/IP Unit or built-in Ether-
Net/IP port
yyyyyyyyyy: EtherNet/IP Unit or built-in EtherNet/IP port model
number (e.g., CS1W-EIP21)
z.zz: Firmware version of EtherNet/IP Unit or built-in EtherNet/
IP port
FTP server
busy 221 FTP server busy, Goodbye.
305
Using the FTP Server Function Section 11-3
11-3 Using the FTP Server Function
11-3-1 Procedure
1,2,3... 1. Make the basic settings.
Refer to Initial Settings on page 34.
2. When using a user-set FTP login name and password:
With the CX-Programmer online, right-click the EtherNet/IP Unit or built-in
EtherNet/IP port in the IO Table Dialog Box of the CX-Programmer, and se-
lect Edit - Unit Setup. Set the following on the FTP Tab Page of the Edit
Parameters Dialog Box.
• FTP login name
• FTP password.
3. Select Transfer to PLC from the PLC Menu and click the Yes Button. The
setting data will be transferred to the CPU Bus Unit System Setup Area in
the CPU Unit.
4. When reading from and writing to the Memory Card:
Mount the Memory Card into the CPU Unit.
5. Connect the EtherNet/IP Unit or built-in EtherNet/IP port using the FTP cli-
ent software.
6. Enter the FTP login name and password set in the Unit Setup and log into
the EtherNet/IP Unit or built-in EtherNet/IP port.
Note Once logged in, the ftp commands can be used, such as cd
(Change Directory), and get (Obtain File).
7. Search in the following directories for the required file in the Memory Card
mounted to the CPU Unit or the EM File Memory.
8. Download the files.
9. Exit the connection.
Note The EtherNet/IP Unit or built-in EtherNet/IP port will be restarted when the
settings data is transferred to the CPU Bus Unit System Setup Area, so that
the new settings are read and become effective. Verify that it is safe for the
EtherNet/IP Unit or built-in EtherNet/IP port to restart before transferring the
settings data.
11-3-2 List of Settings Required for the FTP Server Function
Make the following settings for the unit setup when the server function is used.
File memory type Directory
Memory Card \MEMCARD
EM File Memory \EM
CX-Programmer
tab Settings Setting conditions Page
FTP Login User-set (when the default, CON-
FIDENTIAL, is not used) 306
Password User-set
Port No. Rarely required (when the default,
21, is not used)
306
Using the FTP Server Function Section 11-3
11-3-3 FTP Tab
The CPU Bus Unit System Setup, which is set when using the FTP server
function, is shown in the CX-Programmer's Edit Parameters Dialog Box.
■Settings
Setting Details Default value
Login Set the login name to externally connect to
the EtherNet/IP Unit or built-in EtherNet/IP
port via FTP.
None
(CONFIDENTIAL is
used.)
Password Set the password to externally connect to the
EtherNet/IP Unit or built-in EtherNet/IP port
via FTP.
None
Port No. FTP port number of the EtherNet/IP Unit or
built-in EtherNet/IP port.
This setting does not normally need to be
changed.
FTP uses two ports: a port for control and a
port for data transfer. Set the control port
only. The data transfer port uses the value
set for the control port –1.
0
(21 is used.)
307
FTP Server Application Example Section 11-4
11-4 FTP Server Application Example
The following procedure shows how to use the FTP server by connection with
the default login name, CONFIDENTIAL. No password is required.
Note The login name and a password must be set in the CPU Bus Setup for the
Ethernet Unit in the CPU Unit to use any login name other than CONFIDEN-
TIAL.
Note When general-purpose FTP software is used, files can be transferred and
read using a graphical user interface similar to Explorer.
1,2,3... 1. Make sure that a Memory Card is inserted in the CPU Unit and turn ON
the power supply to the PLC. If EM File Memory is to be used, create the
EM File Memory.
2. Connect to the FTP server from a computer on the Ethernet by entering
the text that is underlined in the following diagram.
3. Enter FTP commands (underlined in the following diagram) to read and
write files. The following directory tree is used in this example.
IP address of the Ethernet/IP Unit or built-in EtherNet/IP port
Results
Login name
$ ftp 150.31.2.83
connected to 150.31.2.83
220 **IPaddress** CJ1W-EIP21 FTP server(FTP**version**)ready
Name:CONFIDENTIAL
230 Guest logged in.
ftp> ls
200 PORT command successful.
150 opening data connection for ls(**IPaddress**port#**)(0bytes).
MEMCARD
EM
226 Transfer complete.
** bytes received in 0 seconds(**bytes/s)
ftp> cd MEMCARD
250 CWD command successful.
ftp> get ABC/DEF.IOM
200 PORT command successful.
150 opening data connection for abc/def.iom(**IPaddress**port#**)(**bytes).
226 Transfer complete
**bytes received in *.*** seconds(**bytes/s)
DEF.IOM (file)
ABC (subdirectory)
EM
MEMCARD
File names read
Results
Change to MEMCARD
directory
Results
Transfer DEF.IOM from
ABC directory
Results
/: root
308
Using FTP Commands Section 11-5
11-5 Using FTP Commands
This section describes the FTP commands which the host computer (FTP cli-
ent) can send to the FTP server of the EtherNet/IP Unit or built-in EtherNet/IP
port. The descriptions should also apply to most UNIX workstations, but slight
differences may arise. Refer to your workstation’s operation manuals for
details.
11-5-1 Table of Commands
The FTP commands which can be sent to the EtherNet/IP Unit or built-in Eth-
erNet/IP port are listed in the following table.
• The EtherNet/IP Unit or built-in EtherNet/IP port is considered to be the
remote host and the host computer (FTP client) is considered to be the
local host.
• A remote file is a file on the Memory Card or in EM File Memory in the
CPU Unit. A local file is one in the host computer (FTP client).
• The parent directory is the directory one above the working directory.
11-5-2 Using the Commands
open
Format
open [IP_address or host_name_of_FTP_server]
Function
Connects the FTP server. Normally when the FTP client is booted, the FTP
server IP address is specified to execute this command automatically.
Command Description
open Connects the specified host FTP server.
user Specifies user name for the remote FTP server.
ls Displays the Memory Card file names.
dir Display the Memory Card file names and details.
rename Changes a file name.
mkdir Creates a new directory in the working directory in the remote host.
rmdir Deletes a new directory from the working directory in the remote host.
cd Changes the Ethernet Unit work directory to the specified directory.
cdup Changes the working directory at the remote host to the parent direc-
tory.
pwd Displays the Ethernet Unit work directory.
type Specifies the data type of transferred files.
get Transfers the specified file from the Memory Card to the local host.
mget Transfers multiple files from the Memory Card to the local host.
put Transfers the specified local file to the Memory Card.
mput Transfers multiple local files to the Memory Card.
delete Deletes the specified file from the Memory Card.
mdelete Deletes multiple files from the Memory Card.
close Disconnects the FTP server.
bye Closes the FTP (client).
quit Closes the FTP (client).
309
Using FTP Commands Section 11-5
user
Format
user [user_name]
Function
Specifies the user name. Specify the FTP login name set in the EtherNet/IP
Unit or built-in EtherNet/IP port system setup. The default FTP login name is
“CONFIDENTIAL.”
If a non-default login name is used, it must be followed by the password. In
this case, enter the FTP password set in the system setup.
The user name is automatically requested immediately after connection to the
FTP server.
ls
Format
ls [-l] [REMOTE_FILE_NAME [local_file_name]]
Function
Displays the remote host (Memory Card or EM File Memory) file names.
Set the switch [-l] to display not only the file names but the creation date and
size as well. If the switch is not set, only the file names will be displayed.
You can specify a file name in the Memory Card or EM File Memory if desired.
If a local file name is specified, the file information will be stored in the speci-
fied file in the host computer.
dir
Format
dir [REMOTE_FILE_NAME [local_file_name]]
Function
Displays the file names, date created, and size of the files in the remote host
(Memory Card or EM File Memory). It displays the same information as com-
mand [ls -l].
Specify a file name in the Memory Card or EM File Memory as the remote file
name.
If a local file name is specified, the file information is stored in the specified file
in the host computer.
rename
Format
rename CURRENT_FILE_NAME NEW_FILE_NAME
Function
Changes the specified current file name to the specified new file name.
rename can be used only to change the file name. It cannot be used to move
the file to a different directory.
310
Using FTP Commands Section 11-5
mkdir
Format
mkdir DIRECTORY_NAME
Function
Creates a directory of the specified name at the remote host (Memory Card or
EM File Memory).
An error will occur if a file or directory of the same name already exists in the
working directory.
rmdir
Format
rmdir DIRECTORY_NAME
Function
Deletes the directory of the specified name from the remote host (Memory
Card or EM File Memory).
The directory must be empty to delete it.
An error will occur if the specified directory does not exist or is empty.
pwd
Format
pwd
Function
Displays the remote host’s (Ethernet Unit) current work directory.
cd
Format
cd [directory_name]
Function
Changes the remote host (Ethernet Unit) work directory to the specified
remote directory.
The files in the Memory Card are contained in the MEMCARD directory under
the root directory (/). The files in EM File Memory are contained in the EM
directory under the root directory (/). The root directory (/) is the directory
used when logging into the EtherNet/IP Unit or built-in EtherNet/IP port. No
MEMCARD directory will exist if a Memory Card is not inserted in the PLC or
if the Memory Card power indicator is not lit. No EM directory will exist if EM
File Memory does not exist.
cdup
Format
cdup
Function
Changes the working directory at the remote host to the parent directory (one
directory above the current working directory).
311
Using FTP Commands Section 11-5
type
Format
type data_type
Function
Specifies the file data type. The following data types are supported:
ascii: Files are transferred as ASCII data
binary (image): Files are transferred as binary data.
All files are treated by the PLC as binary files. Before reading or writing any
files, always use the type command to set the file type to binary. File con-
tents cannot be guaranteed if transferred as ASCII data.
The default file type is ASCII.
get
Format
get FILE_NAME [receive_file_name]
Function
Transfers the specified remote file from the Memory Card or EM File Memory
to the local host.
A receive file name can be used to specify the name of the file in the local
host.
mget
Format
mget FILE_NAME
Function
Allows the use of a wildcard character (*) to transfer multiple remote files from
the Memory Card or EM File Memory to the local host.
put
Format
put file_name [DESTINATION_FILE_NAME]
Function
Transfers the specified local file to the remote host (Memory Card or EM File
Memory).
A destination file name can be used to specify the name the file is stored
under in the Memory Card or EM File Memory.
Any existing file with the same name in the remote host (Memory Card or EM
File Memory) will be overwritten by the contents of the transferred file.
If an error occurs during file transfer, the file being transferred will be deleted
and the transmission will end in an error.
mput
Format
mput FILE_NAME
Function
Allows the use of a wildcard character (*) to transfer multiple local files to the
remote host (Memory Card or EM File Memory).
312
Using FTP Commands Section 11-5
Any existing file with the same name in the remote host (Memory Card or EM
File Memory) will be overwritten by the contents of the transferred file.
If an error occurs during file transfer, the file being transferred will be deleted
and the transmission of that file will end in an error. However, mput execution
will continue and remaining files will be transferred.
delete
Format
delete FILE_NAME
Function
Deletes the specified remote file from the Memory Card or EM File Memory.
mdelete
Format
mdelete FILE_NAME
Function
Allows the use of a wildcard character (*) to delete multiple remote files from
the Memory Card or EM File Memory.
close
Format
close
Function
Disconnects the FTP server of the EtherNet/IP Unit or built-in EtherNet/IP
port.
bye
Format
bye
Function
Ends the FTP (client).
quit
Format
quit
Function
Ends the FTP (client).
313
Using FTP Commands Section 11-5
11-5-3 Error Messages and FTP Status
Error Messages The error messages returned by the EtherNet/IP Unit or built-in EtherNet/IP
port are listed in the following table.
Message Meaning
PPP is a directory. The path name indicated at PPP is a directory.
PPP is not a directory. The path name indicated at PPP is not a directory.
Another unit has access authority
(FINS error 0 x 3001). Another Unit currently has the access right.
Bad sequence of commands. The RNFR command has not been executed.
Can't create data socket (X.X.X.X, YY). A socket cannot be created.
Cannot access to device (FINS error 0 x 250F). A file device error has occurred.
Cannot get memory blocks. A message memory block cannot be allocated.
Command format error (FINS error 0 x 1003). The command format is incorrect.
Connect error. A connection error has occurred.
Directories of old and new paths are not same. The directories before and after changing the name are different.
Directory name length exceeded max. size. The directory name is too long.
Directory not empty (FINS error 0 x 2108). The directory must be empty to delete it.
Fatal error (FINS error 0 x 1101). A parameter error has occurred.
Fatal error (FINS error 0 x 1103).
File or directory already exists. The specified file or directory name already exists.
File or directory already exists
(FINS error 0 x 2107).
File or directory name illegal. The file or directory name is incorrect.
File or directory name illegal
(FINS error 0 x 110C).
File read error (FINS error 0 x 1104). An error occurs when reading the file.
File read error (FINS error 0 x 110B).
File write error (FINS error 0 x 2106). An error occurs when reading the file.
File write error (FINS error 0 x 2107).
FINS error MRES 0 x XX: SRES 0 x XX. Some other FINS error has occurred.
Length of directory name too long. The path name of the directory is too long.
No space to create entry (FINS error 0 x 2103). There are too many files to create a new one.
No such device (FINS error 0 x 2301). The file device cannot be found.
No such file or directory. The specified file or directory does not exist.
No such file or directory (FINS error 0 x 2006).
No such file or directory (FINS error 0 x 2106).
Not enough memory. The communications buffers are full.
Not enough space in the system.
(FINS error 1104). The file device is full.
PLC communication error (timeout). File access timed out.
Socket canceled. The socket was canceled.
Socket error NN. A socket bind error occurred. The error code will be given at NN.
Socket receive error NN. A data reception error occurred. The error code will be given at NN.
Socket send error NN. A data send error occurred. The error code will be given at NN.
Timeout (900 seconds): closing control connection. The connection was closed because the client did not respond for
15 minutes.
Too many open files. Too many sockets have been created.
Write access denied. Writing is not possible.
Write access denied. (FINS error 0 x 2101).
314
Checking FTP Status Section 11-6
PPP: Path name
XXX: IP address
YY: Port number
MM: FINS error code
NN: Socket error code
11-6 Checking FTP Status
11-6-1 FTP Status Flag
The current status of the FTP server can be obtained from the service status
in the words allocated to the EtherNet/IP Unit in the CPU Bus Unit Area in the
CIO Area. The word containing the FTP Status Flag can be computed as fol-
lows: CIO 1500 + (25 x unit number) + 13
Note 1. File operations for files on the Memory Card are performed during FTP
communications. Do not remove the Memory Card or turn OFF power to
the PLC while FTP is being used.
2. When using File Memory Instruction from the program in the CPU Unit,
program exclusive control using the FTP Status Flag so that the same data
is not manipulated simultaneously by more than one instruction.
Status of
bit 00 Meaning
1 FTP server busy (a user is connected)
0 FTP server free
FTP Status Flag
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
n+13
315
Using File Memory Section 11-7
11-7 Using File Memory
There are two media that can be used to store files in memory for CS/CJ-
series PLCs:
• Memory Cards
• EM File Memory
11-7-1 File Memory
11-7-2 File Types
■File Names
Files are distinguished by assigning file names and extensions. The following
characters can be used in file names and extensions:
Alphanumeric characters: A to Z and 0 to 9. (Names converted to all-caps)
! & $ # ’ [ ] - ^ ( ) _
The following characters cannot be used in files names and extensions:
, . / ? * ” : ; < > = + (spaces)
File names are not case sensitive and will be converted to all-caps in the PLC
file system. File names can be up to 8 character long with 3-character exten-
sions. An error will occur if a file name or extension is too long. The first period
(.) in a file name will be taken as the delimiter between the file name and
extension. Extensions are determined by the file type.
■Directories
Up to five levels of directories (including root as the first level) can be created
as file storage locations. A maximum of 65 characters can be used in direc-
tory names.
CPU Unit
Memory Card
EM File
Memory
File
File
File
File
Media Memory type Capacity Model File data recognized by CPU Unit
CS/CJ-
series
Memory
Cards
Flash memory 8 MB HMC-EF861 • Complete user program
• Specified portions of I/O Memory
• Parameter area data (e.g. PLC
Setup)
15 MB HMC-EF171
30 MB HMC-EF371
EM File
Memory RAM Max. capacity of EM Area
in CPU Unit All EM Area banks
from specified bank in
I/O Memory (specified
in PLC Setup)
316
Using File Memory Section 11-7
File Names Handled by CPU Unit
The files described in the following table can be read or written by the CPU
Unit.
Note 1. Refer to information on file memory in the CS/CJ-series Programmable
Controllers Operation Manual (W339).
2. All files transferred automatically at startup must have the name AUTOEX-
EC.
File type File name Extension Contents Description
Data file ******** .IOM Specified ranges of
I/O Memory • Contains word (16-bit) data from a starting
word through an end word in one memory
area.
• The following areas can be used: CIO, HR,
WR, AR, DM, and EM.
Program file ******** .OBJ Complete user pro-
gram • Contains all the programs for cyclic tasks
and interrupt tasks, as well as task infor-
mation for one CPU Unit.
Parameter area file ******** .STD • PLC Setup
• Registered I/O
tables
• Routing tables
• CPU Bus Unit
Setup and other
setup data
• Contains all of the parameter data for one
CPU Unit.
• There is no need for the user to distinguish
the various types of data contained in the
file.
• The file can be automatically read to or
written from the CPU Unit simply by speci-
fying the extension (.STD)
Files
trans-
ferred at
startup
Data files AUTOEXEC .IOM I/O Memory data for
the specified number
of words starting from
D20000
• There does not necessarily need to be a
data file in the Memory Card when the
automatic file transfer function is used at
startup.
• The AUTOEXEC.IOM file always contains
DM Area data starting at D20000.
• All data in the file will be transferred to
memory starting at D20000 at startup.
Program
files AUTOEXEC .OBJ Complete user pro-
gram • There must be a program file in the Mem-
ory Card when the automatic file transfer
function is used at startup.
• Contains all the programs for cyclic tasks
and interrupt tasks, as well as task infor-
mation for one CPU Unit.
Parameter
area file AUTOEXEC .STD • PLC Setup
• Registered I/O
tables
• Routing tables
• CPU Bus Unit
Setup and other
setup data
• There must be a parameter file in the
Memory Card when the automatic file
transfer function is used at startup.
• Contains all of the parameter data for one
CPU Unit.
• There is no need for the user to distinguish
the various types of data contained in the
file.
• All parameters in the file will be automati-
cally transferred to specified locations in
memory at startup.
317
Using File Memory Section 11-7
11-7-3 Initializing File Memory
11-7-4 I/O Memory Data Format
■IOM Format
The IOM format is a data format used for binary data specified by the ladder
instructions, READ DATA FILE (FREAD(700)) and WRITE DATA FILE
(FWRIT(701)), in the CPU Unit.
If five words of data from the I/O memory (1234 hexadecimal, 5678 hexadeci-
mal, 9ABC hexadecimal, etc.) is contained in an attached file in IOM format,
the data will be stored in the attached file as shown in the following diagram.
Example: Binary data format with a delimiter after every 10 fields.
■TXT Format
The TXT format is a data format (using tab delimiters) specified by the ladder
instructions, READ DATA FILE (FREAD(700)) and WRITE DATA FILE
(FWRIT(701)), in the CPU Unit. The format is configured according to the
specified FREAD(700) and FWRIT(701) parameters, as follows:
If data from the I/O memory (1234 hexadecimal, 5678 hexadecimal, 9ABC
hexadecimal, etc.) is contained in an attached file in TXT format, the data will
be converted into ASCII format in words or double-words. The words are
delimited by inserting tabs ([HT]: 09), and carriage returns (CR) after specified
fields ([CR][LF]: 0D0A).
Memory Initialization method
Memory
Cards 1. Insert the Memory Card into the CPU Unit.
2. Initialize the Memory Card from a Programming Device
(Programming Consoles included).
EM File Mem-
ory 1. Specify in the PLC Setup the first bank to convert to file memory.
2. Initialize EM File Memory from the CX-Programmer.
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9
+0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678
+10 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0
XX XX XX 12 34 56 78 9A BC DE F0 12 34
I/O memory
.IOM file contents
48 bytes
(Reserved by the system.)
Data format Use of CRs and CR position
• Words without delimiters
• Double words without delimiters
• Words delimited by tabs.
• Double words delimited by tabs
• No CRs
• CR after every 10 fields.
• CR after each field.
• CR after every 2 fields.
• CR after every 4 fields.
• CR after every 5 fields.
• CR after every 16 fields.
318
Using File Memory Section 11-7
Example: Data format using words delimited by tabs and CRs after every
10 fields.
■CSV Format
The CSV format is a data format (using comma delimiters) that is specified by
ladder instructions, READ DATA FILE (FREAD(700)) and WRITE DATA FILE
(FWRIT(701)), in the CPU Unit. The CSV format is configured according to
the specified FREAD(700) and FWRIT(701) parameters, as follows:
If word data from the I/O memory (1234 hexadecimal, 5678 hexadecimal, up
to DEF0 hexadecimal) is contained in an attached file in CSV format, the word
data will be converted into ASCII format in word or double-word units. The
words are delimited by inserting comma delimiters (',':2C), and CRs after
specified fields ([CR][LF]: 0D0A).
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9
+0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678
+10 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0
31 32 33 34 09 35 36 37 38 09 39 41 42 43 09
I/O memory
.TXT file contents
1234[HT] 5 6 7 8 [HT] 9 A B C [HT]
35 36 37 38 0D 0A 39 41 42 43 09
5678[CR][LF] 9 A B C [HT]
1234@5678@9ABC@DEF0@1234@5678@9ABC@DEF0@1234@5678
9ABC@DEF0@1234@5678@9ABC@DEF0@1234@5678@9ABC@DEF0
@...[HT]: Used to display tab space when displayed as text.
.TXT file displayed as text
Data format Use of CRs and CR position
Words delimited by commas.
Double words delimited by com-
mas.
• No CRs
• CR after every 10 fields.
• CR after each field.
• CR after every 2 fields.
• CR after every 4 fields.
• CR after every 5 fields.
• CR after every 16 fields.
319
Using File Memory Section 11-7
Example: Data format using words delimited by commas with CRs after every
10 fields.
Note FREAD(700) will not be able to read the last byte in a file that has been written
to the Memory Card if the file contains an odd number of bytes. Add 00 hexa-
decimal to the end of the file if necessary to write an even number of bytes to
the Memory Card.
Note The UM and DM Areas contain binary data. Set the data type to binary using
the type command before reading or writing files using FTP. (Refer to type
on page 311.)
Note For details on how to use File Memory Instructions, refer to the CS/CJ Series
Instructions Reference Manual (W340).
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9
+0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678
+10 9ABC DEF0 1234 5678 9ABC DEF0 1234 5678 9ABC DEF0
31 32 33 34 2C 35 36 37 38 2C 39 41 42 43 2C
I/O memory
.CSV file contents
1234,5678 , 9ABC,
35 36 37 38 0D 0A 39 41 42 43 2C
5678[CR] [LF] 9 A B C ,
1234,5678,9ABC,DEF0,1234,5678,9ABC,DEF0,1234,5678
9ABC,DEF0,1234,5678,9ABC,DEF0,1234,5678,9ABC,DEF0
.TXT file displayed as text
320
FTP File Transfer Time Section 11-8
11-8 FTP File Transfer Time
File transfers using FTP can require 30 or 40 minutes depending on the
capacity of the file. Approximate file transfer time are provided in the following
table for reference.
All times are in seconds unless otherwise specified.
■CS1 CPU Units and CJ1 CPU Units
■CS1-H CPU Units, CJ1-H CPU Units, CJ1-R CPU Units, CJ2-H CPU Units,
and CJ2M CPU Units
Note 1. The above times assume that the Fixed Peripheral Servicing Time in the
PLC Setup is set to the default value of 4%.
2. If the Fixed Peripheral Servicing Time in the PLC Setup is increased, FTP
files will be transferred faster.
File system Memory Card EM File Memory
CPU Unit status Operating mode PROGRAM RUN PROGRAM RUN
Cycle time --- 20 ms --- 20 ms
Transfers using
put
1 KB 0.7 s 6.0 s 0.4 s 2.9 s
30 KB 4.5 s 38.3 s 2.5 s 21.5 s
60 KB 7.4 s 72.1 s 5.0 s 44.7 s
120 KB 14.4 s 141.4 s 11.0 s 120.8 s
Transfers using
get
1 KB 0.3 s 1.4 s 0.2 s 0.8 s
30 KB 2.8 s 19.3 s 1.9 s 11.4 s
60 KB 4.9 s 37.6 s 3.8 s 26.7 s
120 KB 9.6 s 75.7 s 8.6 s 68.2 s
File system Memory Card EM File Memory
CPU Unit status Operating mode PROGRAM RUN PROGRAM RUN
Cycle time --- 20 ms --- 20 ms
Transfers using
put
1 KB 0.5 s 2.7 s 0.2 s 0.6 s
30 KB 1.8 s 11.6 s 0.7 s 6.6 s
60 KB 3.2 s 21.1 s 1.5 s 14.0 s
120 KB 6.2 s 40.2 s 3.6 s 32.5 s
Transfers using
get
1 KB 0.2 s 0.3 s 0.2 s 0.2 s
30 KB 1.7 s 4.8 s 1.0 s 4.1 s
60 KB 2.5 s 9.4 s 2.3 s 9.7 s
120 KB 4.9 s 18.8 s 4.9 s 27.0 s
321
Host Computer Application Example Section 11-9
11-9 Host Computer Application Example
The following procedure provides an example of FTP operations from a host
computer. In this example, the following assumptions are made.
• The IP address of the EtherNet/IP Unit or built-in EtherNet/IP port is regis-
tered in /etc/hosts on the host name as [cs1].
• The default FTP login name is being used (CONFIDENTIAL).
• A processing results data file called RESULT.IOM already exists on the
Memory Card in the CPU Unit.
• A processing instructions data file called PLAN.IOM already exists on the
workstation.
The following procedure transfers the processing results file RESULT.IOM
from the Memory Card in the CPU Unit to the workstation and then the pro-
cessing instructions file PLAN.IOM is transferred from the workstation to the
Memory Card in the CPU Unit.
Underlined text is keyed in from the FTP client. The workstation prompt is indi-
cated as $ and the cursor is indicated as ■.
1,2,3... 1. Start FTP and connect to the EtherNet/IP Unit or built-in EtherNet/IP port.
2. Enter the login name.
3. Make sure the Memory Card is inserted. The MEMCARD directory will be
displayed if there is a Memory Card in the CPU Unit.
$ ftp cs1 ··· FTP started.
connected to cs1
220 **IPaddress** CS1W-ETN21 FTP server(FTP**version**)ready
Name(cs1:root): ■
··· Login name
Name(cs1:root):CONFIDENTIAL
230 Guest logged in.
ftp> ■
··· Make sure the Memory Card is inserted.
ftp> ls
200 PORT command successful.
150 opening data connection for ls(**IPaddress**port#**)(0 bytes).
MEMCARD
226 Transfer complete.
15 bytes received in 0 seconds(**bytes/s)
ftp> ■
322
Host Computer Application Example Section 11-9
4. Change to the MEMCARD directory.
5. Change data type to binary.
6. Transfer the file RESULT.IOM to the workstation.
7. Write the file PLAN.IOM to the Memory Card.
8. End FTP.
··· Change to MEMCARD directory.
ftp> cd MEMCARD
250 CWD command successful.
ftp> ■
··· Binary data type set.
ftp> type binary
200 Type set to I.
ftp> ■
ftp> get RESULT.IOM ··· File read.
200 PORT command successful.
150 opening data connection for result.iom (**IPaddress**port#**) (**bytes).
226 Transfer complete.
** bytes received in *.*** seconds (**bytes/s)
ftp> ■
ftp> put PLAN.IOM ··· File written
200 PORT command successful.
150 opening data connection for plan.iom (**IPaddress**port#**).
226 Transfer complete.
** bytes received in *.** seconds (**bytes/s)
ftp> ■
ftp> bye ··· FTP ended.
221 Goodbye.
$ ■
323
SECTION 12
Automatic Clock Adjustment Function
This section provides an overview of the automatic clock adjustment function, including details on specifications, required
settings, operations from CX-Programmer, and troubleshooting.
12-1 Automatic Clock Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
12-1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
12-1-2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
12-2 Using the Automatic Clock Adjustment Function . . . . . . . . . . . . . . . . . . . . . 325
12-2-1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
12-2-2 Settings Required for Automatic Clock Adjustment Function. . . . . 326
12-2-3 Auto Adjust Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
12-3 Automatic Clock Adjustment Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
12-4 Automatic Clock Adjustment Error Processing . . . . . . . . . . . . . . . . . . . . . . . 328
12-4-1 Automatic Clock Adjustment (SNTP) Errors. . . . . . . . . . . . . . . . . . 328
12-4-2 Error Log Error Codes for the Automatic Clock Adjustment Function 328
324
Automatic Clock Adjustment Section 12-1
12-1 Automatic Clock Adjustment
12-1-1 Overview
The EtherNet/IP Unit or built-in EtherNet/IP port can obtain the clock informa-
tion from the SNTP server (see note 1) at a particular time or when a desig-
nated bit turns ON and then refresh the internal clock information of the CPU
Unit to which it is mounted (referred to as the local CPU Unit).
Note (1) The SNTP (Simple Network Time Protocol) server is used to control the
time on the LAN.
(2) An error will occur in the following CPU Units when the automatic clock
adjustment function is executed under the conditions shown in the table.
(3) The manufacturing date can be determined from the lot number on the
side or top corner of the CPU Unit.
(4) The lot numbers are as follows:
YYMMDDnnnn, in which YY indicates the last two digits of the year, MM
the month, DD the day, and nnnn the serial number.
(5) In accordance with SNTP protocol specifications, automatic adjustment
will not be possible from February 7, 2036. In EtherNet/IP Units or built-
in EtherNet/IP ports, this function will no longer operate from February 7,
2036 (an error message will not be displayed).
Intranet
SNTP server
Automatic clock adjustment
Ethernet
EtherNet/IP Unit or
built-in EtherNet/IP port
Clock data is obtained from the
SNTP server and written at a particular
time or when a designated bit turns ON.
The clock information can be broadcast to other CPU Units on the same Network.
24: 00: 00
24: 00: 00
CPU Unit Conditions
CPU Units manufactured on or
before January 31, 2003 (lot num-
bers 030131 or earlier):
CJ1G-CPU@@H
CJ1H-CPU@@H
CS1G-CPU@@H
CS1H-CPU@@H
When the CPU execution mode is set to other
than normal mode (priority peripheral servicing
mode, parallel processing with synchronous
memory access mode, or parallel processing
with asynchronous memory access mode).
AND
When the CPU Unit operating mode is set to
RUN or MONITOR mode.
325
Using the Automatic Clock Adjustment Function Section 12-2
12-1-2 Specifications
12-2 Using the Automatic Clock Adjustment Function
12-2-1 Procedure
1,2,3... 1. Make the basic settings.
Refer to Initial Settings on page 34.
2. With the CX-Programmer online, right-click the EtherNet/IP Unit or built-in
EtherNet/IP port in the IO Table Dialog Box of the CX-Programmer, and se-
lect Edit - Unit Setup Set the following on the Auto Adjust Time Tab Page
of the Edit Parameters Dialog Box.
• SNTP server specification (required)
• Access to the SNTP server is enabled when writing clock information from
the SNTP server to the local CPU Unit when the Automatic Clock Adjust-
ment Switch is turned from OFF to ON and at a set automatic adjustment
time.
• Automatic clock adjustment setting.
3. To perform automatic clock adjustment manually, turn the Automatic Clock
Adjustment Switch from OFF to ON. (The Automatic Clock Adjustment
Switch is word n bit 05 in the words allocated in the CPU Bus Unit Area,
where n = CIO 1500 + (25 × unit number.)
4. Select Transfer to PLC from the PLC Menu and click the Yes Button. The
Unit Setup (CPU Bus System Setup) will be transferred to the CPU Unit
(the setting data will be transferred to the CPU Bus Unit System Setup Ar-
ea).
Item Specification
Protocol SNTP
Port number 123 (UDP)
Can also be set from the CX-Programmer in the Unit Setup.
Adjustment timing Automatic (fixed time) and manual (manual only cannot be
set)
Access to SNTP
server Writes the clock information
from the SNTP server to the
local CPU Unit.
Obtains the clock information
from the SNTP server set up
on the Network, and applies
the information obtained to
the local CPU Unit.
Refresh timing When the automatic clock adjustment switch is turned from
OFF to ON and at a specified time.
326
Using the Automatic Clock Adjustment Function Section 12-2
12-2-2 Settings Required for Automatic Clock Adjustment Function
The following settings must be set in the Unit Setup when using the automatic
clock adjustment function.
Note When the Server specification type field in Auto Adjust Time Tab is set to Host
name.
CX-
Programmer
tab
Settings Setting conditions Reference
Auto Adjust
Time Server specification
type Required. 12-2-3 Auto Adjust
Time on page 327
IP Address One or the other is
required, depending
on the Server specifi-
cation type setting.
Host name
Port No. Rarely required.
(Change when a set-
ting other than the
default setting of 123
is required.)
Get the time informa-
tion from the SNTP
server
Required.
Auto Adjust Time Optional
Retry timer Optional (Change
when the default set-
ting of 10 seconds is
unacceptable.)
Adjust Time Optional
DNS (See
note.) IP Address Required. 3-8 TCP/IP and Link
Settings on page 52
Port No. Rarely required.
(Change when a set-
ting other than the
default setting of 53
is required.)
Retry timer Optional (Change
when the default set-
ting of 10 seconds is
unacceptable.)
327
Using the Automatic Clock Adjustment Function Section 12-2
12-2-3 Auto Adjust Time
The contents in the CPU Bus Unit System Setup that are set for using mail
send and receive functions are shown in the CX-Programmer’s Edit Parame-
ters Dialog Box.
Item Contents Default
Get the time
information from
the SNTP
server
Enable to set the CPU Unit's clock to the time at the
SNTP server's clock.
The clock can be changed only for the CPU Unit to
which the EtherNet/IP Unit or built-in EtherNet/IP port
is mounted.
Not
selected
(disabled)
Auto Adjust
Time Set the time at which the SNTP server is to be
accessed to synchronize the clocks.
When the time that is set here arrives, the SNTP
server is accessed and the CPU Unit clock is
adjusted to match the SNTP server clock.
0:0:0
Server specifi-
cation type Select whether the SNTP server used for automatic
clock adjustment is to be specified by IP address or
by host domain name (i.e., by host name).
IP Address
IP Address Set the IP address for the SNTP server that is to be
used for automatic clock adjustment.
This setting is enabled only when server specification
by IP address has been selected.
0.0.0.0
Host name Set the host domain name (i.e., the host name) for
the SNTP server that is to be used for automatic
clock adjustment.
This setting is enabled only when server specification
by host name has been selected.
None
Port No. Set the port number for connecting to the SNTP
server that is to be used for automatic clock adjust-
ment. This setting does not normally need to be
changed.
0
(Number
123 is
used.)
328
Automatic Clock Adjustment Switch Section 12-3
12-3 Automatic Clock Adjustment Switch
The Automatic Clock Adjustment Switch is allocated in the CIO Area as
shown below. The first word n of the CIO Area is calculated using the following
equation.
n = CIO 1500 + (25 × unit number)
Automatic Clock
Adjustment Switch
(Bit 05 of n)
The Unit control bit is shown in the following diagram.
When the Automatic Clock Adjustment Switch turns from OFF to ON, the Eth-
erNet/IP Unit or built-in EtherNet/IP port obtains the clock data from the SNTP
server on the network, and applies it to the local CPU Unit. After applying the
data, the switch automatically turns OFF again.
12-4 Automatic Clock Adjustment Error Processing
12-4-1 Automatic Clock Adjustment (SNTP) Errors
The following table shows the main causes and remedies for errors that occur
in the automatic clock adjustment function (SNTP).
12-4-2 Error Log Error Codes for the Automatic Clock Adjustment
Function
When an error occurs while the EtherNet/IP Unit or built-in EtherNet/IP port is
operating, the error code, detailed error code, and time the error occurred are
saved in the error log. The following table provides a list of the error codes.
Retry timer Set the time to elapse before retrying when a connec-
tion to the SNTP server fails. This setting does not
normally need to be changed.
0
(10 s)
Adjust Time This sets in the CPU Unit's clock data the time differ-
ence made up from the SNTP server's clock data.
To use the clock data from the SNTP server just as it
is, input 0.
+0:0
Item Contents Default
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
n
Automatic Clock
Adjustment Switch
Cause Correction
SNTP, DNS server address not set Reset each server address (IP address or
host name).
SNTP, DNS server communications time-
out Inspect the communications path (Ether-
Net/IP Unit or built-in EtherNet/IP port,
cable connections, hub, router, server),
and correct the situation that is causing
the error.
CPU Unit internal clock could not be set The automatic clock adjustment function
is not supported by certain CPU Units
(models, lot numbers) if they are in RUN
or MONITOR mode.
329
Automatic Clock Adjustment Error Processing Section 12-4
The error log can be read by sending FINS commands to the EtherNet/IP Unit
or built-in EtherNet/IP port or by using the mail receive function and specifying
the ErrorLogRead command.
Error
code Meaning Detailed error code Correction EEPROM
1st byte 2nd byte
03C1 Server set-
ting error 00H: DNS
03H:
SNTP
04H: FTP
06H:
BOOTP
07H:
SNMP
08H:
SNMP
Trap
09H:
FINS/
UDP
0AH:
FINS/
TCP
01: IP address
02: Host name
03: Port number
04: Other
parameters
Set the server
settings correctly
based on the
information in the
detailed error
code.
---
03C4 Server
connection
error
00H: DNS
03H:
SNTP
04H: FTP
06H:
BOOTP
07H:
SNMP
08H:
SNMP
Trap
01: Specified
host does not
exist
02: No service
at specified host
03: Timeout
04: Closed uni-
laterally by host
05: Cannot con-
nect because
account infor-
mation does not
match
06: Host name
resolution error
07: Transmis-
sion error
08: Reception
error
09: Other error
0AH: Error in
obtained IP
address
Take either of the
following mea-
sures.
• Correct the set-
tings for each
server.
• Inspect the com-
munications
path (EtherNet/
IP Unit or built-in
EtherNet/IP
port), cable con-
nections, hub,
router, server),
and correct the
situation that is
causing the
error.
---
03C6 Clock data
write error 0001: Clock data could not
be refreshed because of a
CPU Unit error.
Clear the CPU
Unit error. ---
0002: Clock data could not
be refreshed because the
CPU Unit could not write
clock data in that operation
mode.
The automatic
clock adjustment
function is not
supported by cer-
tain CPU Units
(models, lot num-
bers) if they are in
RUN or MONI-
TOR mode.
(See note.)
---
330
Automatic Clock Adjustment Error Processing Section 12-4
Note (1) For details on other error log information, refer to the Operation Manual,
Construction of Networks: SECTION 14 Troubleshooting and Error Pro-
cessing.
(2) An error will occur in the following CPU Units when the automatic clock
adjustment function is executed under the conditions shown in the table.
(3) The manufacturing date can be determined from the lot number on the
side or top corner of the CPU Unit.
(4) The lot numbers are as follows:
YYMMDDnnnn, in which YY indicates the last two digits of the year, MM
the month, DD the day, and nnnn the serial number.
CPU Unit Conditions
CPU Units manufactured on or
before January 31, 2003 (lot num-
bers 030131 or earlier):
CJ1G-CPU@@H
CJ1H-CPU@@H
CS1G-CPU@@H
CS1H-CPU@@H
When the CPU execution mode is set to other
than normal mode (priority peripheral servicing
mode, parallel processing with synchronous
memory access mode, or parallel processing
with asynchronous memory access mode).
AND
When the CPU Unit operating mode is set to
RUN or MONITOR mode.
331
SECTION 13
Maintenance and Unit Replacement
This section describes cleaning, inspection, and Unit replacement procedures, as well as the Simple Backup Function.
13-1 Maintenance and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
13-1-1 Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
13-1-2 Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
13-1-3 Unit Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
13-2 Simple Backup Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
13-3 Using the Backup Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
332
Maintenance and Replacement Section 13-1
13-1 Maintenance and Replacement
This section describes the routine cleaning and inspection recommended as
regular maintenance, as well as the Unit replacement procedure required if an
EtherNet/IP Unit needs to be replaced.
13-1-1 Cleaning
Clean the EtherNet/IP Unit regularly as described below in order to keep the
network in its optimal operating condition.
• Wipe the Unit daily with a dry, soft cloth.
• When a spot can’t be removed with a dry cloth, dampen the cloth with a
neutral cleanser (2% solution), wring out the cloth, and wipe the Unit.
• A smudge may remain on the Unit from gum, vinyl, or tape that was left on
for a long time. Remove the smudge when cleaning.
!Caution Never use volatile solvents such as paint thinner, benzene, or chemical wipes.
These substances could damage the surface of the Unit.
13-1-2 Inspection
Be sure to inspect the system periodically to keep it in its optimal operating
condition. In general, inspect the system once every 6 to 12 months, but
inspect more frequently if the system is used with high temperature or humid-
ity or under dirty/dusty conditions.
Inspection Equipment Prepare the following equipment before inspecting the system.
Normally Required
Equipment Have a standard and Phillips-head screwdriver, multimeter, alcohol, and a
clean cloth.
Occasionally Required
Equipment Depending on the system conditions, a synchroscope, oscilloscope, ther-
mometer, or hygrometer (to measure humidity) might be needed.
Inspection Procedure Check the items in the following table and correct any items that are below
standard.
13-1-3 Unit Replacement Procedure
Replace a faulty EtherNet/IP Unit as soon as possible. If the built-in EtherNet/
IP port is faulty, replace the CPU Unit as soon as possible. We recommend
having spare Units available to restore network operation as quickly as possi-
ble.
Precautions Observe the following precautions when replacing a faulty Unit.
• After replacement, verify that there are no errors with the new Unit.
• When a Unit is being returned for repair, attach a sheet of paper detailing
the problem and return the Unit to your OMRON dealer.
Item Standard Inspection
Environmental
conditions Ambient and cabinet temperature 0 to 55°C Thermometer
Ambient and cabinet humidity 10 to 90% (with no condensa-
tion or icing) Hygrometer
Dust/dirt accumulation None Visual
Installation Are the Units installed securely? No looseness Phillips-head
screwdriver
Are the Ethernet cable connectors
fully inserted and locked? No looseness Visual
333
Simple Backup Function Section 13-2
• If there is a faulty contact, try wiping the contact with a clean, lint-free
cloth dampened with alcohol.
Note To prevent electric shock when replacing a Unit, always stop communications
in the network and turn OFF the power supplies to all of the nodes before
removing the faulty Unit.
Settings Required
after Unit
Replacement
After a Unit has been replaced, verify that the following steps have been made
correctly.
• Set the node address and unit number.
• Connect the Ethernet cable.
• Set the configuration data (parameter settings) again and download them.
13-2 Simple Backup Function
Overview The simple backup function can be used to back up not only all of the data in
the CPU Unit, but also all of the data stored in memory in the EtherNet/IP Unit
or data for the built-in EtherNet/IP port. All of this data will automatically be
backed up to the Memory Card.
The simple backup function can be used for the following EtherNet/IP Units
and built-in EtherNet/IP port.
• CS-series EtherNet/IP Unit (CS1W-EIP21) mounted to a CS1D/CS1-
H CPU Unit
• CJ-series EtherNet/IP Unit (CJ1W-EIP21) mounted to a CJ1-H/CJ1M/
CJ2H-CPU@@-EIP CPU Unit
• A built-in EtherNet/IP port on a CJ2H-CPU@@-EIP/CJ2M-CPU3@
CPU Unit
When the EtherNet/IP Unit’s setup data is written to the Memory Card using a
simple backup operation, it is stored in the Memory Card as a Unit/Board
backup file with the file name BACKUP@@.PRM. (The @@ digits in the
backup file name indicate the unit address of the EtherNet/IP Unit or built-in
EtherNet/IP port, which is the unit number + 10 hex.)
This backup file is also used when reading data from the Memory Card or
comparing data with a file in the Memory Card.
Note The following table shows the Units that support the simple backup function.
Confirm that the Units being used support the function.
All setup data • Backup
• Restore
• Compare
EtherNet/IP Unit Memory Card
Power Supply Switch
Memory Card
CPU Unit
All data
CPU Unit EtherNet/IP Unit
CS1W-EIP21 CJ1W-EIP21
CS1D Yes ---
CS1-H Yes ---
334
Simple Backup Function Section 13-2
Applications Use the simple backup function when creating a backup data file for the entire
PLC (including the CPU Unit, EtherNet/IP Units, built-in EtherNet/IP port, and
Serial Communications Units/Boards), or when replacing all the Units.
Backup Sources and
Restore Targets The data that was backed up with the simple backup function can be restored
to Units or built-in ports as shown in the following table. Network Configuration
designations are given for the model numbers and versions of the backup
sources and restore targets.
The model number must be the same for both the backup source and restore
target. The CIP revision must be the same or higher.
Note (1) Functions added for revision 2.1 will be set to their default settings.
The number of settings will be increased, so an error will occur in the
comparison after data is restored.
(2) Data backed up for revision 1.1 using a simple backup can be restored to
an EtherNet/IP Unit or built-in EtherNet/IP port with revision 2.1, but an
error will occur in the comparison. When changing the unit version, refer
to 6-2-18 Changing Devices for information on the Network Configurator
device change function.
Operating Methods
Backing Up EtherNet/IP
Unit or Built-in EtherNet/IP
Port Setup Files to the
Memory Card
Set pins 7 and 8 of the DIP switch on the front panel of the CPU Unit as
shown in the following table, and press the Memory Card Power Supply
Switch for 3 seconds with the Memory Card inserted into the slot. Release the
switch when the BUSY indicator lights.
CS1 No ---
CJ1-H --- Yes
CJ1 --- No
CJ1M --- Yes
CJ2H --- Yes
CJ2M --- Yes
CPU Unit EtherNet/IP Unit
CS1W-EIP21 CJ1W-EIP21
Restore target CS1W-EIP21
CJ1W-EIP21 CJ2B-EIP21 CJ2M-EIP21 CJ1W-EIP21
(CJ2)
Backup source Rev. 1.1 Rev. 2.1 Rev. 2.1 Rev. 2.1 Rev. 2.1
CS1W-EIP21, CJ1W-EIP21
Rev. 1.1 Yes Yes
(See note 1.) No No No
CS1W-EIP21, CJ1W-EIP21
Rev. 2.1 NoYesNoNoNo
CJ2B-EIP21
Rev. 2.1 No No Yes No No
CJ2M-EIP21
Rev. 2.1 No No No Yes No
CJ1W-EIP21 (CJ2)
Rev. 2.1 No No No No Yes
DIP switch settings
SW7 ON
SW8 OFF
335
Simple Backup Function Section 13-2
This operation will create an EtherNet/IP Unit or built-in EtherNet/IP port set-
tings file, and write that file to the Memory Card along with the other backup
files. When the Memory Card Power Supply Switch is pressed, the MCPWR
indicator on the front of the CPU Unit will flash once and then remain lit while
data is being written. If the data is written normally, the MCPWR indicator will
turn OFF. The BUSY indicator will flash while the data is being written.
Note The backup operation will fail if it is performed after the device parameters
were not downloaded successfully from the Network Configurator or CX-Pro-
grammer. Perform the backup operation only if the device parameters were
downloaded normally.
Restoring the EtherNet/IP
Unit or Built-in EtherNet/IP
Port Setup File from the
Memory Card
(Reading and Setting the
Data in the Unit)
Set pins 7 and 8 of the DIP switch on the front panel of the CPU Unit, as
shown in the following table, and turn the power to the CPU Unit OFF and
then ON again with the Memory Card inserted into the slot.
This operation will read the EtherNet/IP Unit or built-in EtherNet/IP port setup
data file from the Memory Card and restore the data in the EtherNet/IP Unit or
built-in EtherNet/IP port.
When the power supply is ON, the MCPWR indicator on the front of the CPU
Unit will turn ON, flash once, and then remain lit while data is being read. The
BUSY indicator will flash while data is being read. After the data has been
read correctly, the MCPWR and BUSY indicators will turn OFF. If the MCPWR
indicator flashes five times or if only the BUSY indicator turns OFF, it means
that an error has occurred.
Note If the restoration from the Memory Card fails, an “H8” error will be displayed
on the 7-segment display on the front panel. If this happens, the data on the
Memory Card may not be correct. Confirm that the backup operation was
completed normally before performing the restore operation.
All setup data
Backup
EtherNet/IP Unit Memory Card
Power Supply Switch
Memory Card
CPU Unit
All data
DIP switch settings
SW7 ON
SW8 OFF
All setup data
Restore
EtherNet/IP Unit
Memory Card
CPU Unit
All data
Power ON
336
Using the Backup Tool Section 13-3
Comparing EtherNet/IP
Unit or Built-in EtherNet/IP
Port Data with the Setup
File in the Memory Card
Set pins 7 and 8 of the DIP switch on the front panel of the CPU Unit, as
shown in the following table, and press down the Memory Card Power Supply
Switch for 3 seconds.
This operation will compare the data in the EtherNet/IP Unit or built-in Ether-
Net/IP port setup file in the Memory Card with the device parameters in the
EtherNet/IP Unit or built-in EtherNet/IP port.
When the Memory Card Power Supply Switch is pressed, the MCPWR indica-
tor on the front of the CPU Unit will flash once, and then remain lit while data
is being compared. The BUSY indicator will flash while data is being com-
pared. If the data matches, the MCPWR and BUSY indicators will turn OFF. If
the MCPWR and BUSY indicators both flash, it means that the data does not
match or that an error has occurred.
Note Data backed up for revision 1.1 using a simple backup can be restored to an
EtherNet/IP Unit or built-in EtherNet/IP port with revision 2.1, but an error will
occur in the comparison. When changing the unit version, refer to 6-2-18
Changing Devices for information on the Network Configurator device change
function.
13-3 Using the Backup Tool
Overview The PLC Backup Tool of the CX-Programmer can be used to back up, com-
pare, and restore data for all Units or only specified Units in the PLC that is
connected online.
DIP switch settings
SW7 OFF
SW8 OFF
All setup data
Compare
EtherNet/IP Unit
Memory Card
CPU Unit
All data
Memory Card
Power Supply Switch
PLC Backup Tool
Back up
Specified backup
folder
CJ2
CPU Unit with Configuration Units
(CPU Bus Units and Special I/O Units)
Restore/compare
Default folder:
C:\Backup\yymmdd_hhmmss
337
Using the Backup Tool Section 13-3
Usage The PLC Backup Tool can be used for the following:
• Backing up all data in a PLC
• Comparing all of the data in a PLC with data that was previously backed
up in the computer
• Using the restore function to transfer all of the PLC data to a system with
the same configuration
• Transferring data to a new Unit after replacing a faulty Unit
Procedure Select PLC Backup Tool from the CX-Programmer's Tool Menu. You can also
select OMRON - CX-One - CX-Programmer - PLC Backup Tool from the
Windows Start Menu.
Backup Menu
Communications Settings
Refer to the CX-Programmer Operation Manual for detailed procedures.
Button Function
Backup from PLC Click this button to back up data. All of the data
in the target PLC will be backed up to the com-
puter.
Compare Click this button to compare data. The data in
the PLC can be compared to the data in a
backup file or the data in two backup files can be
compared. Any differences will be displayed.
Restore to PLC Click this button to restore data. The data in a
backup file will be transferred to the PLC to
restore the status that existed when the data
was backed up.
Button Function
Communications Settings Click this button to set communications condi-
tions for the target PLC. The current PLC model
and network type will be displayed.
338
Using the Backup Tool Section 13-3
339
SECTION 14
Troubleshooting and Error Processing
This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep
the EtherNet/IP network operating properly. We recommend reading through the error processing procedures before
operation so that operating errors can be identified and corrected more quickly.
14-1 Checking Status with the Network Configurator . . . . . . . . . . . . . . . . . . . . . . 340
14-1-1 The Network Configurator’s Device Monitor Function . . . . . . . . . . 340
14-2 Using the LED Indicators and Display for Troubleshooting . . . . . . . . . . . . . 347
14-2-1 Errors Occurring at the EtherNet/IP Unit or
Built-in EtherNet/IP Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
14-3 Connection Status Codes and Error Processing . . . . . . . . . . . . . . . . . . . . . . . 358
14-4 Error Log Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
14-4-1 Error Log Data Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
14-4-2 Error Log Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
14-4-3 FINS Commands for Error Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
14-4-4 Error Log Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
14-5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
14-5-1 CPU Unit's ERR/ALM Indicator Lit or Flashing . . . . . . . . . . . . . . . 368
14-5-2 General Ethernet Problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
14-5-3 Tag Data Links Fail to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
14-5-4 Tag Data Link Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
14-5-5 Message Timeout Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
14-6 Troubleshooting with FINS Response Codes . . . . . . . . . . . . . . . . . . . . . . . . . 371
340
Checking Status with the Network Configurator Section 14-1
14-1 Checking Status with the Network Configurator
14-1-1 The Network Configurator’s Device Monitor Function
Connect the Network Configurator online, select the device to be checked,
right-click to display the pop-up menu, and select Monitor.
The Monitor Device Dialog Box will be displayed.
Note If a communications error occurs during monitoring, the dialog box will con-
tinue to show the last information that was collected. To start monitoring
again, close the Monitor Device Dialog Box, and then open the dialog box
again.
Status 1 Tab Page The information displayed on the Status 1 Tab Page shows the status of the
flags in the following allocated CIO Area words: Unit status 1, Unit status 2,
Communications status 1, Communications status 2, and Communications
status 3. There will be a check mark in the box when the corresponding flag is
ON.
In addition, the Target Node Status Field shows the connection status of the
target nodes that are connected with the EtherNet/IP Unit as the tag data link
originator. The icon will be blue if the connection is normal, or red if an error
occurred.
341
Checking Status with the Network Configurator Section 14-1
Status 2 Tab Page The Status 2 Tab Page’s Target PLC Status Field shows the status of the tar-
get node PLCs that are connected with the EtherNet/IP Unit as the tag data
link originator. The icon will be blue if the CPU Unit is in RUN mode or MONI-
TOR mode, gray if it is in PROGRAM mode, or red if an error occurred.
The Connected Status of FINS/TCP Connections Field shows the status of
FINS/TCP connections. There will be a check mark in the box when the corre-
sponding connection is established (connected).
342
Checking Status with the Network Configurator Section 14-1
Note The target PLC status is can be used when the PLC status is selected for all
the target sets for both originator and target connections. For those that are
not selected, the status will be grayed-out.
343
Checking Status with the Network Configurator Section 14-1
Connection Tab Page The Connection Tab Page’s Target Node Status Field shows the connection
status of the target nodes that are connected with the EtherNet/IP Unit as the
tag data link originator. The icon will be blue if the connection is normal, or red
if an error occurred.
In addition, the Connection Status Area shows the current status each con-
nection that is set as the originator. This information can be used to identify
the cause of tag data link errors. For details on the connection status, refer to
14-3 Connection Status Codes and Error Processing.
344
Checking Status with the Network Configurator Section 14-1
Error History Tab Page The Error History Tab Page displays the error log stored in the EtherNet/IP
Unit or built-in EtherNet/IP port. Errors that occurred in the past are recorded,
and can be cleared or saved in a computer file as required.
In some cases, error records are cleared when the power is turned OFF, and
in other cases the records are retained. For details on the error log, refer to
14-4 Error Log Function.
Controller Error History
Tab Page The error history of the CPU Unit for the EtherNet/IP Unit or built-in EtherNet/
IP port is displayed on this tab page. The error history shows errors that have
occurred. It can be cleared or saved in a file in the computer.
345
Checking Status with the Network Configurator Section 14-1
Refer to the operation manual of the CPU Unit for details on error information.
Tag Status Tab Page This tab page shows if the tag settings for each tag for tag data links is set so
that data can be exchanged with the CPU Unit. The following status is dis-
played.
Ok: Data was exchanged normally.
Processing to solve: The symbol or I/O memory address for the tag is being
resolved. When the resolution is completed normally, a
connection will be established and the data exchange
will start.
Area type error: The area (e.g., EM bank) specified by the tag setting
does not exist in the CPU Unit. A connection will not be
established for a tag for which this error occurs.
Out of address range: The area specified by the tag setting is outside of the
area address range in the CPU Unit. A connection will
not be established for a tag for which this error occurs.
Size error: Different sizes are set for the network symbol and the
tag settings. Connections will not be opened for tags
with this error.
Not exist: A network symbol is not set in the symbol table in the
CPU Unit for the specified tag setting. A connection will
not be established for a tag for which this error occurs.
PLC I/F error: There is a problem in the bus interface with the CPU
Unit. Determine the cause based on the indicators and
the error log.
346
Checking Status with the Network Configurator Section 14-1
If the status is not “OK,” check the tag data link settings or the network symbol
settings in the symbol table in the CJ2 CPU Unit.
347
Using the LED Indicators and Display for Troubleshooting Section 14-2
Ethernet Information Tab
Page The Ethernet Information Tab Page shows the communications status at the
communications driver level. The error counter information can be used to
confirm whether communications problems have occurred. The tag data link
information can be used to confirm characteristics such as the bandwidth
usage (pps).
14-2 Using the LED Indicators and Display for Troubleshooting
14-2-1 Errors Occurring at the EtherNet/IP Unit or Built-in EtherNet/IP
Port
Errors Related to CPU Unit
Data Exchange The 7-segment display alternates between the node address and error code.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
Flashing
red Not lit H1 Duplicate unit
number The same unit
number is set on
another Unit.
Operation stops. --- Set the unit num-
bers correctly and
restart the Ether-
Net/IP Unit or built-
in EtherNet/IP port.
Flashing
red Not lit H2 CPU Unit
faulty --- Operation stops. --- Replace the CPU
Unit if the error
recurs when the
CPU Unit is
restarted.
348
Using the LED Indicators and Display for Troubleshooting Section 14-2
Lit red Not lit H3 EtherNet/IP
Unit or built-in
EtherNet/IP
port faulty
--- Operation stops. --- Replace the Ether-
Net/IP Unit or (for a
built-in EtherNet/IP
port) the CPU Unit
if the error recurs
when the Unit is
restarted.
Flashing
red Not lit H4 Node address
setting error The node
address set on
the switches is
invalid (00 or
FF.)
Operation stops. --- Set the node
address correctly
and restart the Eth-
erNet/IP Unit or
built-in EtherNet/IP
port.
Flashing
red Not lit H6 CPU Unit
faulty --- Records the error in
the error log (time/
date all zeroes).
Operation stops.
000F Replace the CPU
Unit if the error
recurs when the
CPU Unit is
restarted.
Flashing
red Not lit H7 I/O table not
registered The CPU Unit’s
I/O table is not
registered.
Operation stops. 0006 Create the I/O
table.
Flashing
red --- H8 Simple backup
function
restore error
The simple
backup func-
tion’s data resto-
ration failed.
The settings of the
EtherNet/IP Unit or
built-in EtherNet/IP
port are all cleared,
unless the backup file
does not exist, a
Memory Card is not
mounted, or the PLC
model does not
match.
--- Perform the simple
backup operation
again. If the error
recurs, replace the
Memory Card, or
EtherNet/IP Unit,
or (for a built-in
EtherNet/IP port)
the CPU Unit.
Flashing
red --- H9 I/O bus error An error
occurred while
exchanging data
with the CPU
Unit.
• If the Unit is the orig-
inator of the tag data
link connection, it
stops communica-
tions.
• If the Unit is the tar-
get of the tag data
link connection and
the PLC status is
included in the com-
munications data,
the corresponding
Target Node PLC
Error Flag will be
turned ON.
000E Check and correct
the CPU Unit’s
operating environ-
ment.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
349
Using the LED Indicators and Display for Troubleshooting Section 14-2
Flashing
red --- HA CPU Unit
memory error A parity error
occurred during
an operation
such as reading
the routing
tables.
Records the error in
the error log. If the
routing tables were
being read, the rout-
ing tables are treated
as missing.
0012 Register the rout-
ing tables in the
CPU Unit again
and restart the
CPU Unit.
Replace the CPU
Unit if the error
recurs.
A memory error
has occurred for
the tag data-
base in the CPU
Unit (CJ2H/
CJ2M CPU Unit
only).
• If a symbol (tag
name) is specified in
the tag data link or
Unit Status Area,
refreshing the user-
specified status area
is stopped and tag
data links will oper-
ate as follows:
• Tag data link com-
munications will be
stopped for origina-
tor connections.
• Communications will
continue for target
connection. If PLC
status is included in
the communications
data, the target node
PLC error flag for
the relevant target
node will be turned
ON.
Note Recovery is
possible from
this error. If
recovery is
achieved, the
tag data links
will be
restarted to
return to nor-
mal status.
0017 Download the tag
data to the CPU
Unit again.
Replace the CPU
Unit if the error
recurs.
Flashing
red Not lit Hb CPU Unit
event servic-
ing timeout
A timeout
occurred during
an operation
such as reading
the routing
tables to the
CPU Unit.
Operation stops. 0011 Replace the Ether-
Net/IP Unit or (for a
built-in EtherNet/IP
port) the CPU Unit.
if the error recurs
when the Unit is
restarted.
Flashing
red --- HC Routing table
error There is a logic
error in the rout-
ing table set-
tings.
The Unit continues
operating without the
routing tables.
021A Create the routing
tables again.
Flashing
red --- Hd I/O refresh
error The EM Area
bank in which
the device
parameters
were set was
converted to file
memory while
the tag data link
was operating.
Tag data is not
refreshed if it is
assigned to a non-
existent area.
Note:
Recovery is possible
for this error.
0347 Stop using the EM
Area bank (in
which the device
parameters were
set) as file mem-
ory, or correct the
device parameters.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
350
Using the LED Indicators and Display for Troubleshooting Section 14-2
Flashing
red --- HE CPU Unit ser-
vice monitor-
ing error
Servicing from
the CPU Unit
was not com-
pleted within the
fixed interval.
The monitoring
time is normally
11 s.
• If the Unit is the orig-
inator of the tag data
link connection, it
stops communica-
tions.
• If the Unit is the tar-
get of the tag data
link connection and
the PLC status is
included in the com-
munications data,
the corresponding
Target Node PLC
Error Flag will be
turned ON.
Note:
Recovery is possible
for this error. When
operation is restored,
tag data link startup
processing will be
performed and opera-
tions will return to
normal.
0002 Check and correct
the CPU Unit’s
operating environ-
ment.
Flashing
red --- HF CPU Unit
watchdog
timer error
An error
occurred in the
CPU Unit.
• If the Unit is the orig-
inator of the tag data
link connection, it
stops communica-
tions.
• If the Unit is the tar-
get of the tag data
link connection and
the PLC status is
included in the com-
munications data,
the corresponding
Target Node PLC
Error Flag will be
turned ON.
0001 Replace the CPU
Unit.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
351
Using the LED Indicators and Display for Troubleshooting Section 14-2
Errors Related to the CPU
Unit The 7-segment display alternates between the node address and error code.
Errors Related to the
Control Bits The 7-segment display alternates between the node address and error code.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
Flashing
red --- HH CPU Unit
Fatal Error A fatal error
occurred in the
CPU Unit.
• If the Unit is the orig-
inator of the tag data
link connection, it
stops communica-
tions.
• If the Unit is the tar-
get of the tag data
link connection and
the PLC status is
included in the com-
munications data,
the corresponding
Target Node PLC
Error Flag will be
turned ON.
0015 Eliminate the
cause of the error
in the CPU Unit.
The tag data link
will restart auto-
matically when the
cause of the error
is eliminated.
--- --- --- Output OFF
Error An Output OFF
(output inhibit)
condition
occurred in the
CPU Unit.
The tag data link’s
send data will be
cleared to 0 in accor-
dance with the Output
OFF settings, and
data transfer will con-
tinue with that data.
--- Turn OFF the CPU
Unit’s Output OFF
Bit (A50015). The
tag data link’s send
data will be
restored automati-
cally when this bit
is turned OFF.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
--- --- C6 Multiple
Switches ON Two or more
software
switches were
ON simulta-
neously, or a
second soft-
ware switch was
turned ON
before a prior
operation was
completed.
The error code will be
displayed on the 7-
segment display for
30 seconds, and the
Multiple Switches ON
Error Flag (n+11, bit
14) will go ON.
The error display will
be cleared the next
time that a settings
operation is com-
pleted normally.
--- Execute control bit
operations one at a
time.
352
Using the LED Indicators and Display for Troubleshooting Section 14-2
Errors Related to the Tag
Data Links The 7-segment display alternates between the node address and error code.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
--- --- d5 Verification
Error (target
non-existent)
The target regis-
tered in the
device parame-
ters does not
exist.
The Unit will periodi-
cally attempt to
reconnect to the tar-
get.
The Verification Error
Flag (n+12, bit 00),
Unit Error Occurred
Flag (n+10, bit 00),
and Network Error
Occurred Flag (n+10,
bit 01) will go ON.
---
Not
record
ed for
ver-
sion
2.0 or
higher
Check the follow-
ing items:
• Is the registered
node’s power
supply ON?
• Is the cable con-
nected?
• Is the cable dam-
aged or loose?
• Is there excessive
noise?
--- --- d6 Connection
Failed The connection
could not be
established
because device
parameters
(such as the
variable name
and size) did not
match in the
originator and
target, or con-
nection
resources are
insufficient.
The Unit will periodi-
cally attempt to
reconnect to the tar-
get.
The Verification Error
Flag (n+12, bit 00)
and Unit Error
Occurred Flag (n+10,
bit 00) will go ON.
03D4 Correct the device
parameter settings,
and download the
device parameters
again from the Net-
work Configurator.
--- --- d9 Tag Data Link
Error A timeout
occurred in the
tag data link.
(Tag data was
not received
from the target
within the speci-
fied timeout
time.)
The Unit will periodi-
cally attempt to
reconnect to the tar-
get where the error
occurred.
The Tag Data Link
Error Flag (n+12, bit
02), Unit Error
Occurred Flag (n+10,
bit 00), and Network
Error Occurred Flag
(n+10, bit 01) will go
ON.
03D5 Check the follow-
ing items:
• Is the registered
node’s power
supply ON?
• Is the cable con-
nected?
• Is the cable dam-
aged or loose?
• Is there excessive
noise?
353
Using the LED Indicators and Display for Troubleshooting Section 14-2
Errors Related to Memory
Access The 7-segment display alternates between the node address and error code.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
Flashing
red --- E9 Memory
Access Error An error
occurred in the
Unit's non-vola-
tile memory
itself. This error
will occur in the
following cases.
1. An error oc-
curred while
writing the er-
ror log.
2. An error oc-
curred while
writing the
device pa-
rameters.
Note:
This error does
not indicate
checksum errors
detected when
reading data.
Case 1:
The error record
remains in RAM only.
Subsequent writes to
non-volatile memory
are all ignored. Other
than that, normal
operation continues.
(Error records con-
tinue to be written to
RAM.)
Case 2:
Tag data links and
message communica-
tions will continue
operating.
The Unit Error
Occurred Flag (n+10,
bit 00), Unit Memory
Error Flag (n+10, bit
04), and Non-volatile
Memory Error Flag
(n+14, bit 15) will turn
ON.
0602 Download the Unit
Setup from the tab
pages of the Edit
Parameters Dialog
Box of the CX-Pro-
grammer and
download the
device parameters
from the Network
Configurator. If the
error recurs,
replace the Ether-
Net/IP Unit or (for a
built-in EtherNet/IP
port) the CPU Unit.
354
Using the LED Indicators and Display for Troubleshooting Section 14-2
Flashing
red --- E8 Device Param-
eters Error The I/O Area set
in the device
parameters
does not exist in
the CPU Unit, or
the EM Area
was converted
to file memory.
There is an error in
the parameter set-
tings stored in the
Unit’s non-volatile
memory. (An error
can occur when
power is interrupted
while data is being
written to non-volatile
memory.)
The Unit Error
Occurred Flag (n+10,
bit 00) and Invalid
Communications
Parameter Flag
(n+12, bit 04) will go
ON.
021A Download the Unit
Setup from the tab
pages of the Edit
Parameters Dialog
Box of the CX-Pro-
grammer and
download the
device parameters
from the Network
Configurator. If the
error recurs,
replace the Ether-
Net/IP Unit or (for a
built-in EtherNet/IP
port) the CPU Unit.
If the ladder pro-
gram uses the
OUT instruction to
turn ON the CPU
Bus Unit Restart
Bit, change the
OUT instruction to
the SET instruc-
tion and download
the parameters
again.
A checksum
error or logic
error was
detected in the
parameters.
The Unit was
mounted to a
different PLC
(e.g., from CJ1
to CJ2) after the
Unit settings
were made.
Flashing
red --- EA IP Advanced
Settings Error 03D1 Identify the error
log data, correct
the settings, and
then download the
Unit Setup from the
tab pages of the
Edit Parameters
Dialog Box of the
CX-Programmer
Flashing
red --- F2 Ethernet Basic
Settings Error 03D0 Download the set-
tings from the TCP/
IP or Ethernet Tab
Pages of the Edit
Parameters Dialog
Box of the CX-Pro-
grammer or down-
load the TCP/IP
settings from the
Network Configu-
rator.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
355
Using the LED Indicators and Display for Troubleshooting Section 14-2
Errors Related to the
Network The 7-segment display alternates between the node address and error code.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
--- --- E1 Ethernet Link
Not Detected The link with the
switching hub
could not be
detected.
Note This error
will not
occur
when
data links
are not
set for
version
2.0 or
higher.
• The Unit will be
offline and unable to
communicate. Errors
will be returned to all
communications
requests.
• Data exchanges
(refreshing) will con-
tinue with the CPU
Unit.
The Unit Error
Occurred Flag (n+10,
bit 00), Network Error
Occurred Flag (n+10,
bit 01), and Link OFF
Error Flag (n+10, bit
09) will go ON.
The Link Status Flag
(n+13, bit 14) will go
OFF.
03D3 Check the follow-
ing items:
• Is the cable con-
nected?
• Is the cable dam-
aged or loose?
• Is there excessive
noise?
356
Using the LED Indicators and Display for Troubleshooting Section 14-2
--- --- E3 Server Con-
nection Error An error
occurred in
communica-
tions with the
DNS server.
The DNS Server
Error Flag (n+14, bit
05) will turn ON.
03C4
De-
tails:
00xx
Perform one of the
following:
• Correct the DNS
server settings.
• Check the com-
munications path
(EtherNet/IP Unit
or built-in
EtherNet/IP port,
cable connec-
tions, hubs, rout-
ers, and servers)
and correct any
problems.
An error
occurred with
the BOOTP
server.
1. There was no
response
from the
BOOTP serv-
er.
2. The BOOTP
server at-
tempted to
set an invalid
IP address in
the EtherNet/
IP Unit or
built-in Ether-
Net/IP port.
Case 1:
The Unit will continue
sending requests to
the BOOTP server
until there is a
response. In the
meantime, the Unit
will be offline and
unable to communi-
cate. Errors will be
returned to all com-
munications requests.
Data exchanges
(refreshing) will con-
tinue with the CPU
Unit.
Case 2:
The Unit will operate
with the default IP
address
(192.168.250.node_
address).
The Unit Error
Occurred Flag (n+10,
bit 00), Network Error
Occurred Flag (n+10,
bit 01), and BOOTP
Server Error Flag
(n+14, bit 10) will go
ON.
03C4
De-
tails:
06xx
Perform one of the
following:
•Correct the
BOOTP server
settings.
• Check the com-
munications path
(EtherNet/IP Unit
or built-in
EtherNet/IP port,
cable connec-
tions, hubs, rout-
ers, and servers)
and correct any
problems.
An error
occurred in
communica-
tions with the
STNP server.
The SNTP Server
Error Flag (n+14, bit
11) will turn ON.
03C4
De-
tails:
03xx
Perform one of the
following:
• Correct the SNTP
server settings.
• Check the com-
munications path
(EtherNet/IP Unit
or built-in
EtherNet/IP port,
cable connec-
tions, hubs, rout-
ers, and servers)
and correct any
problems.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
357
Using the LED Indicators and Display for Troubleshooting Section 14-2
--- --- E3 Server Con-
nection Error An error
occurred in
transmission to
the SNMP trap.
--- 03C4
De-
tails:
07xx
Perform one of the
following:
•Correct the
SNMP trap set-
tings.
• Check the com-
munications path
(EtherNet/IP Unit
or built-in Ether-
Net/IP port, cable
connections,
hubs, routers, and
servers) and cor-
rect any prob-
lems.
--- Lit red F0 IP Address
Duplication The IP address
of the EtherNet/
IP Unit or built-in
EtherNet/IP port
is the same as
the IP address
set for another
node.
• The Unit will be
offline and unable to
communicate. Errors
will be returned to all
communications
requests.
• Data exchanges
(refreshing) will con-
tinue with the CPU
Unit.
The Unit Error
Occurred Flag (n+10,
bit 00), Network Error
Occurred Flag (n+10,
bit 01), and IP
Address Duplication
Error Flag (n+10, bit
06) will go ON.
0211 Check the IP
addresses set on
other nodes.
Restart the Ether-
Net/IP Unit or built-
in EtherNet/IP port
after correcting the
IP address settings
to eliminate dupli-
cations.
Flashing
red --- F3 Address mis-
match The target IP
address conver-
sion method is
set to Automatic
generation, but
the last byte of
the local IP
address does
not match the
value set on the
Node Address
Setting Switch.
• Operation will con-
tinue with the set IP
address as the local
IP address.
The Address Mis-
match Flag (n+14,
bit 14) will turn ON.
--- Check the IP
address and the
Node Address Set-
ting Switch setting.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
358
Connection Status Codes and Error Processing Section 14-3
Errors Related to the Unit The 7-segment display alternates between the node address and error code.
14-3 Connection Status Codes and Error Processing
This section explains how to identify and correct errors based on the tag data
link’s connection status. The connection status can be read using the Connec-
tion Tab Page of the Network Configurator’s Monitor Device Window. For
details, refer to 14-1-1 The Network Configurator’s Device Monitor Function.
Note 1. The connection status has the same meaning as the Connection Manag-
er’s General and Additional error response codes, as defined in the CIP
specifications.
2. The Open DeviceNet Vendor Association, Inc. (ODVA) can be contacted at
the following address to obtain a copy of the CIP specifications.
ODVA Headquarters
4220 Varsity Drive, Suite A
Ann Arbor, Michigan 48108-5006
USA
TEL: 1 734-975-8840
FAX: 1 734-922-0027
Flashing
red Not lit F4 Communica-
tions Control-
ler Error
An error
occurred in the
Communica-
tions Controller
in the EtherNet/
IP Unit or built-in
EtherNet/IP
port.
• The Unit will be
offline and unable to
communicate. Errors
will be returned to all
communications
requests.
• Data exchanges
(refreshing) will con-
tinue with the CPU
Unit.
The Unit Error
Occurred Flag (n+10,
bit 00), Network Error
Occurred Flag (n+10,
bit 01), and Commu-
nications Controller
Error Flag (n+10, bit
05) will go ON.
020F Replace the Ether-
Net/IP Unit or (for
the built-in Ether-
Net/IP port) the
CPU Unit if the
error recurs when
the Unit is
restarted.
Flashing
red --- C8 Node Address
Setting
Changed Dur-
ing Operation
The Node
Address Setting
Switch was
changed during
operation.
Operation will con-
tinue.
The IP Address
Changed During
Operation Flag (n+11,
bit 02) will turn ON.
--- Restart the Ether-
Net/IP Unit or built-
in EtherNet/IP port
after setting the
correct node
address.
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
Indicator Error Cause Unit operation (Flag
status) Error
log
(hex)
Countermeasure
MS NS 7-segment
Lit red Not lit --- Special Unit
Error An error
occurred in a
Special I/O Unit
or CPU Bus
Unit.
Records the error in
the error log.
Operation stops.
0601 Restart the CPU
Unit.
Replace the Ether-
Net/IP Unit or (for
the built-in Ether-
Net/IP port) the
CPU Unit if the
error recurs.
359
Connection Status Codes and Error Processing Section 14-3
Email odva@odva.org
WEB www.odva.org
The following table shows the possible originator/target configurations.
The following table shows the likely causes of the errors causes for each con-
figuration and connection status (code).
Configuration Originator Target
Configuration 1 CS1W-EIP21, CJ1W-EIP21,
CJ2H-CPU@@-EIP, CJ2M-
CPU3@
CS1W-EIP21, CJ1W-EIP21,
CJ2H-CPU@@-EIP, CJ2M-
CPU3@
Configuration 2 CS1W-EIP21, CJ1W-EIP21,
CJ2H-CPU@@-EIP, CJ2M-
CPU3@
Other company’s device
Configuration 3 Other company’s device CS1W-EIP21, CJ1W-EIP21,
CJ2H-CPU@@-EIP, CJ2M-
CPU3@
Connection status Source of error Handling
General
Status
(hex)
Additional
Status
(hex)
Configuration 1 Configuration 2 Configuration 3
00 0000 Normal status code:
The connection has been
opened and the tag data link is
communicating normally.
--- --- ---
01 0100 Error code returned from target:
Attempted to open multiple con-
nections at the same connec-
tion.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer for details on
preventing the error
from occurring in the
future.)
Depends on the orig-
inator’s specifica-
tions.
(Contact the origina-
tor device’s manufac-
turer for details on
preventing the error
from occurring in the
future.)
01 0103 Error code returned from target:
Attempted to open a connection
with an unsupported transport
class.
This error does
not occur. Confirm that the tar-
get supports Class
1.
Confirm that the
originator supports
Class 1.
01 0106 Duplicate consumers:
Attempted to open multiple con-
nections for single-consumer
data.
If the tag data link
is stopped or
started, this error
may occur accord-
ing to the timing,
but the system will
recover automati-
cally.
Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
If the tag data link is
stopped or started,
this error may occur
according to the tim-
ing, but the system
will recover automat-
ically.
01 0107 Error code returned from target:
Attempted to close a connec-
tion, but that connection was
already closed.
This error does
not occur. This error does not
occur. This is not an error
because the connec-
tion is already
closed.
01 0108 Error code returned from target:
Attempted to open a connection
with an unsupported connection
type.
This error does
not occur. Check which con-
nection types can be
used by the target.
(Contact the manu-
facturer.)
Only multicast and
point-to-point can be
set.
Check which con-
nection types can be
used by the origina-
tor.
(An error will occur if
a connection other
than multicast or
point-to-point is set.)
360
Connection Status Codes and Error Processing Section 14-3
01 0109 Error code returned from target:
The connection size settings
are different in the originator
and target.
Check the connection sizes set in the originator and target.
01 0110 Error code returned from target:
The target was unable to open
the connection, because of its
operating status, such as down-
loading settings.
Check whether
the tag data link is
stopped at the tar-
get. (Restart the
tag data link com-
munications with
the control bit.)
Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Check whether the
tag data link is
stopped at the origi-
nator. (Restart the
tag data link commu-
nications with the
control bit.)
01 0111 Error code returned from target:
The RPI was set to a value that
exceeds the specifications.
This error does
not occur. Check the target’s
RPI setting specifica-
tions.
Set the originator’s
RPI setting to 10
seconds or less.
01 0113 Error code generated by origi-
nator or returned from target:
Attempted to open more con-
nections than allowed by the
specifications (CJ2M: 32, other
CPU Units: 256).
Check the con-
nection settings
(number of con-
nections) at the
originator and tar-
get.
Check the connec-
tion settings (number
of connections) at
the originator and
target.
Check the connec-
tion specifications for
another company’s
devices.
Check the connec-
tion settings (number
of connections) at
the originator and
target.
Check the connec-
tion specifications for
another company’s
devices.
01 0114 Error code returned from target:
The Vendor ID and Product
Code did not match when open-
ing connection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Confirm that the tar-
get device’s EDS file
is correct.
Check the origina-
tor’s connection set-
tings.
01 0115 Error code returned from target:
The Product Type did not match
when opening connection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Confirm that the tar-
get device’s EDS file
is correct.
Check the origina-
tor’s connection set-
tings.
01 0116 Error code returned from target:
The Major/Minor Revisions did
not match when opening con-
nection.
Check the major
and minor revi-
sions set for the
target device and
connection. If nec-
essary, obtain the
EDS file and set it
again.
Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Confirm that the tar-
get device’s EDS file
is correct.
Check the origina-
tor’s connection set-
tings.
01 0117 Error code returned from target:
The tag set specified in the con-
nection’s target variables does
not exist.
Check whether
the originator and
target tag sets
and tags are set
correctly.
CJ2 CPU Units
Only: Check sym-
bol settings in the
CPU Unit.
Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Check the origina-
tor’s connection set-
tings. Check whether
the target’s tag sets
and tags are set cor-
rectly.
CJ2 CPU Units Only:
Check symbol set-
tings in the CPU
Unit.
Connection status Source of error Handling
General
Status
(hex)
Additional
Status
(hex)
Configuration 1 Configuration 2 Configuration 3
361
Connection Status Codes and Error Processing Section 14-3
01 011A Error code returned from origi-
nator:
Connection could not be estab-
lished because the buffer was
full due to high traffic.
An unexpected
network load may
have been
received. Use the
Network Configu-
rator Device Moni-
tor or the Ethernet
Tab Page to check
the bandwidth
usage, and cor-
rect the load. If
there are places
where broadcast
storms occur,
such as loop con-
nections in the
network connec-
tion format, then
correct them.
An unexpected net-
work load may have
been received. Use
the Network Configu-
rator Device Monitor
or the Ethernet Tab
Page to check the
bandwidth usage,
and correct the load.
If there are places
where broadcast
storms occur, such
as loop connections
in the network con-
nection format, then
correct them.
Follow the operating
specifications for the
originator. (Consult
the originator manu-
facturer.)
01 011B Error code returned from target:
The RPI was set to a value that
is below the specifications.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Set the originator’s
RPI setting to 0.5 ms
or greater.
01 0203 Error code returned from target:
The connection timed out.
Tag data link communications from the target timed out. Check
the power supply and cable wiring of the devices in the commu-
nications path, including the target and switches. If performance
has dropped due to heavy load, change the performance set-
tings. For example, increase the timeout time or RPI setting.
01 0204 Error code returned from target:
The connection-opening pro-
cess timed out.
There was no response from the target. Check the power supply
and cable wiring of the devices in the communications path,
including the target and switches.
01 0205 Error code returned from target:
There was a parameter error in
the frame used to open the con-
nection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
01 0302 Error occurred at originator or
error code returned from target:
The tag data link’s allowable
bandwidth (pps) was exceeded.
Check the origina-
tor and target con-
nection settings
(number of con-
nections and
RPI).
Check the target’s
connection settings
(number of connec-
tions and RPI).
Check the originator
and target connec-
tion settings (number
of connections and
RPI).
01 0311 Error code returned from target:
There was a parameter error in
the frame used to open the con-
nection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
01 0312 Error code returned from target:
There was a parameter error in
the frame used to open the con-
nection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
01 0315 Error code returned from target:
There was a parameter error in
the frame used to open the con-
nection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
Connection status Source of error Handling
General
Status
(hex)
Additional
Status
(hex)
Configuration 1 Configuration 2 Configuration 3
362
Connection Status Codes and Error Processing Section 14-3
01 0316 Error code returned from target:
There was a parameter error in
the frame used to close the con-
nection.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
01 031C Error code generated in origina-
tor:
Some other error occurred.
This error does
not occur. The originator gener-
ates this code when
an unsupported
response code is
returned from the
target in reply to a
connection-opening
request.
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
08 --- Error code returned from target:
There is no Forward Open or
Large Forward Open service in
the target device.
This error does
not occur. Depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
D0 0001 Error code generated in origina-
tor:
The connection operation is
stopped.
The connection
was stopped
because the Tag
Data Link Stop Bit
was turned ON, or
the settings data
is being down-
loaded.
Either turn ON the
Tag Data Link
Start Bit, or wait
until the settings
data has been
downloaded.
Includes Control-
ler stop errors,
Unit failure, and
EM bank files at
the refresh desti-
nation. To handle
these errors, refer
to 14-2-1Errors
Occurring at the
EtherNet/IP Unit
or built-in Ether-
Net/IP port.
The meaning of this
error code is defined
by each vendor, so it
depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
D0 0002 Error code generated in origina-
tor:
The connection is being opened
(opening processing in
progress).
Wait until the
opening process-
ing is completed.
The meaning of this
error code is defined
by each vendor, so it
depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
Depends on the orig-
inator’s specifica-
tions. (Contact the
originator device’s
manufacturer.)
Connection status Source of error Handling
General
Status
(hex)
Additional
Status
(hex)
Configuration 1 Configuration 2 Configuration 3
363
Connection Status Codes and Error Processing Section 14-3
Unique OMRON Error Codes
01 0810 Error code returned from target:
New data could not be obtained
from the CPU Unit when open-
ing connection. (The Unit will
automatically retry, and attempt
to open the connection again.)
This error may
occur if the CPU
Unit’s cycle time
was long when
opening the con-
nection, the speci-
fied EM bank was
converted to file
memory, or some
problem in the
PLC caused the
PLC to stop.
If the cycle time
was too long, the
problem will be
resolved automat-
ically. If the EM
bank is set as file
memory, change
the storage loca-
tion for the tag
data. If the PLC
has stopped,
identify and cor-
rect the error.
If the PLC system
is stopped, iden-
tify the cause of
the error from the
CPU Unit error
data.
The meaning of this
error code is defined
by each vendor, so it
depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
The meaning of this
error code is defined
by each vendor, so it
depends on the origi-
nator’s specifica-
tions.
(Contact the origina-
tor device’s manufac-
turer.)
01 0811 Error code generated in origina-
tor:
New data could not be obtained
from the CPU Unit when open-
ing connection. (The Unit will
automatically retry, and attempt
to open the connection again.)
This error may
occur if the CPU
Unit’s cycle time
was long when
opening the con-
nection, or the
specified EM bank
was converted to
file memory.
If the cycle time
was too long, the
problem will be
resolved automat-
ically. If the EM
bank is set as file
memory, change
the storage loca-
tion for the tag
data.
The meaning of this
error code is defined
by each vendor, so it
depends on the tar-
get’s specifications.
(Contact the target
device’s manufac-
turer.)
The meaning of this
error code is defined
by each vendor, so it
depends on the origi-
nator’s specifica-
tions.
(Contact the origina-
tor device’s manufac-
turer.)
Connection status Source of error Handling
General
Status
(hex)
Additional
Status
(hex)
Configuration 1 Configuration 2 Configuration 3
364
Error Log Function Section 14-4
14-4 Error Log Function
Errors detected by the EtherNet/IP Unit or built-in EtherNet/IP port are stored
in the error log along with the date and time of their occurrence. The error log
can be read and cleared from the Network Configurator.
Some error log records are cleared when the CPU Unit’s power goes OFF,
and other records are not cleared.
14-4-1 Error Log Data Specifications
Each error is recorded as one record in the error log.
Structure of Each Record
14-4-2 Error Log Registration
Error Log Storage Area When an error occurs, information on the error and the time stamp are stored
in the Unit’s internal RAM as an error log record. Serious errors are recorded
in non-volatile EEPROM as well as RAM. The time read from the CPU Unit
during cyclic servicing is used for the time stamp.
The error log records stored in EEPROM are copied to RAM when the Unit
starts operating, so these records are retained even when the Unit’s power is
turned OFF or the Unit is restarted.
When the error log is read, the error log records in RAM are read. When the
error log is cleared, the error log records in both RAM and EEPROM are
erased.
Error Log Overflows The error log can record up to 64 records. If another error occurs when the log
is full, the oldest record will be erased to make room for the new error record.
Power Interruptions when
Saving to EEPROM If the power supply is interrupted or the Unit is restarted while the error log is
being written to EEPROM, the error log may be corrupted. When the Unit
starts, it performs a checksum test on the error log data read from EEPROM
to detect corrupted data.
14-4-3 FINS Commands for Error Logs
The following FINS commands can be sent to the EtherNet/IP Unit or built-in
EtherNet/IP port to read or clear the error log.
For details, refer to Appendix E FINS Commands Addressed to EtherNet/IP
Units or Built-in EtherNet/IP Ports.
Item Specifications
Record length 10 bytes/record
Number of records 64 records max.
Data type Binary (time information: BCD)
Bit 15 Bit 00
Error code
Detail code
Minutes Seconds
Day of month Hour
Year Month
Command code Function name
MRC SRC
21 02 ERROR LOG READ
03 ERROR LOG CLEAR
365
Error Log Function Section 14-4
14-4-4 Error Log Error Codes
Error
code
(hex)
Error Detail code Saved in
EEPROM
First byte Second byte
0001 CPU Unit watchdog timer error 00 hex 00 hex Yes
0002 CPU Unit service monitoring error Monitoring time (ms) Yes
0006 Other CPU error Bit D11: Unit not in Registered I/O Tables
(Other bits are reserved for system use.) Yes
000E I/O bus error 00 hex 00 hex Yes
000F CPU Unit initialization error 00 hex 00 hex Yes
0011 Event timed out MRC (main command) SRC (subcommand) Yes
0012 CPU Unit memory error 01 hex: Read error
02 hex: Write error
03 hex: Routing tables
50 hex: CPU Bus Unit
Area (CIO or DM)
Yes
0015 CPU Unit fatal error 00 hex 00 hex Yes
0017 Tag database error 00 hex 00 hex Yes
0103 Resend count exceeded (send failed) FINS Command:
Bit 15: OFF
Bits 08 to 14: Source network address
Bits 00 to 07: Source node address
FINS Response:
Bit 15: ON
Bits 08 to 14: Destination network address
Bits 00 to 07: Destination node address
CIP Frame:
FFFF
No
0105 Node address setting error (send failed) No
0107 Remote node not in network (send failed) No
0108 No Unit with specified unit address (send
failed) No
010B CPU Unit error (send failed) No
010D Destination address not in routing tables
(send failed) No
010E Not registered in routing tables (send failed) No
010F Routing table error (send failed) No
0110 Too many relay points (send failed) No
0111 Command too long (send failed) No
0112 Header error (send failed) No
0117 Internal buffers full; packet discarded No
0118 Illegal packet discarded No
0119 Local node busy (send failed) No
0120 Unexpected routing error No
0122 Service not supported in current mode;
packet discarded No
0123 Internal send buffer full; packet discarded No
0124 Maximum frame size exceeded; routing
failed No
0125 Response timeout; packet discarded No
020F Communications controller error 00 hex 01 hex Yes
0211 IP address duplication Port number (always 02) Lower byte of IP address Yes
021A Logic error in setting table 00 hex 02 hex: Network parame-
ters
03 hex: Routing tables
04 hex: Unit Setup
0E hex: Unit name
12 hex: Status area layout
setting error
13 hex: Status area layout
setting verification error
15 hex: Installation in a
PLC of another series
(e.g., from CJ1 to CJ2)
after setting the Unit.
Yes
366
Error Log Function Section 14-4
0300 Parameter error; packet discarded FINS Command:
Bit 15: OFF
Bits 08 to 14: Source network address
Bits 00 to 07: Source node address
FINS Response:
Bit 15: ON
Bits 08 to 14: Destination network address
Bits 00 to 07: Destination node address
CIP Frame:
FFFF
No
0347 I/O refreshing error 00 hex 00 hex Yes
03C0 FINS/TCP setting error 01 to 10 hex:
Connection number 01: Automatically allo-
cated FINS node address
duplication
02: Destination IP address
error
03: Destination port num-
ber error
No
03C1 Server settings error 00 hex: DNS
03 hex: SNTP
04 hex: FTP
06 hex: BOOTP
07 hex: SNMP
08 hex: SNMP Trap
09 hex: FINS/UDP
0A hex: FINS/TCP
01: IP address
02: Host name
03: Port number
04: Other parameter
No
03C2 FINS/TCP packet discarded 01 to 10 hex:
Connection number 02 hex: Reopening
because remote node
closed
03 hex: Reopening
because of reception error
04 hex: Reopening
because of transmission
error
05 hex: Reopening
because RST received
from remote node
06 hex: Reopening
because of no keep-alive
response
07 hex: Illegal FINS/TCP
procedure
08 hex: Insufficient mem-
ory during server process-
ing
09 hex: Insufficient mem-
ory during client process-
ing
0A hex: Insufficient mem-
ory during node switching
No
03C3 FINS/UDP packet discarded 00 hex 01 to FE hex:
Source node address No
Error
code
(hex)
Error Detail code Saved in
EEPROM
First byte Second byte
367
Error Log Function Section 14-4
03C4 Server connection error 00 hex: DNS
03 hex: SNTP
04 hex: FTP
06 hex: BOOTP
07 hex: SNMP
08 hex: SNMP Trap
01 hex: Specified host
does not exist
02 hex: No such service at
specified host
03 hex: Timeout
06 hex: Host name resolu-
tion error
07 hex: Transmission error
08 hex: Reception error
09 hex: Other error
0A hex: Obtaining IP
address error
No
03C6 Clock write error 0001: The clock time
could not be updated
because a error occurred
in the CPU Unit.
Clear the error from the
CPU Unit. No
0002: The clock time
could not be updated
because the CPU Unit or
operating mode does not
support this function.
Refer to SECTION 12
Automatic Clock Adjust-
ment Function and check
the application conditions.
03D0 Ethernet basic setting error 01 hex: Ethernet setting
error 01 hex: Checksum error
11 hex: Inconsistent set-
tings
12 hex: Specified baud
rate is not supported.
Yes
02 hex: TCP/IP basic set-
ting error 01 hex: Checksum error
11 hex: Invalid IP address
12 hex: Invalid subnet
mask
13 hex: Invalid default
gateway address
14 hex: Invalid primary
name server
15 hex: Invalid secondary
name server
16 hex: Invalid domain
name
17 hex: Invalid host name
03D1 Ethernet advanced setting error 02 hex: FINS setting error 01 hex: Checksum error
10 hex: Invalid IP router
table
11 hex: Invalid FINS/UDP
setting
12 hex: Invalid FINS/TCP
setting
13 hex: Invalid FTP setting
14 hex: Invalid SNTP set-
ting
15 hex: Invalid SNMP set-
ting
16 hex: Invalid SNMP trap
setting
Yes
03D2 Packet discarded. 01 hex 00 hex No
Error
code
(hex)
Error Detail code Saved in
EEPROM
First byte Second byte
368
Troubleshooting Section 14-5
Note If a memory error occurs in the error log area of EEPROM, the record will not
be stored in EEPROM.
14-5 Troubleshooting
14-5-1 CPU Unit's ERR/ALM Indicator Lit or Flashing
Use the following table to troubleshoot the system when the CPU Unit’s ERR/
ALM indicator is lit or flashing when the EtherNet/IP Unit or built-in EtherNet/
IP port is mounted.
For details, refer to the CPU Unit’s Operation Manual.
03D3 Link OFF error 00 hex 00 hex No
03D4 Verification error (Tag data link only)
Note For details on identifying the cause of
the verification error, refer to 14-3
Connection Status Codes and Error
Processing.
This error will not be stored when a
target node is missing for version 2.0
or higher.
Connection instance num-
ber (0 to 255) Lower byte of IP address No
03D5 Tag data link error 00 hex Lower byte of IP address No
0601 CPU Bus Unit error Variable Yes
0602 CPU Bus Unit memory error 01: Read error
02: Write error
02 hex: Network parame-
ter
06 hex: Error log
09 hex: Identity data
0E hex: Unit name
0F hex: Ethernet basic
setting
10 hex: Ethernet
advanced setting
11 hex: MAC address
12 hex: Status area layout
setting
14 hex: Term Tag address
resolution memory write
error
Ye s
(See
note.)
Error
code
(hex)
Error Detail code Saved in
EEPROM
First byte Second byte
An I/O verification
error occurred. • Confirm that the Unit is connected properly.
• Check the I/O table with the I/O Table Verification operation
and correct it if necessary. After correcting it, perform the I/O
Table Create operation.
A CPU Bus Unit
setting error
occurred.
• The CPU Bus Unit model registered in the I/O tables does
not match the model of CPU Bus Unit actually mounted.
Check the I/O tables with the I/O Table Verification operation
and correct it if necessary.
After correcting the I/O tables, perform the I/O Table Create
operation.
A CPU Bus error
occurred. • Confirm that the Unit is connected properly.
• Restart the Unit. Replace the Unit if it doesn’t restart.
An I/O Bus error
occurred. • Confirm that the Unit is connected properly.
• Restart the Unit. Replace the Unit if it doesn’t restart.
369
Troubleshooting Section 14-5
14-5-2 General Ethernet Problems
14-5-3 Tag Data Links Fail to Start
Use the following table to troubleshoot tag data links when the Tag Data Links
Operating Flag (bit 15 in Communications Status 1) does not go ON.
The 100M and 10M
Indicators on the
EtherNet/IP Unit or
CPU Unit are both
OFF.
• Confirm that the cable being used has the correct ratings.
• Confirm that the cable is properly connected to the switching
hub, and the hub’s power supply is ON. (The 7-segment dis-
play will indicate error E1.)
• If the switching hub’s settings can be changed, confirm that
the Ethernet link settings are the same as the settings for the
EtherNet/IP Unit or built-in EtherNet/IP port. (For details,
refer to 3-4 Network Installation.)
The NS Indicator
on the EtherNet/IP
Unit or CPU Unit is
lit red.
• Check whether the same IP address is set on another node.
(The 7-segment display will indicate error F0.)
The indicators on
the EtherNet/IP Unit
or CPU Unit are all
OFF.
• Check whether power is being supplied to the PLC.
• Check whether the EtherNet/IP Unit or built-in EtherNet/IP
port is mounted in the Backplane correctly.
• If a watchdog timer (WDT) error has occurred in the PLC, fol-
low the procedures described in the PLC’s Operation Man-
ual to correct the problem.
• All of the indicators for the EtherNet/IP Unit or built-in Ether-
Net/IP port will be OFF if a CPU Bus Unit error has occurred.
Check for a CPU Bus Unit error.
• Restart the Unit. Replace the Unit if it doesn’t restart.
The MS indicator
on the EtherNet/IP
Unit or CPU Unit is
lit green, but the NS
indicator remains
OFF.
• If the EtherNet/IP Unit's 7-segment display is displaying an
error code, refer to the tables in 14-2 Using the LED Indica-
tors and Display for Troubleshooting.
• Confirm that the cables are properly connected to the
switching hub and the power supply to the switching hub is
ON.
• If data is being restored by the simple backup function, wait
until the restore operation is completed.
The MS indicator
on the EtherNet/IP
Unit or CPU Unit is
lit green, but the NS
indicator contin-
ues to flash green.
• If the EtherNet/IP Unit's 7-segment display is displaying an
error code, refer to the tables in 14-2 Using the LED Indica-
tors and Display for Troubleshooting.
• The NS indicator will continue to flash green if the tag data
link settings have not been set in the Unit. Use the Network
Configurator to set the tag data link settings in the Unit, and
then restart the Unit.
The MS indicators
is lit green on the
EtherNet/IP Unit or
CPU Unit, but the
NS indicator con-
tinues to flash red.
• Identify the error code shown on the 7-segment display
based on the tables in 14-2 Using the LED Indicators and
Display for Troubleshooting, and eliminate the cause of the
error.
370
Troubleshooting Section 14-5
14-5-4 Tag Data Link Problems
The tag data isn't
simultaneous. Observe the following precautions when writing application
programs:
• Maintain the simultaneity of data in connection-units between
the PLC and EtherNet/IP Unit or built-in EtherNet/IP port.
• If another company's device is being used, refer to that
device's user's manual for details.
At startup, the
received data is
OFF unexpectedly.
• When received data is used in the ladder program, use the
All Tag Data Links Operating Flag in Communications Status
1, or the Target Node PLC Operating Flag as a condition. If
the Target Node PLC Operating Flag is used, the PLC status
must be included in tag sets of both the sending and receiv-
ing nodes.
• If the Output OFF function (Output Inhibit) is enabled in the
output (produce) tag settings, all of the output data will be
OFF if a fatal error occurs in the CPU Unit or the Output OFF
Bit is turned ON. Check the status of the output (producer)
PLC.
The tag data links
start and stop com-
municating inter-
mittently.
• Check whether the baud rate is set to 10 Mbps, or a 10M or
100M repeater hub is being used. The tag data link perfor-
mance is based on the use of switching hubs. The bandwidth
listed in the specifications (CJ2M: 3,000 pps, other CPU
Units: 6,000 pps) is achieved when the Unit auto-negotiates
to full-duplex at 100 Mbps.
• Refer to 14-1 Checking Status with the Network Configurator
for details on checking the error counters on the Monitor
Device Window’s Ethernet Information Tab Page. The error
and discarded packet counters indicate problems such as
noise in the communications path, the use of substandard
cables, damaged cables/connectors, loose connectors,
abnormally high communications load, or incorrect wiring
(loops) in the switching hub wiring.
• Contact the switching hub manufacturer to determine
whether there are any problems with the transfer capacity of
the switching hubs in the communications path. If switching
hubs are arranged in a cascade connection, there may be a
heavy load concentrated at a mid-level switching hub. In the
EtherNet/IP Unit or built-in EtherNet/IP port itself, processing
is performed with a higher priority than message communi-
cations, so specifications provide for a 3,000 pps bandwidth
for the CJ2M and a 6,000 pps bandwidth for other CPU Units
in tag data link performance only.
• Refer to 14-1 Checking Status with the Network Configurator
for details on checking the connection status on the Monitor
Device Window’s Connection Tab Page. Eliminate any errors,
which can be identified in the tables in 14-3 Connection Sta-
tus Codes and Error Processing.
371
Troubleshooting with FINS Response Codes Section 14-6
14-5-5 Message Timeout Problems
14-6 Troubleshooting with FINS Response Codes
The cause of errors that occur when using the SEND(090), RECV(098), or
CMND(490) instructions can be identified from the response codes. (Refer to
the description of Communications Port Completion Codes in 8-6-4 Writing
Programs for the storage locations of response codes generated by the
SEND(090), RECV(098), or CMND(490) instructions.)
This section describes the completion codes produced by EtherNet/IP Units.
For details on completion codes produced by CPU Units, other CPU Bus
Units, or computers equipped with FINS services, refer to the device’s opera-
tion manual.
The 6th, 7th, and 15th bits of the response codes have specific functions. The
6th bit will be ON when a non-fatal error has occurred in the PLC at the remote
node; the 7th bit will be ON when a fatal error has occurred in the PLC at the
remote node; and the 15th bit will be ON when a network relay error has
occurred. The following table explains the meaning of the completion codes.
Timeout errors
occur frequently in
message services
(CIP UCMM, CIP
Class 3, or FINS).
• When there is a high load in the tag data link, and the CPU
Unit’s cycle time is relatively long or there are messages
coming in from many nodes, the message service response
time may be delayed and messages may be discarded occa-
sionally.
• In this case, the communications load must be reduced by
increasing (slowing) the tag data link’s RPI, reducing the
message load, or increasing the timeout value.
• The tag data link’s bandwidth usage can be checked on the
Monitor Device Window’s Ethernet Information Tab Page.
Refer to 14-1 Checking Status with the Network Configurator
for details.
• The error log error codes that indicate discarded messages
(insufficient memory) due to heavy communications loads
are 0117, 0119, 0123, 0125, 03C2 (detail code @@08,
@@09, or @@0A), 03C3, and 03D2. Refer to 14-1 Checking
Status with the Network Configurator for details on reading
the error codes on the Error History Tab Page.
• For information on preventing high loads in FINS communi-
cations, refer to 8-7 Precautions on High Traffic in FINS
Communications.
7654321076543210
First byte Second byte
Bit
PLC Fatal Error Flag PLC Non-fatal Error Flag
Relay Error Flag
Main response code (RES) Sub response code (SRES)
Main response
code Sub response code Item to check Likely cause Corrective action
Value and
meaning Value and meaning
00 Normal
completion 00 --- --- --- ---
372
Troubleshooting with FINS Response Codes Section 14-6
01 Local node
error 03 Local node send
error --- Lack of available space in
internal buffers The load (traffic) on the Ether-
net Unit is too heavy. Check
your user applications.
05 Node address set-
ting error Local IP
address The network cannot be
used because the IP
address setting is incor-
rect.
Correct the local IP address.
07 Local node busy
(send failed) System load Lack of available space in
internal buffers The load (traffic) on the Ether-
net Unit is too heavy. Check
your user applications.
02 Remote
node error 01 Remote node not in
network IP address
table and IP
router table
IP address of remote
node not set correctly. Set IP address of remote
node into IP address table
and, if internetwork transmis-
sion is required, into the IP
router table.
02 No Unit with speci-
fied unit address Instruction’s
control data There is no Unit with the
specified unit address. Check the remote node's unit
address.
05 Response timeout Transfer condi-
tions
(Use FINS
status read
commands.)
Message packet was cor-
rupted by transmission
error.
Increase the number of trans-
mit retry attempts.
Instruction’s
control data The response monitoring
time is too short. Set a longer response moni-
toring time.
Read the error
log. The transmission frame
may be corrupted or the
internal reception buffer
full.
Read out the error log and
correct the system as
required.
03 Unit error
(Controller
error)
01 Communications
controller error Affected con-
troller’s ERC
indicator
Error occurred in the
communications control-
ler.
Take corrective action, refer-
ring to troubleshooting proce-
dures in this section.
02 PLC error Affected
node’s LED
indicators
CPU Unit error occurred
in the PLC at the remote
node.
Clear the error in the CPU
Unit. (Refer to the PLC's oper-
ation manuals.)
04 Unit number setting
error Unit number The unit number setting
is incorrect. Confirm that the unit number
set on the switch is within the
specified range and that the
same unit number is not used
twice in the same network.
04 Service not
supported 01 Unsupported com-
mand Command
code The specified command
code is not supported by
the destination Unit.
Check the command code.
FINS header
frame length A short frame (4 bytes) is
being used for the FINS
header frame.
The EtherNet/IP Unit does not
support short headers.
05 Routing
error 01 Routing table setting
error Routing tables Remote node is not set in
the routing tables. Set the destination address in
the routing tables.
02 Routing tables not
registered Routing tables Destination is unknown
because there are no
routing tables.
Set routing tables at the local
node, remote node, and any
relay nodes.
03 Routing table error Routing tables Routing table error Set the routing tables cor-
rectly.
04 Too many relay
points Network con-
figuration The maximum number of
network levels (3) was
exceeded in the com-
mand.
Redesign the network, or
reconsider the routing tables
to reduce the number of relay
nodes in the command.
Main response
code Sub response code Item to check Likely cause Corrective action
Value and
meaning Value and meaning
373
Troubleshooting with FINS Response Codes Section 14-6
10 Command
format error 01 Command too long Command
data The command is too
long. Check the command format of
the command and set it cor-
rectly.
The command exceeded
1,473 bytes when broad-
casting.
02 Command too short Command
data The command is too
short.
03 Number of items
does not match
amount of data
Command
data The specified number of
items does not match the
amount of write data.
Check the number of items
and amount of data, and
make them agree.
05 Header parameter
error Command
data Data for another node on
the same network was
received from the net-
work.
Check the command format of
the command and set it cor-
rectly.
Attempted to send
response data for a
broadcast address.
11 Parameter
error 00 Parameter error Parameters in
command
data
The specified parame-
ters are incorrect. Check the command data and
set the parameters correctly.
The UDP/TCP socket
number was not within
the proper range.
Be sure the socket number is
between 1 and 8.
The local UDP port num-
ber might be set to 0. Set the local UDP port num-
ber correctly.
01 No data area code Variable type
in command
data
A correct memory area
code has not been used
or EM Area is not avail-
able.
Check the command’s data
area code in the Results Stor-
age Area and set the appro-
priate code.
03 Address out-of-
range error First word
address in
command
data
The first word is in an
inaccessible area. Check the data area range,
and set a first word that is in
an accessible area.
The specified bit number
is not 00. Check the command’s data
area code in the Results Stor-
age Area. The bit address
must be 00 for EtherNet/IP
Units.
04 Address range over-
flow Command
data The address range speci-
fied in the command is
not correct.
Set the address in the com-
mand data so that the start
address plus the number of
words does not exceed
accessible memory.
0B Response too long Command
data The response frame is
longer than allowed. Correct the number of data
elements or other parameters
in the command data for
which the response is being
returned.
0C Parameter error Parameters in
command
data
The specified parame-
ters are incorrect. Check the command data and
set the parameters correctly.
21 Cannot
write 08 Cannot change IP address
conversion
method
A FINS message was
received from an IP
address that differed from
the ones in the Unit
Setup with FINS node
addresses that could not
be dynamically changed.
Correct the relationships
between IP addresses and
FINS node addresses. Refer
to SECTION 5 Determining IP
Addresses for details.
Main response
code Sub response code Item to check Likely cause Corrective action
Value and
meaning Value and meaning
374
Troubleshooting with FINS Response Codes Section 14-6
22 Status error
(operating
mode dis-
agreement)
0F Cannot execute
because service is
being processed.
Socket status
area The same socket service
is already in progress at
the specified socket num-
ber.
Use the corresponding socket
status flag in PLC memory to
be sure that socket service
has finished before starting
services again.
10 Socket not open Socket status
area The specified socket is
not open. Open the socket. (For TCP
sockets, wait until the connec-
tion is made.)
11 Local node busy
(send failed) System load Lack of available space in
internal buffers The load (traffic) on the Ether-
net Unit is too heavy. Check
your user applications.
20 FINS/TCP not con-
nected Unit Setup Not opened due to sys-
tem settings. Correctly set the Unit Setup,
FINS/TCP connection num-
ber, remote IP address, and
remote port number.
21 Not opened due to a
change command from
the FINS/TCP connec-
tion’s remote node.
22 Closed by remote node;
opening again.
23 Opening again because
of a reception error.
24 Opening again because
of a send error.
25 Opening again because
of an RST response in
keep-alive.
26 Opening again because
there was no response in
keep-alive.
30 Establishing connec-
tion Command
data A connection is already
established with the
specified remote node.
Correct the settings for the
FINS/TCP connection num-
ber, the remote IP address,
and the remote port number.
31 Cannot change con-
nection Unit Setup
and com-
mand data
The specified connection
number is not set as a
FINS/TCP client in the
Unit Setup.
Correct the settings for the
Unit Setup, the FINS/TCP
connection number, the
remote IP address, and the
remote port number.
32 Cannot execute
because service was
interrupted
Command
data While a remote node
change was being pro-
cessed for the specified
connection number, a
request for a change was
received and the pro-
cessing was stopped.
Correct the settings for the
FINS/TCP connection num-
ber, the remote IP address,
and the remote port number.
23 No such
Unit (Envi-
ronment
error)
05 Parameters Unit Setup IP address conversion
failed. Check the IP address and
subnet mask in the Unit
Setup, and correct if neces-
sary.
07 Configuration error IP address
conversion in
Unit Setup
IP address conversion is
set for automatic conver-
sion only.
Check the IP address conver-
sion setting in the Unit Setup.
This error will be generated
for the READ IP ADDRESS
TABLE command only.
Main response
code Sub response code Item to check Likely cause Corrective action
Value and
meaning Value and meaning
375
Appendix A
CS/CJ-series Ethernet Unit Function Comparison
Item Support for function
Ethernet Unit EtherNet/IP Unit or built-in EtherNet/
IP port
Unit version 1.0 Unit version 2.0
Tag data link communications service No Yes Yes
CIP message communications service No Yes Yes
FINS/UDP service Yes Yes Yes
FINS/TCP service Yes Yes Yes
Socket service Yes No No
File transfer (FTP) Yes No Yes
Mail send/receive Yes No No
Web functions Yes No No
Automatic adjustment of PLC’s internal clock Yes No Yes
Simple backup function Yes Yes Yes
Error log Yes Yes Yes
Response to PING command Yes Yes Yes
SNMP/SNMP trap No No Yes
CIDR function for IP addresses No No Yes
Online connection by EtherNet/IP using CX-One No No Yes
Online connection by Ethernet (FINS) using CX-One Yes Yes Yes
Online connection by EtherNet/IP using Network Configu-
rator No Yes Yes
376
CS/CJ-series Ethernet Unit Function Comparison Appendix A
377
Appendix B
Ethernet Network Parameters
Note The hold time is 3 s for the UCMM service, Class 3 service, and tag data link open/close processing.
Parameter Value Description
TCP send buffer 4,096 bytes Maximum capacity of the TCP send buffer
TCP receive buffer 4,096 bytes Maximum capacity of the TCP receive buffer
UDP send buffer 9,000 bytes Maximum capacity of the UDP send buffer
UDP receive buffer 9,016 bytes Maximum capacity of the UDP receive buffer
FINS receive buffer 16,383 bytes Maximum capacity of the FINS receive buffer
RAW send buffer 2,048 bytes Maximum capacity of the RAW send buffer
RAW receive buffer 2,048 bytes Maximum capacity of the RAW receive buffer
Hold timer 75 s (See note.) The hold timer is used for active open processing of TCP sockets.
An ETIMEDOUT error will occur if connection is not completed within
75 s.
Resend timer Initial value: 250 ms
Maximum value: 64 s
The resend timer is used to monitor completion of reception of arrival
confirmations when transferring data via TCP sockets. If the timer setting
is exceeded before arrival confirmation is received, data is resent.
Resends are performed from the first timeout (1 s) through the 12th time-
out (64 s).
An ETIMEDOUT error will occur after the 12th timeout.
Continue timer Initial value: 1 s
Maximum value: 60 s The continue timer starts if preparations have been completed to send
data but the send window is too small (either 0 or too small) to send the
data and the remote node has not requested that communications be
restarted. Confirmation of the window size is requested from the remote
node when the continue timer times out. The initial value of the timer is
5 s and confirmation processing will continue consecutively with increas-
ingly longer times until the maximum time of 60 s is reached.
2MSL timer 60 s The 2MSL timer starts at the TCP socket that first closes the socket and
will run for 60 s in the TIME_WAIT status.
IP reassemble timer 12 s A fragmented IP packet is discarded if it cannot be reassembled within
12 seconds.
ARP timer 20 min/3 min If a complete ARP table entry (with an Ethernet address) is not referred
to for 20 minutes, it is removed from the table.
An incomplete ARP table entry (no response yet returned to the ARP
request) is removed from the table after 3 minutes.
Window size
(initial value of max-
imum window size)
4,096 bytes The initial value of the maximum capacity used to control the conver-
gence of TCP sockets. Actually, the node negotiates with the remote
node and uses the smaller of the values for the two nodes. The window
size will fluctuate with the available space in the TCP reception buffers of
the remote node when processing communications.
Fragment size 1,500 bytes Data packets are fragmented into 1,500-byte IP packets. UDP data is
separated into 1,472-byte fragments before sending.
Segment size 1,024 bytes TCP data is separated into 1,024-byte units, unless the segments are dif-
ferent, in which case it will be separated into 536-byte units.
TTL (Time to Live) 30 Decremented each time an IP router is passed.
Keep-alive timer First time: 5 min
Resend: 5 s × 5 times The keep-alive timer is used for the keep-alive function with TCP connec-
tions. It must be used with UCMM, Class 3.
378
Ethernet Network Parameters Appendix B
379
Appendix C
TCP Status Transitions
The TCP socket status can be confirmed using the socket status data returned for the FINS command
SOCKET STATUS READ (27 64).
Status Meaning
CLOSED Connection closed.
LISTEN Waiting for connection.
SYN SENT SYN sent in active status.
SYN RECEIVED SYN received and sent.
ESTABLISHED Already established.
CLOSE WAIT FIN received and waiting for completion.
FIN WAIT 1 Completed and FIN sent.
CLOSING Completed and exchanged FIN. Awaiting ACK.
LAST ACK FIN sent and completed. Awaiting ACK.
FIN WAIT 2 Completed and ACK received. Awaiting FIN.
TIME WAIT After closing, pauses twice the maximum segment life (2MSL).
rcv FIN
snd ACK
CLOSE
rcv ACK of FIN
rcv ACK of SYN
CLOSED
LISTEN
SYN
RECEIVED SYN
SENT
ESTABLISHED
CLOSING
CLOSED
WAIT
CLOSED
snd SYN, ACK
Passive OPEN CLOSE
ACTIVE OPEN
snd SYN
snd SYN
SEND
CLOSE
rcv SYN
snd ACK
rcv SYN, ACK
snd ACK
snd FIN
CLOSE
snd ACK
rcv FIN
rcv ACK of FIN
snd FIN
rcv FIN rcv ACK of FIN
Timeout=2MSL
LAST-ACK
CLOSE
snd FIN
TIME WAIT
FIN
WAIT-1
FIN WAIT-2
rcv SYN
snd ACK
380
TCP Status Transitions Appendix C
381
Appendix D
CIP Message Communications
This appendix describes CIP message communications.
The basic concepts of CIP message communications are described in this appendix from CIP Object on
page 381 through Example of CIP Message Creation on page 386. Read these sections to improve your
understanding of CIP message communications.
CIP Object
Object Model
In the CIP (Common Industrial Protocol) system, each device is modeled as a group of “Objects.” An Object
abstractly represents a related group of the device’s data values.
When accessing the device from the outside, access an Object.
An Object represents the abstracted device function, processing, and the resulting data.
A request from the outside of Object, such as Read Data, is called “Service.”
Data belonging to the Object is called “Attribute.”
The actual entity of Object is called “Instance” or “Object Instance.”
When Object is generalized, it is called “Class.” For example, “Japan” is one of Instances (Object Instances) of
Class “Nation.”
Object
Object
Object
Device
Service
Data
Processing
Object Instance
Attribute
External request
(Example. Read, Write)
Data
Data
Data
382
CIP Message Communications Appendix D
Terminology
In CIP specifications, “Object,” “Class,” “Instance,” “Attribute” and “Service” are defined as follows:
Specifying an Object Address (Request Path)
This is the basic concept involved in accessing an Object or Attribute.
Each Object Class has a “Class ID”.
There are two types of “Class ID”; one is standardized by ODVA and the other is decided independently by
each device vendor.
Each Object Instance also has ID. This is called “Instance ID.” Different Instance ID is assigned to each Object.
As for Object Class standardized by ODVA, Instance ID is given to it according to the ODVA method. On the
other hand, vendor's own Instance ID is decided independently by the vendor.
Each Attribute also has “Attribute ID.”
Each Object is accessed to by using “Class ID,” “Instance ID,” and “Attribute ID.”
In the device, you can designate Object by specifying these three IDs.
When requesting “Service,” you should specify “Class ID,” “Instance ID,” and “Attribute ID.” (Instance ID and
Attribute ID may not be required, depending on the Service.)
The “Class ID,” “Instance ID,” and “Attribute ID” identify a location in the device and are known as the request
path.
Term Meaning
Object An abstract representation of a particular component within a product.
Class A set of objects that all represent the same kind of system component. A class is a generalization of an
object. All objects in a class are identical in form and behavior, but may contain different attribute values.
Instance A specific and real (physical) occurrence of an object. For example: New Zealand is an instance of the object
class Country. The terms Object, Instance, and Object Instance all refer to a specific Instance.
Attribute A description of an externally visible characteristic or feature of an object. Typically, attributes provide status
information or govern the operation of an Object. For example: the ASCII name of an object; and the repeti-
tion rate of a cyclic object.
Service A function supported by an object and/or object class. CIP defines a set of common services and provides for
the definition of Object Class and/or Vendor Specific services.
Attribute 1
Class ID = 1
Attribute = 3
Attribute 2
Attribute 3
Attribute 4
Instance ID = 1
Instance ID = 1
Class ID = 2
Device
383
CIP Message Communications Appendix D
Route Path
Route Path
In the CIP, unlike the internet protocol, the transmission frame contains a complete relay route from the trans-
mission node to the reception node. The described route is called the “route path.” The route path is described
as “EPATH type.”
The basic concept of the route path is as follows:
First of all, specify a network port of the transmission node with the destination network, and specify a node
address (called the Link Address) on that network. For the relay node, similarly, specify a network port with the
destination network and node address on that network. Then, repeat the same procedure to the final destina-
tion.
Description by EPATH Type
In CIP, the EPATH type is used to describe the route path and request path.
With this method, the route path and request path are divided into segments and a value is assigned to each
segment, so the route path description shows the path to the final destination when the data segments are
joined together.
The segment includes the segment type information and the segment data.
Details of Segment Type
The interpretation method of a segment is included in the first 1 byte, which consists of two parts; a 3-bit “Seg-
ment Type” and a 5-bit “Segment Format.”
#1
#3 #2 #1
Object A Object B
Route Path = Port A: #3, Port C: #1
X Y Z
When sending data from X to Z.
Send data from the network port of X (Port-A) to #3 on that circuit, and the data
reaches Y. Then, send it from the network port of Y (Port-C) to #1 on that circuit.
Through this procedure, the destination node Z can be designated.
Port-A Port-B Port-C Port-D
Segment 1 Segment 2 Segment 3 Segment 4 · · · ·
Segment Type
Segment Format
7 6 5 4 3 2 1 0
384
CIP Message Communications Appendix D
According to CIP Specifications, the Segment Type specifications are decided as follows:
The specifications of Segment Format are different for each Segment Type.
The following sections describe Port Segment, Logical Segment, and Data Segment which are needed to use
the CIP message communications instructions.
Port Segment
The Port Segment is used to specify the path described above.
Set the ID of the port in Port Identifier.
The Port Identifier is 4 bits, so it can have a value between 0 and 15. A port identifier of “0” is reserved and not
available. A port identifier of “1” indicates the backplane port.
A port identifier of “15” has a special meaning, which indicates that the size of Port Identifier is larger than
1 byte, and the 4-bit port identifier (15) is followed by 2-byte Port Identifier. The port identifier does not exceed
1 byte when using the EtherNet/IP Unit or built-in EtherNet/IP port, so this special case is not explained here.
Set the Extended Link Address Size to “1” when that port’s Link Address is larger than 1 byte.
The following diagram shows the Port Segment value when the Extended Link Address Size is set to “0.”
Segment Type Description
765
000Port Segment
0 0 1 Logical Segment
010Network Segment
011Symbolic Segment
100Data Segment
101Data Type
110Data Type
111Reserved
Segment Type Port Identifier
7 6 5 4 3 2 1 0
0 0 0
Extended Link
Address Size
Segment Type Port Identifier
765 43210
000
Extended Link
Address Size
0
7654 3210
Link Address
385
CIP Message Communications Appendix D
Specify the size of Link Address when the Extended Link Address Size is set to “1.” The following diagram
shows the Port Segment value in this case.
Always set the Link Address to an even number of bytes. If there is an odd number of bytes, pad the Link
Address with “00” so that it has an even number of bytes.
Logical Segment
The Logical Segment is used to specify the request path.
The 32-bit logical address format is reserved and cannot be used.
The 8-bit and 16-bit logical address can be used for the Class ID and Instance ID, which specify the request
path.
Segment Type Port Identifier
7 6 5 4 3 2 1 0
0 0 0
Extended Link
Address Size
1
7 6 5 4 3 2 1 0
Link Address Size
7 6 5 4 3 2 1 0
Link Address
7 6 5 4 3 2 1 0
· · · · · · · · · · ·
·
Link Address
· · · · · ·
→
→
Logical Type Description
432
000Class ID
001Instance ID
010Member ID
011Connection Point
100Attribute ID
101Special (Do not use the logical addressing definition for the Logical Format.)
110Service ID (Do not use the logical addressing definition for the Logical Format.)
111Reserved
Logical Format Description
10
0 0 8-bit logical address
0 1 16-bit logical address
1 0 32-bit logical address
11Reserved
Segment Type Logical Type
7 6 5 4 3 2 1 0
0 0 1
Logical Format
Segment Format Bits
386
CIP Message Communications Appendix D
The 8-bit logical address can be used for the Attribute ID. Use the Attribute ID when requesting a Service of a
particular Object of a particular device.
Example of CIP Message Creation
Setting the Route Path
Port Number
The following description explains the network port, which is used to specify the route path. In the CJ2 Series,
the Backplane is also considered part of the network when specifying the Link Address.
CPU Unit
CJ2 (Not supported by CS1/CJ1 CPU Units.)
Each CPU Unit has one backplane port. By convention, the built-in port on a CJ2H-CPU6@-EIP or a
CJ2M-CPU3@ CPU Unit functions as a CPU Bus Unit.
The Backplane port is the Backplane. CPU Unit communications routed through CPU Bus Units always travel
through the backplane.
EtherNet/IP Unit or CJ2 Built-in EtherNet/IP Port
The EtherNet/IP Unit has two ports. A CJ2 CPU Unit also has two built-in EtherNet/IP ports. One is a Back-
plane port and the other is an Ethernet port.
The Backplane port is the Backplane. Communications routed through the CPU Unit, a Special I/O Unit, or
another CPU Bus Unit always travel through the backplane.
Link Address
The Link Address is a node address on the network, which is used to specify the route path.
The method to set the Link Address is different for each network.
In the CS/CJ Series, the Backplane is also considered part of the network when specifying the Link Address.
Backplane
•CPU Bus Unit or Special I/O Unit
In the CS/CJ Series, the base unit is recognized as a backplane port.
CPU Bus Units, such as the EtherNet/IP Unit, are also recognized as nodes on the backplane port.
The Link Address of a CPU Bus Unit on the Backplane is the “unit number + 10 hex.” For example, when
the unit number is 0, the Link Address is 10 hex. When the unit number is F, the Link Address is 1F hex.
The Link Address of a Special I/O Unit on the Backplane is the “unit number + 20 hex.” For example, when
the unit number is 0, the Link Address is 20 hex.
Network
•EtherNet/IP
The Ethernet port’s Link Address is described by the IP address.
The IP address must be described entirely in ASCII.
For example, IP address of 192.168.200.200 will be [31] [39] [32] [2E] [31] [36] [38] [2E] [32] [30] [30] [2E]
[32] [30] [30].
Port Port Number
Backplane 1
Port Port Number
Backplane 1
Ethernet 2
387
CIP Message Communications Appendix D
Response Codes
General Status Code
The General Status Code is stored in the response data after execution of the CMND instruction has been
completed.
General Status
Code (hex) Status Name Description of Status
00 Success Service was successfully performed by the object specified.
01 Connection failure A connection related service failed along the connection path.
02 Resource unavailable Resources needed for the object to perform the requested service were
unavailable.
03 Invalid parameter value See Status Code 20 hex, which is the preferred value to use for this condition.
04 Path segment error The path segment identifier or the segment syntax was not understood by the
processing node. Path processing shall stop when a path segment error is
encountered.
05 Path destination
unknown The path is referencing an object class, instance or structure element that is
not known or is not contained in the processing node. Path processing shall
stop when a path destination unknown error is encountered.
06 Partial transfer Only part of the expected data was transferred.
07 Connection lost The messaging connection was lost.
08 Service not supported The requested service was not implemented or was not defined for this Object
Class/Instance.
09 Invalid attribute value Invalid attribute data detected.
0A Attribute list error An attribute in the Get_Attribute_List or Set_Attribute_List response has a
non-zero status.
0B Already in requested
mode/state The object is already in the mode/state being requested by the service.
0C Object state conflict The object cannot perform the requested service in its current mode/state.
0D Object already exists The requested instance of object to be created already exists.
0E Attribute not settable A request to modify a non-modifiable attribute was received.
0F Privilege violation A permission/privilege check failed.
10 Device state conflict The device's current mode/state prohibits the execution of the requested ser-
vice.
11 Reply data too large The data to be transmitted in the response buffer is larger than the allocated
response buffer
12 Fragmentation of a
primitive value The service specified an operation that is going to fragment a primitive data
value, i.e. half a REAL data type.
13 Not enough data The service did not supply enough data to perform the specified operation.
14 Attribute not supported The attribute specified in the request is not supported.
15 Too much data The service supplied more data than was expected.
16 Object does not exist The object specified does not exist in the device.
17 Service fragmentation
sequence not in
progress
The fragmentation sequence for this service is not currently active for this data.
18 No stored attribute data The attribute data of this object was not saved prior to the requested service.
19 Store operation failure The attribute data of this object was not saved due to a failure during the
attempt.
1A Routing failure (request
packet too large) The service request packet was too large for transmission on a network in the
path to the destination. The routing device was forced to abort the service.
1B Routing failure
(response packet too
large)
The service response packet was too large for transmission on a network in
the path from the destination. The routing device was forced to abort the ser-
vice.
1C Missing attribute list
entry data The service did not supply an attribute in a list of attributes that was needed by
the service to perform the requested behavior.
388
CIP Message Communications Appendix D
1D Invalid attribute value
list The service is returning the list of attributes supplied with status information for
those attributes that were invalid.
1E Embedded service
error An embedded service resulted in an error.
1F Vendor specific error A vendor specific error has been encountered. The Additional Code Field of
the Error Response defines the particular error encountered. Use of this Gen-
eral Error Code should only be performed when none of the Error Codes pre-
sented in this table or within an Object Class definition accurately reflect the
error.
20 Invalid parameter A parameter associated with the request was invalid. This code is used when a
parameter does not meet the requirements of this specification and/or the
requirements defined in an Application Object Specification.
21 Write-once value or
medium already written An attempt was made to write to a write-once medium (e.g. WORM drive,
PROM) that has already been written, or to modify a value that cannot be
changed once established.
22 Invalid Reply Received An invalid reply is received (e.g. reply service code does not match the request
service code, or reply message is shorter than the minimum expected reply
size). This status code can serve for other causes of invalid replies.
23-24 Reserved by CIP for future extensions
25 Key Failure in path The Key Segment that was included as the first segment in the path does not
match the destination module. The object specific status shall indicate which
part of the key check failed.
26 Path Size Invalid The size of the path which was sent with the Service Request is either not
large enough to allow the Request to be routed to an object or too much rout-
ing data was included.
27 Unexpected attribute in
list An attempt was made to set an attribute that is not able to be set at this time.
28 Invalid Member ID The Member ID specified in the request does not exist in the specified Class/
Instance/Attribute.
29 Member not settable A request to modify a non-modifiable member was received.
2A Group 2 only server
general failure This error code may only be reported by DeviceNet group 2 only servers with
4K or less code space and only in place of Service not supported, Attribute not
supported and Attribute not settable.
2B-CF --- Reserved by CIP for future extensions
D0-FF Reserved for Object
Class and service
errors
This range of error codes is to be used to indicate Object Class specific errors.
Use of this range should only be performed when none of the Error Codes pre-
sented in this table accurately reflect the error that was encountered.
General Status
Code (hex) Status Name Description of Status
389
CIP Message Communications Appendix D
Example of Additional Status in case that General Status Is 01 Hex.
(Status of Connection Manager Object)
General Status
(hex) Additional
Status (hex) Explanation
01 0100 Connection in Use or Duplicate Forward Open.
01 0103 Transport Class and Trigger combination not supported
01 0106 Ownership Conflict
01 0107 Connection not found at target application.
01 0108 Invalid Connection Type. Indicates a problem with either the Connection Type or Prior-
ity of the Connection.
01 0109 Invalid Connection Size
01 0110 Device not configured
01 0111 RPI not supported. May also indicate problem with connection time-out multiplier, or
production inhibit time.
01 0113 Connection Manager cannot support any more connections
01 0114 Either the Vendor Id or the Product Code in the key segment did not match the device
01 0115 Product Type in the key segment did not match the device
01 0116 Major or Minor Revision information in the key segment did not match the device
01 0117 Invalid Connection Point
01 0118 Invalid Configuration Format
01 0119 Connection request fails since there is no controlling connection currently open.
01 011A Target Application cannot support any more connections
01 011B RPI is smaller than the Production Inhibit Time.
01 0203 Connection cannot be closed since the connection has timed out
01 0204 Unconnected Send timed out waiting for a response.
01 0205 Parameter Error in Unconnected Send Service
01 0206 Message too large for Unconnected message service
01 0207 Unconnected acknowledge without reply
01 0301 No buffer memory available
01 0302 Network Bandwidth not available for data
01 0303 No Tag filters available
01 0304 Not Configured to send real-time data
01 0311 Port specified in Port Segment Not Available
01 0312 Link Address specified in Port Segment Not Available
01 0315 Invalid Segment Type or Segment Value in Path
01 0316 Path and Connection not equal in close
01 0317 Either Segment not present or Encoded Value in Network Segment is invalid.
01 0318 Link Address to Self Invalid
01 0319 Resources on Secondary Unavailable
01 031A Connection already established
01 031B Direct connection already established
01 031C Miscellaneous
01 031D Redundant connection mismatch
01 031F No connection resources exist for target path
01 0320-07FF Vendor specific
390
CIP Message Communications Appendix D
Priority/Time Ticks and Time Out Ticks
Format of the Priority/Time Tick
Time tick Base value (ms) Maximum time-out time (ms) that can be set
in the time out ticks
0000 hex 1 255
0001 hex 2 510
0010 hex 4 1,020
0011 hex 8 2,040
0100 hex 16 4,080
0101 hex 32 8,160
0110 hex 64 16,320
0111 hex 128 32,640
1000 hex 256 65,280
1001 hex 512 130,560
1010 hex 1,024 261,120
1011 hex 2,048 522,240
1100 hex 4,096 1,044,480
1101 hex 8,192 2,088,960
1110 hex 16,389 4,177,920
1111 hex 32,768 8,355,840
391
Appendix E
FINS Commands Addressed to EtherNet/IP Units
or Built-in EtherNet/IP Ports
RESET
Resets the EtherNet/IP Unit or built-in EtherNet/IP port.
Command Block
Response Block
Command code Function name Remarks
MRC SRC
04 03 RESET ---
05 01 CONTROLLER DATA READ ---
06 01 CONTROLLER STATUS READ ---
08 01 INTERNODE ECHO TEST ---
02 BROADCAST TEST RESULTS READ ---
03 BROADCAST DATA SEND ---
21 02 ERROR LOG READ ---
03 ERROR LOG CLEAR ---
27 20 PING ---
30 FINS/TCP CONNECTION REMOTE NODE
CHANGE REQUEST ---
31 FINS/TCP CONNECTION STATUS READ ---
50 IP ADDRESS TABLE WRITE ---
57 IP ADDRESS WRITE ---
60 IP ADDRESS TABLE READ ---
61 IP ROUTER TABLE READ ---
62 PROTOCOL STATUS READ ---
63 MEMORY STATUS READ ---
64 SOCKET STATUS READ ---
65 ADDRESS INFORMATION READ ---
67 IP ADDRESS READ ---
28 01 EXPLICIT MESSAGE SEND ---
10 CIP UCMM MESSAGE SEND ---
04 03
Command code
Response
code
04 03
Command
code
392
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Precautions
• No response will be returned if the command ends normally. A response will be returned only if an error
occurs.
• In some cases, send requests (SEND(192)/RECV(193) instructions) made from the PLC to the EtherNet/
IP Unit or built-in EtherNet/IP port just before execution of the RESET command may not be executed.
• Applications that use TCP/IP, such as FINS/TCP communications services, are closed immediately before
resetting.
Response Codes
CONTROLLER DATA READ
Reads the following data from the EtherNet/IP Unit or built-in EtherNet/IP port: Model number, version, IP
address, subnet mask, FINS UDP port number, mode settings, Ethernet address.
Command Block
Response Block
Parameters
Model number, Version (Response)
The model number and version of the EtherNet/IP Unit or built-in EtherNet/IP port are returned as ASCII char-
acters occupying 20 bytes each (i.e., 20 characters each). If all bytes are not used, the remaining bytes will be
all spaces (ASCII 20 Hex).
Example Model: CS1W-EIP21, CJ1W-EIP21, CJ2B-EIP21, or CJ2M-EIP21
Example Version: V2.00
By convention, the model number of the built-in EtherNet/IP port on a CJ2H-CPU@@-EIP CPU Unit is CJ2B-
EIP21.
By convention, the model number of the built-in EtherNet/IP port on a CJ2M-CPU3@ CPU Unit is CJ2M-EIP21.
IP Address, Subnet Mask (Response)
The IP address and subnet mask of the EtherNet/IP Unit or built-in EtherNet/IP port are returned as 4 bytes
each.
FINS UDP Port Number (Response)
The UDP port number of the EtherNet/IP Unit or built-in EtherNet/IP port for FINS is returned as 2 bytes.
Response code Description
1001 Command too large
05 01
Command code
05 01 20 byte 20 byte 4 byte
Subnet
mask
4 byte
FINS UDP
p
ort number Mode
settin
g
6 byte
Ethernet addressResponse
code
Command
code Model number Version IP address
393
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Mode Setting (Response)
The mode setting in the system setup is returned.
Broadcast Address Setting
Communications Partner IP Address Conversion Method Setting
FINS/UDP Port Number Setting
FINS/TCP Port Number Setting
Baud Rate Setting
SNTP Server Specification Method
Ethernet Address (Response)
The Ethernet address of the EtherNet/IP Unit or built-in EtherNet/IP port is returned.
Note This Ethernet address is listed on the label on the side of the EtherNet/IP Unit or (for a built-in EtherNet/
IP port), on the CPU Unit.
Bit 1: Broadcast setting
Bit 4: UDP port number setting for FINS
Bits 2 and 3: IP address conversion method
0 1 2 3 4 5 67 89 10 11 12 1314 15
Bit 5: TCP port number setting for FINS/TCP
Bit 8: Transmission speed (baud rate)
Bit 9: SNTP server s
p
ecification method
Bit 1 Meaning
0 Broadcast with host number set to all ones (4.3BSD specifications)
1 Broadcast with host number set to all zeroes (4.2BSD specifications)
Bit 3 Bit 2 Meaning
0 0 Automatic generation method (dynamic)
0 1 Automatic generation method (static)
1 0 IP address table reference method
1 1 Combined method (IP address table reference + automatic generation
(dynamic))
Bit 4 Meaning
0 Default (9600)
1 Unit Setup value
Bit 5 Meaning
0 Default (9600)
1 Unit Setup value
Bit 8 Meaning
0 Automatic detection
1Fixed
Bit 9 Meaning
0 IP address
1Host name
394
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Codes
CONTROLLER STATUS READ
Reads the controller status.
Command Block
Response Block
Parameters
Communications Status 3 (Response)
Ethernet Basic Setting Error
IP Address Table Error
Response code Description
0000 Normal end
1001 Command too large
06 01
Command cod
e
06 01 4 byte 4 byte
Total number
of
p
ackets sent
4 byte
Total number
of
send errors
4 byte
Total number
of
send collisions
4 byte
Response
code
Command
code
2 byte
Total number
of
p
ackets received
Total number
of
receive errors
Communications
status 3
Bit 3: IP address table error
0123 4 5 6 78910 11 12 13 1415
Bit 4: IP router table error
Bit 6: Routing table error
Bit 15: Non-volatile memory error
Bit 14: Address mismatch
Bit 2: EtherNet/IP basic setting error
Bit 9: EtherNet/IP advanced setting erro
r
Bit 10: BOOTP server error
Bit 11: SNTP server error
Bit 2 Meaning
0 No error
1 An error (such as an invalid IP address) was detected during the validity check of parameters related to the
TCP/IP Interface Object and Ether Link Object.
Bit 3 Meaning
0 No error
1 Error detected (More than 32 records, invalid IP address, or invalid FINS node address).
395
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
IP Router Table Error
Routing Table Error
Ethernet Advanced Setting Error
BOOTP Server Error
SNTP Server Error
Address Mismatch
Non-volatile Memory Error
Total Number of Packets Received (Response)
The total number of packets received by the EtherNet/IP Unit or built-in EtherNet/IP port is returned.
Total Number of Receive Errors (Response)
The total number of packet errors detected while the EtherNet/IP Unit or built-in EtherNet/IP port was receiving
is returned.
The following types of error are detected:
• Short packet errors
• Alignment errors
• CRC errors
• Frame length errors (received frame: 1,515 bytes or more)
• Communications controller overflow errors
Bit 3 Meaning
0 No error
1 Error detected (More than 8 records, or invalid IP address).
Bit 6 Meaning
0 No error
1 Error detected in routing table check.
Bit 9 Meaning
0 No error
1 An error was detected during the validity check of vendor-specific parameters for the TCP/IP Interface
Object and Ether Link Object.
Bit 10 Meaning
0 No error
1 Error detected. (A time-out occurred during communications with the BOOTP server).
Bit 10 Meaning
0 No error
1 Error detected. (The setting of the host specification (IP address or host name) of the SNTP server is not
correct, or communications with the SNTP server timed out.)
Bit 14 Meaning
0 No error
1 Error detected. (The address conversion method was set for automatic generation, but the last eight bits of
the local IP address does not match the local node address (FINS node address), or the host section other
than the last byte of the local IP address is non-zero.)
Bit 15 Meaning
0 No error
1 Error detected. (The non-volatile memory’s service life has expired, or the memory has failed).
396
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Total Number of Packets Sent (Response)
The total number of packets sent by the EtherNet/IP Unit or built-in EtherNet/IP port is returned.
Total Number of Errors Sent (Response)
The total number of packet errors detected while the EtherNet/IP Unit or built-in EtherNet/IP port was sending
is returned.
Total Number of Send Collisions (Response)
Returns the number of packets damaged by 16 collisions with data from other nodes during EtherNet/IP Unit or
built-in EtherNet/IP port transmissions.
Precautions
Counting of the total number of packets received, total number of receive errors, total number of packets sent,
total number of errors sent, and total number of send collisions is discontinued when the counted value
reaches the maximum value.
Response Codes
INTERNODE ECHO TEST
Performs an echoback test (internode communications test) between specified nodes.
Command Block
Response Block
Parameters
Test Data (Command, Response)
This command specifies the data to be sent to the specified nodes. Up to 1,998 bytes can be specified. The
response sends back data identical to the data specified in the command. An abnormality is assumed if the
data returned in the response differs from the test data sent.
Precautions
• The test destination node is the destination node specified in the CMND(194) instruction operands.
• Always specify the unit address of the EtherNet/IP Unit or built-in EtherNet/IP port in the CMND(194)
instruction.
Response code Description
0000 Normal end
1001 Command too large
08 01
Command
code
1,998 bytes max.
Test data
08 01
Response
code
Command
code
1,998 bytes max.
Test data
397
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Codes
BROADCAST TEST RESULTS READ
Reads the results (number of times data received) of the broadcast test.
Command Block
Response Block
Parameters
Times Received (Response)
The number of times the data has been received normally during the broadcast send test is returned as a
hexadecimal number. The number of times received is cleared each time the result is read.
Response Codes
BROADCAST DATA SEND
Sends test data simultaneously to all nodes on the network.
Command Block
Parameters
Test Data (Command)
This command specifies the data to be sent to the specified nodes. Up to 1,460 bytes can be specified.
Response code Description
0000 Normal end
1001 Command too large
1002 Command too small (No test data)
08 02
Command
code
08 02
Times
received
Response
code
Command
code
Response code Description
0000 Normal end
1001 Command too large
08 03
Command
code
1,460 bytes max.
Test data
398
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Precautions
• No response is made to this command.
• When using this command, set the FINS header parameters (or the control data for the CMND(194)
instruction) as follows:
Destination node address: FF (broadcast data)
Destination unit address: FE (EtherNet/IP Unit or built-in EtherNet/IP port)
Response/no response flag: 1 (no response)
ERROR LOG READ
Reads the error log.
Command Block
Response Block
Parameters
Beginning Record Number (Command)
The first record to be read. The first record number can be specified in the range between 0000 and 003F (0 to
63 decimal) where 0000 is the oldest record.
Number of Records (Command, Response)
The number of records to read is specified between 0001 and 0040 (1 to 64 decimal) in the command. The
response returns the actual number of records read.
Maximum Number of Stored Records (Response)
Indicates the maximum number of records that can be stored in the error log. The maximum number of error
log records depends on the model of CPU Unit or CPU Bus Unit being used. In an EtherNet/IP Unit or built-in
EtherNet/IP port, the maximum number of stored records is fixed at 40 (64 decimal).
Number of Stored Records (Response)
The number of records stored at the time the command is executed is returned.
Error Log Data (Response)
The specified number of error log records from the beginning record number is returned sequentially. The total
number of bytes in the error log is calculated as the number of records x 10 bytes/record. Each error log record
thus comprises 10 bytes, configured as follows:
21 02
Beginning
record
number
Number
of
records
Command
code
21 02
Maximum
number
of stored
records
Number
of stored
records
Number
of
records
10 bytes 10 bytes
Error log dataResponse
code
Command
code Error log data
399
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Error Code, Detailed Information
Details of the error stored in the record. Refer to 14-4-4 Error Log Error Codes for details.
Minute, Second, Day, Hour, Year, Month
Indicate the time at which the error stored in the record occurred.
Precautions
• If the error log contains fewer records than the number specified in the number of records parameter, all
records stored in the error log at the time the command is executed will be returned and the command exe-
cuted will end normally.
Response Codes
ERROR LOG CLEAR
Clears the error log for the EtherNet/IP Unit or built-in EtherNet/IP ports, and resets the number of stored
records to 0.
Command Block
Response Block
Response Codes
PING
Performs processing equivalent to a UNIX computer’s PING command (see below).
Error code Detailed
information
1st byte 10th byte
Minutes Second Day Hour Year Month
Response code Description
0000 Normal end
1001 Command too large
1002 Command too small
1103 Beginning record number is out of range
110C The number of read records is 0.
21 03
Command cod
e
21 03
Response
code
Command
code
Response code Description
0000 Normal end
1001 Command too large
400
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Command Block
Response Block
Parameters
Destination IP Address (Command)
The IP address (in hexadecimal) of the destination node for the PING command echo request packet.
Timeout Value (Command)
The wait time for the echo reply packet. The value is set in seconds. The timeout time is set at 20 seconds if the
value is specified as 0. If the echo reply packet is not received within the set time limit, the code for a timeout
error will be set as the results storage response code.
Remarks
PING Command
The PING command runs the echoback test using the ICMP protocol. When the PING command is executed,
an echo request packet is sent to the remote node ICMP. Correct communications are confirmed when the
returned response packet is received normally. The echo reply packet is automatically returned by the remote
node ICMP.
Response Codes
FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST
Requests a remote node change for the FINS/TCP connection.
The default destination IP address in a connection in which the EtherNet/IP Unit or built-in EtherNet/IP port is
used as a client is the destination IP address set under the FINS/TCP Tab Page in the Unit Setup. By sending
this command to the EtherNet/IP Unit or built-in EtherNet/IP port, the destination IP address for the specified
connection can be changed to another IP address.
Remote node changes can be made only for connection numbers specified as FINS/TCP clients in the Unit
Setup.
Destination IP address Timeout
value
Command
code
27 20
Response
code
Command
code
27 20
Response code Description
0000 Normal end (echo reply received from the remote node)
0205 Timeout error
1001 Command too large
1002 Command too small
1100 Zero destination address
220F PING command currently being executed
2211 High traffic at Unit; cannot execute service.
401
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Command Block
Response Block
Parameters
FINS/TCP Connection No. (Command)
Specifies, in two bytes, the FINS/TCP connection number (1 to 16) for which the change is to be made.
Remote IP Address (Command)
Specifies the remote node’s IP address (must be non-zero) in hexadecimal.
Remote Port Number (Command)
Specifies the remote TCP port number (must be non-zero) with this command.
Response Codes
FINS/TCP CONNECTION STATUS READ
Reads the FINS/TCP connection status.
Command Block
27 30
FINS/TCP
connection No.
Command
code Remote IP
address Remote TCP
port number
27 30
Response
code
Command
code
Response code Description
0000 Normal end
0105 Node address setting error
Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 Connection number not set from 1 to 16
Remote IP address set to 0
Remote TCP port number set to 0
2230 Connection already established with specified remote node
2231 Specified connection number not set as FINS/TCP client in
Unit Setup
2232 Remote node change processing for specified connection
number aborted because change request received during pro-
cessing
27 31
FINS/TCP
connection No.
Command
code
402
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Block
Parameters
FINS/TCP Connection No. (Command, Response)
Command: Specifies, in two bytes, the FINS/TCP connection number (1 to 16) for which the status is to be
read.
Response: Specifies the FINS/TCP connection number (1 to 16) for which the status was read.
Connection Service (Response)
Specifies the service that is being used for the FINS/TCP connection as a number.
0003: FINS/TCP server
0004: FINS/TCP client
Local IP Address (Response)
Specifies the IP address for the local node in hexadecimal.
Local TCP Port Number (Response)
Specifies the TCP port number for the local node.
Remote IP Address (Response)
Specifies the IP address for the remote node in hexadecimal.
Remote TCP Port Number (Response)
Specifies the TCP port number for the remote node.
TCP Transitions (Response)
Specifies the TCP connection status using the following numbers.
For details on TCP status changes, refer to Appendix C TCP Status Transitions.
Connection
service TCP transition
27 31
Command
code Local TCP
port number Remote IP
address Remote TCP
port number
Response
code Local IP addressFINS/TCP
connection
No.
Number Status Meaning
00000000 CLOSED Connection closed.
00000001 LISTEN Waiting for connection.
00000002 SYN SENT SYN sent in active status.
00000003 SYN RECEIVED SYN received and sent.
00000004 ESTABLISHED Already established.
00000005 CLOSE WAIT FIN received and waiting for completion.
00000006 FIN WAIT 1 Completed and FIN sent.
00000007 CLOSING Completed and exchanged FIN. Awaiting ACK.
00000008 LAST ACK FIN sent and completed. Awaiting ACK.
00000009 FIN WAIT 2 Completed and ACK received. Awaiting FIN.
0000000A TIME WAIT After closing, pauses twice the maximum seg-
ment life (2MSL).
403
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Codes
IP ADDRESS TABLE WRITE
Writes the IP address table.
Command Block
Response Block
Parameters
Number of Records (Command)
The number of records to write is specified in hexadecimal between 0000 and 0020 (0 to 32 decimal) in the
command. If this value is set to 0, the IP address table will be cleared so that no records are registered.
IP Address Table Records (Command)
Specify the IP address table records. The number of records specified must be provided. The total number of
bytes in the IP address table records is calculated as the number of records × 6 bytes/record. The configuration
of the 6 bytes of data in each record is as shown in the following diagram.
FINS Node Address
Node address for communications via the FINS command (hexadecimal).
IP Address
IP address used by TCP/IP protocol (hexadecimal).
Precautions
• The registered IP address table will not be effective until the PLC or EtherNet/IP Unit or built-in EtherNet/IP
port is restarted.
Response code Description
0000 Normal end
0105 Node address setting error
Local IP address setting error
0302 CPU Unit error; execution not possible.
1001 Command too large
1002 Command too small
1100 Connection number not set from 1 to 16
Number
of records IP address
table records
Command
code
27 50
IP address
table records
6 bytes 6 bytes
Command
code Response
code
27 50
FINS node
number
1
00
IP address
6 bytes
404
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
• An error response will be returned if the IP address conversion method in the system mode settings is set
for automatic generation on the FINS/UDP Tab Page of the Unit.
Response Codes
IP ADDRESS WRITE
Write the local IP address and the subnet mask in the CPU Bus Unit System Setup.
Command Block
Response Block
Parameters
IP Address (Command)
Specify the local IP address of the EtherNet/IP Unit or built-in EtherNet/IP port using 4 pairs of 2-digit hexadec-
imal numbers in the range 00.00.00.00 to FF.FF.FF.FF (0.0.0.0 to 255.255.255.255 decimal). Specify 0.0.0.0 to
enable the local IP address set in the allocated DM Area words.
Example: 150.31.2.83
Subnet Mask (Command)
Specify the local IP address of the EtherNet/IP Unit or built-in EtherNet/IP port using 4 pairs of hexadecimal
numbers in the range 00.00.00.00 to FF.FF.FF.FF (0.0.0.0. to 255.255.255.255 decimal).
Example: 255.255.255.255
Response code Description
0000 Normal end (echo reply received from the remote node)
1001 Command too large
1002 Command too small
1003 The number of records specified does not match the sent data
length.
110C The number of records is not between 0 and 32.
The FINS node address is not between 1 and 126
The IP address is 0.
2307 IP address conversion method is set for automatic generation.
27 57
Subnet maskIP addressCommand
code
27 57
Command
code Response
code
96 531F 02
FF 00FF FF
405
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Codes
Precautions
• The local IP address and subnet mask set by this command are written to the CPU Bus Unit System Setup
for the EtherNet/IP Unit or built-in EtherNet/IP port.
• The new local IP address and subnet mask settings will become effective when the PLC or EtherNet/IP
Unit or built-in EtherNet/IP port is restarted.
IP ADDRESS TABLE READ
Reads the IP address table.
Command Block
Response Block
Parameters
Number of Records (Command, Response)
The number of records to read is specified between 0000 and 0020 (0 to 32 decimal) in the command. If this
value is set to 0, the number of stored records is returned but the IP address table records are not returned.
The response returns the actual number of records read.
Maximum Number of Stored Records (Response)
The maximum number of records that can be stored in the IP address table is returned. The maximum number
of stored records is fixed at 0020 (32 records).
Number of Stored Records (Response)
The number of IP address table records stored at the time the command is executed is returned as a hexadec-
imal number.
IP Address Table Records (Response)
The number of IP address table records specified in the number of records parameter is returned. The total
number of bytes in the IP address table records is calculated as the number of records × 6 bytes/record. The
configuration of the 6 bytes of data in each record is as shown in the following diagram.
Response code Description
0000 Normal end
1001 Command too large
1002 Command too small
Number of
records
Command
code
27 60
Maximum
number
of stored
records
Number
of stored
records
Number
of records IP address
table records
Response
code
Command
code
27 60
IP address
table records
6 bytes 6 bytes
406
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
FINS Node Address
Node address for communications via the FINS command (in hexadecimal).
IP Address
IP number used by TCP/IP protocol (in hexadecimal).
Precautions
• If the IP address table contains fewer records than the number specified in the number of records parame-
ter, all the records contained in the IP address table when the command is executed will be returned and
the command execution will end normally.
• An error response will be returned if the IP address conversion method in the system mode settings is set
to the automatic generation method on the FINS/UDP Tab Page of the Unit.
Response Codes
IP ROUTER TABLE READ
Reads the IP router table.
Command Block
Response Block
Parameters
Number of Records (Command, Response)
The number of records to read is specified between 0000 and 0008 (0 to 8 decimal) in the command. If this
value is set to 0, the number of stored records will be returned but the IP router table records will not be
returned. The response returns the actual number of records read.
FINS node
number
1
00
IP address
6 byte
s
Response code Description
0000 Normal end
1001 Command too large
1002 Command too small
2307 IP address conversion method is set to the automatic genera-
tion method.
Number
of records
Command
code
27 61
Maximum
number
of stored
records
Number
of stored
records
Number
of records
IP router
table records
Response
code
Command
code
27 61
IP router
table records
8 bytes 8 bytes
407
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Maximum Number of Stored Records (Response)
The maximum number of records that can be stored in the IP router table is returned. The maximum number of
stored records is fixed at 0008 (8 records).
Number of Stored Records (Response)
The number of IP router table records stored at the time the command is executed is returned in hexadecimal.
IP Router table Records (Response)
The number of IP router table records specified in the number of records parameter is returned. The total num-
ber of bytes in the IP router table records is calculated as the number of records × 8 bytes/record. The configu-
ration of the 8 bytes of data in each record is shown below.
IP Network Address
The network ID from the IP address in hexadecimal. The network ID part corresponding to the address class
(determined by the leftmost 3 bits) set here, is enabled.
Router IP Address
The IP address (in hexadecimal) of a router connected to a network specified with IP addresses.
Precautions
If the IP router table contains fewer records than the number specified in the number of records parameter, all
the records contained in the IP router table when the command is executed will be returned and the command
execution will end normally.
Response Codes
PROTOCOL STATUS READ
Reads the protocol status or the EtherNet/IP Unit or built-in EtherNet/IP port.
Command Block
Response Block
IP Network address
(Network ID)
Router IP address
18 bytes
Response code Description
0000 Normal end
1001 Command too large
1002 Command too small
27 62
Command
code
27 62
IP status ICMP status TCP status UDP statusResponse
code
Command
code
48 bytes 184 bytes 184 bytes 12 bytes
408
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Parameters
IP Status (Response)
Twelve types of IP status information occupying 4 bytes each are returned in the following sequence. Each
value is returned as an 8-digit hexadecimal value.
1. Total number of IP packets received.
2. The number of IP packets discarded due to an error with the checksum in the packet header.
3. The number of IP packets discarded because the received packet was larger than the overall packet length
value in the packet header.
4. The number of IP packets discarded because the minimum size of the IP header data could not be stored
in the first short buffer (See note.) when an attempt was made to store the packet.
5. The number of packets discarded for one of the following reasons:
• The IP header length value in the IP header was smaller than the smallest size of the IP header.
• The size of the first short buffer (See note.) was smaller than the IP header length value in the IP header
when storing the packet.
6. The number of IP packets discarded because the IP header length was larger than the overall packet length
value in the packet header.
7. The number of fragmented packets received.
8. The number of received fragmented IP packets discarded because a queue for reassembly could not be
secured.
9. The number of fragmented IP packets discarded because they could not be reassembled within 12 seconds
after being received.
10. Always 0.
11. The number of packets addressed to other networks that have been discarded.
12. Always 0.
Note Refer to MEMORY STATUS READ on page 411 for details on the short buffer.
ICMP Status (Response)
Ten types (46 items) of ICMP status information occupying 4 bytes each are returned in the following
sequence. Each value is returned as an 8-digit hexadecimal value.
1. The number of times the ICMP error routine was called. The ICMP error routine uses ICMP packets to inform
the source about errors. The routine is called when an illegal packet is received (error in IP option processing
or error in relay processing) or if the object port does not exist when using UDP.
2. Always 0.
3. Always 0.
4. Total number of outputs of each packet type during ICMP output. The 19 statistical values are returned in
the order shown below. Contents are defined for 13 types only; all other types contain 0. Only #0, #3, #14,
#16, and #18 are counted by the EtherNet/IP Unit or built-in EtherNet/IP port.
Type number Description
#0 Echo reply
#1, #2 Undefined, always 0
#3 Destination unreachable
#4 Source quench
#5 Routing redirect
#0 #1 #2 #3 #4 #5 #15 #16 #17 #18
4 bytes
409
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
5. The number of received ICMP packets discarded because the type-indication code was out of range.
6. The number of received ICMP packets discarded because the overall packet length value in the packet
header was smaller than the minimum ICMP packet length.
7. The number of received ICMP packets discarded because of an incorrect checksum value in the packet
header.
8. The number of received ICMP packets discarded because the ICMP header length value in the packet head-
er did not match the lengths of individual header types.
9. The number of responses returned to received ICMP packets requiring a response.
10. Total number of inputs of each packet type during ICMP input. The 19 statistical values are returned in the
order shown below. Contents are defined for 13 types only; all other types contain 0.
TCP Status (Response)
Three types (46 items) of TCP status information occupying 4 bytes each are returned in the following
sequence. Each value is returned as an 8-digit hexadecimal value.
1) Connection Information (60 Bytes)
Fifteen items are returned in the following sequence:
#6, #7 Undefined, always 0
#8 Echo
#9, #10 Undefined, always 0
#11 Time exceeded
#12 Parameter problem
#13 Time stamp
#14 Time stamp reply
#15 Information request
#16 Information request reply
#17 Address mask request
#18 Address mask reply
Type number Description
Type number Description
#0 Echo reply
#1, #2 Undefined, always 0
#3 Destination unreachable
#4 Source quench
#5 Routing redirect
#6, #7 Undefined, always 0
#8 Echo
#9, #10 Undefined, always 0
#11 Time exceeded
#12 Parameter problem
#13 Time stamp
#14 Time stamp reply
#15 Information request
#16 Information request reply
#17 Address mask request
#18 Address mask reply
#0 #1 #2 #3 #4 #5 #15 #16 #17 #18
4 b
y
tes
410
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
1. The number of times active connections were correctly established.
2. The number of times a SYN packet was received while waiting to establish a passive connection.
3. The number of times active or passive connections were correctly established.
4. The number of times an established connection was cut off.
5. The number of times the connection wait status was cut off.
6. The number of times protocol control blocks or other actively allocated structures were released.
7. The number of segments for the round-trip time (time from segment transmission to ACK).
8. The number of times the round-trip time was changed.
9. The number of times a delayed acknowledgement (ACK) was sent. If the order of the received segments is
reversed, ACK is sent with a packet of data separate from ACK (response to input data, etc.) or is immedi-
ately sent with the ACK for other data.
10. The number of times the connection was cut off because no ACK was returned after several resend at-
tempts.
11. The number of times no ACK was returned within the resend timer set time. (The resend timer sets the max-
imum time limit between the data being output and ACK being returned.)
12. The number of times no window advertisement is received within the time set on the duration timer. (The
duration timer sets the maximum time limit for a window advertisement to be received if the transmission
window is smaller than necessary and the resend timer is not set. If no window advertisement is received
within the time limit, the number of segments permitted by the transmission window are sent. If the trans-
mission window is set to 0, a window probe (1 octet of data) is sent before the timer restarts.)
13. The number of times no segment was sent or received within the time set on the hold timer.
14. The number of times the hold packet is resent. (Always 0.)
15. The number of times the hold packet is sent without response before the connection is cut off.
2) Send Information (40 Bytes)
Ten information items are returned in the following sequence:
1. The total number of packets sent.
2. The number of data packets sent.
3. The number of data bytes sent.
4. The number of data packets resent.
5. The number of data bytes resent.
6. The number of ACK packets sent.
7. The number of window probes (1 octet of data) sent.
8. The number of emergency data packets sent. (Always 0.)
9. The number of window advertisement packets sent.
10. The number of control packets (SYN, FIN, RST) sent.
3) Receive Information (84 Bytes)
Twenty-one information items are returned in the following sequence:
1. The total number of packets received.
2. The number of packets received continuously.
3. The number of bytes received continuously.
4. The number of received packets discarded due to an incorrect checksum.
5. The number of packets discarded because the TCP header was smaller than the minimum size for a TCP
header or was larger than the IP packet.
6. The number of packets discarded because the TCP header and IP header could not be stored in the first
short buffer.
7. The number of resent packets received.
411
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
8. The number of bytes in the resend packets.
9. The number of duplicated resend packets received.
10. The number of bytes in the duplicated resend packets received.
11. The number of out-of-range data packets received. (Always 0.)
12. The number of bytes in the out-of-range data packets received. (Always 0.)
13. The number of packets where the data was larger than the window.
14. The number of bytes in the packets where the data was larger than the window.
15. The number of packets received after closing.
16. The number of window probe packets received.
17. The number of resent ACK packets received.
18. The number of ACK packets received with no data set.
19. The number of ACK packets received.
20. The number of ACK packets received for received transmission acknowledgements (ACK).
21. The number of window advertisement packets received.
UDP Status (Response)
Three items of UDP information occupying 4 bytes each are returned in the following sequence. Each value is
returned as an 8-digit hexadecimal value.
1. The number of packets discarded because the size of the first short buffer was smaller than the minimum
size (28) of the IP header and UDP header when the packet was stored.
2. The number of packets discarded due to an incorrect checksum in the UDP header.
3. The number of packets discarded because the IP overall length in the IP header was shorter than the UDP
overall length in the UDP header.
Precautions
All the above values are set to 0 if network operation stops due to incorrect settings in the system setup.
Counting will be stopped when a count reaches the maximum value. The maximum values are as follows:
IP, ICMP, or UDP status:7FFFFFFF (2,147,483,647 decimal)
TC status: FFFFFFFF (4,294,967,295 decimal)
Response Codes
MEMORY STATUS READ
Reads the status of the network memory for the EtherNet/IP Unit or built-in EtherNet/IP port. The network
memory contains 2,991 bytes that are used as required as for communications buffers for communications ser-
vicing. The network memory consists of 23,928 short buffers (128 bytes each) and 64 long buffers (1,024 bytes
each).
Command Block
Response code Description
0000 Normal end
1001 Command too large
27 63
Command
code
412
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Response Block
Parameters
Memory Status (Response)
A total of 23 data items in six areas are returned in the following order. Each item consists of 4 bytes.
1) Short Buffer Application: Two items are returned (8 bytes).
1. The number of short buffers currently being used.
2. The number of short buffers in the system (fixed at 23,928 decimal).
2) Short Buffer Application by Type: Thirteen items are returned (52 bytes).
1. The number of short buffers used for storing communications data
2. The number of short buffers used for protocol headers (TCP, UDP, IP, ICMP, ARP)
3. The number of short buffers used in socket structures
4. The number of short buffers used as protocol control blocks
5. The number of short buffers used for routing tables
6. Not used (always 0)
7. Not used (always 0)
8. The number of short buffers used for IP fragment re-assembly queue headers
9. The number of short buffers used for storing socket addresses
10. Not used (always 0)
11. The number of short buffers used for storing socket options
12. The number of short buffers used for storing access rights
13. The number of short buffers used for storing interface addresses
3) Long Buffer Application: Two items are returned (8 bytes).
1. The number of long buffers currently being used.
2. The number of long buffers in the system (fixed at 64 decimal).
4) Not Used: Always 0. (4 bytes)
5) Network Memory Application: Two items are returned (8 bytes).
1. The number of bytes used (in K bytes)
2. The percentage used
6) Memory Exhaustion Log (12 bytes)
Counts for the following values indicate a high load on the EtherNet/IP Unit or built-in EtherNet/IP port. These
high loads may be caused by problems in communications, particularly FINS communications and UDP sock-
ets. If these values are consistently high, check your applications.
1. The number of times an attempt was made to secure a short buffer without WAIT when there were no short
buffers available.
2. The number of times an attempt was made to secure a short buffer with WAIT when there were no short
buffers available.
3. The number of times an attempt was made to release and secure a short buffer already being used by an-
other socket when there were no short buffers available.
Memory statusResponse
code
Command
code
27 63 92 bytes
413
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Precautions
All the above values are set to 0 if Ethernet communications functions are stopped due to improper settings in
the system setup.
These values are cleared when the EtherNet/IP Unit or built-in EtherNet/IP port is started or reset. Values will
be counted only until the maximum values are reached.
Response Codes
SOCKET STATUS READ
Reads the network socket status of the EtherNet/IP Unit or built-in EtherNet/IP port.
Command Block
Response Block
Parameters
Socket Status (Response)
Returns eight types of information in records of 32 bytes each. A maximum of 62 records can be returned. The
format of each record is shown below.
Protocol (4 bytes)
The protocol used for the socket is returned as a number.
00 00 00 06: TCP; 00 00 00 11: UDP
Receive Queue (4 bytes)
The number of bytes in the reception queue.
Send Queue (4 bytes)
The number of bytes in the send queue.
Local IP Address (4 bytes)
The local IP address allocated to the socket.
Local Port Number (4 bytes)
The local port number allocated to the socket.
Remote IP Address (4 bytes)
The remote IP address allocated to the socket.
Response code Description
0000 Normal end
1001 Command too large
27 64
Command
code
27 64
Socket statusResponse
code
Command
code
32 bytes 32 bytes
Socket status
414
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Remote Port Number (4 bytes)
The remote port number allocated to the socket.
TCP Transitions (4 bytes)
The TCP connection status is returned as one of the numbers shown in the following table. Refer to Appendix
C TCP Status Transitions for a diagram of transitions.
Precautions
All the above values are set to 0 if Ethernet communications functions are stopped due to improper settings in
the system setup.
Response Codes
ADDRESS INFORMATION READ
Reads FINS node addresses and IP addresses
Command Block
Response Block
Parameters
Number of Addresses (Response)
Returns the number of pairs of FINS node addresses and IP addresses. With the EtherNet/IP Unit or built-in
EtherNet/IP port, this value is always 0001 (1 decimal).
Number Stage Status
00 00 00 00 CLOSED Closed.
00 00 00 01 LISTEN Waiting for connection.
00 00 00 02 SYN SENT SYN sent in active status.
00 00 00 03 SYN RECEIVED SYN received and sent.
00 00 00 04 ESTABLISHED Already established.
00 00 00 05 CLOSE WAIT Received FIN, waiting to close.
00 00 00 06 FIN WAIT 1 Completed and FIN sent.
00 00 00 07 CLOSING Completed and exchanged FIN. Awaiting ACK.
00 00 00 08 LAST ACK FIN sent and completed. Awaiting ACK.
00 00 00 09 FIN WAIT 2 Close completed and ACK received. Awaiting FIN.
00 00 00 0A TIME WAIT After closing, pauses twice the maximum segment life (2MSL).
Response code Description
0000 Normal end
1001 Command too large
27 65
Command
code
27 65
Number
of addresses Address
information
Response
code
Command
code
6 bytes
415
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Address Information
Returns the FINS node addresses and IP addresses. Each pair requires 6 bytes and has the following configu-
ration.
FINS Node Address
Node address set in the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal).
IP Address
IP address set in the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal).
Response Codes
IP ADDRESS READ
Reads the local IP address and subnet mask in the CPU Bus Unit System Setup and the FINS node address.
The values read with this command, however, are not necessarily the settings actually used for operation. The
settings that are actually used for operation can be confirmed using CONTROLLER DATA READ (page 392)
and ADDRESS INFORMATION READ (page 414).
This command is supported for CJ-series EtherNet/IP Units only.
Command Block
Response Block
Parameters
Number of Addresses (Response)
The number of sets of FINS node addresses, IP addresses, and subnet masks being returned. The EtherNet/
IP Unit or built-in EtherNet/IP port is always 0001 (1 decimal).
FINS Node Address (Response)
Node address set on the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal).
FINS node
number
1
00
IP address
6 bytes
Response code Description
0000 Normal end
1001 Command too large
27 67
Command
code
Number of
addresses
Response
code
Command
code FINS
node number
27 67 00
IP address Subnet mask
416
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
IP Address (Response)
The local IP address set in the CPU Bus Unit System Setup for the EtherNet/IP Unit or built-in EtherNet/IP port
is returned in order starting from the leftmost bytes in hexadecimal. If the local IP address set in the allocated
words in the DM Area is enabled, 0.0.0.0 is returned.
Subnet Mask (Response)
The subnet mask set in the CPU Bus Unit System Setup for the EtherNet/IP Unit or built-in EtherNet/IP port is
returned in order starting from the leftmost bytes in hexadecimal.
Response Codes
EXPLICIT MESSAGE SEND
Sends a explicit request message to the specified object, and receives a response.
The rightmost 8 bits of the remote (destination) IP address are used as the remote MAC ID, and the remote IP
address is the network ID of the local IP address + the rightmost 8 bits of the remote IP address.
Command Block
Response Block
Response Codes
Response code Description
0000 Normal end
1001 Command too large
28 01
Command
code Class ID Instance ID Service Data
Destination node address
Service Code
468 bytes max.
28 01
Command
code End
code Number of
bytes received Service Data
Destination node address
(
remote node
)
Service Code
498 bytes max.
00 00
Response code Description
0000 Normal end
0101 The local node’s network has not started up.
0105 Local node setting error (A BOOTP errors occurs, and the IP
address is undetermined.)
0106 Duplicate address error
0201 The remote node’s network has not started up.
0204 Remote node busy, cannot send.
0205 No response returned from remote node. Monitoring timer
timed out.
1001 Command length exceeds maximum command length.
1002 Command length is less than minimum command length.
1004 Command block format does not match.
1005 Header error
417
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Description
For details, refer to EXPLICIT MESSAGE SEND (28 01) on page 241 in 9-1-1 Sending Explicit Messages
Using CMND(490).
CIP UCMM MESSAGE SEND
Sends a message in the CIP message (UCMM) format.
Command Block
Response Block
Response Codes
110B Response length exceeds maximum response length.
2211 Unit is busy.
Response code Description
Service code
Request bus size
(variable length) Request data
(variable length)
Request bus size
2810 hex
Command
code Transport
ID Message monitoring
timer
502 bytes max.
Service code (response)
Service response data
(variable length)
Reserved
Reserved
General status
2810 hex
00
hex 00
hex 00
hex
Command
code End
code Transport
ID Number of
bytes received
0000 hex
502 bytes max.
Response code Description
0000 Normal end
0101 The local node’s network has not started up.
0106 Duplicate address error
0201 The remote node’s network has not started up.
0204 Remote node busy, cannot send.
0205 No response returned from remote node. Monitoring timer timed out.
1001 Command length exceeds maximum command length.
1002 Command length is less than minimum command length.
1004 Command block format does not match.
418
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E
Description
For details, refer to CIP UCMM MESSAGE SEND (28 10) on page 236 in 9-1-1 Sending Explicit Messages
Using CMND(490).
1005 Header error
110B Response length exceeds maximum response length.
2211 Unit is busy.
Response code Description
419
Appendix F
EDS File Management
This section explains the EDS file management functions used in the Network Configurator.
Installing EDS Files
Note Using Windows Vista or Windows 7
Is recommended that you start the Network Configurator from Run as administrator when you install an
EDS file in the Network Configurator. If the EDS file is installed on a Network Configurator that is started
in any other way, Windows security user management will cause the installed EDS file to not be recog-
nized when you log in using a different user account. You can run the Network Configurator as the
administrator by using the following procedure.
1. Select the Network Configurator from the Start Menu, and then right-click.
2. Select Run as administrator from the pop-up menu that is displayed.
EDS File - Install
The Network Configurator can support new devices if the proper EDS files are installed.
To install the EDS file, use the following procedure.
1. Select EDS File and Install.
The following window will be displayed.
2. The device information will be displayed on the bottom of the window when the EDS file is selected.
420
EDS File Management Appendix F
3. Select the EDS file to be installed and click the Open Button.
Next, select the icon file (*.ico), and the EDS file will be added to the Hardware List.
If the EDS file already exists, the new EDS file will overwrite the previous one.
If the hardware versions are different, an EDS file will be added to the Hardware List for each version.
Creating EDS Files
EDS File - Create
The EDS files are required by the Network Configurator in order to create a network configuration. To create an
EDS file, use the following procedure.
1. Select EDS File - Create.
2. Set the device information and I/O information.
The device information can be obtained from the device on the network if the network is online.
3. The device can be added to the Hardware List as a new device, just like installing an EDS file.
Note Device parameters cannot be set with the Network Configurator’s EDS file creation function. Obtain a
proper EDS file from the manufacturer of the device to make device parameter settings for the device.
Deleting EDS Files
EDS File - Delete
To delete an EDS file, use the following procedure.
1. Select the device from the Hardware List.
2. Select EDS File - Delete.
The following confirmation window will be displayed.
3. Click the Yes Button.
The selected device will be deleted from the Hardware List together with the EDS file.
Saving EDS Files
EDS File - Save
To save the EDS file, use the following procedure.
1. Select the device from the Hardware List.
2. Select EDS file - Save As.
The following window will be displayed to specify the name of the folder where the EDS file will be saved
and the name of the EDS file.
421
EDS File Management Appendix F
3. Input the folder and file names and click the Save Button The EDS file will be saved.
Searching EDS Files
EDS File - Search
To search the devices (EDS files) displayed in the Hardware List, use the following procedure.
1. Select EDS file - Find.
The following window will be displayed.
2. Input the character string and click the Find Next Button.
3. When there is a matching device found, the cursor will move to that position.
4. To quit the search operation, click the Cancel Button.
Note (1) The device will be found if it is located below the present cursor position.
(2) To search all the devices, select Hardware in the Hardware List before performing the search pro-
cedure.
Displaying EDS File Properties
EDS File - Property
To display the properties of the EDS file, use the following procedure.
1. Select the desired hardware (device) from the Hardware List.
422
EDS File Management Appendix F
2. Select EDS File - Property.
The following window will be displayed.
The time and date that the EDS file was created will be displayed, along with the device information.
423
Appendix G
Precautions for Using Windows XP, Vista, or
Windows 7
Changing Windows Firewall Settings
Better firewall security for Windows XP (SP2 or higher), Windows Vista, and Windows 7 has increased the
restrictions for data communications on Ethernet ports. When using an EtherNet/IP connection*1 to one of the
following PLCs from an Ethernet port on a computer, you must change the settings of the Windows Firewall to
enable using CX-Programmer or Network Configurator communications.
Applicable PLCs:
• CJ2H-CPU@@-EIP/CJ2M-CPU3@
•CS1W/CJ1W-EIP@@
*1 CX-Programmer
• An EtherNet/IP connection includes the following cases:
• An online connection with the network type set to EtherNet/IP
• An automatic online connection to a PLC on an EtherNet/IP network when Auto Online - EtherNet/IP
Node Online is selected from the PLC Menu
Network Configurator
• A connection made by selecting Option - Select Interface - Ethernet I/F
Note Windows Firewall is mainly designed to prevent inappropriate access from external devices (e.g., via the
Internet). The changes to the Windows Firewall settings described in this document enable EtherNet/IP
connections to be used by the CX-Programmer. If the same computer is being used on a company net-
work or other network, confirm that the changes will not create security problems before proceeding with
the changes. The changes described in this document are required only when you connect using Ether-
Net/IP through an Ethernet port. No changes are necessary if you are connecting through any other
port, such as a USB port.
Changing Windows Firewall Settings
Windows XP
1. When you attempt to connect the CX-Programmer or Network Configurator to a PLC on an EtherNet/IP net-
work through an Ethernet port, the Windows Security Alert Dialog Box will be displayed.
2. Click the Unblock Button.
An EtherNet/IP connection will be accepted from CX-Programmer or Network Configurator and EtherNet/
IP connections will be enabled in the future as well.
Windows Vista or Windows 7
Use the following procedure to change the settings before attempting to connect from the CX-Programmer or
Network Configurator.
424
Precautions for Using Windows XP, Vista, or Windows 7 Appendix G
The User Account Control Dialog Box may be displayed during this procedure. If it appears, click the Continue
Button and continue with the procedure.
1. Select Control Panel from the Windows Start Menu and change the display to Classic View.
2. Open the Administrative Tools and select Windows Firewall with Advanced Security from the dialog box that
is displayed.
3. Select Inbound Rules under Windows Firewall with Advanced Security on Local Computer on the left side
of the Windows Firewall with Advanced Security Dialog Box.
4. Select New Rule under Inbound Rules in the Actions Area on the right side of the dialog box.
5. Make the following settings for each step in the New Inbound Rule Wizard Dialog Box, clicking the Next But-
ton to move between steps.
6. Click the Finish Button. The rule that you defined will be registered in the Inbound Rules (e.g., Omron_EIP).
Close the Windows Firewall with Advanced Security Dialog Box.
7. When you attempt to connect the CX-Programmer or Network Configurator to a PLC on an EtherNet/IP net-
work through an Ethernet port, the Windows Security Alert Dialog Box will be displayed.
8. Click the Unblock Button.
Rule Type Select Custom.
Program Select All Programs.
Protocol and Ports Select ICMPv4 as the protocol type.
Scope Select Any IP address for everything.
Action Select Allow the connection.
Profile Select Domain, Private, and Public.
Name Enter any name, e.g., Omron_EIP.
425
Precautions for Using Windows XP, Vista, or Windows 7 Appendix G
An EtherNet/IP connection will be accepted from CX-Programmer or Network Configurator and EtherNet/
IP connections will be enabled in the future as well.
426
Precautions for Using Windows XP, Vista, or Windows 7 Appendix G
427
Index
Numerics
7-segment display, 24
A
Adjust Time field, 326, 328
alternate DNS server, 54
applications
precautions, xxiv
Auto Adjust Time field, 326, 327
Auto Adjust Time Tab, 326, 327
automatic clock adjustment
Automatic Clock Adjustment Switch, 328
errors
error codes, 328
error log, 328
SNTP, 328
overview, 324
procedure, 325
requirements, 324
settings, 326
specifications, 325
Auxiliary Area
related data, 88
B
Backup Tool, 336
bandwidth usage
relationship to packet interval (RPI), 263
baud rate, 55, 268
CJ-series, 15, 16
CS-series, 14
bits
Automatic Clock Adjustment Switch, 328
boots
recommended models, 28
BROADCAST DATA SEND, 397
broadcast test
command, 397
reading results, 397
BROADCAST TEST RESULTS READ, 397
buffers, 377, 411
bye command, 303, 308, 312
C
cables
connections, 44
installation, 43
precautions, 41
cd command, 303, 308, 310
cdup command, 303, 308
CIDR, 3, 94
CIO Area
allocations, 70
CIP, 3, 381
CIP communications services, 6
CIP message communications., 381
cleaning, 332
close command, 303, 308, 312
CMND(490) instruction, 190, 220, 224
commands
FTP commands, 308
communications
high traffic conditions, 232
message communications, 187, 233
message communications errors, 195
communications cables, xxv
Communications Port Enabled Flags, 226
Communications Port Error Flags, 226
communications specifications, 17
Communications Status 1 Flags, 77
Communications Status 2 Flags, 79
Communications Status 3 Flags, 79
communications test, 65
component names, 21
connecting to the FTP server, 304
connection
setting, 141
Connections settings (Edit All Connections), 144
Connections Tab, 141
connectors (modular plug)
recommended models, 28
Contact Output Units
precautions, 43
control bits, 71
CONTROLLER DATA READ, 392
CONTROLLER STATUS READ, 394
CPU Bus Units
precautions, xxvi
428
Index
creating a tag set, 126
creating tag sets, 126
creating tags, 128
crimp terminals, xxv
current consumption
CJ-series, 15, 16
CS-series, 14
CX-Integrator, 46
creating routing tables, 208
CX-Programmer, 8, 46
connecting to PLC, 211
cyclic communications
required settings, 35
D
Datalink Tool, 57
default gateway, 54
delays
message service delays, 294
delete command, 303, 308, 312
Device Monitor function, 340
device parameters
clearing, 176
editing, 127
devices
registering, 125
DHCP client computer, 102
DHCP service
automatic IP address setting by DHCP service, 102
dimensions
CJ-series, 15, 16, 19
CS-series, 14, 19
dir command, 303, 308, 309
distance
CJ-series transmission distance, 15, 16
transmission distance, 14
DM Area
allocations, 83
DNS server, 54
automatic clock adjustment
errors, 328
DNS Tab, 326
domain name, 55
downloading tag data link parameters, 168
dynamic changes of remote IP address
prohibiting, 99
E
EC Directives, xxvi
Edit Parameters, 52, 61
EDS file management, 419
EDS files, 10, 419
creating, 420
installing, 419
saving, 420
searching, 421
electromagnetic fields, xxiv
EM File Memory, 315
using, 315
EMC Directives, xxvi
EMI Standard, xxvi
EMS Standard, xxvi
EPATH type, 383
error codes
table of error codes, 365
error flags
Target Node PLC Error Flags, 73, 87
error log
clearing, 364
codes, 365
overflow, 364
specifications, 364
ERROR LOG CLEAR, 399
error log function, 364
ERROR LOG READ, 398
error processing, 339
errors
automatic clock adjustment, 328
controller status, 394
error log
clearing, 399
reading, 398
error messages, 313
flags
FINS communications, 394
message communications, 194, 195
Ethernet communications
addresses
reading from Unit, 392
network parameters, 375
parameters, 375, 377
Ethernet Connectors, 44
Ethernet Units
reading status, 411
EtherNet/IP Datalink Tool, 57
Index
429
EtherNet/IP Unit Features, 2
EtherNet/IP Units
resetting, 391
ETN11-compatible mode, 99
explicit message communications, 187, 233
explicit message communications service, 106, 108
explicit messages
list of PLC object services, 249
receiving, 248
sending, 234
sending using CMND(490), 243
F
FALS instruction, xxiii
FINS communications, 233
overview, 8
specifications, 199, 220
testing, 399
FINS communications service, 106, 107
FINS communications services, 94
FINS message communications, 187, 190
FINS node address
relationship to IP address, 94, 105
FINS response codes
troubleshooting with response codes, 371
FINS/TCP, 202
communications, 204
connection numbers, 203
connection status, 204
features, 202
frame format, 203
procedure, 205
TCP port number, 203
FINS/TCP communications method, 100
FINS/TCP Connection Status Flags, 81
FINS/UDP, 200
frame format, 200
procedure, 201
UDP port numbers, 201
FINS/UDP and FINS/TCP
comparison, 199
FINS/UDP communications methods, 96
FinsGateway, 215
flags
Error Flags, 394
FTP Status Flag, 314
FTP, 3, 62, 302
FTP server
application examples, 307
commands, 308
bye, 312
cd, 310
close, 312
delete, 312
dir, 309
get, 311
ls, 309
mdelete, 312
mget, 311
mput, 311
open, 308
put, 311
pwd, 310
quitting, 312
type, 311
user, 309
connecting, 304, 308
data type, 311
displaying current directory, 310
file types, 303
protection, 303
protocol, 303
quitting, 312
See also Memory Cards
specifications, 303
status, 314
FTP Status Flag, 314
full duplex, 55
G
gateway
default gateway, 54
general specifications, 14
get command, 303, 308, 311, 320
Get the time information from the SNTP server field, 326,
327
global address, 106
GMRP, 29
H
half duplex, 55
high communications traffic
preventing, 232
host name, 54
430
Index
Host name field, 326, 327
I
I/O allocations
CIO Area, 70
DM Area, 83
I/O memory address, 116
I/O response time, 283
I/O tables
creating, 46
overview, 46
ICMP communications
status, 408
IGMP snooping, 29
importing, 136
indicators, 23
using LED indicators for troubleshooting, 347
initial settings, 34
installation, 33
cable connections, 44
location, xxiv
mounting Unit to PLC, 38
precautions, 41
INTERNODE ECHO TEST, 396
internode test
command, 396
IP address, 54, 92
automatic generation, 95
automatic generation (dynamic), 96
automatic generation (static), 97
automatic IP address setting by DHCP service, 102
combined method, 98
determining IP addresses, 92
global address, 106
IP address table method, 95, 97
private address, 106
prohibiting dynamic changes of remote IP address, 99
relationship to FINS node address, 94, 105
responding to computers with changed IP address, 102
IP Address Display/Setting Area, 83
IP Address field, 326, 327
IP ADDRESS TABLE READ, 405
IP addresses
allocating, 92
configuration, 92
IP communications
IP addresses
reading from Units, 392
reading tables, 405
IP router tables
reading, 406
status, 408
IP ROUTER TABLE READ, 406
L
ladder programming for tag data links, 183
LED indicators, 23
using for troubleshooting, 347
link setting (baud rate), 55
local network table, 207
locking devices
precautions, xxv
Login field, 306
Low Voltage Directive, xxvi
ls command, 303, 308, 309
M
maintenance, 332
maximum tag data link I/O response time, 286
mdelete command, 303, 308, 312
memory allocation, 68
Memory Card, 334
restoring data, 335
Memory Cards, 303, 315
deleting files, 312
displaying directories, 309
See also FTP server
transferring files from host, 311
transferring files to host, 311
MEMORY STATUS READ, 411
message communications, 7, 233
errors, 194
specifications, 193
message communications functions, 187
message communications service
required settings, 35
mget command, 303, 308, 311
mkdir command, 303, 308
mode settings
reading from Unit, 392
mounting procedure, 39
mput command, 303, 308, 311
MS indicator, 23
Index
431
multicast communications, 114
multicast filter, 29
N
n
beginning word of allocated CIO Area, 70
network
devices required for constructing a network, 4
network configuration file
reading, 178
saving, 177
Network Configurator, 121
connecting to the network, 161
Device Monitor function, 340
requirements, 10
starting, 121
TCP/IP settings, 55
Network Configurator overview, 10
network devices
recommended devices, 28
networks
network memory, 411
network parameters, 375
Node Address Setting Switch, 27
node addresses
setting, 36, 37
noise, xxiv
Contact Output Units, 43
reducing, 41
nomenclature and functions, 21
Normal Target Node Flags, 81, 86
NS indicator, 23
O
online editing, xxiii
open command, 303, 308
operating environment
precautions, xxiv
P
packet interval (RPI)
relationship to bandwidth usage, 263
setting, 262
Password field, 306
PCMR(260) instruction, 227
PING, 399
PING command, 65
PLC object services, 249
Port No. field, 306, 326, 327
port numbers
UDP port
reading from Unit, 392
power supply, xxiv
precautions, xxv
precautions, xxi
applications, xxiv
Contact Output Units, 43
general, xxii
handling, 40
installation, 41
operating environment, xxiv
power supply, xxv
safety, xxii
wiring, 44
preferred DNS server, 54
private address, 106
Programming Console, 46
Programming Devices
connecting, 46
CX-Net, 46
CX-Programmer, 46
Programming Console, 46
PROTOCOL STATUS READ, 407
protocols
FTP server, 303
reading status, 407
put command, 303, 308, 311, 320
pwd command, 303, 308, 310
Q
QoS, 29
quit command, 303, 308, 312
R
radioactivity, xxiv
receiving explicit messages, 248
recommended network devices, 28
recommended products, 41
RECV(098) instruction, 190, 220, 223
accessible data areas, 221
delays, 297
432
Index
refresh cycle, 268
Register Device List, 141
Registered Target Node Flags, 81, 85
registering devices, 125, 141
relay tables, 207
rename command, 303, 308
replacing a Unit, 332
replacing Units
precautions, xxv
restoring data from the Memory Card, 335
Retry timer field, 326, 328
rmdir command, 303, 308
route path, 383
routing tables, 207
precautions, xxvi
relay network table, 207
setting examples, 209
S
safety precautions, xxii
SEND(090) instruction, 190, 220, 222
accessible data areas, 221
delays, 294
sending explicit messages, 243
Server specification type field, 326, 327
Setup Tab, 306
seven-segment Display, 24
seven-segment display
error status, 347, 351, 353, 355, 358
short-circuits
precautions, xxv
Simple Backup Function, 333
SNMP, 3, 64
SNMP trap, 64
SNTP, 3, 63, 324
SNTP server
automatic clock adjustment
errors, 328
obtaining clock information, 324
SOCKET STATUS READ, 379, 413
sockets
reading status, 413
TCP sockets
status, 379
testing communications, 399
specifications, 14
CJ-series general specifications, 15, 16
communications specifications, 17
CS-series general specifications, 14
FINS communications, 220
FTP server, 303
message communications, 193
Network Configurator, 10
startup procedure, 34
static electricity, xxiv
precautions, xxv
status
reading memory status, 411
reading protocol status, 407
reading socket status, 413
status flags for tag data links, 186
subnet mask, 93
subnet masks, 54
reading from Unit, 392
switch
Node Address Setting Switch, 27
switching hub
connection methods, 42
environment precautions, 42
functions, 29
precautions when selecting, 29
recommended models, 28
switching hub types, 28
SYSMAC BUS/2, 220
SYSMAC LINK, 220
T
tag data link parameters
downloading, 113, 168
setting, 113
uploading, 171
verifying, 172
Tag Data Link Start Bit, 72
Tag Data Link Stop Bit, 72
tag data links
checking bandwidth usage, 269
data areas, 116
delay time, 265
functions, 115
I/O response time, 283
ladder programming, 183
maximum I/O response time, 286
overview, 112
required settings, 35
Index
433
specifications, 115
status flags, 186
tag data links (cyclic communications), 6
tag set, 116
tag sets
creating, 126
Target Node PLC Error Flags, 73, 87
Target Node PLC Operating Flags, 73, 87
TCP communications
sockets
status, 379
status, 409
TCP status transitions, 379
TCP/IP, 52
terminal blocks, xxiii
timeout errors, 371
timers, 377
to, 61
troubleshooting, 368
twisted-pair cable
recommended models, 28
twisted-pair cables
precautions, 41
type command, 303, 308, 311
U
unicast communications, 114
unit numbers
setting, 36, 37
Unit replacement, 332
unit setup, 4, 61
Unit Status 1 Flags, 73
Unit Status 2 Flags, 75
Unregister Device List, 142
uploading tag data link parameters, 171
user command, 303, 308, 309
user name
specifying, 309
User Settings Area, 85
using FTP commands, 308
V
verifying tag data link parameters, 172
W
wiring
precautions, 44
434
Index
435
Revision History
A manual revision code appears as a suffix to the catalog number on the front cover of the manual.
The following table outlines the changes made to the manual during each revision. Page numbers refer to the
previous version.
Revision code Date Revised content
01 June 2007 Original production
02 July 2008 Added information for CJ-series CJ2 CPU Units and for new unit version 2.0 func-
tions.
03 December 2008 Added the CJ-series CJ2 CPU Units (CJ2H-CPU@@).
04 December 2009 Added information on methods to create connections and heartbeats.
Greatly changed the structure of sections 1 and 2.
Added and improved information on communications performance and communica-
tions load in section 10.
Made changes accompanying a new version of the Network Configurator (V3.10).
05 February 2010 Added the CJ-series CJ2M CPU Units (CJ2M-CPU3@).
Cat. No. W465-E1-05
Revision code
436
Revision History
Authorized Distributor:
In the interest of product improvement,
specifications are subject to change without notice.
Cat. No. W465-E1-05 Printed in Japan
0210
© OMRON Corporation 2007 All Rights Reserved.
OMRON Corporation Industrial Automation Company
OMRON ELECTRONICS LLC
One Commerce Drive Schaumburg,
IL 60173-5302 U.S.A.
Tel: (1) 847-843-7900/Fax: (1) 847-843-7787
Regional Headquarters
OMRON EUROPE B.V.
Wegalaan 67-69-2132 JD Hoofddorp
The Netherlands
Tel: (31)2356-81-300/Fax: (31)2356-81-388
Contact: www.ia.omron.com
Tokyo, JAPAN
OMRON ASIA PACIFIC PTE. LTD.
No. 438A Alexandra Road # 05-05/08 (Lobby 2),
Alexandra Technopark,
Singapore 119967
Tel: (65) 6835-3011/Fax: (65) 6835-2711
OMRON (CHINA) CO., LTD.
Room 2211, Bank of China Tower,
200 Yin Cheng Zhong Road,
PuDong New Area, Shanghai, 200120, China
Tel: (86) 21-5037-2222/Fax: (86) 21-5037-2200

Navigation menu