Page 1
Machine Automation Controller CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit CJ1W-EIP21 EtherNet/IP Units W495-E1-05...
Page 2
OMRON. No patent liability is assumed with respect to the use of the information contained herein. Moreover, because OMRON is constantly striving to improve its high-quality products, the information contained in this manual is subject to change without notice.
This manual contains information that is necessary to use a CJ1W-EIP21 EtherNet/IP Unit that is con- nected to an NJ-series CPU Unit. Use a CJ1W-EIP21 EtherNet/IP Unit with unit version 2.1 or later for an NJ-series CPU Unit. Also use a CPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher.
Relevant Manuals Relevant Manuals There are three manuals that provide basic information on the NJ-series CPU Units: the NJ-series CPU Unit Hardware User’s Manual, the NJ-series CPU Unit Software User’s Manual, and the NJ-series Instructions Reference Manual. Most operations are performed from the Sysmac Studio Automation Software. Refer to the Sysmac Stu- dio Version 1 Operation Manual (Cat.
Page 5
Relevant Manuals Manual NJ Series NX Series Basic information Purpose of use ▲ ▲ ▲ ▲ ▲ ▲ ● ▲ ▲ ▲ Learning about error management and corrections ● Maintenance ● ● Using motion control ● Using EtherCAT ● Using EtherNet/IP ●...
Manual Structure Manual Structure Page Structure The following page structure is used in this manual. Level 1 heading 4 Installation and Wiring Level 2 heading Mounting Units Level 3 heading Level 2 heading Gives the current headings. Level 3 heading 4-3-1 Connecting Controller Components The Units that make up an NJ-series Controller can be connected simply by pressing the Units together...
Page 7
Manual Structure Special Information Special information in this manual is classified as follows: Precautions for Safe Use Precautions on what to do and what not to do to ensure safe usage of the product. Precautions for Correct Use Precautions on what to do and what not to do to ensure proper operation and performance. Additional Information Additional information to read as required.
Page 8
Manual Structure CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Sections in this Manual Sections in this Manual Introduction FTP Server Automatic Clock Installing Ethernet Adjustment Networks Assigning Device Vari- SNMP Agent ables for CJ-series Units Communications Per- Determining formance and Commu- IP Addresses nications Load Sysmac Studio Settings Troubleshooting for the EtherNet/IP Unit Appendices Testing Communications...
Page 10
Sections in this Manual CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
CONTENTS CONTENTS Introduction....................... 1 Relevant Manuals...................... 2 Manual Structure ...................... 4 Sections in this Manual.................... 7 Read and Understand this Manual................ 15 Safety Precautions ....................19 Precautions for Safe Use ..................24 Precautions for Correct Use .................. 30 Regulations and Standards ................... 33 Unit Versions......................
Page 12
Mounting the Unit to the CPU Rack or Expansion Rack ............2-3 Selecting the Network Devices....................2-4 2-3-1 Recommended Network Devices....................2-4 2-3-2 Network Devices Manufactured by OMRON ................2-5 2-3-3 Ethernet Switch Types ........................ 2-5 2-3-4 Ethernet Switch Functions ......................2-5 2-3-5 Precautions for Ethernet Switch Selection ..................
Page 13
CONTENTS Section 5 Sysmac Studio Settings for the EtherNet/IP Unit Unit Settings for the EtherNet/IP Unit ..................5-2 5-1-1 Updating the Unit Settings ......................5-2 5-1-2 Restoring the Default Unit Settings..................... 5-2 TCP/IP Settings Display ......................5-3 Link Settings Display ......................5-5 FTP Settings Display .......................
Page 14
CONTENTS Section 8 Message Communications Overview of the CIP Message Communications Service............. 8-2 8-1-1 Overview of the CIP Message Communications Service............8-2 8-1-2 Message Communications Service Specifications ..............8-2 Using CIP Message Communications ................... 8-3 8-2-1 Overview ............................. 8-3 8-2-2 CIP Communications Instructions ....................
Page 15
CONTENTS 10-2-3 Updating the Clock Information ....................10-4 Section 11 SNMP Agent 11-1 SNMP Agent ........................... 11-2 11-1-1 Overview........................... 11-2 11-1-2 Specifications..........................11-3 11-1-3 SNMP Messages ........................11-3 11-1-4 MIB Specifications ........................11-4 11-2 Procedure to Use the SNMP Agent ..................11-19 11-2-1 Procedures ..........................
Page 16
CONTENTS 13-7 Cleaning and Maintenance ....................13-52 13-7-1 Cleaning ..........................13-52 13-7-2 Inspection..........................13-52 13-8 Precautions on Equipment Replacement................13-54 13-8-1 Precautions When Replacing the EtherNet/IP Unit..............13-54 13-8-2 Settings Required after Unit Replacement................13-54 13-8-3 EtherNet/IP Unit Replacement Procedure ................13-55 Appendices A-1 Functional Comparison of EtherNet/IP Functionality on NJ-series CPU Units and Other Series........................A-2...
WHETHER SUCH CLAIM IS BASED ON CONTRACT, WARRANTY, NEGLIGENCE, OR STRICT LIABILITY. In no event shall the responsibility of OMRON for any act exceed the individual price of the product on which liability is asserted. IN NO EVENT SHALL OMRON BE RESPONSIBLE FOR WARRANTY, REPAIR, OR OTHER CLAIMS...
Page 18
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.
Page 19
Performance data given in this manual is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of OMRON's test conditions, and the users must correlate it to actual application requirements. Actual performance is subject to the OMRON Warranty and Limitations of Liability.
Page 20
Read and Understand this Manual CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Safety Precautions Safety Precautions Definition of Precautionary Information The following notation is used in this manual to provide precautions required to ensure safe usage of a CJ-series EtherNet/IP Unit. The safety precautions that are provided are extremely important to safety. Always read and heed the information provided in all safety precautions.
Page 22
Safety Precautions Symbols The circle and slash symbol indicates operations that you must not do. The specific operation is shown in the circle and explained in text. This example indicates prohibiting disassembly. The triangle symbol indicates precautions (including warnings). The specific operation is shown in the triangle and explained in text. This example indicates a precaution for electric shock.
Page 23
Safety Precautions Warnings WARNING During Power Supply Do not touch any of the terminals or terminal blocks while the power is being supplied. Doing so may result in electric shock. Do not attempt to take any Unit apart. In particular, high-voltage parts are present in the Power Supply Unit while power is supplied or immediately after power is turned OFF.
Page 24
Safety Precautions Unintended outputs may occur when an error occurs in variable memory or in memory used for CJ-series Units. As a countermeasure for such prob- lems, external safety measures must be provided to ensure safe operation of the system. Provide measures in the communications system and user program to ensure safety in the overall system even if errors or malfunctions occur in data link communications or remote I/O communications.
Page 25
Safety Precautions Cautions Caution Application Do not touch any Unit when power is being supplied or immediately after the power supply is turned OFF. Doing so may result in burn injury. Wiring Be sure that all terminal screws and cable connector screws are tightened to the torque specified in the relevant manuals.
Precautions for Safe Use Precautions for Safe Use Disassembly and Dropping • Do not attempt to disassemble, repair, or modify any Units. Doing so may result in malfunction or fire. • Do not drop any Unit or subject it to abnormal vibration or shock. Doing so may result in Unit malfunc- tion or burning.
Page 27
Precautions for Safe Use • Do not apply voltages or connect loads to the Output Units or slaves in excess of the maximum rat- ings. • Surge current occurs when the power supply is turned ON. When selecting fuses or breakers for external circuits, consider the above precaution and allow sufficient margin in shut-off performance.
Page 28
Precautions for Safe Use • Connecting cables or wiring the system • Connecting or disconnecting the connectors The Power Supply Unit may continue to supply power to the rest of the Controller for a few seconds after the power supply turns OFF. The PWR indicator is lit during this time. Confirm that the PWR indicator is not lit before you perform any of the above.
Page 29
EtherNet/IP Communications • All related EtherNet/IP nodes are reset when you transfer the settings for the CJ1W-EIP21 Ether- Net/IP Unit (including IP addresses and tag data links settings) from the Support Software. Confirm that the system will not be adversely affected by resetting nodes before you transfer the settings.
Page 30
Precautions for Safe Use • After you transfer the user program, the CPU Unit is restarted and communications with the Ether- CAT slaves are cut off. During that period, the slave outputs behave according to the slave settings. The time that communications are cut off depends on the EtherCAT network configuration. Before you transfer the user program, confirm that the system will not be adversely affected.
Page 31
Precautions for Safe Use • The Servomotor or Servo Drive was changed since the data was backed up. • The absolute encoder was set up after the data was backed up. • The absolute data for the absolute encoder was lost. Battery Replacement •...
Precautions for Correct Use Precautions for Correct Use Storage, Mounting, and Wiring • Do not operate or store the Controller in the following locations. Operation may stop or malfunctions may occur. • Locations subject to direct sunlight • Locations subject to temperatures or humidity outside the range specified in the specifications •...
Page 33
Precautions for Correct Use Error Processing • In applications that use the results of instructions that read the error status, consider the affect on the system when errors are detected and program error processing accordingly. For example, even the detection of a minor error, such as Battery replacement during operation, can affect the system depending on how the user program is written.
Page 34
Precautions for Correct Use Battery Replacement • Be sure to install a replacement Battery within two years of the production date shown on the Battery label. • Turn ON the power after replacing the Battery for a CPU Unit that has been unused for a long time. Leaving the CPU Unit unused again without turning ON the power even once after the Battery is replaced may result in a shorter Battery life.
Concepts EMC Directive OMRON devices that comply with EC Directives also conform to the related EMC standards so that they can be more easily built into other devices or the overall machine. The actual products have been checked for conformity to EMC standards.* Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer.
Gives the lot number and serial number of the Unit. serial number DDMYY: Lot number, @: For use by OMRON, xxxx: Serial number “M” gives the month (1 to 9: January to September, X: October, Y: November, Z: December) MAC address Gives the MAC address of the EtherNet/IP Unit.
Page 37
Unit Versions Simple Display Detailed Display In this example, “Ver.1.00” is displayed next to the unit model. The following items are displayed. CPU Unit CJ-series Units Unit model Unit model Unit version Unit version Lot number Lot number Rack number, slot number, and unit number ...
Page 38
There are also places in this manual where the unit version of the EtherNet/IP Unit is called the revision (“Rev.”). CIP Revision The following table gives the CIP revision that is supported by the unit version of the EtherNet/IP Unit. CJ1W-EIP21 Unit version CIP revision 2.04...
Sysmac Studio. W465 CS1W-EIP21 Learning how to use an Information on using an EtherNet/IP Unit that is EtherNet/IP Units CJ1W-EIP21 EtherNet/IP Unit connected to a CS/CJ-series CPU Unit is pro- Operation Manual CJ2H-CPU6@-EIP vided. CJ2M-CPU3@ Information is provided on the basic setup, tag data links, and FINS communications.
Page 40
Related Manuals Manual name Cat. No. Model numbers Application Description CJ-series Special Unit W490 CJ1W-@@@@ Learning how to use CJ- The methods and precautions for using CJ- Manuals for NJ-series W498 series Units with an NJ- series Units with an NJ501 CPU Unit are CPU Unit W491 series CPU Unit.
Revision History Revision History A manual revision code appears as a suffix to the catalog number on the front and back covers of the manual. W495-E1-05 Cat. No. Revision code Revision code Date Revised content March 2012 Original production May 2012 •...
Page 42
Revision History CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
1 Introduction Introduction 1-1-1 EtherNet/IP Features EtherNet/IP is an industrial multi-vendor network that uses Ethernet. The EtherNet/IP specifications are open standards managed by the ODVA (Open DeviceNet Vendor Association), just like DeviceNet. Eth- erNet/IP is not just a network between Controllers. It is also used as a field network. Because Ether- Net/IP uses standard Ethernet technology, various general-purpose Ethernet devices can be used in the network.
1 Introduction 1-1-2 Features of the EtherNet/IP Unit Tag Data Links Cyclic communications between Controllers or between Controllers and other devices are possible on an EtherNet/IP network. Tag data links can quickly perform data exchanges for up to 184,832 words of data.
Page 46
1 Introduction Complete Troubleshooting Functions A variety of functions are provided to quickly identify and handle errors. • Self-diagnosis at startup • Event log that records the time of occurrence and other error details Additional Information CIP (Common Industrial Protocol) CIP is a shared industrial protocol for the OSI application layer.
(1) Per Node These Units are used to connect to an EtherNet/IP net- NJ501-@@@@ NJ-series CPU Unit (built-in Ether- work. Net/IP port) CJ-series CJ1W-EIP21 EtherNet/IP Unit OMRON PLCs CJ2H-CPU@@-EIP or CJ2M-CPU3@ CJ2 CPU Unit (built-in EtherNet/IP port) CS-series CS1W-EIP21 EtherNet/IP Unit...
1 Introduction 1-2-2 Support Software Required to Construct a Network This section describes the Support Software that is required to construct an EtherNet/IP network. The EtherNet/IP Unit has Ethernet Settings and Tag Data Link Settings, which are stored in the non-volatile memory in the EtherNet/IP Unit.
Number of servers that can communicate at one time: 32 CIP message ser- max. vice: Explicit Supported. messages CIP routing is supported for the following remote Units: CIP routing NJ501-@@@@, NJ301-@@@@, CS1W-EIP21, CJ1W-EIP21, CJ2H-CPU@@-EIP, and CJ2M-CPU3@. CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Page 50
1 Introduction Item Specifications Agents SNMPv1 or SNMPv2c SNMP MIB-II EtherNet/IP conformance test Conforms to A8 10Base-T or 100Base-TX Ethernet interface Auto negotiation or fixed settings NJ301-@@@@ CPU Units (unit version 1.01 or later) Applicable CPU Units NJ501-@@@@ CPU Units (unit version 1.01 or later) Unit current consumption 5 VDC 410 mA max.
Ethernet Address Notation A specific Ethernet address is allocated to all devices connected to the Ethernet network. The Ether- Net/IP Unit's address is listed in 12-digit hexadecimal on the right side of the Unit. CJ1W-EIP21 ETHERNET/IP UNIT Lot No.
Page 52
1 Introduction Additional Information An IP address label is included with the EtherNet/IP Unit, so the user can record the user-set IP address and subnet mask on the label, and affix the label to the front of the Unit. When this label is affixed to the front of the Unit, it is easy to confirm the Unit's IP address and subnet mask.
Page 53
1 Introduction Indicators (LEDs) An EtherNet/IP Unit is equipped with the following indicators that indicate the operating status of the node itself and the overall network. EIP 21 COMM 100M Status Indicators: MS, NS, COMM, 100M, and 10M The MS (Module Status) indicator indicates the status of the node itself and the NS (Network Status) indicator indicates the status of the network.
Page 54
1 Introduction Seven-segment Display When the power is turned ON (or the Unit is restarted), all of the segments will flash twice, the IP address set in the EtherNet/IP Unit will be displayed on the 7-segment display just once, from right to left.
Page 55
1 Introduction Example 2: Displaying Multiple Error Sources • A d6 error (failed to establish connection) occurred with IP address 192.168.250.8. • A d6 error (failed to establish connection) occurred with IP address 192.168.250.9. • A d5 error (verification error, target nonexistent) occurred with IP address 192.168.250.64. •...
Page 56
1 Introduction 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 device error is being displayed. Example: Displaying the Following Errors •...
The node address can be set to any number in the setting range (01 to FE), as long as the same address is not set on another node in the network. Additional Information • If the node address setting is changed during operation, the MS Indicator will flash red. 1-3-3 Dimensions • CJ1W-EIP21 65 mm 31 mm EIP21 COMM 100M...
1 Introduction Introduction to Communications Services 1-4-1 CIP (Common Industrial Protocol) Communications Services Tag Data Links (Cyclic Communications) A program is not required to perform cyclic data exchanges with other devices on the EtherNet/IP net- work. Normally, a connection is started with the target device for each tag set that was created with the Network Configurator to start communications for tag data links for an EtherNet/IP Unit.
Page 59
1 Introduction Message Communications (Class 3 UCMM: Unconnected Message Service) User-specified CIP commands can be sent to devices on the EtherNet/IP network. CIP commands, such as those for reading and writing data, can be sent and their responses received by executing the CIP Send instruction from the user program in the NJ-series CPU Unit (without a connection).
1 Introduction 1-4-2 BOOTP Client You set the EtherNet/IP Unit in the BOOTP settings to use the BOOTP client to obtain settings, such as the EtherNet/IP Unit IP address. BOOTP server BOOTP command Ethernet IP address EtherNet/IP Unit EtherNet/IP Unit BOOTP client The EtherNet/IP Unit IP address is obtained from the BOOTP server when the power is turned ON.
1 Introduction 1-4-4 Automatic Clock Adjustment With the EtherNet/IP Unit, clock information is read from the SNTP server at the specified times or when the Clock Information Adjustment Switch is changed to TRUE. The internal clock time in the CPU Unit is updated with the read time.
1-4-6 SNMP Agent The SNMP agent passes internal status information from the EtherNet/IP Unit to network management software that uses an SNMP manager. Monitoring Ethernet/IP Devices CJ1W-EIP21 0C_JB-191.158.038 CJ1W-EIP21 0C_JB CJ1W-EIP21 0C_JB-191.158.072 CJ1W-EIP21CJ1W-EIP21CJ1W-EIP21CJ1W-EIP21CJ1W-EIP21CJ1W-EIP21CJ1W-EIP191.108.039 191 068 038 EIP21CJ1W-EIP21 CJ21-191.168.035 CJ1W-EIP21 0C_JB-191.158.073 CJ1W-EIP21 0C_JB-191.158.074...
1 Introduction EtherNet/IP Communications Procedures 1-5-1 Basic Operation This section provides the basic procedures for the EtherNet/IP Unit. Use the Sysmac Studio to create the programs and set the Unit. Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for specific procedures on the Sysmac Studio.
Page 64
1 Introduction Turn ON the power supply to the Controller. Turn ON the power supply to the Controller. If there is a Unit Configuration registered in the CPU Unit and it does not agree with the actual configuration of the Units, an I/O Setting Check Error will occur. If that occurs, reset the Controller according to step 10, below, to clear the error.
1 Introduction 1-5-2 Procedure for Using Tag Data Links This section gives the setup procedure up to starting tag data links. Use the Network Configurator to set the tag data link parameters to use for tag data links. 7-2-4 Creating Tags and Tag Import the settings of the variables that you specified for the tags on Sets the Sysmac Studio to the Network Configurator.
1 Introduction 1-5-3 Using EtherNet/IP Network Functions Using the Message Communications Service • CIP Communications Instructions Section 8 Message Commu- Execute CIP communications instructions in the user program. nications ↓ 1-3-2 Part Names and Func- Check operation. tions • Use the Sysmac Studio to check the communications status with the end codes Section 13 Troubleshooting of the instructions (Done, Err, and ErrorID).
Page 67
1 Introduction Using BOOTP Section 5 Sysmac Studio Use the Sysmac Studio to set the initial settings of the EtherNet/IP Settings for the EtherNet/IP Function Module. Unit • Set the BOOTP settings. ↓ Check operation. • Check the event log to see if BOOTP started. •...
Page 68
1 Introduction 1-26 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
2 Installing Ethernet Networks Switch Settings on the Front Panel of the EtherNet/IP Unit 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 Controller. Use a small screwdriver to make the setting, taking care not to damage the rotary switch.
II: I/O Interface Unit Additional Information The CJ1W-EIP21 EtherNet/IP Unit's maximum current consumption is 410 mA. Be sure that the total current consumption of all the Units that are mounted to the same CPU Rack or Expansion Rack does not exceed the output capacity of the Power Supply Unit.
Kuramo Electric Co., Ltd. tor pairs: AWG 22 × Co., Ltd. OMR* 2 pairs RJ45 Assembly OMRON XS6G-T421-1* OMRON Corporation, Cus- Connectors tomer Support Center Sizes and conduc- Cables Fujikura Ltd. F-LINK-E Kanetsu Planning Department tor pairs: 0.5 mm ×...
Ethernet switch as IGMP snooping or GMRP. “Specific nodes” are nodes equipped with an IGMP client that have made transfer requests to the Ethernet switch. (OMRON EtherNet/IP Units are equipped with an IGMP client.) When the Ethernet switch does not use multicast filtering, multi- cast packets are sent to all nodes, just like broadcast packets, which increases the traffic in the net- work.
Managed L2 Ethernet Provided. Provided. Both functions must be set switches with a special software tool. OMRON W4S1-series None Provided. L4 QoS is set with a switch. No Ethernet switches software tool is necessary. Additional Information If the Network Configurator is used to set the connection type in the connection settings to a mul- ticast connection, multicast packets are used.
Page 75
2 Installing Ethernet Networks Selecting the Ethernet Switch Based on the Ethernet Switch’s Supported Functions L2 Ethernet Switch without Multicast Filtering We recommend this kind of Ethernet switch when only tag data links are executed and any of the fol- lowing conditions is met.
2 Installing Ethernet Networks Network Installation 2-4-1 Basic Installation Precautions • Take the greatest care when you install the Ethernet System. Be sure to follow ISO 8802-3 specifica- tions. Be sure you understand them before attempting to install an Ethernet System. •...
Page 77
2 Installing Ethernet Networks • Do not lay the twisted-pair cable in locations subject to excessive dirt and dust or to oil mist or other contaminants. Ethernet Switch Installation Environment Precautions • Do not ground the Ethernet switch in the same location as a drive-system component, such as an inverter.
2 Installing Ethernet Networks Connecting to the Network 2-5-1 Ethernet Connectors The following standards and specifications apply to the connectors for the Ethernet twisted-pair cable. • Electrical specifications: Conforming to IEEE 802.3 standards. • Connector structure: RJ45 8-pin Modular Connector (conforming to ISO 8877) Signal direc- Connector pin Signal name...
2 Installing Ethernet Networks 2-5-3 Noise Countermeasures for Contact Output Units When an EtherNet/IP Unit and Contact Output Unit are mounted in the same Controller, communica- tions errors may occur due to the noise that is generated by the contact outputs. Take either of the fol- lowing countermeasures.
Page 80
2 Installing Ethernet Networks 2-12 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
3 Assigning Device Variables for CJ-series Units Data Exchange with the CPU Unit Data exchange between the EtherNet/IP Unit and CPU Unit is performed with the I/O ports that are assigned to the EtherNet/IP Unit and, if required, the memory used for CJ-series Units. Refer to 3-2 Device Variables for the CJ-series Unit for information on I/O ports.
Page 83
3 Assigning Device Variables for CJ-series Units Device Variables for CJ-series Unit A device variable for a CJ-series Unit is a variable with an AT specification to an I/O port. In the user program, you can use device variables for a CJ-series Unit to access Configuration Units, such as the EtherNet/IP Unit.
Page 84
3 Assigning Device Variables for CJ-series Units User-defined Variables User-defined variables are used to perform tag data links and other communications for an EtherNet/IP Unit that is connected to an NJ-series CPU Unit. For details on user-defined variables, refer to the NJ- series CPU Unit Software User’s Manual (Cat.
3 Assigning Device Variables for CJ-series Units 3-1-2 Specifying and Creating Variables Specifying Device Variables for CJ-series Units Assign the device variables for the CJ-series Unit to the I/O ports in the I/O Map on the Sysmac Studio. Specify the assigned variable names as given below. (1) Select existing variables and assign them.
3 Assigning Device Variables for CJ-series Units Device Variables for the CJ-series Unit The section describes the device variables for the CJ-series Unit individually. In this section, the variable names that are created automatically in the I/O Map are used. 3-2-1 Assigning Device Variables for CJ-series Units An NJ-series Controller predefines the following three types of data as I/O ports for the operating data...
Page 87
3 Assigning Device Variables for CJ-series Units Tag Data Link Stop Bit (*_TDLStopCmd) Stop the tag data links by changing this variable to TRUE. After the tag data links stop, they will remain stopped until the Unit is restarted or the Tag Data Link Start Bit is changed to TRUE. (The tag data links will also start automatically when the tag data link parameter settings are downloaded from the Network Configurator.) If the tag data links are already stopped, the signal will be ignored.
3 Assigning Device Variables for CJ-series Units 3-2-3 Device Variables for the CJ-series Unit for Status These variables are used for inputs from the EtherNet/IP Unit to the CPU Unit. Target PLC Information This variable provides information on the target PLCs that are connected to the EtherNet/IP Unit when the EtherNet/IP Unit is the originator.
Page 89
3 Assigning Device Variables for CJ-series Units Unit Status Information This variable gives the status of the EtherNet/IP Unit. Unit Status 1 (EtherNet/IP Unit to CPU Unit) (*_UnitSta1) Device variable name for CJ- Data Meaning Description series Unit type *_UnitSta1 WORD Unit Status 1...
Page 90
3 Assigning Device Variables for CJ-series Units Device variable name for CJ- Data Meaning Description series Unit type *_IPAdrDupErr BOOL IP Address Duplica- TRUE: An ARP was sent with the specified IP tion Error address, indicating that an IP address dupli- cation was detected.
Page 91
3 Assigning Device Variables for CJ-series Units Device variable name for CJ- Data Meaning Description series Unit type *_TDLOprSta BOOL Tag Data Link Oper- TRUE: The tag data links are operating. This vari- ating able changes to TRUE in the following cases: •...
Page 92
3 Assigning Device Variables for CJ-series Units Communications Status Information The status of the tag data links and Ethernet is given in the following variables. Communications Status 1 (EtherNet/IP Unit to CPU Unit) (*_CommSta1) The status of the tag data links is given in the following variable. Device variable name for CJ- Data Meaning...
Page 93
3 Assigning Device Variables for CJ-series Units Device variable name for CJ- Data Meaning Description series Unit type *_TDLAllRunSta BOOL All Tag Data Links TRUE: Tag data links are communicating in all con- Operating nections as the originator. FALSE: A tag data link failed in one or more connec- tions as the originator.
Page 94
3 Assigning Device Variables for CJ-series Units Device variable name for CJ- Data Meaning Description series Unit type *_DNSSvrErr BOOL DNS Server Error TRUE: The DNS client failed to connect to the DNS server (timeout). FALSE: DNS is not set up. Or, DNS server informa- tion is set and the connection was success- ful.
Page 95
3 Assigning Device Variables for CJ-series Units Target Node Information The following variables provide information on the target nodes that are connected to the EtherNet/IP Unit when the EtherNet/IP Unit is the originator. Additional Information These variables give the status of only nodes 0 to 63. If it is necessary to get the error status of nodes higher than node 63, refer to 3-3 User Definition Settings for the Status Area.
3 Assigning Device Variables for CJ-series Units 3-2-4 Device Variables for the CJ-series Unit for Setup IP Address Display/Setting Area (*_IPAdrCfg) Use the following variable to check or set the IP address of the EtherNet/IP Unit. Device variable name for CJ- Data Meaning Description...
3 Assigning Device Variables for CJ-series Units User Definition Settings for the Status Area 3-3-1 Introduction to User Definition Settings If the EtherNet/IP Unit is the originator of a connection, you can store the corresponding target node status information in a user-defined variable instead of the default device variable for the CJ-series Unit. Although the default device variable for CJ-series Unit provides information only for nodes 0 to 63, you can obtain the information for 256 nodes if you use user definition settings for an area.
3 Assigning Device Variables for CJ-series Units Information is stored for nodes 0 to 255. This variable is a union, which allows access with different data types. You can specify different data types to access the data: a BOOL array variable with 256 elements, 256 BOOL variables, or WORD variables.
Page 99
3 Assigning Device Variables for CJ-series Units Target Node PLC Operating Flags (EtherNet/IP Unit to CPU Unit) This variable gives the operating status of the target PLCs. It is valid only when the EtherNet/IP Unit is the originator. The elements of this variable are valid only when the corresponding elements in the Nor- mal Target Node Table is TRUE.
Page 100
3 Assigning Device Variables for CJ-series Units 3-20 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
4 Determining IP Addresses IP Addresses 4-1-1 IP Address Configuration IP addresses are made up of 32 bits of binary data that specify 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.
4 Determining IP Addresses 4-1-2 Allocating IP Addresses You must assign IP addresses nodes so that each IP address is assigned only once in the network or between several networks. 4-1-3 Subnet Masks Operation and management of a network can become very difficult if too many nodes are connected on a single network.
4 Determining IP Addresses Setting the IP Address of the EtherNet/IP Unit 4-2-1 Determining IP Addresses Use one of the following methods to set the IP address of the EtherNet/IP Unit. Setting a User-specified IP Address If you need to change the default IP address of the EtherNet/IP Unit or if you need to use the Ether- Net/IP Unit with another EtherNet/IP node, set the IP address to the required value.
4 Determining IP Addresses 4-2-2 Setting IP Addresses Use the Sysmac Studio to set the IP address of the EtherNet/IP Unit. Select the setting method for IP addresses. Set the IP address of the EtherNet/IP Unit in the Special Unit Setup that is registered in the Unit Configuration of the Sysmac Studio.
Page 106
4 Determining IP Addresses Additional Information If you cannot obtain the IP address from the BOOTP server or the obtained IP address is not cor- rect, select the Fixed setting Option in the IP Address Area and manually set the IP address, subnet mask, and default gateway.
4 Determining IP Addresses 4-2-3 Online Connection Connect the Sysmac Studio online to the NJ-series CPU Unit. Types of Connections between the CPU Unit and Computer That Runs the Sysmac Studio The CPU Unit and the computer that runs Sysmac Studio are connected as shown below via USB or Ethernet: USB Connection USB Direct Connection...
Page 108
4 Determining IP Addresses Precautions for Correct Use Precautions for Correct Use If there is more than one node with the same IP address in the EtherNet/IP network, the Ether- Net/IP Unit will connect to the node that it detects first. An IP Address Duplication Error will not occur.
Page 109
4 Determining IP Addresses Precautions for Correct Use Precautions for Correct Use • If the IP address is duplicated or not set correctly, communications are not possible via the EtherNet/IP network. • The IP address range shown below is used by the system and cannot be specified. 169.254.0.0 to 169.254.255.255 192.168.255.0 to 192.168.255.255 •...
4 Determining IP Addresses Private and Global Addresses 4-3-1 Private and Global Addresses There are two kinds of IP addresses, private and global. IP address Description Global address 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 billion can be allocated world- wide.
4 Determining IP Addresses 4-3-2 Using a Private Address for the EtherNet/IP Unit ● Intranet Explicit message CIP client on a computer, such as Sysmac Studio or Network Configurator Ethernet (EtherNet/IP) Communications in Firewall intranet Controller IP router EtherNet/IP Unit: Private address ●...
4 Determining IP Addresses 4-3-3 Using a Global Address for the EtherNet/IP Unit ● Intranet CIP client on a computer, such as Network Configurator Ethernet (EtherNet/IP) Firewall Communications over Internet Private address IP router Cannot connect to Internet ● Internet Global address (required) ●...
Page 113
Sysmac Studio Settings for the EtherNet/IP Unit 5-1 Unit Settings for the EtherNet/IP Unit ......5-2 5-1-1 Updating the Unit Settings .
5 Sysmac Studio Settings for the EtherNet/IP Unit Unit Settings for the EtherNet/IP Unit Set up the EtherNet/IP Unit on the Edit Special Unit Settings Tab Page on the Sysmac Studio. 5-1-1 Updating the Unit Settings To update the Unit settings in the EtherNet/IP Unit, first transfer them from the Sysmac Studio to the CPU Unit and then perform one of the following methods.
5 Sysmac Studio Settings for the EtherNet/IP Unit TCP/IP Settings Display IP Address Setting Description Default IP address setting method Fixed setting Select the setting method for the IP address for the EtherNet/IP Unit. • Fixed setting • Obtain from BOOTP server •...
Page 116
5 Sysmac Studio Settings for the EtherNet/IP Unit • Class-E IP addresses (240.0.0.0 to 255.255.255.255) IP Router Table Setting Description Default Destination IP address Set these settings when the EtherNet/IP Unit communicates with nodes on None other IP network segments via an IP router. Gateway address None You can set up to eight combinations of IP addresses and gateway...
5 Sysmac Studio Settings for the EtherNet/IP Unit Link Settings Display Setting Description Default LINK settings Set the baud rate for the EtherNet/IP Unit. Auto • Auto • 10 Mbps Half Duplex • 10 Mbps Full Duplex • 100 Mbps Half Duplex •...
5 Sysmac Studio Settings for the EtherNet/IP Unit FTP Settings Display Setting Description Default FTP server Specify whether to use the FTP server. Do not use. FTP connections from external devices will not be possible if the Do not use Option is selected.
5 Sysmac Studio Settings for the EtherNet/IP Unit SNTP Settings Display Setting Description Default SNTP server clock informa- Specify whether to get the clock information from the SNTP server and use Do not get. tion it to update the clock time in the CPU Unit. Set the port number to use to connect to the SNTP server to obtain clock 0 (port No.
Page 120
5 Sysmac Studio Settings for the EtherNet/IP Unit Additional Information Refer to Section 10 Automatic Clock Adjustment for details on obtaining clock information from the SNTP server. CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
5 Sysmac Studio Settings for the EtherNet/IP Unit SNMP Settings Display SNMP Service Setting Description Default SNMP Service Specify whether to use the SNMP monitor service. Do not use. If not using the SNMP monitor service is specified, an SNMP manager cannot connect from an external device.
Page 122
5 Sysmac Studio Settings for the EtherNet/IP Unit Recognition 1 Setting Description Default Recognition method Set the method to use to specify SNMP managers for which access is per- IP address mitted. • IP address • Host name Make these settings to permit access by only certain SNMP managers. Access is not allowed unless an IP address or host name is set.
5 Sysmac Studio Settings for the EtherNet/IP Unit SNMP Trap Settings Display SNMP Trap Setting Description Default SNMP trap Specify whether to use the SNMP trap (network error detection). Do not use. If the SNMP trap service is not enabled, SNMP traps are not sent to the SNMP manager.
Page 124
5 Sysmac Studio Settings for the EtherNet/IP Unit Trap 1 Setting Description Default Specifying method Set the specifying method for the SNMP manager destination for SNMP IP address traps. • IP address • Host name Set the IP address of the SNMP manager. 0.0.0.0 IP address (Set this setting if the specifying method in the trap 1 settings is set to the IP...
5 Sysmac Studio Settings for the EtherNet/IP Unit Status Area Settings Display Status Area Layout Setting Description Default Layout Type Select the variables in which to store the status information on the target nodes Default that are connected to the EtherNet/IP Unit when the EtherNet/IP Unit is the orig- inator.
Page 126
5 Sysmac Studio Settings for the EtherNet/IP Unit 5-14 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
6 Testing Communications Testing Communications If the basic settings (in particular the IP address and subnet mask) have been made correctly for the EtherNet/IP Unit, then it is possible to communicate with nodes on the EtherNet/IP network. This sec- tion describes how to use the PING command to test communications with the EtherNet/IP Unit. 6-1-1 PING Command The PING command sends an echo request packet to a remote node and receives an echo response...
6 Testing Communications 6-1-3 Host Computer Operation The PING command can be executed from the host computer to send an echo request packet to an EtherNet/IP Unit. The following example shows how to use the PING command in the host computer. Application Method Input the following command at the host computer’s prompt ($): $ ping IP_address (host_name)
Page 130
6 Testing Communications CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
7 Tag Data Link Functions Introduction to Tag Data Links 7-1-1 Tag Data Links Tag data links enable cyclic tag data exchanges on an EtherNet/IP network between Controllers or between Controllers and other devices. Variables are assigned to tags. (You can also assign I/O mem- ory addresses to tags.) The settings for tag data links are made with the Network Configurator.
7 Tag Data Link Functions 7-1-2 Data Link Data Areas Tags A tag is a unit that is used to exchange data with tag data links. Data is exchanged between the local network variables and remote network variables specified in the tags or between specified I/O memory areas.
Page 134
7 Tag Data Link Functions Example In the following example, input tags a to g at the originator are a tag set named SP1_IN and output tags i and ii are a tag set named SP1_OUT. A connection is set between these two tag sets. Originator device Target Device IP address: N...
Page 135
7 Tag Data Link Functions Number of Tags in Tag Sets You can set any tag sets containing one or more tags for the input and output tag sets for one con- nection. For example, you can set a tag set with one tag for the input tag set and set a tag set with more than one tag for the output tag set.
7 Tag Data Link Functions Note To enable a connection, each tag set must include only input tags or only output tags. (Both input and output tags cannot be included in the same tag set.) 7-1-3 Tag Data Link Functions and Specifications The tag data link and performance specifications of the NJ-series CPU Unit are given below.
7 Tag Data Link Functions 7-1-4 Overview of Operation In this manual, the connection information that is set is called tag data link parameters. This section describes how to set tag data links with the Sysmac Studio and the Network Configurator. Setting Network Variables (Sysmac Studio) First, create any variables that you want to use for tag data links as network variables in the Sysmac Studio.
Page 138
7 Tag Data Link Functions Setting and Downloading Tag Data Link Parameters (Network Configurator) The tag data link parameters (e.g., connection information) that are described below are created with the Network Configurator, and then the parameters are downloaded to all originator devices on the Eth- erNet/IP network.
Page 139
Tagset_in Version Information You can use the CJ1W-EIP21 EtherNet/IP Unit mounted to an NJ-series Controller with a CPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher. CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
7 Tag Data Link Functions Setting the Requested Packet Interval (RPI) The RPI is the data I/O refresh cycle on the Ethernet line when performing tag data links. The RPI can be set separately for each connection. You can set the EtherNet/IP Unit to between 0.5 and 10,000 ms (in 0.5-ms increments).
Page 141
7 Tag Data Link Functions • *_TargetPLCMdSta (Target Node PLC Operating Flags) • *_TargetPLCErrSta (Target Node PLC Error Flags) Sending the Target Node PLC Operating Flags of the Target Node with an IP Address of 192.168.250.2. IP address = 192.168.250.2 *_TargetPLCMdSta (Target Node PLC Operating Flags) Value of last byte = 2 Target ID = #002...
7 Tag Data Link Functions When you use multiple connections to communicate with one specific node, the information in the Con- troller status is stored in the following variables if the Controller status is specified in the input tags and the output tags for all connections.
Page 143
7 Tag Data Link Functions Maintaining Concurrency in the Tag Data in a Tag Set To maintain concurrency in the values of multiple tags in a tag set, the tags (variables with a Network Publish attribute) must satisfy the following four conditions. (1) The tags must be assigned to the same tag set (connection).
Page 144
7 Tag Data Link Functions • Not Setting Refreshing Tasks for Tags (Network Variables) Concurrency of the tags in the tag set is not maintained. NJ-series Controller NJ-series Controller Refreshing task Refreshing task Value of variable Tag set Tag set Value of variable values of Connection...
Page 145
7 Tag Data Link Functions Additional Information If a program needs to access a network variable with an AT specification, set the program in the primary periodic task so that it matches the refresh timing of the network variable that uses an AT specification.
Tag data links are set from the Network Configurator. Use the following procedure to start the Network Configurator. Using the Windows Start Menu − − To start the Network configurator, select OMRON Sysmac Studio Network Configurator for − EtherNetIP Network Configurator from the Windows Start Menu.
Page 147
7 Tag Data Link Functions Main Window The Main Window consists of a Hardware List and a Network Configuration Pane, as shown in the fol- lowing diagram. Network Configuration Pane: This is used to configure the network by placing devices to be configured and monitored. Hardware List: This is a list of devices that you can add to the network.
7 Tag Data Link Functions 7-2-2 Tag Data Link Setting Procedure This section describes the procedure to set tag data links (i.e., connection information). For data links between Controllers, the connection information is set only in the originator, i.e., the node that receives data.
Hardware List. Hardware List Name in Hardware List CIP revision Unit version CJ1W-EIP21(NJ) Rev. 2.04 Ver. 2.1 Right-click the registered device’s icon to display the pop-up menu, and select Change UNKNOWN Address. Set the IP address to match the node address (IP address) actually used in the device and click the OK Button.
7 Tag Data Link Functions 7-2-4 Creating Tags and Tag Sets You must create the tag sets and set member tags required to create connections for a registered Eth- erNet/IP Unit. You can set the network variables used in control programs for tags. This section first describes the basic procedure to create tags and tag sets (1, below).
Page 151
7 Tag Data Link Functions 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). Creating and Adding Tags Click the Edit Tags Button. The Edit Tags Dialog Box is displayed.
Page 152
7 Tag Data Link Functions Click the In - Consume Tab, and then click the New Button. The Edit Tag Dialog Box is dis- played. Enter the variable name directly into the Name Box. ( Example: Var_In_a) Additional Information • You can use the following characters in tag names. 0 to 9, A to Z, a to z, single-byte kana, _ (underbar), and multi-byte characters (e.g., Japanese) •...
Page 153
7 Tag Data Link Functions Tag that is directly assigned to an I/O memory address Tag that is assigned to a variable with a Network Publish attribute Input the size of the tag in bytes in the Size Field. Input the tag size so that it is the same as the data type size of the variable.
Page 154
7 Tag Data Link Functions After you register all of the required tags, click the OK Button in the Edit Tags Dialog Box. Precautions for Correct Use Precautions for Correct Use Make the following settings to refresh all of the tag data in the same tag set at the same time. •...
Page 155
7 Tag Data Link Functions Changing and Registering Tag Sets The following dialog box is displayed when the tags in the Edit Tags Dialog Box are registered directly as tag sets. If an input tag is already 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 origi- nally registered.
Page 156
7 Tag Data Link Functions A confirmation message is displayed. If the No Button is clicked, only the tag set is deleted. Click the No Button. 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.
Page 157
7 Tag Data Link Functions 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 Var_In_e, Var_In_f are newly added. After you register all of the required tags, click the OK Button at the bottom of the Edit Tags Dia- log Box.
Page 158
7 Tag Data Link Functions Select the tags that you want to add from the Candidate Tag List and click the Button. You can register up to eight tags in a tag set. (If you include the Controller status in the tag set, you can register up to only seven tags, and two bytes are added to the size.) Data is sent and received in the order it is displayed in the tag list.
Page 159
7 Tag Data Link Functions Importing to the Network Configurator Precautions for Correct Use Precautions for Correct Use Variables with a Network Publish attribute that have variable names that are the same as the I/O memory address notation, such as “0000” and “H0000” are not exported to CSV files. 1) Variable names that contain only single-byte numerals (Example: 001) 2) Variable names with the following single-byte letters (uppercase or lowercase) followed by sin- gle-byte numerals...
Page 160
7 Tag Data Link Functions After you import the variables to the tags, click the Yes Button to automatically create tag sets, or click the No Button to set up tag sets manually. The variables will be imported as shown below on the Tag Sets Tab Page. Each variable will be imported into a different tag set and the device parameters will be automatically edited.
7 Tag Data Link Functions Click the New Button to create a new tag set. To place more than one tag in an existing tag set, double-click the tag set, or select it and click the Edit Button. The Edit Tag Set Dialog Box is dis- played.
Page 162
7 Tag Data Link Functions Connection Settings (Connections Tab Page) Registering Devices in the Register Device List Double-click the icon of the device for which to make originator settings in the Network Configu- ration Pane of the Network Configurator. The Edit Device Parameters Dialog Box is displayed. Right-click the icon to display the pop-up menu, and select Parameter –...
Page 163
7 Tag Data Link Functions In the Unregister Device List, click the target device that requires connection settings so its color changes to gray, and click the Button. The selected target device is displayed in the Register Device List, as shown in the following diagram. Target node IDs are assigned to the devices that are registered in the Register Device List.
Page 164
7 Tag Data Link Functions Editing Settings for Individual Connections You can edit each connection separately. Note Refer to the following section for information on how to perform batch editing in a table format. Click the Connections Tab and then click the New Button. The following Edit Connection Dialog Box is displayed according to the type of device that is selected.
Page 165
Connection I/O Type Select Input Only (tag type) to use tag data links with a CS1W-EIP21, CJ1W- EIP21, CJ2B-EIP21, CJ2M-EIP21, CJ1W-EIP21 (CJ2), CJ1W-EIP21 (NJ), NJ301-@@@@, or NJ501-@@@@. When you create tag data links for other 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...
Page 166
Connection I/O Type Select InputOnly (tag type) to use tag data links with a CS1W-EIP21, CJ1W- EIP21, CJ2B-EIP21, CJ2M-EIP21, CJ1W-EIP21 (CJ2), CJ1W-EIP21 (NJ), NJ301-@@@@, or NJ501-@@@@. When you create tag data links for other 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 origina-...
Page 167
7 Tag Data Link Functions Confirming the Connections Settings An overview of the connections that were set in the Register Device List is displayed in the Con- nections Tab Page. Click the OK Button. The following kind of diagram is displayed. Indicates the IP address of the originator where the connection was set.
Page 168
7 Tag Data Link Functions − Automatically Setting Connections (Network Auto Connection) You can use automatic detection of the tag set names that are set for devices to automatically set con- nections between input and output tag sets with the same name (or the same names excluding speci- fied ellipses).
Page 169
7 Tag Data Link Functions Set the same tag set names for the output and input tag sets for the connection. The tag set names can also include forward and backward ellipses. Select Auto Connection Configuration from the Network Menu. The connections will be set automatically.
Page 170
7 Tag Data Link Functions A device connection structure tree is displayed when processing is completed. 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.
Set tags and tag sets for all devices before starting the Wizard. Refer to 7-2-4 Creating Tags and Tag Sets for the setting procedure. For tag data links between OMRON PLCs, a connection is created in the PLC (i.e., the origina- tor device) that receives data as input data.
Page 172
7 Tag Data Link Functions Create the connection following the instructions that are given by the Wizard after the Wizard starts. (See the following figure.) A list of tag sets is displayed on the right side of the Wizard Dialog Box with target devices that support receiving input data.
7 Tag Data Link Functions Click the Next Button to switch to the table in the following Wizard Dialog Box. Follow the instructions to select and input from the list box the input tag set of the originator device that receives the output tag set of the target device.
Page 174
(1) Refer to 7-2-4 Creating Tags and Tag Sets for information on creating the settings if the target is one of the OMRON EtherNet/IP devices given above. (2) If the target is another EtherNet/IP device, refer to the manual of that device and per- form settings as required.
Page 175
7 Tag Data Link Functions (2) Using Other EtherNet/IP Devices as Target The connection I/O type list box in the upper part of the Connection Settings Dialog Box dis- plays the connection I/O types that can be selected. Select the connection I/O type accord- ing to your application.
Page 176
7 Tag Data Link Functions Additional Information 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.
7 Tag Data Link Functions 7-2-8 Connecting the Network Configurator to the Network This section describes how to Connect the Network Configurator online. Connecting through Ethernet Precautions for Correct Use Precautions for Correct Use The first time you connect via Ethernet with Windows XP (SP2 or higher), Windows Vista, or Windows 7, you much change the Windows firewall settings.
Page 178
7 Tag Data Link Functions The Network Configurator will connect to the EtherNet/IP network. If the Network Configurator goes online normally, “Online” is displayed in the status bar at the bottom of the window. The network connection icon is displayed in blue on the Network Tab Page in which the Network Configurator is connected.
Page 179
7 Tag Data Link Functions Click the OK Button. Select the network to connect to. Connections through NJ-series CPU Unit’s USB Port Use the following procedure to connect to the EtherNet/IP Unit via the USB port on the CPU Unit. Select the communications interface.
7 Tag Data Link Functions 7-2-9 Downloading Tag Data Link Parameters To make tag data links, you must download tag data link parameters, such as tag set settings and con- nection settings, to all devices in the EtherNet/IP network. When the download operation is executed, the tag data link parameters are transferred to the EtherNet/IP Units that require the settings.
Page 181
7 Tag Data Link Functions Connect the Network Configurator online. There are two ways to download the parameters. Downloading to All Devices in the Network − Select Network Download. The following dialog box is displayed. Downloading Individually to Particular Devices Select the icon of the EtherNet/IP Unit to which you want to download.
Page 182
You can click the Download with Current mode Button to download the parameters even when one or more CPU Units is in RUN mode. The Download with Current mode Button is disabled if the EtherNet/IP Unit does not support this function (e.g., revision 1 of CJ1W-EIP21 or CS1W- EIP21).
7 Tag Data Link Functions 7-2-10 Uploading Tag Data Link Parameters You can upload tag data link parameters (such as the tag set settings and connection settings) from EtherNet/IP Units in the EtherNet/IP network. The following procedure shows how to upload the param- eters.
Page 184
7 Tag Data Link Functions Clicking the No Button: Performing a Batch Upload over the Network Parameters are uploaded from all devices on the network. The current Network Configuration Information will be lost. The following dialog box will be displayed. Select the devices for which to upload parameters and click the OK Button.
Page 185
7 Tag Data Link Functions Uploading Individually from Particular Devices Connect the Network Configurator online and select the icon of the EtherNet/IP Unit from which you want to upload the parameters. To select multiple nodes, press and hold the Shift Key while you select additional icons.
7 Tag Data Link Functions 7-2-11 Verifying the Tag Data Links Tag data link parameters (such as the tag set settings and connection settings) can be compared with the parameters of the EtherNet/IP Units in the EtherNet/IP network. The following procedure shows how to compare the parameters.
Page 187
7 Tag Data Link Functions Differences Found in the Device Type Click the OK Button or the Close Button. Verifying the Device Parameters Use the following procedure to compare the device parameters for the devices selected in the Network Configuration Pane with those of the devices connected on the EtherNet/IP network. The IP addresses, device types, and device parameters are compared.
Page 188
7 Tag Data Link Functions The following dialog box is displayed. Differences Not Found in the Comparison Differences Found in the Comparison Differences Found in the Device Type Click the OK Button or the Close Button. If multiple nodes have been selected and compared, the following message is displayed. Click the Yes Button.
7 Tag Data Link Functions 7-2-12 Starting and Stopping Tag Data Links Automatically Starting Tag Data Links Tag data links are automatically started immediately after the data link parameters are downloaded from the Network Configurator. (They are automatically started after the CPU Unit’s power is turned ON or the Unit is restarted.) Starting and Stopping Tag Data Links for the Entire Network You can start and stop tag data links for the entire network from the user program or from the Network...
Page 190
7 Tag Data Link Functions Starting and Stopping Tag Data Links for Individual Devices Using the Network Configurator You can start and stop tag data links for individual devices using the Connection Tab Page in the Monitor Device Dialog Box. This applies only to tag data links for which the device is the originator. Select Monitor from the Device Menu to access the Monitor Device Dialog Box.
7 Tag Data Link Functions 7-2-13 Clearing the Device Parameters You can clear the tag data link parameters that are saved in the EtherNet/IP Unit on the EtherNet/IP network to return them to their default settings. The following procedure shows how to clear the tag data link parameters.
7 Tag Data Link Functions Yes Button: The following dialog box is displayed. Select the Initialize tag data link configuration, and then emulate cycling power Option and then click the OK Button. Precautions for Correct Use Precautions for Correct Use The Controller is not restarted.
Page 193
7 Tag Data Link Functions Input the file name, and then click the Save Button. This completes the network configuration file save operation. When the network configuration is changed later, you can overwrite the existing network config- − uration file if you select File Save or click the Button.
7 Tag Data Link Functions 7-2-15 Reading a Network Configuration File You can read a previously saved network configuration file into the Network Configurator. − Select File Open or click the Button. The following dialog box is displayed. If the network configuration file that you want to read is not displayed, change to another folder. If you select the network configuration file that you want to read, that file name is displayed in the File name Field.
7 Tag Data Link Functions The Network Configurator’s Title Bar will display the name of the file that was read. Select any of the options as necessary. The options are listed below. Setting Description Select target network Allows you to select specific networks from the network configuration and open them.
Page 196
7 Tag Data Link Functions The following dialog box is displayed if there are parameter errors. Check the displayed details and review the settings. If an inconsistency is found, open the originator’s Edit Device Parameter Dialog Box and click the Connection Tab. The inconsistent connection in the Register Device List is displayed with a icon (instead of the normal icon).To change the connection setting and select a different target variable, select the connection as shown below and click the Edit Button.
7 Tag Data Link Functions 7-2-18 Displaying Device Status Device status is displayed using the following icons in Maintenance Mode. To enter Maintenance Mode, − select Large Icons Maintenance Mode from the View Menu. Icon Status Offline (white) Default (including no Controller Configurations and Setup) (gray) Idle (including when CPU Unit of Controller is in PROGRAM mode)
Table variable (*_EstbTargetSta) [0] to [63] is TRUE. Condition for the Target Node PLC Operating Flags (operating or stopped) (*_TargetPLCMdSta) (valid for OMRON Controllers only): (4) The Target PLC Operating Mode of the target node is TRUE. Condition for the Target PLC Error Information of the target node (valid for...
Page 200
7 Tag Data Link Functions Programming Example to Detect Normal Operation The following programming can be used to confirm that normal communications are being per- formed for each target node. If the Controller status is included in the tag data, the status of the Con- troller can also be detected.
Page 201
7 Tag Data Link Functions Programming Example to Detect Errors The following programming can be used to check for tag data link errors for each target node. This programming is used to detect errors only after the data links for all nodes have started normally. Online Normal Target Node Table (#1) (*_ETNOnlineSta)
Page 202
7 Tag Data Link Functions • You can use MC − MCR instructions and JMP instructions to process data only when the data links are operating normally as shown below. Node A data link normal operation flag Node A data processing Node B data link normal operation flag Node B data processing...
7 Tag Data Link Functions 7-3-2 Status Flags Related to Tag Data Links The status of the tag data links is reflected in the following device variables for the CJ-series Unit. Variable name Description *_TargetPLCMdSta [0] to [63] (Target Node PLC This variable shows the operating status of the target PLCs Operating Flags) that are connected with the EtherNet/IP Unit as the origina-...
Unit, use tag data link settings that match the Unit with the lower communications performance. Differences in Tag Data Link Performance Specifications CJ2M-CPU3@ NJ-series CPU Unit CS1W-EIP21, Unit version Item CJ1W-EIP21, or Ver. 1.02 Ver. 1.03 CJ2H-CPU6@-EIP 2.1 or later or earlier or later...
Page 205
Name in Hardware List of Network variable I/O memory address Network Configurator name specification specification EtherNet/IP Unit NJ-series CPU Unit NJ301-1100, NJ301-1200, NJ501-1300, NJ501-1400, or NJ501-1500 CJ1W-EIP21 CJ1W-EIP21 (NJ) CJ2H-CPU6@-EIP CJ2B-EIP21 CJ1W-EIP21 CJ1W-EIP21(CJ2) CJ2H-CPU6@ CJ1W-EIP21 CJ1W-EIP21(CJ2) CJ2M-CPU3@ CJ2M-EIP21 CJ1W-EIP21 CJ1W-EIP21(CJ2)
Page 206
7 Tag Data Link Functions 7-76 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Page 207
Message Communications 8-1 Overview of the CIP Message Communications Service ....8-2 8-1-1 Overview of the CIP Message Communications Service ....8-2 8-1-2 Message Communications Service Specifications .
8 Message Communications Overview of the CIP Message Communications Service 8-1-1 Overview of the CIP Message Communications Service CIP commands can be sent to devices on the EtherNet/IP network whenever they are required. You execute CIP_SEND instructions in a program in the NJ-series CPU Unit to send CIP commands, such as those to read and write data and to receive the responses.
8 Message Communications Using CIP Message Communications 8-2-1 Overview CIP communications instructions can be executed in the user program in the NJ-series CPU Unit to read and write variables in a NJ-series CPU Unit or a CJ2 CPU Unit on the EtherNet/IP network, and send specified CIP commands.
8 Message Communications Communica- Instruction Name Description tions method Open CIP Class This instruction opens a CIP class 3 connection with the specified CIP class 3 con- CIPOpen 3 Connection remote node. nection mes- sage Read Variable Reads the value of a variable with a Network Publish attribute from CIPRead Class 3 Explicit the specified remote Controller on the CIP network and stores the...
Page 211
8 Message Communications Local Controller Remote Controller (1) Variable specified. CIPRead Execute Handle (2) Reads data ‘VAR_1’ SrcDat starting at D0000 D00000 Size for the number of Assigned D00001 elements. VAR : ARRAY[0..9] OF WORD AT %D0 D00002 DstDat MyArray Network Publish attribute …….
8 Message Communications 8-2-4 Route Path The route path indicates the path from the local CPU Unit to the remote Controller on the network. Routing is performed for CIP communications instructions based on route paths. Route Path Notation The EPATH data type is used to give route paths. The basic format is shown below. Network_type_number \Remote_address The network type number and the remote address are determined as shown in the following table according to whether the route type is (1) a Unit on the CPU Rack or (2) a communications port on a...
Page 213
8 Message Communications Route Path Notation Examples The notation of the route path is different for communications on the built-in EtherNet/IP port and for communication on an EtherNet/IP Unit. This section provides examples of route paths. Communicating with an EtherNet/IP Unit Example: Communicating from the EtherNet/IP Unit mounted to CPU Unit 1 to CPU Unit 2 via the EtherNet/ IP Unit mounted to CPU Unit 2 EtherNet/IP...
Page 214
8 Message Communications (2) EtherNet/IP Unit 1 to CPU Unit 2 (built-in EtherNet/IP port) • Network type number: “02” (Output the command via EtherNet/IP port.) • Remote address: Specify the remote IP address. Route path:\01\#01\02\192.168.250.2 Access via a Relay Node Example: Communicating from CPU Unit 1 to CPU Unit 3 via CPU Unit 2 EtherNet/IP CPU Unit 2...
Page 215
(3) Unit address of remote CPU Unit Version Information You can use the CJ1W-EIP21 EtherNet/IP Unit mounted to an NJ-series Controller with a CPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher. CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Page 216
8 Message Communications Request Path (IOI) In the CIP world, each device is modeled as a collection of objects. An Object abstractly represents the specific configuration elements of a device. External request (example: read) Object Data Service Object Attributes Data Data Object Processing...
8 Message Communications 8-2-5 Preparing Derivative Data Types to Use CIP Communications Instructions To use CIP communications instructions, you must prepare derivative data type variables to input com- munications parameter settings in advance. Refer to the NJ-series CPU Unit Software User’s Manual (Cat.
Page 218
8 Message Communications Inputting the Values for Each Structure Variable Member Input the following values into the communications parameters that were registered as members of the structure variable. Variable name . ClasslD Rq+Path data type member name A . InstancelD A .
8 Message Communications Use the following procedure to create a variable in the variable table. Select the Array Check Box. Specify the element first number, the element last number, and the data type. Example: UINT Array Variable table Array Variable name Data type Specify the array element first Specifies the data type.
Page 220
8 Message Communications IP address: 192.168.250.2 Unit number: 0 Unit number: 1 EtherNet/IP Unit EtherNet/IP Unit Value of variable written. Variable name: WritingDat WriteDat Global variable Network Publish attribute Value of variable read. Variable name: OriginalDat ReadDat Global variable Network Publish attribute Message sent to read identity information (product name).
Page 222
8 Message Communications Processing after normal end Inline ST CIPUCMMSend_instance.Done Operating 1 // Processing after normal end Processing after error end. Inline ST CIPUCMMWrite_instance.Error Operating 1 // Processing after error end. CIPUCMMRead_instance.Error CIPUCMMSend_instance.Error 8-16 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Page 223
8 Message Communications Internal Variable Data type Initial value Comment Variables Trigger BOOL False Execution condition DoUCMMTrigger BOOL False Processing Stage Status change WriteDat Write data ReadDat Read data ReqPath _sREQUEST_ (ClassID:=0, InstanceID:=0, Request path PATH isAttributeID:=False, AttributeID:=0) RoutePathDat string[256] 01\#10\02\192.168.250.2\01\#00 Route path RespDat...
Page 224
8 Message Communications Stage :=INT#10; // Error end END_IF; // Request reading value of variable. CIPUCMMRead_instance( Execute :=TRUE, RoutePath :='RoutePathDat', // Route path TimeOut :=UINT#20, // Timeout value SrcDat :='OriginalDat', // Source variable name Size :=UINT#1, // Number of elements to read DstDat :=ReadDat);...
8 Message Communications 8-2-7 Sample Programming for CIP Connection (Class 3) Message Communications This sample uses CIP class 3 messages to write a variable, read a variable, and send a message. The Controllers are connected to an EtherNet/IP network. The IP address of the remote node is 192.168.250.2.
Page 226
8 Message Communications Variable Data type Initial value Comment OperatingEnd BOOL False Processing finished. Trigger BOOL False Execution condition Operating BOOL False Processing WriteDat 1234 Source data ReadDat Read data RoutePathDat string[256] 01\#10\02\192.168.250.1\01\#00 Route path ReqPath _sREQUEST_ (ClassID:=0, InstanceID:=0, isAt- Request path PATH tributeID:=False, AttributeID:=0)
Page 228
8 Message Communications Processing after normal end Inline ST CIPClose_instance.Done Operating 1 // Processing after normal end Processing after error end. Inline ST CIPOpen_instance.Error Operating 1 // Processing after error end. CIPWrite_instance.Error CIPRead_instance.Error CIPSend_instance.Error CIPClose_instance.Error 8-22 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Page 229
8 Message Communications Internal Variable Data type Initial value Comment Variables Trigger BOOL False Execution condition DoCIPTrigger BOOL False Processing Stage Status change WriteDat Write data ReadDat Read data RoutePathDat string[256] 01\#10\02\192.168.250.1\01\#00 Route path ReqPath _sREQUEST_ (ClassID:=0, InstanceID:=0, Request path PATH isAttributeID:=False, AttributeID:=0) RespDat...
Page 230
8 Message Communications IF (DoCIPTrigger=TRUE) THEN CASE Stage OF // Open CIP class 3 connection. CIPOpen_instance( Execute :=TRUE, TimeOut :=UINT#20, // Timeout time: 2.0 s RoutePath :='RoutePathDat'); // Route path IF (CIPOpen_instance.Done=TRUE) THEN Stage :=INT#2; // Normal end ELSIF (CIPOpen_instance.Error=TRUE) THEN Stage :=INT#10;...
Page 231
8 Message Communications // Send message ReqPath.ClassID :=UINT#01; ReqPath.InstanceID :=UINT#01; ReqPath.isAttributeID:=TRUE; ReqPath.AttributeID :=UINT#07; CIPSend_instance( Execute :=TRUE, Handle :=CIPOpen_instance.Handle, // Handle ServiceCode:=BYTE#16#0E, // Service code RqPath :=ReqPath, // Request path ServiceDat :=Dummy, // Service data Size :=UINT#0, // Number of elements RespServiceDat:=RespDat);...
8 Message Communications 8-2-8 Operation Timing Output Variable Operation and Timing You can monitor the values of the output variables to determine the status throughout instruction execu- tion. The following timing chart shows the operation of the output variables. Execute Busy (Executing) Changes to FALSE...
8 Message Communications Precautions for Correct Use Precautions for Correct Use If Execute changes back to FALSE before Done changes to TRUE, Done stays TRUE for only one task period. (Example 1) If you want to see if Done is TRUE at any time, make sure to keep Execute TRUE until you con- firm that Done is TRUE.
Page 234
8 Message Communications General sta- Status name Description of status tus code (hex) Service not supported The requested service was not supported or was not defined for this object class/instance. Invalid attribute value Invalid attribute data was detected. Attribute list error An attribute in the Get_Attribute_List or Set_Attribute_List response has a non-zero status.
Page 235
8 Message Communications General sta- Status name Description of status tus code (hex) Write-once value or medium An attempt was made to write to a write-once medium already written (e.g. WORM drive or PROM) that was previously written or cannot be changed. Invalid Reply Received An invalid reply was received.
Page 236
8 Message Communications General Sta- Additional Status (hex) Description tus (hex) 0116 Major or minor revision information in the key segment does not match the device. 0117 Invalid connection point. 0118 Invalid configuration format. 0119 Connection request failed because there is no controlling connection currently open.
8 Message Communications CIP Objects Sent to the EtherNet/IP Unit 8-3-1 CIP Objects Sent to the EtherNet/IP Unit The following CIP objects can be sent to an EtherNet/IP Unit. Object name Function Reference Identity object • Reads ID information from the CPU Unit. page 8-31 •...
Page 238
0666 hex NJ501-1500 0667 hex NJ301-1100 066B hex NJ301-1200 066C hex CJ1W-EIP21(NJ) 0668 hex (2) Status Details of the EtherNet/IP Unit Name Description Owned Indicates when the EtherNet/IP Unit has an open connection as the target of a tag data link.
8 Message Communications Name Description 12 to 15 Reserved Always FALSE. Service Codes Specify the service to execute with the service code. Supported services Service Parameter name Description code Classes Instances 01 hex Get_Attribute_All Reads the values of the attributes. Supported.
Page 240
8 Message Communications Instance Attribute ID The instance attribute ID specifies the attribute of the instance. Read/write data Attribute ID Parameter name Description Attribute Data Value type 01 hex Interface Configuration Indicates the IP address settings Read DWORD Bits 0 to 3: Interface Configuration Status status of the EtherNet/IP Unit.
8 Message Communications Request Paths (IOIs) to Specify Objects When you specify an object, specify the request path (IOI) for each service code as given below. Service code Class ID Instance ID Attribute ID 01 hex Get_Attribute_All F5 hex •...
Page 242
8 Message Communications Read/write data Attribute ID Parameter name Description Attribute Data Value type 04 hex Interface Counters The path to the link object in the Read Struct physical layer In Octets The number of octets received UDINT Reads the current value. through the interface.
Page 243
8 Message Communications Read/write data Attribute ID Parameter name Description Attribute Data Value type 05 hex Media Counters Media counters for the Ether- Read Struct Net/IP Unit. Alignment Errors Number of frames received that UDINT Reads the current value. were not octets in length. FCS Errors Number of frames received that UDINT...
Page 244
8 Message Communications (2) Software Switch Details Name Description Auto-negotiate FALSE: Auto-negotiation is disabled (communications setup is always set to 10 Mbps). TRUE: Auto-negotiation is enabled (communications setup is automatically set to 100 or 10 Mbps). ForcedDuplex Mode FALSE: Half duplex TRUE: Full duplex * When auto-negotiation is enabled (bit 0 is TRUE), this should always be FALSE.
8 Message Communications 8-3-5 Controller Object (Class ID: C4 Hex) This object is used to get the status of the Controller or to change the operating mode of the Controller. Class ID Specify C4 hex. Instance ID Specify 00 hex. Class Attribute ID The class attribute ID specifies the attribute (value) of the entire object.
Page 246
8 Message Communications 8-40 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
9 FTP Server Overview and Specifications 9-1-1 Overview The EtherNet/IP Unit contains an FTP (file transfer protocol) server. You can therefore send FTP com- mands from an FTP client software application on a computer on an Ethernet network to upload and download large files on the SD Memory Card.
Message Normal connection 220 xxx.xx.xx.xx yyyyyyyyyy FTP server (FTP Version z.zz) ready. xxx.xx.xx.xx: IP address of EtherNet/IP Unit yyyyyyyyyy: EtherNet/IP Unit model number (example: CJ1W-EIP21) z.zz: Firmware version of the EtherNet/IP Unit FTP server busy 221 FTP server busy, Goodbye.
Page 250
9 FTP Server Setting Restrictions The following restrictions apply to login names and passwords. • Only single-byte alphanumeric characters can be used in the login name and password. The login name and password are case sensitive. • A login name consists of up to 12 characters. •...
9 FTP Server Using the FTP Server Function 9-3-1 Procedure Make the basic settings. Refer to 1-5-1 Basic Operation for basic operations. Set up the FTP server on the Sysmac Studio. (Refer to 5-4 FTP Settings Display.) Select EtherNet/IP Unit Settings under Configuration − Controller Setup on the Sysmac Studio.
IP address of the EtherNet/IP Unit D:\tmp> ftp 192.168.250.2 Connected to 192.168.250.2 Results 220 192.168.250.2 CJ1W-EIP21 FTP server(FTP Version 1.11)ready. User(192.168.250.2:(none)): user1 Login name 331 Password required for user1. Password: 230 User user1 logged in.
9 FTP Server 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. The descriptions should also apply to most workstations, but slight differ- ences may arise. Refer to your workstation’s operation manuals for details. 9-5-1 Table of Commands The FTP commands which can be sent to the EtherNet/IP Unit are listed in the following table.
9 FTP Server 9-5-2 Using the Commands open Format open [IP_address or host_name_of_FTP_server] Function Connects the FTP server. Normally when the FTP client is booted, the FTP server IP address is specified to execute this command automatically. user ...
Page 255
9 FTP Server rename Format rename current_file_name new_file_name Function • Changes the specified current file name to the specified new file name. • If the new file name is already used on the remote host (on the SD Memory Card), the existing file is overwritten by the file for which the name was changed.
Page 256
9 FTP Server • Files on the SD Memory Card are stored in the MEMCARD directory under the root directory (/). • The root directory (/) is the directory that is used when you log onto the EtherNet/IP Unit. The MEMCARD directory does not exist if an SD Memory Card is not inserted in the CPU Unit or if the SD Memory Card power indicator on the CPU Unit is not lit.
Page 257
9 FTP Server • If an error occurs during file transfer, the file being transferred is deleted and the transmission of that file ends in an error. mput Format mput file_name Function • You can include wildcards (*) in the file name to transfer multiple local files to the remote host (to the SD Memory Card).
Page 258
9 FTP Server Function • Ends the FTP sessions. quit Format quit Function • Ends the FTP sessions. 9-12 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
9 FTP Server FTP Server Status 9-6-1 FTP Status You can use the following device variable for the CJ-series Unit to see whether the FTP server is oper- ating. Device variable name for CJ- Data Meaning Description series Unit type *_CommSta2 WORD Communications Sta-...
9 FTP Server Using SD Memory Card Operations The EtherNet/IP Unit can be used to upload and download the following data between the SD Memory Card and the FTP server. • Variables files (binary format) The following three methods are used by the CPU Unit to store and read data on the SD Memory Card. Sysmac Studio NJ-series EtherNet/IP...
9 FTP Server 9-7-2 File Types File Names Files are distinguished by assigning file names and extensions. The following characters can be used in file names and extensions: File names are not case sensitive. (Lowercase characters are converted to uppercase characters.) A to Z, a to z, 0 to 9, and the following symbols: $ % ’...
9 FTP Server 9-7-4 Format of Variable Data Binary Format The IOM format is a data format used for binary data specified by the ladder instructions, FileReadVar (Read Variables File) and FileWriteVar (Save Variables File), in the CPU Unit. You can also read and save arrays and structures.
9 FTP Server FTP File Transfer Time File transfers using FTP can require 30 or 40 minutes depending on the capacity of the file. Approxi- mate file transfer time are provided in the following table for reference. All times are in seconds unless otherwise specified.
9 FTP Server Application Example from a Host Computer 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 is registered in the hosts as host name [nj]. •...
Page 265
9 FTP Server Read the file RESULT.BIN and transfer it to the workstation. ftp> get RESULT.BIN Read file. 200 PORT command successful. 150 opening data connection for result.bin (**IPaddress**port#**) (**bytes). 226 Transfer complete. ** bytes received in *.*** seconds (**bytes/s) ftp>...
Page 266
9 FTP Server 9-20 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
10 Automatic Clock Adjustment 10-1 Automatic Clock Adjustment 10-1-1 Overview With the EtherNet/IP Unit, clock information is read from the SNTP server at the specified time or when the Clock Information Adjustment Switch variable is changed to TRUE. The internal clock time in the CPU Unit of the EtherNet/IP Unit is updated with the read time.
10 Automatic Clock Adjustment 10-2 Procedure to Use the Automatic Clock Adjustment Function 10-2-1 Procedure Make the basic settings. Refer to 1-5 EtherNet/IP Communications Procedures for the flow of basic operations. Make the following settings in the Special Unit Setup in the Controller Configurations and Setup of the Sysmac Studio.
10 Automatic Clock Adjustment 10-2-3 Updating the Clock Information When you change the following device variable for the CJ-series Unit to TRUE, the EtherNet/ IP Unit obtains the clock data from the SNTP server on the network, and applies it to the local CPU Unit. After applying the data, the variable automatically returns to FALSE.
11 SNMP Agent 11-1 SNMP Agent The SNMP (simple network management protocol) is a network management protocol. You can use the SNMP to manage any network that consists of devices that support SNMP. The server that manages the network is called the SNMP manager. The managed network devices are called SNMP agents. EtherNet/IP devices are monitored.
11 SNMP Agent SNMP Traps When a failure or some other specific problem occurs, a status report called a trap is sent. This enables monitoring changes in status even if the SNMP manager does not monitor the EtherNet/IP Unit period- ically.
11 SNMP Agent 11-1-4 MIB Specifications This section describes the specifications of the MIB that is supported by the EtherNet/IP Unit. MIB System Diagram The EtherNet/IP Unit MIB consists of the following tree structure. root iso (1) org (3) dod (6) internet (1) mgmt (2) mib-2 (1)
Page 275
Detailed Descriptions of MIB Objects System Group Sup- Subtree name Standard [(identifier) attribute] Implementation specifications port sysDescr (1) RO Sup- “OMRON Corporation” + Unit ported. model Device information (including hardware, OS, software names, and versions) ASCII characters only. sysObjectID (2) RO Sup- 1.3.6.1.4.1.16838.1.1025.2 ported.
Page 276
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ifMtu (4) RO Sup- 1500 ported. MTU value The maximum size (in octets) of datagrams that can be sent and received through this interface. ifSpeed (5) RO Sup- 10000000 ported.
Page 277
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ifOutOctets (16) RO Sup- According to the ported. standard. The number of octets of packets sent through this interface. This includes framing characters. ifOutUcast (17) RO Sup- According to the Pkts ported.
Page 278
11 SNMP Agent Ip Group: Ip Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ipForwarding (1) RW Sup- Not-forwarding (2) Indicates if the device operates as a gateway. IP ported. gateways can transfer datagrams, but IP hosts can perform only source routing. Some nodes take only one of these values.
Page 279
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ipOutNoRoutes (12) RO Sup- According to the ported. standard. The number of IP datagrams that were discarded because there was no transmission path. This counter includes datagrams that attempted to be sent through ipForwDatagrams, but were dis- carded because they were set with no-route.
Page 280
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ipAddrEntry (1) NA Row data of address information for IP addresses. The index is ipAdEntAddr. ipAdEntAddr (1) RO Sup- According to the ported. standard. The IP address. ipAdEntIfIndex (2) RO Sup- According to the...
Page 281
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ipRouteMetric1 (3) RW Sup- According to the ported. standard. The primary routing metric for this route. This value is determined based on the protocol speci- fied in ipRouteProto. Set to −1 if you do not want to use this metric (this is also the same for ipRo- uteMetric 2 through 4).
Page 282
11 SNMP Agent Sup- Implementation Subtree name Standard [(identifier) attribute] port specifications ipRouteMask (11) RW Sup- According to the ported. standard. The subnet mask value in relation to ipRouteDest. On systems that do not support a custom subnet mask value, this value is based on the address class of the ipRouteDest field.
Page 283
11 SNMP Agent Ip Group: Icmp Sup- Implementation Name Standard [(identifier) attribute] port specifications icmpInMsgs (1) RO Sup- According to the ported. standard. The total number of received ICMP messages. This includes messages counted by icmpInErrors. icmpInErrors (2) RO Sup- According to the ported.
Page 284
11 SNMP Agent Sup- Implementation Name Standard [(identifier) attribute] port specifications icmpOutRedirects (20) RO Sup- According to the ported. standard. The number of Redirect messages sent. icmpOutEchos (21) RO Sup- According to the ported. standard. The number of Echo (request) messages sent. icmpOutEchoReps (22) RO Sup-...
Page 285
11 SNMP Agent Ip Group: Tcp Sup- Implementation Name Standard [(identifier) attribute] port specifications tcpRtoAlgorithm (1) RO Sup- According to the ported. standard. The algorithm used to determine the timeout value for resending. Other (1): Other than the following items. Constant (2): A constant RTO value.
Page 286
11 SNMP Agent Sup- Implementation Name Standard [(identifier) attribute] port specifications tcpConnTable (13) NA According to the standard. The information table specific to the TCP connec- tion. tcpConnEntry (1) NA According to the standard. Entry information related to a specific TCP con- nection.
Page 287
11 SNMP Agent Ip Group: Udp Sup- Implementation Name Standard [(identifier) attribute] port specifications udpInDatagrams (1) RO Sup- According to the stan- ported. dard. The total number of UDP datagrams (i.e., the number of packets) sent to the UDP user. udpNoPorts (2) RO Sup-...
Page 288
11 SNMP Agent Standard [(identi- Name fier) attribute] snmpInBadValues (10) RO Sup- According to the ported. standard. The total number of PDUs received with an error status of badValue. snmpInReadOnlys (11) RO Sup- According to the ported. standard. The total number of PDUs received with an error status of readOnly.
11 SNMP Agent 11-2 Procedure to Use the SNMP Agent 11-2-1 Procedures Make the basic settings. Refer to 1-5 EtherNet/IP Communications Procedures for the flow of basic operations. Make the following settings in the Special Unit Setup in the Controller Configurations and Setup of the Sysmac Studio and then set the following on the SNMP Settings Display or SNMP Trap Settings Display.
Page 290
11 SNMP Agent Additional Information Make the settings in the SNMP Settings Dialog Box and SNMP Trap Dialog Box if the SNMP agent is used. Refer to 5-6 SNMP Settings Display for information on the SNMP Settings Dialog Box. Refer to 5-7 SNMP Trap Settings Display for information on the SNMP Trap Dialog Box.
Page 291
Communications Performance and Communications Load 12-1 Communications System ........12-2 12-1-1 Tag Data Link Communications Method .
12 Communications Performance and Communications Load 12-1 Communications System 12-1-1 Tag Data Link Communications Method Requested Packet Interval (RPI) Settings In tag data links for the EtherNet/IP Unit, the data transmission period is set for each connection as the RPI. The target device will send data (i.e., output tags) once each RPI, regardless of the number of nodes.
Page 293
12 Communications Performance and Communications Load Requested Packet Interval (RPI) and Bandwidth Usage (PPS) The number of packets transferred each second is called the used bandwidth or PPS (packets per sec- ond). The PPS is calculated from the RPI and heartbeat as follows for each connection: PPS used in a connection (pps) = (1,000 ÷...
12 Communications Performance and Communications Load 12-1-2 Calculating the Number of Connections The maximum number of connections for the EtherNet/IP Unit is 256. The number of connections must be set to 256 or less combining both connections that the Unit opens as the originator and connections that are opened from an originator with the Unit as the target.
12 Communications Performance and Communications Load 12-1-3 Packet Interval (RPI) Accuracy The send processing delay occurs in the EtherNet/IP Unit when data packets are sent once each packet interval (RPI). This delay varies with the RPI error shown in the following graph, so the send processing delay time is the maximum value for each RPI.
12 Communications Performance and Communications Load 12-2 Adjusting the Communications Load In an Ethernet network using an Ethernet switch, the network bandwidth is not shared by all of the nodes; independent transmission paths are established between individual nodes through the Ethernet switch.
12 Communications Performance and Communications Load 12-2-1 Checking Bandwidth Usage for Tag Data Links The Network Configurator can display the bandwidth actually used for tag data links at each Ether- Net/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.
12 Communications Performance and Communications Load Checking the Usage of Capacity and Network Bandwidth for Tag Data Links The percentage of the allowable communications bandwidth for tag data links for each EtherNet/IP Unit is displayed as the Usage of Capacity and the bandwidth used for tag data link communications in the entire network is displayed as the Mbit/s.
12 Communications Performance and Communications Load 12-2-3 Adjusting Device Bandwidth Usage Ethernet Switches without Multicast Filtering (100-Mbps Ethernet Switches) • Is the network bandwidth without multicast filtering usage under 100 Mbps for each node? If any node exceeds 100 Mbps, change the connections settings, such as the RPI. •...
12 Communications Performance and Communications Load 12-2-4 Changing the RPI You can check the usage of capacity offline without multicast filtering against the tag data link’s allow- able bandwidth by following the procedures in 12-2-1 Checking Bandwidth Usage for Tag Data Links. The usage of capacity without multicast filtering can be adjusted against the tag data link’s allowable bandwidth by changing the packet interval (RPI).
Page 301
12 Communications Performance and Communications Load The usage of capacity without multicast filtering can be adjusted against the tag data link’s allowable bandwidth by changing the associated devices’ packet interval (RPI) settings. The RPI settings can be changed with the following three methods. Method 1: Change All Connections to the Same RPI The usage of capacity without a multicast filter can be adjusted for all devices by changing the...
Page 302
12 Communications Performance and Communications Load Method 2: Change a Particular Device’s Packet Interval (RPI) Setting: The usage of capacity without multicast filtering can be adjusted for only a particular device against the tag data link’s allowable bandwidth by changing the packet intervals (RPI) settings for all of the device’s connections together.
Page 303
12 Communications Performance and Communications Load Method 3: Changing a Particular Connection’s Packet Interval (RPI) Setting: The usage of capacity without multicast filtering can be adjusted against the tag data link’s allowable bandwidth by individually changing the packet interval (RPI) for a particular connec- tion.
Page 304
12 Communications Performance and Communications Load (3) In the Register Device List, select the connection for which you want to change the RPI, and click the Edit Button. (4) The device’s Edit Connection Dialog Box will be displayed. Input a new packet inter- val (RPI) value, and click the OK Button.
Page 305
12 Communications Performance and Communications Load 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 12-2-3 Adjusting Device Bandwidth Usage. •...
Conditions • Connections: Example:Twenty CJ1W-EIP21 Units are connected to the network. Each device has one 100-word tag for transmission and nineteen 100-word tags for recep- tion, so that the Units exchange data mutually. By default, the packet intervals (RPIs) are set to 10 ms for all of the connections.
Page 307
12 Communications Performance and Communications Load Checking the Device Bandwidth Usage When the Detail Button is clicked in the Usage of Device Bandwidth Area, it is apparent that the per- centage of the allowed tag data link bandwidth being used by each device’s tag data link (Usage of Capacity) is 33.67%, as shown in the following dialog box.
Page 308
12 Communications Performance and Communications Load If the packet interval for all connections has been set to the same setting, the dialog box will show that the usage of capacity for the tag data link’s allowable communications bandwidth is 76.17% and the fastest set value is 4 ms.
Page 309
12 Communications Performance and Communications Load The percentage of the allowed tag data link bandwidth being used (Usage of Capacity) increases to 77.83% for devices 192.168.250.1 and 192.168.250.10, which indicates that the RPI is set to a higher speed for these devices’ connections. The Usage of Capacity values also indicate that the Usage of Capacity has increased (from 33.64% to 37.83%) for all of the other devices, which connect with devices 192.168.250.1 and 192.168.250.10.
Page 310
12 Communications Performance and Communications Load Information about the connection with device 192.168.250.10 is registered in the Register Device List. Double-click this connection to edit the settings. In the Edit Connection Dialog Box, input 1 ms as the new RPI value, and click the OK Button. The tag data link bandwidth used by device 192.168.250.1 (Usage of Capacity) increases to 48.67%, which indicates that a RPI is set to a higher speed for this device.
12 Communications Performance and Communications Load 12-3 I/O Response Time in Tag Data Links Additional Information This section provides information on the EtherNet/IP Unit. The data processing times for the built-in EtherNet/IP ports on the NJ501-@@@@/NJ301-@@@@ NJ-series CPU Units, CJ2HCPU6@- EIP CPU Units, and CJ2M-CPU3@ CPU Units are different. For details, refer to 7- 4 Tag Data Links with Models Other than NJ-Series CPU Units.
12 Communications Performance and Communications Load 12-3-2 EtherNet/IP Unit Data Processing Time This section describes the data processing time required to transfer data between the EtherNet/IP Unit and the CPU Unit. Data Processing Time Overview The time required for data processing consists of the following four elements. 1.
Page 313
12 Communications Performance and Communications Load 3. I/O Refreshing Time You must calculate the processing time for I/O refreshing between the EtherNet/IP Unit and the CPU Unit. (I/O refreshing is when the data is actually transferred.) The following two elements are relevant. •...
12 Communications Performance and Communications Load Data Processing Time Calculation Example Here we provide an example of how to perform the tag data link calculations described earlier for the following tag data transfers. • CPU Unit with Tag Data Links: NJ501-@@@@ •...
12 Communications Performance and Communications Load 12-3-4 Maximum Tag Data Link I/O Response Time You can find the maximum I/O response time from the total of (1) to (6) in the following figure. I/O refreshing (data link processing) User program execution Motion control System Common Processing 2 Tag data link I/O response time...
Page 316
12 Communications Performance and Communications Load (2) Send Data Processing Time This is the time until the variables in the CPU Unit are transferred to the EtherNet/IP Unit. Data is transferred during task processing. Therefore, the time required for send data processing is the same as the task period.
12 Communications Performance and Communications Load 12-4 Message Service Transmission Delay This section describes the delay time that occurs in CIP communications instruction (CIPWrite) service processing. Instruction (CIPWrite) executed. Instruction completed. IO UPG MC OI UPG MC OI UPG MC OI UPG MC Controller#1 Command generated.
Page 318
12 Communications Performance and Communications Load 12-28 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Troubleshooting This section describes the items to check when errors occur in the EtherNet/IP Func- tion Module. It includes error diagnosis and countermeasures for error indications, and error diagnosis and countermeasures for operating conditions. 13-1 Checking Status with the Network Configurator ....13-2 13-1-1 The Network Configurator's Device Monitor Function .
13 Troubleshooting 13-1 Checking Status with the Network Configurator 13-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. Additional Information If a communications error occurs during monitoring, the dialog box will continue to show the last information that was collected.
Page 321
13 Troubleshooting Status 1 Tab Page The Status 1 Tab Page shows the status that you can monitor with device variables for the CJ-series Unit (i.e., Unit Status 1, Unit Status 2, Communications Status 1, Communications Status 2, and Communications Status 3).
Page 322
13 Troubleshooting Status 2 Tab Page The Target Controller Status Area on the Status 2 Tab Page shows the Target Node PLC Operating Flags and Target Node PLC Error Flags from the Normal Target Node Table of the target table infor- mation that you can monitor with the device variables for the CJ-series Unit for status for the nodes for which the EtherNet/IP Unit is set as the originator of the tag data links.
Page 323
13 Troubleshooting Connection Tab Page Information about the target nodes that act as the originator is displayed. If all tag data link connec- tions to the node are established and normal, this information is displayed in blue. However, if any connection is broken the information is displayed in red.
Page 324
13 Troubleshooting Error History Tab Page The Error History Tab Page displays the error log stored in the EtherNet/IP Unit. Errors that occurred in the past are recorded, and can be saved in a computer file as required. In some cases, error records are cleared when the power is turned OFF, and in other cases the records are retained.
Page 325
13 Troubleshooting Controller Log Tab Page This tab page displays the Controller event log that is stored in the CPU Unit of the Controller where the EtherNet/IP is connected. The error log shows errors that have occurred. It can be saved in a file in the computer.
Page 326
13 Troubleshooting Tag Status Tab Page This tab page shows if the tag settings for each tag for tag data links are set so that data can be exchanged with the CPU Unit. The following status is displayed to show the status of the settings. Normal resolution completed: Normal data exchange is possible.
Page 327
13 Troubleshooting Ethernet Information Tab Page This tab page displays the communications status at the communications driver level of the Ether- Net/IP Unit. The error counter information can be used to confirm whether communications prob- lems have occurred. The tag data link information can be used to confirm characteristics such as the bandwidth usage (pps).
13 Troubleshooting 13-2 Using the LED Indicators and Display for Troubleshooting 13-2-1 Errors Occurring at the EtherNet/IP Unit Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to CPU Unit Data Exchange Flash- Not lit Duplicate unit The same unit num- Operation stops.
Page 329
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to CPU Unit Data Exchange Flash- CPU Unit mem- A parity error Records the error in the 0012 Register the routing ing red ory error occurred during an error log.
Page 330
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to CPU Unit Data Exchange Flash- CPU Unit service Servicing from the • If the Unit is the origina- 0002 Check and correct ing red monitoring error CPU Unit was not tor of the tag data link...
Page 331
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to CPU Unit Data Exchange Flash- CPU Unit Fatal A fatal error occurred • If the Unit is the origina- 0015 Eliminate the cause ing red Error in the CPU Unit.
Page 332
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to the Tag Data Links Connection The connection could The Unit will periodically 03D4 Correct the device Failed not be established attempt to reconnect to parameter settings, because device the target.
Page 333
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to Memory Access Flash- Memory Access An error occurred in Case 1: 0602 Download the Unit ing red Error the Unit's non-vola- The error record remains Setup from the tab tile memory itself.
Page 334
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to Memory Access Flash- IP Advanced Set- There is an error in the 03D1 Identify the error log ing red tings Error parameter settings stored data, correct the set- in the Unit's non-volatile tings, and then down-...
Page 335
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to Memory Access Server Connec- An error occurred in *_DNSSvrErr (DNS 03C4 Perform one of the tion Error communications with Server Error) will change following: Details: the DNS server.
Page 336
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to the Network Server Connec- An error occurred in *_SNTPSvrErr (SNTP 03C4 Perform one of the tion Error communications with Server Error) will change following: Details: the STNP server.
Page 337
13 Troubleshooting Indicator Error log Error Cause Unit operation Countermeasure 7-seg- (hex) ment* Errors Related to the Network Flash- Not lit The target IP address • Operation will continue Check the IP address ing red conversion method is with the set IP address and the Node set to Automatic gen- as the local IP address.
Device Window. For details, refer to 13-1 Checking Status with the Network Configurator. The following table shows the possible originator/target configurations. Originator Target Configu- CS1W-EIP21, CJ1W-EIP21, CJ2H-CPU@@-EIP, CS1W-EIP21, CJ1W-EIP21, CJ2H-CPU@@-EIP, ration 1 CJ2M-CPU3@, NJ501-@@@@, and NJ301- CJ2M-CPU3@, NJ501-@@@@, and NJ301-...
Page 339
13 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0107 Error code returned from tar- This error does This error does This is not an get: not occur. not occur. error because the connection Attempted to close a connec- is already...
Page 340
13 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0115 Error code returned from tar- This error does Depends on Check the origi- get: not occur. the target’s nator’s connec- specifications. tion settings. The Product Type did not (Contact the match when opening connec-...
Page 341
13 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 011B Error code returned from tar- This error does Depends on Set the origina- get: not occur. the target’s tor’s RPI setting specifications. to 0.5 ms or The RPI was set to a value (Contact the...
Page 342
13 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 031C Error code generated in origi- This error does The originator Depends on nator: not occur. generates this the originator’s code when an specifications.
Page 343
Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) Unique OMRON Error Codes 0810 Error code returned from tar- This error may The meaning of The meaning of get: occur if the this error code this error code CPU Unit’s task...
13 Troubleshooting 13-4 Error Log Errors detected by the EtherNet/IP Unit are stored in the error log along with the date and time of their occurrence. The error log can be read from the Network Configurator and cleared from the Sysmac Studio.
13 Troubleshooting Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for the functions and oper- ating procedures for the Controller event logs. 13-4-2 Error Log Error Codes Error Detail code Saved in code Error non-volatile First byte Second byte (hex) memory...
Page 346
13 Troubleshooting Error Detail code Saved in code Error non-volatile First byte Second byte (hex) memory 021A Logic error in setting table 00 hex 02 hex: Network parame- ters 03 hex: Routing tables 04 hex: Unit Setup 0E hex: Unit name 12 hex: Status area layout setting error 13 hex: Status area layout...
Page 347
13 Troubleshooting Error Detail code Saved in code Error non-volatile First byte Second byte (hex) memory 03C3 FINS/UDP packet discarded 00 hex 01 to FE hex: Source node address 03C4 Server connection error 00 hex: DNS 01 hex: Specified host does not exist 03 hex: SNTP 02 hex: No such service at...
Page 348
13 Troubleshooting Error Detail code Saved in code Error non-volatile First byte Second byte (hex) memory 03D1 Ethernet advanced setting error 02 hex: FINS setting error 01 hex: Checksum error 10 hex: Invalid IP router table 11 hex: Invalid FINS/UDP setting 12 hex: Invalid FINS/TCP setting...
13 Troubleshooting 13-5 Event Logs 13-5-1 Overview of the Event Logs You use the same methods to manage all of the events that occur on the NJ-series Controller. (The events include errors and information.) You can use the Sysmac Studio or an NS-series PT to confirm current Controller events and the logs of events that have occurred.
13 Troubleshooting 13-5-2 Error Table The errors that may occur for this Unit are listed below. The following abbreviations and symbols are used in the event level column. Abbreviation Name Major fault level Partial fault level Minor fault level Observation Info Information Symbol...
Page 351
13 Troubleshooting Level Event code Event name Meaning Assumed cause Reference Info 34A90000 hex Tag Data Link There were two or • The power supply to the target page 13-40 Error more errors in a node is OFF. connection as an •...
Page 352
13 Troubleshooting Level Event code Event name Meaning Assumed cause Reference Obs Info 84E10000 hex BOOTP Connection with the • Server setting error (The page 13-46 Server Error BOOTP server acquired IP address is illegal.) failed. • Server is down. •...
13 Troubleshooting 13-5-3 Error Descriptions This section describes the information that is given for individual errors. Controller Error Descriptions The items that are used to describe individual errors (events) are described in the following copy of an error table. Event name Gives the name of the error.
Page 354
13 Troubleshooting Event name Unit Memory Error (Device Error) Event code 047A0000 hex Meaning An error occurred when writing to the error history or device parameters in non-volatile memory in the EtherNet/IP Unit. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing...
Page 355
13 Troubleshooting Event name Non-volatile Memory Error Event code 047B0000 hex Meaning An error occurred in non-volatile memory. Source PLC Function Module Source details CJ-series Unit Detection Continuously timing Error attributes Level Minor fault Recovery Error reset Log category System Effects User program Continues.
Page 356
13 Troubleshooting Event name Invalid Communications Parameter Event code 14840000 hex Meaning An error was found in the validation check of the parameters for tag data links that are saved in non-volatile memory. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing...
Page 357
13 Troubleshooting Event name Verification Error Event code 34A8 0000 hex Meaning The information registered for a target node in the tag data link parameters is different from the actual node informa- tion. Source PLC Function Module Source details CJ-series Unit Detection After link is timing...
Page 358
13 Troubleshooting Event name Tag Data Link Error Event code 34A90000 hex Meaning There were two or more errors in a connection as an originator. The following are excluded. • Connections as a target • Connection timeouts due to a Link OFF Error with the switching hub Source PLC Function Module Source details...
Page 359
13 Troubleshooting Event name Basic Ethernet Setting Error Event code 34AB 0000 hex Meaning There is an illegal TCP/IP setting. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing Controller reset, or Unit restart Error attributes Level Minor fault Recovery...
Page 360
13 Troubleshooting Event name IP Router Table Error Event code 34AD0000 hex Meaning The IP router table information is incorrect. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing Controller reset, or Unit restart Error attributes Level Minor fault Recovery...
Page 361
13 Troubleshooting Event name Ethernet Advanced Setting Error Event code 34AF 0000 hex Meaning There is an illegal FINS setting. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing Controller reset, or Unit restart Error attributes Level Minor fault Recovery...
Page 362
13 Troubleshooting Event name Status Area Layout Setting Error Event code 381C0000 hex Meaning An error occurred in the layout setting of the EtherNet/IP Unit. Source PLC Function Module Source details CJ-series Unit Detection At power ON, timing Controller reset, or Unit restart Error attributes Level...
Page 363
13 Troubleshooting Event name IP Address Duplication Error Event code 84E0 0000 hex Meaning The same IP address is used more than once. Source PLC Function Module Source details CJ-series Unit Detection After determining timing IP addresses Error attributes Level Minor fault Recovery Error reset...
Page 364
13 Troubleshooting Event name BOOTP Server Error Event code 84E10000 hex Meaning Connection with the BOOTP server failed. Source PLC Function Module Source details CJ-series Unit Detection After link is timing established Error attributes Level Minor fault Recovery Error reset Log category System Effects...
Page 365
13 Troubleshooting Event name Link OFF Error Event code 84E2 0000 hex Meaning The Ethernet link status turned OFF. Source PLC Function Module Source details CJ-series Unit Detection After link is timing established Error attributes Level Observation Recovery Log category System Effects User program...
13 Troubleshooting 13-6 Troubleshooting 13-6-1 CPU Unit's ERR Lit or Flashing Use the following table to troubleshoot the system when the CPU Unit's ERR indicator is lit or flashing when the EtherNet/IP Unit is mounted. An I/O verification error occurred. •...
13 Troubleshooting 13-6-3 Tag Data Links Fail to Start* * Use the following table to troubleshoot tag data links when the Tag Data Links Operating Information in Communications Status 1 does not change to TRUE. The indicators on the EtherNet/IP Unit are all •...
13 Troubleshooting 13-6-4 Tag Data Link Problems Tag data is not concurrent. Check the following items and correct the user program. • Data concurrency is maintained for each connection between the CPU Unit and the built-in EtherNet/IP port. To maintain data concurrency for tag data links, set a refreshing task for the network variables that are assigned to tags.
13 Troubleshooting 13-6-5 Message Timeout Problems Timeout errors occur frequently in message ser- • When there is a high load in the tag data link, and the CPU Unit’s vices (CIP UCMM, CIP Class 3, or FINS). task period 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.
13 Troubleshooting 13-7 Cleaning and Maintenance This section describes daily maintenance and the cleaning and inspection methods. 13-7-1 Cleaning Clean the EtherNet/IP Unit regularly as described below in order to keep it in optimal operating condi- tion. • Wipe the Unit daily with a dry, soft cloth. •...
Page 371
13 Troubleshooting Daily Inspections Check the items in the following table and correct any items that are below the standard. Improve the operating environment or adjust the EtherNet/IP Unit to correct the situation if any of the standards in the following table are not met. Daily inspection Inspection Criteria...
• When you return an EtherNet/IP Unit for repair, attach a sheet of paper detailing the problem and return the Unit to your OMRON representative. If there is a faulty contact, try wiping the contact with a clean cotton cloth dampened with alcohol.
13 Troubleshooting 13-8-3 EtherNet/IP Unit Replacement Procedure Turn OFF the power supply to the Controller where the EtherNet/IP Unit to replace is mounted and to all external devices that are connected to the network. Remove the Ethernet cable from the EtherNet/IP Unit to replace and remove the EtherNet/IP Unit.
Page 374
13 Troubleshooting 13-56 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Appendices Functional Comparison of EtherNet/IP Functionality on NJ- series CPU Units and Other Series OK: Supported., ---: Not supported. EtherNet/IP Unit (built-in port on CJ2 Built-in Ether- CJ-series CPU Unit) Net/IP port on Item Ethernet NJ-series CPU Unit ver- Unit ver- Unit ver- Unit Unit...
Appendices EDS File Management This section describes the EDS file management functions used in the Network Configurator. Precautions for Correct Use Precautions for Correct Use For Windows Vista or Windows 7, we recommend that you start the Network Configurator as the administrator.
Appendices A-2-1 Installing EDS Files EDS File − Install The Network Configurator can support new devices if the proper EDS files are installed. To install the EDS file, use the following procedure. Select EDS File − Install. The Install EDS File Dialog Box is displayed. Select the EDS file to install and click the Open Button.
Appendices A-2-3 Deleting EDS Files EDS File − Delete To delete an EDS file, use the following procedure. Select the device from the Hardware List. Select EDS File − Delete. The following confirmation dialog box is displayed. Click the Yes Button. The selected device is deleted from the Hardware List together with the EDS file.
Appendices Additional Information • The device is found only if it is located below the present cursor position in the Hardware List. • To search all the devices, select Hardware in the Hardware List before you perform the search procedure. A-2-6 Displaying EDS File Properties EDS File −...
Appendices Precautions for Using the Network Configurator on Windows XP, Windows Vista, or Windows 7 Better firewall security for Windows XP (SP2 or higher), Windows Vista, and Windows 7 has increased the restrictions for data communications. Therefore, you must perform the corresponding procedure given below to change the settings of the Windows firewall before you use the following operations to perform communications with the Network Configurator connected to an NJ-series CPU Unit.
Page 382
Appendices Windows Vista or Windows 7 Use the following procedure to change the settings. Always perform steps 1 to 6 if you cannot go online. The User Account Control Dialog Box may be displayed during this procedure. If it appears, click the Continue Button and continue with the procedure.
Page 383
Appendices Click the Unblock Button. (Windows Vista) (Windows 7) A USB or EtherNet/IP connection will be approved for the Network Configurator, and you will be able to connect the Network Configurator in the future. CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Appendices Variable Memory Allocation Methods You must be aware of the way in which memory is allocated to variables to align the memory locations of the members of structure or union variables with variables in other devices. Adjustments are neces- sary mainly when structure variables are used in the following type of communications with other devices.
Page 385
Appendices The alignments and the amounts of memory that are allocated for the basic data types and enumera- tions are given below. Amount of memory that Data type Alignment [bytes] is allocated [bytes] BOOL BYTE, USINT, or SINT WORD, UINT, or INT DWORD, UDINT, or DINT LWORD, ULINT, or LINT REAL...
Page 386
Appendices Precautions for Correct Use Precautions for Correct Use Amount of Memory That Is Allocated for BOOL Arrays Two bytes are allocated in memory for individual BOOL variables, BOOL structure members, and BOOL union variables. However, for a BOOL array, two bytes of memory are not allocated for each element.
Page 387
Appendices Variables with Four-byte Alignments (e.g., DWORD) Four bytes of memory are allocated for the four-byte alignment. The location of the first byte of data in memory is an integer multiple of four bytes. Therefore, if a variable with a two-byte alignment, such as WORD data, is inserted, two bytes of unused memory will remain.
Page 388
Appendices Variables with Eight-byte Alignments (e.g., LWORD) Eight bytes of memory are allocated for the eight-byte alignment. The location of the first byte of data in memory is an integer multiple of eight bytes. Therefore, if a variable with a two-byte alignment, such as WORD data, is inserted, six bytes of unused memory will remain.
Page 389
Appendices Arrays A continuous section of memory is allocated for the elements of the array based on the data size of the data type of the array variable. The alignment of an array is the same as alignment of the data type of the elements.
Page 390
Appendices Data Type Definitions First byte + Memory (integer multiple of 4) Name Data type Bytes Structure STR_A STRUCT First byte DINT First byte + 1 First byte + 2 First byte + 3 Variable A, Name Data type First byte + 4 8 bytes Structure STR_B STRUCT...
Page 391
Appendices Example: The alignments and the amounts of memory that are allocated for the four variable declara- tions given in the following figure are given in the following table. Variable Alignment [bytes] Amount of memory that is allocated [bytes] Data Type Definitions Memory First byte + Name...
Page 392
Appendices Unions For a union variable, the members overlap in the same memory locations. The alignment of a union is largest alignment of all of the members. The amount of memory that is allocated is the largest amount of memory that is allocated for any of the members. Example: The alignments and the amounts of memory that are allocated for the four variable declara- tions given in the following figure are given in the following table.
Appendices A-4-2 Important Case Examples When you exchange structure variable data between an NJ-series CPU Unit and a remote device, you must align the memory configuration of the structure variable members with those of the remote device. This section describes what to do in either the NJ-series CPU Unit or in the remote device. Additional Information This is not necessary when you exchange data between NJ-series CPU Units.
Page 394
Appendices Version Information The following table gives the unit version of the CPU Units and the Sysmac Studio version that are required to specify member offsets. Sysmac Studio version Unit version of CPU Unit 1.01 or lower 1.02 1.03 or higher 1.01 or later Not possible.
Page 395
Appendices Data Type Definitions Data Type Definitions NJ-series Structure CJ-series Structure Variable NJ_X Name Data type Name Data type Variable CJ_X Bytes Bytes Structure Y STRUCT Structure Y STRUCT First byte First byte DINT DINT First byte + 4 First byte + 4 DINT DINT Communications is...
Page 396
Appendices Method 2: Changing the Memory Configuration of the Structure Variable in the Remote Device You can insert a member into the structure variable of the remote device to change it to match the memory configuration of the structure variable in the NJ-series CPU Unit. Both the memory configu- ration and the data types must be the same between the two structure variables.
Appendices Precautions When Accessing External Outputs from NJ-series CPU Units Observe the following precautions when you access variables or I/O memory addresses that are assigned to external outputs in an NJ-series CPU Unit. • Precaution on Writing from External Devices, Variables That Are Assigned to External Outputs Any value that is written to a variable that is assigned to an external output in an NJ-series CPU Unit through a tag data link or communications instruction from an external device will be overwritten by the execution results of the user program.
Appendices Differences in Available Functions Depending on the CPU Unit (NJ or CJ Series) Some of the specifications when an EtherNet/IP Unit is connected to a CJ-series CPU Unit are different from the specifications when the EtherNet/IP Unit is connected to an NJ-series CPU Unit. A list of these differences is provided below.
Page 399
Appendices CIO Area Words Allocated to CPU Bus Units CIO n: Software Switches The device variable that corresponds to all of the bits in CIO n is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 400
Appendices The device variables that correspond to bits 00 to 15 in CIO n+2 to n+5 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 401
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description CIO n+3 *_TargetPLCMdSta[16] Target Node PLC Operating Flag for Node Address 16 *_TargetPLCMdSta[17] Target Node PLC Operating Flag for Node Address 17 *_TargetPLCMdSta[18] Target Node PLC Operating Flag for Node...
Page 402
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description CIO n+4 *_TargetPLCMdSta[32] Target Node PLC Operating Flag for Node Address 32 *_TargetPLCMdSta[33] Target Node PLC Operating Flag for Node Address 33 *_TargetPLCMdSta[34] Target Node PLC Operating Flag for Node...
Page 403
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description CIO n+5 *_TargetPLCMdSta[48] Target Node PLC Operating Flag for Node Address 48 *_TargetPLCMdSta[49] Target Node PLC Operating Flag for Node Address 49 *_TargetPLCMdSta[50] Target Node PLC Operating Flag for Node...
Page 404
Appendices The device variables that correspond to bits 00 to 15 in CIO n+6 to n+9 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 405
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description CIO n+9 *_TargetPLCErrSta[48] Target Node PLC Error Flag for Node Address 48 *_TargetPLCErrSta[49] Target Node PLC Error Flag for Node Address 49 *_TargetPLCErrSta[50] Target Node PLC Error Flag for Node Address 50 *_TargetPLCErrSta[51]...
Page 406
Appendices CIO n+11: Unit Status 2 The device variable that corresponds to all of the bits in CIO n+11 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 407
Appendices CIO n+13: Communications Status 2 The device variable that corresponds to all of the bits in CIO n+13 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 408
Appendices CIO n+16 to n+19: Registered Target Node Table The device variable that corresponds to all of the bits in CIO n+16 to n+19 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 409
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers Variable name Description CIO n+17 *_RegTargetSta[16] Registered Target Node Table Bit for Node Address *_RegTargetSta[17] Registered Target Node Table Bit for Node Address *_RegTargetSta[18] Registered Target Node Table Bit for Node Address *_RegTargetSta[19]...
Page 410
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers Variable name Description CIO n+18 *_RegTargetSta[44] Registered Target Node Table Bit for Node Address *_RegTargetSta[45] Registered Target Node Table Bit for Node Address *_RegTargetSta[46] Registered Target Node Table Bit for Node Address *_RegTargetSta[47]...
Page 411
Appendices CIO n+20 to n+23: Normal Target Node Table The device variable that corresponds to all of the bits in CIO n+20 to n+23 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 412
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers Variable name Description CIO n+21 *_EstbRegTargetSta[16] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[17] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[18] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[19]...
Page 413
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers Variable name Description CIO n+22 *_EstbRegTargetSta[44] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[45] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[46] Normal Target Node Table Bit for Node Address *_EstbRegTargetSta[47]...
Page 414
Appendices The device variables that correspond to bits 00 to 15 in CIO n+24 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description...
Page 415
Appendices User Settings Area x: First I/O memory area address that is specified in the allocated CIO Area words. Words x to x+15: Registered Target Node Table The device variable that corresponds to all of the bits in words x to x+15 is given in the following table.
Page 416
Appendices The device variables that correspond to bits 00 to 15 in words x to x+15 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 417
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+7 *_x.RegTargetSta.Target- Registered Target Node Table Bit for Node Sta[112] Address 112 *_x.RegTargetSta.Target- Registered Target Node Table Bit for Node Sta[127] Address 127...
Page 418
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+15 *_x.RegTargetSta.Target- Registered Target Node Table Bit for Node Sta[240] Address 240 *_x.RegTargetSta.Target- Registered Target Node Table Bit for Node Sta[255] Address 255...
Page 419
Appendices The device variables that correspond to bits 00 to 15 in words x+16 to x+31 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 420
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+23 *_x.EstbTarget- Normal Target Node Table Bit for Node Address Sta.TargetSta[112] *_x.EstbTarget- Normal Target Node Table Bit for Node Address Sta.TargetSta[127] Word x+24 *_x.EstbTarget-...
Page 421
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+31 *_x.EstbTarget- Normal Target Node Table Bit for Node Address Sta.TargetSta[240] *_x.EstbTarget- Normal Target Node Table Bit for Node Address Sta.TargetSta[255] CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495) A-47...
Page 422
Appendices Words x+32 to x+47: Target Nod4e PLC Operating Flags The device variable that corresponds to all of the bits in words x+32 to x+47 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 423
Appendices The device variables that correspond to bits 00 to 15 in words x+32 to x+47 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 424
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+39 *_x.TargetPLCMdSta. Target Node PLC Operating Flag for Node TargetSta[112] Address 112 *_x.TargetPLCMdSta. Target Node PLC Operating Flag for Node TargetSta[127] Address 127...
Page 425
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+47 *_x.TargetPLCMdSta. Target Node PLC Operating Flag for Node TargetSta[240] Address 240 *_x.TargetPLCMdSta. Target Node PLC Operating Flag for Node TargetSta[255] Address 255...
Page 426
Appendices Words x+48 to x+63: Target Node PLC Error Flags The device variable that corresponds to all of the bits in words x+48 to x+63 is given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit numbers...
Page 427
Appendices The device variables that correspond to bits 00 to 15 in words x+48 to x+63 are given in the following table. I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name...
Page 428
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description Word x+55 *_x.TargetPLCErrSta. Target Node PLC Error Flag for Node Address TargetSta[112] *_x.TargetPLCErrSta. Target Node PLC Error Flag for Node Address TargetSta[127] Word x+56 *_x.TargetPLCErrSta.
Page 429
Appendices I/O memory location in CJ- Device variable for the CJ-series Unit in NJ-series CPU Unit series CPU Unit Word address Bit number Variable name Description *_x.TargetPLCErrSta. Target Node PLC Error Flag for Node Address Word x+63 TargetSta[240] *_x.TargetPLCErrSta. Target Node PLC Error Flag for Node Address TargetSta[255] CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495) A-55...
Appendices Version Information This appendix describes the changes in and additions to functional specifications that were made for changes in the unit version of the CPU Units. Changes in and Additions to Functional Specifications The following table shows the unit version of the CPU Units and the version of the Sysmac Studio that correspond to changes in or additions to the functional specifications.
Page 431
Index CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495) Index-1...
Page 432
Index Index Numerics Communications Status2 ..........3-13 Communications Status3 ..........3-13 Connection I/O Type ...........7-35, 7-36 100M indicator ............. 1-11 Connection Name ..........7-35, 7-36 10M indicator ............... 1-11 connection settings automatically setting connections ......7-38 batch editing ............7-35 editing individual connections ........ 7-34 *_AdjTmCmd(Adjust Clock Bit) ........
Page 435
Index unit setup ..............5-2 data concurrency ........... 7-12 effect on task periods .......... 12-24 Unit Status1 ..............3-9 introduction .............. 7-2 Unit Status2 ..............3-10 maximum response time ........12-25 *_UnitErr(Unit Error Occurred) ........3-9 models other than NJ-series CPU Units ....7-74 *_UnitMemErr(Unit Memory Error) ........
Page 436
Index Index-6 CJ-series EtherNet/IP Units Operation Manual for NJ-series CPU Unit (W495)
Need help?
Do you have a question about the CJ1W-EIP21 and is the answer not in the manual?
Questions and answers