Omron SYSMAC CJ1W-EIP21 Operation Manual
  1. Manuals
  2. Brands
  3. Omron Manuals
  4. Network Hardware
  5. SYSMAC CJ1W-EIP21
  6. Operation manual

Omron SYSMAC CJ1W-EIP21 Operation Manual

Sysmac cs and cj series ethernet/ip units 100base-tx 100base-tx/10base-t
Hide thumbs Also See for SYSMAC CJ1W-EIP21:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
Table of Contents

Advertisement

Quick Links

Download this manual See also: Operating 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

OPERATION MANUAL

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SYSMAC CJ1W-EIP21 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Omron SYSMAC CJ1W-EIP21

Summary of Contents for Omron SYSMAC CJ1W-EIP21

  • Page 1: 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 OPERATION MANUAL...
  • Page 3 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...

  • Page 5: Omron Product References

    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.

  • Page 7: Table Of Contents

    TABLE OF CONTENTS PRECAUTIONS ........xxi Intended Audience .
  • Page 8 Communicating between OMRON PLCs ........
  • Page 9 TABLE OF CONTENTS SECTION 10 Communications Performance and Communications Load 261 10-1 Communications System ........... . 10-2 Adjusting the Communications Load .
  • Page 10 Appendices CS/CJ-series Ethernet Unit Function Comparison ....... . Ethernet Network Parameters ..........TCP Status Transitions .

  • Page 11: About This Manual

    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.

  • Page 12: Relevant Manuals

    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 Model number W465 CS1W-EIP21 CJ1W-EIP21 CJ2H-CPU6@-EIP CJ2M-CPU3@ W420 CS1W-ETN21 CJ1W-ETN21 W421 CS1W-ETN21 CJ1W-ETN21 W343 CS1W-ETN01 CS1W-ETN11 CJ1W-ETN11 W342 CS1G/H-CPU@@H CS1G/H-CPU@@-V1 CS1W-SCU@@-V1...
  • Page 13 Manual Model number 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 W339 CS1G/H-CPU@@H CS1G/H-CPU-@@V1 W393 CJ1G/H-CPU@@H CJ1G-CPU@@ W394 CS1G/H-CPU@@H CS1G/H-CPU-@@V1 CJ1G/H-CPU@@H CJ1G-CPU@@ NSJ@-@@@@(B)-G5D NSJ@-@@@@(B)-M3D W340 CS1G/H-CPU@@H CS1G/H-CPU-@@V1 CJ1G/H-CPU@@H CJ1G-CPU@@ NSJ@-@@@@(B)-G5D NSJ@-@@@@(B)-M3D W463 CXONE-AL@@C-V4 CXONE-AL@@D-V4 W446 WS02-CXPC@-V9 W464 CXONE-AL@@C-V4/ CXONE-AL@@D-V4 !WARNING...

  • Page 15: Read And Understand This Manual

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

  • Page 16: Application Considerations

    Application Considerations 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.

  • Page 17: 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.
  • Page 18 xviii...

  • Page 19: Unit Versions

    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. Product nameplate CS1W- UNIT Lot No. 040401 0000 Ver.1.0 OMRON Corporation MADE IN JAPAN Product nameplate CJ2H- UNIT Lot No. 080701 CPU Ver. 1.0 EIP Ver.2.0 OMRON Corporation...
  • Page 20 Note Using Unit Version Label Unit Versions and CX-Programmer Versions Unit Version Notation Product nameplate Notation used in this manual Ver. 1.0 or later number Ethernet Unit Ver. 1.0 or later (See note.) shown to right of the lot number Note CIP Revisions and Unit Versions...

  • Page 21: 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.

  • Page 22: Intended Audience

    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.
  • Page 23 Safety Precautions !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.

  • Page 24: Operating Environment Precautions

    Operating Environment Precautions Operating Environment Precautions !Caution Do not operate the control system in the following locations: !Caution Take appropriate and sufficient countermeasures when installing systems in the following locations: Application Precautions Observe the following precautions when using the EtherNet/IP Unit or built-in EtherNet/IP port.
  • Page 25 Application Precautions • 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.

  • Page 26: Conformance To Ec Directives

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

  • Page 27: Overview Of Ethernet/Ip

    This section introduces the functions and protocols used in EtherNet/IP Unit or built-in EtherNet/IP port communications services. EtherNet/IP Unit Features ........Devices Required for Constructing a Network .

  • Page 28: Ethernet/Ip Unit Features

    The communications load to the nodes must be within the Units’ allowed com- munications bandwidth. 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.
  • Page 29 EtherNet/IP Unit Features 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 The clocks built into PLCs connected to Ethernet can be automatically Adjustment adjusted to the time of the clock in the SNTP server.

  • Page 30: Devices Required For Constructing A Network

    Devices Required for Constructing a Network Devices Required for Constructing a Network CX-One Support Software Ethernet (LAN) port Recommended Switching Hubs Note Support Software Required to Construct a Network Note Unit Setup: CX- Programmer 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.
  • Page 31 For details on the Network Configurator, refer to SECTION 6 Tag Data Link Functions. Routing Table Settings: Propriety OMRON FINS network system can be constructed from OMRON CX-Integrator 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...

  • Page 32: Communications Services Overview

    Communications Services Overview Refer to the CX-Integrator Operation Manual (Cat. No. W464) for information on the CX-Integrator. 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.
  • Page 33 Communications Services Overview Connection information • Target IP address • Target tag set • Originator tag set • Packet interval (RPI) Tag Set (Inputs) Tag set name: SP1_IN Originator device 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.

  • Page 34: Fins Communications

    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...
  • Page 35 Communications Services Overview 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) UDP or TCP FINS CS/CJ-series CPU Unit EtherNet/IP Unit Section 1-4...

  • Page 36: Network Configurator 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.

  • Page 37: Precautions When Using The Network Configurator

    Network Configurator Overview 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: •...
  • Page 38 Network Configurator Overview Section 1-5...

  • Page 39: Unit Specifications

    Recommended Network Devices ......2-3-2 Network Devices Manufactured by OMRON ....2-3-3 Switching Hub Types .

  • Page 40: Ethernet/Ip Unit And Built-In Ethernet/Ip Port Specifications

    EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1-1 General Specifications 2-1-2 Unit Specifications CS-series EtherNet/IP Units Item Model number Type Applicable PLCs Unit classification Mounting location Number of Units that can be mounted CPU Unit Allocated CIO Area words used...
  • Page 41 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications CJ-series EtherNet/IP Unit Item Model number CJ1W-EIP21 Type Applicable PLCs Unit classification CJ-series CPU Bus Unit Mounting location CPU Rack or Expansion Rack Number of Units that can be mounted CPU Unit Allocated CIO Area words used words (CPU Bus Unit words)
  • Page 42 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications CJ2 CPU Built-in EtherNet/IP Port Item Model number Type Unit classification CPU Unit Allocated CIO Area words used words (CPU Bus Unit words) Allocated DM Area words (CPU Bus Unit words) User-set area Any usable data area words node information CPU Bus Unit Sys-...

  • Page 43: Communications Specifications

    EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1-3 Communications Specifications Item Tag data Number of connections 256 service links Packet interval (refresh (Cyclic cycle) communi- cations) Allowed communica- tions bandwidth per Unit Number of tags that can be registered Tag types Number of tags per connection (= 1 tag set)
  • Page 44 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Item Explicit Class 3 (connected) service messaging UCMM (unconnected) CIP routing FINS service FINS/UDP (See note 7.) FINS/TCP SNMP Agent EtherNet/IP conformance test Ethernet interface Note CS1/CJ1 Number of connections: 128 Number of clients that can communicate at one time: 32 max.

  • Page 45: Dimensions

    EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1-4 Dimensions CS1W-EIP21 130 mm CJ1W-EIP21 90 mm CJ2H-CPU@@-EIP 90 mm EIP21 COMM 100M UNIT NODE ×16 ×16 ADDRESS 192.168.250.1 SUBNET MASK 255.255.255.0 100BASE-TX 10BASE-T 35 mm 31 mm EIP21 COMM 100M UNIT NODE ADDRESS 192.168.250.1...

  • Page 46: Software Configuration

    EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications CJ2M-CPU3@ 2.7 mm 90 mm 2.7 mm 2-1-5 Software Configuration Memory Card/ EM file memory FINS FINS Service (FINS/UDP and FINS/TCP) 62 mm Interface with CPU Unit FINS Cyclic Tag data link function Encapsulation LAN controller driver LAN controller...

  • Page 47: Nomenclature And Functions

    Nomenclature and Functions Nomenclature and Functions 2-2-1 Nomenclature and Functions CS1W-EIP21 EIP21 COMM 100M UNIT NODE ×16 ADDRESS 192.168.250.1 SUBNET MASK 255.255.255.0 100BASE-TX 10BASE-T CJ1W-EIP21 EIP21 ADDRESS 192.168.250.1 SUBNET 255.255.255.0 100BASE-TX 10BASE-T LED Indicators Unit number setting switch Node address setting switches ×16 Label showing...
  • Page 48 The EtherNet/IP Unit’s address is listed in 12-digit hexadecimal on the right side of the Unit. CS1W-EIP21 ETHERNET/IP UNIT Lot No. OMRON Corporation MADE IN JAPAN @@@@@@@@@@@@ Ethernet Address Ethernet address (12 digits) (1) The Ethernet Address can also be checked with the CONTROLLER DATA READ command.
  • Page 49 Nomenclature and Functions 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 EIP21 CJ1W-EIP21, CJ2H-CPU@@-EIP, and CJ2M-CPU3@ EIP 21 Status Indicators: MS, NS, The MS (Module Status) indicator indicates the status of the node itself and COMM, 100M, and 10M the NS (Network Status) indicator indicates the status of the network.
  • Page 50 Nomenclature and Functions Indicator Name Module Status Network Status Red COMM Communication Yellow 100M 100 Mbps 10 Mbps Seven-segment Display Color LED status Fatal error Flashing Recoverable error Green Normal Not lit Power supply OFF Fatal error Flashing Recoverable error Green Tag data link and message connections established Flashing...
  • Page 51 Nomenclature and Functions 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 •...

  • Page 52: Switch Settings

    Nomenclature and Functions 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 2-2-2 Switch Settings...
  • Page 53 Nomenclature and Functions Node Address Setting Switch Note The Node Address Setting Switch sets the node address of the EtherNet/IP Unit or built-in EtherNet/IP port. Setting method Setting range Two-digit hexadecimal 01 to FE 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.

  • Page 54: Selecting The Network Devices

    Panduit Corporation plug) Boots Tsuko Company Note 2-3-2 Network Devices Manufactured by OMRON The following network devices are manufactured by OMRON for EtherNet/IP networks. Name Switching Hub W4S1-03B 2-3-3 Switching Hub Types Unmanaged Layer 2 (L2) These switching hubs use the Ethernet MAC address to switch ports. Ordi- Switching Hubs nary switching hubs have this function.

  • Page 55: Switching Hub Functions

    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.
  • Page 56 Selecting the Network Devices 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.
  • Page 57 Selecting the Network Devices L3 Switching Hub with We recommend this kind of switching hub when both tag data links and mes- Multicast Filtering and L4 sage communications are executed. QoS Functions 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.
  • Page 58 Section 2-3 Selecting the Network Devices...

  • Page 59: 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. Overview of Initial Setup Procedures ....... 3-1-1 Procedures.

  • Page 60: Overview Of Initial Setup Procedures

    Overview of Initial Setup Procedures 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.
  • Page 61 Overview of Initial Setup Procedures Settings Required for Tag Data Link Service (Cyclic Communications) 1. Using the EtherNet/IP Datalink Tool in the Network Configurator to Set the Parameters 2. Using the Tag Data Link Setting Function in the Network Configurator to Set the Parameters Settings Required for the Message Communications Service 9.

  • Page 62: Switch Settings

    Switch Settings Switch Settings 3-2-1 CS-series EtherNet/IP Units Setting the Unit Number Note Setting the Node Address Note Relationship to IP Addresses 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.

  • Page 63: Cj-Series Ethernet/Ip Units And Cj2 Built-In Ethernet/Ip Port

    Switch Settings 3-2-2 CJ-series EtherNet/IP Units and CJ2 Built-in EtherNet/IP Port Setting the Unit Number Note Setting the Node Address Note Relationship to IP Addresses 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.

  • Page 64: Mounting To A Plc

    Mounting to a PLC Mounting to a PLC 3-3-1 Mounting to a CS-series PLC Note CS1W-BC023/BC033/BC053/BC083/BC103 CPU Backplane 2, 3, 5, 8, or 10 slots (Expansion Backplane not possible with 2-slot CPU Backplane.) CS1W-BI033/BI053/BI083/BI103 CS-series Expansion Backplane 3, 5, 8, or 10 slots CS1W-BI033/BI053/BI083/BI103 CS-series Expansion Backplane 3, 5, 8, or 10 slots Note...

  • Page 65: Mounting

    Mounting to a PLC CPU Rack Expansion Backplane Expansion Backplane Expansion Backplane PS: Power Supply Unit CPU: CPU Unit IC: I/O Control Unit II: I/O Interface Unit Note The CJ1W-EIP21 EtherNet/IP Unit’s maximum current consumption is 3-3-3 Mounting 1,2,3... End cover 10 Units max.

  • Page 66: Handling Precautions

    Mounting to a PLC Note 3-3-4 Handling Precautions 3. When removing the Unit, first loosen the screw at the bottom of the Unit. Fixing screws When mounting the Unit, provide the clearance shown below to facilitate easy mounting or dismounting. Duct 20 mm min.

  • Page 67: Network Installation

    Network Installation Network Installation 3-4-1 Basic Installation Precautions Note The maximum current consumption of the CS1W-EIP21 and CJ1W-EIP21 3-4-2 Recommended Products 3-4-3 Precautions Precautions on Laying Twisted-pair Cable • Take the greatest care when installing the Ethernet System, being sure to follow ISO 8802-3 specifications.
  • Page 68 Network Installation Switching Hub Installation Environment Precautions Switching Hub Connection Methods Note Note Adjust the link settings of the EtherNet/IP Unit or built-in EtherNet/IP port to • Press the cable connector in firmly until it locks into place at both the switching hub and the EtherNet/IP Unit.

  • Page 69: Mounting Location

    Network Installation Note Best = Recommended; OK = Allowed; --- = Not allowed. 3-4-4 Using Contact Outputs (Common to All Units) Mounting Location Cable Location Switching hub setting Auto- negotiation 100 Mbps Full duplex (fixed) Half duplex OK 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.

  • Page 70: Connecting To The Network

    Connecting to the Network Connecting to the Network 3-5-1 Ethernet Connectors 3-5-2 Connecting the Cable !Caution Turn OFF the PLC’s power supply before connecting or disconnecting twisted- !Caution Allow enough space for the bending radius of the twisted-pair cable as shown The following standards and specifications apply to the connectors for the Ethernet twisted-pair cable.
  • Page 71 Connecting to the Network 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.

  • Page 72: Creating I/O Tables

    Creating I/O Tables Creating I/O Tables 3-6-1 I/O Table Overview 3-6-2 Connecting Programming Devices to the PLC Applicable Programming Devices Programming Console CX-Programmer Connecting a Programming Console 3-6-3 Procedure for Creating I/O Tables Programming Console Note I/O tables are used to identify Units mounted to the PLC, and to allocate I/O to them.
  • Page 73 Creating I/O Tables CX-Programmer (Version 8.0 or Higher) 1,2,3... (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.
  • Page 74 Creating I/O Tables 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.
  • Page 75 Creating I/O Tables Note Creating I/O tables is not required if the built-in EtherNet/IP port of a CJ2 CPU 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 menus.

  • Page 76: Setting The Local Ip Address

    Setting the Local IP Address 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.)
  • Page 77 Setting the Local IP Address 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).

  • Page 78: Tcp/Ip And Link Settings

    TCP/IP and Link Settings TCP/IP and Link Settings Note 3-8-1 Setting Procedure with the CX-Programmer 1,2,3... 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.
  • Page 79 TCP/IP and Link Settings Note Settings on the TCP/IP Tab Page 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.
  • Page 80 TCP/IP and Link Settings IP Address Subnet Mask Default Gateway Broadcasting Preferred DNS Server and Alternate DNS Server 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).

  • Page 81: Making Tcp/Ip Settings With The Network Configurator

    TCP/IP and Link Settings Domain Name IP Router Table Settings on the Ethernet Tab Page Link Setting Note Adjust the EtherNet/IP Unit’s link settings to match the communications set- Note Best = Recommended; OK = Allowed; --- = Not allowed. 3-8-2 Making TCP/IP Settings with the Network Configurator 1,2,3...
  • Page 82 TCP/IP and Link Settings Note 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.

  • Page 83: Tag Data Link Parameters

    Tag Data Link Parameters TCP/IP Parameters Tag Data Link Parameters Note The CPU Bus Unit Setup Area is not used for tag data link settings for an 3-9-1 Network Configurator Setting Procedure 1. Using the EtherNet/IP Datalink Tool in the Network Configurator to Set the Parameters 2.
  • Page 84 Tag Data Link Parameters 1,2,3... Note If an EtherNet/IP system has already been installed, you can create a similar 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. Node #1: CJ1H-CPU67H (IP address: 192.168.250.1) (IP address: 192.168.250.2)
  • Page 85 Tag Data Link Parameters − 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.
  • Page 86 Tag Data Link Parameters 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 −...

  • Page 87: Other Parameters

    Other Parameters 3-10 Other Parameters Note The CPU Bus Unit Setup Area is not used for tag data link settings for an Using FINS/UDP Tab Page in Edit Parameters Dialog Box FINS/UDP FINS/UDP Port Conversion IP Address Table Dynamic change the tar- get IP addresses 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...

  • Page 88: Using Ftp

    Other Parameters Using FINS/TCP Tab Page in Edit Parameters Dialog Box FINS/TCP FINS/TCP Port FINS/TCP Connection Setup Protection Setting Using FTP Tab Page in Edit Parameters Dialog Box Not Use FTP or Use FTP Login Password Port No. Setting Specifies the local TCP port number to use in the FINS communi- cations service.
  • Page 89 Other Parameters Using the Automatic Time Adjustment Tab Page in Edit Parameters Dialog Box Auto Adjust Time Not get the time informa- tion from the SNTP server or Get the time information from the SNTP server Auto Adjust time Server Specification Type Specifies whether to use an IP address or a domain name (i.e., IP Address Host Name Port No.

  • Page 90: Using Snmp

    Other Parameters Using SNMP Tab Page in Edit Parameters Dialog Box SNMP Not use SNMP service or Use SNMP service SNMP Port SNMP Contact Informa- tion SNMP Location Informa- tion Authentication Check 1/2 Specifies the SNMP managers that can access the PLC. Using SNMP Trap Tab Page in Edit Parameters Dialog Box...

  • Page 91: Communications Test

    Communications Test 3-11 Communications Test 3-11-1 PING Command 3-11-2 EtherNet/IP Unit or Built-in EtherNet/IP Port Operation 3-11-3 Host Computer Operation Command Method Note The PING command is not supported by some host computers. 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.

  • Page 92: Application Example

    Communications Test Application Example Normal Execution Error Occurred 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. $ ping 130.25.36.8 PING 130.25.36.8: 56 data bytes 64 bytes from 130.25.36.8: icmp_seq=0.

  • Page 93: 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. Overview of Memory Allocated to the EtherNet/IP Unit ....CIO Area Allocations .

  • Page 94: Overview Of Memory Allocated To The Ethernet/Ip Unit

    Overview of Memory Allocated to the EtherNet/IP Unit 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. •...
  • Page 95 Overview of Memory Allocated to the EtherNet/IP Unit CPU Unit ● Allocated CIO Area words (Allocated to the Unit as a CPU Bus Unit.) CIO 1500 CIO 1501 Unit number 0 CIO 1524 CIO 1525 Unit number 1 CIO 1549 CIO 1875 Unit number 15 CIO 1899...

  • Page 96: Cio Area Allocations

    CIO Area Allocations 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.

  • Page 97: Details Of The Allocated Cio Area Words

    CIO Area Allocations User Settings Offset Unit control bits (Reserved) Unit status 1 n+10 Unit status 2 n+11 Communications status 1 n+12 Communications status 2 n+13 Communications status 3 n+14 (Reserved) n+15 n+16 n+17 n+18 n+19 n+20 n+21 n+22 n+23 FINS/TCP Connection Status n+24 4-2-2...
  • Page 98 CIO Area Allocations 6 to 15 Tag Data Link Start Bit (Bit 2) Tag Data Link Stop Bit (Bit 4) Adjust Clock Bit (Bit 5) Target Node PLC Operating Information (EtherNet/IP Unit to CPU Unit) (n + 2 to n + Switch Status Manipulated...

  • Page 99: Unit Status

    CIO Area Allocations Target Node PLC These words show the error status (logical OR of fatal and non-fatal errors) of Error Information the target node PLCs that are connected with the EtherNet/IP Unit as the orig- (EtherNet/IP Unit to inator. This status information is enabled when the PLC status is included in the communications data in both the originator and target node.
  • Page 100 CIO Area Allocations Name Status Manipulated Unit Error Occurred Network Error Occurred 2 to 3 (Not used) Unit Memory Error Communications Controller Error IP Address Duplica- tion Error 7 to 8 (Not used) Link OFF Error Section 4-2 Unit operation Unit Indicates that an error occurred that is related to...
  • Page 101 CIO Area Allocations Unit Status 2 (EtherNet/IP Unit to n+11 CPU Unit) (n + 11) Name Status Manipulated 10 to (Not used) Status Area Layout Setting Error (Not used) User Settings Area Enabled Multiple Switches ON Error Error Log Stored Name Status Manipulated Online...
  • Page 102 CIO Area Allocations Name Status Manipulated Tag Data Link Operating Operating IP Address Change 3 to 10 (Not used) User Setting Area Enabled 12 to (Not used) Multiple Switches ON Error Section 4-2 Unit operation Unit Indicates that the tag data link is operating.
  • Page 103 CIO Area Allocations Communications Status 1 (EtherNet/IP Unit to CPU Unit) (n + 12) n+12 Name Status Manipulated Error Log Stored Word n+12 contains status flags related to the tag data links, as shown in the following diagram. All Tag Data Links Operating Tag Data Links Operating Name Status Manipulated...
  • Page 104 CIO Area Allocations Name Status Manipulated Invalid Communi- cations Parameter Tag Refresh Error Tag Database Error 7 to 13 (Not used) All Tag Data Links Operating Tag Data Links Operating Section 4-2 Unit operation Unit ON when there was an error in the validation check of tag data link parameters stored in the Unit’s non-volatile mem-...

  • Page 105: Communications Status

    CIO Area Allocations Communications Word n+13 contains status flags related to the Ethernet, as shown in the fol- Status 2 lowing diagram. (EtherNet/IP Unit to CPU Unit) (n + 13) n+13 1 to 13 (Not used) Communications Word n+14 contains status flags related to the Ethernet errors, as shown in Status 3 the following diagram.
  • Page 106 CIO Area Allocations Registered Target Words n+16 to n+19 show the registration status of the target nodes that are Node Table connected with the EtherNet/IP Unit as the originator. (EtherNet/IP Unit to These words show the status of nodes 0 to 63 only. If it is necessary to show CPU Unit) (n + 16 to n the status of nodes higher than node 63, select “user settings”...
  • Page 107 CIO Area Allocations n+16 n+17 n+18 n+19 Normal Target Node Words n+20 to n+23 show the connection status of the target nodes that are Table (EtherNet/IP 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 Unit to CPU Unit) target devices is refreshed in the CPU Unit.
  • Page 108 CIO Area Allocations Name Status FINS/TCP Connec- Unit tion 15 Unit FINS/TCP Connec- Unit tion 16 Unit Section 4-2 Manipulated Unit operation Turned ON by the Unit when a connection is established. Turned OFF by the Unit when the connection is terminated. Turned ON by the Unit when a connection is established.

  • Page 109: Dm Area Allocations

    DM Area Allocations 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) Offset...
  • Page 110 DM Area Allocations 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. •...

  • Page 111: User Settings Area

    User Settings Area 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.
  • Page 112 User Settings Area Normal Target Node These flags indicate the connection status of the target nodes. With revision 2 Table (EtherNet/IP 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- Unit to CPU Unit) ately turns ON when all connections are established.

  • Page 113: Error Flags

    User Settings Area Target Node PLC These flags indicate the error status (logical OR of fatal and non-fatal errors) Error Information 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 (EtherNet/IP Unit to Node Flag is ON.

  • Page 114: Auxiliary Area Data

    Auxiliary Area Data 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 A202 A20200 to Communications A20207 Port Enabled Flags A203 to Communications...

  • Page 115: Read/Write Bits (User Settings)

    Auxiliary Area Data Word(s) Bit(s) Name A417 A41700 to CPU Bus Unit Error, A41715 Unit Number Flags A427 A42700 to CPU Bus Unit Set- A42715 ting Error, Unit Number Flags 4-5-2 Read/Write Bits (User Settings) Word Bits Name A501 A50100 to CPU Bus Unit A50115 Restart Bits...
  • Page 116 Section 4-5 Auxiliary Area Data...

  • Page 117: Determining Ip Addresses

    This section explains how to manage and use IP addresses. IP Addresses ..........5-1-1 IP Address Configuration .

  • Page 118: Ip Addresses

    IP Addresses IP Addresses 5-1-1 IP Address Configuration Bit 31 Class A Network number (7 bits) Bit 31 Class B Network number (14 bits) Bit 31 Class C Bit 31 Class D Bit 31 Class E Note 5-1-2 Allocating IP Addresses IP addresses are made up of 32 bits of binary data divided into four 8-bit fields called octets.

  • Page 119: Ethernet/Ip Unit Ip Address Settings

    IP Addresses 5-1-3 EtherNet/IP Unit IP Address Settings 5-1-4 Subnet Masks 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.

  • Page 120: Ip Addresses In Fins Communications

    IP Addresses in FINS Communications 5-1-5 CIDR IP Addresses in FINS Communications 5-2-1 Specifying Nodes in FINS Communications Services Note 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 CIDR, or classless interdomain routing, is used to assign IP addresses that do not use classes.
  • Page 121 IP Addresses in FINS Communications Pairing IP Addresses with FINS Node Addresses at Local Nodes ■ Automatic Generation Method (Dynamic/Static) ■ IP Address Table Method and Combined Method Sending FINS Messages from EtherNet/IP Units or Built-in EtherNet/IP Ports • Ethernet address: A fixed number is assigned to each EtherNet/IP Unit or built-in EtherNet/IP port and it cannot be changed.

  • Page 122: Pairing Addresses In Internal Tables

    IP Addresses in FINS Communications FINS header Internal table Remote port Remote FINS Remote IP number node number address (Example) Connection (Example) 192.168.250.1 9600 192.168.250.2 9600 192.168.250.254 9600 Application level FINS Node number Transport level UDP port number Internet level Physical level Ethernet Ethernet address...
  • Page 123 IP Addresses in FINS Communications Automatic Generation (Static) Personal computer Must be fixed. Local FINS node number Must be fixed. Local IP address IP address IP address IP Address Table Method 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.
  • Page 124 IP Addresses in FINS Communications Combined Method Example When FINS Command is Sent FINS node number IP address table FINS node number Node number in 153.214.0.62 IP address table 153.214.0.129 When FINS Command is Received FINS node number Internal table Node number not in IP address table 153.218.51.10...
  • Page 125 IP Addresses in FINS Communications Note When an internal table IP address has been changed with the reception of a Prohibiting Dynamically Changing Remote IP Addresses Using the ETN11- compatible Mode Example When FINS Command is Sent FINS node number IP address table FINS node IP address...
  • Page 126 IP Addresses in FINS Communications Note If the ETN11-compatible mode is used, the internal table will retain the same FINS/TCP Communications Method Pairing in the FINS/TCP Method Note Internal Processing ■ Local Device: FINS/TCP Client 1,2,3... content from when it was created after the EtherNet/IP Unit was turned ON or restarted.
  • Page 127 IP Addresses in FINS Communications ■ Local Device: FINS/TCP Server 1,2,3... Personal computer or EtherNet/IP Unit (client) (1) The connection is established. Local FINS node number A (2) The local device (such as a personal computer) sends notification that its Local IP address T FINS node number is A.

  • Page 128: Application Examples

    IP Addresses in FINS Communications 5-2-3 Application Examples Responding to Computers with Changed IP Addresses FINS/UDP Communications Method FINS/TCP Communications Method Note 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.

  • Page 129: Related Products And Communications/Setting Methods

    IP Addresses in FINS Communications Simultaneously Running Multiple Applications on a Personal Computer FINS/UDP Communications Method FINS/TCP Communications Method 5-2-4 Related Products and Communications/Setting Methods Models Supporting Automatic Generation Method (Dynamic) server whenever the system is started. Therefore, at a personal computer using the DHCP service, IP addresses may be different with each system startup.
  • Page 130 IP Addresses in FINS Communications Models Supporting Automatic Generation Method (Static) Models Supporting IP Address Table Method Product Programmable Terminal Open Network Controller (ONC) Product CS-series Ethernet 100BASE-TX Unit 10BASE-5 10BASE-T CJ-series Ethernet 100BASE-TX Unit 10BASE-T CV/CVM1-series 10BASE-5 Ethernet Unit FinsGateway Programmable Terminal Open Network Controller (ONC)

  • Page 131: Pairing Ip Addresses And Fins Node Addresses

    IP Addresses in FINS Communications Models that Can Use the Combined Method 5-2-5 Pairing IP Addresses and FINS Node Addresses Communi- Method of pairing cations of IP addresses method and FINS node addresses FINS/UDP By pairing FINS node addresses with IP addresses in Ethernet FINS/TCP...

  • Page 132: Private And Global Addresses

    Private and Global Addresses Private and Global Addresses 5-3-1 Private and Global Addresses Intranet Intranet Global address IP router Private address Firewall Private address Communications Services That Require Global Addresses for EtherNet/IP Units and built-in EtherNet/IP ports There are two kinds of IP addresses, private and global. •...

  • Page 133: Private And Global Addresses

    Private and Global Addresses 5-3-2 Using a Private Address for the EtherNet/IP Unit Intranet Intranet IP router Firewall EtherNet/IP Unit: Private address Conditions for Using Communications Applications ■ FINS Communications Service FINS/TCP client computer with CX-Programmer, etc. CIP client computer with Network Configurator, etc.
  • Page 134 Private and Global Addresses ■ Explicit Message Communications Service Note Network Security and Firewalls • 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.

  • Page 135: Ethernet/Ip Unit With A Global Address

    Private and Global Addresses 5-3-3 EtherNet/IP Unit with a Global Address Intranet Communications over Internet Intranet Global address IP router Private address Firewall Communications in intranet EtherNet/IP Unit: Global address Conditions for Using Communications Applications ■ FINS Communications Service ■ Explicit Message Communications Service FINS/TCP client computer with CX-Programmer, etc.
  • Page 136 Private and Global Addresses Note Network Security and Firewalls • 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. Setting a global IP address for an EtherNet/IP Unit or built-in EtherNet/IP port involves network security considerations.

  • Page 137: Tag Data Link Functions

    This section describes tag data link functions and related Network Configurator operations. Overview of Tag Data Links ........6-1-1 Tag Data Links .

  • Page 138: Overview Of Tag Data Links

    Overview of Tag Data Links Overview of Tag Data Links 6-1-1 Tag Data Links Note CPU Unit DM00100 Var-In(WR200) DM20000 DM00200 Var-Out(WR300) DM20100 PLC status Note 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.

  • Page 139: Overview Of Operation

    Overview of Tag Data Links 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...
  • Page 140 Overview of Tag Data Links Setting the Packet Interval (RPI) Using Multicast and Unicast Communications 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 192.168.250.254 CN.1 Tagset _in1...

  • Page 141: Tag Data Link Functions And Specifications

    Overview of Tag Data Links 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.

  • Page 142: Data Link Data Areas

    Overview of Tag Data Links 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.
  • Page 143 Overview of Tag Data Links Connection Information · Target IP address: # · Originator tag set: SP1_IN · Target tag set: SP1_OUT · Packet interval (RPI) Number of Tags in Tag Sets ■ Tag Sets with Only One Tag One tag each (Each tag is set using a text string of the network symbol or I/O memory address.)

  • Page 144: Plc Status

    Overview of Tag Data Links One tag each (Each tag is set using a text string of the network symbol or I/O memory address.) Note The I/O memory words used in tags in a tag set do not have continuous addresses.
  • Page 145 Overview of Tag Data Links 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.
  • Page 146 Overview of Tag Data Links 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. Target Node PLC Operating Flag Information Layout set to default settings: Words n+2 to n+5...

  • Page 147: Setting Tag Data Links

    Tag data links are set by using the Network Configurator. Use the following procedure to start the Network Configurator. To start the Network configurator, select OMRON - CX-One - Network Con- figurator for EtherNet/IP - Network Configurator from the Windows Start Menu.

  • Page 148: Main Window

    Setting Tag Data Links Main Window When the Network Configurator starts, the following window will be displayed. 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.
  • Page 149 Section 6-2 Setting Tag Data Links 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.

  • Page 150: Tag Data Link Setting Procedure

    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.

  • Page 151: Registering Devices

    Setting Tag Data Links 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 Hardware List CJ2B-EIP21 CJ1W-EIP21 (CJ2)

  • Page 152: Creating Tags And Tag Sets

    Setting Tag Data Links 3. Set the IP address to match the node address (IP address) actually being 4. Repeat steps 1 to 3, and register all of the devices participating in the tag 6-2-4 Creating Tags and Tag Sets Specifying I/O The tag sets and set member tags required to create connections for a regis- Memory Addresses...
  • Page 153 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).
  • Page 154 Setting Tag Data Links Creating and Adding Tags 3. Click the Edit Tags Button. The Edit Tags Dialog Box will be displayed. 4. Click the In - Consume Tab, and click the New Button. The Edit Tag Dialog 5. In the Name Field, enter the character string for the CPU Unit's I/O memory Register the input (consume) tags and output (produce) tags separately.
  • Page 155 Setting Tag Data Links 6. Input the size of the tag in the Size Field, in bytes. 7. Click the Regist Button to register the tag. 8. Click the Out - Produce Tab, and click the New Button. The Edit Tag Dialog 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.
  • Page 156 Setting Tag Data Links 9. When you are finished registering the required tags, click the OK Button at 10. At this point, a confirmation dialog box will be displayed to check whether the bottom of the Edit Tags Dialog Box. the registered tag names will registered without changes as tag sets.
  • Page 157 Setting Tag Data Links Changing and Registering 11. The following dialog box will be displayed when the tags in the Edit Tags Tag Sets 12. If an input tag has already been registered in an input tag set, and you want Dialog Box are registered directly as tag sets.
  • Page 158 Setting Tag Data Links 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 At this point, a confirmation dialog box will be displayed to confirm that you...
  • Page 159 Setting Tag Data Links 13. In order to edit a registered tag set and add tags, either double-click the tag 14. When the PLC status is being included in the tag set, select the Include 15. If you want to change the tag set’s name, it can be changed in this dialog 16.
  • Page 160 Setting Tag Data Links 18. If you want to just add new tags and register the tag set, first register the 19. When you are finished registering the required tags, click the OK Button at 20. At this point, a confirmation dialog box will be displayed to check whether tags with steps 1 to 9.
  • Page 161 Setting Tag Data Links 21. To register the newly added tags in a tag set, either double-click the de- 22. Select the tags that you want to add from the Candidate Tag List and click 23. To confirm the changes, click the OK Button at the bottom of the Edit Tag 24.
  • Page 162 Setting Tag Data Links 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.
  • Page 163 Section 6-2 Setting Tag Data Links 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.
  • Page 164 Setting Tag Data Links 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.
  • Page 165 Setting Tag Data Links 4. You can change tag set names in this dialog box. To confirm a change, click 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.
  • Page 166 Setting Tag Data Links 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- 2. You can add a tag as a network symbol by selecting and executing the CSV Note The following precautions apply when importing.

  • Page 167: Connection Settings

    Setting Tag Data Links 6-2-5 Connection Settings Note Connection Settings (Connections Tab) Registering Devices in the Register Device List 1,2,3... 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. •...
  • Page 168 Setting Tag Data Links Editing Settings for Individual Connections Note 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 Button. The selected target device will be displayed in the Reg- ister Device List, as shown in the following diagram.
  • Page 169 Setting Tag Data Links 1,2,3... 1. Select the Connection Tab and then click the New Button. Using an OMRON EtherNet/IP Unit or Built-in EtherNet/IP Port as the Target Using Other EtherNet/IP Devices as the Target The following Edit Connection Dialog Box will be displayed according to the type of device that is selected.

  • Page 170: Setting Tag Data Links

    Setting Tag Data Links Connections Settings (Editing All Connections) 1,2,3... The settings are as follows: Item 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.
  • Page 171 Setting Tag Data Links 2. When the settings are completed, click the OK Button. The following table describes the various settings in the dialog box. Setting Target Device Selects the target device. Connection Any name can be given to the connection (up to 32 charac- Name ters).
  • Page 172 Setting Tag Data Links Confirming the Connections Settings 1,2,3... 1. An overview of the connections set in the Register Device List is displayed 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 in the Connections Tab Page.
  • Page 173 Setting Tag Data Links Automatically Setting Connections Output tag set: A_Signal 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.
  • Page 174 Setting Tag Data Links 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. Output tag set: O_Signal 1,2,3...
  • Page 175 Setting Tag Data Links 4. A device connection structure tree will be displayed when processing has 5. Use the device connection structure tree as required to change the RPI Device Connection Connection settings can be displayed on the network configuration. Select Structure Tree View Device’s Connection Structure Tree from the Network Menu.

  • Page 176: Setting Tags Using Data Link Tool

    Edit Button. The connections can be edited in this dialog box. • 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.
  • Page 177 Setting Tag Data Links Node List The following items will be displayed in the Node Area on the left side of the window. 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 The data link table of the node selected on the left will be displayed on the Information...

  • Page 178: Setting Procedure

    Setting Tag Data Links 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...
  • Page 179 Setting Tag Data Links 2. Select the memory area (here, W) in the Memory Field and enter the start- 3. Select the memory area (here, D) in the Memory Field and enter the start- 4. Select the Enable Over Load Check Box if the Over Load function is nec- 5.
  • Page 180 Setting Tag Data Links Automatic Allocation Results for Node 1 (IP Address: 192.168.250.1) Automatic Allocation Results for Node 2 (IP Address: 192.168.250.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.
  • Page 181 Setting Tag Data Links 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.

  • Page 182: Creating Connections Using The Wizard

    1,2,3... 1. Set tags and tag sets for all devices before starting the Wizard. Refer to 6- 2. For tag data links between OMRON PLCs, a connection is created in the b. No Table Inconsistencies The following message will be displayed. Click the OK Button.
  • Page 183 Setting Tag Data Links 3. Create the connection following the instructions that are given by the Wiz- 4. A list of tag sets is displayed on the right side of the Wizard Dialog Box with Note Tag sets that are used in connections that are already set are not displayed. The following dialog box will be displayed before the Wizard starts.
  • Page 184 Setting Tag Data Links 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.

  • Page 185: Creating Connections By Device Dragging And Dropping

    If the target is another EtherNet/IP device, refer to the manual of that device and perform settings as required. 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...
  • Page 186 Setting Tag Data Links • 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.

  • Page 187: Connecting The Network Configurator To The Network

    Setting Tag Data Links 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.
  • Page 188 Setting Tag Data Links 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. Select Option - Select Interface - CS/CJ1 Serial Port → EIP Unit I/F. 1,2,3...
  • Page 189 Setting Tag Data Links 3. Input the EtherNet/IP Unit’s unit number in the Unit No. Field, select the 4. After clicking TCP:2, click the OK Button. The Network Configurator will be 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.
  • Page 190 Setting Tag Data Links 2. Select Network - Connect. The Setup Interface Dialog Box will be dis- 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 5.
  • Page 191 Setting Tag Data Links 7. Select the port for the EtherNet/IP Unit and then click the OK Button. The Connecting to an EtherNet/IP Network via an Ethernet Unit Note Ethernet 1,2,3... 1. Select Option - Select Interface - Ethernet Network Configurator will be connected to the EtherNet/IP network. If the Network Configurator goes online normally, “On-line”...
  • Page 192 Setting Tag Data Links 2. Select Network - Connect. 3. Click the Setup Button in the Setup Interface Dialog Box. The Registration The registration information details are as follows: The following Setup Interface Dialog Box will be displayed. 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.
  • Page 193 Setting Tag Data Links 4. Once the settings have been registered, the Setup Interface Dialog Box will 5. The following dialog box will be displayed. Select TCP:2, which represents 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 •...

  • Page 194: Downloading Tag Data Link Parameters

    Setting Tag Data Links 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.
  • Page 195 Setting Tag Data Links 1,2,3... 1. Connect the Network Configurator online. 2. There are two ways to download the parameters. 3. Click the Yes Button to download the tag data link parameters to the Eth- • Downloading to All Devices in the Network Select Network - Download.
  • Page 196 Setting Tag Data Links 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.

  • Page 197: Uploading Tag Data Link Parameters

    Setting Tag Data Links 6-2-11 Uploading Tag Data Link Parameters 1,2,3... 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.

  • Page 198: Verifying The Tag Data Links

    Setting Tag Data Links 6-2-12 Verifying the Tag Data Links 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.

  • Page 199: Verifying The Network Configuration

    Setting Tag Data Links Verifying the Network Compare the list of registered devices in the Network Configuration Window Configuration 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.
  • Page 200 Setting Tag Data Links Verifying the Device Parameters 1,2,3... Click the OK Button or the Close Button. 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.

  • Page 201: Starting And Stopping Tag Data Links

    Setting Tag Data Links 5. If multiple nodes have been selected, the following message will be dis- 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.

  • Page 202: Clearing The Device Parameters

    Setting Tag Data Links 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.

  • Page 203: Saving The Network Configuration File

    Setting Tag Data Links 6-2-15 Saving the Network Configuration File 1,2,3... 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. •...

  • Page 204: Reading A Network Configuration File

    Setting Tag Data Links 3. When the network configuration is changed later, the existing network con- 4. You can select the Select target network Check Box in the Option Area to 6-2-16 Reading a Network Configuration File A previously saved network configuration file can be read into the Network Configurator.
  • Page 205 Setting Tag Data Links 1,2,3... 1. Select File - Open or click the 2. When you click and select the network configuration file that you want to 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 be displayed.

  • Page 206: Checking Connections

    Setting Tag Data Links 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.

  • Page 207: Changing Devices

    Setting Tag Data Links 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.
  • Page 208 Setting Tag Data Links Icon Offline (gray) Default (no configuration) (turquoise edge) (green) Idle (CPU Unit of PLC is in PROGRAM mode.) Communications normal (CPU Unit of PLC is in RUN or MONI- (blue) TOR mode.) Warning (A non-fatal error has occurred in the CPU Unit of the (yellow) PLC.) Alarm (A fatal error has occurred in the CPU Unit of the PLC.)

  • Page 209: Ladder Programming With Tag Data Links

    4. The corresponding Normal Target Node Flag (in words n+20 to n+23) is 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) Condition showing the Target Node PLC’s fatal or non-fatal error status...
  • Page 210 Ladder Programming with Tag Data Links Programming for Revision 2 or Higher Programming for Revision 1 and Revision 2 Programming to Detect The following programming can be used to check for errors for each target Errors: Example 1 node. This programming is used to detect errors only after the data links for all nodes have started normally.
  • Page 211 Ladder Programming with Tag Data Links Programming for Revision 1 or Higher Example of Programming The following type of programming can be used to process data only when the to Process Data data links are operating normally. 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.

  • Page 212: Status Flags Related To Tag Data Links

    Ladder Programming with Tag Data Links 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.

  • Page 213: Message Communications Functions

    This section describes message communications using FINS messages and explicit messages. Overview ........... . . FINS Message Communications.

  • Page 214: 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;...
  • Page 215 I/O link function is disabled. EtherNet/IP Unit FINS FINS message message function Explicit FINS Explicit message message function Ethernet (EtherNet/IP) network Section 7-1 OMRON special message communications FINS message EtherNet/IP message communications Explicit message...

  • Page 216: Fins Message Communications

    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.
  • Page 217 Section 7-2 FINS Message Communications 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 CS/CJ-series EtherNet/IP Unit Controller Link Ethernet (EtherNet/IP) CS/CJ-series EtherNet/IP Unit Ethernet (EtherNet/IP) Note FINS commands sent and received by the CS/CJ-series EtherNet/IP Unit include commands addressed to the CS/CJ-series CPU Unit...

  • Page 218: Explicit Message Communications

    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.

  • Page 219: Message Communications Specifications

    Message Communications Specifications Message Communications Specifications CPU Unit function Unit model number Communications Sending/ receiving instructions data FINS commands Sending Ether- Net/IP CIP UCMM messages Number of desti- FINS message com- nation nodes munications Explicit message communications Transmission data FINS message com- length (not includ- munications ing the command...

  • Page 220: Message Communications Error Indications

    Message Communications Error Indications 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- 2.

  • Page 221: Message Communications Errors

    Message Communications Errors 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.
  • Page 222 Section 7-6 Message Communications Errors...

  • Page 223: Fins Communications

    FinsGateway ......... . . Communicating between OMRON PLCs ......

  • Page 224: Overview Of Fins Communications

    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.

  • Page 225: Using The Fins/Udp And Fins/Tcp Methods

    Overview of FINS Communications 8-1-2 Using the FINS/UDP and FINS/TCP Methods It is recommended that FINS/UDP and FINS/TCP be used as follows: 8-1-3 FINS Communications Service Specifications Item Number of nodes Message length 2,012 bytes max. Number of buffers Protocol name FINS/UDP method Protocol used UDP/IP...

  • Page 226: Fins/Udp Method

    FINS/UDP Method 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.
  • Page 227 FINS/UDP Method UDP Port Numbers for The UDP port number is the number for UDP to identify the application layer FINS/UDP (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.

  • Page 228: Fins/Tcp Method

    FINS/TCP Method 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.
  • Page 229 FINS/TCP Method FINS/TCP Frame Format The following diagram shows the structure of a TCP packet sent over an Ethernet network. Ethernet Ver. 2 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.
  • Page 230 FINS/TCP Method 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).
  • Page 231 FINS/TCP Method After a connection has been established as a FINS/TCP client, it can be termi- nated in the following ways. 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...
  • Page 232 FINS/TCP Method • 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...

  • Page 233: Routing Tables

    Routing Tables 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. 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.

  • Page 234: Connecting And Using A Peripheral Device For The Plc

    Routing Tables The following example shows routing tables for sending data from PLC #1 (the local node: network address 1, node address 1) to PLC #4 (the destination node: network address 3, node address 2). PLC #1 (local node) Node #1 Network #1 PLC #1 relay network table...

  • Page 235: Routing Table Setting Examples

    Routing Tables 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. ■...
  • Page 236 Routing Tables ■ Example 3: All Nodes This example uses the following configuration to show the routing tables for all nodes. Unit #5 Node #6 Unit #3 Node #4 Unit #2 Node #3 Network #20 Unit #0 Unit #5 Unit #1 Node #2 Node #1 Node #5...

  • Page 237: Using Fins Applications

    Using FINS Applications Using FINS Applications 8-5-1 CX-Programmer (CX-Server) ■ System Configuration Example 1: No Routing CX-Programmer/CX-Integrator Node number: 1 IP address: 192.168.250.1 Ethernet port Ethernet or EtherNet/IP (Network address: None) FINS/UDP method The following examples show how to connect online from a CX-Programmer on an Ethernet network to a PLC on the Ethernet network.
  • Page 238 Using FINS Applications Note Example: Inputs to the CX-Programmer's Setup Window Example: Change PLC Settings Example: Network Settings (Network Tab Page) When FinsGateway is selected as the network type, make sure that the frame length is set to 2,000 bytes max. Section 8-5...
  • Page 239 Using FINS Applications 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.
  • Page 240 Using FINS Applications Settings for target PLC (PLC3)'s Change PLC Dialog Box Driver Tab Page Workstation node address Automatic generation method IP address Port number 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.

  • Page 241: Finsgateway

    Using FINS Applications 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.
  • Page 242 (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- Set the IP address conversion method.
  • Page 243 Using FINS Applications Click the Add Button, and then set the IP address table in the following Ether- net Node Definition Dialog Box. • UDP Nodes Tab Page: IP Address Table Method or Combined Method • Node address: Set the remote FINS node address. •...
  • Page 244 Using FINS Applications • 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.
  • Page 245 Using FINS Applications ■ 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.

  • Page 246: Communicating Between Omron Plcs

    Communicating between OMRON PLCs 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.

  • Page 247: Plc Communications Data Areas

    Communicating between OMRON PLCs 8-6-2 PLC Communications Data Areas Note The following table shows the I/O data areas involved when SEND(090) and RECV(098) are used. Area CIO Area Work Area Holding Area Auxiliary Area Timer Area Counter Area DM Area EM Area 1.

  • Page 248: Using Send(090), Recv(098), And Cmnd

    Communicating between OMRON PLCs 8-6-3 Using SEND(090), RECV(098), and CMND(490) SEND(090) (@)SEND(90) 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...
  • Page 249 Communicating between OMRON PLCs 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.
  • Page 250 Communicating between OMRON PLCs CMND(490) (@)CMND(490) 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)
  • Page 251 Communicating between OMRON PLCs 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).

  • Page 252: Writing Programs

    Communicating between OMRON PLCs Usage Command code File memory Debugging 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.
  • Page 253 Communicating between OMRON PLCs Communications Execution Port Enabled Flag condition Reset B Communications Port Enabled Flag Communications Port Error Flag Execution Communications condition Port Enabled Flag Reset D (Continued in same way.) 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-...
  • Page 254 Communicating between OMRON PLCs Communications Port The status of a SEND(090), RECV(098), and CMND(490) instruction after Completion Codes 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...
  • Page 255 Communicating between OMRON PLCs Example Communications Port Enabled Flag Communications instruction: SEND(090), RECV(098), CMND(490) Communications Port Error Flag Communications Port Completion Code Completion Instruction 1 Instruction 2 being executed. being executed. 0000 0000 0000 (Normal completion) Section 8-6 Instruction 3 being executed.

  • Page 256: Program Example

    Communicating between OMRON PLCs 8-6-5 Program Example Execution condition A20207 000000 120002 (See note 1.) 120001 120000 120000 A20207 (See note 1.) 120000 A21907 (Continued on next page.) When the Communications Port Enabled Flag for port 7 KEEP is ON, and RECV(098) is not being executed, the send...
  • Page 257 Communicating between OMRON PLCs (Continued from previous page.) Execution condition A20207 000001 120000 (See note 1.) 120003 120002 120002 A20207 (See note 1.) 120002 A21907 120002 120003 A21907 Note 1. With CS/CJ-series PLCs, the Communications Port Enabled Flags at bits 2.

  • Page 258: Precautions On High Traffic In Fins Communications

    Precautions on High Traffic in FINS Communications 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.

  • Page 259: Message Communications

    This section describes message communications using FINS commands sent from the ladder program in the CPU Unit of the PLC. Sending Explicit Messages ........9-1-1 Sending Explicit Messages Using CMND(490).

  • Page 260: Sending Explicit Messages

    Sending Explicit Messages Sending Explicit Messages CS/CJ-series EtherNet/IP Unit CS/CJ-series CPU Unit Explicit messages can be sent Explicit message Ethernet (EtherNet/IP) CPU Unit Explicit message CMND (490) Note: Use 28 01 for the FINS command code. FINS header 1,2,3... CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports can send explicit messages.
  • Page 261 EtherNet/IP node explicit message. Always perform retry processing when sending explicit mes- sages. Section 9-1 The node address of the non-OMRON node is set as the destination node address in the FINS command data. Command code Explicit command block Node address of the non-...
  • Page 262 Sending Explicit Messages CIP UCMM MESSAGE SEND (28 10) Command Block 28 10 Command Transport code 502 bytes max. request size Time Out Ticks Priority/Time Tick Routing service data This command sends an explicit message for CIP routing to another node’s specified class and receives a response.
  • Page 263 Sending Explicit Messages Response Block Parameters The following normal response is returned to a transmitted CIP UCMM MES- SAGE SEND command if it was completed normally. 2810 Hex 0000 Hex Command Response Transport No. of bytes code code 502 bytes max. Service response data (variable length) Reserved...
  • Page 264 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.
  • Page 265 Sending Explicit Messages Description Note 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.
  • Page 266 Sending Explicit Messages Section 9-1 Ann Arbor, Michigan 48108-5006 TEL: 1 734-975-8840 FAX: 1 734-922-0027 Email odva@odva.org WEB www.odva.org...
  • Page 267 Sending Explicit Messages EXPLICIT MESSAGE SEND (28 01) Command Block Response Block Parameters 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.
  • Page 268 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.
  • Page 269 Sending Explicit Messages 9-1-1 Sending Explicit Messages Using CMND(490) Command Format Example: Get_Attribute_All Service to Identity Object Command Transport code Unconnected Send service: 52 Hex Request path size = 2 words: 02 Hex Class ID Connection Manager: 06 Hex Request path 8-bit class ID Request path size (2 words) Service code...
  • Page 270 Sending Explicit Messages Setting the Command Data for CMND(490) 08 07 FINS command code Transport 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...
  • Page 271 Sending Explicit Messages Example: Sending Explicit Messages Using CMND(490) Operation Command Details data and ERROR CLEAR codes, is also returned in the same order from low to high bytes in the response block. EtherNet/IP Unit with unit number 0 PLC's Unit Explicit message...
  • Page 272 Sending Explicit Messages Response 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...
  • Page 273 Sending Explicit Messages Program Example A20011 000000 First Cycle Flag Execution condition 000000 A20200 151100 000013 Communications Online Flag Enabled Flag (n+11, bit 00) 000001 A20200 A21900 000018 Communications Network Communication Enabled Flag Execution Error Flag 000024 (071) BSET #0000 D00000 D02999 Sets 0000 in D00000 to D02999.

  • Page 274: Receiving Explicit Messages

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

  • Page 275: List Of Plc Object Services

    Receiving Explicit Messages 9-2-1 List of PLC Object Services Status Read/Write for CPU Units Services Service code CPU Unit Informa- 0E Hex tion Read CPU Unit Write 10 Hex CPU Unit Status 40 Hex Read PLC Objects provide the following services. Class ID Instance ID Request...
  • Page 276 Receiving Explicit Messages I/O Memory Read/Write for CPU Units Service Service Class ID code Byte Data Read 1C Hex C4 Hex (2F Hex) (See note.) Word Data 1D Hex Read Byte Data Write 1E Hex Word Data Write 1F Hex Note With a EtherNet/IP Unit or built-in EtherNet/IP port with unit version 2.0 or Instance ID Request...
  • Page 277 Receiving Explicit Messages CPU Information Read (Service Code: 0E Hex) Command Block Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters Reads CPU Unit information, including operating mode, fatal/non-fatal errors, and the CPU Unit model. The class ID depends on the unit version.
  • Page 278 Receiving Explicit Messages Note The codes for the above modes are 1-word (2-byte) data and are returned in CPU Unit Write (Service Code: 10 Hex) Command Block Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters low byte first.
  • Page 279 Receiving Explicit Messages • 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.
  • Page 280 Receiving Explicit Messages CPU Unit Status Read (Service Code: 40 Hex) Command Block Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters This PLC Object service reads status details (operation status, operating mode, fatal and non-fatal errors, etc.) from the CPU Unit. (2F) The class ID depends on the unit version.
  • Page 281 Receiving Explicit Messages Unspecified 1: Unspecified (reserved for system use) 1: Basic I/O Unit error 1: Interrupt task error 1: Unspecified (reserved for system use) 1: System error (FAL) Operation status 0: Stopped (User program is not being executed.) 1: Operating (User program is being executed.) Flash memory access status (CS1H, CJ1-H, CJ1M, and CS1D only) 0: Memory is not being written.
  • Page 282 Receiving Explicit Messages Byte Data Read (Service Code: 1C Hex) Command Block Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters • 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).
  • Page 283 Receiving Explicit Messages Important Points Word Data Read (Service Code: 1D Hex) Command Block Note A body format of either 8 bits or 16 bits is possible. 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.
  • Page 284 Receiving Explicit Messages Response Block Parameters Important Points Byte Data Write (Service Code: 1E Hex) Service Code Word data H Word data L Word data L Read data (200 bytes max.) Service code (command, response): ID Hex is specified for commands. For responses, the highest bit will turn ON and 9D Hex will be returned.
  • Page 285 Receiving Explicit Messages Command Block (2F) Class ID Service Instance ID Code Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters Important Points Word Data Write (Service Code: 1F Hex) Address L Word data L Address H Word data H Word data H...
  • Page 286 Receiving Explicit Messages Command Block (2F) Class ID Service Instance ID Code Note A body format of either 8 bits or 16 bits is possible. Response Block Parameters Important Points Address L Word data H Address H Word data L Word data L Write data (200 bytes max.) Service Code...
  • Page 287 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......... 10-1-1 Tag Data Link Communications Method .

  • Page 288: Communications System

    Communications System 10-1 Communications System 10-1-1 Tag Data Link Communications Method Packet Interval (RPI) In EtherNet/IP tag data links, the data transmission period is set for each con- Settings 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.
  • Page 289 Communications System Packet Interval (RPI) In a tag data link, the number of packets transferred each second is called the and Bandwidth Usage bandwidth used or PPS (packets per second). The PPS is calculated from the RPI and heartbeat as follows for each connec- (PPS) tion: The following equation is used to calculate the total number of packets trans-...

  • Page 290: Calculating The Number Of Connections

    Communications System 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.

  • Page 291: Network Transmission Delay Time

    Communications System 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.
  • Page 292 Communications System 3. Switching Hub The switching hub delay is the delay time between the arrival of the packet at Delay 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.
  • Page 293 Communications System 200 words × 16 PLC #1 PLC #2 PLC #3 5 ms 200 words 5 ms 200 words 5 ms Section 10-1 PLC #17 200 words...

  • Page 294: Adjusting The Communications Load

    Adjusting the Communications Load 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...

  • Page 295: Checking Bandwidth Usage For Tag Data Links

    Adjusting the Communications Load 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.

  • Page 296: Tag Data Link Bandwidth Usage And Rpi

    Adjusting the Communications Load Checking the Usage of The percentage of the allowable communications bandwidth for tag data links Capacity and Network for each EtherNet/IP Unit is displayed as the Usage of Capacity and the band- Bandwidth for Tag Data width used for tag data link communications in the entire network is displayed Links as the Mbit/s.

  • Page 297: Adjusting Device Bandwidth Usage

    Adjusting the Communications Load Note 10-2-3 Adjusting Device Bandwidth Usage Switching Hubs without Multicast Filtering (100- Mbps Hubs) Switching Hubs with Multicast Filtering (100- Mbps Hubs) 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.

  • Page 298: Changing The Rpi

    Adjusting the Communications Load 10-2-4 Changing the RPI 1,2,3... • 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”...
  • Page 299 Adjusting the Communications Load 3. The usage of capacity can be adjusted by changing the associated devic- 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.
  • Page 300 Adjusting the Communications Load 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.
  • Page 301 Adjusting the Communications Load 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.

  • Page 302: Rpi Setting Examples

    Adjusting the Communications Load 4. If the usage of capacity cannot be adjusted to the desired level when the 5. Check the bandwidth usage again. 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.
  • Page 303 Adjusting the Communications Load Example Conditions 192.168.250.1 IP address: 100 words 100 words 100 words 100 words Checking the Device Bandwidth Usage 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.

  • Page 304: Changing The Settings

    Adjusting the Communications Load Changing the Method 1: Same Packet Interval Setting for All Connections Settings 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.
  • Page 305 Section 10-2 Adjusting the Communications Load 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.
  • Page 306 Adjusting the Communications Load 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.
  • Page 307 Section 10-2 Adjusting the Communications Load 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.
  • Page 308 Adjusting the Communications Load 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.

  • Page 309: I/O Response Time In Tag Data Links

    I/O Response Time in Tag Data Links 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.

  • Page 310: Effect On The Cpu Unit's Cycle Time

    I/O Response Time in Tag Data Links 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.

  • Page 311: Tag Data Link I/O Response Time Calculation Example

    I/O Response Time in Tag Data Links CPU Unit Effect of EtherNet/IP Unit or CJ2H built-in port only CJ2H CPU Rack: 0.1 ms Expansion Rack: 0.13 ms CJ2M CPU Rack: 0.14 ms Expansion Rack: 0.16 ms 0.25 ms CJ1M 0.17 ms CJ1-H 0.1 ms 0.2 ms...

  • Page 312: Maximum Tag Data Link I/O Response Time

    I/O Response Time in Tag Data Links EtherNet/IP The following table gives the items required to find the I/O response time and values used in calculations for this system configuration. Total number tag data link words 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.
  • Page 313 I/O Response Time in Tag Data Links (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.
  • Page 314 I/O Response Time in Tag Data Links Total: (2) Send data process- ing time (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.
  • Page 315 I/O Response Time in Tag Data Links D Number of data trans- missions Total: (5) Receive data process- ing time (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.
  • Page 316 I/O Response Time in Tag Data Links 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.

  • Page 317: Tag Data Link Performance For Cj2M Built-In Ethernet/Ip Ports

    Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports 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.

  • Page 318: Tag Data Link I/O Response Time

    Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports 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 <...
  • Page 319 Section 10-4 Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports 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...

  • Page 320: Message Service Transmission Delay

    Message Service Transmission Delay 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.
  • Page 321 Message Service Transmission Delay For details, refer to the CPU Unit’s Operation Manual. CPU Bus Unit Service The following table shows the CPU Bus Unit service processing time, which Processing Time (Local depends on the CPU Unit’s CPU processing mode setting. Node) For details, refer to the CPU Unit’s Operation Manual.
  • Page 322 Message Service Transmission Delay CPU Bus Unit Service The following table shows the CPU Bus Unit service processing time, which Processing Time (Remote depends on the CPU Unit’s CPU processing mode setting. Node) 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.
  • Page 323 Message Service Transmission Delay RECV(098) Instruction Execution of RECV(099) in user program CPU Bus Unit service cycle (Local node, 1) Maximum transmission delay = CPU Bus Unit Service The following table shows the service cycle, which depends on the CPU Unit’s Cycle (Local Node, 1) CPU processing mode setting.
  • Page 324 Message Service Transmission Delay 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...
  • Page 325 Message Service Transmission Delay For details, refer to the CPU Unit’s Operation Manual. CPU Bus Unit Service The following table shows the CPU Bus Unit service cycle, which depends on Cycle (Local Node, 2) the CPU Unit’s CPU processing mode setting. For details, refer to the CPU Unit’s Operation Manual.
  • Page 326 Message Service Transmission Delay 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 •...

  • Page 327: Ftp Server

    This section describes the functions provided by the FTP server. 11-1 Overview and Specifications........11-1-1 Overview.

  • Page 328: Overview And Specifications

    Overview and Specifications 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.

  • Page 329: Ftp Server Function Details

    FTP Server Function Details 11-1-2 Specifications Item Executable com- Connects the specified host FTP server. open: mands Specifies user name for the remote FTP server. user: Displays the Memory Card file names. Display the Memory Card file names and details. dir: rename: Changes a file name.

  • Page 330: Connecting To The Ftp Server

    FTP Server Function Details 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.

  • Page 331: Using The Ftp Server Function

    Using the FTP Server Function 11-3 Using the FTP Server Function 11-3-1 Procedure 1,2,3... 1. Make the basic settings. 2. When using a user-set FTP login name and password: 3. Select Transfer to PLC from the PLC Menu and click the Yes Button. The 4.

  • Page 332: Ftp Tab

    Using the FTP Server Function 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 Login Set the login name to externally connect to the EtherNet/IP Unit or built-in EtherNet/IP port via FTP.

  • Page 333: Ftp Server Application Example

    FTP Server Application Example 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.

  • Page 334: Using Ftp Commands

    Using FTP Commands 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.
  • Page 335 Using FTP Commands 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.
  • Page 336 Using FTP Commands 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.
  • Page 337 Using FTP Commands type Format type data_type Function Specifies the file data type. The following data types are supported: ascii: 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.
  • Page 338 Using FTP Commands 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.

  • Page 339: Error Messages And Ftp Status

    Using FTP Commands 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 PPP is a directory. PPP is not a directory. Another unit has access authority (FINS error 0 x 3001).

  • Page 340: Checking Ftp Status

    Checking FTP Status PPP: Path name XXX: IP address 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.

  • Page 341: Using File Memory

    Using File Memory 11-7 Using File Memory There are two media that can be used to store files in memory for CS/CJ- series PLCs: 11-7-1 File Memory Media Memory type CS/CJ- Flash memory 8 MB series 15 MB Memory 30 MB Cards EM File Max.
  • Page 342 Using File Memory File Names Handled by CPU Unit The files described in the following table can be read or written by the CPU Unit. File type File name Data file ******** Program file ******** Parameter area file ******** Files Data files AUTOEXEC .IOM trans-...

  • Page 343: Initializing File Memory

    Using File Memory 11-7-3 Initializing File Memory Memory Cards EM File Mem- 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.
  • Page 344 Using File Memory Example: Data format using words delimited by tabs and CRs after every I/O memory ■ 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.
  • Page 345 Using File Memory Example: Data format using words delimited by commas with CRs after every I/O memory .CSV file contents 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.

  • Page 346: Ftp File Transfer Time

    FTP File Transfer Time 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. ■...

  • Page 347: Host Computer Application Example

    Host Computer Application Example 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 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.
  • Page 348 Host Computer Application Example 4. Change to the MEMCARD directory. ftp> cd MEMCARD 250 CWD command successful. ftp> ■ 5. Change data type to binary. ··· Binary data type set. ftp> type binary 200 Type set to I. ftp> ■ 6.

  • Page 349: 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 ........12-1-1 Overview.

  • Page 350: Automatic Clock Adjustment

    Automatic Clock Adjustment 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).

  • Page 351: Using The Automatic Clock Adjustment Function

    Using the Automatic Clock Adjustment Function 12-1-2 Specifications 12-2 Using the Automatic Clock Adjustment Function 12-2-1 Procedure 1,2,3... 1. Make the basic settings. 2. With the CX-Programmer online, right-click the EtherNet/IP Unit or built-in 3. To perform automatic clock adjustment manually, turn the Automatic Clock 4.

  • Page 352: Settings Required For Automatic Clock Adjustment Function

    Using the Automatic Clock Adjustment Function 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. Auto Adjust Time DNS (See note.) Note When the Server specification type field in Auto Adjust Time Tab is set to Host name.

  • Page 353: Auto Adjust Time

    Using the Automatic Clock Adjustment Function 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 Get the time Enable to set the CPU Unit's clock to the time at the information from...

  • Page 354: Automatic Clock Adjustment Switch

    Automatic Clock Adjustment Switch 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 Automatic Clock The Unit control bit is shown in the following diagram.
  • Page 355 Automatic Clock Adjustment Error Processing 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. 03C1 03C4 03C6 Error Meaning Detailed error code code 1st byte...
  • Page 356 Automatic Clock Adjustment Error Processing 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.

  • Page 357: 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 ........13-1-1 Cleaning .

  • Page 358: Maintenance And Replacement

    • 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. Section 13-1...

  • Page 359: Simple Backup Function

    Simple Backup Function 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 a Unit has been replaced, verify that the following steps have been made after Unit correctly.
  • Page 360 Simple Backup Function 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 The data that was backed up with the simple backup function can be restored Restore Targets to Units or built-in ports as shown in the following table.
  • Page 361 Simple Backup Function 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.

  • Page 362: Using The Backup Tool

    Using the Backup Tool Comparing EtherNet/IP Set pins 7 and 8 of the DIP switch on the front panel of the CPU Unit, as Unit or Built-in EtherNet/IP shown in the following table, and press down the Memory Card Power Supply Port Data with the Setup Switch for 3 seconds.
  • Page 363 The PLC Backup Tool can be used for the following: 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...
  • Page 364 Section 13-3 Using the Backup Tool...

  • Page 365: 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 .

  • Page 366: Checking Status With The Network Configurator

    Checking Status with the Network Configurator 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.
  • Page 367 Section 14-1 Checking Status with the Network Configurator 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.
  • Page 368 Checking Status with the Network Configurator 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. Section 14-1...
  • Page 369 Section 14-1 Checking Status with the Network Configurator 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.
  • Page 370 Checking Status with the Network Configurator 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.
  • Page 371 Checking Status with the Network Configurator 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.
  • Page 372 Checking Status with the Network Configurator 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. Section 14-1...

  • Page 373: Using The Led Indicators And Display For Troubleshooting

    Using the LED Indicators and Display for Troubleshooting Ethernet Information Tab The Ethernet Information Tab Page shows the communications status at the Page 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).
  • Page 374 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Lit red Not lit EtherNet/IP Unit or built-in EtherNet/IP port faulty Flashing Not lit Node address setting error Flashing Not lit CPU Unit faulty Flashing Not lit I/O table not registered Flashing Simple backup...
  • Page 375 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Flashing CPU Unit memory error Flashing Not lit CPU Unit event servic- ing timeout Flashing Routing table error Flashing I/O refresh error Error Cause Unit operation (Flag A parity error Records the error in occurred during the error log.
  • Page 376 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Flashing CPU Unit ser- vice monitor- ing error Flashing CPU Unit watchdog timer error Error Cause Unit operation (Flag Servicing from • If the Unit is the orig- the CPU Unit inator of the tag data was not com- link connection, it...
  • Page 377 Using the LED Indicators and Display for Troubleshooting Errors Related to the CPU The 7-segment display alternates between the node address and error code. Unit Indicator 7-segment Flashing CPU Unit Fatal Error Output OFF Error Errors Related to the The 7-segment display alternates between the node address and error code. Control Bits Indicator 7-segment...

  • Page 378: Errors Related To Tag Data Links

    Using the LED Indicators and Display for Troubleshooting Errors Related to the Tag The 7-segment display alternates between the node address and error code. Data Links Indicator 7-segment Verification Error (target non-existent) Connection Failed Tag Data Link Error Error Cause Unit operation (Flag The target regis- The Unit will periodi-...
  • Page 379 Using the LED Indicators and Display for Troubleshooting Errors Related to Memory The 7-segment display alternates between the node address and error code. Access Indicator 7-segment Flashing Memory Access Error Error Cause Unit operation (Flag An error Case 1: occurred in the The error record Unit's non-vola- remains in RAM only.
  • Page 380 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Flashing Device Param- eters Error Flashing IP Advanced Settings Error Flashing Ethernet Basic Settings Error Error Cause Unit operation (Flag The I/O Area set There is an error in in the device the parameter set- parameters tings stored in the...

  • Page 381: Errors Related To Network

    Using the LED Indicators and Display for Troubleshooting Errors Related to the The 7-segment display alternates between the node address and error code. Network Indicator 7-segment Ethernet Link Not Detected Error Cause Unit operation (Flag The link with the • The Unit will be switching hub offline and unable to could not be...
  • Page 382 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Server Con- nection Error Error Cause Unit operation (Flag An error The DNS Server occurred in Error Flag (n+14, bit communica- 05) will turn ON. tions with the DNS server. An error Case 1: occurred with...
  • Page 383 Using the LED Indicators and Display for Troubleshooting Indicator 7-segment Server Con- nection Error Lit red IP Address Duplication Flashing Address mis- match Error Cause Unit operation (Flag An error occurred in transmission to the SNMP trap. The IP address •...

  • Page 384: Errors Related To Unit

    Connection Status Codes and Error Processing Indicator 7-segment Flashing Not lit Communica- tions Control- ler Error Flashing Node Address Setting Changed Dur- ing Operation Errors Related to the Unit The 7-segment display alternates between the node address and error code. Indicator 7-segment Lit red...
  • Page 385 Connection Status Codes and Error Processing The following table shows the possible originator/target configurations. Configuration 1 Configuration 2 Configuration 3 The following table shows the likely causes of the errors causes for each con- figuration and connection status (code). Connection status Source of error General Additional...
  • Page 386 Connection Status Codes and Error Processing Connection status Source of error General Additional Status Status (hex) (hex) 0109 Error code returned from target: The connection size settings are different in the originator and target. 0110 Error code returned from target: The target was unable to open the connection, because of its operating status, such as down-...
  • Page 387 Connection Status Codes and Error Processing Connection status Source of error General Additional Status Status (hex) (hex) 011A Error code returned from origi- nator: Connection could not be estab- lished because the buffer was full due to high traffic. 011B Error code returned from target: The RPI was set to a value that is below the specifications.
  • Page 388 Connection Status Codes and Error Processing Connection status Source of error General Additional Status Status (hex) (hex) 0316 Error code returned from target: There was a parameter error in the frame used to close the con- nection. 031C Error code generated in origina- tor: Some other error occurred.
  • Page 389 Source of error General Additional Status Status (hex) (hex) Unique OMRON Error Codes 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.)

  • Page 390: Error Log Function

    Error Log Function 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.

  • Page 391: Error Log Error Codes

    Error Log Function 14-4-4 Error Log Error Codes Error Error code (hex) 0001 CPU Unit watchdog timer error 0002 CPU Unit service monitoring error 0006 Other CPU error 000E I/O bus error 000F CPU Unit initialization error 0011 Event timed out 0012 CPU Unit memory error 0015...
  • Page 392 Error Log Function Error Error code (hex) 0300 Parameter error; packet discarded 0347 I/O refreshing error 03C0 FINS/TCP setting error 03C1 Server settings error 03C2 FINS/TCP packet discarded 03C3 FINS/UDP packet discarded Detail code First byte Second byte FINS Command: Bit 15: OFF Bits 08 to 14: Source network address Bits 00 to 07: Source node address...
  • Page 393 Error Log Function Error Error code (hex) 03C4 Server connection error 03C6 Clock write error 03D0 Ethernet basic setting error 03D1 Ethernet advanced setting error 03D2 Packet discarded. Detail code First byte Second byte 00 hex: DNS 01 hex: Specified host does not exist 03 hex: SNTP 02 hex: No such service at...

  • Page 394: Troubleshooting

    Troubleshooting Error Error code (hex) 03D3 Link OFF error 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.

  • Page 395: Troubleshooting Section

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

  • Page 396: Tag Data Link Problems

    Troubleshooting 14-5-4 Tag Data Link Problems The tag data isn't Observe the following precautions when writing application simultaneous. 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.

  • Page 397: Troubleshooting With Fins Response Codes

    Troubleshooting with FINS Response Codes 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.
  • Page 398 Troubleshooting with FINS Response Codes Main response Sub response code code Value and Value and meaning meaning Local node Local node send error error Node address set- ting error Local node busy (send failed) Remote Remote node not in node error network No Unit with speci- fied unit address...
  • Page 399 Troubleshooting with FINS Response Codes Main response Sub response code code Value and Value and meaning meaning Command Command too long format error Command too short Number of items does not match amount of data Header parameter error Parameter Parameter error error No data area code Address out-of-...
  • Page 400 Troubleshooting with FINS Response Codes Main response Sub response code code Value and Value and meaning meaning Status error Cannot execute because service is (operating being processed. mode dis- agreement) Socket not open Local node busy (send failed) FINS/TCP not con- nected Establishing connec- tion...

  • Page 401: Cs/Cj-Series Ethernet Unit Function Comparison

    CS/CJ-series Ethernet Unit Function Comparison Item Tag data link communications service CIP message communications service FINS/UDP service FINS/TCP service Socket service File transfer (FTP) Mail send/receive Web functions Automatic adjustment of PLC’s internal clock Simple backup function Error log Response to PING command SNMP/SNMP trap CIDR function for IP addresses Online connection by EtherNet/IP using CX-One...

  • Page 402: A Cs/Cj-Series Ethernet Unit Function Comparison

    Appendix A CS/CJ-series Ethernet Unit Function Comparison...

  • Page 403: Ethernet Network Parameters

    Ethernet Network Parameters Parameter Value TCP send buffer 4,096 bytes TCP receive buffer 4,096 bytes UDP send buffer 9,000 bytes UDP receive buffer 9,016 bytes FINS receive buffer 16,383 bytes RAW send buffer 2,048 bytes RAW receive buffer 2,048 bytes Hold timer 75 s (See note.) Resend timer...
  • Page 404 Appendix B Ethernet Network Parameters...

  • Page 405: 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). RECEIVED CLOSE snd FIN WAIT-1 rcv ACK of FIN FIN WAIT-2 rcv FIN snd ACK Status CLOSED Connection closed. LISTEN Waiting for connection.
  • Page 406 Appendix C TCP Status Transitions...

  • Page 407: Cip Object

    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.
  • Page 408 CIP Message Communications Terminology In CIP specifications, “Object,” “Class,” “Instance,” “Attribute” and “Service” are defined as follows: Term 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.

  • Page 409: Route Path

    CIP Message Communications 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.”...

  • Page 410: Cip Message Communications

    CIP Message Communications According to CIP Specifications, the Segment Type specifications are decided as follows: Segment Type Port Segment Logical Segment Network Segment Symbolic Segment Data Segment Data Type Data Type Reserved 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.

  • Page 411: Logical Segment

    CIP Message Communications 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. Extended Link Segment Type Address Size Link Address → 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”...

  • Page 412: Port Number

    CIP Message Communications 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.

  • Page 413: Response Codes

    CIP Message Communications 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 Status Name Code (hex) Success Connection failure Resource unavailable Invalid parameter value See Status Code 20 hex, which is the preferred value to use for this condition. Path segment error Path destination unknown...
  • Page 414 CIP Message Communications General Status Status Name Code (hex) Invalid attribute value list Embedded service error Vendor specific error Invalid parameter Write-once value or medium already written Invalid Reply Received An invalid reply is received (e.g. reply service code does not match the request 23-24 Key Failure in path Path Size Invalid...
  • Page 415 CIP Message Communications Example of Additional Status in case that General Status Is 01 Hex. (Status of Connection Manager Object) General Status Additional (hex) Status (hex) 0100 Connection in Use or Duplicate Forward Open. 0103 Transport Class and Trigger combination not supported 0106 Ownership Conflict 0107...
  • Page 416 CIP Message Communications Priority/Time Ticks and Time Out Ticks Format of the Priority/Time Tick Time tick Base value (ms) 0000 hex 0001 hex 0010 hex 0011 hex 0100 hex 0101 hex 0110 hex 0111 hex 1000 hex 1001 hex 1010 hex 1,024 1011 hex 2,048...

  • Page 417: Efins Commands Addressed To Ethernet/Ip Units Or Built-In Ethernet/Ip Ports

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Command code RESET CONTROLLER DATA READ CONTROLLER STATUS READ INTERNODE ECHO TEST BROADCAST TEST RESULTS READ BROADCAST DATA SEND ERROR LOG READ ERROR LOG CLEAR PING FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST FINS/TCP CONNECTION STATUS READ IP ADDRESS TABLE WRITE...

  • Page 418: Controller Data Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.
  • Page 419 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Mode Setting (Response) The mode setting in the system setup is returned. Broadcast Address Setting Bit 1 Broadcast with host number set to all ones (4.3BSD specifications) Broadcast with host number set to all zeroes (4.2BSD specifications) Communications Partner IP Address Conversion Method Setting Bit 3 Bit 2...

  • Page 420: Controller Status Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Codes Response code 0000 Normal end 1001 Command too large CONTROLLER STATUS READ Reads the controller status. Command Block 06 01 Command code Response Block 06 01 2 byte 4 byte Command Response...
  • Page 421 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports IP Router Table Error Bit 3 No error Error detected (More than 8 records, or invalid IP address). Routing Table Error Bit 6 No error Error detected in routing table check. Ethernet Advanced Setting Error Bit 9 No error...

  • Page 422: Internode Echo Test

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.

  • Page 423: Broadcast Test Results Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Codes Response code 0000 Normal end 1001 Command too large 1002 Command too small (No test data) BROADCAST TEST RESULTS READ Reads the results (number of times data received) of the broadcast test. Command Block 08 02 Command...

  • Page 424: Error Log Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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: Destination unit address: Response/no response flag: 1 (no response) ERROR LOG READ...

  • Page 425: Error Log Clear

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 1st byte Error code Detailed Day Hour Year Month Minutes Second information 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.

  • Page 426: Fins/Tcp Connection Remote Node Change Request

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Command Block 27 20 Command Destination IP address Timeout code value Response Block 27 20 Command Response code code 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.

  • Page 427: Fins/Tcp Connection Status Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Command Block 27 30 Command FINS/TCP Remote IP code connection No. address Response Block 27 30 Command Response code code 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.
  • Page 428 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Block 27 31 Command Response FINS/TCP Connection code code connection service 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.

  • Page 429: Ip Address Table Write

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Codes Response code 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 IP ADDRESS TABLE WRITE...

  • Page 430: Ip Address Write

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports • 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 Response code 0000...

  • Page 431: Ip Address Table Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Codes Response code 0000 Normal end 1001 Command too large 1002 Command too small 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.

  • Page 432: Ip Router Table Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 6 bytes IP address FINS node number 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 •...

  • Page 433: Protocol Status Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.
  • Page 434 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.
  • Page 435 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Type number #6, #7 #9, #10 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.
  • Page 436 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.

  • Page 437: Memory Status Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.
  • Page 438 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response Block 27 63 92 bytes Command Response Memory status code code 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).

  • Page 439: Socket Status Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.

  • Page 440: Address Information Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.

  • Page 441: Ip Address Read

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Address Information Returns the FINS node addresses and IP addresses. Each pair requires 6 bytes and has the following configu- ration. 6 bytes FINS node IP address number FINS Node Address Node address set in the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal).

  • Page 442: Explicit Message Send

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 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.

  • Page 443: Cip Ucmm Message Send

    FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response code 110B Response length exceeds maximum response length. 2211 Unit is busy. Description For details, refer to EXPLICIT MESSAGE SEND (28 01) on page 241 in 9-1-1 Sending Explicit Messages Using CMND(490).
  • Page 444 FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response code 1005 Header error 110B Response length exceeds maximum response length. 2211 Unit is busy. Description For details, refer to CIP UCMM MESSAGE SEND (28 10) on page 236 in 9-1-1 Sending Explicit Messages Using CMND(490).

  • Page 445: Installing Eds Files

    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.

  • Page 446: Creating Eds Files

    EDS File Management 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.

  • Page 447: Eds File Management

    EDS File Management 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.
  • Page 448 EDS File Management 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. Appendix F...

  • Page 449: Precautions For Using Windows Xp, Vista, Or Windows 7

    Precautions for Using Windows XP, Vista, or 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.
  • Page 450 Precautions for Using Windows XP, Vista, or Windows 7 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.

  • Page 451: G Precautions For Using Windows Xp, Vista, Or Windows 7

    Appendix G Precautions for Using Windows XP, Vista, or Windows 7 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.
  • Page 452 Appendix G Precautions for Using Windows XP, Vista, or Windows 7...

  • Page 453: Index

    Numerics 7-segment display Adjust Time field alternate DNS server applications precautions xxiv Auto Adjust Time field Auto Adjust Time Tab automatic clock adjustment Automatic Clock Adjustment Switch errors error codes error log SNTP overview procedure requirements settings specifications Auxiliary Area related data Backup Tool bandwidth usage...
  • Page 454 creating a tag set creating tag sets creating tags crimp terminals current consumption CJ-series CS-series CX-Integrator creating routing tables CX-Programmer connecting to PLC cyclic communications required settings Datalink Tool default gateway delays message service delays delete command Device Monitor function device parameters clearing editing...
  • Page 455 EtherNet/IP Unit Features EtherNet/IP Units resetting ETN11-compatible mode explicit message communications explicit message communications service explicit messages list of PLC object services receiving sending sending using CMND(490) FALS instruction xxiii FINS communications overview specifications testing FINS communications service FINS communications services FINS message communications FINS node address relationship to IP address...
  • Page 456 Host name field I/O allocations CIO Area DM Area I/O memory address I/O response time I/O tables creating overview ICMP communications status IGMP snooping importing indicators using LED indicators for troubleshooting initial settings installation cable connections location xxiv mounting Unit to PLC precautions INTERNODE ECHO TEST internode test...
  • Page 457 multicast communications multicast filter beginning word of allocated CIO Area network devices required for constructing a network network configuration file reading saving Network Configurator connecting to the network Device Monitor function requirements starting TCP/IP settings Network Configurator overview network devices recommended devices networks network memory...
  • Page 458 refresh cycle Register Device List Registered Target Node Flags registering devices relay tables rename command replacing a Unit replacing Units precautions restoring data from the Memory Card Retry timer field rmdir command route path routing tables precautions xxvi relay network table setting examples safety precautions xxii...
  • Page 459 specifications status flags tag data links (cyclic communications) tag set tag sets creating Target Node PLC Error Flags Target Node PLC Operating Flags TCP communications sockets status status TCP status transitions TCP/IP terminal blocks xxiii timeout errors timers troubleshooting twisted-pair cable recommended models twisted-pair cables precautions...
  • Page 460 Index...

  • Page 461: 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 June 2007 July 2008...
  • Page 462 Revision History...
  • Page 464 200 Yin Cheng Zhong Road, PuDong New Area, Shanghai, 200120, China Tel: (86) 21-5037-2222/Fax: (86) 21-5037-2200 Authorized Distributor: © OMRON Corporation 2007 All Rights Reserved. In the interest of product improvement, specifications are subject to change without notice. Printed in Japan Cat.

This manual is also suitable for:

Sysmac cj2h-cpu6*-eipSysmac cs1w-eip21Sysmac cj2m-cpu3 seriesCj1w-eip21 - rev 02-2010Cj2h-cpu6 - rev 02-2010Cj2m-cpu3 - rev 02-2010 ... Show all

Table of Contents

Save PDF