Cat. No.
CS1W-EIP21 (100Base-TX) CJ1W-EIP21 (100Base-TX) CJ2H-CPU6@-EIP (100Base-TX) CJ2M-CPU3@ (100Base-TX/10Base-T) EtherNet/IP Units Operation Manual Revised February 2010
iv
Notice: OMRON products are manufactured for use according to proper procedures by a qualified operator and only for the purposes described in this manual. The following conventions are used to indicate and classify precautions in this manual. Always heed the information provided with them. Failure to heed precautions can result in injury to people or damage to property. !DANGER Indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
vi
TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii 2 General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii 3 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS SECTION 4 Memory Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4-1 Overview of Memory Allocated to the EtherNet/IP Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 4-2 CIO Area Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4-3 DM Area Allocations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS SECTION 10 Communications Performance and Communications Load 261 10-1 Communications System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 10-2 Adjusting the Communications Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268 10-3 I/O Response Time in Tag Data Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE OF CONTENTS Appendices A CS/CJ-series Ethernet Unit Function Comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 B Ethernet Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 C TCP Status Transitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 D CIP Message Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About this Manual: This manual describes the operation of the CS/CJ-series EtherNet/IP Units and the built-in EtherNet/IP ports on a CJ2 CPU Unit for constructing applications and includes the sections described below. Please read this manual carefully and be sure you understand the information provided before attempting to install or operate the EtherNet/IP Unit or built-in EtherNet/IP port. Be sure to read the precautions provided in the following section.
Relevant Manuals The following table lists CS- and CJ-series manuals that contain information relevant to EtherNet/IP Units or built-in EtherNet/IP ports.
Manual number W474 W339 Model 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 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 CXONE-AL@@C-V4 CXONE-AL@@D-V4 W463 W446 WS02-CXPC@-V9 W464 CXONE-AL@@C-V4/ CXONE-A
xiv
Read and Understand this Manual Please read and understand this manual before using the product. Please consult your OMRON representative if you have any questions or comments. Warranty and Limitations of Liability WARRANTY OMRON's exclusive warranty is that the products are free from defects in materials and workmanship for a period of one year (or other period if specified) from date of sale by OMRON.
Application Considerations SUITABILITY FOR USE OMRON shall not be responsible for conformity with any standards, codes, or regulations that apply to the combination of products in the customer's application or use of the products. At the customer's request, OMRON will provide applicable third party certification documents identifying ratings and limitations of use that apply to the products.
Disclaimers CHANGE IN SPECIFICATIONS Product specifications and accessories may be changed at any time based on improvements and other reasons. It is our practice to change model numbers when published ratings or features are changed, or when significant construction changes are made. However, some specifications of the products may be changed without any notice. When in doubt, special model numbers may be assigned to fix or establish key specifications for your application on your request.
xviii
Unit Versions of CS/CJ-series Unit Versions A “unit version” has been introduced to manage Units in the CS/CJ Series according to differences in functionality accompanying Unit upgrades. Notation of Unit Versions on Products The unit version is given to the right of the lot number on the nameplate of the products for which unit versions are being managed, as shown below. ■ CS1W-EIP21/CJ1W-EIP21 Product nameplate CS1WUNIT Unit version Example for unit version 1.0 Lot No. Lot No.
Unit version Note Using Unit Version Label The unit version will be displayed in the Unit Manufacturing Information Dialog Box. The following unit version label is provided with the EtherNet/IP Unit. This label can be attached to the front of the EtherNet/IP Unit to differentiate between EtherNet/IP Units with different unit versions. Unit Versions and CX-Programmer Versions Use the following versions of the CX-Programmer to make the Unit settings for the EtherNet/IP Unit. Unit version Unit version 1.
PRECAUTIONS This section provides general precautions for using the CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports. The information contained in this section is important for the safe and reliable application of EtherNet/IP Units or built-in EtherNet/IP ports. You must read this section and understand the information contained before attempting to set up or operate an EtherNet/IP Unit or built-in EtherNet/IP port. 1 2 3 4 5 6 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . .
1 Intended Audience 1 Intended Audience This manual is intended for the following personnel, who must also have knowledge of electrical systems (an electrical engineer or the equivalent). • Personnel in charge of installing FA systems. • Personnel in charge of designing FA systems. • Personnel in charge of managing FA systems and facilities. 2 General Precautions The user must operate the product according to the performance specifications described in the operation manuals.
Safety Precautions 3 !WARNING Provide safety measures in external circuits (i.e., not in the Programmable Controller), including the following items, to ensure safety in the system if an abnormality occurs due to malfunction of the Programmable Controller or another external factor affecting the operation of the Programmable Controller. “Programmable Controller” indicates the CPU Unit and all other Units and is abbreviated “PLC” in this manual.
Operating Environment Precautions 4 4 Operating Environment Precautions !Caution Do not operate the control system in the following locations: • Locations subject to direct sunlight. • Locations subject to temperatures or humidity outside the range specified in the specifications. • Locations subject to condensation as the result of severe changes in temperature. • Locations subject to corrosive or flammable gases. • Locations subject to dust (especially iron dust) or salts.
5 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. An incorrect power supply may result in malfunction. • Install external breakers and take other safety measures against short-circuiting in external wiring.
6 Conformance to EC Directives • When transporting the Unit, use special packing boxes and protect it from being exposed to excessive vibration or impacts during transportation. • CPU Bus Units will be restarted when routing tables are transferred from a Programming Device to the CPU Unit. Restarting these Units is required to read and enable the new routing tables. Confirm that the system will not be adversely affected before allowing the CPU Bus Units to be reset.
SECTION 1 Overview of EtherNet/IP This section introduces the functions and protocols used in EtherNet/IP Unit or built-in EtherNet/IP port communications services. 1-1 EtherNet/IP Unit Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1-2 Devices Required for Constructing a Network . . . . . . . . . . . . . . . . . . . . . . . . 4 1-3 Support Software Required to Construct a Network. . . . . . . . . . . . . . . . . . . .
Section 1-1 EtherNet/IP Unit Features 1-1 EtherNet/IP Unit Features CX-One Support Software (3) Switching hub (2) Twisted-pair cable (1) Built-in EtherNet/IP port on 100 m max. (1) CS1W-EIP21 EtherNet/IP Unit for CS-series Ethernet (LAN) port CS-series PLC (1) CJ1W-EIP21 EtherNet/IP Unit CJ-series PLC CJ2 CPU Unit (CJ2H-CPU@@-EIP/ CJ2M-CPU3@) CJ-series PLC EtherNet/IP System Configuration Example EtherNet/IP is an industrial multi-vendor network that uses Ethernet components.
Section 1-1 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 Adjustment The clocks built into PLCs connected to Ethernet can be automatically adjusted to the time of the clock in the SNTP server.
Section 1-2 Devices Required for Constructing a Network 1-2 Devices Required for Constructing a Network The basic configuration for an EtherNet/IP System consists of one switching hub to which nodes are attached in star configuration using twisted-pair cable. CX-One Support Software (3) Switching hub (2) Twisted-pair cable (1) Built-in EtherNet/IP port on 100 m max.
Section 1-3 Support Software Required to Construct a Network Computer CX-Programmer EtherNet/IP Unit or built-in EtherNet/IP port Edit Parameters Dialog Box Unit settings (Built-in non-volatile memory) CS/CJ-series CPU Unit Refer to the CX-Programmer Operation Manual (Cat. No. W446) for information on the CX-Programmer. Tag Data Link Settings: Network Configurator The Network Configurator is used to set the tag data links for the EtherNet/IP Unit or built-in EtherNet/IP port.
Section 1-4 Communications Services Overview Personal computer running Windows CX-Integrator Routing table settings EtherNet/IP Unit or built-in EtherNet/IP port Routing Table Area CS/CJ-series CPU Unit Refer to the CX-Integrator Operation Manual (Cat. No. W464) for information on the CX-Integrator. 1-4 Communications Services Overview The following communications services are supported.
Section 1-4 Communications Services Overview Connection information • Target IP address • Target tag set • Originator tag set • Packet interval (RPI) Connection Tag Set (Inputs) Tag Set (Outputs) Tag set name: SP1_IN Tag set name: SP1_IN PLC Status PLC Status Tag a Tag i Tag b Tag ii Data flow Tag c : Tag g Originator device Note Target device EtherNet/IP In this example, a connection is established with the originator’s tag list containing tags a to g (inputs), which are grouped in a tag
Section 1-4 Communications Services Overview EtherNet/IP CS/CJ-series CPU Unit EtherNet/IP Unit Ethernet (EtherNet/IP), etc. EtherNet/IP Unit FINS Communications Service FINS commands can be sent to or received from other PLCs or computers on the same Ethernet network by executing SEND(090), RECV(098), or CMND(490) instructions in the ladder diagram program. This enables various control operations such as the reading and writing of I/O memory between PLCs, mode changes, and file memory operations.
Section 1-4 Communications Services Overview Ethernet (EtherNet/IP) IP UDP or TCP FINS CS/CJ-series CPU Unit EtherNet/IP Unit 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.
Network Configurator Overview 1-5 Section 1-5 Network Configurator Overview 1-5-1 Overview The Network Configurator Ver. 3.0 or higher is a software package designed for building, setting, and controlling a multi-vendor EtherNet/IP Network using OMRON's EtherNet/IP. It is included in CX-One version 4.0 or higher. The Network Configurator provides the following functions for building, setting, and controlling EtherNet/IP.
Section 1-5 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 connection using the Network Configurator.
Network Configurator Overview 12 Section 1-5
SECTION 2 Unit Specifications This section provides the specifications of EtherNet/IP Units and introduces recommended network configuration devices. 2-1 2-2 2-3 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications . . . . . . . . . . . 14 2-1-1 General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2-1-2 Unit Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2-1-3 Communications Specifications . . . .
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1 2-1-1 Section 2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications General Specifications The general specifications conform to those of the CS-series and CJ-series PLCs. 2-1-2 Unit Specifications CS-series EtherNet/IP Units Item Model number Type Applicable PLCs Unit classification Mounting location Number of Units that can be mounted Specifications CS1W-EIP21 100Base-TX (See note.
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1 CJ-series EtherNet/IP Unit Item Model number Type Applicable PLCs Unit classification Mounting location Number of Units that can be mounted CPU Unit Allocated CIO Area words used words (CPU Bus Unit words) Allocated DM Area words (CPU Bus Unit words) User-set area CPU Bus Unit System Setup Non-volatile memory within EtherNet/IP Unit (See note.
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Section 2-1 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 CPU Bus Unit System Setup Non-volatile memory for the CJ2 built-in EtherNet/IP port Specifications CJ2H-CPU@@-EIP CJ2M-CPU3@ 100Base-TX (See note.
EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1-3 Section 2-1 Communications Specifications CIP Tag data service links (Cyclic communications) Item CS1/CJ1 CJ2H Number of connections 256 Packet interval (refresh 0.5 to 10,000 ms (in 0.5-ms units) cycle) Can be set independently for each connection. (Data is refreshed over the network at the preset interval and does not depend on the number of nodes.) Allowed communications bandwidth per Unit 6000 pps (See note 1.
Section 2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications Item CIP Explicit service messaging CS1/CJ1 CJ2H CJ2M Class 3 (connected) UCMM (unconnected) Number of connections: 128 Number of clients that can communicate at one time: 32 max. Number of servers that can communicate at one time: 32 max. CIP routing CS1W-EIP21 CJ1W-EIP21 CJ2H-CPU@@-EIP CJ2M-CPU3@ Supported 16 connections max.
Section 2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications 2-1-4 Dimensions CS1W-EIP21 EIP21 MS NS COMM 100M 10M UNIT NO. NODE NO. 0 0 1 ×161 130 mm IP ×160 ADDRESS 192.168.250.1 SUBNET MASK 255.255.255.0 100BASE-TX 10BASE-T 35 mm 101 mm CJ1W-EIP21 65 mm 31 mm EIP21 MS NS COMM 100M 10M EF01 6789 2345 ABCD IP ADDRESS EF01 EF01 6789 ABCD ABCD 90 mm x161 6789 2345 2345 UNIT No. NODE No. x160 192.168.250.1 SUBNET MASK 255.255.255.
Section 2-1 EtherNet/IP Unit and Built-in EtherNet/IP Port Specifications CJ2M-CPU3@ 76.16 mm 2.7 mm 90 mm 2.7 mm 75 mm 62 mm 84.
Section 2-2 Nomenclature and Functions 2-2 2-2-1 Nomenclature and Functions Nomenclature and Functions CS1W-EIP21 EIP21 MS NS COMM 100M 10M LED Indicators UNIT NO. NODE NO. 0 Node address setting switches 1 ×161 IP Unit number setting switch 0 ×160 ADDRESS Label showing IP address 192.168.250.1 SUBNET MASK 255.255.255.
Section 2-2 Nomenclature and Functions Built-in EtherNet/IP Port in CJ2H-CPU@@-EIP LED Indicators Unit number setting switch Node address setting switches Label showing IP address Ethernet connector Built-in EtherNet/IP Port in CJ2M-CPU3@ LED Indicators Unit number setting switch Node address setting switches Label showing IP address Ethernet connector Ethernet Address Notation A specific Ethernet address is allocated to all devices connected to the Ethernet network.
Section 2-2 Nomenclature and Functions EIP21 MS NS COMM 100M 10M EF012 6789 345 UNIT No. Example label IP ADDRESS 192.168.250.1 SUBNET MASK ABCD 255.255.255.0 EF012 EF012 ADDRESS ABCD 6789 IP x161 6789 345 345 NODE No. x160 Affix the label on the front of the EtherNet/IP Unit, between the node address switches and the Ethernet connector. ABCD 192.168.250.1 SUBNET MASK 255.255.255.
Section 2-2 Nomenclature and Functions Indicator Name MS Module Status NS Color Red Green --Network Status Red Green COMM --Communication Yellow 100M 100 Mbps Yellow 10M 10 Mbps Yellow Seven-segment Display LED status Lit Flashing Lit Not lit Lit Flashing Lit Flashing Not lit Lit Not lit Lit Not lit Lit Not lit Indicated operating status Fatal error Recoverable error Normal Power supply OFF Fatal error Recoverable error Tag data link and message connections established Tag data link and mess
Section 2-2 Nomenclature and Functions If an error occurs, the error code will be displayed alternately with the rightmost byte of the affected device’s IP address. For details on error codes, refer to SECTION 14 Troubleshooting and Error Processing. Displaying Multiple Error Sources • A d6 error (failed to establish connection) occurred with IP address 192.168.250.8. • A d6 error (failed to establish connection) occurred with IP address 192.168.250.9.
Section 2-2 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 • A d6 error (failed to establish connection) occurred with IP address 10.0.1.8. • A d6 error (failed to establish connection) occurred with IP address 10.0.2.8.
Section 2-2 Nomenclature and Functions The Node Address Setting Switch sets the node address of the EtherNet/IP Unit or built-in EtherNet/IP port. 3210F 7654 6543 X161 EDC DCB 210FE BA98 Node Address Setting Switch X160 A987 Setting method Two-digit hexadecimal Setting range 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 EtherNet/IP Unit or built-in EtherNet/IP port.
Section 2-3 Selecting the Network Devices 2-3 Selecting the Network Devices 2-3-1 Recommended Network Devices The following table shows the devices recommended for use with the EtherNet/IP. Part Switching Hub Twisted-pair cable Connectors (Modular plug) Boots Maker Cisco Systems, Inc. Model number Consult the manufacturer. Contec USA, Inc. Phoenix Contact Consult the manufacturer. Consult the manufacturer. 100BASE-TX Fujikura F-LINK-E 0.
Section 2-3 Selecting the Network Devices 2-3-4 Switching Hub Functions This section describes the switching hub functions that are important when using an EtherNet/IP network. When using an EtherNet/IP Unit, set the following two functions. • Multicast filtering • QoS (Quality of Service) for TCP/UDP port numbers (L4) Multicast Filtering Multicast filtering transfers multicast packets to the specific nodes only. This function is implemented in the switching hub as IGMP Snooping or GMRP.
Section 2-3 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 communications that will be performed in the network or the kind of switching hub that you want to use. Refer to the following precautions when selecting a switching hub. Refer to 10-2 Adjusting the Communications Load to estimate the communications load for tag data links.
Selecting the Network Devices L3 Switching Hub with Multicast Filtering and L4 QoS Functions Section 2-3 We recommend this kind of switching hub when both tag data links and message communications are executed. By setting tag data links for higher-priority transmission, it is possible to prevent problems such as transmission delays due to message communications traffic and packet losses due to buffer overflow.
Selecting the Network Devices 32 Section 2-3
SECTION 3 Installation and Initial Setup This section explains how to install and make the initial settings required for operation of the EtherNet/IP Unit or built-in EtherNet/IP port. 3-1 3-2 3-3 3-4 3-5 3-6 Overview of Initial Setup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3-1-1 Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Switch Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of Initial Setup Procedures 3-1 3-1-1 Section 3-1 Overview of Initial Setup Procedures Procedures Initial Settings 1,2,3... 1. Set the unit number and node address with the switches on the front of the EtherNet/IP Unit or, for the built-in EtherNet/IP port, on the front of the CPU Unit. Refer to 3-2 Switch Settings. 2. Mount the Unit in the CPU Rack.
Overview of Initial Setup Procedures Section 3-1 9. Test communications. Send a PING command to the EtherNet/IP Unit or built-in EtherNet/IP port. Refer to 3-11 Communications Test. Settings Required for Tag Data Link Service (Cyclic Communications) 1.
Section 3-2 Switch Settings 3-2 3-2-1 Switch Settings CS-series EtherNet/IP Units Setting the Unit Number The unit number is used to identify individual CPU Bus Units when more than one CPU Bus Unit is mounted to the same PLC. Use a small screwdriver to make the setting, taking care not to damage the rotary switch. The unit number is factory-set to 0. UNIT No. Note Setting range: 0 to F (1) Turn OFF the power supply before setting the unit number.
Section 3-2 Switch Settings 3-2-2 CJ-series EtherNet/IP Units and CJ2 Built-in EtherNet/IP Port Setting the Unit Number The unit number is used to identify individual CPU Bus Units when more than one CPU Bus Unit is mounted to the same PLC. Use a small screwdriver to make the setting, taking care not to damage the rotary switch. The unit number is factory-set to 0. UNIT No. Note Setting range: 0 to F (1) Turn OFF the power supply before setting the unit number.
Section 3-3 Mounting to a PLC 3-3 3-3-1 Mounting to a PLC Mounting to a CS-series PLC EtherNet/IP Units can be mounted to any slot in a CS-series CPU Rack or a CS-series Expansion CPU Rack, but the number of slots to which they can be mounted depends on the Backplane. Up to four EtherNet/IP Units can be mounted to a single PLC. If it is mounted in combination with other CPU Bus Units (e.g., Controller Link Units), the maximum total number of CPU Bus Units that can be mounted is 8.
Section 3-3 Mounting to a PLC CPU Rack 10 Units max. End cover P C I S P C U Expansion Backplane 10 Units max. End cover P I S I Up to eight EtherNet/IP Units can be mounted. Expansion Backplane 10 Units max. End cover P I S I Expansion Backplane 10 Units max. End cover P I S I 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 410 mA.
Section 3-3 Mounting to a PLC 3. When removing the Unit, first loosen the screw at the bottom of the Unit. Fixing screws Note When mounting the Unit, provide the clearance shown below to facilitate easy mounting or dismounting. Duct 20 mm min. Backplane 20 mm min. Duct Phillips screwdriver 3-3-4 Handling Precautions • Always turn OFF the power supply to the PLC before mounting or dismounting a Unit or connecting or disconnecting cables.
Section 3-4 Network Installation 3-4 3-4-1 Network Installation Basic Installation Precautions • Take the greatest care when installing the Ethernet System, being sure to follow ISO 8802-3 specifications. You must obtain a copy of these specifications and be sure you understand them before attempting to install an Ethernet System. Unless you are already experienced in installing communications systems, we strongly recommend that you employ a professional to install your system.
Section 3-4 Network Installation • Press the cable connector in firmly until it locks into place at both the switching hub and the EtherNet/IP Unit. • Do not lay the twisted-pair cable together with high-voltage lines. • Do not lay the twisted-pair cable near devices that generate noise. • Do not lay the twisted-pair cable in locations subject to high temperatures or high humidity. • Do not lay the twisted-pair cable in locations subject to excessive dirt and dust or to oil mist or other contaminants.
Section 3-4 Network Installation Switching hub setting Autonegotiation 100 Mbps Full duplex (fixed) Half duplex --OK EtherNet/IP Unit setting 10 Mbps (fixed) 100 Mbps (fixed) Full Half Full Half duplex duplex duplex duplex ----Best --------OK Note Best = Recommended; OK = Allowed; --- = Not allowed.
Section 3-5 Connecting to the Network 3-5 3-5-1 Connecting to the Network Ethernet Connectors The following standards and specifications apply to the connectors for the Ethernet twisted-pair cable. • Electrical specifications: Conforming to IEEE802.3 standards. • Connector structure: Connector pin 1 2 3 4 5 6 7 8 Hood 3-5-2 RJ45 8-pin Modular Connector (conforming to ISO 8877) Signal name Transmission data + Transmission data – Reception data + Not used. Not used. Reception data – Not used. Not used.
Section 3-5 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.
Section 3-6 Creating I/O Tables 3-6 3-6-1 Creating I/O Tables I/O Table Overview I/O tables are used to identify Units mounted to the PLC, and to allocate I/O to them. With CS-series and CJ-series PLCs, whenever there is a change to the Unit configuration it is necessary to create I/O tables and register the mounted Units in the CPU Unit. The I/O tables can be created in the following ways. • Using the CX-Programmer offline.
Section 3-6 Creating I/O Tables (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. Initial screen SHIFT CH *DM 000000 I/O TBL ? CHG 000000 I/O TBL WRIT ???? WRITE Password 000000CPU BU ST? 0:CLR 1:KEEP or (Save or clear the CPU Bus Unit System Setup.
Creating I/O Tables Section 3-6 2. The Direct Online Dialog Box will be displayed. Select a serial connection, select the name of the applicable computer serial port, and then press the Connect Button. 3. If the connection process is successful, the system will be connected online. Here, check the operating mode of the PLC. If the operating mode is not PROGRAM mode, change the mode by selecting PLC − Operating Mode − Program from the menus. 4.
Section 3-6 Creating I/O Tables 5. The EtherNet/IP Unit will be displayed at the position it is mounted in the PLC. Note If it is not displayed, select Options − Transfer from PLC from the menus. Note Creating I/O tables is not required if the built-in EtherNet/IP port of a CJ2 CPU Unit is used. It is registered as a built-in port/Inner Board with a model number of CJ2B-EIP21 for the CJ2H and a model number of CJ2M-EIP21 for the CJ2M. You cannot delete a built-in port from the I/O tables.
Section 3-7 Setting the Local IP Address 3-7 Setting the Local IP Address This section describes the 3 ways to set the local I/O address of an EtherNet/ IP Unit or built-in EtherNet/IP port. Method 1: Using the default IP address: The default IP address is 192.168.250.Node_address. (The node address is set with the rotary switches on the front of the EtherNet/IP Unit or, for the built-in EtherNet/IP port, on the front of the CPU Unit.
Section 3-7 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). The IP address can be written in the two IP Address Display/Setting Area words using the CX-Programmer or the Programming Console.
Section 3-8 TCP/IP and Link Settings 3-8 TCP/IP and Link Settings This section describes the TCP/IP-related settings, such as the local IP address and subnet mask for the EtherNet/IP Unit or built-in EtherNet/IP port. Use the CX-Programmer to make these settings. The settings are stored in non-volatile memory in the Unit. Note 3-8-1 Unlike the Ethernet Units, the TCP/IP settings of the EtherNet/IP Unit and built-in EtherNet/IP port are not stored in the CPU Unit’s CPU Bus Unit System Setup Area.
Section 3-8 TCP/IP and Link Settings 4. Place the CX-Programmer online with the PLC and transfer the settings to the EtherNet/IP Unit or built-in EtherNet/IP port. 5. After transferring the settings, a message will ask if you want to restart the EtherNet/IP Unit or built-in EtherNet/IP port. The Unit/port must be restarted to enable the settings. 6. Check the 7-segment display for the EtherNet/IP Unit or built-in EtherNet/ IP port. 7.
Section 3-8 TCP/IP and Link Settings IP Address Sets the local IP address of the EtherNet/IP Unit or built-in EtherNet/IP port. Set the local IP address on the TCP/IP Tab Page when not setting the IP address in the CPU Unit’s allocated DM Area or using the default IP address (default IP address = 192.168.250.Node_address). When the IP address is set on the TCP/IP Tab Page, it will be stored as the IP address in the DM Area words allocated to the Unit/port as a CPU Bus Unit.
Section 3-8 TCP/IP and Link Settings functions that require a DNS server, so these settings are not used. (The functionality required to use a DNS server is not provided on EtherNet/IP Units with unit version 1.0. The DNS server cannot be used with these Units.) Domain Name Sets the domain name of the domain to which the EtherNet/IP Unit or built-in EtherNet/IP port belongs. The EtherNet/IP Unit or built-in EtherNet/IP port does not use a domain name in actual communications.
TCP/IP and Link Settings Section 3-8 2. Select Tools - Setup TCP/IP Configuration to display the following Setup TCP/IP Configuration Dialog Box, and set the TCP/IP Configuration for the target device. In the following example, the settings are all at their default values. 3. Enter the IP address to set and press the Get from the Device Button. The present setting will be obtained. Change the IP address in the New Configuration Box if required. 4. Press the Set to the Device Button.
Section 3-9 Tag Data Link Parameters Configurator, connect the devices one at a time, and download the TCP/ IP Configuration’s IP address parameters. If TCP/IP parameters are set for the EtherNet/IP Unit or built-in EtherNet/IP port from the Network Configurator, the EtherNet/IP Unit may automatically be reset and restarted. Before setting the TCP/IP parameters, make sure that no system problems will occur when the Unit is restarted.
Section 3-9 Tag Data Link Parameters The following method can be used to easily set the data links shown in the following figure using a wizard in the EtherNet/IP Datalink Tool. Node #1: CJ1H-CPU67H (IP address: 192.168.250.1) Node #2: CJ1H-CPU67H (IP address: 192.168.250.2) Node #3: CJ1H-CPU67H (IP address: 192.168.250.
Tag Data Link Parameters Section 3-9 3. Select Datalink − Wizard from the menus in the Datalink Tool when it has started. 4. In the Datalink Wizard Dialog Box, enter 50 words starting from memory address W000 for area 1 and 100 words starting from D00050 for area 2, and then press the OK Button. 5. The data link settings will be automatically created in the window of the EtherNet/IP Datalink Tool. Select File − Save to end. The settings will be saved in the Network Configurator.
Tag Data Link Parameters Section 3-9 6. In the Device Configuration Window of the Network Configurator, a mark will be added to each EtherNet/IP Unit to show that data links have been set. 7. Connect the Network Configurator to the EtherNet/IP network and select Network − Download from the menus. The data link settings will be downloaded to the EtherNet/IP Units, and the data links will operate.
Section 3-10 Other Parameters 3-10 Other Parameters In addition to the tag data link parameters, the EtherNet/IP Unit and built-in EtherNet/IP port also have the following communications and operation parameters. • FINS/UDP • FINS/TCP • FTP • Auto Adjust Time • Status Area • SNMP • SNMP Trap These parameters are set as Unit Setup from the CX-Programmer. The parameter settings are saved in flash memory in the EtherNet/IP Unit or CPU Unit. (See note.
Section 3-10 Other Parameters Using FINS/TCP Tab Page in Edit Setting Parameters Dialog Box FINS/TCP FINS/TCP Port FINS/TCP Connection Setup Protection Setting Function Specifies the local TCP port number to use in the FINS communications service. The TCP uses the TCP port number to distinguish the application layer (FINS communications service in this case). • Default value (9,600) • User-set value (1 to 65,535) This is the network API used when TCP is used for the FINS communications service.
Section 3-10 Other Parameters Using the Automatic Time Adjustment Tab Page in Edit Setting Parameters Dialog Box Auto Adjust Time Not get the time information from the SNTP server or Get the time information from the SNTP server Auto Adjust time Function Specifies whether to set the clock in the CPU Unit to the time on the SNTP server. The time can be set only in CPU Units with an EtherNet/IP Unit or a built-in EtherNet/IP port.
Section 3-10 Other Parameters Using SNMP Tab Page in Edit Setting Function Parameters Dialog Box SNMP Not use SNMP service or Specifies whether to use the SNMP. Use SNMP service If not using the SNMP service is specified, an SNMP manager will not be able to connected from an external device. SNMP Port Sets the port number to use when connecting from an SNMP manager. It is normally not necessary to change this setting. SNMP Contact Informa- Specifies the contact information as text.
Section 3-11 Communications Test 3-11 Communications Test If the basic settings (in particular the IP address and subnet mask) have been made correctly for the EtherNet/IP Unit or built-in EtherNet/IP port, then it should be possible to communicate with nodes on the EtherNet/IP network. This section describes how to use the PING command to test communications with the EtherNet/IP Unit or built-in EtherNet/IP port.
Section 3-11 Communications Test Application Example In this example, a PING command is sent to the node at IP address 130.25.36.8. The “$” in the example represents the host computer prompt. Normal Execution $ ping 130.25.36.8 ← Executes the PING command. PING 130.25.36.8: 56 data bytes 64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms 64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms : : : : : 64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms ← Press the Ctrl+C Keys to cancel execution. ---- 130.25.36.
SECTION 4 Memory Allocations This section describes the words allocated in the CIO Area and the DM Area for EtherNet/IP Units or built-in EtherNet/IP ports. 4-1 4-2 4-3 4-4 4-5 Overview of Memory Allocated to the EtherNet/IP Unit . . . . . . . . . . . . . . . . 68 CIO Area Allocations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4-2-1 Overview of the Allocated CIO Area Words . . . . . . . . . . . . . . . . . .
Overview of Memory Allocated to the EtherNet/IP Unit 4-1 Section 4-1 Overview of Memory Allocated to the EtherNet/IP Unit The following CPU Unit words are allocated to the EtherNet/IP Unit or built-in EtherNet/IP port. • CPU Unit’s allocated CIO Area words Contains software switch and status information. • CPU Unit’s allocated DM Area words Contains the IP Address Display/Setting Area • CPU Unit’s user settings area Contains status information.
Section 4-1 Overview of Memory Allocated to the EtherNet/IP Unit CPU Unit EtherNet/IP Unit ● Allocated CIO Area words (Allocated to the Unit as a CPU Bus Unit.
Section 4-2 CIO Area Allocations 4-2 CIO Area Allocations 4-2-1 Overview of the Allocated CIO Area Words The various kinds of data are stored in the allocated CIO Area words, which are identified by the offset from the beginning word (n) allocated to each Unit. There are two patterns for the layout of the allocated CIO Area words: the default settings and user settings. The layout can be selected in the Status Area settings in the Edit Parameters Dialog Box from the CX-Programmer.
Section 4-2 CIO Area Allocations User Settings Offset Bit 15 8 7 0 Data direction Unit control bits CPU Unit → EtherNet/IP Unit (Reserved) EtherNet/IP Unit → CPU Unit n+10 Unit status 1 EtherNet/IP Unit → CPU Unit 11 n+11 Unit status 2 12 n+12 Communications status 1 13 n+13 Communications status 2 14 n+14 Communications status 3 15 n+15 (Reserved) EtherNet/IP Unit → CPU Unit 16 n+16 17 n+17 18 n+18 19 n+19 20 n+20 21 n+21 22 n+22 23 n+23 24 n+24 FINS/TCP Conne
Section 4-2 CIO Area Allocations Bit 3 4 5 6 to 15 Tag Data Link Start Bit (Bit 2) Switch (Not used.) Tag Data Link Stop Bit Adjust Clock Bit (Not used.) Status Manipulated by --ON --User OFF Unit ON User OFF Unit --- --- Unit operation --The tag data link stops when this bit is switched from OFF to ON. Turned OFF by Unit after the tag data link stops operating. The clock time is automatically adjusted when this bit is switched from OFF to ON.
Section 4-2 CIO Area Allocations 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 n+2 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 n+3 n+4 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 n+5 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 Bit --- Target Node PLC Error Information (EtherNet/IP Unit to CPU Unit) (n + 6 to n + 9) Name Status Target Node PLC Operating Flags ON Manipulated by U
Section 4-2 CIO Area Allocations Bit 74 Name 0 Unit Error Occurred 1 Network Error Occurred 2 to 3 4 (Not used) Unit Memory Error 5 Communications Controller Error 6 IP Address Duplication Error 7 to 8 9 (Not used) Link OFF Error Status Manipulated Unit operation by ON Unit Indicates that an error occurred that is related to EtherNet/IP Unit operation. This flag is turned ON when any bit in Unit Status 1 is ON. (Bits 1 to 15 are logically ORed.
Section 4-2 CIO Area Allocations Bit Name 10 to 13 14 (Not used) Status Area Layout Setting Error 15 Unit Status 2 (EtherNet/IP Unit to CPU Unit) (n + 11) Status Manipulated by ------- (Not used) 15 14 13 12 11 10 9 8 7 ON Unit OFF Unit --- --- 6 5 4 3 Unit operation Indicates that there was an error in the allocated CIO Area’s layout settings. When this error occurs, the allocated CIO Area layout is set to the default pattern.
Section 4-2 CIO Area Allocations Bit 1 2 Name Tag Data Link Operating ON Unit OFF Unit ON Unit OFF Unit --ON --Unit OFF Unit (Not used) --- --- Multiple Switches ON Error ON Unit OFF Unit Operating IP Address Change 3 to 10 (Not used) 11 User Setting Area Enabled 12 to 13 14 76 Status Manipulated by Unit operation Indicates that the tag data link is operating. Turned OFF when communications stop in the following cases.
Section 4-2 CIO Area Allocations Bit Name 15 Communications Status 1 (EtherNet/IP Unit to CPU Unit) (n + 12) Status Manipulated by Error Log Stored ON Unit OFF Unit Unit operation Indicates that an error record is registered in the error log. Indicates that no error records are registered in the error log. Also turned OFF when an error log clear request is received. Word n+12 contains status flags related to the tag data links, as shown in the following diagram.
Section 4-2 CIO Area Allocations Bit 4 5 6 Name Invalid Communications Parameter Tag Refresh Error Tag Database Error 7 to 13 (Not used) 14 All Tag Data Links Operating 15 78 Tag Data Links Operating Status Manipulated by ON Unit OFF Unit ON Unit OFF Unit ON Unit OFF Unit --ON --Unit OFF Unit ON Unit OFF Unit Unit operation ON when there was an error in the validation check of tag data link parameters stored in the Unit’s non-volatile memory, and a checksum error occurred.
CIO Area Allocations Section 4-2 Communications Status 2 (EtherNet/IP Unit to CPU Unit) (n + 13) Word n+13 contains status flags related to the Ethernet, as shown in the following diagram. 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 n+13 Link Status Bit FTP Status Name 0 Status Manipulated Unit operation by ON Unit ON when the FTP server is operating (i.e., when there is an FTP client connection). OFF Unit OFF when the FTP is on standby (i.e., waiting for a client connection).
Section 4-2 CIO Area Allocations Bit 4 5 6 7 to 8 9 10 Registered Target Node Table (EtherNet/IP Unit to CPU Unit) (n + 16 to n + 19) 80 Name IP Router Table Error Status Manipulated by ON Unit OFF Unit (Not used) --Routing Table Error ON (Not used) Ethernet Expansion Settings Error BOOTP Server Error 11 to 13 14 (Not used) 15 Non-volatile Memory Error --Unit OFF Unit --ON --Unit OFF Unit ON Unit OFF Unit --- --- Address Mismatch ON Unit OFF Unit ON Unit OFF Unit Unit
Section 4-2 CIO Area Allocations 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 n+16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 n+17 n+18 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 n+19 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 Bit --- Normal Target Node Table (EtherNet/IP Unit to CPU Unit) (n+20 to n+23) Name Status Registered Target Node Flags ON Manipulated by Unit OFF
Section 4-2 CIO Area Allocations Bit 14 15 82 Name FINS/TCP Connection 15 FINS/TCP Connection 16 Status ON Manipulated by Unit OFF Unit ON Unit OFF Unit 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. Turned OFF by the Unit when the connection is terminated.
Section 4-3 DM Area Allocations 4-3 4-3-1 DM Area Allocations Overview of the Allocated DM Area Words The various kinds of data are stored in the offset positions shown in the following diagram, from the beginning word in the area for each Unit.
Section 4-3 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. • IP addresses where all network number bits are 0 or 1. • IP addresses where all host number bits are 0 or 1. • IP addresses where all subnet number bits are 1. • IP addresses that start with 127 (7F hexadecimal, e.g., 127.35.21.16).
Section 4-4 User Settings Area 4-4 4-4-1 User Settings Area Overview of the User Settings Area When the layout of the allocated CIO Area words is set to user settings, the user settings area can be used in addition to the allocated CIO Area words and allocated DM Area words. The beginning word of the user settings area can be set in the Status Area Tab Page in the Edit Parameters Dialog Box of the CX-Programmer.
Section 4-4 User Settings Area Normal Target Node Table (EtherNet/IP Unit to CPU Unit) These flags indicate the connection status of the target nodes. With revision 2 or higher, the flag turns ON after all data for multiple connections for individual target devices is refreshed in the CPU Unit. With revision 1, each flag immediately turns ON when all connections are established.
Section 4-4 User Settings Area 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 +32 +33 +34 +35 +36 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 +37 +38 +39 +40 +41 +42 +43 +44 +45 +46 +47 95 94 93 92 91 90 89 88 87 86 85 84 83
Section 4-5 Auxiliary Area Data 4-5 Auxiliary Area Data The following table and descriptions cover the words and bits in the CPU Unit’s Auxiliary Area that are related to the EtherNet/IP Unit. 4-5-1 Read-only Bits/Words Word(s) Bit(s) A202 A20200 to A20207 Name Communications Port Enabled Flags Function Bits A20200 to A20207 turn ON when a network instruction (SEND, RECV, CMND, or PMCR) can be executed with the corresponding port number. Bits 00 to 07 correspond to communications ports 0 to 7.
Section 4-5 Auxiliary Area Data Word(s) Bit(s) A417 A41700 to A41715 A427 A42700 to A42715 4-5-2 Word A501 Name Function CPU Bus Unit Error, When an error occurs in a data exchange between Unit Number Flags the CPU Unit and a CPU Bus Unit, the CPU Bus Unit Error Flag (A40207) and the corresponding flag in A417 are turned ON. Bits 00 to 15 correspond to unit numbers 0 to F. The ERR/ALM indicator on the front of the CPU Unit will flash, but CPU operation will continue.
Auxiliary Area Data 90 Section 4-5
SECTION 5 Determining IP Addresses This section explains how to manage and use IP addresses. 5-1 5-2 5-3 IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5-1-1 IP Address Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5-1-2 Allocating IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 5-1-3 EtherNet/IP Unit IP Address Settings. . . . . . . . . . . . . . . . . .
Section 5-1 IP Addresses 5-1 5-1-1 IP Addresses IP Address Configuration IP addresses are made up of 32 bits of binary data divided into four 8-bit fields called octets. These four octets provide the network number (net ID) and host number (host ID). The network number identifies the network, and the host number identifies the node (or host) on the network.
Section 5-1 IP Addresses 5-1-3 EtherNet/IP Unit IP Address Settings An IP address must be set even for the EtherNet/IP Unit or built-in EtherNet/IP port before Ethernet communications can proceed. Use one of the following methods to set the IP address of the EtherNet/IP Unit or built-in EtherNet/IP port.
Section 5-2 IP Addresses in FINS Communications 5-1-5 CIDR CIDR, or classless interdomain routing, is used to assign IP addresses that do not use classes. IP addresses that use classes are separated into blocks according to net IDs and host IDs, resulting in inefficient usage of IP address space. CIDR does not use classes, so IP address space can be divided as required to more efficiently use IP address space.
Section 5-2 IP Addresses in FINS Communications Pairing IP Addresses with FINS Node Addresses at Local Nodes • Ethernet address: A fixed number is assigned to each EtherNet/IP Unit or built-in EtherNet/IP port and it cannot be changed. • IP address: Use the default IP address (192.168.250.FINS_node number), set the address in the allocated DM Area words, or set the address on the TCP/IP Tab Page of the Edit Parameters Dialog Box from the CX-Programmer. • FINS/UDP port No.
Section 5-2 IP Addresses in FINS Communications FINS data FINS header Internal table Remote FINS node number 1 2 ! ! ! 254 Remote IP address (Example) Connection Remote port number (Example) 192.168.250.1 192.168.250.2 UDP UDP 9600 9600 192.168.250.
Section 5-2 IP Addresses in FINS Communications Automatic Generation (Static) With the static method as well, the following values are set for addresses in the internal table when the EtherNet/IP Unit or built-in EtherNet/IP port is turned ON or restarted.
Section 5-2 IP Addresses in FINS Communications Example When FINS Command is Sent FINS node number IP address table Node number in IP address table FINS node number 18 20 153.214.0.62 153.214.0.129 23 153.218.51.8 IP address IP address 153.214.0.129 FINS command sent When FINS Command is Received FINS node number Node number not in IP address table Internal table 25 153.218.51.10 Changed Combined Method IP address 153.218.51.
Section 5-2 IP Addresses in FINS Communications Example When FINS Command is Sent FINS node number IP address table FINS node IP address number Node number in 18 153.214.0.62 IP address table 20 153.214.0.129 23 153.218.51.8 Node number not in IP address table Network number: xx.xx.00.00 + FINS node number: xx Automatic generation method IP address FINS command sent IP address (See note.
IP Addresses in FINS Communications Section 5-2 Note If the ETN11-compatible mode is used, the internal table will retain the same content from when it was created after the EtherNet/IP Unit was turned ON or restarted. This feature provides protection from access via FINS/UDP from computers that dynamically change their IP address.
Section 5-2 IP Addresses in FINS Communications ■ 1,2,3... Local Device: FINS/TCP Server 1. A request to open a connection is received in TCP/IP protocol from the remote device (i.e., the client, either a personal computer, an EtherNet/IP Unit or built-in EtherNet/IP port), and the connection is established. 2. Notification is received from the remote node (i.e., the client) of the remote node's FINS node address. 3. The local device provides notification of the local FINS node address. 4.
Section 5-2 IP Addresses in FINS Communications 2. Set IP addresses for the devices to be connected. Set the IP address for the remote EtherNet/IP Unit or built-in EtherNet/IP port (i.e., the server) connected by FINS/TCP. This setting must be made if this EtherNet/IP Unit will be used as a FINS/ TCP client.
Section 5-2 IP Addresses in FINS Communications server whenever the system is started. Therefore, at a personal computer using the DHCP service, IP addresses may be different with each system startup. DHCP service is mainly used for automatic settings in devices such as personal computers that are used for client applications. Nodes used for server applications, such as mail servers, are normally allocated fixed IP addresses.
Section 5-2 IP Addresses in FINS Communications Product Programmable Terminal Open Network Controller (ONC) Model/Series/ Version NS Series --- Supports automatic generation method (dynamic)? No: Set manually so that automatic settings can be used with the automatic generation method.
Section 5-2 IP Addresses in FINS Communications Models that Can Use the Combined Method Product CS-series Ethernet Unit CJ-series Ethernet Unit CV/CVM1-series Ethernet Unit FinsGateway 100BASE-TX 10BASE-5 10BASE-T 100BASE-TX 10BASE-T 10BASE-5 Programmable Terminal Open Network Controller (ONC) 5-2-5 Model/Series/ Version CS1W-ETN21 CS1W-ETN01 CS1W-ETN11 CJ1W-ETN21 CJ1W-ETN11 CV500-ETN01 Supports combined method? Yes No No Yes No No Version 4.
Section 5-3 Private and Global Addresses 5-3 5-3-1 Private and Global Addresses Private and Global Addresses There are two kinds of IP addresses, private and global. • Global addresses: These are IP addresses that connect directly to the Internet. Allocated by application to NIC, each address is unique in the world, and as many as 4.3 million can be allocated worldwide. • Private addresses: These are IP addresses for Intranet (LAN) use, and cannot connect directly to the Internet.
Section 5-3 Private and Global Addresses 5-3-2 Using a Private Address for the EtherNet/IP Unit Intranet FINS/TCP client computer with CX-Programmer, etc. or CIP client computer with Network Configurator, etc. FINS communications, Explicit messages Ethernet (EtherNet/IP) Communications in intranet Firewall PLC IP router EtherNet/IP Unit: Private address Internet Intranet FINS/TCP client computer with CX-Programmer, etc. or CIP client computer with Network Configurator, etc.
Section 5-3 Private and Global Addresses • With FINS/UDP, when the IP address (private address) of a computer serving as a DHCP client is changed, the IP address conversion method of the EtherNet/IP Unit or built-in EtherNet/IP port will be the automatic generation method (dynamic), the combined method, or the IP address table method. When FINS/TCP is used, IP addresses can be changed automatically.
Section 5-3 Private and Global Addresses 5-3-3 EtherNet/IP Unit with a Global Address Intranet FINS/TCP client computer with CX-Programmer, etc. or CIP client computer with Network Configurator, etc.
Private and Global Addresses Section 5-3 • If the TCP port number (44818) or UDP port number (44818) that is used for EtherNet/IP cannot be used if prohibited by a firewall in the communications path. Note Network Security and Firewalls Setting a global IP address for an EtherNet/IP Unit or built-in EtherNet/IP port involves network security considerations.
SECTION 6 Tag Data Link Functions This section describes tag data link functions and related Network Configurator operations. 6-1 6-2 6-3 Overview of Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6-1-1 Tag Data Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 6-1-2 Overview of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 6-1 Overview of Tag Data Links 6-1 6-1-1 Overview of Tag Data Links Tag Data Links Tag data links enable cyclic data exchanges on an EtherNet/IP network between PLCs or between PLCs and another device. I/O memory addresses (e.g., in the CIO or DM Area) and symbols can be assigned to tags. The settings for tag data links are made using the Network Configurator. Refer to 6-2 Setting Tag Data Links for information on how to make the settings.
Section 6-1 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.
Section 6-1 Overview of Tag Data Links 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.1 192.168.250.254 Tagset _in1 Tagset _in2 Tagset_in128 CN.1 Tagset_out Tagset_in CN.2 CN.129 : 192.168.250.2 Tagset_out CN.128 CN.130 Tagset_out25 4 Tagset_in : : The maximum number of connections for node 192.168.250.254 is 32 for the CJ2M and 256 for other CPU Units.
Section 6-1 Overview of Tag Data Links If multicast connections are used, however, use a switching hub that has multicast 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.
Section 6-1 Overview of Tag Data Links Item Connection type Specification Each connection can be set for 1-to-1 (unicast) or 1-to-N (multicast) communications. (Default: Multicast) Packet interval (RPI) 1 to 10,000 ms for CJ2M and 0.5 to 10,000 ms for other CPU Units (in 0.5-ms units) The packet interval can be set separately for each connection.
Section 6-1 Overview of Tag Data Links Target device Originator device IP address: # Connection Information · Target IP address: # · Originator tag set: SP1_IN · Target tag set: SP1_OUT · Packet interval (RPI) Tag Set (Output Tags) Tag Set (Input Tags) Tag set name: SP1_IN Tag set name: SP1_OUT PLC status PLC status Tag a Tag i Connection Tag ii Tag b Tag c Tag g EtherNet/IP There are both input and output tag sets. Each tag set can contain only input tags or only output tags.
Section 6-1 Overview of Tag Data Links CPU Unit CPU Unit Tag set SP1_IN (group of tags a, b, and c) I/O memory One tag each (Each tag is set using a text string of the network symbol or I/O memory address.
Section 6-1 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. The following example shows the relationship between the Target Node PLC Operating Flag location and target ID of the target node with 192.168.250.2.
Section 6-1 Overview of Tag Data Links The following table shows the operation of each the bits when multiple connections are used to communicate with a node, and the PLC status is specified in all of the connections. Name (allocated area) Target Node PLC Operating Flag Information Layout set to default settings: Words n+2 to n+5 Layout set to user settings: Words n+32 to n+47 Note Corresponds to the PLC status’s PLC Operating Flag.
Section 6-2 Setting Tag Data Links 6-2 6-2-1 Setting Tag Data Links Starting the Network Configurator Procedure Tag data links are set by using the Network Configurator. Use the following procedure to start the Network Configurator. ■ Starting from the Windows Start Menu To start the Network configurator, select OMRON - CX-One - Network Configurator for EtherNet/IP - Network Configurator from the Windows Start Menu.
Section 6-2 Setting Tag Data Links When the Network Configurator starts, the following window will be displayed. Main Window The Main Window consists of a Hardware List and a Network Configuration Window, as shown in the following diagram. Hardware List: Displays the devices that can be added to the network. 122 Network Configuration Window: Displays the layout and network configuration of devices that are set and monitored.
Setting Tag Data Links Section 6-2 When two or more networks are being managed, a new Network Configuration Window can be added by selecting Network - Add. To change the name displayed in the Network Tab Page, select Network Property. The name set in the Comment Field of the Network Property Window can be changed.
Section 6-2 Setting Tag Data Links 6-2-2 Tag Data Link Setting Procedure The section describes the procedure for setting tag data links (i.e., connection information). For data links between PLCs, the connection information is set only in the originator, i.e., the node that receives data. 1. Creating a Network Configuration Register all EtherNet/IP Units or built-in EtherNet/IP ports for which connections will be created in the EtherNet/IP Network Configuration Window.
Section 6-2 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 the devices from the Hardware List and dropping them in the Network Configuration Window.
Section 6-2 Setting Tag Data Links 3. Set the IP address to match the node address (IP address) actually being used in the device. 4. Repeat steps 1 to 3, and register all of the devices participating in the tag data links. 6-2-4 Creating Tags and Tag Sets Specifying I/O Memory Addresses The tag sets and set member tags required to create connections for a registered EtherNet/IP Unit must be created.
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).
Section 6-2 Setting Tag Data Links Creating and Adding Tags 3. Click the Edit Tags Button. The Edit Tags Dialog Box will be displayed. Register the input (consume) tags and output (produce) tags separately. 4. Click the In - Consume Tab, and click the New Button. The Edit Tag Dialog Box will be displayed. 5. In the Name Field, enter the character string for the CPU Unit's I/O memory address or a network symbol (e.g., 100, W100, D0, Input_signal). Addresses in the following I/O memory areas can be set.
Section 6-2 Setting Tag Data Links (b) Be sure to directly enter the CPU Unit's I/O memory address (e.g., 100, W100, D0) or a network symbol as a character string. 6. Input the size of the tag in the Size Field, in bytes. 7. Click the Regist Button to register the tag. If an I/O memory address is specified for a tag name, the Edit Tags Dialog Box will be displayed with the next consecutive address as the tag name for editing the next tag. Once you have registered the tags, click the Cancel Button. 8.
Setting Tag Data Links Section 6-2 9. When you are finished registering the required tags, click the OK Button at the bottom of the Edit Tags Dialog Box. 10. At this point, a confirmation dialog box will be displayed to check whether the registered tag names will registered without changes as tag sets. A tag set can contain up to 8 tags, but tag sets will be registered with one tag per tag set if the tags are registered as tag sets. In this case, the Yes Button is clicked to register one tag per tag set.
Setting Tag Data Links Changing and Registering Tag Sets Section 6-2 11. The following dialog box will be displayed when the tags in the Edit Tags Dialog Box are registered directly as tag sets. 12. If an input tag has already been registered in an input tag set, and you want to change its registration to a different input tag set, it is necessary to delete the tag from the tag set in which it was originally registered.
Section 6-2 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 Button.
Section 6-2 Setting Tag Data Links 13. In order to edit a registered tag set and add tags, either double-click the tag set, or select the tag set and click the Edit Button. The Edit Tag Set Dialog Box will be displayed. The Tag List on the left side of the dialog box shows the tags that are already registered, and the Candidate Tag List on the right side of the dialog box shows the other tags that have not been registered yet. To add a tag, select it in the Candidate Tag List and click the Button. 14.
Setting Tag Data Links Section 6-2 18. If you want to just add new tags and register the tag set, first register the tags with steps 1 to 9. In this example, input tags D00004 and D00005 have been newly added. 19. When you are finished registering the required tags, click the OK Button at the bottom of the Edit Tags Dialog Box. 20. At this point, a confirmation dialog box will be displayed to check whether the registered tag names will be registered without changes as tag sets.
Section 6-2 Setting Tag Data Links 21. To register the newly added tags in a tag set, either double-click the desired tag set, or select the tag set and click the Edit Button. The Tag List on the left side of the dialog box shows the tags that are already registered, and the Candidate Tag List on the right side of the dialog box shows the other tags that have not been registered yet. 22. Select the tags that you want to add from the Candidate Tag List and click the Button.
Setting Tag Data Links Section 6-2 2. Importing Network Symbols Created with the CX-Programmer to the Network Configurator If the CJ2H-CPU6@-EIP or CJ2M-CPU3@ is used, you can create network symbols using the CX-Programmer, import them into the Network Configurator, 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.
Setting Tag Data Links Section 6-2 A confirmation message will be displayed. Click the Yes Button. The symbols will be imported as shown below on the Tag Sets Tab Page. Each symbol will be imported into a different tag set and the device parameters will be automatically edited. (The symbol name will be used for the tag set name.
Setting Tag Data Links Section 6-2 To place more than one input symbol (input tag) imported from the CXProgrammer into one tag set, you must delete the input tags that were registered to separate input tag sets. Select the tag sets for the symbols that are included in the one tag set and click the Delete Button. A confirmation message will be displayed. Click the No Button to delete only the tag sets. To create a new tag set for more than one tag, click the New Button.
Section 6-2 Setting Tag Data Links 4. You can change tag set names in this dialog box. To confirm a change, click the OK Button in the dialog box. 5. Perform steps 1 to 3 for all the devices that will perform tag data links. 3. Importing Network Symbols That Were Registered to Tags with the Network Configurator to the CX-Programmer If the CJ2H-CPU6@-EIP or CJ2M-CPU3@ is used, you can specify network symbols for tags using the Network Configurator.
Section 6-2 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 CJ2MCPU3@, right-click and select Import Network Variable from the pop-up menu. 2. You can add a tag as a network symbol by selecting and executing the CSV file exported using the Network Configurator. Note The following precautions apply when importing. • Tags that have a specified I/O memory address cannot be imported.
Section 6-2 Setting Tag Data Links 6-2-5 Connection Settings After creating the tag sets, click the Connections Tab at the top of the Edit Device Parameters Dialog Box, and set the following connection information. • The target devices with which connections will be opened • Whether the tag sets are input or output tag sets • The length of the packet intervals (RPI) Make the Connections settings in the originator only. The Connections settings are not necessary in the target device.
Section 6-2 Setting Tag Data Links 3. In the Unregister Device List, select the target device that requires connection settings by clicking the device so its color changes to gray, and click the Button. The selected target device will be displayed in the Register Device List, as shown in the following diagram. 4. Target node IDs are assigned to devices registered in the Register Device List.
Section 6-2 Setting Tag Data Links 1,2,3... 1. Select the Connection Tab and then click the New Button. The following Edit Connection Dialog Box will be displayed according to the type of device that is selected.
Section 6-2 Setting Tag Data Links The settings are as follows: Item Description Connection I/O Type When creating tag data links for a CS1W-EIP21, CJ1W-EIP21, CJ2B-EIP21, or CJ2M-EIP21, select Input Only (Tag Type). When creating tag data links for other target devices, select the connection I/O type specified in that device’s EDS file. Use the Input Only (ID type) setting when another company's node is the originator and does not support connection settings with a Tag type setting.
Section 6-2 Setting Tag Data Links The following table describes the various settings in the dialog box. Setting Target Device Connection Name Connection I/O Type In/Out Target Variable Originator Variable Connection Type RPI Timeout Value Function Selects the target device. Any name can be given to the connection (up to 32 characters). If this field is left blank, a default name will be assigned. This Connection Name can be used for comments.
Section 6-2 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 in the Connections Tab Page. 2. Click the OK Button. The following kind of diagram will be displayed. Indicates the IP address of the originator where the connection was set. 3. Repeat the Connections setting procedure until all of the connections have been set.
Section 6-2 Setting Tag Data Links 4. If the tag set’s size is changed in either the originator or target after the connection was set, the size will not match the other node and a parameter data mismatch will occur. In this case, if the connection settings have been changed, be sure to check the connections. (Refer to 6-2-17 Checking Connections.
Section 6-2 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. Node A Output tag set: O_Signal Excluded characters: O_ and I_ Connection Node B Input tag set: I_Signal Node C Input tag set: I_Signal Connection EtherNet/IP 1,2,3... 1.
Section 6-2 Setting Tag Data Links Click the OK Button to start processing. 4. A device connection structure tree will be displayed when processing has been completed. 5. Use the device connection structure tree as required to change the RPI and timeout settings. Device Connection Structure Tree Connection settings can be displayed on the network configuration. Select View Device’s Connection Structure Tree from the Network Menu.
Section 6-2 Setting Tag Data Links • The Display the detail of Connection Check Box can be used to switch between device-level and connection-level displays of tag data link communications. • An asterisk will be displayed after the device name of the originator set for the connection. • The Edit Device Parameters Dialog Box can be displayed by selecting a connection and clicking the Edit Button. The connections can be edited in this dialog box.
Section 6-2 Setting Tag Data Links Node List The following items will be displayed in the Node Area on the left side of the window. • IP Address: The IP address of the node. • Device: The name (model number) of the device at the node. Note Data Link Table Information The node list will display the node registered in the Network Configurator. Nodes cannot be added or deleted from this window. The data link table of the node selected on the left will be displayed on the right.
Section 6-2 Setting Tag Data Links • Tag Set Name: If the Wizard is used, the names will be automatically assigned using consecutive IP addresses in the following form for both input and output tags: TagSet1_192168.250.1. There is no reason to be concerned with these names. If the Wizard is not used, then names will not be automatically assigned and they must be entered directly into the data link table. • Total Size: The total number of words in areas 1 and 2.
Setting Tag Data Links Section 6-2 2. Select the memory area (here, W) in the Memory Field and enter the starting address (here, 0) and number of words (here, 50) in the Start Address and Size Fields for Area 1. 3. Select the memory area (here, D) in the Memory Field and enter the starting address (here, 50) and number of words (here, 100) in the Start Address and Size Fields for Area 2. 4. Select the Enable Over Load Check Box if the Over Load function is necessary. 5. Click the OK Button.
Setting Tag Data Links Section 6-2 If the creating the data link table is continued, the data link table will be created with the same size of data link for all registered nodes. Examples are shown below. Automatic Allocation Results for Node 1 (IP Address: 192.168.250.1) Automatic Allocation Results for Node 2 (IP Address: 192.168.250.
Section 6-2 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 results will be displayed. a. Table Inconsistencies The following Check Result Dialog Box will be displayed. Correct the data link table according to the displayed information.
Section 6-2 Setting Tag Data Links b. No Table Inconsistencies The following message will be displayed. Click the OK Button. 7. Select Exit from the File Menu. The EtherNet/IP Datalink Tool will be exited and you’ll return to the Network Configurator. 8. Returning to the Network Configurator Click the icon for each device and check the settings made with the EtherNet/IP Datalink Tool in the Edit Device Parameters Dialog Box.
Section 6-2 Setting Tag Data Links The following dialog box will be displayed before the Wizard starts. Click the Yes Button to delete the connections that have been set with OMRON PLCs before starting the Wizard. 3. Create the connection following the instructions that are given by the Wizard after the Wizard starts. (See the following figure.) 4. A list of tag sets is displayed on the right side of the Wizard Dialog Box with target devices that support receiving input data.
Setting Tag Data Links Section 6-2 The following display will appear when you click the Show Detail Button. The specified values for detailed parameters will be displayed. Change the values as required. The connection name cannot be set. They are automatically created using the following rule. default_N (where N is a 3-digit number (001, 002, etc.) starting from 1) 5. Click the Next Button to switch to the table in the following Wizard Dialog Box.
Section 6-2 Setting Tag Data Links 6-2-8 Creating Connections by Device Dragging and Dropping You can create a connection to the originator by dragging a target device and dropping it at the originator device. Network Configurator version 3.10 or higher is required to drag and drop devices to make connections. Example: Drag the target device at 192.168.250.1 and drop it at the originator device at 192.168.250.100. Drag & Drop Note The EtherNet/IP originator device (i.e.
Section 6-2 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 selected. Select the connection I/O type according to your application. • The connection I/O types that can be selected depend on the target device.
Section 6-2 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. After you have set all of the connection, click the Regist Button to create the connection. When creating the connection has been completed, the input tag set and output tag set will be blank.
Section 6-2 Setting Tag Data Links The Network Configurator will connect to the EtherNet/IP network. If the Network Configurator is connected online properly, On-line will be displayed in the status bar at the bottom of the window. The network connection icon will be displayed in blue in the Network Tab Page in which the Network Configurator is connected. Network connection icon The connecting network can be switched by selecting Network - Change Connect Network.
Setting Tag Data Links Section 6-2 3. Input the EtherNet/IP Unit’s unit number in the Unit No. Field, select the connecting COM port number, and click the OK Button. Usually, the Baud Rate is left at this setting. The following dialog box will be displayed. 4. After clicking TCP:2, click the OK Button. The Network Configurator will be connected to the EtherNet/IP network. If the Network Configurator is connected online properly, On-line will be displayed in the status bar at the bottom of the window.
Section 6-2 Setting Tag Data Links 2. Select Network - Connect. The Setup Interface Dialog Box will be displayed. 3. Set the port type to either USB or serial. 4. Set the port to use and then click the OK Button. (Leave the baud rate at the default setting.) The following dialog box will be displayed. 5. Select the Backplane Icon and click the Refresh Button. The CPU Unit, CPU Bus Units, and Special I/O Units connected in the PLC will be displayed as shown below. 6.
Section 6-2 Setting Tag Data Links Select the TCP port of the EtherNet/IP Unit. 7. Select the port for the EtherNet/IP Unit and then click the OK Button. The Network Configurator will be connected to the EtherNet/IP network. If the Network Configurator goes online normally, “On-line” will be displayed in the status bar at the bottom of the window.
Section 6-2 Setting Tag Data Links 2. Select Network - Connect. The following Setup Interface Dialog Box will be displayed. 3. Click the Setup Button in the Setup Interface Dialog Box. The Registration of the connection Dialog Box will be displayed. Enter the network information for the connection destination, and then click the Add Button to register the settings. The registration information details are as follows: a. Registration name Enter any name. b.
Section 6-2 Setting Tag Data Links • Node address Last value in the IP address of the Unit above (e.g., 3 for 192.168.251.3) • Unit number of CPU Bus Unit Unit number of the Unit above d. Remote Information - Ethernet Unit Enter the information for the Ethernet Unit of the PLC that will be the relay node. 4. Once the settings have been registered, the Setup Interface Dialog Box will be displayed again. Check the registered information that has been entered, and then click the OK Button. 5.
Section 6-2 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 network. When the download operation is executed, the tag data link parameters will be transferred to the EtherNet/IP Units that require the settings.
Section 6-2 Setting Tag Data Links 1,2,3... 1. Connect the Network Configurator online. 2. There are two ways to download the parameters. • Downloading to All Devices in the Network Select Network - Download. The following dialog box will be displayed. • Downloading Individually to Particular Devices Select the icon of the EtherNet/IP Unit to which you want to download. To select multiple nodes, press and hold the Shift Key while selecting additional icons.
Section 6-2 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 returned to the previous setting after the parameters have been downloaded.
Section 6-2 Setting Tag Data Links If the operating mode of one or more CPU Units was changed to download the parameters, the CPU Units can be returned to the previous operating mode. If the No Button is clicked, the CPU Units will remain in PROGRAM mode. 4. The following dialog box will be displayed, indicating that the download was completed.
Section 6-2 Setting 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 additional 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 display the pop-up menu, and select Parameter - Upload. The following confirmation dialog box will be displayed. Click the Yes Button or No Button.
Section 6-2 Setting Tag Data Links Verifying the Network Configuration 1,2,3... Compare the list of registered devices in the Network Configuration Window with the devices connected on the EtherNet/IP network, and check the IP addresses and device types. This function cannot be used to verify device parameters. 1. Connect the Network Configurator to the network. 2. The following progress monitor will be displayed to show the progress as data is read from the network and compared. 3.
Section 6-2 Setting Tag Data Links Click the OK Button or the Close Button. Verifying the Device Parameters 1,2,3... Use the following procedure to compare the device parameters for the devices selected in the Network Configuration Window with those of the devices connected on the EtherNet/IP network. The IP addresses, device types, and device parameters are compared. 1. Connect the Network Configurator to the network. 2. Click the icon of the EtherNet/IP Unit that is to be verified.
Section 6-2 Setting Tag Data Links • Differences Found in the Device Type Click the OK Button or the Close Button. 5. If multiple nodes have been selected, the following message will be displayed. Click the Yes Button. The comparison results will be displayed in order of the selected nodes.
Section 6-2 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.
Section 6-2 Setting Tag Data Links 3. Select Device - Reset. The following dialog box will be displayed. • Clicking the Yes Button: The following dialog box will be displayed. Select one of the following options and click the OK Button. • Emulate cycling power Restarts the Unit. • Return to the out-of-box configuration, and then emulate cycling power Returns the Unit to its factory default settings, and restarts the Unit. • Clicking the No Button: The device parameters are not cleared or reset.
Section 6-2 Setting Tag Data Links The network configuration file save operation is complete. 3. When the network configuration is changed later, the existing network configuration file can be overwritten by selecting File - Save or clicking the Button. 4. You can select the Select target network Check Box in the Option Area to save a network configuration file with only the required networks. Select the check boxes of the networks to save and click the OK Button.
Section 6-2 Setting Tag Data Links 1,2,3... 1. Select File - Open or click the be displayed. Button. The following dialog box will If the network configuration file that you want to read is not displayed, change to (Look in) another folder. 2. When you click and select the network configuration file that you want to read, that file name will be displayed in the File name Field. 3. Click the Open Button to read the network configuration file. 4.
Section 6-2 Setting Tag Data Links 5. Select any of the options as necessary. The options are listed below. Option Select target network Add to current document Note Function Allows you to select specific networks from the network configuration and open them. Allows you to add the networks from the network configuration file being opened to the current configuration file. The save format will vary depending on the Network Configurator version. Configuration files (*.
Section 6-2 Setting Tag Data Links Icon (When normal: ) 6-2-18 Changing Devices Devices that are registered in a network configuration with the Network Configurator can be changed. Select Change Device from the Device Menu to display a list of the devices that can be changed to. Select the desired device. A device can be changed only when there is complete or upward compatibility with the device being changed to.
Section 6-2 Setting Tag Data Links Icon (gray) Status Offline 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 MONITOR 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.
Ladder Programming with Tag Data Links 6-3 6-3-1 Section 6-3 Ladder Programming with Tag Data Links Ladder Programming Related to Tag Data Links If data in the ladder program is linked by tag data links, add conditions 1 to 4 in the ladder program for that data. If you want to use target node PLC flags as input conditions, add conditions 5 and 6. For details on the various flags, refer to 4-2 CIO Area Allocations. Conditions showing the EtherNet/IP Unit’s Tag Data Links are enabled: 1.
Section 6-3 Ladder Programming with Tag Data Links Programming for Revision 2 or Higher Tag Data Link Operating Normal Target Node Flag 1 PLC Operating Flag 1 PLC Error Flag 1 Node 1 Data Link Normal Operation Flag n+11 bit 01 n+20 bit 01 n+2 bit 01 n+6 bit 01 Normal Target Node Flag 2 PLC Operating Flag 2 PLC Error Flag 2 Node 2 Data Link Normal Operation Flag n+20 bit 02 n+2 bit 02 n+6 bit 02 Programming for Revision 1 and Revision 2 Tag Data Link Operating All Tag Data Links Operating Nor
Section 6-3 Ladder Programming with Tag Data Links Programming for Revision 1 or Higher Tag Data Link Operating Unit Error Occurred DIFD 10000 n+11 bit 01 n+10 bit 00 Unit Error Occurred DIFU 10000 n+10 bit 00 10000 Release Flag Local node Error output Local node Error output Example of Programming to Process Data The following type of programming can be used to process data only when the data links are operating normally.
Ladder Programming with Tag Data Links Note 6-3-2 Section 6-3 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. Status Flags Related to Tag Data Links The status of the tag data links is reflected in the following words.
SECTION 7 Message Communications Functions This section describes message communications using FINS messages and explicit messages. 7-1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 7-2 FINS Message Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 7-3 Explicit Message Communications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 7-1 Overview 7-1 Overview The message communications functions send command/response messages between nodes on the Ethernet network. The messages can be sent between a computer and PLC, between two PLCs, between an OMRON PLC and a master made by another company, or between slaves. The messages can be used to send/receive data; read time data, error logs, and other data; or control operation, e.g., by force-setting/resetting bits.
Section 7-1 Overview Overall Structure CPU Unit CMND(490) instruction CMND(490) instruction (2810 Hex) EtherNet/IP Unit FINS message function FINS message FINS Explicit message Explicit message function OMRON special message communications Ethernet (EtherNet/IP) network FINS message EtherNet/IP message communications Explicit message Note With the EtherNet/IP Unit or built-in EtherNet/IP port, message communications are possible even if the I/O link function is disabled.
Section 7-2 FINS Message Communications 7-2 FINS Message Communications Messages containing FINS commands can be exchanged over the Ethernet network between nodes that support FINS messages. Note Type of FINS message Network communications instructions PLC to PLC (both must be CS/CJ-series PLCs with a CS/CJ-series EtherNet/IP Unit, built-in EtherNet/IP port, or Ethernet Units) (See note 1.
Section 7-2 FINS Message Communications Up to 8 network levels, including the EtherNet/IP network, can be crossed.
Explicit Message Communications 7-3 Section 7-3 Explicit Message Communications Explicit messages defined in EtherNet/IP can be used to send service requests to other companies’ EtherNet/IP masters/slaves and OMRON PLCs with CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports. Note Specific FINS commands (commands 2810 and 2801) are used to send explicit messages.
Message Communications Specifications 7-4 Section 7-4 Message Communications Specifications CPU Unit function Unit model number Communications Sending/ receiving instructions data FINS commands CS/CJ Series CS1W-EIP21, CJ1W-EIP21, CJ2H-CPU@@-EIP, or CJ2M-CPU3@ SEND and RECV instructions No.
Section 7-5 Message Communications Error Indications 7-5 Message Communications Error Indications There are two ways to obtain information on communications errors that occur in message communications: checking the EtherNet/IP Unit’s error log or checking its indicators. 1,2,3... 1. Each time a communications error occurs, an error code is placed in an error record in the error log stored in RAM in the EtherNet/IP Unit or CPU Unit with the built-in EtherNet/IP Port.
Section 7-6 Message Communications Errors 7-6 Message Communications Errors The following table shows the main errors that may occur when messages are sent or received. Refer to SECTION 14 Troubleshooting and Error Processing for corrective measures and details on errors that are recorded in error log but not indicated by the LED indicators.
Message Communications Errors 196 Section 7-6
SECTION 8 FINS Communications This section provides information on communicating on EtherNet/IP Systems and interconnected networks using FINS commands. The information provided in the section deals only with FINS communications in reference to EtherNet/IP Units or built-in EtherNet/IP ports. FINS commands issued from a PLC are sent via the SEND(090), RECV(098), and CMND(490) instructions programmed into the user ladder-diagram program.
Section 8-1 Overview of FINS Communications 8-1 8-1-1 Overview of FINS Communications Communications On an Ethernet Network The EtherNet/IP Units and built-in EtherNet/IP ports support the FINS communications service, which can be used simultaneously with the CIP communications service. FINS communications data is sent and received as UDP/IP packets or TCP/IP packets.
Section 8-1 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: • When remote devices do not support the FINS/TCP method: Use the FINS/UDP method for FINS communications with those devices. • When FINS nodes are connected on the same Ethernet segment: Use the FINS/UDP method between those nodes. Note FINS/UDP offers a slight advantage in performance.
Section 8-2 FINS/UDP Method 8-2 8-2-1 FINS/UDP Method 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 relationship and there is no clear connection. If using TCP is like making a telephone call, then UDP is more like delivering a memo by hand.
Section 8-2 FINS/UDP Method UDP Port Numbers for FINS/UDP The UDP port number is the number for UDP to identify the application layer (i.e., the FINS communications service in this case). When communications are executed by UDP/IP, this port number must be allocated to the communications service. The default setting for the UDP port number (i.e., the UDP port number of the EtherNet/IP Unit or built-in EtherNet/IP port) is 9600.
Section 8-3 FINS/TCP Method 8-3 8-3-1 FINS/TCP Method 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 virtual circuit, i.e., a connection. Once a connection has been established, communications are quite reliable.
Section 8-3 FINS/TCP Method • After a FINS/TCP connection (connection number, remote IP address) has been set in the FINS/TCP Tab Page of the Network Configurator’s Edit Parameters Dialog Box, it can be dynamically changed from the ladder program using a FINS command (i.e., FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST). FINS/TCP Frame Format The following diagram shows the structure of a TCP packet sent over an Ethernet network. Ethernet Ver.
Section 8-3 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 terminated by a communications error or a FINS command (i.e., FINS/TCP CONNECTION REMOTE NODE CHANGE REQUEST).
Section 8-3 FINS/TCP Method After a connection has been established as a FINS/TCP client, it can be terminated in the following ways. • If the connection is closed by the server. • If there is no response from the client when the keep-alive function is in effect. Even if the connection is closed at the FINS/TCP client, requests continue to be made to the FINS/TCP server every few seconds to open a connection.
FINS/TCP Method Section 8-3 • When routing tables are used for one or more other nodes on the same network It is not necessary to set routing tables if one Communications Unit is mounted to the PLC and the nodes are connected as one network. (2) If EtherNet/IP is selected for CX-Programmer communications, FINS message communications and remote programming/monitoring from the CX-Programmer will be possible as long as CIP routing is possible for the entire communications path.
Section 8-4 Routing Tables 8-4 Routing Tables When the FINS communications service is used, routing tables must be created in advance. Routing tables are required in the following circumstances. • When communicating with a PLC or computer on another network (e.g., remote programming or monitoring using FINS messages or a CX-Programmer) • When multiple Communications Units are mounted to a single PLC (i.e., CPU Unit). • When routing tables are used for one or more other nodes on the same network.
Section 8-4 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).
Section 8-4 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 multiple CPU Bus Units are mounted. Ethernet (EtherNet/IP) network Controller Link network (Network #A) (Network #B) PS: CPU: EIP: CLK: E C C P I L P S P K U Power Supply Unit CPU Unit EtherNet/IP Unit Controller Link Unit Unit #a Unit #b Local Network Table No.
Section 8-4 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 C L K E I P CE L I PLC KP 2 PLC 4 Unit #0 Node #1 C L K CPU Bus Unit No. 05 CPU Bus Unit No. 03 02 PLC #3 Routing Table (Local network table) Local No. network 1 010 2 030 3 CPU Bus Unit No. 04 07 PLC #4 Routing Table (Local network table) Local No. network 1 020 2 3 CPU Bus Unit No.
Section 8-5 Using FINS Applications 8-5 Using FINS Applications 8-5-1 CX-Programmer (CX-Server) The following examples show how to connect online from a CX-Programmer on an Ethernet network to a PLC on the Ethernet network. ■ System Configuration Example 1: No Routing In this example, an online connection is made by FINS/UDP to a PLC on an Ethernet network (PLC1 in the diagram below) from a CX-Programmer/CXIntegrator connected to the Ethernet network.
Section 8-5 Using FINS Applications Example: Inputs to the CX-Programmer's Setup Window Example: Change PLC Settings Example: Network Settings (Network Tab Page) Note 212 When FinsGateway is selected as the network type, make sure that the frame length is set to 2,000 bytes max.
Section 8-5 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. Conditions • FINS/UDP method • IP address conversion: Automatic generation method (dynamic) Controller Link Unit Node address: 1 IP address: 192.168.250.
Section 8-5 Using FINS Applications Settings for target PLC (PLC3)'s Change PLC Dialog Box Driver Tab Page Workstation node address Automatic generation method IP address Setting 1 Not selected 192.168.250.2 (EtherNet/IP Unit or built-in EtherNet/IP port IP address) 9600 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. 1.
Section 8-5 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 communicating by the FINS/UDP method only. ■ Overview of Setup Methods 1. Starting FinsGateway Settings Select FinsGateway − FinsGateway Setup to start the FinsGateway Setup. 2.
Section 8-5 Using FINS Applications • Communication Unit Tab Page • UDP port number Set the local UDP port number for the personal computer (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.
Section 8-5 Using FINS Applications • UDP Nodes Tab Page: IP Address Table Method or Combined Method Click the Add Button, and then set the IP address table in the following Ethernet Node Definition Dialog Box. • Node address: • IP address: Set the remote FINS node address. Set the remote IP address.
Section 8-5 Using FINS Applications • TCP Nodes Tab Page Click the Add Button, and then set the IP address table in the following Ethernet Node Definition Dialog Box. • Node address: • IP address: • Destination port number: • Keep-alive setting: Set the remote FINS node address. Set the remote IP address. Set the FINS/TCP port number for the remote node. Normally the PLC's default setting of 9600 should be specified. Sets the keep-alive function. Normally this should be selected. 3.
Section 8-5 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/CXIntegrator connected to the Ethernet network. Conditions • FINS/TCP method CX-Programmer/CX-Integrator Node number: 1 IP address: 192.168.250.
Section 8-6 Communicating between OMRON PLCs 8-6 Communicating between OMRON PLCs FINS commands can be sent from the CPU Unit of a PLC by using the SEND(090), RECV(098), and CMND(490) instructions. SEND(090): Writes I/O data from the local node to another node. RECV(098): Reads I/O data from another node to the local node. CMND(490): Issues FINS commands for controlling operations such as sending and receiving I/O memory data to and from other nodes, reading information regarding other nodes, and so on.
Section 8-6 Communicating between OMRON PLCs 8-6-2 PLC Communications Data Areas The following table shows the I/O data areas involved when SEND(090) and RECV(098) are used. Area CIO Area Work Area Holding Area Auxiliary Area Timer Area Counter Area DM Area EM Area Note Range CIO 0000 to CIO 6143 W000 to W511 H000 to H1535 A000 to A959 (See note 1.) TIM0000 to 4095 CNT0000 to 4095 D00000 to D32767 E00000 to E32767 (See note 2.) 1. Data cannot be written to words A000 to A447 in the Auxiliary Area. 2.
Section 8-6 Communicating between OMRON PLCs 8-6-3 Using SEND(090), RECV(098), and CMND(490) Make the settings shown below when using the SEND(090), RECV(098), and CMND(490) instructions in the user’s ladder-diagram program in the PC. SEND(090) The SEND(090) instruction sends the data in n number of words, starting from the beginning word S at the local node, to the words starting from the beginning word D at the remote destination node (node address N).
Section 8-6 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.
Section 8-6 Communicating between OMRON PLCs CMND(490) The CMND(490) instruction sends n bytes of command data, starting from the beginning word S at the local node, to the node at node address N. the data in m number of words, starting from the beginning word S at the remote node (node address M) is received at the words starting from the beginning word D at the local node.
Section 8-6 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 Programmable Controllers Communications Commands Reference Manual (W342). For details on FINS commands that can be processed by the EtherNet/IP Unit or built-in EtherNet/IP port, refer to Appendix E FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports.
Section 8-6 Communicating between OMRON PLCs Usage File memory Debugging 8-6-4 Command code MR SR 22 22 01 02 22 03 22 22 04 05 22 07 22 22 08 0A 22 0B 22 0C 22 23 15 01 23 02 Name Function FILE NAME READ SINGLE FILE READ Reads file memory data. Reads a specified length of file data from a specified position within a single file. SINGLE FILE WRITE Writes a specified length of file data from a specified position within a single file.
Section 8-6 Communicating between OMRON PLCs Communications Port Enabled Flag Execution condition C KEEP(011) A Input A remains ON from start to completion of communications instruction. Operand, control data created with @MOV and @XFER. Creates operand and control data in a given area. Reset B A Communications instructions @SEND @RECV @CMND Executes communications instructions. Communications Port Enabled Flag A DIFU(013) B Creates reset input.
Communicating between OMRON PLCs Communications Port Completion Codes Section 8-6 The status of a SEND(090), RECV(098), and CMND(490) instruction after execution is reflected as a communications port completion code, in one word (two bytes) of data as shown in the following table. (The value is 0000 during instruction execution.) The recorded status is saved until execution of the next instruction.
Section 8-6 Communicating between OMRON PLCs Example 1 0 Communications Port Enabled Flag Communications instruction: SEND(090), RECV(098), CMND(490) Communications Port Error Flag Communications Port Completion Code Instruction 1 being executed. Instruction 2 being executed. Instruction 3 being executed.
Section 8-6 Communicating between OMRON PLCs 8-6-5 Program Example Execution condition A20207 000000 (See note 1.) 120002 S KEEP 120000 R When the Communications Port Enabled Flag for port 7 is ON, and RECV(098) is not being executed, the send execution program will start when execution condition CIO 000000 turns ON. 120001 120000 @MOV(21) #000A D00000 Input CIO 120000 remains ON from the start of SEND(090) execution until completion.
Section 8-6 Communicating between OMRON PLCs (Continued from previous page.) Execution condition A20207 000001 (See note 1.) 120000 S KEEP 120002 When the Communications Port Enabled Flag for port 7 is ON, and SEND(090) is not being executed, the transmission execution program will start when execution condition CIO 000001 turns ON. R 120003 120002 @MOV(21) #0010 D00005 Input CIO 120002 remains ON from the start of RECV(098) execution until completion.
Precautions on High Traffic in FINS Communications 8-7 Section 8-7 Precautions on High Traffic in FINS Communications When applications are constructed using FINS communications services, communications errors (from multiple response timeouts) may occasionally occur due to high traffic, depending on the system configuration and the application programs. This section describes precautions for systems with high traffic in FINS communications.
SECTION 9 Message Communications This section describes message communications using FINS commands sent from the ladder program in the CPU Unit of the PLC. 9-1 Sending Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sending Explicit Messages Using CMND(490). . . . . . . . . . . . . . . . 243 9-2 Receiving Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 9-2-1 249 9-1-1 List of PLC Object Services . . . .
Section 9-1 Sending Explicit Messages 9-1 Sending Explicit Messages CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports can send explicit messages. Only CIP unconnected message (UCMM) communications can be used to send explicit messages. Explicit messages can be sent to the following destinations.
Section 9-1 Sending Explicit Messages in the same network layer and the remote node’s IP address range is limited. The following diagram shows an example of actual node address specifications. EtherNet/IP Unit with unit number 2 PLC's CPU Unit FINS command CMND S D C The node address of the non-OMRON node is set as the destination node address in the FINS command data.
Section 9-1 Sending Explicit Messages CIP UCMM MESSAGE SEND (28 10) This command sends an explicit message for CIP routing to another node’s specified class and receives a response. There are two command formats: one with a specified route path (path to the target device), and the other without the route path. Command Block • Relay Hop Format The following format includes the route path (routing service data). Specify the entire routing path in the command’s request path. 502 bytes max.
Section 9-1 Sending Explicit Messages Response Block The following normal response is returned to a transmitted CIP UCMM MESSAGE SEND command if it was completed normally. 2810 Hex 0000 Hex Command code Response code 00 Hex Transport No. of bytes ID received 502 bytes max. 00 00 Hex Hex Service response data (variable length) Reserved General status Reserved Service code (response) The following response is returned if an error occurs in a transmitted CIP UCMM MESSAGE SEND command.
Section 9-1 Sending Explicit Messages In the routing format for rely hops, the first service code (in the routing service data) is 52 Hex, which is the Unconnected Send service. Request path size (command): Specifies the number of words of data that are specified in the request path field. In the routing format for relay hops, the first request path size (in the routing service data) is 02 Hex. Request path (command): Specifies the request path (class ID, instance ID, etc.) in bytes.
Section 9-1 Sending Explicit Messages 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 Communications. Service response data (response): The reception data determined by the service code is returned.
Section 9-1 Sending Explicit Messages Ann Arbor, Michigan 48108-5006 USA TEL: 1 734-975-8840 FAX: 1 734-922-0027 Email odva@odva.org WEB www.odva.
Section 9-1 Sending Explicit Messages EXPLICIT MESSAGE SEND (28 01) EXPLICIT MESSAGE SEND will send a DeviceNet Unit-compatible explicit message to the specified class of another node and receive a response. The other node is specified with the destination node address in the command. The actual destination IP address is as follows. Destination IP address = (Local IP address & Subnet mask) + Destination node address Command Block 28 01 468 bytes max.
Section 9-1 Sending Explicit Messages Class ID (command): The class ID of the destination of the explicit message. Instance ID (command): The instance ID of the destination of the explicit message. Service data (command, response): The data defined for the services codes. No. of bytes received (response): The number of bytes received from the destination node address (remote node).
Section 9-1 Sending Explicit Messages 9-1-1 Sending Explicit Messages Using CMND(490) With a CS/CJ-series EtherNet/IP Unit or built-in EtherNet/IP port, a CMND(490) in the CPU Unit’s ladder program can send CIP UCMM explicit messages. Send the CIP UCMM explicit message’s command data in a FINS command following the 2810 hex FINS command code. The CIP UCMM explicit message’s response is received following the 2810 hex FINS command code and the FINS completion code.
Section 9-1 Sending Explicit Messages Setting the Command Data for CMND(490) Bit 15 08 07 00 S+0 28 10 S+1 00 00 FINS command code Transport ID S+2 05 DC Message monitoring time S+3 52 02 S+4 20 06 S+5 24 01 S+6 0A 0C 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 S+7 06 00 Message request size
Section 9-1 Sending Explicit Messages data and ERROR CLEAR codes, is also returned in the same order from low to high bytes in the response block.
Section 9-1 Sending Explicit Messages D01016 = 382E hex D01017 = 3235 hex D01018 = 302E hex D01019 = 3200 hex D = D02000: C = D00000: First response word at local node First control word D00000 = 0028 hex D00001 = 0064 hex D00002 = 0001 hex D00003 = 0510 hex D00004 = 0000 hex D00005 = 00A0 hex Response IP address: “8.” IP address: “25” IP address: “0.
Section 9-1 Sending Explicit Messages Program Example A20011 (071) BSET #0000 D00000 D02999 000000 First Cycle Flag Sets 0000 in D00000 to D02999. (021) MOV #0028 D00000 Sets 0028 in D00000. (Number of send data bytes: 40) (021) MOV #0064 D00001 Sets 0064 in D00001. (Number of receive data bytes: 100). (021) MOV #0001 D00002 Sets 0001 in D00002. (Destination network address: 01). (021) MOV #0510 D00003 Sets 0510 in D00003.
Section 9-2 Receiving Explicit Messages 9-2 Receiving Explicit Messages The CS/CJ-series EtherNet/IP Units and built-in EtherNet/IP ports are equipped with a PLC Object that is functionally compatible with CS/CJ-series DeviceNet Units. The Unit will receive messages addressed to the PLC Object, process service requests addressed to the CPU Unit, and return responses.
Section 9-2 Receiving Explicit Messages 9-2-1 List of PLC Object Services PLC Objects provide the following services. Status Read/Write for CPU Units Services CPU Unit Information Read CPU Unit Write CPU Unit Status Read Service code 0E Hex 10 Hex 40 Hex Class ID C4 Hex (2F Hex) (See note.
Section 9-2 Receiving Explicit Messages I/O Memory Read/Write for CPU Units Service Service code Byte Data Read 1C Hex Word Data Read 1D Hex Byte Data Write 1E Hex Word Data Write 1F Hex Class ID Instance ID C4 Hex (2F Hex) (See note.) Specifies area (01 Hex to 14 Hex) Request Contents service data Address, No. Reads the specified node data in byte units. of read bytes The word data is read in order, from high to low bytes. Read data: 200 bytes max. Address, No.
Section 9-2 Receiving Explicit Messages CPU Information Read (Service Code: 0E Hex) Reads CPU Unit information, including operating mode, fatal/non-fatal errors, and the CPU Unit model. Command Block 0E C4 (2F) (*) 00 (*) The class ID depends on the unit version. Version 2.0: The class ID is C4. Version 1.0: The class ID is 2F. Attribute ID Class ID Instance ID Service Code Note A body format of either 8 bits or 16 bits is possible.
Section 9-2 Receiving Explicit Messages Note The codes for the above modes are 1-word (2-byte) data and are returned in low byte first. For example, for PROGRAM mode, the code is returned as 01 Hex followed by 00 Hex. • CPU Unit Errors (when Attribute ID = 65 Hex) The CPU Unit fatal/non-fatal error data is returned in 1-word (2-byte) hexadecimal format, as follows: 01 Hex: Error; 00 Hex: No error. 1: Error • CPU Unit Model (when Attribute ID = 66 Hex) The CPU Unit model is returned in ASCII.
Section 9-2 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. For example, for PROGRAM mode, the code is specified as 01 Hex followed by 00 Hex.
Section 9-2 Receiving Explicit Messages CPU Unit Status Read (Service Code: 40 Hex) This PLC Object service reads status details (operation status, operating mode, fatal and non-fatal errors, etc.) from the CPU Unit. Command Block 40 C4 00 (2F) (*) (*) The class ID depends on the unit version. Version 2.0: The class ID is C4. Version 1.0: The class ID is 2F. Class ID Service Code Instance ID Note A body format of either 8 bits or 16 bits is possible.
Section 9-2 Receiving Explicit Messages Bit 7 6 - 5 - 4 - 3 - 2 1 0 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. 1: Memory is being written.
Section 9-2 Receiving Explicit Messages • 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). Message No. 0 (1: exists; 0: does not exist) Message No. 1 (1: exists; 0: does not exist) Message No. 2 (1: exists; 0: does not exist) Message No. 3 (1: exists; 0: does not exist) Message No. 4 (1: exists; 0: does not exist) Message No.
Section 9-2 Receiving Explicit Messages Class ID (command): Always C4 (2F). The class ID depends on the unit version. The class ID is C4 for unit version 2.0, and 2F for unit version 1.0. Instance ID (command): The memory area that will read the data is specified as shown in the following table.
Section 9-2 Receiving Explicit Messages Response Block 9D Service Code Word data H Word data L Word data H Word data L Read data (200 bytes max.) Parameters Service code (command, response): ID Hex is specified for commands. For responses, the highest bit will turn ON and 9D Hex will be returned. Class ID (command): Always C4 (2F). The class ID depends on the unit version. The class ID is C4 for unit version 2.0, and 2F for unit version 1.0.
Section 9-2 Receiving Explicit Messages Command Block 1E C4 (2F) (*) Class ID The class ID depends on the unit version. Version 2.0: The class ID is C4. Version 1.0: The class ID is 2F. (*) Address L Word data L Address H Service Instance ID Code Word data H Word data L Word data H Write data (200 bytes max.) Note A body format of either 8 bits or 16 bits is possible. Response Block 9E Service Code Parameters Service code (command, response): IE Hex is specified for commands.
Section 9-2 Receiving Explicit Messages Command Block 1F C4 (2F) (*) Class ID Service Code The class ID depends on the unit version. Version 2.0: The class ID is C4. Version 1.0: The class ID is 2F. (*) Address L Instance ID Word data H Address H Word data L Word data H Word data L Write data (200 bytes max.) Note A body format of either 8 bits or 16 bits is possible. Response Block 9F Service Code Parameters Service code (command, response): IF Hex is specified for commands.
SECTION 10 Communications Performance and Communications Load This section describes the communications performance in an EtherNet/IP network, and shows how to estimate the I/O response times and transmission delays. 10-1 Communications System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262 10-1-1 Tag Data Link Communications Method . . . . . . . . . . . . . . . . . . . . . 262 10-1-2 Calculating the Number of Connections. . . . . . . . . . . . . . . . . . . . . .
Section 10-1 Communications System 10-1 Communications System 10-1-1 Tag Data Link Communications Method Packet Interval (RPI) Settings In EtherNet/IP tag data links, the data transmission period is set for each connection as the packet interval (RPI). The target device will send data (i.e., output tags) once each packet interval (RPI), regardless of the number of nodes. Also, the heartbeat frame is sent from the originator to the target for each connection.
Communications System Section 10-1 Packet Interval (RPI) and Bandwidth Usage (PPS) In a tag data link, the number of packets transferred each second is called the bandwidth used or PPS (packets per second).
Section 10-1 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.
Section 10-1 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. The following diagram shows the 4 major delay sources.
Section 10-1 Communications System 3. Switching Hub Delay The switching hub delay is the delay time between the arrival of the packet at the switching hub and the output of the packet from the hub’s transmission port. This delay depends on the total number of connections used for reception and data sizes used in the tag data links. In addition, this delay depends on the switching hub maker and model, but the delay can be approximated with the following table.
Section 10-1 Communications System PLC #1 PLC #2 PLC #3 PLC #17 5 ms #2 #3 200 words 5 ms 200 words 200 words × 16 #17 5 ms 200 words 267
Section 10-2 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.
Section 10-2 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 network 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 Network Configuration Window.
Adjusting the Communications Load Section 10-2 Item Description Total usage of IP The number of multicast IP addresses used in the entire netmulticast addresses work is shown. This value is used to estimate the number of multicast filters for switching. Network Total of The total network bandwidth used for tag data link communicaMax. Mbit/s tions in the entire network is shown. Tag data links will not operate normally if 100 Mbps is exceeded for the network bandwidth.
Adjusting the Communications Load Section 10-2 Example: If the RPI is set to 50 ms for all connections and the usage of capacity is 40%, the usage of capacity may increase to 80% when the RPI is reduced to 25 ms for all connections.
Adjusting the Communications Load Section 10-2 • Is the network bandwidth usage without multicast filtering under 100 Mbps for each node or the usage of capacity without multicast filtering under 100% for each node? (These appear as “Mbit/s” and “Usage of Capacity” in the dialog box shown on page 269.) → If the total bandwidth usage exceeds 100 Mbps, the bandwidth of part of the transmission path (e.g., a switching hub or media converter) had been exceeded as the result of how the network was wired (e.g.
Adjusting the Communications Load Section 10-2 The Usage of Capacity column will show the percentage of the allowed tag data link bandwidth being used, and the Mbit/s column will show the network bandwidth being used. 3. The usage of capacity can be adjusted by changing the associated devices’ RPI settings. The RPI settings can be changed with the following three methods.
Adjusting the Communications Load Section 10-2 Method 2: Changing a Particular Device’s RPI Setting The usage of capacity can be adjusted for only a particular device by changing the packet intervals (RPI) for all of the device’s connections together. In this case, the usage of capacity will also change for the devices that are the target devices of the connection which was adjusted. a. Click the Set Packet Interval (RPI) Button at the bottom of the Usage of Device Bandwidth Dialog Box. b.
Adjusting the Communications Load Section 10-2 a. Click the Close Button at the bottom of the Usage of Device Bandwidth Dialog Box. b. Double-click the device that is set as the originator of the desired connection. The Edit Device Parameters Dialog Box will be displayed. c. In the Register Device List, select the connection for which you want to change the RPI, and click the Edit Button. d. The device’s Edit Connections Dialog Box will be displayed. Input a new RPI value, and click the OK Button.
Adjusting the Communications Load Section 10-2 4. If the usage of capacity cannot be adjusted to the desired level when the setting described above has been performed, reconsider the network configuration considering the following points. Refer to 10-2-3 Adjusting Device Bandwidth Usage. • Reduce the number of nodes and number of connections. • Split the network. 5. Check the bandwidth usage again.
Section 10-2 Adjusting the Communications Load Example Conditions Connections In this example, there are 10 CS1W-EIP21 Units and 10 CJ1W-EIP21 Units for a total of 20 devices connected in the network. Each device has one 100word tag for transmission and nineteen 100-word tags for reception, so that the Units exchange data mutually. By default, the packet intervals (RPI) are set to 10 ms for all of the connections. The devices’ IP addresses range from 192.168.250.1 to 192.168.250.20. IP address: 192.168.
Adjusting the Communications Load Changing the Settings Section 10-2 Method 1: Same Packet Interval Setting for All Connections The percentage of the allowed tag data link bandwidth being used (Usage of Capacity) was 39.67% with the RPI set to 10.0 ms for all of the connections, so the RPI will be set to 5.0 ms, with a target of 80% or less of the allowable bandwidth. Click the Set Packet Interval (RPI) Button at the bottom of the Usage of Device Bandwidth Dialog Box.
Adjusting the Communications Load Section 10-2 If the packet interval for all connections has been set to the same setting, the dialog box will show that the usage of capacity for the tag data link's allowable communications bandwidth is 73.00% and the fastest set value is 5.0 ms. Method 2: Changing the Packet Interval (RPI) of Only Specific Devices In this example, we want faster tag data links for devices 192.168.250.1 and 192.168.250.10 only.
Adjusting the Communications Load Section 10-2 The Usage of Capacity values also indicate that the Usage of Capacity has increased (from 39.67% to 43.00%) for all of the other devices, which connect with devices 192.168.250.1 and 192.168.250.10. In this case, if there is no multicast filter, the value becomes 106.33%. If there is no multicast filter for a switching hub, communications errors may occur depending on the communications load of the EtherNet/IP Unit or built-in EtherNet/IP Unit port.
Adjusting the Communications Load Section 10-2 Method 3: Changing the Packet Interval (RPI) of Only Specific Connections In this example, we want a faster tag data links for just a particular connection of device 192.168.250.1. Double-click device 192.168.250.1 in the Network Configuration Window. Information about the connection with device 192.168.250.20 is registered in the Register Device List. Double-click this connection to edit the settings.
Adjusting the Communications Load Section 10-2 In the Edit Connection Dialog Box, input 1.0 ms as the new RPI value, and click the OK Button. The tag data link bandwidth being used by device 192.168.250.1 (Usage of Capacity) increases to 54.67%, which indicates that a RPI is set to a higher speed for this device. In this case, the tag data link bandwidth being used by device 192.168.250.20 (Usage of Capacity) also increases (from 39.67% to 56.33%).
Section 10-3 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 processing time for a built-in EtherNet/IP port on the CJ2M-CPU3@ CPU Unit is different. For details, refer to 10-4 Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports.
Section 10-3 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 number 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 transferred in multiple data exchanges. The following table shows the number of words that each CPU Unit can exchange at one time.
Section 10-3 I/O Response Time in Tag Data Links CPU Unit CJ2H Effect of EtherNet/IP Unit or CJ2H built-in port only CPU Rack: 0.1 ms Expansion Rack: 0.13 ms CJ2M CPU Rack: 0.14 ms Expansion Rack: 0.16 ms CJ1 CJ1M CJ1-H CS1 CS1-H Long-distance Rack 0.25 ms 0.17 ms 0.1 ms 0.2 ms 0.1 ms 0.2 ms × Coefficient 2 Note Total effect when tag data links are being used CPU Rack: Value from left column + 0.1 ms + No. of words transferred × 0.33 µs (See note 2.) Expansion Rack: Value from left column + 0.
Section 10-3 I/O Response Time in Tag Data Links EtherNet/IP PLC#1 PLC#2 Node 3 Node 2 Node 1 Input switch (external input device) Input PLC#3 Output relay (external output device) W000.01 W000.
Section 10-3 I/O Response Time in Tag Data Links : I/O processing : Data exchange Tag data link I/O response time Input device (4) Network transmission delay time (1) Input ON (2) Send data (6) Output ON processing response (5) Receive data (3) RPI response time time time processing time Input PLC #1 processing Send data processing time Cycle time x 2 Tag data link refresh cycle Receive data processing time Calculation PLC #2 processing Output device PLC #2 Transmission path PLC #1 Calculatio
Section 10-3 I/O Response Time in Tag Data Links Item Calculation formula Time D Number of data trans- A 10 m sec > C 6.15 m sec 2 missions To meet the conditions, the number of transmissions is the same as B. Total: CPU Unit cycle time of A PLC #1 × D Num- 20 m sec ber of data transmissions (2) Send data processing time (3) Packet Interval (RPI) This is the communications refresh cycle set for each connection using the Network Configurator.
Section 10-3 I/O Response Time in Tag Data Links Item Calculation formula Time D Number of data transmissions A 10 m sec > C 6.15 m sec 4 To meet the condition to enable processing in one data transmission, the number of transmissions is the same as B plus 1.
Section 10-3 I/O Response Time in Tag Data Links Minimum Tag Data Link I/O Response Time : I/O processing : Data exchange Tag data link I/O response time (2) Network transmission delay time Input device (1) Input ON response time (3) Output ON response time Input Calculation Transmission path PLC #1 PLC #1 processing PLC #2 Tag data link refresh cycle Output device Calculation PLC #2 processing Output The minimum tag data link I/O response time, which occurs when there are no processing del
Section 10-4 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 connection. These specifications are different from those of CJ2H built-in ports and EtherNet/IP Units. The maximum number of words that can be transmitted for tag data links is 640 words.
Section 10-4 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.
Tag Data Link Performance for CJ2M Built-in EtherNet/IP Ports Section 10-4 For example, the maximum and minimum I/O response times would be as follows for the above system. Maximum response time: 1.5 ms + 5 ms × 2 + 12 ms + 10 ms × 2 + 2.0 ms = 45.5 ms Minimum response time: 1.5 ms + 5 ms + 10 ms + 2.0 ms = 18.5 ms Note If the message service is used at the same time on the CJ2M built-in port, the tag data link I/O response time will change.
Section 10-5 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) instruction 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.
Section 10-5 Message Service Transmission Delay For details, refer to the CPU Unit’s Operation Manual. CPU Bus Unit Service Processing Time (Local Node) The following table shows the CPU Bus Unit service processing time, which depends on the CPU Unit’s CPU processing mode setting. CPU execution mode Normal Mode (See note.
Section 10-5 Message Service Transmission Delay CPU Bus Unit Service Processing Time (Remote Node) The following table shows the CPU Bus Unit service processing time, which depends on the CPU Unit’s CPU processing mode setting. CPU execution mode Normal Mode (See note.
Section 10-5 Message Service Transmission Delay RECV(098) Instruction Execution of RECV(099) in user program CPU Bus Unit service cycle (Local node, 1) CPU Bus Unit service cycle (Local node, 2) CPU Bus Unit service processing time (Local node, 2) CPU Bus Unit service processing time (Local node, 1) Send processing (Command) Transmission delay (Response) Transmission delay (Command) CPU data set processing Transmission delay (Response) Receive processing (Command) Send processing (Response) CPU Bus
Section 10-5 Message Service Transmission Delay For details, refer to the CPU Unit’s Operation Manual. Send Processing Command Response Transmission Delay 0.550 ms (Number of words being transferred × 0.002) + 0.550 ms 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 switching hubs.) Baud rate Delay time 100Base-TX Command 0.
Section 10-5 Message Service Transmission Delay CPU execution mode Processing time details Parallel processing with syn4% of CPU Unit cycle time chronous memory access Parallel processing with asyn- 1 ms max. chronous memory access Note CJ2 CPU Units support only Normal Mode. For details, refer to the CPU Unit’s Operation Manual. CPU Bus Unit Service Cycle (Local Node, 2) The following table shows the CPU Bus Unit service cycle, which depends on the CPU Unit’s CPU processing mode setting.
Section 10-5 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.
SECTION 11 FTP Server This section describes the functions provided by the FTP server. 11-1 Overview and Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 11-1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302 11-1-2 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303 11-2 FTP Server Function Details. . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 11-1 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 Transfer Protocol) server function, so other computers on the Ethernet can read or write (upload/download) large files in the EM file memory by executing FTP commands from the FTP client software. FTP can be used for EtherNet/IP Units with unit version 2.0.
Section 11-2 FTP Server Function Details 11-1-2 Specifications Item Executable commands Protection Protocol Number of connections Specification open: Connects the specified host FTP server. user: Specifies user name for the remote FTP server. ls: Displays the Memory Card file names. dir: Display the Memory Card file names and details. rename: Changes a file name. mkdir: Creates a new directory in the working directory in the remote host.
Section 11-2 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. The FTP server in the EtherNet/IP Unit or built-in EtherNet/IP port can connect to only one client at a time.
Section 11-3 Using the FTP Server Function 11-3 Using the FTP Server Function 11-3-1 Procedure 1,2,3... 1. Make the basic settings. Refer to Initial Settings on page 34. 2. When using a user-set FTP login name and password: With the CX-Programmer online, right-click the EtherNet/IP Unit or built-in EtherNet/IP port in the IO Table Dialog Box of the CX-Programmer, and select Edit - Unit Setup. Set the following on the FTP Tab Page of the Edit Parameters Dialog Box. • FTP login name • FTP password. 3.
Section 11-3 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 Login Password Port No. 306 Details Set the login name to externally connect to the EtherNet/IP Unit or built-in EtherNet/IP port via FTP. Default value None (CONFIDENTIAL is used.
Section 11-4 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 CONFIDENTIAL. Note When general-purpose FTP software is used, files can be transferred and read using a graphical user interface similar to Explorer.
Section 11-5 Using FTP Commands 11-5 Using FTP Commands This section describes the FTP commands which the host computer (FTP client) can send to the FTP server of the EtherNet/IP Unit or built-in EtherNet/IP port. The descriptions should also apply to most UNIX workstations, but slight differences may arise. Refer to your workstation’s operation manuals for details.
Section 11-5 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. The user name is automatically requested immediately after connection to the FTP server.
Section 11-5 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. rmdir Format rmdir DIRECTORY_NAME Function Deletes the directory of the specified name from the remote host (Memory Card or EM File Memory). The directory must be empty to delete it.
Section 11-5 Using FTP Commands type Format type data_type Function Specifies the file data type. The following data types are supported: ascii: Files are transferred as ASCII data binary (image): Files are transferred as binary data. All files are treated by the PLC as binary files. Before reading or writing any files, always use the type command to set the file type to binary. File contents cannot be guaranteed if transferred as ASCII data. The default file type is ASCII.
Section 11-5 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. However, mput execution will continue and remaining files will be transferred.
Section 11-5 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). Bad sequence of commands. Can't create data socket (X.X.X.X, YY). Cannot access to device (FINS error 0 x 250F). Cannot get memory blocks. Command format error (FINS error 0 x 1003). Connect error.
Section 11-6 Checking FTP Status PPP: XXX: YY: MM: NN: Path name IP address Port number FINS error code 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.
Section 11-7 Using File Memory 11-7 Using File Memory There are two media that can be used to store files in memory for CS/CJseries PLCs: • Memory Cards • EM File Memory CPU Unit File Memory Card File File EM File Memory File 11-7-1 File Memory Media CS/CJseries Memory Cards EM File Memory Memory type Capacity Flash memory 8 MB 15 MB 30 MB RAM Model HMC-EF861 HMC-EF171 HMC-EF371 File data recognized by CPU Unit • Complete user program • Specified portions of I/O Memory • Parameter area data (e.g.
Section 11-7 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 Data file File name ******** Extension Contents .IOM Specified ranges of I/O Memory Program file ******** .OBJ Parameter area file ******** .STD Files transferred at startup Data files AUTOEXEC .IOM Program files AUTOEXEC .OBJ Parameter area file AUTOEXEC .
Section 11-7 Using File Memory 11-7-3 Initializing File Memory Memory Memory Cards Initialization method 1. Insert the Memory Card into the CPU Unit. 2. Initialize the Memory Card from a Programming Device (Programming Consoles included). EM File Mem- 1. Specify in the PLC Setup the first bank to convert to file memory. ory 2. Initialize EM File Memory from the CX-Programmer.
Section 11-7 Using File Memory Example: Data format using words delimited by tabs and CRs after every 10 fields. I/O memory +0 +0 +10 +1 1234 5678 9ABC DEF0 +2 +3 9ABC DEF0 1234 +4 +5 1234 5678 +6 +7 9ABC DEF0 5678 9ABC DEF0 1234 +8 +9 1234 5678 5678 9ABC DEF0 .TXT file contents 31 32 33 34 09 35 36 37 38 09 39 41 42 43 09 1 2 3 4 [HT] 5 6 7 8 [HT] 9 A B C [HT] 35 36 37 38 0D 0A 39 41 42 43 09 5 6 7 8 [CR][LF] 9 A B C [HT] .
Section 11-7 Using File Memory Example: Data format using words delimited by commas with CRs after every 10 fields. I/O memory +0 +0 +10 +1 1234 +2 5678 +3 9ABC DEF0 9ABC DEF0 1234 +4 +5 1234 5678 +6 +7 9ABC DEF0 5678 9ABC DEF0 1234 +8 +9 1234 5678 5678 9ABC DEF0 .CSV file contents 31 32 33 34 2C 35 36 37 38 2C 39 41 42 43 2C 1 2 3 4 , 5 6 7 8 , 9 A B C , 35 36 37 38 0D 0A 39 41 42 43 2C 5 6 7 8 [CR] [LF] 9 A B C , .
Section 11-8 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. ■ CS1 CPU Units and CJ1 CPU Units File system CPU Unit status Operating mode Cycle time Transfers using 1 KB put 30 KB 60 KB 120 KB Transfers using 1 KB get 30 KB 60 KB 120 KB Memory Card PROGRAM RUN --20 ms 0.7 s 6.
Host Computer Application Example Section 11-9 11-9 Host Computer Application Example The following procedure provides an example of FTP operations from a host computer. In this example, the following assumptions are made. • The IP address of the EtherNet/IP Unit or built-in EtherNet/IP port is registered in /etc/hosts on the host name as [cs1]. • The default FTP login name is being used (CONFIDENTIAL). • A processing results data file called RESULT.IOM already exists on the Memory Card in the CPU Unit.
Host Computer Application Example 4. Change to the MEMCARD directory. ftp> cd MEMCARD ··· Change to MEMCARD directory. 250 CWD command successful. ftp> ■ 5. Change data type to binary. ftp> type binary ··· Binary data type set. 200 Type set to I. ftp> ■ 6. Transfer the file RESULT.IOM to the workstation. ftp> get RESULT.IOM ··· File read. 200 PORT command successful. 150 opening data connection for result.iom (**IPaddress**port#**) (**bytes). 226 Transfer complete. ** bytes received in *.
SECTION 12 Automatic Clock Adjustment Function This section provides an overview of the automatic clock adjustment function, including details on specifications, required settings, operations from CX-Programmer, and troubleshooting. 12-1 Automatic Clock Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 12-1-1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 12-1-2 Specifications . . . . . . . . . . . . . . . .
Section 12-1 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 information from the SNTP server (see note 1) at a particular time or when a designated 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). Intranet SNTP server Automatic clock adjustment The clock information can be broadcast to other CPU Units on the same Network.
Using the Automatic Clock Adjustment Function Section 12-2 12-1-2 Specifications Item Protocol Port number Adjustment timing Access to SNTP server Refresh timing Specification SNTP 123 (UDP) Can also be set from the CX-Programmer in the Unit Setup. Automatic (fixed time) and manual (manual only cannot be set) Obtains the clock information Writes the clock information from the SNTP server set up from the SNTP server to the on the Network, and applies local CPU Unit.
Section 12-2 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. CXProgrammer tab Auto Adjust Time Settings Setting conditions Reference Server specification type IP Address Host name Required.
Using the Automatic Clock Adjustment Function Section 12-2 12-2-3 Auto Adjust Time The contents in the CPU Bus Unit System Setup that are set for using mail send and receive functions are shown in the CX-Programmer’s Edit Parameters Dialog Box. Item Get the time information from the SNTP server Auto Adjust Time Server specification type IP Address Host name Port No. Contents Enable to set the CPU Unit's clock to the time at the SNTP server's clock.
Section 12-3 Automatic Clock Adjustment Switch Item Contents Retry timer Default Set the time to elapse before retrying when a connec- 0 tion to the SNTP server fails. This setting does not (10 s) normally need to be changed. This sets in the CPU Unit's clock data the time differ- +0:0 ence made up from the SNTP server's clock data. To use the clock data from the SNTP server just as it is, input 0.
Section 12-4 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.
Section 12-4 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 Processing. (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.
SECTION 13 Maintenance and Unit Replacement This section describes cleaning, inspection, and Unit replacement procedures, as well as the Simple Backup Function. 13-1 Maintenance and Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 13-1-1 Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332 13-1-2 Inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 13-1 Maintenance and Replacement 13-1 Maintenance and Replacement This section describes the routine cleaning and inspection recommended as regular maintenance, as well as the Unit replacement procedure required if an EtherNet/IP Unit needs to be replaced. 13-1-1 Cleaning Clean the EtherNet/IP Unit regularly as described below in order to keep the network in its optimal operating condition. • Wipe the Unit daily with a dry, soft cloth.
Section 13-2 Simple Backup Function • If there is a faulty contact, try wiping the contact with a clean, lint-free cloth dampened with alcohol. Note Settings Required after Unit Replacement 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. After a Unit has been replaced, verify that the following steps have been made correctly. • Set the node address and unit number.
Section 13-2 Simple Backup Function CPU Unit EtherNet/IP Unit CS1W-EIP21 CS1 CJ1-H CJ1 CJ1M CJ2H CJ2M CJ1W-EIP21 No ----------- --Yes No Yes Yes Yes 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.
Section 13-2 Simple Backup Function EtherNet/IP Unit CPU Unit Memory Card Power Supply Switch All data Memory Card All setup data Backup This operation will create an EtherNet/IP Unit or built-in EtherNet/IP port settings 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.
Section 13-3 Using the Backup Tool Comparing EtherNet/IP Unit or Built-in EtherNet/IP Port Data with the Setup File in the Memory Card Set pins 7 and 8 of the DIP switch on the front panel of the CPU Unit, as shown in the following table, and press down the Memory Card Power Supply Switch for 3 seconds.
Section 13-3 Using the Backup Tool Usage The PLC Backup Tool can be used for the following: • Backing up all data in a PLC • Comparing all of the data in a PLC with data that was previously backed up in the computer • Using the restore function to transfer all of the PLC data to a system with the same configuration • Transferring data to a new Unit after replacing a faulty Unit Procedure Select PLC Backup Tool from the CX-Programmer's Tool Menu.
Using the Backup Tool 338 Section 13-3
SECTION 14 Troubleshooting and Error Processing This section describes error processing, periodic maintenance operations, and troubleshooting procedures needed to keep the EtherNet/IP network operating properly. We recommend reading through the error processing procedures before operation so that operating errors can be identified and corrected more quickly. 14-1 Checking Status with the Network Configurator . . . . . . . . . . . . . . . . . . . . . .
Checking Status with the Network Configurator Section 14-1 14-1 Checking Status with the Network Configurator 14-1-1 The Network Configurator’s Device Monitor Function Connect the Network Configurator online, select the device to be checked, right-click to display the pop-up menu, and select Monitor. The Monitor Device Dialog Box will be displayed. Note Status 1 Tab Page If a communications error occurs during monitoring, the dialog box will continue to show the last information that was collected.
Checking Status with the Network Configurator Status 2 Tab Page Section 14-1 The Status 2 Tab Page’s Target PLC Status Field shows the status of the target node PLCs that are connected with the EtherNet/IP Unit as the tag data link originator. The icon will be blue if the CPU Unit is in RUN mode or MONITOR mode, gray if it is in PROGRAM mode, or red if an error occurred. The Connected Status of FINS/TCP Connections Field shows the status of FINS/TCP connections.
Checking Status with the Network Configurator Note 342 Section 14-1 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.
Checking Status with the Network Configurator Connection Tab Page Section 14-1 The Connection Tab Page’s Target Node Status Field shows the connection status of the target nodes that are connected with the EtherNet/IP Unit as the tag data link originator. The icon will be blue if the connection is normal, or red if an error occurred. In addition, the Connection Status Area shows the current status each connection that is set as the originator.
Checking Status with the Network Configurator Error History Tab Page Section 14-1 The Error History Tab Page displays the error log stored in the EtherNet/IP Unit or built-in EtherNet/IP port. Errors that occurred in the past are recorded, and can be cleared or saved in a computer file as required. In some cases, error records are cleared when the power is turned OFF, and in other cases the records are retained. For details on the error log, refer to 14-4 Error Log Function.
Section 14-1 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. The following status is displayed. Ok: Data was exchanged normally. Processing to solve: The symbol or I/O memory address for the tag is being resolved.
Checking Status with the Network Configurator Section 14-1 If the status is not “OK,” check the tag data link settings or the network symbol settings in the symbol table in the CJ2 CPU Unit.
Using the LED Indicators and Display for Troubleshooting Ethernet Information Tab Page Section 14-2 The Ethernet Information Tab Page shows the communications status at the communications driver level. The error counter information can be used to confirm whether communications problems have occurred. The tag data link information can be used to confirm characteristics such as the bandwidth usage (pps).
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS Indicator NS 7-segment Error Cause Error log (hex) Countermeasure Operation stops. --- Replace the EtherNet/IP Unit or (for a built-in EtherNet/IP port) the CPU Unit if the error recurs when the Unit is restarted. Set the node address correctly and restart the EtherNet/IP Unit or built-in EtherNet/IP port. Replace the CPU Unit if the error recurs when the CPU Unit is restarted. Create the I/O table.
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS Flashing red Indicator NS 7-segment --- HA Error Cause Unit operation (Flag status) Error log (hex) Countermeasure CPU Unit memory error A parity error occurred during an operation such as reading the routing tables. Records the error in the error log. If the routing tables were being read, the routing tables are treated as missing. 0012 Register the routing tables in the CPU Unit again and restart the CPU Unit.
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS Indicator NS 7-segment Error Flashing red --- HE CPU Unit service monitoring error Flashing red --- HF CPU Unit watchdog timer error 350 Cause Unit operation (Flag status) Error log (hex) • If the Unit is the orig- 0002 Servicing from inator of the tag data the CPU Unit link connection, it was not completed within the stops communications. fixed interval.
Using the LED Indicators and Display for Troubleshooting Errors Related to the CPU Unit MS Indicator NS 7-segment The 7-segment display alternates between the node address and error code. Error Cause Flashing red --- HH CPU Unit Fatal Error A fatal error occurred in the CPU Unit. --- --- --- Output OFF Error An Output OFF (output inhibit) condition occurred in the CPU Unit.
Section 14-2 Using the LED Indicators and Display for Troubleshooting Errors Related to the Tag Data Links MS Indicator NS 7-segment The 7-segment display alternates between the node address and error code. Error Cause Unit operation (Flag status) Error log (hex) --Not record ed for version 2.0 or higher --- --- d5 Verification Error (target non-existent) The target registered in the device parameters does not exist. The Unit will periodically attempt to reconnect to the target.
Using the LED Indicators and Display for Troubleshooting Errors Related to Memory Access MS Flashing red Indicator NS 7-segment --- E9 Section 14-2 The 7-segment display alternates between the node address and error code. Error Memory Access Error Error Countermeasure log (hex) 0602 Download the Unit Case 1: An error Setup from the tab occurred in the The error record pages of the Edit Unit's non-vola- remains in RAM only. Parameters Dialog Subsequent writes to tile memory Box of the CX-Proitself.
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS Indicator NS 7-segment Error Cause Unit operation (Flag status) Error log (hex) 021A There is an error in the parameter settings stored in the Unit’s non-volatile memory. (An error can occur when power is interrupted while data is being written to non-volatile memory.) The Unit Error Occurred Flag (n+10, bit 00) and Invalid Communications Parameter Flag (n+12, bit 04) will go ON.
Using the LED Indicators and Display for Troubleshooting Errors Related to the Network MS --- Indicator NS 7-segment --- E1 Section 14-2 The 7-segment display alternates between the node address and error code. Error Ethernet Link Not Detected Cause Unit operation (Flag status) The link with the • The Unit will be offline and unable to switching hub communicate. Errors could not be will be returned to all detected. Note This error communications requests.
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS --- Indicator NS 7-segment --- E3 Error Server Connection Error Cause Unit operation (Flag status) Error log (hex) Countermeasure An error occurred in communications with the DNS server. The DNS Server Error Flag (n+14, bit 05) will turn ON. 03C4 Details: 00xx An error occurred with the BOOTP server. 1. There was no response from the BOOTP server. 2.
Section 14-2 Using the LED Indicators and Display for Troubleshooting MS Indicator NS 7-segment Error Cause Unit operation (Flag status) Error log (hex) Countermeasure --- 03C4 Details: 07xx Perform one of the following: • Correct the SNMP trap settings. • Check the communications path (EtherNet/IP Unit or built-in EtherNet/IP port, cable connections, hubs, routers, and servers) and correct any problems. Check the IP addresses set on other nodes.
Section 14-3 Connection Status Codes and Error Processing MS Indicator NS 7-segment Flashing red Not lit F4 Flashing red --- C8 Lit red Unit operation (Flag status) Error log (hex) 020F • The Unit will be An error offline and unable to occurred in the communicate. Errors Communicawill be returned to all tions Controller communications in the EtherNet/ IP Unit or built-in requests. EtherNet/IP • Data exchanges port. (refreshing) will continue with the CPU Unit.
Section 14-3 Connection Status Codes and Error Processing Email odva@odva.org WEB www.odva.org The following table shows the possible originator/target configurations.
Section 14-3 Connection Status Codes and Error Processing Connection status General Additional Status Status (hex) (hex) 01 0109 01 0110 01 0111 01 0113 01 0114 01 0115 01 0116 01 0117 360 Source of error Configuration 1 Error code returned from target: The connection size settings are different in the originator and target. Error code returned from target: The target was unable to open the connection, because of its operating status, such as downloading settings.
Section 14-3 Connection Status Codes and Error Processing Connection status General Additional Status Status (hex) (hex) Source of error Configuration 1 An unexpected network load may have been received. Use the Network Configurator Device Monitor or the Ethernet Tab Page to check the bandwidth usage, and correct the load. If there are places where broadcast storms occur, such as loop connections in the network connection format, then correct them.
Section 14-3 Connection Status Codes and Error Processing Connection status General Additional Status Status (hex) (hex) Source of error Configuration 1 Handling Configuration 2 Configuration 3 01 0316 Error code returned from target: This error does There was a parameter error in not occur. the frame used to close the connection. Depends on the originator’s specifications. (Contact the originator device’s manufacturer.) 01 031C Error code generated in originator: Some other error occurred.
Section 14-3 Connection Status Codes and Error Processing Connection status General Additional Status Status (hex) (hex) Source of error Configuration 1 Unique OMRON Error Codes 01 0810 Error code returned from target: New data could not be obtained from the CPU Unit when opening connection. (The Unit will automatically retry, and attempt to open the connection again.
Section 14-4 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. 14-4-1 Error Log Data Specifications Each error is recorded as one record in the error log.
Section 14-4 Error Log Function 14-4-4 Error Log Error Codes Error code (hex) 0001 0002 0006 CPU Unit watchdog timer error CPU Unit service monitoring error Other CPU error 000E 000F 0011 0012 I/O bus error CPU Unit initialization error Event timed out CPU Unit memory error 0015 0017 0103 0105 0107 0108 CPU Unit fatal error Tag database error Resend count exceeded (send failed) Node address setting error (send failed) Remote node not in network (send failed) No Unit with specified unit address (send
Section 14-4 Error Log Function Error code (hex) 0300 Parameter error; packet discarded 0347 03C0 I/O refreshing error FINS/TCP setting error 03C1 Server settings error 03C2 FINS/TCP packet discarded 03C3 FINS/UDP packet discarded 366 Error 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 FINS Response: Bit 15: ON Bits 08 to 14: Destination network address Bits 00 to 07: Destination node address CIP Frame: FF
Section 14-4 Error Log Function Error code (hex) 03C4 Server connection error 00 hex: DNS 03 hex: SNTP 04 hex: FTP 06 hex: BOOTP 07 hex: SNMP 08 hex: SNMP Trap 03C6 Clock write error 0001: The clock time could not be updated because a error occurred in the CPU Unit. 0002: The clock time could not be updated because the CPU Unit or operating mode does not support this function.
Section 14-5 Troubleshooting Error code (hex) 03D3 03D4 03D5 0601 0602 Error Detail code First byte Second byte Link OFF error Verification error (Tag data link only) 00 hex 00 hex Connection instance num- Lower byte of IP address Note For details on identifying the cause of ber (0 to 255) 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.
Section 14-5 Troubleshooting 14-5-2 General Ethernet Problems The 100M and 10M Indicators on the EtherNet/IP Unit or CPU Unit are both OFF. The NS Indicator on the EtherNet/IP Unit or CPU Unit is lit red. • Confirm that the cable being used has the correct ratings. • Confirm that the cable is properly connected to the switching hub, and the hub’s power supply is ON. (The 7-segment display will indicate error E1.
Section 14-5 Troubleshooting 14-5-4 Tag Data Link Problems The tag data isn't simultaneous. Observe the following precautions when writing application programs: • Maintain the simultaneity of data in connection-units between the PLC and EtherNet/IP Unit or built-in EtherNet/IP port. • If another company's device is being used, refer to that device's user's manual for details.
Section 14-6 Troubleshooting with FINS Response Codes 14-5-5 Message Timeout Problems Timeout errors occur frequently in message services (CIP UCMM, CIP Class 3, or FINS). • When there is a high load in the tag data link, and the CPU Unit’s cycle time is relatively long or there are messages coming in from many nodes, the message service response time may be delayed and messages may be discarded occasionally.
Section 14-6 Troubleshooting with FINS Response Codes Main response code Value and meaning 01 Local node error Sub response code 03 07 Remote node error 01 02 05 03 Unit error (Controller error) 01 02 04 04 Service not 01 supported 05 Routing error 01 02 03 04 372 Likely cause Corrective action Value and meaning 05 02 Item to check Local node send error --- Lack of available space in The load (traffic) on the Etherinternal buffers net Unit is too heavy.
Section 14-6 Troubleshooting with FINS Response Codes Main response code Value and meaning 10 Sub response code Command 01 format error 21 Parameter error Cannot write Likely cause Corrective action The command is too long. The command exceeded 1,473 bytes when broadcasting. The command is too short. The specified number of items does not match the amount of write data. Data for another node on the same network was received from the network. Attempted to send response data for a broadcast address.
Section 14-6 Troubleshooting with FINS Response Codes Main response code Value and meaning 22 Sub response code Item to check Likely cause Cannot execute because service is being processed. Socket status area The same socket service is already in progress at the specified socket number.
Appendix A CS/CJ-series Ethernet Unit Function Comparison Item Ethernet Unit 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 No No Yes Yes Yes Yes Yes Yes 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 Online connection by Ethernet (FI
CS/CJ-series Ethernet Unit Function Comparison 376 Appendix A
Appendix B Ethernet Network Parameters Parameter TCP send buffer TCP receive buffer UDP send buffer UDP receive buffer FINS receive buffer RAW send buffer RAW receive buffer Hold timer Value 4,096 bytes 4,096 bytes 9,000 bytes 9,016 bytes 16,383 bytes 2,048 bytes 2,048 bytes 75 s (See note.
Ethernet Network Parameters 378 Appendix B
Appendix C TCP Status Transitions The TCP socket status can be confirmed using the socket status data returned for the FINS command SOCKET STATUS READ (27 64).
TCP Status Transitions 380 Appendix C
Appendix D CIP Message Communications This appendix describes CIP message communications. The basic concepts of CIP message communications are described in this appendix from CIP Object on page 381 through Example of CIP Message Creation on page 386. Read these sections to improve your understanding of CIP message communications. CIP Object Object Model In the CIP (Common Industrial Protocol) system, each device is modeled as a group of “Objects.
Appendix D CIP Message Communications Terminology In CIP specifications, “Object,” “Class,” “Instance,” “Attribute” and “Service” are defined as follows: Term Object Class Instance Attribute Service Meaning An abstract representation of a particular component within a product. A set of objects that all represent the same kind of system component. A class is a generalization of an object. All objects in a class are identical in form and behavior, but may contain different attribute values.
Appendix D CIP Message Communications Route Path Route Path In the CIP, unlike the internet protocol, the transmission frame contains a complete relay route from the transmission node to the reception node. The described route is called the “route path.” The route path is described as “EPATH type.
Appendix D CIP Message Communications According to CIP Specifications, the Segment Type specifications are decided as follows: 7 0 0 0 0 1 1 1 1 Segment Type 6 5 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 1 Description 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.
Appendix D 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 Address Size Segment Type 7 6 5 4 0 0 0 1 Port Identifier 3 6 5 4 3 1 0 7 6 5 4 3 2 1 0 → · · · · · · · · · · · · Link Address 7 2 Link Address Size 2 1 0 7 Link Address 6 5 4 3 2 1 0 · · · · · · → Always set the Link Address to an even number of bytes.
CIP Message Communications Appendix D The 8-bit logical address can be used for the Attribute ID. Use the Attribute ID when requesting a Service of a particular Object of a particular device. Example of CIP Message Creation Setting the Route Path Port Number The following description explains the network port, which is used to specify the route path. In the CJ2 Series, the Backplane is also considered part of the network when specifying the Link Address. CPU Unit CJ2 (Not supported by CS1/CJ1 CPU Units.
Appendix D 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) 00 Success 01 Connection failure 02 Resource unavailable Description of Status 06 Service was successfully performed by the object specified. A connection related service failed along the connection path.
Appendix D CIP Message Communications General Status Code (hex) 1D 1E 1F 20 21 22 23-24 25 26 27 28 29 2A 2B-CF D0-FF 388 Status Name Invalid attribute value list Embedded service error Vendor specific error Description of Status The service is returning the list of attributes supplied with status information for those attributes that were invalid. An embedded service resulted in an error. A vendor specific error has been encountered.
Appendix D CIP Message Communications Example of Additional Status in case that General Status Is 01 Hex. (Status of Connection Manager Object) General Status (hex) 01 01 01 01 01 Additional Status (hex) 0100 0103 0106 0107 0108 Explanation 01 01 01 0109 0110 0111 01 01 01 01 01 01 01 01 01 01 01 0113 0114 0115 0116 0117 0118 0119 011A 011B 0203 0204 Connection in Use or Duplicate Forward Open.
Appendix D CIP Message Communications Priority/Time Ticks and Time Out Ticks Format of the Priority/Time Tick Time tick 0000 hex 0001 hex 0010 hex 0011 hex 0100 hex 0101 hex 0110 hex 0111 hex 1000 hex 1001 hex 1010 hex 1 2 4 8 16 32 64 128 256 512 1,024 Maximum time-out time (ms) that can be set in the time out ticks 255 510 1,020 2,040 4,080 8,160 16,320 32,640 65,280 130,560 261,120 1011 hex 2,048 522,240 1100 hex 1101 hex 1110 hex 1111 hex 4,096 8,192 16,389 32,768 1,044,480 2,088,960 4,177,920
Appendix E FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 04 05 06 08 21 27 Command code MRC SRC 03 01 01 01 02 03 02 03 20 30 31 50 57 60 61 62 63 64 65 67 01 10 28 Function name 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 IP ADDRESS WRITE IP ADDRESS TABLE READ IP R
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Precautions • No response will be returned if the command ends normally. A response will be returned only if an error occurs. • In some cases, send requests (SEND(192)/RECV(193) instructions) made from the PLC to the EtherNet/ IP Unit or built-in EtherNet/IP port just before execution of the RESET command may not be executed.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Mode Setting (Response) The mode setting in the system setup is returned.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Codes Response code 0000 1001 Description Normal end Command too large CONTROLLER STATUS READ Reads the controller status.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E IP Router Table Error Bit 3 Meaning 0 No error 1 Error detected (More than 8 records, or invalid IP address). Routing Table Error Bit 6 0 No error 1 Error detected in routing table check. Meaning Ethernet Advanced Setting Error Bit 9 Meaning 0 No error 1 An error was detected during the validity check of vendor-specific parameters for the TCP/IP Interface Object and Ether Link Object.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Total Number of Packets Sent (Response) The total number of packets sent by the EtherNet/IP Unit or built-in EtherNet/IP port is returned. Total Number of Errors Sent (Response) The total number of packet errors detected while the EtherNet/IP Unit or built-in EtherNet/IP port was sending is returned.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Codes Response code 0000 1001 1002 Description Normal end Command too large Command too small (No test data) BROADCAST TEST RESULTS READ Reads the results (number of times data received) of the broadcast test.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Precautions • No response is made to this command. • When using this command, set the FINS header parameters (or the control data for the CMND(194) instruction) as follows: Destination node address: FF (broadcast data) Destination unit address: FE (EtherNet/IP Unit or built-in EtherNet/IP port) Response/no response flag: 1 (no response) ERROR LOG READ Reads the error log.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 1st byte Appendix E 10th byte Error code Detailed Minutes Second Day Hour Year Month 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.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Command Block 27 20 Command code Destination IP address Timeout value Response Block 27 20 Command code Response 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. The value is set in seconds.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Command Block 27 30 Command FINS/TCP connection No. code Remote IP address Remote TCP port number Response Block 27 30 Command code Response 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.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Block 27 31 Command code Response code FINS/TCP Connection connection service No. Local IP address Local TCP port number Remote IP address Remote TCP TCP transition port number 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.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Codes Response code Description 0000 Normal end 0105 Node address setting error Local IP address setting error 0302 CPU Unit error; execution not possible. 1001 Command too large 1002 Command too small 1100 Connection number not set from 1 to 16 IP ADDRESS TABLE WRITE Writes the IP address table.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E • An error response will be returned if the IP address conversion method in the system mode settings is set for automatic generation on the FINS/UDP Tab Page of the Unit. Response Codes Response code 0000 1001 1002 1003 110C 2307 Description Normal end (echo reply received from the remote node) Command too large Command too small The number of records specified does not match the sent data length.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Codes Response code 0000 1001 1002 Description Normal end Command too large 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.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports 1 Appendix E 6 bytes 00 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).
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Maximum Number of Stored Records (Response) The maximum number of records that can be stored in the IP router table is returned. The maximum number of stored records is fixed at 0008 (8 records). Number of Stored Records (Response) The number of IP router table records stored at the time the command is executed is returned in hexadecimal.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Parameters IP Status (Response) Twelve types of IP status information occupying 4 bytes each are returned in the following sequence. Each value is returned as an 8-digit hexadecimal value. 1. Total number of IP packets received. 2. The number of IP packets discarded due to an error with the checksum in the packet header. 3.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Type number #6, #7 #8 #9, #10 #11 #12 #13 #14 #15 #16 #17 #18 Appendix E Description Undefined, always 0 Echo Undefined, always 0 Time exceeded Parameter problem Time stamp Time stamp reply Information request Information request reply Address mask request Address mask reply 5. The number of received ICMP packets discarded because the type-indication code was out of range. 6.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E 1. The number of times active connections were correctly established. 2. The number of times a SYN packet was received while waiting to establish a passive connection. 3. The number of times active or passive connections were correctly established. 4. The number of times an established connection was cut off. 5. The number of times the connection wait status was cut off. 6.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E 8. The number of bytes in the resend packets. 9. The number of duplicated resend packets received. 10. The number of bytes in the duplicated resend packets received. 11. The number of out-of-range data packets received. (Always 0.) 12. The number of bytes in the out-of-range data packets received. (Always 0.) 13. The number of packets where the data was larger than the window. 14.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Response Block 27 63 Command code 92 bytes Response code Memory status Parameters Memory Status (Response) A total of 23 data items in six areas are returned in the following order. Each item consists of 4 bytes. 1) Short Buffer Application: Two items are returned (8 bytes). 1. The number of short buffers currently being used. 2. The number of short buffers in the system (fixed at 23,928 decimal).
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Precautions All the above values are set to 0 if Ethernet communications functions are stopped due to improper settings in the system setup. These values are cleared when the EtherNet/IP Unit or built-in EtherNet/IP port is started or reset. Values will be counted only until the maximum values are reached.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Remote Port Number (4 bytes) The remote port number allocated to the socket. TCP Transitions (4 bytes) The TCP connection status is returned as one of the numbers shown in the following table. Refer to Appendix C TCP Status Transitions for a diagram of transitions.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E Address Information Returns the FINS node addresses and IP addresses. Each pair requires 6 bytes and has the following configuration. 1 6 bytes 00 FINS node number IP address FINS Node Address Node address set in the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal). IP Address IP address set in the EtherNet/IP Unit or built-in EtherNet/IP port (hexadecimal).
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Appendix E IP Address (Response) The local IP address set in the CPU Bus Unit System Setup for the EtherNet/IP Unit or built-in EtherNet/IP port is returned in order starting from the leftmost bytes in hexadecimal. If the local IP address set in the allocated words in the DM Area is enabled, 0.0.0.0 is returned.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response code 110B 2211 Appendix E Description Response length exceeds maximum response length. 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). CIP UCMM MESSAGE SEND Sends a message in the CIP message (UCMM) format. Command Block 2810 hex Command code Transport Message monitoring ID timer 502 bytes max.
FINS Commands Addressed to EtherNet/IP Units or Built-in EtherNet/IP Ports Response code 1005 110B 2211 Appendix E Description Header error Response length exceeds maximum response length. 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).
Appendix F EDS File Management This section explains the EDS file management functions used in the Network Configurator. Installing EDS Files Note Using Windows Vista or Windows 7 Is recommended that you start the Network Configurator from Run as administrator when you install an EDS file in the Network Configurator.
EDS File Management Appendix F 3. Select the EDS file to be installed and click the Open Button. Next, select the icon file (*.ico), and the EDS file will be added to the Hardware List. If the EDS file already exists, the new EDS file will overwrite the previous one. If the hardware versions are different, an EDS file will be added to the Hardware List for each version. Creating EDS Files EDS File - Create The EDS files are required by the Network Configurator in order to create a network configuration.
EDS File Management Appendix F 3. Input the folder and file names and click the Save Button The EDS file will be saved. Searching EDS Files EDS File - Search To search the devices (EDS files) displayed in the Hardware List, use the following procedure. 1. Select EDS file - Find. The following window will be displayed. 2. Input the character string and click the Find Next Button. 3. When there is a matching device found, the cursor will move to that position. 4.
EDS File Management Appendix F 2. Select EDS File - Property. The following window will be displayed. The time and date that the EDS file was created will be displayed, along with the device information.
Appendix G Precautions for Using Windows XP, Vista, or Windows 7 Changing Windows Firewall Settings Better firewall security for Windows XP (SP2 or higher), Windows Vista, and Windows 7 has increased the restrictions for data communications on Ethernet ports. When using an EtherNet/IP connection*1 to one of the following PLCs from an Ethernet port on a computer, you must change the settings of the Windows Firewall to enable using CX-Programmer or Network Configurator communications.
Precautions for Using Windows XP, Vista, or Windows 7 Appendix G The User Account Control Dialog Box may be displayed during this procedure. If it appears, click the Continue Button and continue with the procedure. 1. Select Control Panel from the Windows Start Menu and change the display to Classic View. 2. Open the Administrative Tools and select Windows Firewall with Advanced Security from the dialog box that is displayed. 3.
Precautions for Using Windows XP, Vista, or Windows 7 Appendix G An EtherNet/IP connection will be accepted from CX-Programmer or Network Configurator and EtherNet/ IP connections will be enabled in the future as well.
Precautions for Using Windows XP, Vista, or Windows 7 426 Appendix G
Index Numerics 7-segment display, 24 A Adjust Time field, 326, 328 alternate DNS server, 54 applications precautions, xxiv Auto Adjust Time field, 326, 327 Auto Adjust Time Tab, 326, 327 automatic clock adjustment Automatic Clock Adjustment Switch, 328 errors error codes, 328 error log, 328 SNTP, 328 overview, 324 procedure, 325 requirements, 324 settings, 326 specifications, 325 Auxiliary Area related data, 88 B C cables connections, 44 installation, 43 precautions, 41 cd command, 303, 308, 310 cdup com
Index creating a tag set, 126 creating tag sets, 126 E creating tags, 128 EC Directives, xxvi crimp terminals, xxv Edit Parameters, 52, 61 current consumption CJ-series, 15, 16 CS-series, 14 CX-Integrator, 46 creating routing tables, 208 CX-Programmer, 8, 46 connecting to PLC, 211 cyclic communications required settings, 35 EDS file management, 419 EDS files, 10, 419 creating, 420 installing, 419 saving, 420 searching, 421 electromagnetic fields, xxiv EM File Memory, 315 using, 315 EMC Directives, xx
Index EtherNet/IP Unit Features, 2 EtherNet/IP Units resetting, 391 ETN11-compatible mode, 99 explicit message communications, 187, 233 explicit message communications service, 106, 108 explicit messages list of PLC object services, 249 receiving, 248 sending, 234 sending using CMND(490), 243 F FALS instruction, xxiii FINS communications, 233 overview, 8 specifications, 199, 220 testing, 399 FINS communications service, 106, 107 FINS communications services, 94 FINS message communications, 187, 190 FINS no
Index Host name field, 326, 327 I I/O allocations CIO Area, 70 DM Area, 83 I/O memory address, 116 reading tables, 405 IP router tables reading, 406 status, 408 IP ROUTER TABLE READ, 406 L I/O response time, 283 ladder programming for tag data links, 183 I/O tables creating, 46 overview, 46 LED indicators, 23 using for troubleshooting, 347 ICMP communications status, 408 link setting (baud rate), 55 local network table, 207 IGMP snooping, 29 locking devices precautions, xxv importing, 136 Login
Index multicast communications, 114 multicast filter, 29 PING, 399 PING command, 65 PLC object services, 249 N n beginning word of allocated CIO Area, 70 Port No.
Index refresh cycle, 268 Register Device List, 141 Registered Target Node Flags, 81, 85 registering devices, 125, 141 relay tables, 207 rename command, 303, 308 CJ-series general specifications, 15, 16 communications specifications, 17 CS-series general specifications, 14 FINS communications, 220 FTP server, 303 message communications, 193 Network Configurator, 10 replacing a Unit, 332 startup procedure, 34 replacing Units precautions, xxv static electricity, xxiv precautions, xxv restoring data from
Index specifications, 115 status flags, 186 tag data links (cyclic communications), 6 tag set, 116 W wiring precautions, 44 tag sets creating, 126 Target Node PLC Error Flags, 73, 87 Target Node PLC Operating Flags, 73, 87 TCP communications sockets status, 379 status, 409 TCP status transitions, 379 TCP/IP, 52 terminal blocks, xxiii timeout errors, 371 timers, 377 to, 61 troubleshooting, 368 twisted-pair cable recommended models, 28 twisted-pair cables precautions, 41 type command, 303, 308, 311 U unica
Index 434
Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. W465-E1-05 Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to the previous version. Revision code 01 02 03 04 05 Date June 2007 July 2008 Revised content Original production Added information for CJ-series CJ2 CPU Units and for new unit version 2.0 functions.
Revision History 436
OMRON Corporation Industrial Automation Company Authorized Distributor: Tokyo, JAPAN Contact: www.ia.omron.com Regional Headquarters OMRON EUROPE B.V. Wegalaan 67-69-2132 JD Hoofddorp The Netherlands Tel: (31)2356-81-300/Fax: (31)2356-81-388 OMRON ELECTRONICS LLC One Commerce Drive Schaumburg, IL 60173-5302 U.S.A. Tel: (1) 847-843-7900/Fax: (1) 847-843-7787 OMRON ASIA PACIFIC PTE. LTD. No.