diff --git "a/textbook.jsonl" "b/textbook.jsonl"
new file mode 100644--- /dev/null
+++ "b/textbook.jsonl"
@@ -0,0 +1,152 @@
+{"question": "Machine Automation Controller", "answer": "NJ/NX-series\nCPU Unit Built-in EtherNet/IPTM Port\nUser’s Manual\nNX701-1\nNX502-1\nNX102-1\nNX102-90\nNX1P2-1\nNX1P2-9\nNJ501-\nNJ301-\nNJ101-10\nNJ101-90\nCPU Unit\nW506-E1-37\nNOTE"}
+{"question": "All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or", "answer": "transmitted, in any form, or by any means, mechanical, electronic, photocopying, recording, or\notherwise, without the prior written permission of OMRON."}
+{"question": "No patent liability is assumed with respect to the use of the information contained herein.", "answer": "Moreover, because OMRON is constantly striving to improve its high-quality products, the infor-\nmation contained in this manual is subject to change without notice."}
+{"question": "Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON as-", "answer": "sumes no responsibility for errors or omissions.\nNeither is any liability assumed for damages resulting from the use of the information contained in\nthis publication.\nTrademarks\n• Sysmac and SYSMAC are trademarks or registered trademarks of OMRON Corporation in Japan\nand other countries for OMRON factory automation products.\n• Microsoft, Windows, Excel, Visual Basic, and Microsoft Edge are either registered trademarks or\ntrademarks of Microsoft Corporation in the United States and other countries.\n• EtherCAT® is registered trademark and patented technology, licensed by Beckhoff Automation\nGmbH, Germany.\n• ODVA, CIP, CompoNet, DeviceNet, and EtherNet/IP are trademarks of ODVA.\n• The SD and SDHC logos are trademarks of SD-3C, LLC.\nOther company names and product names in this document are the trademarks or registered trade-\nmarks of their respective companies.\nCopyrights\n• Microsoft product screen shots used with permission from Microsoft.\n• This product incorporates certain third party software. The license and copyright information associ-\nated with this software is available at http://www.fa.omron.co.jp/nj_info_e/.\nIntroduction\nIntroduction\nThank you for purchasing an NJ/NX-series CPU Unit.\nThis manual contains information that is necessary to use the NJ/NX-series CPU Unit. Please read\nthis manual and make sure you understand the functionality and performance of the NJ/NX-series\nCPU Unit before you attempt to use it in a control system.\nKeep this manual in a safe place where it will be available for reference during operation.\nIntended Audience\nThis manual is intended for the following personnel, who must also have knowledge of electrical sys-\ntems (electrical engineers or the equivalent).\n• Personnel in charge of introducing FA systems.\n• Personnel in charge of designing FA systems.\n• Personnel in charge of installing and maintaining FA systems.\n• Personnel in charge of managing FA systems and facilities.\nFor programming, this manual is intended for personnel who understand the programming language\nspecifications in international standard IEC 61131-3 or Japanese standard JIS B 3503.\nApplicable Products\nThis manual covers the following products.\n• NX-series CPU Units • NJ-series CPU Units\n• NX701-1£££ • NJ501-££££\n• NX502-1£££ • NJ301-££££\n• NX102-1£££ • NJ101-10££\n• NX102-90££ • NJ101-90££\n• NX1P2-1£££££\n• NX1P2-9£££££\nPart of the specifications and restrictions for the CPU Units are given in other manuals.\nRefer to Relevant Manuals on page 2 and Related Manuals on page 24.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1\nRelevant Manuals\nThe following table provides the relevant manuals for the NJ/NX-series CPU Units. Read all of the\nmanuals that are relevant to your system configuration and application before you use the NJ/NX-ser-\nies CPU Unit.\nMost operations are performed from the Sysmac Studio Automation Software. Refer to the Sysmac\nStudio Version 1 Operation Manual (Cat. No. W504) for information on the Sysmac Studio.\nManual\nBasic information\nPurpose of use\nHardware\nUser’s\nManual\nNX-series\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX502\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX102\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX1P2\nCPU\nUnit\nHardware\nUser’s\nManual\nNJ-series\nCPU\nUnit\nSoftware\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nI/O\nand\nOption\nBoard\nUser's\nManual\nNX-series\nNX1P2\nCPU\nUnit\nInstructions\nReference\nManual\nNJ/NX-series Motion\nControl\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nMotion\nControl\nInstructions\nReference\nManual\nNJ/NX-series Built-in\nEtherCAT\nPort\nUser´s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nEtherNet/IP\nPort\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nOPC\nUA\nFINS\nUser’s\nManual\nNX-series\nCPU\nUnit\nUser's\nManual\nNJ/NX-series\nDatabase\nConnection\nCPU\nUnits\nUser's\nManual\nNJ-series\nSECS/GEM\nCPU\nUnits\nUser’s\nManual\nNJ-series\nRobot\nIntegrated\nCPU\nUnit\nUser's\nManual\nNJ-series\nNJ\nRobotics\nCPU\nUnit\nUser’s\nManual\nNJ/NY-series\nNC\nIntegrated\nController\nTroubleshooting\nManual\nNJ/NX-series\nRelevant Manuals\nIntroduction to NX701\n¡\nCPU Units\nIntroduction to NX502\n¡\nCPU Units\nIntroduction to NX102 ¡\nCPU Units\nIntroduction to NX1P2\n¡\nCPU Units\nIntroduction to NJ-series\n¡\nControllers\nSetting devices and hard-\nware\nUsing motion control ¡\nUsing EtherCAT ¡ ¡ ¡ ¡ ¡ ¡\nUsing EtherNet/IP ¡\nUsing robot control for\n¡\nOMRON robots\n2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nManual\nBasic information\nPurpose of use\nHardware\nUser’s\nManual\nNX-series\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX502\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX102\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX1P2\nCPU\nUnit\nHardware\nUser’s\nManual\nNJ-series\nCPU\nUnit\nSoftware\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nI/O\nand\nOption\nBoard\nUser's\nManual\nNX-series\nNX1P2\nCPU\nUnit\nInstructions\nReference\nManual\nNJ/NX-series Motion\nControl\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nMotion\nControl\nInstructions\nReference\nManual\nNJ/NX-series Built-in\nEtherCAT\nPort\nUser´s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nEtherNet/IP\nPort\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nOPC\nUA\nFINS\nUser’s\nManual\nNX-series\nCPU\nUnit\nUser's\nManual\nNJ/NX-series\nDatabase\nConnection\nCPU\nUnits\nUser's\nManual\nNJ-series\nSECS/GEM\nCPU\nUnits\nUser’s\nManual\nNJ-series\nRobot\nIntegrated\nCPU\nUnit\nUser's\nManual\nNJ-series\nNJ\nRobotics\nCPU\nUnit\nUser’s\nManual\nNJ/NY-series\nNC\nIntegrated\nController\nTroubleshooting\nManual\nNJ/NX-series\nRelevant Manuals\nSoftware settings\nUsing motion control ¡\nUsing EtherCAT ¡\nUsing EtherNet/IP ¡\nUsing OPC UA ¡\nUsing FINS ¡\nUsing the database\n¡\nconnection service\nUsing the GEM Serv- ¡\n¡\nices\nUsing robot control for\n¡\nOMRON robots\nUsing robot control by\n¡\nNJ Robotics function\nUsing numerical con-\n¡\ntrol\nUsing the NX1P2 CPU\n¡\nUnit functions\nWriting the user program\nUsing motion control ¡ ¡\nUsing EtherCAT ¡\nUsing EtherNet/IP ¡\nUsing OPC UA ¡\nUsing FINS ¡\nUsing the database\n¡\nconnection service\nUsing the GEM Serv-\n¡\nices\n¡ ¡\nUsing robot control for\n¡\nOMRON robots\nUsing robot control by\n¡\nNJ Robotics function\nUsing numerical con- ¡\ntrol\nProgramming error\n¡\nprocessing\nUsing the NX1P2 CPU\n¡\nUnit functions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3\nManual\nBasic information\nPurpose of use\nHardware\nUser’s\nManual\nNX-series\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX502\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX102\nCPU\nUnit\nHardware\nUser’s\nManual\nNX-series\nNX1P2\nCPU\nUnit\nHardware\nUser’s\nManual\nNJ-series\nCPU\nUnit\nSoftware\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nI/O\nand\nOption\nBoard\nUser's\nManual\nNX-series\nNX1P2\nCPU\nUnit\nInstructions\nReference\nManual\nNJ/NX-series Motion\nControl\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nMotion\nControl\nInstructions\nReference\nManual\nNJ/NX-series Built-in\nEtherCAT\nPort\nUser´s\nManual\nNJ/NX-series\nCPU\nUnit\nBuilt-in\nEtherNet/IP\nPort\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nUser’s\nManual\nNJ/NX-series\nCPU\nUnit\nOPC\nUA\nFINS\nUser’s\nManual\nNX-series\nCPU\nUnit\nUser's\nManual\nNJ/NX-series\nDatabase\nConnection\nCPU\nUnits\nUser's\nManual\nNJ-series\nSECS/GEM\nCPU\nUnits\nUser’s\nManual\nNJ-series\nRobot\nIntegrated\nCPU\nUnit\nUser's\nManual\nNJ-series\nNJ\nRobotics\nCPU\nUnit\nUser’s\nManual\nNJ/NY-series\nNC\nIntegrated\nController\nTroubleshooting\nManual\nNJ/NX-series\nRelevant Manuals\nTesting operation and de-\nbugging\nUsing motion control ¡\nUsing EtherCAT ¡\nUsing EtherNet/IP ¡\nUsing OPC UA ¡\nUsing FINS ¡\nUsing the database\n¡\nconnection service\n¡\nUsing the GEM Serv-\n¡\nices\nUsing robot control for\n¡\nOMRON robots\nUsing robot control by\n¡\nNJ Robotics function\nUsing numerical con- ¡\ntrol\nUsing the NX1P2 CPU\n¡\nUnit functions\nLearning about error\nmanagement and correc- r r r r r r r ¡\ntions*1\nMaintenance\nUsing motion control ¡\n¡ ¡ ¡ ¡ ¡\nUsing EtherCAT ¡\nUsing EtherNet/IP ¡\n*1. Refer to the NJ/NX-series Troubleshooting Manual (Cat. No. W503) for the error management concepts and the error items. However,\nrefer to the manuals that are indicated with triangles for details on errors corresponding to the products with the manuals that are indi-\ncated with triangles.\n4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nManual Structure\nPage Structure\nThe following page structure is used in this manual.\n4 Installation and Wiring\nNJ-series CPU Unit Hardware User’s Manual (W500) 4-9\n4-3\nMounting\nUnits\n4\n4-3-1\nConnecting\nController\nComponents\nManual Structure\nLevel 1 heading\nLevel 2 heading\nLevel 2 heading 4-3 Mounting Units Level 3 heading\nGives the current\nLevel 3 heading 4-3-1 Connecting Controller Components headings.\nThe Units that make up an NJ-series Controller can be connected simply by pressing the Units together\nand locking the sliders by moving them toward the back of the Units. The End Cover is connected in the\nsame way to the Unit on the far right side of the Controller.\nA step in a procedure 1 Join the Units so that the connectors fit exactly.\nIndicates a procedure. Hook Hook holes\nConnector\nPage tab\n2 The yellow sliders at the top and bottom of each Unit lock the Units together. Move the sliders Gives the number\ntoward the back of the Units as shown below until they click into place. of the main section.\nMove the sliders toward the back\nuntil they lock into place.\nLock\nRelease\nSlider\nSpecial information PPrreeccaauuttiioonnss ffoorr CCoorrrreecctt UUssee\nThe sliders on the tops and bottoms of the Power Supply Unit, CPU Unit, I/O Units, Special I/O\nIcons indicate Units, and CPU Bus Units must be completely locked (until they click into place) after connecting\nthe adjacent Unit connectors.\nprecautions, additional\ninformation, or reference\ninformation.\nManual name\nThis illustration is provided only as a sample. It may not literally appear in this manual.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5\nManual Structure\nSpecial Information\nSpecial information in this manual is classified as follows:\nPrecautions for Safe Use\nPrecautions on what to do and what not to do to ensure safe usage of the product.\nPrecautions for Correct Use\nPrecautions on what to do and what not to do to ensure proper operation and performance.\nAdditional Information\nAdditional information to read as required.\nThis information is provided to increase understanding or make operation easier.\nVersion Information\nInformation on differences in specifications and functionality for Controller with different unit versions\nand for different versions of the Sysmac Studio is given.\nPrecaution on Terminology\nIn this manual, \"download\" refers to transferring data from the Sysmac Studio to the physical Control-\nler and \"upload\" refers to transferring data from the physical Controller to the Sysmac Studio.\nFor the Sysmac Studio, \"synchronization\" is used to both \"upload\" and \"download\" data. Here,\n\"synchronize\" means to automatically compare the data for the Sysmac Studio on the computer with\nthe data in the physical Controller and transfer the data in the direction that is specified by the user.\n6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nSections in this Manual\nSections in this Manual\n1 10\n2 11\n1 Introduction 10 FTP Server\n3 12\nInstalling Ethernet\n2 11 FTP Client\nNetworks\n4 13\nSystem-defined Variables\nAutomatic Clock\n3 Related to the Built-in Eth- 12\nAdjustment\nerNet/IP Port 5 14\nSysmac Studio Settings\n4 for the Built-in Ether- 13 SNMP Agent\n6 15\nNet/IP Port\nCommunications Per-\n7 A\n5 TCP/IP Functions 14 formance and Commu-\nnications Load\n8 I\n6 Tag Data Link Functions 15 Troubleshooting\n9\nCIP Message\n77 A Appendices\nCommunications\n8 Socket Service I Index\nModbus TCP Master\n9\nFunction\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7\nCONTENTS\nCONTENTS\nIntroduction..............................................................................................................1\nIntended Audience...........................................................................................................................................1\nApplicable Products.........................................................................................................................................1\nRelevant Manuals.....................................................................................................2\nManual Structure......................................................................................................5\nPage Structure.................................................................................................................................................5\nSpecial Information..........................................................................................................................................6\nPrecaution on Terminology..............................................................................................................................6\nSections in this Manual...........................................................................................7\nTerms and Conditions Agreement........................................................................15\nWarranty, Limitations of Liability....................................................................................................................15\nApplication Considerations............................................................................................................................16\nDisclaimers....................................................................................................................................................16\nStatement of security responsibilities for assumed use cases and against threats.......................................17\nSafety Precautions.................................................................................................18\nPrecautions for Safe Use ......................................................................................19\nPrecautions for Correct Use.................................................................................20\nRegulations and Standards ..................................................................................21\nSoftware Licenses and Copyrights................................................................................................................21\nVersions..................................................................................................................22\nUnit Versions of CPU Units and Sysmac Studio Versions.............................................................................22\nUnit Versions of CPU Units and Peripheral Tool Versions.............................................................................22\nRelated Manuals.....................................................................................................24\nRevision History.....................................................................................................28\nSection 1 Introduction\n1-1 Introduction............................................................................................................................1-2\n1-1-1 EtherNet/IP Features..................................................................................................................1-2\n1-1-2 Features of Built-in EtherNet/IP Port on NJ/NX-series CPU Units..............................................1-2\n1-2 System Configuration and Configuration Devices.............................................................1-6\n1-2-1 Devices Required to Construct a Network..................................................................................1-6\n1-2-2 Support Software Required to Construct a Network...................................................................1-7\n1-3 Built-in EtherNet/IP Port........................................................................................................1-9\n1-3-1 Specifications..............................................................................................................................1-9\n1-3-2 Part Names and Functions........................................................................................................1-13\n1-4 Introduction to Communications Services........................................................................1-20\n1-4-1 CIP (Common Industrial Protocol) Communications Services..................................................1-20\n1-4-2 IP Routing.................................................................................................................................1-22\n1-4-3 Packet Filter..............................................................................................................................1-23\n1-4-4 Packet Filter (Simple) ...............................................................................................................1-24\n8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nCONTENTS\n1-4-5 BOOTP Client...........................................................................................................................1-24\n1-4-6 DHCP Client..............................................................................................................................1-25\n1-4-7 FTP Server................................................................................................................................1-25\n1-4-8 FTP Client.................................................................................................................................1-25\n1-4-9 Automatic Clock Adjustment.....................................................................................................1-26\n1-4-10 Socket Service..........................................................................................................................1-26\n1-4-11 Secure Socket Services............................................................................................................1-27\n1-4-12 Specifying Host Names.............................................................................................................1-28\n1-4-13 SNMP Agent.............................................................................................................................1-28\n1-4-14 TCP/UDP Message Service......................................................................................................1-29\n1-5 EtherNet/IP Communications Procedures.........................................................................1-30\nSection 2 Installing Ethernet Networks\n2-1 Selecting the Network Devices.............................................................................................2-2\n2-1-1 Recommended Network Devices................................................................................................2-2\n2-1-2 Ethernet Switch Types................................................................................................................2-3\n2-1-3 Ethernet Switch Functions..........................................................................................................2-3\n2-1-4 Precautions for Ethernet Switch Selection..................................................................................2-4\n2-2 Network Installation...............................................................................................................2-7\n2-2-1 Basic Installation Precautions.....................................................................................................2-7\n2-2-2 Recommended Network Devices................................................................................................2-7\n2-2-3 Precautions When Laying Twisted-pair Cable............................................................................2-7\n2-2-4 Precautions When Installing and Connecting Ethernet Switches.............................................2-11\n2-3 Connecting to the Network.................................................................................................2-13\n2-3-1 Ethernet Connectors.................................................................................................................2-13\n2-3-2 Connecting the Cable................................................................................................................2-14\nSection 3 System-defined Variables Related to the Built-in Ether-\nNet/IP Port\n3-1 System-defined Variables Related to the Built-in EtherNet/IP Port...................................3-2\n3-2 System-defined Variables.....................................................................................................3-3\n3-2-1 EtherNet/IP Function Module, Category Name: _EIP.................................................................3-3\n3-2-2 Meanings of Error Status Bits...................................................................................................3-37\n3-3 Specifications for Individual System-defined Variables..................................................3-39\n3-3-1 EtherNet/IP Function Module, Category Name: _EIP...............................................................3-39\nSection 4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-1 TCP/IP Settings Display........................................................................................................4-2\n4-2 LINK Settings Display..........................................................................................................4-12\n4-3 FTP Settings Display...........................................................................................................4-14\n4-4 NTP Settings Display...........................................................................................................4-15\n4-5 SNMP Settings Display........................................................................................................4-17\n4-6 SNMP Trap Settings Display...............................................................................................4-19\n4-7 CIP Settings Display............................................................................................................4-21\nSection 5 TCP/IP Functions\n5-1 Determining IP Addresses....................................................................................................5-2\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 9\nCONTENTS\n5-1-1 IP Addresses...............................................................................................................................5-2\n5-1-2 Built-in EtherNet/IP Port IP Address Settings.............................................................................5-4\n5-1-3 Private and Global Addresses...................................................................................................5-11\n5-2 Default States of TCP/UDP Ports and the Changing Procedure.....................................5-15\n5-3 Testing Communications....................................................................................................5-18\n5-3-1 PING Command........................................................................................................................5-18\n5-3-2 Using the PING Command........................................................................................................5-18\n5-3-3 Host Computer Operation.........................................................................................................5-18\n5-4 Packet Filter..........................................................................................................................5-20\n5-4-1 Introduction to Packet Filter......................................................................................................5-20\n5-4-2 Packet Filter Specifications.......................................................................................................5-21\n5-4-3 Packet Filter Settings................................................................................................................5-21\n5-4-4 Case Where Packet Filter Is Used............................................................................................5-21\n5-4-5 Settings for Devices That Access the Controller.......................................................................5-33\nSection 6 Tag Data Link Functions\n6-1 Introduction to Tag Data Links.............................................................................................6-2\n6-1-1 Tag Data Links............................................................................................................................6-2\n6-1-2 Data Link Data Areas..................................................................................................................6-3\n6-1-3 Tag Data Link Functions and Specifications...............................................................................6-6\n6-1-4 Overview of Operation................................................................................................................6-7\n6-1-5 Starting and Stopping Tag Data Links.......................................................................................6-10\n6-1-6 Controller Status.......................................................................................................................6-10\n6-1-7 Concurrency of Tag Data Link Data..........................................................................................6-14\n6-2 Setting Tag Data Links........................................................................................................6-21\n6-2-1 Starting the Network Configurator.............................................................................................6-21\n6-2-2 Tag Data Link Setting Procedure..............................................................................................6-23\n6-2-3 Registering Devices..................................................................................................................6-23\n6-2-4 Creating Tags and Tag Sets......................................................................................................6-25\n6-2-5 Connection Settings..................................................................................................................6-38\n6-2-6 Creating Connections Using the Wizard...................................................................................6-48\n6-2-7 Creating Connections by Dragging and Dropping Devices.......................................................6-52\n6-2-8 Connecting the Network Configurator to the Network...............................................................6-54\n6-2-9 Downloading Tag Data Link Parameters...................................................................................6-62\n6-2-10 Uploading Tag Data Link Parameters.......................................................................................6-65\n6-2-11 Verifying Tag Data Link Parameters..........................................................................................6-68\n6-2-12 Starting and Stopping Tag Data Links.......................................................................................6-72\n6-2-13 Clearing the Device Parameters...............................................................................................6-75\n6-2-14 Saving the Network Configuration File......................................................................................6-77\n6-2-15 Reading a Network Configuration File......................................................................................6-78\n6-2-16 Checking Connections..............................................................................................................6-80\n6-2-17 Changing Devices.....................................................................................................................6-81\n6-2-18 Displaying Device Status..........................................................................................................6-83\n6-3 Ladder Programming for Tag Data Links..........................................................................6-85\n6-3-1 Ladder Programming for Tag Data Links..................................................................................6-85\n6-3-2 Status Flags Related to Tag Data Links....................................................................................6-89\n6-4 Tag Data Links with Other Models.....................................................................................6-91\nSection 7 CIP Message Communications\n7-1 Overview of the CIP Message Communications Service...................................................7-3\n7-1-1 Overview of the CIP Message Communications Service............................................................7-3\n7-1-2 Message Communications Service Specifications......................................................................7-3\n7-2 Client Function of CIP Message Communications.............................................................7-4\n7-2-1 Overview.....................................................................................................................................7-4\n7-2-2 CIP Communications Instructions...............................................................................................7-4\n10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nCONTENTS\n7-2-3 Using CIP Communications Instructions.....................................................................................7-5\n7-2-4 Route Path..................................................................................................................................7-6\n7-2-5 Request Path (IOI)....................................................................................................................7-16\n7-2-6 Service Data and Response Data.............................................................................................7-20\n7-2-7 Sample Programming for CIP Connectionless (UCMM) Message Communications................7-22\n7-2-8 Sample Programming for CIP Connection (Class 3) Message Communications.....................7-27\n7-2-9 Operation Timing.......................................................................................................................7-34\n7-2-10 Response Codes.......................................................................................................................7-35\n7-3 Server Function of CIP Message Communications..........................................................7-39\n7-3-1 CIP Message Structure for Accessing CIP Objects..................................................................7-40\n7-3-2 CIP Message Structure for Accessing Variables.......................................................................7-41\n7-4 Specifying Request Path.....................................................................................................7-42\n7-4-1 Examples of CIP Object Specifications.....................................................................................7-42\n7-4-2 Examples of Variable Specifications.........................................................................................7-43\n7-4-3 Logical Segment.......................................................................................................................7-43\n7-4-4 Data Segment...........................................................................................................................7-43\n7-4-5 Specifying Variable Names in Request Paths...........................................................................7-44\n7-5 CIP Object Services.............................................................................................................7-48\n7-5-1 CIP Objects Sent to the Built-in EtherNet/IP Port.....................................................................7-48\n7-5-2 Identity Object (Class ID: 01 hex).............................................................................................7-48\n7-5-3 NX Configuration Object (Class ID: 74 hex)..............................................................................7-53\n7-5-4 TCP/IP Interface Object (Class ID: F5 hex)..............................................................................7-74\n7-5-5 Ethernet Link Object (Class ID: F6 hex)....................................................................................7-77\n7-5-6 Controller Object (Class ID: C4 hex).........................................................................................7-83\n7-6 Read and Write Services for Variables..............................................................................7-85\n7-6-1 Read Service for Variables........................................................................................................7-85\n7-6-2 Write Service for Variables........................................................................................................7-86\n7-7 Variable Data Types.............................................................................................................7-89\n7-7-1 Data Type Codes......................................................................................................................7-89\n7-7-2 Common Format.......................................................................................................................7-89\n7-7-3 Elementary Data Types.............................................................................................................7-90\n7-7-4 Derived Data Types...................................................................................................................7-91\nSection 8 Socket Service\n8-1 Basic Knowledge on Socket Communications...................................................................8-2\n8-1-1 Sockets.......................................................................................................................................8-2\n8-1-2 Port Numbers for Socket Services..............................................................................................8-2\n8-2 Basic Knowledge on Protocols............................................................................................8-3\n8-2-1 Differences between TCP and UDP............................................................................................8-3\n8-2-2 Fragmenting of Send Data..........................................................................................................8-4\n8-2-3 Data Receive Processing............................................................................................................8-6\n8-2-4 Broadcasting...............................................................................................................................8-9\n8-3 Overview of Built-in EtherNet/IP Port Socket Services....................................................8-10\n8-3-1 Overview...................................................................................................................................8-10\n8-3-2 Procedure..................................................................................................................................8-10\n8-4 Settings Required for the Socket Services.......................................................................8-12\n8-5 Socket Service Instructions................................................................................................8-13\n8-6 Details on Using the Socket Services................................................................................8-14\n8-6-1 Using the Socket Services........................................................................................................8-14\n8-6-2 Procedure to Use Socket Services...........................................................................................8-14\n8-6-3 Timing Chart for Output Variables Used in Communications....................................................8-16\n8-6-4 UDP Sample Programming.......................................................................................................8-18\n8-6-5 TCP Sample Programming.......................................................................................................8-23\n8-7 Precautions in Using Socket Services...............................................................................8-31\n8-7-1 Precautions for UDP and TCP Socket Services.......................................................................8-31\n8-7-2 Precautions for UDP Socket Services.......................................................................................8-31\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11\nCONTENTS\n8-7-3 Precautions for TCP Socket Services.......................................................................................8-31\n8-8 TCP/UDP Message Service.................................................................................................8-33\n8-8-1 Outline of TCP/UDP Message Service.....................................................................................8-33\n8-8-2 Specifications of TCP/UDP Message Service...........................................................................8-33\n8-8-3 Settings Required for TCP/UDP Message Service...................................................................8-33\n8-8-4 Command Format Specifications..............................................................................................8-34\n8-9 Secure Socket Services......................................................................................................8-36\n8-9-1 Overview of Secure Socket Communications...........................................................................8-36\n8-9-2 System Configuration of Secure Socket Services.....................................................................8-38\n8-9-3 Procedure to Use Secure Socket Setting Function of the Sysmac Studio................................8-39\n8-9-4 Executing Instructions for Secure Socket Communications......................................................8-47\n8-9-5 Troubleshooting Errors in Secure Socket Communications......................................................8-51\n8-9-6 Secure Socket Communications Logging.................................................................................8-51\n8-9-7 Handling of Secure Socket Communications Setting Information.............................................8-54\nSection 9 Modbus TCP Master Function\n9-1 Overview of Modbus TCP Master Function.........................................................................9-2\n9-2 Modbus TCP Master Function Details.................................................................................9-3\n9-2-1 Modbus TCP Instruction Type.....................................................................................................9-3\n9-2-2 Modbus TCP Instruction Function...............................................................................................9-3\n9-3 Modbus TCP Master Function Procedure...........................................................................9-4\nSection 10 FTP Server\n10-1 Overview and Specifications..............................................................................................10-2\n10-1-1 Overview...................................................................................................................................10-2\n10-1-2 Specifications............................................................................................................................10-3\n10-2 FTP Server Function Details...............................................................................................10-4\n10-2-1 Supported Files.........................................................................................................................10-4\n10-2-2 Connecting to the FTP Server...................................................................................................10-4\n10-3 Using the FTP Server Function..........................................................................................10-7\n10-3-1 Procedure..................................................................................................................................10-7\n10-3-2 List of Settings Required for the FTP Server Function..............................................................10-7\n10-4 FTP Server Application Example........................................................................................10-9\n10-5 Using FTP Commands.......................................................................................................10-11\n10-5-1 Table of Commands................................................................................................................10-11\n10-5-2 Using the Commands..............................................................................................................10-11\n10-6 Using SD Memory Card Operations.................................................................................10-18\n10-6-1 SD Memory Card Types..........................................................................................................10-18\n10-6-2 File Types................................................................................................................................10-18\n10-6-3 Initializing SD Memory Cards..................................................................................................10-19\n10-6-4 Format of Variable Data..........................................................................................................10-19\n10-7 Application Example from a Host Computer...................................................................10-20\nSection 11 FTP Client\n11-1 Using the FTP Client to Transfer Files...............................................................................11-2\n11-1-1 Transferring Files......................................................................................................................11-2\n11-1-2 Connectable FTP Servers.........................................................................................................11-3\n11-1-3 File Transfer Options.................................................................................................................11-3\n11-1-4 Other Functions.........................................................................................................................11-4\n11-2 FTP Client Communications Instructions.........................................................................11-5\n12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nCONTENTS\n11-2-1 Functions of the FTP Client Communications Instructions.......................................................11-5\n11-2-2 Restrictions on the FTP Client Communications Instructions...................................................11-8\n11-3 FTP Client Application Example.........................................................................................11-9\nSection 12 Automatic Clock Adjustment\n12-1 Automatic Clock Adjustment..............................................................................................12-2\n12-1-1 Overview...................................................................................................................................12-2\n12-1-2 Specifications............................................................................................................................12-2\n12-2 Procedure to Use the Automatic Clock Adjustment Function........................................12-4\n12-2-1 Procedure..................................................................................................................................12-4\n12-2-2 Settings Required for Automatic Clock Adjustment..................................................................12-4\nSection 13 SNMP Agent\n13-1 SNMP Agent.........................................................................................................................13-2\n13-1-1 Overview...................................................................................................................................13-2\n13-1-2 Specifications............................................................................................................................13-3\n13-1-3 SNMP Messages......................................................................................................................13-3\n13-1-4 MIB Specifications.....................................................................................................................13-4\n13-2 Procedure to Use the SNMP Agent..................................................................................13-28\n13-2-1 Procedures..............................................................................................................................13-28\n13-2-2 Settings Required for the SNMP Agent...................................................................................13-28\nSection 14 Communications Performance and Communications\nLoad\n14-1 Communications System....................................................................................................14-2\n14-1-1 Tag Data Link Communications Method...................................................................................14-2\n14-1-2 Calculating the Number of Connections....................................................................................14-4\n14-1-3 Packet Interval (RPI) Accuracy.................................................................................................14-5\n14-2 Adjusting the Communications Load................................................................................14-7\n14-2-1 Checking Bandwidth Usage for Tag Data Links........................................................................14-8\n14-2-2 Tag Data Link Bandwidth Usage and RPI.................................................................................14-9\n14-2-3 Adjusting Device Bandwidth Usage........................................................................................14-10\n14-2-4 Changing the RPI....................................................................................................................14-11\n14-2-5 RPI Setting Examples.............................................................................................................14-16\n14-3 I/O Response Time in Tag Data Links..............................................................................14-23\n14-3-1 Timing of Data Transmissions.................................................................................................14-23\n14-3-2 Built-in EtherNet/IP Port Data Processing Time......................................................................14-24\n14-3-3 Relationship between Task Periods and Packet Intervals (RPIs)...........................................14-26\n14-3-4 Maximum Tag Data Link I/O Response Time..........................................................................14-27\n14-4 Message Service Transmission Delay.............................................................................14-30\nSection 15 Troubleshooting\n15-1 Overview of Troubleshooting.............................................................................................15-2\n15-2 Checking Status with the Network Configurator..............................................................15-3\n15-2-1 The Network Configurator's Device Monitor Function...............................................................15-3\n15-2-2 Connection Status Codes and Troubleshooting......................................................................15-11\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13\nCONTENTS\nAppendices\nA-1 Functional Comparison of EtherNet/IP Ports on NJ/NX-series CPU Units and\nOther Series...........................................................................................................................A-3\nA-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP Connections)...............A-5\nA-2-1 Overview of the Tag Data Links (EtherNet/IP Connections) Settings with the Sysmac Studio..A-5\nA-2-2 Procedure to Make the EtherNet/IP Connection Settings with the Sysmac Studio....................A-6\nA-2-3 EtherNet/IP Connection Settings...............................................................................................A-7\nA-2-4 Making the EtherNet/IP Connection Settings with the Sysmac Studio.....................................A-11\nA-2-5 Checking Communications Status with the Sysmac Studio and Troubleshooting...................A-32\nA-2-6 Troubleshooting........................................................................................................................A-36\nA-3 EDS File Management........................................................................................................A-42\nA-3-1 Installing EDS Files..................................................................................................................A-42\nA-3-2 Creating EDS Files...................................................................................................................A-43\nA-3-3 Deleting EDS Files...................................................................................................................A-43\nA-3-4 Saving EDS Files.....................................................................................................................A-44\nA-3-5 Searching EDS Files................................................................................................................A-44\nA-3-6 Displaying EDS File Properties................................................................................................A-45\nA-3-7 Creating EDS Index Files.........................................................................................................A-45\nA-4 Precautions for Using the Network Configurator on Windows XP, Windows Vis-\nta, or Windows 7 or Higher................................................................................................A-46\nA-4-1 Changing Windows Firewall Settings.......................................................................................A-46\nA-5 Variable Memory Allocation Methods...............................................................................A-49\nA-5-1 Variable Memory Allocation Rules............................................................................................A-49\nA-5-2 Important Case Examples........................................................................................................A-58\nA-6 Precautions When Accessing External Outputs in CPU Units.......................................A-62\nA-7 TCP State Transitions.........................................................................................................A-63\nA-8 Example of NX Unit Setting Using NX Configuration Object Service............................A-65\nA-8-1 Changing the Unit Operation Settings for Singe NX Unit.........................................................A-65\nA-8-2 Changing the Unit Operation Settings for Multiple NX Units....................................................A-66\nA-8-3 Initializing the Unit Operation Settings for Singe NX Unit........................................................A-66\nA-9 Tag Data Link Settings with Generic Devices..................................................................A-67\nA-9-1 Creating Generic Devices........................................................................................................A-67\nA-9-2 Creating a Tag or Tag Set for Generic Device..........................................................................A-68\nA-10 Procedure to Use Secure Socket Service with Secure Socket Configuration\nCommands..........................................................................................................................A-72\nA-10-1 Settings for Starting Secure Socket Services..........................................................................A-72\nA-10-2 Procedure for Replacing the CPU Unit....................................................................................A-74\nA-11 Secure Socket Configuration Commands........................................................................A-79\nA-11-1 Operating Environment for Secure Socket Configuration Commands.....................................A-79\nA-11-2 Location and Starting Procedure of Secure Socket Configuration Commands.......................A-80\nA-11-3 Command and Option Formats................................................................................................A-80\nA-11-4 Common Specifications to All Commands...............................................................................A-81\nA-11-5 Command Specifications.........................................................................................................A-83\nA-12 TCP/ UDP Port Numbers Used for the Built-in EtherNet/IP Port....................................A-95\nA-13 Version Information..........................................................................................................A-100\nIndex\n14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nTerms and Conditions Agreement\nTerms and Conditions Agreement\nWarranty, Limitations of Liability\nWarranties\n Exclusive Warranty\nOmron’s exclusive warranty is that the Products will be free from defects in materials and work-\nmanship for a period of twelve months from the date of sale by Omron (or such other period ex-\npressed in writing by Omron). Omron disclaims all other warranties, express or implied.\n Limitations\nOMRON MAKES NO WARRANTY OR REPRESENTATION, EXPRESS OR IMPLIED, ABOUT\nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OF\nTHE PRODUCTS. BUYER ACKNOWLEDGES THAT IT ALONE HAS DETERMINED THAT THE\nPRODUCTS WILL SUITABLY MEET THE REQUIREMENTS OF THEIR INTENDED USE.\nOmron further disclaims all warranties and responsibility of any type for claims or expenses based\non infringement by the Products or otherwise of any intellectual property right.\n Buyer Remedy\nOmron’s sole obligation hereunder shall be, at Omron’s election, to (i) replace (in the form originally\nshipped with Buyer responsible for labor charges for removal or replacement thereof) the non-com-\nplying Product, (ii) repair the non-complying Product, or (iii) repay or credit Buyer an amount equal\nto the purchase price of the non-complying Product; provided that in no event shall Omron be re-\nsponsible for warranty, repair, indemnity or any other claims or expenses regarding the Products\nunless Omron’s analysis confirms that the Products were properly handled, stored, installed and\nmaintained and not subject to contamination, abuse, misuse or inappropriate modification. Return\nof any Products by Buyer must be approved in writing by Omron before shipment. Omron Compa-\nnies shall not be liable for the suitability or unsuitability or the results from the use of Products in\ncombination with any electrical or electronic components, circuits, system assemblies or any other\nmaterials or substances or environments. Any advice, recommendations or information given orally\nor in writing, are not to be construed as an amendment or addition to the above warranty.\nSee https://www.omron.com/global/ or contact your Omron representative for published informa-\ntion.\nLimitation on Liability; Etc\nOMRON COMPANIES SHALL NOT BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL, OR CON-\nSEQUENTIAL DAMAGES, LOSS OF PROFITS OR PRODUCTION OR COMMERCIAL LOSS IN ANY\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15\nTerms and Conditions Agreement\nWAY CONNECTED WITH THE PRODUCTS, WHETHER SUCH CLAIM IS BASED IN CONTRACT,\nWARRANTY, NEGLIGENCE OR STRICT LIABILITY.\nFurther, in no event shall liability of Omron Companies exceed the individual price of the Product on\nwhich liability is asserted.\nApplication Considerations\nSuitability of Use\nOmron Companies shall not be responsible for conformity with any standards, codes or regulations\nwhich apply to the combination of the Product in the Buyer’s application or use of the Product. At Buy-\ner’s request, Omron will provide applicable third party certification documents identifying ratings and\nlimitations of use which apply to the Product. This information by itself is not sufficient for a complete\ndetermination of the suitability of the Product in combination with the end product, machine, system, or\nother application or use. Buyer shall be solely responsible for determining appropriateness of the par-\nticular Product with respect to Buyer’s application, product or system. Buyer shall take application re-\nsponsibility in all cases.\nNEVER USE THE PRODUCT FOR AN APPLICATION INVOLVING SERIOUS RISK TO LIFE OR\nPROPERTY OR IN LARGE QUANTITIES WITHOUT ENSURING THAT THE SYSTEM AS A WHOLE\nHAS BEEN DESIGNED TO ADDRESS THE RISKS, AND THAT THE OMRON PRODUCT(S) IS\nPROPERLY RATED AND INSTALLED FOR THE INTENDED USE WITHIN THE OVERALL EQUIP-\nMENT OR SYSTEM.\nProgrammable Products\nOmron Companies shall not be responsible for the user’s programming of a programmable Product, or\nany consequence thereof.\nDisclaimers\nPerformance Data\nData presented in Omron Company websites, catalogs and other materials is provided as a guide for\nthe user in determining suitability and does not constitute a warranty. It may represent the result of\nOmron’s test conditions, and the user must correlate it to actual application requirements. Actual per-\nformance is subject to the Omron’s Warranty and Limitations of Liability.\nChange in Specifications\nProduct specifications and accessories may be changed at any time based on improvements and oth-\ner reasons. It is our practice to change part numbers when published ratings or features are changed,\nor when significant construction changes are made. However, some specifications of the Product may\n16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nTerms and Conditions Agreement\nbe changed without any notice. When in doubt, special part numbers may be assigned to fix or estab-\nlish key specifications for your application. Please consult with your Omron’s representative at any\ntime to confirm actual specifications of purchased Product.\nErrors and Omissions\nInformation presented by Omron Companies has been checked and is believed to be accurate; how-\never, no responsibility is assumed for clerical, typographical or proofreading errors or omissions.\nStatement of security responsibilities for assumed use cases and\nagainst threats\nOMRON SHALL NOT BE RESPONSIBLE AND/OR LIABLE FOR ANY LOSS, DAMAGE, OR EX-\nPENSES DIRECTLY OR INDIRECTLY RESULTING FROM THE INFECTION OF OMRON PROD-\nUCTS, ANY SOFTWARE INSTALLED THEREON OR ANY COMPUTER EQUIPMENT, COMPUTER\nPROGRAMS, NETWORKS, DATABASES OR OTHER PROPRIETARY MATERIAL CONNECTED\nTHERETO BY DISTRIBUTED DENIAL OF SERVICE ATTACK, COMPUTER VIRUSES, OTHER\nTECHNOLOGICALLY HARMFUL MATERIAL AND/OR UNAUTHORIZED ACCESS.\nIt shall be the users sole responsibility to determine and use adequate measures and checkpoints to\nsatisfy the users particular requirements for (i) antivirus protection, (ii) data input and output, (iii) main-\ntaining a means for reconstruction of lost data, (iv) preventing Omron Products and/or software instal-\nled thereon from being infected with computer viruses and (v) protecting Omron Products from unau-\nthorized access.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 17\nSafety Precautions\nSafety Precautions\nRefer to the following manuals for safety precautions.\n• NX-series CPU Unit Hardware User's Manual (Cat. No. W535)\n• NX-series NX502 CPU Unit Hardware User’s Manual (Cat. No. W629)\n• NX-series NX102 CPU Unit Hardware User's Manual (Cat. No. W593)\n• NX-series NX1P2 CPU Unit Hardware User's Manual (Cat. No. W578)\n• NJ-series CPU Unit Hardware User’s Manual (Cat No. W500)\n18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nPrecautions for Safe Use\nPrecautions for Safe Use\nRefer to the following manuals for precautions for safe use.\n• NX-series CPU Unit Hardware User's Manual (Cat. No. W535)\n• NX-series NX502 CPU Unit Hardware User’s Manual (Cat. No. W629)\n• NX-series NX102 CPU Unit Hardware User's Manual (Cat. No. W593)\n• NX-series NX1P2 CPU Unit Hardware User's Manual (Cat. No. W578)\n• NJ-series CPU Unit Hardware User’s Manual (Cat No. W500)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 19\nPrecautions for Correct Use\nPrecautions for Correct Use\nRefer to the following manuals for precautions for correct use.\n• NX-series CPU Unit Hardware User's Manual (Cat. No. W535)\n• NX-series NX502 CPU Unit Hardware User’s Manual (Cat. No. W629)\n• NX-series NX102 CPU Unit Hardware User's Manual (Cat. No. W593)\n• NX-series NX1P2 CPU Unit Hardware User's Manual (Cat. No. W578)\n• NJ-series CPU Unit Hardware User’s Manual (Cat No. W500)\n20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nRegulations and Standards\nRegulations and Standards\nRefer to the following manuals for regulations and standards.\n• NX-series CPU Unit Hardware User's Manual (Cat. No. W535)\n• NX-series NX502 CPU Unit Hardware User’s Manual (Cat. No. W629)\n• NX-series NX102 CPU Unit Hardware User's Manual (Cat. No. W593)\n• NX-series NX1P2 CPU Unit Hardware User's Manual (Cat. No. W578)\n• NJ-series CPU Unit Hardware User’s Manual (Cat No. W500)\nSoftware Licenses and Copyrights\nThe products supporting secure socket services incorporate the following third party software. The li-\ncense and copyright information associated with this software is available at http://www.fa.omron.co.jp/\nnj_info_e/.\n• OpenSSL\nThis product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit\n(http://www.openssl.org/).\nCopyright (C) 1998-2019 The OpenSSL Project. All rights reserved.\nCopyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved.\nThis product includes cryptographic software written by Eric Young\n(eay@cryptsoft.com)\nRefer to 8-9 Secure Socket Services on page 8-36 for models that support secure socket services.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 21\nVersions\nVersions\nHardware revisions and unit versions are used to manage the hardware and software in NJ/NX-series\nUnits and EtherCAT slaves. The hardware revision or unit version is updated each time there is a\nchange in hardware or software specifications. Even when two Units or EtherCAT slaves have the\nsame model number, they will have functional or performance differences if they have different hard-\nware revisions or unit versions.\nRefer to the following manuals for versions.\n• NX-series CPU Unit Hardware User's Manual (Cat. No. W535)\n• NX-series NX502 CPU Unit Hardware User’s Manual (Cat. No. W629)\n• NX-series NX102 CPU Unit Hardware User's Manual (Cat. No. W593)\n• NX-series NX1P2 CPU Unit Hardware User's Manual (Cat. No. W578)\n• NJ-series CPU Unit Hardware User’s Manual (Cat No. W500)\nUnit Versions of CPU Units and Sysmac Studio Versions\nThe functions that are supported depend on the unit version of the NJ/NX-series CPU Unit. The ver-\nsion of Sysmac Studio that supports the functions that were added for an upgrade is required to use\nthose functions.\nRefer to the NJ/NX-series CPU Unit Software User’s Manual (Cat. No. W501) for the relationship be-\ntween the unit versions of CPU Units and the Sysmac Studio versions, and for the functions that are\nsupported by each unit version.\nUnit Versions of CPU Units and Peripheral Tool Versions\nWhen you set tag data links for the built-in EtherNet/IP port on an NJ/NX-series CPU Unit, use the\nversions of the Network Configurator and the Sysmac Studio that are given in the following table.\nOK: Supported, ---: Not supported\nCPU Unit Network Configurator for EtherNet/IP Sysmac Studio\nVer. Ver. Ver. Ver.\nVer.3 Ver. Ver. Ver. Ver. Ver. Ver. Ver."}
+{"question": "3x 3.74 1.09 1.51", "answer": "Ver- Ver. .50 3.53 3.59 3.61 3.64 1.10 1.13 1.17 Ver.\nModel or or or or\nsion 3.40 or to to to to to to to 1.23\nlow- high- low- high-"}
+{"question": "51 3.58 3.60 3.63 3.66 1.12 1.16 1.22", "answer": "er er er er\nNJ501 Ver. --- OK OK OK OK OK OK OK --- OK OK OK OK OK"}
+{"question": "00", "answer": "to"}
+{"question": "02", "answer": "NJ301 Ver. --- --- OK OK OK OK OK OK --- OK OK OK OK OK"}
+{"question": "01", "answer": "to"}
+{"question": "02", "answer": "NJ501 Ver. --- --- --- OK OK OK OK OK --- OK OK OK OK OK\nNJ301 1.03\nor lat-\ner\n22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nVersions\nCPU Unit Network Configurator for EtherNet/IP Sysmac Studio\nVer. Ver. Ver. Ver.\nVer.3 Ver. Ver. Ver. Ver. Ver. Ver. Ver."}
+{"question": "3x 3.74 1.09 1.51", "answer": "Ver- Ver. .50 3.53 3.59 3.61 3.64 1.10 1.13 1.17 Ver.\nModel or or or or\nsion 3.40 or to to to to to to to 1.23\nlow- high- low- high-"}
+{"question": "51 3.58 3.60 3.63 3.66 1.12 1.16 1.22", "answer": "er er er er\nNJ101 Ver. --- --- --- --- OK OK OK OK --- --- OK OK OK OK\nNX701 1.10\nor lat-\ner\nNX1P2 Ver. --- --- --- --- --- OK OK OK --- --- --- OK OK*1 OK"}
+{"question": "13", "answer": "or lat-\ner\nNX102 Ver. --- --- --- --- --- --- OK OK --- --- --- --- OK OK"}
+{"question": "30", "answer": "or lat-\ner\nNX502 Ver. --- --- --- --- --- --- --- OK --- --- --- --- --- OK"}
+{"question": "60", "answer": "or lat-\ner\n*1. Use an NX1P2-9B£££££ CPU Unit with Sysmac Studio version 1.30 or higher.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 23\nRelated Manuals\nRelated Manuals\nThe followings are the manuals related to this manual. Use these manuals for reference.\nManual name Cat. No. Model numbers Application Description\nNX-series CPU Unit W535 NX701-££££ Learning the basic An introduction to the entire NX701 system\nHardware User's Manual specifications of the is provided along with the following infor-\nNX701 CPU Units, mation on the CPU Unit.\nincluding introductory • Features and system configuration\ninformation, design- • Introduction\ning, installation, and • Part names and functions\nmaintenance. • General specifications\nMainly hardware in- • Installation and wiring\nformation is provided. • Maintenance and inspection\nNX-series W629 NX502-££££ Learning the basic An introduction to the entire NX502 system\nNX502 CPU Unit specifications of the is provided along with the following infor-\nHardware NX502 CPU Units, mation on the CPU Unit.\nUser’s Manual including introductory • Features and system configuration\ninformation, design- • Introduction\ning, installation, and • Part names and functions\nmaintenance. • General specifications\nMainly hardware in- • Installation and wiring\nformation is provided. • Maintenance and inspection\nNX-series W593 NX102-££££ Learning the basic An introduction to the entire NX102 system\nNX102 CPU Unit specifications of the is provided along with the following infor-\nHardware NX102 CPU Units, mation on the CPU Unit.\nUser’s Manual including introductory • Features and system configuration\ninformation, design- • Introduction\ning, installation, and • Part names and functions\nmaintenance. • General specifications\nMainly hardware in- • Installation and wiring\nformation is provided. • Maintenance and inspection\nNX-series W578 NX1P2-££££ Learning the basic An introduction to the entire NX1P2 system\nNX1P2 CPU Unit specifications of the is provided along with the following infor-\nHardware NX1P2 CPU Units, mation on the CPU Unit.\nUser’s Manual including introductory • Features and system configuration\ninformation, design- • Introduction\ning, installation, and • Part names and functions\nmaintenance. • General specifications\nMainly hardware in- • Installation and wiring\nformation is provided. • Maintenance and inspection\nNJ-series CPU Unit W500 NJ501-££££ Learning the basic An introduction to the entire NJ-series sys-\nHardware User's Manual NJ301-££££ specifications of the tem is provided along with the following in-\nNJ101-££££ NJ-series CPU Units, formation on the CPU Unit.\nincluding introductory • Features and system configuration\ninformation, design- • Introduction\ning, installation, and • Part names and functions\nmaintenance. • General specifications\nMainly hardware in- • Installation and wiring\nformation is provided. • Maintenance and inspection\n24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nRelated Manuals\nManual name Cat. No. Model numbers Application Description\nNJ/NX-series CPU Unit W501 NX701-££££ Learning how to pro- The following information is provided on a\nSoftware User’s Manual NX502-££££ gram and set up an Controller built with an NJ/NX-series CPU\nNX102-££££ NJ/NX-series CPU Unit.\nNX1P2-££££ Unit. • CPU Unit operation\nNJ501-££££ Mainly software infor- • CPU Unit features\nNJ301-££££ mation is provided. • Initial settings\nNJ101-££££ • Programming based on IEC 61131-3\nlanguage specifications\nNX-series NX1P2 CPU Unit W579 NX1P2-££££ Learning about the Of the functions for an NX1P2 CPU Unit,\nBuilt-in I/O and Option Board details of functions the following information is provided.\nUser’s Manual only for an NX-series • Built-in I/O\nNX1P2 CPU Unit and • Serial Communications Option Boards\nan introduction of • Analog I/O Option Boards\nfunctions for an An introduction of following functions for an\nNJ/NX-series CPU NJ/NX-series CPU Unit is also provided.\nUnit. • Motion control functions\n• EtherNet/IP communications functions\n• EtherCAT communications functions\nNJ/NX-series Instructions W502 NX701-££££ Learning detailed The instructions in the instruction set (IEC\nReference Manual NX502-££££ specifications on the 61131-3 specifications) are described.\nNX102-££££ basic instructions of\nNX1P2-££££ an NJ/NX-series\nNJ501-££££ CPU Unit.\nNJ301-££££\nNJ101-££££\nNJ/NX-series CPU Unit W507 NX701-££££ Learning about mo- The settings and operation of the CPU Unit\nMotion Control User’s Man- NX502-££££ tion control settings and programming concepts for motion con-\nual NX102-££££ and programming trol are described.\nNX1P2-££££ concepts.\nNJ501-££££\nNJ301-££££\nNJ101-££££\nNJ/NX-series W508 NX701-££££ Learning about the The motion control instructions are descri-\nMotion Control Instructions NX502-££££ specifications of the bed.\nReference Manual NX102-££££ motion control in-\nNX1P2-££££ structions.\nNJ501-££££\nNJ301-££££\nNJ101-££££\nNJ/NX-series W505 NX701-££££ Using the built-in Information on the built-in EtherCAT port is\nCPU Unit NX502-££££ EtherCAT port on an provided.\nBuilt-in EtherCAT® Port NX102-££££ NJ/NX-series CPU This manual provides an introduction and\nUser’s Manual NX1P2-££££ Unit. provides information on the configuration,\nNJ501-££££ features, and setup.\nNJ301-££££\nNJ101-££££\nNJ/NX-series W506 NX701-££££ Using the built-in Information on the built-in EtherNet/IP port\nCPU Unit NX502-££££ EtherNet/IP port on is provided.\nBuilt-in EtherNet/IP™ Port NX102-££££ an NJ/NX-series Information is provided on the basic setup,\nUser’s Manual NX1P2-££££ CPU Unit. tag data links, and other features.\nNJ501-££££\nNJ301-££££\nNJ101-££££\nNJ/NX-series W588 NX701-££££ Using the OPC UA. Describes the OPC UA.\nCPU Unit NX502-££££\nOPC UA NX102-££££\nUser’s Manual NJ501-1£00\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 25\nRelated Manuals\nManual name Cat. No. Model numbers Application Description\nNX-series W596 NX701-££20 Using the FINS func- Describes the FINS function of an NX-ser-\nCPU Unit NX502-££££ tion of an NX-series ies CPU Unit.\nFINS Function NX102-££££ CPU Unit.\nUser’s Manual\nNJ/NX-series W527 NX701-££20 Using the database Describes the database connection serv-\nDatabase Connection CPU NX502-££££ connection service ice.\nUnits NX102-££20 with NJ/NX-series\nUser’s Manual NJ501-££20 Controllers.\nNJ101-££20\nNJ-series W528 NJ501-1340 Using the GEM Serv- Provides information on the GEM Services.\nSECS/GEM CPU Units ices with NJ-series\nUser’s Manual Controllers.\nNJ-series O037 NJ501-R£££ Using the NJ-series Describes the settings and operation of the\nRobot Integrated CPU Unit Robot Integrated CPU Unit and programming concepts for\nUser’s Manual CPU Unit. OMRON robot control.\nSysmac Studio W595 SYSMAC-SE2£££ Learning about the Describes the operating procedures of the\nRobot Integrated System SYSMAC- operating procedures Sysmac Studio for Robot Integrated CPU\nBuilding Function with Robot SE200D-64 and functions of the Unit.\nIntegrated CPU Unit Opera- Sysmac Studio to\ntion Manual configure Robot Inte-\ngrated System using\nRobot Integrated\nCPU Unit.\nSysmac Studio W621 SYSMAC-SE2£££ Learning about the Describes the operating procedures of the\nRobot Integrated System SYSMAC- operating procedures Sysmac Studio for IPC Application Control-\nBuilding Function with IPC SE200D-64 and functions of the ler.\nApplication Controller Opera- Sysmac Studio to\ntion Manual configure Robot Inte-\ngrated System using\nIPC Application Con-\ntroller.\nSysmac Studio W618 SYSMAC-SE2£££ Learning about an Describes an outline, execution proce-\n3D Simulation Function Op- SYSMAC-SA4££ outline of the 3D sim- dures, and operating procedures for the 3D\neration Manual £-64 ulation function of the simulation function of the Sysmac Studio.\nSysmac Studio and\nhow to use the func-\ntion.\nNJ-series W539 NJ501-4£££ Controlling robots Describes the functionality to control ro-\nNJ Robotics CPU Unit NJ501-R£££ with NJ-series CPU bots.\nUser’s Manual Units.\nNJ/NY-series O030 NJ501-5300 Performing numerical Describes the functionality to perform the\nNC Integrated Controller NY532-5400 control with NJ/NY- numerical control.\nUser’s Manual series Controllers.\nNJ/NY-series O031 NJ501-5300 Learning about the The G code/M code instructions are descri-\nG code NY532-5400 specifications of the bed.\nInstructions Reference Man- G code/M code in-\nual structions.\nNJ/NX-series W503 NX701-££££ Learning about the Concepts on managing errors that may be\nTroubleshooting Manual NX502-££££ errors that may be detected in an NJ/NX-series Controller and\nNX102-££££ detected in an information on individual errors are descri-\nNX1P2-££££ NJ/NX-series Con- bed.\nNJ501-££££ troller.\nNJ301-££££\nNJ101-££££\nSysmac Studio Version 1 W504 SYSMAC Learning about the Describes the operating procedures of the\nOperation Manual -SE2£££ operating procedures Sysmac Studio.\nand functions of the\nSysmac Studio.\n26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nRelated Manuals\nManual name Cat. No. Model numbers Application Description\nCNC Operator O032 SYSMAC Learning an introduc- An introduction of the CNC Operator, in-\nOperation Manual -RTNC0£££D tion of the CNC Op- stallation procedures, basic operations,\nerator and how to connection operations, and operating pro-\nuse it. cedures for main functions are described.\nNX-series Z930 NX-SL££££ Learning how to use Describes the hardware, setup methods,\nSafety Control Unit NX-SI££££ NX-series Safety and functions of the NX-series Safety Con-\nUser's Manual NX-SO££££ Control Units. trol Units.\nSysmac Library W625 SYSMAC-XR020 Learning how to per- Describes the specifications and proce-\nUser's Manual form Pub/Sub mes- dures to use the function block of MQTT\nfor MQTT Communications sage communica- communications library.\nLibrary tions through MQTT\nbroker.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 27\nRevision History\nRevision History\nA manual revision code appears as a suffix to the catalog number on the front and back covers of the\nmanual.\nCat. No. W506-E1-37\nRevision code\nRevision\nDate Revised content\ncode\n01 July 2011 Original production\n02 March 2012 • Added information on the NJ301-££££.\n• Added A-8 Accesing Variables with CIP Message Communications.\n• Added information on the functions supported by unit version 1.01 of the\nCPU Units.\n• Corrected mistakes.\n03 May 2012 • Added information on the functions supported by unit version 1.02 of the\nCPU Units.\n• Corrected mistakes.\n04 August 2012 • Added information on the functions supported by unit version 1.03 of the\nCPU Units.\n• Corrected mistakes.\n05 February 2013 • Added information on the functions supported by unit version 1.04 of the\nCPU Units.\n• Corrected mistakes.\n06 April 2013 • Corrected mistakes.\n07 June 2013 • Added information on the functions supported by unit version 1.06 of the\nCPU Units.\n08 December 2013 • Added information on the functions supported by unit version 1.08 of the\nCPU Units.\n• Corrected mistakes.\n09 July 2014 • Added information on the functions supported by unit version 1.09 of the\nCPU Units.\n• Corrected mistakes.\n10 January 2015 • Added information on the functions supported by unit version 1.10 of the\nCPU Units.\n• Corrected mistakes.\n11 April 2015 • Added information on the NX701-££££.\n• Added information on the NJ101-££££.\n• Corrected mistakes.\n12 October 2015 • Added information on the hardware revision.\n• Corrected mistakes.\n13 April 2016 • Added information on the functions supported by unit version 1.11 of the\nCPU Units.\n• Corrected mistakes.\n28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nRevision History\nRevision\nDate Revised content\ncode\n14 July 2016 • Added information on the functions supported by unit version 1.12 of the\nCPU Units.\n• Corrected mistakes.\n15 October 2016 • Added information on the NX1P2-££££££.\n• Added information on the functions supported by unit version 1.13 of the\nCPU Units.\n• Corrected mistakes.\n16 April 2017 • Added information on the functions supported by unit version 1.14 of the\nCPU Units.\n• Corrected mistakes.\n17 October 2017 • Corrected mistakes.\n18 January 2018 • Added information on the functions supported by unit version 1.17 of the\nCPU Units.\n• Corrected mistakes.\n19 April 2018 • Added information on the NX102-££££.\n• Added information on the functions supported by unit version 1.30 of the\nCPU Units.\n• Consolidated descriptions related to event codes and errors into the\nNJ/NX-series Troubleshooting Manual.\n• Corrected mistakes.\n20 July 2018 • Added information on the functions supported by unit version 1.31 of the\nNX102-££££.\n21 April 2019 • Added information on the functions supported by unit version 1.32 of\nNX102-££££.\n• Added information on the functions supported by unit version 1.21 of the\nNX1P2-££££££, NJ501-1£00, NJ301-££££, and NJ101-££00.\n• Corrected mistakes.\n22 July 2019 • Added information on the functions supported by unit version 1.21 of the\nNX701-££££, NJ501-4£00, NJ501-4£10, NJ501-1340 and\nNJ501-5300.\n• Corrected mistakes.\n23 October 2019 • Added information on the NX1P2-9B££££.\n• Corrected mistakes.\n24 August 2020 • Made changes accompanying the addition of NJ501-R£££.\n• Corrected mistakes.\n25 July 2021 • Added information on the functions supported by unit version 1.24 of the\nNX701-1££0.\n• Added information on the functions supported by unit version 1.36 of the\nNX102-1£20.\n• Added information on the functions supported by unit version 1.45 of the\nNX1P2-££00, NJ301-££00, and NJ101-££00.\n• Added information on the functions supported by unit version 1.25 of the\nNJ501-1£20, NJ501-1340, NJ501-4£££, NJ501-5300, and\nNJ101-1£20.\n• Added information on the functions supported by unit version 1.43 of the\nNX102-££00, NJ501-1£00, and NJ501-R£00.\n• Made changes on the information of the SD Memory Card.\n• Corrected mistakes.\n26 October 2021 • Added information related to the hardware revision A of the NX701-£££\n£.\n• Corrected mistakes.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 29\nRevision History\nRevision\nDate Revised content\ncode\n27 November 2021 • Added information related to the hardware revision D of the NJ-series\nCPU Unit.\n28 April 2022 • Added information to Terms and Conditions Agreement.\n29 June 2022 • Added information related to the hardware revision B of the NX701-£££\n£.\n30 November 2022 • Added information on the functions supported by unit version 1.60 of the\nNJ-series, NX102, and NX1P2 CPU Units.\n• Added information on the functions supported by unit version 1.32 of the\nNX701 CPU Units.\n31 January 2023 • Corrected mistakes.\n32 April 2023 • Added information on the NX502-1£££.\n33 May 2023 • Corrected mistakes.\n34 October 2023 • Made changes accompanying the release of unit version 1.64 of NX502\nCPU Units.\n35 April 2024 • Added information on the NX502-1700 and NX502-1600.\n36 October 2024 • Made changes on specifications of the CJ-series EtherNet/IP Unit CJ1W-\nEIP21S.\n37 February 2025 • Added information on the functions supported by unit version 1.68 of the\nNX102 CPU Units.\n30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1\nIntroduction\n1-1 Introduction....................................................................................................1-2\n1-1-1 EtherNet/IP Features.......................................................................................1-2\n1-1-2 Features of Built-in EtherNet/IP Port on NJ/NX-series CPU Units..................1-2\n1-2 System Configuration and Configuration Devices.....................................1-6\n1-2-1 Devices Required to Construct a Network......................................................1-6\n1-2-2 Support Software Required to Construct a Network.......................................1-7\n1-3 Built-in EtherNet/IP Port................................................................................1-9\n1-3-1 Specifications..................................................................................................1-9\n1-3-2 Part Names and Functions............................................................................1-13\n1-4 Introduction to Communications Services................................................1-20\n1-4-1 CIP (Common Industrial Protocol) Communications Services......................1-20\n1-4-2 IP Routing......................................................................................................1-22\n1-4-3 Packet Filter..................................................................................................1-23\n1-4-4 Packet Filter (Simple) ...................................................................................1-24\n1-4-5 BOOTP Client................................................................................................1-24\n1-4-6 DHCP Client..................................................................................................1-25\n1-4-7 FTP Server....................................................................................................1-25\n1-4-8 FTP Client.....................................................................................................1-25\n1-4-9 Automatic Clock Adjustment.........................................................................1-26\n1-4-10 Socket Service..............................................................................................1-26\n1-4-11 Secure Socket Services................................................................................1-27\n1-4-12 Specifying Host Names.................................................................................1-28\n1-4-13 SNMP Agent..................................................................................................1-28\n1-4-14 TCP/UDP Message Service..........................................................................1-29\n1-5 EtherNet/IP Communications Procedures.................................................1-30\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-1\n1\n1 Introduction\n1-1 Introduction\n1-1-1 EtherNet/IP Features\nEtherNet/IP is an industrial multi-vendor network that uses Ethernet.\nThe EtherNet/IP specifications are open standards managed by the ODVA (Open DeviceNet Vendor\nAssociation), just like DeviceNet.\nEtherNet/IP is not just a network between Controllers. It is also used as a field network. Because\nEtherNet/IP uses standard Ethernet technology, various general-purpose Ethernet devices can be\nused in the network.\nSysmac Studio Ethernet switch\n(Support Software)\nTwisted-pair cable\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\n100 m\nEthernet (LAN) port port on NJ/NX -series port on NJ/NX -series port on NJ/NX -series\nmax.\nController Controller Controller\nEtherNet/IP System Configuration Example\n High-speed, High-capacity Data Exchange through Tag Data Links\nThe EtherNet/IP protocol supports implicit communications, which allows cyclic communications\n(called tag data links in this manual) with EtherNet/IP devices.\n Tag Data Link (Cyclic Communications) Cycle Time\nTag data links (cyclic communications) operate at the cyclic period specified for each application,\nregardless of the number of nodes. Data is exchanged over the network at the refresh cycle set for\neach connection, so the communications refresh cycle will not increase even if the number of no-\ndes is increased, i.e., the concurrency of the connection's data is maintained.\nBecause the refresh cycle can be set for each connection, each application can communicate at its\nideal refresh cycle. For example, interprocess interlocks can be transferred at high speed, while the\nproduction commands and the status monitor information are transferred at low speed.\n1-1-2 Features of Built-in EtherNet/IP Port on NJ/NX-series CPU Units\n Tag Data Links\nCyclic communications between Controllers or between a Controller and other devices are possible\non an EtherNet/IP network.\nHigh-speed data exchange can be performed through tag data links.\n1-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n CIP Message Communications\nYou can send CIP commands to devices on the EtherNet/IP network when required by executing\nCIP communications instructions in a program.\nAs a result, it is possible to send and receive data with the devices on the EtherNet/IP network.\n BOOTP Client\nIf the built-in EtherNet/IP port on an NJ/NX-series CPU Unit is set in the BOOTP settings, the\nBOOTP client operates when the Controller power is turned ON, and the IP address is obtained\nfrom the BOOTP server.\nIt is possible to set all of the IP addresses of multiple built-in EtherNet/IP ports at the same time.\n DHCP Client\nIf the built-in EtherNet/IP port on an NX502 CPU Unit is set in the DHCP settings, the DHCP client\noperates when the Controller power is turned ON, and the IP address is obtained from the DHCP\nserver.\nIt is possible to set all of the IP addresses of multiple built-in EtherNet/IP ports at the same time.\n FTP Server for File Transfers to and from Host Computers\nAn FTP server is built into the Controller. You can use it to read and write data within the Controller\nas files from workstations and computers with FTP clients.\nThe FTP server enables the transfer of large amounts of data from a client without any additional\nladder programming.\n FTP Client for File Transfers to and from Host Computers\nAn FTP client is built into the Controller, so you can read and write files on workstations and com-\nputers that have an FTP server from the Controller.\nYou can use the FTP client communications instructions to transfer one or more files between the\nController and an FTP server.\n NTP Client for Automatic Controller Clock Adjustment\nThe clocks built into Controllers connected to Ethernet can be automatically adjusted to the time of\nthe clock in the NTP server. If all of the clocks in the system are automatically adjusted to the same\ntime, time stamps can be used to analyze production histories.\n*1. A separate NTP server is necessary to automatically adjust the Controller clocks.\n Socket Services\nSocket services can be used to send and receive data between general-purpose applications and\nControllers.\nThrough the communications services with sockets, you can send and receive data to and from re-\nmote nodes, i.e., between the host computer and Controllers or between Controllers.\nYou can execute socket communications instructions in order in a program to execute communica-\ntions processes with the socket services.\nThere are two socket services, the UDP socket service and TCP socket service.\nIn addition, secure socket services which perform encrypted communications using TLS are availa-\nble.\nSecure socket service instructions can be used for secure socket communications with external\ncloud or on-premises servers.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-3\n1-1\nIntroduction\n1\n1-1-2\nFeatures\nof\nBuilt-in\nEtherNet/IP\nPort\non\nNJ/NX-series\nCPU\nUnits\n1 Introduction\nIn addition, the MQTT communications library can be used for secure socket communications with\na MQTT broker .\nAdditional Information\nFunction Blocks (FBs) for MQTT communications are available for the secure socket communi-\ncations between a CPU Unit and a MQTT broker.\nRefer to the Sysmac Library User’s Manual for MQTT Communications Library (Cat. No. W625)\nfor more information on FBs for MQTT communications.\n DNS Client for Specifying Host Names\nWhen you specify an NTP server, SNMP manager, or the destination of socket instructions or CIP\ncommunications instructions, you can use the host name, as well as its IP address (DNS client or\nhosts settings).\nThis will help identify the IP address automatically even after the IP addresses of relevant servers\nare changed due to system revisions.\n*1. A separate DNS server is necessary when you use host names with the DNS client.\n*2. The DNS server is specified directly using its IP address.\n Network Management with an SNMP Manager\nThe SNMP agent passes internal status information from the built-in EtherNet/IP port to network\nmanagement software that uses an SNMP manager.\n*1. A separate SNMP manager is necessary for network management.\n Complete Troubleshooting Functions\nA variety of functions are provided to quickly identify and handle errors.\n• Self-diagnosis at startup\n• Event log that records the time of occurrence and other error details\n Two EtherNet/IP Communications Ports as a Standard Feature, Equipped\nwith IP Routing Function (Only with the NX701, NX502, and NX102 CPU\nUnits)\nThese CPU Units are equipped with two EtherNet/IP ports for EtherNet/IP communications as\nstandard.\nThis feature allows you to separate the information network from the control network. In addition,\nthe built-in EtherNet/IP ports support the IP routing function to send IP packets to devices on other\nIP network segments.\n*1. In order to use the function, you must appropriately set the IP router table and default gateway settings for\neach device on the network according to your network configuration. For details on the settings, refer to\n4-1 TCP/IP Settings Display on page 4-2.\n CIP Safety on EtherNet/IP Compatible (Only with the NX502 and NX102\nCPU Units)\nCombined with the NX-SL5£££ Safety Control Unit, you can build a system which uses CIP\nSafety on EtherNet/IP communications in networks between Controllers and field networks. Safety\ncommunications by CIP Safety is enabled with devices that support CIP Safety on EtherNet/IP and\nother Safety CPU Units.\n1-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nVersion Information\n• For NX502 CPU Units, CIP Safety communications via the built-in EtherNet/IP port can be\nperformed only when an NX502 CPU Unit with unit version 1.64 or later and an NX-SL5£££\nSafety Control Unit are used together.\n• To perform CIP Safety communications in the NX502 CPU Unit of unit version earlier than"}
+{"question": "64, use an NX-EIP201 EtherNet/IP Unit in addition to the NX-SL5£££ Safety Control Unit.", "answer": "Additional Information\nCIP (Common Industrial Protocol)\nCIP is a shared industrial protocol for the OSI application layer. The CIP is used in networks\nsuch as EtherNet/IP, CompoNet, and DeviceNet.\nData can be routed easily between networks that are based on the CIP. You can therefore easi-\nly configure a transparent network from the field device level to the host level.\nThe CIP has the following advantages.\n• Destination nodes are specified by a relative path, without fixed routing tables.\n• The CIP uses the producer/consumer model. Nodes in the network are arranged on the same\nlevel and it is possible to communicate with required devices whenever it is necessary.\nThe consumer node will receive data sent from a producer node when the connection ID in\nthe packet indicates that the node requires the data. Because the producer can send the\nsame data with the same characteristics in a multicast format, the time required for the trans-\nfer is fixed and not dependent on the number of consumer nodes. (Either multicast or unicast\ncan be selected.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-5\n1-1\nIntroduction\n1\n1-1-2\nFeatures\nof\nBuilt-in\nEtherNet/IP\nPort\non\nNJ/NX-series\nCPU\nUnits\n1 Introduction\n1-2 System Configuration and Configura-\ntion Devices\n1-2-1 Devices Required to Construct a Network\nThe basic configuration for an EtherNet/IP system includes one Ethernet switch to which nodes are\nattached in star configuration using twisted-pair cable.\nSysmac Studio (3) Ethernet switch\n(Support Software)\n(2) Twisted-pair cable\n(1) Built-in EtherNet/IP (1) Built-in EtherNet/IP (1) Built-in EtherNet/IP\nport on NJ/NX- port on NJ/NX- port on NJ/NX-\nEthernet (LAN) port 100 m series CPU Unit series CPU Unit series CPU Unit\nmax.\nThe following products are also required to build a network. Obtain them in advance.\nNetwork device Function\nPer Node These Units are used to connect to an EtherNet/IP\n• NJ-series CPU Unit (built-in EtherNet/IP port) network.\n(NJ501-££££/NJ301-££££/NJ101-££££)\n• NX-series CPU Unit (built-in EtherNet/IP port)\n(NX701-££££/NX502-££££/NX102-£££££\n£/NX1P2-££££££)\n• Other OMRON PLCs\nCJ2 CPU Units (built-in EtherNet/IP port)\n(CJ2H-CPU££-EIP/CJ2M-CPU3£)\nCJ-series EtherNet/IP Unit\n(CJ1W-EIP21/CJ1W-EIP21S)\nCS-series EtherNet/IP Unit\n(CS1W-EIP21/CS1W-EIP21S)\n(2)Twisted-pair cable The twisted-pair cable has an RJ45 Modular Connec-\ntor at each end.\nThis cable is used to connect the built-in EtherNet/IP\nport or EtherNet/IP Unit to an Ethernet switch.\nUse an STP (shielded twisted-pair) cable of category\n5, 5e, or higher.\n(3)Ethernet switch This is a relay device that connects multiple nodes in a\nstar LAN.\nFor details on recommended devices to configure a\nnetwork, refer to 2-1-1 Recommended Network Devi-\nces on page 2-2.\n1-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n1-2-2 Support Software Required to Construct a Network\nThis section describes the Support Software that is required to construct an EtherNet/IP network.\nThe built-in EtherNet/IP port has Ethernet Settings and Tag Data Link Settings, which are both stored\nin the non-volatile memory of the CPU Unit.\nSupport Software is provided for each, as described below.\n Built-in EtherNet/IP Port Settings: Sysmac Studio\nUse the Sysmac Studio to set the basic settings, such as the local IP address and subnet mask of\nthe built-in EtherNet/IP port.\nThe Sysmac Studio can also be used to check if data I/O is being performed correctly for tag data\nlinks.\nWindows Computer\nSysmac Studio\nEdit Parameters\nBuilt-in EtherNet/IP port Dialog Box\nsettings (non-volatile memory)\nBuilt-in EtherNet/IP port\nNJ/NX-series CPU Unit\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on the Sysmac\nStudio.\n Tag Data Link Settings: Network Configurator\nUse the Network Configurator to set the tag data links for the built-in EtherNet/IP port. (The Net-\nwork Configurator is included in the Sysmac Studio Standard Edition.) The main functions of the\nNetwork Configurator are given below.\n• Setting and Monitoring Tag Data Links (Connections)\nThe network device configuration and tag data links (connections) can be created and edited. Af-\nter connecting to the network, the device configuration and tag data link settings can be upload-\ned and monitored.\n• Multi-vendor Device Connections\nEDS files can be installed and deleted so that you can construct, set, and manage networks that\ncontain EtherNet/IP devices from other companies. The IP addresses of EtherNet/IP devices can\nalso be changed.\nWindows computer with\nNetwork Configurator\nTag Data Link Settings Edit Device\n(non-volatile memory) Parameters\nDialog Box\nTransferred.\nBuilt-in EtherNet/IP port\nNJ/NX-series CPU Unit\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-7\nConfiguration\nDevices\n1-2\nSystem\nConfiguration\nand\n1\n1-2-2\nSupport\nSoftware\nRequired\nto\nConstruct\na\nNetwork\n1 Introduction\nFor details on the Network Configurator, refer to Section 6 Tag Data Link Functions on page\n6-1.\nAdditional Information\nYou can also use the Sysmac Studio to set the tag data links.\nRefer to A-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP Connections) on\npage A-5 for details on setting the tag data links on the Sysmac Studio.\n1-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n1-3 Built-in EtherNet/IP Port\n1-3-1 Specifications\nSpecifications\nNX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££\n££ ££ ££ ££££ NJ301-££££ ££\nItem\nUnit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-\nsion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10\nor later or later or later or later to 1.02 or later or later\nCommunications protocol TCP/IP or UDP/IP\nSysmac Studio connection, tag data link, CIP message communications, socket services, FTP serv-\nSupported services er, FTP client, automatic clock adjustment (NTP client), SNMP agent, DNS client, BOOTP client,\nDHCP client*1, Packet Filterr*2, and Packet Filter (Simple)*3\nNumber of ports 2 (IP routing function supported) 1\n100Base-TX, 10Base-T, or 100Base-TX or 10Base-T (100Base-TX is recommended.) *4\n1000Base-T (1000Base-T\nPhysical layer\nor 100Base-TX is recom-\nmended.) *4\nMedia access CSMA/CD\nmethod\nModulation Baseband\nTransmission Star form\npaths\nBaud rate 1,000 Mbps (1000Base-T) 100 Mbps (100Base-TX)\nTransmission\nTransmission Shielded twisted-pair (STP) cable, Category 5, 5e, or higher\nspecifications\nmedia\nTransmission 100 m max. (distance between hub and node)\ndistance\nNumber of cas- There is no limitation when an Ethernet switch is used.\ncade connec-\ntions\n256 per port 64 per port 32 per port 32\nNumber of con- (total of 512 (total of 128 (total of 64\nnections with two with two with two\nCIP service: ports) ports) ports)\nTag data links 0.5 to 1 to 10,000 ms in 1-ms in- 2 to 10,000 10 to 1 to 10,000 ms in 1-ms in-\n(cyclic com- 10,000 ms crements ms in 1-ms 10,000 ms crements\nmunications) Packet interval in 0.5-ms increments in 1-ms in-\n(refresh cycle) increments crements\nPacket intervals can be set independently for each connection. (Data is refreshed over the network\nat preset intervals and the refresh cycle does not depend on the number of nodes.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-9\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-1\nSpecifications\n1 Introduction\nSpecifications\nNX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££\n££ ££ ££ ££££ NJ301-££££ ££\nItem\nUnit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-\nsion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10\nor later or later or later or later to 1.02 or later or later\n40,000 20,000 12,000 3,000 pps*5 1,000 pps*5 3,000 pps*5\npps*5*6 pps*5*6 pps*5*6\nAllowed com- Note: The Note: The Note: The Note: The heartbeat is included.\nmunications heartbeat is heartbeat heartbeat\nbandwidth per included. and the CIP and the CIP\nUnit Safety rout- Safety rout-\ning are in- ing are in-\ncluded.*7 cluded.*8\nNumber of reg- 256 per port (total of 512 with two ports) 256\nistrable tags\nNetwork Network variable Network Network variable\nvariable CIO, Work, Holding, DM, variable CIO, Work, Holding, DM, or EM Areas\nCIO, Work, or EM Areas can be used. CIO, Work, can be used.\nHolding, Holding, or\nCIP service: Tag types\nDM, or EM DM Areas\nTag data links\nAreas can- can be\n(cyclic com-\nnot be used.\nmunications)\nused.\n8 (7 tags 64 (63 tags 8 (7 tags when the tag set includes the Controller status)\nwhen the when the\nNumber of tags\ntag set in- tag set in-\nper connection\ncludes the cludes the\n(= 1 tag set)\nController Controller\nstatus) status)\n369,664 92,416 19,200 19,200 bytes\nbytes per bytes per bytes per\nMaximum link\nport (total of port (total of port (total of\ndata size per\n739,328 184,832 38,400\nnode\nbytes with bytes with bytes with\ntwo ports) two ports) two ports)\n1,444 bytes*9 600 bytes*9\nMaximum data\nData concurrency is maintained within each connection.\nsize per connec-\nRefer to 6-1-7 Concurrency of Tag Data Link Data on page 6-14 for methods to maintain concur-\ntion\nrency.\n256 per port 64 per port 32 per port 32 (1 connection = 1 tag set)\n(1 connec- (1 connec- (1 connec-\ntion = 1 tag tion = 1 tag tion = 1 tag\nNumber of reg-\nset) set) set)\nistrable tag sets\n(total of 512 (total of 128 (total of 40\nwith two with two with two\nports) ports) ports)*10\n722 words 300 words\n(The Controller status (The Controller status uses 1 word when the tag set includes the Con-\nMaximum size\nuses 1 word when the tag troller status.)\nof 1 tag set\nset includes the Controller\nstatus.)\nChanging tag Supported*11\ndata link param-\neters when Con-\ntroller is in RUN\nmode\n1-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nSpecifications\nNX701-££ NX502-££ NX102-££ NX1P2-££ NJ501-££££ NJ101-££\n££ ££ ££ ££££ NJ301-££££ ££\nItem\nUnit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver-\nsion 1.10 sion 1.60 sion 1.30 sion 1.13 sion 1.00 sion 1.03 sion 1.10\nor later or later or later or later to 1.02 or later or later\nMulti-cast pack- Supported\net filter*12\nConnections: 128 per port Connec- Connections: 32 (clients plus servers)\n(total of 256 with two tions: 32\nports) (clients plus server) per port (to-\nClass 3 (number tal of 64\nof connections) with two\nports) (cli-\nents plus\nCIP message server)\nservice: UCMM (uncon- Number of clients that can communicate at one time: 32 max.\nExplicit nected) Number of servers that can communicate at one time: 32 max.\nmessages*13 Supported\nCIP routing is supported for the following remote Units:\nNX701-££££, NX502-££££, NX102-££££, and NX1P2-££££\nNJ501-££££, NJ301-££££, NJ101-££££,\nCIP routing*14\nCS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, CJ1W-EIP21S,\nCJ2H-CPU££-EIP, and CJ2M-CPU3£.\nUsing a combination of any Units above, communication can be extended up to a maximum of 8\nlevels.\nMaximum num- --- 128 total 16 total ---\nber of routable\nCIP Safety con-\nCIP Safety nections\nrouting*7*8*15 Maximum routa- --- 32 bytes ---\nble safety data\nlength per con-\nnection\nAgents SNMPv1 or SNMPv2c\nSNMP\nMIB MIB-II\nConforms to CT18 Conforms Conforms Conforms to CT18\nEtherNet/IP conformance test to CT20 to CT13\n*16\n10Base-T, Fixed to au- 10Base-T or 100Base-TX\n100Base- to negotia- Auto negotiation or fixed settings\nTX, or tion\n1000Base-\nEthernet interface T\nAuto nego-\ntiation or\nfixed set-\ntings\n*1. The DHCP client is available only with NX502 CPU Units.\n*2. The Packet Filter can be used in CPU Units with the following unit versions.\n• NX502 CPU Unit: Version 1.60 or later\n• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later\n• NX701 CPU Unit: Version 1.29 or later\n*3. The Packet Filter (Simple) is available only with NX102 CPU Units.\n*4. If tag data links are being used, use 100Base-TX or 1000Base-T.\n*5. Here, pps means “packets per second” and indicates the number of packets that can be processed in one second.\n*6. If the two built-in EtherNet/IP ports are used simultaneously, the maximum communications data size means the maximum data size of\nthe total of the two ports.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-11\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-1\nSpecifications\n1 Introduction\n*7. An NX502 CPU Unit with unit version 1.64 or later is required to use the CIP Safety routing.\n*8. An NX102 CPU Unit with unit version 1.31 or later is required to use the CIP Safety routing.\n*9. To use a data size of 505 bytes or larger, the system must support a large forward open (an optional CIP specification). The CS, CJ,\nNJ, and NX-series Units support a large forward open, but before connecting to nodes of other companies, confirm that the devices\nalso support it.\n*10. When tag sets that exceed total of 40 are set, a Number of Tag Sets for Tag Data Links Exceeded (840E0000 hex) event occurs.\n*11. If the parameters of the built-in EtherNet/IP port are changed, the port is restarted. When other nodes are in communications with the\naffected node, the communications will temporarily time out and automatically recover after the restart.\n*12. Because the built-in EtherNet/IP port is equipped with an IGMP client (version 2), unnecessary multicast packets can be filtered out by\nan Ethernet switch that supports IGMP snooping.\n*13. The built-in EtherNet/IP port uses the TCP/UDP port numbers shown in A-12 TCP/ UDP Port Numbers Used for the Built-in\nEtherNet/IP Port on page A-95.\nDo not set the same port number for more than one TCP/UDP service.\n*14. A CPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher are required to use CIP routing.\n*15. When CIP Safety routing is used with the NX502 CPU Unit, it cannot be used if the task period of the primary periodic task is less than\n500 µs.\n*16. A CPU Unit with the unit version earlier than 1.64 conforms to CT14.\n1-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n1-3-2 Part Names and Functions\nParts and Names\n NX701 CPU Unit\nRUN\nERROR\nBUSY\nSHTDWN\nSD PWR\nSD BUSY\nPORT1\nEtherNet/IP\nNET RUN\nIndicators NET ERR\nLINK/ACT\nPORT1 EtherNet/IP\nPORT2 PORT3\nEtherNet/IP EtherCAT\nNET RUN NET RUN\nBuilt-in EtherNet/IP\nNET ERR NET ERR\nport 1 LINK/ACT LINK/ACT\nPORT2 EtherNet/IP PORT3 EtherCAT\nBuilt-in EtherNet/IP Built-in\nport 2 EtherCAT\nport\nMAC Address Notation\nA MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC\naddress of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in\nthe place of the Unit as shown below.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-13\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-2\nPart\nNames\nand\nFunctions\n1 Introduction\nLOT No. DDMYY£ xxxx Ver.1.££\nPORT1 : ££££££££££££ HW Rev.£\nPORT2 : ££££££££££££\nMAC addresses\n NX502 CPU Unit\nPOWER\nBuilt-in EtherNet/IP\nport 1\nIndicators\nPORT2 Built-in EtherNet/IP\nport 2\nBuilt-in EtherCAT\nport\nMAC Address Notation\nA MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC\naddress of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in\nthe place of the Unit as shown below.\n1-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nNX502-1£00 Ver.£.££ HW Rev.£\nPORT1 MAC ADDRESS:££££££££££££\nPORT2 MAC ADDRESS:££££££££££££\nPORT3 MAC ADDRESS:££££££££££££\nLOT No. DDMYY£ xxxx\nMAC addresses\n NX102 CPU Unit\nPORT1 EtherNet/IP\nBuilt-in EtherNet/IP\nport 1\nIndicators\nPORT2 EtherNet/IP\nBuilt-in EtherNet/IP\nport 2\nPORT3 EtherCAT\nBuilt-in EtherCAT\nport\nMAC Address Notation\nA MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC\naddress of each built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in\nthe place of the Unit as shown below.\nVer.£.££ HW Rev.£ LOT No. DDMYY£ xxxx\nPORT1 ££££££££££££\nPORT2 ££££££££££££\nMAC addresses\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-15\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-2\nPart\nNames\nand\nFunctions\n1 Introduction\n NX1P2 CPU Unit\nIN\nSW SETTING\nPORT1 EtherNet/IP P RO UNWER\nERROR\nBuilt-in EtherNet/IP port B SU DS PY WR\nSD BUSY\nPORT1 EtherNet/IP\nNET RUN\nPORT2 EtherCAT NET ERR\nLINK/ACT\nPORT2 EtherCAT\nNETRUN\nNET ERR\nLINK/ACT\nOUT\nIndicators\nMAC Address Notation\nA MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC\naddress of the built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in\nthe place of the Unit as shown below.\nPORT1 : ££££££££££££\nPORT2 : ££££££££££££\nVer.1.££ HW Rev. £\nLOT No. DDMYY£ xxxx\nMAC address of built-in EtherNet/IP port\n1-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n NJ-series CPU Unit\nUSB port\nBuilt-in EtherNet/IP port\nBuilt-in EtherCAT port\nIndicators\nMAC Address Notation\nA MAC address is uniquely allocated to each device connected to the Ethernet network. The MAC\naddress of the built-in EtherNet/IP port is represented in 12-digit hexadecimal format and listed in\nthe two places of the Unit as shown below.\nUpper 6 digits of MAC address\nPORT 1\nXXXXXX\nXXXXXX Lower 6 digits of MAC address\nMAC address (12 digits)\nNJ501-XXXX Ver. XXX\nPORT1 : XXXXXXXXXXXX\nPORT2 : XXXXXXXXXXXX\nXXXXXXX XXXX\nIndicators (LEDs)\nNX701 CPU Unit NX102 CPU Unit NX1P2 CPU Unit\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-17\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-2\nPart\nNames\nand\nFunctions\n1 Introduction\nPORT1\nSD BUSY\nEtherNet/IP\nNET RUN PORT1 EtherNet/IP\nNET RUN\nNET ERR NET ERR\nLINK/ACT LINK/ACT\nPORT2 EtherCAT\nPORT2 PORT3\nEtherNet/IP EtherCAT\nNET RUN NET RUN\nNET ERR NET ERR\nLINK/ACT LINK/ACT\nNJ-series CPU Unit NX502 CPU Unit\n NET RUN, NET ERR, and LINK/ACT\n• NET RUN indicator\nThis shows the status of the CIP connection (tag data links, Class 3 messages).\n• NET ERR indicator\nThis shows the network communications error status. Refer to Section 15 Troubleshooting on\npage 15-1 for details.\n• LINK/ACT indicator\nThis shows the Ethernet communications status.\nCol\nIndicator Status Operating status\nor\nEthernet communications are not possible.\n• The power supply is OFF or the Controller is reset.\n--- Not lit\n• A MAC address error or Communications Controller error is occurring.\n• The same IP address is assigned to more than one node.\nEthernet communications are in progress.\nFlash-\nNET RUN • Tag data link connection establishment in progress (originator operation)\ning\nGr • IP address acquisition with BOOTP in progress.\nee Normal\nn If only the target is set for the tag data link, this indicator is lit regardless of\nLit\nwhether the connection from the originator is established. It remains lit even\nif the data links are stopped.\nThere are no Ethernet communications errors.\n--- Not lit\n• The power supply is OFF or the Controller is reset.\nA user-recoverable error is occurring.\n• An error is occurring in TCP/IP communications or CIP communications.\nFlash-\nNET ERR • FTP Server Setting Error, NTP Server Setting Error, etc.\nRe ing\n• Tag Data Link Setting Error, Tag Data Link Verification Error, etc.\nd\n• The same IP address is assigned to more than one node.\nA user-non-recoverable error is occurring.\nLit\n• A MAC address error or Communications Controller error is occurring.\n1-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nCol\nIndicator Status Operating status\nor\nThe link is not established.\n--- Not lit • The cable is not connected.\n• The power supply is OFF or the Controller is reset.\nLINK/ACT\nFlash- Data communications in progress after establishing the link.\nYel\ning\nlow\nLit Link established.\nAdditional Information\nWhen the built-in EtherNet/IP port is set to be disabled, all the indicators are turned OFF.\nRefer to 4-1 TCP/IP Settings Display on page 4-2 for details on the settings of a built-in\nEtherNet/IP port.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-19\n1-3\nBuilt-in\nEtherNet/IP\nPort\n1\n1-3-2\nPart\nNames\nand\nFunctions\n1 Introduction\n1-4 Introduction to Communications\nServices\n1-4-1 CIP (Common Industrial Protocol) Communications Services\nTag Data Links (Cyclic Communications)\nA program is not required to perform cyclic data exchanges with other devices on the EtherNet/IP net-\nwork.\nNormally, a connection is started with the target device for each tag set that was created with the Net-\nwork Configurator to start communications for tag data links for a built-in EtherNet/IP port. One con-\nnection is used per tag set.\nThe maximum number of connections that can be registered is shown below.\n• NX701 CPU Unit: 256 connections (total of 512 connections with two ports)\n• NX502 CPU Unit: 64 connections (total of 128 connections with two ports)\n• NX102 CPU Unit: 32 connections (total of 64 connections with two ports)\n• NX1P2 CPU Unit: 32 connections\n• NJ-series CPU Unit: 32 connections\nAdditional Information\nThe NX502 CPU Unit can be used with the NX-EIP201 (EherNet/IP Unit) for tag data link com-\nmunications.\nHowever, check the effect on task execution time because it increases I/O refreshing time.\nRefer to 1-3-1 Specifications on page 1-9 for the built-in EtherNet/IP port tag and tag set specifica-\ntions.\n1-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nConnection Information\n• Target IP address\n• Target tag set\n• Originator tag set\n• Packet interval (RPI) Connection\nTag Set (Input) Tag Set (Output)\nTag set name: SP1_IN Tag set name: SP1_OUT\nController status Controller Status\nTag a Tag i\nTag b Tag ii\nData flow\nTag c\nTag g\nOriginator device Target device\nEtherNet/IP\nNoteIn this example, a connection is established with the originator’s tag list with tags a to g (inputs), which are\nin a tag set called SP1_IN, and the target’s tag list with tags i and ii (outputs), which are in a tag set called\nSP1_OUT.\nCIP Message Communications\nUser-specified CIP commands can be sent to devices on the EtherNet/IP network.\nCIP commands, such as those for reading and writing data, can be sent and their responses received\nby executing the CIP communications instructions from the user program in the NJ/NX-series CPU\nUnit.\nNJ/NX-series Controller Built-in EtherNet/IP port\nCIP message\nCIP_SEND\nEthernet\nCIP command\n(EtherNet/IP)\nCIP response\nBy specifying a route path, you can send CIP messages (CIP commands and responses) to a device\non another CIP-based network segment via a built-in EtherNet/IP port or the EtherNet/IP Unit (CIP\nrouting function for message communications).\nThe maximum number of levels of CIP routing via the ports is eight for any combination of CS, CJ, NJ,\nand NX-series CPU Units. Note that the number of levels of IP routing using an L3 Ethernet switch is\nnot counted in the number of levels of CIP routing via the ports.\n• NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-21\ntions\nServices\n1-4\nIntroduction\nto\nCommunica-\n1\n1-4-1\nCIP\n(Common\nIndustrial\nProtocol)\nCommunications\nServices\n1 Introduction\nBecause there are two built-in EtherNet/IP ports, CIP routing is possible by the CPU Unit alone.\nEthernet\n(EtherNet/IP)\nNX701 CPU Unit, NX502 CPU Unit and NX102 CPU Unit\nBuilt-in EtherNet/IP\nport 1\nEthernet\nBuilt-in EtherNet/IP\n(EtherNet/IP)\nport 2\n• NJ-series CPU Unit\nBy combining the built-in EtherNet/IP port and an EtherNet/IP Unit, CIP routing can be performed.\nEthernet\n(EtherNet/IP)\nNJ-series CPU Unit EtherNet/IP Unit\nEthernet\n(EtherNet/IP)\nBuilt-in EtherNet/IP port\nAdditional Information\nIn CIP routing, a node (Unit) that routes information subtracts the equivalent of one hop from\nthe timeout, deletes its own address from the route information, and relays the information to\nthe next node (Unit).\nWhen a timeout is specified, the timeout for the actual request service processing is set in the\nlast hop.\nIn the case of relay hops, the timeout for the relay route must be added to the timeout for the\nrequest.\nOMRON products that support CIP subtract 5 seconds per hop.\nVersion Information\nFor an NJ-series CPU Unit, you can use the EtherNet/IP Unit with a CPU Unit with unit version"}
+{"question": "01 or later and Sysmac Studio version 1.02 or higher.", "answer": "1-4-2 IP Routing\nThe EtherNet/IP on the NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units have the IP rout-\ning function. The IP routing function sends IP packets to other network segments based on the routing\ninformation set in the IP router table.\nTo communicate with devices on other network segments, you must set the IP router table and default\ngateway settings for the CPU Unit and each device on the network appropriately for your network con-\nfiguration.\n1-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nPrecautions for Correct Use\n• You cannot create tag data links between multiple CPU Units using IP routing on the NX701\nCPU Units, NX502 CPU Units, and NX102 CPU Units.\n• The IP routing function can only be used with the NX701 CPU Units, NX502 CPU Units, and\nNX102 CPU Units. IP routing cannot be used with a combination of a built-in EtherNet/IP port\non an NJ-series CPU Unit and an EtherNet/IP Unit.\nComputer\nHMI\nSysmac Studio\nIP address: 10.1.1.1/24 IP address: 10.1.1.2/24\nEtherNet/IP Network address: 10.1.1.0/24\nNX701, NX502, or\nNX102 CPU Unit IP router\ntable\nEtherNet/IP Network address: 10.1.2.0/24\nNX701, NX502, or\nNX102 CPU Unit IP router\ntable\nEtherNet/IP Network address: 10.1.3.0/24\nNJ-series\nCPU Unit\nIP address: 10.1.3.1/24\n Port Forward - IP Forward\nThis function divides the network for the built-in EtherNet/IP ports 1 and 2. When you divide the\nnetwork, set IP Forward to Do not use. When it is set to Do not use, any other IP packets than\nthose addressed to the Controller are discarded. Refer to 4-1 TCP/IP Settings Display on page\n4-2 for details. You can use this function only for the NX502 CPU Units and NX102 CPU Units.\nAdditional Information\nCIP routing is not be affected by the IP Forward setting.\n1-4-3 Packet Filter\nThis function filters IP packets in the receive processing at the built-in EtherNet/IP ports. While Packet\nFilter (Simple) is used to restrict Sysmac Studio connections, Packet Filter performs general-purpose\npacket filtering that does not restrict communication partner to Sysmac Studio. Specify packets al-\nlowed to be received by IP address or TCP/UDP port number.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-23\ntions\nServices\n1-4\nIntroduction\nto\nCommunica-\n1\n1-4-3\nPacket\nFilter\n1 Introduction\nVersion Information\nPacket Filter is available in the following CPU Units of stated versions.\n• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later\n• NX701 CPU Unit: Version 1.29 or later\n• NX502 CPU Unit: Version 1.60 or later\n1-4-4 Packet Filter (Simple)\nThis function filters IP packets in the receive processing at the built-in EtherNet/IP ports. When Packet\nFilter (Simple) is enabled, it will allow you to connect the Sysmac Studio only from a computer with the\npreregistered IP address, and restrict any other connection from those with unregistered IP addresses.\nThis function can be used only for NX102 CPU Unit.\nPrecautions for Correct Use\n• Connections to NA-series and NS-series Programmable Terminals are restricted if this func-\ntion is enabled. To make connections to these devices, register their IP addresses in the\nPacket Filter (Simple) settings. Refer to Packet Filter (Simple) on page 4-10 for details on\nthe setting.\n• If this function is enabled, you cannot connect the Sysmac Studio from a computer whose IP\naddress is not registered. Before enabling this function, confirm in advance that the IP ad-\ndress of the computer is correctly registered.\n• If this function is enabled, you cannot connect the Sysmac Studio to the Controller with the\nDirect connection via Ethernet Option selected for the connection type. Select Controller -\nCommunications Setup to confirm that Ethernet connection via a hub is selected for con-\nnection type.\n• You can disable this function tentatively by starting the Unit in Safe Mode in case you forget\nthe registered IP address and cannot go online from the Sysmac Studio. Refer to\nTroubleshooting When You Cannot Go Online from the Sysmac Studio in the NJ/NX-series\nTroubleshooting Manual (Cat. No. W503) for details.\n• You can use the Packet Filter (Simple) with Sysmac Studio version 1.49 or lower. Use the\nPacket Filter instead of the Packet Filter (Simple) when you use Sysmac Studio version 1.50\nor higher.\n1-4-5 BOOTP Client\nYou set the built-in EtherNet/IP port in the BOOTP settings to use the BOOTP client to obtain settings,\nsuch as the built-in EtherNet/IP port IP address, from the BOOTP server.\nBOOTP server\nBOOTP command Ethernet\nBuilt-in Built-in\nIP address EtherNet/IP port EtherNet/IP port\nBOOTP client\nThe built-in EtherNet/IP port IP address is obtained\nfrom the BOOTP server when the power is turned ON.\n1-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n1-4-6 DHCP Client\nYou set the built-in EtherNet/IP port in DHCP setting to use the DHCP client to obtain settings, such as\nthe built-in EtherNet/IP port IP address, from the DHCP server.\nThis function can be used only for the NX502 CPU Unit.\nDHCP server\nDHCP command Ethernet\nNJ/NX-series NJ/NX-series\nIP address\nController Controller\nDHCP client\n1-4-7 FTP Server\nAn FTP server is built into the built-in EtherNet/IP port so that files can be read from and written to the\nSD Memory Card in the CPU Unit of the Controller from computers at other Ethernet nodes.\nThis makes it possible to exchange data files between a host computer and the Controller with the\nhost computer as the FTP client and the Controller as the FTP server.\nHost computer\n(FTP client)\nEthernet\nFTP command Built-in EtherNet/IP port\nNJ-series Controller\nSD Memory\nCard\nHost computer to Controller Controller to Host computer\nFile data File data\nSD Memory SD Memory\nCard Card\n1-4-8 FTP Client\nThe built-in EtherNet/IP port contains an FTP client. With it, you can use FTP client communications\ninstructions to transfer files between the CPU Unit and host computers on Ethernet.\nThis makes it possible to exchange data files between a host computer and the Controller with the\nController as the FTP client and the host computer as the FTP server.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-25\ntions\nServices\n1-4\nIntroduction\nto\nCommunica-\n1\n1-4-6\nDHCP\nClient\n1 Introduction\nHost computer\n(FTP server)\nEthernet\nFile data Built-in EtherNet/IP Port\nNJ/NX-series\nController\nSD Memory\nCard\nDownloading Data Uploading Data\nFile data File data\nSD Memory SD Memory\nCard Card\n1-4-9 Automatic Clock Adjustment\nWith the built-in EtherNet/IP port, clock information is read from the NTP server at the specified time or\nat a specified interval after the power supply to the CPU Unit is turned ON. The internal clock time in\nthe CPU Unit is updated with the read time.\nNTP server\nNTP command\nEthernet\nClock information\nBuilt-in EtherNet/IP port\nNJ/NX-series\nController\nPrecautions for Correct Use\nAn NTP server is required to use automatic clock adjustment.\n1-4-10 Socket Service\nYou can send data to and receive data from any node on Ethernet with the UDP or TCP protocol.\nTo send/receive data with a socket service, you execute multiple socket communications instructions\nin sequence in an ST program to execute the required communications processes.\nAfter a connection with the other communications device is opened with an open instruction, the val-\nues of the variables that are specified for the send instruction are sent and the data that was received\nfor a receive instruction is stored in the specified variables.\nThe connection is closed with a close instruction, and communications end.\nFor TCP, you can also read the socket status and received data.\n1-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nYou can use a total of 30 TCP ports and UDP ports. (A total of 60 ports for NX502 and NX102 CPU\nUnits)\nEthernet\nCommunications processes are\nperformed with socket commu-\nnications instructions (for UDP).\nOpen processing\nSend processing\nReceive processing\nClose processing\ntekcoS\nUNIX computer or\nother node with socket\nservice interfaces\nBuilt-in EtherNet/IP port\nTCP/UDP\nprotocol\nNJ/NX-series CPU Unit\nST Programming\nTCP/UDP\nprotocol\nBuilt-in EtherNet/IP port\nPI\nPCT\nPDU\n1 Introduction\nSktUDPCreate(...)\nSktUDPSend(...)\nSktUDPRcv(...)\nSktClose(...)\nNJ/NX-series CPU Unit\n1-4-11 Secure Socket Services\nThe secure socket services allow the built-in EtherNet/IP port on the CPU Unit to act as a client, ena-\nbling secure socket communications with the on-premises server on the private network or with the\ncloud server on the external network.\nThis function performs encrypted communications using TLS, which use client private keys and certifi-\ncates, and enables safe communications.\nCloud\nserver\nInternet\nIP router\nFirewall\nOn-premises\nserver\nEthernet (EtherNet/IP)\nController\nBuilt-in EtherNet/IP port\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-27\ntions\nServices\n1-4\nIntroduction\nto\nCommunica-\n1\n1-4-11\nSecure\nSocket\nServices\n1 Introduction\n1-4-12 Specifying Host Names\nYou can directly specify IP addresses, but you can also use the host names instead of the IP address-\nes for NTP servers, SNMP managers, or the destinations of socket instructions and CIP\ncommunications instructions (DNS client or hosts settings).\nExample: Setting Host Names on the DNS Server\nDNS server\nIP address Ethernet\nHost name\nBuilt-in EtherNet/IP port\nNJ/NX-series\nController\nPrecautions for Correct Use\n• A DNS server is required to use the server host names for the DNS client.\n1-4-13 SNMP Agent\nThe SNMP agent has the following functions.\nSNMP Agent\nThe SNMP agent passes internal status information from the built-in EtherNet/IP port to network man-\nagement software that uses an SNMP manager.\nMonitors devices on Ethernet/IP\nSNMP\nmanager\nBuilt-in EtherNet/IP port\nEthernet\nSNMP message\nManagement\ninformation Device that supports SNMP\nSNMP agent SNMP agent SNMP agent\n1-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\nSNMP Trap\nWhen specific conditions occur, the built-in EtherNet/IP port that is set as the SNMP agent sends sta-\ntus notification reports to the SNMP manager.\nThe SNMP manager can learn about changes in status even without periodically monitoring the built-\nin EtherNet/IP port.\nStatus notification reports are sent under the following conditions.\n• When the Controller is turned ON\n• When links are established\n• When an SNMP agent fails to be authorized\nSNMP manager\nController power\nTrap is turned ON.\nBuilt-in EtherNet/IP port\nSNMP agent\n1-4-14 TCP/UDP Message Service\nThis function supports TCP/UDP socket communications, which allow simple access to CIP objects of\nthe Controller from a system where EtherNet/IP is not supported. This will allow you to change settings\nand perform I/O control for NX Units connected to the Controller or the NX bus.\nYou can use the TCP/UDP message service only for the NX502 CPU Units and NX102 CPU Units.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-29\ntions\nServices\n1-4\nIntroduction\nto\nCommunica-\n1\n1-4-14\nTCP/UDP\nMessage\nService\n1 Introduction\n1-5 EtherNet/IP Communications Proce-\ndures\n Basic Operation\n1 Wire the Ethernet network with twisted-pair cable. Section 2 Installing Ethernet Net-\nworks on page 2-1\n↓\n2 Set the built-in EtherNet/IP port IP address with the Sysmac 5-1 Determining IP Addresses on\nStudio. page 5-2"}
+{"question": "Set the local IP address in one of the following ways:", "answer": "• Defaults:\nNX701 CPU Unit\nBuilt-in EtherNet/IP port 1 : 192.168.250.1\n(subnet mask = 255.255.255.0)\nBuilt-in EtherNet/IP port 2 : 192.168.251.1\n(subnet mask = 255.255.255.0)\nNX502 CPU Unit\nBuilt-in EtherNet/IP port 1 : 192.168.250.1\n(subnet mask = 255.255.255.0)\nBuilt-in EtherNet/IP port 2 : 192.168.251.1\n(subnet mask = 255.255.255.0)\nNX102 CPU Unit\nBuilt-in EtherNet/IP port 1 : 192.168.250.1\n(subnet mask = 255.255.255.0)\nBuilt-in EtherNet/IP port 2 : 192.168.251.1\n(subnet mask = 255.255.255.0)\nNX1P2 CPU Unit Built-in EtherNet/IP port : 192.168.250.1\nNJ-series CPU Unit Built-in EtherNet/IP port (subnet mask = 255.255.255.0)\n• Set any IP address.\n• Obtain from the BOOTP server.\n• Obtain from the DHCP server (this can be set only for the NX502 CPU Units).\n↓\n3 Perform a communications test with a PING command from a 5-3 Testing Communications on\ncomputer. page 5-18\n↓\n4 Use the Sysmac Studio to set the initial settings of the Ether- Section 4 Sysmac Studio Set-\nNet/IP Function Module. tings for the Built-in EtherNet/IP\nPort on page 4-1\n• Set the TCP/IP settings and Ethernet settings as required.\n Using Tag Data Links\n1 Import the variable settings for the tags that were created on 6-2-4 Creating Tags and Tag Sets\nthe Sysmac Studio to the Network Configurator. on page 6-25\n↓\n2 Use the Network Configurator to create the tag data link table. Section 6 Tag Data Link Func-\ntions on page 6-1\n1-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n1 Introduction\n• Create the network configuration.\n• Set the tags, tag sets, and connections.\n↓\n3 Connect the Network Configurator online.\n↓\n4 Download the tag data link setting.\n↓\n5 Start the tag data links (the links starts automatically when\npower is turned ON).\n↓\n6 Check operation. 1-3-2 Part Names and Functions\non page 1-13\nSection 15 Troubleshooting on\npage 15-1\n• Check the built-in EtherNet/IP port indicators.\n• Use the Sysmac Studio to check the communications status\nwith the All Tag Data Link Communications Status system-de-\nfined variable.\n• Use the monitor function of the Network Configurator to con-\nfirm that the tag data links are in normal operation.\n Using the Message Communications Service\n• CIP Communications Instructions\n1 Execute CIP communications instructions in the user program. Section 7 CIP Message Commu-\nnications on page 7-1\n↓\n2 Check operation. 1-3-2 Part Names and Functions\non page 1-13\nSection 15 Troubleshooting on\npage 15-1\n• Use the Sysmac Studio to check the communications status\nwith the end codes of the instructions (Done, Err, and ErrID).\n Using the Socket Services\n1 Execute the socket service instructions in the user program. Section 8 Socket Service on\npage 8-1\n↓\n2 Check operation.\n• Use the Sysmac Studio to check the communications status\nwith the end codes of the instructions (Done, Err, and Error-\nID).\n Using the FTP Server\n1 Use the Sysmac Studio to set the initial settings of the Ether- Section 10 FTP Server on page\nNet/IP Function Module. 10-1\n• Set the FTP settings (enabling FTP, login name, and pass-\nword).\n↓\n2 Connect to the FTP server in the NJ-series CPU Unit from an\nFTP client application.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 1-31\nProcedures\n1-5\nEtherNet/IP\nCommunications\n1\n1 Introduction\n• Input the FTP login name and password to log onto the built-\nin EtherNet/IP port.\n• Check the event log to see if the FTP server started.\n Using the Automatic Clock Adjustment\n1 Use the Sysmac Studio to set the initial settings of the Ether- Section 12 Automatic Clock Ad-\nNet/IP Function Module. justment on page 12-1\n• Set the NTP settings (enabling NTP and execution condi-\ntions).\n↓\n2 Execute automatic clock adjustment.\n• Execute automatic adjustment at specified times or specified\nintervals.\n• Use the Sysmac Studio to check the NTP Last Operation\nTime and NTP Operation Result system-defined variables.\n• Check the event log to see if the NTP client started.\n Using the SNMP Agent\n1 Use the Sysmac Studio to set the initial settings of the Ether- Section 13 SNMP Agent on page\nNet/IP Function Module. 13-1\n• Set the SNMP settings.\n• Set the SNMP trap settings.\n↓\n2 Check operation.\n• Check the event log to see if the SNMP agent started.\n Using BOOTP\n1 Use the Sysmac Studio to set the initial settings of the Ether- Section 4 Sysmac Studio Set-\nNet/IP Function Module. tings for the Built-in EtherNet/IP\nPort on page 4-1\n• Set the BOOTP settings.\n↓\n2 Check operation.\n• Check the event log to see if BOOTP started.\n• Check the Online system-defined variable.\n1-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2\nInstalling Ethernet Networks\n2-1 Selecting the Network Devices.....................................................................2-2\n2-1-1 Recommended Network Devices....................................................................2-2\n2-1-2 Ethernet Switch Types.....................................................................................2-3\n2-1-3 Ethernet Switch Functions...............................................................................2-3\n2-1-4 Precautions for Ethernet Switch Selection......................................................2-4\n2-2 Network Installation.......................................................................................2-7\n2-2-1 Basic Installation Precautions.........................................................................2-7\n2-2-2 Recommended Network Devices....................................................................2-7\n2-2-3 Precautions When Laying Twisted-pair Cable.................................................2-7\n2-2-4 Precautions When Installing and Connecting Ethernet Switches...................2-11\n2-3 Connecting to the Network..........................................................................2-13\n2-3-1 Ethernet Connectors.....................................................................................2-13\n2-3-2 Connecting the Cable....................................................................................2-14\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-1\n2\n2 Installing Ethernet Networks\n2-1 Selecting the Network Devices\n2-1-1 Recommended Network Devices\nThe following table shows the devices recommended for use with the EtherNet/IP.\n Ethernet Switches\nManufacturer Model Description\nOMRON W4S1-05D Packet priority control (QoS): EtherNet/IP control data priority\nEthernet standard: IEEE 802.3 10Base-T, 100Base-TX\nAuto-negotiation: Supported\nBroadcast storm detection function: Supported\nNumber of ports: 5\nCisco Systems, Consult the manufacturer.\nInc. http://www.cisco.com/\nContec USA, Consult the manufacturer.\nInc. http://www.contec.com/\nPhoenix Con- Consult the manufacturer.\ntact USA https://www.phoenixcontact.com\n Twisted-pair Cables and Connectors\nApplicable EtherNet/IP communications cables and connectors vary depending on the used baud\nrate.\nFor 100Base-TX and 10Base-T, use an STP (shielded twisted-pair) cable of category 5 or higher.\nYou can use either straight or cross cable.\nFor 1000Base-T, use an STP (shielded twisted-pair) cable (double shielding with aluminum tape\nand braiding) of category 5e or higher. You can use either straight or cross cable.\nCabling materials used for EtherNet/IP communication cables are shown in the table below.\n\"100Base-TX\" in the \"Product\" column of the table below indicates that either 100Base-TX or\n10Base-T can be used.\nProduct Manufacturer Model\nFor 1000Base-T Size and con- Cable Hitachi Metals, Ltd. NETSTAR-C5E\nand 100Base- ductor pairs: SAB 0.5 × 4P CP\nTX AWG24 × 4 Kuramo Electric Co. KETH-SB\npairs\nJMACS Japan Co., Ltd. IETP-SB\n*1\nRJ45 Connec- Panduit Corporation MPS588\ntors\nFor 100Base- Size and con- Cable Kuramo Electric Co., Ltd. KETH-PSB-OMR\nTX ductor pairs: JMACS Japan Co., Ltd. PNET/B\nAWG22 × 2\nRJ45 Assembly OMRON XS6G-T421-1\npairs*1 Connectors\n*1. We recommend that you use cables and connectors in above combinations.\n2-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2 Installing Ethernet Networks\n2-1-2 Ethernet Switch Types\n Unmanaged Layer 2 (L2) Ethernet Switches\nThese Ethernet switches use the Ethernet MAC address to switch ports. Ordinary Ethernet\nswitches have this function. Ethernet switch functions and settings cannot be changed.\n Managed Layer 2 (L2) Ethernet Switches\nThese Ethernet switches use the Ethernet MAC address to switch ports. Ethernet switch functions\nand settings can be changed with special software tools for Ethernet switches running on a network\nnode. You can also collect analytical data. These Ethernet switches provide more-advanced func-\ntions than unmanaged layer 2 Ethernet switches.\n2-1-3 Ethernet Switch Functions\nThis section describes the Ethernet switch functions that are important for an EtherNet/IP network. For\na built-in EtherNet/IP port, consider whether the Ethernet switch supports these functions when you\nselect the Ethernet switch.\n• Multicast filtering\n• QoS (Quality of Service) for TCP/UDP port numbers (L4)\n Multicast Filtering\nMulticast filtering transfers multicast packets to the specific nodes only. This function is implement-\ned in the Ethernet switch as IGMP snooping or GMRP.\n“Specific nodes” are nodes equipped with an IGMP client, and have made transfer requests to the\nEthernet switch. (OMRON built-in EtherNet/IP ports are equipped with an IGMP client.) When the\nEthernet switch does not use multicast filtering, multicast packets are sent to all nodes, just like\nbroadcast packets, which increases the traffic in the network.\nSettings must be made in the Ethernet switch to enable this function. There must be enough multi-\ncast filters for the network.\n QoS (Quality of Service) Function for TCP/UDP Port Numbers (L4)\nThis function controls the priority of packet transmissions so that packets can be sent with higher\npriority to a specific IP address or TCP (UDP) port. The TCP and UDP protocols are called trans-\nport layer protocols, leading to the name L4 (layer 4) QoS function.\nWhen tag data links and message communications are executed on the same network, tag data\nlinks can be sent at higher priority to prevent problems such as transmission delays due to mes-\nsage communications traffic and packet losses due to buffer overflow.\nSettings must be made in the Ethernet switch to enable QoS function and give higher priority to tag\ndata link packets.\nThese functions are supported by Ethernet switches as described in the table below.\nEthernet switch type Multicast filtering L4 QoS Remarks\nUnmanaged L2 Ethernet switch Not supported Not sup- ---\nported\nManaged L2 Ethernet switch Supported Supported Both functions must be set\nwith a special software tool.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-3\n2-1\nSelecting\nthe\nNetwork\nDevices\n2\n2-1-2\nEthernet\nSwitch\nTypes\n2 Installing Ethernet Networks\nEthernet switch type Multicast filtering L4 QoS Remarks\nOMRON Ethernet switch Not supported Supported L4 QoS is set with a switch.\n(W4S1-series Ethernet switches) No software tool is necessa-\nry. QoS (Quality of Service)\nFunction for TCP/UDP Port\nNumbers (L4) on page 2-3\nAdditional Information\nIf you select Multicast Connection for the connection type in the connection settings on the\nNetwork Configurator, multicast packets are used. If the connection type is set to a Point to\nPoint Connection, multicast packets are not used.\n2-1-4 Precautions for Ethernet Switch Selection\nThe functions supported by the Ethernet switch may affect tag data link transmission delays and the\nsettings in the Controller configurations and setup.\nIn addition, if the Ethernet switch supports advanced functions, special settings are required for the\nfunctions.\nWhen you select an Ethernet switch, it is necessary to consider what kind of data transmission and\nhow much traffic you use over the the network.\nRefer to the following precautions when you select an Ethernet switch.\nRefer to 14-2 Adjusting the Communications Load on page 14-7 to estimate the communications\nload for tag data links.\nSelecting the Ethernet Switch Based on the Type of Network Com-\nmunications\n Executing Tag Data Links Only\nWe recommend that you use an L2 Ethernet switch without multicast filtering or an L2 Ethernet\nswitch with multicast filtering.\nAn L2 Ethernet switch with multicast filtering prevents increased traffic due to unnecessary multi-\ncast packets, so the tag data links can operate at higher speed.\nIf either of the following conditions exists, there is no difference in the traffic condition whether mul-\nticast filtering is supported or not.\n• The tag data links are set to share the same data with all nodes in the network. (Multicast pack-\nets are transferred to all nodes in the network, just like broadcast transmission.)\n• The tag data link settings are all one-to-one (unicast) and multicast packets are not used.\nWhen multicast filtering is used, settings must be made accordingly on the Ethernet switch. There\nmust be enough multicast filters for the network.\n Executing Tag Data Links and Message Communications\nWe recommend an L2 Ethernet switch with multicast filtering and L4 QoS.\nIf you set tag data links for higher-priority transmission, it is possible to prevent problems such as\ntransmission delays due to message communications traffic and packet losses due to buffer over-\nflow.\nWhen multicast filtering and L4 QoS are used, settings must be made accordingly on the Ethernet\nswitch.\n2-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2 Installing Ethernet Networks\nSelecting the Ethernet Switch Based on the Ethernet Switch's Sup-\nported Functions\n L2 Ethernet Switch without Multicast Filtering\nWe recommend this kind of Ethernet switch when only tag data links are executed and any of the\nfollowing conditions is met.\n• The tag data links are set to share the same data with all nodes in the network. (Multicast pack-\nets are transferred to all nodes in the network, just like broadcast transmission.)\n• The tag data link settings are all one-to-one (unicast) and multicast packets are not used.\n• There is little traffic in the tag data links.\nNo special settings are required for an L2 Ethernet switch without multicast filtering.\n L2 Ethernet Switch with Multicast Filtering\nWe recommend this kind of Ethernet switch when only tag data links are executed and the follow-\ning condition is met.\n• There are many 1:N links (where N represents some number of nodes in the network) in the tag\ndata link settings, i.e., there are many multicast packets used, or there is heavy traffic in the tag\ndata links.\nSpecific settings are required for an L2 Ethernet switch with multicast filtering. There must be\nenough multicast filters for the network.\n L3 Ethernet Switch with Multicast Filtering and L4 QoS Functions\nWe recommend this kind of Ethernet switch when both tag data links and message communica-\ntions are executed.\nIf you set tag data links for higher-priority transmission, you can prevent problems such as trans-\nmission delays due to message communications traffic and packet losses due to buffer overflow.\nWhen multicast filtering and L4 QoS are used, settings must be made accordingly on the Ethernet\nswitch. There must be enough multicast filters for the network.\nSelecting the Ethernet Switch Based on the Network Communica-\ntion Speed\n Executing Tag Data Links at a Baud Rate Over 100 Mbps\nIf you use data tag links with the following conditions, use an Ethernet switch with multicast filtering\nor an Ethernet switch that supports a baud rate of 1,000 Mbps.\n• Multicast\n• Baud rate over 100 Mbps\nIf there is an Ethernet device on the same network that communicates at a speed of 100 Mbps or\nless, the device may affect tag data link communications and cause tag data links to be broken,\neven if the device is not related to tag data link communications.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-5\n2-1\nSelecting\nthe\nNetwork\nDevices\n2\n2-1-4\nPrecautions\nfor\nEthernet\nSwitch\nSelection\n2 Installing Ethernet Networks\nPrecautions for Correct Use\n• Ask the Ethernet switch manufacturer for setting procedures for the Ethernet switch.\n• Install the Ethernet switch based on its environmental resistance specifications so that the\nenvironmental resistance specifications are fully met. Ask the Ethernet switch manufacturer\nfor information on the environmental resistance of the Ethernet switch.\n2-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2 Installing Ethernet Networks\n2-2 Network Installation\n2-2-1 Basic Installation Precautions\n• Take the greatest care when you install the Ethernet System. Be sure to follow ISO 8802-3 specifi-\ncations. Be sure you understand them before attempting to install an Ethernet System.\n• Unless you are already experienced in installation of communications systems, we strongly recom-\nmend that you employ a professional to install your system.\n• Do not install Ethernet equipment near sources of noise.\nIf a noisy environment is unavoidable, take adequate measures against noise interference, such as\ninstallation of network components in metal cases or the use of optical cable in the system.\n• When using a shielded cable with the shields on both ends of the cable connected to connector\nhoods, ground loops induced by improper grounding methods may decrease noise immunity and\ncause device damage. To prevent ground loops caused by differences in potential between device\ngrounding points, the reference potential between the devices must be stabilized. Design grounding\nappropriately so that noise current does not flow to ground lines between the devices.\nFor grounding methods, refer to the NJ-series CPU Unit Hardware User's Manual (Cat. No. W500),\nNX-series CPU Unit Hardware User’s Manual (Cat. No. W535), NX-series NX502 CPU Unit\nHardware User’s Manual (Cat. No. W629), NX-series NX102 CPU Unit Hardware User’s Manual\n(Cat. No. W593), or NX-series NX1P2 CPU Unit Hardware User’s Manual (Cat. No. W578).\n• To obtain information on installing EtherNet/IP cable, contact ODVA.\nODVA web site: http://www.odva.org\n• When you install an EtherNet/IP network that combines an information network with the control sys-\ntem, and the communications load may be heavy due to tag data links, we recommend that you set\nup a network where the load does not affect communications. For example, install the tag data links\nin a segment that is separate from the information network.\n2-2-2 Recommended Network Devices\nRefer to 2-1 Selecting the Network Devices on page 2-2 for the devices recommended for use with the\nbuilt-in EtherNet/IP port.\n2-2-3 Precautions When Laying Twisted-pair Cable\nConnecting the Shield to Connector Hoods\n Between an EtherNet/IP Port and an Ethernet Switch\nConnect the shield to connector hoods as described below.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-7\n2-2\nNetwork\nInstallation\n2\n2-2-1\nBasic\nInstallation\nPrecautions\n2 Installing Ethernet Networks\nNJ-series CPU Unit NX-series CPU Unit\n1000Base-T\n10Base-T 100Base-TX 10Base-T 100Base-TX\n*1\n• Connect the shield at both ends • Connect the shield at both ends Connect the shield\nor or at both ends\n• Connect the shield only at the Ethernet • Connect the shield only at the Ethernet\nswitch side switch side. A clamp core must be at-\ntached to the EtherNet/IP port side of\nthe cable.\n*1. For NX701 CPU Units and NX502 CPU Units only.\n• 10Base-T or 100Base-TX\nConnect the cable shields to the connector hoods as described in either (1) or (2) below."}
+{"question": "Connecting the shields at both ends of the cable", "answer": "Connect the shields to the connector hoods at both ends of the cables.\nEthernet switch\nConnect shield to connector hood\nConnector Connector Connector\nGR\nterminal\nBuilt-in EtherNet/IP port Power Supply\non NX-series CPU Unit Unit\nSTP Connector\n(Shield) GR\nterminal\nBuilt-in EtherNet/IP port Power Supply\non NJ-series CPU Unit Unit\nSTP Connector\n(Shield) GR\nterminal"}
+{"question": "Connecting the shields only at the Ethernet switch side", "answer": "Connect the shields to the connector hoods only at the Ethernet switch side.\n• For an NX-series CPU Unit, a clamp core must be attached to the end of the cable at the\nEtherNet/IP port side. For a recommended clamp core and attachment methods, refer to\nRecommended Clamp Core and Attachment Method on page 2-10.\nTo comply with EMC standards, it is mandatory that a clamp core be attached when con-\nnecting the shield to the connector hood only at the Ethernet switch side.\n• For an NJ-series CPU Unit, it is not necessary to attach a clamp core.\n2-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2 Installing Ethernet Networks\nEthernet switch\nConnect shield to connector hood\nConnector Connector Connector Do not connect shield to connector hood\nGR\nterminal\nBuilt-in EtherNet/IP Power Supply\nport on NX-series Unit\nCPU Unit\nClamp core\nSTP Connector\n(Shield) GR\nterminal\nBuilt-in EtherNet/IP Power Supply\nport on NJ-series Unit\nCPU Unit\nSTP Connector\n(Shield) GR\nterminal\nAdditional Information\nNoise immunity may be reduced and device damage may occur due to ground loops, which\nmay be caused by improper shield connections and grounding methods.\nWhen using a baud rate of 100 Mbps or less, it may be possible to alleviate this problem by\nconnecting the shield only at the Ethernet switch side as described in (2), rather than connect-\ning both ends as described in (1).\n• 1000Base-T\nConnect the shields to respective connector hoods at both ends of the cables.\nThis connection is required for 1000Base-T to ensure compliance with EMC standards.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-9\n2-2\nNetwork\nInstallation\n2\n2-2-3\nPrecautions\nWhen\nLaying\nTwisted-pair\nCable\n2 Installing Ethernet Networks\nEthernet switch\nConnect shield to connector hood\nGR Connector Connector Connector\nterminal\nBuilt-in EtherNet/IP Power Supply\nport on NX-series Unit\nCPU Unit\nSTP Connector\n(Shield) GR\nterminal\nBuilt-in EtherNet/IP Power Supply\nport on NX-series Unit\nCPU Unit\nSTP Connector\n(Shield) GR\nterminal\n Between Two Ethernet Switches\nRegardless of which baud rate is used, check with the Ethernet switch manufacturers for informa-\ntion about installing the network between Ethernet switches, and in particular whether or not it is\nnecessary to connect the cable shields to the connector hoods.\nOther Precautions When Laying the Twisted-pair Cable\n• Firmly insert the connector until it locks into place when you connect the cable to the Ethernet switch\nand the built-in EtherNet/IP port.\n• Do not install the twisted-pair cable together with high-voltage lines.\n• Do not install the twisted-pair cable near devices that generate noise.\n• Do not install the twisted-pair cable in locations subject to high temperatures or high humidity.\n• Do not install the twisted-pair cable in locations subject to excessive dirt, dust, oil mist or other con-\ntaminants.\nRecommended Clamp Core and Attachment Method\nWhen you use an NX-series CPU Unit and connect the cable shield only with the connector hood of\nthe Ethernet switch, you need to attach a clamp core to the EtherNet/IP port of the CPU Unit.\nThe recommended clamp core and attachment method are given below.\n Recommended Clamp Core\nManufacturer Product Model\nNEC TOKIN Clamp core ESD-SR-250\nESD-SR-250 dimensions\n2-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)"}
+{"question": "13", "answer": "2 Installing Ethernet Networks\n13 dia. max.\n Recommended Attachment Method\n• Attach a clamp core to the communications cable as shown below.\nMake two loops with the cable\nas shown.\n• Connect the communications cable as shown below.\nBuilt-in\nEtherNet/IP\nAttach close to the cable\nport on\nNX-series connection as shown.\nController\n2-2-4 Precautions When Installing and Connecting Ethernet Switches\nPrecautions When Installing Ethernet Switches\n• Do not ground the Ethernet switch in the same location as a drive-system component, such as an\ninverter.\n• Always use a dedicated power supply for the Ethernet switch. Do not use the same power supply for\nother equipment, such as an I/O power supply, motor power supply, or control power supply.\n• Before installation, check the Ethernet switch's environmental resistance specifications, and use an\nEthernet switch that is appropriate for the ambient conditions. Contact the Ethernet switch manufac-\nturer for details on Ethernet switch's environmental resistance specifications.\nEthernet Switch Connection Methods\n• Connect Ethernet switches with twisted-pair cables, as follows: Connect an MDI port to an MDI-X\nport with a straight cable. Connect two MDI ports or two MDI-X ports with a cross cable.\nNoteIt is very difficult to distinguish cross cables and straight cables by appearance. Incorrect cables will\ncause communications to fail. We recommend cascade connections with straight cables wherever possi-\nble.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-11\n2-2\nNetwork\nInstallation\n2\n2-2-4\nPrecautions\nWhen\nInstalling\nand\nConnecting\nEthernet\nSwitches\n2 Installing Ethernet Networks\nMDI ports\n: Straight cable\nMDI-X port (cross)\nEthernet switch\n: Cross cable\nEthernet Ethernet Ethernet\nswitch switch switch\n• Some Ethernet switches can automatically distinguish between MDI and MDI-X. When this kind of\nEthernet switch is used, straight cable can be used between Ethernet switches.\nPrecautions for Correct Use\nAdjust the built-in EtherNet/IP port's link settings to match the communications mode settings of\nthe connected Ethernet switch. If the settings do not match, the link will be unstable and prevent\nnormal communications. The following table shows the allowed settings for each Ethernet\nswitch communications mode.\n(Auto-Nego: Auto negotiation, Full: Full duplex, Half: Half duplex)\nBuilt-in EtherNet/IP port\n1,000 Mbps\nEthernet switch Auto- 10 Mbps (fixed) 100 Mbps (fixed)\n(fixed)\nNego\nFull Half Full Half Full\nAuto-Nego Best --- OK --- OK ---\n10 Mbps Full --- OK --- --- --- ---\n(fixed) Half OK --- OK --- --- ---\n100 Mbps Full --- --- --- OK --- ---\n(fixed) Half OK --- --- --- OK ---\n1,000 Mbps Full --- --- --- --- --- Best\n(fixed)\nBest = Recommended; OK = Allowed; --- = Not allowed.\n2-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n2 Installing Ethernet Networks\n2-3 Connecting to the Network\n2-3-1 Ethernet Connectors\nThe following standards and specifications apply to the connectors for the Ethernet twisted-pair cable.\n• Electrical specifications: Conforming to IEEE 802.3 standards.\n• Connector structure: RJ45 8-pin Modular Connector (conforming to ISO 8877)\n• For information on connecting shield wire to connector hoods, refer to 2-1-2 Ethernet Switch Types\non page 2-3.\n10Base-T and 100Base-TX\nConnector pin Signal name Abbr. Signal direction\n1 Transmission data + TD+ Output\n2 Transmission data − TD− Output\n3 Reception data + RD+ Input\n4 Not used --- ---\n5 Not used --- ---\n6 Reception data − RD− Input\n7 Not used --- ---\n8 Not used --- ---\n1000Base-T\nConnector pin Signal name Abbr. Signal direction\n1 Communication data DA+ BI_DA+ Input/output\n2 Communication data DA− BI_DA- Input/output\n3 Communication data DB+ BI_DB+ Input/output\n4 Communication data DC+ BI_DC+ Input/output\n5 Communication data DC− BI_DC− Input/output\n6 Communication data DB− BI_DB− Input/output\n7 Communication data DD+ BI_DD+ Input/output\n8 Communication data DD− BI_DD− Input/output\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 2-13\n2-3\nConnecting\nto\nthe\nNetwork\n2\n2-3-1\nEthernet\nConnectors\n2 Installing Ethernet Networks\n2-3-2 Connecting the Cable\nPrecautions for Correct Use\n• Turn OFF the Controller's power supply before connecting or disconnecting Ethernet commu-\nnications cable.\n• Allow extra space for the bending radius of the communications cable.\nFor the CPU Unit dimensions when the communications cable is connected to the Unit, refer\nto the NJ-series CPU Unit Hardware User's Manual (Cat. No. W500), NX-series CPU Unit\nHardware User’s Manual (Cat. No. W535), NX-series NX502 CPU Unit Hardware User’s\nManual (Cat. No. W629), NX-series NX102 CPU Unit Hardware User’s Manual (Cat. No.\nW593), or NX-series NX1P2 CPU Unit Hardware User’s Manual (Cat. No. W578). The re-\nquired space depends on the communications cable and connector that are used. Consult\nthe manufacturer or sales agent.\n1\nInstall the twisted-pair cable.\n2\nConnect the cable to the Ethernet switch.\n3\nConnect the twisted-pair cable to the connector on the built-in EtherNet/IP port.\nBe sure to press the connectors (both the Ethernet switch side and Ethernet side) until they\nlock into place.\n2-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3\nSystem-defined Variables Related\nto the Built-in EtherNet/IP Port\n3-1 System-defined Variables Related to the Built-in EtherNet/IP Port...........3-2\n3-2 System-defined Variables..............................................................................3-3\n3-2-1 EtherNet/IP Function Module, Category Name: _EIP.....................................3-3\n3-2-2 Meanings of Error Status Bits........................................................................3-37\n3-3 Specifications for Individual System-defined Variables...........................3-39\n3-3-1 EtherNet/IP Function Module, Category Name: _EIP...................................3-39\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-1\n3\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n3-1 System-defined Variables Related to\nthe Built-in EtherNet/IP Port\nYou can use the system-defined variables that are provided for the built-in EtherNet/IP port in pro-\ngrams to check the status of the built-in EtherNet/IP port.\n Checking for Errors in the Built-in EtherNet/IP Port\nYou can check for built-in EtherNet/IP port errors, Sysmac Studio setting errors, Network Configu-\nrator setting errors, TCP/IP application errors (e.g., FTP or NTP), etc.\nThe following hierarchy is used. The system gives the error status at each level by logically ORing\nthe error status information in the next lower level.\n_EIP_ErrSta Error status variable for EtherNet/IP Function Module\nError status variable for\n_EIP_PortErr*1\ncommunications port\n_EIP_MacAdrErr*1 MAC Address Error\n_EIP_LanHwErr*1 Communications Controller Error\n_EIP_IPAdrDupErr*1 IP Address Duplication Error\n_EIP_EtnCfgErr*1 Basic Ethernet Setting Error\n_EIP_IPAdrCfgErr*1 IP Address Setting Error\n_EIP_IPRTblErr IP Route Table Error\n_EIP_BootpErr*1 BOOTP Server Error\n_EIP_DNSSrvErr DNS Server Connection Error\n_EIP_DNSCfgErr*2 DNS Setting Error\nError status variable for\n_EIP_CipErr*1\nCIP communications\n_EIP_IdentityErr*1 Identity Error\n_EIP_TDLinkCfgErr*1 Tag Data Link Setting Error\n_EIP_TDLinkOpnErr*1 Tag Data Link Connection Failed\n_EIP_TDLinkErr*1 Tag Data Link Communications Error\n_EIP_MultiSwONErr*1 Multiple Switches ON Error\n_EIP_TagAdrErr*1 Tag Name Resolution Error\nError status variable for\n_EIP_TcpAppErr\nTCP/IP application function\n_EIP_TcpAppCfgErr TCP Application Setting Error\n_EIP_NTPSrvErr NTP Server Connection Error\n*1. Error status variables for errors related to NX-series CPU Units are provided individually for communica-\ntions port 1 and communications port 2. You can use error status variables for communications port 2 with\nthe NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units only.\nRefer to Hierarchical Relationship of System-defined Variables Related to EtherNet/IP Errors in the NX-\nseries CPU Unit page 3-21 for details.\n*2. With the NJ-series CPU Unit, this variable can be used with the unit version 1.11 or later.\n3-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n3-2 System-defined Variables\nThe variables are described in the tables as shown below.\nRange of\nVariable name Meaning Function Data type Reference\nvalues\nThis is the system- This is the mean- The function of the variable is descri- The data The range The page of\ndefined variable ing of the variable. bed. type of the of values the individ-\nname. The prefix variable is that the var- ual system-\ngives the category given. iable can defined var-\nname. take is giv- iable speci-\nen. fications ta-\nble is given.\n3-2-1 EtherNet/IP Function Module, Category Name: _EIP\n Functional Classification: EtherNet/IP Communications Errors\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_ErrSta EtherNet/IP Error This is the error status variable for the WORD 16#0000 to page 3-39\nbuilt-in EtherNet/IP port. 16#00F0\nNX-series CPU Units: Represents the\ncollective status of the following error\nflags.\n• _EIP1_PortErr (Communications Port1\nError)\n• _EIP2_PortErr (Communications Port2\nError)\n• _EIP1_CipErr (CIP Communications1\nError)\n• _EIP2_CipErr (CIP Communications2\nError)\n• _EIP_TcpAppErr (TCP Application\nCommunications Error)\nNJ-series CPU Units: Represents the col-\nlective status of the following error flags.\n• _EIP_PortErr (Communications Port\nError)\n• _EIP_CipErr (CIP Communications Er-\nror)\n• _EIP_TcpAppErr (TCP Application\nCommunications Error)\nNoteRefer to Meanings of Error\nStatus Bits for the meanings of\nthe error status bits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-3\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_PortErr Communications Port This is the error status variable for the WORD 16#0000 to page 3-40\nError communications port. 16#00F0\nNX-series CPU Units: Represents the\ncollective status of the following error\nflags.\n• _EIP1_MacAdrErr (Port1 MAC Ad-\ndress Error)\n• _EIP1_LanHwErr (Port1 Communica-\ntions Controller Error)\n• _EIP1_EtnCfgErr (Port1 Basic Ether-\nnet Setting Error)\n• _EIP1_IPAdrCfgErr (Port1 IP Address\nSetting Error)\n• _EIP1_IPAdrDupErr (Port1 IP Address\nDuplication Error)\n• _EIP1_BootpErr (Port1 BOOTP Serv-\ner Error)\n• _EIP1_DhcpErr (Port1 DHCP Server\nError)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Con-\nnection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNJ-series CPU Units: Represents the col-\nlective status of the following error flags.\n• _EIP_MacAdrErr (MAC Address Error)\n• _EIP_LanHwErr (Communications\nController Error)\n• _EIP_EtnCfgErr (Basic Ethernet Set-\nting Error)\n• _EIP_IPAdrCfgErr (IP Address Setting\nError)\n• _EIP_IPAdrDupErr (IP Address Dupli-\ncation Error)\n• _EIP_BootpErr (BOOTP Server Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or\nEtherNet/IP Error occurs, it is\nrecorded in the event log and\nthen the corresponding bit\nturns ON.\nRefer to Meanings of Error\nStatus Bits for the meanings of\nthe error status bits.\n3-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_PortErr Communications This is the error status variable for the WORD 16#0000 to page 3-40\nPort1 Error communications port 1. 16#00F0\nRepresents the collective status of the\nfollowing error flags.\n• _EIP1_MacAdrErr (Port1 MAC Ad-\ndress Error)\n• _EIP1_LanHwErr (Port1 Communica-\ntions Controller Error)\n• _EIP1_EtnCfgErr (Port1 Basic Ether-\nnet Setting Error)\n• _EIP1_IPAdrCfgErr (Port1 IP Address\nSetting Error)\n• _EIP1_IPAdrDupErr (Port1 IP Address\nDuplication Error)\n• _EIP1_BootpErr (Port1 BOOTP Serv-\ner Error)\n• _EIP1_DhcpErr (Port1 DHCP Server\nError)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Con-\nnection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or\nEtherNet/IP Error occurs, it is\nrecorded in the event log and\nthen the corresponding bit\nturns ON.\nRefer to Meanings of Error\nStatus Bits for the meanings of\nthe error status bits.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-5\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_PortErr Communications This is the error status variable for the WORD 16#0000 to page 3-41\nPort2 Error communications port 2. 16#00F0\nRepresents the collective status of the\nfollowing error flags.\n• _EIP2_MacAdrErr (Port2 MAC Ad-\ndress Error)\n• _EIP2_LanHwErr (Port2 Communica-\ntions Controller Error)\n• _EIP2_EtnCfgErr (Port2 Basic Ether-\nnet Setting Error)\n• _EIP2_IPAdrCfgErr (Port2 IP Address\nSetting Error)\n• _EIP2_IPAdrDupErr (Port2 IP Address\nDuplication Error)\n• _EIP2_BootpErr (Port2 BOOTP Serv-\ner Error)\n• _EIP2_DhcpErr (Port2 DHCP Server\nError)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Con-\nnection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or\nEtherNet/IP Error occurs, it is\nrecorded in the event log and\nthen the corresponding bit\nturns ON.\nRefer to Meanings of Error\nStatus Bits for the meanings of\nthe error status bits.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_CipErr CIP Communications This is the error status variable for CIP WORD 16#0000 to page 3-41\nError communications. 16#00F0\nNX-series CPU Units: Represents the\ncollective status of the following error\nflags.\n• _EIP1_IdentityErr (CIP Communica-\ntions1 Identity Error)\n• _EIP1_TDLinkCfgErr (CIP Communi-\ncations1 Tag Data Link Setting Error)\n• _EIP1_TDLinkOpnErr (CIP Communi-\ncations1 Tag Data Link Connection\nFailed)\n• _EIP1_TDLinkErr (CIP Communica-\ntions1 Tag Data Link Communications\nError)\n• _EIP1_TagAdrErr (CIP Communica-\ntions1 Tag Name Resolution Error)\n• _EIP1_MultiSwONErr (CIP Communi-\ncations1 Multiple Switches ON Error)\nNJ-series CPU Units: Represents the col-\nlective status of the following error flags.\n• _EIP_IdentityErr (Identity Error)\n• _EIP_TDLinkCfgErr (Tag Data Link\nSetting Error)\n• _EIP_TDLinkOpnErr (Tag Data Link\nConnection Failed)\n• _EIP_TDLinkErr (Tag Data Link Com-\nmunications Error)\n• _EIP_TagAdrErr (Tag Name Resolu-\ntion Error)\n• _EIP_MultiSwOnErr (Multiple\nSwitches ON Error)\nNoteIf a Tag Name Resolution Error\noccurs, it is recorded in the\nevent log and this variable\nchanges to TRUE. Refer to\nMeanings of Error Status Bits\nfor the meanings of the error\nstatus bits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-7\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_CipErr CIP Communica- This is the error status variable for CIP WORD 16#0000 to page 3-42\ntions1 Error communications 1. 16#00F0\nRepresents the collective status of the\nfollowing error flags.\n• _EIP1_IdentityErr (CIP Communica-\ntions1 Identity Error)\n• _EIP1_TDLinkCfgErr (CIP Communi-\ncations1 Tag Data Link Setting Error)\n• _EIP1_TDLinkOpnErr (CIP Communi-\ncations1 Tag Data Link Connection\nFailed)\n• _EIP1_TDLinkErr (CIP Communica-\ntions1 Tag Data Link Communications\nError)\n• _EIP1_TagAdrErr (CIP Communica-\ntions1 Tag Name Resolution Error)\n• _EIP1_MultiSwONErr (CIP Communi-\ncations1 Multiple Switches ON Error)\nNoteIf a Tag Name Resolution Error\noccurs, it is recorded in the\nevent log and this variable\nchanges to TRUE. Refer to\nMeanings of Error Status Bits\nfor the meanings of the error\nstatus bits.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_CipErr CIP Communica- This is the error status variable for CIP WORD 16#0000 to page 3-42\ntions2 Error communications 2. 16#00F0\nRepresents the collective status of the\nfollowing error flags.\n• _EIP2_IdentityErr (CIP Communica-\ntions2 Identity Error)\n• _EIP2_TDLinkCfgErr (CIP Communi-\ncations2 Tag Data Link Setting Error)\n• _EIP2_TDLinkOpnErr (CIP Communi-\ncations2 Tag Data Link Connection\nFailed)\n• _EIP2_TDLinkErr (CIP Communica-\ntions2 Tag Data Link Communications\nError)\n• _EIP2_TagAdrErr (CIP Communica-\ntions2 Tag Name Resolution Error)\n• _EIP2_MultiSwONErr (CIP Communi-\ncations2 Multiple Switches ON Error)\nNoteIf a Tag Name Resolution Error\noccurs, it is recorded in the\nevent log and this variable\nchanges to TRUE. Refer to\nMeanings of Error Status Bits\nfor the meanings of the error\nstatus bits.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TcpAppErr TCP Application This is the error status variable for TCP WORD 16#0000 to page 3-42\nCommunications Er- application communications. 16#00F0\nror Represents the collective status of the\nfollowing error flags.\n• _EIP_TcpAppCfgErr (TCP Application\nSetting Error)\n• _EIP_NTPSrvErr (NTP Server Con-\nnection Error)\nNoteRefer to Meanings of Error\nStatus Bits for the meanings of\nthe error status bits.\n_EIP_MacAdrErr MAC Address Error NX-series CPU Units: Indicates that an BOOL TRUE or page 3-43\nerror occurred when the MAC address FALSE\nwas read on the communications port 1\nat startup.\nTRUE: Error\nFALSE: Normal\nNJ-series CPU Units: Indicates that an\nerror occurred when the MAC address\nwas read at startup.\nTRUE: Error\nFALSE: Normal\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-9\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_MacAdrErr Port1 MAC Address Indicates that an error occurred when the BOOL TRUE or page 3-43\nError MAC address was read on the communi- FALSE\ncations port 1 at startup.\nTRUE: Error\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_MacAdrErr Port2 MAC Address Indicates that an error occurred when the BOOL TRUE or page 3-43\nError MAC address was read on the communi- FALSE\ncations port 2 at startup.\nTRUE: Error\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_LanHwErr Communications NX-series CPU Units: Indicates that a BOOL TRUE or page 3-43\nController Error Communications Controller failure occur- FALSE\nred on the communications port 1.\nTRUE: Failure\nFALSE: Normal\nNJ-series CPU Units: Indicates that a\nCommunications Controller failure occur-\nred.\nTRUE: Failure\nFALSE: Normal\n_EIP1_LanHwErr Port1 Communica- Indicates that a Communications Control- BOOL TRUE or page 3-44\ntions Controller Error ler failure occurred on the communica- FALSE\ntions port 1.\nTRUE: Failure\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_LanHwErr Port2 Communica- Indicates that a Communications Control- BOOL TRUE or page 3-44\ntions Controller Error ler failure occurred on the communica- FALSE\ntions port 2.\nTRUE: Failure\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_EtnCfgErr Basic Ethernet Set- NX-series CPU Units: Indicates that the BOOL TRUE or page 3-44\nting Error Ethernet communications speed setting FALSE\n(Speed/Duplex) for the communications\nport 1 is incorrect. Or, a read operation\nfailed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the\nEthernet communications speed setting\n(Speed/Duplex) is incorrect. Or, a read\noperation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\n_EIP1_EtnCfgErr Port1 Basic Ethernet Indicates that the Ethernet communica- BOOL TRUE or page 3-44\nSetting Error tions speed setting (Speed/Duplex) for FALSE\nthe communications port 1 is incorrect.\nOr, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_EtnCfgErr Port2 Basic Ethernet Indicates that the Ethernet communica- BOOL TRUE or page 3-45\nSetting Error tions speed setting (Speed/Duplex) for FALSE\nthe communications port 2 is incorrect.\nOr, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_IPAdrCfgErr IP Address Setting NX-series CPU Units: Indicates the IP BOOL TRUE or page 3-45\nError address setting errors for the communi- FALSE\ncations port 1.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the\nBOOTP server is inconsistent.\n• The IP address obtained from the\nDHCP server is inconsistent.\nFALSE: Normal\nNJ-series CPU Units: Indicates the IP ad-\ndress setting errors.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the\nBOOTP server is inconsistent.\n• The default gateway settings are not\ncorrect.\nFALSE: Normal\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-11\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_IPAdrCfgErr Port1 IP Address Indicates the IP address setting errors for BOOL TRUE or page 3-45\nSetting Error the communications port 1. FALSE\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the\nBOOTP server is inconsistent.\n• The IP address obtained from the\nDHCP server is inconsistent.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_IPAdrCfgErr Port2 IP Address Indicates the IP address setting errors for BOOL TRUE or page 3-46\nSetting Error the communications port 2. FALSE\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the\nBOOTP server is inconsistent.\n• The IP address obtained from the\nDHCP server is inconsistent.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_IPAdrDupErr IP Address Duplica- NX-series CPU Units: Indicates that the BOOL TRUE or page 3-46\ntion Error same IP address is assigned to more FALSE\nthan one node for the communications\nport 1.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that the\nsame IP address is assigned to more\nthan one node.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\n_EIP1_IPAdrDupErr Port1 IP Address Du- Indicates that the same IP address is as- BOOL TRUE or page 3-46\nplication Error signed to more than one node for the FALSE\ncommunications port 1.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_IPAdrDupErr Port2 IP Address Du- Indicates that the same IP address is as- BOOL TRUE or page 3-46\nplication Error signed to more than one node for the FALSE\ncommunications port 2.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_DNSCfgErr*1 DNS Setting Error Indicates that the DNS or hosts settings BOOL TRUE or page 3-47\nare incorrect. Or, a read operation failed. FALSE\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\n_EIP_BootpErr BOOTP Server Error NX-series CPU Units: Indicates that a BOOL TRUE or page 3-47\nBOOTP server connection failure occur- FALSE\nred on the communications port 1.\nTRUE: There was a failure to connect to\nthe BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or\nBOOTP is enabled and an IP address\nwas normally obtained from the BOOTP\nserver.\nNJ-series CPU Units: Indicates that a\nBOOTP server connection failure occur-\nred.\nTRUE: There was a failure to connect to\nthe BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or\nBOOTP is enabled and an IP address\nwas normally obtained from the BOOTP\nserver.\n_EIP1_BootpErr Port1 BOOTP Server Indicates that a BOOTP server connec- BOOL TRUE or page 3-47\nError tion failure occurred on the communica- FALSE\ntions port 1.\nTRUE: There was a failure to connect to\nthe BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or\nBOOTP is enabled and an IP address\nwas normally obtained from the BOOTP\nserver.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_BootpErr Port2 BOOTP Server Indicates that a BOOTP server connec- BOOL TRUE or page 3-47\nError tion failure occurred on the communica- FALSE\ntions port 2.\nTRUE: There was a failure to connect to\nthe BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or\nBOOTP is enabled and an IP address\nwas normally obtained from the BOOTP\nserver.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-13\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_DhcpErr DHCP Server Error Indicates that a DHCP server connection BOOL TRUE or page 3-47\nfailure occurred on the communications FALSE\nport 1.\nTRUE: There was a failure to connect to\nthe DHCP server (timeout).\nFALSE: The DHCP is not enabled, or\nDHCP is enabled and an IP address was\nnormally obtained from the DHCP server.\nNoteYou can use this system-de-\nfined variable only for the\nNX502 CPU Units.\n_EIP1_DhcpErr Port1 DHCP Server Indicates that a DHCP server connection BOOL TRUE or page 3-47\nError failure occurred on the communications FALSE\nport 1.\nTRUE: There was a failure to connect to\nthe DHCP server (timeout).\nFALSE: The DHCP is not enabled, or\nDHCP is enabled and an IP address was\nnormally obtained from the DHCP server.\nNoteYou can use this system-de-\nfined variable only for the\nNX502 CPU Units.\n_EIP2_DhcpErr Port2 DHCP Server Indicates that a DHCP server connection BOOL TRUE or page 3-47\nError failure occurred on the communications FALSE\nport 2.\nTRUE: There was a failure to connect to\nthe DHCP server (timeout).\nFALSE: The DHCP is not enabled, or\nDHCP is enabled and an IP address was\nnormally obtained from the DHCP server.\nNoteYou can use this system-de-\nfined variable only for the\nNX502 CPU Units.\n_EIP_IPRTblErr IP Route Table Error NX-series CPU Units: Indicates that the BOOL TRUE or page 3-48\ndefault gateway settings or IP router ta- FALSE\nble settings are incorrect.\nOr, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the\nIP router table or hosts settings are incor-\nrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\n_EIP_IdentityErr Identity Error NX-series CPU Units: Indicates that the BOOL TRUE or page 3-49\nidentity information for CIP communica- FALSE\ntions 1 (which you cannot overwrite) is in-\ncorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the\nidentity information (which you cannot\noverwrite) is incorrect. Or, a read opera-\ntion failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\n3-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_IdentityErr CIP Communica- Indicates that the identity information for BOOL TRUE or page 3-49\ntions1 Identity Error CIP communications 1 (which you cannot FALSE\noverwrite) is incorrect. Or, a read opera-\ntion failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_IdentityErr CIP Communica- Indicates that the identity information for BOOL TRUE or page 3-49\ntions2 Identity Error CIP communications 2 (which you cannot FALSE\noverwrite) is incorrect. Or, a read opera-\ntion failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TDLinkCfgErr Tag Data Link Setting NX-series CPU Units: Indicates that the BOOL TRUE or page 3-49\nError tag data link settings for CIP communica- FALSE\ntions 1 are incorrect. Or, a read operation\nfailed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the\ntag data link settings are incorrect. Or, a\nread operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\n_EIP1_TDLinkCfgErr CIP Communica- Indicates that the tag data link settings BOOL TRUE or page 3-50\ntions1 Tag Data Link for CIP communications 1 are incorrect. FALSE\nSetting Error Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TDLinkCfgErr CIP Communica- Indicates that the tag data link settings BOOL TRUE or page 3-50\ntions2 Tag Data Link for CIP communications 2 are incorrect. FALSE\nSetting Error Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-15\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TDLinkOpnErr Tag Data Link Con- NX-series CPU Units: Indicates that es- BOOL TRUE or page 3-50\nnection Failed tablishing a tag data link connection for FALSE\nCIP communications 1 failed.\nTRUE: Establishing a tag data link con-\nnection failed due to one of the following\ncauses.\n• The information registered for a target\nnode in the tag data link parameters is\ndifferent from the actual node informa-\ntion.\n• There was no response from the re-\nmote node.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that es-\ntablishing a tag data link connection\nfailed.\nTRUE: Establishing a tag data link con-\nnection failed due to one of the following\ncauses.\n• The information registered for a target\nnode in the tag data link parameters is\ndifferent from the actual node informa-\ntion.\n• There was no response from the re-\nmote node.\nFALSE: Other than the above.\n_EIP1_TDLinkOp- CIP Communica- Indicates that establishing a tag data link BOOL TRUE or page 3-51\nnErr tions1 Tag Data Link connection for CIP communications 1 FALSE\nConnection Failed failed.\nTRUE: Establishing a tag data link con-\nnection failed due to one of the following\ncauses.\n• The information registered for a target\nnode in the tag data link parameters is\ndifferent from the actual node informa-\ntion.\n• There was no response from the re-\nmote node.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_TDLinkOp- CIP Communica- Indicates that establishing a tag data link BOOL TRUE or page 3-51\nnErr tions2 Tag Data Link connection for CIP communications 2 FALSE\nConnection Failed failed.\nTRUE: Establishing a tag data link con-\nnection failed due to one of the following\ncauses.\n• The information registered for a target\nnode in the tag data link parameters is\ndifferent from the actual node informa-\ntion.\n• There was no response from the re-\nmote node.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TDLinkErr Tag Data Link Com- NX-series CPU Units: Indicates that a BOOL TRUE or page 3-51\nmunications Error timeout occurred in a tag data link con- FALSE\nnection for CIP communications 1.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that a\ntimeout occurred in a tag data link con-\nnection.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\n_EIP1_TDLinkErr CIP Communica- Indicates that a timeout occurred in a tag BOOL TRUE or page 3-52\ntions1 Tag Data Link data link connection for CIP communica- FALSE\nCommunications Er- tions 1.\nror TRUE: A timeout occurred.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TDLinkErr CIP Communica- Indicates that a timeout occurred in a tag BOOL TRUE or page 3-52\ntions2 Tag Data Link data link connection for CIP communica- FALSE\nCommunications Er- tions 2.\nror TRUE: A timeout occurred.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-17\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TagAdrErr Tag Name Resolution NX-series CPU Units: Indicates that the BOOL TRUE or page 3-52\nError tag resolution for CIP communications 1 FALSE\nfailed (i.e., the address could not be iden-\ntified from the tag name).\nTRUE: Tag resolution failed (i.e., the ad-\ndress could not be identified from the tag\nname). The following causes are possi-\nble.\n• The size of the network variable is dif-\nferent from the tag settings.\n• The I/O direction that is set in the tag\ndata link settings does not agree with\nthe I/O direction of the variable in the\nCPU Unit.\n• There is no network variable in the\nCPU Unit that corresponds to the tag\nsetting.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that tag\nname resolution failed (i.e., the address\ncould not be identified from the tag\nname).\nTRUE: Tag resolution failed (i.e., the ad-\ndress could not be identified from the tag\nname). The following causes are possi-\nble.\n• The size of the network variable is dif-\nferent from the tag settings.\n• The I/O direction that is set in the tag\ndata link settings does not agree with\nthe I/O direction of the variable in the\nCPU Unit.\n• There is no network variable in the\nCPU Unit that corresponds to the tag\nsetting.\nFALSE: Other than the above.\n_EIP1_TagAdrErr CIP Communica- Indicates that the tag resolution for CIP BOOL TRUE or page 3-53\ntions1 Tag Name communications 1 failed (i.e., the ad- FALSE\nResolution Error dress could not be identified from the tag\nname).\nTRUE: Tag resolution failed (i.e., the ad-\ndress could not be identified from the tag\nname). The following causes are possi-\nble.\n• The size of the network variable is dif-\nferent from the tag settings.\n• The I/O direction that is set in the tag\ndata link settings does not agree with\nthe I/O direction of the variable in the\nCPU Unit.\n• There is no network variable in the\nCPU Unit that corresponds to the tag\nsetting.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_TagAdrErr CIP Communica- Indicates that the tag resolution for CIP BOOL TRUE or page 3-53\ntions2 Tag Name communications 2 failed (i.e., the ad- FALSE\nResolution Error dress could not be identified from the tag\nname).\nTRUE: Tag resolution failed (i.e., the ad-\ndress could not be identified from the tag\nname). The following causes are possi-\nble.\n• The size of the network variable is dif-\nferent from the tag settings.\n• The I/O direction that is set in the tag\ndata link settings does not agree with\nthe I/O direction of the variable in the\nCPU Unit.\n• There is no network variable in the\nCPU Unit that corresponds to the tag\nsetting.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_MultiSwONErr Multiple Switches ON NX-series CPU Units: Indicates that more BOOL TRUE or page 3-53\nError than one switch turned ON at the same FALSE\ntime in CIP communications 1.\nTRUE: More than one data link start/stop\nswitch changed to TRUE at the same\ntime.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that more\nthan one switch turned ON at the same\ntime.\nTRUE: More than one data link start/stop\nswitch changed to TRUE at the same\ntime.\nFALSE: Other than the above.\n_EIP1_MultiSwO- CIP Communica- Indicates that more than one switch BOOL TRUE or page 3-54\nNErr tions1 Multiple turned ON at the same time in CIP com- FALSE\nSwitches ON Error munications 1.\nTRUE: More than one data link start/stop\nswitch changed to TRUE at the same\ntime.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-19\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_MultiSwO- CIP Communica- Indicates that more than one switch BOOL TRUE or page 3-54\nNErr tions2 Multiple turned ON at the same time in CIP com- FALSE\nSwitches ON Error munications 2.\nTRUE: More than one data link start/stop\nswitch changed to TRUE at the same\ntime.\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TcpAppCfgErr TCP Application Set- TRUE: At least one of the set values for a BOOL TRUE or page 3-54\nting Error TCP application (FTP, NTP, SNMP) is in- FALSE\ncorrect. Or, a read operation failed.\nFALSE: Normal\n_EIP_NTPSrvErr NTP Server Connec- TRUE: The NTP client failed to connect BOOL TRUE or page 3-54\ntion Error to the server (timeout). FALSE\nFALSE: NTP is not set. Or, NTP is set\nand the connection was successful.\n_EIP_DNSSrvErr DNS Server Connec- TRUE: The DNS client failed to connect BOOL TRUE or page 3-54\ntion Error to the server (timeout). FALSE\nFALSE: DNS is not enabled. Or, DNS is\nenabled and the connection was suc-\ncessful.\n*1. With the NJ-series CPU Unit, this variable can be used with the unit version 1.11 or later.\nHierarchical Relationship of System-defined Variables Related to EtherNet/IP Errors in the\nNJ-series CPU Unit\nThe system-defined variables that are related to EtherNet/IP errors have the following hierarchical\nrelationship. For example, if the value of any of the _EIP_PortErr, _EIP_CipErr, or _EIP_TcpAppErr\nvariables in the second level is TRUE, then the _EIP_ErrSta variable in the first level also changes\nto TRUE. Therefore, you can check the values of system-defined variables in a higher level to see\nif an error has occurred for a variable in a lower level.\n3-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nLevel 1 Level 2 Level 3\nVariable Name Variable Name Variable Name\n_EIP_ErrSta EtherNet/IP _EIP_Por- Communi- _EIP_MacAdrErr MAC Address Error\nError tErr cations _EIP_LanHwErr Communications Controller Error\nPort Error\n_EIP_EtnCfgErr Basic Ethernet Setting Error\n_EIP_IPAdrCfgErr IP Address Setting Error\n_EIP_IPAdrDupErr IP Address Duplication Error\n_EIP_BootpErr BOOTP Server Error\n_EIP_DNSSrvErr DNS Server Connection Error\n_EIP_IPRTblErr IP Route Table Error\n_EIP_Ci- CIP Com- _EIP_IdentityErr Identity Error\npErr munica- _EIP_TDLinkCfgErr Tag Data Link Setting Error\ntions Error\n_EIP_TDLinkOpnErr Tag Data Link Connection Failed\n_EIP_TDLinkErr Tag Data Link Communications Er-\nror\n_EIP_TagAdrErr Tag Name Resolution Error\n_EIP_MultiSwONErr Multiple Switches ON Error\n_EIP_Tcp TCP Ap- _EIP_TcpAppCfgErr TCP Application Setting Error\nAppErr plication _EIP_NTPSrvErr NTP Server Connection Error\nCommuni-\ncations\nError\nHierarchical Relationship of System-defined Variables Related to EtherNet/IP Errors in the\nNX-series CPU Unit\nThe system-defined variables that are related to EtherNet/IP errors have the following hierarchical\nrelationship. For example, if the value of any of the _EIP1_PortErr, _EIP2_PortErr, EIP1_CipErr,\n_EIP2_CipErr, and _EIP_TcpAppErr variables in the second level is TRUE, then the _EIP_ErrSta\nvariable in the first level also changes to TRUE. Therefore, you can check the values of system-\ndefined variables in a higher level to see if an error has occurred for a variable in a lower level.\nLevel 1 Level 2 Level 3\nVariable Name Variable Name Variable Name\n_EIP_ErrSta EtherNet/IP _EIP1_Po Communi- _EIP1_MacAdrErr Port1 MAC Address Error\nError rtErr cations\nPort1 Er-\nror\n_EIP1_LanHwErr Port1 Communications Controller\nError\n_EIP1_EtnCfgErr Port1 Basic Ethernet Setting Error\n_EIP1_IPAdrCfgErr Port1 IP Address Setting Error\n_EIP1_IPAdrDupErr Port1 IP Address Duplication Error\n_EIP1_BootpErr Port1 BOOTP Server Error\n_EIP1_DhcpErr Port1 DHCP Server Error\n_EIP_DNSCfgErr DNS Setting Error\n_EIP_DNSSrvErr DNS Server Connection Error\n_EIP_IPRTblErr IP Route Table Error\n_EIP2_Po Communi- _EIP2_MacAdrErr Port2 MAC Address Error\nrtErr cations\nPort2 Er-\nror\n_EIP2_LanHwErr Port2 Communications Controller\nError\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-21\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nLevel 1 Level 2 Level 3\nVariable Name Variable Name Variable Name\n_EIP2_EtnCfgErr Port2 Basic Ethernet Setting Error\n_EIP2_IPAdrCfgErr Port2 IP Address Setting Error\n_EIP2_IPAdrDupErr Port2 IP Address Duplication Error\n_EIP2_BootpErr Port2 BOOTP Server Error\n_EIP2_DhcpErr Port2 DHCP Server Error\n_EIP_DNSCfgErr DNS Setting Error\n_EIP_DNSSrvErr DNS Server Connection Error\n_EIP_IPRTblErr IP Route Table Error\n_EIP1_Ci- CIP Com- _EIP1_IdentityErr CIP Communications1 Identity Error\npErr munica- _EIP1_TDLinkCfgErr CIP Communications1 Tag Data\ntions1 Er- Link Setting Error\nror\n_EIP1_TDLinkOpnErr CIP Communications1 Tag Data\nLink Connection Failed\n_EIP1_TDLinkErr CIP Communications1 Tag Data\nLink Communications Error\n_EIP1_TagAdrErr CIP Communications1 Tag Name\nResolution Error\n_EIP1_MultiSwONErr CIP Communications1 Multiple\nSwitches ON Error\n_EIP2_Ci- CIP Com- _EIP2_IdentityErr CIP Communications2 Identity Error\npErr munica- _EIP2_TDLinkCfgErr CIP Communications2 Tag Data\ntions2 Er- Link Setting Error\nror\n_EIP2_TDLinkOpnErr CIP Communications2 Tag Data\nLink Connection Failed\n_EIP2_TDLinkErr CIP Communications2 Tag Data\nLink Communications Error\n_EIP2_TagAdrErr CIP Communications2 Tag Name\nResolution Error\n_EIP2_MultiSwONErr CIP Communications2 Multiple\nSwitches ON Error\n_EIP_Tcp TCP Ap- _EIP_TcpAppCfgErr TCP Application Setting Error\nAppErr plication _EIP_NTPSrvErr NTP Server Connection Error\nCommuni-\ncations\nError\nNote 1. You can access the same values of the system-defined variables whose variable names with _EIP1\nand the system-defined variables whose variable names with _EIP. For example, you can access the\nsame values of _EIP1_PortErr (Communications Port1 Error) and _EIP_PortErr (Communications\nPort Error).\nNote 2. You can use the system-defined variables whose variable names with _EIP2 only for the NX701 CPU\nUnits, NX502 CPU Units, and NX102 CPU Units.\n3-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n Functional Classification: EtherNet/IP Communications Status\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_EtnOnlineSta Online NX-series CPU Units: Indicates that the BOOL TRUE or page 3-55\nbuilt-in EtherNet/IP port's communica- FALSE\ntions can be used via the communica-\ntions port 1 (that is, the link is ON, IP ad-\ndress is defined, and there are no errors.)\nTRUE: The built-in EtherNet/IP port’s\ncommunications can be used.\nFALSE: The built-in EtherNet/IP port’s\ncommunications is disabled due to an er-\nror in initial processing, restart process-\ning, or link OFF status.\nNJ-series CPU Units: Indicates that the\nbuilt-in EtherNet/IP port's communica-\ntions can be used via the communica-\ntions port (that is, the link is ON and IP\naddress is defined, and there are no er-\nrors.)\nTRUE: The built-in EtherNet/IP port’s\ncommunications can be used.\nFALSE: The built-in EtherNet/IP port’s\ncommunications is disabled due to an er-\nror in initial processing, restart process-\ning, or link OFF status.\n_EIP1_EtnOnlineSta Port1 Online Indicates that the built-in EtherNet/IP BOOL TRUE or page 3-55\nport's communications can be used via FALSE\nthe communications port 1 (that is, the\nlink is ON, IP address is defined, and\nthere are no errors.)\nTRUE: The built-in EtherNet/IP port’s\ncommunications can be used.\nFALSE: The built-in EtherNet/IP port’s\ncommunications is disabled due to an er-\nror in initial processing, restart process-\ning, or link OFF status.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_EtnOnlineSta Port2 Online Indicates that the built-in EtherNet/IP BOOL TRUE or page 3-55\nport's communications can be used via FALSE\nthe communications port 2 (that is, the\nlink is ON, IP address is defined, and\nthere are no errors.)\nTRUE: The built-in EtherNet/IP port’s\ncommunications can be used.\nFALSE: The built-in EtherNet/IP port’s\ncommunications is disabled due to an er-\nror in initial processing, restart process-\ning, or link OFF status.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-23\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TDLinkRunSta Tag Data Link Com- NX-series CPU Units: Indicates that at BOOL TRUE or page 3-56\nmunications Status least one connection is in normal opera- FALSE\ntion in CIP communications 1.\nTRUE: Normal operation\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that at\nleast one connection is in normal opera-\ntion.\nTRUE: Normal operation\nFALSE: Other than the above.\n_EIP1_TDLinkRun- CIP Communica- Indicates that at least one connection is BOOL TRUE or page 3-56\nSta tions1 Tag Data Link in normal operation in CIP communica- FALSE\nCommunications Sta- tions 1.\ntus TRUE: Normal operation\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TDLinkRun- CIP Communica- Indicates that at least one connection is BOOL TRUE or page 3-56\nSta tions2 Tag Data Link in normal operation in CIP communica- FALSE\nCommunications Sta- tions 2.\ntus TRUE: Normal operation\nFALSE: Other than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TDLinkAllRun- All Tag Data Link NX-series CPU Units: Indicates that all BOOL TRUE or page 3-56\nSta Communications Sta- tag data links are communicating in CIP FALSE\ntus communications 1.\nTRUE: Tag data links are communicating\nin all connections as the originator.\nFALSE: An error occurred in at least one\nconnection.\nNJ-series CPU Units: Indicates that all\ntag data links are communicating.\nTRUE: Tag data links are communicating\nin all connections as the originator.\nFALSE: An error occurred in at least one\nconnection.\n_EIP1_TDLinkAll- CIP Communica- Indicates that all tag data links are com- BOOL TRUE or page 3-57\nRunSta tions1 All Tag Data municating in CIP communications 1. FALSE\nLink Communications TRUE: Tag data links are communicating\nStatus in all connections as the originator.\nFALSE: An error occurred in at least one\nconnection.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_TDLinkAll- CIP Communica- Indicates that all tag data links are com- BOOL TRUE or page 3-57\nRunSta tions2 All Tag Data municating in CIP communications 2. FALSE\nLink Communications TRUE: Tag data links are communicating\nStatus in all connections as the originator.\nFALSE: An error occurred in at least one\nconnection.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_RegTarget- Registered Target NX-series CPU Units: Gives a list of no- ARRAY TRUE or page 3-57\nSta[255] Node Information des for which EtherNet/IP connections [0..255] OF FALSE\nare registered for CIP communications 1. BOOL\nThis variable is valid only when the\nEtherNet/IP port is the originator.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x is registered.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x is not registered.\nNJ-series CPU Units: Gives a list of no-\ndes for which EtherNet/IP connections\nare registered.\nThis variable is valid only when the\nEtherNet/IP port is the originator.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x is registered.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x is not registered.\n_EIP1_RegTarget- CIP Communica- Gives a list of nodes for which ARRAY TRUE or page 3-57\nSta[255] tions1 Registered EtherNet/IP connections are registered [0..255] OF FALSE\nTarget Node Informa- for CIP communications 1. BOOL\ntion This variable is valid only when the\nEtherNet/IP port is the originator.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x is registered.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x is not registered.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-25\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_RegTarget- CIP Communica- Gives a list of nodes for which ARRAY TRUE or page 3-58\nSta[255] tions2 Registered EtherNet/IP connections are registered [0..255] OF FALSE\nTarget Node Informa- for CIP communications 2. BOOL\ntion This variable is valid only when the\nEtherNet/IP port is the originator.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x is registered.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x is not registered.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_EstbTarget- Normal Target Node NX-series CPU Units: Gives a list of no- ARRAY TRUE or page 3-58\nSta[255] Information des that have normally established Ether- [0..255] OF FALSE\nNet/IP connections for CIP communica- BOOL\ntions 1.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x was established normally.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x was not established, or an\nerror occurred.\nNJ-series CPU Units: Gives a list of no-\ndes that have normally established Ether-\nNet/IP connections.\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x was established normally.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x was not established, or an\nerror occurred.\n_EIP1_EstbTarget- CIP Communica- Gives a list of nodes that have normally ARRAY TRUE or page 3-58\nSta[255] tions1 Normal Target established EtherNet/IP connections for [0..255] OF FALSE\nNode Information CIP communications 1. BOOL\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x was established normally.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x was not established, or an\nerror occurred.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_EstbTarget- CIP Communica- Gives a list of nodes that have normally ARRAY TRUE or page 3-59\nSta[255] tions2 Normal Target established EtherNet/IP connections for [0..255] OF FALSE\nNode Information CIP communications 2. BOOL\nArray[x] is TRUE:\nThe connection to the node with a target\nnode ID of x was established normally.\nArray[x] is FALSE:\nThe connection to the node with a target\nnode ID of x was not established, or an\nerror occurred.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TargetPLCMo- Target PLC Operat- NX-series CPU Units: Shows the operat- ARRAY TRUE or page 3-59\ndeSta[255] ing Mode ing status of the target node Controllers [0..255] OF FALSE\nthat are connected for CIP communica- BOOL\ntions 1, with the EtherNet/IP port as the\noriginator.\nThe array elements are valid only when\nthe corresponding Normal Target Node\nInformation is TRUE. If the corresponding\nNormal Target Node Information is\nFALSE, it indicates the previous operat-\ning status.\nArray[x] is TRUE:\nThis is the operating state of the target\nController with a node address of x.\nArray[x] is FALSE:\nOther than the above.\nNJ-series CPU Units: Shows the operat-\ning status of the target node Controllers\nthat are connected with the EtherNet/IP\nport as the originator.\nThe array elements are valid only when\nthe corresponding Normal Target Node\nInformation is TRUE. If the corresponding\nNormal Target Node Information is\nFALSE, it indicates the previous operat-\ning status.\nArray[x] is TRUE:\nThis is the operating state of the target\nController with a node address of x.\nArray[x] is FALSE:\nOther than the above.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-27\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_TargetPLC- CIP Communica- Shows the operating status of the target ARRAY TRUE or page 3-59\nModeSta[255] tions1 Target PLC node Controllers that are connected for [0..255] OF FALSE\nOperating Mode CIP communications 1, with the Ether- BOOL\nNet/IP port as the originator.\nThe array elements are valid only when\nthe corresponding Normal Target Node\nInformation is TRUE. If the corresponding\nNormal Target Node Information is\nFALSE, it indicates the previous operat-\ning status.\nArray[x] is TRUE:\nThis is the operating state of the target\nController with a node address of x.\nArray[x] is FALSE:\nOther than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TargetPLC- CIP Communica- Shows the operating status of the target ARRAY TRUE or page 3-60\nModeSta[255] tions2 Target PLC node Controllers that are connected for [0..255] OF FALSE\nOperating Mode CIP communications 2, with the Ether- BOOL\nNet/IP port as the originator.\nThe array elements are valid only when\nthe corresponding Normal Target Node\nInformation is TRUE. If the corresponding\nNormal Target Node Information is\nFALSE, it indicates the previous operat-\ning status.\nArray[x] is TRUE:\nThis is the operating state of the target\nController with a node address of x.\nArray[x] is FALSE:\nOther than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TargetPL- Target PLC Error In- NX-series CPU Units: Shows the error ARRAY TRUE or page 3-60\nCErr[255] formation status (logical OR of fatal and non-fatal [0..255] OF FALSE\nerrors) of the target node Controllers that BOOL\nare connected for CIP communications 1,\nwith the EtherNet/IP ports as the origina-\ntor. The array elements are valid only\nwhen the corresponding Normal Target\nNode Information is TRUE. The immedi-\nately preceding value is retained if this\nvariable is FALSE.\nArray[x] is TRUE:\nA fatal or non-fatal error occurred in the\ntarget Controller with a target node ID of\nx.\nArray[x] is FALSE:\nOther than the above.\nNJ-series CPU Units: Shows the error\nstatus (logical OR of fatal and non-fatal\nerrors) of the target node Controllers that\nare connected with the EtherNet/IP ports\nas the originator. The array elements are\nvalid only when the corresponding Nor-\nmal Target Node Information is TRUE.\nThe immediately preceding value is re-\ntained if this variable is FALSE.\nArray[x] is TRUE:\nA fatal or non-fatal error occurred in the\ntarget Controller with a target node ID of\nx.\nArray[x] is FALSE:\nOther than the above.\n_EIP1_TargetPL- CIP Communica- Shows the error status (logical OR of fa- ARRAY TRUE or page 3-60\nCErr[255] tions1 Target PLC Er- tal and non-fatal errors) of the target [0..255] OF FALSE\nror Information node Controllers that are connected for BOOL\nCIP communications 1, with the Ether-\nNet/IP ports as the originator. The array\nelements are valid only when the corre-\nsponding Normal Target Node Informa-\ntion is TRUE. The immediately preceding\nvalue is retained if this variable is FALSE.\nArray[x] is TRUE:\nA fatal or non-fatal error occurred in the\ntarget Controller with a target node ID of\nx.\nArray[x] is FALSE:\nOther than the above.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-29\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_TargetPL- CIP Communica- Shows the error status (logical OR of fa- ARRAY TRUE or page 3-61\nCErr[255] tions2 Target PLC Er- tal and non-fatal errors) of the target [0..255] OF FALSE\nror Information node Controllers that are connected for BOOL\nCIP communications 2, with the Ether-\nNet/IP ports as the originator. The array\nelements are valid only when the corre-\nsponding Normal Target Node Informa-\ntion is TRUE. The immediately preceding\nvalue is retained if this variable is FALSE.\nArray[x] is TRUE:\nA fatal or non-fatal error occurred in the\ntarget Controller with a target node ID of\nx.\nArray[x] is FALSE:\nOther than the above.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TargetNo- Target Node Error In- NX-series CPU Units: Indicates that the ARRAY TRUE or page 3-61\ndeErr[255] formation connection for the Registered Target [0..255] OF FALSE\nNode Information for CIP communica- BOOL\ntions 1 was not established or that an er-\nror occurred in the target Controller.\nThe array elements are valid only when\nthe Registered Target Node Information\nis TRUE.\nArray[x] is TRUE:\nA connection was not normally establish-\ned with the target node for a target node\nID of x (the Registered Target Node Infor-\nmation is TRUE and the Normal Target\nNode Information is FALSE), or a con-\nnection was established with the target\nnode but an error occurred in the target\nController.\nArray[x] is FALSE:\nThe target node is not registered for a\ntarget node ID of x (the Registered Target\nNode Information is FALSE), or a con-\nnection was normally established with the\ntarget node (the Registered Target Node\nInformation is TRUE and the Normal Tar-\nget Node Information is TRUE). An error\noccurred in the target Controller (the Tar-\nget PLC Error Information is TRUE).\nNJ-series CPU Units: Indicates that the\nconnection for the Registered Target\nNode Information was not established or\nthat an error occurred in the target Con-\ntroller.\nThe array elements are valid only when\nthe Registered Target Node Information\nis TRUE.\nArray[x] is TRUE:\nA connection was not normally establish-\ned with the target node for a target node\nID of x (the Registered Target Node Infor-\nmation is TRUE and the Normal Target\nNode Information is FALSE), or a con-\nnection was established with the target\nnode but an error occurred in the target\nController.\nArray[x] is FALSE:\nThe target node is not registered for a\ntarget node ID of x (the Registered Target\nNode Information is FALSE), or a con-\nnection was normally established with the\ntarget node (the Registered Target Node\nInformation is TRUE and the Normal Tar-\nget Node Information is TRUE). An error\noccurred in the target Controller (the Tar-\nget PLC Error Information is TRUE).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-31\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_TargetNo- CIP Communica- Indicates that the connection for the Reg- ARRAY TRUE or page 3-62\ndeErr[255] tions1 Target Node istered Target Node Information for CIP [0..255] OF FALSE\nError Information communications 1 was not established or BOOL\nthat an error occurred in the target Con-\ntroller.\nThe array elements are valid only when\nthe Registered Target Node Information\nis TRUE.\nArray[x] is TRUE:\nA connection was not normally establish-\ned with the target node for a target node\nID of x (the Registered Target Node Infor-\nmation is TRUE and the Normal Target\nNode Information is FALSE), or a con-\nnection was established with the target\nnode but an error occurred in the target\nController.\nArray[x] is FALSE:\nThe target node is not registered for a\ntarget node ID of x (the Registered Target\nNode Information is FALSE), or a con-\nnection was normally established with the\ntarget node (the Registered Target Node\nInformation is TRUE and the Normal Tar-\nget Node Information is TRUE). An error\noccurred in the target Controller (the Tar-\nget PLC Error Information is TRUE).\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n3-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP2_TargetNo- CIP Communica- Indicates that the connection for the Reg- ARRAY TRUE or page 3-62\ndeErr[255] tions2 Target Node istered Target Node Information for CIP [0..255] OF FALSE\nError Information communications 2 was not established or BOOL\nthat an error occurred in the target Con-\ntroller.\nThe array elements are valid only when\nthe Registered Target Node Information\nis TRUE.\nArray[x] is TRUE:\nA connection was not normally establish-\ned with the target node for a target node\nID of x (the Registered Target Node Infor-\nmation is TRUE and the Normal Target\nNode Information is FALSE), or a con-\nnection was established with the target\nnode but an error occurred in the target\nController.\nArray[x] is FALSE:\nThe target node is not registered for a\ntarget node ID of x (the Registered Target\nNode Information is FALSE), or a con-\nnection was normally established with the\ntarget node (the Registered Target Node\nInformation is TRUE and the Normal Tar-\nget Node Information is TRUE). An error\noccurred in the target Controller (the Tar-\nget PLC Error Information is TRUE).\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_NTPResult NTP Operation Infor- Use the GetNTPStatus instruction to read _sNTP_RE- page 3-62\nmation the NTP operation information from the SULT\nuser program.\nDirect access is not possible.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-33\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n.ExecTime NTP Last Operation Gives the last time that NTP processing DATE_AND_ Depends on page 3-63\nTime ended normally. TIME data type.\nThe time that was obtained from the NTP\nserver is stored when the time is ob-\ntained normally.\nThe time is not stored if it is not obtained\nfrom the NTP server normally.\nNoteDo not use this variable in the\nuser program. There may be a\ndelay in updating it. Use this\nvariable only to access status\nthrough communications from\nan external device.\n.ExecNormal NTP Operation Re- TRUE: Indicates an NTP normal end. BOOL TRUE or page 3-63\nsult FALSE: Indicates that NTP operation FALSE\nended in an error or has not been execut-\ned even once.\nNoteDo not use this variable in the\nuser program. There may be a\ndelay in updating it. Use this\nvariable only to access status\nthrough communications from\nan external device.\n3-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nPrecautions for Correct Use\nCommunications Status with Target Node\nThe communications status with the target node of an NJ/NX-series Controller is shown by the\ncombination of the values of four system-defined variables.\n• _EIP_RegTargetSta (Registered Target Node Information)\n• _EIP_EstbTargetSta (Normal Target Node Information)\n• _EIP_TargetPLCErr (Target PLC Error Information)\n• _EIP_TargetNodeErr (Target Node Error Information)\nValue of Value of Value of Value of\nCommunications status\n_EIP_RegTarget- _EIP_EstbTar- _EIP_Tar- _EIP_Target-\nwith target node\nSta getSta getPLCErr NodeErr\nTRUE TRUE FALSE FALSE A connection with the target\nnode was established normal-\nly and there is no error in the\ntarget PLC.\nTRUE TRUE A connection with the target\nnode was established but\nthere is an error in the target\nPLC.\nFALSE --- TRUE A connection with the target\nnode was not established nor-\nmally.\nFALSE --- --- --- The information is not valid\nbecause the target node is not\nregistered.\nFor the NX-series Controller, the communications status of CIP communications 1 and CIP\ncommunications 2 is shown by the combination of the values of four system-defined variables in\nthe same way as shown in the above table.\n• CIP Communications 1\n• _EIP1_RegTargetSta (CIP Communications1 Registered Target Node Information)\n• _EIP1_EstbTargetSta (CIP Communications1 Normal Target Node Information)\n• _EIP1_TargetPLCErr (CIP Communications1 Target PLC Error Information)\n• _EIP1_TargetNodeErr (CIP Communications1 Target Node Error Information)\n• CIP Communications 2\n• _EIP2_RegTargetSta (CIP Communications2 Registered Target Node Information)\n• _EIP2_EstbTargetSta (CIP Communications2 Normal Target Node Information)\n• _EIP2_TargetPLCErr (CIP Communications2 Target PLC Error Information)\n• _EIP2_TargetNodeErr (CIP Communications2 Target Node Error Information)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-35\n3-2\nSystem-defined\nVariables\n3\n3-2-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n Functional Classification: EtherNet/IP Communications Switches\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP_TDLink- Tag Data Link Com- NX-series CPU Units: Change this varia- BOOL TRUE or page 3-63\nStartCmd munications Start ble to TRUE to start tag data links for CIP FALSE\nSwitch communications 1.\nIt automatically changes back to FALSE\nafter tag data link operation starts.\nNJ-series CPU Units: Change this varia-\nble to TRUE to start tag data links.\nIt automatically changes back to FALSE\nafter tag data link operation starts.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\n_EIP1_TDLink- CIP Communica- Change this variable to TRUE to start tag BOOL TRUE or page 3-63\nStartCmd tions1 Tag Data Link data links for CIP communications 1. FALSE\nCommunications It automatically changes back to FALSE\nStart Switch after tag data link operation starts.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TDLink- CIP Communica- Change this variable to TRUE to start tag BOOL TRUE or page 3-64\nStartCmd tions2 Tag Data Link data links for CIP communications 2. FALSE\nCommunications It automatically changes back to FALSE\nStart Switch after tag data link operation starts.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n_EIP_TDLink- Tag Data Link Com- NX-series CPU Units: Change this varia- BOOL TRUE or page 3-64\nStopCmd munications Stop ble to TRUE to stop tag data links for CIP FALSE\nSwitch communications 1.\nIt automatically changes back to FALSE\nafter tag data link operation stops.\nNJ-series CPU Units: Change this varia-\nble to TRUE to stop tag data links.\nIt automatically changes back to FALSE\nafter tag data link operation stops.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\n3-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nRange of\nVariable name Meaning Function Data type Reference\nvalues\n_EIP1_TDLink- CIP Communica- Change this variable to TRUE to stop tag BOOL TRUE or page 3-64\nStopCmd tions1 Tag Data Link data links for CIP communications 1. FALSE\nCommunications It automatically changes back to FALSE\nStop Switch after tag data link operation stops.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\nNoteYou can use this system-de-\nfined variable only for NX-ser-\nies CPU Units.\n_EIP2_TDLink- CIP Communica- Change this variable to TRUE to stop tag BOOL TRUE or page 3-64\nStopCmd tions2 Tag Data Link data links for CIP communications 2. FALSE\nCommunications It automatically changes back to FALSE\nStop Switch after tag data link operation stops.\nNoteDo not force this switch to\nchange to FALSE from the\nuser program or from the Sys-\nmac Studio. It changes to\nFALSE automatically.\nNoteYou can use this system-de-\nfined variable only for the\nNX701 CPU Units, NX502\nCPU Units, and NX102 CPU\nUnits.\n3-2-2 Meanings of Error Status Bits\nThe meanings of the individual bits in the error status are shown in the following table.\nBit: 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0\nWORD - - - - - - - - - -\nBit Description\n15 Master-detected error: This bit indicates whether the master detected a Controller error in the Unit/slave for the\nerror status of the Controller error.\nTRUE: The master detected a Controller error.\nFALSE: The master has not detected a Controller error.\n14 Collective slave error status: This bit indicates if a Controller error is detected for levels (e.g., a Unit, slave, axis,\nor axes group) that are lower than the event source (i.e., for a function module).\nTRUE: A Controller error has occurred at a lower level.\nFALSE: A Controller error has not occurred at a lower level.\n13 to 8 Reserved.\n7 This bit indicates whether a major fault level Controller error has occurred.\nTRUE: A major fault level Controller error has occurred.\nFALSE: A major fault level Controller error has not occurred.\n6 This bit indicates whether a partial fault level Controller error has occurred.\nTRUE: A partial fault level Controller error has occurred.\nFALSE: A partial fault level Controller error has not occurred.\n5 This bit indicates whether a minor fault level Controller error has occurred.\nTRUE: A minor fault level Controller error has occurred.\nFALSE: A minor fault level Controller error has not occurred.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-37\n3-2\nSystem-defined\nVariables\n3\n3-2-2\nMeanings\nof\nError\nStatus\nBits\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nBit Description\n4 This bit indicates whether an observation level Controller error has occurred.\nTRUE: An observation level Controller error has occurred.\nFALSE: An observation level Controller error has not occurred.\n3 to 0 Reserved.\nA list of variables for error status is given below. The following table shows whether bit 14 and bit 15 of\neach variable are valid or invalid and whether they can be used in the user program.\nVariable name Valid or inva- Valid or inva- Usage in user\nlid for bit 15 lid for bit 14 program\n_ErrSta (Controller Error Status) Valid Valid Not possible*1\n_PLC_ErrSta (PLC Function Module Error Status) Invalid Invalid Possible\n_CJB_ErrSta (I/O Bus Error Status) Valid Valid Not possible*2\n_CJB_MstrErrSta (I/O Bus Master Error Status) Invalid Invalid\n_CJB_UnitErrSta (I/O Bus Unit Error Status) Valid Invalid\n_NXB_ErrSta (NX Bus Function Module Error Status) Invalid Valid Not recom-\n_NXB_MstrErrSta (NX Bus Function Module Master Error Status) Invalid Valid mended*3\n_NXB_UnitErrStaTbl (NX Bus Function Module Unit Error Status) Invalid Valid\n_MC_ErrSta (MC Error Status) Invalid Valid Possible\n_MC_ComErrSta (MC Common Error Status) Invalid Invalid\n_MC_AX_ErrSta (Axis Error Status) Invalid Invalid\n_MC_GRP_ErrSta (Axes Group Error Status) Invalid Invalid\n_EC_ErrSta (EtherCAT Error) Invalid Valid Possible\n_EC_PortErr (Communications Port Error) Invalid Invalid\n_EC_MstrErr (Master Error) Invalid Invalid\n_EC_SlavErr (Slave Error) Invalid Invalid\n_EC_SlavErrTbl (Slave Error Table) Invalid Invalid\n_EIP_ErrSta (EtherNet/IP Error) Invalid Invalid Possible\n_EIP_PortErr (Communications Port Error), _EIP1_PortErr (Communi- Invalid Invalid\ncations Port1 Error), _EIP2_PortErr (Communications Port2 Error)\n_EIP_CipErr (CIP Communications Error), _EIP1_CipErr (CIP Com- Invalid Invalid\nmunications1 Error), _EIP2_CipErr (CIP Communications2 Error)\n_EIP_TcpAppErr (TCP Application Communications Error) Invalid Invalid\n_XBU_ErrSta (X Bus Function Module Error Status) Invalid Valid Not recom-\n_XBU_MstrErr (X Bus Function Module Master Error Status) Invalid Invalid mended*3\n_XBU_UnitErr (X Bus Function Module Unit Error Status) Invalid Valid\n_XBU_UnitErrTbl (X Bus Function Module Unit Error Status Table) Invalid Invalid\n*1. Do not use this variable in the user program. There may be a delay in updating it and concurrency problems in relation to\nthe error status of the function module. Use this variable only to access status through communications from an external\ndevice.\n*2. Do not use this variable in the user program. There may be a delay in updating it. Use this variable only to access status\nthrough communications from an external device such as an HMI.\n*3. We do not recommend the use of this variable in the user program. There may be a delay in updating it. Use this variable\nonly to access status through communications from an external device such as an HMI.\n3-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n3-3 Specifications for Individual System-\ndefined Variables\nThe specifications for each system-defined variable are given as described below.\nVariable name This is the system-defined variable name. Members The member names are given\nThe prefix gives the category name. for structure variables.\nMeaning This is the meaning of the variable. Global/local Global: Global variable, Local:\nLocal variable\nFunction The function of the variable is described.\nData type The data type of the variable is given. Range of values The range of values that the var-\niable can take is given.\nR/W access R: Read on- Retained The Retain Network Publish The Network Publish attribute of\nly, attribute of the variable is given.\nRW: Read/ the variable\nwrite is given.\nUsage in user Whether you Related in- The instructions that are related to the variable are given.\nprogram can use the structions If you cannot use the variable directly in the user program, the instruc-\nvariable di- tions that access the variable are given.\nrectly in the\nuser pro-\ngram is\nspecified.\n3-3-1 EtherNet/IP Function Module, Category Name: _EIP\n Functional Classification: EtherNet/IP Communications Errors\nVariable name _EIP_ErrSta\nMeaning EtherNet/IP Error Global/local Global\nFunction This is the error status variable for the built-in EtherNet/IP port.\nNX-series CPU Units: Represents the collective status of the following error flags.\n• _EIP1_PortErr (Communications Port1 Error)\n• _EIP2_PortErr (Communications Port2 Error)\n• _EIP1_CipErr (CIP Communications1 Error)\n• _EIP2_CipErr (CIP Communications2 Error)\n• _EIP_TcpAppErr (TCP Application Communications Error)\nNJ-series CPU Units: Represents the collective status of the following error flags.\n• _EIP_PortErr (Communications Port Error)\n• _EIP_CipErr (CIP Communications Error)\n• _EIP_TcpAppErr (TCP Application Communications Error)\nNoteRefer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the meanings of the error status\nbits.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-39\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_PortErr\nMeaning Communications Port Error Global/local Global\nFunction This is the error status variable for the communications port.\nNX-series CPU Units: Represents the collective status of the following error flags.\n• _EIP1_MacAdrErr (Port1 MAC Address Error)\n• _EIP1_LanHwErr (Port1 Communications Controller Error)\n• _EIP1_EtnCfgErr (Port1 Basic Ethernet Setting Error)\n• _EIP1_IPAdrCfgErr (Port1 IP Address Setting Error)\n• _EIP1_IPAdrDupErr (Port1 IP Address Duplication Error)\n• _EIP1_BootpErr (Port1 BOOTP Server Error)\n• _EIP1_DhcpErr (Port1 DHCP Server Error)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Connection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNJ-series CPU Units: Represents the collective status of the following error flags.\n• _EIP_MacAdrErr (MAC Address Error)\n• _EIP_LanHwErr (Communications Controller Error)\n• _EIP_EtnCfgErr (Basic Ethernet Setting Error)\n• _EIP_IPAdrCfgErr (IP Address Setting Error)\n• _EIP_IPAdrDupErr (IP Address Duplication Error)\n• _EIP_BootpErr (BOOTP Server Error)\n• _EIP_DNSSrvErr (DNS Server Connection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or EtherNet/IP Error occurs, it is recorded in the event log and then the\ncorresponding bit turns ON. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the\nmeanings of the error status bits.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nVariable name _EIP1_PortErr\nMeaning Communications Port1 Error Global/local Global\nFunction This is the error status variable for the communications port 1.\nIt represents the collective status of the following error flags.\n• _EIP1_MacAdrErr (Port1 MAC Address Error)\n• _EIP1_LanHwErr (Port1 Communications Controller Error)\n• _EIP1_EtnCfgErr (Port1 Basic Ethernet Setting Error)\n• _EIP1_IPAdrCfgErr (Port1 IP Address Setting Error)\n• _EIP1_IPAdrDupErr (Port1 IP Address Duplication Error)\n• _EIP1_BootpErr (Port1 BOOTP Server Error)\n• _EIP1_DhcpErr (Port1 DHCP Server Error)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Connection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or EtherNet/IP Error occurs, it is recorded in the event log and then the\ncorresponding bit turns ON. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the\nmeanings of the error status bits.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\n3-40 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_PortErr\nMeaning Communications Port2 Error Global/local Global\nFunction This is the error status variable for the communications port 2.\nIt represents the collective status of the following error flags.\n• _EIP2_MacAdrErr (Port2 MAC Address Error)\n• _EIP2_LanHwErr (Port2 Communications Controller Error)\n• _EIP2_EtnCfgErr (Port2 Basic Ethernet Setting Error)\n• _EIP2_IPAdrCfgErr (Port2 IP Address Setting Error)\n• _EIP2_IPAdrDupErr (Port2 IP Address Duplication Error)\n• _EIP2_BootpErr (Port2 BOOTP Server Error)\n• _EIP2_DhcpErr (Port2 DHCP Server Error)\n• _EIP_DNSCfgErr (DNS Setting Error)\n• _EIP_DNSSrvErr (DNS Server Connection Error)\n• _EIP_IPRTblErr (IP Route Table Error)\nNoteIf a Link OFF Detected or EtherNet/IP Error occurs, it is recorded in the event log and then the\ncorresponding bit turns ON. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the\nmeanings of the error status bits.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nVariable name _EIP_CipErr\nMeaning CIP Communications Error Global/local Global\nFunction This is the error status variable for CIP communications.\nNX-series CPU Units: Represents the collective status of the following error flags.\n• _EIP1_IdentityErr (CIP Communications1 Identity Error)\n• _EIP1_TDLinkCfgErr (CIP Communications1 Tag Data Link Setting Error)\n• _EIP1_TDLinkOpnErr (CIP Communications1 Tag Data Link Connection Failed)\n• _EIP1_TDLinkErr (CIP Communications1 Tag Data Link Communications Error)\n• _EIP1_TagAdrErr (CIP Communications1 Tag Name Resolution Error)\n• _EIP1_MultiSwONErr (CIP Communications1 Multiple Switches ON Error)\nNJ-series CPU Units: Represents the collective status of the following error flags.\n• _EIP_IdentityErr (Identity Error)\n• _EIP_TDLinkCfgErr (Tag Data Link Setting Error)\n• _EIP_TDLinkOpnErr (Tag Data Link Connection Failed)\n• _EIP_TDLinkErr (Tag Data Link Communications Error)\n• _EIP_TagAdrErr (Tag Name Resolution Error)\n• _EIP_MultiSwOnErr (Multiple Switches ON Error)\nNoteIf a Tag Name Resolution Error occurs, it is recorded in the event log and this variable changes\nto TRUE. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the meanings of the\nerror status bits.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-41\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_CipErr\nMeaning CIP Communications1 Error Global/local Global\nFunction This is the error status variable for CIP communications 1.\nIt represents the collective status of the following error flags.\n• _EIP1_IdentityErr (CIP Communications1 Identity Error)\n• _EIP1_TDLinkCfgErr (CIP Communications1 Tag Data Link Setting Error)\n• _EIP1_TDLinkOpnErr (CIP Communications1 Tag Data Link Connection Failed)\n• _EIP1_TDLinkErr (CIP Communications1 Tag Data Link Communications Error)\n• _EIP1_TagAdrErr (CIP Communications1 Tag Name Resolution Error)\n• _EIP1_MultiSwONErr (CIP Communications1 Multiple Switches ON Error)\nNoteIf a Tag Name Resolution Error occurs, it is recorded in the event log and this variable changes\nto TRUE. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the meanings of the\nerror status bits.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nVariable name _EIP2_CipErr\nMeaning CIP Communications2 Error Global/local Global\nFunction This is the error status variable for CIP communications 2.\nIt represents the collective status of the following error flags.\n• _EIP2_IdentityErr (CIP Communications2 Identity Error)\n• _EIP2_TDLinkCfgErr (CIP Communications2 Tag Data Link Setting Error)\n• _EIP2_TDLinkOpnErr (CIP Communications2 Tag Data Link Connection Failed)\n• _EIP2_TDLinkErr (CIP Communications2 Tag Data Link Communications Error)\n• _EIP2_TagAdrErr (CIP Communications2 Tag Name Resolution Error)\n• _EIP2_MultiSwONErr (CIP Communications2 Multiple Switches ON Error)\nNoteIf a Tag Name Resolution Error occurs, it is recorded in the event log and this variable changes\nto TRUE. Refer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the meanings of the\nerror status bits.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\nVariable name _EIP_TcpAppErr\nMeaning TCP Application Communications Error Global/local Global\nFunction This is the error status variable for TCP application communications.\nIt represents the collective status of the following error flags.\n• _EIP_TcpAppCfgErr (TCP Application Setting Error)\n• _EIP_NTPSrvErr (NTP Server Connection Error)\nNoteRefer to 3-2-2 Meanings of Error Status Bits on page 3-37 for the meanings of the error status\nbits.\nData type WORD Range of values 16#0000 to 16#00F0\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- You can access this variable from the user program with the following instruc-\ngram structions tion.\n• GetEIPError\n3-42 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_MacAdrErr\nMeaning MAC Address Error Global/local Global\nFunction NX-series CPU Units: Indicates that an error occurred when the MAC address was read on the communications\nport 1 at startup.\nTRUE: Error\nFALSE: Normal\nNJ-series CPU Units: Indicates that an error occurred when the MAC address was read at startup.\nTRUE: Error\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_MacAdrErr\nMeaning Port1 MAC Address Error Global/local Global\nFunction Indicates that an error occurred when the MAC address was read on the communications port 1 at startup.\nTRUE: Error\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_MacAdrErr\nMeaning Port2 MAC Address Error Global/local Global\nFunction Indicates that an error occurred when the MAC address was read on the communications port 2 at startup.\nTRUE: Error\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_LanHwErr\nMeaning Communications Controller Error Global/local Global\nFunction NX-series CPU Units: Indicates that a Communications Controller failure occurred on the communications port 1.\nTRUE: Failure\nFALSE: Normal\nNJ-series CPU Units: Indicates that a Communications Controller failure occurred.\nTRUE: Failure\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-43\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_LanHwErr\nMeaning Port1 Communications Controller Error Global/local Global\nFunction Indicates that a Communications Controller failure occurred on the communications port 1.\nTRUE: Failure\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TTRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_LanHwErr\nMeaning Port2 Communications Controller Error Global/local Global\nFunction Indicates that a Communications Controller failure occurred on the communications port 2.\nTRUE: Failure\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_EtnCfgErr\nMeaning Basic Ethernet Setting Error Global/local Global\nFunction NX-series CPU Units: Indicates that the Ethernet communications speed setting (Speed/Duplex) for the communi-\ncations port 1 is incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the Ethernet communications speed setting (Speed/Duplex) is incorrect. Or, a\nread operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_EtnCfgErr\nMeaning Port1 Basic Ethernet Setting Error Global/local Global\nFunction Indicates that the Ethernet communications speed setting (Speed/Duplex) for the communications port 1 is incor-\nrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-44 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_EtnCfgErr\nMeaning Port2 Basic Ethernet Setting Error Global/local Global\nFunction Indicates that the Ethernet communications speed setting (Speed/Duplex) for the communications port 2 is incor-\nrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_IPAdrCfgErr\nMeaning IP Address Setting Error Global/local Global\nFunction NX-series CPU Units: Indicates the IP address setting errors for the communications port 1.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the BOOTP server is inconsistent.\n• The IP address obtained from the DHCP server is inconsistent.\nFALSE: Normal\nNJ-series CPU Units: Indicates the IP address setting errors.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the BOOTP server is inconsistent.\n• The default gateway settings are not correct.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_IPAdrCfgErr\nMeaning Port1 IP Address Setting Error Global/local Global\nFunction Indicates the IP address setting errors for the communications port 1.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the BOOTP server is inconsistent.\n• The IP address obtained from the DHCP server is inconsistent.\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Related in- Related in- ---\ngram structions structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-45\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_IPAdrCfgErr\nMeaning Port2 IP Address Setting Error Global/local Global\nFunction Indicates the IP address setting errors for the communications port 2.\nTRUE:\n• There is an illegal IP address setting.\n• A read operation failed.\n• The IP address obtained from the BOOTP server is inconsistent.\n• The IP address obtained from the DHCP server is inconsistent.\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_IPAdrDupErr\nMeaning IP Address Duplication Error Global/local Global\nFunction NX-series CPU Units: Indicates that the same IP address is assigned to more than one node for the communica-\ntions port 1.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that the same IP address is assigned to more than one node.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_IPAdrDupErr\nMeaning Port1 IP Address Duplication Error Global/local Global\nFunction Indicates that the same IP address is assigned to more than one node for the communications port 1.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_IPAdrDupErr\nMeaning Port2 IP Address Duplication Error Global/local Global\nFunction Indicates that the same IP address is assigned to more than one node for the communications port 2.\nTRUE: Duplication occurred.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-46 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_DNSCfgErr*1\nMeaning DNS Setting Error Global/local Global\nFunction Indicates that the DNS or hosts settings are incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n*1. With the NJ-series CPU Unit, this variable can be used with the unit version 1.11 or later.\nVariable name _EIP_BootpErr\nMeaning BOOTP Server Error Global/local Global\nFunction NX-series CPU Units: Indicates that a BOOTP server connection failure occurred on the communications port 1.\nTRUE: There was a failure to connect to the BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or BOOTP is enabled and an IP address was normally obtained from the\nBOOTP server.\nNJ-series CPU Units: Indicates that a BOOTP server connection failure occurred.\nTRUE: There was a failure to connect to the BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or BOOTP is enabled and an IP address was normally obtained from the\nBOOTP server.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_BootpErr\nMeaning Port1 BOOTP Server Error Global/local Global\nFunction Indicates that a BOOTP server connection failure occurred on the communications port 1.\nTRUE: There was a failure to connect to the BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or BOOTP is enabled and an IP address was normally obtained from the\nBOOTP server.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_BootpErr\nMeaning Port2 BOOTP Server Error Global/local Global\nFunction Indicates that a BOOTP server connection failure occurred on the communications port 2.\nTRUE: There was a failure to connect to the BOOTP server (timeout).\nFALSE: The BOOTP is not enabled, or BOOTP is enabled and an IP address was normally obtained from the\nBOOTP server.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-47\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_DhcpErr\nMeaning DHCP Server Error Global/local Global\nFunction Indicates that a DHCP server connection failure occurred on the communications port 1.\nTRUE: There was a failure to connect to the DHCP server (timeout).\nFALSE: The DHCP is not enabled, or DHCP is enabled and an IP address was normally obtained from the DHCP\nserver.\nNoteYou can use this system-defined variable only for the NX502 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_DhcpErr\nMeaning Port1 DHCP Server Error Global/local Global\nFunction Indicates that a DHCP server connection failure occurred on the communications port 1.\nTRUE: There was a failure to connect to the DHCP server (timeout).\nFALSE: The DHCP is not enabled, or DHCP is enabled and an IP address was normally obtained from the DHCP\nserver.\nNoteYou can use this system-defined variable only for the NX502 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_DhcpErr\nMeaning Port2 DHCP Server Error Global/local Global\nFunction Indicates that a DHCP server connection failure occurred on the communications port 2.\nTRUE: There was a failure to connect to the DHCP server (timeout).\nFALSE: The DHCP is not enabled, or DHCP is enabled and an IP address was normally obtained from the DHCP\nserver.\nNoteYou can use this system-defined variable only for the NX502 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_IPRTblErr\nMeaning IP Route Table Error Global/local Global\nFunction NX-series CPU Units: Indicates that the default gateway settings or IP router table settings are incorrect. Or, a\nread operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the IP router table or hosts settings are incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-48 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_IdentityErr\nMeaning Identity Error Global/local Global\nFunction NX-series CPU Units: Indicates that the identity information for CIP communications 1 (which you cannot over-\nwrite) is incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the identity information (which you cannot overwrite) is incorrect. Or, a read\noperation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_IdentityErr\nMeaning CIP Communications1 Identity Error Global/local Global\nFunction Indicates that the identity information for CIP communications 1 (which you cannot overwrite) is incorrect. Or, a\nread operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_IdentityErr\nMeaning CIP Communications2 Identity Error Global/local Global\nFunction Indicates that the identity information for CIP communications 2 (which you cannot overwrite) is incorrect. Or, a\nread operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TDLinkCfgErr\nMeaning Tag Data Link Setting Error Global/local Global\nFunction NX-series CPU Units: Indicates that the tag data link settings for CIP communications 1 are incorrect. Or, a read\noperation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNJ-series CPU Units: Indicates that the tag data link settings are incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-49\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TDLinkCfgErr\nMeaning CIP Communications1 Tag Data Link Setting Global/local Global\nError\nFunction Indicates that the tag data link settings for CIP communications 1 are incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkCfgErr\nMeaning CIP Communications2 Tag Data Link Setting Global/local Global\nError\nFunction Indicates that the tag data link setting for CIP communications 2 are incorrect. Or, a read operation failed.\nTRUE: Setting incorrect or read failed.\nFALSE: Normal\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TDLinkOpnErr\nMeaning Tag Data Link Connection Failed Global/local Global\nFunction NX-series CPU Units: Indicates that establishing a tag data link connection for CIP communications 1 failed.\nTRUE: Establishing a tag data link connection failed due to one of the following causes.\n• The information registered for a target node in the tag data link parameters is different from the actual node\ninformation.\n• There was no response from the remote node.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that establishing a tag data link connection failed.\nTRUE: Establishing a tag data link connection failed due to one of the following causes.\n• The information registered for a target node in the tag data link parameters is different from the actual node\ninformation.\n• There was no response from the remote node.\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-50 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TDLinkOpnErr\nMeaning CIP Communications1 Tag Data Link Connec- Global/local Global\ntion Failed\nFunction Indicates that establishing a tag data link connection for CIP communications 1 failed.\nTRUE: Establishing a tag data link connection failed due to one of the following causes.\n• The information registered for a target node in the tag data link parameters is different from the actual node\ninformation.\n• There was no response from the remote node.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkOpnErr\nMeaning CIP Communications2 Tag Data Link Connec- Global/local Global\ntion Failed\nFunction Indicates that establishing a tag data link connection for CIP communications 2 failed.\nTRUE: Establishing a tag data link connection failed due to one of the following causes.\n• The information registered for a target node in the tag data link parameters is different from the actual node\ninformation.\n• There was no response from the remote node.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TDLinkErr\nMeaning Tag Data Link Communications Error Global/local Global\nFunction NX-series CPU Units: Indicates that a timeout occurred in a tag data link connection for CIP communications 1.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that a timeout occurred in a tag data link connection.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-51\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TDLinkErr\nMeaning CIP Communications1 Tag Data Link Communi- Global/local Global\ncations Error\nFunction Indicates that a timeout occurred in a tag data link connection for CIP communications 1.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkErr\nMeaning CIP Communications2 Tag Data Link Communi- Global/local Global\ncations Error\nFunction Indicates that a timeout occurred in a tag data link connection for CIP communications 2.\nTRUE: A timeout occurred.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TagAdrErr\nMeaning Tag Name Resolution Error Global/local Global\nFunction NX-series CPU Units: Indicates that the tag resolution for CIP communications 1 failed (i.e., the address could not\nbe identified from the tag name).\nTRUE: Tag resolution failed (i.e., the address could not be identified from the tag name). The following causes are\npossible.\n• The size of the network variable is different from the tag settings.\n• The I/O direction that is set in the tag data link settings does not agree with the I/O direction of the variable in\nthe CPU Unit.\n• There is no network variable in the CPU Unit that corresponds to the tag setting.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that tag name resolution failed (i.e., the address could not be identified from the\ntag name).\nTRUE: Tag resolution failed (i.e., the address could not be identified from the tag name). The following causes are\npossible.\n• The size of the network variable is different from the tag settings.\n• The I/O direction that is set in the tag data link settings does not agree with the I/O direction of the variable in\nthe CPU Unit.\n• There is no network variable in the CPU Unit that corresponds to the tag setting.\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-52 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TagAdrErr\nMeaning CIP Communications1 Tag Name Resolution Global/local Global\nError\nFunction Indicates that the tag resolution for CIP communications 1 failed (i.e., the address could not be identified from the\ntag name).\nTRUE: Tag resolution failed (i.e., the address could not be identified from the tag name). The following causes are\npossible.\n• The size of the network variable is different from the tag settings.\n• The I/O direction that is set in the tag data link settings does not agree with the I/O direction of the variable in\nthe CPU Unit.\n• There is no network variable in the CPU Unit that corresponds to the tag setting.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TagAdrErr\nMeaning CIP Communications2 Tag Name Resolution Global/local Global\nError\nFunction Indicates that the tag resolution for CIP communications 2 failed (i.e., the address could not be identified from the\ntag name).\nTRUE: Tag resolution failed (i.e., the address could not be identified from the tag name). The following causes are\npossible.\n• The size of the network variable is different from the tag settings.\n• The I/O direction that is set in the tag data link settings does not agree with the I/O direction of the variable in\nthe CPU Unit.\n• There is no network variable in the CPU Unit that corresponds to the tag setting.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_MultiSwONErr\nMeaning Multiple Switches ON Error Global/local Global\nFunction NX-series CPU Units: Indicates that more than one switch turned ON at the same time in CIP communications 1.\nTRUE: More than one data link start/stop switch changed to TRUE at the same time.\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that more than one switch turned ON at the same time\nTRUE: More than one data link start/stop switch changed to TRUE at the same time.\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-53\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_MultiSwONErr\nMeaning CIP Communications1 Multiple Switches ON Global/local Global\nError\nFunction Indicates that more than one switch turned ON at the same time in CIP communications 1.\nTRUE: More than one data link start/stop switch changed to TRUE at the same time.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_MultiSwONErr\nMeaning CIP Communications2 Multiple Switches ON Global/local Global\nError\nFunction Indicates that more than one switch turned ON at the same time in CIP communications 2.\nTRUE: More than one data link start/stop switch changed to TRUE at the same time.\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TcpAppCfgErr\nMeaning TCP Application Setting Error Global/local Global\nFunction TRUE: At least one of the set values for a TCP application (FTP, NTP, SNMP) is incorrect. Or, a read operation\nfailed.\nFALSE: Normal\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_NTPSrvErr\nMeaning NTP Server Connection Error Global/local Global\nFunction TRUE: The NTP client failed to connect to the server (timeout).\nFALSE: NTP is not set. Or, NTP is set and the connection was successful.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_DNSSrvErr\nMeaning DNS Server Connection Error Global/local Global\nFunction TRUE: The DNS client failed to connect to the server (timeout).\nFALSE: DNS is not enabled. Or, DNS is enabled and the connection was successful.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Global\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-54 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\n Functional Classification: EtherNet/IP Communications Status\nVariable name _EIP_EtnOnlineSta\nMeaning Online Global/local Global\nFunction NX-series CPU Units: Indicates that the built-in EtherNet/IP port's communications can be used via the communi-\ncations port 1 (that is, the link is ON, IP address is defined, and there are no errors.)\nTRUE: The built-in EtherNet/IP port’s communications can be used.\nFALSE: The built-in EtherNet/IP port’s communications is disabled due to an error in initial processing, restart\nprocessing, or link OFF status.\nNJ-series CPU Units: Indicates that the built-in EtherNet/IP port's communications can be used via the communi-\ncations port (that is, the link is ON and IP address is defined, and there are no errors.)\nTRUE: The built-in EtherNet/IP port’s communications can be used.\nFALSE: The built-in EtherNet/IP port’s communications is disabled due to an error in initial processing, restart\nprocessing, or link OFF status.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_EtnOnlineSta\nMeaning Port1 Online Global/local Global\nFunction Indicates that the built-in EtherNet/IP port's communications can be used via the communications port 1 (that is,\nthe link is ON, IP address is defined, and there are no errors.)\nTRUE: The built-in EtherNet/IP port’s communications can be used.\nFALSE: The built-in EtherNet/IP port’s communications is disabled due to an error in initial processing, restart\nprocessing, or link OFF status.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_EtnOnlineSta\nMeaning Port2 Online Global/local Global\nFunction Indicates that the built-in EtherNet/IP port's communications can be used via the communications port 2 (that is,\nthe link is ON, IP address is defined, and there are no errors.)\nTRUE: The built-in EtherNet/IP port’s communications can be used.\nFALSE: The built-in EtherNet/IP port’s communications is disabled due to an error in initial processing, restart\nprocessing, or link OFF status.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-55\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_TDLinkRunSta\nMeaning Tag Data Link Communications Status Global/local Global\nFunction NX-series CPU Units: Indicates that at least one connection is in normal operation in CIP communications 1.\nTRUE: Normal operation\nFALSE: Other than the above.\nNJ-series CPU Units: Indicates that at least one connection is in normal operation.\nTRUE: Normal operation\nFALSE: Other than the above.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_TDLinkRunSta\nMeaning CIP Communications1 Tag Data Link Communi- Global/local Global\ncations Status\nFunction Indicates that at least one connection is in normal operation in CIP communications 1.\nTRUE: Normal operation\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkRunSta\nMeaning CIP Communications2 Tag Data Link Communi- Global/local Global\ncations Status\nFunction Indicates that at least one connection is in normal operation in CIP communications 2.\nTRUE: Normal operation\nFALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TDLinkAllRunSta\nMeaning All Tag Data Link Communications Status Global/local Global\nFunction NX-series CPU Units: Indicates that all tag data links are communicating in CIP communications 1.\nTRUE: Tag data links are communicating in all connections as the originator.\nFALSE: An error occurred in at least one connection.\nNJ-series CPU Units: Indicates that all tag data links are communicating.\nTRUE: Tag data links are communicating in all connections as the originator.\nFALSE: An error occurred in at least one connection.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-56 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TDLinkAllRunSta\nMeaning CIP Communications1 All Tag Data Link Com- Global/local Global\nmunications Status\nFunction Indicates that all tag data links are communicating in CIP communications 1.\nTRUE: Tag data links are communicating in all connections as the originator.\nFALSE: An error occurred in at least one connection.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkAllRunSta\nMeaning CIP Communications2 All Tag Data Link Com- Global/local Global\nmunications Status\nFunction Indicates that all tag data links are communicating in CIP communications 2.\nTRUE: Tag data links are communicating in all connections as the originator.\nFALSE: An error occurred in at least one connection.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_RegTargetSta[255]\nMeaning Registered Target Node Information Global/local Global\nFunction NX-series CPU Units: Gives a list of nodes for which EtherNet/IP connections are registered for CIP communica-\ntions 1.\nThis variable is valid only when the EtherNet/IP port is the originator.\nArray[x] is TRUE: The connection to the node with a target node ID of x is registered.\nArray[x] is FALSE: The connection to the node with a target node ID of x is not registered.\nNJ-series CPU Units: Gives a list of nodes for which EtherNet/IP connections are registered.\nThis variable is valid only when the EtherNet/IP port is the originator.\nArray[x] is TRUE: The connection to the node with a target node ID of x is registered.\nArray[x] is FALSE: The connection to the node with a target node ID of x is not registered.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_RegTargetSta[255]\nMeaning CIP Communications1 Registered Target Node Global/local Global\nInformation\nFunction Gives a list of nodes for which EtherNet/IP connections are registered for CIP communications 1.\nThis variable is valid only when the EtherNet/IP port is the originator.\nArray[x] is TRUE: The connection to the node with a target node ID of x is registered.\nArray[x] is FALSE: The connection to the node with a target node ID of x is not registered.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-57\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_RegTargetSta[255]\nMeaning CIP Communications2 Registered Target Node Global/local Global\nInformation\nFunction Gives a list of nodes for which EtherNet/IP connections are registered for CIP communications 2.\nThis variable is valid only when the EtherNet/IP port is the originator.\nArray[x] is TRUE: The connection to the node with a target node ID of x is registered.\nArray[x] is FALSE: The connection to the node with a target node ID of x is not registered.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_EstbTargetSta[255]\nMeaning Normal Target Node Information Global/local Global\nFunction NX-series CPU Units: Gives a list of nodes that have normally established EtherNet/IP connections for CIP com-\nmunications 1.\nArray[x] is TRUE: The connection to the node with a target node ID of x was established normally.\nArray[x] is FALSE: The connection to the node with a target node ID of x was not established, or an error occur-\nred.\nNJ-series CPU Units: Gives a list of nodes that have normally established EtherNet/IP connections.\nArray[x] is TRUE: The connection to the node with a target node ID of x was established normally.\nArray[x] is FALSE: The connection to the node with a target node ID of x was not established, or an error occur-\nred.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_EstbTargetSta[255]\nMeaning CIP Communications1 Normal Target Node In- Global/local Global\nformation\nFunction Gives a list of nodes that have normally established EtherNet/IP connections for CIP communications 1.\nArray[x] is TRUE: The connection to the node with a target node ID of x was established normally.\nArray[x] is FALSE: The connection to the node with a target node ID of x was not established, or an error occur-\nred.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-58 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_EstbTargetSta[255]\nMeaning CIP Communications2 Normal Target Node In- Global/local Global\nformation\nFunction Gives a list of nodes that have normally established EtherNet/IP connections for CIP communications 2.\nArray[x] is TRUE: The connection to the node with a target node ID of x was established normally.\nArray[x] is FALSE: The connection to the node with a target node ID of x was not established, or an error occur-\nred.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TargetPLCModeSta[255]\nMeaning Target PLC Operating Mode Global/local Global\nFunction NX-series CPU Units: Shows the operating status of the target node Controllers that are connected for CIP com-\nmunications 1, with the EtherNet/IP port as the originator.\nThe array elements are valid only when the corresponding Normal Target Node Information is TRUE. If the corre-\nsponding Normal Target Node Information is FALSE, it indicates the previous operating status.\nArray[x] is TRUE: This is the operating state of the target Controller with a node address of x.\nArray[x] is FALSE: Other than the above.\nNJ-series CPU Units: Shows the operating status of the target node Controllers that are connected with the Ether-\nNet/IP port as the originator.\nThe array elements are valid only when the corresponding Normal Target Node Information is TRUE. If the corre-\nsponding Normal Target Node Information is FALSE, it indicates the previous operating status.\nArray[x] is TRUE: This is the operating state of the target Controller with a node address of x.\nArray[x] is FALSE: Other than the above.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_TargetPLCModeSta[255]\nMeaning CIP Communications1 Target PLC Operating Global/local Global\nMode\nFunction Shows the operating status of the target node Controllers that are connected for CIP communications 1, with the\nEtherNet/IP port as the originator.\nThe array elements are valid only when the corresponding Normal Target Node Information is TRUE. If the corre-\nsponding Normal Target Node Information is FALSE, it indicates the previous operating status.\nArray[x] is TRUE: This is the operating state of the target Controller with a node address of x.\nArray[x] is FALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-59\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_TargetPLCModeSta[255]\nMeaning CIP Communications2 Target PLC Operating Global/local Global\nMode\nFunction Shows the operating status of the target node Controllers that are connected for CIP communications 2, with the\nEtherNet/IP port as the originator.\nThe array elements are valid only when the corresponding Normal Target Node Information is TRUE. If the corre-\nsponding Normal Target Node Information is FALSE, it indicates the previous operating status.\nArray[x] is TRUE: This is the operating state of the target Controller with a node address of x.\nArray[x] is FALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TargetPLCErr[255]\nMeaning Target PLC Error Information Global/local Global\nFunction NX-series CPU Units: Shows the error status (logical OR of fatal and non-fatal errors) of the target node Control-\nlers that are connected for CIP communications 1, with the EtherNet/IP ports as the originator. The array ele-\nments are valid only when the corresponding Normal Target Node Information is TRUE. The immediately preced-\ning value is retained if this variable is FALSE.\nArray[x] is TRUE: A fatal or non-fatal error occurred in the target Controller with a target node ID of x.\nArray[x] is FALSE: Other than the above.\nNJ-series CPU Units: Shows the error status (logical OR of fatal and non-fatal errors) of the target node Control-\nlers that are connected with the EtherNet/IP ports as the originator. The array elements are valid only when the\ncorresponding Normal Target Node Information is TRUE. The immediately preceding value is retained if this vari-\nable is FALSE.\nArray[x] is TRUE: A fatal or non-fatal error occurred in the target Controller with a target node ID of x.\nArray[x] is FALSE: Other than the above.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_TargetPLCErr[255]\nMeaning CIP Communications1 Target PLC Error Infor- Global/local Global\nmation\nFunction Shows the error status (logical OR of fatal and non-fatal errors) of the target node Controllers that are connected\nfor CIP communications 1, with the EtherNet/IP ports as the originator. The array elements are valid only when\nthe corresponding Normal Target Node Information is TRUE. The immediately preceding value is retained if this\nvariable is FALSE.\nArray[x] is TRUE: A fatal or non-fatal error occurred in the target Controller with a target node ID of x.\nArray[x] is FALSE: Other than the above.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-60 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_TargetPLCErr[255]\nMeaning CIP Communications2 Target PLC Error Infor- Global/local Global\nmation\nFunction Shows the error status (logical OR of fatal and non-fatal errors) of the target node Controllers that are connected\nfor CIP communications 2, with the EtherNet/IP ports as the originator. The array elements are valid only when\nthe corresponding Normal Target Node Information is TRUE. The immediately preceding value is retained if this\nvariable is FALSE.\nArray[x] is TRUE: A fatal or non-fatal error occurred in the target Controller with a target node ID of x.\nArray[x] is FALSE: Other than the above.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TargetNodeErr[255]\nMeaning Target Node Error Information Global/local Global\nFunction NX-series CPU Units: Indicates that the connection for the Registered Target Node Information for CIP communi-\ncations 1 was not established or that an error occurred in the target Controller.\nThe array elements are valid only when the Registered Target Node Information is TRUE.\nArray[x] is TRUE: A connection was not normally established with the target node for a target node ID of x (the\nRegistered Target Node Information is TRUE and the Normal Target Node Information is FALSE), or a connection\nwas established with the target node but an error occurred in the target Controller.\nArray[x] is FALSE: The target node is not registered for a target node ID of x (the Registered Target Node Infor-\nmation is FALSE), or a connection was normally established with the target node (the Registered Target Node\nInformation is TRUE and the Normal Target Node Information is TRUE). An error occurred in the target Controller\n(the Target PLC Error Information is TRUE).\nNJ-series CPU Units: Indicates that the connection for the Registered Target Node Information was not establish-\ned or that an error occurred in the target Controller.\nThe array elements are valid only when the Registered Target Node Information is TRUE.\nArray[x] is TRUE: A connection was not normally established with the target node for a target node ID of x (the\nRegistered Target Node Information is TRUE and the Normal Target Node Information is FALSE), or a connection\nwas established with the target node but an error occurred in the target Controller.\nArray[x] is FALSE: The target node is not registered for a target node ID of x (the Registered Target Node Infor-\nmation is FALSE), or a connection was normally established with the target node (the Registered Target Node\nInformation is TRUE and the Normal Target Node Information is TRUE). An error occurred in the target Controller\n(the Target PLC Error Information is TRUE).\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-61\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP1_TargetNodeErr[255]\nMeaning CIP Communications1 Target Node Error Infor- Global/local Global\nmation\nFunction Indicates that the connection for the Registered Target Node Information for CIP communications 1 was not es-\ntablished or that an error occurred in the target Controller.\nThe array elements are valid only when the Registered Target Node Information is TRUE.\nArray[x] is TRUE: A connection was not normally established with the target node for a target node ID of x (the\nRegistered Target Node Information is TRUE and the Normal Target Node Information is FALSE), or a connection\nwas established with the target node but an error occurred in the target Controller.\nArray[x] is FALSE: The target node is not registered for a target node ID of x (the Registered Target Node Infor-\nmation is FALSE), or a connection was normally established with the target node (the Registered Target Node\nInformation is TRUE and the Normal Target Node Information is TRUE). An error occurred in the target Controller\n(the Target PLC Error Information is TRUE).\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TargetNodeErr[255]\nMeaning CIP Communications2 Target Node Error Infor- Global/local Global\nmation\nFunction Indicates that the connection for the Registered Target Node Information for CIP communications 2 was not es-\ntablished or that an error occurred in the target Controller.\nThe array elements are valid only when the Registered Target Node Information is TRUE.\nArray[x] is TRUE: A connection was not normally established with the target node for a target node ID of x (the\nRegistered Target Node Information is TRUE and the Normal Target Node Information is FALSE), or a connection\nwas established with the target node but an error occurred in the target Controller.\nArray[x] is FALSE: The target node is not registered for a target node ID of x (the Registered Target Node Infor-\nmation is FALSE), or a connection was normally established with the target node (the Registered Target Node\nInformation is TRUE and the Normal Target Node Information is TRUE). An error occurred in the target Controller\n(the Target PLC Error Information is TRUE).\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type ARRAY [0..255] OF BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_NTPResult\nMeaning NTP Operation Information Global/local Global\nFunction Use the GetNTPStatus instruction to read the NTP operation information from the user program.\nDirect access is not possible.\nData type _sNTP_RESULT Range of values ---\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Not possible. Related in- You can read the contents of this variable with the GetNTPStatus instruction.\ngram structions\n3-62 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP_NTPResult Member name .ExecTime\nMeaning NTP Last Operation Time Global/local Global\nFunction Gives the last time that NTP processing ended normally.\nThe time that was obtained from the NTP server is stored when the time is obtained normally.\nThe time is not stored if it is not obtained from the NTP server normally.\nNoteDo not use this variable in the user program. There may be a delay in updating it. Use this vari-\nable only to access status through communications from an external device.\nData type DATE_AND_TIME Range of values Depends on data type.\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Not possible. Related in- You can read the contents of this variable with the GetNTPStatus instruction.\ngram structions\nVariable name _EIP_NTPResult Member name .ExecNormal\nMeaning NTP Operation Result Global/local Global\nFunction This variable shows if the NTP operation ended normally.\nTRUE: Indicates an NTP normal end.\nFALSE:Indicates that NTP operation ended in an error or has not been executed even once.\nNoteDo not use this variable in the user program. There may be a delay in updating it. Use this vari-\nable only to access status through communications from an external device.\nData type BOOL Range of values TRUE or FALSE\nR/W access R Retained Not retained. Network Publish Published.\nUsage in user pro- Not possible. Related in- You can read the contents of this variable with the GetNTPStatus instruction.\ngram structions\n Functional Classification: EtherNet/IP Communications Switches\nVariable name _EIP_TDLinkStartCmd\nMeaning Tag Data Link Communications Start Switch Global/local Global\nFunction NX-series CPU Units: Change this variable to TRUE to start tag data links for CIP communications 1.\nIt automatically changes back to FALSE after tag data link operation starts.\nNJ-series CPU Units: Change this variable to TRUE to start tag data links.\nIt automatically changes back to FALSE after tag data link operation starts.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_TDLinkStartCmd\nMeaning CIP Communications1 Tag Data Link Communi- Global/local Global\ncations Start Switch\nFunction Change this variable to TRUE to start tag data links for CIP communications 1.\nIt automatically changes back to FALSE after tag data link operation starts.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 3-63\nbles\n3-3\nSpecifications\nfor\nIndividual\nSystem-defined\nVaria-\n3\n3-3-1\nEtherNet/IP\nFunction\nModule,\nCategory\nName:\n_EIP\n3 System-defined Variables Related to the Built-in EtherNet/IP Port\nVariable name _EIP2_TDLinkStartCmd\nMeaning CIP Communications2 Tag Data Link Communi- Global/local Global\ncations Start Switch\nFunction Change this variable to TRUE to start tag data links for CIP communications 2.\nIt automatically changes back to FALSE after tag data link operation starts.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP_TDLinkStopCmd\nMeaning Tag Data Link Communications Stop Switch Global/local Global\nFunction NX-series CPU Units: Change this variable to TRUE to stop tag data links for CIP communications 1.\nIt automatically changes back to FALSE after tag data link operation stops.\nNJ-series CPU Units: Change this variable to TRUE to stop tag data links.\nIt automatically changes back to FALSE after tag data link operation stops.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP1_TDLinkStopCmd\nMeaning CIP Communications1 Tag Data Link Communi- Global/local Global\ncations Stop Switch\nFunction Change this variable to TRUE to stop tag data links for CIP communications 1.\nIt automatically changes back to FALSE after tag data link operation stops.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nNoteYou can use this system-defined variable only for NX-series CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\nVariable name _EIP2_TDLinkStopCmd\nMeaning CIP Communications2 Tag Data Link Communi- Global/local Global\ncations Stop Switch\nFunction Change this variable to TRUE to stop tag data links for CIP communications 2.\nIt automatically changes back to FALSE after tag data link operation stops.\nNoteDo not force this switch to change to FALSE from the user program or from the Sysmac Studio.\nIt changes to FALSE automatically.\nNoteYou can use this system-defined variable only for the NX701 CPU Units, NX502 CPU Units,\nand NX102 CPU Units.\nData type BOOL Range of values TRUE or FALSE\nR/W access RW Retained Not retained. Network Publish Published.\nUsage in user pro- Possible. Related in- ---\ngram structions\n3-64 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4\nSysmac Studio Settings for the\nBuilt-in EtherNet/IP Port\n4-1 TCP/IP Settings Display.................................................................................4-2\n4-2 LINK Settings Display..................................................................................4-12\n4-3 FTP Settings Display...................................................................................4-14\n4-4 NTP Settings Display...................................................................................4-15\n4-5 SNMP Settings Display................................................................................4-17\n4-6 SNMP Trap Settings Display.......................................................................4-19\n4-7 CIP Settings Display....................................................................................4-21\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-1\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-1 TCP/IP Settings Display\nFor NX701 CPU Units For NX502 CPU Units For NX102 CPU Units\nFor NX1P2 CPU Units For NJ-series CPU Units\n IP Address - Port 1 (NX-series CPU Unit)\nSet an IP address for the built-in EtherNet/IP port 1.\n4-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nIP address setting Select one of the following IP address setting methods for Fixed setting\nmethod the built-in EtherNet/IP port 1.\n• Fixed setting\n• Obtain from BOOTP server.\n• Fix at the IP address obtained from BOOTP server.\n• Obtain from DHCP server.*3\nIP address*1 Set the IP address for the built-in EtherNet/IP port 1. *2 192.168.250.1\nSubnet mask*2 Set the subnet mask for the built-in EtherNet/IP port 1. 255.255.255.0\n*1. These settings are required if you set IP address setting method to Fixed setting.\n*2. Refer to 5-1-2 Built-in EtherNet/IP Port IP Address Settings on page 5-4 for details on setting IP ad-\ndresses.\n*3. This setting method can be selected for NX502 CPU Units only.\n IP Address - Port 2 (NX701, NX502, and NX102 CPU Units)\nSet an IP address for the built-in EtherNet/IP port 2.\nSetting Description Default\nUse Port 2 Select the check box to use the built-in EtherNet/IP port 2. Selected\n(use)\nIP address setting Select one of the following IP address setting methods for the built-in Fixed setting\nmethod EtherNet/IP port 2.\n• Fixed setting\n• Obtain from BOOTP server.\n• Fix at the IP address obtained from BOOTP server.\n• Obtain from DHCP server.*3\nIP address*1 Set the IP address for the built-in EtherNet/IP port 2. *2 192.168.251.1\nSubnet mask*2 Set the subnet mask for the built-in EtherNet/IP port 2. 255.255.255.0\n*1. These settings are required if you select Fixed setting for the IP address setting method.\n*2. Refer to 5-1-2 Built-in EtherNet/IP Port IP Address Settings on page 5-4 for details on setting IP ad-\ndresses.\n*3. This setting method can be selected for NX502 CPU Units only.\nPrecautions for Correct Use\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, you cannot set IP addresses\nthat make two built-in EtherNet/IP ports belong to the same network.\n IP Address - Internal Network (NX502 CPU Unit)\nWhen the NX-series EtherNet/IP Unit is used, set the IP address of the internal communications\nnetwork between the CPU Unit and the NX-series EtherNet/IP Unit.\nMake these settings when the network address of the internal communications network is same as\nthe network addresses of the built-in EtherNet/IP port on the CPU Unit and the EtherNet/IP port on\nthe NX-series EtherNet/IP Unit.\nThe settings that you set are as follows.\nSetting Description Default\nIP Address Set the IP address of the internal communications network. 192.168.254.0\nSet all bits after the bit to be masked to 0.*1*2\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-3\n4-1\nTCP/IP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nMask Set the subnet mask for the internal communications network. 255.255.255.0\nSet the bit to be masked to 0.\nSet within the range of 192.0.0.0 to 255.255.255.0.\n*1. For example, if the Mask is set to 255.255.255.0 to mask the fourth octet of the IP address, set the\nfourth octet of the IP Address to all zeros, as in 192.168.255.0.\nFor example, if the Mask is set to 255.255.0.0 to mask the third and later octets of the IP address, set\nthe third and later octets of the IP Address to all zeros, as in 192.168.0.0.\n*2. If two NX-series EtherNet/IP Units are mounted to an NX502 CPU Unit with default values for both IP\nAddress and Mask, the IP address of each unit will be as follows.\n• NX502 CPU Unit: 192.168.254.100\n• NX-series EtherNet/IP Unit (Unit number 1): 192.168.254.1\n• NX-series EtherNet/IP Unit (Unit number 2): 192.168.254.2\nPrecautions for Correct Use\nAn IP address whose internal communications network is the same network as the following\ncannot be set.\n• Built-in EtherNet/IP port on the CPU Unit\n• EtherNet/IP port on the NX-series EtherNet/IP Unit\n IP Address (NJ-series CPU Unit)\nSetting Description Default\nIP address setting Select one of the following IP address setting methods for the Fixed setting\nmethod built-in EtherNet/IP port. *1\n• Fixed setting\n• Obtain from BOOTP server.\n• Fix at the IP address obtained from BOOTP server.\nIP address*2 Set the IP address for the built-in EtherNet/IP port. 192.168.250.1\nSubnet mask*2 Set the subnet mask for the built-in EtherNet/IP port. 255.255.255.0\nDefault gateway*3 Set the IP address of the default gateway for the built-in Ether- None\nNet/IP port.\nThis setting is not required when the default gateway is not used.\n*1. Refer to 5-1-2 Built-in EtherNet/IP Port IP Address Settings on page 5-4 for details on setting IP ad-\ndresses.\n*2. These settings are required if you select Fixed setting for the IP address setting method.\n*3. This setting is valid if you select Fixed setting for the IP address setting method.\n Default Gateway (NX-series CPU Unit)\nSetting Description Default\nDefault gateway*1 Set the IP address of the default gateway for the built-in Ether- None\nNet/IP port. *2\nThis setting is not required when the default gateway is not used.\n*1. If you select Obtain from BOOTP server or Fix at the IP address obtained from BOOTP server for\nthe IP address setting method, the default gateway obtained from a BOOTP server is enabled.\n*2. For NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, even if you are using both of port 1\nand port 2, you can set the default gateway for only one of the ports.\n4-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n Operation at IP Address Duplication\nSetting Description Default\nUse of duplicated IP ad- When you set an IP address for the built-in EtherNet/IP port and Stop\ndress find an IP address conflict with another node, select whether to\nstop the use of the IP address.\n• Stop\nIf the IP address conflict is not resolved for a certain length of\ntime, the use of the IP address is stopped, and an IP Address\nDuplication Error will occur.\n• Do not stop*1\nIP Address Duplication Error does not occur and you continue\nto use the IP address that you set. This setting is used if you\nwant to avoid that communications are stopped because the\nsame IP address is assigned to more than one node.\n*1. For systems that use OPC UA to connect to an information system network, it is recommended that you\nset this to Do not stop.\nPrecautions for Correct Use\nIf this setting is Do not stop, it is not notified that the same IP address is assigned to more than\none node to the user. Also, if the same IP address is assigned to more than one node while this\nsetting is Do not stop, the communications may become unstable, such as being temporarily\nunavailable. If it is unacceptable for the communication to be unstable, detect that the same IP\naddress is assigned to more than one node to the remote node.\nVersion Information\nThe setting for the Use of duplicated IP address can be used with the CPU Units that support\nOPC UA, and the Sysmac Studio. Refer to the NJ/NX-series CPU Unit OPC UA User’s Manual\n(Cat. No. W588) for information on the models and unit versions of the CPU Units that support\nOPC UA, and the Sysmac Studio version.\n Host Name(NX502 CPU Unit)\nSetting Description Default\nHost Name Set the host name for the local Unit. The local host name can be None*3\nset for each Unit. The set host name is set to sysName of the\nsystem group and lldpLocSysName of the lldp group in the MIB\n(Management Information Base). *1*2\n(Single-byte alphanumeric characters, dots, and hyphens: 63\ncharacters max.)\n*1. Since the local host name identifies the Unit, set the name so that it does not use the same name in the\nsame network.\n*2. Refer to 13-1-4 MIB Specifications on page 13-4 for details on the MIB.\n*3. If you do not set the local host name, the model of the Unit will be the local host name.\n DNS\nSetting Description Default\nUse/ When you specify a host name for CIP communications instruc- Do not use\nDo not use DNS tions, socket instructions or NTP server settings, select the Use\nOption if you use DNS for resolving host name.\nA DNS server is required to use DNS.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-5\n4-1\nTCP/IP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nPriority DNS server*1 Set the IP address of the DNS server. None\nYou can set priority and secondary IP addresses.\nSecondary DNS server None\nDomain name*1 Set the domain name of the domain to which the built-in Ether- None\nNet/IP port belongs.\n(Single-byte alphanumeric characters, dots, and hyphens: 48\ncharacters max.)\n*1. These settings are required if you select the Use Option for DNS.\n Host Name - IP Address\nSetting Description Default\nHost Name Addresses are converted according to this setting when a host None\nname is used to specify remote communications nodes.\nHost names can be set whether DNS is used or not.\nYou can set up to six host names.\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric charac-\nters between dots.)\nIP Address Set the IP address of the registered host name. None\n Keep Alive\nSetting Description Default\nKeep Alive Set whether to use the remote node Keep Alive function of con- Use\nnected servers and clients (such as socket service, FTP server,\nSysmac Studio, and FINS/TCP) for each connection number.\nIf the Use Option is selected for Keep Alive and no communica-\ntions are performed with the remote node for the Keep Alive\nmonitoring time, transmission of Keep Alive packets is started.\nIf the remote node does not respond beyond the following, the\nconnection is disconnected.\n• For NX502\nKeepAlive packet transmission + resending for 2 seconds × 5\ntimes*2\n• Others:\nKeepAlive packet transmission + resending for 5 seconds × 5\ntimes*1\nThe connection to the remote node is left open if the power sup-\nply to the remote node is turned OFF without warning. Select the\nUse Option for Keep Alive wherever possible.\n• Use\n• Do not use\nKeep Alive monitoring This is a set period of time before the transmission of Keep Alive 300\ntime packets is started.\nSetting range: 1 to 65,535 (seconds)\n4-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nLinger option Set whether to specify the Linger Option for connections to Do not specify\nFINS/TCP or socket services.\nIf the Linger Option is specified, the port number is immediately\nopened even before the port number is released after the socket\ncloses (approx. 1 minute).\n• Specify\n• Do not specify\n*1. If the remote node does not respond, the connection is disconnected after the Keep Alive monitoring\ntime + 30 seconds.\n*2. If the remote node does not respond, the connection is disconnected after the Keep Alive monitoring\ntime + 12 seconds.\n IP Router Table\nSetting Description Default\nDestination IP Address Set these settings when the built-in EtherNet/IP port is used for None\nDestination Mask IP Ad- tag data links or CIP message communications with nodes on\ndress other IP network segments via an IP router. Accordingly, set\nthese settings when you use an NX-series CPU Unit as an IP\nGateway Address None\nrouter using the IP routing function for the built-in EtherNet/IP\nport.\nYou can set up to 128 combinations of an IP address and a gate-\nway address for an NX701 CPU Unit or an NX502 CPU Unit, up\nto 64 combinations for an NX102 CPU Unit, and up to eight com-\nbinations for an NJ-series CPU Unit or an NX1P2 CPU Unit.\nSpecify 0 for the host portions of the IP addresses.\nAdditional Information\nIP Router Table Setting Example\nWhen the EtherNet/IP port built-in the NN/NX-series CPU Unit performs Ethernet communica-\ntions, such as communications instructions and CIP message communications, with a remote\nnode via an IP router, set an IP router table as follows for the built-in EtherNet/IP port. By con-\nfiguring the IP router table, the built-in EtherNet/IP port can send packets to the gateway ad-\ndress 130.25.36.253."}
+{"question": "25. XX. XX 130. 26. XX. XX", "answer": "NJ/NX-series"}
+{"question": "25.36.253 130.26.2.254", "answer": "CPU Unit Destination Node\nBuilt-in EtherNet/IP Port IP router\nThe host fields are set to 0 in the destination IP address.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-7\n4-1\nTCP/IP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n Port Forward (NX502 and NX102 CPU Units)\nSetting Description Default\nIP Forward Select whether to transfer IP packets between communications *1\nports.\n*1. For NX502 CPU Units, the default is Do not use.\nFor NX102 CPU Units, the default is Use.\nPrecautions for Correct Use\nFor CPU Units other than the NX502 CPU Unit and NX102 CPU Unit, there is no setting for port\nforward. To disable port forward, specify the IP address of the built-in EtherNet/IP port in the\ndestination IP address of the Packet Filter.\n Packet Filter\nFor information on usage and restrictions of Packet Filter, refer to 5-4 Packet Filter on page 5-20.\nSetting Description Default\nPacket Filter Select whether to use Packet Filter or not. Do not use\nUse\nDo not use\nSource Set the conditions for the source. ---\nIP Address Specifi- Select the method for specifying the IP address of the source. any\ncation Method any*1\nIP address specification\nIP Address If the IP address specification method is IP address specification, set None\nthe source IP address.*2\nMask If the IP address specification method is IP address specification, set None\nthe mask of source IP address.*3\nDestination Set the conditions for the destination. ---\nIP Address Specifi- Same as those for the source.\ncation Method\nIP Address\nMask\nProtocol Set the communications protocol. any\nany*4\ntcp\nudp\nigmp*5\nicmp*6\nSource Port If tcp or udp is selected for Protocol, set the source port conditions. ---\n4-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nSpecification Select the method for specifying the IP packets of the source port. any\nMethod any*7\nPort specification\nRange Speci- Specify whether or not to set the port range if the specification method No check.\nfication selected is Port specification.\nIf it is selected, reception from the source ports from the Start Number\nto the End Number is allowed.\nIf it is not selected, reception from the source port specified by the\nStart Number is allowed.\nNo check.\nChecked.\nStart Number Set the start number when Port specification is selected for the speci- None\nfication method.\n1 to 65535\nEnd Number Set the end number when the specification method is Port None\nspecification and the range specification is selected.\n1 to 65535\nDestination Port Set the conditions for the destination port if tcp or udp is selected for Protocol.\nSame as the settings for the source port.\nSpecification\nMethod\nRange Speci-\nfication\nStart Number\nEnd Number\n*1. If you select any, packets from any IP addresses will be allowed.\n*2. The allowed IP address is calculated by the logical AND of the IP address and the Mask. If you want to\nallow more than one IP address, mask a part of the IP address by setting the Mask. In this case, set 0 to\nthe bits to be masked in the IP address and Mask.\nThe following is an example of how to calculate the allowed IP addresses.\nExample 1. Allowing IP address 192.168.250.1\nIf you want to allow one IP address, set 255.255.255.255 to the mask.\nSetting Decimal notation Binary notation\nIP address 192.168.250.1 11000000.10101000.11111010.00000001\nMask 255.255.255.255 11111111.11111111.11111111.11111111\nExample 2. Allowing IP address 192.168.250.***\nSet 255.255.255.0 to the mask to mask the lower 8 bits of the IP address.\nSetting Decimal notation Binary notation\nIP address 192.168.250.0 11000000.10101000.11111010.00000000\nMask 255.255.255.0 11111111.11111111.11111111.00000000\nExample 3. Allowing IP address 192.168.250.1 to 192.168.250.31\nSet 255.255.255.224 to the mask to mask the lower 5 bits if the IP address.\nSetting Decimal notation Binary notation\nIP address 192.168.250.0 11000000.10101000.11111010.00000000\nMask 255.255.255.224 11111111.11111111.11111111.11100000\n*3. Set 0 to the bits to be masked in Mask. Multiple bits can be masked, but only bits from the least signifi-\ncant can be masked. It is not possible to mask the higher bits, such as 0.255.255.255, or the middle bits,\nsuch as 255.0.255.255.\nThe following are examples of setting a mask.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-9\n4-1\nTCP/IP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nExample 1. Masking the lower 8 bits\nSet 0 to the lower 8 bits.\nSetting Decimal notation Binary notation\nMask 255.255.255.0 11111111.11111111.11111111.00000000\nExample 2. Masking the lower 24 bits\nSet 0 to the lower 24 bits.\nSetting Decimal notation Binary notation\nMask 255.0.0.0 11111111.00000000.00000000.00000000\n*4. If you select any, packets from tcp, udp, igmp, and icmp will be allowed.\n*5. Select igmp when EtherNet/IP tag data links are used for multicast and the built-in EtherNet/IP is speci-\nfied as the originator.\n*6. Select icmp for receiving Ping requests.\n*7. If you select any, packets from any TCP/UDP port are allowed.\nVersion Information\nPacket Filter is available in the following CPU Units of the stated versions.\n• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later\n• NX701 CPU Unit: Version 1.29 or later\n• NX502-££££ CPU Unit: Version 1.60 or later\n Packet Filter (Simple)\nYou can select Use Packet Filter (Simple) on NX102 CPU Units only.\nSetting Description Default\nPacket Filter (Simple) Select whether or not to set conditions of IP packets to be re- Do not use\nceived at the communications port.\nPass Frame Set the following items as the conditions of IP packets to be re- ---\nceived at the communications port. You can set the conditions\nunder which up to 32 packets are allowed to be received.\nThis setting is valid only when the Use Option is selected for\nPacket Filter (Simple).\nPort Select the communications port to use Packet Filter (Simple). No.1: Port 1\nNo.2: Port 2\nSpecification Meth- Select the method for specifying IP packets to be received. No.1: any\nod IP address specification No.2: any\nany*1\nIP Address Specify an IP address that is allowed to be received. None\nMask Set the mask for the IP address allowed to be received. If you None\nselect IP address specification for Specification Method,"}
+{"question": "255.255.255 is automatically set.", "answer": "*1. If you select any, packets from any IP addresses will be received.\n4-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nPrecautions for Correct Use\n• Connections to NA-series and NS-series Programmable Terminals are restricted if this func-\ntion is enabled. To make connections to these devices, register their IP addresses in the\nPacket Filter (Simple) settings.\n• If this function is enabled, you cannot connect the Sysmac Studio from a computer whose IP\naddress is not registered. Before enabling this function, confirm in advance that the IP ad-\ndress of the computer is correctly registered.\n• If this function is enabled, you cannot connect the Sysmac Studio to the Controller with the\nDirect connection via Ethernet Option selected for the connection type. Select Controller -\nCommunications Setup to confirm that the connection type is Ethernet connection via a\nhub.\n• You can disable this function tentatively by starting the Unit in Safe Mode in case you forget\nthe registered IP address and cannot go online from the Sysmac Studio. Refer to\nTroubleshooting When You Cannot Go Online from the Sysmac Studio in the NJ/NX-series\nTroubleshooting Manual (Cat. No. W503) for details.\n• You can use the Packet Filter (Simple) with Sysmac Studio version 1.49 or lower. Use the\nPacket Filter instead of the Packet Filter (Simple) when you use Sysmac Studio version 1.50\nor higher.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-11\n4-1\nTCP/IP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-2 LINK Settings Display\nNX701 CPU Unit NX502 CPU Unit\nNX102 CPU Unit NJ-series CPU Unit\nNX1P2 CPU Unit\n LINK Settings - Port 1 and Port 2 (NX701 CPU Units)\nSet for each built-in EtherNet/IP port.\nSetting Description Default\nLINK settings Set the baud rate for the built-in EtherNet/IP ports.*1 Auto\n• Auto\n• 10 Mbps Half Duplex\n• 10 Mbps Full Duplex\n• 100 Mbps Half Duplex\n• 100 Mbps Full Duplex\n• 1000Mbps Full Duplex\n*1. For an NX701 CPU Unit with the hardware revision B or later, Auto will be set regardless of the setting of\nthe Sysmac Studio. If an item other than Auto is selected and the setting is transferred from the Sysmac\nStudio, Link Setting Not Supported (342B0000 hex) event will occur.\n4-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n LINK Settings - Port 1 and Port 2 (NX502 CPU Unit)\nSet for each built-in Ethernet port.\nSetting Description Default\nLINK settings The baud rate for the built-in EtherNet/IP ports. Auto\nThis is fixed to Auto.\nLLDP Specify whether to use LLDP or not. Use\n LINK Settings - Port 1 and Port 2 (NX102 CPU Units)\nSet for each built-in EtherNet/IP port.\nSetting Description Default\nLINK settings Set the baud rate for the built-in EtherNet/IP ports. Auto\n• Auto\n• 10Mbps Half Duplex\n• 10Mbps Full Duplex\n• 100Mbps Half Duplex\n• 100Mbps Full Duplex\nLLDP Specify whether to use LLDP or not. Use\nVersion Information\nA CPU Unit with unit version 1.64 or later is required to use LLDP.\n LINK Settings (NJ-series CPU Unit and NX1P2 CPU Unit)\nSetting Description Default\nLINK settings Set the baud rate for the built-in EtherNet/IP ports. *1 Auto\n• Auto\n• 10 Mbps Half Duplex\n• 10 Mbps Full Duplex\n• 100 Mbps Half Duplex\n• 100 Mbps Full Duplex\n*1. For an NJ-series CPU Unit with the hardware revision D or later, Auto will be set regardless of the setting\nfrom the Sysmac Studio. If an item other than Auto is selected and the setting is transferred from the\nSysmac Studio, Link Setting Not Supported (342B0000 hex) event will occur.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-13\n4-2\nLINK\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-3 FTP Settings Display\nSetting Description Default\nFTP server Specify whether to use the FTP server or not. Do not use\nFTP connections from external devices will not be possible if the\nDo not use Option is selected.\nPort No.*1,*2 Set the FTP port number of the built-in EtherNet/IP port. This set- 21\nting does not normally need to be changed.\nThe FTP control port is set here. The FTP data transfer port is al-\nways port 20.\nLogin name *1 Set the login name to externally connect to the built-in EtherNet/IP None\nport via FTP.\n(You can use up to 12 alphanumeric characters.)*3\nPassword*1 Set the password to externally connect to the built-in EtherNet/IP None\nport via FTP.\n(You can use 8 to 32 alphanumeric characters.)*3\n*1. These settings are required when the Use Option is selected for the FTP server.\n*2. The following ports are used by the system and cannot be set by the user: 20, 23, 25, 80, 110, 9610, and"}
+{"question": "*3. The login name and password are case sensitive.", "answer": "Additional Information\nRefer to Section 10 FTP Server on page 10-1 for details on the FTP server.\n4-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-4 NTP Settings Display\nSetting Description Default\nNTP server clock infor- Set whether to obtain clock information from the NTP server to up- Do not get\nmation date the clock in the CPU Unit.\nPort No. *1 *2 Set the port number to use to connect to the NTP server to obtain 123\nclock information. It is normally not necessary to change this set-\nting.\nServer specifying meth- Set the method to use to specify the NTP server to obtain clock in- IP address\nod*1 formation.\n• IP address\n• Host name\nIP address Set the IP address of the NTP server. None\nSpecify this setting if the server specifying method is set to the IP\naddress Option.\nHost name Set the host name of the NTP server (i.e., the domain name of the None\nhost).\nSpecify this setting if the server specifying method is set to the\nHost name Option.\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric characters\nbetween dots.)\nNTP operation timing*1 Set the time at which the NTP server is accessed to synchronize Specify a time\nthe clocks.\n• Specify a time\n• Specify a time interval\nTime [hours:mi- The NTP server is accessed at the specified time. 00:00:00\nnutes:seconds] (Setting range: 00:00:00 to 23:59:59)\nSpecify this setting if the NTP operation timing is set to the\nSpecify a time Option.\nInterval [minutes] The NTP server is accessed when the specified period of time has 60 minutes\npassed.\n(Setting range: 1 to 1,440 minutes)\nSpecify this setting if the NTP operation timing is set to the\nSpecify a time interval Option.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-15\n4-4\nNTP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nTimeout time (sec- Set the timeout detection time. 10 seconds\nonds)*1 (Setting range: 1 to 255 seconds)\nIf the remote host does not respond, retry processing is performed\nfour times within the time interval that is set here.\nIf the Specify a time interval Option is selected for the NTP\noperation timing, timing for the next execution of the NTP opera-\ntion starts when the fourth retry processing times out.\n*1. This setting is required when the Get Option is selected for the NTP server clock information.\n*2. The following ports are used by the system and cannot be set by the user: 25, 53, 68, 110, 2222, 2223,\n2224, 9600, and 44818.\nAdditional Information\nRefer to Section 12 Automatic Clock Adjustment on page 12-1 for details on obtaining clock\ninformation from the NTP server.\n4-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-5 SNMP Settings Display\n SNMP Service\nSetting Description Default\nSNMP service Specify whether to use the SNMP monitor service.*1 Do not use\nIf the Do not use Option is selected, an SNMP manager cannot\nconnect from an external device.\nPort No.*2 Set the port number to use to connect to the SNMP server that is 161\nused to connect from an SNMP manager.\nThis setting does not normally need to be changed.\nAddress Set the communications device administrator’s name and instal- None\nLocation lation location as text information. You do not necessarily have to None\ninput all items. This information is read by the SNMP manager.\n(You can input up to 255 single-byte alphanumeric characters for\neach item.)\nSend a recognition Set whether to send an authentication trap. Not selected\ntrap If you select Send a recognition trap and there is access from\nan SNMP manager that is not set in Recognition 1 or Recognition\n2, an authentication trap is sent to the SNMP manager.\nIf you select Send a recognition trap, specify the SNMP trap\nsettings on the SNMP Trap Tab.\n*1. If you select the Use Option for the SNMP service, you also have to set Recognition 1 and 2 as descri-\nbed below.\n*2. The following ports are used by the system and cannot be set by the user: 25, 53, 68, 110, 2222, 2223,\n2224, 9600, and 44818.\nAdditional Information\nRefer to Section 13 SNMP Agent on page 13-1 for details on the SNMP service.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-17\n4-5\nSNMP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n Recognition 1\nSetting Description Default\nRecognition method Set the method to use to specify SNMP managers for which ac- IP address\ncess is permitted.\n• IP address\n• Host name\nMake these settings to permit access by only certain SNMP\nmanagers.\nAccess is not allowed unless an IP address or host name is set.\nIP address Set the IP address of the SNMP manager. None\nIf the default setting of 0.0.0.0 is used, access by all SNMP man-\nagers is permitted.\n(Set this setting if Recognition method in Recognition 1 is set to\nthe IP address Option.)\nHost name Set the host name of the SNMP manager. None\n(Set this setting if Recognition method in Recognition 1 is set to\nthe Host name Option.)\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric charac-\nters between dots.)\nCommunity name Set the community name to enable the SNMP manager to ac- public\ncess information from the built-in EtherNet/IP port.\n(Single-byte alphanumeric characters, dots, and hyphens: 255\ncharacters max.)\n Recognition 2\nSetting Description Default\nRecognition 2 Specify whether to use the recognition 2 settings. Do not use\n• Use\n• Do not use\nRecognition method Set the method to use to specify SNMP managers for which ac- IP address\ncess is permitted.\n• IP address\n• Host name\nMake these settings to permit access by only certain SNMP man-\nagers.\nAccess is not allowed unless an IP address or host name is set.\nIP address Set the IP address of the SNMP manager. None\nIf the default setting of 0.0.0.0 is used, access by all SNMP man-\nagers is permitted.\n(Set this setting if Recognition method in Recognition 2 is set to\nthe IP address Option.)\nHost name Set the host name of the SNMP manager. None\n(Set this setting if Recognition method in Recognition 2 is set to\nthe Host name Option.)\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric charac-\nters between dots.)\nCommunity name Set the community name to enable the SNMP manager to ac- public\ncess information from the built-in EtherNet/IP port.\n(Single-byte alphanumeric characters, dots, and hyphens: 255\ncharacters max.)\n4-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-6 SNMP Trap Settings Display\n SNMP Trap\nSetting Description Default\nSNMP trap Specify whether to use the SNMP trap (network error detec- Do not use\ntion).*1\nIf the Do not use Option is selected for SNMP trap, SNMP traps\nare not sent to the SNMP manager\nPort No.*2 Set the port number to use to connect to the SNMP server. 162\nIt is normally not necessary to change this setting.\n*1. If you specify to use the SNMP trap, you also have to set Trap 1 and Trap 2 as described below.\n*2. The following ports are used by the system and cannot be set by the user: 25, 53, 68, 110, 2222, 2223,\n2224, 9600, and 44818.\nAdditional Information\nRefer to 13-1-1 Overview on page 13-2 for details on the SNMP trap.\n Trap 1\nIf the Use Option is selected for SNMP trap, you need to make the following settings.\nSetting Description Default\nSpecifying method Set the specifying method for the SNMP manager destination for IP address\nSNMP traps.\n• IP address\n• Host name\nIP address Set the IP address of the SNMP manager. None\n(Set this setting if the Specifying method in the Trap 1 settings\nis set to the IP address Option.)\nHost name Set the host name of the SNMP manager. None\n(Set this setting if the Specifying method in the Trap 1 settings\nis set to the Host name Option.)\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric charac-\nters between dots.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-19\n4-6\nSNMP\nTrap\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\nSetting Description Default\nCommunity name Set the community name. public\n(You can use up to 255 single-byte alphanumeric characters.)\nVersion Set the version of the SNMP manager. SNMPv1\n• SNMPv1\n• SNMPv2C\n Trap 2\nIf the Use Option is selected for SNMP trap, you need to make the following settings.\nSetting Description Default\nTrap 2 Specify whether to use the Trap 2 settings. Do not use\n• Use\n• Do not use\nSpecifying method Set the specifying method for the SNMP manager destination for IP address\nSNMP traps.\n• IP address\n• Host name\nIP address Set the IP address of the SNMP manager. None\n(Set this setting if the Specifying method in the Trap 2 settings\nis set to the IP address Option.)\nHost name Set the host name of the SNMP manager. None\n(Set this setting if the Specifying method in the Trap 2 settings\nis set to the Host name Option.)\n(Single-byte alphanumeric characters, dots, and hyphens: 200\ncharacters max. with up to 63 single-byte alphanumeric charac-\nters between dots.)\nCommunity name Set the community name. public\n(You can use up to 255 single-byte alphanumeric characters.)\nVersion Set the version of the SNMP manager. SNMPv1\n• SNMPv1\n• SNMPv2C\n4-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n4-7 CIP Settings Display\nNJ-series, NX701, NX102, and NX1P2 CPU Unit NX502 CPU Unit\n CIP Message Server\nSetting Description Default\nCIP Message Server Specify whether to use the CIP message server or not. Use\nIf the Use Option is selected, the following ports will be opened.\n• UDP 2222\n• UDP 44818\n• TCP 44818\nRefer to 7-3 Server Function of CIP Message Communications on page 7-39 for restrictions when\nthe Do not use Option is selected for CIP message server.\n CIP Safety Communications (NX502 CPU Unit)\nSetting Description Default\nCIP Safety Communica- Select whether to use CIP Safety communications. Use\ntions However, if the task period for the primary periodic task is set to\nless than 500 μs, the Use Option cannot be selected. When us-\ning CIP Safety communications, set the task period for the pri-\nmary periodic task to 500 μs or more.\nThe relationship between the combination of CIP message server and CIP Safety\ncommunications settings and the availability of CIP Safety communications is as follows.\nCIP message server CIP Safety communications\nAvailability of CIP Safety communications\nsetting setting\nUse Use CIP Safety communications are available.\nDo not use CIP Safety communications are unavailable.*1\nDo not use Use\nDo not use\n*1. If you try to use CIP Safety communications via the built-in EtherNet/IP port of the NX502 CPU Unit, an\nevent of CIP Safety Originator Connection Not Established Error (80310000 hex) or CIP Safety Target\nConnection Timeout (80340000 hex) will occur.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 4-21\n4-7\nCIP\nSettings\nDisplay\n4\n4 Sysmac Studio Settings for the Built-in EtherNet/IP Port\n QoS (NX502 CPU Unit)\nSetting Description Default\nPrefer CIP safety com- Select whether to prioritize CIP Safety communications in QoS. No\nmunications\nVersion Information\nCIP Safety communications via the built-in EtherNet/IP port on the NX502 CPU Unit and QoS\nsetting can be used with the NX502 CPU Unit with unit version 1.64 or later.\n4-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5\nTCP/IP Functions\n5-1 Determining IP Addresses............................................................................5-2\n5-1-1 IP Addresses...................................................................................................5-2\n5-1-2 Built-in EtherNet/IP Port IP Address Settings..................................................5-4\n5-1-3 Private and Global Addresses........................................................................5-11\n5-2 Default States of TCP/UDP Ports and the Changing Procedure..............5-15\n5-3 Testing Communications.............................................................................5-18\n5-3-1 PING Command............................................................................................5-18\n5-3-2 Using the PING Command............................................................................5-18\n5-3-3 Host Computer Operation.............................................................................5-18\n5-4 Packet Filter..................................................................................................5-20\n5-4-1 Introduction to Packet Filter...........................................................................5-20\n5-4-2 Packet Filter Specifications...........................................................................5-21\n5-4-3 Packet Filter Settings....................................................................................5-21\n5-4-4 Case Where Packet Filter Is Used................................................................5-21\n5-4-5 Settings for Devices That Access the Controller...........................................5-33\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-1\n5\n5 TCP/IP Functions\n5-1 Determining IP Addresses\n5-1-1 IP Addresses\nIP Address Configuration\nIP addresses are made up of 32 bits of binary data that specify the network number (net ID) and host\nnumber (host ID). The net ID is an address used for identifying a network. The host ID is an address\nused for identifying a host (node).\nIP addresses are divided into three classes, A, B, and C, so that the address system can be selected\naccording to the scale of the network. (Classes D and E are not used.)\nBit 31 23 0\nClass A\n0 Network ID (7 bits) Host ID (24 bits)\nBit 31 15 0\nClass B 1 0 Network ID (14 bits) Host ID (16 bits)\nBit 31 7 0\nClass C 1 1 0 Network ID (21 bits) Host ID (8 bits)\nBit 31 0\nClass D 1 1 1 0 Multicast address (Cannot be used.)\nBit 31 0\nClass E 1 1 1 1 Experimental address (Cannot be used.)\nThe number of networks in each class and the number of hosts possible on the network differ accord-\ning to the class.\nClass Number of networks Number of hosts\nClass A Small 224−2 max. (16,777,214 max.)\nClass B Medium 216−2 max. (65,534 max.)\nClass C Large 28−2 max. (254 max.)\nThe 32 bits of binary data in an IP address are divided into four sections of eight bits each. IP address-\nes are represented by the decimal equivalent of each of the four octets in the 32-bit address, each\nseparated by a period.\nFor example, the binary address 10000010 00111010 00010001 00100000 would be represented as"}
+{"question": "58.17.32.", "answer": "Allocating IP Addresses\nYou must assign IP addresses nodes so that each IP address is assigned only once in the network or\nbetween several networks.\n5-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nSubnet Mask\nOperation and management of a network can become very difficult if too many nodes are connected\non a single network. In such a case it can be helpful to configure the system so that a single network is\ndivided up into several subnetworks. Internally the network can be treated as a number of subnet-\nworks, but from the outside it acts as a single network and uses only a single network ID.\nTo establish subnetworks, the host ID in the IP address is divided into a subnet ID and a host ID by\nusing a setting called the subnet mask.\nThe subnet mask indicates which part of the host ID is to be used as the subnet ID. All bits in the sub-\nnet mask that correspond to the bits in the IP address used either as the network ID or subnet ID are\nset to \"1\", and the remaining bits, which correspond to the bits in the IP address actually used for the\nhost ID, are set to \"0\".\nThe following example shows the subnet mask for an 8-bit subnet ID used in the class-B IP address.\nBit 31 15 0\nClass B 1 0 Network ID (14 bits) Host ID (16 bits)\nSubnet mask 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 FF FF FF 00\nNetwork ID Subnet ID Host ID\nSet the same subnet mask for all of the nodes on the subnetwork. The built-in EtherNet/IP port sup-\nports CIDR (Classless Inter-Domain Routing). The subnet mask can be set to 192.0.0.0 to"}
+{"question": "255.255.252.", "answer": "If subnetworks are not used, set the following subnet mask values for IP address classes A to C.\nClass Subnet mask\nClass A 255.0.0.0\nClass B 255.255.0.0\nClass C 255.255.255.0\nA network address is information derived from a subnet mask and used to identify each network. A\nnetwork address enables users to determine whether multiple nodes belong to the same network. A\nnetwork address is calculated by performing a logical AND operation on the IP address and subnet\nmask of a node.\nThe following are examples of network address calculation.\nIn this example, the IP address of node 1 is set to 192.168.250.20, the IP address of node 2 is set to"}
+{"question": "168.245.30, and the subnet mask is set to 255.255.240.0. The network addresses of the two no-", "answer": "des are calculated as follows.\n• Calculating network address of node 1\nItem Decimal notation Binary notation\nIP address 192.168.250.20 11000000.10101000.11111010.00010100\nSubnet Mask 255.255.240.0 11111111.11111111.11110000.00000000\nNetwork address 192.168.240.0 11000000.10101000.11110000.00000000\n• Calculating network address of node 2\nItem Decimal notation Binary notation\nIP address 192.168.245.30 11000000.10101000.11111010.00010100\nSubnet Mask 255.255.240.0 11111111.11111111.11110000.00000000\nNetwork address 192.168.240.0 11000000.10101000.11110000.00000000\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-3\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-1\nIP\nAddresses\n5 TCP/IP Functions\nAs shown in the above tables, node 1 and node 2 have the same network address, which means\nthese nodes belong to the same network.\nCIDR\nCIDR, or classless interdomain routing, is used to assign IP addresses that do not use classes.\nIP addresses that use classes are separated into blocks according to network IDs and host IDs, result-\ning in inefficient usage of IP address space.\nCIDR does not use classes, so IP address space can be divided as required to more efficiently use IP\naddress space.\nFor example, using a subnet mask setting with CIDR enables building a horizontally distributed net-\nwork exceeding 254 nodes even if a class C address block (e.g., 192, 168...) is used.\nSubnet Mask Range"}
+{"question": "0.0.0 to 255.255.255.252", "answer": "5-1-2 Built-in EtherNet/IP Port IP Address Settings\nDetermining IP Addresses\nUse one of the following methods to set an IP address of a built-in EtherNet/IP port.\n Setting a User-specified IP Address\nIf you need to change the default IP address of the built-in EtherNet/IP port or if you need to use\nthe built-in EtherNet/IP port with another EtherNet/IP node, set the IP address to a required value.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, you cannot set IP addresses\nthat make two built-in EtherNet/IP ports belong to the same network.\n Automatically Obtaining an IP Address from the BOOTP Server\nThere are two methods to automatically obtain an IP address.\n• Obtain an IP address from the BOOTP server each time the power is turned ON.\n• Obtain an IP address from the BOOTP server at initial power on and set the address as a fixed\nIP address.\nBOOTP server\nBOOTP command\nEthernet\nNJ/NX-series Controller NJ/NX-series Controller\nIP address\nBOOTP client\n5-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\n Automatically Obtaining an IP Address from the DHCP Server\nThis method automatically obtains an IP address from the DHCP server as a DHCP client each\ntime the power is turned ON.\nDHCP server\nDHCP command Ethernet\nNJ/NX-series NJ/NX-series\nIP address\nController Controller\nDHCP client\nVersion Information\nYou can use the DHCP client only with the NX502 CPU Units.\nSetting IP Addresses\nUse the Sysmac Studio to set an IP address of the built-in EtherNet/IP port.\n1\nSelect a method for setting the IP address.\nMake the following settings on the TCP/IP Settings Display of the Built-in EtherNet/IP Port\nSettings Tab Page in the Controller Setup to set the local IP address.\nUsed to set a user-specified IP address.\nUsed to obtain the IP address from the BOOTP\nserver each time the power is turned ON.\nUsed to obtain the IP address from the BOOTP\nserver and use the address without changing it.\nUsed to obtain the IP address from the DHCP\nserver each time the power is turned ON.\nFor an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, the IP addresses must be\nset separately for built-in EtherNet/IP ports 1 and 2.\nPrecautions for Correct Use\nYou cannot set IP addresses that make two built-in EtherNet/IP ports belong to the same net-\nwork.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-5\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-2\nBuilt-in\nEtherNet/IP\nPort\nIP\nAddress\nSettings\n5 TCP/IP Functions\n2\nConnect the Sysmac Studio to the NJ/NX-series CPU Unit via a USB connection or the Ether-\nnet network.\nPrecautions for Correct Use\nThe NX502, NX102, and NX1P2 CPU Units can be connected only via Ethernet.\n3\nConnect the Sysmac Studio online to the NJ/NX-series CPU Unit.\nRefer to Online Connection on page 5-8 for the procedure to connect online.\n4\nUse one of the following methods to download the IP address that was set on the Sysmac Stu-\ndio to the NJ/NX-series CPU Unit.\n1) Go online with the Controller, and then select Synchronization from the Controller Menu.\nThe data on the computer and the data in the physical Controller are compared to each oth-\ner automatically.\n2) Click the Transfer to Controller Button.\nNoteUse the \"synchronization\" of the Sysmac Studio to upload and download data.\n5\nAfter the IP address settings are downloaded, the IP address is reflected in the CPU Unit as\nfollows:\n• Setting a User-specified IP Address\nAfter the IP address settings are downloaded, the set IP address is automatically reflect-\ned in the CPU Unit.\n• Obtaining the IP Address from the BOOTP Server Each Time the Power Is Turned ON\nAfter the IP address settings are downloaded, the IP address from the BOOTP server is\nautomatically reflected in the CPU Unit.\nEach time the power supply is turned ON, the IP address from the BOOTP server is auto-\nmatically reflected in the CPU Unit.\n• Obtaining the IP Address from the DHCP Server Each Time the Power Is Turned ON\nAfter the IP address settings are downloaded, the IP address from the DHCP server is\nautomatically reflected in the CPU Unit.\nEach time the power supply is turned ON, the IP address from the DHCP server is auto-\nmatically reflected in the CPU Unit.\nAdditional Information\n• If you cannot obtain the IP address from the BOOTP server or DHCP server, or the obtained\nIP address is not correct, select the Fixed setting Option in the IP Address Area and man-\nually set the IP address, subnet mask, and default gateway.\nRequests to the BOOTP server or DHCP server for an IP address will continue if connecting\nto the BOOTP server or DHCP server fails.\n• If both built-in EtherNet/IP port 1 and EtherNet/IP port 2 are set to obtain IP addresses from\nBOOTP server or DHCP server, since they are obtained in order from EtherNet/IP port 1 to\nEtherNet/IP port 2, the IP address of the EtherNet/IP port 2 is disabled (0.0.0.0) until the port\nobtains the IP address.\n• Obtaining the IP Address from the BOOTP Server When the Power Is Turned ON and\nFixing at It\nAfter the IP address settings are downloaded, the IP address from the BOOTP server is\nautomatically reflected in the Controller and set for Fixed setting.\n5-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nAdditional Information\n• The TCP/IP Settings Display is not updated even if the IP address is obtained normally from\nthe BOOTP server.\nTo check the IP address that was obtained from the BOOTP server, upload the project from\nthe NJ/NX-series Controller and check the Controller Status Pane.\n• If you cannot obtain the IP address from the BOOTP server, the Fix at the IP address\nobtained from BOOTP server Option is selected on the TCP/IP Settings Display.\nTo stop obtaining the IP address from the BOOTP server, select Fixed setting in the IP\nAddress Area and manually set the IP address, subnet mask, and default gateway.\n• If the Controller power supply is turned OFF and then ON after the IP address was not nor-\nmally obtained from the BOOTP server, the setting remains at Fix at the IP address\nobtained from BOOTP server.\n• After you select Fix at the IP address obtained from BOOTP server and download the IP\naddress from the BOOTP server, the built-in EtherNet/IP port IP address setting is automati-\ncally set to Fixed setting. Therefore, the IP address will not match when the program is veri-\nfied on the Sysmac Studio.\n• To use the Packet Filter, you must allow packets (UDP:68) used for BOOTP and DHCP. Re-\nfer to 5-4-5 Settings for Devices That Access the Controller on page 5-33 for details on the\nsettings.\nAdditional Information\nFor an NX701-££20 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, when the local IP ad-\ndress of the built-in EtherNet/IP port is set, the FINS node address is automatically set as\nshown below. You can set the FINS node address only with the NX701-££20 CPU Unit,\nNX502 CPU Unit, and NX102 CPU Unit.\nExample: Pairing an IP Address and an FINS Node Address with the Automatic generation\nMethod\nTCP/IP Settings Display FINS Settings Display\nHost ID\n(lower 8 bits of the IP address)\nThe same value as the host ID is set.\nAfter the IP address is obtained from the If you select the Automatic generation Option,\nBOOTP server, the FINS node address the value of host ID is set to FINS node\nfor the built-in EtherNet/IP port is set. address and it cannot be changed.\nIf you select the Combination or IP address\nOption, you can change the set value.\nThe FINS node address is required for FINS communications (e.g., to connect to the CX-Inte-\ngrator and other Support Software).\nWhen the Automatic generation Method is selected, do not set the lower 8 bits of the IP ad-\ndress to 0 or 255.\nThe NX502 CPU Unit and NX102 CPU Unit have two EtherNet/IP ports. The FINS node ad-\ndress is set according to the IP address of port 2.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-7\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-2\nBuilt-in\nEtherNet/IP\nPort\nIP\nAddress\nSettings\n5 TCP/IP Functions\nOnline Connection\nConnect the Sysmac Studio online to the CPU Unit.\nAdditional Information\nFor the procedure to go online to the CPU Unit from the Sysmac Studio, refer to Online\nConnections to a Controller in the Sysmac Studio Version 1 Operation Manual (Cat. No. W504).\n Types of Connection between the CPU Unit and Computer That Runs the\nSysmac Studio\nThe CPU Unit and the computer that runs Sysmac Studio are connected via USB or Ethernet as\nshown below:\n• USB Connection\nDirect Connection via USB\nSysmac Studio\nUSB connection\n*1. NX701 CPU Units with hardware revision A or\nlater and NX502, NX102, and NX1P2 CPU\nUnits do not support USB connection.\n• Ethernet Connection\nDirect Connection via Ethernet (1:1 Connection\nEthernet Connection via a Hub (1:N Connection)\nwith Auto IP)\nEthernet\nEthernet\n*1. An Ethernet switch is required to connect. Refer\nto 2-1-4 Precautions for Ethernet Switch Selec-\n*1. An Ethernet switch is not necessarily required. tion on page 2-4 for details.\n*2. You can use a straight or cross Ethernet cable\nto connect.\n*3. For NX701 CPU Units, NX502 CPU Units, and\nNX102 CPU Units, 1:1 connection is supported\nonly for the built-in EtherNet/IP port 1.\n• Connection from USB Across Ethernet\n5-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nRemote Connection via USB\n(1:N Connection)\nEthernet\nUSB\n*1. An NJ/NX-series Controller with a USB port is\nrequired to connect.\n*2. An Ethernet switch is required to connect. Re-\nfer to 2-1-4 Precautions for Ethernet Switch\nSelection on page 2-4 for details.\nPrecautions for Correct Use\nIf you connect the computer that runs the Sysmac Studio to the EtherNet/IP port on the CPU\nUnit, you cannot use direct connection via Ethernet. Use the Ethernet connection via a hub\nthrough an Ethernet switch. In that case, you must specify the destination IP address.\nAdditional Information\n• Auto IP automatically assigns IP addresses in Windows 98 and later operating systems.\nUnique IP addresses are automatically assigned from the address 169.254.0.0 to"}
+{"question": "254.255.255.", "answer": "• If the Sysmac Studio is connected online via a built-in EtherNet/IP port, changing the IP ad-\ndress of the connected built-in EtherNet/IP port will cause a timeout on the Sysmac Studio.\nIn the case, switch the Sysmac Studio status to offline, restore the original IP address of the\nconnected built-in EtherNet/IP port, and then switch back the Sysmac Studio status to online.\nThis will allow you to reconnect.\nPrecautions for Correct Use\nIf there is more than one node with the same IP address in the EtherNet/IP network, the built-in\nEtherNet/IP port will connect to the node that is detected first.\nNote that an IP Address Duplication Error will not be detected in this case.\n Online Connection Procedure\nConnect the CPU Unit and the computer that runs the Sysmac Studio via USB or Ethernet, and\nthen perform the following procedure.\n1\nSelect Controller - Communications Setup and click the OK Button in the Sysmac Studio\nProject Window.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-9\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-2\nBuilt-in\nEtherNet/IP\nPort\nIP\nAddress\nSettings\n5 TCP/IP Functions\n1:1 Connection 1:N Connection\nDirect Connection Ethernet Connection\n·Remote connection via USB\n·Direct connection via USB\nEtherNet/IP Connection\n·Ethernet connection via a hub\n·Direct connection via Ethernet\nAdditional Information\nIf there is any error in the set IP address, the CPU Unit behaves as follows:\n• The NET RUN indicator on the CPU Unit does not light and the NET ERR indicator flashes\nred. For NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, indicators will indicate\nthe status of each built-in EtherNet/IP port.\n• An IP Address Setting Error is recorded in the event log.\nPrecautions for Correct Use\n• If the IP address is duplicated or not set correctly, communications are not possible via the\nEtherNet/IP network. Use the Sysmac Studio to set the IP address again in direct connection\nvia Ethernet.\n• The IP address range shown below is used by the system and cannot be specified."}
+{"question": "168.255.0 to 192.168.255.255", "answer": "• Due to Ethernet restrictions, you cannot specify the following IP addresses.\na) An IP address that is all 0's or all 1's\nb) IP addresses that start with 127, 0, or 255 (decimal)\nc) IP addresses that have a host ID that is all 0's or all 1's\nd) Class-D IP addresses (224.0.0.0 to 239.255.255.255)\ne) Class-E IP addresses (240.0.0.0 to 255.255.255.255)\n Connecting from a Saved Project\nThe connection configuration that is set (via USB or EtherNet/IP) is saved in the project.\nWhen you open a saved project on the Sysmac Studio, you can connect to the EtherNet/IP network\nwithout redoing the settings.\n5-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nChecking the Current IP Address\nThe current IP address can be confirmed in the Controller Status Pane of the Sysmac Studio, whether\nit is manually set or obtained from the BOOTP server.\nDisplay when using the NJ-series CPU Units and NX1P2 CPU Units\n• Basic Controller Status Pane • Controller Status Pane with Details\nDisplay when using the NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units\n• Basic Controller Status Pane • Controller Status Pane with Details\nAdditional Information\n• If the IP address of the built-in EtherNet/IP port is not registered due to the following reasons,\nthe IP address field shows \"0.0.0.0\".\n• The IP address was not obtained from the BOOTP server or DHCP server.\n• The built-in EtherNet/IP port on the NX701 CPU Unit, NX502 CPU Unit, or NX102 CPU\nUnit is disabled. Refer to 4-1 TCP/IP Settings Display on page 4-2 for details on the set-\ntings for the IP address of the built-in EtherNet/IP port.\n5-1-3 Private and Global Addresses\nPrivate and Global Addresses\nThere are two kinds of IP addresses, private and global.\nGlobal address These are IP addresses that connect directly to the Internet. Allocated by applica-\ntion to NIC, each address is unique in the world, and as many as 4.3 billion can be\nallocated worldwide.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-11\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-3\nPrivate\nand\nGlobal\nAddresses\n5 TCP/IP Functions\nPrivate address These are IP addresses for Intranet (LAN) use. Direct connection to the Internet is\nnot possible. Frames that include private IP addresses are restricted by the router\nfrom being sent outside the LAN.\nGenerally, as shown below, global addresses in the intranet are allocated only to IP routers (such as\nbroadband routers) interfaced with the Internet. All other nodes in the intranet, which includes the built-\nin EtherNet/ IP port, are allocated private addresses.\nIntranet\nPersonal computer\n(e.g., Sysmac Studio)\nEthernet (EtherNet/IP)\nFirewall Controller\nPrivate address\nIP router\nPrivate address\nCannot connect to Internet\nInternet\nGlobal address (required)\nIntranet Cannot connect to Internet\nGlobal address\nIP router Private address\nPrivate address Personal computer\n(e.g., Sysmac Studio)\nFirewall\nEthernet (EtherNet/IP)\nController Controller\nPrivate address Private address\n5-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nUsing a Private Address for the Built-in EtherNet/IP Port\nIntranet\nPersonal computer\n(e.g., Sysmac Studio)\nEthernet (EtherNet/IP)\nFirewall Controller\nPrivate address\nIP router\nPrivate address\nCannot connect to Internet\nInternet\nGlobal address (required)\nIntranet Cannot connect to Internet\nGlobal address\nIP router Private address\nPrivate address Personal computer\n(e.g., Sysmac Studio)\nFirewall\nEthernet (EtherNet/IP)\nController Controller\nPrivate address Private address\nConditions for Communications Applications\n¢\nIf the built-in EtherNet/IP port uses a private address, you can use explicit message communi-\ncations service under the following conditions.\n• The explicit message communications service can be executed on the intranet between built-\nin EtherNet/IP ports with private addresses only.\n• A device such as a personal computer (CIP applications including the Network Configurator)\ncannot connect online and communicate over the Internet with a built-in EtherNet/IP port that\nhas a private address.\nExplicit message communications are also not possible over the Internet between built-in\nEtherNet/IP ports with private addresses.\nPrecautions for Correct Use\n• To set up an intranet through a global address involves network security considerations. Be\nsure to consult with a network specialist in advance and consider installation of a firewall.\n• Some communication applications may not be available depending on the firewall settings\nmade by the communications company. If there are communication applications that cannot\nbe used, be sure to check with your communications company.\n• When sending and receiving data over a global address, use secure communications, such\nas secure socket communications and OPC UA, that ensure confidentiality and integrity.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-13\n5-1\nDetermining\nIP\nAddresses\n5\n5-1-3\nPrivate\nand\nGlobal\nAddresses\n5 TCP/IP Functions\nUsing a Global Address for the Built-in EtherNet/IP Port\nIntranet\nCIP client on a computer,\nsuch as Network\nConfigurator\nEthernet (EtherNet/IP)\nCommunications Firewall\nover Internet\nPrivate address\nIP router\nCannot connect to Internet\nInternet\nGlobal address (required)\nIntranet Cannot connect to Internet\nGlobal address\nIP router\nPrivate address\nPrivate address\nFirewall\nEthernet (EtherNet/IP)\nCommunications Controller\nin intranet\nBuilt-in EtherNet/IP port: Global address\nConditions for Communications Applications\n¢\nYou can use the explicit message communications service over the Internet under the following\nconditions.\n• A device such as a personal computer (a CIP application including the Network Configurator)\ncan connect online and communicate over the Internet with a built-in EtherNet/IP port that has\na global address.\n• The TCP port number (44818) or UDP port number (44818) that is used for EtherNet/IP can-\nnot be used because it is prohibited by a firewall in the communications path.\nPrecautions for Correct Use\n• To set a global IP address for a built-in EtherNet/IP port involves network security considera-\ntions. It is recommended that the user contract with a communications company for a dedi-\ncated line, rather than for a general line such as a broadband line. Also, be sure to consult\nwith a network specialist and consider security measures such as a firewall.\n• Some communication applications may not be available depending on the firewall settings\nmade by the communications company. If there are communication applications that cannot\nbe used, be sure to check with your communications company.\n• When sending and receiving data over a global address, use secure communications, such\nas secure socket communications and OPC UA, that ensure confidentiality and integrity.\n5-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\n5-2 Default States of TCP/UDP Ports and\nthe Changing Procedure\nThe following table shows the applications that use TCP/UDP ports for which a user can change the\nport state, CPU Unit models, port numbers, default port states, usages, and how to change a port from\nopen to close and close to open.\nRefer to A-12 TCP/ UDP Port Numbers Used for the Built-in EtherNet/IP Port on page A-95 for infor-\nmation on all TCP/UDP ports of the built-in EtherNet/IP port.\nUDP TCP\nDefault\nApplica- port port How to change from How to change from\nCPU Unit model port Usage\ntion num- num- open to close close to open\nstate\nber ber\nFTP All models --- 20 Close Used On the Sysmac Studio, On the Sysmac Studio,\nserver --- 21 Close when select Built-in select Built-in\nusing EtherNet/IP Port EtherNet/IP Port\nthe FTP Settings - FTP Settings - FTP\nserver. Settings, and then se- Settings, and then se-\nlect Do not use for FTP lect Use for FTP\nserver. server.\nSNMP All models 161 --- Close Used On the Sysmac Studio, On the Sysmac Studio,\nwhen select Built-in select Built-in\nusing EtherNet/IP Port EtherNet/IP Port\nthe Settings - SNMP Settings - SNMP\nSNMP Settings, and then se- Settings, and then se-\nagent. lect Do not use for lect Use for SNMP\nSNMP service. service.\nHTTPS All models --- 443 Open Used for Make one of the follow- • Use the Packet Filter.\nserver commu- ing settings. • Do not set the DIP\nnica- • Use the Packet Filter. switch to enable\ntions *1 connections to the\nwith the • Set the DIP switch to Sysmac Studio and\nSysmac enable connections to NA that are not\nStudio. the Sysmac Studio supporting secure\nand NA that are not communication. *6\nsupporting secure\ncommunication. *1*6\nFINS/U • All NJ-series 9600 --- Open Used for On the Sysmac Studio, On the Sysmac Studio,\nDP models the select Built-in select Built-in\n• All NX1P2 CPU FINS/ EtherNet/IP Port EtherNet/IP Port\nUnit models UDP. Settings - FINS Settings - FINS\n• All NX102 CPU Settings, and then se- Settings, and then se-\nUnit models*2 lect Do not use for lect Use for FINS/UDP.\nFINS/UDP.\n• NX701-1£20*2\n• All NX502 CPU\nUnit models*2\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-15\n5-2\nDefault\nStates\nof\nTCP/UDP\nPorts\nand\nthe\nChanging\nProcedure\n5\n5 TCP/IP Functions\nUDP TCP\nDefault\nApplica- port port How to change from How to change from\nCPU Unit model port Usage\ntion num- num- open to close close to open\nstate\nber ber\nFINS/TC • All NJ-series --- 9600 Open Used for On the Sysmac Studio, On the Sysmac Studio,\nP models the select Built-in select Built-in\n• All NX102 CPU FINS/ EtherNet/IP Port EtherNet/IP Port\nUnit models*2 TCP. Settings - FINS Settings - FINS\nSettings, and then se- Settings, and then se-\n• NX701-1£20*2\nlect Do not use for lect Use for FINS/TDP.\n• All NX502 CPU\nFINS/TCP.\nUnit models*2\nSysmac All models 9600 --- Open Used for Use the Packet Filter. *1 Use the Packet Filter.\nStudio CPU Unit with a 2224 --- Close*4 commu-\nUSB port nica-\n• All NJ-series tions\nmodels with the\n• All NX701 CPU Sysmac\nStudio.\nUnit models*3\nCIP All models 44818 44818 Open Used for On the Sysmac Studio, On the Sysmac Studio,\nmessag- the CIP select Built-in select Built-in\nes messag- EtherNet/IP Port EtherNet/IP Port\nes. Settings - CIP Settings - CIP\nSettings, and then se- Settings, and then se-\nlect Do not use for CIP lect Use for CIP\nMessage Server. Message Server.\nOPC UA CPU Units that sup- --- 4840 Close Used On the Sysmac Studio, On the Sysmac Studio,\nport OPC UA when select OPC UA select OPC UA\n• NJ501-1£00 using Settings - OPC UA Settings - OPC UA\n• All NX102 CPU the OPC Server Settings - Server Settings -\nUnit models*5 UA. Server Settings, and Server Settings, and\nthen select Do not use then select Use for\n• NX701-1£££*5\nfor OPC UA Server. OPC UA Server.\n• All NX502 CPU\nUnit models*5\nTCP/UD CPU Units that sup- 64000 64000 Close Used On the Sysmac Studio, On the Sysmac Studio,\nP mes- port TCP/UDP mes- when select Built-in select Built-in\nsage sage service using EtherNet/IP Port EtherNet/IP Port\nservice • All NX102 CPU the Settings - TCP/UDP Settings - TCP/UDP\nUnit models TCP/UD Message Service Message Service\n• All NX502 CPU P mes- Settings, and then se- Settings, and then se-\nUnit models sage lect Do not use for lect Use for TCP/UDP\nservice. TCP/UDP message message service.\nservice.\n*1. Closing the port may prevent communications with the Sysmac Studio. Refer to Troubleshooting When You Cannot Go\nOnline from the Sysmac Studio in the NJ/NX-series Troubleshooting Manual (Cat. No. W503) on how to make correc-\ntions.\n*2. This port number is supported only on Port 2. It cannot be used on Port 1.\n*3. Only if the CPU Unit has a USB port.\n*4. Always closed for the built-in EtherNet/IP port. Opened for the USB port only.\n*5. This port number is supported only on Port 1. It cannot be used on Port 2.\n*6. The NX502 CPU Units do not have this setting.\n5-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nPrecautions for Correct Use\nWhen using socket service instructions, specify the port number so that the port numbers used\ndo not overlap. If the port numbers used are duplicated, an error will occur during instruction\nexecution.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-17\n5-2\nDefault\nStates\nof\nTCP/UDP\nPorts\nand\nthe\nChanging\nProcedure\n5\n5 TCP/IP Functions\n5-3 Testing Communications\nIf the basic settings (in particular the IP address and subnet mask) have been made correctly for the\nbuilt-in EtherNet/IP port, then it is possible to communicate with nodes on the EtherNet/IP network.\nThis section describes how to use the PING command to test communications with the built-in Ether-\nNet/IP port.\n5-3-1 PING Command\nThe PING command sends an echo request packet to a remote node and receives an echo response\npacket to confirm that the remote node communications are normal. The PING command uses the\nICMP echo request and response. The echo response packet is automatically returned in the ICMP.\nThe PING command is normally used to check the connections of remote nodes when you set up a\nnetwork. The built-in EtherNet/IP port supports both the ICMP echo request and response functions.\nIf the remote node returns a normal response to the PING command, then the node is physically con-\nnected correctly and Ethernet node settings are correct.\nRemote node\n(e.g., host computer)\nBuilt-in EtherNet/IP port\nTCP UDP\nICMP IP\nEthernet\nEcho request\nEcho response\n5-3-2 Using the PING Command\nThe built-in EtherNet/IP port automatically returns an echo response packet in response to an echo\nrequest packet sent by another node (e.g., host computer).\nPrecautions for Correct Use\nWhen the Use Option is selected for Packet Filter of the built-in EtherNet/IP port, PING com-\nmand cannot be received unless icmp is selected for Protocol of Pacekt Filter settings. For the\ndetails on the settings, refer to Packet Filter on page 4-8.\n5-3-3 Host Computer Operation\nThe PING command can be executed from the host computer to send an echo request packet to a\nbuilt-in EtherNet/IP port.\nThe following example shows how to use the PING command in the host computer.\n5-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nApplication Method\nInput the following command at the host computer's prompt ($):\n$ ping IP_address (host_name)\nThe destination is specified by its IP address or host name.\nAdditional Information\nThe PING command is not supported by some host computers.\nApplication Example\nIn this example, a PING command is sent to the node at IP address 130.25.36.8.\nThe \"$\" in the example represents the host computer prompt.\n Normal Execution\n$ ping 130.25.36.8 Executes the PING command.\nPING 130.25.36.8: 56 data bytes\n64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms\n64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms\n: : : : :\n64 bytes from 130.25.36.8: icmp_seq=0. time=0. ms\nPress the Ctrl+C Keys to cancel execution.\n---- 130.25.36.8 PING Statistics ----\n9 packets transmitted, 9 packets received, 0% packets loss\nround-trip ms min/avg/max = 0/1/16\n$\n Error\n$ ping 130.25.36.8 Executes the PING command.\nPING 130.25.36.8: 56 data bytes\nPress the Ctrl+C Keys to cancel execution.\n---- 130.25.36.8 PING Statistics ----\n9 packets transmitted, 0 packets received, 100% packets loss\n$\nRefer to the command reference manual for your computer's OS for details on using the PING\ncommand.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-19\n5-3\nTesting\nCommunications\n5\n5-3-3\nHost\nComputer\nOperation\n5 TCP/IP Functions\n5-4 Packet Filter\nThis section provides an overview of Packet Filter, explains the specifications, settings, and usage ex-\namples.\n5-4-1 Introduction to Packet Filter\nThis function filters IP packets in the receive processing at the built-in EtherNet/IP ports. While Packet\nFilter (Simple) is used to restrict Sysmac Studio connections, Packet Filter performs general-purpose\npacket filtering that does not restrict communication partner to Sysmac Studio.\nPacket Filter settings are configured in the permit list. If any is set in Packet Filter, all packets are al-\nlowed. If a value other than any is set in Packet Filter, the received packet is compared with Packet\nFilter settings. When a matching packet is received, reception is permitted. When a non-matching\npacket is received, reception is prohibited and the packet is discarded. Packet Filter settings include\nthe source IP address, destination IP address, and TCP/UDP port number.\nSupport software or a device\nEthernet\nPacket\nSource IP address Destination IP address Source port Destination port\nCompare packets in order from No.1 in the list.\nIf matched: allow to receive the packet\nIf not matched: reject reception and discard the packet\nEtherNet/IP port Packet Filter settings\nNo. Source IP address Destination IP address Source port Destination port\n1 *.*.*.* *.*.*.* *** ***\nPacket Filter function\n2 *.*.*.* *.*.*.* *** ***\n: : : :\nPrecautions for Correct Use\n• If you use an NX701 CPU Unit, NX502 CPU Unit, NX102 CPU Unit, or NX1P2 CPU Unit and\ncannot go online with the Sysmac Studio because of forgetting the registered IP address, you\ncan disable this function tentatively by starting the Unit in Safe Mode. Refer to\nTroubleshooting When You Cannot Go Online from the Sysmac Studio in the NJ/NX-series\nTroubleshooting Manual (Cat. No. W503) for details.\n• If you use an NJ-series CPU Unit and cannot go online with the Sysmac Studio because of\nforgetting the registered IP address, connect using the USB port.\n• Packet Filter supports the stateful inspection. Therefore, if the Controller is specified as a cli-\nent, as in DNS, NTP, DB connection services, and communication instructions, you do not\nneed to add the responses from other devices to Packet Filter settings. For example, if you\nexecute the FTP client instruction of the Controller, you can receive responses from the FTP\nserver through stateful inspection even if you have not registered the response from the FTP\nserver in Packet Filter settings.\n5-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nVersion Information\nPacket Filter is available in the following CPU Units of the stated versions.\n• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later\n• NX701 CPU Unit: Version 1.29 or later\n• NX502 CPU Unit: Version 1.60 or later\n5-4-2 Packet Filter Specifications\nThe specifications for Packet Filter are given below.\nItem Specification Remarks\nFiltering system Permit list The system enables reception of\npackets registered in Packet Filter\nsettings and prohibits reception of\nunregistered packets.\nLocation to perform filtering Receive processing at the built-in • No filtering is applied to the\nEtherNet/IP port sending process of the built-in\n(If the Controller has two built-in EtherNet/IP port.\nEtherNet/IP ports, you can config- • Stateful inspection is supported.\nure the setting for each port.)\nNumber of Packet Filter tables 32\nSettings for Packet Filter tables • Source IP Address/Mask Range specification can be set for\n• Destination IP Address/Mask the IP address and TCP/UDP ports.\n• Protocol (tcp, udp, igmp, icmp)\nIf tcp or udp is selected for Proto-\ncol, specify the source port and\ndestination port.\n5-4-3 Packet Filter Settings\nFor details on Packet Filter settings, refer to Packet Filter on page 4-8.\nAdditional Information\nFor set values of Destination Port for each communication, refer to 5-4-5 Settings for Devices\nThat Access the Controller on page 5-33.\n5-4-4 Case Where Packet Filter Is Used\nPackets sent from a computer or a device to the Controller include the following four types of informa-\ntion.\n• Source IP address\nUnique numbers assigned to each source device. This address can be used to identify the source\ndevice.\n• Destination IP address\nUnique numbers assigned to each Controller that is the destination. This address can be used to\nidentify the Controller to which the packets are sent.\n• Source port\nA unique number assigned to the source application. This number can be used to identify the source\napplication.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-21\n5-4\nPacket\nFilter\n5\n5-4-2\nPacket\nFilter\nSpecifications\n5 TCP/IP Functions\n• Destination port\nA unique number assigned to the destination application. This number can be used to identify the\napplication to which the packets are sent.\nSource device Controller\nApplication Source port FTP server Destination port\nApplication Source port SNMP server Destination port\nApplication Source port CIP message server Destination port\n: : : :\nPacket Filter function\n(1) Filtering by source IP address Allow reception\n(2) Filtering by destination IP address\n(3) Filtering by source port\nProhibit reception\n(4) Filtering by destination port\nSource IP address Destination IP address\nPacket\nSource IP address Destination IP address Source port Destination port\nPacket Filter function can enable or disable the reception of packets using these four types of informa-\ntion. If the content of the packet matches the permitted content in Packet Filter settings, reception is\npermitted. Otherwise, reception is disabled and the packet is discarded.\nIn the case where Packet Filter is used, the four types of information are related as follows.\nCase where Packet Filter\nDescription Reference\nis used\n(1) Filtering by source IP Enables or disables reception of packets Case 1: Filtering by Source IP Ad-\naddress sent from a specific device. dress on page 5-23\n(2) Filtering by destination Only packets sent to a specific Controller Case 2: Filtering by Destination IP\nIP address are allowed to be received. Address on page 5-25\n(3)Filtering by source port Allow or disallow packets sent using a spe- Case 3: Filtering by Source Port on\ncific application. page 5-29\n(4)Filtering by destination Allow and receive only packets sent to a Case 4: Filtering by Destination\nport specific application. Port on page 5-31\nPacket Filter settings can also be set as shown below according to the case where the four types of\nPacket Filter are used.\n(1) Filtering by source IP address (2) Filtering by destination IP address (3) Filtering by source port (4) Filtering by destination port\nCase 1 Case 2 Case 3 Case 4\nThe following describes usage examples and set values for each of the four types of cases.\n5-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nCase 1: Filtering by Source IP Address\nYou can filter access to the Controller by source IP address. This is useful when the IP address can be\nused to distinguish client devices that are prohibited from communicating with client devices that are\npermitted to communicate. In Packet Filter’s source IP address setting, set the IP address of the de-\nvice that is allowed to communicate. Communications with devices whose IP addresses are not regis-\ntered are prohibited.\n Application Example\nAn application example under the following conditions is shown below.\n• Communications between the computer used in the facility and the Controller are permitted, and\ncommunications with a computer brought without permission are prohibited.\n• The IP addresses of the computers that are permitted to communicate are fixed.\n• The computers that are allowed to communicate have Sysmac Studio and OPC UA respectively.\nThe configuration of this application example is as follows.\nA computer brought without permission\nSysmac Studio Sysmac Studio OPC UA\nIP address:192.168.250.100/24 IP address:192.168.250.2/24 IP address:192.168.250.3/24\nEthernet\nProhibited Permitted\nNJ-series CPU Unit\nPacket Filter settings are as follows. Enter the IP address of the computer to use Sysmac Studio in\nthe No.1 Source IP Address field. Enter the IP address of the computer to use OPC UA in the\nNo.2 Source IP Address field.\nNo. Setting Set value\n1 Source IP Address Specification Method IP address specification\nIP Address 192.168.250.2\nMask 255.255.255.255\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-23\n5-4\nPacket\nFilter\n5\n5-4-4\nCase\nWhere\nPacket\nFilter\nIs\nUsed\n5 TCP/IP Functions\nNo. Setting Set value\n2 Source IP Address Specification Method IP address specification\nIP Address 192.168.250.3\nMask 255.255.255.255\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nAdditional Information\nYou can also mask the IP address to specify multiple devices that are allowed to communicate.\nThe following is sample Packet Filter settings to allow communications with devices with IP ad-\ndresses from 192.168.250.1 to 192.168.250.3.\nNo. Setting Set value\n1 Source IP Address Specification Method IP address specification\nIP Address 192.168.250.0\nMask 255.255.255.252\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\n Restrictions\nWhen filtering by the source IP address is used, communication from devices that are not regis-\ntered to the source IP address of Packet Filter settings is prohibited. Therefore, the IP addresses of\nall devices communicating with the Controller must be registered to the source IP addresses.\nIf the Controller cannot communicate with a device that you want to allow, make sure that the IP\naddress of that device is correctly set to the source IP address.\n5-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nCase 2: Filtering by Destination IP Address\nYou can filter access to the Controller by destination IP address in the packets received by the built-in\nEtherNet/IP port. This is useful in the following cases.\n• Where you want to prohibit the receipt of broadcast packets that are unnecessary for the Controller\n• Where you want to prohibit direct connection via Ethernet in the Sysmac Studio, but allow connec-\ntion by a specified IP address\n Application Example 1\nAn application example under the following conditions is shown below.\n• Reception of unnecessary broadcast packets for the Controller is prohibited.\n• Connection of Sysmac Studio through Ethernet connection via a hub is allowed and connec-\ntion through Direct connection via Ethernet is prohibited.\nThe configuration of this application example is as follows. Destination IP address for direct con-\nnection via Ethernet is 169. 254.***.***. Destination IP address of unnecessary broadcast packets\nfor the Controller is 192.168.250.255.\nSysmac Studio\nEthernet connection via a hub Broadcast packet\nDestination IP address:192.168.250.255\nDestination IP address:192.168.250.1\nSysmac Studio\nProhibited Ethernet Permitted\nDestination IP address:169.254.***.***\nDirect connection via Ethernet\nProhibited\nNJ-series CPU Unit\nIP address:192.168.250.1/24\nPacket Filter settings are as follows. Set the IP address for the Controller's built-in EtherNet/IP port\nto the destination IP address.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-25\n5-4\nPacket\nFilter\n5\n5-4-4\nCase\nWhere\nPacket\nFilter\nIs\nUsed\n5 TCP/IP Functions\nNo. Setting Set value\n1 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method IP address specification\nIP Address 192.168.250.1\nMask 255.255.255.255\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\n Application Example 2\nIf filtering by destination IP address is enabled in a Controller between devices, it can restrict the\ndevices that are allowed to communicate with each other.\nAn application example under the following conditions is shown below.\n• Controller A has two built-in EtherNet/IP ports.\n• Port 1 of Controller A is connected to the information network, and the computer with Sysmac\nStudio and the computer using Database are connected to the information network.\n• Port 2 of Controller A is connected to the control network, and Controller B and Controller C are\nconnected to the control network.\n• The computer with Sysmac Studio communicates only with Controller A and Controller B. The\ncomputer using Database only communicates with Controller C.\nThe configuration of this application example is as follows.\nSysmac Studio Database\nIP address:192.168.250.200/24 IP address:192.168.250.100/24\nEthernet\nPermitted Controller A\nInformation network\n(Built-in EtherNet/IP Port 1) Port 1 IP address:192.168.250.1/24\nPort 2 IP address:192.168.251.1/24\nControl network\n(Built-in EtherNet/IP Port 2)\nPermitted\nNX701 or NX102 CPU Unit\nEthernet\nController B Controller C\nNJ-series CPU Unit NJ-series CPU Unit\nIP address:192.168.251.2/24 IP address:192.168.251.3/24\n5-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nPacket Filter settings of Controller A are as follows.\nEnter the IP address of Controller A and Controller B to Destination IP Address field.\nEnter the IP address of the computer using Database to Port 2 Destination IP Address field.\nPort 1 Packet Filter Settings\nNo. Setting Set value\n1 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method IP address specification\nIP Address 192.168.251.2\nMask 255.255.255.255\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\n2 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method IP address specification\nIP Address 192.168.250.1\nMask 255.255.255.255\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nPort 2 Packet Filter Settings\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-27\n5-4\nPacket\nFilter\n5\n5-4-4\nCase\nWhere\nPacket\nFilter\nIs\nUsed\n5 TCP/IP Functions\nNo. Setting Set value\n1 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method IP address specification\nIP Address 192.168.250.100\nMask 255.255.255.255\nProtocol any\nSource Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method ---\nRange Specification ---\nStart Number ---\nEnd Number ---\nTo route different networks, the computers, Controller B, and Controller C must be configured with\na default gateway or an IP router table.\n Restrictions\nWhen filtering by the destination IP address is used, communication to an IP address not regis-\ntered in Packet Filter settings is prohibited. Therefore, all destination IP addresses of the packets\nthat you want to allow must be set to the destination IP address in Packet Filter settings.\nIn addition, attention should be paid to the following.\n• When you connect Sysmac Studio though Direct connection via Ethernet, set the Destination\nIP Address to 169.254.0.0 and the Destination Mask to 255.255.0.0, and allow 169.254. ***.***.\nOtherwise, the connection will fail.\n5-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nCase 3: Filtering by Source Port\nYou can filter access to the Controller by the source TCP/UDP port. This is useful when the source\nTCP/UDP ports can be used to distinguish communications that are prohibited from communications\nthat are permitted. In Packet Filter’s source port settings, register TCP/UDP ports that are allowed to\ncommunicate. Communications with unregistered TCP/UDP ports are prohibited.\n Application Example\nAn application example under the following conditions is shown below.\n• Communications between the computer used in the facility and the Controller (source port: fixed\nto TCP6000) are permitted, and communications with applications that are not permitted (source\nport: other than TCP6000) are prohibited.\n• An application running on the computer in the facility uses a socket communications program\nand has a fixed source port.\nThe configuration of this application example is as follows. The socket communications program\nthat is allowed to communicate uses TCP port 6000.\nOther application Socket communications Socket communications\nTCP port No. other than 6000 TCP port No. 6000 TCP port No. 6000\nEthernet\nProhibited Permitted\nNJ-series CPU Unit\nPacket Filter settings are as follows: For Protocol, tcp is selected and 6000 for the source port.\nNo. Setting Set value\n1 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol tcp\nSource Port Specification Method Port specification\nRange Specification No check.\nStart Number 6000\nEnd Number ---\nDestination Port Specification Method any\nRange Specification ---\nStart Number ---\nEnd Number ---\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-29\n5-4\nPacket\nFilter\n5\n5-4-4\nCase\nWhere\nPacket\nFilter\nIs\nUsed\n5 TCP/IP Functions\n Restrictions\nIf filtering by source port is used, communication from an unregistered TCP/UDP port is prohibited.\nTherefore, the TCP/UDP ports of all devices communicating with the Controller must be set as the\nsource ports.\nOmron's Support Software, such as Sysmac Studio, selects an unused port each time, so the user\ncannot specify the source port. Therefore, the destination port must be set according to the proto-\ncols used by the Omron’s Support Software. For details on the destination port settings, refer to\nCase 4: Filtering by Destination Port on page 5-31.\nIf the Controller cannot communicate with a device that you want to allow, make sure that\nTCP/UDP port used by the device is set correctly to the source port.\n5-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nCase 4: Filtering by Destination Port\nYou can filter access to the Controller by destination port in the packets received by the built-in Ether-\nNet/IP port. Because the destination port is determined for each communication protocol, this function\nis useful when the communication protocols used in the facility are fixed and you want to prohibit other\ncommunications protocols. Register the destination port of allowed communications in Packet Filter\nsettings. Communications using unregistered destination ports are prohibited.\n Application Example\nAn application example under the following conditions is shown below.\n• Communication protocols used in the facility are permitted, and the communication protocols not\nused in the facility are prohibited.\n• Access to the Controller from sources other than Sysmac Studio and OPC UA is prohibited in the\nfacility.\nThe configuration of this application example is as follows.\nSysmac Studio OPC UA FTP client\nProhibited\nEthernet\nPermitted\nController\nNJ-series CPU Unit\nPacket Filter settings are as follows. When Sysmac Studio version 1.50 or higher is connected, it\nuses TCP port 443. OPC UA uses TCP port 4840.\nSettings that allow Sysmac Studio to connect\nNo. Setting Set value\n1 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol tcp\nSource Port Specification Method any\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method Port specification\nRange Specification No check.\nStart Number 443\nEnd Number ---\nSettings that allow OPC UA to connect\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-31\n5-4\nPacket\nFilter\n5\n5-4-4\nCase\nWhere\nPacket\nFilter\nIs\nUsed\n5 TCP/IP Functions\nNo. Setting Set value\n2 Source IP Address Specification Method any\nIP Address ---\nMask ---\nDestination IP Address Specification Method any\nIP Address ---\nMask ---\nProtocol tcp\nSource Port Specification Method any\nRange Specification ---\nStart Number ---\nEnd Number ---\nDestination Port Specification Method Port specification\nRange Specification No check.\nStart Number 4840\nEnd Number ---\n Restrictions\nIf filtering by destination port is used, communications to an unregistered destination port are pro-\nhibited. Therefore, all destination ports used by the devices to communicate with must be regis-\ntered to the destination port.\nIf the destination ports are not registered, the devices may time out.\nIf communication with a device that you want to allow fails, make sure that the destination port\nused by the device is set correctly to the destination port of Packet Filter.\nAdditional Information\nSelecting the Do not use Option for each communications protocol closes the TCP/UDP port\nused for the communications protocol. This allows you to filter communications by destination\nport in the same way as in Case 4.\n5-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\n5-4-5 Settings for Devices That Access the Controller\nThis section shows the set values of Packet Filter for each device that accesses the Controller.\nSettings for Connecting Sysmac Studio\nThis section describes how to configure the destination port of Packet Filter when the Sysmac Studio\nis connected.\nThe setting values for the destination port differ as shown below depending on the connection type\nand setting on enabling connections to the Sysmac Studio and NA that are not supporting secure\ncommunication.\nSetting on ena- Destination port settings\nbling connec-\ntions to the Destination\nDestination Destina- Destina-\nSysmac Studio Port\nConnection type*1 Port tion Port tion Port\nand NA that are Protocol Range\nSpecification Start End\nnot supporting Specifica-\nMethod Number Number\nsecure commu- tion\nnication*2\nDirect connection via Enable tcp Port specification No check. 80 ---\nEthernet*3 udp Port specification No check. 9600 ---\ntcp*4 Port specification No check. 44818 ---\nudp*4 Port specification No check. 44818 ---\nicmp*4 --- --- --- ---\nDisable tcp Port specification No check. 443 ---\nudp Port specification No check. 9600 ---\nEthernet connection Enable tcp Port specification No check. 80 ---\nvia a hub tcp*4 Port specification No check. 44818 ---\nicmp*4 --- --- --- ---\nDisable tcp Port specification No check. 443 ---\nRemote connection Enable tcp Port specification No check. 80 ---\nvia USB*5 tcp Port specification No check. 44818 ---\nudp*6 Port specification No check. 44818 ---\nDisable tcp Port specification No check. 443 ---\ntcp Port specification No check. 44818 ---\nudp*6 Port specification No check. 44818 ---\n*1. For this setting, select Communications Setup from the Controller Menu, and select Connection type on\nthe Sysmac Studio.\n*2. Set with the DIP switch. Refer to Troubleshooting When You Cannot Go Online from the Sysmac Studio in\nthe NJ/NX-series Troubleshooting Manual (Cat. No. W503) for details.\n*3. For direct connection via Ethernet, the source and destination IP addresses must be set to 169.254. ***.***.\nWhen filtering by IP address is used, set 169.254.0.0 to IP address and 255.255.0.0 to mask to allow this\naddress.\n*4. This setting is required only when EtherNet/IP connection settings are made in the Sysmac Studio. This set-\nting is not required if no EtherNet/IP connection settings are made.\n*5. For remote connection via USB, specify the IP address of the relayed Controller as the source IP address.\nWhen filtering by IP address is used, allow this address.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-33\n5-4\nPacket\nFilter\n5\n5-4-5\nSettings\nfor\nDevices\nThat\nAccess\nthe\nController\n5 TCP/IP Functions\n*6. This packet is sent by local broadcast. Allow this address if filtering by destination IP address is enabled.\nFor example, if the Controller’s IP address is 192.168.250.1/24, specify 192.168.250.255 to the destination\nIP address.\nAdditional Information\n• To use the Ethernet Communications Test, which can be started by selecting Controller −\nCommunications Setup on the Sysmac Studio in the environment where Ethernet direct\nconnection is made, the following settings are required. Since this packet is sent by local\nbroadcast, allow this address when filtering by the destination IP address is used. For exam-\nple, if the Controller IP address is 192.168.250.1/24, specify 192.168.250.255 to the destina-\ntion IP address.\nDestination Port Destination Port Destination Port Destination Port\nProtocol\nSpecification Method Range Specification Start Number End Number\nudp Port specification No check. 9600 ---\n• When the Use Option is selected for Packet Filter of the relayed Controller in the environment\nwhere remote connection is made via USB, the following settings are required. In this case,\nthis packet has the connected Controller’s IP address as the source IP address and the re-\nlayed Controller’s IP address as the destination IP address. When filtering by IP address is\nused, allow these addresses.\nDestination Port Destination Port Destination Port Destination Port\nProtocol\nSpecification Method Range Specification Start Number End Number\nudp Port specification No check. 44818 ---\nSettings for Connecting Support Software Other Than Sysmac Stu-\ndio\nThe settings for connecting the Support Software other than Sysmac Studio are as follows.\nDestination port settings\nDestination Destination Destination Destination\nSupport Connection\nPort Port Port Port\nSoftware type Protocol\nSpecification Range Speci- Start Num- End Num-\nMethod fication ber ber\nNetwork Either Ethernet tcp*1 Port specifica- No check. 44818 ---\nConfigura- I/F or NJ/NX/NY tion\ntor for Series Ethernet udp*2 Port specifica- No check. 44818 ---\nEtherNet/IP Direct I/F tion\nicmp*1 --- --- --- ---\n5-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nDestination port settings\nDestination Destination Destination Destination\nSupport Connection\nPort Port Port Port\nSoftware type Protocol\nSpecification Range Speci- Start Num- End Num-\nMethod fication ber ber\nCX-Config- Either Ethernet Same settings as for Network Configurator.\nuratorFDT I/F or NJ/NX/NY\nSeries Ethernet\nDirect I/F\n(Communication\nDTM: OMRON\nEtherNet/IP)\nAny of Direct Same settings as for Sysmac Studio. Refer to Settings for Connecting Sysmac\nconnection via Studio on page 5-33 for settings for the Sysmac Studio.\nEthernet, The setting value differs depending on the version of CX-ConfiguratorFDT.\nEthernet For CX-ConfiguratorFDT version 2.57 or higher, set tcp: 443 for the destination\nconnection via port in Packet Filter settings.\na hub, or For CX-ConfiguratorFDT version 2.56 or lower, set tcp: 80 for the destination\nRemote port in Packet Filter settings.\nconnection via\nUSB\n(Communication\nDTM: Nx built-in\nEtherCAT or NX\nCPU Unit Bus)\nCX-Integra- Direct tcp Port specifica- No check. 9600 ---\ntor, CX- connection via tion\nProtocol Ethernet*3 udp Port specifica- No check. 9600 ---\n(Network type: tion\nEthernet (FINS/\nTCP))\nEthernet tcp Port specifica- No check. 9600 ---\nconnection via tion\na hub\n(Network type:\nEthernet (FINS/\nTCP))\nEthernet udp Port specifica- No check. 9600 ---\nconnection via tion\na hub\n(Network type:\nEthernet)\nCNC Oper- --- tcp any*4 --- --- ---\nator\nicmp --- --- --- ---\nSECS/GE --- tcp any*4 --- --- ---\nM Configu-\nicmp --- --- --- ---\nrator\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-35\n5-4\nPacket\nFilter\n5\n5-4-5\nSettings\nfor\nDevices\nThat\nAccess\nthe\nController\n5 TCP/IP Functions\nDestination port settings\nDestination Destination Destination Destination\nSupport Connection\nPort Port Port Port\nSoftware type Protocol\nSpecification Range Speci- Start Num- End Num-\nMethod fication ber ber\nSysmac Any of Direct Same settings as for Sysmac Studio. Refer to Settings for Connecting Sysmac\nConrtoller connection via Studio on page 5-33 for settings for the Sysmac Studio.\nLog Upload Ethernet, The setting value differs depending on the version of Sysmac Studio that is in-\nTool Ethernet stalled.\nconnection via For Sysmac Studio version 1.50 or higher, allow tcp: 443 for the destination\na hub, or port.\nRemote For Sysmac Studio version 1.49 or lower, allow tcp: 80 for the destination port.\nconnection via\nUSB\n*1. For NJ/NX/NY Series Ethernet Direct I/F connection, specify 169.254.***.*** for the source IP address and\ndestination IP address. When filtering by IP address is used, set 169.254.0.0 to IP address and 255.255.0.0\nto mask to allow this address.\n*2. When filtering by IP address is used, allow the following IP addresses.\n• NJ/NX/NY Series Ethernet Direct I/F: allow the following two addresses\na) Source IP address: Controller's IP address, Destination IP address: Local broadcast to the Control-\nler's network (When the Controller's IP address is 192.168.250.1/24, allow 192.168.250.255.)\nb) Source IP address :169.254.***. ***, Destination IP address :169.254.***. *** (IP address 169.254.\n***.*** is allowed by setting 169.254.0.0 to the IP address and 255.255.0.0 to the mask.)\n• Ethernet I/F Connection\na) Source IP address: Computer's IP address, Destination IP address: Local broadcast to the comput-\ner's network (When the computer's IP address is 192.168.250.100/24, allow 192.168.250.255.)\n*3. For Direct connection via Ethernet, the source and destination IP addresses must be set to 169.254.\n***.***. When filtering by IP address is used, set 169.254.0.0 to IP address and 255.255.0.0 to mask to allow\nthis address.\n*4. This is selected to connect in FTP Passive Mode. Because the port used for data connection is not uniquely\ndetermined, any must be selected for specification method.\nSettings for Connecting a Programmable Terminal\nThe settings for connecting Programmable Terminals are as follows.\nDestination port settings\nProgrammable Destination Port Destination Destination\nDestination Port\nTerminal Protocol Range Specifica- Port Port\nSpecification Method\ntion Start Number End Number\nNA-series tcp Port specification No check. 80 or 443*1 ---\nNS-series tcp Port specification No check. 80 ---\ntcp Port specification No check. 44818 ---\nNB-series udp Port specification No check. 9600 ---\n*1. For NA Runtime version 1.161 and NA5 system program version 10.0.0 or higher, set the destination port\nstart number to 443.\nSettings for Each Communications Protocol\nThe settings for each communications protocol are as follows.\n5-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n5 TCP/IP Functions\nDestination port settings\nDestination\nCommunications pro- Destination Port Destination Port Destination\nPort\ntocol Protocol Specification Meth- Range Specifica- Port\nEnd Num-\nod tion Start Number\nber\nBOOTP client udp Port specification No check. 68 ---\nDHCP client\nOPC UA server tcp Port specification No check. 4840*1 ---\nFINS/TCP server tcp Port specification No check. 9600*1 ---\nFINS/UDP server udp Port specification No check. 9600*1 ---\nSNMP agent udp Port specification Checked. 161*1 162*1\nFTP server*2 tcp Port specification Checked. 20 21*1\nIn Active Mode\nFTP server*2 tcp any*3 --- --- ---\nIn Passive Mode\nTCP/UDP message udp Port specification No check. 64000*1 ---\nservice\ntcp Port specification No check. 64000*1 ---\n*1. If the port number has been changed, the new port number must be set.\n*2. If the Controllers are FTP-clients, no Packet Filter settings are required.\n*3. Because the port used for data connection is not uniquely determined, any must be selected for specifica-\ntion method.\nSettings for Using EtherNet/IP Communications\nMake the following settings to use EtherNet/IP communications.\nDestination port settings\nDestination\nCommuni- Destination Destina- Destina-\nCommunica- Port cations Condition Port tion Port tion Port\ntions Protocol Range\nprotocol Specification Start End\nSpecifica-\nMethod Number Number\ntion\nCIP messages UCMM Server tcp Port specifica- No check. 44818 ---\ntion\nicmp*1 --- --- --- ---\nClass3 Server tcp Port specifica- No check. 44818 ---\ntion\nicmp*1 --- --- --- ---\nTag data links Class1 Originator igmp*2 --- --- --- ---\nTarget tcp Port specifica- No check. 44818 ---\ntion\nicmp*3 --- --- --- ---\nCIP Safety Class0 Originator igmp*2 --- --- --- ---\ncommunica-\nTarget tcp Port specifica- No check. 44818 ---\ntions\ntion\n*1. Select this if CX-Compolet/SYSMAC Gateway is a client.\n*2. Select this for Multicast.\n*3. Select this when SYSMAC Gateway is the originator.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 5-37\n5-4\nPacket\nFilter\n5\n5-4-5\nSettings\nfor\nDevices\nThat\nAccess\nthe\nController\n5 TCP/IP Functions\n5-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6\nTag Data Link Functions\n6-1 Introduction to Tag Data Links......................................................................6-2\n6-1-1 Tag Data Links.................................................................................................6-2\n6-1-2 Data Link Data Areas......................................................................................6-3\n6-1-3 Tag Data Link Functions and Specifications....................................................6-6\n6-1-4 Overview of Operation.....................................................................................6-7\n6-1-5 Starting and Stopping Tag Data Links...........................................................6-10\n6-1-6 Controller Status............................................................................................6-10\n6-1-7 Concurrency of Tag Data Link Data..............................................................6-14\n6-2 Setting Tag Data Links.................................................................................6-21\n6-2-1 Starting the Network Configurator.................................................................6-21\n6-2-2 Tag Data Link Setting Procedure...................................................................6-23\n6-2-3 Registering Devices......................................................................................6-23\n6-2-4 Creating Tags and Tag Sets..........................................................................6-25\n6-2-5 Connection Settings......................................................................................6-38\n6-2-6 Creating Connections Using the Wizard.......................................................6-48\n6-2-7 Creating Connections by Dragging and Dropping Devices...........................6-52\n6-2-8 Connecting the Network Configurator to the Network...................................6-54\n6-2-9 Downloading Tag Data Link Parameters.......................................................6-62\n6-2-10 Uploading Tag Data Link Parameters............................................................6-65\n6-2-11 Verifying Tag Data Link Parameters..............................................................6-68\n6-2-12 Starting and Stopping Tag Data Links...........................................................6-72\n6-2-13 Clearing the Device Parameters...................................................................6-75\n6-2-14 Saving the Network Configuration File..........................................................6-77\n6-2-15 Reading a Network Configuration File...........................................................6-78\n6-2-16 Checking Connections..................................................................................6-80\n6-2-17 Changing Devices.........................................................................................6-81\n6-2-18 Displaying Device Status...............................................................................6-83\n6-3 Ladder Programming for Tag Data Links...................................................6-85\n6-3-1 Ladder Programming for Tag Data Links.......................................................6-85\n6-3-2 Status Flags Related to Tag Data Links........................................................6-89\n6-4 Tag Data Links with Other Models..............................................................6-91\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-1\n6\n6 Tag Data Link Functions\n6-1 Introduction to Tag Data Links\n6-1-1 Tag Data Links\nTag data links enable cyclic tag data exchanges on an EtherNet/IP network between Controllers or be-\ntween Controllers and other devices. Variables are assigned to tags. (You can also assign I/O memory\naddresses to tags.)\nThe settings for tag data links are made with the Network Configurator. Refer to 6-2 Setting Tag Data\nLinks on page 6-21 for information on how to make the settings.\nAdditional Information\nYou can also use the Sysmac Studio to set the tag data links.\nRefer to A-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP Connections) on\npage A-5 for details on setting the tag data links on the Sysmac Studio.\nWith a tag data link, one node requests the connection of a communications line to exchange data\nwith another node.\nThe node that requests the connection is called the originator, and the node that receives the request\nis called the target.\nNJ/NX-series CPU Unit EtherNet/IP Unit CJ-series CPU Unit\nInput Output\nConnection\nTag set name: ABC Tag set name: OUT1\nVar_In_a I/O refreshing • Var_In_a • Var-Out1 Var-Out1(DM0)\nVar_In_b • • V Va ar r_ _I In n_ _b c Input tags Output tags • • V Vaa rr -- OO uu tt 32 I/O refreshing Var-Out2(DM100)\nVar_In_c Var-Out3(DM200)\nOriginator Target\nOutput Input DM00200\nVar_Out_d Connection\nTag set name: XYZ Tag set name: IN1 WR300\nVV aar r_ _O Ou ut t_ _e f I/O refreshing • • VV aa rr __O Ou ut t_ _ed Output tags Input tags • • D WM R0 30 02 000 I/O refreshing DM20100\n• Var_Out_f • DM20100\nController status\nController status Target Originator\nEEtthheerrNNeett//IIPP\nFor communications between Controllers, the connection information is set in the built-in EtherNet/IP\nport of the Controller that receives (consumes) the data (i.e., the originator).\nAdditional Information\nFor communications between a Controller and an I/O device, the connection information is set\nin the built-in EtherNet/IP port that is the originator. If an I/O device is used, the Network Config-\nurator must have an EDS file installed that includes connection information for the I/O device.\nRefer to A-3 EDS File Management on page A-42 for the installation procedure.\nThe output words and input words for each node for which data is exchanged must be set in the con-\nnection information. These words are called an output tag set and an input tag set, respectively. Each\ntag set must contain at least one tag.\n6-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nThe size of data for data exchange is the total size of tags included in the tag set. The size of the out-\nput tag set and the size of the input tag set must match.\nPrecautions for Correct Use\n• Select the Use Option for the CIP message server of the built-in EtherNet/IP port. If the Do\nnot use Option for the CIP message server is selected, tag data links cannot be performed.\nFor the details on the settings, refer to CIP Message Server on page 4-21.\n• If the Use Option is selected for Packet Filter of the built-in EtherNet/IP port, make sure to\npermit packets to be used for tag data links. If they are not permitted, tag data links are not\npossible. For the details on the settings, refer to Packet Filter on page 4-8.\n6-1-2 Data Link Data Areas\nTags\nA tag is a unit that is used to exchange data with tag data links.\nData is exchanged between the local network variables and remote network variables specified in the\ntags or between specified I/O memory areas.\nPrecautions for Correct Use\nTo maintain concurrency in the values of network variables that are assigned to tags, you must\nset refreshing tasks.\nRefer to 6-1-7 Concurrency of Tag Data Link Data on page 6-14 for details.\nTag Sets\nWhen a data link connection is established, one or more tags (up to eight tags including Controller sta-\ntus) are configured as a collective set of tags for the connection. This is called a tag set. Each tag set\nrepresents a unit of data for one tag data link connection.\nTag data links are therefore created through a connection between one tag set and another tag set. A\ntag set name must be set for each tag set.\nNoteA connection is used to exchange data as a unit within which data concurrency is maintained.\nThus, data concurrency is maintained for all the data exchanged for one or more tags in one tag set.\nPrecautions for Correct Use\nData with tags is exchanged in the order that the tags are registered in the tag set. Register the\ntags in the same order of the input and output tag sets.\n Example\nIn the following example, input tags \"a\" to \"g\" at the originator are a tag set named SP1_IN and\noutput tags \"I\" and \"ii\" are a tag set named SP1_OUT. A connection is set between these two tag\nsets.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-3\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-2\nData\nLink\nData\nAreas\n6 Tag Data Link Functions\nOriginator device Target device\nIP address: N\nConnection Information\nž Target IP address: N\nž Originator tag set SP1_IN\nž Target tag set: SP1_OUT\nž Packet interval (RPI)\nTag set (input) Tag set (output)\nTag set name: SP1_IN Tag set name: SP1_OUT\nController Status Controller Status\nTag i\nTag a\nConnection\nTag ii\nTag b\nTag c\n:\nTag g\nEtherNet/IP\nThere are input (consume) and output (produce) tag sets. Each tag set can contain either input\ntags or output tags. The same input tag cannot be included in more than one input tag set.\n Number of Tags in Tag Sets\nYou can set one or more tags for each of the input and output tag sets for one connection.\nFor example, you can set the input tag set with one tag, and the output tag set with more than one\ntag.\n• Tag Set with Only One Tag Each\nWith basic Network Configurator procedures, each tag set contains only one tag.\n6-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nNJ/NX-series CPU Unit CJ-series CPU Unit\nI/O memory\nTag set SP1_IN Tag set SP1_OUT\n(tag a) (tag c)\nConnection\nVariable a Variable c\nIndividual tags\nTag set SP2_OUT Tag set SP2_IN\n(tag b) (tag d)\nConnection\nVariable b Variable d\nEtherNet/IP\n• Tag Sets Each with Multiple Tags\nFor NX701 CPU Units, you can assign up to eight tags (up to 722 words in total) in one tag set.\nFor NX502 CPU Units, you can assign up to 64 tags (up to 722 words in total) in one tag set.\nFor NX102 CPU Units, NX1P2 CPU Units, and NJ-series CPU Units, you can assign up to eight\ntags (up to 300 words in total) in one tag set.\nNJ/NX-series CPU Unit CJ-series CPU Unit\nI/O memory\nTag set SP1_IN\n(group of tags a, b, and c)\nTag set SP1_OUT\nVariable a Variable f\nConnection\nVariable b Variable g\nVariable c Variable h Individual tags\nTag set SP2_OUT\nTag set SP2_IN\n(group of tags d and e)\nVariable d Connection Variable i\nVariable e Variable j\nEtherNet/IP\nNoteTo enable a connection, each tag set must include only one of ether input tags or output tags. (Both in-\nput and output tags cannot be included in one tag set.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-5\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-2\nData\nLink\nData\nAreas\n6 Tag Data Link Functions\n6-1-3 Tag Data Link Functions and Specifications\nThe tag data link and performance specifications of the NJ/NX-series CPU Unit are given below.\nSpecification\nNJ501-££££/NJ301-£\n£££/NJ101-££££\nItem NX701-££ NX502-££ NX102-££ NX1P2-££\nUnit ver- Unit ver-\n££ ££ ££ £££££\nsion 1.00 sion 1.03\nto 1.02 or later\nCommunications type Standard EtherNet/IP implicit communications (connection-type cyclic communica-\ntions)\nSetting method After you have set tags, tag sets, and connections with the Network Configurator,\nyou must download tag data link parameters to all devices on the EtherNet/IP net-\nwork. After the parameters are downloaded, the EtherNet/IP Units are restarted to\nstart the tag data links.\nYou can export network variables that you created on the Sysmac Studio to a CSV\nfile.\nYou can then import the file to the Network Configurator and assign the network\nvariables to the tags.\nTags Supported variable You can specify the following network variables as tags. *2, *3\n*1 types • Global variables\nMaximum number 722 words (1,444 bytes) 300 words (600 bytes)\nof words per tag\nMaximum number 256 256*4\nof tags (total of 512 with two ports)\nTag Maximum number 8 (7 when 64 (63 8 (7 when Controller status is included)\nsets of tags per tag set Controller when Con-\nstatus is in- troller sta-\ncluded) tus is in-\ncluded)\nMaximum number 722 words (1,444 bytes) 300 words (600 bytes)\nof words per tag\nset\nMaximum number 256 (total of 64 (total of 32 (total of 32\nof tag sets 512 with 128 with 40 with two\ntwo ports) two ports) ports)*5\nConnection Maximum Maximum Maximum Maximum number of connections per\nnumber of number of number of Unit: 32\nconnections connections connections\nper Unit: per Unit: per Unit: 64\n512 (256 128 (64 per (32 per\nper port) port) port)\nConnection type Each connection can be set for 1-to-1 (unicast) or 1-to-N (multicast) communica-\ntions.\nPacket intervals (RPI) 0.5 to 1 to 10,000 ms in 1-ms in- 2 to 10,000 10 to 1 to 10,000\n10,000 ms crements ms in 1-ms 10,000 ms ms in 1-ms\nin 0.5-ms increments in 1-ms in- increments\nincrements crements\nThe packet interval can be set separately for each connection.\n6-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nSpecification\nNJ501-££££/NJ301-£\n£££/NJ101-££££\nItem NX701-££ NX502-££ NX102-££ NX1P2-££\nUnit ver- Unit ver-\n££ ££ ££ £££££\nsion 1.00 sion 1.03\nto 1.02 or later\nAllowed communications 40,000 20,000 12,000 pps 3,000 pps 1,000 pps 3,000 pps\nbandwidth per Unit (pps) pps*6 pps*6 *6\nNote: The Note: The Note: The Note: The heartbeat is included.\nheartbeat is heartbeat heartbeat\nincluded. and the CIP and the CIP\nSafety rout- Safety rout-\ning are in- ing are in-\ncluded. *7 cluded. *8\n*1. When you specify a specific I/O memory address for a tag for an NX502 CPU Unit, NX102 CPU Unit,\nNX1P2 CPU Unit, or NJ-series CPU Unit, create a variable with an AT specification for the I/O memory ad-\ndress on the Sysmac Studio, and then specify the variable with the AT specification for the tag. For NX502\nCPU Units, NX102 CPU Units, and NX1P2 CPU Units, you need to set memory used for CJ-series Unit to\nuse the I/O memory address.\nFor details on memory settings used for CJ-series Unit, refer to the NJ/NX-series CPU Unit Software User's\nManual (Cat. No. W501).\n*2. You can import network variables created in the Sysmac Studio to the Network Configurator as tags.\nIf variables for which Network publish attribute is set on the Sysmac Studio contain I/O memory addresses,\nsuch as \"0000\" and \"H0000\", they are not exported to CSV files.\n*3. The following table lists variables that you can specify as tags.\nData types Example Specification\nVariables with basic data types aaa Supported\nEnumerated variables bbb Supported\nArray variables Arrays ccc Supported\nElements ccc[2] Supported\nStructure variables Structures ddd Supported\nMembers ddd.xxx Supported\nUnion variables Unions eee Supported\nMembers eee.yyy Supported\n*4. The maximum number of tags is given for the following conditions.\n• All tag sets contain eight tags.\n• The maximum number of tag sets (32) is registered.\n*5. If more than 40 tag sets are set in total, a Number of Tag Sets for Tag Data Links Exceeded (840E0000 hex)\nevent occurs.\n*6. If the two built-in EtherNet/IP ports are used simultaneously, the maximum communications data size means\nthe maximum data size of the total of the two ports.\n*7. An NX502 CPU Unit with unit version 1.64 or later is required to use the CIP Safety routing.\n*8. An NX102 CPU Unit with unit version 1.31 or later is required to use the CIP Safety routing.\n6-1-4 Overview of Operation\nIn this manual, the connection information that is set is called tag data link parameters.\nThis section describes how to set tag data links with the Sysmac Studio and the Network Configurator.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-7\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-4\nOverview\nof\nOperation\n6 Tag Data Link Functions\nSetting Network Variables (Sysmac Studio)\nFirst, create any variables that you want to use for tag data links as network variables on the Sysmac\nStudio.\n1\nSet the Network Publish attribute to Input or Output in the Global Variable Table for variables\nyou want to use for tag data links (i.e., as tags).\n2\nTo maintain concurrency in tag data within a tag set, set all tags (i.e., variables with a Network\nPublish attribute) within the same tag set as follows:\nSet a refreshing task for variables with a Network Publish attribute to maintain concurrency for\ntag data link data as described below.\n• Maintain concurrency in the tag data in a tag set.\n• The timing of updating network variables that are assigned to tags is synchronized with the\nexecution period of a program that accesses the network variables.\nRefer to 6-1-7 Concurrency of Tag Data Link Data on page 6-14 for details on the concurren-\ncy of tag data link data.\nPrecautions for Correct Use\n• If a variable with an AT specification is used as a tag, you do not need to set a refreshing\ntask.\nIt is refreshed in the primary periodic task.\n• You cannot use the following notation, which specifies an I/O memory address, in the variable\nname of any variable used in a tag data link.\na) Variable names that contain only single-byte numerals (Example: 001)\nb) Variable names with the following single-byte letters (uppercase or lowercase) followed by\nsingle-byte numerals\n1) H (Example: H30)\n2) W (Example: w30)\n3) D (Example: D100)\n4) E0_ to E18_\n• When the server function of CIP message communications is disabled, the tag data links can-\nnot be used. Enable the server function of CIP message communications. Refer to CIP Mes-\nsage Server on page 4-21 for details on setting CIP message server.\nSetting and Downloading Tag Data Link Parameters (Network Con-\nfigurator or Sysmac Studio)\nThe following tag data link parameters (e.g., connection information) are created with the Network\nConfigurator or the Sysmac Studio, and then the parameters are downloaded to all originator devices\non the EtherNet/IP network.\n6-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nWhen the tag data links are used on built-in EtherNet/IP ports, use the Network Configurator to make\nthe following settings.\nAdditional Information\nIn the settings of the following tag data link parameters, the specifications of the settable num-\nbers and the ranges differ depending on the CPU Unit or the version of the CPU Unit. For de-\ntails, refer to 1-3-1 Specifications on page 1-9.\n1\nCreating the Configuration Information\nRegister EtherNet/IP ports and EtherNet/IP Units to create connections that define the tag data\nlinks. For details, refer to 6-2-3 Registering Devices on page 6-23.\n2\nSetting Tags\nCreate CPU Unit variables for input (consume) tags and output (produce) tags.\nYou can import and export network variables that are created on the Sysmac Studio to CSV\nfiles. This allows you to register them as tags on the Network Configurator.\nOutput (produce) tags can be defined to clear output data to 0 or to hold the output data from\nbefore the error when a fatal error occurs in the CPU Unit.\n3\nSetting Tag Sets\nCreate output tag sets and input tag sets and assign tags to them. (You can create up to eight\nI/O tag sets.) You can specify the Controller status that indicates the CPU Unit's operating sta-\ntus (operating information and error information) in a tag set.\n4\nSetting connections\nLink the output tag sets for the target device and the input tag sets for the originator device as\nconnections.\n Connection Setting Parameters\nThe connection settings in step 4 above have the following setting parameters.\n• Setting the Requested Packet Interval (RPI)\nThe RPI (Requested Packet Interval) is the I/O data refresh cycle on the Ethernet line when tag\ndata links are established. With EtherNet/IP, data is exchanged on the communications line at\nthe RPI that is set for each connection, regardless of the number of nodes.\nWith the built-in EtherNet/IP port, you can set RPI for each connection.\n• Setting Multi-cast or Unicast Communications\nYou can select a multicast connection or unicast (point-to-point) connection as the connection\ntype in the tag data link connection settings.\nWith a multicast connection, you can send an output tag set in one packet to multiple nodes and\nmake allocations to the input tag sets.\nA unicast connection separately sends one output tag set to each node, and so it sends the\nsame number of packets as the number of input tag sets.\nTherefore, multicast connections can decrease the communications load if one output tag set is\nsent to multiple nodes.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-9\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-4\nOverview\nof\nOperation\n6 Tag Data Link Functions\nTo use a multicast connection and send an output tag set in one packet to multiple nodes, the\nfollowing settings for the receiving node must be the same as the settings of the sending node:\nthe connection type (multicast), the connection I/O type, packet internal (RPI), and timeout value.\nPrecautions for Correct Use\n• The performance of communications devices is limited to some extent by the limitations of\neach product's specifications. Consequently, there are limits to the packet interval (RPI) set-\ntings.\nRefer to 14-2 Adjusting the Communications Load on page 14-7Checking the Device Band-\nwidth Usage on page A-25 and set an appropriate packet interval (RPI).\n• If multicast connections are used, however, use an Ethernet switch that has multicast filtering,\nunless packets are received by all nodes in the network.\nIf an Ethernet switch without multicast filtering is used, multicast packets are broadcast to the\nentire network, and so the packets are sent to nodes that do not require them, which will\ncause the communications load on those nodes to increase.\n• If you use data tag links with multicast traffic at a baud rate over 100 Mbps, use an Ethernet\nswitch that supports a baud rate of 1000 Mbps.\nIf there is an Ethernet device on the same network that communicates at 100 Mbps or less,\nthe device may affect tag data link communications and cause tag data links to be broken,\neven if the device is not related to tag data link communications.\nAdditional Information\n• To calculate the number of connections of each connection type, refer to 14-1-2 Calculating\nthe Number of Connections on page 14-4.\n• If the maximum number of connections is exceeded, you must review the number of connec-\ntions for the built-in EtherNet/IP port, or the number of nodes. When you use an NJ-series\nCPU Unit, you can also consider adding EtherNet/IP Units.\n6-1-5 Starting and Stopping Tag Data Links\nTag data links are automatically started when the data link parameters are downloaded from the Net-\nwork Configurator and the power supply to the NJ/NX-series Controller is turned ON.\nThereafter, you can start and stop tag data links for the entire network or individual devices from the\nNetwork Configurator. Starting and stopping tag data links for individual devices must be performed for\nthe originator.\nFurthermore, you can use system-defined variables to start and stop the entire network. Refer to\n6-2-12 Starting and Stopping Tag Data Links on page 6-72 for details.\n6-1-6 Controller Status\nYou can include the Controller status as a member of a tag set in the data sent and received.\nThe Controller status is a set of flags that indicate the operating status of the CPU Unit (operating in-\nformation, error information, Controller error level).\nIf the Controller status is specified as an output (produce) tag, the Controller status is added to the\nstart of the tag set in the following format.\n(Select the Include Option for Controller Status in the upper right of the Edit Tag Set Dialog Box.)\n6-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0\n0 0 0 0 0 0 0 0 0 0 0\nController Operating Flag\nMinor fault level\nController error\nController Error Flag\nPartial fault level Controller error\nMajor fault level\nController error\nNoteOf the flags in bits 5 to 7 that indicate the current error level, only the flag for the highest error level changes\nto TRUE.\nFor example, if a minor fault level Controller error and a major fault level Controller error occur at the same\ntime, only the flag for the major fault level Controller error (bit 7) will change to TRUE and the flag for the\nminor fault level Controller error (bit 5) will remain as FALSE.\nTo receive the Controller status, specify the Controller status for the In - Consume Tab Page in the\ndialog box used to edit the receive tag set.\n(Select the Include Option for Controller Status in the upper right of the Edit Tag Set Dialog Box.)\nWhen a tag data link is started, the contents of the Controller status is stored in the system variables\nthat are given below.\n• Target PLC Operating Mode\nNX701 CPU Unit: _EIP1_TargetPLCModeSta (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCModeSta (for the built-in EtherNet/IP port 2)\nNX102 CPU Unit: _EIP1_TargetPLCModeSta (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCModeSta (for the built-in EtherNet/IP port 2)\nNX502 CPU Unit: _EIP1_TargetPLCModeSta (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCModeSta (for the built-in EtherNet/IP port 2)\nNX1P2 CPU Unit: _EIP1_TargetPLCModeSta (for the built-in EtherNet/IP port 1)\nNJ-series CPU Unit _EIP_TargetPLCModeSta\n• Target PLC Error Information\nNX701 CPU Unit: _EIP1_TargetPLCErr (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCErr (for the built-in EtherNet/IP port 2)\nNX102 CPU Unit: _EIP1_TargetPLCErr (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCErr (for the built-in EtherNet/IP port 2)\nNX502 CPU Unit: _EIP1_TargetPLCErr (for the built-in EtherNet/IP port 1)\n_EIP2_TargetPLCErr (for the built-in EtherNet/IP port 2)\nNX1P2 CPU Unit: _EIP1_TargetPLCErr (for the built-in EtherNet/IP port 1)\nNJ-series CPU Unit: _EIP_TargetPLCErr\nExample: Using an NJ-series CPU Unit to send the Target PLC Operating Mode of the Target Node\nwith an IP Address of 192.168.250.2\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-11\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-6\nController\nStatus\n6 Tag Data Link Functions\nIP address = 192.168.250.2\n_EIP_TargetPLCModeSta (Target PLC Operating Mode)\n0\nValue of last byte = 2 1\n2\nTarget node ID = #002\n254\n255\nNJ-series Controller CJ-series CPU Unit\nController status\nController status (when included) Controller status (when included)\nController Status\nI/O memory\nOutput tag set Input tag set\nVariable a Variable f\nConnection\nVariable b Variable g\nVariable c Variable h\nTarget data link status\nEtherNet/IP\nAdditional Information\nThe target node ID may be duplicated depending on the IP address of the target node. In this\ncase, it is necessary to change the target node ID on the Network Configurator so that the\nsame address could not be used by more than one node.\nFor information on how to change the target node ID, refer to Step 4 under Registering Devices\nin the Register Device List in Connection Settings in 6-2-5 Connection Settings on page 6-38.\nWhen you use multiple connections to communicate with one specific node, the information of the\nController status is stored in the following variables if the Controller status is specified in the input tags\nand the output tags for all the connections.\n6-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nController sta-\nVariable name Description of operation\ntus\nController Oper- Target PLC Operating Mode This flag shows the operation information of the\nating Flag • NX701 CPU Unit Controller at the target node.\n_EIP1_TargetPLCModeSta (for (When the Built-in EtherNet/IP Port Is the Originator\nthe built-in EtherNet/IP port 1), or of the Connection)\n_EIP2_TargetPLCModeSta (for The array element that corresponds to the target\nthe built-in EtherNet/IP port 2) node ID at the target is set to TRUE when all infor-\n• NX102 CPU Unit mation for all the connections to the relevant target\n_EIP1_TargetPLCModeSta (for node shows operating status.\nthe built-in EtherNet/IP port 1), or You can change the target node ID for the IP ad-\n_EIP2_TargetPLCModeSta (for dress from the Network Configurator.\nthe built-in EtherNet/IP port 2) This status information is enabled when the Control-\n• NX502 CPU Unit ler status is included in the communications data for\n_EIP1_TargetPLCModeSta (for both the originator and the target node.\nthe built-in EtherNet/IP port 1), or This variable is updated when necessary.\n_EIP2_TargetPLCModeSta (for\nthe built-in EtherNet/IP port 2)\n• NX1P2 CPU Unit\n_EIP1_TargetPLCModeSta (for\nthe built-in EtherNet/IP port 1)\n• NJ-series CPU Unit\n_EIP_TargetPLCModeSta\nController Error Target PLC Error Information This variable shows the error status (logical OR of\nFlag • NX701 CPU Unit fatal and non-fatal errors) of the target node Control-\n_EIP1_TargetPLCErr (for the built- lers.\nin EtherNet/IP port 1), or (When the Built-in EtherNet/IP Port Is the Originator\n_EIP2_TargetPLCErr (for the built- of the Connection)\nin EtherNet/IP port 2) You can change the target node ID for the IP ad-\n• NX102 CPU Unit dress from the Network Configurator.\n_EIP1_TargetPLCErr (for the built- The Controller Error Flags are enabled when the\nin EtherNet/IP port 1), or Controller status is included in the communications\n_EIP2_TargetPLCErr (for the built- data for both the originator and target node.\nin EtherNet/IP port 2) This variable is updated when necessary.\n• NX502 CPU Unit\n_EIP1_TargetPLCErr (for the built-\nin EtherNet/IP port 1), or\n_EIP2_TargetPLCErr (for the built-\nin EtherNet/IP port 2)\n• NX1P2 CPU Unit\n_EIP1_TargetPLCErr (for the built-\nin EtherNet/IP port 1)\n• NJ-series CPU Unit\n_EIP_TargetPLCErr\nAdditional Information\nEven if you specify including the Controller status in output (produce) tags, you do not necessa-\nrily need to include the Controller status in input (consume) tags.\nIf you do not include the Controller status in an input (consume) tag, the contents of the Control-\nler status are not updated in the Target PLC Operating Mode and Target PLC Error Information\nvariables, but they are sent in the input (consume) tag.\nTherefore, you can use the Controller status data that was received in the input (consume) tag\nas receive data.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-13\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-6\nController\nStatus\n6 Tag Data Link Functions\n6-1-7 Concurrency of Tag Data Link Data\nTo maintain the concurrency of data in a tag data link, you must set a refreshing task for each network\nvariable that is assigned to a tag.\n• Maintain concurrency in tag data in a tag set.\n• The timing of updating network variables that are assigned to tags is synchronized with the execu-\ntion period of the program that accesses the network variables\nAdditional Information\nA refreshing task maintains concurrency of the value of a global variable from all tasks that ac-\ncess that global variable. This is achieved by specifying a single task that can write to that glob-\nal variable and not allowing any other task to write to that global variable.\nFor details on refreshing tasks, refer to the NJ/NX-series CPU Unit Software User's Manual\n(Cat. No. W501).\nMaintaining Concurrency in the Tag Data in a Tag Set\nTo maintain concurrency in the values of multiple tags in a tag set, the tags (variables with a Network\nPublish attribute) must satisfy all of the following conditions.\na. The tags must be assigned to the same tag set (connection).\nb. A refreshing task must be set for network variables assigned to the tags, and the refreshing task\nmust be the same for all the tags in the tag set. *1\nc. For NX502, NX102, NX1P2, and NJ-series CPU Units, a tag with an AT specification must not be\nincluded in the tag set.\nd. The variable access time set for each task must be set to a higher value than is required to transfer\nthe tag data.\nRefer to 14-3-3 Relationship between Task Periods and Packet Intervals (RPIs) on page 14-26 for\ndetails on the variable access time and data transfer.\n*1. If you set a refreshing task for network variables, you must set a variable access time to allocate enough time\nto access the network variables from outside of the Controller.\n• Setting Refreshing Tasks for Tags (Network Variables)\nConcurrency of the tags in the tag set is maintained.\n6-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nNJ/NX-series Controller NJ/NX-series Controller\nRefreshing task Refreshing task\nValue of variable Tag set Tag set Value of variable\nVariable a 100\"10 Variable a Connection Variable d 10\nThe values of the\nVariable b 100\"10 Variable b Tag data links updated. Variable e 10 tags in the tag set\nare refreshed at\nVariable c 100\"10 Variable c Variable f 10 the same time.\nEtherNet/IP\nAdditional Information\nFor NX502, NX102, NX1P2, and NJ-series CPU Units, you do not need to set a refreshing task\nfor variables (tags) with AT specifications since they are updated in the primary periodic task.\n• Not Setting Refreshing Tasks for Tags (Network Variables)\nConcurrency of the tags in the tag set is not maintained.\nNJ/NX-series Controller NJ/NX-series Controller\nRefreshing task Refreshing task\nValue of variable Tag set Tag set Value of variable\nThe\nvalues of\nVariable a 100 → 10 Variable a Connection Variable d 10 Refreshed. tags in\nthe tag\nVariable b 100 → 10 Variable b Tag data links updated. Variable e 10 Refreshed. set are\nnot\nrefreshed\nVariable c 100 → 10 Variable c Variable f 100 Not refreshed. at the\nsame\ntime.\nEtherNet/IP\nSynchronizing the Update Timing of Network Variables (Tags) with\nthe User Program Execution Period\nTo have the values of network variables (tags) updated to the latest tag data values each time the user\nprogram that accesses those network variables is executed, set the refreshing task for the network\nvariables (tags) to the same type of the task as for the user program that accesses the network varia-\nbles (tags).\nThe difference between the operation of tags with a refreshing task that is the same as the user pro-\ngram and tags without a refreshing task is described below.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-15\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-7\nConcurrency\nof\nTag\nData\nLink\nData\n6 Tag Data Link Functions\n• Tag (network variable) with a refreshing task\nThe tag is refreshed each time the program with the task that is set as the refreshing task is execut-\ned.\n• Tag (network variable) without a refreshing task\nThe tag (network variable) is refreshed in the following processing. Refreshing is not synchronized\nwith the execution timing of the program.\na) NJ-series Controller, NX102, and NX1P2 CPU Units: System service\nb) NX701 CPU and NX502 CPU Units: Tag data link variable access service\nThe following figures show the refreshing timing of network variables for the respective CPU Units.\nNX701 CPU Unit\n• The tag data link service and tag data link variable access service are executed without being affect-\ned by the task and system services.\n• The system services are executed at the required time without being affected by the task, tag data\nlink service, and tag data link variable access service.\n(1) Execution timing of the program\n(2) Refresh timing of network variables (tags) with the primary periodic task set as the refreshing task*\n(3) Refresh timing of network variables (tags) that do not have the primary periodic task set as the refreshing task\n(1) (2) (1) (2) (1) (2) (1) (2) (1) (2)\nPrimary period\nExecution\npriority\nHigh\nIOUPG MC IOUPG MC IOUPG MC IOUPGMC IOUPG MC\nPrimary\nperiodic task\nTask period\nPriority-16 IOUPG (2) IO UPG\nperiodic task\nTag data link\nservice\n(3)\nTag data is read\nTag data link\nfrom the tag set.\nvariable\naccess service\nTask period\nPriority-17\nUPG Pausing\nperiodic task\nLow\n*: Refreshed during system common processing 2 in the task processing.\nNX502 CPU Unit\n• Communications bridge service, tag data link service, tag data link refresh service for X Bus Units,\ntag data link variable access service, and system services can be executed in parallel with task exe-\ncution.\n• The order of execution priority is in the following order; communications bridge service, tag data link\nservice, tag data link refresh service for X Bus Units, tag data link variable access service. The sys-\ntem services are executed without being affected by the communications bridge service, tag data\nlink service, tag data link refresh service for X Bus Units, and tag data link variable access service.\n6-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n(1) Execution timing of the program\n(2) Refresh timing of network variables (tags) with the primary periodic task set as the refreshing task*\n(3) Refresh timing of network variables (tags) that do not have the primary periodic task set as the refreshing task\n(1) (2) (1) (2) (1) (2) (1) (2) (1) (2)\nExecution\nPrimary period\npriority\nHigh\nPrimary IO UPGMC IO UPGMC IO UPGMC IO UPGMC IO UPGMC\nperiodic task\nExecution interval of the communucations bridge service\nCommunications\nbridge service\nExecution time\nof the communucations bridge service\n(2)\nTag data link\nservice\nExecution time of the tag data link service\nTag data is read\nfrom the tag set.\nTag data link\nrefresh service\nfor X Bus Units\nExecution time of the tag data link refresh\nservice for X Bus Units\n(3)\nTag data link\nvariable\naccess service\nExecution time of the tag data link variable\naccess service\nTask period\nPriority-17 UPG Pausing\nperiodic task\nLow\n*: Refreshed during system common processing 2 in the task processing.\nVersion Information\n• The communications bridge service is executed for an NX502 CPU Unit with unit version 1.64\nor later.\n• The tag data link refresh service for X Bus Units is executed when the NX502 CPU Unit with\nunit version 1.66 or later and the NX-series EtherNet/IP Unit with unit version 1.01 or later are\nused together.\nNX102 CPU Units\n• The communications bridge service, tag data link service and system service can be executed in\nparallel with the tasks.\n• The execution priority is higher in the order of communications bridge service, tag data link service\nand then system service.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-17\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-7\nConcurrency\nof\nTag\nData\nLink\nData\n6 Tag Data Link Functions\n(1) Execution timing of the program\n(2) Refresh timing of network variables (tags) with the primary periodic task set as the refreshing task*\n(3) Refresh timing of network variables (tags) that do not have the primary periodic task set as the refreshing task\n(1) (2) (1) (2) (1) (2) (1) (2) (1) (2)\nExecution\nPrimary period\npriority\nHigh\nPrimary IO UPGMC IO UPGMC IO UPGMC IO UPGMC IO UPGMC\nperiodic task\nExecution interval of the communucations bridge service\nCommunications\nbridge service\n(2)\nExecution time\nof the communucations bridge service\nTag data link\nservice\nTag data is read Execution time of the tag data link service\nfrom the tag set.\n(3)\nTask period\nPriority-17\nperiodic task UPG Pausing\nSystem\nservices\nLow\n(3)\n*: Refreshed during system common processing 2 in the task processing.\nVersion Information\nThe communications bridge service is executed by the NX102 CPU Unit with unit version 1.31\nor later.\nNX1P2 CPU Unit\n• The tag data link service, option board service, and system services can be executed in parallel with\nthe the execution of tasks.\n• The order of execution priority is tag data link service, option board service and then system serv-\nices.\n6-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n(1) Execution timing of the program\n(2) Refresh timing of network variables (tags) with the primary periodic task set as the refreshing task*\n(3) Refresh timing of network variables (tags) that do not have the primary periodic task set as the refreshing task\n(1) (2) (1) (2) (1) (2) (1) (2) (1) (2)\nPrimary period\nExecution\npriority\nHigh Primary IOUPGMC IOUPGMC IOUPGMC IOUPGMC IOUPGMC\nperiodic task\nTag data link service execution interval\n(2)\nTag data link\nservice\n(3)\nTag data is read\nOption board from the tag set.\nservice\nTask period\nPriority-17\nUPG Pausing\nperiodic task\nSystem service\n(3)\nLow *: Refreshed during system common processing 2 in the task processing.\nNJ-series CPU Units\n• Execution of the tag data link service is given priority over execution of the priority-17 periodic task.\nHowever, execution of the primary periodic task and priority-16 periodic task is given even higher\npriority.\n• System services are executed in unused time between execution of all of the tasks and tag data link\nservice.\n(1) Execution timing of the program\n(2) Refresh timing of network variables (tags) with the primary periodic task set as the refreshing task*\n(3) Refresh timing of network variables (tags) that do not have the primary periodic task set as the refreshing task\n(1) (2) (1) (2) (1) (2) (1) (2) (1) (2)\nExecutio n\npriority Primary period\nHigh IOUPG MC IOUPG MC IOUPG MC IOUPGMC IOUPG MC\nPrimary\nperiodic task\nTask period\nPriority-16 IOUPG IO UPG\nperiodic task (2)\n(3)\nTag data link\nservice\nTask period\nPriority-17 Tag data is read UPG Pausing\nperiodic task from the tag set. (3)\n.....The system service is executed\nSystem service\nduring free time between task\nexecution.\nLow *: Refreshed during system common processing 2 in the task processing.\nAdditional Information\nIf a user program needs to access a network variable with an AT specification, set the program\nin the primary periodic task so that it matches the refresh timing of the network variable with the\nAT specification. (This applies to NX502, NX102, NX1P2, and NJ-series CPU Units.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-19\n6-1\nIntroduction\nto\nTag\nData\nLinks\n6\n6-1-7\nConcurrency\nof\nTag\nData\nLink\nData\n6 Tag Data Link Functions\nAdditional Information\nRelationship between Refreshing Tasks and Data Concurrency in Tag Data Links\nIf you do not specify a refreshing task for global variables in tag data links, the following may\noccur."}
+{"question": "When data is sent for the output tag set, another task may have already written different val-", "answer": "ues before that data is sent, depending on the timing of the task."}
+{"question": "When data is received by an input tag set, another task may write different values after that", "answer": "data is received, depending on the timing of the task.\nTherefore, to maintain concurrency of data in tag data links, you must specify the same re-\nfreshing task on both the output CPU Unit and the input CPU Unit.\nNJ/NX-series CPU Unit NJ/NX-series CPU Unit\nRefreshing Refreshing\ntask task\nThis variable may Tag set Tag set\nalready be written This variable\nby another task Variable a Connection Variable d may be written\nbefore you send by another task\nthe data. after you receive\nVariable b Tag data links Variable e the data.\nupdated.\nVariable c Variable f\nEtherNet/IP\nData concurrency is not maintained\nunless you assign the same\nrefreshing task for both the output\nand the input tags.\nRequired Processing Time to Maintain Concurrency\nWhen you set a refreshing task for tags (network variables) to maintain the concurrency of data link\ndata, the processing time required for that specified task increases. Due to this increase in task proc-\nessing time, tag data link data may not be refreshed at the packet interval (RPI) period set for each\nconnection.\nTherefore, you need to adjust the packet interval (RPI) settings to match the period of the task speci-\nfied as the refreshing task.\nRefer to 14-3-3 Relationship between Task Periods and Packet Intervals (RPIs) on page 14-26 for de-\ntails.\nTask Setup Procedure"}
+{"question": "Set the global variables for which to specify a refreshing task, and set the refreshing tasks and ac-", "answer": "cessing tasks in the Settings for Exclusive Control of Variables in Tasks in the Task Setup Tab\nPage on the Sysmac Studio."}
+{"question": "Set the variable access time for each refreshing task.", "answer": "For details, refer to NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501).\n6-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-2 Setting Tag Data Links\nAdditional Information\nYou can also use the Sysmac Studio to set the tag data links.\nRefer to A-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP Connections) on\npage A-5 for details on setting the tag data links on the Sysmac Studio.\n6-2-1 Starting the Network Configurator\nProcedure\nTag data links are set from the Network Configurator. Use the following procedure to start the Network\nConfigurator.\n Using the Windows Start Menu\nTo start the Network Configurator, select OMRON – Sysmac Studio – Network Configurator for\nEtherNetIP – Network Configurator.\nWhen the Network Configurator starts, the following window is displayed.\nMain Window\nThe Main Window consists of a Hardware List and a Network Configuration Pane, as shown in the\nfollowing diagram.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-21\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-1\nStarting\nthe\nNetwork\nConfigurator\n6 Tag Data Link Functions\nTo manage two or more networks, you can select Network – Add. You can add a new Network Con-\nfiguration Pane.\nTo change the network name displayed in the Network Tab Page, select Network – Property. You can\nchange the network name as set in the Comment Field of the Network Property Dialog Box.\n6-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-2-2 Tag Data Link Setting Procedure\nThis section describes the procedure to set tag data links (i.e., connection information).\nFor data links between Controllers, the connection information is set only in the originator, i.e., the\nnode that receives data.\n1 Create the network configuration."}
+{"question": "Register all the built-in EtherNet/IP ports for which to create connections, in the EtherNet/IP Net-", "answer": "work Configuration Pane. (Refer to 6-2-3 Registering Devices on page 6-23)\nNoteIf a system has already been installed, connect online to the EtherNet/IP network and up-\nload the network configuration. (Refer to 6-2-10 Uploading Tag Data Link Parameters on\npage 6-65)\n↓\n2 Create the tag and tag set connections."}
+{"question": "Create tags and tag sets for all the registered devices (built-in EtherNet/IP ports). (Refer to", "answer": "6-2-4 Creating Tags and Tag Sets on page 6-25)"}
+{"question": "Create a connection for the originator device (i.e., the registered device that receives data as in-", "answer": "put data). (Refer to 6-2-5 Connection Settings on page 6-38)\n↓\n3 Download the tag data link parameters. (Refer to 6-2-9 Downloading Tag Data Link Parameters\non page 6-62)\n↓\n4 Make sure that the tag data links are operating normally, by using the indicators for the built-\nin EtherNet/IP port (refer to the NJ/NX-series Troubleshooting Manual (Cat. No. W503)) and the\ndevice monitor function of the Network Configurator (refer to 15-2 Checking Status with the\nNetwork Configurator on page 15-3).\n↓\n5 Make sure that the output tag data is reflected in the input tags by checking the Watch Tab\nPage on the Sysmac Studio.\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for the procedure.\nAdditional Information\nIf the tag data links are performed with a device that do not have EDS files, use the Generic\nDevice to make the settings.\nRefer to A-9 Tag Data Link Settings with Generic Devices on page A-67 for information on how\nto make the settings with the Generic Device.\n6-2-3 Registering Devices\nRegister all of the devices required in the equipment (such as EtherNet/IP Units performing tag data\nlinks) in the network configuration.\n1\nRegister the devices that will participate in the tag data links by dragging the devices from the\nHardware List and dropping them in the Network Configuration Pane on the right. (To drag and\ndrop an icon, click and hold the left mouse button over the icon, move the icon to the destina-\ntion, and release the mouse button.)\nYou can also select a device in the Hardware List and press the Enter Key to register it. The\nicon of the device is displayed in the Network Configuration Pane, as shown in the following\npicture.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-23\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-2\nTag\nData\nLink\nSetting\nProcedure\n6 Tag Data Link Functions\nDrag icons from the\nhardware list. Select\ndevice icons with the\nsame major CIP\nrevision (Rev £).\nThe device names and major CIP revisions (Rev £) are displayed in the hardware list.\nFor the NJ/NX-series Controllers, device names of Units and major CIP revisions are as shown\nin the following table.\nCIP revisions\nDevice name in\nUnit version Revision name in\nHardware List Major revision\nHardware List\nNX701 Unit version 1.10 or later 2 None\nNX502-££££ Unit version 1.60 or later 2 None\nNX102-££££ Unit version 1.30 or later 2 None\nNX1P2 Unit version 1.13 or later 2 None\nNJ501-££££ Unit version 1.00 to 1.02 1 Rev1\nUnit version 1.03 or later 2 Rev2\nNJ301-££££ Unit version 1.01 or 1.02 1 Rev1\nUnit version 1.03 or later 2 Rev2\nNJ101 Unit version 1.10 or later 2 None\n6-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nPrecautions for Correct Use\nMake sure that you select the devices with the same device names and the same major CIP\nrevisions as the devices you use in the actual operation. The following will occur if any device\nname or CIP revision is incorrect when you attempt to download tag data link parameters on the\nNetwork Configurator.\n• If a device name is incorrect, an error message will be displayed saying “Specified device\ncan not be accessed, or wrong device type”, and the download will fail.\n• If a revision is incorrect, a message will be displayed saying “Wrong unit revision”, and the\ndownload will fail.\nSimilarly, the above will occur when performing upload or comparison of the tag data link pa-\nrameters.\nIn any of the above cases, refer to 6-2-17 Changing Devices on page 6-81 and change the\ndevice.\n2\nRight-click the registered device’s icon to display the pop-up menu, and select Change Node\nAddress.\n3\nSet the IP address to match the node address (IP address) actually used in the device, and\nclick the OK Button.\n4\nRepeat steps 1 to 3, and register all devices to which tag data links are made.\n6-2-4 Creating Tags and Tag Sets\nYou must create tag sets and member tags that are required to create connections for a registered\nbuilt-in EtherNet/IP port and EtherNet/IP Unit. You can set the network variables used in control pro-\ngrams for tags.\nThis section first describes the basic procedure to create tags and tag sets, as described in (1) below.\nThen it explains how to import variables with a Network Publish attribute from the Sysmac Studio to\nthe Network Configurator, as described in (2) below."}
+{"question": "Creating Tags and Tag Sets with the Network Configurator’s Device Parameter Editing Function", "answer": "NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-25\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions"}
+{"question": "Importing Variables with a Network Publish Attribute Created in the Sysmac Studio to the Network", "answer": "Configurator\n(1) Creating Tags and Tag Sets with the Network Configurator's De-\nvice Parameter Editing Function\n Creating a Tag Set\n1\nDouble-click the icon of the device for which to create a tag set to display the Edit Device\nParameters Dialog Box. Or, right-click the icon to display the pop-up menu, and select\nParameter – Edit.\n2\nClick the Tag Sets Tab at the top of the Edit Device Parameters Dialog Box.\nThere are two kinds of tag sets: input (consume) and output (produce).\n6-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n Creating and Adding Tags\n1\nClick the Edit Tags Button.\nThe Edit Tags Dialog Box is displayed. Register input (consume) tags and output (produce)\ntags separately.\n2\nClick the In - Consume Tab, and then click the New Button.\nThe Edit Tag Dialog Box is displayed.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-27\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\n3\nEnter the variable name directly into the Name Box. (Example: Var_In_a)\nAdditional Information\n• You can use the following characters in tag names.\n0 to 9, A to Z, a to z, single-byte kana, _ (underbar), and multi-byte characters (e.g., Japa-\nnese)\n• You cannot use the following characters in tag names.\n! “ # $ & ‘ ( ) * + ‚ - . / : ; < = > ? @ [ ] ^ ‘ % spaces or text strings that start with numerals (0 to\n9)\n• The maximum length of a tag name is 255 bytes.\n• Specify array variables, structure variables, and union variables, if any, as shown below.\n• Specifying array elements\nExample: array [2][3] (or array [2,3]) and array [2][3][4] (or array [2,3,4])\n• Specifying structure members\nExample: Struct.member (Separate the member name with a period.)\n• Specifying union members\nExample: Union.member (Separate the member name with a period.)\n6-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nPrecautions for Correct Use\nNX502 CPU Unit, NX102 CPU Unit, NX1P2 CPU Unit, and NJ-series CPU Unit\n• To specify an I/O memory address for a tag, create a variable with an AT specification of the\nI/O memory address on the Sysmac Studio, and then specify the variable with the AT specifi-\ncation for the tag.\nFor NX102 and NX1P2 CPU Units, you need to set memory used for CJ-series Unit to use\nthe I/O memory address. For details on memory settings used for CJ-series Unit, refer to the\nNJ/NX-series CPU Unit Software User's Manual (Cat. No. W501).\n• If you enter the following I/O memory addresses for tag names on the Network Configurator,\nthe tags are directly assigned to the I/O memory addresses in the CPU Unit, and not to the\nvariables. Always specify variable names for tags.\na) Variable names that contain only single-byte numerals from 0000 to 6143\nb) Variable names with the following single-byte letters (uppercase or lowercase) followed\nby single-byte numerals\n• H (H000 to H511)\n• W (W000 to W511)\n• D (D00000 to D32767)\n• E0_ to E18_ (E0_00000 to E0_32767, to E18_00000 to E18_32767)\nYou can check the memory address or variable to which a tag is assigned, with icons in the\nEdit Tags Dialog Box.\nTag that is directly assigned to an I/O memory address\nTag that is assigned to a variable with a Network Publish attribute\nNX701 CPU Unit\n• If you apply the notation that specifies the above I/O memory address for a tag name, a Tag\nName Resolution Error occurs. A tag data link will not be started.\n4\nInput the size of the tag in bytes in the Size Field.\nSpecify the tag size to be the same as the data type size of the variable.\nTo use a BOOL variable, select the Use Bit Data Check Box, and enter 1 in the Size Field.\n5\nClick the Regist Button to register the tag.\nIf an I/O memory address is specified as the tag name, another Edit Tag Dialog Box will be\ndisplayed with the next address as the tag name so that you can register the next tag consecu-\ntively.\nAfter you register the tags, click the Close Button.\n6\nClick the Out - Produce Tab, and then click the New Button.\nThe Edit Tag Dialog Box is displayed. Input output tags in the same way.\nIn case a major fault occurs in the CPU Unit, use the Fault Action setting of the output (pro-\nduce) tag to select whether to clear output data or continue to send data.\nThe Fault Action setting is not required for input (consume) tag sets.\n• Retain output after major fault: Hold (default)\nOutput data maintains its previous status even after a major fault occurs.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-29\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\n• Clear output at major fault: Clear\nOutput data is cleared to 0 when a major fault occurs.\nSelect the Hold or Clear Option.\nPrecautions for Correct Use\nConnections are cut off if any of the following errors occurs in the CPU Unit that is the originator\nwhile tag data links are active.\n• Major fault level Controller error\n• Partial fault level Controller error\n7\nAfter you register all of the required tags, click the OK Button in the Edit Tags Dialog Box.\nPrecautions for Correct Use\nMake the following settings to refresh all of the tag data in one tag set at the same time.\n• Use the Sysmac Studio, in advance, to specify the same refreshing task for all of the varia-\nbles that are assigned to tags in the tag set.\n• Do not place tag variables that have AT specifications in I/O memory and tag variables that\ndo not have AT specifications in the same tag set.\n6-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n8\nAt this point, a confirmation dialog box is displayed to check whether the registered tag names\nare used as the tag set names. A tag set can contain up to eight tags, but tag sets are regis-\ntered with one tag per tag set if the tag names are registered as tag set names. In this case,\nclick the Yes Button.\nIf the No Button is clicked, you can add more tags to the tag set. Refer to step 8 in Changing\nand Registering Tag Sets for details on how to register new tags first and add more tags to the\ntag set later.\n Changing and Registering Tag Sets\n1\nThe following dialog box is displayed when the tags in the Edit Tags are registered directly as\ntag sets.\n2\nIf an input tag is already registered in an input tag set, and you want to change its registration\nto a different input tag set, it is necessary to delete the tag from the tag set in which it was origi-\nnally registered.\nOpen the Edit Device Parameters Dialog Box, select the tag set containing the tag that you\nwant to delete on the Tag Sets Tab Page, and click the Delete Button. (If there are other tags\nregistered in the tag set, it is possible to delete just one tag by selecting the tag that you want\nto delete in the Edit Tag Set Dialog Box and clicking the Button.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-31\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\nA confirmation message is displayed.\nIf the No Button is clicked, only the selected tag set is deleted. Click the No Button.\n3\nTo edit a registered tag set and add tags, either double-click the tag set, or select the tag set\nand click the Edit Button.\nThe Edit Tag Set Dialog Box is displayed.\nThe Tag List on the left side of the dialog box shows tags that are already registered, and the\nCandidate Tag List on the right side of the dialog box shows the other tags that are not regis-\ntered yet.\n6-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nTo add a tag, select it in the Candidate Tag List and click the Button.\n4\nTo include the Controller status in the tag set, select the Include Option for the Controller\nStatus at the upper-right corner of the Edit Tag Set Dialog Box.\n5\nTo confirm the change, click the OK Button in the Edit Tag Set Dialog Box.\n6\nClick the OK Button in the Edit Device Parameters Dialog Box.\n7\nIf you want to just add a new tag and register it in an existing tag set, first register the new tag\nby following steps 1 in Creating a Tag Set to 7 in Creating and Adding Tags. In this example,\ninput tags, Var_In_e and Var_In_f, are newly added.\n8\nAfter you register the tags, click the OK Button in the Edit Tags Dialog Box.\n9\nAt this point, a confirmation dialog box is displayed to check whether you want to use the regis-\ntered tag names as tag set names. They are supposed to be added as tags in this case, so\nclick the No Button. Then, the tags are registered just as tags but not as tag sets.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-33\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\n10\nTo register the newly added tags in an existing tag set, either double-click the desired tag set,\nor select the tag set and click the Edit Button.\nThe Tag List on the left side of the dialog box shows tags that are already registered in the tag\nset, and the Candidate Tag List on the right side of the dialog box shows the other tags that are\nnot registered yet.\n11\nSelect the tags that you want to add from the Candidate Tag List and click the Button.\nYou can register up to eight tags in a tag set. (If you include the Controller status in the tag set,\nyou can register up to only seven tags, and two bytes are added to the size.)\nTag data is sent and received in the order of tags displayed in the tag list. To change the order\nof tag data, select a tag and click the or Button.\n6-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n12\nTo confirm the change, click the OK Button in the Edit Tag Set Dialog Box.\n13\nClick the OK Button in the Edit Device Parameters Dialog Box.\n(2) Importing Variables with a Network Publish Attribute Created in\nthe Sysmac Studio to the Network Configurator\nYou can create network variables in the Sysmac Studio and import these variables to the Network\nConfigurator to assign them to tags and tag sets. Use the following procedure.\n Exporting Global Variables on the Sysmac Studio\n1\nCreate a global variable on the global variable table of the Sysmac Studio and select Input or\nOutput for the Network Publish attribute of the variable.\n2\nSelect Export Global Variables - Network Configurator... from the Tools Menu.\nAny global variables with Input or Output set for the Network Publish attribute are imported\nfrom the csv file through the import procedure described below ( Importing to the Network Con-\nfigurator).\n Importing to the Network Configurator\nPrecautions for Correct Use\nVariables with a Network Publish attribute that have variable names that are the same as the\nI/O memory address notation, such as, \"0000\" and \"H0000\" are not exported to CSV files.\n• Variable names that contain only single-byte numerals (Example: 001)\n• Variable names with the following single-byte letters (uppercase or lowercase) followed by\nsingle-byte numerals\n• H (Example: H30)\n• W (Example: w30)\n• D (Example: D100)\n• E0_ to E18_ (Example: EA_100)\n1\nFrom the devices registered on the Network Configurator, select and double-click the icon of\nthe device for which you want to import the variable with a Network Publish attribute. Then, the\nEdit Device Parameters Dialog Box is displayed.\nOr, right-click the icon to display the pop-up menu, and select Device - Parameter - Edit.\n2\nClick the Tag Sets Tab at the top of the Edit Device Parameters Dialog Box. Select Import\nfrom File from the To/From File Button.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-35\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\nTo import all variables with a Network Publish attribute, click the Yes Button. To import only\nsome of these variables, click the No Button.\nAfter you import the variables to the tags, click the Yes Button to automatically create tag sets,\nor click the No Button to set up tag sets manually.\nIf you select the Yes Button in the previous step, the variables will be imported as shown below\non the Tag Sets Tab Page. Each variable will be imported into a separate tag set and the de-\nvice parameters will be automatically edited. (The variable name will be used for the tag set\nname.)\n6-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nTo place more than one input variable (input tag) imported from the Sysmac Studio into one tag\nset, you must delete the input tags that were registered.\nSelect the tag set containing the variables you want to put into a tag set, then click the Delete\nButton. A message box is displayed to confirm that you want to delete the selected tag set and\nthe tags contained in that tag set. You only want to delete the tag set, so click the No Button.\nClick the New Button to create a new tag set. To place more than one tag in an existing tag set,\ndouble-click the tag set, or select it and click the Edit Button.\nThe Edit Tag Set Dialog Box is displayed. Imported tags that are not registered in another tag\nset are displayed in the Candidate Tag List on the right side of the Edit Tag Set Dialog Box.\nClick the Button to add tags individually.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-37\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-4\nCreating\nTags\nand\nTag\nSets\n6 Tag Data Link Functions\n3\nYou can change tag set names in this dialog box. To confirm a change, click the Regist Button\nin the Edit Tag Set Dialog Box.\n4\nPerform steps 1 to 3 for all the devices to which tag data links are made to import variables and\nto create tag sets.\n6-2-5 Connection Settings\nAfter you create the tag sets, click the Connections Tab at the top of the Edit Device Parameters\nDialog Box, and set the following connection information.\n• The target devices and tag sets with which connections are opened\n• The connection type (multicast or unicast)\n• The length of the packet intervals (RPI)\n• Connection name (optional)\nMake the connections settings on the originator only. The connections settings are not necessary on\nthe target device.\nPrecautions for Correct Use\nMake the connections settings after you create tag sets for all of the devices involved in tag da-\nta links.\nConnection Settings (Connections Tab Page)\n Registering Devices in the Register Device List\n1\nDouble-click the icon of the device for which to make originator settings in the Network Config-\nuration Pane of the Network Configurator. The Edit Device Parameters Dialog Box is dis-\nplayed. Or, right-click the icon to display the pop-up menu, and select Parameter – Edit.\n2\nClick the Connections Tab in the Edit Device Parameters Dialog Box.\nAll of the devices registered in the network (except the local node) are displayed.\n6-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n3\nIn the Unregister Device List, click the target device that requires connection settings so its\ncolor changes to gray, and click the Button.\nThe selected target device is displayed in the Register Device List, as shown below.\n4\nTarget node IDs are assigned to the devices that are registered in the Register Device List.\nThe target node ID serves as the bit array position for the following variables in the originator\nController: Target Node Controller Mode, Target Node Controller Error Information, Target\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-39\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-5\nConnection\nSettings\n6 Tag Data Link Functions\nNode Error Information, Registered Target Node Information, and Normal Target Node Informa-\ntion. By default, the target ID is automatically set to the rightmost 8 bits of the IP address. In\nthe example above, the target device's IP address is 192.168.250.2, so the target node ID is\n#002. If a target node ID is duplicated and you want to change the target node ID, click the\nChange Target Node ID Button and change the target ID.\n Editing Settings for Individual Connections\nYou can edit each connection separately.\nRefer to Editing Settings for All Connections on page 6-42 for information on how to edit all the\nconnections in a table format.\n1\nClick the Connections Tab and then the click the New Button.\nThe following Edit Connection Dialog Box is displayed according to the type of device that is\nselected.\n• (A) Using Built-in EtherNet/IP Ports as Targets (for Input Only)\n• (B) Using Other EtherNet/IP Devices as Targets (for Settings Other Than Input Only)\n6-40 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nThe settings are as follows:\nSetting Description\nConnection I/O Type Select Input Only (Tag type) to use tag data links with a CS1W-EIP21,\nCS1W-EIP21S, CJ1W-EIP21, CJ1W-EIP21S, CJ2B-EIP21*1, CJ2M-\nEIP21*2, CJ1W-EIP21 (CJ2)*3, CJ1W-EIP21 (NJ)*4, CJ1W-EIP21S\n(CJ2)*5, CJ1W-EIP21S (NJ)*6, NX701, NX502-££££, NX102-££££,\nNX1P2, NJ501-££££, NJ301-££££, or NJ101 CPU Unit.\nWhen you create tag data links for other devices, select the connection\nI/O type specified in that device's EDS file.\nUse the Input Only (ID type) setting when another company’s node is\nthe originator and does not support connection settings with a Tag type\nsetting.\nConnection Type Select whether the data is sent in multicast or unicast (point-to-point)\nform. The default setting is multicast.\n• Multi-cast connection:\nSelect when the same data is shared by multiple nodes. This setting is\nusually used.\n• Point-to-point connection:\nSelect when the same data is not shared by multiple nodes. In a uni-\ncast transmission, other nodes are not burdened with an unnecessary\nload.\nRefer to 6-1-4 Overview of Operation on page 6-7 for details on using\nmulti-cast and unicast connections, and counting the number of connec-\ntions.\nThe Connection Structure Area and the following items are not displayed if the Hide Detail Button is\nclicked.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-41\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-5\nConnection\nSettings\n6 Tag Data Link Functions\nSetting Description\nPacket Interval (RPI) Set the data update cycle (i.e., the packet interval) of each connection\nbetween the originator and target.\nThe default setting is 50 ms (i.e., data is updated once every 50 ms).\n• NX701 CPU Unit:\nSet the RPI between 0.5 and 10,000 ms in 0.5-ms increments.\n• NX502 CPU Unit and NX102 CPU Unit:\nSet the RPI between 1 and 10,000 ms in 1-ms increments.\n• NX1P2 CPU Unit:\nSet the RPI between 2 and 10,000 ms in 0.5-ms increments.\n• NJ-series CPU Unit:\nSet the RPI between 1 and 10,000 ms in 1-ms increments.*7\nTimeout Value Set the time elapsed until a connection timeout is detected. The timeout\nvalue is set as a multiple of the packet interval (RPI) and can be set to 4,\n8, 16, 32, 64, 128, 256, or 512 times the packet interval.\nThe default setting is 4 times the packet interval (RPI).\nConnection Name Set a name for the connection. (32 single-byte characters max.)\n*1. Built-in EtherNet/IP port in CJ2H-CPU6£-EIP CPU Unit\n*2. Built-in EtherNet/IP port in CJ2M-CPU££ CPU Unit\n*3. CJ1W-EIP21 mounted to CJ2 CPU Unit\n*4. CJ1W-EIP21 mounted to NJ-series CPU Unit\n*5. CJ1W-EIP21S mounted to CJ2 CPU Unit\n*6. CJ1W-EIP21S mounted to NJ-series CPU Unit\n*7. For a CPU Unit with unit version 1.02 or earlier, you can set the RPI between 10 and 10,000 ms in\n1-ms increments.\n2\nAfter you make all of the settings, click the OK Button.\n Editing Settings for All Connections\nYou can edit the connection settings between the originator and all of the target devices selected in\nthe Register Device List together in a table.\n1\nClick the Connections Tab, and then click the Edit All Button.\nThe following Edit All Connections Dialog Box is displayed.\nThe settings are as follows:\n6-42 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nSetting Description\nTarget Device Select the target device.\nConnection Name Any name can be given to the connection. (32 single-byte characters\nmax.)\nIf this field is left blank, a default name is assigned.\nThe connection name is used as a comment.\nConnection I/O Type Select Input Only (Tag type) to use tag data links with a CS1W-EIP21,\nCS1W-EIP21S, CJ1W-EIP21, CJ1W-EIP21S, CJ2B-EIP21*1, CJ2M-\nEIP21*2, CJ1W-EIP21 (CJ2)*3, CJ1W-EIP21 (NJ)*4, CJ1W-EIP21S\n(CJ2)*5, CJ1W-EIP21S (NJ)*6, NX701, NX502-££££, NX102-££££,\nNX1P2, NJ501-££££, NJ301-££££, or NJ101 CPU Unit.\nWhen you create tag data links for other devices, select the connection\nI/O type specified in that device's EDS file.\nUse the Input Only (ID type) setting when another company’s node is the\noriginator and does not support connection settings with a Tag type set-\nting.\nIn/Out The connection's I/O is automatically displayed based on the selected\nconnection.\nInput Only: Just In is displayed.\nTarget Variable Select the target node's tag set to assign.\n• In: Select the target's output (produce) tag set.\n• Out: Select the target's input (consume) tag set.\nOriginator Variable Select the originator node's tag set to assign.\n• In: Select the originator's input (consume) tag set.\n• Out: Select the originator's output (produce) tag set.\nConnection Type Select whether the data is sent in multi-cast or unicast (point-to-point)\nform. The default setting is multi-cast.\n• Multi-cast connection:\nSelect when the same data is shared by multiple nodes. This setting is\nusually used.\n• Point-to-point connection:\nSelect when the same data is not shared by multiple nodes. In a unicast\ntransmission, other nodes are not burdened with an unnecessary load.\nRefer to 6-1-4 Overview of Operation on page 6-7 for details on using mul-\nti-cast and unicast connections, and counting the number of connections.\nRPI Set the data update cycle (i.e., the packet interval) of each connection be-\ntween the originator and target.\nThe default setting is 50 ms (i.e., data is updated once every 50 ms).\n• NX701 CPU Unit:\nSet the RPI between 0.5 and 10,000 ms in 0.5-ms increments.\n• NX502 CPU Unit and NX102 CPU Unit:\nSet the RPI between 1 and 10,000 ms in 1-ms increments.\n• NX1P2 CPU Unit:\nSet the RPI between 2 and 10,000 ms in 0.5-ms increments.\n• NJ-series CPU Unit:\nSet the RPI between 1 and 10,000 ms in 1-ms increments.*7\nTimeout Value Set the time elapsed until a connection timeout is detected. The timeout\nvalue is set as a multiple of the packet interval (RPI) and can be set to 4,\n8, 16, 32, 64, 128, 256, or 512 times the packet interval.\nThe default setting is 4 times the packet interval (RPI).\n*1. Built-in EtherNet/IP port in CJ2H-CPU6£-EIP CPU Unit\n*2. Built-in EtherNet/IP port in CJ2M-CPU££ CPU Unit\n*3. CJ1W-EIP21 mounted to CJ2 CPU Unit\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-43\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-5\nConnection\nSettings\n6 Tag Data Link Functions\n*4. CJ1W-EIP21 mounted to NJ-series CPU Unit\n*5. CJ1W-EIP21S mounted to CJ2 CPU Unit\n*6. CJ1W-EIP21S mounted to NJ-series CPU Unit\n*7. For a CPU Unit with unit version 1.02 or earlier, you can set the RPI between 10 and 10,000 ms in\n1-ms increments.\n2\nAfter you make all of the settings, Click the OK Button.\n Confirming the Connection Settings\n1\nAn overview of the connections that were set in the Register Device List is displayed in the\nConnections Tab Page.\n2\nClick the OK Button. The following figure is displayed.\nIndicates the IP address of the\noriginator where the connection\nwas set.\n3\nRepeat the connections setting procedure until all of the connections are set.\n6-44 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nPrecautions for Correct Use\nAfter you have made all of the settings, always click the OK Button before you close the Edit\nDevice Parameters Dialog Box. If the Cancel Button is clicked and the dialog box is closed, all\nthe settings you made here are discarded.\n4\nIf you change the size of a tag set for the originator or a target node after the connection set-\ntings, a parameter data mismatch will occur due to the size difference between them.\nif you change the connection settings, be sure to check the connections. (Refer to\n6-2-16 Checking Connections on page 6-80 for details.)\nAutomatically Setting Connections (Network - Auto Connection)\nYou can use automatic detection of the tag set names that are set for devices to automatically set con-\nnections between input and output tag sets with the same name (or the same names excluding speci-\nfied ellipses).\nConnections are automatically set under the following conditions.\nOutput tag set names for connec- Except for specified ellipses, the output tag set name must be the same as\ntion setting the input tag set name.\nEllipses can be set for the beginning or end of tag set names.\nInput tag set names for connection Except for specified ellipses, the input tag set name must be the same as\nsettings the output tag set name.\nEllipses can be set for the beginning or end of tag set names.\nConnection type The connection I/O type must be Input Only.\nMulticast or unicast connections can be specified for a connection.\nRPI The default setting is used.\nTimeout The default setting is used.\nExample 1: Automatic Connections with the Same Tag Set Names\nThe following connections are automatically set with the same tag set name (A_Signal) if there is an\noutput (produce) tag set named A_Signal at node A, and input (consume) tag sets named A_Signal at\nnodes B and C.\nNode A Excluded characters: None Node B Node C\nOutput tag set: A_Signal Connection Input tag set: A_Signal Input tag set: A_Signal\nConnection\nEtherNet/IP\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-45\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-5\nConnection\nSettings\n6 Tag Data Link Functions\nExample 2: Automatic Connections with the Ellipses\nThe following connections are automatically set with the same tag set name (Signal) if there is an out-\nput (produce) tag set named O_Signal at node A, and input (consume) tag sets named I_Signal at no-\ndes B and C, and O_ and I_ are set as forward ellipses.\nNode A Excluded characters: O_ and I_ Node B Node C\nOutput tag set: O_Signal Connection Input tag set: I_Signal Input tag set: I_Signal\nConnection\nEtherNet/IP\n1\nSet the same tag set names for the output and input tag sets for the connection. The tag set\nnames can also include forward and backward ellipses.\n2\nSelect Auto Connection Configuration from the Network Menu.\nA dialog box will appear to set forward and backward ellipses for both output and input tag sets\nas soon as automatic connection setting processing starts.\nInput the ellipses and click the OK Button. Processing for automatic setting is started.\n3\nIf there are tag sets that meet the conditions for automatic connection setting, they are dis-\nplayed.\n6-46 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nClick the OK Button. Processing for automatic setting is started.\n4\nA device connection structure tree is displayed when processing is completed.\n5\nUse the device connection structure tree to change the RPI and timeout settings if necessary.\nDevice Connection Structure Tree\nConnection settings can be displayed on the network configuration.\nSelect View Device’s Connection Structure Tree from the Network Menu.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-47\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-5\nConnection\nSettings\n6 Tag Data Link Functions\n• You can check the Display the detail of Connection Check Box to switch between device-level\nand connection-level views of tag data link communications.\n• An asterisk is displayed after the device name of the originator set for the connection.\n• The Edit Device Parameters Dialog Box is displayed if you select a connection and click the Edit\nButton. You can edit the connections in this dialog box.\n6-2-6 Creating Connections Using the Wizard\nYou can use the Network Configurator's Wizard to easily create connections between OMRON PLCs\nfollowing the instructions provided by the Wizard.\n6-48 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nAdditional Information\nThe Wizard can be used only with the following OMRON EtherNet/IP devices.\nDevice name Remarks\nCJ1W-EIP21 (NJ) CJ1W-EIP21 mounted to NJ-series CPU Unit*1\nCJ1W-EIP21 CJ1W-EIP21 mounted to CJ1 CPU Unit\nCJ1W-EIP21 (CJ2) CJ1W-EIP21 mounted to CJ2 CPU Unit\nCJ1W-EIP21S (NJ) CJ1W-EIP21S mounted to NJ-series CPU Unit*2\nCJ1W-EIP21S CJ1W-EIP21S mounted to CJ1-series CPU Unit\nCJ1W-EIP21S (CJ2) CJ1W-EIP21S mounted to CJ2-series CPU Unit\nCJ2B-EIP21 Built-in EtherNet/IP port in CJ2H-CPU6£-EIP CPU Unit\nCJ2M-EIP21 Built-in EtherNet/IP port in CJ2M-CPU££ CPU Unit\nCS1W-EIP21 CS1W-EIP21 mounted to CS1 CPU Unit\nCS1W-EIP21S CS1W-EIP21S mounted to CS1-series CPU Unit\nNX701 Built-in EtherNet/IP port on NX-series CPU Unit\nNX502-££££\nNX102-££££\nNX1P2\nNJ501-££££ Built-in EtherNet/IP port on NJ-series CPU Unit\nNJ301-££££\nNJ101\n*1. The CJ1W-EIP21 can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21: Unit version 2.1 or later\n• NJ-series CPU Unit: Unit version. 1.01 or later\n• Sysmac Studio: Version 1.02 or higher\n*2. The CJ1W-EIP21S can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21S: Lot. number: 241001£ or later\n• NJ-series CPU Unit: Unit version 1.67 or later\n• Sysmac Studio: Version 1.60 or higher\nUse the following procedure to create connections (i.e., tag data links) with the Wizard.\n1\nSet tags and tag sets for all the devices before starting the Wizard. Refer to 6-2-4 Creating\nTags and Tag Sets on page 6-25 for the setting procedure.\n2\nFor tag data links between OMRON PLCs, a connection is created in the PLC (i.e., the origina-\ntor device) that receives data as input data. First, select the registered device for which you\nwant to create a connection in the Network Configuration Window of the Network Configurator,\nand then select Device - Parameters - Wizard from the menu.\nThe following message box will be displayed before the Wizard starts.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-49\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-6\nCreating\nConnections\nUsing\nthe\nWizard\n6 Tag Data Link Functions\nClick the Yes Button to delete the connections that are set with OMRON PLCs before starting\nthe Wizard.\n3\nCreate the connection following the instructions that are given by the Wizard after the Wizard\nstarts. (See the following figure.)\n4\nA list of tag sets is displayed on the right side of the Wizard with target devices that support\nreceiving input data.\nSelect the tag sets that you want to receive at the originator device.\nThe following table describes the meanings of the icons and check marks displayed in the tag\nset list.\nDisplay posi-\nIcon Status\ntion\nAll All output tag sets for all devices are selected.\nDevice All output tag sets for the applicable device are selected.\nTag set The applicable output tag sets are selected. These are the tag\nsets that will be set in the connection.\nAll All or some output tag sets for some devices are selected.\nDevice Some output tag sets for applicable devices are selected.\nAll All output tag sets for all devices are not selected.\nDevice All output tag sets for applicable devices are not selected.\nTag set The applicable output tag sets are not selected. The connections\nfor this tag set will be deleted.\nDevice No applicable tag sets.\nNoteTag sets used in connections that are already set are not displayed.\nThe following display will appear when you click the Show Detail Button.\n6-50 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nThe preset values for detailed parameters will be displayed. Change the values as required.\nThe connection name cannot be set. They are automatically created using the following\nrule.\ndefault_N (where N is a 3-digit number (001, 002, etc.) starting from 1)\n5\nClick the Next Button to switch to the table in the following Wizard Dialog Box. Follow the in-\nstructions to select the input tag set of the originator device that receives the output tag set of\nthe target device from the list box.\n• The blank area in the Input Tag Set Column is for the connection that you are creating.\n• For the connections that are already set, values are already given in the Input Tag Set Col-\numn.\n• To prevent duplicate settings, input tag sets that are used are not displayed in the list box for\ninput tag sets.\n• If there is no applicable input tag set, you can edit a tag set or create a new one by using the\nEdit Tag Sets Button and the Edit Tag Button.\n6\nOnce the input tag set settings are completed, click the Finish Button. You can check the set\nconnection by selecting Network - View Devices Connection Structure Tree from the menu.\n• The Wizard can be ended even if the input tag set includes a blank row. In that case, a con-\nnection is not created for the blank row.\n• You can delete a connection by deleting the input tag sets that were previously set.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-51\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-6\nCreating\nConnections\nUsing\nthe\nWizard\n6 Tag Data Link Functions\n6-2-7 Creating Connections by Dragging and Dropping Devices\nYou can create a connection to the originator by dragging a target device and dropping it at the origi-\nnator device.\nExample) Drag the target device at 192.168.250.1 and drop it at the originator device at"}
+{"question": "168.250.100.", "answer": "Drag & Drop\nAdditional Information\nThe EtherNet/IP originator device (i.e., a device in which connections can be set) must be one\nof the following OMRON EtherNet/IP devices.\nDevice name Remarks\nCJ1W-EIP21 (NJ) CJ1W-EIP21 mounted to NJ-series CPU Unit*1\nCJ1W-EIP21 CJ1W-EIP21 mounted to CJ1 CPU Unit\nCJ1W-EIP21 (CJ2) CJ1W-EIP21 mounted to CJ2 CPU Unit\nCJ1W-EIP21S (NJ) CJ1W-EIP21S mounted to NJ-series CPU Unit*2\nCJ1W-EIP21S CJ1W-EIP21S mounted to CJ1-series CPU Unit\nCJ1W-EIP21S (CJ2) CJ1W-EIP21S mounted to CJ2-series CPU Unit\nCJ2B-EIP21 Built-in EtherNet/IP port in CJ2H-CPU6£-EIP CPU Unit\nCJ2M-EIP21 Built-in EtherNet/IP port in CJ2M-CPU££ CPU Unit\nCS1W-EIP21 CS1W-EIP21 mounted to CS1 CPU Unit\nCS1W-EIP21S CS1W-EIP21S mounted to CS1-series CPU Unit\nNX701 Built-in EtherNet/IP port on NX-series CPU Unit\nNX502-££££\nNX102-££££\nNX1P2\nNJ501-££££ Built-in EtherNet/IP port on NJ-series CPU Unit\nNJ301-££££\nNJ101\n*1. The CJ1W-EIP21 can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21: Unit version 2.1 or later\n• NJ-series CPU Unit: Unit version. 1.01 or later\n• Sysmac Studio: Version 1.02 or higher\n*2. The CJ1W-EIP21S can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21S: Lot. number: 241001£ or later\n• NJ-series CPU Unit: Unit version 1.67 or later\n• Sysmac Studio: Version 1.60 or higher\nUse the following procedure to create connections (i.e., tag data links) by dragging and dropping devi-\nces.\n6-52 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n1\nSet the tags and tag sets for the target device that will be dragged.\n• Refer to 6-2-4 Creating Tags and Tag Sets on page 6-25 for information on the settings if the\ntarget is one of the OMRON EtherNet/IP devices given above.\n• If the target is another EtherNet/IP device, refer to the manual of that device and perform\nsettings as required.\n2\nA dialog box as in the following figure for connection allocation will be displayed when you drag\nthe target device and drop it at the OMRON EtherNet/IP device.\n• Using One of the Above OMRON EtherNet/IP Devices As Target\nSelect an output tag set from the Target Device Area on the right side of the Edit\nConnection Dialog Box, and then select an input tag set to receive the output tag set in the\nOriginator Device Area on the left.\n• If there is no applicable input tag set at the originator, you can create a new one by using\nthe Edit Tag Sets Button and the Edit Tag Button.\n• Using Other EtherNet/IP Devices as Target\nThe Connection I/O Type list box in the upper part of the Edit Connection Dialog Box lists\nconnection I/O types. Select a connection I/O type according to your application.\n• The connection I/O types that can be selected depend on the target device.\n• Items that can be selected depend on the connection I/O type that is selected.\n• Select the output, input, or both output and input tag sets at the target and specify the cor-\nresponding input, output, or both input and output tag sets at the originator.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-53\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-7\nCreating\nConnections\nby\nDragging\nand\nDropping\nDevices\n6 Tag Data Link Functions\n• If there is no applicable tag set at the originator, you can create a new one by using the\nEdit Tag Sets Button and the Edit Tag Button.\nThe following view will appear when you click the Show Detail Button.\nThe specified values for detailed parameters will be displayed. Change the values as required.\nConnection names are automatically created using the following rule.\ndefault_N (where N is a 3-digit number (001, 002, etc.) starting from 1)\nAdditional Information\nThe following dialog box will be displayed if a target device that does not have I/O data is drop-\nped.\nBefore dropping again, refer to the manual of the applicable device and create the I/O data (i.e.,\noutput tag sets) required to create a connection.\n3\nAfter you complete the settings, click the Regist Button to create the connection. When the\nconnection is completed, the input tag set box and the output tag set box will be blank. You can\ncontinue to create another connection by selecting a next connection I/O type and setting a tag\nset.\n6-2-8 Connecting the Network Configurator to the Network\nThis section describes how to connect the Network Configurator to the network.\nPrecautions for Correct Use\nConnection may not be possible if the following settings are made on an NJ/NX-series Control-\nler on the connection path or on a connection destination NJ/NX-series Controller. If connection\nfails, check the following settings. For the details on the settings, refer to CIP Message Server\non page 4-21 and Packet Filter on page 4-8.\n• The Do not use Option is selected for the CIP message server.\n• The Use Option is selected for Packet Filter.\n6-54 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nAdditional Information\nAlthough NX502 CPU Units, NX102 CPU Units, and NX701 CPU Units provide two EtherNet/IP\nports, the Network Configurator treats these two ports as two different Units and connects them\nindividually.\nConnecting through Ethernet\nConnect to the built-in EtherNet/IP port on the CPU Unit via an Ethernet switch.\nPrecautions for Correct Use\nThe first time you connect via Ethernet with Windows XP (SP2 or higher), Windows Vista, or\nWindows 7, you must change the Windows firewall settings.\nFor the procedure, refer to A-4 Precautions for Using the Network Configurator on Windows XP,\nWindows Vista, or Windows 7 or Higher on page A-46.\n1\nSelect Option - Select Interface - Ethernet I/F.\n2\nSelect Network - Connect.\nIf there are multiple Ethernet interfaces on the computer, the Select Interface Dialog Box is\ndisplayed. Select the interface to connect, and press the OK Button.\nThe following dialog box is displayed.\n3\nClick the OK Button.\nSelect the network to connect to.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-55\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-8\nConnecting\nthe\nNetwork\nConfigurator\nto\nthe\nNetwork\n6 Tag Data Link Functions\nThe Network Configurator will connect to the EtherNet/IP network. If the Network Configurator\ngoes online normally, On-line is displayed in the status bar at the bottom of the window.\nThe network connection icon is displayed in blue on the Network Tab Page in which the Net-\nwork Configurator is connected.\nNetwork connection icon\nSelect Network - Change Connect Network to switch the connected network.\n4\nThe following dialog box is displayed.\n6-56 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n5\nClick the OK Button.\nSelect the network to connect to.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-57\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-8\nConnecting\nthe\nNetwork\nConfigurator\nto\nthe\nNetwork\n6 Tag Data Link Functions\nAdditional Information\nIf the following dialog box appears in the Network Configurator when you go online with an\nNJ/NX-series CPU Unit, refer to the following table for possible causes and corrections.\nAssumed cause Correction\nThe cable is not connected cor- Check if the cable is disconnected or loose.\nrectly.\nConnection with the Controller is If connection with the Controller is blocked due to the firewall set-\nblocked due to the firewall set- tings, disable the blocking.\ntings. For the firewall settings, refer to A-4 Precautions for Using the Net-\nwork Configurator on Windows XP, Windows Vista, or Windows 7 or\nHigher on page A-46.\nCommunications with Network Allow communications with Network Configurator.\nConfigurator are blocked due to For details on Packet Filter settings, refer to Packet Filter on page\nPacket Filter of the Controller. 4-8.\nThe server function of CIP mes- Enable the server function of CIP message communications. Refer\nsage communications is disa- to CIP Message Server on page 4-21 for details on setting CIP mes-\nbled. sage server.\nConnections through CPU Unit’s USB Port\nUse the following procedure to connect to the built-in EtherNet/IP port via the USB port on the CPU\nUnit.\nPrecautions for Correct Use\nNX701 CPU Units with hardware revision A or later and NX502, NX102, and NX1P2 CPU Units\ndo not support connections via USB port.\n1\nSelect the communications interface.\nSelect Option - Select Interface - NJ/NX Series USB Port.\n2\nSelect Network - Connect.\nThe following dialog box is displayed.\n6-58 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n3\nSelect TCP:2 and then click the OK Button.\nThe following dialog box is displayed.\n4\nSelect the network to connect and click the OK Button.\nThe Network Configurator will connect to the EtherNet/IP network. If the Network Configurator\ngoes online normally, On-line is displayed in the status bar at the bottom of the window.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-59\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-8\nConnecting\nthe\nNetwork\nConfigurator\nto\nthe\nNetwork\n6 Tag Data Link Functions\nAdditional Information\nIf the following dialog box appears in the Network Configurator when you go online with an\nNJ/NX-series CPU Unit, refer to the following table for possible causes and corrections.\nAssumed cause Correction\nThe cable is not connected cor- Check if the cable is disconnected or loose.\nrectly.\nConnection with the Controller is If connection with the Controller is blocked due to the firewall set-\nblocked due to the firewall set- tings, disable the blocking.\ntings. For the firewall settings, refer to A-4 Precautions for Using the Net-\nwork Configurator on Windows XP, Windows Vista, or Windows 7 or\nHigher on page A-46.\nThe USB driver is not installed Install the USB driver correctly.\ncorrectly. For how to install the USB driver, refer to the Sysmac Studio Version\n1 Operation Manual (Cat. No. W504).\nThe server function of CIP mes- Enable the server function of CIP message communications. Refer\nsage communications is disa- to CIP Message Server on page 4-21 for details on setting CIP mes-\nbled. sage server.\nDirect Connection via Ethernet to Built-in EtherNet/IP Port\nUse the following procedure to directly connect to a built-in EtherNet/IP port on an NJ/NX-series CPU\nUnit via Ethernet.\nYou can connect to the built-in EtherNet/IP port even if the IP address is not set on the computer.\n1\nSelect the communications interface.\nSelect Option - Select Interface - NJ/NX Series Ethernet Direct I/F.\n2\nSelect Network - Connect.\nThe Select Interface Dialog Box is displayed if there are several CPU Units that you can con-\nnect to.\n6-60 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n3\nSelect the Interface Card to connect and click the OK Button.\nWhen you select one of the options listed as CPU Unit model (IP number), the following dia-\nlog box is displayed.\n4\nSelect TCP:2 and then click the OK Button.\nThe following dialog box is displayed.\n5\nSelect the network to connect to.\nThe Network Configurator will connect to the EtherNet/IP network. If the Network Configurator\ngoes online normally, On-line is displayed in the status bar at the bottom of the window.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-61\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-8\nConnecting\nthe\nNetwork\nConfigurator\nto\nthe\nNetwork\n6 Tag Data Link Functions\nAdditional Information\nIf the following dialog box appears in the Network Configurator when you go online with an\nNJ/NX-series CPU Unit, refer to the following table for possible causes and corrections.\nAssumed cause Correction\nThe cable is not connected cor- Check if the cable is disconnected or loose.\nrectly.\nConnection with the Controller is If connection with the Controller is blocked due to the firewall set-\nblocked due to the firewall set- tings, disable the blocking.\ntings. For the firewall settings, refer to A-4 Precautions for Using the Net-\nwork Configurator on Windows XP, Windows Vista, or Windows 7 or\nHigher on page A-46.\n6-2-9 Downloading Tag Data Link Parameters\nTo make tag data links, you must download tag data link parameters, such as tag set settings and con-\nnection settings, to all devices in the EtherNet/IP network.\nWhen the download operation is executed, the tag data link parameters are transferred to the Ether-\nNet/IP devices that require the settings.\nThe following procedure shows how to download the tag data link parameters.\nFor details on how to connect to the network from the Network Configurator, refer to 6-2-8 Connecting\nthe Network Configurator to the Network on page 6-54.\n6-62 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nPrecautions for Correct Use\n• If the node addresses (IP addresses) are not set correctly, you may connect to the wrong\nController and set incorrect device parameters. Download data only after you confirm that\nyou are connected to the correct Controller.\n• If incorrect tag data link parameters are set, it may cause equipment to operate unpredictably.\nEven when the correct tag data link parameters are set, make sure that there will be no effect\non equipment before you transfer the data.\n• When network variables are used in tag settings, a connection error will result if the variables\nare not set in the CPU Unit. Before downloading the tag data link parameters, check to con-\nfirm that the network variables are set in the CPU Unit. Check whether the network variable,\ntag, and connection settings are correct on the Connection Tab Page and the Tag Status\nTab Page as described in 15-2-1 The Network Configurator's Device Monitor Function on\npage 15-3.\n• If a communications error occurs, the output status depends on the specifications of the de-\nvice being used. When a communications error occurs for a device that is used along with\noutput devices, check the operating specifications and implement safety countermeasures.\n• The built-in EtherNet/IP port is automatically restarted after the parameters are downloaded.\nThis restart is required to enable the tag set and connection information. Before you down-\nload the parameters, make sure that restarting the port will not adversely affect the controlled\nsystem.\n• Make sure that the major CIP revision of the device registered with the Network Configurator\nis the same as the major CIP revision of the CPU Unit that you use. If the major CIP revisions\nare not the same, the parameters may not be downloaded. To determine whether download-\ning is possible, refer to 6-2-3 Registering Devices on page 6-23.\n• Do not disconnect the Ethernet cable or reset or turn OFF the power to the EtherNet/IP Unit\nduring the parameter download.\n• Tag data links (data exchange) between relevant nodes are stopped during a download. Be-\nfore you download data in RUN mode, make sure that it will not adversely affect the control-\nled system.\nAlso implement interlocks on data processing in ladder programming that uses tag data links\nwhen the tag data links are stopped or a tag data link error occurs.\n• For EtherNet/IP Units with revision 1, you can download tag data link parameters only when\nthe CPU Unit is in PROGRAM mode.\n• Even for Units with revision 2 or later, all CPU Units must be in PROGRAM mode to down-\nload the parameters if any Units with revision 1 are included in the network.\n1\nConnect the Network Configurator to the network.\n2\nThere are two ways to download the parameters.\n• Downloading to All Devices in the Network\nSelect Network - Download.\nThe following dialog box is displayed.\n• Downloading Individually to Particular Devices\nSelect the icon of the EtherNet/IP Unit to which you want to download. To select multiple no-\ndes, hold down the Shift Key or the Ctrl Key while you click the icons. (In the following exam-\nple, 2 nodes are selected: 192.168.250.1 and 192.168.250.2.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-63\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-9\nDownloading\nTag\nData\nLink\nParameters\n6 Tag Data Link Functions\nRight-click the icon to display the popup menu, and select Parameter - Download.\nThe following dialog box is displayed.\n3\nClick the Yes Button to download the tag data link parameters to the EtherNet/ IP Unit.\nThe following dialog box is displayed if any of the CPU Units is not in PROGRAM mode.\nIf the Download after changed to Program mode Button is clicked, all CPU Units are\nchanged to PROGRAM mode and the parameters are downloaded. Confirm safety for all con-\ntrolled equipment before you change the CPU Units to PROGRAM mode. You can restore the\noperating modes after the parameters are downloaded.\nYou can click the Download with Current mode Button to download the parameters even\nwhen one or more CPU Units is in RUN mode.\nThe Download with Current mode Button is disabled if the EtherNet/IP Unit does not support\nthe Download with Current mode Button (e.g., revision 1 of CJ1W-EIP21 or CS1W-EIP21).\n6-64 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nDuring the download, the following progress indicator is displayed to show the progress of the\ndownload.\nIf the operating mode of one or more CPU Units was changed to download the parameters,\nyou can return the CPU Units to the previous operating modes. If the No Button is clicked, the\nCPU Units remain in PROGRAM mode.\n4\nThe following dialog box is displayed to show that the download was completed.\n6-2-10 Uploading Tag Data Link Parameters\nYou can upload tag data link parameters (such as tag set settings and connection settings) from Ether-\nNet/IP devices in the EtherNet/IP network.\nThe following procedure shows how to upload the parameters. For details on how to connect to the\nnetwork from the Network Configurator, refer to 6-2-8 Connecting the Network Configurator to the Net-\nwork on page 6-54.\nPrecautions for Correct Use\n• Make sure that the major CIP revision of the device registered with the Network Configurator\nis the same as the major CIP revision of the NJ/NX-series CPU Unit that you use. If the major\nCIP revisions are not the same, the parameters may not be uploaded. To determine whether\nuploading is possible, refer to 6-2-3 Registering Devices on page 6-23.\nThere are two ways to upload the parameters.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-65\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-10\nUploading\nTag\nData\nLink\nParameters\n6 Tag Data Link Functions\nUploading from All Devices in the Network\n1\nConnect the Network Configurator online, and then select Upload from the Network Menu.\n2\nThe following dialog box is displayed.\n• Clicking the Yes Button:\nThe tag data link parameters in the current project are uploaded.\n• Clicking the No Button:\nYou open a new project to upload the tag data link parameters. The current project is closed.\n• Clicking the Cancel Button:\nThe upload operation is canceled. The upload is not performed.\n3\nIf you click the Yes Button in step 2, the following dialog box is displayed.\n• Clicking the Yes Button:\nParameters are uploaded only from the devices registered in the Network Configuration\nPane. Parameters are not uploaded from devices that are not registered in the Network Con-\nfiguration Pane.\n• Clicking the No Button:\nPerforming a Batch Upload over the Network\nParameters are uploaded from all devices on the network.\nThe current Network Configuration Information will be lost.\nThe following dialog box will be displayed. Select the devices for which to upload parameters\nand click the OK Button.\n6-66 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n• Clicking the Cancel Button:\nThe upload operation is canceled. The upload is not performed.\n4\nIf you click the No Button in step 2, the following dialog box is displayed.\nSelect the devices for which to upload parameters and click the OK Button.\nUploading Individually from Particular Devices\n1\nConnect the Network Configurator to the network.\nSelect the icon of the EtherNet/IP Unit from which you want to upload parameters. To select\nmultiple nodes, press and hold the Shift Key or the Ctrl Key while you select additional icons.\n(In the following example, 2 nodes are selected: 192.168.250.1 and 192.168.250.2.)\nRight-click the icon to display the pop-up menu, and select Parameter - Upload.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-67\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-10\nUploading\nTag\nData\nLink\nParameters\n6 Tag Data Link Functions\n2\nThe following dialog box is displayed.\nClick the Yes Button or the No Button.\n3\nDuring the upload, the following progress indicator is displayed to show the progress of the up-\nload.\n4\nThe following dialog box is displayed to show that the upload was completed.\n6-2-11 Verifying Tag Data Link Parameters\nTag data link parameters (such as tag set settings and connection settings) can be compared with the\nparameters of the built-in EtherNet/IP ports in the EtherNet/IP network.\n6-68 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nThe following procedure shows how to compare the parameters. For details on how to connect to the\nnetwork from the Network Configurator, refer to 6-2-8 Connecting the Network Configurator to the\nNetwork on page 6-54.\nPrecautions for Correct Use\n• Make sure that the major CIP revision of the device registered with the Network Configurator\nis the same as the major CIP revision of the NJ/NX-series CPU Unit that you use. If the major\nCIP revisions are not the same, the parameters may not be compared. To determine whether\ncomparison is possible, refer to 6-2-3 Registering Devices on page 6-23.\nVerifying the Network Configuration\nYou can use the following procedure to compare the list of registered devices in the Network Configu-\nration Pane with the devices connected on the EtherNet/IP network, and check the IP addresses and\ndevice types.\nThis function does not verify device parameters.\n1\nConnect the Network Configurator to the network.\n2\nSelect Network - Verify Structure.\nThe following progress indicator is displayed to show the progress as data is read from the net-\nwork and compared.\n3\nThe result of the comparison between the network configuration file and data from the network\nis displayed as shown below.\n• Differences Not Found in the Comparison\n• Differences Found in the Comparison\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-69\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-11\nVerifying\nTag\nData\nLink\nParameters\n6 Tag Data Link Functions\n• Differences Found in the Device Type\nClick the OK Button or the Close Button.\nVerifying the Device Parameters\nUse the following procedure to compare the device parameters for the devices selected in the Network\nConfiguration Pane with those of the devices connected on the EtherNet/IP network.\nThe IP addresses, device types, and device parameters are compared.\n1\nConnect the Network Configurator to the network.\n2\nClick the icon of the built-in EtherNet/IP port to verify. To select multiple nodes, press and hold\nthe Shift Key or the Ctrl Key while you select additional icons. (In the following example, 2 no-\ndes are selected: 192.168.250.1 and 192.168.250.2.)\nRight-click the icon to display the pop-up menu and select Parameter - Verify.\n6-70 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n3\nThe following dialog box is displayed.\nClick the Yes Button or the No Button.\n4\nThe following dialog box is displayed.\n• Differences Not Found in the Comparison\n• Differences Found in the Comparison\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-71\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-11\nVerifying\nTag\nData\nLink\nParameters\n6 Tag Data Link Functions\n• Differences Found in the Device Type\nClick the OK Button or the Close Button.\n5\nIf multiple nodes have been selected and compared, the following message is displayed. Click\nthe Yes Button.\nThe comparison results are displayed in order of the selected nodes.\n6-2-12 Starting and Stopping Tag Data Links\nThis section describes the procedure for starting/stopping tag data links. For details on how to connect\nNetwork Configurator to a network, refer to 6-2-8 Connecting the Network Configurator to the Network\non page 6-54.\nAutomatically Starting Tag Data Links\nTag data links are automatically started immediately after the data link parameters are downloaded\nfrom the Network Configurator.\n6-72 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n(They are automatically started after the CPU Unit's power is turned ON or the Unit is restarted.)\nAdditional Information\nWith a CPU Unit with unit version 1.04 or later that operates as the originator device, a Tag\nData Link Connection Timeout error will occur if a connection is not established with the target\ndevice within one minute after the tag data links are started.\nEven after this error occurs, reconnection processing is continued periodically until automatic\nrecovery is performed.\nIf the application environment allows you to ignore this error, such as when a target device is\nstarted later than the originator device, you can change the event level to the observation level.\nStarting and Stopping Tag Data Links for the Entire Network\nYou can start and stop tag data links for the entire network from the user program or from the Network\nConfigurator.\nPrecautions for Correct Use\nUse the same method (i.e., either the user program or the Network Configurator) to both start\nand stop tag data links.\nFor example, if you use the _EIP_TDLinkStopCmd (Tag Data Link Communications Stop\nSwitch) system-defined variable stop tag data links, you cannot start them from the Network\nConfigurator.\n Using Commands in the User Program\nYou can start and stop tag data links on a device basis by changing the values of the following sys-\ntem-defined variables from FALSE to TRUE in the user program. (Refer to Section 3 System-de-\nfined Variables Related to the Built-in EtherNet/IP Port on page 3-1.)\n• NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit:\nYou can individually start and stop tag data links for each built-in EtherNet/IP port.\n• Tag data links start/stop operation switch for built-in EtherNet/IP port 1\n_EIP1_TDLinkStartCmd (CIP Communications1 Tag Data Link Communications Start Switch)\n_EIP1_TDLinkStopCmd (CIP Communications1 Tag Data Link Communications Stop Switch)\n• Tag data links start/stop operation switch for built-in EtherNet/IP port 2\n_EIP2_TDLinkStartCmd (CIP Communications2 Tag Data Link Communications Start Switch)\n_EIP2_TDLinkStopCmd (CIP Communications2 Tag Data Link Communications Stop Switch)\n• NX1P2 CPU Unit:\n_EIP1_TDLinkStartCmd (CIP Communications1 Tag Data Link Communications Start Switch)\n_EIP1_TDLinkStopCmd (CIP Communications1 Tag Data Link Communications Stop Switch)\n• NJ-series CPU Unit:\n_EIP_TDLinkStartCmd (Tag Data Link Communications Start Switch)\n_EIP_TDLinkStopCmd (Tag Data Link Communications Stop Switch)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-73\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-12\nStarting\nand\nStopping\nTag\nData\nLinks\n6 Tag Data Link Functions\nAdditional Information\n• Change the Tag Data Link Communications Start Switch to TRUE, while the Tag Data Link\nCommunications Stop Switch is FALSE.\nIf the Tag Data Link Communications Stop Switch is TRUE, the tag data links do not start\neven if the Tag Data Link Communications Start Switch is changed to TRUE.\nFurthermore, if the Tag Data Link Start Switch and the Tag Data Link Stop Switch are both\nTRUE, an error occurs, the Multiple Switches ON Error system-defined variable changes to\nTRUE, and the event is recorded in the event log.\n• After you start the tag data links, do not force the Tag Data Link Communications Start Switch\nto change to FALSE from the user program or from the Sysmac Studio. It will change to\nFALSE automatically.\n Using the Network Configurator\nYou can select I/O Connection - Start or Stop from the Network Menu to start and stop tag data\nlinks for individual devices.\nStarting and Stopping Tag Data Links for Individual Devices\n Using the Network Configurator\nYou can start and stop tag data links on a device basis (at the originator) by selecting Monitor from\nthe Device Menu and performing the following operation in the Connection Tab Page in the\nMonitor Device Dialog Box.\nWhen using an NX701 CPU Unit, NX502 CPU Unit, or NX102 CPU Unit, you can start and stop tag\ndata links for each of the built-in EtherNet/IP port 1 and 2 connected to the Network Configurator.\nStart Connection Button:\nStarts all connections for which the device is the originator.\nStop Connection Button:\nStops all connections for which the device is the originator.\n6-74 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-2-13 Clearing the Device Parameters\nYou can clear the tag data link settings (or return them to their factory settings) that are saved in the\nregistered EtherNet/IP device.\nThe following shows how to clear tag data link parameters. For details on how to connect to the net-\nwork from the Network Configurator, refer to 6-2-8 Connecting the Network Configurator to the Net-\nwork on page 6-54.\nPrecautions for Correct Use\nFor a CPU Unit with Unit Version 1.10 or Later\n• Use the Network Configurator version 3.58 or higher to perform the following procedure to\nclear the tag data link settings.\n• If you perform the following procedure from the Network Configurator version 3.57 or lower,\nthe tag data link settings are not cleared. Refer to Additional Information in this section for the\nprocedure to clear the tag data link settings from the Network Configurator version 3.57 or\nlower.\n1\nConnect the Network Configurator to the network.\n2\nSelect the icon of the device from which you want to clear the device parameters.\nIn the following example, two nodes are selected: 192.168.250.1 and 192.168.250.2. To select\nmultiple nodes, press and hold the Shift Key while you select additional icons.\n3\nSelect Device - Reset.\nYou can also right-click the icon and select Reset from the pop up menu.\n4\nThe following dialog box is displayed.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-75\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-13\nClearing\nthe\nDevice\nParameters\n6 Tag Data Link Functions\n• If you click the Yes Button:\nThe following dialog box is displayed.\nRestart the device.\nClear the tag data link settings and restart\nthe device.\nNOTE : The Controller will not be restarted.\nSelect the Initialize tag data link configuration, and then emulate cycling power Option,\nand then click the OK Button.\nPrecautions for Correct Use\nThe Controller is not restarted. Only the built-in EtherNet/IP port is reset.\n• If you click the No Button:\nThe tag data link settings will not be cleared and the built-in EtherNet/IP port will not be re-\nset.\nAdditional Information\nYou can also execute the Reset service of the Identity Object for the CPU Unit to clear the tag\ndata link settings. The procedure to execute the service from the Network Configurator is given\nbelow."}
+{"question": "Select Tool - Setup Parameters in the main window.", "answer": "Then the dialog box for the general parameter settings are displayed."}
+{"question": "Specify the target device and message to send.", "answer": "• Target Node Address : Enter the IP address of the target device.\n• Service : Select Reset.\n• Class : Enter 01.\n• Instance : Enter 01.\n• Attribute : Enter 00.\n• Data : Enter 02*1."}
+{"question": "Click the Send Button.", "answer": "*1. For a CPU Unit with unit version 1.09 or earlier, specify 01.\n6-76 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-2-14 Saving the Network Configuration File\nYou can save device parameters set in the Network Configurator or device parameters uploaded from\nthe network in a network configuration file.\n1\nSelect File - Save As.\nThe following dialog box is displayed.\nUntitled.nvf is displayed as the default file name.\n2\nInput the file name, and then click the Save Button.\nThis completes the network configuration file save operation.\n3\nWhen the network configuration is changed later, you can overwrite the existing network con-\nfiguration file if you select File - Save, or click the Button.\n4\nYou can select the Select target network Check Box in the Option Area to select and save\nonly the required network configuration files from the existing multiple files.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-77\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-14\nSaving\nthe\nNetwork\nConfiguration\nFile\n6 Tag Data Link Functions\nSelect the check boxes of the networks to save and click the OK Button.\n6-2-15 Reading a Network Configuration File\nYou can read out a previously saved network configuration file into the Network Configurator.\n1\nSelect File - Open, or click the Button.\nThe following dialog box is displayed.\n6-78 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nIf the network configuration file that you want to read out is not displayed, change to another\nfolder.\n2\nIf you select the network configuration file that you want to read out, that file name is displayed\nin the File name Field.\n3\nClick the Open Button to read out the network configuration file.\n4\nThe Network Configurator's Title Bar will display the name of the file that was read out.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-79\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-15\nReading\na\nNetwork\nConfiguration\nFile\n6 Tag Data Link Functions\n5\nSelect options in the Option Area as necessary.\nThe options are listed below.\nSetting Description\nSelect target network Allows you to select specific networks from the network configura-\ntion and open them.\nAdd to current document Allows you to add the networks from the network configuration file\nthat is currently open to the current configuration file.\nAdditional Information\nThe save format will depend on the version of the Network Configurator. You can import config-\nuration files (*.ncf) created with the Network Configurator for EtherNet/IP (version 2 or lower) if\nyou select External Data - Import from the File Menu.\n6-2-16 Checking Connections\nYou can check the consistency of connection parameters for network configuration files with device\nparameters that were set with the Network Configurator or device parameters uploaded from the net-\nwork.\n1\nSelect Check Connection from the Network Menu.\nThe following dialog box is displayed if parameters are normal.\nThe following dialog box is displayed if there are parameter errors. Check the displayed details\nand review the settings.\n6-80 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nIf an inconsistency is found, open the originator’s Edit Device Parameter Dialog Box and click\nthe Connection Tab. The inconsistent connection in the Register Device List is displayed\nwith a icon (instead of the normal icon).\nTo change the connection setting and select a different target variable, select the connection as\nshown below and click the Edit Button.\nicon (normally )\n6-2-17 Changing Devices\nYou can change devices that are registered in a network configuration with the Network Configurator.\nSelect Change Device from the Device Menu to display a list of the possible devices to change.\nYou can change a device only when there is complete or upward compatibility with the device.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-81\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-17\nChanging\nDevices\n6 Tag Data Link Functions\nDevice Changes\nModel after change\nNX- CS1W- CS1W CJ1W- CJ1W- CJ1W CJ1W- CJ1W CJ1W CJ2B- CJ2M\nModel be- EIP20 EIP21 - EIP21 EIP21 - EIP21 - - EIP21\nCIP\nfore 1 EIP21 (CJ2) EIP21 (NJ) EIP21 EIP21\nRev.\nchange S S S S (NJ)\n(CJ2)\nRev 2 Rev 3 Rev 4 Rev 3 Rev 3 Rev 4 Rev 3 Rev 4 Rev 4 Rev 3 Rev 2\nNX-EIP201 Rev 2 --- No No No r2/6/7 No r2/4/7 r2/6/ r2/4/ r2/6/ r2/4/7\n7 7 7\nCS1W- Rev 3 No --- Yes Yes Yes Yes r5 Yes r5 Yes r3\nEIP21\nCS1W- Rev 4 No Yes --- Yes Yes Yes r5 Yes r5 Yes r3\nEIP21S\nCJ1W- Rev 3 No Yes Yes --- Yes Yes r5 Yes r5 Yes r3\nEIP21\nCJ1W- Rev 3 r5 r1 r1 r1 --- r1 r5 Yes r5 Yes r3\nEIP21\n(CJ2)\nCJ1W- Rev 4 No Yes Yes Yes Yes --- r5 Yes r5 Yes r3\nEIP21S\nCJ1W- Rev 3 Yes r1/2 r1/2 r1/2 r2 r1/2 --- r2 Yes r2 r2/6\nEIP21 (NJ)\nCJ1W- Rev 4 r5 r1 r1 r1 Yes r1 r5 --- r5 Yes r3\nEIP21S\n(CJ2)\nCJ1W- Rev 4 Yes r1/2 r1/2 r1/2 r2 r1/2 Yes r2 --- r2 r2/6\nEIP21S\n(NJ)\nCJ2B- Rev 3 r5 r1 r1 r1 Yes r1 r5 Yes r5 --- r3\nEIP21\nCJ2M Rev 2 r5 r1 r1 r1 Yes r1 r5 Yes r5 Yes ---\nNJ501 Rev 1 No r1/2 r1/2 r1/2 r2 r1/2 Yes r2 Yes r2 r2/6\nNJ301 Rev 2 Yes r1/2 r1/2 r1/2 r2 r1/2 Yes r2 Yes r2 r2/6\nNJ101 Rev 2 Yes r1/2 r1/2 r1/2 r2 r1/2 Yes r2 Yes r2 r2/6\nNX701 Rev 2 Yes No No No r2 No Yes r2 Yes r2 r2/6\nNX502 Rev 2 Yes No No No r2/7 No r2/7 r2/7 r2/7 r2/7 r2/6/7\nNX102 Rev 2 Yes No No No r2 No Yes r2 Yes r2 r2/6\nNX1P2 Rev 2 Yes No No No r2 No Yes r2 Yes r2 r2/6\nModel after change\nNJ501 NJ101 NX701 NX502 NX102 NX1P2\nModel before\nCIP Rev NJ301\nchange\nRev 1 Rev 2 Rev 2\nRev 2 Rev 2 Rev 2 Rev 2\n*1 *2 *2\nNX-EIP201 Rev 2 No r4/7 r4/7 r6/7 r4 r4/7 r4/7\nCS1W-EIP21 Rev 3 r4/5 r4/5 r4/5 No No No No\nCS1W-EIP21S Rev 4 r4/5 r4/5 r4/5 No No No No\nCJ1W-EIP21 Rev 3 r4/5 r4/5 r4/5 No No No No\nCJ1W-EIP21 Rev 3 r4/5 r4/5 r4/5 r5 r4/5 r4/5 r4/5\n(CJ2)\nCJ1W-EIP21S Rev 4 r4/5 r4/5 r4/5 No No No No\nCJ1W-EIP21 Rev 3 r4 r4 r4 Yes r4 r4 r4\n(NJ)\n6-82 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nModel after change\nNJ501 NJ101 NX701 NX502 NX102 NX1P2\nModel before\nCIP Rev NJ301\nchange\nRev 1 Rev 2 Rev 2\nRev 2 Rev 2 Rev 2 Rev 2\n*1 *2 *2\nCJ1W-EIP21S Rev 4 r4/5 r4/5 r4/5 r5 r4/5 r4/5 r4/5\n(CJ2)\nCJ1W-EIP21S Rev 4 r4 r4 r4 Yes r4 r4 r4\n(NJ)\nCJ2B-EIP21 Rev 3 r4/5 r4/5 r4/5 r5 r4/5 r4/5 r4/5\nCJ2M Rev 2 r4/5 r4/5 r4/5 r5 r5 r4/5 r4/5\nNJ501 Rev 1 ---- Yes r4 No No No No\nNJ301 Rev 2 Yes --- r4 Yes Yes Yes r4\nNJ101 Rev 2 Yes Yes --- Yes Yes Yes r4\nNX701 Rev 2 No r4 r4 --- r4 r4 r4\nNX502 Rev 2 No r4/7 r4/7 r7 --- r4/7 r4/7\nNX102 Rev 2 No Yes Yes Yes Yes ---- r4\nNX1P2 Rev 2 No Yes Yes Yes Yes Yes ----\n*1. CPU Unit with a unit version 1.00 to 1.02\n*2. CPU Unit with a unit version 1.03 or later\nYes Can be changed.\nNo: Cannot be changed.\nr0 Cannot be changed if a Japanese variable is specified in the tag.\nr1 Cannot be changed if a network variable is specified as a tag.\nr2 Cannot be changed if the maximum size of a tag name or tag set name (size after conversion into\nUTF-8) exceeds 48 bytes.\nr3 Cannot be changed if the following items exceed the permissible settings of the device after the\nchange:\n• Number of I/O connections, number of tags, number of tag sets, and size of one tag set.\nr4 Cannot be changed in any of the following cases:\n• The number of I/O connections, number of tags, number of tag sets, or size of one tag set ex-\nceeds the permissible settings for the device after the change.\n• RPI exceeds the permissible settings or is set in 0.5-ms increments (such as 10.5ms)\nr5 Cannot be changed if a tag set size is an odd number of bytes.\nr6 Cannot be changed if tags, tag sets, or refreshing sizes exceed the permissible settings.\nr7 Cannot be changed if the maximum number of tags per tag set exceeds the permissible setting.\n6-2-18 Displaying Device Status\nDevice status is displayed using the following icons in Maintenance Mode.\nTo enter Maintenance Mode, select Large Icons - Maintenance Mode from the View Menu.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-83\n6-2\nSetting\nTag\nData\nLinks\n6\n6-2-18\nDisplaying\nDevice\nStatus\n6 Tag Data Link Functions\nIcon Status\nOffline\n(white)\nDefault (including no Controller Configurations and Setup)\n(gray)\nIdle (including when the Controller is in PROGRAM mode)\n(green)\nNormal communications state (including when the Controller is in RUN mode)\n(blue)\nWarning status (including when there is a partial fault or non-fatal error in the Con-\ntroller)\n(yellow)\nAlarm status (including when there is a major fault or fatal error in the Controller)\n(red)\n6-84 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-3 Ladder Programming for Tag Data\nLinks\n6-3-1 Ladder Programming for Tag Data Links\nThe following conditions 1 to 3 should be fulfilled if you use tag data link data for a ladder program.\nThe additional conditions 4 and 5 should be also fulfilled if you input the Controller information of the\ntarget node.\n Conditions for enabling tag data links for the built-in EtherNet/IP port on a\nNJ/NX-series CPU Unit\nThe following conditions 1 and 2 should be both fulfilled.\nNo. Condition\n1 The following error status bits in the _EIP_ErrSta (EtherNet/IP Error) variable are\nFALSE.\n• Major fault: Bit 7\n• Partial fault: Bit 6\n• Minor fault: Bit 5\n2 The _EIP_EtnOnlineSta (Online) variable*1 is TRUE.\n Condition for Tag Data Links with Connection Established to the Target\nDevice\nThe following condition 3 should be fulfilled.\nNo. Condition\n3 In the _EIP_EstbTargetSta (Normal Target Node Information) variable*2, the bit corre-\nsponding to the target node address is TRUE.\n Condition of the Controller Operating Mode (Operating or Stopped) (Only\nfor OMRON Controllers)\nThe following condition 4 should be fulfilled.\nNo. Condition\n4 In the _EIP_TargetPLCModeSta (Target PLC Operating Mode) variable*3, the bit cor-\nresponding to the target node address is TRUE.\n Condition of the Controller Error Status (Fatal or Non-fatal Error) of the\nTarget Node (Only for OMRON Controllers)\nThe following condition 5 should be fulfilled.\nNo. Condition\n5 In the _EIP_TargetPLCErr (Target PLC Error Information) variable*4, the bit corre-\nsponding to the target node address is FALSE.\nWhen you want to use the Target Node Controller Error Flag, the Controller status\nmust be included in the tag sets for both the originator and target. Include the Control-\nler status by using the Network Configurator to select the Include Option in the Edit\nTag Set Dialog Box.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-85\n6-3\nLadder\nProgramming\nfor\nTag\nData\nLinks\n6\n6-3-1\nLadder\nProgramming\nfor\nTag\nData\nLinks\n6 Tag Data Link Functions\n*1. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\nBuilt-in EtherNet/IP port 2: _EIP2_EtnOnlineSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\n*2. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\nBuilt-in EtherNet/IP port 2: _EIP2_EstbTargetSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\n*3. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\nBuilt-in EtherNet/IP port 2: _EIP2_TargetPLCModeSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\n*4. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCErr\nBuilt-in EtherNet/IP port 2: _EIP2_TargetPLCErr\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCErr\n Programming Example for Normal Operation Detection\nThe following program can be used to confirm that normal communications are being performed for\neach target node. If the Controller status is included in the tag data, the status of the Controller can\nalso be detected.\n• Normal Operation Detection Programming Example 1\nNormal Target Node Target PLC Operating Target PLC Error\nOnline Information (#1) Mode (#1) Information (#1)\n(_EIP_EtnOnlineSta)*1 _EIP_EstbTargetSta[1]*2 _EIP_TargetPLCModeSta[1]*3 _EIP_TargetPLCErr[1]*4\nNode 01 data\nlink operation\nnormal\nNormal Target Node\nInformation Target PLC Operating Target PLC Error\n(#2) Mode (#2) Information (#2)\n_EIP_EstbTargetSta[2]*2 _EIP_TargetPLCModeSta[2]*3 _EIP_TargetPLCErr[2]*4\nNode 02 data\nlink operation\nnormal\n• Normal Operation Detection Programming Example 2\n6-86 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nAll Tag Data Link\nOnline Communications Status\n(_EIP_EtnOnlineSta)*1 _EIP_TDLinkAllRunSta*5\nData link\noperation\nnormal\nTarget PLC Target PLC\nOperating Mode (#1) Error Information (#1)\n_EIP_TargetPLCModeSta[1]*2 _EIP_TargetPLCErr[1]*4\nNode 01 data\nlink operation\nnormal\nTarget PLC Target PLC\nOperating Mode (#2) Error Information (#2)\n_EIP_TargetPLCModeSta[2]*2 _EIP_TargetPLCErr[2]*4\nNode 02 data\nlink operation\nnormal\n*1. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\nBuilt-in EtherNet/IP port 2: _EIP2_EtnOnlineSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\n*2. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\nBuilt-in EtherNet/IP port 2: _EIP2_EstbTargetSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\n*3. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\nBuilt-in EtherNet/IP port 2: _EIP2_TargetPLCModeSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\n*4. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCErr\nBuilt-in EtherNet/IP port 2: _EIP2_TargetPLCErr\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCErr\n*5. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TDLinkAllRunSta\nBuilt-in EtherNet/IP port 2: _EIP2_TDLinkAllRunSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TDLinkAllRunSta\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-87\n6-3\nLadder\nProgramming\nfor\nTag\nData\nLinks\n6\n6-3-1\nLadder\nProgramming\nfor\nTag\nData\nLinks\n6 Tag Data Link Functions\n Programming Example for Error Detection\nThe following program can be used to check for tag data link errors for each target node. This pro-\ngramming is used to detect errors which may occur after the data links for all the nodes are started\nnormally.\nNormal Target\nOnline Node Information (#1)\n(_EIP_EtnOnlineSta)*1 _EIP_EstbTargetSta[1]*2\nNode 01 error output\nNormal Target\nNode Information (#1) Node 01\n_EIP_EstbTargetSta[1]*2 error output\nNormal Target\nNode Information (#2)\n_EIP_EstbTargetSta[2]*2\nNode 02 error output\nNormal Target\nNode Information (#2) Node 02\n_EIP_EstbTargetSta[2]*2 error output\n*1. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\nBuilt-in EtherNet/IP port 2: _EIP2_EtnOnlineSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EtnOnlineSta\n*2. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\nBuilt-in EtherNet/IP port 2: _EIP2_EstbTargetSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\n Data Processing Programming Example\n• The following shows an example where data processing is performed only when data links are\noperating normally.\n6-88 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nThe parts of the ladder\nNormal operation flag program that use the data\nAdditional parts\nlink area for the relevant\nnode are processed only\nwhen the corresponding\nNormal operation flag normal operation flag is ON.\n• The following shows an example where data processing is performed only when data links are\noperating normally with MC and MCR instructions, or with JMP instructions.\nNode A data link\nnormal operation flag\nMC\nNode A data processing\nMCR\nNode B data link\nnormal operation flag\nMC\nNode B data processing\nMCR\nNode C data link\nnormal operation flag\nMC\nNode C data processing\nMCR\nPrecautions for Correct Use\nEven if an error occurs in communications with a target device, the input data from the target\ndevice will remain stored in words allocated in memory to the local node. To prevent malfunc-\ntions, write the user program so that no input processing is performed when any of the following\nbits of the _EIP_ErrSta (EtherNet/IP Error) variable is TRUE.\n• Major fault: Bit 7\n• Partial fault: Bit 6\n• Minor fault: Bit 5\n6-3-2 Status Flags Related to Tag Data Links\nThe status of the tag data links is reflected in the following system-defined variables.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-89\n6-3\nLadder\nProgramming\nfor\nTag\nData\nLinks\n6\n6-3-2\nStatus\nFlags\nRelated\nto\nTag\nData\nLinks\n6 Tag Data Link Functions\nVariable Description\n_EIP_TargetPLCModeSta[255]*1 (Target This variable shows the operating status of the target node Control-\nPLC Operating Mode) ler that is connected with the built-in EtherNet/IP port as the origina-\n(Corresponds to the Controller Operating tor.\nFlag in the Controller status.) The information in this area is valid only when the corresponding\nNormal Target Node Information is TRUE. If the value is FALSE, the\nTarget Node Controller Operating Information indicates the previous\noperating status.\nArray[x] is TRUE: The target Controller with a node address of x\nis in operating status.\nArray[x] is FALSE: Other than the above.\n_EIP_TargetNodeErr[255]*2 (Target Node This variable indicates that the connection for Registered Target\nError Information) Node Information is not established or that an error has occurred in\n(Corresponds to the Controller Error Flag the target the Controller.\nin the Controller status.) The array elements are valid only when the Registered Target Node\nInformation is TRUE.\nArray[x] is TRUE: The Registered Target Node Information for a\nnode address of x is TRUE, and the Normal\nTarget Node Information is FALSE or the Target\nPLC Error Information is TRUE.\nArray[x] is FALSE: When the Registered Target Node Information\nfor a node address of x is FALSE, or when the\nRegistered Target Node Information is TRUE,\nthe Normal Target Node Information is TRUE,\nand the Target PLC Error Information is\nFALSE.\n_EIP_EstbTargetSta[255]*3 (Normal Tar- This variable gives a list of nodes that have normally established\nget Node Information) EtherNet/IP connections.\n(This status is not included in the Control- Array[x] is TRUE: The connection to the node with a node ad-\nler status.) dress of x is established normally.\nArray[x] is FALSE: A connection is not established yet, or an error\nhas occurred.\n*1. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\nBuilt-in EtherNet/IP port 2: _EIP2_TargetPLCModeSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetPLCModeSta\n*2. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetNodeErr\nBuilt-in EtherNet/IP port 2: _EIP2_TargetNodeErr\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_TargetNodeErr\n*3. This is a system-defined variable for NJ-series CPU Units.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, the variable varies depending on the\nbuilt-in EtherNet/IP port, as shown below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\nBuilt-in EtherNet/IP port 2: _EIP2_EstbTargetSta\nFor NX1P2 CPU Units, the variable is as below.\nBuilt-in EtherNet/IP port 1: _EIP1_EstbTargetSta\n6-90 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\n6-4 Tag Data Links with Other Models\nThe performance of tag data links depends on the CPU Unit model and EtherNet/IP Unit model as\nshown below.\nWhen you use tag data links between the built-in EtherNet/IP port on an NJ/NX-series CPU Unit and\nanother CPU Unit or EtherNet/IP Unit, configure the tag data link settings based on the Unit which has\nthe lower level of communications performance.\n Differences in Tag Data Link Performance Specifications\nCPU CS1W-EIP21\nNX-series CPU Unit NJ-series CPU CJ2M-CPU3£\nUnit CS1W-\nUnit\nUnit version EIP21S\nCJ1W-EIP21\nItem\nNX- Ver. CJ1W-\nNX701 NX502 NX102 NX1P2 1.03 or 2.1 or\nEIP201 1.00 to 2.0 EIP21S\nlater later"}
+{"question": "02 CJ2H-", "answer": "CPU6£-EIP\nTag Total 184,832 184,832 46,208 9,600 9,600 words 640 words 184,832\nsize of words words words words words\nall tags (total of (total of (total of (total of\n369,664 369,664 92,416 19,200\nwords words words words\nwith two with two with two with two\nports) ports) ports) ports)\nMaxi- 722 722 words 300 words 20 640 722 words\nmum words (721 words when (299 words when the tag set includes the words words (721 words\nsize of (721 the tag set includes Controller status) (19 (639 when the tag\ntag words the Controller sta- words words set includes\nwhen tus) when when the Controller\nthe tag the tag the tag status)\nset in- set in- set in-\ncludes cludes cludes\nthe Con- the Con- the Con-\ntroller troller troller\nstatus) status) status)\nNumber 1024 256 256*1 32 256\nof regis- (total of (total of 512 with two ports)\ntrable 2048\ntags with two\nports)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-91\n6-4\nTag\nData\nLinks\nwith\nOther\nModels\n6\n6 Tag Data Link Functions\nCPU CS1W-EIP21\nNX-series CPU Unit NJ-series CPU CJ2M-CPU3£\nUnit CS1W-\nUnit\nUnit version EIP21S\nCJ1W-EIP21\nItem\nNX- Ver. CJ1W-\nNX701 NX502 NX102 NX1P2 1.03 or 2.1 or\nEIP201 1.00 to 2.0 EIP21S\nlater later"}
+{"question": "02 CJ2H-", "answer": "CPU6£-EIP\nTag set Maxi- 722 722 words 300 words 20 640 722 words\nmum words (721 words when (299 words when the tag set includes the words words (721 words\nsize of 1 (721 the tag set includes Controller status) (19 (639 when the tag\ntag set words the Controller sta- words words set includes\nwhen tus) when when the Controller\nthe tag the tag the tag status)\nset in- set in- set in-\ncludes cludes cludes\nthe Con- the Con- the Con-\ntroller troller troller\nstatus) status) status)\nNumber 64 8 64 8\nof tags (63 tags (7 tags (63 tags (7 tags when the tag set includes the Controller status)\nper tag when when when Note: Input and output variables cannot be combined in one tag set.\nset the tag the tag the tag\nset in- set in- set in-\ncludes cludes cludes\nthe Con- the Con- the Con-\ntroller troller troller\nstatus) status) status)\nNote: In- Note: In- Note: In-\nput and put and put and\noutput output output\nvaria- varia- varia-\nbles bles bles\ncannot cannot cannot\nbe com- be com- be com-\nbined in bined in bined in\none tag one tag one tag\nset. set. set.\nNumber 256 256 64 32 (total 32 32 256\nof regis- (total of (total of (total of of 40\ntrable 512 with 512 with 128 with with two\ntag sets two two two ports)*2\nports) ports) ports)\nConnec- Number 256 256 64 32 (total 32 32 256\ntion of con- (total of (total of (total of of 64\nnections 512 with 512 with 128 with with two\ntwo two two ports)\nports) ports) ports)\nMaxi- 722 722 words *3 300 words 20 640 252 or 722\nmum words *3 (Data concurrency (Refer to 6-1-7 Concurrency of Tag Data words words words*3\ndata (Data is maintained at Link Data on page 6-14 for the conditions (Data concurrency (Data concur-\nsize per concur- each connection.) for maintaining data concurrency on a is maintained at rency is main-\nconnec- rency is connection basis.) each connection.) tained at each\ntion main- connection.)\ntained at\neach\nconnec-\ntion.)\n6-92 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n6 Tag Data Link Functions\nCPU CS1W-EIP21\nNX-series CPU Unit NJ-series CPU CJ2M-CPU3£\nUnit CS1W-\nUnit\nUnit version EIP21S\nCJ1W-EIP21\nItem\nNX- Ver. CJ1W-\nNX701 NX502 NX102 NX1P2 1.03 or 2.1 or\nEIP201 1.00 to 2.0 EIP21S\nlater later"}
+{"question": "02 CJ2H-", "answer": "CPU6£-EIP\nPacket intervals 1.0 to 0.5 to 1 to 10,000 ms in 1- 2 to 10 to 1 to 1 to 10,000 ms in 0.5 to 10,000\n(RPIs) 10,000 10,000 ms increments 10,000 10,000 10,000 0.5-ms increments ms in 0.5-ms\nms in ms in ms in 1- ms in 1- ms in 1- increments"}
+{"question": "0-ms 0.5-ms ms in- ms in- ms in-", "answer": "incre- incre- cre- cre- cre-\nments ments ments ments ments\nCommunications 40,000 40,000 20,000 12,000 3,000 1,000 3,000 3,000 pps 6,000 pps\nbandwidth used pps*5 pps*5 pps*5 pps*5 pps pps pps\n(pps)*4\n*1. The maximum number of tags is given for the following conditions.\n• All tag sets contain eight tags.\n• The maximum number of tag sets (32) is registered.\n*2. When tag sets that exceed total of 40 are set, a Number of Tag Sets for Tag Data Links Exceeded (840E0000 hex) event occurs.\n*3. To use data of 505 bytes or more, large forward open (an optional CIP specification) should be supported. The SYSMAC CS/CJ-series\nUnits support large forward open, and if you use nodes from other companies, confirm that the devices also support it.\n*4. Here, pps means “packets per second” and indicates the number of packets that can be processed in one second.\n*5. If the two EtherNet/IP ports are used simultaneously, the maximum communications data size means the maximum data size of the\ntotal of the two ports.\n*6. An NX-EIP201 can only be used with the NX502 CPU Unit. However, check the effect on task execution time because it increases I/O\nrefreshing time.\n Specifying Tags\nWhen you assign a tag to a device, you can specify the device with its network variable or I/O\nmemory address. Some CPU Units, however, may not support both of these methods.\nCommunications with such CPU Units are possible though, regardless of whether the I/O memory\naddress or network variable is specified for the tag assignment.\nThe supported tag specification methods for each CPU Unit are listed in the table below.\nYes: Supported, No: Not supported\nCPU Unit Network Configura- Specifying Specifying\ntor with network with I/O memo-\nEtherNet/IP Unit\nhardware list name variable ry address\nNX-series CPU Unit --- NX701 Yes No\nNX502 Yes Yes *1\nNX102 Yes Yes *1*2\nNX1P2££££ Yes Yes *1*2\nNJ-series CPU Unit --- NJ501-££££ Yes Yes*1\nNJ301-££££\nNJ101\nCJ1W-EIP21*3 CJ1W-EIP21 (NJ) Yes Yes*1\nCJ1W-EIP21S*4 CJ1W-EIP21S (NJ) Yes Yes*1\nCJ2H-CPU6£-EIP --- CJ2B-EIP21 Yes Yes\nCJ1W-EIP21 CJ1W-EIP21 (CJ2) Yes Yes\nCJ1W-EIP21S CJ1W-EIP21S (CJ2) Yes Yes\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 6-93\n6-4\nTag\nData\nLinks\nwith\nOther\nModels\n6\n6 Tag Data Link Functions\nCPU Unit Network Configura- Specifying Specifying\ntor with network with I/O memo-\nEtherNet/IP Unit\nhardware list name variable ry address\nCJ2H-CPU6£ CJ1W-EIP21 CJ1W-EIP21 (CJ2) Yes*5 Yes\nCJ1W-EIP21S CJ1W-EIP21S (CJ2) Yes*5 Yes\nCJ2M-CPU3£ --- CJ2M-EIP21 Yes Yes\nCJ1W-EIP21 CJ1W-EIP21 (CJ2) Yes Yes\nCJ1W-EIP21S CJ1W-EIP21S (CJ2) Yes Yes\nCJ2M-CPU1£ CJ1W-EIP21 CJ1W-EIP21 (CJ2) Yes*6 Yes\nCJ1W-EIP21S CJ1W-EIP21S (CJ2) Yes*6 Yes\nCJ1 CPU Unit CJ1W-EIP21 CJ1W-EIP21 No Yes\nCJ1W-EIP21S CJ1W-EIP21S No Yes\nCS1 CPU Unit CS1W-EIP21 CS1W-EIP21 No Yes\nCS1W-EIP21S CS1W-EIP21S No Yes\n*1. To specify an I/O memory address for tag assignment, do not specify the address directly. Instead, cre-\nate a variable with an AT specification of the I/O memory address on the Sysmac Studio, and then speci-\nfy the variable for the tag.\n*2. For NX102 and NX1P2 CPU Units, you need to set memory used for CJ-series Unit to use the I/O mem-\nory address. For details on memory settings used for CJ-series Unit, refer to the NJ/NX-series CPU Unit\nSoftware User's Manual (Cat. No. W501).\n*3. The CJ1W-EIP21 can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21: Unit version 2.1 or later\n• NJ-series CPU Unit: Unit version. 1.01 or later\n• Sysmac Studio: Version 1.02 or higher\n*4. The CJ1W-EIP21S can be mounted to the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21S: Lot. number: 241001£ or later\n• NJ-series CPU Unit: Unit version 1.67 or later\n• Sysmac Studio: Version 1.60 or higher\n*5. A CJ2H-CPU6£ with unit version 1.6 or later is required to use this function.\n*6. A CJ2M-CPU1£ with unit version 2.2 or later is required to use this function.\n6-94 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7\nCIP Message Communications\n7-1 Overview of the CIP Message Communications Service...........................7-3\n7-1-1 Overview of the CIP Message Communications Service................................7-3\n7-1-2 Message Communications Service Specifications..........................................7-3\n7-2 Client Function of CIP Message Communications.....................................7-4\n7-2-1 Overview.........................................................................................................7-4\n7-2-2 CIP Communications Instructions...................................................................7-4\n7-2-3 Using CIP Communications Instructions.........................................................7-5\n7-2-4 Route Path......................................................................................................7-6\n7-2-5 Request Path (IOI)........................................................................................7-16\n7-2-6 Service Data and Response Data.................................................................7-20\n7-2-7 Sample Programming for CIP Connectionless (UCMM) Message\nCommunications............................................................................................7-22\n7-2-8 Sample Programming for CIP Connection (Class 3) Message Com-\nmunications...................................................................................................7-27\n7-2-9 Operation Timing...........................................................................................7-34\n7-2-10 Response Codes...........................................................................................7-35\n7-3 Server Function of CIP Message Communications..................................7-39\n7-3-1 CIP Message Structure for Accessing CIP Objects......................................7-40\n7-3-2 CIP Message Structure for Accessing Variables...........................................7-41\n7-4 Specifying Request Path.............................................................................7-42\n7-4-1 Examples of CIP Object Specifications.........................................................7-42\n7-4-2 Examples of Variable Specifications.............................................................7-43\n7-4-3 Logical Segment............................................................................................7-43\n7-4-4 Data Segment...............................................................................................7-43\n7-4-5 Specifying Variable Names in Request Paths...............................................7-44\n7-5 CIP Object Services.....................................................................................7-48\n7-5-1 CIP Objects Sent to the Built-in EtherNet/IP Port..........................................7-48\n7-5-2 Identity Object (Class ID: 01 hex)..................................................................7-48\n7-5-3 NX Configuration Object (Class ID: 74 hex)..................................................7-53\n7-5-4 TCP/IP Interface Object (Class ID: F5 hex)..................................................7-74\n7-5-5 Ethernet Link Object (Class ID: F6 hex)........................................................7-77\n7-5-6 Controller Object (Class ID: C4 hex).............................................................7-83\n7-6 Read and Write Services for Variables.......................................................7-85\n7-6-1 Read Service for Variables............................................................................7-85\n7-6-2 Write Service for Variables............................................................................7-86\n7-7 Variable Data Types......................................................................................7-89\n7-7-1 Data Type Codes...........................................................................................7-89\n7-7-2 Common Format...........................................................................................7-89\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-1\n7\n7 CIP Message Communications\n7-7-3 Elementary Data Types.................................................................................7-90\n7-7-4 Derived Data Types.......................................................................................7-91\n7-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n7-1 Overview of the CIP Message Com-\nmunications Service\n7-1-1 Overview of the CIP Message Communications Service\nCIP commands can be sent to devices on the EtherNet/IP network whenever they are required.\nYou execute CIP_SEND instructions in a program in the NJ/NX-series CPU Unit to send CIP com-\nmands, such as those to read and write data and to receive the responses.\nYou can use CIP messages from the client to read and write memory in the Controller with the server\nwithout adding any special programming to the user program of the Controller with the server.\nBuilt-in\nNJ/NX-series\nController EtherNet/IP or host computer\nport\nCIP command\nEtherNet/IP\nCIP response\nBuilt-in\nNJ/NX-series EtherNet/IP\nController port\n7-1-2 Message Communications Service Specifications\nItem Specification\nMessage type Either of the following can be selected.\nCIP UCMM connectionless messages\nCIP class 3 connection messages\nExecution method CIPSend (Send Explicit Message Class 3) instruction or CI-\nPUCMMSend (Send Explicit Message UCMM) instruction\nData contents Sending required CIP commands and receiving responses\nCommunications parameters Message type, timeout value, and route path specification\nMaximum length per Non-connection type 502 bytes\nconnection (UCMM)\nConnection type • Using Forward_Open\n(class 3) 502 bytes\n• Using Large_Forward_Open\nNX701 CPU Unit: 8,192 bytes\nNX502 CPU Unit: 1,994 bytes\nNX102 CPU Unit: 1,994 bytes\nNX1P2 CPU Unit: 1,994 bytes\nNJ-series CPU Unit: 1,994 bytes\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-3\n7-1\nOverview\nof\nthe\nCIP\nMessage\nCommunications\nService\n7\n7-1-1\nOverview\nof\nthe\nCIP\nMessage\nCommunications\nService\n7 CIP Message Communications\n7-2 Client Function of CIP Message Com-\nmunications\n7-2-1 Overview\nThe NJ/NX-series CPU Units can send a CIP message to an external device to request a service by\nspecifying an internal object of the device which supports the server function of CIP message commu-\nnications.\nThis is called the client function of CIP message communications.\nThe NJ/NX-series CPU Units execute CIP communications instructions in the user program and send\nCIP messages. With those CIP messages, you can read and write variables of an NJ/NX-series CPU\nUnit on the EtherNet/IP network.\nNJ/NX-series NJ/NX-series\nCPU Unit Built-in EtherNet/IP port CPU Unit Built-in EtherNet/IP port\nCIP_SEND CIP communications instruction Specify a variable name.\nEtherNet/IP\nSpecify the CIP communications parameters,\nsuch as the route path, as well as the service\ncode, the request path, and the service data.\n7-2-2 CIP Communications Instructions\nThe following CIP communications instructions are available.\nFor details on CIP communications instructions, refer to the NJ/NX-series Instructions Reference\nManual (Cat. No. W502).\nInstruc- Communica-\nName Description\ntions tions method\nCIPUCMM- Read Variable Reads the value of a variable with a Network Publish at- CIP UCMM\nRead UCMM Explicit tribute from the specified remote Controller on the CIP connectionless\nnetwork and stores the value in a variable at the local message\nController.\nCIPUCMM- Write Variable Writes the value of a variable at the local Controller to a\nWrite UCMM Explicit variable with a Network Publish attribute at the specified\nremote Controller on the CIP network.\nCIPUCMM- Send Explicit Mes- Sends a specified CIP command to the specified remote\nSend sage UCMM Controller on the CIP network.\nRefer to 7-2-10 Response Codes on page 7-35 and\n7-5 CIP Object Services on page 7-48 for information\non the service codes and response codes that are used\nwith the NJ/NX-series CPU Units.\n7-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nInstruc- Communica-\nName Description\ntions tions method\nCIPOpen Open CIP Class 3 Opens a CIP class 3 connection (Large_Forward_Open) CIP class 3\nConnection with the specified remote node. connection\n(Large_For- message\nward_Open)\nCIPOpen- Open CIP Class 3 Opens a CIP class 3 connection with the specified re-\nWithData- Connection with mote node that allows class 3 explicit messages of the\nSize Specified Data Size specified data length or shorter to be sent and received.\nCIPRead Read Variable Reads the value of a variable with a Network Publish at-\nClass 3 Explicit tribute from the specified remote Controller on the CIP\nnetwork and stores the value in a variable at the local\nController.\nCIPWrite Write Variable Writes the value of a variable at the local Controller to a\nClass 3 Explicit variable with a Network Publish attribute at the specified\nremote Controller on the CIP network.\nCIPSend Send Explicit Mes- Sends a specified class 3 CIP command to the specified\nsage Class 3 remote Controller on the CIP network.\nRefer to 7-2-10 Response Codes on page 7-35 and\n7-5 CIP Object Services on page 7-48 for information\non the service codes and response codes that are used\nwith the NJ/NX-series CPU Units.\nCIPClose Close CIP Class 3 Closes the CIP class 3 connection that is specified by\nConnection the handle.\nVersion Information\nA CPU Unit with unit version 1.06 or later and Sysmac Studio version 1.07 or higher are re-\nquired to use the CIPOpenWithDataSize instruction.\n7-2-3 Using CIP Communications Instructions\nCIP message communications include the following processes.\nIf CIP class 3 connections are used, the open and close processes are required before and after the\ndata is sent and received.\nProcess Description Instruction\nOpen process Execute this process before you use a CIP message. CIPOpen\n(only for CIP class 3 con- Open processing is continued until a CIP class 3 con- CIPOpenWithData-\nnections)*1 nection is established. Size\nSending and receiving varia- This process is used to read and write data for specified CIPUCMMRead\nble data*2 variables with the Network Publish attributes. CIPUCMMWrite\nCIPRead\nCIPWrite\nSending CIP commands You can set the required CIP command. CIPUCMMSend\nCIPSend\nClose process This process closes the connection. CIPClose\n(only for CIP class 3 con-\nnections)\n*1. The maximum number of connection handles that you can obtain simultaneously through the opening proc-\ness is 32. Even if a connection is disconnected for a timeout, the handle is not released. Execute the CIP-\nClose instruction to close the connection.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-5\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-3\nUsing\nCIP\nCommunications\nInstructions\n7 CIP Message Communications\n*2. Addresses in memory for CJ-series Units (e.g., D0000) cannot be specified directly. To access memory for CJ-\nseries Units, access a variable with an AT specification. (Accessing is possible only for NJ-series CPU Units.)\nLocal Controller Remote Controller\n(1) Specifies\nthe variable.\nCIPRead\nExecute\nHandle (2) Reads data\n‘VAR_1’ SrcDat starting at D0000 D00000\n5 Size for the number of Allocated. D00001\nelements.\nDstDat VAR : ARRAY[0..9] OF WORD AT %D0 D00002\nMyArray Network Publish attribute …….\nWORD[10]\nRcvSize D00009\n*\nAddresses in the memory for\n* To access memory for CJ-series Units in\nCJ-series Units are assigned to the\nthe local Controller, you also must assign\nvariable and the variable is given\nthe required addresses to variables.\nthe Network Publish attribute.\nMyArray : ARRAY[0..9] OF WORD:\nMyArray[0] : Value of D00000 in remote Controller\nValue of D00001 in remote Controller\nValue of D00002 in remote Controller\n…….\nMyArray[9] : Value of D00009 in remote Controller\nPrecautions for Correct Use\nYou can execute up to 32 CIP communications instructions at the same time regardless of the\ninstruction types.\nUse exclusive control in the user program so that the number of CIP communications instruc-\ntions executed at the same time does not exceed the above number.\n7-2-4 Route Path\nThe route path indicates the path from the local CPU Unit to the remote Controller on the network.\nRouting for CIP communications instructions is performed based on the route path.\nRoute Path Notation\nThe EPATH data type is used to give route paths. The basic format is shown below.\nNetwork_type_number\\Destination_address\n NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit\nTwo internal CPU Units are provided (each with a unique unit address) to control the two built-in\nEtherNet/IP ports.\n• For the built-in EtherNet/IP port 1: CPU Unit with a unit address of 00 hex (CPU #00)\n• For the built-in EtherNet/IP port 2: CPU Unit with a unit address of 01 hex (CPU #01)\nThe RoutePath input variable for the CIP communications instructions is used to distinguish the two\nCPU Units (CPU #00 and CPU #01) and send the CIP communications instructions.\n7-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRoute path for sending a CIP communications instruction\n• The CIP communications instruction is issued from CPU #00. (a)\n• The output from the built-in EtherNet/IP port 2 is routed from CPU #00 via CPU #01. (b) to (c)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit\nBackplane\nCPU#00 port (#01) CPU#01\n(Unit address 00 hex) (Unit address 01 hex)\n(b)\n(a) (c)\nCommunications Communications\nport (#02) port (#02) IP address : IP address :"}
+{"question": "168.250.2 192.168.251.2", "answer": "Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2\nRoute path specifications\nRoute no-\nRoute Network type number (hexadeci- Destination address (hexadeci-\ntation\nmal) mal)\nOutput from the (a) #02 (communications port) IP address\nbuilt-in\nEtherNet/IP port\n1\nOutput from the (b) #01 (backplane port) #01 (unit address of the CPU Unit)\nbuilt-in (CPU #01 for built-in EtherNet/IP\nEtherNet/IP port port 2 communications)\n2 (c) #02 (communications port) IP address\nRoute Path\nOutput from built-in EtherNet/IP port 1: 02\\192.168.251.2\n(a)\nOutput from built-in EtherNet/IP port 2: 01\\#01 \\02\\192.168.250.2\n(b) (c)\n• The CPU Units (CPU#00 and CPU#01), which control the respective built-in EtherNet/IP ports,\ncan be accessed via the backplane port regardless of whether the input is routed via the Ether-\nNet/IP port 1 or 2.\nExample: Inputting an Ethernet Link object (class ID: F6 hex) to the built-in EtherNet/IP port 1 of\nthe remote NX701 CPU Unit, and reading out the settings and status of the built-in EtherNet/IP port"}
+{"question": "NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-7", "answer": "7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-4\nRoute\nPath\n7 CIP Message Communications\nNX701 CPU Unit\nBackplane\nCPU#00 port (#01) CPU#01\n(Unit address 00 hex) (Unit address 01 hex)\n(b)\nCommunications Communications\nport (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP\nIP address : port 1 port 2"}
+{"question": "168.250.1", "answer": "(a)\nRoute Path : 02\\192.168.250.1 \\01\\#01\n(a) (b)\n NX1P2 CPU Unit\nAs shown in the table below, the network type number and the destination address are determined\ndepending on whether the output is routed (1) to a Unit on the CPU Rack or (2) from a communica-\ntions port on a Communications Unit.\nNetwork type number (hexadec- Destination address (hexadeci-\nRoute\nimal) mal)\n(1) Output to a Unit on the CPU #01 (backplane port) Unit address of the destination\nRack Unit (Refer to Additional Informa-\ntion below.)\n(2) Output from a communications #02 (built-in EtherNet/IP port) IP address\nport on a Communications Unit\nNX1P2\nCPU Unit\n(1)\nBackPlane\nPort (#01)\nCommunications\nIP address\nport (#02)\n(2)"}
+{"question": "When Routing the Output to a Unit on the CPU Rack", "answer": "Route the output to the backplane port for the network with the CPU Rack, with the Unit ad-\ndress of the destination Unit specified as the destination address."}
+{"question": "When Routing the Output from a Communications Port on a Communications Unit", "answer": "Route the output to an EtherNet/IP port, with the IP address specified as the destination node\naddress.\n7-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAdditional Information\nUnit Addresses\nUnit addresses are used to identify each of devices connected to a single node on a network.\nUnit addresses are set as shown below.\n• CPU Unit: 00 hex\n NJ-series CPU Unit\nAs shown in the table below, the network type number and the destination address are determined\ndepending on whether the output is routed (1) to a Unit on the CPU Rack or (2) from a communica-\ntions port on a Communications Unit.\nNetwork type number (hexadec- Destination address (hexadeci-\nRoute\nimal) mal)\n(1) Output to a Unit on the CPU #01 (backplane port) Unit address of the destination\nRack Unit (Refer to Additional Informa-\ntion below.)\n(2) Output from a communications #02 (built-in EtherNet/IP port) IP address\nport on a Communications Unit\n(1)\nIP address\n(2)\nsserdda\ntinU\n7 CIP Message Communications\nNJ-series CPU Unit\nBackplane\nport #01\nCommunications\nport (#02)"}
+{"question": "When Routing the Output to a Unit on the CPU Rack", "answer": "Route the output to the backplane port for the network with the CPU Rack, with the Unit ad-\ndress of the destination Unit specified as the destination address."}
+{"question": "When Routing the Output from a Communications Port on a Communications Unit", "answer": "Route the output to an EtherNet/IP port, with the IP address specified as the destination node\naddress.\nAdditional Information\nUnit Addresses\nUnit addresses are used to identify each of devices connected to a single node on a network.\nUnit addresses are set as shown below.\n• CPU Unit: 00 hex, 01 hex\n• CPU Bus Units (EtherNet/IP Units): Unit number + 10 hex\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-9\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-4\nRoute\nPath\n7 CIP Message Communications\nRoute Path Notation Examples\n NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit\nThe route path notation is different for communications using the built-in EtherNet/IP port 1\n(CPU#00) and for communications using the built-in EtherNet/IP port 2 (CPU#01).\nThis section provides examples of route paths.\nThis example explains communications via an NX-series CPU Unit."}
+{"question": "Using the built-in EtherNet/IP port 1 (local CPU #00)", "answer": "(Local CPU #00 to destination CPU #00)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit\nCPU#00 CPU#01 CPU#00 CPU#01\n(Unit address 00 hex) (Unit address 01 hex) (Unit address 00 hex) (Unit address 01 hex)\nCommunications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2\n(a) IP address :"}
+{"question": "168.250.2", "answer": "a) Local CPU #00 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nRoute Path : 02\\192.168.250.2"}
+{"question": "Using the built-in EtherNet/IP port 2 (local CPU #01)", "answer": "(Local CPU #00 to destination CPU #01 via local CPU #01)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit\nBackplane port\nCPU#00 (#01) CPU#01 CPU#00 CPU#01\n(Unit address 00 hex) (Unit address 01 hex) (Unit address 00 hex) (Unit address 01 hex)\n(a)\nCommunications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2\n(b)\nIP address :"}
+{"question": "168.251.2", "answer": "a) Local backplane to local CPU #01\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#01\" (CPU#01) Note: This is in order to output using the sender IP\naddress of the built-in EtherNet/IP port 2.\nb) Local CPU #01 to destination IP address\n7-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nRoute Path : 01\\#01 \\02\\192.168.251.2\n(a) (b)"}
+{"question": "Communicating with the destination built-in EtherNet/IP port 2 (destination CPU #01) via the", "answer": "destination built-in EtherNet/IP port 1 (destination CPU #00)\n(Local CPU #00 to destination CPU #01 via destination CPU #00)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit\nBackplane port\nCPU#00 CPU#01 CPU#00 (#01) CPU#01\n(Unit address 00 hex) (Unit address 01 hex) (Unit address 00 hex) (Unit address 01 hex)\n(b)\nCommunications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2\n(a) IP address :"}
+{"question": "168.250.2", "answer": "a) Local CPU #00 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nb) Destination backplane to destination CPU #01\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#01\" (CPU#01)\nRoute Path : 02\\192.168.250.2 \\01\\#01\n(a) (b)"}
+{"question": "Communicating with the destination built-in EtherNet/IP port 1 (destination CPU #00) via the", "answer": "destination built-in EtherNet/IP port 2 (destination CPU #01)\n(Local CPU #00 to destination CPU #00 via destination CPU #01)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit\nBackplane port Backplane port\nCPU#00 (#01) CPU#01 CPU#00 (#01) CPU#01\n(Unit address 00 hex) (Unit address 01 hex) (Unit address 00 hex) (Unit address 01 hex)\n(a) (c)\nCommunications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2\n(b)\nIP address :"}
+{"question": "168.251.2", "answer": "a) Local backplane to local CPU #01\n• Network type number: \"01\" (Output to Backplane port)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-11\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-4\nRoute\nPath\n7 CIP Message Communications\n• Destination address: \"#01\" (CPU#01) Note: This is in order to output using the sender IP\naddress of the built-in EtherNet/IP port 2.\nb) Local CPU #01 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nRoute Path : 01\\#01 \\02\\192.168.251.2\n(a) (b)\nc) Destination CPU #01 to destination CPU #00\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#00\" (CPU#00)\nRoute Path : 01\\#01 \\02\\192.168.251.2\\01\\#00\n(a) (b) (c)"}
+{"question": "Using an NX701 CPU Unit, NX502 CPU Unit, or NX102 CPU Unit as a relay Unit (the built-in", "answer": "EtherNet/IP port 1 to the built-in EtherNet/IP port 2)\n(Local CPU #00 to destination CPU #00 via relay CPU #00 and relay CPU #01)\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit (Relay Unit) NX701, NX502, or NX102 CPU Unit\nBackplane\nCPU#00 CPU#01 CPU#00 port (#01) CPU#01 CPU#00 CPU#01\n(Unit address (Unit address (Unit address (Unit address (Unit address (Unit address\n00 hex) 01 hex) 00 hex) (b) 01 hex) 00 hex) 01 hex)\nCommunications Communications Communications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2 port 1 port 2\nIP address : IP address :\n(a) 192.168.250.2 (c) 192.168.252.3\na) Local CPU #00 to relay IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the relay IP address\nb) Relay backplane to relay CPU #01\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#01\" (CPU#01) Note: This is in order to output using the sender IP\naddress of the built-in EtherNet/IP port 2.\nc) Relay CPU #01 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nRoute Path : 02\\192.168.250.2\\01\\#01\\02\\192.168.252.3\n(a) (b) (c)"}
+{"question": "Using an NX701 CPU Unit, NX502 CPU Unit, or NX102 CPU Unit as a relay Unit (the built-in", "answer": "EtherNet/IP port 2 to the built-in EtherNet/IP port 1)\n(Local CPU #00 to destination CPU #00 via local CPU #01, relay CPU #01, and relay CPU #00)\n7-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nNX701, NX502, or NX102 CPU Unit NX701, NX502, or NX102 CPU Unit (Relay Unit) NX701, NX502, or NX102 CPU Unit\nBackplane Backplane\nCPU#00 port (#01) CPU#01 CPU#00 port (#01) CPU#01 CPU#00 CPU#01\n(Unit address (Unit address (Unit address (Unit address (Unit address (Unit address\n00 hex) (a) 01 hex) 00 hex) (c) 01 hex) 00 hex) 01 hex)\nCommunications Communications Communications Communications Communications Communications\nport (#02) port (#02) port (#02) port (#02) port (#02) port (#02)\nBuilt-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP Built-in EtherNet/IP\nport 1 port 2 port 1 port 2 port 1 port 2\nIP address : IP address :"}
+{"question": "168.251.2 192.168.252.3", "answer": "(d)\n(b)\na) Local backplane to local CPU #01\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#01\" (CPU#01) Note: This is in order to output using the sender IP\naddress of the built-in EtherNet/IP port 2.\nb) Local CPU #01 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nc) Relay backplane to relay CPU #00\n• Network type number: \"01\" (Output to Backplane port)\n• Destination address: \"#00\" (CPU#00) Note: This is in order to output using the sender IP\naddress of the built-in EtherNet/IP port 1.\nd) Relay CPU #00 to destination IP address\n• Network type number: \"02\" (Output to the communications port)\n• Destination address: Specify the destination IP address\nRoute Path : 01\\#01\\02\\192.168.251.2\\01\\#00\\02\\192.168.252.3\n(a) (b) (c) (d)\n NX1P2 CPU Unit\nThis section provides examples of route paths."}
+{"question": "Communicating between Built-in EtherNet/IP Ports", "answer": "Example: Communicating between the built-in EtherNet/IP ports on CPU Unit 1 and CPU\nUnit 2\nCPU Unit #1 CPU Unit #2\nCPU#00\n(Unit address 00 hex)\nCommunications port (#02) IP address"}
+{"question": "168.250.2", "answer": "Built-in EtherNet/IP port Built-in EtherNet/IP port\nCommunications port (#02)\n• Network type number: \"#02\" (Output the command via the built-in EtherNet/IP port)\n• Destination address: Specify the destination IP address\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-13\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-4\nRoute\nPath\n7 CIP Message Communications\n• Route path: 02\\192.168.250.2\n NJ-series CPU Unit\nThe notation of the route path is different for communications on the built-in EtherNet/IP port and\nfor communications on an EtherNet/IP Unit.\nThis section provides examples of route paths."}
+{"question": "Communicating between Built-in EtherNet/IP Ports", "answer": "Example: Communicating between the built-in EtherNet/IP ports on CPU Unit 1 and CPU\nUnit 2\nCPU Unit #1 CPU Unit #2\nCPU#00\n(Unit address 00 hex)\nCommunications port (#02) IP address"}
+{"question": "168.250.2", "answer": "Built-in EtherNet/IP port Built-in EtherNet/IP port\nCommunications port (#02)\n• Network type number: \"#02\" (Output the command via the EtherNet/IP port)\n• Destination address: Specify the destination IP address\n• Route path: 02\\192.168.250.2"}
+{"question": "Communicating from a Built-in EtherNet/IP Port to an EtherNet/IP Unit", "answer": "Example: Communicating from the built-in EtherNet/IP port on CPU Unit 1 to CPU Unit 2 via\nthe EtherNet/IP Unit mounted to CPU Unit 2\nCPU Unit 1 CPU Unit 2 EtherNet/IP Unit 2\nUnit address Backplane\n00 hex port #01\nCommunications\nport (#02)\nIP address:"}
+{"question": "168.250.2", "answer": "Built-in EtherNet/IP port EtherNet/IP port\na) CPU Unit 1 to EtherNet/IP Unit 2\n• Network type number: \"#02\" (Output the command via the EtherNet/IP port)\n• Destination address: Specify the destination IP address\nb) EtherNet/IP Unit 2 to CPU Unit 2\n• Network type number: \"#01\" (Output the command via the internal backplane port)\n• Destination address: \"#00\" (Unit address of the CPU Unit)\n7-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRoute path : 02\\192.168.250.2\\01\\#00\n(1) (2)"}
+{"question": "Communicating between EtherNet/IP Units", "answer": "Example: Communicating via EtherNet/IP Units mounted to CPU Unit 1 and CPU Unit 2\nCPU Unit 1 EtherNet/IP Unit 1 CPU Unit 2 EtherNet/IP Unit 2\nUnit address Unit address Backplane\n11 hex 00 hex port #01\nBackplane\nport #01\nIP address:"}
+{"question": "168.250.2", "answer": "Communications\nEtherNet/IP port\nport (#02)\na) CPU Unit 1 to EtherNet/IP Unit 1\n• Network type number: \"#01\" (Output the command via the internal backplane port)\n• Destination address: \"#11\" (Unit address of EtherNet/IP Unit (Unit number: 1+10 hex))\nb) EtherNet/IP Unit 1 to EtherNet/IP Unit 2\n• Network type number: \"#02\" (Output the command via the EtherNet/IP port)\n• Destination address: Specify the destination IP address\nc) EtherNet/IP Unit 2 to CPU Unit 2\n• Network type number: \"#01\" (Output the command via the internal backplane port)\n• Destination address: \"#00\" (Unit address of the CPU Unit)\nRoute path : 01\\#11\\02\\192.168.250.2\\01\\#00\n(1) (2) (3)\nVersion Information\n• You can use the CJ1W-EIP21 EtherNet/IP Unit mounted to an NJ-series Controller with a\nCPU Unit with unit version 1.01 or later and Sysmac Studio version 1.02 or higher.\n• The CJ1W-EIP21S can be used in the following combinations.\na) CJ1W-EIP21S: Lot. number: 241001£ or later\nb) NJ-series CPU Unit: Unit version 1.67 or later\nc) Sysmac Studio: Ver.1.60 or higher"}
+{"question": "Accessing via a Relay Node", "answer": "Example: Communicating from CPU Unit 1 to CPU Unit 3 via CPU Unit 2\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-15\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-4\nRoute\nPath\n7 CIP Message Communications\nCPU Unit 1 CPU Unit 2 EtherNet/IP Unit 2 CPU Unit 3 EtherNet/IP Unit 3\nIP address: Backplane Unit address Backplane"}
+{"question": "168.250.2 port #01 00 hex port #01", "answer": "Communica- Unit address\ntions port 12 hex IP address:\n(#02) Built-in"}
+{"question": "168.257.3", "answer": "EtherNet/IP port\nCommunications\nport (#02)\nBuilt-in EtherNet/IP EtherNet/IP port\nEtherNet/IP port\nport\na) CPU Unit 1 to CPU Unit 2\n• Network type number: \"#02\" (Output the command via the EtherNet/IP port)\n• Destination address: Specify the destination IP address\nb) CPU Unit 2 to EtherNet/IP Unit 2\n• Network type number: \"#01\" (Output the command via the internal backplane port)\n• Destination address: \"#12 hex\" (Unit address of the EtherNet/IP Unit (Unit number: 2+10\nhex =12 hex))\nc) EtherNet/IP Unit 2 to EtherNet/IP Unit 3\n• Network type number: \"#02\" (Output the command via the EtherNet/IP port)\n• Destination address: Specify the destination IP address\nd) EtherNet/IP Unit 3 to CPU Unit 3\n• Network type number: \"#01\" (Output the command via the internal backplane port)\n• Destination address: \"#00\" (Unit address of the CPU Unit)\nRoute path : 02\\192.168.250.2\\01\\#12\\02\\192.168.257.3\\01\\#00\n(1) (2) (3) (4)\n7-2-5 Request Path (IOI)\nA request path indicates an object of a device on the network.\nA CIP communications instruction uses the request path to access an object of a device.\nOverview of Request Path\nIn the CIP world, each device is modeled as a collection of objects. An Object abstractly represents\nthe specific configuration elements of a device.\nExternal request\n(example: read)\nObject\nAttributes\nService Data\nObject\nData\nData\nObject\nData\nProcessing\nObject Instance\nDevice\n7-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nIn the CIP Common Specification, Object, Class, Instance, Attribute, and Service are defined as fol-\nlows: (Source: CIP Common Specification)\nTerm Definition\nObject An abstract representation of a particular component within a device.\nClass A set of objects that all represent the same kind of system component.\nInstance A specific and real (physical) occurrence of an object.\nAttribute A description of an externally visible characteristic or feature of an object.\nService A request from an external object (e.g., to read data).\nYou use the Class ID Instance ID and Attribute ID to access an object.\nYou specify these three IDs to designate an object in a device.\nWhen you make a request from an external device for a service, you must specify the Class ID In-\nstance ID and Attribute ID. (The Instance ID and Attribute ID are not required for some services.)\n.....\n7 CIP Message Communications\nExample: Reading the Name of a Device\n(Identity Object Class ID = 1)\nClass ID = 1\nInstance ID = 1\nService Request Destination\nGet_Attribute_ Class: 1 Instance ID = 1\nSingle Instance: 1\nAttribute: 7 Attribute 1\nAttribute 6\nResponse\nProduct Name Attribute 7\nClass ID = 2\nAttribute = 7\nDevice\nThese are called IOI (Internal Object Identifier) because they identify the Class ID, Instance ID, and\nAttribute ID within the device.\nRefer to 7-5 CIP Object Services on page 7-48 for the class ID, instance ID, attribute ID, and service\ncode for each object.\nProviding the Structure Variables to Input Request Paths\nFor a CIP communications instruction, you prepare a variable to store the request path. In this varia-\nble, you specify the object to access with the user program.\nA structure in which the Class ID, Instance ID, and Attribute ID are specified is provided for the data\ntype of a variable for a request path.\nThere are two types of structures: standard structure (_sREQUEST_PATH) and extension structure\n(_sREQUEST_PATH_EX). When you use an extension structure, it is possible to specify the size ac-\ncording to the size of values of the Class ID, Instance ID, and Attribute ID of the object that you ac-\ncess. When you use a standard structure, the size is always set to 16 bits.\nVersion Information\nA CPU Unit with unit version 1.11 or later and Sysmac Studio version 1.15 or higher are re-\nquired to specify extension structure (_sREQUEST_PATH_EX).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-17\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-5\nRequest\nPath\n(IOI)\n7 CIP Message Communications\n When a Standard Structure Variable Is Used\nExample: Using a standard structure variable to input values into RqPath (Request Path) for the\nCIPSend instruction\nCreate variable A with a variable with\nthe standard structure (_sREQUEST_PATH).\nRqPath data type\nCIP communications instruction\nMember Value\nCIPSend\nClassID 2\n(Class ID)\nVariable A RqPath\n(Request Path) InstanceID 3\n(Instance ID)\nisAttributeID\nTRUE\n(Attribute usage)\nAttributeID\n1\n(Attribute ID)\n1\nCreate a standard structure variable.\nTo use a standard structure variable to input values into RqPath (Request Path) for a CIP com-\nmunications instruction, first you need to create a standard structure user-defined variable.\nWhen you create a variable in a variable table, select the pre-registered standard structure\n(_sREQUEST_PATH) for a CIP communications instruction.\nVariable table\nName Data type\nA _sREQUEST_PATH\nSelect a standard structure for the data type of variable A.\n2\nInput a value for each standard structure variable member.\nInput the following values into the communications parameters that were registered as mem-\nbers of the standard structure variable.\nMOVE\nVariable name\nEN\n2 IN1 OUT1 A. ClasslD\nMOVE\nMember name of RqPath data type\nEN\n3 IN1 OUT1 A . InstancelD\nMOVE\nEN\nTRUE IN1 OUT1 A . isAttributeID\nMOVE\nEN\n1 IN1 OUT1 A . AttributelD\n7-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n When an Extension Structure Variable Is Used\nExample: Using an extension structure variable to input values into RqPath (Request Path) for the\nCIPSend instruction\nCreate variable A with a variable with\nthe extension structure (_sREQUEST_PATH_EX).\nRqPath data type\nCIP communications instruction\nMember Value\nCIPSend\nClassIDLogicalFormat _8BIT\n(Class ID logical format)\nVariable A RqPath\n(Request Path) ClassID 3\n(Class ID)\nInstanceIDLogicalFormat _16BIT\n(Instance ID logical format)\nInstanceID 256\n(Instance ID)\nisAttributeID TRUE\n(Attribute usage)\nAttributeID _8BIT\n(Attribute ID logical format)\nAttributeID\n1\n(Attribute ID)\n1\nCreate an extension structure variable.\nTo use an extension structure variable to input values into RqPath (Request Path) for a CIP\ncommunications instruction, first you need to create an extension structure user-defined varia-\nble.\nWhen you create a variable in a variable table, select the pre-registered extension structure\n(_sREQUEST_PATH_EX) for a CIP communications instruction.\nVariable table\nName Data type\nA _sREQUEST_PATH_EX\nSelect an extension structure for the data type of variable A.\n2\nInput a value for each extension structure variable member.\nInput the following values into the communications parameters that were registered as mem-\nbers of the extension structure variable.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-19\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-5\nRequest\nPath\n(IOI)\n7 CIP Message Communications\nMOVE\nVariable name\nEN\n_8BIT IN1 OUT1 A . ClassIDLogicalFormat\nMOVE\nMember name of RqPath data type\nEN\n3 IN1 OUT1 A. ClasslD\nMOVE\nEN\n_16BIT IN1 OUT1 A . InstanceIDLogicalFormat\nMOVE\nEN\n256 IN1 OUT1 A . InstancelD\nMOVE\nEN\nTRUE IN1 OUT1 A . isAttributeID\nMOVE\nEN\n_8BIT IN1 OUT1 A . AttributeIDLogicalFormat\nMOVE\nEN\n1 IN1 OUT1 A . AttributelD\n7-2-6 Service Data and Response Data\nCIP communications instructions send and receive data that is stored in array variables.\nPreparing Array Variables to Input and Output Service Data and Re-\nsponse Data\nThis section describes the array variables for storing service data and response data that CIP commu-\nnications instructions send and receive.\n Creating Array Variables\nTo input a value into the array variable of a CIP communications instruction, you must create a vari-\nable with the same configuration as the array variable in advance.\nExample: Creating a Variable to Input Data to the CIPSend Instruction Array Variables\n7-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nCIP communications instruction\nCIPSend\nVariable A ServiceDat\n(Command Data)\n(1)\nVariable B Size\n(Number of Elements)\nRespSize\n(Response Variable D\nData Size)\nResServiceDat\n(2) Variable C\n(Response Data)\n(1) Input the service data to send (2) Store received response data\nThe data to send is stored in array variable A. The data that is received is stored in variable C.\nIf only certain elements are specified in array var- The byte size of the data that was actually re-\niable A, specify the number of elements in varia- ceived is stored in variable D.\nble B.\nArray variable: A Array variable: C[0..9]\n[0] [0]\n[1]\n[1] [2]\n[2] [3]\nNumber of elements: 2 Variable D [4]\n[3] [5]\n: 10\n[6]\nIf the service data (ServiceDat) is [7]\nArray[2] and number of elements [8]\n(Size) = 2, Array[2] and Array[3] [9]\nare sent.\nUse the following procedure to create a variable in the variable table.\nSpecify the element first number, the element last number, and the data type.\nExample: UINT Array\nVariable table\nVariable name Data type\nA ARRAY[0..19] OF UINT\nSpecifies the data type.\n CIP Communications Instructions That Use Array Variables\nStructure variable name\nInstruction\nInput variable In-out variable Output variable\nCIPRead --- --- DstDat (Read Data)\nCIPWrite SrcDat (Write Data) --- ---\nCIPSend ServiceDat (Command Da- ResServiceDat (Response ---\nta) Data)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-21\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-6\nService\nData\nand\nResponse\nData\n7 CIP Message Communications\n7-2-7 Sample Programming for CIP Connectionless (UCMM) Message\nCommunications\nThis sample uses CIP UCMM messages to write a variable, read a variable, and send a message.\nThe Controllers are connected to an EtherNet/IP network. The IP address of the remote node is"}
+{"question": "168.250.2.", "answer": "The following procedure is used.\n1\nThe CIPUCMMWrite instruction is used to write the value of a variable at a remote node. The\nvariable name at the remote node is WritingDat and the contents of the WriteDat is written to it.\nWritingDat must be defined as a global variable at the remote node and the Network Publish\nattribute must be set.\n2\nThe CIPUCMMRead instruction is used to read the value of a variable at a remote node. The\nvalue of the variable OriginalDat at the other node is read and the read value is stored in the\nReadDat variable. OriginalDat must be defined as a global variable at the remote node and the\nNetwork Publish attribute must be set.\n3\nThe CIPUCMMSend instruction is used to send an explicit message to a remote node. The\ncontents of the message is to read identity information (product name). The class ID, instance\nID, attribute ID, and service code are as follows. The response data is stored in the RespDat\nvariable.\nItem Value\nClass ID 1\nInstance ID 1\nAttribute ID 7\nService Code 16#0E\nIP address: 192.168.250.2\nBuilt-in EtherNet/IP Port Built-in EtherNet/IP Port\nValue of variable written. Variable name: WritingDat\nWriteDat Global variable\nNetwork Publish attribute\nValue of variable read. Variable name: OriginalDat\nReadDat Global variable\nNetwork Publish attribute\nMessage sent to read identity\ninformation (product name).\nRespDat\nResponse\n7-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nLD\nVariable Data type Initial value Comment\nOperatingEnd BOOL False Processing\ncompleted\nTrigger BOOL False Execution con-\ndition\nOperating BOOL False Processing\nWriteDat INT 1234 Write data\nReadDat INT 0 Read data\nReqPath _sRE- (ClassID:=0, InstanceID:=0, Request path\nQUEST_PATH isAttributeID:=False, AttributeID:=0)\nRespDat ARRAY[0..10] OF [11(16#0)] Response data\nBYTE\nDummy BYTE 16#0 Dummy\nRS_instance RS\nCIPUCMMWrite_instance CIPUCMMWrite\nCIPUCMMRead_instance CIPUCMMRead\nCIPUCMMSend_instance CIPUCMMSend\nDetermine if instruction execution is completed.\nCIPUCMMWrite_instance.Done CIPUCMMRead_instance.Done CIPUCMMSend_instance.Done OperatingEnd\nCIPUCMMWrite_instance.Error\nCIPUCMMRead_instance.Error\nCIPUCMMSend_instance.Error\nAccept trigger.\nCIPUCMMWrite CIPUCMMRead CIPUCMMSend RS_instance\nTrigger _instance.Busy _instance.Busy _instance.Busy Operating\nRS\nSet Q1\nOperatingEnd Reset1\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-23\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\ntions 7-2-7\nSample\nProgramming\nfor\nCIP\nConnectionless\n(UCMM)\nMessage\nCommunica-\n7 CIP Message Communications\nExecute instructions.\nCIPUCMMWrite_instance\nOperating\nCIPUCMMWrite\nExecute Done\n‘02\\192.168.250.2’ RoutePath Busy\nUINT#20 TimeOut Error\n‘WritingDat’ DstDat ErrorID\nUINT#1 Size ErrorIDEx\nWriteDat SrcDat\nCIPUCMMRead_instance\nCIPUCMMWrite_instance.Done CIPUCMMRead\nExecute Done\n‘02\\192.168.250.2’ RoutePath Busy\nUINT#20 TimeOut Error\n‘OriginalDat’ SrcDat ErrorID\nUINT#1 Size ErrorIDEx\nDstDat\nReadDat ReadDat\nRcvSize\nCIPUCMMRead_instance.Done\n@MOVE\nEN ENO\nUINT#1 In Out ReqPath.ClassID\n@MOVE\nEN ENO\nUINT#1 In Out ReqPath.InstanceID\n@MOVE\nEN ENO\nTRUE In Out ReqPath.isAttributeID\n@MOVE\nEN ENO\nUINT#7 In Out ReqPath.AttributeID\nCIPUCMMSend_instance\nCIPUCMMSend\nExecute Done\n‘02\\192.168.250.2’ RoutePath Busy\nUINT#20 TimeOut Error\nBYTE#16#0E ServiceCode ErrorID\nReqPath RqPath ErrorIDEx\nDummy ServiceDat RespSize\nUINT#0 Size\nRespServiceDat\nRespDat RespDat\nProcessing after normal end\nInline ST\nOperating CIPUCMMSend_instance.Done\n1 // Processing after normal end\n2 ;\nProcessing after error end.\nInline ST\nOperating CIPUCMMWrite_instance.Error\n1 // Processing after error end.\n2 ;\nCIPUCMMRead_instance.Error\nCIPUCMMSend_instance.Error\n7-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nST\nInternal\nVariable Data type Initial value Comment\nvariables\nTrigger BOOL False Execution condi-\ntion\nDoUCMMTrigger BOOL False Processing\nStage INT 0 Status change\nWriteDat INT 1234 Write data\nReadDat INT 0 Read data\nReqPath _sRE- (ClassID:=0, InstanceID:=0, Request path\nQUEST_PATH isAttributeID:=False, AttributeID:=0)\nRespDat ARRAY[0..10] OF [11(16#0)] Response data\nBYTE\nDummy BYTE 16#0 Dummy\nCIPUCMMWrite_instance CIPUCMMWrite\nCIPUCMMRead_instance CIPUCMMRead\nCIPUCMMSend_instance CIPUCMMSend\nExternal\nVariable Data type Constant Comment\nvariable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1\nOnline) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port which is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE\nIF ((Trigger=TRUE) AND (DoUCMMTrigger=FALSE) AND (_EIP_EtnOnlineSta=TRU\nE))\nTHEN\nDoUCMMTrigger :=TRUE;\nStage :=INT#1;\nCIPUCMMWrite_instance(\nExecute :=FALSE, // Initialize instan\nce\nSrcDat :=WriteDat); // Dummy\nCIPUCMMRead_instance( // Initialize in\nstance\nExecute :=FALSE, // Dummy\nDstDat :=ReadDat); // Dummy\nCIPUCMMSend_instance(\nExecute :=FALSE, // Initialize instan\nce\nServiceDat :=Dummy, // Dummy\nRqpath :=ReqPath, // Dummy\nRespServiceDat :=RespDat); // Dummy\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-25\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\ntions 7-2-7\nSample\nProgramming\nfor\nCIP\nConnectionless\n(UCMM)\nMessage\nCommunica-\n7 CIP Message Communications\nEND_IF;\nIF (DoUCMMTrigger=TRUE) THEN\nCASE Stage OF\n1 : // Request writi\nng value of variable\nCIPUCMMWrite_instance(\nExecute :=TRUE,\nRoutePath :='02\\192.168.250.2', // Route path\nTimeOut :=UINT#20, // Timeout time\nDstDat :='WritingDat', // Destination variable\nname\nSize :=UINT#1, // Number of elements to\nwrite\nSrcDat :=WriteDat); // Write data\nIF (CIPUCMMWrite_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\nELSIF (CIPUCMMWrite_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Request readi\nng value of variable\nCIPUCMMRead_instance(\nExecute :=TRUE,\nRoutePath :='02\\192.168.250.2', // Route path\nTimeOut :=UINT#20, // Timeout time\nSrcDat :='OriginalDat', // Source variable name\nSize :=UINT#1, // Number of elements to\nread\nDstDat :=ReadDat); // Read data\nIF (CIPUCMMRead_instance.Done=TRUE) THEN\nStage :=INT#3; // Normal end\nELSIF (CIPUCMMRead_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\n3 : // Send message\nReqPath.ClassID :=UINT#01;\nReqPath.InstanceID :=UINT#01;\nReqPath.isAttributeID:=TRUE;\nReqPath.AttributeID :=UINT#07;\nCIPUCMMSend_instance(\nExecute :=TRUE,\nRoutePath :='02\\192.168.250.2', // Route path\nTimeOut :=UINT#20, // Timeout time\n7-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nServiceCode :=BYTE#16#0E, // Service code\nRqPath :=ReqPath, // Request path\nServiceDat :=Dummy, // Service data\nSize :=UINT#0, // Number of elements\nRespServiceDat :=RespDat); // Response data\nIF (CIPUCMMSend_instance.Done=TRUE) THEN\nStage :=INT#0; // Normal end\nELSIF (CIPUCMMSend_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n0: // Processing af\nter normal end\nDoUCMMTrigger :=FALSE;\nTrigger :=FALSE;\nELSE // Processing af\nter error end\nDoUCMMTrigger :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\n7-2-8 Sample Programming for CIP Connection (Class 3) Message\nCommunications\nThis sample uses CIP class 3 messages to write a variable, read a variable, and send a message.\nThe Controllers are connected to an EtherNet/IP network. The IP address of the remote node is"}
+{"question": "168.250.2.", "answer": "The following procedure is used.\n1\nThe CIPOpen is used to open a class 3 connection (Large_Forward_Open). The timeout time\nis 2 s.\n2\nThe CIPWrite instruction is used to write the value of a variable at a remote node. The variable\nname at the remote node is WritingDat and the contents of the WriteDat is written to it.\nWritingDat must be defined as a global variable at the remote node and the Network Publish\nattribute must be set.\n3\nThe CIPRead instruction is used to read the value of a variable at a remote node. The value of\nthe variable OriginalDat at the other node is read and the read value is stored in the ReadDat\nvariable. OriginalDat must be defined as a global variable at the remote node and the Network\nPublish attribute must be set.\n4\nThe CIPSend instruction is used to send an explicit message to a remote node. The contents\nof the message is to read identity information (product name). The class ID, instance ID, attrib-\nute ID, and service code are as follows. The response data is stored in the RespDat variable.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-27\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-8\nSample\nProgramming\nfor\nCIP\nConnection\n(Class\n3)\nMessage\nCommunications\n7 CIP Message Communications\nItem Value\nClass ID 1\nInstance ID 1\nAttribute ID 7\nService Code 16#0E\n5\nThe CIPClose instruction is used to close the class 3 connection.\nIP address: 192.168.250.2\nBuilt-in EtherNet/IP Port Built-in EtherNet/IP Port\nValue of variable written. Variable name: WritingDat\nWriteDat Global variable\nNetwork Publish attribute\nValue of variable read. Variable name: OriginalDat\nReadDat Global variable\nNetwork Publish attribute\nMessage sent to read identity\ninformation (product name).\nRespDat\nResponse\nLD\nVariable Data type Initial value Comment\nOperatingEnd BOOL False Processing com-\npleted\nTrigger BOOL False Execution condi-\ntion\nOperating BOOL False Processing\nWriteDat INT 1234 Write data\nReadDat INT 0 Read data\nReqPath _sRE- (ClassID:=0, InstanceID:=0, isAttribu- Request path\nQUEST_PATH teID:=False, AttributeID:=0)\nRespDat ARRAY[0..10] OF [11(16#0)] Response data\nBYTE\nDummy BYTE 16#0 Dummy\nRS_instance RS\nCIPOpen_instance CIPOpen\nCIPWrite_instance CIPWrite\nCIPRead_instance CIPRead\nCIPSend_instance CIPSend\nCIPClose_instance CIPClose\n7-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nDetermine if instruction execution is completed.\nCIPWrite_instance.Done CIPSend_instance.Done OperatingEnd\nCIPOpen_instance.Done CIPRead_instance.Done CIPClose_instance.Done\nCIPOpen_instance.Error\nCIPWrite_instance.Error\nCIPRead_instance.Error\nCIPSend_instance.Error\nCIPClose_instance.Error\nAccept trigger.\nCIPOpen_ CIPWrite_ CIPRead_ CIPSend_ CIPClose_ RS_instance\nTrigger instance.Busy instance.Busy instance.Busy instance.Busy instance.Busy RS Operating\nSet Q1\nOperatingEnd Reset1\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-29\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-8\nSample\nProgramming\nfor\nCIP\nConnection\n(Class\n3)\nMessage\nCommunications\n7 CIP Message Communications\nExecute instructions.\nCIPOpen_instance\nOperating\nCIPOpen\nExecute Done\n‘02\\192.168.250.2’ RoutePath Busy\nUINT#20 TimeOut Error\nErrorID\nErrorIDEx\nHandle\nCIPWrite_instance\nCIPOpen_instance.Done CIPWrite\nExecute Done\nCIPOpen_instance.Handle Handle Busy\n‘WritingDat’ DstDat Error\nUINT#1 Size ErrorID\nWriteDat SrcDat ErrorIDEx\nCIPRead_instance\nCIPWrite_instance.Done CIPRead\nExecute Done\nCIPOpen_instance.Handle Handle Busy\n‘OriginalDat’ SrcDat Error\nUINT#1 Size ErrorID\nDstDat ErrorIDEx\nReadDat ReadDat\nRcvSize\nCIPRead_instance.Done\n@MOVE\nEN ENO\nUINT#1 In Out ReqPath.ClassID\n@MOVE\nEN ENO\nUINT#1 In Out ReqPath.InstanceID\n@MOVE\nEN ENO\nTRUE In Out ReqPath.isAttributeID\n@MOVE\nEN ENO\nUINT#7 In Out ReqPath.AttributeID\nCIPSend_instance\nCIPSend\nExecute Done\nCIPOpen_instance.Handle Handle Busy\nBYTE#16#0E ServiceCode ErrorID\nReqPath RqPath ErrorIDEx\nDummy ServiceDat RespSize\nUINT#0 Size RespSize\nRespServiceDat\nRespDat RespDat\nCIPClose_instance\nCIPSend_instance.Done CIPClose\nExecute Done\nCIPOpen_instance.Handle Handle Busy\nError\nErrorID\nErrorIDEx\n7-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nProcessing after normal end\nInline ST\nOperating CIPClose_instance.Done\n1 // Processing after normal end\n2 ;\nProcessing after error end.\nInline ST\nOperating CIPOpen_instance.Error\n1 // Processing after error end.\n2 ;\nCIPWrite_instance.Error\nCIPRead_instance.Error\nCIPSend_instance.Error\nCIPClose_instance.Error\nST\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nTrigger BOOL False Execution con-\ndition\nDoCIPTrigger BOOL False Processing\nStage INT 0 Status change\nWriteDat INT 1234 Write data\nReadDat INT 0 Read data\nReqPath _sRE- (ClassID:=0, InstanceID:=0, Request path\nQUEST_PATH isAttributeID:=False, Attribu-\nteID:=0)\nRespDat ARRAY[0..10] [11(16#0)] Response data\nOF BYTE\nDummy BYTE 16#0 Dummy\nCIPOpen_instance CIPOpen\nCIPWrite_instance CIPWrite\nCIPRead_instance CIPRead\nCIPSend_instance CIPSend\nCIPClose_instance CIPClose\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-31\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-8\nSample\nProgramming\nfor\nCIP\nConnection\n(Class\n3)\nMessage\nCommunications\n7 CIP Message Communications\nExternal\nVariable Data type Constant Comment\nvariable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnli-\nneSta (Port1 Online) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port\nwhich is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE\nIF ((Trigger=TRUE) AND (DoCIPTrigger=FALSE) AND (_EIP_EtnOnlineSta=TRUE))THEN\nDoCIPTrigger :=TRUE;\nStage :=INT#1;\nCIPOpen_instance(Execute:=FALSE); // Initialize instance\nCIPWrite_instance(\nExecute :=FALSE, // Initialize instance\nSrcDat :=WriteDat); // Dummy\nCIPRead_instance( // Initialize instance\nExecute :=FALSE, // Dummy\nDstDat :=ReadDat); // Dummy\nCIPSend_instance(\nExecute :=FALSE, // Initialize instance\nServiceDat := Dummy, // Dummy\nRespServiceDat :=RespDat); // Dummy\nCIPClose_instance(Execute:=FALSE); // Initialize instance\nEND_IF;\nIF (DoCIPTrigger=TRUE) THEN\nCASE Stage OF\n1 : // Open CIP Class 3 Connection (\nLarge_Forward_Open)\nCIPOpen_instance(\nExecute :=TRUE,\nTimeOut :=UINT#20, // Timeout time: 2.0 s\nRoutePath :='02\\192.168.250.2'); // Route path\nIF (CIPOpen_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\nELSIF (CIPOpen_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Request writing value\nof variable\nCIPWrite_instance(\nExecute :=TRUE,\nHandle :=CIPOpen_instance.Handle, // Handle\nDstDat :='WritingDat', // Destination variable\n7-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nname\nSize :=UINT#1, // Number of elements to\nwrite\nSrcDat :=WriteDat); // Write data\nIF (CIPWrite_instance.Done=TRUE) THEN\nStage :=INT#3; // Normal end\nELSIF (CIPWrite_instance.Error=TRUE) THEN\nStage :=INT#20; // Error end\nEND_IF;\n3 : // Request reading value\nof variable\nCIPRead_instance(\nExecute :=TRUE,\nHandle :=CIPOpen_instance.Handle, // Handle\nSrcDat :='OriginalDat', // Source variable name\nSize :=UINT#1, // Number of elements to\nread\nDstDat :=ReadDat); // Read data\nIF (CIPRead_instance.Done=TRUE) THEN\nStage :=INT#4; // Normal end\nELSIF (CIPRead_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n4 : // Send message\nReqPath.ClassID :=UINT#01;\nReqPath.InstanceID :=UINT#01;\nReqPath.isAttributeID:=TRUE;\nReqPath.AttributeID :=UINT#07;\nCIPSend_instance(\nExecute :=TRUE,\nHandle :=CIPOpen_instance.Handle, // Handle\nServiceCode :=BYTE#16#0E, // Service code\nRqPath :=ReqPath, // Request path\nServiceDat :=Dummy, // Service data\nSize :=UINT#0, // Number of elements\nRespServiceDat :=RespDat); // Response data\nIF (CIPSend_instance.Done=TRUE) THEN\nStage :=INT#5; // Normal end\nELSIF (CIPSend_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-33\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-8\nSample\nProgramming\nfor\nCIP\nConnection\n(Class\n3)\nMessage\nCommunications\n7 CIP Message Communications\n5 : // Request closing CIP c\nlass 3 connection\nCIPClose_instance(\nExecute :=TRUE,\nHandle :=CIPOpen_instance.Handle); // Handle\nIF (CIPClose_instance.Done=TRUE) THEN\nStage :=INT#0;\nELSIF (CIPClose_instance.Error=TRUE) THEN\nStage :=INT#50;\nEND_IF;\n0: // Processing after norm\nal end\nDoCIPTrigger :=FALSE;\nTrigger :=FALSE;\nELSE // Processing after erro\nr end\nDoCIPTrigger :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\n7-2-9 Operation Timing\nOutput Variable Operation and Timing\nYou can monitor the values of the output variables to determine the status throughout instruction exe-\ncution.\nThe following timing chart shows the operation of the output variables.\n(3) (4) (5) (8)\nExecute\n(1)\nBusy\n(Executing)\nChanges to FALSE\nbecause Execute\nchanges to FALSE.\nDone Changes to FALSE\nbecause Execute\nchanges to FALSE.\nError\n(6)\n(2) (7)\nErrorID 0x0000 0x1234\n7-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications"}
+{"question": "After the results of instruction execution are stored in the output variables, Done changes to TRUE", "answer": "and Busy changes to FALSE."}
+{"question": "If an error occurs, several retries are attempted internally. The error code in ErrorID is not updated", "answer": "during the retries."}
+{"question": "When a communications error occurs, Error changes to TRUE and the value of ErrorID is stored.", "answer": "Also, Busy and Done change to FALSE."}
+{"question": "When Execute changes to FALSE, Error changes to FALSE.", "answer": "Precautions for Correct Use\nIf Execute changes back to FALSE before Done changes to TRUE, Done stays TRUE for only\none task period. (Example 1)\nIf you want to see if Done is TRUE at any time, make sure to keep Execute TRUE until you\nconfirm that Done is TRUE.\nIf Execute is TRUE until Done changes to TRUE, Done stays TRUE until Execute changes to\nFALSE. (Example 2)\nExample 1 Example 2\nExecute Execute When Execute\nChanges to changes to\nFALSE in next Busy FALSE, Done\nBusy task period. (Executing) returns to FALSE.\n(Executing)\nDone Done\n7-2-10 Response Codes\nThis section describes the response codes stored in the ErrorIDEx output variable if an error occurs\nduring execution of a CIP message communications instruction.\nGeneral Status Codes\nAs response codes, general codes are stored in the ErrorIDEx output variable (DWORD data) after\nexecution of a CIP communications instruction is completed.\nIf an additional code is added, the additional code is also stored.\nGeneral status code (1 byte)\n31 24 23 16 15 0\nErrorIDEx\nAdditional code (1 word)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-35\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-10\nResponse\nCodes\n7 CIP Message Communications\nGeneral\nstatus Status name Description of status\ncode (hex)\n00 Success Service was successfully performed by the object specified.\n01 Connection failure A connection related to service failed along the connection path.\n02 Resource unavailable Resources needed for the object to perform the requested service\nwere unavailable.\n03 Invalid parameter value See Status Code 20 hex.\n04 Path segment error The path segment identifier or the segment syntax was not under-\nstood by the processing node. Path processing stops when a path\nsegment error occurs.\n05 Path destination unknown The path is referencing an object class, instance, or structure ele-\nment that is not known or is not contained in the processing node.\nPath processing stops when a Path Destination Unknown Error oc-\ncurs.\n06 Partial transfer Only part of the expected data was transferred.\n07 Connection lost The message connection was lost.\n08 Service not supported The requested service was not supported or was not defined for this\nobject class/instance.\n09 Invalid attribute value Invalid attribute data was detected.\n0A Attribute list error An attribute in the Get_Attribute_List or Set_Attribute_List response\nhas a non-zero status.\n0B Already in requested The object is already in the mode/state being requested by the serv-\nmode/state ice.\n0C Object state conflict The object cannot perform the requested service in its current mode/\nstate.\n0D Object already exists The requested instance of object to be created already exists.\n0E Attribute not settable A request to modify a non-modifiable attribute was received.\n0F Privilege violation A permission/privilege check failed.\n10 Device state conflict The device's current mode/state prohibits the execution of the re-\nquested service.\n11 Reply data too large The data to be transmitted in the response buffer is larger than the\nallocated response buffer.\n12 Fragmentation of a primi- The service specified an operation that is going to fragment a primi-\ntive value tive data value, i.e. half a REAL data type.\n13 Not enough data The requested service did not supply enough data to perform the\nspecified operation.\n14 Attribute not supported The attribute specified in the request is not supported.\n15 Too much data The service supplied more data than was expected.\n16 Object does not exist An object that does not exist was specified for the requested serv-\nice.\n17 Service fragmentation se- The fragmentation sequence for this service is not currently active\nquence not in progress for this data.\n18 No stored attribute data The attribute data of this object was not saved prior to the requested\nservice.\n19 Store operation failure The attribute data of this object was not saved due to a failure dur-\ning the attempt.\n1A Routing failure (request The service request packet was too large for transmission on a net-\npacket too large) work in the path to the destination. The routing device was forced to\nabort the service.\n7-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nGeneral\nstatus Status name Description of status\ncode (hex)\n1B Routing failure (response The service response packet was too large for transmission on a\npacket too large) network in the path from the destination. The routing device was\nforced to abort the service.\n1C Missing attribute list entry The service did not supply an attribute in a list of attributes that was\ndata needed by the service to perform the requested behavior.\n1D Invalid attribute value list The service is returning the list of attributes supplied with status in-\nformation for those attributes that were invalid.\n1E Embedded service error An embedded service resulted in an error.\n1F Vendor specific error A vendor-specific error occurred. The Additional Code Field of the\nerror response defines the error. This is a general error code that is\nused only for errors that do not correspond to any of the error codes\nin this table and are not in an object class definition.\n20 Invalid parameter A parameter for the requested service is invalid. This code is used\nwhen a parameter does not meet the requirements of the specifica-\ntion and/or the requirements defined in an application object specifi-\ncation.\n21 Write-once value or medi- An attempt was made to write to a write-once medium (e.g. WORM\num already written drive or PROM) that was previously written or cannot be changed.\n22 Invalid Reply Received An invalid reply was received. (For example, the reply service code\ndoes not match the request service code. Or, the reply message is\nshorter than the minimum expected reply size.) This status code is\nused for other causes of invalid replies.\n23-24 Reserved by CIP for future extensions.\n25 Key Failure in path The key segment that was included as the first segment in the path\ndoes not match the destination module. The object specific status\nmust indicate which part of the key check failed.\n26 Path Size Invalid The size of the path that was sent with the service request is either\ntoo large or too small for the request to be routed to an object.\n27 Unexpected attribute in list An attempt was made to set an attribute that is not able to be set at\nthis time.\n28 Invalid Member ID The member ID specified in the request does not exist in the speci-\nfied class, instance, and attribute.\n29 Member not settable A request to modify a non-modifiable member was received.\n2A Group 2 only server gen- This error code is reported only by group 2 only servers with 4K or\neral failure less of code space and only in place of Service not supported,\nAttribute not supported, or Attribute not settable.\n2B-CF Reserved by CIP for future extensions.\nD0-FF Reserved for Object Class This range of error codes is to be used to indicate object class-spe-\nand service errors cific errors. This code range is used only when none of the error co-\ndes in this table accurately reflect the error that occurred. The addi-\ntional code field is used to describe the general error code in more\ndetail.\n Examples of Additional Status When General Status Is 01 hex (Status of\nConnection Manager Object)\nGeneral Additional\nStatus Status Description\n(hex) (hex)\n01 0100 Connection in use or duplicate forward open.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-37\n7-2\nClient\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-2-10\nResponse\nCodes\n7 CIP Message Communications\nGeneral Additional\nStatus Status Description\n(hex) (hex)\n01 0103 Transport class and trigger combination not supported.\n01 0106 Ownership conflict.\n01 0107 Connection not found at target application.\n01 0108 Invalid connection type. There is a problem with either the connection type or\npriority of the connection.\n01 0109 Invalid connection size.\n01 0110 Device not configured.\n01 0111 RPI not supported. May also indicate problem with connection time-out multi-\nplier, or production inhibit time.\n01 0113 Connection Manager cannot support any more connections.\n01 0114 Either the vendor ID or the product code in the key segment does not match\nthe device.\n01 0115 Device type in the key segment does not match the device.\n01 0116 Major Revision or Minor Revision in the key segment.\n01 0117 Invalid connection point.\n01 0118 Invalid configuration format.\n01 0119 Connection request failed because there is no controlling connection currently\nopen.\n01 011A Target application cannot support any more connections.\n01 011B RPI is smaller than the production inhibit time.\n01 0127 Invalid originator to target network connection size\n01 0128 Invalid target to originator network connection size\n01 0203 Connection cannot be closed because the connection has timed out.\n01 0204 Unconnected_Send service timed out while waiting for a response.\n01 0205 Parameter error in Unconnected_Send service.\n01 0206 Message too large for unconnected message service.\n01 0207 Unconnected acknowledgment without reply.\n01 0301 No buffer memory available.\n01 0302 Network bandwidth not available for data.\n01 0303 No tag filters available.\n01 0304 Not configured to send real-time data.\n01 0311 Port that was specified in port segment is not available.\n01 0312 Link address that was specified in port segment is not available.\n01 0315 Invalid segment type or segment value in path.\n01 0316 Path and connection were not equal when closing the connection.\n01 0317 The segment is not present. Or, the encoded value in the network segment is\ninvalid.\n01 0318 Link address to self is invalid.\n01 0319 Resources on secondary are unavailable.\n01 031A Connection is already established.\n01 031B Direct connection is already established.\n01 031C Others\n01 031D Redundant connection mismatch.\n01 031E There are no more reception resources available on the sending module.\n01 031F No connection resources exist for the target path.\n01 0320-07FF Vendor specific.\n7-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n7-3 Server Function of CIP Message\nCommunications\nAfter the NJ/NX-series Controller receives the CIP messages from external devices, this function exe-\ncutes services for a specified self-contained object in the CPU Unit.\nThis is called the server function of CIP message communications.\nThis section provides information on CIP messages structure along with information about how to use\nCIP messages in a program that runs on a computer or by other means and uses the server function\nof CIP message communications to perform the following: -Writing CIP objects and the values of varia-\nbles to the NJ/NX-series Controller, -Reading CIP objects and the values of variables from the NJ/NX-\nseries Controller.\nTo read and write CIP objects or the values of variables between NJ/NX-series Controllers, use the\nCIP communications instructions.\nRefer to 7-2 Client Function of CIP Message Communications on page 7-4 for information on how to\nuse CIP communications instructions for CIP message communications.\nComputer\nRequest\nThe variable to access\nis specified in the\nrequest path of the\nCIP object or the Response\nexplicit message\nto read or write data. The writing results of the\nspecified CIP object or\nvariable, or the value that was\nNJ/NX-series Controller read from the specified CIP NJ/NX-series Controller\nobject or variable are stored\nin the response.\nVariable Variable\nYou can read and write variables with\nCIP communications instructions.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-39\n7-3\nServer\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-3-1\nCIP\nMessage\nStructure\nfor\nAccessing\nCIP\nObjects\n7 CIP Message Communications\nPrecautions for Correct Use\n• To allow the Controller to receive CIP messages, select the Use Option for the CIP message\nserver of the built-in EtherNet/IP port. If the Do not use Option for the CIP message server is\nselected, the Controller cannot receive CIP messages. For the details on the settings, refer to\nCIP Message Server on page 4-21.\n• If the Use Option is selected for Packet Filter of the built-in EtherNet/IP port, make sure to\npermit packets to be used for CIP messages. If they are not permitted, the CIP message can-\nnot be received. For the details on the settings, refer to Packet Filter on page 4-8.\n• If the Do not use Option for the CIP message server is selected, EtherNet/IP communica-\ntions cannot be used. This causes the following restrictions on the functionality of connected\ndevices, tools, and Controllers.\nCategory Restrictions\nConnect- • The programmable terminal NS-series cannot be connected.\ned device\nTools • Sysmac Studio cannot go online through Remote connection via USB.\n• Tag data link setting using Sysmac Studio is not possible.\n• CX-Compolet and SYSMAC Gateway cannot be connected.\n• CNC Operator cannot be connected.\n• Network Configurator cannot be connected. Or, devices cannot be displayed.\n• CX-Configurator FDT (communication DTM OMRON EtherNet/IP) cannot be connect-\ned.\n• Sysmac Conrtoller Log Upload Tool cannot be connected to the Controller through\nRemote connection via USB.\nController • The tag data link function cannot be used.\nfeatures • CIP Safety communications cannot be used with a configuration in which an NX-SL5£\n££ is connected to the CPU Unit.\n• The server function of CIP messages (UCMM, Class 3) in the built-in EtherNet/IP port\ncannot be used.\nAdditional Information\n• Selecting the Do not use Option for the CIP message server closes the TCP/UDP ports used\nfor EtherNet/IP communications. This improves security of communications over the network.\n• Even if the Do not use Option for the CIP message server is selected, the TCP/UDP mes-\nsage services can be used. You can also use the client function (CIP communications instruc-\ntions) of CIP message communications.\nVersion Information\nThe CIP message server settings can be used with the following unit versions of the CPU Unit.\n• NJ-series, NX102, NX1P2 CPU Unit: Version 1.49 or later\n• NX701 CPU Unit: Version 1.29 or later\n• NX502 CPU Unit: Version 1.60 or later\n7-3-1 CIP Message Structure for Accessing CIP Objects\nThis section shows how to specify messages to access CIP objects.\nThe CIP objects to be accessed are expressed by connecting the segments\ndefined in the CIP Common Specifications in the request path field in a CIP explicit message.\n7-40 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nExample: Performing the Reset service (0x05) to the Instance (01 hex) of the Identity object (class: 01\nhex)\nCIP Explicit Message (Request)\nRequest Path Request\nService Service\nRequest\nCode Path Length [1] [2] Data\n(20 01) (24 01)\n(0x05) (num of\n(02)\nelem)\nLogical Segment Logical Segment\n(Class ID) (Instance ID)\nSpecify the service Specify the Class ID and Specify the Request Data\ncode to perform. (*1) Instance ID to access. according to the service.\n*1. Refer to 7-5 CIP Object Services on page 7-48 for information about the service codes.\n7-3-2 CIP Message Structure for Accessing Variables\nThis section shows how to specify messages to access variables.\nThe variables to access are given by connecting the segments that are defined in the CIP Common\nspecifications so that explicit message can be set in the request path field.\nThe following elements are combined to make the specification.\nSpecifying the variable to access: The elements are stored in the CIP segments and then joined to\nmake the message.\nExample: Reading the Present Value of One Member of the VarAA.MemB[1.2] Structure Variable\nExample for Using the CIP Read Data Service for a Variable Object\nCIP Explicit Message for a Request\nRequest Path Request\nService Service\nRequest\nCode Path Length “VarAA” “MemB” [1] [2] Data\n(91 05 56 61 72 41 41 00) (91 04 4D 65 6D 42) (28 01) (28 02)\n(4C hex) (num of\n(09)\nelem)\nANSI Extended Symbol Segment Logical Segment\n(Member ID)\nSpecify the service code to perform Specify the variable name and Specify the data format to read\nreading and writing variables. (*1) range to access. (*2) and write. (*3)\n*1. Refer to 7-6 Read and Write Services for Variables on page 7-85 for information about the service codes.\n*2. Refer to 7-4-5 Specifying Variable Names in Request Paths on page 7-44 for information about how to speci-\nfy variables names.\n*3. Refer to 7-7 Variable Data Types on page 7-89 for details about how to specify data formats.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-41\n7-3\nServer\nFunction\nof\nCIP\nMessage\nCommunications\n7\n7-3-2\nCIP\nMessage\nStructure\nfor\nAccessing\nVariables\n7 CIP Message Communications\n7-4 Specifying Request Path\nThe CIP object, variable name, structure member name, and array index are specified in the request\npath.\nIn CIP, the EPATH data type is used for the request path.\nWith this method, the request path is divided into segments and a value is assigned to each segment.\nThe request path notation shows the path to the final destination when the data segments are joined\ntogether.\nEach segment includes the segment type information and the segment data.\nSegment 1 Segment 2 Segment 3 Segment 4\nThe first byte gives the interpretation method for the segment. It consists of two parts; a 3-bit segment\ntype and a 5-bit segment format.\nSegment Type Segment Format\n7 6 5 4 3 2 1 0\nThe segment type specifications are defined as follows in the CIP specifications.\nSegment Type\nMeaning\n7 6 5\n0 0 0 Port Segment\n0 0 1 Logical Segment\n0 1 0 Network Segment\n0 1 1 Symbolic Segment\n1 0 0 Data Segment\n1 0 1 Data Type\n1 1 0 Data Type\n1 1 1 Reserved\nThe specifications for the segment format are different for each segment type. Use the segment format\nto request a service from a particular object of a particular device.\nLogical segments and data segments, which are needed to specify variables in CIP message commu-\nnications, are described below.\n7-4-1 Examples of CIP Object Specifications\nLogical Segments are joined to form the request path that specifies the object to access.\nLogical Segment Logical Segment Logical Segment\n(Class ID) (Instance ID) (Attribute ID)\nSpecify the Class ID. Specify the Instance ID. Specify the Attribute ID.\n7-42 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n7-4-2 Examples of Variable Specifications\nSegments are joined to form the request path that specifies the variable to access.\nData Segment Logical Segment\n(ANSI Extended Symbol Segment) (Member ID)\nSpecify the variable name and Specify the array index.\nthe member name.\n7-4-3 Logical Segment\nA logical segment is used to give the range of the CIP Object or variable (array) in the request path.\nSegment Format Bits\nSegment Type Logical Type Logical Format\n7 6 5 4 3 2 1 0\n0 0 1\nLogical Type\nMeaning\n4 3 2\n0 0 0 Class ID\n0 0 1 Instance ID\n0 1 0 Member ID\n0 1 1 Connection Point\n1 0 0 Attribute ID\n1 0 1 Special (Do not use the logical addressing definition for the Logical Format.)\n1 1 0 Service ID (Do not use the logical addressing definition for the Logical Format.)\n1 1 1 Reserved\nLogical\nFormat Meaning\n1 0\n0 0 8 bit logical address\n0 1 16 bit logical address\n1 0 32 bit logical address\n1 1 Reserved\nAn 8-bit or 16-bit logical address can be used for the class ID and attribute ID.\nAn 8-bit,16-bit, or 32-bit logical address can be used for the instance ID.\n7-4-4 Data Segment\nA data segment is used to give the specified variable name in the request path.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-43\n7-4\nSpecifying\nRequest\nPath\n7\n7-4-2\nExamples\nof\nVariable\nSpecifications\n7 CIP Message Communications\nSSSSSSeeeeeeggggggmmmmmmeeeeeennnnnntttttt TTTTTTyyyyyyppppppeeeeee SSSSSSSSSSSSSeeeeeeeeeeeeegggggggggggggmmmmmmmmmmmmmeeeeeeeeeeeeennnnnnnnnnnnnttttttttttttt SSSSSSSSSSSSSuuuuuuuuuuuuubbbbbbbbbbbbb-------------TTTTTTTTTTTTTyyyyyyyyyyyyypppppppppppppeeeeeeeeeeeee DDDDDDDDDDDaaaaaaaaaaatttttttttttaaaaaaaaaaa SSSSSSSSSSSeeeeeeeeeeegggggggggggmmmmmmmmmmmeeeeeeeeeeennnnnnnnnnnttttttttttt DDDDDDDDDDDaaaaaaaaaaatttttttttttaaaaaaaaaaa\n77 66 55 44 33 22 111 000\n111 000 000 VVVVVVVVVVVVVVVaaaaaaaaaaaaaaarrrrrrrrrrrrrrriiiiiiiiiiiiiiiaaaaaaaaaaaaaaabbbbbbbbbbbbbbbllllllllllllllleeeeeeeeeeeeeee llllllllllllllleeeeeeeeeeeeeeennnnnnnnnnnnnnngggggggggggggggttttttttttttttthhhhhhhhhhhhhhh\nSegment Sub-Type\nMeaning\n4 3 2 1 0\n0 0 0 0 0 Simple Data Segment\n1 0 0 0 1 ANSI Extended Symbol Segment\nA data segment is mainly used for an ANSI extended symbol segment.\nThis segment sub-type is used to read and write the values of variables.\nANSI Extended Symbol Segment\nSegment Type Segment Sub Type Symbol Size\n7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0\n1 0 0 1 0 0 0 1\nSymbol (ANSI) Symbol (ANSI)\n7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0\n7-4-5 Specifying Variable Names in Request Paths\nVariable Names\nA variable name is specified as a symbolic segment (ANSI extended symbol segment).\nVariable Name Specification Format\nBYTE 91 hex ANSI Extended Symbol Segment\nBYTE Length in BYTE Length of variable name in bytes\nArray of : Variable name encoded in UTF-8\noctet Variable_name\n:\nOctet (pad) 00 hex. One byte is padded if the variable\nname length is an odd number of bytes.\nVariable Names\nVariable names are encoded in UTF-8.\n7-44 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nStructure Member Names\nStructure member names are specified in the same way as variable names.\nStore UTF-8 character codes in the ANSI extended symbol segment.\nArray Indices\nSpecify the array index in a logical segment that is set as a member ID.\nYou can specify an array index ([x]) in a variable name.\n(Specification Method 1: 8-bit Index)\nBYTE 28 hex Logical Segment (Member ID)\nUSINT Index Array index from 0 to 255\n(Specification Method 2: 16-bit Index)\nBYTE 29 hex Logical Segment (Member ID)\noctet 00 hex Pad\nUINT Index (L) Array index from 0 to 65,535\n(H)\nRange Specifications with the Num of Element Field\nThere is a Num of Element field in the request data for the variable read and variable write services.\nYou can use these services to access the specified range of an array with the following specifications.\n• Specify the first element in the range of elements to access in the array variable as the variable to\nread or write.\n• Specify the number of elements to access in the Num of Element field.\nSpecification Examples\nThis example shows how to specify VarAA.MemB[1.2] for the following structure variable.\nstruct\n{\nUINT MemA;\nBOOL MemB[10][10];\n} VarAA;\nVariable Name Specification Format\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-45\n7-4\nSpecifying\nRequest\nPath\n7\n7-4-5\nSpecifying\nVariable\nNames\nin\nRequest\nPaths\n7 CIP Message Communications\nBYTE 91 hex ANSI Extended Symbol Segment\nBYTE 05 hex Length of variable name in bytes\nArray of 'V' Variable name\noctet 'a'\n'r'\n'A'\n'A'\nOctet 00 hex Pad\nBYTE 91 hex ANSI Extended Symbol Segment\nBYTE 04 hex Length of variable name in bytes\nArray of 'M' Variable name\noctet 'e'\n'm'\n'B'\nBYTE 28 hex Logical Segment (Member ID)\nUSINT 01 hex Array index for the first element\nBYTE 28 hex Logical Segment (Member ID)\nUSINT 02 hex Array index for the second element\nThe variable name that is specified in the symbolic segment (ANSI extended symbol segment) must\nbe converted to a text string to pass it to the communications thread. The following conversion rules\napply.\nSpecification Example for Structure Members and Array Elements\n0x91 0x05“VarAA”0x00 0x91 0x04“MemB” 0x28 0x01 0x28 0x02\nVVAarRA:A//V.maerAmAB.m[1e.2m] b er[1][2]\nThis example shows how to specify VarAA[1].MemB[1.2] for the following structure variable.\nstruct\n{\nUINT MemA;\nBOOL MemB[10][10];\n} VarAA[3]\nVariable Name Specification Format\n7-46 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nBYTE 91 hex ANSI Extended Symbol Segment\nBYTE 05 hex Length of variable name in bytes\nArray of 'V' Variable name\noctet 'a'\n'r'\n'A'\n'A'\nOctet 00 hex Pad\nBYTE 28 hex Logical Segment (Member ID)\nUSINT 01 hex Array index\nBYTE 91 hex ANSI Extended Symbol Segment\nBYTE 04 hex Length of variable name in bytes\nArray of 'M' Variable name\noctet 'e'\n'm'\n'B'\nBYTE 28 hex Logical Segment (Member ID)\nUSINT 01 hex Array index for the first element\nBYTE 28 hex Logical Segment (Member ID)\nUSINT 02 hex Array index for the second element\nSpecification Example for Structure Array\n0x91 0x05 “VarAA” 0x00 0x28 0x01 0x91 0x04 “MemB” 0x28 0x01 0x28 0x02\nVVaArRA:A//[V1a].rmAAem.mBe[m1.b2e] r[1][2]\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-47\n7-4\nSpecifying\nRequest\nPath\n7\n7-4-5\nSpecifying\nVariable\nNames\nin\nRequest\nPaths\n7 CIP Message Communications\n7-5 CIP Object Services\nThis section shows services that specify the CIP object in the Request Path and access the CIP mes-\nsage server function of the NJ/NX-series Controllers.\n7-5-1 CIP Objects Sent to the Built-in EtherNet/IP Port\nThe following CIP objects can be sent to an EtherNet/IP port.\nObject name Function Reference\nIdentity object • Reads ID information from the CPU Unit. page 7-48\n• Resets the built-in EtherNet/IP port.\nNX Configuration object • Reads and Writes NX object. page 7-53\n• Restarts the NX Unit and initializes the Unit opera-\ntion settings.\n• Saves the parameters of the NX Unit and switches\nthe write mode.\n• Obtains the current errors of the Controller and NX\nUnit, and obtains and clears an event log.\n• Obtains the user-defined errors of the Controller.\nTCP/IP Interface object • Writes and reads TCP/IP settings. page 7-74\nEthernet Link object • Reads Ethernet settings. page 7-77\n• Reads Ethernet status.\nController object • Gets the Controller status. page 7-83\n• Changes the operating mode of the Controller.\n7-5-2 Identity Object (Class ID: 01 hex)\nThis object reads the ID information of the CPU Unit and resets the built-in EtherNet/IP port.\nWhen using an NX701 CPU Unit, NX502 CPU Unit, or NX102 CPU Unit, use the route path to specify\nthe port number (1 or 2) of the built-in EtherNet/IP port to access.\nService Codes\nSpecify the service to execute with the service code.\nSupported serv-\nService ices\nParameter name Description\ncode Instan-\nClasses\nces\n01 hex Get_Attribute_All Reads the values of the attributes. Support- Support-\ned ed\n0E hex Get_Attribute_Single Reads the value of the specified attribute. Support- Support-\ned ed\n7-48 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nSupported serv-\nService ices\nParameter name Description\ncode Instan-\nClasses\nces\n05 hex Reset Resets the built-in EtherNet/IP port.\nThis parameter is used to reset the built-in EtherNet/IP port\nwhen you change the IP address or other parameter settings\nand want to apply them.\nNot sup- Support-\nInput one of the following values for the ServiceDat input vari-\nported ed\nable to the CIPSend instruction to specify the reset method.\n00 hex: Resets the built-in EtherNet/IP port.\n02 hex*1: Clears the saved tag data link settings and resets\nthe built-in EtherNet/IP port.\n*1. The value is 01 hex for a CPU Unit with unit version 1.09 or earlier.\nClass ID\nSpecify 01 hex.\nInstance ID\nSpecify 00 or 01 hex.\nAttribute ID\nThe attribute ID specifies the information to read.\n Class Attribute ID\nThe class attribute ID specifies the attribute of the entire object.\nRead data\nAttrib-\nAttribute ID Parameter name Description Data\nute Value\ntype\n01 hex Revision Revision of the object Read UINT 0001 hex\n02 hex Max Instance The maximum instance num- Read UINT 0001 hex\nber\n Instance Attribute ID\nThe instance attribute ID specifies the attribute of the instance.\nRead data\nAttribute ID Parameter name Description Attribute Data\nValue\ntype\n01 hex Vendor ID Vendor ID Read UINT 002F hex\n02 hex Device Type Device type Read UINT 000C hex\n03 hex Product Code Product code Read UINT Refer to (1) Product Codes\nfor Each Model, below.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-49\n7-5\nCIP\nObject\nServices\n7\n7-5-2\nIdentity\nObject\n(Class\nID:\n01\nhex)\n7 CIP Message Communications\nRead data\nAttribute ID Parameter name Description Attribute Data\nValue\ntype\n04 hex Revision Device revision Read Struct ---\nMajor Revision Major revision Read USINT Refer to (2) Major and Minor\nMinor Revision Minor revision Read USINT CIP Revisions, below.\n05 hex Status Status of the built-in Ether- Read WORD Refer to (3) Status Details of\nNet/IP port the Built-in EtherNet/IP Port,\nbelow.\n06 hex Serial Number Serial number Read UDINT Set value\n07 hex Product Name Product name Read STRIN Refer to (1) Product Names\nG for Each Model, below."}
+{"question": "Product Codes and Product Names for Each Model", "answer": "Product\nModel Product Name\nCode\nNX701-1600 067D hex 4E583730312D31363030 Hex\nNX701-1620 4E583730312D31363230 Hex\nNX701-1700 4E583730312D31373030 Hex\nNX701-1720 4E583730312D31373230 Hex\nNX701-Z600 4E583730312D5A363030 Hex\nNX701-Z700 4E583730312D5A373030 Hex\nNX502-1300 0BF5 hex 4E583530322D31333030 Hex\nNX502-1400 0BF6 hex 4E583530322D31343030 Hex\nNX502-1500 0BF7 hex 4E583530322D31353030 Hex\nNX502-1600 0C00 hex 4E583530322D31363030 Hex\nNX502-1700 0C01 hex 4E583530322D31373030 Hex\nNX102-1200 0BBB hex 4E583130322D31323030 Hex\nNX102-1100 0BBA hex 4E583130322D31313030 Hex\nNX102-1000 0BB9 hex 4E583130322D31303030 Hex\nNX102-9000 0BB8 hex 4E583130322D39303030 Hex\nNX102-1220 0BBF hex 4E583130322D31323230 Hex\nNX102-1120 0BBE hex 4E583130322D31313230 Hex\nNX102-1020 0BBD hex 4E583130322D31303230 Hex\nNX102-9020 0BBC hex 4E583130322D39303230 Hex\nNX1P2-9B24DT 068B hex 4E583150322D394232344454 Hex\nNX1P2-9B24DT1 4E583150322D39423234445431 Hex\nNX1P2-9B40DT 4E583150322D394234304454 Hex\nNX1P2-9B40DT1 4E583150322D39423430445431 Hex\nNX1P2-9024DT 4E583150322D393032344454 Hex\nNX1P2-9024DT1 4E583150322D39303234445431 Hex\nNX1P2-1040DT 4E583150322D313034304454 Hex\nNX1P2-1040DT1 4E583150322D31303430445431 Hex\nNX1P2-1140DT 4E583150322D313134304454 Hex\nNX1P2-1140DT1 4E583150322D31313430445431 Hex\nNJ501-1300 0665 hex 4E4A3530312D31333030 Hex\nNJ501-1320 4E4A3530312D31333230 Hex\nNJ501-1340 4E4A3530312D31333430 Hex\n7-50 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nProduct\nModel Product Name\nCode\nNJ501-1400 0666 hex 4E4A3530312D31343030 Hex\nNJ501-1420 4E4A3530312D31343230 Hex\nNJ501-1500 0667 hex 4E4A3530312D31353030 Hex\nNJ501-1520 4E4A3530312D31353230 Hex\nNJ501-4300 066E hex 4E4A3530312D34333030 Hex\nNJ501-4310 4E4A3530312D34333130 Hex\nNJ501-4320 4E4A3530312D34333230 Hex\nNJ501-4400 066F hex 4E4A3530312D34343030 Hex\nNJ501-4500 0670 hex 4E4A3530312D34353030 Hex\nNJ501-5300 068C hex 4E4A3530312D35333030 Hex\nNJ501-R300 069C hex 4E4A3530312D52333030 Hex\nNJ501-R400 069D hex 4E4A3530312D52343030 Hex\nNJ501-R500 069E hex 4E4A3530312D52353030 Hex\nNJ501-R320 069F hex 4E4A3530312D52333230 Hex\nNJ501-R420 06A0 hex 4E4A3530312D52343230 Hex\nNJ501-R520 06A1 hex 4E4A3530312D52353230 Hex\nNJ301-1100 066B hex 4E4A3330312D31313030 Hex\nNJ301-1200 066C hex 4E4A3330312D31323030 Hex\nNJ101-9000 0680 hex 4E4A3130312D39303030 Hex\nNJ101-1000 4E4A3130312D31303030 Hex\nNJ101-9020 4E4A3130312D39303230 Hex\nNJ101-1020 4E4A3130312D31303230 Hex"}
+{"question": "Major and Minor CIP Revisions", "answer": "CIP revisions\nUnit version\nMajor revision Minor revision\nUnit version 1.00 01 hex 01 hex\nUnit version 1.01 or 1.02 03 hex\nUnit version 1.03 to 1.08 02 hex 01 hex\nUnit version 1.09 02 hex\nUnit version 1.10 03 hex\nUnit version 1.11 or 1.12 04 hex\nUnit version 1.13 to 1.20 05 hex\nUnit version 1.21 or later 06 hex\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-51\n7-5\nCIP\nObject\nServices\n7\n7-5-2\nIdentity\nObject\n(Class\nID:\n01\nhex)\n7 CIP Message Communications\nCIP revisions\nModel Unit version\nMajor revision Minor revision\nAll CPU Unit Unit version 1.00 01 hex 01 hex\nmodels Unit version 1.01 or 1.02 03 hex\nUnit version 1.03 to 1.08 02 hex 01 hex\nUnit version 1.09 02 hex\nUnit version 1.10 03 hex\nUnit version 1.11 or 1.12 04 hex\nUnit version 1.13 to 1.20 05 hex\nNJ Series Unit version 1.21 to 1.23 06 hex\nUnit version 1.26 08 hex\nUnit version 1.27 09 hex\nUnit version 1.40 to 1.41 06 hex\nUnit version 1.46 08 hex\nUnit version 1.47 09 hex\nNX Series Unit version 1.21 to 1.22 06 hex\nUnit version 1.28 09 hex\nUnit version 1.30 to 1.43 06 hex\nUnit version 1.44 08 hex\nUnit version 1.60 0A hex"}
+{"question": "Status Details of the Built-in EtherNet/IP Port", "answer": "Bit Name Description\n0 Owned Indicates when the built-in EtherNet/IP port has an open connection as the\ntarget of a tag data link.\n1 Reserved Always FALSE.\n2 Configured Tag data link settings exist.\n3 Reserved Always FALSE.\n4 to 7 Extended Device Status Indicates the status of the built-in EtherNet/IP port.*1\n8 Minor Recoverable Fault TRUE when any of the following errors occurs.\n• IP Route Table Setting Error\n• DNS Server Connection Error\n• Tag Data Link Setting Error\n• Tag Data Link Timeout\n• Tag Data Link Connection Timeout\n• FTP Server Setting Error\n• NTP Client Setting Error\n• SNMP Setting Error\n• NTP Server Connection Error\n• Tag Name Resolution Error\n9 Minor Unrecoverable Fault TRUE when the following error occurs.\n• Identity Error\n10 Major Recoverable Fault TRUE when any of the following errors occurs.\n• IP Address Duplication Error\n• BOOTP Server Error\n• DHCP Server Connection Error\n• Basic Ethernet Setting Error\n• IP Address Setting Error\n7-52 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nBit Name Description\n11 Major Unrecoverable Fault TRUE when any of the following errors occurs.\n• Communications Controller Error\n• MAC Address Error\n12 to 15 Reserved Always FALSE.\n*1. Bits 7 to 4 indicate the status of the built-in EtherNet/IP port.\nb7 b6 b5 b4\n0 1 0 1 A major fault occurred.\n0 0 1 0 A timeout occurred in one or more target connections.\n0 0 1 1 Indicates that there are no tag data link settings.\n0 1 1 0 Indicates that one or more connections are performing communications\nnormally.\n0 1 1 1 Other than the above.\nRequest Paths (IOIs) to Specify Objects\nWhen you specify an object, specify the request path (IOI) for each service code as given below.\nService code Class ID Instance ID Attribute ID\n01 hex Get_Attribute_All 01 hex • Specifying a service for a class Not required.\n0E hex Get_Attribute_Single : 00 hex • Reading a class attribute\n• Specifying a service for an in- : 01 or 02 hex\nstance • Reading an instance attribute\n: Always 01 hex : 01 to 07 hex\n05 hex Reset Always 01 hex Not required.\n7-5-3 NX Configuration Object (Class ID: 74 hex)\nThis object is used to control the NX Unit on the CPU Rack such as reading and writing an NX object,\nrestarting the NX Unit, obtaining an event log and current errors, and clearing the log. This can only be\nused for the NX502 CPU Units and NX102 CPU Units.\nService Codes\nSpecify the service to execute with the service code.\nSupported serv-\nService ices\nParameter name Description Reference\nCode Classe Instan-\ns ces\n33 hex Read NX object Reads the NX object of the specified NX Unit. Not Support- page 7-54\nsup- ed.\nported.\n34 hex Write NX object Writes the NX object of the specified NX Unit. Not Support- page 7-56\nsup- ed.\nported.\n35 hex Restart NX unit Restarts the specified NX Units. Not Support- page 7-57\nsup- ed.\nported.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-53\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nSupported serv-\nService ices\nParameter name Description Reference\nCode Classe Instan-\ns ces\n36 hex Save parameter Saves the parameters of the specified NX Not Support- page 7-58\nUnit. sup- ed.\nported.\n37 hex Switch parameter write Switches the parameter write mode of the Not Support- page 7-59\nmode specified NX Units. sup- ed.\nported.\n38 hex Read total power on Reads the total power on time of the specified Not Support- page 7-61\ntime NX Unit. sup- ed.\nported.\n3A hex Get current error Obtains the current errors of the Controller or Not Support- page 7-62\nspecified NX Unit. sup- ed.\nported.\n3B hex Get event log Obtains the event log of the Controller or Not Support- page 7-65\nspecified NX Unit. sup- ed.\nported.\n3C hex Clear event log Clears the event log of the Controller or speci- Not Support- page 7-69\nfied NX Unit. sup- ed.\nported.\n3D hex Initialize unit operation Initializes the Unit operation settings (NX ob- Not Support- page 7-70\nparameter ject) of the specified NX Unit. sup- ed.\nported.\n3E hex Get current user error Obtains the user-defined errors of the Control- Not Support- page 7-72\nler. sup- ed.\nported.\nClass ID\nSpecify 74 hex.\nInstance ID\nSpecify 01 hex.\nRead NX object (Service Code: 33 hex)\nRead the NX object of the specified NX Unit.\n Request Data Format\nParameter name Data type Description\nService USINT Read NX object service: 33 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\n7-54 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nUnit No UINT Unit number\n0001 to 003F hex: NX Unit*1\nIndex UINT NX object index\nSub index USINT NX object sub index\nControl Field USINT Complete access specification\n00 hex: Not specified\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Read NX object service response: B3 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nLength UINT Read data size (Byte)\nRead data Depends on data Read data\ntype\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Read NX object service response: B3 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n10 Device state conflict The state of the NX object is not in a state to execute the re-\nquired service.\n11 Reply data too large Data larger than the maximum response data length was\nread.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-55\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nGeneral sta-\ntus code Error name Cause\n(hex)\n20 Invalid parameter • The Unit number is out of the supported range.\n• The object of the index specified for the NX object does\nnot exist.\n• The Index specified for the NX object exists but the Sub\nIndex does not exist.\nWrite NX Object (Service Code: 34 hex)\nWrite the NX object of the specified NX Unit.\n Request Data Format\nParameter name Data type Description\nService USINT Write NX object service: 34 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0001 to 003F hex: NX Unit*1\nIndex UINT NX object index\nSub index USINT NX object sub index\nControl Field USINT Complete access specification\n00 hex: Not specified\nLength UINT Write data size (Byte)\nWrite Data Depends on data Write data\ntype\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Write NX object service response: B4 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Write NX object service response: B4 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n7-56 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n0E Attribute not settable The NX object which is not modifiable is specified.\n10 Device state conflict • Carried out writing in a state that was not the parameter\nwrite mode.\n• The state of the NX object is not in a state to execute the\nrequired service.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The sizes of the specified object and Length do not match.\n• The object of the index specified for the NX object does\nnot exist.\n• The Index specified for the NX object exists, but the Sub\nIndex does not exist.\n• Write data is out of the range.\nRestart NX Unit (Service Code: 35 hex)\nRestart the specified NX Units.\n Request Data Format\nParameter name Data type Description\nService USINT Restart NX Unit service: 35 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: All NX Units\n0001 to 003F hex: NX Unit*1\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Restart NX Unit service response: B5 hex\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-57\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nParameter name Data type Description\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Restart NX Unit service response: B5 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP*1\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*2\nAdditional Status UINT Additional Status*3\n*1. When the request is made to an NX Unit that does not support the Restart NX Unit service, error codes\nare returned. (General status: 1F hex, Additional status: 2601 hex)\n*2. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*3. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n10 Device state conflict The target Unit is not in a state to execute the required serv-\nice.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The unit number is out of the supported range.\n• The Unit does not exist.\nSave Parameter (Service Code: 36 hex)\nSave the parameters of the specified NX Unit.\nThe saved parameter is valid after the NX Unit is restarted.\n Request Data Format\nParameter name Data type Description\nService USINT Save parameter service: 36 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\n7-58 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nUnit No UINT Unit number\n0001 to 003F hex: NX Unit*1\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Save parameter service response: B6 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Save parameter service response: B6 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n19 Store operation failure The parameters could not be saved due to internal reasons.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\nSwitch Parameter Write Mode (Service Code: 37 hex)\nSwitch the parameter write mode of the specified NX Units.\n Request Data Format\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-59\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nParameter name Data type Description\nService USINT Switch parameter write mode service: 37 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: All NX Units\n0001 to 003F hex: NX Unit*1\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Switch parameter write mode service response: B7\nhex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Switch parameter write mode service response: B7\nhex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n10 Device state conflict This service could not change because the transition to the\nparameter write mode is in progress.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\n7-60 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRead Total Power On Time (Service Code: 38 hex)\nRead the total power on time of the specified NX Unit.\n Request Data Format\nParameter name Data type Description\nService USINT Read total power on time service: 38 hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0001 to 003F hex: NX Unit*1\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Read total power on time service response: B8 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nTotal power on time ULINT Total power on time of NX Units.\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Read total power on time service response: B8 hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-61\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nGeneral sta-\ntus code Error name Cause\n(hex)\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\nGet Current Error (Service Code: 3A hex)\nObtain the current errors of the Controller or specified NX Unit.\n Request Data Format\nParameter name Data type Description\nService USINT Get current error service: 3A hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: Controller\n0001 to 003F hex: NX Unit*1\nStart number of read record UINT Top number of read record\nNumber of read record UINT Number of read records\nController (0 to 5)\nNX Units (0 to 9)\nWhen the registered number of records is smaller\nthan the number of read records, an error does not\noccur, and all the registered event codes are read.\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Get current error service response: BA hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nError update count UINT Total count value of errors\nRecord size UINT Size of one record (Byte)\nController error: 0060 hex\nNX Unit error: 0032 hex\nNumber of registered record UINT Number of registered records\nNumber of readout record UINT Number of readout records\n7-62 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nCurrent error record[0] Array of struct Cur- Current error array\nto rent error record Stores data for the \"Number of readout record\" from\nCurrent error record[8] index 0 of the current error record. The remaining\nelements of the current error record array are not\nincluded in the response data.\nExample: When the \"Number of readout record\" is 3\nand the response data includes the current error re-\ncord array [0-2], the current error record array [3-8]\nis not included in the response data.\nFor details of the specifications of the structure, re-\nfer to Current Error Record Structure on page\n7-63.\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Get current error service response: BA hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n Current Error Record Structure\nThe format of the current error record information differs between the Controller and NX Unit.\nController\nParameter name Data type Description\nIndex UDINT Current error index number\nThis number is assigned when system event logs\nand access event logs are registered.\nEvent occurred time ULINT Error occurred time\nEvent source UINT Error source\nEvent priority UINT Error level\nEvent code UDINT Event code\nCode system UINT Code system\nEvent source details UINT Error source details\nReserved UDINT Reserved\nVendor code UDINT Vendor code\nDevice type code UDINT Device type code\nProduct code UDINT Product code of the Unit in which errors occurred\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[31]\nReserved[0] Array of BYTE Reserved\nto\nReserved[23]\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-63\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nNX Unit\nParameter name Data type Description\nIndex UDINT Current error index number\nThis number is assigned when system event logs\nand access event logs are registered.\nUnit number USINT Unit number\n0000 hex: Controller\n0001 to 003F hex: NX Unit*1\nEvent priority USINT Error level\nEvent occurred time UDINT Error occurred time\nProduct code UDINT Product code of the Unit in which errors occurred\nEvent code UDINT Event code\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[31]\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The specification of the number of readout records is out\nof the range.\n• The Unit does not exist.\n Method of Use\n1\nThe following variables are generated and initialized to 0.\n• Total number of readout records (UINT)\n• Previous error update count (UINT)\n2\nSpecify the following parameters and execute Get current error (3A hex).\n• Unit No: Unit number subject to error information read\n• Start number of read record: 0\n• Number of read record: Number of read records\n3\nThe following parameters are read from the response data.\n• Error update count\n• Number of registered record\n7-64 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n• Number of readout record\n• Current error record\nWhen the first response is obtained, the value of Error update count is retained as the previous\nerror update count.\nWhen the second response onwards is obtained, the previous error update count and the Error\nupdate count are compared. If the value is updated with any additional current errors of the\nUnit, execute this operation from step1 again.\n4\nAdd the Number of readout record value of the response data to the total number of readout\nrecords.\n5\nIf the total number of readout records does not reach the Number of registered record, it\nmeans that some records have not been read yet. Specify the following parameters and exe-\ncute Get current error again.\n• Start number of read record: Start number of read record when the previous service was\nexecuted + Number of readout record of response.\n• Number of read record: Number of read records\nRepeat steps (3) to (5) until the total number of readout records matches the Number of registered\nrecord.\nGet Event Log (Service Code: 3B hex)\nObtain the event log of the Controller or specified NX Unit.\nWhen the Controller is specified, the event log saved in the Controller is obtained. Event logs of slaves\nconnected to the Controller such as EtherCAT slaves cannot be obtained.\n Request Data Format\nParameter name Data type Description\nService USINT Get event log service: 3B hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: Controller\n0001 to 003F hex: NX Unit*1\nEvent log type UINT Event log type\n0000 hex: System event log\n0001 hex: Access event log\n0002 hex: User event log\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-65\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nParameter name Data type Description\nStart index of read record UDINT Top index number of read record\nIf the record specified by the Start index of read re-\ncord is not found in the Unit, the record will be read\nfrom the oldest index. If the maximum number of\nevent log records which can be registered for the\nUnit is exceeded, this will occur since old records\nare overwritten by new records.\nNumber of read record UINT Number of read records\nController (0 to 5)\nNX Units (0 to 9)\nWhen the registered number of records is smaller\nthan the number of read records, an error does not\noccur, and all the registered event logs are read.\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Get event log service response: BB hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nRecord size UINT Size of one record (Byte)\nController event log: 0060 hex\nNX Unit event log: 0032 hex\nNumber of registered record UINT Number of registered records\nLatest index of registered record UDINT Index number of the latest registered record\nLast index of readout record UDINT Index number of last readout record\nNumber of readout record UINT Number of readout records\nReserved UINT Reserved\nEvent log record[0] Array of struct Event log array\nto Event Log Record Stores data for the \"Number of readout record\" from\nEvent log record[8] index 0 of the event log record. The remaining ele-\nments of the event log record array are not included\nin the response data.\nExample: When the \"Number of readout record\" is 3\nand the response data includes the event log re-\ncord array [0-2], the event log record array [3-8] is\nnot included in the response data.\nFor details of the specifications of the structure, re-\nfer to Event Log Record Structure on page 7-67.\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Get event log service response: BB hex\nReserved USINT Reserved: 00 hex\n7-66 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n Event Log Record Structure\nThe format of the event log record information differs between the Controller and NX Unit.\nController system event log and access event log\nParameter name Data type Description\nIndex UDINT Event log index number\nThis number is assigned when system event logs\nand access event logs are registered.\nEvent occurred time ULINT Event occurred time\nEvent source UINT Event source\nEvent priority UINT Event level\nEvent code UDINT Event code\nCode system UINT Code system\nEvent source details UINT Event source details\nReserved UDINT Reserved\nVendor code UDINT Vendor code\nDevice type code UDINT Device type code\nProduct code UDINT Product code of the Unit in which event occurred\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[31]\nReserved[0] Array of BYTE Reserved\nto\nReserved[23]\nController user event log\nParameter name Data type Description\nIndex UDINT Event log index number\nThis number is assigned when system event logs\nand access event logs are registered.\nEvent occurred time ULINT Event occurred time\nEvent source UINT Event source\nEvent priority UINT Event level\nEvent code UDINT Event code\nEvent priority details UINT Event level details\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[39]\nReserved[0] Array of BYTE Reserved\nto\nReserved[31]\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-67\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nNX Unit\nParameter name Data type Description\nIndex UDINT Event log index number\nThis number is assigned when system event logs\nand access event logs are registered.\nUnit number USINT Unit number\n0000 hex: Controller\n0001 to 003F hex: NX Unit*1\nEvent priority USINT Event level\nEvent occurred time UDINT Event occurred time\nProduct code UDINT Product code of the Unit in which event occurred\nEvent code UDINT Event code\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[31]\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The specification of the number of readout records is out\nof the range.\n• The Unit does not exist.\n Method of Use\n1\nThe following variables are generated and initialized to 0.\n• Total number of readout records (UINT)\n• Record index during the previous readout (UDINT)\n• Previous latest record index (UDINT)\n2\nSpecify the following parameters and execute Get event log(3B hex).\n• Unit No: Unit number subject to event information readout\n• Start number of read record: 0\n• Number of read record: Number of read records\n3\nThe following parameters are read from the response data.\n• Number of registered record\n7-68 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n• Latest index of registered record\n• Last index of readout record\n• Number of readout record\n• Event log record\nWhen the first response is obtained, the value of Latest index of registered record value is re-\ntained as the record index during the previous readout.\nWhen the second response onwards is obtained, the record index during the previous readout\nand Latest index of registered record value are compared. If the value is updated with any ad-\nditional event logs of the Unit, execute this operation from step1 again.\n4\nAdd the Number of readout record value of the response data to the total number of readout\nrecords.\n5\nIf the total number of readout records does not reach the Number of registered record, it\nmeans that some records have not been read yet. Specify the following parameters and exe-\ncute Get event log again.\n• Start number of read record: Last index of readout record when the previous service was\nexecuted + 1.\n• Number of read record: Number of read records\nRepeat steps (3) to (5) until the total number of readout records matches the Number of registered\nrecord.\nClear Event Log (Service Code: 3C hex)\nClear the event log of the Controller or specified NX Unit.\nThe event log is immediately cleared after the service is successful. When it is executed for the Con-\ntroller, only the event log saved in the Controller is cleared. Event logs of slaves connected to the Con-\ntroller such as EtherCAT slaves are not cleared.\n Request Data Format\nParameter name Data type Description\nService USINT Clear event log service: 3C hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: Controller\n0001 to 003F hex: NX Unit*1\nEvent log type UINT Event log type\n0000 hex: System event log\n0001 hex: Access event log\n0002 hex: User event log*2\n0003 hex: All types of the system event log, access\nevent log, user event log.\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n*2. The User event log is valid only when the Controller is specified for the Unit number.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-69\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Clear event log service response: BC hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Clear event log service response: BC hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\nInitialize Unit Operation Parameter (Service Code: 3D hex)\nInitializes the Unit operation settings (NX object) of the specified NX Unit.\nThe initialized parameters are valid after the NX Unit is restarted.\nBy executing this service, NX Unit Memory All Cleared (95810000 hex) is registered in the event log.\nWhen the NX Unit is Operational or Safe-Operational, you need to initialize the status beforehand with\nthe Switch parameter write mode service. If the Initialize unit operation parameter is executed without\ncarrying out this step, error will result, and Device state conflict (10 hex) will be returned to the General\nStatus.\nThis service does not support the NX-series Safety Control Unit. If this service is executed for the\nNXseries Safety Control Unit, an error will occur.\n Request Data Format\n7-70 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nService USINT Initialize unit operation parameter service: 3D hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0001 to 003F hex: NX Unit*1\n*1. The range is 0001 to 0020 hex for an NX102 CPU Unit.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Initialize unit operation parameter service response:\nBD hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Initialize unit operation parameter service response:\nBD hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n10 Device state conflict The device state is not in a state to execute the required\nservice.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-71\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\nGet Current User Error (Service Code: 3E hex)\nObtain the user-defined errors of the Controller.\n Request Data Format\nParameter name Data type Description\nService USINT Get current user error service: 3E hex\nRequest Path Size USINT Size of Request Path: 02 hex\nRequest Path Padded EPATH Request path: 2074 2401 hex\nClass ID: 74 hex\nInstance ID: 01 hex\nUnit No UINT Unit number\n0000 hex: Controller\n0001 hex or above: Not supported\nStart number of read record UINT Top number of read record\nNumber of read record UINT Number of read records (0 to 5)\nWhen the registered number of records is smaller\nthan the number of read records, an error does not\noccur, and all the registered event logs are read.\n Response Data Format\nWhen the processing is successful\nParameter name Data type Description\nReply Service USINT Get current user error service response: BE hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Code indicating normal: 00 hex\nSize of Additional Status USINT Size of Additional Status: 00 hex\nError update count UINT Total count value of errors\nRecord size UINT Size of one record (Byte):0060 hex\nNumber of registered record UINT Number of registered records\nNumber of readout record UINT Number of readout records\nUser error record[0] Array of struct User User-defined error array\nto error record Stores data for the \"Number of readout record\" from\nUser error record[8] index 0 of the User error record. The remaining ele-\nments of the User error record array are not includ-\ned in the response data.\nExample: When the \"Number of readout record\" is 3\nand the response data includes the User error re-\ncord array [0-2], the User error record array [3-8] is\nnot included in the response data.\nFor details of the specifications of the structure, re-\nfer to User Error Record Structure.\nWhen the processing failed\nParameter name Data type Description\nReply Service USINT Get current user error service response: BE hex\nReserved USINT Reserved: 00 hex\nGeneral Status USINT Current error code defined by CIP\n7-72 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nParameter name Data type Description\nSize of Additional Status USINT Size of Additional Status: 00 hex or 01 hex*1\nAdditional Status UINT Additional Status*2\n*1. When the General Status of the response code is 1F hex (Vendor specific error), becomes 01 hex.\n*2. This is stored only when the Size of Additional Status is 01 hex.\n User Error Record Structure\nParameter name Data type Description\nIndex UDINT User-defined error index number\nThis number is assigned when system event logs\nand access event logs are registered.\nEvent occurred time ULINT Error occurred time\nEvent source UINT Error source\nEvent priority UINT Error level\nEvent code UDINT Event code\nEvent priority details UINT Error level details\nReserved UINT Reserved\nAdditional information[0] Array of BYTE Attached information (system information) of event.\nto\nAdditional information[39]\nReserved[0] Array of BYTE Reserved\nto\nReserved[31]\n CIP Error Codes\nGeneral sta-\ntus code Error name Cause\n(hex)\n02 Resource unavailable Resources needed for the object to perform the requested\nservice were unavailable.\n0C Object state conflict The object cannot perform the requested service in its cur-\nrent mode/state.\n13 Not enough data Data required for the execution of the required service is in-\nsufficient.\n15 Too much data Extra data for the execution of the required service is includ-\ned.\n1F Vendor specific error The service could not be executed due to internal reasons.\n20 Invalid parameter • The Unit number is out of the supported range.\n• The Unit does not exist.\n Method of Use\n1\nThe following variables are generated and initialized to 0.\n• Total number of readout records (UINT)\n• Previous error update count (UINT)\n2\nSpecify the following parameters and execute Get current user error (3E hex).\n• Unit No: Unit number subject to error information readout\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-73\n7-5\nCIP\nObject\nServices\n7\n7-5-3\nNX\nConfiguration\nObject\n(Class\nID:\n74\nhex)\n7 CIP Message Communications\n• Start number of read record: 0\n• Number of read record: Number of read records\n3\nThe following parameters are read from the response data.\n• Error update count\n• Number of registered record\n• Number of readout record\n• User error record\nWhen the first response is obtained, the value of Error update count is retained as the previous\nerror update count.\nWhen the second response onwards is obtained, the previous error update count and the Error\nupdate count are compared. If the value is updated with any additional user-defined errors of\nthe Unit, execute this operation from step1 again.\n4\nAdd the Number of readout record value of the response data to the total number of readout\nrecords.\n5\nIf the total number of readout records does not reach the Number of registered record, it\nmeans that some records have not been read yet. Specify the following parameters and exe-\ncute Get current error again.\n• Start number of read record: Start number of read record when the previous service was\nexecuted + Number of readout record of response.\n• Number of read record: Number of read records\nRepeat steps (3) to (5) until the total number of readout records matches the Number of registered\nrecord.\n7-5-4 TCP/IP Interface Object (Class ID: F5 hex)\nThis object is used to read and write settings such as the IP address, subnet mask, and default gate-\nway.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, it is necessary to use the route path\nof the CIP communications instruction (the RoutePath input variable) to specify the port number (1 or\n2) of the built-in EtherNet/IP port to access.\nService Codes\nSpecify the service to execute with the service code.\nService Supported services\nParameter name Description\ncode Classes Instances\n01 hex Get_Attribute_All Reads the values of the attributes. Supported Not sup-\nported\n0E hex Get_Attribute_Single Reads the value of the specified attribute. Supported Supported\n7-74 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nService Supported services\nParameter name Description\ncode Classes Instances\n10 hex Set_Attribute_Single Writes a value to the specified attribute. Not sup- Supported\nThe built-in EtherNet/IP port restarts automatically after ported\nthe value is written to the attribute.\nWhen the next Set_Attribute_Single is executed before\nthe restart process is completed, the general status \"0C\nhex\" (Object State Conflict) is returned.\nClass ID\nSpecify F5 hex.\nInstance ID\nSpecify 00 or 01 hex.\n00: Specify the class\n01: Built-in EtherNet/IP Port\nAttribute ID\nThe attribute ID specifies the information to read.\n Class Attribute ID\nThe class attribute ID specifies the attribute of the entire object.\nAt- Read data\nAttrib-\nParameter name Description trib-\nute ID Data type Value\nute\n01 hex Revision Revision of the object Read UINT 0001 hex: Unit version 1.01 or\nearlier\n0002 hex: Unit version 1.02 to"}
+{"question": "09", "answer": "0003 hex: Unit version 1.10\n0004 hex: Unit version 1.11 or\nlater\n02 hex Max Instance The maximum instance num- Read UINT 0001 hex\nber\n03 hex Number of Instances The number of object instan- Read UINT 0001 hex\nces\n Instance Attribute ID\nThe instance attribute ID specifies the attribute of the instance.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-75\n7-5\nCIP\nObject\nServices\n7\n7-5-4\nTCP/IP\nInterface\nObject\n(Class\nID:\nF5\nhex)\n7 CIP Message Communications\nRead/write data\nAttrib-\nAttribute ID Parameter name Description Data\nute Value\ntype\n01 hex Interface Configura- Indicates the IP address set- Read DWOR Bits 0 to 3: Interface Configu-\ntion Status ting status of the interface. D ration Status:\n0 = IP address is not set. (This\nincludes when BOOTP is\nstarting.)\n1 = IP address is set.\nBits 4 and 5: Reserved (al-\nways FALSE).\nBit 6: AcdStatus*1:\nFALSE = IP address collisions\nhave not been detected.\nTRUE = IP address collisions\nhave been detected.\nBits 7 to 31: Reserved (always\nFALSE).\n02 hex Configuration Capabil- Indicates a Controller Con- Read DWOR Bit 0: BOOTP Client: Always\nity figurations and Setup that D TRUE.\ncan be set to the interface. Bit 1: DNS Client: Always\nTRUE.\nBit 2: DHCP Client: *4\nBit 3: DHCP-DNS Update: Al-\nways FALSE.\nBit 4: Configuration Settable:\nAlways TRUE.\nBit 5: Hardware Configurable:\nAlways FALSE.\nBit 6: Interface Configuration\nChange Requires Reset: Al-\nways FALSE.\nBit 7: ACD Capable*1: Always\nTRUE.\nBits 8 to 31: Reserved (always\nFALSE).\n03 hex Configuration Control Sets the method used to set Read/ DWOR Bit 0 to 3: IP Address Setting\nthe IP address when the in- Write D Method\nterface starts. 0 = Setting the static IP ad-\ndress.\n1 = Setting by BOOTP.\n2 = Setting by DHCP\nBit 4: DNS Enable/Disable\nSetting\nFALSE = DNS disabled.\nTRUE = DNS enabled.\nBits 5 to 31: Reserved (always\nFALSE).\n04 hex Physical Link Object The path to the link object in Read Struct ---\nthe physical layer.\nPath size The path size (WORD size). UINT 0002 hex\nPath The path to the link object in EPATH 20 F6 24 01 hex\nthe physical layer (static).\n7-76 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRead/write data\nAttrib-\nAttribute ID Parameter name Description Data\nute Value\ntype\n05 hex Interface Configura- The interface settings. Read/ Struct ---\ntion Write\nIP Address IP address. UDINT Set value\nNetwork Mask Subnet mask. UDINT Set value\nGateway Address The default gateway. UDINT Set value\nName Server The primary name server. UDINT Set value\nName Server2 The secondary name server. UDINT Set value\nDomain Name The domain name. STRIN Set value*2\nG\n06 hex Host Name The host name (reserved). Read/ STRIN Set value*3\nWrite G\n*1. The value is always FALSE for a CPU Unit with unit version 1.01 or earlier.\n*2. The value is the size of domain name (2 bytes) + domain name (48 bytes max.).\n*3. The value is the size of host name (2 bytes) + host name (64 bytes max.).\n*4. The value is always TRUE for CPU Units that support the DHCP client. The value is always FALSE for unsupported\nCPU Units.\nRefer to A-1 Functional Comparison of EtherNet/IP Ports on NJ/NX-series CPU Units and Other Series on page A-3\nfor checking whether the CPU Unit that you use supports the DHCP client.\nRequest Paths (IOIs) to Specify Objects\nWhen you specify an object, specify the request path (IOI) for each service code as given below.\nClass\nService code Instance ID Attribute ID\nID\n01 hex Get_Attribute_All F5 hex • Specifying a service for a class: 00 Not required.\n0E hex Get_Attribute_Single hex • Reading a class attribute: 01\n10 hex Set_Attribute_Single • Specifying a service for an in- or 03 hex\nstance: 01 hex • Reading and writing an in-\nstance attribute: 01 to 06 hex\n7-5-5 Ethernet Link Object (Class ID: F6 hex)\nThis object is used to set and read Ethernet communications and read Ethernet communications sta-\ntus information.\nFor NX701 CPU Units, NX502 CPU Units, and NX102 CPU Units, it is necessary to use the route path\nof the CIP communications instruction (the RoutePath input variable) to specify the port number (1 or\n2) of the built-in EtherNet/IP port to access.\nService Codes\nSpecify the service to execute with the service code.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-77\n7-5\nCIP\nObject\nServices\n7\n7-5-5\nEthernet\nLink\nObject\n(Class\nID:\nF6\nhex)\n7 CIP Message Communications\nSupported\nService\nParameter name Description service range\ncode\nClass Instance\n0E hex Get_Attribute_Single Reads the value of the specified attribute. Support- Support-\ned ed\n10 hex Set_Attribute_Single Writes a value to the specified attribute. Support- Support-\ned ed\n4C hex Get_and_Clear Specify Attribute4 or Attribute5 to reset the value of the Not sup- Support-\nattribute to 0. ported ed\nClass ID\nSpecify F6 hex.\nInstance ID\nSpecify 00 or 01 hex.\n00: Specify the class\n01: Built-in EtherNet/IP Port\nAttribute ID\nThe attribute ID specifies the information to read.\n Class Attribute ID\nThe class attribute ID specifies the attribute of the entire object.\nAt- Read data\nAttrib-\nParameter name Description trib-\nute ID Data type Value\nute\n01 hex Revision Revision of the object Read UINT 0002 hex: Unit version 1.11 or\nearlier\n0004 hex: Unit version 1.12 or\nlater\n02 hex Max Instance The maximum instance num- Read UINT 0001 hex\nber\n03 hex Number of Instances The number of object instan- Read UINT 0001 hex\nces\n Instance Attribute ID\nThe instance attribute ID specifies the attribute of the instance.\nRead/write data\nAttribute Attrib-\nParameter name Description Data\nID ute Value\ntype\n01 hex Interface Speed Gives the baud rate for the in- Read UDINT Reads the current value.\nterface.\n02 hex Interface Flags Gives the status of the inter- Read DWOR Refer to (1) Interface Flag\nface. D Details, below.\n7-78 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRead/write data\nAttribute Attrib-\nParameter name Description Data\nID ute Value\ntype\n03 hex Physical Address Gives the MAC address of Read ARRAY Reads the current value of\nthe interface. [0...5] the MAC address.\nOF\nUSINT\n04 hex Interface Counters The number of packets sent/ Read Struct ---\nreceived through the inter-\nface.\nIn Octets The number of octets re- UDINT Reads the current value.\nceived through the interface.\nThis includes unnecessary\nmulticast packets and dis-\ncarded packets counted by\nInDiscards.\nIn Unicast Packets The number of unicast pack- UDINT Reads the current value.\nets received through the inter-\nface. This does not include\ndiscarded packets counted by\nInDiscards.\nIn NonUnicast Packets The number of packets be- UDINT Reads the current value.\nsides unicast packets re-\nceived through the interface.\nThis includes unnecessary\nmulticast packets, but does\nnot include discarded packets\ncounted by InDiscards.\nIn Discards The number of discarded in- UDINT Reads the current value.\ncoming packets received\nthrough the interface.\nIn Errors The number of incoming UDINT Reads the current value.\npackets that had errors. This\nis not included in InDiscards.\nIn Unknown Protos The number of incoming UDINT Reads the current value.\npackets that were of an un-\nknown protocol.\nOut Octets The number of octets sent UDINT Reads the current value.\nthrough the interface.\nOut Unicast Packets The number of unicast pack- UDINT Reads the current value.\nets sent through the interface.\nOut NonUnicast Pack- The number of packets be- UDINT Reads the current value.\nets sides unicast packets sent\nthrough the interface.\nOut Discards The number of discarded sent UDINT Reads the current value.\npackets.\nOut Errors The number of sent packets UDINT Reads the current value.\nthat had errors.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-79\n7-5\nCIP\nObject\nServices\n7\n7-5-5\nEthernet\nLink\nObject\n(Class\nID:\nF6\nhex)\n7 CIP Message Communications\nRead/write data\nAttribute Attrib-\nParameter name Description Data\nID ute Value\ntype\n05 hex Media Counters Media counters for the com- Read Struct ---\nmunications port.\nAlignment Errors Number of frames received UDINT Reads the current value.\nthat were not octets in length.\nFCS Errors Number of frames received UDINT Reads the current value.\nthat did not pass the FCS\ncheck.\nSingle Collisions Number of frames sent suc- UDINT Reads the current value.\ncessfully with only one colli-\nsion.\nMultiple Collisions Number of frames sent suc- UDINT Reads the current value.\ncessfully with two or more\ncollisions.\nSQE Test Errors Number of times a SQE test UDINT Reads the current value.\nerror message was generat-\ned.\nDeferred Transmis- The number of frames for UDINT Reads the current value.\nsions which the first attempt to send\nwas delayed because the me-\ndia was busy.\nLate Collisions The number of collisions de- UDINT Reads the current value.\ntected in packets that were\nsent after 512 bit times.\nExcessive Collisions The number of frames that UDINT Reads the current value.\nfailed to be sent because of\nexcessive collisions.\nMAC Transmit Errors The number of frames that UDINT Reads the current value.\nfailed to be sent due to an in-\nternal MAC sublayer trans-\nmission error.\nCarrier Sense Errors The number of times the car- UDINT Reads the current value.\nrier sense condition was lost\nor the number of times an as-\nsertion did not occur when an\nattempt was made to send\nthe frame.\nFrame Too Long The number of frames re- UDINT Reads the current value.\nceived that exceeded the\nmaximum allowed frame size.\nMAC Receive Errors The number of frames that UDINT Reads the current value.\ncould not be received through\nthe interface due to an inter-\nnal MAC sublayer reception\nerror.\n7-80 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRead/write data\nAttribute Attrib-\nParameter name Description Data\nID ute Value\ntype\n06 hex Interface Control Control settings for the inter- Read/ Struct ---\nface. Write\nControl Bits Auto Nego for Ethernet com- WORD Refer to (2) Control Bit De-\nmunications that specifies full tails, below.\nduplex.\nForced Interface Speed Gives the set value of the UINT Reads the set value.\nEthernet baud rate.\n0C hex *1 HC Interface Counters The number of packets sent/ Read Struct ---\nreceived through the HC in-\nterface.\nHCInOctets The number of octets re- ULINT Reads the current value.\nceived through the interface.\nThis counter is the 64-bit edi-\ntion of In Octets.\nHCInUnicastPkts The number of unicast pack- ULINT Reads the current value.\nets received through the inter-\nface. This counter is the 64-\nbit edition of In Ucast Pack-\nets.\nHCInMulticastPkts The number of multicast ULINT Reads the current value.\npackets received through the\ninterface.\nHCInBroadcastPkts The number of broadcast ULINT Reads the current value.\npackets received through the\ninterface.\nHCOutOctets The number of octets sent ULINT Reads the current value.\nthrough the interface.\nHCOutUnicastPkts The number of unicast pack- ULINT Reads the current value.\nets sent through the interface.\nThis counter is the 64-bit edi-\ntion of Out Octets.\nHCOutMulticastPkts The number of multicast ULINT Reads the current value.\npackets sent through the in-\nterface.\nHCOutBroadcastPkts The number of broadcast ULINT Reads the current value.\npackets sent through the in-\nterface.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-81\n7-5\nCIP\nObject\nServices\n7\n7-5-5\nEthernet\nLink\nObject\n(Class\nID:\nF6\nhex)\n7 CIP Message Communications\nRead/write data\nAttribute Attrib-\nParameter name Description Data\nID ute Value\ntype\n0D hex*1 HC Media Counters Media counters for the com- Read Struct ---\nmunications port.\nHCStatsAlignmentEr- The number of frames re- ULINT Reads the current value.\nrors ceived that were not octets in\nlength. This counter is the 64-\nbit edition of Alignment Er-\nrors.\nHCStatsFCSErrors The number of frames re- ULINT Reads the current value.\nceived that did not pass the\nFCS check. This counter is\nthe 64-bit edition of FCS Er-\nrors.\nHCStatsInternalMac- The number of frames that ULINT Reads the current value.\nTransmitErrors failed to be sent due to an in-\nternal MAC sublayer trans-\nmission error. This counter is\nthe 64-bit edition of MAC\nTransmit Errors.\nHCStatsFrameToo- The number of frames re- ULINT Reads the current value.\nLongs ceived that exceeded the\nmaximum allowed frame size.\nThis counter is the 64-bit edi-\ntion of Frame Too Long.\nHCStatsInternalMa- The number of frames that ULINT Reads the current value.\ncReceiveErrors could not be received through\nthe interface due to an inter-\nnal MAC sublayer reception\nerror. This counter is the 64-\nbit edition of MAC Receive\nErrors.\nHCStatsMacSymbolEr- The number of frames that ULINT Reads the current value.\nrors could not be received through\nthe interface due to an inter-\nnal MAC sublayer rsymbol er-\nror.\n*1. A CPU Unit with unit version 1.13 or later is required to use this attribute."}
+{"question": "Interface Flag Details", "answer": "Bit Name Description\n0 LinkStatus FALSE: The link is down. TRUE: The link is up.\n1 Half/FullDuplex FALSE: Half duplex TRUE: Full duplex\n2 to 4 Negotiation Status 00 hex: Auto-negotiation is in progress.\n01 hex: Auto-negotiation and speed detection failed.\n02 hex: Auto-negotiation failed, but speed detection succeeded.\n03 hex: Speed and duplex mode negotiation succeeded.\n04 hex: Auto-negotiation was not attempted.\n5 Manual Setting Requires Always FALSE: Changes can be applied automatically.\nSpeed\n6 Local Hardware Fault Always FALSE\n7-82 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nBit Name Description\n7 to 31 Reserved Always FALSE"}
+{"question": "Control Bit Details", "answer": "Bit Name Description\n0 Auto-negotiate FALSE: Auto-negotiation is disabled.\nTRUE: Auto-negotiation is enabled.\n1 ForcedDuplex Mode FALSE: Half duplex TRUE: Full duplex*1\n2 to 16 Reserved Always FALSE\n*1. When auto-negotiation is enabled (bit 0 is TRUE), this should always be FALSE.\nRequest Paths (IOIs) to Specify Objects\nWhen you specify an object, specify the request path (IOI) for each service code as given below.\nClass\nService code Instance ID Attribute ID\nID\n0E hex Get_Attribute_Single F6 hex • Specifying a service for a class: 00 • Reading a class attribute: 01\n10 hex Set_Attribute_Single hex to 03 hex\n• Specifying a service for an in- • Reading and writing a in-\nstance: Always 01 hex stance attribute: 01 to 06 hex,\n0C hex, and 0D hex\n4C hex Get_and_Clear Specify an attribute to clear the\nvalue to 0: 04 hex, 05 hex, 0C\nhex, 0D hex\n7-5-6 Controller Object (Class ID: C4 hex)\nThis object is used to get the status of the Controller or to change the operating mode of the Control-\nler.\nService Codes\nSpecify the service to execute with the service code.\nSupported service\nService\nParameter name Description range\ncode\nClass Instance\n0E hex Get_Attribute_Single Reads the value of the specified attribute. Support- Not sup-\ned ported\n10 hex Set_Attribute_Single Writes a value to the specified attribute. Support- Not sup-\ned ported\n51 hex Reset_Sys- Clears all errors of CPU Unit. Support- Not sup-\ntem_Alarm_All ed ported\nClass ID\nSpecify C4 hex.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-83\n7-5\nCIP\nObject\nServices\n7\n7-5-6\nController\nObject\n(Class\nID:\nC4\nhex)\n7 CIP Message Communications\nInstance ID\nSpecify 00 hex.\n Class Attribute ID\nThe class attribute ID specifies the attribute (value) of the entire object.\nRead/write data\nAttrib-\nAttribute ID Parameter name Description Data\nute Value\ntype\n01 hex Revision Revision of the object Read UINT Always 0002 hex.\n02 hex Max Instance The maximum instance num- Read UINT Always 0001 hex.\nber\n64 hex PLC Mode This can be used to read and Read/ UINT Specify this when you want\nmodify the Controller operat- Write to write to an attribute.\ning mode. 0001 hex: PROGRAM\nmode\n0004 hex: RUN mode\n65 hex PLC Error Status Indicates when there is a Read UINT 0000 hex: There is no Con-\nController error. Changes to troller error.\nTRUE when a fatal or non-fa- 0001 hex: There is a Con-\ntal error occurs. troller error.\n66 hex PLC Model Indicates the model of the Read STRING\nController. The length is al-\nways 2 bytes for the size +\n20 bytes for the name. Un-\nused area is padded with\nspaces.\n Instance Attribute ID\nNone\nRequest Paths (IOIs) to Specify Objects\nWhen you specify an object, specify the request path (IOI) for each service code as given below.\nService code Class ID Instance ID Attribute ID\n0E hex Get_Attribute_Single C4 hex 00 hex Specifies the attribute of the\n10 hex Set_Attribute_Single class to read or write\n: 01 hex, 02 hex, or 64 to 66 hex\n7-84 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n7-6 Read and Write Services for Variables\nThis section shows services that specify the CIP object in the Request Path and access the CIP mes-\nsage server function of the NJ/NX-series Controllers.\n7-6-1 Read Service for Variables\nSpecify service code 4C hex to read the value of the variable that is specified by the request path.\nService code: 4C hex\n Request Data Format\nRequest Path Data\nVariable name specification\nRequest Service Data\n+0 Num of Element (L) UINT Specify the number of elements to read for an array variable.\n+1 (H)\nResponse Service Data\nData Type USINT Data type of variable to read\nAddInfo Length USINT Additional information: Field length in bytes\n(AddInfo) Additional information: CRC value of structure\nActual data*\n*1. The actual data is stored in little-endian format.\nData Type Code for data type of variable to read. Refer to 7-7-1 Data Type Codes on page 7-89.\nAddInfoLength The size of the AddInfo area is stored only when accessing a structure variable.\nSet 02 hex for a structure variable. Otherwise, set 00 hex.\nAddInfo The CRC code of the structure definition is stored only when accessing a structure vari-\nable. In this case, the size of AddInfo will be 2 bytes.\nActual data The actual data is stored in little-endian format.\nIf 0001 hex is specified for an array, the actual data is stored in the same format as\nwhen you access a variable with the data type of the elements of the array.\nResponse Codes\nCIP Add\nMeaning Cause\nstatus status\n00 SUCCESS --- The service ended normally.\n02 RESOURCE_UNAVAILABLE --- The internal processing buffer is not\navailable.\n04 PATH_SEGMENT_ERROR --- The request path specification is not cor-\nrect.\n05 PATH_DESTINATION_UNKNOWN --- The variable specification is not correct.\n0C OBJECT_STATE_CONFLICT 8010 Downloading, starting up\n8011 There is an error in tag memory.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-85\n7-6\nRead\nand\nWrite\nServices\nfor\nVariables\n7\n7-6-1\nRead\nService\nfor\nVariables\n7 CIP Message Communications\nCIP Add\nMeaning Cause\nstatus status\n11 REPLY_DATA_TOO_LARGE --- The response exceeds the maximum re-\nsponse length.\n13 NOT_ENOUGH_DATA --- The data length was too short for the\nspecified service.\n15 TOO_MUCH_DATA --- The data length was too long for the\nspecified service.\n1F VENDOR_SPECIFIC_ERROR 0102,2104 An attempt was made to read an I/O var-\niable that cannot be read.\n0104,1103 The specified address and size exceed a\nsegment boundary.\n8001 An internal error occurred.\n8007 An inaccessible variable was specified.\n8031 An internal error occurred. (A memory al-\nlocation error occurred.)\n20 INVALID_PARAMETER 8009 A segment type error occurred.\n800F There is an inconsistency in data length\ninformation in the request data\n8017 More than one element was specified for\na variable that does not have elements.\n8018 Zero elements or data that exceeded the\nrange of the array was specified for an\narray.\n8023 An internal error occurred. (An illegal\ncommand format was used.)\n8024 An internal error occurred. (An illegal\ncommand length was used.)\n8025 An internal error occurred. (An illegal pa-\nrameter was used.)\n8027 An internal error occurred. (A parameter\nerror occurred.)\n8028 • An attempt was made to write an out-\nof-range value for a variable for which\na subrange is specified.\n• An attempt was made to write an un-\ndefined value to an enumeration varia-\nble.\n7-6-2 Write Service for Variables\nSpecify service code 4D hex to write the value of the variable that is specified by the request path.\n7-86 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nRequest Data Format for Writing a Variable\nRequest Path Data\nVariable name specification\nRequest Service Data\nData Type USINT Data type of variable to write\nAddInfo Length USINT Additional information: Field length in bytes\n(AddInfo) Additional information: CRC value of structure\nNum of Element (L) UINT\n(H)\nActual data*\nResponse Service Data\nThere is no response service data.\n*1. Data to write: Store the data to write in little-endian format.\nData Type Code for data type of variable to write. Refer to 7-7 Variable Data Types on page 7-89.\nAddInfoLength Specify the size of the AddInfo area only when accessing a structure variable.\nSet 02 hex for a structure variable. Otherwise, set 00 hex.\nAddInfo The CRC code of the structure definition is specified only when accessing a structure\nvariable.\nIn this case, the size of AddInfo will be 2 bytes.\nNumOfElement Specify the number of elements in the array. Do not specify 0000 hex (an error will oc-\ncur).\nFor variables other than arrays, set 0001 hex.\nActual data Specify the actual data in little-endian format.\nIf 0001 hex is specified for an array, specify the actual data in the same format as when\nyou access a variable with the data type of the elements of the array.\nResponse Codes\nCIP Add\nMeaning Cause\nstatus status\n00 SUCCESS --- The service ended normally.\n02 RESOURCE_UNAVAILABLE --- The internal processing buffer is not availa-\nble.\n04 PATH_SEGMENT_ERROR --- The request path specification is not cor-\nrect.\n05 PATH_DESTINATION_UNKNOWN --- The link was followed to the end, but the\nvariable was not found.\n0C OBJECT_STATE_CONFLICT 8010 Downloading, starting up\n8011 There is an error in tag memory.\n13 NOT_ENOUGH_DATA --- The data length was too short for the speci-\nfied service.\n15 TOO_MUCH_DATA --- The data length was too long for the speci-\nfied service.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-87\n7-6\nRead\nand\nWrite\nServices\nfor\nVariables\n7\n7-6-2\nWrite\nService\nfor\nVariables\n7 CIP Message Communications\nCIP Add\nMeaning Cause\nstatus status\n1F VENDOR_SPECIFIC_ERROR 0102,2103 An attempt was made to write a constant or\nread-only variable.\n0104,1103 The specified address and size exceed a\nsegment boundary.\n8001 An internal error occurred. (An information\ninconsistency was detected in the interface\nin the Module.)\n8007 An inaccessible variable was specified.\n8029 A region that all cannot be accessed at the\nsame time was specified for SimpleData-\nSegment.\n8031 An internal error occurred. (A memory allo-\ncation error occurred.)\n20 INVALID_PARAMETER 8009 A segment type error occurred.\n800F There is an inconsistency in data length in-\nformation in the Request Data.\n8017 More than one element was specified for a\nvariable that does not have elements.\n8018 Zero elements or data that exceeded the\nrange of the array was specified for an ar-\nray.\n8021 A value other than 0 and 2 was specified\nfor an AddInfo area.\n8022 • The data type that is specified in the re-\nquest service data does not agree with\nthe tag information.\n• The AddInfo Length in the request serv-\nice data is not 0.\n8023 An internal error occurred. (An illegal com-\nmand format was used.)\n8024 An internal error occurred. (An illegal com-\nmand length was used.)\n8025 An internal error occurred. (An illegal pa-\nrameter was used.)\n8027 An internal error occurred. (A parameter er-\nror occurred.)\n8028 • An attempt was made to write an out-of-\nrange value for a variable for which a\nsubrange is specified.\n• An attempt was made to write an unde-\nfined value to an enumeration variable.\n7-88 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\n7-7 Variable Data Types\nThis section provides the data types of variables that can be used with CIP message communications.\n7-7-1 Data Type Codes\nThe following codes are given to variable data types.\nData Type Code (hex) Group*1\nBoolean (bit) C1 CIP Common\nSINT (1-byte signed binary) C2 CIP Common\nINT (1-word signed binary) C3 CIP Common\nDINT (2-word signed binary) C4 CIP Common\nLINT (4-word signed binary) C5 CIP Common\nUSINT (1-byte unsigned binary) C6 CIP Common\nUINT (1-word unsigned binary) C7 CIP Common\nUDINT (2-word unsigned binary) C8 CIP Common\nULINT (4-word unsigned binary) C9 CIP Common\nREAL (2-word floating point) CA CIP Common\nLREAL (4-word floating point) CB CIP Common\nSTRING D0 CIP Common\nBYTE (1-byte hexadecimal) D1 CIP Common\nWORD (1-word hexadecimal) D2 CIP Common\nDWORD (2-word hexadecimal) D3 CIP Common\nTIME ( 8-byte data) DB CIP Common\nLWORD (4-word hexadecimal) D4 CIP Common\nAbbreviated STRUCT A0 CIP Common\nSTRUCT A2 CIP Common\nARRAY A3 CIP Common\nUINT BCD (1-word unsigned BCD) 04 Vendor Specific\nUDINT BCD (2-word unsigned BCD) 05 Vendor Specific\nULINT BCD (4-word unsigned BCD) 06 Vendor Specific\nENUM 07 Vendor Specific\nDATE_NSEC 08 Vendor Specific\nTIME_NSEC 09 Vendor Specific\nDATE_AND_TIME_NSEC 0A Vendor Specific\nTIME_OF_DAY_NSEC 0B Vendor Specific\nUnion 0C Vendor Specific\n*1. “CIP Common” indicates codes that are defined in the CIP Common Specifications. “Vendor Specific” indi-\ncates codes that are assigned by OMRON.\n7-7-2 Common Format\nThe basic format on the data line is shown below.\nData Format\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-89\n7-7\nVariable\nData\nTypes\n7\n7-7-1\nData\nType\nCodes\n7 CIP Message Communications\nUSINT Data Type Refer to Data Type Codes on page 8-43 for specific values.\nUSINT AddInfo Length Additional information: Field length in bytes\n(AddInfo) Additional information: CRC value of structure or other\nUINT Num of Element (L) information\n(H) This field exists only in the parameters for the variable\nwrite service.\nActual data\n7-7-3 Elementary Data Types\nFixed-length Byte Data\nApplicable data types: BYTE, USINT, and SINT\nData Format\nUSINT Data Type\nUSINT 00h\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\nUSINT Data\nFixed-length 2-byte Data\nApplicable data types: INT, UINT, UINT BCD, and WORD\nData Format\nUSINT Data Type\nUSINT 00h\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\nData (L)\n(H)\nFixed-length 4-byte Data\nApplicable data types: DINT, UDINT, UDINT BCD, REAL, and DWORD\nData Format\nUSINT Data Type\nUSINT 00h\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\nData (LL)\n(LH)\n(HL)\n(HH)\n7-90 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nFixed-length 8-byte Data\nApplicable data types: LINT, ULINT, ULINT BCD, LREAL, and LWORD\nData Format\nUSINT Data Type\nUSINT 00 hex\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\nData (Least-significant byte)\n:\n:\n:\n:\n:\n:\n(Most-significant byte)\nBoolean Data\nData Format\nUSINT Data Type C1 hex\nUSINT 00 hex\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\nUSINT Status 01 hex: TRUE, 00 hex : FALSE\nUSINT Forced set/reset information* 01 hex: Forced, 00 hex: Not forced\n*1. Specify 0 when writing data.\n7-7-4 Derived Data Types\nArrays and structures are handled as derived data types.\nAccessing One Member\nThe data format for accessing one element of an array or one member of a structure is the same as\nthe data format for the corresponding elementary data type.\nExample: If you specify Var[5] to access a variable defined with UINT Var[10], use the same data for-\nmat as for UINT data.\nAccessing More Than One Element at the Same Time\n Arrays\n• Accessing an Entire Array\nIf you access an array variable without specifying an element, the entire array is accessed.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-91\n7-7\nVariable\nData\nTypes\n7\n7-7-4\nDerived\nData\nTypes\n7 CIP Message Communications\nThe following data format is used.\nData Format\nUSINT Data Type Data type of array elements (D0 hex is not used.)\nUSINT 00 hex\nUINT Num of Elem (L) Gives the number of elements in the array.\n(H)\nData The actual data for the elements of the array are\n: given in order in the same format as when the\nelements are accessed individually.\nData\n• Handling Multi-dimensional Array\nElements for a multi-dimensional array are given in order from the deepest elements.\nFor example, the data is read in the following format when Var is specified for a variable defined\nwith UINT Var[2][2].\nData Format\nUSINT C7 hex Data type code for UINT\nUSINT 00 hex\nUINT Value of Var[0][0] (L)\n(H)\nUINT Value of Var[0][1] (L)\n(H)\nUINT Value of Var[1][0] (L)\n(H)\nUINT Value of Var[1][1] (L)\n(H)\nThe following data format is used for a BOOL array (using BOOL b[2][3] as an example).\nData Format\nUSINT C1 hex (data type code for BOOL)\nUSINT 00 hex\n(WORD) rsv rsv b[1][2] b[1][1] b[1][0] b[0][2] b[0][1] b[0][0]\nrsv rsv rsv rsv rsv rsv rsv rsv\n• Exceptions When Specifying the Num of Element Field\nThe following data format is used if a specification is made in the Num of Element field for a\nBOOL array. (Refer to 7-4-5 Specifying Variable Names in Request Paths on page 7-44 for infor-\nmation on the Num of Element field.) The status (TRUE/FALSE) is given in order for each ele-\nment of the BOOL variable.\nData Format\n7-92 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n7 CIP Message Communications\nUSINT Data Type C1 hex\nUSINT 00 hex\nUINT Num of Elem (L) Gives the number of elements in the array.\n(H)\nUSINT Status 01 hex: TRUE, 00 hex: FALSE\n: :\nUSINT Status\n Structure Variables\n• Accessing an Entire Structure\nIf a structure variable is specified, it is treated as an access request for all of the members of the\nstructure.\nData Format\nUSINT Data Type A0 hex (Abbreviated STRUCT)\nUSINT 02 hex\nUINT CRC (L) CRC value for the structure definition\n(H)\nUINT Num of Elem (L) 01 hex\n(H) 00 hex\n:\nData\n:\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 7-93\n7-7\nVariable\nData\nTypes\n7\n7-7-4\nDerived\nData\nTypes\n7 CIP Message Communications\n7-94 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8\nSocket Service\n8-1 Basic Knowledge on Socket Communications...........................................8-2\n8-1-1 Sockets............................................................................................................8-2\n8-1-2 Port Numbers for Socket Services..................................................................8-2\n8-2 Basic Knowledge on Protocols....................................................................8-3\n8-2-1 Differences between TCP and UDP................................................................8-3\n8-2-2 Fragmenting of Send Data..............................................................................8-4\n8-2-3 Data Receive Processing................................................................................8-6\n8-2-4 Broadcasting...................................................................................................8-9\n8-3 Overview of Built-in EtherNet/IP Port Socket Services............................8-10\n8-3-1 Overview.......................................................................................................8-10\n8-3-2 Procedure......................................................................................................8-10\n8-4 Settings Required for the Socket Services................................................8-12\n8-5 Socket Service Instructions........................................................................8-13\n8-6 Details on Using the Socket Services........................................................8-14\n8-6-1 Using the Socket Services............................................................................8-14\n8-6-2 Procedure to Use Socket Services................................................................8-14\n8-6-3 Timing Chart for Output Variables Used in Communications........................8-16\n8-6-4 UDP Sample Programming...........................................................................8-18\n8-6-5 TCP Sample Programming...........................................................................8-23\n8-7 Precautions in Using Socket Services.......................................................8-31\n8-7-1 Precautions for UDP and TCP Socket Services............................................8-31\n8-7-2 Precautions for UDP Socket Services...........................................................8-31\n8-7-3 Precautions for TCP Socket Services...........................................................8-31\n8-8 TCP/UDP Message Service.........................................................................8-33\n8-8-1 Outline of TCP/UDP Message Service..........................................................8-33\n8-8-2 Specifications of TCP/UDP Message Service...............................................8-33\n8-8-3 Settings Required for TCP/UDP Message Service.......................................8-33\n8-8-4 Command Format Specifications..................................................................8-34\n8-9 Secure Socket Services...............................................................................8-36\n8-9-1 Overview of Secure Socket Communications...............................................8-36\n8-9-2 System Configuration of Secure Socket Services.........................................8-38\n8-9-3 Procedure to Use Secure Socket Setting Function of the Sysmac Studio....8-39\n8-9-4 Executing Instructions for Secure Socket Communications..........................8-47\n8-9-5 Troubleshooting Errors in Secure Socket Communications..........................8-51\n8-9-6 Secure Socket Communications Logging.....................................................8-51\n8-9-7 Handling of Secure Socket Communications Setting Information.................8-54\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-1\n8\n8 Socket Service\n8-1 Basic Knowledge on Socket Commu-\nnications\n8-1-1 Sockets\nA socket is an interface that allows you to directly use TCP or UDP functions from the user program.\nOn a host computer (e.g., personal computer), sockets are provided in the form of a C language inter-\nface library. If you load the library, you can program communications via TCP and UDP in the user\nprogram.\nOn a UNIX computer, a socket interface is provided in the format of system calls.\nWith a built-in EtherNet/IP port, you can execute instructions in the user program by using sockets.\nThrough the communications services with sockets, you can send and receive data to and from re-\nmote nodes, i.e., between the host computer and Controllers or between Controllers.\nBuilt-in EtherNet/IP ports support UDP socket service as well as TCP socket service.\n8-1-2 Port Numbers for Socket Services\nPorts 0 to 1023 to be used for TCP/IP are reserved as well-known ports. In addition, ports 1024 to\n49151 are reserved as registered ports by the protocols that are used.\nTherefore, we recommend that you use port numbers 49152 to 65535 for applications other than the\nprotocols that are registered with the socket service.\nYou cannot specify port number 0 for the built-in EtherNet/IP port.\nFurthermore, the built-in EtherNet/IP port uses TCP/UDP ports for some applications, therefore make\nsure to avoid those ports when you set ports. Refer to A-12 TCP/ UDP Port Numbers Used for the\nBuilt-in EtherNet/IP Port on page A-95 for details on the TCP/UDP port numbers that are used by the\nbuilt-in EtherNet/IP ports.\n8-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-2 Basic Knowledge on Protocols\n8-2-1 Differences between TCP and UDP\nThe TCP and UDP functions used on socket services differ as shown below.\nTCP Communications\nThe following operations are performed each time data is sent to ensure that it reaches the destination\nnode.\nThe destination node returns an acknowledgment (ACK) when data is received normally.\nThe sending node sends the next data after ACK is returned. It resends the same data if ACK is not\nreceived within a certain length of time.\nSend data\nSend Receive\nrequest Acknowledgement (ACK) request\nResend data\nSending node If ACK is not returned Destination node\nIn TCP, the remote IP address and the remote TCP port number are specified when a request is made\nto open a socket. The variables that store the data to send are specified when the send request is\nmade.\nUDP Communications\nData is simply sent to the destination node, and neither acknowledgment nor resends are performed\nlike they are for TCP.\nTo increase the reliability of communications, some user application must be used to perform data re-\nsend processing.\nSend data\nSend\nReceive\nrequest Acknowledgement (ACK) request\n(When ACK processing is performed by user application)\nSending node Destination node\nIn UDP, the remote IP address and the remote UDP port number are not specified when a request is\nmade to open a socket. The variables that store the remote IP address, the remote UDP port number,\nand the data to send are specified when the send request is made.\n(The send data includes information on the IP address and UDP port number of the sending node.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-3\n8-2\nBasic\nKnowledge\non\nProtocols\n8\n8-2-1\nDifferences\nbetween\nTCP\nand\nUDP\n8 Socket Service\nFurthermore, once a socket is opened in UDP, communications with other remote nodes is possible\nwithout closing the socket.\nTCP Communications Procedure\nYou execute socket communications instructions in sequence to perform TCP communications for the\nbuilt-in EtherNet/IP port.\nClient Server\nSocket\nBind\nSktTCPAccept Instruction\nSocket Listen\n• Execution of Socket Functions\nSktTCPConnect Instruction Accept Socket(), Bind(), Listen(), and\nConnect SYN\n• Execution of the Socket Function Accept()\nConnect() • Timeout monitoring until Connect is\nThe connection is established by SYN ACK completed\nthe normal completion of the Instruction The connection is established by the\nSktTCPConnect instruction. completed. normal completion of the SktTCPAc-\ncept instruction.\nACK Instruction\ncompleted.\nSktSetOption Instruction\nSetopt\n• Execution of the Socket Function\nsetsoketopt()\nSktSetOption Instruction\nThe option for TCP socket is set\n• Execution of the Socket Function\nby the normal completion of the Setopt\nsetsoketopt()\nSktSetOption instruction. (Note)\nThe option for TCP socket is set\nby the normal completion of the\nSktSetOption instruction. (Note)\nSktTCPSend Instruction\nSend\n• Execution of the Socket Function\nSend() Recv SktTCPRcv Instruction\nThe data is stored in the send • Execution of Socket Function Recv()\nbuffer by the normal completion of Instruction • Timeout monitoring until data is\nthe SktTCPSend instruction. completed. received from the remote node\nACK\nWriting the received data to the variable\nis completed by the normal completion\nof the SktTCPRcv instruction.\nSktClose Instruction Close\n• Execution of the Socket Function FIN\nClose()\nThe acknowledgment (ACK) of Socket interface\nFIN from the remote node is\nreceived by the normal comple- ACK Packets sent by the TCP/IP layer\ntion of the SktClose instruction.\nPackets sent by higher layers\nHowever, RST (not FIN) is sent if Instruction\nthe Linger Option is specified. completed.\nNoteSet the socket option as required. Refer to the NJ/NX-series Instructions Reference Manual (Cat. No.\nW502) for the socket option.\n8-2-2 Fragmenting of Send Data\nThe receive buffer for the built-in EtherNet/IP port is a maximum of 9,000 bytes per socket handle. If\nany data that is larger than 9,000 bytes is received, the data is discarded.\n8-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nUp to 2,000 bytes can be received for a single request. In this case, the data is sent in fragments as\ndescribed below.\nUsing TCP\nThe following figure shows what occurs when data is sent in fragments in TCP communications."}
+{"question": "A send request is sent from the user program at the sending node. It specifies a variable with a", "answer": "data length of 2,000 bytes."}
+{"question": "The built-in EtherNet/IP port separates the send data into 1,024 bytes as data A and 976 bytes as", "answer": "data B."}
+{"question": "After data A is received, the remaining data B is received.", "answer": "Sending node (Controller) Receiving node (host computer)\nUser program Built-in Receiving node User program\nEtherNet/IP port\nEthernet line\n(4) Receive request\n(1) Send request (2) Fragmenting (3)\nData A and\ndata B are\n2,000 bytes 1,024 bytes 2,000 bytes\nsent in\nsuccession.\nOriginal data Data A Data A Data A\n1,024 bytes\n(5) Receives remaining 976 bytes.\n2,000 bytes\nData B Data B Data B\n976 bytes 976 bytes\n(6) Receive request\n(request for 2,000 bytes)\nData is delivered to the user program in a fragmented form in TCP communications, as shown\nabove.\nThe size of received data must be checked to confirm that all the data was received before the\nnext receive request is made. (You can use the RecvSize output variable of the socket receive\nrequest instruction to check the received data.)\nAdditional Information\nIf TCP is used to send data to a different segment, the data is separated into 536-byte frag-\nments.\nUsing UDP\nThe following figure shows what occurs when data is sent in fragments in UDP communications."}
+{"question": "A send request is sent from the user program at the sending node. It specifies a variable with a", "answer": "data length of 2,000 bytes.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-5\n8-2\nBasic\nKnowledge\non\nProtocols\n8\n8-2-2\nFragmenting\nof\nSend\nData\n8 Socket Service"}
+{"question": "The built-in EtherNet/IP port separates the send data into 1,472 bytes as data A and 528 bytes as", "answer": "data B."}
+{"question": "Data A and data B are joined and restored as the original send data, and the data is passed to the", "answer": "user program.\nSending node (Controller) Receiving node (host computer)\nUser program Built-in Receiving node User program\nEtherNet/IP port\nEthernet line\n(1) Send request (2) Fragmenting (3)\nData A and\ndata B are\n2,000 bytes 1,472 bytes\nseparated\nand sent.\nOriginal data Data A\n(4) Receive request\n2,000 bytes\nData B Data A Data B\n528 bytes\nSince UDP communications are performed in datagram units as shown above, send data is re-\nstored in the original data format before it is passed to the user program.\n8-2-3 Data Receive Processing\nThis section describes data receive processing for TCP and UDP.\nTCP Receive Processing\nIn TCP communications, receive data stored in the receive buffer (a maximum of 9,000 bytes) can be\ndivided to be received.\nThus, if received data is larger than the maximum size of data that can be received with one data re-\nquest (2,000 bytes), more than one receive request can be sent to receive all of the data.\nIf the data in the receive buffer is smaller than the size of the variable specified by the receive request,\nthe entire receive data is received.\nExample) Receiving 3,000 Bytes of Receive Data in Two Sections"}
+{"question": "The data is divided to be sent in two sends from the sending node, and is stored in the receive", "answer": "buffer."}
+{"question": "More than one receive request is used to receive all of the send data.", "answer": "8-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nSending node (host computer) Receiving node (Controller)\nUser program Built-in EtherNet/IP port User program\n(1) Data received to\nEthernet line receive buffer. (2) The data is received in\ntwo sections.\nReceive buffer\n(9,000 bytes)\n1st send 1st receive request\nrequest (Request for 1,000 bytes)\n1,000 bytes Data A Data A\nData A 1,000 bytes\n2,000 bytes Data B Data B\n2nd send\nrequest\n2nd receive request\n3,000 bytes (request for 2,000 bytes)\nData B 2,000 bytes\nUDP Receive Processing\nIn UDP communications, receive data stored in the receive buffer (a maximum of 9,000 bytes) cannot\nbe divided to be received.\nTherefore, if data is sent for one send request, it must be received with one receive request.\nThe following must be considered to receive data at the receiving node.\n• When the Size of the Variable Specified in the Receive Request Is Smaller Than the Data Sent with\nthe Send Request\nIf receive data exceeds the size of the variable specified in the receive request, the excess of the\ndata is discarded.\nIf the data in the receive buffer is smaller than the size of the variable specified in the receive re-\nquest, the entire receive data is received.\nExample 1: 1,000-Byte Receive Request Is Made for 2,000-Byte Data"}
+{"question": "The data is divided to be sent in two sends from the sending node, and is stored in the receive", "answer": "buffer."}
+{"question": "If a 1,000-byte receive request is made for the first send, the remaining 1,000 bytes of the data is", "answer": "discarded."}
+{"question": "If the next receive request is made for 2,000 bytes, the data for the second send is all received.", "answer": "NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-7\n8-2\nBasic\nKnowledge\non\nProtocols\n8\n8-2-3\nData\nReceive\nProcessing\n8 Socket Service\nSending node (host computer) Receiving node (Controller)\nUser program Built-in EtherNet/IP port User program\n(1) Data received to\nEthernet line\nreceive buffer.\n(2) 1st receive\nReceive buffer request (request\n(9,000 bytes) for 1,000 bytes)\n1st send\nrequest Data A (upper bytes) Data A (upper bytes) 1,000 bytes\n2,000 bytes Data A\nData A (lower bytes)\nThe remaining\n2,000 bytes Data B Data B data is discarded.\n2nd send\nData A (lower bytes) 1,000 bytes\nrequest\n4,000 bytes (3) 2nd receive\nrequest (request\nfor 2,000 bytes)\nData B 2,000 bytes\n• When Only One Receive Request Is Made for Data Sent for Multiple Send Requests\nIf data is sent for multiple sent requests, you cannot receive the entire data with one receive request\nregardless of the size of the data.\nExample 2: 1,000-Byte Receive Request Is Made for 200-Byte Data Sent for Two Send Requests"}
+{"question": "The data is divided to be sent in two sends from the sending node, and is stored in the receive", "answer": "buffer."}
+{"question": "Even if a receive request is made for 2,000 bytes, only 100 bytes of the data is received as re-", "answer": "quested with the first send request.\nSending node (host computer) Receiving node (Controller)\nUser program Built-in EtherNet/IP port User program\n(1) Data received to\nEthernet line\nreceive buffer.\n(2) 1st receive request\nReceive buffer (request for 1,000\n(9,000 bytes) bytes)\n1st send\nrequest\n100 bytes Data A Data A Data A\n100 bytes Data B Data B 100 bytes\n2nd send\nrequest You can receive the rest\nof the data with another\n200 bytes\nreceive request.\nData B\n8-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-2-4 Broadcasting\nIf you specify a broadcast address as the destination IP address for a UDP socket, data can be broad-\ncast to all nodes on the network to which the host for the EtherNet/IP port belongs.\nIf there is a router on the network, packets are not sent beyond the router.\nYou can broadcast up to 1,472 bytes of data. Data larger than the maximum size cannot be broadcast.\nYou can specify either of the two following types of broadcast addresses.\n• Local Broadcast\nIf no destination IP address is specified, the following IP address is specified automatically.\nNetwork segment: The network segment of the local IP address is set.\nHost segment: All bits are set to 1.\n• Global Broadcast\nSpecify this type when the IP address of the local node or the subnet to which the local node be-\nlongs is unknown.\nAs shown below, every bit of the 32-bit address is set to 1."}
+{"question": "255.255.255", "answer": "NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-9\n8-2\nBasic\nKnowledge\non\nProtocols\n8\n8-2-4\nBroadcasting\n8 Socket Service\n8-3 Overview of Built-in EtherNet/IP Port\nSocket Services\n8-3-1 Overview\nSocket services on the built-in EtherNet/IP port are used to exchange data between Controllers and\ngeneral-purpose applications that do not support CIP message communications.\nThe Controller requests the socket service from the user program.\nGeneral purpose (non-CIP communications) application\nIntranet\nAt the host, system calls of sockets, e.g.,\nfrom a C language interface library, can\nbe used to directly use TCP/IP or UDP/IP\nto access Controller data.\nEthernet\nBuilt-in EtherNet/IP port\nData\nAt the Controller, socket instructions can\nbe executed in the user program to\ndirectly use UDP or TCP to exchange\ndata with the host computer.\nOverview of Socket Services with Socket Service Instructions\nYou can use socket services by executing socket service instructions.\nThe maximum total number of UDP and TCP sockets that you can use is given in the following table.\nMaximum number of sockets\nNX-series CPU Unit NJ-series CPU Unit\nUDP/TCP\nOther than the Unit version Unit version\nNX502 NX102\nleft. 1.00 to 1.02 1.03 or later\nUDP socket Total of 60 sock- Total of 60 sock- Total of 30 sock- Total of 16 sock- Total of 30 sock-\nservice ets ets ets ets ets\nTCP socket\nservice\nSecure socket Not supported\nservice*1\n*1. An NX102-££00 CPU Unit with unit version 1.46 or later or an NX102-££20 CPU Unit with unit version"}
+{"question": "37 or later and Sysmac Studio version 1.46 or higher are required to use the secure socket services.", "answer": "An NX1P2-££££££ CPU Unit with unit version 1.46 or later and Sysmac Studio version 1.46 or higher\nare required.\nAn NX502-££££ CPU Unit with unit version 1.60 or later and Sysmac Studio version 1.54 or higher are\nrequired.\n8-3-2 Procedure\n1 Make the settings that are required for socket services.\nRefer to 8-4 Settings Required for the Socket Services on page 8-12.\n8-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n↓\n2 Execute the socket service instructions from the user program.\nRefer to 8-5 Socket Service Instructions on page 8-13.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-11\n8-3\nOverview\nof\nBuilt-in\nEtherNet/IP\nPort\nSocket\nServices\n8\n8-3-2\nProcedure\n8 Socket Service\n8-4 Settings Required for the Socket\nServices\nMake the following settings in the Unit Setup to use the socket services.\nSysmac Studio\nUnit Settings Tab Setting Setting conditions\nPage\nSetting Local IP Address Required\nSubnet Mask Required\nTCP/IP Keep Alive Optional (Change when the default setting of 5 minutes is un-\nacceptable.)\nLinger Option Optional\nAdditional Information\nMake this setting in the TCP/IP Settings Display. Refer to 4-1 TCP/IP Settings Display on\npage 4-2 for information on the TCP/IP Settings Display.\n8-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-5 Socket Service Instructions\nYou can use the following socket service instructions for socket services.\nRefer to the NJ/NX-series Instructions Reference Manual (Cat. No. W502) for information on the sock-\net service instructions.\nUDP/TCP Instruction Socket service\nUDP sockets SktUDPCreate Create UDP Socket instruction\nSktUDPRcv UDP Socket Receive instruction\nSktUDPSend UDP Socket Send instruction\nTCP sockets SktTCPAccept Accept TCP Socket instruction\nSktTCPConnect Connect TCP Socket instruction\nSktTCPRcv TCP Socket Receive instruction\nSktTCPSend TCP Socket Send instruction\nSktGetTCPStatus Read TCP Socket Status instruction\nServices for both UDP SktClose Close TCP/UDP Socket instruction\nand TCP sockets SktClearBuf Clear TCP/UDP Socket Receive Buffer instruction\nSktSetOption Set TCP Socket Option instruction\nPrecautions for Correct Use\nYou can execute a maximum of 32 socket service instructions (64 for NX502 and NX102) at the\nsame time.\nPerform exclusive control in the user program so that 33 or more socket instructions (65 or\nmore for NX502 and NX102) will not be executed at the same time.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-13\n8-5\nSocket\nService\nInstructions\n8\n8 Socket Service\n8-6 Details on Using the Socket Services\n8-6-1 Using the Socket Services\nThe following table shows the maximum total number of TCP and UDP sockets for the built-in Ether-\nNet/IP port.\nMaximum number of sockets\nNX-series CPU Unit NJ-series CPU Unit\nUDP/TCP\nOther than the Unit version Unit version\nNX502 NX102\nleft. 1.00 to 1.02 1.03 or later\nUDP socket Total of 60 sockets Total of 30 sock- Total of 16 sock- Total of 30 sock-\nservice ets ets ets\nTCP socket\nservice\nTo use these sockets for communications, special ST instructions for sockets are executed to perform\nthe following processes.\nOpen processing: This process places the socket in a usable state. This is the first process to use socket\nservices. With TCP, open processing is performed until a connection is established.\nClose processing: This process ends the use of the socket. With TCP, it closes the connection.\nSend processing This process sends data from the socket.\nReceive processing This process receives data from the socket.\nClear processing: This process clears the receive buffer to remove data received from the remote node.\n8-6-2 Procedure to Use Socket Services\nYou execute special instructions for sockets in sequence to use the socket services according to the\nprocedure shown below.\nUse the values of the output variables for each instruction to confirm that each instruction is normally\ncompleted.\n8-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nTCP\nOpening a Connection Accepting a Connection\nExecute SktTCPConnect instruction. Execute SktTCPAccept instruction.\nError End\nCheck error details based on\nOutput variable: Error = TRUE\nInstruction end normally? the error code and take\nsuitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nSend Processing\nExecute SktTCPSend instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nNormal End Output variable: ErrorID\nOutput variable: Done = TRUE\nChecking TCP Status\nExecute SktGetTCPSatus\ninstruction.\nOutput variable BufferDataByte\n≤ Number of send bytes\nAll data received?\nOutput variable BufferDataByte\n≥ Number of send bytes\nReceive Processing\nExecute SktTCPRcv instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nClose Processing\nExecute SktClose instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nNormal End Output variable: ErrorID\nOutput variable: Done = TRUE\nEnd socket communications.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-15\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-2\nProcedure\nto\nUse\nSocket\nServices\n8 Socket Service\nUDP\nOpen Processing\nExecute SktUDPCreate instruction.\nError End\nOutput variable: Error = TRUE Check error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nSend Processing\nExecute SktUDPSend instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nReceive Processing\nExecute SktUDPRcv instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nClose Processing\nExecute SktClose instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take\nsuitable actions.\nNormal End Output variable: ErrorID\nOutput variable: Done = TRUE\nEnd socket communications.\n8-6-3 Timing Chart for Output Variables Used in Communications\nOutput Variable Operation and Timing\nYou can monitor the values of the output variables to determine the status throughout instruction exe-\ncution.\nThe following timing chart shows the operation of the output variables.\n8-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n(3) (4) (5) (8)\nExecute\n(1)\nBusy\n(Executing)\nChanges to FALSE\nbecause Execute\nchanges to FALSE.\nDone Changes to FALSE\nbecause Execute\nchanges to FALSE.\nError\n(6)\n(2) (7)\nErrorID 0x0000 0x1234"}
+{"question": "After the results of instruction execution are stored in the output variables, Done changes to TRUE", "answer": "and Busy changes to FALSE."}
+{"question": "If an error occurs, several retries are attempted internally. The error code in ErrorID is not updated", "answer": "during the retries."}
+{"question": "When a communications error occurs, Error changes to TRUE and the ErrorID is stored. Also,", "answer": "Busy and Done change to FALSE."}
+{"question": "When Execute changes to FALSE, Error changes to FALSE.", "answer": "Precautions for Correct Use\nIf Execute changes back to FALSE before Done changes to TRUE, Done stays TRUE for only\none task period. (Example 1)\nIf you want to see if Done is TRUE at any time, make sure to keep Execute TRUE until you\nconfirm that Done is TRUE.\nIf Execute is TRUE until Done changes to TRUE, Done stays TRUE until Execute changes to\nFALSE. (Example 2)\nExample 1 Example 2\nExecute Execute When Execute\nChanges to changes to\nFALSE in next Busy FALSE, Done\nBusy task period. (Executing) returns to FALSE.\n(Executing)\nDone Done\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-17\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-3\nTiming\nChart\nfor\nOutput\nVariables\nUsed\nin\nCommunications\n8 Socket Service\n8-6-4 UDP Sample Programming\nIn this sample, the UDP socket service is used for data communications between the NJ/NX-series\nController and a remote node.\nIn this example, programming is also required in the remote node. The order of sending and receiving\nis reversed in comparison with the above procedure.\nIP address: 192.168.250.1 IP address: 192.168.250.2\nUDP port number: 6000 UDP port number: 6001\nData sent.\nRemote node\nData received.\nBuilt-in EtherNet/IP Port\nEthernet line\nLocal Node Programming\nThe processing procedure at the local node is as follows:\n1\nThe SktUDPCreate instruction is used to make a request to create a UDP socket.\n2\nThe SktUDPSend instruction is used to make a send request. The data in SendSocketDat[] is\nsent.\n3\nThe SktUDPRcv instruction is used to make a receive request. The received data is stored in\nRcvSocketDat[].\n4\nThe SktClose instruction is used to close the socket.\nST\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nTrigger BOOL False Execution\ncondition\nDoSendAndRcv BOOL False Processing\nStage INT 0 Status\nchange\nRcvSocketDat ARRAY[0..1999] OF [2000(16#0)] Received\nBYTE data\nWkSocket _sSOCKET (Handle:=0, SrcAdr:=(Port- Socket\nNo:=0,IpAdr:=''), DstAdr:=(Port-\nNo:=0,IpAdr:=''))\nSendSocketDat ARRAY[0..1999] OF [2000(16#0)] Send data\nBYTE\nSktUDPCreate_instance SktUDPCreate\nSktUDPSend_instance SktUDPSend\n8-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nSktUDPRcv_instance SktUDPRcv\nSktClose_instance SktClose\nExter-\nnal vari- Variable Data type Constant Comment\nable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnli-\nneSta (Port1 Online) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port\nwhich is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE.\nIF((Trigger=TRUE) AND(DoSendAndRcv=FALSE) AND (_EIP_EtnOnlineSta=TRUE))THEN\nDoSendAndRcv :=TRUE;\nStage :=INT#1;\nSktUDPCreate_instance(Execute:=FALSE); // Initialize instance.\nSktUDPSend_instance( // Initialize instance.\nExecute :=FALSE,\nSendDat :=SendSocketDat[0]); // Dummy\nSktUDPRcv_instance( // Initialize instance.\nExecute :=FALSE,\nRcvDat :=RcvSocketDat[0]); // Dummy\nSktClose_instance(Execute:=FALSE); // Initialize instance.\nEND_IF;\nIF (DoSendAndRcv=TRUE) THEN\nCASE Stage OF\n1 : // Request to create a s\nocket.\nSktUDPCreate_instance(\nExecute :=TRUE,\nSrcUdpPort :=UINT#6000, // Local UDP port number\nSocket =>WkSocket); // Socket\nIF (SktUDPCreate_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\nELSIF (SktUDPCreate_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Send request\nWkSocket.DstAdr.PortNo :=UINT#6001;\nWkSocket.DstAdr.IpAdr :='192.168.250.2';\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-19\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-4\nUDP\nSample\nProgramming\n8 Socket Service\nSktUDPSend_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nSendDat :=SendSocketDat[0], // Send data\nSize :=UINT#2000); // Send data size\nIF (SktUDPSend_instance.Done=TRUE) THEN\nStage :=INT#3; // Normal end\nELSIF (SktUDPSend_instance.Error=TRUE) THEN\nStage :=INT#20; // Error end\nEND_IF;\n3 : // Receive request\nSktUDPRcv_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nTimeOut :=UINT#0, // Timeout value\nSize :=UINT#2000, // Receive data size\nRcvDat :=RcvSocketDat[0]); // Receive data\nIF (SktUDPRcv_instance.Done=TRUE) THEN\nStage :=INT#4; // Normal end\nELSIF (SktUDPRcv_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n4 : // Requestto close the s\nocket\nSktClose_instance(\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nIF (SktClose_instance.Done=TRUE) THEN\nStage :=INT#0; // Normal end\nELSIF (SktClose_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\n0 : // Normal end\nDoSendAndRcv :=FALSE;\nTrigger :=FALSE;\nELSE // Interrupted by error.\nDoSendAndRcv :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\n8-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nRemote Node Programming\nThe processing procedure at the remote node is as follows:\n1\nThe SktUDPCreate instruction is used to make a request to create a UDP socket.\n2\nThe SktUDPRcv instruction is used to make a receive request. The received data is stored in\nRcvSocketDat[].\n3\nThe SktUDPSend instruction is used to make a send request. The data in SendSocketDat[] is\nsent.\n4\nThe SktClose instruction is used to close the socket.\nST\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nTrigger BOOL False Execution\ncondition\nDoSendAndRcv BOOL False Processing\nStage INT 0 Status\nchange\nRcvSocketDat ARRAY[0..1999] OF [2000(16#0)] Received\nBYTE data\nWkSocket _sSOCKET (Handle:=0, SrcAdr:=(PortNo:=0, Socket\nIpAdr:=''), DstAdr:=(PortNo:=0,\nIpAdr:=''))\nSendSocketDat ARRAY[0..1999] OF [2000(16#0)] Send data\nBYTE\nSktUDPCreate_in- SktUDPCreate\nstance\nSktUDPSend_instance SktUDPSend\nSktUDPRcv_instance SktUDPRcv\nSktClose_instance SktClose\nExternal\nVariable Data type Constant Comment\nvariable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnli-\nneSta (Port1 Online) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port\nwhich is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE.\nIF((Trigger=TRUE) AND (DoSendAndRcv=FALSE) AND (_EIP_EtnOnlineSta=TRUE))THEN\nDoSendAndRcv :=TRUE;\nStage :=INT#1;\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-21\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-4\nUDP\nSample\nProgramming\n8 Socket Service\nSktUDPCreate_instance(Execute:=FALSE); // Initialize instance.\nSktUDPSend_instance( // Initialize instance.\nExecute :=FALSE,\nSendDat :=SendSocketDat[0]); // Dummy\nSktUDPRcv_instance( // Initialize instance.\nExecute :=FALSE,\nRcvDat :=RcvSocketDat[0]); // Dummy\nSktClose_instance(Execute:=FALSE); // Initialize instance.\nEND_IF;\nIF (DoSendAndRcv=TRUE) THEN\nCASE Stage OF\n1 : // Request to create a s\nocket\nSktUDPCreate_instance(\nExecute :=TRUE,\nSrcUdpPort :=UINT#6001, // Local UDP port number\nSocket =>WkSocket); // Socket\nIF (SktUDPCreate_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\nELSIF (SktUDPCreate_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Receive request\nSktUDPRcv_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nTimeOut :=UINT#0, // Timeout value\nSize :=UINT#2000, // Receive data size\nRcvDat :=RcvSocketDat[0]); // Receive data\nIF (SktUDPRcv_instance.Done=TRUE) THEN\nStage :=INT#3; // Normal end\nELSIF (SktUDPRcv_instance.Error=TRUE) THEN\nStage :=INT#20; // Error end\nEND_IF;\n3 : // Send request\nWkSocket.DstAdr.PortNo :=UINT#6000;\nWkSocket.DstAdr.IpAdr :='192.168.250.1';\nSktUDPSend_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nSendDat :=SendSocketDat[0], // Send data\nSize :=UINT#2000); // Send data size\n8-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nIF (SktUDPSend_instance.Done=TRUE) THEN\nStage :=INT#4; // Normal end\nELSIF (SktUDPSend_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n4 : // Request to close the\nsocket\nSktClose_instance(\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nIF (SktClose_instance.Done=TRUE) THEN\nStage :=INT#0; // Normal end\nELSIF (SktClose_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\n0 : // Normal end\nDoSendAndRcv :=FALSE;\nTrigger :=FALSE;\nELSE // Interrupted by error.\nDoSendAndRcv :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\n8-6-5 TCP Sample Programming\nIn this sample, the TCP socket service is used for data communications between the NJ/NX-series\nController and a remote node.\nIn this example, programming is also required in the remote node. The order of sending and receiving\nis reversed in comparison with the above procedure.\nIP address: 192.168.250.1 IP address: 192.168.250.2\nTCP port number: Automatically assigned. TCP port number: 6000\nData sent.\nRemote node\nData received.\nBuilt-in EtherNet/IP Port\nEthernet line\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-23\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-5\nTCP\nSample\nProgramming\n8 Socket Service\nLocal Node Programming\nThe processing procedure at the local node is as follows:\n1\nThe SktTCPConnect instruction is used to make a request for connection to the TCP port on\nthe remote node.\n2\nThe SktClearBuf instruction is used to clear the receive buffer of a TCP socket.\n3\nThe SktGetTCPStatus instruction is used to read the status of the TCP socket.\n4\nThe SktTCPSend instruction is used to make a send request The data in SendSocketDat[] is\nsent.\n5\nThe SktTCPRcv instruction is executed to make a receive request. The received data is stored\nin RcvSocketDat[].\n6\nThe SktClose instruction is used to close the socket.\nST\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nTrigger BOOL False Execution\ncondition\nDoTCP BOOL False Processing\nStage INT 0 Status\nchange\nRcvSocketDat ARRAY[0..1999] OF [2000(16#0)] Received\nBYTE data\nWkSocket _sSOCKET (Handle:=0, SrcAdr:=(PortNo:=0, Socket\nIpAdr:=''), DstAdr:=(PortNo:=0,\nIpAdr:=''))\nSendSocketDat ARRAY[0..1999] OF [2000(16#0)] Send data\nBYTE\nSktTCPConnect_in- SktTCPConnect\nstance\nSktClearBuf_instance SktClearBuf\nSktGetTCPStatus_in- SktGetTCPStatus\nstance\nSktTCPSend_instance SktTCPSend\nSktTCPRcv_instance SktTCPRcv\nSktClose_instance SktClose\n8-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nExternal\nVariable Data type Constant Comment\nvariable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnli-\nneSta (Port1 Online) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port\nwhich is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE.\nIF ((Trigger=TRUE) AND (DoTCP=FALSE) AND (_EIP_EtnOnlineSta=TRUE)) THEN\nDoTCP :=TRUE;\nStage :=INT#1;\nSktTCPConnect_instance(Execute:=FALSE); // Initialize instance.\nSktClearBuf_instance(Execute:=FALSE); // Initialize instance.\nSktGetTCPStatus_instance(Execute:=FALSE); // Initialize instance.\nSktTCPSend_instance( // Initialize instance.\nExecute :=FALSE,\nSendDat :=SendSocketDat[0]); // Dummy\nSktTCPRcv_instance( // Initialize instance.\nExecute :=FALSE,\nRcvDat :=RcvSocketDat[0]); // Dummy\nSktClose_instance(Execute:=FALSE); // Initialize instance.\nEND_IF;\nIF (DoTCP=TRUE) THEN\nCASE Stage OF\n1 : // Connection request\nSktTCPConnect_instance(\nExecute :=TRUE,\nSrcTcpPort :=UINT#0, // Local TCP port number\n: Automatically assigned\nDstAdr :='192.168.250.2', // Remote IP address\nDstTcpPort :=UINT#6000, // Destination TCP port\nnumber\nSocket =>WkSocket); // Socket\nIF (SktTCPConnect_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\nELSIF (SktTCPConnect_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Receive buffer clear\nSktClearBuf_instance(\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-25\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-5\nTCP\nSample\nProgramming\n8 Socket Service\nIF (SktClearBuf_instance.Done=TRUE) THEN\nStage :=INT#3; //Normal end\nELSIF (SktClearBuf_instance.Error=TRUE) THEN\nStage :=INT#20; //Error end\nEND_IF;\n3 : // Status read request\nSktGetTCPStatus_instance(\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nIF (SktGetTCPStatus_instance.Done=TRUE) THEN\nStage :=INT#4; // Normal end\nELSIF (SktGetTCPStatus_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n4 : // Send request\nSktTCPSend_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nSendDat :=SendSocketDat[0], // Send data\nSize :=UINT#2000); // Send data size\nIF (SktTCPSend_instance.Done=TRUE) THEN\nStage :=INT#5; // Normal end\nELSIF (SktTCPSend_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\n5 : // Receive request\nSktTCPRcv_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nTimeOut :=UINT#0, // Timeout value\nSize :=UINT#2000, // Receive data size\nRcvDat :=RcvSocketDat[0]); // Receive data\nIF (SktTCPRcv_instance.Done=TRUE) THEN\nStage :=INT#6; // Normal end\nELSIF (SktTCPRcv_instance.Error=TRUE) THEN\nStage :=INT#50; // Error end\nEND_IF;\n6 : // Request to close the\nsocket\nSktClose_instance(\n8-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nIF (SktClose_instance.Done=TRUE) THEN\nStage :=INT#0; // Normal end\nELSIF (SktClose_instance.Error=TRUE) THEN\nStage :=INT#60; // Error end\nEND_IF;\n0 : // Normal end\nDoTCP :=FALSE;\nTrigger :=FALSE;\nELSE // Interrupted by error.\nDoTCP :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\nRemote Node Programming\nThe processing procedure at the remote node is as follows:\n1\nThe SktTCPAccept instruction is used to make a request to accept the connection on the TCP\nsocket.\n2\nThe SktTCPRcv instruction is used to make a receive request. The received data is stored in\nRcvSocketDat[].\n3\nThe SktTCPSend instruction is used to make a send request The data in SendSocketDat[] is\nsent.\n4\nThe SktClose instruction is used to close the socket.\nST\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nTrigger BOOL False Execution\ncondition\nDoTCP BOOL False Processing\nStage INT 0 Status\nchange\nRcvSocketDat ARRAY[0..1999] OF [2000(16#0)] Receive da-\nBYTE ta\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-27\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-5\nTCP\nSample\nProgramming\n8 Socket Service\nInternal\nvaria- Variable Data type Initial value Comment\nbles\nWkSocket _sSOCKET (Handle:=0, SrcAdr:=(PortNo:=0, Socket\nIpAdr:=''), DstAdr:=(PortNo:=0,\nIpAdr:=''))\nSendSocketDat ARRAY[0..1999] OF [2000(16#0)] Send data\nBYTE\nSktTCPAccept_instance SktTCPAccept\nSktTCPSend_instance SktTCPSend\nSktTCPRcv_instance SktTCPRcv\nSktClose_instance SktClose\nExternal\nVariable Data type Constant Comment\nvariable\n_EIP_EtnOnlineSta*1 BOOL Online\n*1. For an NX701 CPU Unit, NX502 CPU Unit, and NX102 CPU Unit, replace the variable with _EIP1_EtnOnli-\nneSta (Port1 Online) or _EIP2_EtnOnlineSta (Port2 Online), depending on the built-in EtherNet/IP port\nwhich is used.\nFor an NX1P2 CPU Unit, replace the variable with _EIP1_EtnOnlineSta (Port1 Online).\n// Start sequence when Trigger changes to TRUE.\nIF ((Trigger=TRUE) AND (DoTCP=FALSE) AND (_EIP_EtnOnlineSta=TRUE)) THEN\nDoTCP :=TRUE;\nStage :=INT#1;\nSktTCPAccept_instance(Execute:=FALSE); // Initialize instance.\nSktTCPSend_instance( // Initialize instance.\nExecute :=FALSE,\nSendDat :=SendSocketDat[0]); // Dummy\nSktTCPRcv_instance( // Initialize instance.\nExecute :=FALSE,\nRcvDat :=RcvSocketDat[0]); // Dummy\nSktClose_instance(Execute:=FALSE); // Initialize instance.\nEND_IF;\nIF (DoTCP=TRUE) THEN\nCASE Stage OF\n1 : // Request to accept a s\nocket connection\nSktTCPAccept_instance(\nExecute :=TRUE,\nSrcTcpPort :=UINT#6000, // Local TCP port number\nTimeOut :=UINT#0, // Timeout value\nSocket =>WkSocket); // Socket\nIF (SktTCPAccept_instance.Done=TRUE) THEN\nStage :=INT#2; // Normal end\n8-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nELSIF (SktTCPAccept_instance.Error=TRUE) THEN\nStage :=INT#10; // Error end\nEND_IF;\n2 : // Receive request\nSktTCPRcv_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nTimeOut :=UINT#0, // Timeout value\nSize :=UINT#2000, // Receive data size\nRcvDat :=RcvSocketDat[0]); // Receive data\nIF (SktTCPRcv_instance.Done=TRUE) THEN\nStage :=INT#3; // Normal end\nELSIF (SktTCPRcv_instance.Error=TRUE) THEN\nStage :=INT#20; // Error end\nEND_IF;\n3 : // Send request\nSendSocketDat:=RcvSocketDat;\nSktTCPSend_instance(\nExecute :=TRUE,\nSocket :=WkSocket, // Socket\nSendDat :=SendSocketDat[0], // Send data\nSize :=UINT#2000); // Send data size\nIF (SktTCPSend_instance.Done=TRUE) THEN\nStage :=INT#4; // Normal end\nELSIF (SktTCPSend_instance.Error=TRUE) THEN\nStage :=INT#30; // Error end\nEND_IF;\n4 : // Request to close the\nsocket\nSktClose_instance(\nExecute :=TRUE,\nSocket :=WkSocket); // Socket\nIF (SktClose_instance.Done=TRUE) THEN\nStage :=INT#0; // Normal end\nELSIF (SktClose_instance.Error=TRUE) THEN\nStage :=INT#40; // Error end\nEND_IF;\n0 : // Normal end\nDoTCP :=FALSE;\nTrigger :=FALSE;\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-29\n8-6\nDetails\non\nUsing\nthe\nSocket\nServices\n8\n8-6-5\nTCP\nSample\nProgramming\n8 Socket Service\nELSE // Interrupted by error\nDoTCP :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\n8-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-7 Precautions in Using Socket Services\n8-7-1 Precautions for UDP and TCP Socket Services\n• Communications processing are sometimes delayed when multiple functions of the built-in\nEtherNet/IP port are used simultaneously or due to the contents of the user program.\n• Communications efficiency is sometimes reduced by high communications traffic on the network\nline.\n• The close processing for a close request instruction discards all of the buffered send and receive\ndata for the socket.\nFor example, send data for a send request which is issued immediately before the close processing\nmay not be sent.\n• After a socket is open, the built-in EtherNet/IP port provides a receive buffer of 9,000 bytes per TCP\nsocket and 9,000 bytes per UDP socket to enable data to be received at any time.\nIf the receive buffer is full, data received by the socket is discarded. Make sure that the user applica-\ntion constantly issues receive requests to prevent the internal buffer from becoming full.\n• If the Use Option is selected for Packet Filter of the built-in EtherNet/IP port, make sure to permit\npackets to be used for socket services. If they are not permitted, packets used by the socket serv-\nices cannot be received. For the details on the settings, refer to Packet Filter on page 4-8.\n8-7-2 Precautions for UDP Socket Services\n• The destination IP address can be set to a broadcast address for a UDP socket to broadcast data to\nall nodes on the network.\nHowever, in this case, the maximum length of send data is 1,472 bytes.\nData divided into multiple fragments (1,473 bytes or more in UDP) cannot be sent.\n• UDP sockets do not perform controls intended to secure the reliability of communications, such as\nconfirming if the send data is received. To improve the reliability of communications when you use\nUDP sockets, make sure the user program confirms that data is sent and resends the data when\nnecessary.\n8-7-3 Precautions for TCP Socket Services\n• If the TCP socket is closed on the remote node without warning during communications (i.e., if the\nconnection is closed), the socket at the local node must also be closed.\nYou can use the Read TCP Socket Status instruction (SktGetTCPstatus) to see if the connection is\nclosed.\nImmediately close the socket at the local node if the TCP socket at the remote node is closed.\n• If the remote node's TCP socket closes without warning, the data to send may remain in the buffer\nat the local node. The remaining data is discarded in the local node's TCP close processing.\nThe steps that are required in applications to avoid this include sending data from the sending node\nthat permits closing and closing the socket only after checking the remote node.\n• While open processing is performed for a TCP socket, a port that was closed first cannot be opened\nagain for 60 seconds from the time the close processing is performed for the remote socket.\nHowever, this is not true if you specified 0 (automatic assignment by the Unit) as the port for the\nSktTCPConnect instruction.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-31\n8-7\nPrecautions\nin\nUsing\nSocket\nServices\n8\n8-7-1\nPrecautions\nfor\nUDP\nand\nTCP\nSocket\nServices\n8 Socket Service\n• You can open a connection by performing Connect from one socket to another socket that is open\nwith Accept. Connections cannot be opened if you attempt Connect from one socket to another\nsocket which is open with Connect.\nConnections cannot be opened either if you attempt Accept from one socket to another socket\nwhich is open with Accept.\nFurthermore, you cannot use more than one Connect from another node to open multiple connec-\ntions to a single TCP socket which is open with Accept on the build-in EtherNet/IP port.\n• You can use the keep-alive function for TCP sockets at the built-in EtherNet/IP port.\nThe keep alive function checks whether a connection is normally established when no data is sent\nor received for a certain period on the communications line where the connection was established.\nThe built-in EtherNet/IP port responds to checks from other nodes even if keep alive is not specified.\n• For TCP sockets, the send data is resent up to 12 times if an acknowledgment (ACK) from the re-\nmote node is not received. The resend interval increases every resend in a range from one second\nto 64 seconds.\n• For TCP sockets, a connection request (SYN) is sent by performing an open connection. SYN is re-\nsent up to four times if an acknowledgment (SYN + ACK) from the remote node is not received. An\nerror will occur if SYN + ACK is not received yet even after 75 seconds has elapsed since the open\nprocessing.\n8-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-8 TCP/UDP Message Service\n8-8-1 Outline of TCP/UDP Message Service\nTCP/UDP message service provides a simple form of TCP/UDP socket communications intended for\naccess to CIP objects of the Controller from a system where EtherNet/IP is not supported. With this\nfunction, you can change settings and perform I/O control for the Controller and Units connected to the\nNX Bus. TCP/UDP message service can be performed simultaneously with tag data link communica-\ntions.\nThis function is available only with NX502 CPU Units and NX102 CPU Units.\n8-8-2 Specifications of TCP/UDP Message Service\nItem Specifications\nMaximum number of clients which can 32 (for UDP and TCP each)\nbe connected simultaneously\nMaximum message size Request: 492 bytes\nResponse: 496 bytes\nMaximum NX data output size Maximum size of NX output data which can be written with the\nTCP/UDP message service\n488 bytes\nMaximum NX data input size Maximum size of NX input data which can be read with the TCP/UDP\nmessage service\n496 bytes\nPort number Port number used in the TCP/UDP message service\nDefault value: 64000 (decimal number)\n8-8-3 Settings Required for TCP/UDP Message Service\nWhen you use the TCP/UDP message service, you need to set the following unit settings.\nThe settings can be configured with the Sysmac Studio version 1.23 or higher.\nSysmac Studio Unit Settings Setting condi-\nSetting Setting range Default\nTab Page tions\nTCP/UDP message service Use/Do not use Optional Use/Do not use Do not use\nTCP/UDP message\nservice\nPort 1-Port No. Optional 1024-65535 *1 64000\nPort 2-Port No. Optional 1024-65535 *1 64000\n*1. When you use the TCP socket, the following port numbers are used by the system and cannot be set by the\nuser: 20, 23, 25, 80, 110, 9610, and 44818.\nWhen you use the UDP socket, the following port numbers are used by the system and cannot be set by the\nuser: 25, 53, 68, 110, 2222, 2223, 2224, 9600, and 44818.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-33\n8-8\nTCP/UDP\nMessage\nService\n8\n8-8-1\nOutline\nof\nTCP/UDP\nMessage\nService\n8 Socket Service\nPrecautions for Correct Use\nIf the Use Option is selected for Packet Filter on the built-in EtherNet/IP port, make sure to per-\nmit packets to be used for TCP/UDP message services. If they are not permitted, packets used\nby TCP/UDP message services cannot be received. For the details on the settings, refer to\nPacket Filter on page 4-8.\n8-8-4 Command Format Specifications\nRequest Command\nExample of\nParameter Offset ad- Size\nDescription VendorID\nname dress (bytes)\nreadout*1\nSequence 0 2 The user specifies an arbitrary number. The number 1000\nNo. specified here is stored in the sequence No. of the re-\nsponse command corresponding to the request com-\nmand.\nReserved 1 2 2 Reserved. Specify 0. 0000\nData Size 4 2 Specify the command size after the Reserved 2 pa- 0800\nrameter.\nReserved 2 6 1 Reserved. Specify 0. 00\nService 7 1 CIP service 0E\ncode\nClass ID 8 2 Controller object class ID 0100\nInstance ID 10 2 CIP object instance ID 0100\nAttribute ID 12 2 CIP object attribute ID. Specify if attribute ID specifica- 0100\ntion is required in the specified CIP service This can\nbe omitted if such specification is not required.\nData 12*2 Maximum Specify request data. ---\n492*3\n*1. Hexadecimal data in little-endian format.\n*2. The offset address will be 14 if the attribute ID is specified.\n*3. The size will be 488 bytes if the attribute ID is specified.\nResponse Command\nExample of\nParameter Offset ad- Size\nDescription VendorID\nname dress (bytes)\nreadout*1\nSequence 0 2 This is the sequence number specified in the request 1000\nNo. command corresponding to the response command.\nData Size 2 2 The command size after the Reserved parameter is 0600\nstored.\nReserved 4 1 Reserved. 0 is stored. 00\nService 5 1 The executed service code + most significant bit 1 is 8E\ncode stored.\n8-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nExample of\nParameter Offset ad- Size\nDescription VendorID\nname dress (bytes)\nreadout*1\nGeneral 6 1 00 is stored when the service ends normally, and a 00\nstatus value other than 00 is stored when the service ends in\nerror.\nStatus codes stored when an error occurs conform to\nthe CIP General Status Code.\nAdditional 7 1 00 is stored when the service ends normally. 00\nstatus size If the service ends in error, the Additional status size\n(word size) stored in the Data area will be stored.\nData 8 Maximum The response data is stored when the service ends 2F00\n496 normally.\nIf the service ends in error, the Additional status will be\nstored for the word size stored in the Additional\nstatus size parameter.\n*1. Hexadecimal data in little-endian format.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-35\n8-8\nTCP/UDP\nMessage\nService\n8\n8-8-4\nCommand\nFormat\nSpecifications\n8 Socket Service\n8-9 Secure Socket Services\nThe secure socket services perform encrypted secure socket communications (hereinafter called “se-\ncure socket communications”) using TLS (Transport Layer Security).\nThe CPU Unit can be used as a client to connect to cloud and on-premises servers via TCP/IP and\nexchange messages.\nVersion Information\nAn NX102-££00 CPU Unit with unit version 1.46 or later or an NX102-££20 CPU Unit with\nunit version 1.37 or later and Sysmac Studio version 1.46 or higher are required to use the se-\ncure socket services.\nAn NX1P2-££££££ CPU Unit with unit version 1.46 or later and Sysmac Studio version"}
+{"question": "46 or higher are required to use secure socket services.", "answer": "An NX502-££££ CPU Unit with unit version 1.60 or later and Sysmac Studio version 1.54 or\nhigher are required to use secure socket services.\nAdditional Information\nFunction Blocks (FBs) for MQTT communications are available for the secure socket communi-\ncations between a CPU Unit and a MQTT broker.\nRefer to the Sysmac Library User’s Manual for MQTT Communications Library (Cat. No. W625)\nfor more information on FBs for MQTT communications.\n8-9-1 Overview of Secure Socket Communications\nSecure socket communications use TLS1.2 to encrypt communication data between the client and the\nserver. By encrypting communication data, you can prevent third parties from eavesdropping or tam-\npering with the data.\nClient authentication also allows the server to detect client spoofing.\nClient Authentication\nIn secure socket communications, client authentication, which allows only certain clients to access the\nserver, is supported at the same time as encryption of communication data.\nUsing client certificates and client private keys, only devices with client certificates can establish TLS\nsessions with the server.\nRequest a signature from the Certification Authority (CA) to obtain the CA certificate to confirm the val-\nidity of the client certificate.\nClient authentication allows you to operate a more secure system.\n8-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nPrecautions for Correct Use\n• Determine the need for client authentication by taking into conditions such as the specifica-\ntions, operating costs, and security policies of the server.\n• Network security issues such as the server data be illegally obtained or tampered, or commu-\nnications to the server be disabled may occur due to theft, information leaks and tampering of\nclient certificates, private keys and secure socket setting by third parties. Take necessary\nmeasures for the management of client certificates, private keys and secure socket setting\nand for the prevention of theft, information leaks and tampering of those.\nEspecially, use an encrypted safe communications path, etc. when obtaining the private key\nto avoid information leaks. Furthermore, store the private key in a safe location where the risk\nof information leakage is extremely low.\nAdditional Information\nYou can obtain the client certificate and client private key in the following ways.\na. Request to issue a certificate to the Certification Authority.\nb. Create client certificates and client private keys by using OpenSSL or other tool.\nCreate X.509 digital certificates with Base64 Encode (convert to Pem format).\nc. Use an external certificate creation service.\nOutline of Secure Socket Communications Processing Procedure\nThe outline of processing procedure of secure socket communications is as follows.\nClient TCP connection request Server\n(CPU Unit) -------------------------------------------------------->\nTLS session connection request\n-------------------------------------------------------->\nSending the server certificate\n<--------------------------------------------------------\nClient certificate request\n(when the server performs client authentication)\n<--------------------------------------------------------\nSending client certificate and client private key\n(when the server performs client authentication)\n-------------------------------------------------------->\nDetermining cipher suite*1\n<------------------------------------------------------>\nEstablishment of TLS session\n<------------------------------------------------------>\nEncrypted data communications\n<------------------------------------------------------>\n*1. A cipher suite is a set of key exchange algorithm, key authentication method, encryption method and mes-\nsage authentication code.\nPrecautions for Correct Use\nServer certificates are used only to encrypt communications. It is not necessary to set the serv-\ner certificate or CA certificate on the CPU Unit.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-37\n8-9\nSecure\nSocket\nServices\n8\n8-9-1\nOverview\nof\nSecure\nSocket\nCommunications\n8 Socket Service\n8-9-2 System Configuration of Secure Socket Services\nThe system configuration for performing the secure socket communications is shown below.\n(b) (c)\n(g)\nCloud server\nComputer\nSysmac Studio Cloud service\nSecure Socket (i)\nConfiguration Certificate\nPrivate key\nUser programming Secure Socket (h)\nConfiguration commands Firewall and Router\nSecure socket service\ninstructions\nOn-premises\nserver\nTransferring Transferring\nEthernet\nDownloading Secure socket communications\nCPU Unit\nTCP/IP\n(f)\n(e)\nCertificate\nExecuting\nPrivate key\ninstructions\nSecure socket setting\nUser program SD Memory Card\nSecure socket service\nSecure socket services Secure socket\ninstructions\nRecording secure socket communications log\ncommunications log\nPLC Function Module EtherNet/IP Function Module\n(d)\n(a)\nThe system components are described in the following table.\nComponent Description\n(a) Secure socket service in- CPU Unit instructions that perform secure socket communications\nstructions\n(b) Secure socket setting*1 A Sysmac Studio function to configure secure socket setting in a CPU\nUnit (such as transferring client certificates and private keys, and ena-\nbling or disabling secure socket communications log, etc.)\n(c) Secure Socket Configura- A command-line tool to configure secure socket setting in a CPU Unit\ntion commands*2 (such as transferring client certificates and private keys, and enabling\nor disabling secure socket communications log, etc.)\n(d) Secure socket communica- Logs of secure socket communications\ntions logs TLS session parameters, starting and ending of a TLS session, and\ncommunications error information are output as a log.\n(e) Certificate A client certificate and a client private key used by a server for client (a\n(f) Private key CPU Unit) authentication.\nThe certificate and the private key are transferred to a CPU Unit using\nthe Secure Socket Configuration commands on the computer.\n(g) Cloud server A server that provides cloud services on an external network.\n(h) On-premises server A server installed in your own facility.\n8-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nComponent Description\n(i) Firewall and Router Communication devices that relay between different networks, such as\na cloud server on an external network.\n*1. An NX102 CPU Unit or NX1P2 CPU Unit with unit version 1.60 or later and Sysmac Studio version 1.53 or\nhigher are required to use the settings.\n*2. Use the commands for an NX102 CPU Unit or NX1P2 CPU Unit with unit version 1.50 or earlier.\nPrecautions for Correct Use\n• Setting up an intranet through a global address involves network security considerations. Be\nsure to consult with a network specialist in advance and consider using a VPN or installing a\nfirewall. After a firewall is set up by a communications technician, there may be some applica-\ntions that cannot be used. Be sure to check first with the communications technician.\n• To reduce the risk of unauthorized access by a third party using the Secure Socket Configu-\nration commands, consider setting operation authority verification on the CPU Unit. You can\nrestrict the use of Secure Socket Configuration commands to administrators only.\nFor details on how to set operation authority verification, refer to \"Operation Authority Verifica-\ntion” on the Sysmac Studio Version 1 Operation Manual (Cat. No. W504).\nRefer to Operation Authority Verification on page A-81 for operating specifications of Secure\nSocket Configuration commands when operation authority verification is set.\n8-9-3 Procedure to Use Secure Socket Setting Function of the Sysmac\nStudio\nThis section describes the procedure to use secure socket services for the following use cases.\n• Starting to use secure socket services\nRefer to Settings for Starting Secure Socket Services on page 8-40.\n• Replacing CPU Units\nRefer to Procedure for Replacing the CPU Unit on page 8-43.\nThe setting method of the secure socket service depends on the unit version and project unit version\nof the CPU Unit and version of the Sysmac Studio as shown below.\nCPU Unit Sysmac Studio version\nProject unit\nUnit version Ver.1.52 or lower Ver.1.53 Ver.1.54 or higher\nversion\nVer.1.48 or Ver.1.48 or earli- Secure Socket Configuration commands*1 Secure Socket\nearlier er Settings Dialog Box\nVer.1.50 or Ver.1.50 or earli- Secure Socket Configuration commands*1*2\nlater er\nVer.1.60 or later Secure Socket Configura- Secure Socket\ntion commands*1*2 Settings Dialog Box\n*1. Refer to A-10 Procedure to Use Secure Socket Service with Secure Socket Configuration Commands on\npage A-72 for details on how to use the secure socket service with the Secure Socket Configuration com-\nmands.\n*2. Please enable connections to the Sysmac Studio and NA which do not support secure communication.\nWhen user authentication or operation authority verification is set, only Administrator can use the se-\ncure socket setting function.\nSecure socket setting can be set only when the operating mode is PROGRAM mode. If the operating\nmode is RUN mode, change to PROGRAM mode before the settings.\nThe secure socket setting with the Sysmac Studio are as follows.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-39\n8-9\nSecure\nSocket\nServices\n8\nStudio 8-9-3\nProcedure\nto\nUse\nSecure\nSocket\nSetting\nFunction\nof\nthe\nSysmac\n8 Socket Service\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on the operations\non the Sysmac Studio.\n1\nSelect Controller - Security - Secure Socket Settings on the Sysmac Studio.\nIf user authentication is set, the following Authentication Dialog Box is displayed.\nIf operation authority verification is set, the following Verification Dialog Box is displayed.\n2\nEnter the Administrator password authenticated when connecting online, and click the OK But-\nton.\nAfter authentication is completed, the Secure Socket Settings Dialog Box is displayed.\nSettings for Starting Secure Socket Services\nThe following two procedures describe how to set up a new configuration.\n• If you do not use a client certificate and a client private key\n• If you use a client certificate and a client private key\n8-40 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n If you do not use a client certificate and a client private key\nThe setting procedure to start secure socket services when the client certificate and client private\nkey are not used is as follows.\nAs a prerequisite, set the built-in EtherNet/IP of the CPU Unit as follows.\n• If the server is on the Internet, configure the default gateway and routing table.\nIf the server is specified by an item other than the IP address, such as \"xxx.com\", configure the\nDNS server settings.\n• Configure NTP Settings.\nThe NTP Settings are optional. It is recommended for matching with the server time.\nCheck with the network administrator of the installation site for the settings of the default gateway,\nrouting table, DNS server, and NTP server.\nThe secure socket setting in this procedure is described in the following example.\n• The session ID set in the secure socket setting is 0.\n1\nConfigure the server and check the server's IP address, HOST name, and other settings.\nCheck with the server installer for details on how to check.\n2\nConfigure the secure socket setting.\nUse the Sysmac Studio to configure secure socket setting for the session ID. Set different ses-\nsion IDs for all connected destinations.\n1) Connect the Sysmac Studio online, and select Controller - Security - Secure Socket\nSettings.\n2) Press the + Button in the Session List of the Secure Socket Settings Dialog Box.\nThe Session Edit Dialog Box is displayed.\n3) Select 0 for Session ID and enter the session comment if necessary.\n4) Clear the Select Certificate and Private Key Files Check Box.\n5) Click the Transfer to Controller Button to transfer the settings to the Controller.\nTo enable secure socket communications log, select Communications Log to Enabled in the\nSecure Socket Settings Dialog Box and click the Transfer to Controller Button.\n3\nCreate a user program.\nCreate a session for secure socket communications with SktTCPConnect instruction to the\nserver in step 1. Set the TLS session name for the session ID to TLSSessionName, which is\nthe input variable of SktTLSConnect instruction. If the session ID in the Session Edit Dialog\nBox is 0, the TLS session name is TLSSession0.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-41\n8-9\nSecure\nSocket\nServices\n8\nStudio 8-9-3\nProcedure\nto\nUse\nSecure\nSocket\nSetting\nFunction\nof\nthe\nSysmac\n8 Socket Service\nUse SktTLSRead and SktTLSWrite instructions to process data communications with the serv-\ner.\n4\nDownload the user program using the synchronization function.\nDownload the user program from the computer to the CPU Unit.\nAfter sufficiently confirming that the connection destination is correct, start operation.\n If you use a client certificate and a client private key\nThe setting procedure to start secure socket services when the client certificate and client private\nkey are used is as follows.\nAs a prerequisite, set the built-in EtherNet/IP of the CPU Unit as follows.\n• If the server is on the Internet, configure the default gateway and routing table.\nIf the server is specified by an item other than the IP address, such as \"xxx.com\", configure the\nDNS server settings.\n• Configure NTP settings.\nThe NTP settings are optional. It is recommended for matching with the server time.\nCheck with the network administrator of the installation site for the settings of the default gateway,\nrouting table, DNS server, and NTP server.\nThe secure socket setting in this procedure is described in the following example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected\nthrough Ethernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP port of the CPU Unit is set to 192.168.250.1.\n• The session ID set in the secure socket setting is 0.\n1\nPrepare the client certificate, client private key, and CA certificate.\nIn this procedure, the file name of the prepared client certificate is client.cert. The file name of\nthe client private key is client.key.\nNote that the prepared client certificate and client private key must be stored and managed by\nthe customer.\n2\nInstall the client certificate and CA certificate on the server.\nCheck with the server administrator for details such as whether installation on the server is re-\nquired.\n3\nConfigure the server and check the server's IP address, HOST name, and other settings.\nCheck with the server installer for details on how to check.\n4\nConfigure the secure socket setting.\nUse the Sysmac Studio to configure session information for the session ID.\n1) Press the + Button in the Session List of the Secure Socket Settings Dialog Box.\nThe Session Edit Dialog Box is displayed.\n2) Select 0 for Session ID and enter the session comment if necessary.\n3) Select the Select Certificate and Private Key Files Check Box.\n4) Click the buttons to display the file selection dialog box for Certificate and Private key and\nselect the client certificate file client.cert and client private key file client.key respectively.\n8-42 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n5) Click the Transfer to Controller Button to transfer the settings to the Controller.\nTo enable secure socket communications log, select Communications Log to Enabled in the\nSecure Socket Settings Dialog Box and click the Transfer to Controller Button.\n5\nCreate a user program.\nCreate a session for secure socket communications with SktTCPConnect instruction to the\nserver in step 3. Set the TLS session name for the session ID to TLSSessionName, which is\nthe input variable of SktTLSConnect instruction. If the session ID in the Session Edit Dialog\nBox is 0, the TLS session name is TLSSession0.\nUse SktTLSRead and SktTLSWrite instructions to process data communication with the server.\n6\nDownload the user program using the synchronization function.\nDownload the user program from the computer to the CPU Unit.\nAfter sufficiently confirming that the connection destination is correct, start operation.\nProcedure for Replacing the CPU Unit\nThis section describes the following three procedures for replacing the CPU Unit.\n• If you do not use a client certificate and a client private key\n• If you have stored the client certificate and client private key\n• If you have not stored the client certificate and client private key\nWhen you replace the CPU Unit, be sure to perform the following steps before proceeding to the re-\nplacement procedure.\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on the operations\non the Sysmac Studio.\nThe secure socket setting in this procedure is described in the following example.\n• The session ID set in the secure socket setting is 2.\n• The folder to save the secure socket setting is C:\\Users\\omron.\n1\nBack up the data in the Controller.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on\nController backups.\n2\nRead the secure socket setting.\nDisplay the Secure Socket Settings Dialog Box and save the secure socket setting.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-43\n8-9\nSecure\nSocket\nServices\n8\nStudio 8-9-3\nProcedure\nto\nUse\nSecure\nSocket\nSetting\nFunction\nof\nthe\nSysmac\n8 Socket Service\n1) Click the folder selection button of the Get session information in the Secure Socket\nSettings Dialog Box, and select the folder to output the session information file.\nThe folder that you select is displayed to Output to:.\n2) Click the Get Button.\nThe session information file is output to the selected folder.\nCheck the status of Communications Log (Enabled or Disabled) in the Secure Socket\nSettings Dialog Box.\n3\nCheck that the client certificate and client private key are stored.\nCheck the read secure socket setting to ensure that the required client private key is stored.\n If you do not use a client certificate and a client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key are not\nused is as follows.\nThe secure socket setting in the replacement procedure is described in the following example.\n• The session ID in the secure socket setting before replacement is set to 2.\n1\nReplace to a new CPU Unit.\n2\nCheck the secure socket setting.\nUse the secure socket setting to check the session ID that is being used before replacing the\nCPU Unit.\n3\nConfigure the secure socket setting.\n1) Connect the Sysmac Studio online, and select Controller - Security - Secure Socket\nSettings.\n8-44 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n2) Press the + Button in the Session List of the Secure Socket Settings Dialog Box.\nThe Session Edit Dialog Box is displayed.\n3) Select 2 for Session ID and enter the session comment if necessary.\n4) Clear the Select Certificate and Private Key Files Check Box.\n5) Click the Transfer to Controller Button to transfer the settings to the Controller.\n4\nCheck the secure socket setting.\nDisplay the Secure Socket Settings Dialog Box and verify that it matches the session ID set\nin the folder of Output to: read in step 2 of Procedure for Replacing the CPU Unit on page\n8-43.\nCheck the status of Communications Log (Enabled or Disabled) in the Secure Socket\nSettings Dialog Box.\n5\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\n6\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\n If you have stored the client certificate and client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key have\nbeen stored is as follows.\nThe secure socket setting in the replacement procedure is described in the following example.\n• The session ID in the secure socket setting before replacement is set to 2.\n• The file name in the computer that stores the client certificate file used in the secure socket set-\nting of session ID=2 is client.cert.\n• The file name in the computer that stores the client private key file used in the secure socket set-\nting of session ID=2 is client.key.\n1\nReplace to a new CPU Unit.\n2\nCheck the secure socket setting.\nUse the secure socket setting to check the session ID that is being used before replacing the\nCPU Unit.\nPrepare the client certificate and client private key for each session ID that are stored in the\ncomputer.\n3\nConfigure the secure socket setting.\n1) Press the + Button in the Session List of the Secure Socket Settings Dialog Box.\nThe Session Edit Dialog Box is displayed.\n2) Select 2 for Session ID and enter the session comment if necessary.\n3) Select the Select Certificate and Private Key Files Check Box.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-45\n8-9\nSecure\nSocket\nServices\n8\nStudio 8-9-3\nProcedure\nto\nUse\nSecure\nSocket\nSetting\nFunction\nof\nthe\nSysmac\n8 Socket Service\n4) Click the buttons to display the file selection dialog box for Certificate and Private key and\nselect the client certificate file client.cert and client private key file client.key respectively.\n5) Click the Transfer to Controller Button to transfer the settings to the Controller.\nTo enable secure socket communications log, select Communications Log to Enabled in the\nSecure Socket Settings Dialog Box and click the Transfer to Controller Button.\n4\nCheck the secure socket setting.\nDisplay the Secure Socket Settings Dialog Box and verify that it matches the session ID set\nin the folder read in step 2 of Procedure for Replacing the CPU Unit on page 8-43 (C:\\Users\n\\omron in this example).\nCheck the status of Communications Log (Enabled or Disabled) in the Secure Socket\nSettings Dialog Box.\n5\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\n6\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\n If you have not stored the client certificate and client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key have not\nbeen stored is as follows.\n1\nCreate a client certificate and client private key.\nDepending on whether you are creating a client certificate and client private key on the server\nor preparing the client private key and client certificate yourself, the procedures are different as\nfollows.\nCreating a client certificate and client private key on the server\n1) Create a client certificate and client private key on the server and download them to the\ncomputer.\nIn this procedure, the file name of the downloaded client certificate is client.cert. The file\nname of the client private key is client.key.\nNote that you must store and manage the downloaded client certificate and client private\nkey yourself.\nCreating a client certificate and client private key yourself\n1) Prepare the client certificate, client private key, and CA certificate.\nIn this procedure, the file name of the prepared client certificate is client.cert. The file name\nof the client private key is client.key.\nNote that the prepared client certificate, client private key, and CA certificate must be stored\nand managed by the customer.\n2) Install the client certificate and CA certificate on the server.\n8-46 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nCheck with the server administrator for details such as whether installation on the server is\nrequired.\n2\nCheck the secure socket setting.\nUse the secure socket setting to check the session ID that is being used before replacing the\nCPU Unit.\nPrepare the client certificate and client private key for each session ID that are stored in the\ncomputer.\n3\nConfigure the secure socket setting.\n1) Press the + Button in the Session List of the Secure Socket Settings Dialog Box.\nThe Session Edit Dialog Box is displayed.\n2) Select 2 for Session ID and enter the session comment if necessary.\n3) Select the Select Certificate and Private Key Files Check Box.\n4) Click the buttons to display the file selection dialog box for Certificate and Private key and\nselect the client certificate file client.cert and client private key file client.key respectively.\n5) Click the Transfer to Controller Button to transfer the settings to the Controller.\nTo enable secure socket communications log, select Communications Log to Enabled in the\nSecure Socket Settings Dialog Box and click the Transfer to Controller Button.\n4\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\n5\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\n8-9-4 Executing Instructions for Secure Socket Communications\nYou can execute the secure socket communications using the socket service instructions and secure\nsocket service instructions.\nSecure Socket Service Instructions\nThe following table lists all of the secure socket service instructions.\nInstruction Function\nSktTLSConnect Establish TLS Session\nSktTLSWrite Send TLS\nSktTLSRead Receive TLS\nSktTLSClearBuf Clear TLS Session Receive Buffer\nSktTLSDisconnect Disconnect TLS Session\nSktTLSStopLog Stop Secure Socket Communications Log\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-47\n8-9\nSecure\nSocket\nServices\n8\n8-9-4\nExecuting\nInstructions\nfor\nSecure\nSocket\nCommunications\n8 Socket Service\nAdditional Information\nSpecify the TLS session name of the TLS session information that is set on the Sysmac Studio\nor with Secure Socket Configuration commands for the input variable of SktTLSConnect in-\nstruction. Refer to A-11 Secure Socket Configuration Commands on page A-79 for details on\nthe Secure Socket Configuration commands.\nRefer to the NJ/NX-series Instructions Reference Manual (Cat. No. W502) for details on the secure\nsocket service instructions.\nInstruction Execution Flow for Secure Socket Communications\nThe instruction execution flow for secure socket communications is as follows."}
+{"question": "The receive buffer is cleared by SktTLSClearBuf instruction, and communication with the server is", "answer": "performed using SktTLSWrite or SktTLSRead instructions."}
+{"question": "When the communications with the server are completed, terminate the TLS session with", "answer": "SktTLSDisconnect instruction and close the socket with the SktClose instruction.\nPrecautions for Correct Use\nThe number of TLS sessions that can be established in the secure socket communications is\nequal to the number of sockets that you can use in the TCP socket service. Therefore, it is\nshared with sockets used by normal socket service. Refer to Overview of Socket Services with\nSocket Service Instructions on page 8-10 for the number of sockets that you can use for the\nTCP socket service.\nThe following diagram shows the exchanges with the server in secure socket communications by the\nexecution of instructions on the CPU Unit.\n8-48 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nUser program Secure socket service Server\nSktTCPConnect\nSktSetOption\nSYN\nSYN ACK\nACK\nSktTLSConnect Secure socket communications\nTLS handshake\nSktTLSClearBuf\nSktTLSWrite\nApplication Data\nServer Application\nApplication Data\nSktTLSRead\nSktTLSDisconnect\nTLS handshake\nSktClose\nFIN Legend:\nDouble-line arrows indicate FIN ACK\nencrypted communications.\nTLS Handshake exchanges and verifies the data (such as certificates) required for encrypted commu-\nnications.\nTroubleshooting Secure Socket Service Instructions\nThis section describes how to identify errors when secure socket service instructions are executed\nand how to confirm the error details for troubleshooting when instructions ended in error.\nCheck the values of the output variables of each instruction to confirm whether the execution of in-\nstruction ended normally. Refer to the NJ/NX-series Instructions Reference Manual (Cat. No. W502)\nfor values of output variables of each instruction.\nFurthermore, for secure socket service instructions, you can find more detailed error information from\nthe secure socket communications log than from the ErrorID output variable for the instruction which is\nreferenced in error end. Refer to 8-9-6 Secure Socket Communications Logging on page 8-51 for de-\ntails on the secure socket communications log.\nThe diagram below shows the troubleshooting flow when instructions to perform secure socket com-\nmunications, which also include socket service instructions, are executed.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-49\n8-9\nSecure\nSocket\nServices\n8\n8-9-4\nExecuting\nInstructions\nfor\nSecure\nSocket\nCommunications\n8 Socket Service\nStarting Secure Socket Communications\nShaded: Secure socket service instructions\nOpening a TCP Socket Connection\nExecute SktTCPConnect instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nOpening a Secure Socket Connection\nExecute SktTLSConnect instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nSend Processing of Secure Socket\nExecute SktTLSWrite instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nReceive Processing of Secure Socket\nExecute SktTLSRead instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nClose Processing of Secure Socket\nExecute SktTLSDisconnect instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nClose Processing\nExecute SktClose instruction.\nError End\nOutput variable: Error = TRUE\nCheck error details based on\nInstruction end normally? the error code and take suitable actions.\nOutput variable: ErrorID\nNormal End\nOutput variable: Done = TRUE\nEnding Secure Socket Communications\n8-50 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\n8-9-5 Troubleshooting Errors in Secure Socket Communications\n1\nUse Sysmac Studio on the computer to check the event log of the CPU Unit.\n2\nCheck the secure socket communications log in the SD Memory Card in an editor of the com-\nputer.\nRefer to 8-9-6 Secure Socket Communications Logging on page 8-51 for details on the se-\ncure socket communications log.\nTo check the error details in the secure socket communications log, enable the secure socket\ncommunications log in the secure socket setting beforehand.\n3\nIdentify error causes from the event log and secure socket communications log and take re-\nquired measures.\n8-9-6 Secure Socket Communications Logging\nYou can record communications logs of secure socket communications.\nThis log records parameters, starting and ending of a TLS session, and communications error informa-\ntion.\nThe secure socket communications log file is recorded in the SD Memory Card and you can use this\nlog file for troubleshooting, etc., by viewing it in an editor.\nHow to Start and Stop Secure Socket Communication Log Output\n• How to start\nEnable the secure socket communications log in the Secure Socket Settings Dialog Box or with\nthe Secure Socket Configuration commands.\n• How to stop\nDisable the secure socket communications log in the Secure Socket Settings Dialog Box or with\nthe Secure Socket Configuration commands.\nOr, execute SktTLSStopLog instruction.\nRefer to 8-9-3 Procedure to Use Secure Socket Setting Function of the Sysmac Studio on page 8-39\nfor details on how to make secure socket settings on the Sysmac Studio.\nRefer to A-11 Secure Socket Configuration Commands on page A-79 on how to set the Secure Sock-\net Configuration commands.\nRefer to the NJ/NX-series Instructions Reference Manual (Cat. No. W502) for details on the\nSktTLSStopLog instruction.\nPrecautions for Correct Use\nStop the output of secure socket communications log before interrupting power to the CPU Unit.\nIf it is not stopped, the file of secure socket communications log may be corrupted.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-51\n8-9\nSecure\nSocket\nServices\n8\n8-9-5\nTroubleshooting\nErrors\nin\nSecure\nSocket\nCommunications\n8 Socket Service\nFile Types and Record Formats of Secure Socket Communications\nLog\nYou can find the file types, file names, file storage directories, and record formats of secure socket\ncommunications log in the following tables.\n Log File Types\nThe file name and storage directory for each file type are described in the table below.\nStorage directo-\nFile type File name ry (in the SD Remarks\nMemory Card)\nRecording log file SecureSocket.log /fs/MEMCARD1/ Recording log file is\nSecureSocket/Lo renamed to a past\ng/ log file name when\nthe maximum num-\nber of records is\nreached in the recod-\ning log file.\nPast log file SecureSock- The oldest file is de-\net_YYYYMMDDHHmmssSSS.log leted when the next\nYYYY: Year, MM: Month, DD: Day, file is created if the\nHH: Hour, mm: Minutes, ss: Seconds, SSS: number of log files\nMilliseconds reaches the maxi-\nIf all the input digits are not filled, it is com- mum number of files.\nplemented by inputting “0”.\nE.g. SecureSocket_20170724220915040.log\nSystem file SecureSocket.fjc /fs/MEMCARD1/ Log file management\nSecureSocket/ file\nSystem/\nPrecautions for Correct Use\nIf the recording log file (SecureSocket.log) or the log file management file (SecureSocket.fjc) in\nthe SD Memory Card is deleted during operation, the secure socket communications log is not\nrecorded.\n Number of Log Data and Formats\nA log file stores the maximum of 12,000 records.\nThe parameters and corresponding formats contained in one record are listed in the table below.\nThe maximum size of one record is 256 bytes.\nParameter Size Format\nSerial number 1 to 5 bytes 0 to 65535\nDate 10 bytes (fixed) Year, month, day\nYYYY-MM-DD\nTime of day 8 bytes (fixed) Hour, minutes, seconds\nhh:mm:ss\nMilliseconds 3 bytes (fixed) 3-digit decimal integer (000 to 999)\nE.g. 10 msec: 010, 623 msec: 623\n8-52 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nParameter Size Format\nCategory 16 bytes max. (varia- Category\nble)\nLog code 4 bytes (fixed) Unique identifying code within a category\n4-digit decimal code (zero padding)\nLog name 32 bytes max. (varia- Name indicating the meaning of log\nble)\nDetailed information 168 bytes max. (varia- Detailed information of log\nble) Information is separated with a tab when multiple informa-\ntion is provided.\nCR+LF 2 bytes (fixed) ---\n Detailed Information of Log Data\nLog code\nCategory Log name Definition Detailed information\n(decimal)\nINFO 1000 Parameter TLS session parameter HOST=[host name or ip address]\nHOST, PORT <tab> PORT=[port]\nRemarks\nHOST: Destination host name or\nIP address\nPORT: Destination port number\n1001 Parameter TLS session parameter CAFile=[root certificate of server]\nCAFile CAFile: File name of CA-signed\nserver certificate\n1002 Parameter TLS session parameter CERT=[session name]/[client cer-\nCERT tificate file name]\nExample.\nCERT=TLSSession0/client.crt\n1003 Parameter TLS session parameter KEY=[session name]/[client pri-\nKEY vate key file name]\nExample.\nKEY=TLSSession0/client.key\n1010 Established TLS session established None\n1011 Disconnect TLS session terminated None\nERROR 5000 SessionFail TLS session error API=[API name]<tab>Code=[Er-\nror Code]<tab>[Message]\n5001 Timeout Timeout in secure socket None\ncommunications\n5002 CommError Communications error [message]\n5103 ClientCertifica- Client certificate error FILE=[session name]/[file name]\nteError Example.\nFILE=TLSSession0/client.crt\n5104 ClientPrivate- Client private key error FILE=[session name]/[file name]\nKeyError Example.\nFILE=TLSSession0/client.key\n Example of Log Data\nThis is an example of log data output to the log file.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-53\n8-9\nSecure\nSocket\nServices\n8\n8-9-6\nSecure\nSocket\nCommunications\nLogging\n8 Socket Service\n0 2021-06-14 16:30:48 000 INFO 1000 Parameter HOST=192.168.250.40 PORT=8883\n1 2021-06-14 16:30:48 002 INFO 1001 Parameter CAFile=none\n2 2021-06-14 16:30:48 002 INFO 1002 Parameter CERT=TLSSession0/server.crt\n3 2021-06-14 16:30:48 005 INFO 1003 Parameter KEY=TLSSession0/server.key\n4 2021-06-14 16:30:48 024 INFO 1010 Established\n8-9-7 Handling of Secure Socket Communications Setting Information\nThe following table shows whether each setting information of secure socket communications is sup-\nported for synchronization (transfer), backup and restoration or Clear All Memory operation.\nNo: Not applicable.\nOperation\nBackup Restoration\n• Automatic\n• SD Memory • SD Memory transfers\nSecure socket Synchroniza- Clear All Mem-\nCard back- Card Back- from SD\ncommunications tion from Sys- ory operation\nups ups Memory\nsetting mac Studio from Sysmac\n• Sysmac Stu- • Sysmac Stu- Card\n(transfer) Studio\ndio Control- dio Control- • Sysmac Stu-\nler backups ler backups dio Control-\nler backups\nSecure socket set- No No No No Not cleared *1\nting\nClient certificate No No No No Not cleared *1\nClient private key No No No No Not cleared *1\nSecure socket com- No No No No Not cleared\nmunications log\n*1. Use the Secure Socket Settings Dialog Box on the Sysmac Studio or the Secure Socket Configuration\ncommands to clear the settings.\n8-54 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n8 Socket Service\nPrecautions for Correct Use\n• The client certificate and client private key that are related to the secure socket communica-\ntions are information attached to the CPU Unit itself, therefore, the information is out of the\ntarget of backup and restoration.\nWhen you replace the hardware of the CPU Unit, use the Secure Socket Settings Dialog\nBox on the Sysmac Studio or the Secure Socket Configuration commands to transfer the cli-\nent certificate, private key, and secure socket setting to the CPU Unit.\nSimilarly, the secure socket setting is also not the backup and restoration target. Use the\nSecure Socket Settings Dialog Box on the Sysmac Studio or the Secure Socket Configura-\ntion commands to make settings to the CPU Unit.\n• Network security issues such as the server data be illegally obtained or tampered, or commu-\nnications to the server be disabled may occur due to theft, information leaks and tampering of\nclient certificates, private keys and secure socket setting by third parties. Take necessary\nmeasures for the management of client certificates, private keys and secure socket setting\nand for the prevention of theft, information leaks and tampering of those.\nEspecially, use an encrypted safe communications path, etc. when obtaining the private key\nto avoid information leaks. Furthermore, store the private key in a safe location where the risk\nof information leakage is extremely low.\n• It is not possible to clear client certificates, private keys, and secure socket setting informa-\ntion on secure socket communications by Clear All Memory operation from the Sysmac Stu-\ndio. To clear the information on secure socket communications, for example when discarding\na CPU Unit, use the Secure Socket Settings Dialog Box on the Sysmac Studio, select and\nexecute Erase the data completely of the Clear All Memory option, or use the Secure\nSocket Configuration commands.\nAdditional Information\nSecure socket communications log is out of the target of backup and restoration.\nIf you want to carry over the contents of the secure socket communications log after the CPU\nUnit replacement, mount the SD Memory Card that was in use in the previous Unit to the re-\nstored CPU Unit.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 8-55\n8-9\nSecure\nSocket\nServices\n8\n8-9-7\nHandling\nof\nSecure\nSocket\nCommunications\nSetting\nInformation\n8 Socket Service\n8-56 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n9\nModbus TCP Master Function\n9-1 Overview of Modbus TCP Master Function.................................................9-2\n9-2 Modbus TCP Master Function Details..........................................................9-3\n9-2-1 Modbus TCP Instruction Type.........................................................................9-3\n9-2-2 Modbus TCP Instruction Function...................................................................9-3\n9-3 Modbus TCP Master Function Procedure....................................................9-4\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 9-1\n9\n9 Modbus TCP Master Function\n9-1 Overview of Modbus TCP Master\nFunction\nThe Modbus TCP is a protocol for using the message of the Modbus protocol on Ethernet. The Mod-\nbus TCP Master function sends Modbus commands to the Modbus TCP slave and receives responses\nfrom the Modbus TCP slave.\nModbus TCP Master\nBuilt-in EtherNet/IP port\nCPU Unit\nEthernet\nSending Modbus command\nSending Modbus command response\nOmron RFID, etc.\nModbus TCP slave\n9-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n9 Modbus TCP Master Function\n9-2 Modbus TCP Master Function Details\nThe Modbus TCP Master Function can be used by executing Modbus TCP instructions in the user\nprogram.\n9-2-1 Modbus TCP Instruction Type\nThe Modbus TCP instruction type and function are as follows.\nInstruction Function\nModbusTCPCmd Sends general commands to the Modbus TCP slave and receives responses.\nModbusTCPRead Sends read commands to the Modbus TCP slave and receives responses.\nModbusTCPWrite Sends write commands to the Modbus TCP slave and receives responses.\nFor details on Modbus TCP instructions, refer to the NJ/NX-series Instructions Reference Manual (Cat.\nNo. W502).\n9-2-2 Modbus TCP Instruction Function\nThis section describes Modbus TCP instruction functions.\nInstruction Function\nModbusTCPCmd The ModbusTCPCmd instruction sends Modbus commands of the specified proto-\ncol data unit (PDU) to the specified Modbus TCP slave and receives responses.\nModbusTCPRead The ModbusTCPRead instruction sends read commands to the specified Modbus\nTCP slave and receives responses. The following four Modbus commands can be\nsent by the ModbusTCPRead instruction.\n• Output read\n• Input read\n• Retained register read\n• Input register read\nModbusTCPWrite The ModbusTCPWrite instruction sends write commands to the specified Modbus\nTCP slave and receives responses. The following four Modbus commands can be\nsent by the ModbusTCPWrite instruction.\n• One output write\n• One retained register write\n• Multiple output write\n• Multiple retained register write\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 9-3\n9-2\nModbus\nTCP\nMaster\nFunction\nDetails\n9\n9-2-1\nModbus\nTCP\nInstruction\nType\n9 Modbus TCP Master Function\n9-3 Modbus TCP Master Function Proce-\ndure\nWhen you use the Modbus TCP Master Function, you need to also use the following instructions other\nthan the Modbus TCP instruction.\nInstruction Description\nSktTCPConnect Establishes the TCP/IP connection with the Modbus TCP slave before the execu-\ntion of the Modbus TCP instruction. The default connection port is 502.\nSktClose Disconnects the TCP/IP connection with the Modbus TCP slave after the execution\nof the Modbus TCP instruction.\nSktSetOption The application of the TCP-NODELAY option in the TCP/IP settings with the Mod-\nbus standard is recommended. Set it before the execution of the Modbus TCP in-\nstruction after the TCP/IP connection is established with the Modbus TCP slave.\nSktClearBuf The receive buffer is not cleared during the execution of the Modbus TCP instruc-\ntion. This instruction is executed if the receive buffer needs to be cleared during\nuse of the Modbus TCP instruction. For example, execute this instruction when the\nprevious Modbus TCP command response may be stored in the receive buffer.\n9-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n9 Modbus TCP Master Function\n Procedure\nUse the Modbus TCP Master Function as follows. Check the values of the output variables of each\ninstruction to confirm whether the instruction ended normally.\nExecute SktTCPConnect\ninstruction.\nError end\nOutput variable ErrorID=TRUE Check error details based on the error code which\nInstruction end normally? is output to the ErrorID output variable and take\nsuitable actions.\nNormal end\nOutput variable\nDone=TRUE\nExecute SktSetOption instruction\nError end\nOutput variable ErrorID=TRUE Check error details based on the error code which\nInstruction end normally? is output to the ErrorID output variable and take\nsuitable actions.\nNormal end\nOutput variable\nDone=TRUE\nExecute Modbus TCP instruction\nError end\nOutput variable ErrorID=TRUE Check error details based on the error code which\nInstruction end normally? is output to the ErrorID output variable and take\nsuitable actions.\nNormal end\nOutput variable\nDone=TRUE\nExecute SktClose instruction\nError end\nOutput variable ErrorID=TRUE Check error details based on the error code which\nInstruction end normally? is output to the ErrorID output variable and take\nsuitable actions.\nNormal end\nOutput variable\nDone=TRUE\nEnd Modbus TCP Master\nFunction.\nIf the response from the other equipment is slow and the Modbus TCP instruction ends before the\nresponse is returned, there may be data remaining in the receive buffer. In such cases, execute the\nModbus TCP instruction after the receive buffer is cleared with the SktClearBuf instruction or\nSktTCPConnect instruction.\nRefer to the Modbus TCP instructions in the NJ/NX-series Instructions Reference Manual (Cat. No.\nW502) for sample programming.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 9-5\n9-3\nModbus\nTCP\nMaster\nFunction\nProcedure\n9\n9 Modbus TCP Master Function\n9-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10\nFTP Server\n10-1 Overview and Specifications......................................................................10-2\n10-1-1 Overview.......................................................................................................10-2\n10-1-2 Specifications................................................................................................10-3\n10-2 FTP Server Function Details.......................................................................10-4\n10-2-1 Supported Files.............................................................................................10-4\n10-2-2 Connecting to the FTP Server.......................................................................10-4\n10-3 Using the FTP Server Function...................................................................10-7\n10-3-1 Procedure......................................................................................................10-7\n10-3-2 List of Settings Required for the FTP Server Function..................................10-7\n10-4 FTP Server Application Example................................................................10-9\n10-5 Using FTP Commands...............................................................................10-11\n10-5-1 Table of Commands.....................................................................................10-11\n10-5-2 Using the Commands...................................................................................10-11\n10-6 Using SD Memory Card Operations.........................................................10-18\n10-6-1 SD Memory Card Types..............................................................................10-18\n10-6-2 File Types....................................................................................................10-18\n10-6-3 Initializing SD Memory Cards......................................................................10-19\n10-6-4 Format of Variable Data..............................................................................10-19\n10-7 Application Example from a Host Computer...........................................10-20\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-1\n10\n10 FTP Server\n10-1 Overview and Specifications\n10-1-1 Overview\nThe built-in EtherNet/IP port has FTP (File Transfer Protocol) server capabilities. You can therefore\nsend FTP commands from an FTP client software application on a computer on the Ethernet network\nto upload and download large files from and to an SD Memory Card.\nFTP client\nSpecify the file and upload or download it by\nIntranet using FTP commands such as get and put.\nEthernet\nDownload\nUpload\nLarge file\nTo file on SD Memory\nCard in CPU Unit\nBuilt-in\nEtherNet/IP port\nAdditional Information\nWhen the NX502 CPU Unit is used as the FTP server and accesses the FTP server of the CPU\nUnit via an NX-series EtherNet/IP Unit, set IP Forward to Use. For details on the settings for the\nNX-series EtherNet/IP Unit, refer to the NX-series EtherNet/IP Unit User's Manual (Cat. No.\nW627).\n10-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n10-1-2 Specifications\nItem Specifications\nExecutable com- open : Connects the specified host FTP server.\nmands user : Specifies a user name for the remote FTP server.\nls : Displays file names in the remote host.\nmls : Displays file names in multiple remote hosts.\ndir : Displays file names and details in the remote host.\nmdir : Displays file names and details in multiple remote hosts.\nrename : Changes a file name.\nmkdir : Creates a new directory in the working directory on the remote host.\nrmdir : Deletes a directory from the working directory on the remote host.\ncd : Changes the work directory on the remote host to the specified directo-\nry.\npwd : Displays the work directory on the remote host.\ntype : Changes the file transfer type.\nget : Transfers a specified remote file to the local host.\nmget : Transfers specified multiple remote files to the local host.\nput : Transfers a specified local file to the remote host.\nmput : Transfers specified multiple local files to the remote host.\ndelete : Deletes a specified file from the remote host.\nmdelete : Deletes specified multiple files from the remote host.\nappend : Uses the currently specified file data type to append a local file to the\nremote host.\nclose : Disconnects the FTP server.\nbye : Closes the FTP client.\nquit : Closes the FTP client.\nProtection Login name (up to 12 characters)\nPassword consists of 8 to 32 characters.\nProtocol used FTP (Port No.: 20/TCP, 21/TCP)\nNumber of connec- 6\ntions\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-3\ntions\n10-1\nOverview\nand\nSpecifica-\n10\n10-1-2\nSpecifications\n10 FTP Server\n10-2 FTP Server Function Details\n10-2-1 Supported Files\nThe file system in the Controller that can be accessed by the built-in EtherNet/IP port includes files in\nan SD Memory Card mounted in the CPU Unit.\nThe directory tree is shown below.\n/: root\nMEMCARD1:SD\nusr\nbin Used by system\ndev\nA connection is initially made to the root directory.\nAdditional Information\n• The date of the MEMCARD1 directory displayed for ls, dir, and mkdir commands in the root\ndirectory is the date of the file system volume label.\n• The login date is displayed for MEMCARD1 if a volume label has not been created.\n10-2-2 Connecting to the FTP Server\nInput the FTP login name and password to login to the built-in EtherNet/IP port from an FTP client ap-\nplication. Use the Built-in EtherNet/IP Port Settings in the Sysmac Studio to set the FTP login name\nand password.\nAdditional Information\nWhen a general-purpose FTP application is used, you can use a graphical user interface similar\nto Explorer to transfer and read files.\n Login Name and Password Setting\nThe FTP login name and password are not set by default.\nUse the Built-in EtherNet/IP Port Settings to set any login name and password.\n Login Messages\nStatus Message\nNormal connection 220 xxx.xx.xx.xx FTP server ready.\nxxx.xx.xx.xx: CPU Unit model (example: NJ501-1300)\nConnected to maximum 530 FTP server busy, Goodbye.\nnumber of connections (6)\n Restrictions on Login Name and Password Setting\nThe following restrictions apply to login names and passwords.\n• Only single-byte alphanumeric characters can be used for login names and passwords. The login\nname and password are case sensitive.\n• A login name consists of up to 12 characters.\n10-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n• A password consists of 8 to 32 characters.\n• Always set a password when you set a new login name. The login name will not be valid unless\na password is set for it.\n• The login name is invalid if the login name is not set or characters other than single-byte alpha-\nnumeric characters are used.\n FTP File Transfer Mode\nFTP has two file transfer modes: ASCII mode and binary mode. Before you start to transfer files,\nuse the type command (specifies the data type of transferred files) to select the required mode.\n• To transfer a file in binary format: Select binary mode.\n• To transfer a file in ASCII format: Select ASCII mode.\n Multiple Accesses to the Same File\nFiles accessed with the FTP server may be simultaneously accessed by multiple sources with com-\nmunications commands from other FTP servers or programming instructions.\nExclusive control is required to prevent multiple accesses.\nThis is to prevent reading and writing the same file at the same time.\nThe CPU Unit automatically performs exclusive control as shown below only when the following\ncombinations of instructions are used.\nIn other cases, use file operation instructions (Change File Name, Copy File, etc.) or communica-\ntions commands and perform exclusive control.\n• Exclusive Control When Accessing the Same File on the SD Memory Card\nFirst access\nFile operations from the\nInstructions*1 FTP server\nSysmac Studio\nReading Writing Reading Writing Reading Writing\nExclusive control is per- Exclusive Perform ex- Exclusive Perform ex-\nRea formed automatically, and control is clusive con- control is clusive con-\nding an error occurs for the in- not re- trol. not re- trol.\nInstruc-\nstruction that is executed quired. quired.\ntions\nlater. Perform ex- Perform ex-\nL Writ\nclusive con- clusive con-\na ing\ntrol. trol.\nt\nExclusive Perform ex- Exclusive Perform ex- Exclusive\ne\nFile oper- Rea control is clusive con- control is clusive con- control is\nr\nations ding not re- trol. not re- trol. not re-\na\nfrom the quired. quired. quired.\nc\nSysmac Perform exclusive control. Perform exclusive control. Perform ex-\nc Writ\nStudio clusive con-\ne ing\ntrol.\ns\nExclusive Perform ex- Exclusive Perform ex- Exclusive Perform ex-\ns\nRea control is clusive con- control is clusive con- control is clusive con-\nFTP ding not re- trol. not re- trol. not re- trol.\nserver quired. quired. quired.\nWrit Perform exclusive control. Perform exclusive control.\ning\n*1. The instructions include the SD Memory Card operation instructions and the FTP client communications\ninstructions.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-5\n10-2\nFTP\nServer\nFunction\nDetails\n10\n10-2-2\nConnecting\nto\nthe\nFTP\nServer\n10 FTP Server\n Restrictions on Connection to FTP Server\nIf you repeat connection to and disconnection from the FTP server frequently in a short period of\ntime, access to the server may be restricted temporarily for system protection. If you cannot con-\nnect to the FTP server, wait for 10 minutes and try again.\n10-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n10-3 Using the FTP Server Function\n10-3-1 Procedure\n1\nMake the basic settings.\nRefer to 1-5 EtherNet/IP Communications Procedures on page 1-30 for the basic operation\nflow.\n2\nSet up the FTP server on the Sysmac Studio. (Refer to 4-3 FTP Settings Display on page\n4-14.)\n3\nSelect Controller Setup - Built-in EtherNet/IP Port Settings on the Sysmac Studio. Make the\nfollowing settings on the FTP Settings Display.\n• FTP server\n• Port number\n• Login name\n• Password\n4\nConnect the CPU Unit online and transfer the settings to the Controller.\n5\nInsert the SD Memory Card into the CPU Unit.\n6\nConnect to the built-in EtherNet/IP port from an FTP client.\n7\nInput the FTP login name and password that you set in the Built-in EtherNet/IP Port Settings to\nlog in to the built-in EtherNet/IP port.\n8\nAfter you are logged in, you can use ftp commands, such as cd (Change Directory) and get\n(Obtain File) for the MEMCARD1 directory in the SD Memory Card in the Controller.\n9\nClose the connection.\n10-3-2 List of Settings Required for the FTP Server Function\nMake the following settings for the unit setup when the FTP server function is used.\nBuilt-in EtherNet/IP Port\nSettings Tab Page on Setting Setting conditions Reference\nSysmac Studio\nFTP FTP server Required page 4-14\nPort No. Any number*1\nRequired when changing the de-\nfault value of 21.\nLogin name Required*1\nPassword Required*1\n*1. If the Do not use Option is selected for the FTP server, these settings are not required.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-7\ntion\n10-3\nUsing\nthe\nFTP\nServer\nFunc-\n10\n10-3-1\nProcedure\n10 FTP Server\nPrecautions for Correct Use\nAllow packets from the FTP client if the Use Option is selected for Packet Filter of the built-in\nEtherNet/IP port. If they are not permitted, communication with the FTP client is not possible.\nFor the details on the settings, refer to Packet Filter on page 4-8.\nAdditional Information\nMake settings in the FTP Settings Display if the FTP server is used. Refer to 4-3 FTP Settings\nDisplay on page 4-14 for information on the FTP Settings Display.\n10-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n10-4 FTP Server Application Example\nAn example of using the FTP server with the login name \"user1\" and the password \"password\" is\nshown below.\nAdditional Information\nWhen a general-purpose FTP application is used, you can use a graphical user interface similar\nto Explorer to transfer and read files.\n Step"}
+{"question": "Connect to the FTP server from a computer on the Ethernet by entering the text that is under-", "answer": "lined in the following diagram.\nIP address of built-in EtherNet/IP port\nC:\\>ftp 192.168.250.1\nConnected to 192.168.250.1.\nResults\n220 NJ501-1500 FTP server ready.\nUser (192.168.250.1: (none)) : user1 Login name\n331 Password required for user1.\nPassword: Password\n230 User user1 logged in. (hidden)\nftp>\nftp> bye\n221-\nData traffic for this session was 0 bytes in 0 files.\nTotal traffic for this session was 204 bytes in 0 transfers.\n221 Thank you for using the FTP service on 192.168.250.1.\nC:\\>"}
+{"question": "Enter FTP commands (underlined in the following diagram) to read and write files. The following", "answer": "directory tree is used in this example.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-9\nample\n10-4\nFTP\nServer\nApplication\nEx-\n10\n10 FTP Server\n/ (root directory)\nMEMCARD1\nABC (subdirectory)\nDEF.BIN(file)\nftp>ls File names read.\n200 PORT command successful.\n150 Opening ASCII mode data connection for ‘file list’\nusr\nbin Results\nMEMCARD1\ndev\n226 Transfer complete.\nftp:** bytes received in 0 seconds(**bytes/s) Change to\nftp>cd MEMCARD1 MEMCARD1 directory\n250 CWD command successful. Results\nftp>get ABC/DEF.BIN Get DEF.BIN from ABC\n200 PORT command successful. directory\n150 opening ASCII mode data connection for ‘ABC/DEF.BIN’(**bytes).\nResults\n226 Transfer complete\n**bytes received in *.*** seconds(**bytes/s)\n10-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n10-5 Using FTP Commands\nThis section describes the FTP commands which the host computer (FTP client) can send to the FTP\nserver of the built-in EtherNet/IP port.\nThere may be slight differences in the descriptions depending on the model of your workstation. Refer\nto your workstation's operation manuals for details.\n10-5-1 Table of Commands\nThe FTP commands which can be sent to the built-in EtherNet/IP port are listed in the following table.\nCommand Description\nopen Connects the specified host FTP server.\nuser Specifies a user name for the remote FTP server.\nls Displays file names in the remote host.\nmls Displays file names in multiple remote hosts.\ndir Displays file names and details in the remote host.\nmdir Displays file names and details in multiple remote hosts.\nrename Rename a file\nmkdir Creates a new directory in the working directory on the remote host.\nrmdir Deletes a directory from the working directory on the remote host.\ncd Changes the work directory on the remote host to the specified directory.\npwd Displays the work directory on the remote host.\ntype Changes the file transfer type.\nget Transfers a specified remote file to the local host.\nmget Transfers specified multiple remote files to the local host.\nput Transfers a specified local file to the remote host.\nmput Transfers specified multiple local files to the remote host.\ndelete Deletes a specified file from the remote host.\nmdelete Deletes specified multiple files from the remote host.\nappend Uses the file data type that is specified by the type command to append a local file to the\nremote host.\nclose Disconnects the FTP server.\nbye Closes the FTP client.\nquit Closes the FTP client.\nNote 1. \"Remote host\" refers to the built-in EtherNet/IP port.\nNote 2. \"Remote file\" refers to a file on the SD Memory Card in the CPU Unit.\nNote 3. \"Local host\" refers to the host computer (FTP client).\nNote 4. \"Local file\" refers to a file on the host computer (FTP client).\n10-5-2 Using the Commands\nopen\n Format\nopen [IP_address or host_name_of_FTP_server]\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-11\n10-5\nUsing\nFTP\nCommands\n10\n10-5-1\nTable\nof\nCommands\n10 FTP Server\n Function\n• Connects the FTP server. Normally, the FTP server IP address is specified to execute this com-\nmand automatically when the FTP client is booted.\nuser\n Format\nuser [user_name]\n Function\n• Specifies the user name. Specify the FTP login name set in the built-in EtherNet/IP port system\nsetup.\n• The user name is automatically requested immediately after connection to the FTP server is\nopened.\nls\n Format\nls [-l] [remote_file_name [local_file_name]]\n Function\n• Displays the names of files on the remote host (on the SD Memory Card).\n• Set the switch [-l] to display not only the file names but the creation dates and sizes as well. If the\nswitch is not set, only the file names are displayed.\n• Specify a file on the SD Memory Card for the remote_file_name.\n• If the local_file_name is specified, the file information is stored in the specified file.\nmls\n Format\nmls remote_file_name local_file_name\n Function\n• Displays a list of the names of files on multiple remote hosts (on the SD Memory Card).\n• For the remote_file_name, specify a directory on the SD Memory Card in which you wish to list\nfiles contained, or a file name. Input an asterisk (*) to display a list of the current working directo-\nry.\n• If the local_file_name is specified, the file information is stored in the specified file. Input a hy-\nphen (-) to display a list of the remote hosts but not store the list of file names.\n10-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\ndir\n Format\ndir [remote_file_name [local_file_name]]\n Function\n• Displays the names, creation dates, and sizes of files on the remote host (on the SD Memory\nCard).\n• It displays the same information as command [ls -l].\n• Specify a file on the SD Memory Card for the remote_file_name.\n• If the_local_file name is specified, the file information is stored in the specified file.\nmdir\n Format\nmdir remote_file_name local_file_name\n Function\n• Displays the names of files, subdirectories, creation dates, and sizes on multiple remote hosts\n(on the SD Memory Card).\n• For the remote_file_name, specify the directory or file name on the SD Memory Card you wish to\nlist. Input a hyphen (-) to display a list of the current working directory.\n• If the_local_file_name is specified, the file information is stored in the specified file. Input a hy-\nphen (-) to display a list of the remote hosts and not store the file information.\nrename\n Format\nrename current_file_name new_file_name\n Function\n• Changes the specified current file name to the specified new file name.\n• If the new file name is already used by an existing file on the remote host (on the SD Memory\nCard), the existing file is overwritten by the file whose name was changed.\n• rename can just change the file name. It cannot be used to move the file to a different directory.\nmkdir\n Format\nmkdir directory_name\n Function\n• Creates a directory of the specified name on the remote host (on the SD Memory Card).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-13\n10-5\nUsing\nFTP\nCommands\n10\n10-5-2\nUsing\nthe\nCommands\n10 FTP Server\n• An error will occur if a file or directory of the same name already exists in the working directory.\nrmdir\n Format\nrmdir directory_name\n Function\n• Deletes the directory with the specified name from the remote host (from the SD Memory Card).\n• The directory must be empty to be deleted.\n• An error will occur if the specified directory does not exist or is not empty.\npwd\n Format\npwd\n Function\n• Displays the work directory on the remote host.\nappend\n Format\nappend local_file_name [remote_file_name]\n Function\n• Uses the file data type that is specified by the type command to append the local file to the re-\nmote host (on the SD Memory Card).\ncd\n Format\ncd [directory_name]\n Function\n• Changes the remote host work directory to the specified remote directory.\n• Files on the SD Memory Card are stored in the MEMCARD1 directory under the root directory (/).\n• The root directory (/) is the directory that is used when you log onto the built-in EtherNet/IP port.\nThe MEMCARD1 directory does not exist if an SD Memory Card is not inserted in the CPU Unit\nor if the SD Memory Card power indicator on the CPU Unit is not lit.\n10-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\ntype\n Format\ntype data_type\n Function\n• Specifies the file data type.\n• The following data types are supported:\nascii: Files are transferred as ASCII data.\nbinary (image): Files are transferred as binary data.\nThe CPU Unit handles binary files. Use the type command to specify binary transfers before you\nupload or download files.\n• The default file type is ASCII.\nget\n Format\nget file_name [receive_file_name]\n Function\n• Transfers the specified remote file from the SD Memory Card to the local host.\n• You can specify the name of the file to be received on the local host by setting receive file name.\nmget\n Format\nmget file_name\n Function\n• With wildcards (*) included in the file_name, transfers multiple remote files from the SD Memory\nCard to the local host.\nput\n Format\nput file_name [destination_file_name]\n Function\n• Transfers the specified local file to the remote host (to the SD Memory Card).\n• You can save the transfered file with the name you specify for the destination_file_name.\n• Any existing file with the same name in the remote host (on the SD Memory Card) is overwritten\nby the contents of the transferred file.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-15\n10-5\nUsing\nFTP\nCommands\n10\n10-5-2\nUsing\nthe\nCommands\n10 FTP Server\nmput\n Format\nmput file_name\n Function\n• With wildcards (*) included in the file_name, transfers multiple local files to the remote host (to\nthe SD Memory Card).\n• Any existing file with the same name in the remote host (on the SD Memory Card) is overwritten\nby the contents of the transferred file.\ndelete\n Format\ndelete file_name\n Function\n• Deletes the specified remote file (on the SD Memory Card).\nmdelete\n Format\nmdelete file_name\n Function\n• With wildcards (*) included in the file_name, deletes multiple remote files from the SD Memory\nCard.\nclose\n Format\nclose\n Function\n• Disconnects the FTP server of the built-in EtherNet/IP port.\nbye\n Format\nbye\n10-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\n Function\n• Ends the FTP session.\nquit\n Format\nquit\n Function\n• Ends the FTP session.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-17\n10-5\nUsing\nFTP\nCommands\n10\n10-5-2\nUsing\nthe\nCommands\n10 FTP Server\n10-6 Using SD Memory Card Operations\nThe built-in EtherNet/IP port can be used to upload and download the following data between the SD\nMemory Card and the FTP server.\n• Variables files (binary format)\nThe following three methods are available when a CPU Unit saves data to and reads data from the SD\nMemory Card.\nSysmac Studio\n1) Creating and reading files\nfrom the Sysmac Studio\n2) File operations from Windows\nNJ/NX-series CPU Units\n3) Reading and writing variable files with\nSD Memory Card instructions\nSD Memory Card Uploading data to or downloading\ndata from the FTP server\n10-6-1 SD Memory Card Types\nRefer to Specifications of Supported SD Memory Cards, Folders, and Files in the NJ/NX-series CPU\nUnit Software User's Manual (Cat. No. W501) for details.\n10-6-2 File Types\nFile Names\nFile names and extensions are assigned to identify files.\nThe following characters can be used in file names and extensions. File names are not case sensitive.\nA to Z, a to z, and 0 to 9\nthe following symbols: $ % ’ - _ @ ! ‘ ( ) ~ = # & + ^ [ ] { } , . ;\nThe following characters cannot be used in files names.\nBlanks, multi-byte characters, and the following symbols: / \\ ? * ” : < >\nThe maximum length of a file name with the extension is 65 characters.\nThe first period (.) in a file name is taken as the delimiter between the file name and extension.\nExtensions are determined by the file type.\nDirectory\nYou can create up to five levels of directories to store files on the SD Memory Card (count the root\ndirectory as one level).\nA maximum of 65 characters can be used in a directory name.\n10-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server\nFile Names Handled by CPU Unit\nThe files described in the following table can be read or written by the CPU Unit.\nEx-\nFile type File name ten- Contents Description\nsion\nVariables file (bi- Refer to .bin Specified variables The variables file contains the values of\nnary format) 10-6-2 File specified variables (which include arrays\nTypes on and structures) in binary format (.bin).\npage 10-18.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details.\n10-6-3 Initializing SD Memory Cards\n1\nInsert the SD Memory Card into the CPU Unit.\n2\nUse the Sysmac Studio to initialize the SD Memory Card.\n10-6-4 Format of Variable Data\nBinary Format\nThis is a data format used for binary data specified by the ladder instructions, FileReadVar (Read Vari-\nables File) and FileWriteVar (Save Variables File), in the CPU Unit.\nYou can also read and save arrays and structures.\nData is created as shown below when the data of variable Var_A is placed in an attached file in binary\nformat.\nSD Memory Card\nSaveVar instruction Var_A\nexecuted.\n16#1234\nVariable values are 16#4567\nwritten to the binary 16#abcd\nfile in sequence 16#0987\nfrom the beginning.\n12344567\nabcd0987\nBinary file\nAdditional Information\n• When you handle a binary file on the NJ/NX-series CPU Unit, always specify the binary data\ntype with the type command before you read or write the file via FTP. (Refer to 10-5-2 Using\nthe Commands on page 10-11.)\n• For details on how to use ladder diagram instructions to process files, refer to the NJ/NX-\nseries Instructions Reference Manual (Cat. No. W502).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-19\nerations\n10-6\nUsing\nSD\nMemory\nCard\nOp-\n10\n10-6-3\nInitializing\nSD\nMemory\nCards\n10 FTP Server\n10-7 Application Example from a Host\nComputer\nThe following procedure provides an example of FTP operations from a host computer. In this exam-\nple, the following assumptions are made.\n• The IP address of the built-in EtherNet/IP port is registered in the hosts as host name [nj].\n• The FTP login name is \"LogIn\".\n• Manufacturing results are stored in a file named RESULT.BIN. in the SD Memory Card in the CPU\nUnit.\n• A manufacturing instructions data file called PLAN.BIN already exists on the workstation.\nIn the following procedure, the manufacturing results file (RESULT.BIN) in the SD Memory Card in the\nCPU Unit is transferred to a workstation, and then a manufacturing instructions file (PLAN.BIN) on the\nworkstation is transferred to the SD Memory Card in the CPU Unit.\nUnderlined text is keyed in from the FTP client. The workstation prompt is indicated as $, and the cur-\nsor is indicated as ¢."}
+{"question": "Start the FTP application and connect to the built-in EtherNet/IP port.", "answer": "$ ftp nj FTP started.\nconnected to nj\n220 **IPaddress** NJ501-1300 FTP server(FTP**version**)ready\nName(nj:root):"}
+{"question": "Enter the login name.", "answer": "Name(nj:root):LogIn Enter the login name.\n331 Password required for LogIn.\nPassword: Enter the password.\n230 LogIn logged in.\nftp>"}
+{"question": "Make sure the Memory Card is correctly inserted. The MEMCARD1 directory is displayed if there is", "answer": "an SD Memory Card in the CPU Unit.\nftp> ls Make sure the Memory\n200 PORT command successful. Card is inserted.\n150 opening data connection for ls(**IPaddress**port#**)(0 bytes).\nMEMCARD1\n226 Transfer complete.\n15 bytes received in 0 seconds(**bytes/s)\nftp>"}
+{"question": "Change to the MEMCARD1 directory.", "answer": "ftp> cd MEMCARD1 Change the directory.\n250 CWD command successful.\nftp>\n10-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n10 FTP Server"}
+{"question": "Change data type to binary.", "answer": "ftp> type binary Set binary data type.\n200 Type set to I.\nftp>"}
+{"question": "Read the file RESULT.BIN and transfer it to the workstation.", "answer": "ftp> get RESULT.BIN Read file.\n200 PORT command successful.\n150 opening data connection for result.bin (**IPaddress**port#**) (**bytes).\n226 Transfer complete.\n** bytes received in *.*** seconds (**bytes/s)\nftp>"}
+{"question": "Write the file PLAN.BIN to the Memory Card.", "answer": "ftp> put PLAN.BIN Write file.\n200 PORT command successful.\n150 opening data connection for plan.bin (**IPaddress**port#**) .\n226 Transfer complete.\n** bytes received in *.** seconds (**bytes/s)\nftp>"}
+{"question": "End the FTP session.", "answer": "ftp> bye FTP ended.\n221 Goodbye.\n$\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 10-21\nHost\nComputer\n10-7\nApplication\nExample\nfrom\na\n10\n10 FTP Server\n10-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11\nFTP Client\n11-1 Using the FTP Client to Transfer Files.......................................................11-2\n11-1-1 Transferring Files............................................................................................11-2\n11-1-2 Connectable FTP Servers..............................................................................11-3\n11-1-3 File Transfer Options......................................................................................11-3\n11-1-4 Other Functions..............................................................................................11-4\n11-2 FTP Client Communications Instructions..................................................11-5\n11-2-1 Functions of the FTP Client Communications Instructions.............................11-5\n11-2-2 Restrictions on the FTP Client Communications Instructions........................11-8\n11-3 FTP Client Application Example.................................................................11-9\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-1\n11\n11 FTP Client\n11-1 Using the FTP Client to Transfer Files\nYou can use the FTP client to transfer files between the FTP client and an FTP server. You can trans-\nfer files in either direction: download data from the FTP server to the FTP client or upload data from\nthe FTP client to the FTP server.\nVersion Information\nA CPU Unit with unit version 1.08 or later is required to use the FTP client.\n11-1-1 Transferring Files\nAll file transfers that use the FTP client are executed with FTP client communications instructions in\nthe user program. The file transfer settings are all made with the parameters of the FTP client commu-\nnications instructions. No settings are required from the Sysmac Studio.\nThe FTP client communications instructions and their functions are given in the following table. You\ncan execute up to three FTP client communications instructions at the same time.\nInstruction Function\nFTPGetFileList Gets a file list from the FTP server.\nFTPGetFile Downloads one or more files from the FTP server.\nFTPPutFile Uploads one or more files to the FTP server.\nFTPRemoveFile Deletes one or more files from the FTP server.\nFTPRemoveDir Deletes a directory from the FTP server.\nDownloaded files are stored on the SD Memory Card. When uploading files, files that are stored on\nthe SD Memory Card are uploaded to the FTP server. Therefore, when you upload or download files,\nan SD Memory Card must be inserted in the NJ-/ NX series CPU Unit.\nFTP server\nUploading and downloading files are executed\nwith FTP client communications instructions.\nEthernet\nDownloading\nUploading\nFile\nFile on SD Memory Card\nin CPU Unit\nBuilt-in EtherNet/IP Port\nFTP client\nAdditional Information\nWhen the FTP server is accessed from the FTP client function of the NX502 CPU Unit via an\nNX-series EtherNet/IP Unit, set IP Forward to Use. For details on the settings for the NX-series\nEtherNet/IP Unit, refer to the NX-series EtherNet/IP Unit User's Manual (Cat. No. W627).\n11-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\n11-1-2 Connectable FTP Servers\nAn NJ/NX-series CPU Unit can connect to the following FTP servers. Refer to the relative manuals for\ninformation on setting and using the FTP servers.\n• Built-in EtherNet/IP port on NJ/NX-series CPU Unit\n• CJ-series EtherNet/IP Unit with unit version 2.0 or later\n• CJ-series CJ2 CPU Unit with Built-in EtherNet/IP\n• CJ-series CJ1M CPU Unit with Ethernet Functions\n• CJ-series Ethernet Unit\n• Windows7: Windows Server 2008 R2 (Internet Information Services (IIS) 7.5)\n• Windows8: Windows Server 2012 (IIS8.0)\n• Windows10: Windows Server2016 (IIS10.0)\n• Linux\n11-1-3 File Transfer Options\nYou can use the following options for file transfers. All the options are specified in the parameters of\nthe FTP client communications instructions.\n• File transfer mode\n• Open mode for data connection\n• Deleting files after transfer\n• Overwriting\nThe following sections describe each of these options.\n File Transfer Mode\nThere are two file transfer modes, ASCII Mode and Binary Mode, that differ in how line feeds in text\ndata are handled. The following table describes the differences.\nTransfer mode Handling of line feeds in text data\nASCII Mode Line feeds are converted to the line feed code of the destination system, e.g., Unix or\nWindows.\nBinary Mode Line feeds are transferred without conversion.\n Open Mode for Data Connection\nIn order to transfer files, a TCP connection between the FTP server and FTP client should be\nopened. TCP connections include control connections to control communications and data connec-\ntions to transfer data. When a data connection is opened, the connection is assigned with either\nActive Mode or Passive Mode, depending on whether the connection request is issued by the FTP\nserver or FTP client. The following table describes the differences.\nOpen mode Request to establish a connection\nActive Mode The FTP server makes the connection request.\nPassive Mode The FTP client makes the connection request.\nFor example, if the FTP server is not on the Internet and you use Active Mode to open a data con-\nnection, a connection request from the FTP server may not be permitted due to security policies. In\nthis case, you must set Passive Mode for the data connection and sends a connection request from\nthe FTP client.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-3\n11-1\nUsing\nthe\nFTP\nClient\nto\nTransfer\nFiles\n11\n11-1-2\nConnectable\nFTP\nServers\n11 FTP Client\n File Deletion after Transfer\nYou can specify whether to delete the source files after the file transfer. If the file transfer fails for\nany reason, the source files are not deleted even if deletion is specified.\n Overwriting\nYou can specify whether to overwrite a file of the same name as the transferred file at the file trans-\nfer destination. If you specify not overwriting files and a file of the same name exists at the transfer\ndestination, the source file will not be transferred.\n11-1-4 Other Functions\nYou can also use the following two functions for file transfers.\n• Retrying connection processing with the FTP server\n• Using wildcards to specify the files to transfer\nThese functions are described in the following sections.\n Retrying Connection Processing with the FTP Server\nIf connection processing fails to connect with the FTP server, the connection is automatically retired\nup to three times. You can set the timeout time that is used to determine connection failure, the\nnumber of retries, and the retry interval.\n Using Wildcards to Specify the Files to Transfer\nYou can use wildcards to specify the names of files to transfer. This allows you to transfer more\nthan one file at one time.\n11-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\n11-2 FTP Client Communications Instruc-\ntions\nFTP client communications instructions are always used to transfer files with the FTP client. The FTP\nclient communications instructions and their functions are given in the following table.\nInstruction Function\nFTPGetFileList Gets a file list from the FTP server.\nFTPGetFile Downloads one or more files from the FTP server.\nFTPPutFile Uploads one or more files to the FTP server.\nFTPRemoveFile Deletes one or more files from the FTP server.\nFTPRemoveDir Deletes a directory from the FTP server.\nFor details on the FTP client communications instructions, refer to the NJ/NX-series Instructions\nReference Manual (Cat. No. W502).\n11-2-1 Functions of the FTP Client Communications Instructions\nThis section describes the functions of the FTP client communications instructions.\nFTPGetFileList Instruction\nThe FTPGetFileList instruction gets a list of files and folders in a specified directory on the FTP server.\nThe following information is obtained.\n• The number of files and folders in the specified directory\n• The names of the files and folders\n• The last updated date and time of each file and folder\n• The file sizes\n• The read-only attributes of the files and folders\nYou can specify the following option.\n• Open Mode for data connection\nFTP server\nEthernet\nFile and folder information from\nthe specified directory on the FTP server\nFTP client\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-5\ntions\n11-2\nFTP\nClient\nCommunications\nInstruc-\n11\n11-2-1\nFunctions\nof\nthe\nFTP\nClient\nCommunications\nInstructions\n11 FTP Client\nAdditional Information\nThe updated dates of files at 12 am and 12 pm are improved in the CPU Unit with unit version"}
+{"question": "14 or later.", "answer": "FTPGetFile Instruction\nThe FTPGetFile instruction downloads the specified file from the specified directory on the FTP server\nto the specified directory in the SD Memory Card.\nYou can use wildcards to specify the file name to allow you to download more than one file at the\nsame time.\nIf the directory specified for the download does not exist in the SD Memory Card, the directory is creat-\ned and the data is downloaded to it.\nYou can specify the following options.\n• Transfer mode\n• Open Mode for data connection\n• Deleting files after transfer\n• Overwriting\nFTP server\nEthernet\nDownloading\nOne or more files\nFTP client\nFTPPutFile Instruction\nThe FTPPutFile instruction uploads the specified file from the specified directory in the SD Memory\nCard to the specified directory on the FTP server.\nYou can use wildcards to specify the file name to allow you to upload more than one file at the same\ntime.\nIf the directory specified for the upload does not exist on the FTP server, the directory is created and\nthe data is uploaded to it.\nYou can specify the following options.\n• Transfer mode\n• Open Mode for data connection\n• Deleting files after transfer\n• Overwriting\n11-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\nFTP server\nEthernet\nUploading\nOne or more files\nFTP client\nFTPRemoveFile Instruction\nThe FTPRemoveFile instruction deletes the specified file in the specified directory on the FTP server.\nYou can use wildcards to specify the file name to allow you to delete more than one file at the same\ntime.\nYou can specify the following option.\n• Open Mode for data connection\nFTP server\nOne or more files are deleted.\nEthernet\nFTP client\nFTPRemoveDir Instruction\nThe FTPRemoveDir instruction deletes the specified directory from the FTP server.\nFTP server\nDirectory is deleted.\nEthernet\nFTP client\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-7\ntions\n11-2\nFTP\nClient\nCommunications\nInstruc-\n11\n11-2-1\nFunctions\nof\nthe\nFTP\nClient\nCommunications\nInstructions\n11 FTP Client\n11-2-2 Restrictions on the FTP Client Communications Instructions\nThe following restrictions apply to the FTP client communications instructions. Keep in mind these re-\nstrictions when you create the user program.\n• If you execute more than one FTP client communications instruction to read and write data in the\nSD Memory Card at the same time, unexpected operation may result, such as reading data from a\nfile to which data is being written. Perform exclusive control of the instructions in the user program.\n• If you execute an FTP client communications instruction to read or write data in the SD Memory\nCard at the same time as another operation to read or write data in the SD Memory Card, unexpect-\ned operation may result, such as reading data from a file to which data is being written. Perform ex-\nclusive control of the instructions in the user program. Refer to the NJ/NX-series CPU Unit Software\nUser's Manual (Cat. No. W501) for information on exclusive control of access to files in the SD\nMemory Card.\n11-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\n11-3 FTP Client Application Example\nFTP client functionality is executed with FTP client communications instructions. This section provides\nsample programming that uses the FTP client communications instructions.\nThis program executes an SD Memory Card backup and then uploads all of the backup-related files to\nthe /Backup/yyyy-mm-dd directory on the FTP server.\nFTP server\nIP address: 192.168.250.2\nUDP port number: 21\nUser name: FtpUser\nPassword: 12345678\nEthernet\nFTP client\nThe backup-related files are uploaded\nto the /Backup/yyyy-mm-dd directory on the FTP server.\nBuilt-in EtherNet/IP port\nThe Controller is connected to the FTP server through an EtherNet/IP network. The settings of the pa-\nrameters to connect to the FTP server are given in the following table.\nParameter Value\nIP address 192.168.250.2\nUDP port number 21\nUser name FtpUser\nPassword 12345678\nThe following procedure is used.\n1\nThe BackupToMemoryCard instruction is used to save backup-related files of a NJ/NX-series\nController to the root directory on the SD Memory Card.\n2\nThe FTPPutFile instruction is used to upload the backup-related files to the /Backup/yyyy-mm-\ndd directory on the FTP server. The wildcard specification *.* is used to specify the names of\nthe files to transfer.\n3\nNormal end processing is performed if the operation is normally completed. Error end process-\ning is performed if an error occurs.\nLD\nInternal\nVariable Data type Initial value Comment\nvariables\nFTPPutFile_in- FTPPutFile Instance of FTPPutFile in-\nstance struction\nFTPAddr _sFTP_CON- (Adr := '', PortNo := 0, User- Connected FTP server\nNECT_SVR Name := '', Password := '') settings\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-9\n11-3\nFTP\nClient\nApplication\nExample\n11\n11 FTP Client\nInternal\nVariable Data type Initial value Comment\nvariables\nPutResult ARRAY[0..0] OF [(Name := '', TxError := False, Uploaded file results\n_sFTP_FILE_RE- RemoveError := False, Re-\nSULT served := [4(16#0)])]\nRS_instance RS Instance of RS instruction\nOperatingEnd BOOL FALSE Processing completed\nTrigger BOOL FALSE Execution condition\nOperating BOOL FALSE Processing\nBackupToMe- BackupToMemory- Instance of BackupToMe-\nmoryCard_in- Card moryCard instruction\nstance\nPrepare connected FTP server settings.\nP_First_RunMode\nMOVE MOVE\nEN ENO EN ENO 1\n'192.168.250.2' In Out FTPAddr.Adr UINT#21 In Out FTPAddr.PortNo\nMOVE MOVE\n1 EN ENO EN ENO\n'FTPUser' In Out FTPAddr.UserName '12345678' In Out FTPAddr.Password\nDetermine if instruction execution is completed.\nBackupToMemoryCard_instance.Done FTPPutFile_instance.Done OperatingEnd\nBackupToMemoryCard_instance.Error\nFTPPutFile_instance.Error\n11-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\nAccept trigger. RS_instance\nTrigger BackupToMemoryCard_instance.Busy FTPPutFile_instance.Busy Operating RS\nSet Q1\nOperatingEnd Reset1\nExecute BackupToMemoryCard and FTPPutFile instructions.\nBackupToMemoryCard_instance\nOperating\nBackupToMemoryCard\nExecute Done\nDirName Busy\nCancel Error\nOption Canceled\nErrorID\nFTPPutFile_instance\nBackupToMemoryCard_instance.Done\nFTPPutFile\nExecute Done\nFTPAddr ConnectSvr Busy\n'/Backup/yyyy-mm-dd' SvrDirName CommandCanceled\n'/' LocalDirName Error\n'*.*' FileName ErrorID\nExecOption ErrorIDEx\nRetryCfg PutNum\nCancel\nPutFileResult\nPutResult PutResult\nProcessing after normal end\nInline ST\nOperating BackupToMemoryCard_instance.Done FTPPutFile_instance.Done\n1 // Processing after normal end\n2 ;\nProcessing after error end\nInline ST\nOperating BackupToMemoryCard_instance.Error\n1 // Processing after error end\n2 ;\nFTPPutFile_instance.Error\nST\nInternal\nVariable Data type Initial value Comment\nvariables\nR_TRIG_in- R_TRIG Instance of R_TRIG in-\nstance struction\nUP_Q BOOL FALSE Trigger output\nFTPPutFile_in- FTPPutFile Instance of FTPPutFile in-\nstance struction\nDoFTPTrigger BOOL FALSE Execution condition for\nBackupToMemoryCard\nand FTPPutFile\nFTPAddr _sFTP_CON- (Adr := '', PortNo := 0, User- Connected FTP server\nNECT_SVR Name := '', Password := '') settings\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-11\n11-3\nFTP\nClient\nApplication\nExample\n11\n11 FTP Client\nInternal\nVariable Data type Initial value Comment\nvariables\nPutResult ARRAY[0..0] OF [(Name := '', TxError := False, Uploaded file results\n_sFTP_FILE_RE- RemoveError := False, Re-\nSULT served := [4(16#0)])]\nStage UINT 0 Instruction execution\nstage\nTrigger BOOL FALSE Execution condition\nBackupToMe- BackupToMemory- Instance of BackupToMe-\nmoryCard_in- Card moryCard instruction\nstance\n// Prepare connected FTP server settings.\nIF P_First_RunMode THEN\nFTPAddr.Adr := '192.168.250.2'; // Address\nFTPAddr.PortNo := UINT#21; // Port number\nFTPAddr.UserName := 'FtpUser'; // User name\nFTPAddr.Password := '12345678'; // Password\nEND_IF;\n// Accept trigger.\nR_TRIG_instance(Trigger, UP_Q);\nIF ( (UP_Q = TRUE) AND (BackupToMemoryCard_instance.Busy = FALSE) AND\n(FTPPutFile_instance.Busy = FALSE) ) THEN\nDoFTPTrigger := TRUE;\nStage := INT#1;\nBackupToMemoryCard_instance( // Initialize instan\nce.\nExecute := FALSE) ;\nFTPPutFile_instance( // Initialize instan\nce.\nExecute := FALSE,\nConnectSvr := FTPAddr,\nSvrDirName := '/Backup/yyyy-mm-dd',\nLocalDirName := '/',\nFileName := '*.*',\nPutFileResult := PutResult) ;\nEND_IF;\nIF (DoFTPTrigger = TRUE) THEN\nCASE Stage OF\n1 : // Execute BackupToM\nemoryCard instruction.\nBackupToMemoryCard_instance(\nExecute := TRUE) ; // Execution\nIF (BackupToMemoryCard_instance.Done = TRUE) THEN\nStage := INT#2; // To next stage\nELSIF (BackupToMemoryCard_instance.Error = TRUE) THEN\n11-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n11 FTP Client\nStage := INT#10; // Error end\nEND_IF;\n2 : //Execute FTPPutFile\ninstruction.\nFTPPutFile_instance(\nExecute := TRUE, // Execution\nConnectSvr := FTPAddr, // Connected FTP ser\nver\nSvrDirName := '/Backup/yyyy-mm-dd', // FTP server direct\nory name\nLocalDirName := '/', // Local directory n\name\nFileName := '*.*', // File name\nPutFileResult:= PutResult) ; // Uploaded file res\nults\nIF (FTPPutFile_instance.Done = TRUE) THEN\nStage := INT#0; // Normal end\nELSIF (FTPPutFile_instance.Error = TRUE) THEN\nStage := INT#20; // Error end\nEND_IF;\n0 : // Processing after\nnormal end\nDoFTPTrigger :=FALSE;\nTrigger :=FALSE;\nELSE // Processing after\nerror end\nDoFTPTrigger :=FALSE;\nTrigger :=FALSE;\nEND_CASE;\nEND_IF;\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 11-13\n11-3\nFTP\nClient\nApplication\nExample\n11\n11 FTP Client\n11-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n12\nAutomatic Clock Adjustment\n12-1 Automatic Clock Adjustment......................................................................12-2\n12-1-1 Overview.......................................................................................................12-2\n12-1-2 Specifications................................................................................................12-2\n12-2 Procedure to Use the Automatic Clock Adjustment Function.................12-4\n12-2-1 Procedure......................................................................................................12-4\n12-2-2 Settings Required for Automatic Clock Adjustment.......................................12-4\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 12-1\n12\n12 Automatic Clock Adjustment\n12-1 Automatic Clock Adjustment\n12-1-1 Overview\nThe built-in EtherNet/IP port reads clock information from the NTP server and updates the internal\nclock time in the CPU Unit at the specified time or at a specified interval after the power supply to the\nController is turned ON.\nNTP server\nAutomatic clock adjustment\nTime information written. Time query sent. Ethernet (EtherNet/IP)\n23:59:59\nBuilt-in EtherNet/IP port\nClock data is obtained from the NTP server and\nwritten to the CPU Unit at the following times.\n• When power supply is turned ON to CPU Unit\n• At specified times or at specified intervals\nNTP client NTP client NTP client\nThe NTP (Network Time Protocol) server is used to control the time on the LAN.\nAdditional Information\nWhen the NTP server is accessed from the NTP client function of the NX502 CPU Unit via an\nNX-series EtherNet/IP Unit, set IP Forward to Use. For details on the settings for the NX-series\nEtherNet/IP Unit, refer to the NX-series EtherNet/IP Unit User's Manual (Cat. No. W627).\n12-1-2 Specifications\nItem Specification\nProtocol NTP\nPort No. 123 (UDP)\nHowever, you can change the port number in the Built-in EtherNet/IP Port Settings on\nthe Sysmac Studio.\nAccess to NTP server Writes the clock informa- Obtains the clock information from the NTP server set up\ntion from the NTP server on the Network, and applies the information obtained to\nto the local CPU Unit. the local CPU Unit.\nNTP Operation Timing Clock information is automatically updated at the following times if the NTP function is\nused.\n• After links are established when the power supply to the Controller is turned ON\n• At specified times or at specified intervals (according to the option selected for the\nNTP operation timing)\nClock information is updated at the following times.\nNTP command sent NTP command sent NTP command sent\n(clock information update) (clock information update) (clock information update)\nWhen links are\nestablished.*1 At specified times or At specified times or at\nat specified intervals*2 specified intervals*2\n12-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n12 Automatic Clock Adjustment\n*1. This is performed when the Get Option is selected for the NTP server clock information in the NTP\nSettings Display.\n*2. Depends on the option set for the NTP operation timing in the NTP Settings Display.\nAdditional Information\n• NTP clock synchronization is normally performed as follows:\n• If the clock deviation is within 128 ms: The clock is synchronized every 0.5 ms.\n• If the clock deviation exceeds 128 ms: The clock is synchronized immediately.\n• If the NTP operation timing is set for a specified time interval, the timing will not change even\nif the time in the CPU Unit is changed during operation.\n(For example, if the time interval is set to 60 minutes, the information is updated 60 minutes\nafter the last time it was updated even if the time in the CPU Unit is changed.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 12-3\n12-1\nAutomatic\nClock\nAdjustment\n12\n12-1-2\nSpecifications\n12 Automatic Clock Adjustment\n12-2 Procedure to Use the Automatic\nClock Adjustment Function\n12-2-1 Procedure\n1\nMake the basic settings.\nRefer to 1-5 EtherNet/IP Communications Procedures on page 1-30 for the basic operation\nflow.\n2\nSelect Controller Setup - Built-in EtherNet/IP Port Settings on the Sysmac Studio.\nSet the following on the NTP Settings Display.\n• NTP server settings (required)\n• NTP operation timing\n3\nSelect Synchronization from the Controller Menu. The built-in EtherNet/IP port settings are\ntransferred to the CPU Unit.\n12-2-2 Settings Required for Automatic Clock Adjustment\nThe following Built-in EtherNet/IP Port Settings are made from the Sysmac Studio to use automatic\nclock adjustment.\nTab page Setting Setting conditions Reference\nNTP NTP server clock informa- Required. page 4-15\ntion\nPort No. Specified by user.*1\nServer specifying method Required\nIP address One of these must be set, depending on\nHost name the Server specification type setting.\nNTP operation timing Required\nSpecify a Time One of these must be set.\nSpecify a time in- (Set according to the NTP operation\nterval timing.)\nTimeout time Specified by user.*2\n*1. Required to change from the default value of 123.\n*2. Required to change from the default value of 10 seconds.\nAdditional Information\nMake the settings in the NTP Settings Display if automatic clock adjustment is used. Refer to\n4-4 NTP Settings Display on page 4-15 for information on the NTP Settings Display.\n12-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13\nSNMP Agent\n13-1 SNMP Agent..................................................................................................13-2\n13-1-1 Overview.......................................................................................................13-2\n13-1-2 Specifications................................................................................................13-3\n13-1-3 SNMP Messages...........................................................................................13-3\n13-1-4 MIB Specifications.........................................................................................13-4\n13-2 Procedure to Use the SNMP Agent..........................................................13-28\n13-2-1 Procedures..................................................................................................13-28\n13-2-2 Settings Required for the SNMP Agent.......................................................13-28\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-1\n13\n13 SNMP Agent\n13-1 SNMP Agent\nThe SNMP (simple network management protocol) is a network management protocol.\nYou can use the SNMP to manage any network that consists of devices that support SNMP.\nThe server that manages the network is called the SNMP manager. The managed network devices\nare called SNMP agents.\nEtherNet/IP devices are monitored.\nManagement information\ndatabase SNMP manager\nEthernet\nScheduled status SNMP agent SNMP agent SNMP agent\nmonitoring\nDevice that supports SNMP\nBuilt-in EtherNet/IP Port\n13-1-1 Overview\nSNMP Agent\nThe built-in EtherNet/IP port has its own management information called the MIB (management infor-\nmation base). This information can be provided to the SNMP manager.\nThe SNMP manager is software that gathers and processes information about devices on the SNMP\nnetwork and provides that information to the network administrator.\nYou can use the SNMP manager to monitor the built-in EtherNet/IP port.\nSNMP manager\nInformation requested SNMP agent\n(SNMP command).\nInformation sent\nMIB\n(management\ninformation).\nBuilt-in EtherNet/IP port\nThe SNMP manager has a SNMP command to request MIB information.\n13-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nThe built-in EtherNet/IP port SNMP agent function supports SNMPv1 (RFC1157) and SNMPv2C\n(RFC1901).\nUse the SNMPv1 or SNMPv2C protocol to manage the built-in EtherNet/IP port with the SNMP man-\nager. You can also use both the SNMPv1 and SNMPv2C protocols together at the same time.\nSNMP Traps\nWhen a failure or some other specific problem occurs, a status report called a trap is sent.\nThis enables monitoring changes in status even if the SNMP manager does not monitor the built-in\nEtherNet/IP port periodically.\nHowever, traps use UDP. Therefore, you cannot check to see if the SNMP manager receives traps\nfrom the EtherNet/IP port.\nThus, depending on the network status, some traps may not reach the SNMP manager.\nSNMP manager\nController power supply\nturned ON.\nBuilt-in EtherNet/IP port\nMIB\nTrap\nSNMP agent\n13-1-2 Specifications\nItem Specification\nProtocol SNMP\nAgent SNMPv1, SNMPv2C\nMIB MIB-II\nPort No. SNMP agent: 161 (UDP)\nSNMP trap: 162 (UDP)\nThese can be changed in the Built-in EtherNet/IP Port Settings from the Sysmac Stu-\ndio.\nTiming of SNMP trap Status reports are sent to the SNMP manager at the following times.\noperation • When the Controller is turned ON\n• When links are established\n• When an SNMP agent fails to be authorized\nSupported MIB com- GetRequest/GetNextRequest\nmands\n13-1-3 SNMP Messages\nThe structure of SNMP messages is as follows:\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-3\n13-1\nSNMP\nAgent\n13\n13-1-2\nSpecifications\n13 SNMP Agent\nVariable length (1,472 bytes max.)\nMAC header IP header UDP header SNMP message\nVersion Community PDU\nItem Set value\nVersion This value gives the SNMP version.\nSNMPv1: 0\nSNMPv2C: 1\nCommunity Community name for verification\nPDU This depends on the PDU type.\n13-1-4 MIB Specifications\nThis section describes the specifications of the MIB that is supported by the built-in EtherNet/IP port.\nMIB System Diagram\nThe built-in EtherNet/IP port MIB consists of the following tree structure.\nroot\niso (1)\norg (3)\ndod (6)\ninternet (1)\nmgmt (2)\nmib-2 (1)\n-system (1) Unit information\ninterface (2) Interface information\nip (4) IP information\nicmp (5) ICMP information\ntcp (6) TCP information\nudp (7) UDP information\nsnmp (11) SNMP information\nstd(0)\niso8802(8802)\nieee802dot1(1)\niso8802dot1mibs(1)\nlldpMIB(2) LLDP information\nVersion Information\nThe MIB of LLDP information is supported on the following CPU Unit versions:\n• NX502 CPU Unit : Unit version 1.60 or later\n• NX102 CPU Unit : Unit version 1.68 or later\n13-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nMIB Groups\nMIB group Stored information\nStandard MIB system group The MIB for information related to the de-\nvice.\ninterfaces group The MIB for information related to the in-\nterface.\nip group ip The MIB for IP information.\nipAddrTable The MIB for addressing table information\nrelated to IP addresses.\nipRouteTable The MIB for information related to IP\nrouting tables.\nipNetToMediaTable The MIB for information related to IP ad-\ndress conversion tables.\nipForward The MIB for information related to IP for-\nwarding tables.\nicmp group The MIB for ICMP information.\ntcp group tcp The MIB for TCP information.\nudp group udp The MIB for UDP information.\nsnmp group snmp The MIB for SNMP information.\nIEEE802.1X MIB lldp group The MIB for LLDP information.\nDetailed Descriptions of MIB Objects\n System Group\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nsysDescr (1) Support- \"OMRON Corporation\"\nDevice information (including hardware, OS, ed + CPU Unit model +\nsoftware names, and versions) CPU Unit version\nASCII characters only. • CPU Unit model (ex-\nample): NJ501-1200\n• CPU Unit version\n(example): Version"}
+{"question": "0", "answer": "sysObjectID (2) Support- NX-series CPU Units:\nVendor OID. ed 1.3.6.1.4.1.16838.1.10\nTells where this device information was as- 25.5\nsigned in the private MIB. NJ-series CPU Units:"}
+{"question": "4", "answer": "sysUpTime (3) Support- According to the stand-\nThe time elapsed since the system was start- ed ard.\ned (unit: 1/100 s).\nsysContact (4) Support- Set by the user.\nHow to contact the administrator and infor- ed\nmation on the administrator.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-5\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nsysName (5) Support- • NX502 CPU Unit:\nThe name for management. Sets the full do- ed Host Name\nmain name of the device. • CPU Units other\nthan above: CPU\nUnit Name\nsysLocation (6) Support- Set by the user.\nThe physical location of the device. ed\nsysServices (7) Support- Always 64.\nThe value of the provided service. ed\n Interfaces Group\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nifNumber (1) Support- • NX701 CPU Unit: 3\nThe number of network interfaces. ed • NX502 CPU Unit: 3\nor 4\n• NX102 CPU Unit: 3\n• NX1P2 CPU Unit: 2\n• NJ-series CPU Unit:\n2\nifTable (2) --- ---\nInterface entity table\nifEntry (1) --- ---\nRow data for interface information\nThe index is ifIndex.\nifIndex (1) Support- • NX701 CPU Unit: 1\nA number used to identify the interface. ed to 3\n• NX502 CPU Unit: 1\nto 4\n• NX102 CPU Unit: 1\nto 3\n• NX1P2 CPU Unit: 1\nto 2\n• NJ-series CPU Unit:\n1 to 2\n13-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nifDescr (2) Support- • NX701 CPU Unit:\nInformation related to the interface (includes ed 10/100/1000M Giga-\nmanufacturer name, product name, and hard- bit Ethernet Port\nware interface version). • NX502 CPU Unit:\n10/100/1000M Giga-\nbit Ethernet Port\n• NX102 CPU Unit:\n10/100M Fast Ether-\nnet Port\n• NX1P2 CPU Unit:\n10/100M Fast Ether-\nnet Port\n• NJ-series CPU Unit:\n10/100M Fast Ether-\nnet Port\nifType (3) Support- ethernet-csmacd (6)\nThe type of interface classified according to ed\nthe physical/link layer protocol directly under\nthe network layer of the protocol stack.\nifMtu (4) Support- Always 1,500.\nMTU value ed\nThe maximum size (in octets) of datagrams\nthat can be sent and received through this in-\nterface.\nifSpeed (5) Support- • NX701 CPU Unit:\nEstimated bandwidth ed 10000000/\nIf a stable, accurate value cannot be obtained 100000000/\nfor the bandwidth, a nominal value is set in- 1000000000\nstead. • NX502 CPU Unit:\n10000000/\n100000000/\n1000000000\n• NX102 CPU Unit:\n10000000/\n100000000\n• NX1P2 CPU Unit:\n10000000/\n100000000\n• NJ-series CPU Unit:\n10000000/\n100000000\nifPhysAddress (6) Support- The MAC address of\nMAC address ed the EtherNet/IP port\nThe physical address under the network layer\nof the interface.\nifAdminStatus (7) Support- According to the stand-\nThe preferred status of the interface. ed ard.\nYou cannot send normal packets in the test-\ning state.\nup (1)\ndown (2)\ntesting (3)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-7\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nifOperStatus (8) Support- According to the stand-\nThe current status of the interface. ed ard.\nYou cannot send normal packets in the test-\ning state.\nup (1)\ndown (2)\ntesting (3)\nifLastChange (9) Support- According to the stand-\nThe sysUpTime (in 0.01 seconds) at the last ed ard.\nchange in ifOperStatus for this interface.\nifInOctets (10) Support- According to the stand-\nThe number of octets received through this ed ard.\ninterface. This includes framing characters.\nifInUcastPkts (11) Support- According to the stand-\nThe number of unicast packets reported to a ed ard.\nhigher level protocol.\nifInNUcastPkts (12) Support- According to the stand-\nThe number of non-unicast packets (broad- ed ard.\ncast or multicast packets) reported to a high-\ner level protocol.\nifInDiscards (13) Support- According to the stand-\nThe number of packets that had no errors but ed ard.\ncould not be passed to a higher level protocol\n(i.e., the number of packets received but dis-\ncarded due to a buffer overflow).\nifInErrors (14) Support- According to the stand-\nThe number of packets discarded because ed ard.\nthey contained errors.\nifInUnknown- (15) Support- According to the stand-\nProtos The number of packets received, but discard- ed ard.\ned because they were of an illegal or unsup-\nported protocol.\nFor example, Ethernet packets did not have\nIP set for the field that identifies their higher\nlevel protocol.\nifOutOctets (16) Support- According to the stand-\nThe number of octets of packets sent through ed ard.\nthis interface.\nThis includes framing characters.\nifOutUcastPkts (17) Support- According to the stand-\nThe number of unicast packets sent by high- ed ard.\ner level protocols.\nThis includes discarded packets and unsent\npackets.\nifOutNU- (18) Support- According to the stand-\ncastPkts The number of non-unicast packets sent by ed ard.\nhigher level protocols.\nThis includes discarded packets and unsent\npackets.\n13-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nifOutDiscards (19) Support- According to the stand-\nThe number of packets that had no errors but ed ard.\nwere discarded in the sending process (due\nto a send buffer overflow, etc.).\nifOutErrors (20) Support- According to the stand-\nThe number of packets that could not be sent ed ard.\nbecause of an error.\nifOutQLen (21) Support- Always 0.\nThe size of the send packet queue (i.e., the ed\nnumber of packets).\nifSpecific (22) Support- Always 0.0.\nThe object ID that represents a reference to ed\nthe media-specific MIB for the interface.\nFor example, for Ethernet, set the object ID\nof the MIB that defines Ethernet. If there is no\ninformation, set { 0.0 }.\n Ip Group: Ip\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipForwarding (1) Support- • NX701 CPU Unit:\nIndicates if the device operates as a gateway. ed forwarding (1)\nIP gateways can transfer datagrams, but IP • NX502 CPU Unit:\nhosts can perform only source routing. Some forwarding (1), not-\nnodes take only one of these values. There- forwarding (2)\nfore, if you attempt to change this object from • NX102 CPU Unit:\nthe SNMP Manager, a badValue error is re- forwarding (1), not-\nturned. forwarding (2)\nforwarding (1) • NX1P2 CPU Unit:\nnot-forwarding (2) not-forwarding (2)\n• NJ-series CPU Unit:\nnot-forwarding (2)\nDepends on the set-\ntings in Built-in\nEtherNet/IP Port\nSettings - TCP/IP\nSettings - Port\nForward on the Sys-\nmac Studio.\nIpDefaultTTL (2) Support- Always 64.\nThe default value set for the IP header TTL if ed\nno TTL value was given by the transport lay-\ner protocol.\nIpInReceives (3) Support- According to the stand-\nThe number of all IP datagrams that reached ed ard.\nthe interface, including errors.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-9\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nIpInHdrErrors (4) Support- According to the stand-\nThe number of received datagrams that were ed ard.\ndiscarded because of an IP header error\n(checksum error, version number error, for-\nmat error, TTL error, IP option error, etc.).\nIpInAddrErrors (5) Support- According to the stand-\nThe number of packets that were discarded ed ard.\nbecause the destination address in the IP\nheader was not valid.\nipForwDatagrams (6) Support- According to the stand-\nThe number of IP datagrams that were trans- ed ard.\nferred to their final destination. If this node\ndoes not operate as an IP gateway, this is the\nnumber of datagrams that were successfully\ntransferred through source routing.\nipInUnknownProtos (7) Support- According to the stand-\nThe number of IP datagrams that were re- ed ard.\nceived but discarded because they were of\nan unsupported or unrecognized protocol.\nipInDiscards (8) Support- According to the stand-\nThe number of IP datagrams that could have ed ard.\ncontinued to be processed without any prob-\nlems, but were discarded (for example, be-\ncause of insufficient buffer space).\nipInDelivers (9) Support- According to the stand-\nThe number of datagrams delivered to an IP ed ard.\nuser protocol (any higher level protocol, in-\ncluding ICMP).\nipOutRequests (10) Support- According to the stand-\nThe number of times a send request was ed ard.\nmade for an IP datagram by a local IP user\nprotocol (any higher level protocol, including\nICMP). This counter does not include ipForw-\nDatagrams.\nipOutDiscards (11) Support- According to the stand-\nThe number of IP datagrams that could have ed ard.\nbeen sent without any problems, but were\ndiscarded (for example, because of insuffi-\ncient buffer space).\nipOutNoRoutes (12) Support- According to the stand-\nThe number of IP datagrams that were dis- ed ard.\ncarded because there was no transmission\npath. This counter includes datagrams that\nattempted to be sent through ipForwData-\ngrams, but were discarded because they\nwere set with no-route. This value indicates\nthe number of datagrams that could not be\ntransferred because the default gateway was\ndown.\n13-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipReasmTimeout (13) Support- 60 s\nThe maximum number of seconds to wait to ed\nreceive all IP datagrams for reassembly if a\nfragmented IP datagram is received.\nipReasmReqds (14) Support- According to the stand-\nThe number of IP datagrams received that ed ard.\nrequire reassembly. There is a flag in the IP\nheader that indicates if the datagram is frag-\nmented. You can use that flag to identify frag-\nments.\nipReasmOKs (15) Support- According to the stand-\nThe number of IP datagrams received that ed ard.\nwere successfully reassembled.\nipReasmFails (16) Support- According to the stand-\nThe number of IP datagrams received that ed ard.\nwere not successfully reassembled.\nipFragOKs (17) Support- According to the stand-\nThe number of IP datagrams that were suc- ed ard.\ncessfully fragmented.\nipFragFails (18) Support- According to the stand-\nThe number of IP datagrams that were not ed ard.\nsuccessfully fragmented. (For example, be-\ncause the Don't Fragment flag was set for the\nIP datagram.)\nipFragCreates (19) Support- According to the stand-\nThe number of IP datagrams created as a re- ed ard.\nsult of fragmentation.\nipAddrTable (20) --- ---\nAn address information table for IP address-\nes.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-11\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipAddrEntry (1) --- ---\nRow data of address information for IP ad-\ndresses. The index is ipAdEntAddr.\nipAdEntAddr (1) Support- According to the stand-\nThe IP address. ed ard.\nipAdEntIfIndex (2) Support- According to the stand-\nThe index value of the interface that this en- ed ard.\ntry applies to. This is the same value as ifIn-\ndex.\nipAdEntNet- (3) Support- According to the stand-\nMask The subnet mask for the IP address of this ed ard.\nentry.\nipAdEntBcas- (4) Support- According to the stand-\ntAddr The value of the least significant bit of the ad- ed ard.\ndress when an IP broadcast is sent. An ad-\ndress represented by all 1 bits is used for\nbroadcasting as an Internet standard. In that\ncase, this value is always 1.\nipAdEntReasm- (5) Support- According to the stand-\nMaxSize The maximum IP packet size that can be re- ed ard.\nassembled from IP fragmented input IP data-\ngrams received through the interface.\nipRouteTable (21) --- ---\nThe IP routing table for this entity.\n13-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipRouteEntry (1) --- ---\nRoute information for a specific destination.\nThe index is ipRouteDest.\nipRouteDest (1) Support- According to the stand-\nThe destination IP address for this route. A ed ard.\nvalue of 0.0.0.0 for this entry indicates the\ndefault route.\nipRouteIfIndex (2) Support- According to the stand-\nThe ID number of the interface required to ed ard.\nsend to the next destination host in this route.\nThis ID number is the same number as ifIn-\ndex, which is used to identify the interface.\nipRouteMetric1 (3) Support- According to the stand-\nThe primary routing metric for this route. This ed ard.\nvalue is determined based on the protocol\nspecified in ipRouteProto. Set to -1 if you do\nnot want to use this metric (this is also the\nsame for ipRouteMetric 2 through 4).\nipRouteMetric2 (4) Support- According to the stand-\nThe alternative routing metric for this route. ed ard.\nipRouteMetric3 (5) Support- According to the stand-\nThe alternative routing metric for this route. ed ard.\nipRouteMetric4 (6) Support- According to the stand-\nThe alternative routing metric for this route. ed ard.\nipRouteNex- (7) Support- According to the stand-\ntHop The IP address of the next hop in this route ed ard.\n(for routes connected by a broadcast or me-\ndia, this is the agent address or address of\nthat interface).\nipRouteType (8) Support- According to the stand-\nThe type of route. ed ard.\nother (1): Not any of the following types.\ninvalid (2): An invalid route.\ndirect (3): A direct connection.\nindirect (4): An indirect connection (not con-\nnected to LOCAL).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-13\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipRouteProto (9) Support- According to the stand-\nThis is the routing mechanism used to deter- ed ard.\nmine routes. Some values correspond to\ngateway routing protocols, but be aware that\nthe host may not support those protocols.\nother (1): Other than the following items.\nlocal (2): A route set on the local machine.\nnetmgmt (3): A route set by network manage-\nment.\nicmp (4): A route set by an ICMP redirect or\nsome other ICMP function.\negp (5): EGP\nThe following are gateway protocols:\nggp (6): GGP\nhello (7): HELLO\nrip (8): RIP\nis-is (9)\nes-is (10)\nciscolgrp (11)\nbbnSpflgp (12)\nospf (13): OSPF\nbgp (14)\nipRouteAge (10) Support- Always 0.\nThe elapsed time since this route was updat- ed\ned (in seconds).\nipRouteMask (11) Support- According to the stand-\nThe subnet mask value in relation to ipRou- ed ard.\nteDest.\nOn systems that do not support a custom\nsubnet mask value, this value is based on the\naddress class of the ipRouteDest field.\nIf ipRouteDest is 0.0.0.0, this value is also"}
+{"question": "0.0.0.", "answer": "ipRouteMetric5 (12) Support- According to the stand-\nThe alternative routing metric. ed ard.\nipRouteInfo (13) Support- Always 0.0.\nThe MIB object ID for the routing protocol ed\nused by this route. If not defined, set to {0.0}.\nipNetToMediaTable (22) --- ---\nThe IP address conversion table used to map\nIP addresses to physical addresses.\n13-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nipNetToMediaEntry (1) --- ---\nRow data for the conversion table. The indi-\nces are ipNetToMediaIfIndex and\nipNetToMediaNetAddress.\nipNetToMediaI- (1) Support- According to the stand-\nfIndex The interface ID number for this entry. The ed ard.\nvalue of ifIndex is used for this value.\nipNetToMedia- (2) Support- According to the stand-\nPhysAddress The media-dependent physical address. ed ard.\nipNetToMedia- (3) Support- According to the stand-\nNetAddress The IP address that corresponds to the me- ed ard.\ndia-dependent physical address.\nipNetToMedia- (4) Support- According to the stand-\nType The address conversion method. ed ard.\nother (1): A method other than the following\nitems.\ninvalid (2): An invalid value.\ndynamic (3): Dynamic conversion.\nstatic (4): Static conversion.\nipRoutingDiscards (23) Support- According to the stand-\nThe number of routing entries that were valid ed ard.\nbut discarded. For example, if there was not\nenough buffer space because of other routing\nentries.\n Ip Group: Icmp\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nicmpInMsgs (1) Support- According to the stand-\nThe total number of received ICMP messag- ed ard.\nes. This includes messages counted by icm-\npInErrors.\nicmpInErrors (2) Support- According to the stand-\nThe number of received ICMP message er- ed ard.\nrors. (Checksum errors, frame length errors,\netc.)\nicmpInDestUnreachs (3) Support- According to the stand-\nThe number of Destination Unreachable ed ard.\nmessages received.\nicmpInTimeExcds (4) Support- According to the stand-\nThe number of Time Exceed messages re- ed ard.\nceived.\nicmpInParmProbs (5) Support- According to the stand-\nThe number of Parameter Problem messag- ed ard.\nes received.\nicmpInSrcQuenchs (6) Support- According to the stand-\nThe number of Source Quench messages re- ed ard.\nceived.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-15\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nicmpInRedirects (7) Support- According to the stand-\nThe number of Redirect messages received. ed ard.\nicmpInEchos (8) Support- According to the stand-\nThe number of Echo (request) messages re- ed ard.\nceived.\nicmpInEchoReps (9) Support- According to the stand-\nThe number of Echo Reply messages re- ed ard.\nceived.\nicmpInTimestamps (10) Support- According to the stand-\nThe number of Timestamp messages re- ed ard.\nceived.\nicmpInTimestampReps (11) Support- According to the stand-\nThe number of Timestamp Reply messages ed ard.\nreceived.\nicmpInAddrMasks (12) Support- According to the stand-\nThe number of Address Mask Request mes- ed ard.\nsages received.\nicmpInAddrMaskReps (13) Support- According to the stand-\nThe number of Address Mask Reply messag- ed ard.\nes received.\nicmpOutMsgs (14) Support- According to the stand-\nThe total number of ICMP messages sent. ed ard.\nThis includes messages counted by icmpOu-\ntErrors.\nicmpOutErrors (15) Support- According to the stand-\nThe number of ICMP messages that could ed ard.\nnot be sent because of an error.\nicmpOutDestUnreachs (16) Support- According to the stand-\nThe number of Destination Unreachable ed ard.\nmessages sent.\nicmpOutTimeExcds (17) Support- According to the stand-\nThe number of Time Exceed messages sent. ed ard.\nicmpOutParmProbs (18) Support- According to the stand-\nThe number of Parameter Problem messag- ed ard.\nes sent.\nicmpOutSrcQuenchs (19) Support- According to the stand-\nThe number of Source Quench messages ed ard.\nsent.\nicmpOutRedirects (20) Support- According to the stand-\nThe number of Redirect messages sent. ed ard.\nicmpOutEchos (21) Support- According to the stand-\nThe number of Echo (request) messages ed ard.\nsent.\nicmpOutEchoReps (22) Support- According to the stand-\nThe number of Echo Reply messages sent. ed ard.\nicmpOutTimestamps (23) Support- According to the stand-\nThe number of Timestamp messages sent. ed ard.\nicmpOutTimestam- (24) Support- According to the stand-\npReps The number of Timestamp Reply messages ed ard.\nsent.\n13-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nicmpOutAddrMasks (25) Support- According to the stand-\nThe number of Address Mask Request mes- ed ard.\nsages sent.\nicmpOutAddrMa- (26) Support- According to the stand-\nskReps The number of Address Mask Reply messag- ed ard.\nes sent.\n Ip Group: Tcp\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\ntcpRtoAlgorithm (1) Support- vanj (4)\nThe algorithm used to determine the timeout ed\nvalue for resending.\nother (1): Other than the following items.\nconstant (2): A constant RTO value.\nrsre (3): The algorithm specified by the MIL-\nSTD-1778 standard.\nvanj (4): The Van Jacobson algorithm.\ntcpRtoMin (2) Support- Always 1000.\nThe minimum resend timeout value (in 0.01 ed\ns).\nThis value depends on the algorithm used to\ndetermine the resend timeout value.\ntcpRtoMax (3) Support- Always 64,000.\nThe maximum resend timeout value (in 0.01 ed\ns).\nThis value depends on the algorithm used to\ndetermine the resend timeout value.\ntcpMaxConn (4) Support- Always -1.\nThe total number of supported TCP connec- ed\ntions. If the maximum number of connections\nis dynamic, this value is -1.\ntcpActiveOpens (5) Support- According to the stand-\nThe number of times the TCP connection ed ard.\nchanged from the CLOSE state directly to the\nSYN-SENT state. (Active connection estab-\nlishment.)\ntcpPassiveOpens (6) Support- According to the stand-\nThe number of times the TCP connection ed ard.\nchanged from the LISTEN state directly to\nthe SYN-RCVD state. (Passive connection\nestablishment.)\ntcpAttemptFails (7) Support- According to the stand-\nThe total number of times the TCP connec- ed ard.\ntion changed from the SYN-SENT or SYN-\nRCVD state directly to the CLOSE state and\nfrom the SYN-RCVD state directly to the LIS-\nTEN state.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-17\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\ntcpEstabResets (8) Support- According to the stand-\nThe number of times the TCP connection ed ard.\nchanged from the ESTABLISHED or the\nCLOSE-WAIT state directly to the CLOSE\nstate.\ntcpCurrEstab (9) Support- According to the stand-\nThe total number of TCP connections cur- ed ard.\nrently in the ESTABLISHED or the CLOSE-\nWAIT state.\ntcpInSegs (10) Support- According to the stand-\nThe total number of received segments. This ed ard.\nincludes the number of error segments.\ntcpOutSegs (11) Support- According to the stand-\nThe total number of sent segments. This in- ed ard.\ncludes the number of segments for the cur-\nrent connection, but does not include the\nnumber of segments for resent data only.\ntcpRetransSegs (12) Support- According to the stand-\nThe total number of resent segments. ed ard.\ntcpConnTable (13) --- ---\nThe information table specific to the TCP\nconnection.\n13-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\ntcpConnEntry (1) --- ---\nEntry information related to a specific TCP\nconnection. This value is deleted if the con-\nnection changes to the CLOSE state. The in-\ndices are tcpConnLocalAddress,\ntcpConnLocalPort, tcpConnRemAddress,\nand tcpConnRemPort.\ntcpConnState (1) Support- According to the stand-\nThe status of the TCP connection. ed ard.\nclosed (1)\nlisten (2)\nsynSent (3)\nsynReceived (4)\nestablished (5)\nfinWait1 (6)\nfinWait2 (7)\ncloseWait (8)\nlastAck (9)\nclosing (10)\ntimeWait (11)\ntcpConnLoca- (2) Support- According to the stand-\nlAddress The local IP address of this TCP connection. ed ard.\nA value of 0.0.0.0 is used for connections in\nthe LISTEN state that accept connections\nfrom any IP interface related to the node.\ntcpConnLocal- (3) Support- According to the stand-\nPort The local port number for this TCP connec- ed ard.\ntion.\ntcpConnRe- (4) Support- According to the stand-\nmAddress The remote IP address for this TCP connec- ed ard.\ntion.\ntcpConnRem- (5) Support- According to the stand-\nPort The remote port number for this TCP connec- ed ard.\ntion.\ntcpInErrs (14) Support- According to the stand-\nThe total number of error segments received ed ard.\n(TCP checksum errors, etc.).\ntcpOutRsts (15) Support- According to the stand-\nThe number of segments sent with the RST ed ard.\nflag (the number of times the TCP connection\nwas reset).\n Ip Group: Udp\nEach object can be used for read only.\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nudpInDatagrams (1) ¡ According to the stand-\nThe total number of UDP datagrams (i.e., the ard.\nnumber of packets) sent to the UDP user.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-19\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Implementation spec-\nObject name Support\nStandard specifications ifications\nudpNoPorts (2) ¡ According to the stand-\nThe number of UDP datagrams that were re- ard.\nceived but did not start an application at the\ndestination port.\nudpInErrors (3) ¡ According to the stand-\nThe number of UDP datagrams that were not ard.\nsent to a higher level protocol for a reason\nother than udpNoPorts.\nudpOutDatagrams (4) ¡ According to the stand-\nThe total number of sent UDP datagrams. ard.\nudpTable (5) --- ---\nThe information table for the UDP listener.\nudpEntry (1) --- ---\nAn entry related to a specific UDP listener.\nThe indices are udpLocalAddress and\nudpLocalPort.\nudpLocalAd- (1) ¡ According to the stand-\ndress The local IP address of this UDP listener. A ard.\nvalue of 0.0.0.0 is used for UDP listeners that\naccept datagrams from any IP interface relat-\ned to the node.\nudpLocalPort (2) ¡ According to the stand-\nThe local port number for this UDP listener. ard.\n Ip Group: Snmp\nEach object can be used for read only.\n(Identifier) Sup- Implementation\nObject name\nStandard specifications port specifications\nsnmpInPkts (1) ¡ According to the\nThe total number of SNMP messages received. standard.\nsnmpOutPkts (2) ¡ According to the\nThe total number of SNMP messages sent. standard.\nsnmpInBadVersions (3) ¡ According to the\nThe total number of messages received of an standard.\nunsupported version.\nsnmpInBadCommunity- (4) ¡ According to the\nNames The total number of messages received from standard.\nan unregistered community.\nsnmpInBadCommuni- (5) ¡ According to the\ntyUses The total number of messages received that standard.\nspecify an operation that is not allowed by that\ncommunity.\nsnmpInASNParseErrs (6) ¡ According to the\nThe total number of messages received that re- standard.\nsulted in an ASN.1 error or BER error during\ndecoding.\nsnmpInTooBigs (8) ¡ According to the\nThe total number of PDUs received with an er- standard.\nror status of tooBig.\n13-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\n(Identifier) Sup- Implementation\nObject name\nStandard specifications port specifications\nsnmpInNoSuchNames (9) ¡ According to the\nThe total number of PDUs received with an er- standard.\nror status of noSuchName.\nsnmpInBadValues (10) ¡ According to the\nThe total number of PDUs received with an er- standard.\nror status of badValue.\nsnmpInReadOnlys (11) ¡ According to the\nThe total number of PDUs received with an er- standard.\nror status of readOnly.\nsnmpInGenErrs (12) ¡ According to the\nThe total number of PDUs received with an er- standard.\nror status of genErr.\nsnmpInTotalReqVars (13) ¡ According to the\nThe total number of MIB objects read normally standard.\nafter receiving GetRequest or GetNextRequest.\nsnmpInTotalSetVars (14) ¡ According to the\nThe total number of MIB objects updated nor- standard.\nmally after receiving SetRequest.\nsnmpInGetRequests (15) ¡ According to the\nThe total number of GetRequest PDUs re- standard.\nceived.\nsnmpInGetNexts (16) ¡ According to the\nThe total number of GetNextRequest PDUs re- standard.\nceived.\nsnmpInSetRequests (17) ¡ According to the\nThe total number of SetRequest PDUs re- standard.\nceived.\nsnmpInGetResponses (18) ¡ According to the\nThe total number of GetResponse PDUs re- standard.\nceived.\nsnmpInTraps (19) ¡ According to the\nThe total number of trap PDUs received. standard.\nsnmpOutTooBigs (20) ¡ According to the\nThe total number of PDUs sent with an error standard.\nstatus of tooBig.\nsnmpOutNoSuch- (21) ¡ According to the\nNames The total number of PDUs sent with an error standard.\nstatus of noSuchName.\nsnmpOutBadValues (22) ¡ According to the\nThe total number of PDUs sent with an error standard.\nstatus of badValue.\nsnmpOutGenErrs (24) ¡ According to the\nThe total number of PDUs sent with an error standard.\nstatus of genErr.\nsnmpOutGetRequests (25) ¡ According to the\nThe total number of GetRequest PDUs sent. standard.\nsnmpOutGetNexts (26) ¡ According to the\nThe total number of GetNextRequest PDUs standard.\nsent.\nsnmpOutSetRequests (27) ¡ According to the\nThe total number of SetRequest PDUs sent. standard.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-21\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n(Identifier) Sup- Implementation\nObject name\nStandard specifications port specifications\nsnmpOutGetResponses (28) ¡ According to the\nThe total number of GetResponse PDUs sent. standard.\nsnmpOutTraps (29) ¡ According to the\nThe total number of trap PDUs sent. standard.\nsnmpEnableAuthen- (30) ¡ According to the\nTraps Determines if the agent generates verification standard.\nfailed traps.\nenabled (1)\ndisabled (2)\n lldpMIB Group\nEach object can be used for read only.\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpConfiguration (1) --- ---\nThe MIB for LLDP configuration.\nlldpMessageTxInterval (1) Sup- Variable value\nThe LLDP frame transmission inter- port- depending on\nval. ed setting: 5 to\nDefault value: 30 (seconds) 32,768\nDefault: 30\nlldpMessageTxHoldMultiplier (2) Sup- Variable value\nThe value to determine TTL of the port- depending on\nLLDP frame, this is placed in the ed setting: 1 to 100\nLLDP frame header. Default: 4\nTTL (seconds) = lldpMessageTx-\nHoldMultipler × lldpMessageTxIn-\nterval\nHowever, the maximum value of TTL\nshall be 65,535 seconds.\nDefault value: 4\nlldpReinitDelay (3) Sup- Always 2.\nThe time until re-initialization proc- port-\ness is attempted when lldpPortConfi- ed\ngAdminStatus becomes “disabled”.\nDefault value: 2 (seconds)\nlldpTxDelay (4) Sup- Always 2.\nThe interval between successive port-\nLLDP frame transmissions. ed\nDefault value: 2 (seconds)\nlldpNotificationInterval (5) Sup- Always 0.\nIndicates the transmission interval at port-\nwhich SNMP notifications are sent ed\ndue to information updates from the\nremote system. Only one SNMP no-\ntification is sent even if multiple re-\nmote system information updates\noccur within the transmission inter-\nval.\nDefault value: 30 (seconds)\n13-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpStatistics (2) --- ---\nThe MIB for LLDP statistics informa-\ntion\nlldpStatsRemTablesLastChange- (1) Sup- According to the\nTime Last time when the addition/change/ port- standard.\ndeletion of neighbor information oc- ed\ncurred.\nlldpStatsRemTablesInserts (2) Sup- According to the\nCounts up when neighbor informa- port- standard.\ntion increased. ed\nlldpStatsRemTablesDeletes (3) Sup- According to the\nCounts up when neighbor informa- port- standard.\ntion is deleted. ed\nlldpStatsRemTablesDrops (4) Sup- According to the\nCounts up when neighbor informa- port- standard.\ntion cannot be added due to lack of ed\nresources.\nlldpStatsRemTablesAgeouts (5) Sup- According to the\nCounts up when the retention time port- standard.\nexpired and the neighbor information ed\nbecame invalid.\nlldpStatsTxPortTable (6) --- ---\nThe table containing transmission\nframe statistics information for indi-\nvidual LLDP transmission ports.\nlldpStatsTxPortEntry (1) --- ---\nThe table entry of transmission\nframe statistics information for indi-\nvidual LLDP transmission ports.\nlldpStatsTxPort- (1) --- ---\nNum The interface index value used to\nidentify the LLDP transmission port.\nlldpStatsTxPort- (2) Sup- According to the\nFramesTotal The number of LLDP frame trans- port- standard.\nmissions on the LLDP transmission ed\nport.\nlldpStatsRxPortTable (7) --- ---\nThe table containing reception frame\nstatistics information for individual\nLLDP reception ports.\nlldpStatsRxPortEntry (1) --- ---\nThe table entry of reception frame\nstatistics information for individual\nLLDP reception ports.\nlldpStatsRxPort- (1) --- ---\nNum The interface index value used to\nidentify the LLDP reception port.\nlldpStatsRxPort- (2) Sup- According to the\nFramesDiscar- The total number of discarded LLDP port- standard.\ndedTotal frames on the LLDP reception port. ed\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-23\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpStatsRxPort- (3) Sup- According to the\nFramesErrors The number of invalid LLDP frames port- standard.\nreceived on the LLDP reception port. ed\nlldpStatsRxPort- (4) Sup- According to the\nFramesTotal The number of valid LLDP frames port- standard.\nreceived on the LLDP reception port. ed\nlldpStatsRx- (5) Sup- According to the\nPortTLVsDiscar- The total number of discarded TLVs port- standard.\ndedTotal on the LLDP reception port. ed\nlldpStatsRx- (6) Sup- According to the\nPortTLVsUnre- The number of TLVs received in the port- standard.\ncognizedTotal previous version on the LLDP recep- ed\ntion port.\nlldpStatsRxPortA- (7) Sup- According to the\ngeoutsTotal Counts up when the retention time port- standard.\nexpired and the neighbor information ed\nbecame invalid on the LLDP recep-\ntion port.\nlldpLocalSystemData (3) --- ---\nThe MIB for information regarding\nthe LLDP local system.\nlldpLocChassisIdSubtype (1) Sup- macAddress(4)\nThe chassis type for the local sys- port-\ntem. ed\nlldpLocChassisId (2) Sup- Port 1 macAd-\nThe identifier of the chassis compo- port- dress\nnent for the local system. ed\nlldpLocSysName (3) Sup- • NX502 CPU\nThe system name for the local sys- port- Unit:\ntem. ed Host Name\n• NX102 CPU\nUnit:\nCPU Unit\nName\nlldpLocSysDesc (4) Sup- \"OMRON\nThe system information for the local port- Corporation\" +\nsystem. ed CPU Unit model\n+ CPU Unit ver-\nsion\n• CPU Unit\nmodel (exam-\nple):\nNJ501-1200\n• CPU Unit ver-\nsion (exam-\nple): Version"}
+{"question": "0", "answer": "13-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpLocSysCapSupported (5) Sup- stationOnly(7)\nThe bitmap representation of the list port-\nof functions supported by the local ed\nsystem.\nlldpLocSysCapEnabled (6) Sup- stationOnly(7)\nThe bitmap representation of the list port-\nof functions running on the local sys- ed\ntem.\nlldpLocPortTable (7) --- ---\nThe table of LLDP ports on the local\nsystem.\nlldpLocPortEntry (1) --- ---\nThe table entry of a LLDP port on\nthe local system.\nlldpLocPortNum (1) --- ---\nThe interface index value used to\nidentify the LLDP port.\nlldpLocPortIdSub- (2) Sup- Port 1: macAd-\ntype The type indicating the port ID of the port- dress(3)\nlocal system. ed Port 2: macAd-\ndress(3)\nlldpLocPortId (3) Port 1: Port 1\nThe port ID (string) for the local sys- Sup- macAddress\ntem port. port- Port 2: Port 2\ned macAddress\nlldpLocPortDesc (4) Sup- • NX502 CPU\nThe port information (string) for the port- Unit:\nlocal system port. ed 10/100/1000\nM Gigabit\nEthernet Port\n• NX102 CPU\nUnit:\n10/100M Fast\nEthernet Port\nlldpLocManAddrTable (1) --- ---\nThe table of management address\non the local system.\nlldpLocManAddrEntry (1) --- ---\nThe table entry of management ad-\ndress on the local system.\nlldpLocManAddr- (1) --- ---\nSubtype Indicates the type of management\naddress on the local system.\nlldpLocManAddr (2) --- ---\nThe management address to identify\nthe local system.\nlldpLocManAddr- (3) Sup- Always 5.\nLen The length of LLDP management port-\naddress field transmitted from the lo- ed\ncal system.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-25\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpLocManAddrIf- (4) Sup- ifIndex(2)\nSubtype The type related to the numbering port-\nmethod for the local system inter- ed\nface.\nlldpLocManAddrI- (5) Sup- Always 2.\nfId The interface number related to the port-\nlocal system management address. ed\nlldpLocManAd- (6) Sup- SNMPv2-\ndrOID The ID that identifies the hardware port- SMI::zeroDot-\ncomponent or protocol type of the lo- ed Zero\ncal system.\nlldpV2RemoteSystemsData (4) --- ---\nThe MIB for information regarding\nthe remote system that is connected\nto the LLDP local system.\nlldpRemTable (1) --- ---\nThe table of information from the re-\nmote system.\nlldpRemEntry (1) --- ---\nThe table entry of information from\nthe remote system.\nlldpRemTimeMark (1) --- ---\nThe time elapsed after the informa-\ntion of the remote system was ob-\ntained.\nlldpRemLocal- (2) --- ---\nPortNum The interface index value used to\nidentify the port information from the\nremote system.\nlldpRemIndex (3) --- ---\nThe unique ID provided as an index\nwhen a RemEntry is created.\nlldpRemChassi- (4) Sup- According to the\nsIdSubtype The chassis type for the remote sys- port- standard.\ntem. ed\nlldpRemChassisId (5) Sup- According to the\nThe chassis ID for the remote sys- port- standard.\ntem. ed\nlldpRemPortId- (6) Sup- According to the\nSubtype The type indicating the port ID for port- standard.\nthe remote system. ed\nlldpRemPortId (7) Sup- According to the\nThe port ID for the remote system. port- standard.\ned\n(8) Sup- According to the\nThe description (string) to identify port- standard.\nthe port of remote system. ed\nlldpRemSysName (9) Sup- According to the\nThe system name for the remote port- standard.\nsystem. ed\n13-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nImplementa-\n(Identifier) Sup-\nObject name tion specifica-\nStandard specifications port\ntions\nlldpRemSysDesc (10) Sup- According to the\nThe description (string) to identify port- standard.\nthe remote system. ed\nlldpRemSysCap- (11) Sup- According to the\nSupported The bitmap representation of the list port- standard.\nof functions supported by the remote ed\nsystem.\nlldpRemSysCa- (12) Sup- According to the\npEnabled The bitmap representation of the list port- standard.\nof functions running on the remote ed\nsystem.\nlldpRemManAddrTable (2) --- ---\nThe table of management address\ncontrol on the remote system.\nlldpRemManAddrEntry (1) --- ---\nThe table entry of management ad-\ndress on the remote system.\nlldpRemManAddr- (1) --- ---\nSubtype Indicates the type of management\naddress on the remote system.\nlldpRemManAddr (2) --- ---\nThe management address of the re-\nmote system.\nlldpRemManAd- (3) Sup- According to the\ndrIfSubtype The type related to the numbering port- standard.\nmethod for the remote system inter- ed\nface.\nlldpRemManAd- (4) Sup- According to the\ndrIfId The interface number related to the port- standard.\nmanagement address of the remote ed\nsystem.\nlldpRemManAd- (5) Sup- According to the\ndrOID The ID indicating hardware configu- port- standard.\nration and protocols related to the ed\nmanagement address of the remote\nsystem.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-27\n13-1\nSNMP\nAgent\n13\n13-1-4\nMIB\nSpecifications\n13 SNMP Agent\n13-2 Procedure to Use the SNMP Agent\n13-2-1 Procedures"}
+{"question": "Make the basic settings.", "answer": "Refer to 1-5 EtherNet/IP Communications Procedures on page 1-30 for the basic operation\nflow."}
+{"question": "Select Controller Setup - Built-in EtherNet/IP Port Settings on the Sysmac Studio.", "answer": "Make the following settings on the SNMP Settings Display or the SNMP Trap Settings Dis-\nplay.\n• SNMP Service\n• Recognition 1\n• Recognition 2"}
+{"question": "Select Transfer to Controller from the Controller Menu and click the Yes Button. The built-in", "answer": "EtherNet/IP port settings are transferred to the CPU Unit.\nPrecautions for Correct Use\nIf the Use Option is selected for Packet Filter of the built-in EtherNet/IP port, allow packets from\nthe SNMP manager. If they are not permitted, communication with SNMP manager is not possi-\nble. For the details on the settings, refer to Packet Filter on page 4-8.\n13-2-2 Settings Required for the SNMP Agent\nThe following Built-in EtherNet/IP Port Settings are made from the Sysmac Studio to use the SNMP\nagent.\nTab page Setting Setting conditions Reference\nSNMP Settings SNMP service Required. page 4-17\nPort No. Specified by user.\nRequired to change from the default value\nof 161.\nContact, location Specified by user.\nSend a recognition trap Specified by user.\nSelect this check box to send a recogni-\ntion trap if there is access from an SNMP\nmanager that is not specified (Access oth-\ner than Recognition 1 and 2).\nRecognition 1 and Recog- Specified by user. page 4-18\nnition 2 Make these settings to permit access by\nonly certain SNMP managers.\nIP address\nHost name\nCommunity name\n13-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n13 SNMP Agent\nTab page Setting Setting conditions Reference\nSNMP Trap Settings SNMP trap Required page 4-19\nPort No. Specified by user.\nRequired to change from the default value\nof 162.\nTrap 1 and trap 2 page 4-19\nIP address Required\nHost name Set an IP address or a host name as the\nSNMP trap destination.\nCommunity name Specified by user.\nVersion Required\nSet the version of the SNMP manager.\nAdditional Information\nMake the settings in the SNMP Settings Display and the SNMP Trap Settings Display if the\nSNMP agent is used.\nRefer to 4-5 SNMP Settings Display on page 4-17 for information on the SNMP Settings Dia-\nlog Box. Refer to 4-6 SNMP Trap Settings Display on page 4-19 for information on the SNMP\nTrap Dialog Box.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 13-29\n13-2\nProcedure\nto\nUse\nthe\nSNMP\nAgent\n13\n13-2-2\nSettings\nRequired\nfor\nthe\nSNMP\nAgent\n13 SNMP Agent\n13-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14\nCommunications Performance\nand Communications Load\n14-1 Communications System............................................................................14-2\n14-1-1 Tag Data Link Communications Method........................................................14-2\n14-1-2 Calculating the Number of Connections........................................................14-4\n14-1-3 Packet Interval (RPI) Accuracy.....................................................................14-5\n14-2 Adjusting the Communications Load.........................................................14-7\n14-2-1 Checking Bandwidth Usage for Tag Data Links............................................14-8\n14-2-2 Tag Data Link Bandwidth Usage and RPI.....................................................14-9\n14-2-3 Adjusting Device Bandwidth Usage............................................................14-10\n14-2-4 Changing the RPI.........................................................................................14-11\n14-2-5 RPI Setting Examples.................................................................................14-16\n14-3 I/O Response Time in Tag Data Links......................................................14-23\n14-3-1 Timing of Data Transmissions.....................................................................14-23\n14-3-2 Built-in EtherNet/IP Port Data Processing Time..........................................14-24\n14-3-3 Relationship between Task Periods and Packet Intervals (RPIs)................14-26\n14-3-4 Maximum Tag Data Link I/O Response Time..............................................14-27\n14-4 Message Service Transmission Delay.....................................................14-30\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-1\n14\n14 Communications Performance and Communications Load\n14-1 Communications System\n14-1-1 Tag Data Link Communications Method\nRequested Packet Interval (RPI) Settings\nIn tag data links for the built-in EtherNet/IP port, the data transmission period is set for each connec-\ntion as the RPI.\nThe target device sends data (i.e., output tags) based on the specified RPI, regardless of the number\nof nodes.\nAlso, the heartbeat frame is sent from the originator to the target device for each connection. The tar-\nget device uses the heartbeat to check if any errors have occurred in the connection with the origina-\ntor. The data transmission period of the heartbeat frame depends on the RPI settings.\nHeartbeat Frame Transmission Period\n• If packet interval is shorter than 100 ms, the heartbeat frame transmission period is 100 ms.\n• If packet interval is equal to or larger than 100 ms, the heartbeat frame transmission period is the\nsame as the RPI.\nExample)\nIn this example, two tag data link connections are set for node 2 (the originator) and node 1 (the tar-\nget).\nThe RPI for output data 1 is set to 10 ms.\nThe RPI for output data 2 is set to 15 ms.\nIn this case, output data 1 is sent from node 1 to node 2 every 10 ms, and output data 2 is sent from\nnode 1 to node 2 every 15 ms, as shown in the following diagram.\nAlso, data is sent from node 2 (the originator) to node 1 (the target) with a heartbeat of 100 ms for\nconnection 1 and a heartbeat of 100 ms for connection 2.\n14-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nNode 1 Node 2\nTarget Output data 1 Originator\nConnection 1 heartbeat\n100-ms interval\nOutput data 2\n10 ms\nConnection 2 heartbeat\n100-ms interval\nOutput data 1\n15 ms\n10 ms\nOutput data 2\nOutput data 1\nRequested Packet Interval (RPI) and Bandwidth Usage (PPS)\nThe number of packets transferred each second is called the used bandwidth, or PPS (packets per\nsecond).\nThe PPS is calculated from the RPI and heartbeat for each connection as follows:\nPPS for a connection (pps)\n= (1,000/RPI (ms)) + (1,000/Heartbeat transmission period (ms))\nUse the following equation to calculate the total number of packets transferred by each built-in Ether-\nNet/IP port (Unit) in 1 second.\nTotal PPS for the built-in EtherNet/IP port = Total PPS of originator connections + Total PPS of target\nconnections (*)\n* Connections set as target connections must be added, too.\nThe following shows the maximum number of packets that each CPU Unit can send and receive per\nsecond via the built-in EtherNet/IP port through tag data links (i.e., the allowed communications band-\nwidth per Unit). You need to consider these values when configuring connections.\n• NX701 CPU Unit: 40,000 pps\n• NX502 CPU Unit: 20,000 pps\n• NX102 CPU Unit: 12,000 pps\n• NX1P2 CPU Unit: 3,000 pps\n• NJ-series CPU Unit: 3,000 pps (*)\n*Note that the bandwidth allowed for NJ-series CPU Units with unit version 1.00 to 1.02 is 1,000 pps.\nExample)\nNode 1 has an originator connection with the receive RPI of 500 ms, and two target connections with\nthe send RPIs of 200 ms and 2 ms.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-3\n14-1\nCommunications\nSystem\n14\n14-1-1\nTag\nData\nLink\nCommunications\nMethod\n14 Communications Performance and Communications Load\nNode 2 has three originator connections with the receive RPIs of 200 ms, 2 ms, and 5 ms.\nNode 3 has two target connections with the send RPIs of 5 ms and 1 ms.\nO: Originator\nNode 1\nT: Target\nT T O\nHB: Heartbeat\nRPI: 200 ms\nHB: 200 ms\nRPI: 500 ms\nRPI: 2 ms HB: 500 ms\nHB: 100 ms\nO O T\nNode 2 Node 3\nO RPI: 5 ms T\nHB: 100 ms\nThe total PPS of each node is calculated as follows:\n• Total PPS of the Unit Node 1\n= 1,000/200 ms + 1,000/2 ms+ 1,000/500 ms (for data)\n+ 1,000/200 ms + 1,000/100 ms + 1,000/500 ms (for heartbeat)\n= 524 pps\n• Total PPS of the Unit Node 2\n= 1,000/200 ms + 1,000/2 ms + 1,000/5 ms (for data)\n+ 1,000/200 ms + 1,000/100 ms + 1,000/100 ms (for heartbeat)\n= 730 pps\n• Total PPS of the Unit Node 3\n= 1,000/5 ms + 1,000/500 ms (for data)\n+ 1,000/100 ms + 1,000/500 ms (for heartbeat)\n= 214 pps\nIn this example, the total PPS of each Unit is below the maximum bandwidth allowed for the Unit, so\ndata transmission can be successfully performed.\n14-1-2 Calculating the Number of Connections\nThe maximum number of connections per built-in EtherNet/IP port on a CPU Unit is as follows.\n• NX701 CPU Unit: 256\n• NX502 CPU Unit: 64\n• NX102 CPU Unit: 32\n• NX1P2 CPU Unit: 32\n• NJ-series CPU Unit: 32\nThe maximum number of connections for a Unit should not be exceeded by the total number of origi-\nnator connections, which the Unit opens, and target connections, which other nodes open to the Unit.\nExample)\nNode 1 has two target connections with Node 2, and opens one originator connection to Node 3. So,\nNode 1 has three connections in total.\nNode 2 opens two originator connections to Node 1, and one originator connection to Node 3. So,\nNode 2 has three connections in total.\nNode 3 has one target connection with Node 1, and one target connection with Node 2. So, Node 3\nhas two connections in total.\n14-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nIn either case, the connections can be successfully opened since the total number of connections is\nbelow the maximum number for a built-in EtherNet/IP port, as shown above.\nO: Originator\nNode 1\nT: Target\nT T O\nO O T\nNode 2 Node 3\nO T\nIf multicast is specified for data transmission and the node sends out just one multicast packet to other\nnodes, it requires respective connections for them.\nExample)\nNode 3 sends out one multicast packet to Node 1 and Node 2. Node 3 has one target connection with\nNode 1, and one target connection with Node 2, requiring two connections in total.\nYou need to keep in mind that the number of required connections is the same, whether multicast or\nunitcast is specified for the communications.\nO: Originator\nNode 1\nT: Target\nO\nMulticast\nT\nMulticast\nNode 2 Node 3\nO T\n14-1-3 Packet Interval (RPI) Accuracy\nA send processing delay occurs in a built-in EtherNet/IP port when data packets are sent based on a\npacket interval (RPI).\nThis delay varies within the RPI error margin as shown below, so the send processing may be delayed\nfor the maximum value for each RPI.\nPacket interval (RPI) RPI error margin (±) (%)"}
+{"question": "5 to 1,000 ms (NX701 CPU Unit) 15 − (RPI [ms]/100)", "answer": "1 to 1,000 ms (NX502 and NX102 CPU Units)\n2 to 1,000 ms (NX1P2 CPU Unit)\n1 to 1,000 ms (NJ-series CPU Unit)*1\n1,000 to 10,000 ms 5% of the RPI\n*1. Note that the RPI for a NJ-series CPU Unit with unit version 1.00 to 1.02 is between 10 ms to 1,000 ms.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-5\n14-1\nCommunications\nSystem\n14\n14-1-3\nPacket\nInterval\n(RPI)\nAccuracy\n16\n14\n12\n10\n8\n6\n4\n2\n0\nRPI [ms]\n)%(\n)±(\nrorre\nIPR\n14 Communications Performance and Communications Load\n0 1000 2000 3000 4000 5000 6000 7000 8000 9000 10000\n14-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\n14-2 Adjusting the Communications Load\nIn an Ethernet network using an Ethernet switch, the network bandwidth is not shared by all of the no-\ndes; independent transmission paths are established between individual nodes through the Ethernet\nswitch.\nA dedicated communications buffer is established in the Ethernet switch for communications between\nthe nodes, and full-duplex communications (simultaneous transmission and reception) are performed\nasynchronously with other transmission paths. The communications load in other transmission paths\ndoes not affect communications, so packet collisions do not occur and stable, high-speed communica-\ntions can be performed.\nThe Ethernet switch functions shown in the following table determine the performance of tag data\nlinks.\nItem Description\nBuffer capacity This is the amount of data that can be buffered when packets ac-\ncumulate at the Ethernet switch.\nMulticast filtering This function transfers multicast packets to specific nodes only.\nQoS function This function performs priority control on packet transfers.\nThe following table shows the setting ranges of the tag data link settings that can be made for a built-\nin EtherNet/IP port.\nNX-series CPU Unit NJ-series CPU Unit\nUnit ver- Unit ver-\nItem Description\nNX701 NX502 NX102 NX1P2 sion 1.00 sion 1.03\nto 1.02 or later\nNetwork band- Physical 1,000 Mbps 100 Mbps or 10 Mbps\nwidth Ethernet\nbaud rate\nAllowable tag da- Maximum 40,000 20,000 12,000 3,000 pps 1,000 pps 3,000 pps\nta link communi- number of tag pps max. pps max. pps max. max. max. max.\ncations band- data link (total of (total of (total of\nwidth packets that 40,000 20,000 12,000\ncan be proc- pps with pps with pps with\nessed in 1 two ports) two ports) two ports)\nsecond (pps:\npackets per\nsecond)\nConnection re- Number of 256 max. 64 max. 32 max. 32 max.\nsources connections (total of (total of (total of 64\nthat can be 512 with 128 with with two\nestablished two ports) two ports) ports)\nPacket interval Refresh peri- 0.5 to 1 to 10,000 ms in 1-ms 2 to 10 to 1 to\n(RPI: Requested od for tag da- 10,000 ms increments 10,000 ms 10,000 ms 10,000 ms\nPacket Interval) ta in 0.5-ms in 1-ms in- in 1-ms in- in 1-ms in-\nincre- crements crements crements\nments\nWhen the tag data link settings exceed the capabilities of the Ethernet switch to be used, increase the\npacket interval (RPI) value for adjustment.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-7\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-1\nChecking\nBandwidth\nUsage\nfor\nTag\nData\nLinks\n14 Communications Performance and Communications Load\nParticularly when you configure the settings with an Ethernet switch that does not support multicast\nfiltering, you need to consider that multicast packets will be sent to all the nodes on the network with-\nout setting the connections.\nAdditional Information\nIf you select Multi-cast Connection for the connection type in the connection settings on the\nNetwork Configurator, multicast packets are used. If the connection type is set to a Point to\nPoint Connection, multicast packets are not used.\nIf required tag data link performance cannot be achieved with the Ethernet switch, re-evaluate the\noverall network configuration and take necessary measures such as selecting a different Ethernet\nswitch or splitting the network.\nThe following sections show how to check the device bandwidth used by the tag data links in the de-\nsigned network, and how to set appropriate values.\n14-2-1 Checking Bandwidth Usage for Tag Data Links\nThe Network Configurator can display the bandwidth to be actually used for tag data links at each\nbuilt-in EtherNet/IP port, based on the connections set in the network configuration.\nThe device bandwidth used for tag data links can be checked by clicking the Detail Button in the\nUsage of Device Bandwidth Area at the bottom of the Network Configuration Window.\nItem Description\n# The IP address of the device.\nComment A description of the device. The comment is displayed below the device icon.\nThe model number of the device is displayed by default.\nUsage of Capacity (without The usage rate of allowable tag data link bandwidth for the device is given.\nMulticast Filter) Bandwidth used/Allowable tag data link bandwidth\nThe values outside parentheses are for when multicast filtering is used.\nThe values inside parentheses are for when multicast filtering is not used.\nMbit/s (without Multicast Fil- The network bandwidth used by the device for tag data link communications is\nter) given.\nThe values outside parentheses are for when multicast filtering is used.\nThe values inside parentheses are for when multicast filtering is not used.\n14-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nItem Description\nUsage of IP multicast ad- The number of multicast IP addresses actually used by the device for commu-\ndresses nications is given.\nTotal usage of IP multicast ad- The number of multicast IP addresses used in the entire network is given. This\ndresses value is used to estimate the number of multicast filters required for a switch.\nNetwork Total of Max. Mbit/s The total bandwidth used for tag data link communications in the entire network\nis given.\nTag data links will not normally operate if the bandwidth allowed for the network\nis exceeded.\n Checking the Usage of Capacity and Network Bandwidth for Tag Data\nLinks\nThe usage rate of allowable tag data link bandwidth for each built-in EtherNet/IP port is given in the\nUsage of Capacity (without Multicst Filter) column, and the network bandwidth usage for tag da-\nta link communications is given in the Mbit/s (without Multicast Filter) column.\nThe usage rate and the network bandwidth usage of tag data link communications for which multi-\ncast filtering is not supported by the Ethernet switch are given in parentheses in each correspond-\ning column. These values include bandwidth usage for multicast packets since they are sent to all\nthe nodes without connection settings.\nThese values can be adjusted as described in 14-2-4 Changing the RPI on page 14-11.\n Checking the Total Number of Multicast IP Addresses in the Network\nWhen using an Ethernet switch that supports multicast filtering, there must be sufficient multicast\nfilters for the network. Based on the setting of connections, the Network Configurator indicates the\nnumber of multicast IP addresses to be used in the entire network.\nMake sure that the number of multicast IP addresses to be used in the entire network does not ex-\nceed the number of multicast filters supported by the Ethernet switch. If necessary, replace the\nEthernet switch with another one with sufficient multicast filters, or adjust the usage rate and net-\nwork bandwidth usage with the values given for an Ethernet switch without multicast filtering (i.e.,\nthe values in parentheses). These values can be adjusted as described in 14-2-4 Changing the RPI\non page 14-11.\n Checking the Total Maximum Network Bandwidth\nThe Network Configurator displays the total maximum bandwidth to be used for the entire network.\nThis value indicates the maximum possible bandwidth for a transmission path which connects\nEthernet switches in cascade. If this value exceeds the bandwidth for each cascade connection in\nthe actual network (e.g., 1,000 Mbps for an NX-series CPU Unit, or 100 Mbps for an NJ-series\nCPU Unit), the bandwidth for some transmission paths may be exceeded depending on the net-\nwork wiring, and the tag data links may not operate normally.\nIf this occurs, calculate the bandwidth usage of each transmission path and make sure that the\nbandwidth for any cascade connection is not exceeded, or adjust the bandwidth to ensure that the\nvalue of Network Total of Max. Mbit/s does not exceed the bandwidth for any cascade connec-\ntion. These values can be adjusted as described in 14-2-4 Changing the RPI on page 14-11.\n14-2-2 Tag Data Link Bandwidth Usage and RPI\nThe usage rate of allowable tag data link bandwidth as given in the Usage of Capacity (without\nMulticast Filter) column can be adjusted by changing the packet interval (RPI) setting.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-9\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-2\nTag\nData\nLink\nBandwidth\nUsage\nand\nRPI\n14 Communications Performance and Communications Load\nIf the RPI is set shorter, the Usage of Capacity (without Multicast Filter) will increase.\nIf the RPI is set longer, the Usage of Capacity (without Multicast Filter) will decrease.\nThe RPI can be set in one of the following ways.\n• Setting the same PRI for all the connections\n• Setting a PRI for connections of a particular device\n• Setting a PRI for a particular connection\nWhen the same RPI is set for all the connections, the Usage of Capacity (without Multicast Filter)\nwill basically increase proportionally as the RPI is set shorter.\nExample: If the Usage of Capacity (without Multicast Filter) is 40% with the PRI set to 50 ms for all\nthe connections, the Usage of Capacity (without Multicast Filter) may increase to 80% when the\nRPI is changed to 25 ms for all the connections.\nPrecautions for Correct Use\nIf the Usage of Capacity (without Multicast Filter) is between 80% and 100%, some opera-\ntion with the Network Configuator which may cause load on the network, such as monitoring, or\nmessage communications with some user application may temporarily cause excessive load on\nthe network and result in timeouts. If timeouts occur, increase one or all of the RPI values and\nreduce the usage of capacity.\n14-2-3 Adjusting Device Bandwidth Usage\nThis section provides methods for adjusting the device bandwidth usage for tag data links.\nPrecautions for Correct Use\nThe Ethernet switch should be able to support the maximum network bandwidth for each CPU\nUnit. The maximum network bandwidth for each CPU Unit model is as follows.\n• NX701 CPU Unit: 1,000 Mbit/s\n• NX502 CPU Unit: 1,000 Mbit/s\n• NX102 CPU Unit: 100 Mbit/s\n• NX1P2 CPU Unit: 100 Mbit/s\n• NJ-series CPU Unit: 100 Mbit/s\nEthernet Switches without Multicast Filtering\n• Is the Mbit/s (without Multicast Filter) value for each node below the maximum network band-\nwidth?\nIf any node exceeds the maximum network bandwidth, change the connection settings, such as the\nRPI.\n• Is the value of Usage of Capacity (without Multicast Filter) for each node below 100%?\nIf any node exceeds 100%, change the connections settings, such as the RPI.\n• Is the value of Network Total of Max. Mbit/s below the maximum network bandwidth?\nIf the value exceeds the maximum network bandwidth, the bandwidth for some transmission paths\n(e.g., an Ethernet switch or media converter) may be exceeded depending on the network wiring\n(e.g., cascade connection of Ethernet switches), and the tag data links may not operate normally.\nCheck if the bandwidth of the transmission path in each cascade connection is not exceeded. If the\nbandwidth is exceeded, rewire the network or increase the bandwidth between Ethernet switches\n14-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\n(e.g., increase to 1 Gbps). If these countermeasures are not possible, change the connection set-\ntings such as the RPI settings, and adjust the bandwidth to ensure that the value of Network Total\nof Max. Mbit/s does not exceed the bandwidth for any cascade connection.\nEthernet Switches with Multicast Filtering\n• Is the Mbit/s value for each node below the maximum network bandwidth?\nIf any node exceeds the maximum network bandwidth, change the connection settings, such as the\nRPI.\n• Is the Usage of Capacity value for each node below 100%?\nIf any node exceeds 100%, change the connection settings, such as the RPI.\n• Is the Network Total of Max. Mbit/s value below the maximum network bandwidth?\nIf the value exceeds the maximum network bandwidth, the bandwidth for some transmission paths\n(e.g., an Ethernet switch or media converter) may be exceeded due to the network wiring (e.g., cas-\ncade connection of Ethernet switches), and the tag data links may not operate normally. Check if the\nbandwidth of the transmission path in each cascade connection is not exceeded. If the bandwidth is\nexceeded, rewire the network or increase the bandwidth between Ethernet switches (e.g., to 1\nGbps). If these countermeasures are not possible, change the connection settings such as the RPI\nsettings, and adjust the bandwidth to ensure that the value of Network Total of Max. Mbit/s does\nnot exceed the bandwidth for any cascade connection.\n• Is the Mbit/s (without Multicast Filter) value for each node below the maximum network band-\nwidth? Or, is the value of Usage of Capacity (without Multicast Filter) for each node below\n100%?\nIf any node exceeds either of them, check whether the multicast filtering on the relevant Ethernet\nswitch is functioning correctly. If the number of multicast filters on the Ethernet switch is less than\nthe number of Total usage of IP multicast addresses, the bandwidth for some transmission paths\nmay be exceeded depending on the network wiring (e.g., cascade connection of Ethernet switches),\nand the tag data links may not operate normally. Calculate the number of multicast filters required\nfor each Ethernet switch on the network, and check if the resulting number is below the number of\nmulticast filters provided by the Ethernet switch. If the Ethernet switch does not have a sufficient\nnumber of multicast filters, replace it with another one which has sufficient multicast filters, or\nchange the connection settings, such as the RPI settings.\n14-2-4 Changing the RPI\nYou can check Usage of Capacity (without Multicast Filter) values offline for the usage rate of al-\nlowable tag data link bandwidth if you follow the procedure provided in 14-2-1 Checking Bandwidth\nUsage for Tag Data Links on page 14-8.\nYou can adjust Usage of Capacity (without Multicast Filter) values by changing packet interval\n(RPI) values.\nIf required communications performance cannot be achieved after the adjustment, re-evaluate the net-\nwork configuration.\n1\nMake required settings in the Network Configuration Window on the Network Configurator.\n2\nClick the Detail Button in the Usage of Device Bandwidth Area at the bottom of the Network\nConfiguration Window.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-11\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-4\nChanging\nthe\nRPI\n14 Communications Performance and Communications Load\nThe Usage of Device Bandwidth Dialog Box is displayed.\nThe Usage of Capacity (without Multicast Filter) column shows the usage rate of allowable\ntag data link bandwidth, and the Mbit/s (without Multicast Filter) column shows the network\nbandwidth usage.\n3\nYou can adjust the Usage of Capacity (without Multicast Filter) value by changing the pack-\net interval (RPI) for the relevant device.\nThere are three methods for changing the RPI as shown below.\n• Method 1: Set the Same RPI for All the Connections\nYou can adjust the Usage of Capacity (without Multicast Filter) value by changing the\npacket interval (RPI) values for all the connections at the same time.\n1) Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog\nBox.\n14-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\n2) The Set Packet Interval (RPI) Dialog Box is displayed. Input a new RPI value, and click\nthe OK Button.\n• Method 2: Change the RPI for a Specific Device\nYou can adjust the Usage of Capacity (without Multicast Filter) value by changing the RPI\nfor all the connections of a specific device.\nNote that the Usage of Capacity (without Multicast Filter) values for the target devices of\nthe connections are also changed.\n1) Click the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog\nBox.\n2) The Set Packet Interval (RPI) Dialog Box is displayed. In the Target Device Area, clear\nthe check boxes for devices to which this RPI setting change is not applied.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-13\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-4\nChanging\nthe\nRPI\n14 Communications Performance and Communications Load\n3) Input a new RPI value, and click the OK Button.\n• Method 3: Change the RPI for a Specific Connection\nYou can adjust the Usage of Capacity (without Multicast Filter) value by changing the RPI\nfor a specific connection.\nNote that the Usage of Capacity (without Multicast Filter) value for the target device of the\nconnection are also changed.\n1) Click the Close Button in the Usage of Device Bandwidth Dialog Box.\n2) Double-click the device that is set as the originator of the connection. The Edit Device\nParameters Dialog Box is displayed.\n14-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\n3) In the Register Device List Area, select the connection for which you want to change\nthe RPI, and click the Edit Button.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-15\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-4\nChanging\nthe\nRPI\n14 Communications Performance and Communications Load\n4) The Edit Connection Dialog Box for the device is displayed. Input a new packet interval\n(RPI) value, and click the OK Button.\n4\nIf the bandwidth usage rate is not set as desired even after the above operation, re-evaluate\nthe network configuration,considering the following points. (Refer to 14-2-3 Adjusting Device\nBandwidth Usage on page 14-10.)\n• Reduce the number of nodes and connections\n• Split the network\n5\nCheck the bandwidth usage rate again.\nAfter you change the connection settings, click the Detail Button in the Usage of Device\nBandwidth Area at the bottom of the Network Configuration Window to check the bandwidth\nusage as described in 14-2-1 Checking Bandwidth Usage for Tag Data Links on page 14-8.\nIt is important to check the bandwidth usage particularly after you change the RPI values for\nindividual connections, instead of setting the same RPI for all the connections.\n6\nRun user tests to verify that there are no problems with the new values.\n14-2-5 RPI Setting Examples\nThe following examples explain how to calculate the packet intervals (RPIs) in the following network\nconfiguration.\n14-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nConditions\n• Connections:\nExample) Seventeen NJ501-1300 Units are connected to the network.\nEach device has one 100-word tag for sending and sixteen 100-word tags for receiving, and ex-\nchanges data with each other.\nThe packet interval (RPI) for all the connections is set to 120 ms.\nThe IP addresses of the devices range from 192.168.250.1 to 192.168.250.17.\nIP address: 192.168.250.1 192.168.250.2 192.168.250.3 192.168.250.17\nNJ501-1300 NJ501-1300 NJ501-1300 NJ501-1300\nSend\n100CH In_02_a In_03_a In_17_a\nOut_01_a\nSend\n100CH In_01_b In_03_b In_17_b\nOut_02_b\nSend\n100CH In_01_c In_02_c In_17_c 17 network variables,\nOut_03_c\n100 words ea ch\nSend\n100CH In_01_t In_02_t In_03_t\nOut_17_t\nNJ501-1300: 17 Units\nConnection RPI: 120 ms\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-17\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-5\nRPI\nSetting\nExamples\n14 Communications Performance and Communications Load\nChecking the Device Bandwidth Usage\nWhen you click the Detail Button in the Usage of Device Bandwidth Area, the window shows that the\nusage rate of the tag data link bandwidth for each device is 40.83%, as given in the Usage of Capacity\ncolumn in the following window.\nChanging Settings\nMethod 1: Setting the Same RPI for All the Connections\nIn the previous example, the usage rate of allowable tag data link bandwidth is 40.83% for all the devi-\nces as given in the Usage of Capacity column, and the RPI is set to 120 ms for all the connections. In\nthe next example, change the RPI to 40 ms so as to increase the usage rate of allowable tag data link\nbandwidth up to 80% or less.\nClick the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog Box to display\nthe Set Packet Interval (RPI) Dialog Box.\nInput 40 ms as the new RPI value, and click the OK Button.\n14-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nIf you set the same packet interval (RPI) for all the connections, the table shows that the usage rate of\nallowable tag data link bandwidth is 74.50% for all the device as shown in the Usage of Capacity col-\numn, and this indicates that the shortest packet interval is 40 ms.\nMethod 2: Changing the Packet Intervals (RPIs) of Specific Devices\nIn this example, set faster tag data links for specific two devices: 192.168.250.1 and 192.168.250.10.\nClick the Set Packet Interval (RPI) Button in the Usage of Device Bandwidth Dialog Box to display\nthe Set Packet Interval (RPI) Dialog Box.\nIn the Target Device Area, clear the check boxes for devices to which this RPI change is not applied\n(all the devices except 192.168.250.1 and 192.168.250.10). Input 30 ms as the new RPI value, and\nclick the OK Button.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-19\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-5\nRPI\nSetting\nExamples\n14 Communications Performance and Communications Load\nThe usage rate of allowable tag data link bandwidth for each of the two devices, 192.168.250.1 and"}
+{"question": "168.250.10, increases to 87.00% as shown in the Usage of Capacity column, and this indicates", "answer": "that the shorter RPI is set for the connections of these devices.\nNote that the usage rate of allowable tag data link bandwidth for all the other devices is also increased\nfrom 40.83% to 44.50% since they are connected with the two devices, 192.168.250.1 and"}
+{"question": "168.250.10.", "answer": "In this case, if the Ethernet switch has no multicast filter, the Usage of Capacity value would be"}
+{"question": "33% and communications errors might occur due to traffic overload at the built-in EtherNet/IP port.", "answer": "Method 3: Changing the Packet Interval (RPI) of a Specific Connection\nIn this example, set faster tag data links for a specific connection of a device, 192.168.250.1. Double-\nclick the device, 192.168.250.1, in the Network Configuration Window.\n14-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nSince the Register Device List shows a list of devices connected with 192.168.250.1, double-click a\ndevice, 192.168.250.10, in the list.\nInput 10 ms as the new RPI value in the Edit Connection Dialog Box, and click the OK Button. The\nusage rate of allowable tag data link bandwidth for the device 192.168.250.1 increases to 50.17% as\nshown in the Usage of Capacity column, and this indicates that the RPI for the specific connection is\nset shorter.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-21\n14-2\nAdjusting\nthe\nCommunications\nLoad\n14\n14-2-5\nRPI\nSetting\nExamples\n14 Communications Performance and Communications Load\nNote that the usage rate of allowable tag data link bandwidth for the device, 192.168.250.10, is also\nincreased from 40.83% to 51.00%.\n14-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14-3 I/O Response Time in Tag Data Links\nAdditional Information\nThis section describes built-in EtherNet/IP ports on the NX and NJ-series CPU Units.\nCompared to those built-in EtherNet/IP ports, EtherNet/IP Units, and built-in EtherNet/IP ports\non CJ2H CPU Units (CJ2H-CPU6£-EIP) and CJ2M CPU Units (CJ2M-CPU3£) support differ-\nent data processing performance. Refer to 6-4 Tag Data Links with Other Models on page 6-91\nfor details.\nAs explained in 6-1-7 Concurrency of Tag Data Link Data on page 6-14, the tag (network variable) with\na refreshing task is refreshed when the refreshing task is executed in the user program. By setting the\nrefreshing task, you can calculate the I/O response time that is not affected by the system service.\nPrecautions for Correct Use\nThe refreshing task must be set to all tags (network variables). If both tags (network variable)\nwith a refreshing task and without it exist in a configuration, system service may affect the oper-\nation and I/O response time described in this section may not be maintained.\nThis section describes the I/O response time when refreshing tasks are set properly.\n14-3-1 Timing of Data Transmissions\nThe following figure shows the timing of transmitting data for tag data link between a built-in\nEtherNet/IP port and a CPU Unit.\nData is transmitted at the timing of executing the system common processing 2 of the refreshing task.\nI/O refresh Control processing\nRefreshing Execution of System common programs processing 1 atad tuptuO gnissecorp atad tupnI gnissecorp nommoc metsyS 1 gnissecorp noitoM lortnoc nommoc metsyS 2 gnissecorp atad tuptuO gnissecorp\n14 Communications Performance and Communications Load\nData received.\nPrimary periodic task\nController Processing\nVariable refresh processing\nController task period\nYou can specify either of the following task types for a refreshing task.\n• Primary periodic task\nThe primary periodic task has the highest execution priority. It is executed with high speed and high\nprecision.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-23\n14-3\nI/O\nResponse\nTime\nin\nTag\nData\nLinks\n14\n14-3-1\nTiming\nof\nData\nTransmissions\n14 Communications Performance and Communications Load\n• Periodic task\nA periodic task is executed during the interval between executions of a primary periodic task.\nYou do not need to specify a refreshing task for tags (variables) with AT specifications; the tag data is\ntransmitted in a primary periodic task. (This applies to NX502, NX102, NX1P2, and NJ-series CPU\nUnits.)\nSpecify a task type for each tag for tag data link processing.\nOn the Sysmac Studio, set a refreshing task for each variable assigned as a tag.\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on setting refresh-\ning tasks.\n14-3-2 Built-in EtherNet/IP Port Data Processing Time\nThis section describes the data processing time required to transfer data between the built-in Ether-\nNet/IP port and the CPU Unit.\nData Processing Time Overview\nThe time required for data processing consists of the following three elements."}
+{"question": "Variable Access Time", "answer": "Calculate the time required to transfer tag data, which is regarded as the time required to access\nthe variable.\nThis calculation is performed for each task. Therefore, if multiple tag sets are set for the same re-\nfreshing task, use the total for all tag values in the tag sets.\nUse the following equation for calculating the variable access time.\nVariable access time [μs] = total size of variables [bytes] × a + number of variables × b + number of\naccesses × c + d\nNumber of accesses: equal to the number of tag sets\na to d: Constant values as given below\nConstant value (μs)\nCPU Unit model\na b c d\nNX701-££££ 0.0005 0.033 2.67 7.22\nNX502-££££ 0.0012 0.0736 1.34 17.33\nNX102-££££ 0.0040 0.240 3.27 25.21\nNX1P2-££££ 0.0040 0.240 3.27 25.21\nNJ501-££££ 0.0010 0.490*1 1.41 6.68\nNJ301-££££ 0.0015*2 0.560*3 2.15 7.52\nNJ101-££££ 0.0015 0.560 3.83 7.52\n*1. The value is 0.58 for CPU Units with unit version 1.02 or earlier.\n*2. The value is 0.0009 for CPU Units with unit version 1.02 or earlier.\n*3. The value is 1.03 for CPU Units with unit version 1.02 or earlier."}
+{"question": "Number of Data Transfers", "answer": "Tag data transfer is executed as part of the task processing.\n14-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nIf the time required to process the data transfer is greater than the variable access time (*2), the\nentire data cannot be sent in one task period and needs to be split and sent over multiple times\ninstead.\nNumber of data transfers = Time required to send the entire data (*1) / Variable access time (*2)\nset for the task\n*1. This is the variable access time as calculated in step 1 above.\n*2. The variable access time is the maximum processing time for accessing the variable. Double-click Task\nSettings under Configurations and Setup on the Sysmac Studio to display the Task Settings Tab\nPage, and configure the settings for each task.\nPrecautions for Correct Use\nThe maximum number of tag data link words that can be transferred through a built-in\nEtherNet/IP port is 184,832 words on an NX701 CPU Unit (total of 369,664 words with two\nports), 46,208 words on an NX502 CPU Unit (total of 92,416 words with two ports), 9,600 words\non an NX102 CPU Unit (total of 19,200 words with two ports), and 9,600 words on an NX1P2\nCPU Unit or NJ-series CPU Unit.\nIf the number of tag data link words exceeds the number of words that can be exchanged with\nthe CPU Unit at one time, the data is divided and transferred over multiple times"}
+{"question": "Actual Time Required for Data Transfer", "answer": "You can use the task period of the refreshing task and the number of data transfers as calculated\nin (2) above to calculate the actual time required to transfer the data.\nTask period × Number of data transfers\nData Processing Time Calculation Example\nThe following shows an example to explain how to calculate the time required for tag data transfer.\n• CPU Unit model\nNJ501-££££\n• Refreshing task\nPrimary periodic task\nTask period: 500μs (variable access time: 3%)\n• Settings of tag sets\nTag set Refreshing task Number of variables Total size of variables\nTag set A Primary periodic task 8 600 bytes\nTag set B Primary periodic task 4 200 bytes\nTag set C Primary periodic task 10 1,000 bytes\n1\nCalculate the variable access time as shown below.\n[(600 + 200 + 1,000) bytes × 0.001 μs] + [(8 + 4 + 10) variables × 0.49 μs] + 3 × 1.41 μs + 6.68\nμs = 23.49 μs\n2\nCalculate the number of data transfers.\nTime required for data transfer: Variable access time in step1 = 23.49 μs\nVariable access time set for the task: 500 μs × 0.03 = 15 μs\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-25\n14-3\nI/O\nResponse\nTime\nin\nTag\nData\nLinks\n14\n14-3-2\nBuilt-in\nEtherNet/IP\nPort\nData\nProcessing\nTime\n14 Communications Performance and Communications Load\nNumber of data transfers 23.49 μs ÷ 15 μs = 1.6 times\nThus, approximately two data transfers are required.\n3\nCalculate the actual time required for the entire data transfer.\n500 μs × 2 times = 1,000 μs\n14-3-3 Relationship between Task Periods and Packet Intervals (RPIs)\nEffect of Tag Data Links on Task Periods\nTag data transfer is executed as part of the task processing.\nTherefore, the tag data transfer process is added to the task processing for tasks set as a tag’s re-\nfreshing task. This requires you to make adjustments to the variable access time and task period in\nthe Task Settings Tab Page so that these processes are completed within a single task period.\n1\nCalculate the time required for the data transfer and set the result as the variable access\ntime(*).\nFor the formula for calculating the time required for data transfer, refer to Data Processing\nTime Overview on page 14-24.\n* If the same refreshing task is set for multiple tag sets, calculate the total time required for all tags in tag\nsets.\n2\nSet the variable access time in the Task Setup to a value equal to or greater than the value\ncalculated in step 1 above.\nAdjust the task period time after adding in the time calculated in step 1. Use the Sysmac Studio\nto set the variable access time and task period settings.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details.\nAdjusting Packet Intervals (RPIs) According to the Task Period\nTag data is transferred based on the actual time required for the transfer (task period × number of data\ntransfers), regardless of the packet interval (RPI) setting.\nSet the packet interval (RPI) as below.\nActual time required for data transfer (Task period × Number of data transfers) < RPI\nFor details on the actual time required for data transfer, refer to 14-3-2 Built-in EtherNet/IP Port Data\nProcessing Time on page 14-24.\nExample: Relationship between the RPI Setting and the Time Required for Data Transfer\n• Task period: 10 ms\n• Number of data transfers: 2 times\n• Actual time required for data transfer: 10 ms × 2 times = 20 ms\nRegardless of the RPI value, the time required for the data transfer is 20 ms.\n14-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nI/O refreshing\nUser program execution\nMotion control\nRPI of 10 ms RPI of 20 ms\nExample: Primary periodic task Example: Primary periodic task\n(1) (2) (1) (2)\nTask period: 10 ms Task period: 10 ms\nSend data Send data\nprocessing Task period × 2 processing Task period × 2\nRefreshing period Refreshing period\nduring RPI during RPI:\n10 ms 20 ms\nTo Controller #2 To Controller #2\nTime required to transfer data from Controller #1: 20 ms\nnoissimsnarT\n1#rellortnoC\nhtap\nnoissimsnarT\n1#rellortnoC\nhtap\n14 Communications Performance and Communications Load\nOI\nUPG\nMC\nData link processing\n(system common processing 3)\nOIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC OIUPG MC\nTag data link service Tag data link service\n14-3-4 Maximum Tag Data Link I/O Response Time\nYou can calculate the maximum I/O response time by adding up the time of (1) to (6) in the following\nfigure.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-27\n14-3\nI/O\nResponse\nTime\nin\nTag\nData\nLinks\n14\n14-3-4\nMaximum\nTag\nData\nLink\nI/O\nResponse\nTime\n(1) (2) (3)\nExample of data transfer processing over 3 task periods\nnoissimsnarT\ntuptuO\necived\ntupnI\nhtap\necived\nI/O refreshing\nUser program execution\nMotion control\nData link processing (system\nTag data link I/O response time common processing 2)\n(4) Network transmission delay time\n(5) Receive data\nprocessing time\n(1) Input ON\nresponse time (2) pS re on ced s d sa inta g time (3) RPI (6) rO esu ptp ou nt s O e N tim e\nInput\nTask period\nTag data link\nrefresh period\nController #2\nprocessing\nTask period\nrellortnoC\nrellortnoC\n1#\n2#\n14 Communications Performance and Communications Load\nOI\nUPG\nMC\nExample: Primary periodic task\nOIUP MC OIUP MC OIUP MC OIUP MC OIUP MC Controller #1 processing\nG G G G G\nTag data link service\nTag data link service\nOIUP MC OIUP MC OIUP MC OIUP MC OIUP MC\nG G G G G\nOutput\nAdditional Information\n• In CPU Units with unit version 1.03 or later, tag data link is processed in the tag data link\nservice.\n• In CPU Units with unit version 1.00 to 1.02, tag data link is processed in the system service. If\na tag data link timeout occurs, reconsider the execution time of the system service.\n• The tag data link service is not executed during execution of the communications bridge serv-\nice. Therefore, the I/O response time for the tag data links may be longer when CIP Safety\ncommunications are performed."}
+{"question": "Input ON Response Time", "answer": "The input ON response time contains the delay time for the external input device from when the\ninput occurs until the switch actually changes to ON and the time until the input data is stored in\nthe memory area of the CPU Unit. Refer to the input delay information of the device for input\nswitch delay time.\nOne task period is required until the input data is stored in the memory area of the CPU Unit. Ac-\ncordingly, the input ON response time is calculated as below.\nInput ON response time = Input device delay time + Task period"}
+{"question": "Send Data Processing Time", "answer": "This is the time required to transfer a variable from a CPU Unit to the built-in EtherNet/IP port.\n14-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\nSince data transfer is executed as part of task processing, the send data processing time is as\nlong as the task period.\nIf the data is larger than the allowable data size to send in a single task process (which can be set\nwith Variable Access Time of the task), the data will be transferred over more than one task peri-\nod, requiring additional time equivalent to the task period multiplied by the number of transfers.\nFor details on the send data processing time, refer to 14-3-2 Built-in EtherNet/IP Port Data Proc-\nessing Time on page 14-24."}
+{"question": "Packet Interval (RPI)", "answer": "This is the communications refresh period which can be specified on the Network Configurator."}
+{"question": "Network Transmission Delay Time", "answer": "The transmission delay on an Ethernet line is 50 μs or less. This delay time can be ignored."}
+{"question": "Receive Data Processing Time", "answer": "This is the time required to transfer data that is received on the built-in EtherNet/IP port to a varia-\nble in the CPU Unit.\nSince data receive is executed as part of task processing, the receive data processing time is as\nlong as the task period.\nIf the data is larger than the allowable data size to receive in a single task process (which can be\nset with Variable Access Time of the task), the data will be transferred over more than one task\nperiod, requiring additional time equivalent to the task period multiplied by the number of transfers.\nFor details on the receive data processing time, refer to 14-3-2 Built-in EtherNet/IP Port Data Proc-\nessing Time on page 14-24.\nData transfer is executed once every task period. If another input data is received just after the da-\nta transfer in the current task period, the transfer of the received data will be delayed by one Con-\ntroller task period.\nAdditional Information\nIf the Unit has connections with multiple nodes, the total amount of data to be exchanged will\nincrease, and the Unit may send or receive data larger than the data size allowed per transfer.\nIn this case, the number of data transfers increases."}
+{"question": "Output ON Response Time", "answer": "This is the delay time from when an output command is issued by the Controller until the output is\nexecuted on the external output device.\nOutput ON response time = Output device delay time + CPU task period\nAdditional Information\nThe I/O response time may be longer due to noise, or other causes.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-29\n14-3\nI/O\nResponse\nTime\nin\nTag\nData\nLinks\n14\n14-3-4\nMaximum\nTag\nData\nLink\nI/O\nResponse\nTime\n14 Communications Performance and Communications Load\n14-4 Message Service Transmission Delay\nThis section describes delay time in the service processing of a CIP communications instruction (CIP-\nWrite).\nInstruction (CIPWrite) executed. Instruction completed.\nOI UPG MC IO UPG MC OI UPG MC OI UPG MC\nController#1\nCommand generated. Received response interpreted.\nSystem System\nservice × service\nLine Line\nTransmission path\nController#2\n×\nIO UPG MC IO UPG MC Variable written.\nReceived command interpreted. Response generated.\nSystem System\nservice service\nTransmission System Transmission Receive System Variable System Transmission Receive System\ndelay service delay delay service written. service delay delay service\nTask period Line Task period Task period Line Task period\n(local node) (remote node) (remote node) (local node)\nMaximum transmission delay time = Send delay + System service execution time + Transmission delay\n(Local node task period)\n+ Receive delay + System service execution time\n(Remote node task period)\n+ Variable write time + System service execution time + Transmission delay\n(Remote node task period)\n+ Receive delay + System service execution time\n(Local node task period)\nProcesses with delay time are processed within the task period of each node as shown in the above\ndiagram.\nDelay time related to transmission lines is as below.\n14-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n14 Communications Performance and Communications Load\n Transmission Delay\nThe transmission delay on an Ethernet line is 50 μs or less. This delay time can be ignored.\nAdditional Information\nDepending on the actual operating environment, the transmission time may be longer\nthan the one calculated with the equations given above.\nThe following factors can cause longer transmission time: the load rate of the network (the de-\ngree of network congestion), the window size of each network node, traffic load on the built-in\nEtherNet/IP port (e.g., simultaneous tag data link communications), and the system configura-\ntion.\nCIP communications instructions are executed in the system service process.\nIf a timeout occurs for a CIP communications instruction, reconsider the execution time for the\nsystem service.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 14-31\n14-4\nMessage\nService\nTransmission\nDelay\n14\n14 Communications Performance and Communications Load\n14-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15\nTroubleshooting\nThis section explains how to detect errors, how to check the communication status of\nthe EtherNet/IP network with the Network Configurator, and how to identify and trou-\nbleshoot errors which may occur due to the tag data link connection status.\n15-1 Overview of Troubleshooting......................................................................15-2\n15-2 Checking Status with the Network Configurator.......................................15-3\n15-2-1 The Network Configurator's Device Monitor Function...................................15-3\n15-2-2 Connection Status Codes and Troubleshooting...........................................15-11\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-1\n15\n15 Troubleshooting\n15-1 Overview of Troubleshooting\nYou manage all of the errors that occur on the NJ/NX-series Controller as events.\nThis allows you to see what errors have occurred and find corrections for them with the same methods\nfor the entire range of errors that is managed (i.e., CPU Unit, NX Units, NX-series Slave Terminals,\nEtherCAT slaves,*1 and CJ-series Units).\n*1. Only Sysmac devices are supported.\nHost computer HMI\nChecking Network Status\nEtherNet/IP\nTroubleshooter\nNetwork Configurator\nBuilt-in\nNJ/NX-series EtherNet/IP CJ-series Units and\nPort\nCPU Unit NX Units\nTroubleshooting\nSysmac Studio\nBuilt-in EtherCAT port\nEtherCAT\nEtherCAT\nslaves\nError management range for NJ/NX-series Controller\nYou can use the troubleshooting functions of the Sysmac Studio or the Troubleshooter on an HMI to\nquickly check for errors that have occurred and find corrections for them.\nRefer to the NJ/NX-series Troubleshooting Manual (Cat. No. W503) for error types and details, specific\ncorrections when errors occur, and troubleshooting information on the entire NJ/NX-series Controllers.\n15-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\n15-2 Checking Status with the Network\nConfigurator\n15-2-1 The Network Configurator's Device Monitor Function\nConnect the Network Configurator online, select the device to be checked, right-click to display the\npop-up menu, and select Monitor.\nThe Monitor Device Dialog Box will be displayed.\nPrecautions for Correct Use\nMonitoring may not be performed if the following settings are configured on the NJ/NX-series\nController on the connection route or on the destination NJ/NX-series Controller. If monitoring is\nnot performed, check the following settings. Refer to CIP Message Server on page 4-21,\nandPacket Filter on page 4-8 for details on the settings.\n• The Do not use Option is selected for the CIP message server.\n• The Use Option is selected for Packet Filter.\nAdditional Information\nIf a communications error occurs during monitoring, the dialog box will continue to show the last\ninformation that was collected.\nTo start monitoring again, close the Monitor Device Dialog Box, and then open the Monitor\nDevice Dialog Box again.\nYou cannot monitor the CIP Safety communications status with Network Configurator. Refer to the NX-\nseries Safety Control Unit User’s Manual (Cat. No. Z930) for details on confirming CIP Safety commu-\nnications status.\n Status 1 Tab Page\nThe following check boxes are displayed for the status. If a check box is checked with , the sta-\ntus is TRUE.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-3\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-1\nThe\nNetwork\nConfigurator's\nDevice\nMonitor\nFunction\n15 Troubleshooting\nClassification Item TRUE status description\nEthernet Status Com. Controller Error An error occurred in the Communications Controller.\nIP Address Duplicated The same IP address is assigned to more than one\nnode.\nOn-Line The Unit is online. (The EtherNet/IP Unit can perform\ncommunications processing.)\nMultiple Switch ON More than one data link start/stop switch changed to\nTRUE at the same time.\nData Link Status Comparison Error The remote node information in the tag data link param-\neters was different from the actual node information.\nMain causes:\n• The specified target does not exist.\n• The variable name does not match.\n• The connection size is different.\n• Connection resources are not sufficient.\nData Link Status Tag Data Link Error There were two or more errors in a connection as an\noriginator.\nInvalid Parameter An error was found in the parameters for tag data links\nthat are saved in non-volatile memory.\nAll Tag Data Link Tag data links are communicating in all connections as\nthe originator.\nTag Data Link Tag data links are communicating in one or more con-\nnections as the originator.\nConfiguration Er- Ethernet Link Status A link is established with the Ethernet switch.\nror Status Ethernet Basic Settings Log- The following settings are incorrect:\nic Error • TCP/IP settings (IP address, subnet mask, or link set-\ntings)\nIP Router Table Error There is a mistake in the IP router table information.\nEthernet Ext Config Logical Always FALSE.\nError\nBOOTP Server Error One of the following errors occurred when using the\nBOOTP server:\n• The IP address received from the BOOTP server is\nincorrect.\n• A communications timeout occurred with the server.\nIn the Target Node Status, information about the target node that acts as the originator is dis-\nplayed.\nIf all tag data link connections to the node are established and normal, this information is displayed\nin blue. However, if any connection is broken it is displayed in red.\n15-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-5\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-1\nThe\nNetwork\nConfigurator's\nDevice\nMonitor\nFunction\n15 Troubleshooting\n Status 2 Tab Page\nThis tab page displays information on nodes with tag data link originator settings. This information\nis in blue if the connection is normal, or red if an error occurred.\nAdditional Information\nThe target Controller status can be used when the Controller status is set to Included for all the\ntarget sets for both originator and target connections.\nIf it is set to Not included, it is grayed out on the display.\n15-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\n Connection Tab Page\n• Target Node Status\nInformation about the target node that acts as the originator is displayed.\nIf all tag data link connections to the node are established and normal, this information is dis-\nplayed in blue. However, if any connection is broken it is displayed in red.\nHowever, this information is displayed in gray if the connection to the node is stopped.\n• Connection Status\nThe Status Column of the connection status shows the status of each connection that is set as\nthe originator. The connection status can be used to identify the cause of tag data link errors.\nRefer to 15-2-2 Connection Status Codes and Troubleshooting on page 15-11 for details on the\nconnection status.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-7\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-1\nThe\nNetwork\nConfigurator's\nDevice\nMonitor\nFunction\n15 Troubleshooting\n Controller Log Tab Page\nThis tab page displays the Controller event log that is stored in the CPU Unit.\nThe error history shows errors that have occurred. It can be saved in a file in the computer.\nRefer to the operation manual of the CPU Unit for details on error information.\n15-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\n Tag Status Tab Page\nThis tab page displays if the tag settings for each tag for tag data links are set so that data can be\nexchanged with the CPU Unit.\nThe following status is displayed depending on the status that is set.\nNormally resolved: Normal data exchange is possible.\nResolving: The variables with tags are being resolved.\nWhen the resolution is completed normally, a connection will be established and the data ex-\nchange will start.\nDifferent sizes: Different sizes are set for the network variables and the tag settings.\nA connection will not be established for a tag for which this error occurs.\nNo tag: A network variable is not set in the variable table in the CPU Unit for the specified tag setting. Or,\ninstead of a member of union variable, unions are specified.\nA connection will not be established for a tag for which this error occurs.\nAttribute error: 1. Writing is not possible for Read Only and Constant attributes."}
+{"question": "The I/O direction that is set in the tag data link settings does not agree with the I/O direction", "answer": "of the variable in the CPU Unit. There is an error in the setting of a Network Publish attribute\nfor a CPU Unit variable.\nA connection will not be established for a tag for which this error occurs.\nIf the status is not “Normal resolution completed,” check the tag data link settings or the network\nvariable settings in the variable table in the NJ/NX-series CPU Unit.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-9\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-1\nThe\nNetwork\nConfigurator's\nDevice\nMonitor\nFunction\n15 Troubleshooting\n Ethernet Information Tab Page\nThis tab page displays the communications status at the communications driver level of the built-in\nEthernet/IP port.\nThe error counter information can be used to confirm whether communications problems have oc-\ncurred.\nThe tag data link information can be used to confirm characteristics such as the Bandwidth (pps).\n15-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\n15-2-2 Connection Status Codes and Troubleshooting\nThis section explains how to identify and correct errors based on the tag data link's connection status.\nThe connection status can be read using the Connection Tab Page of Monitor Device Window with\nthe Network Configurator. Refer to 15-2-1 The Network Configurator's Device Monitor Function on\npage 15-3 for details.\nAdditional Information\nThe connection status has the same meaning as the Connection Manager's General and Addi-\ntional error response codes, as defined in the CIP specifications.\nThe following table shows the likely causes of the errors causes for each configuration and connection\nstatus (code).\nOriginator Target\nConfiguration 1 CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21,\nCJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M- CJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-\nCPU3£, NJ501-££££, NJ301-££££, NJ101- CPU3£, NJ501-££££, NJ301-££££, NJ101-\n££££, NX701-££££, NX502-££££, NX- ££££, NX701-££££, NX502-££££, NX-\nEIP201, NX102-££££, NX1P2-££££££ EIP201, NX102-££££, NX1P2-££££££\nConfiguration 2 CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, Products from other manufacturers\nCJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-\nCPU3£, NJ501-££££, NJ301-££££, NJ101-\n££££, NX701-££££, NX502-££££, NX-\nEIP201, NX102-££££, NX1P2-££££££\nConfiguration 3 Products from other manufacturers CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21,\nCJ1W-EIP21S, CJ2H-CPU££-EIP, CJ2M-\nCPU3£, NJ501-££££, NJ301-££££, NJ101-\n££££, NX701-££££, NX502-££££, NX-\nEIP201, NX102-££££, NX1P2-££££££\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n00 0000 Normal status code: --- --- ---\nThe connection has been opened and\nthe tag data link is communicating nor-\nmally.\n01 0100 Error code returned from target: This error does Depends on Depends on\nAttempted to open multiple connections not occur. the target's the originator's\nfor the same connection. specifications. specifications.\n(This error (This error\nshould not oc- should not oc-\ncur. If it does, cur. If it does,\ncontact the tar- contact the\nget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-11\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-2\nConnection\nStatus\nCodes\nand\nTroubleshooting\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0103 Error code returned from target: This error does Confirm that Confirm that\nAttempted to open a connection with an not occur. the target sup- the originator\nunsupported transport class. ports Class 1. supports Class"}
+{"question": "01 0106 Duplicate consumers: If the tag data Depends on If the tag data", "answer": "Attempted to open multiple connections link is stopped the target's link is stopped\nfor single-consumer data. or started, this specifications. or started, this\nerror may oc- (Contact the error may oc-\ncur according target device's cur according\nto the timing, manufacturer.) to the timing,\nbut the system but the system\nwill recover au- will recover au-\ntomatically. tomatically.\n01 0107 Error code returned from target: This error does This error does This is not an\nAttempted to close a connection, but that not occur. not occur. error because\nconnection was already closed. the connection\nis already\nclosed.\n01 0108 Error code returned from target: This error does Check which Check which\nAttempted to open a connection with an not occur. connection connection\nunsupported connection type. types can be types can be\nused by the used by the\ntarget. originator. (An\n(Contact the error will occur\nmanufacturer.) if a connection\nOnly multicast other than a\nand point-to- multicast or\npoint connec- point-to-point\ntions can be connection is\nset. set.)\n01 0109 Error code returned from target: Check the connection (sizes) set in the originator\nThe connection size settings are differ- and target.\nent in the originator and target.\n01 0110 Error code returned from target: Check whether Depends on Check whether\nThe target was unable to open the con- the tag data the target's the tag data\nnection, because of its operating status, link is stopped specifications. link is stopped\nsuch as downloading settings. at the target. (Contact the at the target.\n(Restart the tag target device's (Restart the tag\ndata link com- manufacturer.) data link com-\nmunications munications\nwith the soft- with the soft-\nware switch.) ware switch.)\n01 0111 Error code returned from target: This error does Check the tar- Set the origina-\nThe RPI was set to a value that exceeds not occur. get's RPI set- tor's RPI set-\nthe specifications. ting specifica- ting to 10 sec-\ntions. onds or less.\n15-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0113 Error code generated by originator or re- Check the con- Check the con- Check the con-\nturned from target: nection set- nection set- nection settings\nAttempted to open more connections tings (number tings (number (number of\nthan allowed by the specifications. of connections) of connections) connections) at\nat the origina- at the origina- the originator\ntor and target. tor and target. and target.\nCheck the con- Check the con-\nnection specifi- nection specifi-\ncations for de- cations for de-\nvices from oth- vices from oth-\ner manufactur- er manufactur-\ners. ers.\nThe NX502 CPU Unit is set to disable Make sure that the NX502 CPU Unit on the CIP\nCIP Safety communications. Safety communications path is set to enable CIP\nSafety communications.\n01 0114 Error code returned from target: This error does Depends on Check the orig-\nThe Vendor ID and Product Code did not not occur. the target's inator's con-\nmatch when opening connection. specifications. nection set-\n(Contact the tings.\ntarget device's\nmanufacturer.)\nCheck that the\ntarget device's\nEDS file is cor-\nrect.\n01 0115 Error code returned from target: This error does Depends on Check the orig-\nThe Product Type did not match when not occur. the target's inator's con-\nopening connection. specifications. nection set-\n(Contact the tings.\ntarget device's\nmanufacturer.)\nCheck that the\ntarget device's\nEDS file is cor-\nrect.\n01 0116 Error code returned from target: Check the ma- Depends on Check the orig-\nThe Major/Minor Revisions did not jor and minor the target's inator's con-\nmatch when opening connection. revisions set specifications. nection set-\nfor the target (Contact the tings.\ndevice and target device's\nconnection. If manufacturer.)\nnecessary, ob- Check that the\ntain the most target device's\nrecent EDS file EDS file is cor-\nand set it rect.\nagain.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-13\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-2\nConnection\nStatus\nCodes\nand\nTroubleshooting\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0117 Error code returned from target: Check whether Depends on Check the orig-\nThe tag set specified in the connection's the originator the target's inator's con-\ntarget variables does not exist. and target tag specifications. nection set-\nsets and tags (Contact the tings. Check\nare set correct- target device's whether the\nly. manufacturer.) target tag sets\nand tags are\nset correctly.\n01 011A Error code generated by originator: Unexpected Unexpected Depends on\nConnection could not be established be- network traffic network traffic the target's\ncause the buffer was full due to high traf- may have been may have been specifications.\nfic. received. received. (Contact the\nUse the Ether- Use the Ether- target device's\nnet Information net Information manufacturer.)\nTab Page of Tab Page of\nthe Network the Network\nConfigurator's Configurator's\ndevice monitor device monitor\nto check the to check the\nbandwidth us- bandwidth us-\nage, and cor- age, and cor-\nrect the load. rect the load.\nIf there are pla- If there are pla-\nces where ces where\nbroadcast broadcast\nstorms occur, storms occur,\nsuch as loop such as loop\nconnections in connections in\nthe network the network\nconnection for- connection for-\nmat, then cor- mat, then cor-\nrect them. rect them.\n01 011B Error code returned from target: This error does Depends on Set the origina-\nThe RPI was set to a value that is below not occur. the target's tor's RPI set-\nthe specifications. specifications. ting to 1 ms or\n(Contact the greater.\ntarget device's\nmanufacturer.)\n15-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0127 Error code returned from target: This error does Check the con- This error does\nThe connection data size settings are not occur. nection (sizes) not occur.\ndifferent in the originator and target. set in the origi-\n(data from originator to target) nator and tar-\nget.\n(data from orig-\ninator to target)\nDepends on\nthe target's\nspecifications.\n(Contact the\nmanufacturer.)\nCheck that the\ntarget device's\nEDS file is cor-\nrect.\n01 0128 The connection data size settings are Check the connection (sizes) set in the originator\ndifferent in the originator and target. and target.\n(data from target to originator) (data from target to originator)\n01 0203 Error code generated by originator: Tag data link communications from the target timed\nThe connection timed out. out. Check the power supply and cable wiring of\nthe devices in the communications path, including\nthe target and switches. If performance has drop-\nped due to heavy traffic, change the performance\nsettings. For example, increase the timeout time or\nRPI setting.\nAlso, check whether the CIP message communica-\ntions of the target are stopped and whether the CIP\ncommunications are permitted by Packet Filter\nfunction of the originator or the device on the route.\n01 0204 Error code generated by originator: There was no response from the target. Check the\nThe connection open process timed out. power supply and cable wiring of the devices in the\ncommunications path, including the target and\nswitches.\nAlso, check whether the CIP message communica-\ntions of the target or originator are stopped and\nwhether the CIP communications are permitted by\nPacket Filter function of the target device or the de-\nvice on the route.\n01 0205 Error code returned from target: This error does Depends on Depends on\nThere was a parameter error in the not occur. the target's the originator's\nframe used to open the connection. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-15\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-2\nConnection\nStatus\nCodes\nand\nTroubleshooting\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0301 Error code generated by originator or re- Check the total Check the total Check the total\nturned from target: number of the number of the number of the\nTotal number of tag sets that are set to tag sets that tag sets that tag sets that\nthe product was exceeded. are set to the are set to the are set to the\nproduct and set product and set product and set\nthe tag sets so the tag sets so the tag sets so\nthat the total that the total that the total\nnumber does number does number does\nnot exceed the not exceed the not exceed the\nmaximum of maximum of maximum of\nthe allowable the allowable the allowable\nnumber. number. number.\n01 0302 Error code generated by originator or re- Check the con- Check the tar- Check the con-\nturned from target: nection set- get's connec- nection settings\nThe tag data link's allowable bandwidth tings (number tion settings (number of\n(pps) was exceeded. of connections (number of connections\nand RPI) at the connections and RPI) at the\noriginator and and RPI). originator and\ntarget. Check the con- target.\nnection set-\ntings (number\nof connections\nand RPI) at the\noriginator and\ntarget.\n01 0311 Error code returned from target: This error does Depends on Depends on\nThere was a parameter error in the not occur. the target's the originator's\nframe used to open the connection. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\n01 0312 Error code returned from target: This error does Depends on Depends on\nThere was a parameter error in the not occur. the target's the originator's\nframe used to open the connection. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\n01 0315 Error code returned from target: This error does Depends on Depends on\nThere was a parameter error in the not occur. the target's the originator's\nframe used to open the connection. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\n15-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\n01 0316 Error code returned from target: This error does Depends on Depends on\nThere was a parameter error in the not occur. the target's the originator's\nframe used to close the connection. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\n01 031C Error code generated by originator: This error does The originator Depends on\nSome other error occurred. not occur. generates this the originator's\ncode when an specifications.\nunsupported (Contact the\nresponse code originator devi-\nis returned ce's manufac-\nfrom the target turer.)\nin reply to an\nopen request.\n08 --- Error code returned from target: This error does Depends on Depends on\nThere is no Forward Open or Large For- not occur. the target's the originator's\nward Open service in the target device. specifications. specifications.\n(Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-17\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-2\nConnection\nStatus\nCodes\nand\nTroubleshooting\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\nD0 0001 Error code generated by originator: The connection The meaning Depends on\nThe connection operation is stopped. was stopped of this error the originator's\nbecause the code is defined specifications.\nTag Data Link by each ven- (Contact the\nStop Bit was dor, so it de- originator devi-\nturned ON, or pends on the ce's manufac-\nthe settings da- target's specifi- turer.)\nta is being cations.\ndownloaded. (Contact the\nEither turn ON target device's\nthe Tag Data manufacturer.)\nLink Start\nSwitch, or wait\nuntil the set-\ntings data has\nbeen down-\nloaded.\nThis code in-\ncludes fatal\nController er-\nrors and Unit\nfailure. To han-\ndle these er-\nrors, refer to\nthe NJ/NX-\nseries\nTroubleshootin\ng Manual (Cat.\nNo. W503).\nD0 0002 Error code generated by originator: Wait until the The meaning Depends on\nThe connection is being opened (open- opening proc- of this error the originator's\ning processing in progress). essing is com- code is defined specifications.\npleted. by each ven- (Contact the\ndor, so it de- originator devi-\npends on the ce's manufac-\ntarget's specifi- turer.)\ncations.\n(Contact the\ntarget device's\nmanufacturer.)\n15-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n15 Troubleshooting\nConnection status Handling\nGeneral Additional\nSource of error Configuration Configuration Configuration\nStatus Status\n1 2 3\n(hex) (hex)\nOMRON error code\n01 0810 Error code returned from target: It occurs when The meaning The meaning of\nThe latest data cannot be retrieved from the CPU Unit of this error this error code\nthe CPU Unit after a connection was task period is code is defined is defined by\nopened. (Automatic recovery by connec- too long after a by each ven- each vendor,\ntion open retry) connection was dor, so it de- so it depends\nopened or pends on the on the origina-\nwhen the Con- target's specifi- tor's specifica-\ntroller system cations. tions.\nstopped due to (Contact the (Contact the\nan error on the target device's originator devi-\nController. manufacturer.) ce's manufac-\nIf it occurred turer.)\ndue to a long\ntask period, the\nerror will be re-\ncovered auto-\nmatically. If it\nwas caused by\nstoppage of the\nController sys-\ntem, the cause\nof the error will\nbe identified\nfrom the error\ninformation of\nthe CPU Unit.\n01 0811 Error code generated by originator: It occurs when The meaning The meaning of\nThe latest data cannot be retrieved from the CPU Unit of this error this error code\nthe CPU Unit after a connection was task period is code is defined is defined by\nopened. (Automatic recovery by connec- too long after a by each ven- each vendor,\ntion open retry) connection was dor, so it de- so it depends\nopened. pends on the on the origina-\nThe error will target's specifi- tor's specifica-\nbe recovered cations. tions.\nautomatically. (Contact the (Contact the\ntarget device's originator devi-\nmanufacturer.) ce's manufac-\nturer.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) 15-19\n15-2\nChecking\nStatus\nwith\nthe\nNetwork\nConfigurator\n15\n15-2-2\nConnection\nStatus\nCodes\nand\nTroubleshooting\n15 Troubleshooting\n15-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nA\nAppendices\nA-1 Functional Comparison of EtherNet/IP Ports on NJ/NX-series\nCPU Units and Other Series..........................................................................A-3\nA-2 Use the Sysmac Studio to Set the Tag Data Links (EtherNet/IP\nConnections)..................................................................................................A-5\nA-2-1 Overview of the Tag Data Links (EtherNet/IP Connections) Settings\nwith the Sysmac Studio...................................................................................A-5\nA-2-2 Procedure to Make the EtherNet/IP Connection Settings with the\nSysmac Studio................................................................................................A-6\nA-2-3 EtherNet/IP Connection Settings.....................................................................A-7\nA-2-4 Making the EtherNet/IP Connection Settings with the Sysmac Studio..........A-11\nA-2-5 Checking Communications Status with the Sysmac Studio and Trou-\nbleshooting....................................................................................................A-32\nA-2-6 Troubleshooting.............................................................................................A-36\nA-3 EDS File Management.................................................................................A-42\nA-3-1 Installing EDS Files.......................................................................................A-42\nA-3-2 Creating EDS Files........................................................................................A-43\nA-3-3 Deleting EDS Files........................................................................................A-43\nA-3-4 Saving EDS Files..........................................................................................A-44\nA-3-5 Searching EDS Files.....................................................................................A-44\nA-3-6 Displaying EDS File Properties.....................................................................A-45\nA-3-7 Creating EDS Index Files..............................................................................A-45\nA-4 Precautions for Using the Network Configurator on Windows XP,\nWindows Vista, or Windows 7 or Higher....................................................A-46\nA-4-1 Changing Windows Firewall Settings............................................................A-46\nA-5 Variable Memory Allocation Methods.......................................................A-49\nA-5-1 Variable Memory Allocation Rules.................................................................A-49\nA-5-2 Important Case Examples.............................................................................A-58\nA-6 Precautions When Accessing External Outputs in CPU Units...............A-62\nA-7 TCP State Transitions.................................................................................A-63\nA-8 Example of NX Unit Setting Using NX Configuration Object Service....A-65\nA-8-1 Changing the Unit Operation Settings for Singe NX Unit..............................A-65\nA-8-2 Changing the Unit Operation Settings for Multiple NX Units.........................A-66\nA-8-3 Initializing the Unit Operation Settings for Singe NX Unit..............................A-66\nA-9 Tag Data Link Settings with Generic Devices...........................................A-67\nA-9-1 Creating Generic Devices.............................................................................A-67\nA-9-2 Creating a Tag or Tag Set for Generic Device...............................................A-68\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-1\nA\nAppendices\nA-10 Procedure to Use Secure Socket Service with Secure Socket\nConfiguration Commands...........................................................................A-72\nA-10-1 Settings for Starting Secure Socket Services................................................A-72\nA-10-2 Procedure for Replacing the CPU Unit..........................................................A-74\nA-11 Secure Socket Configuration Commands................................................A-79\nA-11-1 Operating Environment for Secure Socket Configuration Commands..........A-79\nA-11-2 Location and Starting Procedure of Secure Socket Configuration\nCommands....................................................................................................A-80\nA-11-3 Command and Option Formats.....................................................................A-80\nA-11-4 Common Specifications to All Commands....................................................A-81\nA-11-5 Command Specifications...............................................................................A-83\nA-12 TCP/ UDP Port Numbers Used for the Built-in EtherNet/IP Port.............A-95\nA-13 Version Information..................................................................................A-100\nA-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-1 Functional Comparison of EtherNet/IP\nPorts on NJ/NX-series CPU Units and\nOther Series\n¡: Supported, ---: Not supported\nBuilt-in Built-in Built-in Built-in Built-in\nEtherNet/IP EtherNet/IP EtherNet/IP EtherNet/IP EtherNet/IP NX-series\nItem port on port on port on port on port on NJ- EtherNet/IP\nNX701 CPU NX502 CPU NX102 CPU NX1P2 CPU series CPU Unit\nUnit Unit Unit Unit Unit\nTag data link communica- OK OK OK OK OK OK\ntions service\nCIP message communica- OK OK OK OK OK OK\ntions service\nIP routing OK OK OK --- --- OK\nSocket services OK OK OK OK OK ---\nFTP server OK OK OK OK OK ---\nFTP client OK OK OK OK OK ---\nMail send/receive --- --- --- --- --- ---\nWeb functions --- --- --- --- --- ---\nAutomatic adjustment of OK OK OK OK OK ---\nPLC/Controller’s internal\nclock\nError history OK*1 OK*1 OK*1 OK*1 OK*1 OK*1\nResponse to PING com- OK OK OK OK OK OK\nmand\nSNMP/SNMP trap OK OK OK OK OK OK\nCIDR function for IP ad- OK OK OK OK OK OK\ndresses\nDHCP client --- OK --- --- --- ---\nLLDP --- OK ¡*2 --- --- OK\nOnline connection via Ether- --- --- --- --- --- ---\nNet/IP using CX-One\nOnline connection via Ether- OK OK OK OK OK OK\nNet/IP using Network Con-\nfigurator\nMounting in an NJ-series --- --- --- --- --- ---\nCPU Unit\nConnection settings using OK OK OK OK OK OK\nthe Sysmac Studio\n*1. This is equivalent to the event log in the EtherNet/IP of an NJ-series Controller.\n*2. A CPU Unit with unit version 1.64 or later is required to use LLDP.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-3\nA-1\nFunctional\nComparison\nof\nEtherNet/IP\nPorts\non\nNJ/NX-series\nCPU\nUnits\nand\nOther\nSeries\nA\nAppendices\nOK: Supported, ---: Not supported\nCJ2H-CPU6£-EIP CS1W-EIP21 CS1W-\nCJ-series\nCJ2M-CPU3£ CJ1W-EIP21 EIP21S\nItem Ethernet\nUnit ver- Unit ver- Unit ver- Unit ver- Unit ver- Unit ver- CJ1W-\nUnit\nsion 1.0 sion 2.0 sion 2.1 sion 1.0 sion 2.0 sion 2.1 EIP21S\nTag data link commu- --- OK OK OK OK OK OK OK\nnications service\nCIP message commu- --- OK OK OK OK OK OK OK\nnications service\nIP routing --- --- --- --- --- --- --- ---\nSocket services OK --- --- --- --- --- --- OK\nFTP server OK --- OK OK --- OK OK OK\nFTP client --- --- --- --- --- --- --- ---\nMail send/receive OK --- --- --- --- --- --- ---\nWeb functions OK --- --- --- --- --- --- ---\nAutomatic adjustment OK --- OK OK --- OK OK OK\nof PLC/Controller’s in-\nternal clock\nError history OK OK OK OK OK OK OK OK\nResponse to PING OK OK OK OK OK OK OK OK\ncommand\nSNMP/SNMP trap --- --- OK OK --- OK OK OK\nCIDR function for IP --- --- OK OK --- OK OK OK\naddresses\nDHCP client --- --- --- --- --- --- --- ---\nLLDP --- --- --- --- --- --- --- ---\nOnline connection via OK --- OK OK --- OK OK OK\nEtherNet/IP using CX-\nOne\nOnline connection via --- OK OK OK OK OK OK OK\nEtherNet/IP using Net-\nwork Configurator\nMounting in an NJ- --- --- --- --- --- --- OK*1*2 OK*1*3\nseries CPU Unit\nConnection settings --- --- --- OK --- --- OK OK\nusing the Sysmac Stu-\ndio\n*1. You cannot use the following functions if you connect to the CPU Unit through an EtherNet/IP Unit.\n• Placing the Sysmac Studio online with the CPU Unit (However, you can place the Network Configurator online)\n• Using the Troubleshooter of an NS-series PT\n*2. The CJ1W-EIP21 can be mounted on the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21: Unit version 2.1 or later\n• NJ-series CPU Unit: Unit version 1.01 or later\n• Sysmac Studio: Version 1.02 or higher\nThe CS1W-EIP21 cannot be mounted to the NJ-series CPU Unit.\n*3. The CJ1W-EIP21S can be mounted on the NJ-series CPU Unit in the following combinations.\n• CJ1W-EIP21S: Lot number: 241001£ or later\n• NJ-series CPU Unit: Unit version 1.67 or later\n• Sysmac Studio: Version 1.60 or higher\nThe CS1W-EIP21S cannot be mounted to the NJ-series CPU Unit.\nA-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-2 Use the Sysmac Studio to Set the Tag\nData Links (EtherNet/IP Connections)\nA-2-1 Overview of the Tag Data Links (EtherNet/IP Connections) Set-\ntings with the Sysmac Studio\nYou can use the Sysmac Studio to set the settings required for creating tag data links (EtherNet/IP\nconnections)*1 between NJ/NX-series Controllers.\n*1. The tag data links and EtherNet/IP connections enable cyclic tag data exchanges on an EtherNet/IP network\nbetween Controllers or between Controllers and other devices. Here, \"EtherNet/IP connection\" refers to both\nthe tag data links and the EtherNet/IP connections.\nVersion Information\nSysmac Studio version 1.10 or higher is required to use the Tag Data Link (EtherNet/IP Con-\nnection) Settings.\nAcceptable System Configuration Conditions for Setting the Ether-\nNet/IP Connection Settings on the Sysmac Studio\nIf an NJ/NX-series Controller operates as the originator device, you can use the Sysmac Studio to set\nthe originator device settings for the EtherNet/IP connections.\nSimilarly, if an NJ/NX-series Controller operates as the target device, you can use the Sysmac Studio\nto set the tags and tag sets of the target device.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-5\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nSysmac\nStudio\nA-2-1\nOverview\nof\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nSettings\nwith\nthe\nAppendices\nSettings for the originator device Settings for the target device\nNX-series Controller NX-series Controller\n(Two built-in (Two built-in\nEtherNet/IP ports) EtherNet/IP ports)\nNJ-series Controller NJ-series Controller\nTag and tag set settings\nSetting with the Sysmac\nStudio is possible.\n(A built-in (A built-in EtherNet/IP port on the\nEtherNet/IP port on CPU Unit or EtherNet/IP Unit)\nthe CPU Unit or Tag and tag set settings\nCS-/CJ-series PLC\nEtherNet/IP Unit)\nSetting is possible only with\nthe Network Configurator.\nFH/FZ/FQ/ZW-series Sensor\nor another similar Unit Tag and tag set settings\nSettings not required.\nTag and tag set settings Connection settings\nSetting with the Sysmac Setting with the Sysmac\nStudio is possible. Studio is possible.\nUse the Network Configurator if a CS/CJ-series PLC operates as the originator device.\nSettings for the originator device Settings for the target device\nCS-/CJ-series PLC NJ/NX-series Controller\nSetting is possible only with\nthe Network Configurator.\nA-2-2 Procedure to Make the EtherNet/IP Connection Settings with the\nSysmac Studio\n1 Registering devices • Main Window\n↓ Register devices with which the EtherNet/IP connections\nare established to the project.\nSetup Window\n2 Creating network variables*1 --- Refer to Registering the Net- Global Variable Table on the\nwork Variable for the Origina- Sysmac Studio\ntor Device on page A-12.\n↓\n3 Registering tags and tag sets --- Refer to Registering the Tag EtherNet/IP Connection Set-\nand Tag Set on page A-13. tings (Tag Set Display)\nA-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n↓ Register the network variables that are set in step 2 as\ntags and tag sets.\n4 Setting connections --- Refer to Setting Connections EtherNet/IP Connection Set-\nfor the Originator Device on tings (Connection Display)\npage A-16.\n↓ Specify devices (i.e., target devices and originator devi-\nces) and tag sets to communicate with using the Ether-\nNet/IP connections.\n5 Going online from the Sysmac Studio --- Refer to Transferring the • Main Window\nConnection Settings Data on\npage A-28.\n↓\n6 Downloading EtherNet/IP connection --- Refer to Transferring the • Synchronization Window/\nsettings Connection Settings Data on Transfer to Controller Dia-\nNote Connections automatically start after page A-28. log Box\nthe download. • EtherNet/IP Connection\nSettings\n↓\n7 Checking operation --- Refer to A-2-5 Checking EtherNet/IP Connection Moni-\nStopping and starting connections Communications Status with tor Tab Page\nthe Sysmac Studio and Trou-\nbleshooting on page A-32.\n*1. Variables with its Network Publish attribute set to Output or Input in the Global Variable Table are called\nnetwork variables.\nA-2-3 EtherNet/IP Connection Settings\nThis section describes the screen configuration for EtherNet/IP connection settings.\nScreen Transitions in the EtherNet/IP Connection Settings\n• Connection Settings\nSelect EtherNet/IP Connection Settings from the Tools Menu.\nEtherNet/IP Device List Tab Page\nDouble-click or right-click the\ndevice to set and select Edit EtherNet/IP Connection Settings (Tag Set Display)\nfrom the menu.\nUse the tab icons to switch\nbetween displays.\nEtherNet/IP Connection Settings\n(Connection Display)\nRight-click the device to set\nand select Monitor from the EtherNet/IP Connection Monitor Tab Page\nmenu.\n• Transferring connection settings to the Controller from the computer\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-7\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-3\nEtherNet/IP\nConnection\nSettings\nAppendices\nSelect EtherNet/IP Connection\nSettings from the Tools Menu to\ndisplay the device list.\nSelect Synchronization Select Transfer - To Controller Right-click the device and select\nfrom the Controller Menu. from the Controller Menu. Edit from the menu.\nTransfer to Controller Dialog EtherNet/IP Connection\nSynchronization Window\nBox Settings Tab Page\nPrecautions for Correct Use\nTo transfer only the connection settings, execute Transfer from the EtherNet/IP Connection Set-\nting Tab Page.\nEven if you clear the Do not transfer the connection setting Check Box, the connection set-\ntings are not transferred from the Synchronization Window, the Transfer to the Controller Dia-\nlog Box, or the Transfer from the Controller Dialog Box as long as the data in the computer is\nsynchronized with the data in the Controller.\nEtherNet/IP Device List Tab Page\nThe list indicates the devices to which EtherNet/IP connections can be set.\nFor information on how to access this tab page, refer to Registering the Tag and Tag Set on page\nA-13.\nEtherNet/IP Connection Settings (Tag Set Display)\nRegister tag sets required to create connections.\nEach tag set represents the data that is sent and received through a connection. You can register up\nto eight tags in one tag set.\nA-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nThe name and size of the tag must be the same as those of the network variable *1. Set whether to\ninclude the Controller status information in tags for the tag sets. You can also set the data output oper-\nation at a fatal error occurrence for output tags.\nRefer to Registering the Tag and Tag Set on page A-13 for information on how to register tags and\ntag sets.\n*1. A variable with its Network Publish attribute set to Output or Input in the Global Variable Table is called a\nnetwork variable.\nEtherNet/IP Connection Settings (Connection Display)\nSpecify the target devices and set their connections.\nFor each connection, set the following information: Connection Name, Connection I/O Type, I/O, target\ndevice tag set (target variable), originator device tag set (originator variable), Packet Interval (RPI),\nand Timeout Value.\nRefer to Setting Connections for the Originator Device on page A-16 for information on how to make\nconnection settings.\nPrecautions for Correct Use\nIf you changed the IP address, model, or revision of the target device after making the connec-\ntion settings, perform the following.\nWith the Sysmac Studio version 1.11 or higher, change the connection settings entirely.\nWith the Sysmac Studio version 1.10 or lower, create the connections again.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-9\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-3\nEtherNet/IP\nConnection\nSettings\nAppendices\nEtherNet/IP Connection Monitor Tab Page\nYou can check the EtherNet/IP connection setting status offline and communications status online.\nWhen online, you can start and stop connections.\nRefer to A-2-5 Checking Communications Status with the Sysmac Studio and Troubleshooting on\npage A-32 for information on how to check the EtherNet/IP connection setting status and communi-\ncations status.\nA-10 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-2-4 Making the EtherNet/IP Connection Settings with the Sysmac\nStudio\nThis section describes the procedure to make the EtherNet/IP connection settings with the Sysmac\nStudio.\nHere, we take the following system configuration as an example to describe how to set the\nEtherNet/IP connection settings.\nExample: System that connects the built-in EtherNet/IP port on Controller 1 and the built-in\nEtherNet/IP port on Controller 2 via Ethernet\n• Set the settings so that values in the network variable Net_Out1 allocated for Controller 2 are sent to\nthe network variable Net_In1 allocated for Controller 1 at the set RPI of 50 ms cycle.\n• This example assumes the programs for both Controllers 1 and 2 are registered in the same project.\nSysmac Studio\nProject on the Sysmac Studio\nControllers 1 and 2 are respectively named as follows and registered in the same project.\n· Controller_1 (Controller 1: NJ501-1500 (Built-in EtherNet/IP Port))\n· Controller_2 (Controller 2: NJ501-1500)\nEthernet\nOriginator device Target device\nController 1 Controller 2 CJ1W-EIP21\n(NJ501-1500: (NJ501-1500) (NJ)\nBuilt-in EtherNet/IP\nport)\nOriginator device tag set Target device tag set\nNet_In1 (Tag set) Net_Out1 (Tag set)\n(Tag) (Tag)\nNet_In1 Net_Out1\nConvert the network variable to the tag.\nNetwork variable Network variable\n(Network Publish attribute: Input) (Network Publish attribute: Output)\nNet_In1 Net_Out1\n(Data type: WORD) (Data type: WORD)\nFollow the flow below to set the settings to Controllers 1 and 2 for which to establish EtherNet/IP con-\nnections.\nThe required settings for the originator device and the target device are shown below.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-11\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nSettings for the originator device (Controller 1) Settings for the target device (Controller 2)\nRegistering the network variable Registering the network variable\nRegistering the tag and tag set Registering the tag and tag set\nSetting connections\nTransferring settings for the connection, Transferring settings for the tag and\nthe tag, and the tag set the tag set\nRegistering the Network Variable for the Originator Device\nRegister the network variable that is sent and received using the EtherNet/IP connections.\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for the operations for regis-\ntering variables.\n1\nAssign the network variable to the tag used for the EtherNet/IP connection for Controller 1\n(originator device).\nThis network variable receives data from Controller 2 (target device).\nSelect Input or Output for Network Publish of a variable in the Global Variable Table so that\nthe variable can serve as a network variable, i.e. the variable can be used for the EtherNet/IP\nconnections.\nIn this example, set the network variable for Controller 1 as shown below.\n• Variable name: Net_In1\n• Data type: WORD\n• Network Publish attribute: Input\n Network Variables Used for EtherNet/IP Connections\n• Network variable name\nA-12 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nYou cannot specify an I/O memory address for a tag name in the EtherNet/IP connection set-\ntings. Thus, do not specify an I/O memory address for the network variable name that is to be\nassigned to a tag.\nThe following text strings are recognized as the I/O memory address names."}
+{"question": "Variable names with the following single-byte letters (uppercase or lowercase) followed by", "answer": "single-byte numerals\n• H (H000 to H511)\n• W (W000 to W511)\n• D (D00000 to D32767)\n• E0_ to E18_(E0_00000 ... E0_32767 to E18_00000 ... E18_32767)\nTo specify an I/O memory address for a tag on an NJ-series CPU Unit, NX102 CPU Unit, or\nNX1P2 CPU Unit, do not specify the I/O memory address for the tag directly. Instead, create a\nvariable, set an AT specification of the I/O memory address on the Sysmac Studio, and then\nspecify the variable with the AT specification for the tag.\n• Size of variables\nTo use an EtherNet/IP Unit as an EtherNet/IP device, set an even number of bytes for the size of\nthe network variable used for the EtherNet/IP connections regardless of an odd number of bytes\nfor the tag size.\nNetwork variable Tag\nAAA AAA\n(4 bytes) (3 bytes)\nThe CPU Unit memory is consumed in units of two bytes. To assign tags of odd numbers of bytes\nto network variables, specify even byte numbers (i.e., sizes of the tags + 1) to the network variables.\n• Data concurrency\nTo maintain concurrency in the values of network variables that are assigned to tags, you must\nset refreshing tasks.\nRefer to 6-1-7 Concurrency of Tag Data Link Data on page 6-14 for details.\nRegistering the Tag and Tag Set\nRegister the required tag and tag set for the EtherNet/IP connections.\nYou can register tags and tag sets in the EtherNet/IP Connection Setting Tab Page.\nPrecautions for Correct Use\nMake the following settings to refresh all of the tag data in the same tag set at the same time.\n• Use the Sysmac Studio, in advance, to specify the same refreshing task for all of the varia-\nbles that are assigned to tags in the tag set.\n• If you use the NJ-series CPU Unit, do not place tag variables that have AT specifications in\nI/O memory and tag variables that do not have AT specifications in the same tag set.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-13\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\n1\nSelect EtherNet/IP Connection Settings from the Tools Menu.\nThe EtherNet/IP Device List Tab Page is displayed.\n2\nIn this example, right-click Built-in EtherNet/IP Port Settings for the originator device and se-\nlect Edit from the menu to open the EtherNet/IP Connection Setting Tab Page.\n3\nClick the (Show Tag Set Display) icon in the EtherNet/IP Connection Setting Tab Page.\n4\nClick the Input tab to switch to the Input Tab Page. Register the tag set and the tag.\nUse one of the following methods to register the tag set and the tag.\n• Independ- : Manually registers network variables in the Controller as tags.\nent registra-\ntion\n• Batch regis- : Registers all network variables in the Controller as tags at the same time.\ntration\n5\nRegister tags and tag sets independently.\n1) Right-click anywhere in the Input Tab Page of the EtherNet/IP Connection Setting Tab Page\nand select Create New Tag Set from the menu.\n2) Enter the tag set name, Net_In1, directly into the list in the Input Tab Page.\n3) Right-click anywhere in the Input Tab Page and select Create New Tag from the menu.\n4) Enter tag name Net_In1.\nTag set name\nTag name\nPrecautions for Correct Use\nAny name can be specified for the tag set if the name matches one of the registered network\nvariable names in the Controller.\nAs you enter characters (or immediately after you press the Ctrl + Space Keys), the Sysmac\nStudio Entry Assistance provides a list of variable names registered in the Controller. Select the\nvariable name from the list.\nA-14 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nAdditional Information\nYou can register up to 8 tags in a tag set.\nSet as shown below to register multiple tags.\nExamples:\nTag set name\n▼ Network_Input_Value .... (Tag set name)\nNet_In1 .... (Tag name)\nNet_In2 .... (Tag name)\n6\nRegister all tags and tag sets at the same time.\n1) Right-click anywhere on the Input Tab Page of the EtherNet/IP Connection Settings Tab\nPage and select Register All Tag Sets or click the Registration All Button to display the\nTag Set Registration Setting Dialog Box.\nThis dialog box lists the variables that are registered in the Global Variable Table and\nalso have the Network Publish attribute set to Input or Output.\n2) Select the variable to register as a tag, and then click the Register Button.\n3) The automatically registered tag is added to the list in the EtherNet/IP Connection Setting\nTab Page.\nWith automatic registration, the tag is registered under a tag set having the same name\nas the tag, i.e., a single tag is registered in a single tag set.\nTag set name\nTag name\n7\nSet the following settings for the registered tag and tag set.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-15\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\n• Setting for Tag Sets\nName Item\nTag Set Name Enter the tag set name.\nYou can change the names as required.\nSize (Byte) Gives the total size of the tag in bytes.\nInstance ID Gives the instance ID.\n• Auto\n• IN_{min}...IN_{max}\n{min} represents the minimum number of Produced Assembly identifica-\ntion numbers recorded in the EDS files for the relevant devices.\n{max} represents the maximum number of Produced Assembly identifica-\ntion numbers recorded in the EDS files for the relevant devices.\nController Status Specify whether to include the Controller status in the tag set.\n• Setting for Tags\nName Item\nTag Name Enter the tag name.\nSpecify the tag name that matches one of the registered network variable\nnames in the Controller.\nBit Selection Specify whether to set the tag data size in bits.\nSelected: Set the size in bits.\nNot selected: Set the size in bytes.\nSize (Byte) Gives the size of the tag in bytes.\nSize (Bit) Gives the size of the tag in bits.\nOutput at Fatal Error Specify whether to clear the output data or continue to send it when a ma-\njor fault level Controller error occurs in the Controller.\n• Retained\n• Cleared\nSetting Connections for the Originator Device\nAfter the tag set registration, set the connection settings for transferring data using the EtherNet/IP\nconnections.\nMake the connection settings in the originator device (i.e., Controller 1 in this example) only.\nRegister the tag and tag set for Controller 2 (Target device) before setting the connection settings as\ndescribed in this example.\nRefer to Registering the Tag and Tag Set for the Target Device on page A-24 for the operations for\nregistering tags and tag sets.\nA-16 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nPrecautions for Correct Use\nIf you change the IP address, model, or revision of the target device after making the connec-\ntion settings, you must also change the target device settings that are included in the connec-\ntion settings.\nFor information on how to change the target device settings in the connection settings, refer to\nChanging the Target Device Settings after Making Connection Settings on page A-23.\n1\nSelect EtherNet/IP Connection Settings from the Tools Menu to display the EtherNet/IP De-\nvice List Tab Page.\n2\nRight-click Built-in EtherNet/IP Port Settings for Controller 1 (originator device in this exam-\nple), and select Edit from the menu.\nThe EtherNet/IP Connection Setting Tab Page is displayed.\n3\nClick the (Show Connection Display) icon in the EtherNet/IP Connection Setting Tab\nPage.\n4\nSelect CJ1W-EIP21(NJ) from Target Device in the Toolbox on the right of the tab page.\nWhen you select CJ1W-EIP21(NJ), the target device tag set (Net_Out1) for Controller 2 is dis-\nplayed in the Variable Name column in the Toolbox.\n5\nDrag the target device tag set Net_Out1 from the Variable Name column in the Toolbox to the\nConnection List.\nAs you enter characters (or immediately after you press the Ctrl + Space Keys), a list of target\ndevice variables that can be set for the connection is provided. Select the value from the list.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-17\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nDrag\n6\nSpecify Originator Variable and its Size [Byte] for the tag set Net_Out1 added in step 5.\nHere, specify Net_In1 for Originator Variable and 2 for its Size [Byte].\nChange the other settings as required.\nYou can set the following items in the connection settings.\nName Setting Methods\nTarget Device Select the target device.\nConnection Name Any name can be given to the connection (32 single-byte characters\nmax.).\nConnection I/O Type Input Only (Tag type) is selected if the EtherNet/IP connection is es-\ntablished on a CS1W-EIP21, CS1W-EIP21S, CJ1W-EIP21, CJ1W-\nEIP21S, CJ2B-EIP21*1, CJ2M-EIP21*2, CJ1W-EIP21 (CJ2)*3, CJ1W-\nEIP21 (NJ)*4, CJ1W-EIP21S (CJ2)*5, CJ1W-EIP21S (NJ)*6, NX701,\nNX502-££££, NX102-££££, NX1P2, NJ501-££££, NJ301-££\n££, or NJ101 CPU Unit.\nWhen you create EtherNet/IP connection for another target device,\nselect the connection I/O type specified in the device's EDS file.\nUse the Input Only (ID type) setting when the originator is a node\nfrom another manufacturer and does not support connection settings\nwith a Tag type setting.\nInput/Output The connection's input/output is automatically displayed based on the\nselected connection.\nInput Only: Just Input is displayed.\nTarget Variable Select the target node's tag set to assign it.\n• Input is specified for Input/Output: Select the target's output (pro-\nduce) tag set.\n• Output is specified for Input/Output: Select the target's input (con-\nsume) tag set.\nSize [Byte] The data sizes of the target variables are displayed.\nA-18 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nName Setting Methods\nOriginator Variable Select the originator node's tag set to assign it.\n• Input is specified for Input/Output: Select the originator's input\n(consume) tag set.\n• Output is specified for Input/Output: Select the originator's output\n(produce) tag set.\nSize [Byte] Enter the data sizes of the originator variables.\nConnection Type Select whether the data is to be sent in the multicast or unicast (point-\nto-point) form. The default setting is multicast.\n• Multi-cast connection: Select when the same data is to be shared\nby multiple nodes. This setting is usually used.\n• Point-to-point connection: Select when the same data is not to be\nshared by multiple nodes.\nSince the data is sent in unicast transmission, other nodes are not\nburdened with unnecessary load.\nNoteRefer to 6-1-4 Overview of Operation on page 6-7 for details on\nhow to use multi-cast and unicast connections, and how to count\nthe number of connections.\nRPI [ms] Set the data update cycle (i.e., the packet interval) of each connection\nbetween the originator and target.\nThe default setting is 50 ms (i.e., data is updated once every 50 ms).\nTimeout Value Set the time until a connection timeout is detected.\nThe timeout value is set as a multiple of the packet interval (RPI) and\ncan be set to 4, 8, 16, 32, 64, 128, 256, or 512 times the packet inter-\nval.\nThe default setting is RPI x 4.\nThe timeout value must be at least 10 ms.\n*1. Built-in EtherNet/IP port in CJ2H-CPU6£-EIP CPU Unit\n*2. Built-in EtherNet/IP port in CJ2M-CPU££ CPU Unit\n*3. CJ1W-EIP21 mounted to CJ2 CPU Unit\n*4. CJ1W-EIP21 mounted to NJ-series CPU Unit\n*5. CJ1W-EIP21S mounted to CJ2 CPU Unit\n*6. CJ1W-EIP21S mounted to NJ-series CPU Unit\n7\nThe Toolbox displays the target devices if the devices are registered in the same Sysmac Stu-\ndio project as where the originator devices are registered.\nYou can use one of the following methods to add unregistered devices in the same Sysmac\nStudio project as where the originator devices are registered to the Target Device List.\n• Importing devices that are registered in another project\nYou can import NJ/NX-series Controllers registered in another project data and add them to\nthe Device List.\n• Registering devices using user-specified settings\nYou can manually add target devices to the device list.\nAdditional Information\nYou can add target devices to the Device List by installing EDS files that include connection in-\nformation for the devices in the Sysmac Studio and register the devices to the project.\nRefer to Adding EDS Files on page A-22 for details.\n8\nImport devices that are registered in another project.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-19\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\n1) Click the (Import a device from another project) Button in the Toolbox on the right of\nthe EtherNet/IP Connection Setting Tab Page.\n2) The Import from Another Project Dialog Box is displayed. Click the Project Button, select a\nproject to import and click the Open Button.\n3) The list of EtherNet/IP devices registered in the selected project will be displayed. Select\nthe target devices to import, and click the Import Button.\nNoteOnly the project for which the EtherNet/IP connection settings are set will be displayed.\nThe imported EtherNet/IP devices are added to the Target Device List in the Toolbox.\nA-20 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n9\nRegister devices as required.\n1) Click the + Button under the Target Device List in the Toolbox.\nThe Add Target Device Pane is displayed.\n2) Enter relevant items for the target devices to add.\nMenu Description\nNode address Enter the target device IP address.\nModel name Select the target device model.\nRevision Select the revision of the target device.\n3) Here, set the following items for Controller 3 and click the Add Button.\nThe target device is added to the Target Device List in the Toolbox.\nNode address: 192.168.250.3\nModel name: NJ501-1500\nRevision: 2\n4) You can click the Import Tag Set Button to import the tag sets that are set in the Network\nConfigurator to the target devices.\nSelect To/From File - Export to File in the Tag Sets Tab Page of the Edit Device\nParameters Dialog Box, and generate CSV files to import.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-21\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\n Adding EDS Files\nNoteThe Modular EDS device is supported by the Sysmac Studio version 1.11 or higher.\n1\nRight-click anywhere in the Target Device List in the Toolbox of the EtherNet/IP Connection\nSetting Tab Page and select Display EDS Library from the menu.\n2\nThe EDS Library Dialog Box is displayed. Click the Install Button.\n3\nSelect the EDS file to add, and then click the Open Button.\nThe EDS file is added.\n4\nThe EtherNet/IP device with the EDS file installed is added to the EDS Library.\nDevices listed in the EDS Library are used as a candidate device list when adding devices to\nthe Target Device List in the Toolbox of the EtherNet/IP Connection Setting Tab Page.\nA-22 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nChanging the Target Device Settings after Making Connection Set-\ntings\nIf you change the IP address, model, or revision of the target device after making the connection set-\ntings, you must also change the target device settings that are included in the connection settings.\nYou can change the target device settings entirely.\nPrecautions for Correct Use\nWhen you use the Sysmac Studio version 1.10 or lower, create the connections again if you\nchanged the target device after configuring the connection settings.\n Changing the IP Addresses for All Target Devices\n1\nRight-click one of the connection lines and select Change Node Address from the menu.\n2\nThe Node Address Change Dialog Box is displayed. Enter a new IP address in New IP\naddress.\nTo apply the same change to other connections, select the Apply the change to other\nconnections Check Box.\n3\nTo apply the same change to other connections, select the Apply the change to other\nconnections Check Box.\n4\nClick the OK Button.\n Changing All Target Device Information including Model Names and Revi-\nsions\n1\nRight-click one of the connection lines and select Change Target Device from the menu.\n2\nThe Target Device Change Dialog Box is displayed. Select a target device from New device.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-23\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nPrecautions for Correct Use\n• Changeable target devices are limited to ones that have \"OMRON\" in the Vendor ID and is an\nEDS device of the Communications Adapter in the Device Type.\n• To display a device in the list of selectable new target devices, the device must be registered\nas the target device in the Toolbox.\n3\nTo apply the same change to other connections, select the Apply the change to other\nconnections Check Box.\n4\nClick the OK Button.\nRegistering the Network Variable for the Target Device\n1\nAssign the network variable to the tag used for the EtherNet/IP connection for Controller 2 (tar-\nget device).\nThis network variable stores data to send to Controller 1 (originator device).\nSet the Network Publish attribute to Input or Output in the Global Variable Table for the varia-\nble so that the variable serves as a network variable, i.e., the variable can be used for the\nEtherNet/IP connections. In this example, set the network variable for Controller 1 as shown\nbelow.\n• Name: Net_Out1\n• Data type: WORD\n• Network Publish attribute: Output\nRegistering the Tag and Tag Set for the Target Device\nSet the tag and tag set for the target device.\n1\nSelect EtherNet/IP Connection Settings from the Tools Menu.\nThe EtherNet/IP Device List Tab Page is displayed.\nA-24 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n2\nRight-click CJ1W-EIP21, the EtherNet/IP Unit connected to the Controller 2 (originator device\nin this example), and select Edit from the menu.\nThe EtherNet/IP Connection Setting Tab Page is displayed.\n3\nClick the (Show Tag Set Display) icon in the EtherNet/IP Connection Setting Tab Page.\n4\nClick the Output tab to switch to the Output Tab Page. Register the following tag and tag set.\nThe tag and tag set can be registered in the same way as for the target device. (Refer to Reg-\nistering the Tag and Tag Set on page A-13.)\nChecking the Device Bandwidth Usage\nThe bandwidth usage for the device can be displayed from the EtherNet/IP Connection Setting Tab\nPage.\nThis value is for when multicast filtering is used.\nPrecautions for Correct Use\nIn the Device Bandwidth Dialog Box, you can only check the bandwidth being used for the\nEtherNet/IP connections from one originator device to its target devices.\nThe actual bandwidth used for the EtherNet/IP network must be calculated by taking into ac-\ncount of all bandwidths used on the EtherNet/IP network (i.e., bandwidths used for connections\nfor the other devices in the EtherNet/IP network than the one given on the dialog box must be\nincluded into the calculation).\n Procedure\nClick the Device Bandwidth Button in the EtherNet/IP Connection Setting Tab Page for the target\ndevice.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-25\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nMenu Description\nPPS Gives the bandwidth used for each target device and total bandwidth used\nfor all target devices.\nSet Packet Interval (RPI) for Changes all Packet Interval (RPI) values for all target devices.\nAll Connections\nAdditional Information\nYou can specify a value in Set Packet Interval (RPI) for All Connections and click the Update\nButton to change packet interval (RPI) values set in the connection settings for all target devi-\nces to the specified value.\n Calculation Example for Bandwidth Used (PPS) for Each Device by the\nEtherNet/IP Connections\nEstablishing following three EtherNet/IP connections between Controllers (1) to (3) in the\nEtherNet/IP network\nDevice bandwidth\nConnection type Relevant devices in the EtherNet/IP connections\nusage (PPS)\nConnection (1) NJ-series Controller 2 (target device) 50 pps\nto NJ-series Controller 1 (originator device)\nConnection (2) NJ-series Controller 1 (target device) 10 pps\nto NJ-series Controller 2 (originator device)\nConnection (3) NJ-series Controller 3 (target device) 210 pps\nto NJ-series Controller 1 (originator device)\nEtherNet/IP network\nConnection (3) Connection (1)\nConnection (2)\nNJ-series Controller 3 NJ-series Controller 1 NJ-series Controller 2\n(192.168.250.3) (192.168.250.1) (192.168.250.2)\nBandwidth used (PPS) for each EtherNet/IP device is as given below.\nA-26 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nConnection (1)\nConnection (3)\nEtherNet/IP connection settings for Controller 1\nConnection (2)\nEtherNet/IP connection settings for Controller 2\nIn this example, the PPS for Connection (1) is 50 pps, the PPS for Connection (2) is 10 pps, and\nthe PPS for Connection (3) is 210 pps. Therefore, bandwidth used (PPS) for each EtherNet/IP de-\nvice is as given below."}
+{"question": "168.250.1: 270 pps = 50 pps (for Connection (1)) + 10 pps (for Connection (2)) + 210 pps (for", "answer": "Connection (3))"}
+{"question": "168.250.3: 210 pps = 210 pps (for Connection (3))", "answer": " Adjusting Method\nIf the calculation result value exceeds the values in the specifications of the devices used in the\nEtherNet/IP connections, re-evaluate the overall network configuration and correct it by taking\nsteps such as selecting a different Ethernet switch or splitting the network.\nIf the RPI is made longer, the PPS for the EtherNet/IP connections will decrease.\nYou can change the RPI values in the connection settings for all the target devices by specifying a\nvalue in Set Packet Interval (RPI) for All Connections in this dialog box.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-27\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nRefer to 14-2-2 Tag Data Link Bandwidth Usage and RPI on page 14-9 for the relationship between\nthe PPS for the device and the RPI.\nTransferring the Connection Settings Data\nYou can synchronize and transfer EtherNet/IP connection settings along with the program data. You\ncan also transfer all the EtherNet/IP connection settings along with the program data.\nPrecautions for Correct Use\n• If the node addresses (IP addresses) are not set correctly, you may connect to the wrong\nController and set incorrect device parameters. Download data only after you confirm that\nyou are connected to the correct Controller.\n• If incorrect connection settings are set, it may cause equipment to operate unpredictably.\nEven when the correct connection settings are set, make sure that there will be no effect on\nequipment before you transfer the data.\n• A connection error will result if the network variables that are used in the tag settings are not\nset in the Controller. Before downloading the connection settings, check to confirm that the\nnetwork variables used in the tag settings are set in the Controller.\n• If a communications error occurs, the output status depends on the specifications of the de-\nvice being used. When a communications error occurs for a device that is used along with\noutput devices, check the operating specifications and implement safety countermeasures.\n• The built-in EtherNet/IP port and the port on the EtherNet/IP Unit are automatically restarted\nafter the parameters are downloaded. This restart is required to enable the tag set and con-\nnection information. Before you download the parameters, check to confirm that problems will\nnot occur with the equipment when the port is restarted.\n• Do not disconnect the Ethernet cable or reset or turn OFF the power to the EtherNet/IP Unit\nduring the parameter download.\n• The EtherNet/IP connections between relevant nodes is stopped during a download. Before\nyou download data in RUN mode, make sure that it will not affect the controlled system.\nAlso implement interlocks on data processing in ladder programming that uses EtherNet/IP\nconnections when the connections are stopped or a connection error occurs.\n• In the EtherNet/IP network, if the device bandwidth usage (PPS) exceeds the Unit allowable\nbandwidth (PPS), the EtherNet/IP connection operations may not agree with the settings.\nIf you increase the RPI value in such a case, there are cases when the problem can be re-\nsolved (i.e., the operations agree the settings).\n Synchronizing/Transferring a Whole Project\n1\nEstablish an online connection between the computer and the Controller, and then select\nSynchronization from the Controller Menu. (Or, click the Button on the Toolbar.)\nA-28 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nThe Synchronization Window is displayed, and comparison of the user program and parameter\nsettings between the Sysmac Studio and the Controller is started.\n2\nThe following Uploading and Downloading Data Window is displayed after the automatic com-\nparison.\n3\nClear the Do not transfer the EtherNet/IP connection settings (i.e., tag data link settings)\nCheck Box and then click the Transfer To Controller Button.\nThen the EtherNet/IP connection settings are transferred along with the not-synchronized data.\nIf no EtherNet/IP connection settings are set in the Sysmac Studio, no data will be sent.\n Transferring all data\n1\nEstablish an online connection between the computer and the Controller and then select\nTransfer - To Controller from the Controller Menu. (Or, click the Button on the Toolbar.)\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-29\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\n2\nThe Transfer to Controller Dialog Box is displayed.\nClear the selection of the Do not transfer the EtherNet/IP connection settings (i.e., tag data\nlink settings) Check Box, and then click the Execute Button.\nPrecautions for Correct Use\nTo transfer only the connection settings, execute Transfer from the EtherNet/IP Connection Set-\nting Tab Page.\nEven if you clear the Do not transfer the connection setting Check Box, the connection set-\ntings are not transferred from the Synchronization Window, the Transfer to Controller Dialog\nBox, or the Transfer from Controller Dialog Box as long as the data in the computer is\nsynchronized with the data in the Controller.\n Transferring Only the EtherNet/IP Connection Settings\nYou can transfer tag sets and connections to the EtherNet/IP devices.\n1\nEstablish an online connection with the Controller.\n2\nClick the Transfer to Controller or Transfer from Controller Button in the EtherNet/IP Con-\nnection Setting Tab Page.\nThe tag settings and connection settings set at that time are transferred to the Controller con-\nnected online.\n3\nIf the Controller connected online is in RUN mode, the dialog box to confirm whether to switch\nto PROGRAM mode before transferring the settings is displayed.\nA-30 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n Comparison\nThe differences in the tag set and connection settings between the project and the EtherNet/IP de-\nvices can be displayed.\n1\nClick the Compare Button in the EtherNet/IP Connection Setting Tab Page.\nStarting and Stopping EtherNet/IP Connections\n Automatically Starting EtherNet/IP Connections\nThe EtherNet/IP device is automatically restarted and EtherNet/IP connections are automatically\nstarted immediately after the connection settings are downloaded from the Sysmac Studio.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-31\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-4\nMaking\nthe\nEtherNet/IP\nConnection\nSettings\nwith\nthe\nSysmac\nStudio\nAppendices\nPrecautions for Correct Use\nConnections are adversely cut off if any of the following errors occurs in the CPU Unit that is the\noriginator while EtherNet/IP connections are active.\n• Major fault level Controller error\n• Partial fault level Controller error\n Starting and Stopping the EtherNet/IP Connections for the Entire Network\nYou can start and stop EtherNet/IP connections from the user program or from the Sysmac Studio.\nPrecautions for Correct Use\nUse the same method (i.e., either the user program or the tool software) to both start and stop\nEtherNet/IP connections.\nFor example, if you use the _EIP_TDLinkStopCmd (Tag Data Link Communications Stop\nSwitch) system-defined variable to stop EtherNet/IP connections, you cannot start them from\nthe Sysmac Studio and the Network Configurator.\nA-2-5 Checking Communications Status with the Sysmac Studio and\nTroubleshooting\nYou can monitor the communications status of the EtherNet/IP connections after their settings are set.\nYou can also check errors.\nPrecautions for Correct Use\nMake sure that the connection settings in both the Sysmac Studio and the Controller are con-\nsistent before using the monitor functions. You can use the Comparison on page A-31 to see if\nthey are the same.\nChecking Communications Status with the Sysmac Studio\nYou can check the communications status on the EtherNet/IP connections in the EtherNet/IP Connec-\ntion Monitor Tab Page.\n1\nSelect EtherNet/IP Connection Settings from the Tools Menu to display the EtherNet/IP De-\nvice List Tab Page.\n2\nRight-click the Controller for which you want to check the communications status, and select\nMonitor from the menu.\nThe EtherNet/IP Connection Monitor Tab Page is displayed. In the EtherNet/IP Connection\nMonitor Tab Page, each communications status is displayed in six tabs.\nA-32 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n3\nSelect one of the six tabs for which you want to confirm the communications status.\n• Status Tab Page\nThis tab page gives the TRUE/FALSE status of the system-defined variables that monitors the tag\ndata link status and communication status for errors. If any of the variables is TRUE, its checkbox is\nmarked with .\nRefer to 15-2-1 The Network Configurator's Device Monitor Function on page 15-3 for details on\neach status item.\n• Connection Status Tab Page\nCurrent status of each connection is given.\nName Description\nConnection Name Gives the current status of each connection with the following text colors.\nBlue: Normal\nRed: There is at least one connection that has not been established.\nGray: There are no connections or the connection operation is stopped.\nType Gives the connection type.\nStatus Gives the current status on each connection with codes.\n• Normal operation: 00:0000\n• Abnormal operation: Gives an error code.\nThis information can be used to identify the cause of EtherNet/IP connec-\ntion errors. Refer to 15-2-2 Connection Status Codes and Troubleshooting\non page 15-11 for details on the connection status.\n• Tag Status Tab Page\nThis tab page gives if the tag settings for each tag for EtherNet/IP connections are set so that data\ncan be exchanged with target devices.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-33\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-5\nChecking\nCommunications\nStatus\nwith\nthe\nSysmac\nStudio\nand\nTroubleshooting\nAppendices\nName Description\nTag Name The current status of each tag is indicated by its color.\nRed: Tag name resolution error\nBlue: Tag name resolution normal\nGray: Not yet transferred (no information in device).\nInput/Output Gives the type of the tag.\nStatus The following status is displayed depending on the status that is set.\n• Normally resolved: Normal data exchange is possible.\n• Different sizes: Different sizes are set for the network variables and the tag\nsettings.\nA connection will not be established for a tag for which this error occurs.\n• No tag: A network variable is not set in the variable table in the CPU Unit\nfor the specified tag setting. Or, instead of a member of union variable, un-\nions are specified.\nA connection will not be established for a tag for which this error occurs.\n• Attribute error: The following two factors cause this error."}
+{"question": "The I/O direction that is set in the tag data link settings does not agree", "answer": "with the I/O direction of the variable in the CPU Unit. There is an error in\nthe setting of a Network Publish attribute for a CPU Unit variable.\nA connection will not be established for a tag for which this error occurs.\n• Output Tag Set and Input Tag Set Tab Pages\nYou can monitor the status of each input/output tag set that is used for the EtherNet/IP connections.\nNoteThe tag set status monitor is not available for a built-in EtherNet/IP port on NJ-series Controller version"}
+{"question": "08 or earlier.", "answer": "Click ▼ of each tag to display its detailed information.\nName Description\nTag Set Name Gives the connection status.\nIf there is a connection error, \"Not connected or error\" is given.\nA-34 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nName Description\nTag set size Gives the size of the tag set in bytes.\nConnected time Gives the total connection duration in milliseconds.\nUnconnected time Gives the total disconnection duration in milliseconds.\nNumber of connections (in the Gives the number of connections.\nOutput Tag Set Tab Page)\nNumber of connected origina- Gives the number of the connected originator devices.\ntors (in the Output Tag Set\nTab Page)\nOriginator list (in the Output Gives the detailed information of the connected originators.\nTag Set Tab Page), Target list\n(in the Input Tag Set Tab\nPage)\nOriginator name (in the Gives no information.\nOutput Tag Set Tab Page),\nor Target name (in the\nInput Tag Set Tab Page)\nIP address (in the Output Gives the IP addresses allocated for the originators.\nTag Set Tab Page), or Re-\nmote IP address (in the\nInput Tag Set Tab Page)\nConnected time (in the Gives the total duration of connection with the originator in milliseconds.\nOutput Tag Set Tab Page)\nUnconnected time (in the Gives the total duration of disconnection with the originator in milliseconds.\nOutput Tag Set Tab Page)\nDestination IP address (in Gives the destination IP addresses. If the multi-cast connections are used,\nthe Output Tag Set Tab its own multi-cast address is displayed.\nPage)\nO->T RPI (packet interval) Gives the RPI of connection from the originator to the target in milliseconds.\nT->O Heartbeat transmis- Gives the heartbeat transmission period of the connections from the target\nsion cycle (ms) to the originator in milliseconds.\nO->T Timeout Gives the timeout time for the connections from the originator to the target\nin milliseconds.\nT->O Timeout Gives the timeout time for the connections from the target to the originator\nin milliseconds.\nO -> T API (actual packet Gives the RPI of connection from the originator to the target in milliseconds.\ninterval)\nT->O Actual heartbeat Gives the actual heartbeat transmission period of the connections from the\ntransmission cycle (ms) target to the originator in milliseconds.\nO->T Connection ID Gives the connection identification for the connections from the originator to\nthe target in hexadecimal.\nT->O Connection ID Gives the connection identification for the connections from the target to the\noriginator in hexadecimal.\n• Ethernet Information Tab Page\nThis tab page displays the communications status at the communications driver level of the Ether-\nnet/IP port.\nThe error counter information can be used to confirm whether communications problems have oc-\ncurred.\nUnder the Tag Data Link, you can confirm characteristics such as the bandwidth usage (PPS).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-35\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-5\nChecking\nCommunications\nStatus\nwith\nthe\nSysmac\nStudio\nand\nTroubleshooting\nAppendices\nDisplay example for an NJ-series CPU Unit\nDisplay example for an NJ-series CPU Unit\nWith an NX701 CPU Unit, the status for each port is displayed.\nA-2-6 Troubleshooting\nIn the case that there is a setting error or a communications error in the EtherNet/IP networks, the\nSysmac Studio displays the error in the Troubleshooting Dialog Box.\nRefer to the NJ/NX-series Troubleshooting Manual (Cat. No. W503) for how to identify errors and de-\ntails on errors.\nTroubleshooting When Transferring and Monitoring the EtherNet/IP\nConnection Settings Fail with Sysmac Studio Version 1.10 or High-\ner\nThe first time you establish an online connection between the Controller and the computer that runs\nthe Sysmac Studio version 1.10 or higher with Windows Firewall on the computer enabled, a dialog\nbox may be displayed to confirm the connection. If that occurs, make the following selection in the dia-\nlog box.\n• Unblock (on Windows XP/Vista)\n• Allow access (on Windows 7 or higher)\nA-36 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nIf you make other settings than above, transferring and monitoring the EtherNet/IP connection settings\nmay not be properly performed even if the online connection is successfully established between the\nSysmac Studio version 1.10 or higher and the Controller.\nIf the above problem occurs, take the following corrective method 1 or 2.\n Problems\n• The connection setting data cannot be transferred.\nData Transmission Screen Problem\nSynchronization Window The Sysmac Studio displays the following error message and the data will\nnot be transferred.\nTransfer to Controller Dia- The Sysmac Studio displays the following error dialog box and the data will\nlog Box not be transferred.\nEtherNet/IP Connection Set- The Transfer to Controller and Transfer from Controller Buttons are\nting Tab Page grayed out and the data cannot be transferred/compared.\n• Monitoring cannot be performed\nMonitor results in the EtherNet/IP Connection Monitor Tab Page remain as \"---\".\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-37\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-6\nTroubleshooting\nAppendices\nMethod 1: Disabling Windows Firewall Settings\nPrecautions for Correct Use\nThe main function of the firewall is to prevent unwanted access from external sources (e.g., the\nInternet).\nThe changes that are made with the following procedures are to allow the Sysmac Studio and\nthe NJ/NX-series Controller to connect. If your computer is on an inhouse network, make sure\nthat security will not be jeopardized before you change the settings.\n Windows XP\n1\nOpen the Control Panel from the Windows Start Menu and then select Windows Firewall\nicon.\nThe Windows Firewall Dialog Box is displayed.\n2\nClick on the Exceptions tab and select Sysmac Studio in the Programs and Services list.\nA-38 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n Windows Vista, Windows 7, or later version\n1\nOpen the Control Panel from the Windows Start Menu and then select Windows Firewall\nicon.\nThe Windows Firewall Dialog Box is displayed.\n2\nSelect Turn Windows Firewall On or Off.\nThe Customize Settings Dialog box is displayed.\n3\nClear the Block all incoming connections, including those in the list of allowed programs\nCheck Box and click the OK Button.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-39\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-6\nTroubleshooting\nAppendices\n4\nSelect the Advanced Tab in the Windows Firewall Dialog Box.\nThe Windows Firewall with Advanced Security Dialog Box is displayed.\n5\nClick Inbound Rules in the left pane and then double-click SysmacX86Server in the Inbound\nRules list for Sysmac Studio Ver.1.31 or later. For Sysmac Studio earlier than Ver.1.31, double-\nclick Sysmac Studio.\nIf you double-click SysmacX86Server, SysmacX86Server Properties window appears. If you\ndouble-click Sysmac Studio, Sysmac Studio Properties window is displayed.\n6\nFor Sysmac Studio Ver.1.31 or later, make the following settings in the SyamacX86Server\nProperties window. If Sysmac Studio version is earlier than Ver. 1.31, make the following set-\ntings in the Syamac Studio Properties window.\n• If the Public Check Box under Profiles is not selected in the Advanced Tab Page, select it.\n• If the Enabled under General is not selected in the General Tab Page, select it.\n• Select Allow the connection under Action in the General Tab Page.\nMethod 2: Selecting the Use Option for the CIP Message Server\n1\nConnect the Sysmac Studio to the Controller.\nA-40 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n2\nSelect Configurations and Setup - Controller Setup - Built-in EtherNet/IP Port Settings -\nCIP Settings.\n3\nChange the setting to select the Use Option for CIP Message Server.\nMethod 3: Configuring Packet Filter Settings to Allow Packets Used\nby Sysmac Studio's EtherNet/IP Connection Settings\n1\nConnect the Sysmac Studio to the Controllers.\n2\nSelect Configurations and Setup - Controller Setup - Built-in EtherNet/IP Port Settings -\nTCP/IP Settings.\n3\nEnter the settings for Packet Filter to allow packets used by Sysmac Studio's EtherNet/IP con-\nnection settings. Refer to Packet Filter on page 4-8 for detailed settings.\nMethod 4: Cycling the Power Supply to the Controller\nCycle the power supply to the NJ/NX-series Controller and transfer/monitor the EtherNet/IP connec-\ntions settings again.\nNoteYou may need to cycle the power supply when reflecting the changes in the IP address of the built-in Ether-\nNet/IP port or executing Transfer to the Controller.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-41\nA-2\nUse\nthe\nSysmac\nStudio\nto\nSet\nthe\nTag\nData\nLinks\n(EtherNet/IP\nConnections)\nA\nA-2-6\nTroubleshooting\nAppendices\nA-3 EDS File Management\nThis section describes the EDS file management on the Network Configurator.\nPrecautions for Correct Use\nOn Windows Vista or Windows 7:\nWe recommend that you select Run as administrator to start the Network Configurator for op-\nerations with EDS files.\nIf you do not select Run as administrator, the following condition will result according to Win-\ndows user management for security purposes.\nThe following operations are not valid if you log in with another user account, and you need to\nrestart the Network Configurator again: Install, Create, Delete, and Create EDS Index File un-\nder EDS File.\nWhen you start the Network Configrator, select Run as administrator as below."}
+{"question": "Select Run as administrator from the displayed pop-up menu.", "answer": "A-3-1 Installing EDS Files\nEDS File - Install\nThe Network Configurator can support new devices if the proper EDS files are installed.\nTo install the EDS file, use the following procedure.\n1\nSelect EDS File - Install.\nThe Install EDS File Dialog Box is displayed.\nA-42 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n2\nSelect the EDS file to install, and click the Open Button.\nNext, select the icon file (*.ico). The EDS file is added to the Hardware List as a new device.\nIf the hardware already exists, the new Hardware List will overwrite the previous one.\nIf the hardware has different versions, each hardware version is added to the Hardware List.\nA-3-2 Creating EDS Files\nEDS File - Create\nThe EDS files are required for the Network Configurator to create a network configuration. To create\nan EDS file, use the following procedure.\n1\nSelect EDS File - Create.\n2\nSet the device information. You can obtain the device information from the device on the net-\nwork if it is online.\n3\nThe device is added to the Hardware List as a new device, just like when you install an EDS\nfile.\nAdditional Information\nYou cannot set device parameters when you create an EDS file with the Network Configurator.\nObtain a proper EDS file from the manufacturer of the device to make device parameter set-\ntings for the device.\nA-3-3 Deleting EDS Files\nEDS File - Delete\nTo delete an EDS file, use the following procedure.\n1\nSelect the device from the Hardware List.\n2\nSelect EDS File - Delete.\nThe following confirmation dialog box is displayed.\n3\nClick the Yes Button.\nThe selected device is deleted from the Hardware List together with the EDS file.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-43\nA-3\nEDS\nFile\nManagement\nA\nA-3-2\nCreating\nEDS\nFiles\nAppendices\nA-3-4 Saving EDS Files\nEDS File - Save\nTo save the EDS file, use the following procedure.\n1\nSelect the target hardware device in the Hardware List, and then select EDS File - Save.\n2\nA Save EDS File Dialog Box is displayed.\n3\nInput the folder and file names and click the Save Button.\nThe EDS file is saved.\nA-3-5 Searching EDS Files\nEDS File - Find\nTo search the devices in the Hardware List for EDS files, use the following procedure.\n1\nSelect EDS File - Find.\nThe following dialog box is displayed.\n2\nInput the character string to search for, and click the Find Next Button.\n3\nIf a matching device is found, the cursor moves to the position of the device.\n4\nTo quit the search operation, click the Cancel Button.\nAdditional Information\n• The search is performed for the device on which the cursor stays and subsequent ones in the\nHardware List.\n• To search all the devices, select Hardware in the Hardware List before you perform the\nsearch.\nA-44 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-3-6 Displaying EDS File Properties\nEDS File - Property\nTo display the properties of the EDS file, use the following procedure.\n1\nSelect the desired hardware (device) from the Hardware List.\n2\nSelect EDS File - Property.\nThe following dialog box is displayed.\nThe time and date when the EDS file was created is displayed, along with the device informa-\ntion.\nA-3-7 Creating EDS Index Files\nEDS File - Create EDS Index File\nWhen an EDS file is manually added or when a device is not correctly indicated in the Hardware List,\nuse the following procedure to recreate the EDS index file.\n(This applies to Network Configurator version 3.30 or higher.)\n1\nSelect EDS File - Create EDS Index File.\n2\nRestart the Network Configurator.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-45\nA-3\nEDS\nFile\nManagement\nA\nA-3-6\nDisplaying\nEDS\nFile\nProperties\nAppendices\nA-4 Precautions for Using the Network\nConfigurator on Windows XP, Win-\ndows Vista, or Windows 7 or Higher\nBetter firewall security for Windows XP (SP2 or higher), Windows Vista, and Windows 7 or higher has\nincreased the restrictions for data communications. Before connecting the Network Configurator and\nan NJ/NX-series CPU Unit and starting communications through the following procedures, you may\nneed to change the settings of the Windows firewall as described in this section.\n• If you select Option - Select Interface - Ethernet I/F.\n• If you select Option - Select Interface - NJ/NX Series Ethernet Direct I/F.\n• If you select Option - Select Interface - NJ/NX Series USB Port.\nPrecautions for Correct Use\nThe main function of the firewall is to prevent illegal access from external sources (e.g., the In-\nternet). The purpose of changing the firewall settings through this procedure is to connect the\nNetwork Configurator to an NJ/NX-series CPU Unit. If your computer is connected to an in-\nhouse network, make such changes only after confirming that they have no security impact on\nthe network.\nA-4-1 Changing Windows Firewall Settings\nWindows XP\n1\nWhen you attempt to connect to the NJ/NX-series CPU Unit from the Network Configurator, the\nWindows Security Alert Dialog Box is displayed.\n2\nClick the Unblock Button.\nThis allows USB connection and EtherNet/IP connection to the Network Configurator, and you\nwill be able to connect to the NJ/NX-series CPU Unit via the Network Configurator.\nWindows Vista or Windows 7 or Higher\nUse the following procedure to change the settings.\nAlways perform steps 1 to 6 if you cannot go online. The User Account Control Dialog Box may be\ndisplayed during this procedure. If it appears, click the Continue Button and continue with the proce-\ndure.\n1\nSelect Control Panel from the Windows Start Menu, and select Classic View to change the\nview.\nA-46 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n2\nOpen Administrative Tools, and select Windows Firewall with Advanced Security in the\ndisplayed dialog box.\n3\nSelect Inbound Rules under Windows Firewall with Advanced Security on Local\nComputer on the left side of the Windows Firewall with Advanced Security Dialog Box.\n4\nSelect New Rule under Inbound Rules in the Actions Area on the right side of the dialog box.\n5\nFollow the steps below to make the settings in the New Inbound Rule Wizard Dialog Box. Se-\nlect the specified option at each step, and click the Next Button to move to the next step.\nRule Type Select Custom.\nProgram Select All Programs.\nProtocol and support Select ICMPv4 as the protocol type.\nScope Select Any IP address for all.\nAction Select Allow the connection.\nProfile Select Domain, Private, and Public.\nName Enter an arbitrary name (e.g., Omron_EIP).\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-47\nHigher\nA-4\nPrecautions\nfor\nUsing\nthe\nNetwork\nConfigurator\non\nWindows\nXP,\nWindows\nVista,\nor\nWindows\n7\nor\nA\nA-4-1\nChanging\nWindows\nFirewall\nSettings\nAppendices\n6\nClick the Finish Button. The rule that you defined (i.e., Omron_EIP) is registered in the list of\nInbound Rules.\nClose the Windows Firewall with Advanced Security Dialog Box.\n7\nWhen you attempt to connect to the NJ/NX-series CPU Unit from the Network Configurator, the\nWindows Security Alert Dialog Box is displayed.\n8\nClick the Allow access Button.\n(On Windows 7) This allows USB connection and EtherNet/IP connection to the Network Con-\nfigurator, and you will be able to connect to the NJ/NX-series CPU Unit via the Network Config-\nurator.\nA-48 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-5 Variable Memory Allocation Methods\nYou must be aware of the way in which memory is allocated to variables to align the memory locations\nof the members of structure or union variables with variables in other devices. Adjustments are neces-\nsary mainly when structure or union variables are used in the following type of communications with\nother devices.\n• When using EtherNet/IP tag data links or CIP messages to access variables between NJ/NX-series\nCPU Units and other CPU Units\n• When using structure or union variables to exchange data with devices other than CPU Units, such\nas ID Tags\nA-5-1 Variable Memory Allocation Rules\nThe amount of memory and the memory locations that are allocated for a variable depend on the data\ntype of the variable. The amount of memory and the memory locations that are allocated for array ele-\nments, structure members, and union members depend on the data types, but also on the declara-\ntions that are made for the arrays, structures, and unions.\nData Type Alignment and Memory Allocation Amounts\nThe data size is determined for each data type. The data size is the minimum amount of memory that\nis required to store the value or values of that data type.\nOn the other hand, memory for variables is automatically structured by the Controller for the most effi-\ncient access. Therefore, the total amount of memory that is required for variables is not necessarily the\ntotal of the data sizes of the variables. For example, if WORD and DWORD variables are declared, the\ntotal of the data sizes is six bytes, but eight bytes are allocated in memory, as shown in the following\nfigure.\nMemory Variable Table\nBytes Name Data type\nVariable A First byte A WORD\nFirst byte + 1 WORD data: 2 bytes B DWORD\nFirst byte + 2\nFirst byte + 3 Not used: 2 bytes\nVariable B First byte + 4\nFirst byte + 5\nDWORD data: 4 bytes\nFirst byte + 6\nFirst byte + 7\nThis information for determining the location of a variable in memory is called the alignment. The align-\nment is determined for each data type. The amount of memory and the memory locations for the varia-\nbles are given below.\nItem Specification\nAmount of memory that is allo- An integral multiple of the alignment. However, the minimum amount\ncated of memory is the data size.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-49\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-1\nVariable\nMemory\nAllocation\nRules\nAppendices\nItem Specification\nLocations in memory At an integral multiple of the alignment starting from the start of the\nvariable in memory.\nThe alignments and the amounts of memory that are allocated for the basic data types and enumera-\ntions are given below.\nAmount of memory that is allo-\nData type Alignment [bytes]\ncated [bytes]\nBOOL 2 2\nBYTE, USINT, or SINT 1 1\nWORD, UINT, or INT 2 2\nDWORD, UDINT, or DINT 4 4\nLWORD, ULINT, or LINT 8 8\nREAL 4 4\nLREAL 8 8\nTIME, DATE, TIME_OF_DAY, or 8 8\nDATE_AND_TIME\nSTRING[N+1]*1 1 N+1\nEnumerations 4 4\n*1. N is the maximum number of characters handled. For example, if a maximum of 10 single-byte characters\nare handled, the NULL character is added, so memory for 11 characters must be reserved.\nThe elements of arrays and the members of structures and unions are located in memory for the most\nefficient access. The alignments and the amounts of memory that are allocated for arrays, structures,\nand unions are determined by the variable declarations, as described below.\nData type Alignment Amount of memory that is allocated\nArray Same as alignment of the data type of (Amount of memory that is allocated for the data type of\nthe elements the elements) × Number of elements*1\nStructure The largest alignment of all of the The integral multiple of the alignment that is larger than\nmembers the total amount of memory that is allocated when the\nmembers are arranged in order at integral multiples of\nthe alignment of the data types of the members\nUnion The largest alignment of all of the The largest amount of memory that is allocated for any\nmembers of the members\n*1. BOOL arrays are an exception. Refer to Precautions for Correct Use, below, for the amount of memory that\nis allocated for BOOL arrays.\nA-50 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nPrecautions for Correct Use\nAmount of Memory That Is Allocated for BOOL Arrays\nTwo bytes are allocated in memory for individual BOOL variables, BOOL structure members, and\nBOOL union variables.\nHowever, for a BOOL array, two bytes of memory are not allocated for each element. One bit is\nallocated in order for each element. For the entire array, a multiple of two bytes of memory is allo-\ncated (including unused bits).\nMemory Variable Table\nBytes Name Data type\nVariable A First byte A BOOL\nTwo bytes are allocated.\nFirst byte + 1 B ARRAY[1..5]OF BOOL\nVariable B First byte + 2 C ARRAY[0..18]OF BOOL\nTwo bytes are allocated\nFirst byte + 3\nfor 5 elements.\nVariable C First byte + 4\nFirst byte + 5\nFour bytes are allocated\nFirst byte + 6 for 19 elements.\nFirst byte + 7\nTherefore, the following formula gives the amount of memory that is allocated for a BOOL array.\nFor 1 to 16 elements, 2 bytes are allocated. For 17 to 32 elements, 4 bytes are allocated.\nNumber of\nelements − 1\nAmount of memory = 2 +2\n16\nTruncate the decimal portion of the result\nof the calculation in brackets.\nSpecific examples of the rules for memory allocation for variables of each data type are given below.\nBasic Data Types\n Variables with One-Byte Alignments (e.g., BYTE)\nOne byte of memory is allocated for the one-byte alignment.\nExample: Two consecutive BYTE variables\nMemory Variable Table\nBytes\nName Data type\nFirst byte Variable A, 1 byte A BYTE\nFirst byte + 1 Variable B, 1 byte B BYTE\n Variables with Two-byte Alignments (e.g., BOOL and WORD)\nTwo bytes of memory are allocated for the two-byte alignment.\nExample: Two consecutive BOOL variables\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-51\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-1\nVariable\nMemory\nAllocation\nRules\nAppendices\nFirst byte + Variable Table\nMemory\n(integer multiple of 2)\nName Data type\nBytes\nFirst byte + First byte A BOOL\n(integer multiple of 2) First byte + 1 Variable A, 2 bytes B BOOL\nFirst byte + 2\nVariable B, 2 bytes\nFirst byte + 3\n Variables with Four-byte Alignments (e.g., DWORD)\nFour bytes of memory are allocated for the four-byte alignment.\nThe location of the first byte of data in memory is an integer multiple of four bytes. Therefore, if a\nvariable with a two-byte alignment, such as WORD data, is inserted, two bytes of unused memory\nwill remain.\nExample: Consecutive variables in the following order: DWORD, WORD, and DWORD\nFirst byte + Variable Table\nMemory\n(integer multiple of 4) Name Data type\nBytes\nFirst byte A DWORD\nFirst byte + 1 Variable A, B WORD\nFirst byte + First byte + 2 4 bytes C DWORD\n(integer multiple of 2)\nFirst byte + 3\nFirst byte + 4 Variable B,\nFirst byte + 5 2 bytes\nFirst byte +\nFirst byte + 6\n(integer multiple of 4) Not used.\nFirst byte + 7\nFirst byte + 8\nFirst byte + 9 Variable C,\nFirst byte + 10 4 bytes\nFirst byte + 11\n Variables with Eight-byte Alignments (e.g., LWORD)\nEight bytes of memory are allocated for the eight-byte alignment.\nThe location of the first byte of data in memory is an integer multiple of eight bytes. Therefore, if a\nvariable with a two-byte alignment, such as WORD data, is inserted, six bytes of unused memory\nwill remain. If a variable with a four-byte alignment, such as DWORD data, is inserted, four bytes of\nunused memory will remain.\nExample: Consecutive variables in the following order: LWORD, WORD, and LWORD\nA-52 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nFirst byte + Variable Table\n(integer multiple of 8) Memory\nName Data type\nBytes\nFirst byte A LWORD\nFirst byte + 1 B WORD\nFirst byte + 2 C LWORD\nVariable A,\nFirst byte + 3\n8 bytes\nFirst byte + 4\nFirst byte + 5\nFirst byte +\n(integer multiple of 2) First byte + 6\nFirst byte + 7\nFirst byte + 8\nVariable B,\nFirst byte + 9\n2 bytes\nFirst byte + 10\nFirst byte + 11\nFirst byte + 12\nNot used.\nFirst byte + 13\nFirst byte +\nFirst byte + 14\n(integer multiple of 8)\nFirst byte + 15\nFirst byte + 16\nFirst byte + 17\nFirst byte + 18\nVariable C,\nFirst byte + 19\n8 bytes\nFirst byte + 20\nFirst byte + 21\nFirst byte + 22\nFirst byte + 23\nArrays\nA continuous section of memory is allocated for the elements of the array based on the data size of\nthe data type of the array variable. The alignment of an array is the same as alignment of the data\ntype of the elements.\nExample: Continuous variables in the following order: two BOOL variable, one BOOL array with five\nelements, one BOOL array with 19 elements, and one BOOL array with four elements\nFirst byte + Variable Table\nMemory\n(integer multiple of 2) Name Data type\nBytes\nFirst byte + First byte Variable A, A BOOL\n(integer multiple of 2)\nFirst byte + 1 2 bytes B BOOL\nFirst byte + First byte + 2 Variable B, C ARRAY[1..5]OF BOOL\n(integer multiple of 2)\nFirst byte + 3 2 bytes D ARRAY[0..18]OF BOOL\nF (inir ts et gb ey rt e m + u ltiple of 2) First byte + 4 Variable C, E ARRAY[5..8]OF BOOL\nFirst byte + 5 2 bytes\nFirst byte + 6\nFirst byte + 7 Variable D,\nFirst byte +\nFirst byte + 8 4 bytes\n(integer multiple of 2)\nFirst byte + 9\nFirst byte + 10 Variable E,\nFirst byte + 11 2 bytes\nExample: INT array with five elements\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-53\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-1\nVariable\nMemory\nAllocation\nRules\nAppendices\nFirst byte + Memory Variable Table\n(integer multiple of 2) Bytes Name Data type\nFirst byte + A[0] First byte\nVariable A ARRAY[0..4] OF INT\n(integer multiple of 2)\nFirst byte + 1\nFirst byte + A[1] First byte + 2\n(integer multiple of 2) First byte + 3 Variable A,\nFirst byte + A[2] First byte + 4 10 bytes\n(integer multiple of 2)\nFirst byte + 5\nFirst byte + A[3] First byte + 6\n(integer multiple of 2) First byte + 7\nA[4] First byte + 8\nFirst byte + 9\nExample: BYTE array with four elements for each dimension with two-dimensional array\nMemory Variable Table\nBytes Name Data type\nA[0, 0] First byte\nVariable A ARRAY[0..3, 0..3] OF BYTE\nA[0, 1] First byte + 1\nA[0, 2] First byte + 2\nA[0, 3] First byte + 3\nA[1, 0] First byte + 4\nA[1, 1] First byte + 5\nA[1, 2] First byte + 6\nA[1, 3] First byte + 7\nA[2, 0] First byte + 8\nA[2, 1] First byte + 9\nA[2, 2] First byte + 10\nA[2, 3] First byte + 11\nA[3, 0] First byte + 12\nA[3, 1] First byte + 13\nA[3, 2] First byte + 14\nA[3, 3] First byte + 15\nExample: WORD array with three elements for each dimension with two-dimensional array\nFirst byte + Memory Variable Table\n(integer multiple of 2) Bytes\nName Data type\nFirst byte + B[0, 0] First byte Variable B ARRAY[0..2, 0..2] OF WORD\n(integer multiple of 2) First byte + 1\nFirst byte + B[0, 1] First byte + 2\n(integer multiple of 2) First byte + 3\nFirst byte + B[0, 2] First byte + 4\n(integer multiple of 2) First byte + 5\nFirst byte + B[1, 0] First byte + 6\n(integer multiple of 2) First byte + 7\nFirst byte + B[1, 1] First byte + 8\n(integer multiple of 2) First byte + 9\nFirst byte + B[1, 2]First byte + 10\n(integer multiple of 2) First byte + 11\nFirst byte + B[2, 0]First byte + 12\n(integer multiple of 2)\nFirst byte + 13\nFirst byte + B[2, 1]First byte + 14\n(integer multiple of 2)\nFirst byte + 15\nB[2, 2]First byte + 16\nFirst byte + 17\nA-54 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nStructures\nFor a structure variable, the members are located in memory in the order that they are declared. Each\nmember is located at an integer multiple of the alignment of the data type of the member. Therefore,\nthere can be unused memory between members or at the end of members. The alignment of a struc-\nture is the largest alignment of all of the members. The amount of memory that is allocated is the inte-\ngral multiple of the alignment that is larger than the total amount of memory that is allocated when the\nmembers are arranged in order at integral multiples of the alignment of the data types of the members.\nExample: The alignments and the amounts of memory that are allocated for the four variable declara-\ntions given in the following figure are given in the following table.\nAmount of memory that is allocated\nVariable Alignment [bytes]\n[bytes]\nA 4 8\nB 4 8\nC 4 16\nD 4 16\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-55\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-1\nVariable\nMemory\nAllocation\nRules\nAppendices\nFirst byte + Data Type Definitions\nMemory\n(integer multiple of 4) Name Data type\nBytes\nStructure STR_A STRUCT\nA.a First byte\na DINT\nFirst byte + 1\nb INT\nFirst byte + 2\nFirst byte + 3 Variable A, Name Data type\nA.b First byte + 4 8 bytes Structure STR_B STRUCT\nFirst byte + 5 c INT\nFirst byte +\nFirst byte + 6 d DINT\n(integer multiple of 4) Not used.\nFirst byte + 7\nVariable Table\nB.c First byte + 8\nName Data type\nFirst byte + 9\nVariable A Structure STR_A\nFirst byte + 10 Variable B,\nNot used. Variable B Structure STR_B\nFirst byte + 11 8 bytes\nVariable C ARRAY[0..1] OF STR_A\nB.d First byte + 12\nVariable D ARRAY[0..1] OF STR_B\nFirst byte + 13\nFirst byte +\n(integer multiple of 4)First byte + 14\nFirst byte + 15\nC[0].a First byte + 16\nFirst byte + 17\nFirst byte + 18\nFirst byte + 19\nC[0].b First byte + 20\nFirst byte + 21\nFirst byte + 22 Variable C,\nNot used.\nFirst byte + 23 16 bytes\nC[1].a First byte + 24\nFirst byte + 25\nFirst byte + 26\nFirst byte + 27\nC[1].b First byte + 28\nFirst byte + 29\nFirst byte +\nFirst byte + 30\n(integer multiple of 4) Not used.\nFirst byte + 31\nD[0].c First byte + 32\nFirst byte + 33\nFirst byte + 34\nNot used.\nFirst byte + 35\nD[0].d First byte + 36\nFirst byte + 37\nFirst byte + 38 Variable D,\nFirst byte + 39 16 bytes\nD[1].c First byte + 40\nFirst byte + 41\nFirst byte + 42\nNot used.\nFirst byte + 43\nD[1].d First byte + 44\nFirst byte + 45\nFirst byte + 46\nFirst byte + 47\nExample: The alignments and the amounts of memory that are allocated for the four variable declara-\ntions given in the following figure are given in the following table.\nAmount of memory that is allocated\nVariable Alignment [bytes]\n[bytes]\nE 2 4\nF 2 4\nA-56 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nAmount of memory that is allocated\nVariable Alignment [bytes]\n[bytes]\nG 2 8\nH 2 8\nData Type Definitions\nMemory\nFirst byte +\nBytes Name Data type\n(integer multiple of 2)\nE.a[0] to E.a[7] First byte Structure STR_C STRUCT\nFirst byte + 1 NNoott uusseedd.. Variable E, a ARRAY[0..7] OF BOOL\nE.b First byte + 2 4 bytes b BYTE\nFirst byte +\nFirst byte + 3 Not used.\n(integer multiple of 2) Name Data type\nF.c First byte + 4 Structure STR_D STRUCT\nFirst byte + 5 Not used. Variable F, c BYTE\nFirst byte + F.d[0] to F.d[7] First byte + 6 4 bytes d ARRAY[0..7] OF BOOL\nFirst byte + 7 Not used.\n(integer multiple of 2)\nVariable Table\nG[0].a[0] to G[0].a[7] First byte + 8\nName Data type\nFirst byte + 9 Not used.\nVariable E Structure STR_C\nG[0].b First byte + 10\nVariable F Structure STR_D\nFirst byte + 11 Not used. Variable G,\nVariable G ARRAY[0..1] OF STR_C\nG[1].a[0] to G[1].a[7] First byte + 12 8 bytes\nVariable H ARRAY[0..1] OF STR_D First byte + 13 Not used.\nG[1].b First byte + 14\nFirst byte +\nFirst byte + 15 Not used.\n(integer multiple of 2)\nH[0].c First byte + 16\nFirst byte + 17 Not used.\nH[0].d[0] to H[0].d[7] First byte + 18\nFirst byte + 19 Not used. Variable H,\nH[1].c First byte + 20 8 bytes\nFirst byte + 21 Not used.\nH[1].d[0] to H[1].d[7] First byte + 22\nFirst byte + 23 Not used.\nUnions\nFor a union variable, the members overlap in the same memory locations.\nThe alignment of a union is largest alignment of all of the members. The amount of memory that is\nallocated is the largest amount of memory that is allocated for any of the members.\nExample: The alignments and the amounts of memory that are allocated for the four variable declara-\ntions given in the following figure are given in the following table.\nAmount of memory that is allocated\nVariable Alignment [bytes]\n[bytes]\nA 4 4\nB 4 4\nC 4 8\nD 4 8\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-57\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-1\nVariable\nMemory\nAllocation\nRules\nAppendices\nFirst byte + Data Type Definitions\nMemory\n(integer multiple of 4)\nName Data type\nBytes\nA.a A.b First byte Union UNI_A UNION\nFirst byte + 1 a DWORD\nFirst byte + First byte + 2 Variable A, b WORD\n(integer multiple of 4) 4 bytes\nFirst byte + 3 Name Data type\nB.c B.d First byte + 4 Union UNI_B UNION\nFirst byte + First byte + 5 Variable B, c WORD\n(integer multiple of 4) First byte + 6 4 bytes d DWORD\nFirst byte + 7\nVariable Table\nC[0].a C[0].b First byte + 8\nName Data type\nFirst byte + 9\nVariable A Union UNI_A\nFirst byte + 10\nVariable C, Variable B Union UNI_B\nFirst byte + 11\n8 bytes Variable C ARRAY[0..1] OF UNI_A\nC[1].a C[1].b First byte + 12\nVariable D ARRAY[0..1] OF UNI_B\nFirst byte + 13\nFirst byte +\nFirst byte + 14\n(integer multiple of 4)\nFirst byte + 15\nD[0].c D[0].d First byte + 16\nFirst byte + 17\nFirst byte + 18\nVariable D,\nFirst byte + 19\n8 bytes\nD[1].c D[1].d First byte + 20\nFirst byte + 21\nFirst byte + 22\nFirst byte + 23\nA-5-2 Important Case Examples\nWhen you exchange structure variable data between an NJ/NX-series CPU Unit and a remote device,\nyou must align the memory configuration of the structure variable members with those of the remote\ndevice.\nThis section describes what to do in either the NJ/NX-series CPU Unit or in the remote device.\nAdditional Information\nThis is not necessary when you exchange data between NJ/NX-series CPU Units.\nAligning the Memory Configuration with a Remote Device\nThere are two methods that you can use to align the memory configuration with a remote device.\nFor example, the differences in the memory configuration for structure variables between an NJ/NX-\nseries CPU Unit and a CJ-series CPU Unit are shown below.\nThis section describes how to align the memory configuration for these Units.\nA-58 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nData Type Definitions Data Type Definitions\nName Data type NJ/NX-series Structure Variable NJ_X Name Data type CJ-series Structure Variable CJ_X\nStructure Y STRUCT Bytes Structure Y STRUCT Bytes\na DINT First byte a a DINT First byte a\nb INT b INT\nc DINT First byte + 4 b c DINT First byte + 4 b\nVariable Table First byte + 6 Not used. Variable Table First byte + 6 c\nName Data type First byte + 8 c Name Data type\nVariable NJ_X Structure Y Variable CJ_X Structure Y\n Method 1: Changing the Memory Configuration of the Structure Variable in\nthe NJ/NX-series CPU Unit\nWith an NJ/NX-series CPU Unit, you can specify member offsets to change the memory configura-\ntion of the members of a structure variable. You can change the memory configuration of the mem-\nbers of a structure variable in the NJ/NX-series CPU Unit so that it is the same as the memory con-\nfiguration in a remote device that the CPU Unit will communicate with.\nSpecify the member offsets for a structure variable when you register the structure data type.\nTo communicate with a CJ-series CPU Unit, you can set the offset type to CJ to automatically use\nthe CJ-series memory configuration.\nYou can set the offset type to User to freely set your own offsets.\nVersion Information\nThe following table gives the unit version of the CPU Units and the Sysmac Studio version that\nare required to specify member offsets.\nSysmac Studio version\nUnit version of CPU Unit\nVer.1.01 or lower Ver.1.02 Ver.1.03 or higher\nVer.1.01 or later Not possible. Possible.*1 Possible.\nVer.1.00 Not possible. Not possible. Not possible.\n*1. You cannot select the memory offset type. You can set member offsets.\nIf you change the memory configuration of a structure variable by setting offsets, you must make\nthe same changes for the same structure variable in other NJ/NX-series CPU Units on the network.\nRefer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for the procedure to\nchange the memory configuration of a structure variable.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-59\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-2\nImportant\nCase\nExamples\nAppendices\nExample: The following example shows how the memory configuration of the structure variable in\nthe NJ/NX-series CPU Unit is changed to match the memory configuration of the structure variable\nin the CJ-series CPU Unit.\nData Type Definitions NJ/NX-series Structure Data Type Definitions CJ-series Structure\nName Data type Variable NJ_X Name Data type Variable CJ_X\nStructure Y STRUCT Bytes Structure Y STRUCT Bytes\na DINT First byte a a DINT First byte a\nb INT b INT\nc DINT First byte + 4 b c DINT First byte + 4 b\nCommunications is\nVariable Table First byte + 6 Not used. not possible Variable Table First byte + 6 c\nName Data type First byte + 8 c because the memory Name Data type\nVariable NJ_X Structure Y configuration is not Variable CJ_X Structure Y\nthe same.\nTo align the memory configurations in the NJ-series and CJ-series CPU Units, offsets are set in the Sysmac Studio.\nHere, the following offsets are set for member c of data type Y of the structure variable NJ_X.\n(1) Offset type is set to CJ.\n(3) Bit Offset\nSet the location of the first bit of the member variable.\n(2) Byte Offset\nSet the location of the first byte of the member from\nthe beginning of the structure variable.\n(1) Offset Type\nSpecify User.\nMemory Bytes Memory Bytes\nFirst byte First byte\n(2) Byte Offset\nFirst byte + 1 First byte + 1 Variable c starts from the 6th\nFirst byte + 2 Variable a First byte + 2 Variable a byte from the start of the\nstructure.\nFirst byte + 3 First byte + 3\nFirst byte + 4 First byte + 4\nVariable b Variable b\nFirst byte + 5 First byte + 5\nFirst byte + 6 First byte + 6\nNot used.\nFirst byte + 7 First byte + 7\nVariable c\nFirst byte + 8 The location of First byte + 8\nvariable c changes\nFirst byte + 9 First byte + 9\nVariable c according to the\nFirst byte + 10 offsets. First byte + 10\nFirst byte + 11 First byte + 11\n(3) Bit Offset\nSet a byte offset of 6 and a bit offset Variable c starts from the 0th\nof 0 (no offset) for variable c. bit from the start of the byte.\nA-60 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n Method 2: Changing the Memory Configuration of the Structure Variable in\nthe Remote Device\nYou can insert a member into the structure variable of the remote device to change it to match the\nmemory configuration of the structure variable in the NJ/NX-series CPU Unit.\nBoth the memory configuration and the data types must be the same between the two structure\nvariables. You therefore need to create the same members in both the remote device and the\nNJ/NX-series CPU Unit.\nExample: The following example shows how the memory configuration of the structure variable in\nthe CJ-series CPU Unit is changed to match the memory configuration of the structure variable in\nthe NJ/NX-series CPU Unit.\nData Type Definitions Data Type Definitions\nNJ/NX-series Structure Variable NJ_X CJ-series Structure Variable CJ_X\nName Data type Name Data type\nStructure Y STRUCT Bytes Structure Y STRUCT Bytes\na DINT First byte a a DINT First byte a\nb INT b INT\nc DINT First byte + 4 b c DINT First byte + 4 b\nVariable Table First byte + 6 Not used. Variable Table First byte + 6 c\nName Data type First byte + 8 Name Data type\nVariable NJ_X Structure Y c Variable CJ_X Structure Y\nMake the following changes to align the memory\nconfigurations in the NJ/NX-series and CJ-series CPU Units.\nData Type Definitions Data Type Definitions\nName Data type NJ/NX-series Structure Variable NJ_X Name Data type CJ-series Structure Variable CJ_X\nStructure Y STRUCT Bytes Structure Y STRUCT Bytes\na DINT First byte a a DINT First byte a\nb INT b INT\nb2 INT First byte + 4 b b2 INT First byte + 4 b\nc DINT First byte + 6 b2 c DINT First byte + 6 b2\nVariable Table First byte + 8 c Variable Table First byte + 8 c\nName Data type Name Data type\nVariable NJ_X Structure Y Variable CJ_X Structure Y\n(2) Add the dummy variable b2 that you created in the (1) Add a dummy member variable b2 that matches the\nCJ-series CPU Unit to the NJ/NX-series CPU Unit as well. unused memory location on the NJ/NX-series CPU Unit.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-61\nA-5\nVariable\nMemory\nAllocation\nMethods\nA\nA-5-2\nImportant\nCase\nExamples\nAppendices\nA-6 Precautions When Accessing Exter-\nnal Outputs in CPU Units\nObserve the following precautions when you access variables or I/O memory addresses that are as-\nsigned to external outputs in an NJ/NX-series CPU Unit.\n Precaution on Writing from External Devices, Variables That Are Assigned\nto External Outputs\nAny value that is written to a variable that is assigned to an external output in an NJ/NX-series CPU\nUnit through a tag data link or communications instruction will be overwritten by the execution re-\nsults of the user program.\nThe value that is written from the tag data link or communications instruction will therefore not be\noutput to the external device.\nThe following types of variable are assigned to the external outputs.\nCPU Unit Common\n• The device variables (or global variables) that are assigned to an I/O port of an EtherCAT output\nslave\nNJ-series CPU Unit\n• The devices variables (or global variables) that are assigned to an I/O port of a CJ-series Basic\nOutput Unit\n• The global variables with AT specifications to output bits that are assigned to CJ-series Basic\nOutput Units\nNX502 CPU Unit, NX102 CPU Unit, and NX1P2 CPU Unit\n• The global variables with AT specifications to the memory used for CJ-series Units, of which Net-\nwork Publish attributes are set to output\n Precaution When Directly Writing to I/O Memory Addresses Assigned to\nOutput Bits for CJ-series Basic Output Units\nAny value that is written to an I/O memory address that corresponds to an output bit that is as-\nsigned to a CJ-series Basic Output Unit through a tag data link will be overwritten by the execution\nresults of the user program.\nThe value that is written directly to the I/O memory address from the tag data link will therefore not\nbe output to the external device.\nA-62 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-7 TCP State Transitions\nThere are 11 types of TCP connection state.\nYou can check the TCP state with the TCP connection status that is output by the SktGetTCPStatus\n(Read TCP Socket Status) instruction.\nThe table below shows the TCP states and what each state means.\nTCP state Definition\nCLOSED The connection is closed.\nLISTEN The server is waiting for a connection request (SYN) with a passive open.\nSYN SENT The client sent a connection request (SYN) for an active open and is waiting for acknowl-\nedgment (SYN + ACK).\nSYN RECEIVED The server sent an acknowledgment (SYN + ACK) to a connection request (SYN) and is\nwaiting for acknowledgment (ACK).\nESTABLISHED A connection is established.\nCLOSE WAIT The server sent acknowledgment (ACK) to a connection close request (FIN) and is wait-\ning for the server application to be ready to close.\nFIN WAIT-1 The client sent a connection close request (FIN) and is waiting for acknowledgment\n(ACK).\nCLOSING The client and server simultaneously received a connection close request (FIN) and are\nwaiting for acknowledgment (ACK).\nLAST-ACK The server sent a connection close request (FIN) and is waiting for acknowledgment\n(ACK).\nFIN WAIT-2 The client is waiting for a connection close request (FIN).\nTIME WAIT The client received acknowledgment (ACK) to a connection close request (FIN) and is\nwaiting for it to be received and processed by the server.\nThe TCP state changes as requests and acknowledgments are received from the remote node, and\nas TCP socket connection and close instructions are executed in the user program.\nWhen the state changes, a connection request (SYN), close request (FIN), and acknowledgment\n(ACK) to those requests are sent to and received from the remote node.\nThe following figure shows TCP state transitions.\nThe TCP states are given in £ in the figure. Between states, the text in the upper row indicates the\ncondition for the state change, and the text in the lower row indicates the action that is performed at\nthe state change. (If no action is performed, none is given.)\nExample: When SYN and ACK are received in SYN SENT state, ACK is sent and the state changes to\nESTABLISHED.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-63\nA-7\nTCP\nState\nTransitions\nA\nAppendices\nCLOSED\nActive OPEN\nSYN sent.\nPassive OPEN CLOSE\nCLOSE\nLISTEN\nSYN received. SEND\nSYN + ACK sent. SYN sent.\nSYN SYN received. SYN\nRECIEVED ACK sent.\nSENT\nACK for SYN received. SYN + ACK received.\nACK sent.\nCLOSE\nFIN sent.\nESTABLISHED\nCLOSE FIN received.\nFIN sent. ACK sent.\nFIN WAIT-1 CLOSE WAIT\nFIN received.\nACK for FIN received. CLOSE\nACK sent.\nFIN sent.\nFIN WAIT-2 CLOSING LAST-ACK\nFIN received. ACK for FIN received. ACK for FIN received.\nACK sent.\nTimeout=2MSL\nTIME WAIT CLOSED\nA-64 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-8 Example of NX Unit Setting Using NX\nConfiguration Object Service\nYou can change the settings for the NX Unit mounted to the CPU Rack by using the NX Configuration\nobject service.\nThis section provides examples of the procedure for NX Unit setting using the NX Configuration object\nservice.\nRefer to 7-5-3 NX Configuration Object (Class ID: 74 hex) on page 7-53 for details on the NX Configu-\nration object.\nThe following three types of procedure are given as the examples.\n• Changing the Unit operation settings for a singe NX Unit.\n• Changing the Unit operation settings for multiple NX Units.\n• Initializing the Unit operation settings for a singe NX Unit.\nPrecautions for Correct Use\nRefer to 15-2 Checking Status with the Network Configurator on page 15-3 for troubleshooting\nerrors that may occur while setting NX Units using the NX Configuration object service.\nVersion Information\nYou can perform the NX Unit setting using the NX Configuration object service only with NX502\nCPU Units and NX102 CPU Units.\nA-8-1 Changing the Unit Operation Settings for Singe NX Unit\nChange the Unit operation settings for a single NX Unit mounted to the Controller. In this example, the\nunit number of the NX Unit is 1.\nThe following table gives the setting procedure.\nCIP Object to use\nStep Description Unit\nClass ID Instance ID Service code\nnumber\n1 Change the parameter write 0x74 0x01 0x37 0x01\nmode of the NX Unit to Write NX Configuration Switch parameter\nmode. object write mode\n2 Write values to the NX object 0x74 0x01 0x34 0x01\nof the NX Unit. NX Configuration Write NX object\nobject\n3 Save the values that are set in 0x74 0x01 0x36 0x01\nthe NX Unit. NX Configuration Save parameter\nobject\n4 Restart the NX Unit. 0x74 0x01 0x35 0x01\nNX Configuration Restart NX unit\nobject\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-65\nA-8\nExample\nof\nNX\nUnit\nSetting\nUsing\nNX\nConfiguration\nObject\nService\nA\nA-8-1\nChanging\nthe\nUnit\nOperation\nSettings\nfor\nSinge\nNX\nUnit\nAppendices\nA-8-2 Changing the Unit Operation Settings for Multiple NX Units\nChange the Unit operation settings for multiple NX Units mounted to the Controller. In this example,\nthe unit numbers of the NX Units are 1 and 2.\nThe following table gives the setting procedure.\nCIP Object to use\nStep Description Unit\nClass ID Instance ID Service code\nnumber\n1 Change the parameter write 0x74 0x01 0x37 0x01\nmode of the NX Unit with unit NX Configuration Switch parameter\nnumber 1 to Write mode. object write mode\n2 Change the parameter write 0x74 0x01 0x37 0x02\nmode of the NX Unit with unit NX Configuration Switch parameter\nnumber 2 to Write mode. object write mode\n3 Write values to the NX object 0x74 0x01 0x34 0x01\nof the NX Unit with unit num- NX Configuration Write NX object\nber 1. object\n4 Write values to the NX object 0x74 0x01 0x34 0x02\nof the NX Unit with unit num- NX Configuration Write NX object\nber 2. object\n5 Save the values that are set in 0x74 0x01 0x36 0x01\nthe NX Unit with unit number NX Configuration Save parameter"}
+{"question": "object", "answer": "6 Save the values that are set in 0x74 0x01 0x36 0x02\nthe NX Unit with unit number NX Configuration Save parameter"}
+{"question": "object", "answer": "7 Restart the NX Unit with unit 0x74 0x01 0x35 0x01\nnumber 1. NX Configuration Restart NX unit\nobject\n8 Restart the NX Unit with unit 0x74 0x01 0x35 0x02\nnumber 2. NX Configuration Restart NX unit\nobject\nA-8-3 Initializing the Unit Operation Settings for Singe NX Unit\nInitialize the Unit operation settings for a single NX Unit mounted to the Controller. In this example, the\nunit number of the NX Unit is 1.\nThe following table gives the setting procedure.\nCIP Object to use\nStep Description Unit\nClass ID Instance ID Service code\nnumber\n1 Change the parameter write 0x74 0x01 0x37 0x01\nmode of the NX Unit to Write NX Configuration Switch parameter\nmode. object write mode\n2 Initialize the Unit operation 0x74 0x01 0x3D 0x01\nsettings for the NX Unit with NX Configuration Initialize unit opera-\nunit number 1. object tion parameter\n3 Restart the NX Unit with unit 0x74 0x01 0x35 0x01\nnumber 1. NX Configuration Restart NX unit\nobject\nA-66 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-9 Tag Data Link Settings with Generic\nDevices\nUse the Generic Device if you want to perform tag data links with a device that does not have an EDS\nfile.\nCreate a Generic Device with the Network Configurator to use a Generic Device.\nThe procedures to create a Generic Device and the procedures to create a tag or tag set are shown\nbelow.\nAdditional Information\nThe procedures after creating a tag or tag set are the same as for devices that have EDS files.\nRefer to 6-2 Setting Tag Data Links on page 6-21.\nA-9-1 Creating Generic Devices\n1\nSelect Create Generic Device from the EDS File Menu.\nThe Create Generic device EDS Dialog Box is displayed.\n2\nSet the information for the device and click the Create Button.\nA confirmation dialog to install an icon is displayed.\n3\nSet a device icon.\n• If you click the Yes Button:\nThe Install Icon (EDS file name) Dialog Box is displayed.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-67\nA-9\nTag\nData\nLink\nSettings\nwith\nGeneric\nDevices\nA\nA-9-1\nCreating\nGeneric\nDevices\nAppendices\n• If you click the No Button:\nA default icon for the Network Configurator is set.\n4\nSelect the icon file (*.ico) to set as the EDS file and click the Open Button.\nThe created Generic Device is added to the hardware list.\nA-9-2 Creating a Tag or Tag Set for Generic Device\nThis section describes two types of methods for creating a tag or tag set: tag type and instance ID\ntype. Each procedure is described below.\nThe type is what you select in Connection I/O Type when you create a Generic Device.\nCreation Procedure for Tag Type\n1\nAdd the Generic Device that you created to the network window.\n2\nDouble-click the device icon.\nThe Edit Device Parameters Dialog Box is displayed.\nA-68 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n3\nSelect the slot number 00 in the Configuration from the Module Tab Page and then click the\nEdit Button.\nThe Edit Module Parameters Dialog Box is displayed.\n4\nSelect Input Only (Tag type) or Input & Output (Tag type) from Type and click the New But-\nton.\nThe Edit Variable Dialog Box is displayed.\n5\nSet the following parameters for the variable.\n• Name\nEnter the name of the network variable. (Example: VarInputOnly)\n• Size\nEnter the size of the tag in bytes.\n• I/O Type\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-69\nA-9\nTag\nData\nLink\nSettings\nwith\nGeneric\nDevices\nA\nA-9-2\nCreating\na\nTag\nor\nTag\nSet\nfor\nGeneric\nDevice\nAppendices\nIf Type is Input & Output (Tag type), select Out or In.\n6\nClick the OK Button.\nThe Edit Module Parameters Dialog Box is displayed, and the added variable is displayed.\n7\nRepeat steps 4 through 6 to register the required variables. Click the OK Button when the reg-\nistration is complete.\nCreation Procedure for Instance ID Type\n1\nAdd the Generic Device that you created to the network window.\n2\nDouble-click the device icon.\nThe Edit Device Parameters Dialog Box is displayed.\n3\nClick the New Button from the I/O Configuration Tab Page.\nThe Edit I/O Instance Dialog Box is displayed.\nA-70 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n4\nEnter the following parameters.\n• Instance No.\nEnter the instance ID for the I/O instance.\n• Size\nEnter the size of the tag in bytes.\n• I/O Type\nSelect Out or In.\n5\nClick the OK Button.\nThe Edit Device Parameters Dialog Box is displayed, and the added I/O instance is displayed\nin the I/O Configuration Tab Page.\n6\nRepeat steps 3 through 5 to register the required I/O instances. Click the OK Button when the\nregistration is complete.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-71\nA-9\nTag\nData\nLink\nSettings\nwith\nGeneric\nDevices\nA\nA-9-2\nCreating\na\nTag\nor\nTag\nSet\nfor\nGeneric\nDevice\nAppendices\nA-10 Procedure to Use Secure Socket\nService with Secure Socket Configu-\nration Commands\nThis section describes the procedure to use secure socket services for the following use cases.\n• Starting to use secure socket services\nRefer to A-10-1 Settings for Starting Secure Socket Services on page A-72.\n• Replacing CPU Units\nRefer to A-10-2 Procedure for Replacing the CPU Unit on page A-74.\nA-10-1 Settings for Starting Secure Socket Services\nThe following two procedures describe how to set up a new configuration.\n• If you do not use a client certificate and a client private key\n• If you use a client certificate and a client private key\nFor details on Secure Socket Configuration commands that are used in the procedures, refer to\nA-11 Secure Socket Configuration Commands on page A-79.\nIf you do not use a client certificate and a client private key\nThe setting procedure to start secure socket services when the client certificate and client private key\nare not used is as follows.\nAs a prerequisite, set the built-in EtherNet/IP of the CPU Unit as follows.\n• If the server is on the Internet, configure the default gateway and routing table.\nIf the server is specified by an item other than the IP address, such as \"xxx.com\", configure the DNS\nserver settings.\n• Configure NTP settings.\nThe NTP settings are optional. It is recommended for matching with the server time.\nCheck with the network administrator of the installation site for the settings of the default gateway,\nrouting table, DNS server, and NTP server.\nThe options for Secure Socket Configuration commands in this procedure are described in the follow-\ning example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected through\nEthernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP Port 1 of the CPU Unit is set to 192.168.250.1.\n• Set the session ID to 0 in the secure socket setting.\n1\nConfigure the server and check the server's IP address, HOST name, and other settings.\nCheck with the server installer for details on how to check.\n2\nConfigure the secure socket setting.\nUse the Secure Socket Configuration commands to configure secure socket setting for the ses-\nsion ID. Set different session IDs for all connected destinations.\nA-72 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\ntlsconfig setSessionInfo /id 0 /ip:192.168.250.1\nTo enable secure socket communications log, execute the following command.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\n3\nCreate a user program.\nCreate a session for secure socket communications with SktTCPConnect instruction to the\nserver in step 1. Set the TLS session name for the session ID to TLSSessionName, which is\nthe input variable of SktTLSConnect instruction. If \"N\" is 0, TLS session name is TLSSession0.\nUse SktTLSRead and SktTLSWrite instructions to process data communication with the server.\n4\nDownload the user program using the synchronization function.\nDownload the user program from the computer to the CPU Unit.\nAfter sufficiently confirming that the connection destination is correct, start operation.\nIf you use a client certificate and a client private key\nThe setting procedure to start secure socket services when the client certificate and client private key\nare used is as follows.\nAs a prerequisite, set the built-in EtherNet/IP of the CPU Unit as follows.\n• If the server is on the Internet, configure the default gateway and routing table.\nIf the server is specified by an item other than the IP address, such as \"xxx.com\", configure the DNS\nserver settings.\n• Configure NTP settings.\nThe NTP settings are optional. It is recommended for matching with the server time.\nCheck with the network administrator of the installation site for the settings of the default gateway,\nrouting table, DNS server, and NTP server.\nThe options for Secure Socket Configuration commands in this procedure are described in the follow-\ning example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected through\nEthernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP Port of the CPU Unit is set to 192.168.250.1.\n• The session ID set in the secure socket setting is 0.\n1\nPrepare the client private key, client certificate, and CA certificate.\nIn this procedure, the path and filename of the prepared client certificate is “C:\\dir1\\dir2\\0\\cli-\nent.cert”. The path and filename of the client private key is “C:\\dir1\\dir2\\0\\client.key”.\nNote that the prepared client certificate and client private key must be stored and managed by\nthe customer.\n2\nInstall the client certificate and CA certificate on the server.\nCheck with the server administrator for details such as whether installation on the server is re-\nquired.\n3\nConfigure the server and check the server's IP address, HOST name, and other settings.\nCheck with the server installer for details on how to check.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-73\nA-10\nProcedure\nto\nUse\nSecure\nSocket\nService\nwith\nSecure\nSocket\nConfiguration\nCommands\nA\nA-10-1\nSettings\nfor\nStarting\nSecure\nSocket\nServices\nAppendices\n4\nConfigure the secure socket setting.\nUse the Secure Socket Configuration commands to configure session information for the ses-\nsion ID.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\nTo enable secure socket communications log, execute the following command.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\n5\nCreate a user program.\nCreate a session for secure socket communications with SktTCPConnect instruction to the\nserver confirmed in step 3. Set the TLS session name for the session ID to TLSSessionName,\nwhich is the input variable of SktTLSConnect instruction. If \"N\" is 0, TLS session name is\nTLSSession0.\nUse SktTLSRead and SktTLSWrite instructions to process data communication with the server.\n6\nDownload the user program using the synchronization function.\nDownload the user program from the computer to the CPU Unit.\nAfter sufficiently confirming that the connection destination is correct, start operation.\nA-10-2 Procedure for Replacing the CPU Unit\nThis section describes the following three procedures for replacing the CPU Unit.\n• If you do not use a client certificate and a client private key\n• If you have stored the client certificate and client private key\n• If you have not stored the client certificate and client private key\nWhen you replace the CPU Unit, be sure to perform the following steps before proceeding to the re-\nplacement procedure.\nFor more information about Secure Socket Configuration commands, refer to A-11 Secure Socket\nConfiguration Commands on page A-79.\nThe options for Secure Socket Configuration commands in this procedure are described in the follow-\ning example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected through\nEthernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP Port of the CPU Unit is set to 192.168.250.1.\n• The session ID set in the secure socket setting is 2.\n1\nBack up the data in the Controller.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on\nController backups.\n2\nRead the secure socket setting.\nUse the Secure Socket Configuration commands to save the secure socket setting to\n<PC_Folder>.\ntlsconfig getAllSessionInfo /f /o <PC_Folder> /ip:192.168.250.1\nRead and confirm the enable/disable status of the secure socket communications log.\nA-74 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\ntlsconfig getLogLevel /ip:192.168.250.1\n3\nCheck that the client certificate and client private key are stored.\nCheck the read secure socket seting to ensure that the required client private key is stored.\nIf you do not use a client certificate and a client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key are not\nused is as follows.\nThe options for the Secure Socket Configuration commands in the replacement procedure are descri-\nbed in the following example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected through\nEthernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP Port of the CPU Unit is set to 192.168.250.1.\n• The session ID in the secure socket setting before replacement is set to 2.\n1\nReplace to a new CPU Unit.\n2\nCheck the secure socket setting.\nConfirm the session ID that is being used by the secure socket setting before replacing the\nCPU Unit. Read the session ID with Secure Socket Configuration commands.\n3\nConfigure the secure socket setting.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\nTo enable secure socket communications log, execute the following command.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\n4\nCheck the secure socket setting.\nUse the Secure Socket Configuration commands to view the secure socket setting and verify\nthat it matches the session ID set in the <PC Folder> read in step 2 of A-10-2 Procedure for\nReplacing the CPU Unit on page A-74. In this procedure, the /o option is not used.\ntlsconfig getLogLevel /ip:192.168.250.1\nRead and confirm the enable/disable status of the secure socket communications log.\ntlsconfig getLogLevel /ip:192.168.250.1\n5\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\n6\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-75\nA-10\nProcedure\nto\nUse\nSecure\nSocket\nService\nwith\nSecure\nSocket\nConfiguration\nCommands\nA\nA-10-2\nProcedure\nfor\nReplacing\nthe\nCPU\nUnit\nAppendices\nIf you have stored the client certificate and client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key have been\nstored is as follows.\nThe options for the Secure Socket Configuration commands in the replacement procedure are descri-\nbed in the following example.\n• To connect the computer to the CPU Unit, an EtherNet/IP port is used. They are connected through\nEthernet connection via a Hub or remote connection via USB.\n• The IP address of the built-in EtherNet/IP Port of the CPU Unit is set to 192.168.250.1.\n• The session ID in the secure socket setting before replacement is set to 2.\n• The file name and path in the computer that stores the client certificate file used in the secure socket\nsetting of session ID=2 is \"C:\\dir1\\dir2\\2\\client.cert\".\n• The path and file name of the client private key file stored on the computer used in the secure client\nsetting of session ID=2 is “C:\\dir1\\dir2\\2\\client.key”.\n1\nReplace to a new CPU Unit.\n2\nCheck the secure socket setting.\nConfirm the session ID that is being used by the secure socket setting before replacing the\nCPU Unit. Read the session ID with Secure Socket Configuration commands.\nPrepare the client certificate and client private key for each session ID that are stored in the\ncomputer.\n3\nConfigure the secure socket setting.\nUse the Secure Socket Configuration commands to configure session information for each ses-\nsion ID.\ntlsconfig setSessionInfo /id 2 /cert C:\\dir1\\dir2\\2\\client.cert /key C:\\dir1\n\\dir2\\2\\client.key /ip:192.168.250.1\nTo enable secure socket communications log, execute the following command.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\n4\nCheck the secure socket setting.\nUse the Secure Socket Configuration commands to view the secure socket setting and verify\nthat it matches the session ID set in the <PC Folder> read in step 2 of A-10-2 Procedure for\nReplacing the CPU Unit on page A-74. In this procedure, the /o option is not used.\ntlsconfig getLogLevel /ip:192.168.250.1\nRead and confirm the enable/disable status of the secure socket communications log.\ntlsconfig getLogLevel /ip:192.168.250.1\n5\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\nA-76 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n6\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\nIf you have not stored the client certificate and client private key\nThe procedure for replacing the CPU Unit when the client certificate and client private key have not\nbeen stored is as follows.\n1\nCreate a client certificate and client private key.\nDepending on whether you are creating a client certificate and client private key on the server\nor preparing the client private key and client certificate yourself, the procedures are different as\nfollows.\nCreating a client certificate and client private key on the server\n1) Create a client certificate and client private key on the server and download them to the\ncomputer.\nIn this procedure, the path and filename of the downloaded client certificate is\n“C:\\dir1\\dir2\\2\\client.cert”. The path and filename of the client private key is\n“C:\\dir1\\dir2\\2\\client.key”.\nNote that the prepared client certificate and client private key must be stored and managed\nby the customer.\nCreating a client certificate and client private key yourself\n1) Prepare the client certificate, client private key, and CA certificate.\nIn this procedure, the path and filename of the prepared client certificate is\n“C:\\dir1\\dir2\\2\\client.cert”. The path and filename of the client private key is\n“C:\\dir1\\dir2\\2\\client.key”.\nNote that you must store and manage the prepared client certificate, client private key, and\nCA certificate yourself.\n2) Install the client certificate and CA certificate on the server.\nCheck with the server administrator for details such as whether installation on the server is\nrequired.\n2\nCheck the secure socket setting.\nConfirm the session ID that is being used by the secure socket setting before replacing the\nCPU Unit. Read the session ID with Secure Socket Configuration commands.\nPrepare the client certificate and client private key for each session ID that are stored in the\ncomputer.\n3\nConfigure the secure socket setting.\nUse the Secure Socket Configuration commands to configure session information for each ses-\nsion ID.\ntlsconfig setSessionInfo /id 2 /cert C:\\dir1\\dir2\\2\\client.cert /key C:\\dir1\n\\dir2\\2\\client.key /ip:192.168.250.1\nTo enable secure socket communications log, execute the following command.\ntlsconfig setLogLevel /enable /ip:192.168.250.1\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-77\nA-10\nProcedure\nto\nUse\nSecure\nSocket\nService\nwith\nSecure\nSocket\nConfiguration\nCommands\nA\nA-10-2\nProcedure\nfor\nReplacing\nthe\nCPU\nUnit\nAppendices\n4\nRestore data to the Controller.\nRestore is performed using the backed up data.\nRefer to the NJ/NX-series CPU Unit Software User's Manual (Cat. No. W501) for details on re-\nstoration on the Controller.\n5\nCheck the operation.\nVerify that the program and settings are restored and the Controller is working correctly.\nA-78 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-11 Secure Socket Configuration Com-\nmands\nSecure Socket Configuration commands are command line tools.\nWhen a command is entered on the command line, the CPU Unit is temporarily connected online and\nthe secure socket setting in the CPU Unit is updated.\nPrecautions for Correct Use\nTo reduce the risk of unauthorized access by a third party using the Secure Socket Configura-\ntion commands, consider setting operation authority verification on the CPU Unit. You can re-\nstrict the use of Secure Socket Configuration commands to administrators only.\nUse of the Secure Socket Configuration commands is not subject to user authentication. Even if\nuser authentication is enabled in the CPU Unit of unit version 1.50 or later, please consider set-\nting operation authority verification.\nFor details on how to set operation authority verification, refer to Operation Authority Verification\non the .\nRefer to Operation Authority Verification on page A-81 for operating specifications of Secure\nSocket Configuration commands when operation authority verification is set.\nThe functions of the Secure Socket Configuration commands are described in the table below.\nFunction Description\nTLS session setting • You can register the TLS session information to the secure socket setting in\nthe CPU Unit. You can also read and delete the registered TLS session in-\nformation.\nSet one TLS session for one socket used in the secure socket communica-\ntions.\n• You can transfer the client certificate and client private key as required.\nSecure socket communica- You can set to enable or disable the secure socket communications log. You\ntions log setting can also read the set enable or disable status of secure socket communica-\ntions log.\nA-11-1 Operating Environment for Secure Socket Configuration Com-\nmands\nThe operating environment of the Secure Socket Configuration Commands on the computer is as fol-\nlows.\nItem System requirement\nCommunications port USB 2.0 port or Ethernet port\nThe operating environment other than above, such as the operating system, is the same as that for\nthe Sysmac Studio. Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for de-\ntails on the operating environment of the Sysmac Studio.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-79\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-1\nOperating\nEnvironment\nfor\nSecure\nSocket\nConfiguration\nCommands\nAppendices\nA-11-2 Location and Starting Procedure of Secure Socket Configuration\nCommands\nLocation\nThe Secure Socket Configuration Commands are stored in the following folder under the Sysmac Stu-\ndio installation folder.\n.\\TLSSettingTool\\tlsconfig.exe\nProcedure\nTo start the Secure Socket Configuration commands, proceed as follows.\n1\nFrom Windows Start menu, select OMRON – Sysmac Studio – Tools – Secure Socket\nConfiguration Command.\nThe command prompt starts in the folder where tlsconfig.exe is located.\n2\nFrom the command line, run tlsconfig.exe.\nA-11-3 Command and Option Formats\nThe table below describes the meaning of command and option symbols that are used in each com-\nmand.\nSymbol Meaning\n£ (square) Indicates single-byte space.\n| (stroke) Indicates separation between items for multiple items.\nE.g. \"A|B|C\" means that \"A, B, or C\".\n{} (wave brackets) An item must be selected out of ones within this symbol. Separation of items is in-\ndicated by \"|\".\nE.g. “{A|B|C}” indicates that \"one of the A, B, or C must be specified\".\n[] (square brackets) Item enclosed in this symbol can be omitted.\nE.g. \"[A]\" indicates that \"A is specified as needed\".\n... (dot line) More than one item of the previous one described before this symbol can be speci-\nfied.\nWhen more than one item is specified, a single-byte space is used to separate the\nitems.\nE.g. \"A B...\" indicates \"A can be followed by several B\".\nA-80 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nSymbol Meaning\n_ (underline) Indicates the default values when items are omitted.\nE.g.: “A|B” indicates that when neither A nor B was specified, A was specified.\nThe format of the command to be entered is as follows.\na. The order of the options is random.\nb. A single-byte space is entered as an separator of options.\nc. Case-sensitive for both commands and options.\nd. Specify an option with \"/\" (slash).\ne. An error occurs in the following cases:\n• You specified a command that does not exist.\n• You specified an option that does not exist.\n• You specified the same option.\n• The number of options does not match.\n• When there is an option to specify one from more than one, you specified more than one.\nA-11-4 Common Specifications to All Commands\nThe function, specification of connection method and execution result displays that are common to all\ncommands and options are described below.\n<TLSSettingTool Folder> in the execution example indicates the <Sysmac Studio Installed Folder>\n\\TLSSettingTool folder.\nOperation Authority Verification\nIf the CPU Unit was configured to be operated with different operation authorities, the user is prompted\nto enter the password before the command is executed.\nIf the password is correct, the command is executed. If the password is wrong, an error is displayed.\nThe following dialog to enter password is displayed.\nOperation authority: Administrator\nPassword:\nAn example is shown below.\n• When operation authority is set\n• If the password is correct\n<TLSSettingTool Folder>>tlsconfig setSessionInfo /id 1 /key C:\\private\\foo.private.key /cert\nC:\\certs\\foo.cert.pem /ip:192.168.250.1\nOperation authority: Administrator\nPassword:******\n000: Success\n<TLSSettingTool Folder>>\n• If the password is correct and the command execution result is displayed\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-81\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-4\nCommon\nSpecifications\nto\nAll\nCommands\nAppendices\n<TLSSettingTool Folder>>tlsconfig getSessionInfo /id 0 /ip:192.168.250.1\nOperation authority: Administrator\nPassword:******\nId=0\nPrivateKey=private.key\nCertificate=client.crt\nDescription=\n000: Success\n<TLSSettingTool Folder>>\n• If the password is incorrect\n<TLSSettingTool Folder>>tlsconfig setSessionInfo /id 1 /key C:\\private\\foo.private.key /cert\nC:\\certs\\foo.cert.pem /ip:192.168.250.1\nOperation authority: Administrator\nPassword:******\n13: Operation authority verification error\n<TLSSettingTool Folder>>\n• When operation authority is not set\n<TLSSettingTool Folder>>tlsconfig setSessionInfo /id 1 /key C:\\private\\foo.private.key /cert\nC:\\certs\\foo.cert.pem /ip:192.168.250.1\n000: Success\n<TLSSettingTool Folder>>\nSpecifying Connection Method\nYou can specify the method to connect to the CPU Unit with the command option.\nUse either one of the command options below to specify.\n• /usb\nSpecify this option for connecting to the USB port of the CPU Unit through direct connection via\nUSB.\nIf the CPU Unit does not support USB connection, an error occurs.\n• /ip:xxx.xxx.xxx.xxx\nThe xxx.xxx.xxx.xxx is the IP address of the connected CPU Unit.\nSpecify this option for connecting to an Ethernet port of the CPU Unit through Ethernet connection\nvia a hub or remote connection via USB.\nPrecautions for Correct Use\nDirect connection via Ethernet is not supported.\nExecution Result Displays\nThe execution results of the command are displayed as follows.\n• Normal operation\nCommands that have functions to show the execution results display the results.\n000: Success\n• Abnormal operation\nA-82 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nCommands display the error code and error message.\nThe error code display format is as follows.\n[error code]:[error message]\nThe [error code] is stored in the Windows environment variable ERRORLEVEL. ERRORLEVEL can\nbe checked with echo %ERRORLEVEL%.\nThe error codes and error messages are given in the following table.\nError code Error message Description\n1 Undefined command ; type \"tlsconfig help\" Command that does not exist\n2 Illegal argument Incorrect argument\n3 Communication error Communication error with CPU Unit\n4 Operating mode error Command not permitted in RUN mode\n5 Session setting already exists Session setting already exists.\n6 Session setting does not exist Session setting does not exist.\n7 Non-supported session ID Session ID is not supported by the connect-\ned CPU Unit.\n8 Invalid target file path/name The path/file name of the specified file is in-\nvalid.\n9 Target file not found The specified file does not exist.\n10 Output folder already exists The specified destination folder already ex-\nists.\n11 Can not create output file File output failed.\n12 Controller execution error Execution error of CPU Unit processing for\nthe command\n13 Operation authority verification error Operation authority verification error\n14 Too large file The specified file exceeded the maximum\nfile size\n15 Client certificate and key do not match or The client certificate and the private key do\nare broken not match, or one or both of them are cor-\nrupted.\nA-11-5 Command Specifications\nThe specifications of the Secure Socket Configuration commands are described below.\nCommand Function Reference\nsetSessionInfo Sets the TLS session information of the specified session ID and page A-84\nregisters it to the secure socket setting in the CPU Unit.\ndelSessionInfo Deletes the TLS session information of the specified session ID page A-86\nfrom the secure socket setting in the CPU Unit.\ndelAllSessionInfo Deletes the TLS session information of all session IDs from the page A-86\nsecure socket setting in the CPU Unit.\ngetSessionInfo Reads the TLS session information of the specified session ID page A-87\nfrom the CPU Unit and displays it.\nAlternatively, reads the TLS session information and client certifi-\ncate files from the CPU Unit and saves them in the computer.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-83\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\nCommand Function Reference\ngetAllSessionInfo Reads the TLS session information of all session IDs from the page A-89\nCPU Unit, and displays it in order from the smallest session ID\nnumber.\nAlternatively, reads the TLS session information and client certifi-\ncate files from the CPU Unit and saves them in the computer.\nsetLogLevel Enables or disables the secure socket communications log. page A-91\ngetLogLevel Reads the enable or disable state of the secure socket communi- page A-92\ncations log.\nclearAllSettings Initializes the secure socket setting. page A-92\nhelp Displays the version of the Secure Socket Configuration com- page A-93\nmands and how they are used.\nsetSessionInfo\n• Format\nsetSessionInfo£/id£n£[/key£xxxx£/cert□xxxx]£[/desc£xxxx]£[/f]£{/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can set TLS session information of the specified session ID to the secure socket setting in the\nCPU Unit.\nThe TLS session information includes the TLS session name, the file name of the client certificate,\nthe file name of the client private key, and a description of the session.\nThe TLS session name is automatically set with the session ID specified in the /id option. “TLSSes-\nsion” + ”session ID” is the session name. If 5 is specified for session ID, the TLS session name is\n“TLSSession5”.\nYou must set client private keys and client certificates only when a server performs client authentica-\ntion with the X.509 public key certificates.\nWhen the files of the client certificate and the client private key are specified in the /cert and /key\noptions, the files are transferred from the computer to the CPU Unit.\nYou can use the /f option to overwrite and update the client certificate and client private key for the\nsession ID that is already set in the TLS session information.\nAdditional Information\na) The TLS session name is used as the input variable of SktTLSConnect (Establish TLS Ses-\nsion) instruction.\nb) As an alternative method, you can also update the client certificate and client private key by\ndeleting the registered session with the delSessionInfo command and then setting the ses-\nsion again with the setSessionInfo command.\n• Restrictions\nThis command can be used only when the CPU Unit is in PROGRAM mode. An error occurs when it\nis used in RUN mode.\n• Option details\n• /id n\nn: Session ID\nThis option specifies the session ID in TLS session information to register.\nA-84 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nSpecify a value from 0 to 59 for an NX502 CPU Unit or an NX102 CPU Unit. For other models,\nspecify 0 to 29.\nIf the /f option is not specified and the specified session ID is already registered, an error occurs.\n• /key xxxx\nxxxx: Path to the client private key file and file name\nSpecify the path to the folder on the computer where the client private key file is located. The path\nalso has a file name.\nYou can specify either with a relative or an absolute path to the folder.\nIf you do not want to set the client private key in the TLS session information, specify \"none\" in the\npath or omit the option.\nThe TLS session information contains only the file name of the client private key and does not\ncontain any path information.\nAn error occurs in the following cases:\n• The client private key file does not exist at the specified location.\n• When the file size of the client private key exceeds 10KB\n• /cert xxxx\nxxxx: Path to the client certificate file and the file name\nSpecify the path to the folder on the computer where the client certificate file is located. The path\nalso has a file name.\nYou can specify either with a relative or an absolute path to the folder.\nIf you do not want to set the client certificate in the TLS session information, specify “none” in the\npath or omit the option.\nThe TLS session information contains only the file name of the client certificate and does not con-\ntain any path information.\nAn error occurs in the following cases:\n• The client certificate file does not exist at the specified location.\n• The size of client certificate file exceeds 10 KB.\n• /f\nEven when the client private key and client certificate are already set in the TLS session informa-\ntion of the session ID specified with the /id, they are overwritten with the client private key and\nclient certificate that are specified with the /key and /cert.\nIf both of the /key and /cert are not specified, the set client private key and client certificate are\ndeleted.\nIf the /desc is not specified, the comments set with the /desc will be cleared.\n• /desc\nDescription of the session\nYou can comment on TLS session information.\nThe following characters can be used in comments: 0-9, A-Z, a-z, - (hyphen), _ (underscore),\n( (parenthesis), and ) (closing parenthesis).\nThe maximum length is 32 characters.\n• Execution results\nNone\n• Execution examples\na) When session ID=1, and client certificate and client private key are not set in TLS session infor-\nmation\n<TLSSettingTool Folder>>tlsconfig setSessionInfo /id 1 /key none /cert none /ip:192.168.250.1\n<\\TLSSettingTool Folder>>\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-85\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\nb) When session ID=1, and client certificate = client.crt and client private key = private.key are set\nin the TLS session information\n<TLSSettingTool Folder>>tlsconfig setSessionInfo /id 1 /key C:\\privates\\private.key /cert C:\\certs\n\\client.crt /ip:192.168.250.1\n<TLSSettingTool Folder>>\ndelSessionInfo\n• Format\ndelSessionInfo□/id□n□{/usb|/ipxxx.xxx.xxx.xxx}\n• Functions\nYou can delete TLS session information of the specified session ID from the secure socket setting in\nthe CPU Unit.\n• Restrictions\nThis command can be used only when the CPU Unit is in PROGRAM mode. An error occurs when it\nis used in RUN mode.\n• Option details\n• /id n\nn: Session ID\nThis option specifies the session ID of TLS session to delete.\nSpecify a value from 0 to 59 for an NX502 CPU Unit or an NX102 CPU Unit. For other models,\nspecify 0 to 29.\nIf the specified session ID is not already registered in the secure socket setting, an error occurs.\n• Execution results\nNone\n• Execution examples\nWhen you want to delete TLS session information of session ID=1\n<TLSSettingTool Folder>>tlsconfig delSessionInfo /id 1 /ip:192.168.250.1\n<TLSSettingTool Folder>>\ndelAllSessionInfo\n• Format\ndelAllSessionInfo□{/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can delete TLS session information of all session IDs from the secure socket setting in the CPU\nUnit.\nThe secure socket communications log enable or disable setting will not be changed.\nWhen you execute the command, the warning message \"This command deletes all session settings\nof destination Controller. Confirm the settings to be deleted first, and enter \"Yes”.[Enter]\" is dis-\nplayed.\nIf you enter \"Yes\", all TLS session information is deleted and the message \"All settings are deleted.\"\nis displayed.\nIf an entry other than “Yes” is made, the message \"Operation is canceled.” is displayed and TLS\nsession information will not be deleted from the secure socket setting in the CPU Unit.\nYes is case sensitive. An entry of yes, YES, etc. will cause an error.\nA-86 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n• Restrictions\nThis command can be used only when the CPU Unit is in PROGRAM mode. An error occurs when it\nis used in RUN mode.\n• Option details\nNone\n• Execution results\nNone\n• Execution examples\nIn the examples below, what it displayed by the command is underlined.\na) When you delete all TLS session information from the secure socket setting of the CPU Unit (if\noperation authority is not set)\n<TLSSettingTool Folder>>tlsconfig delAllSessionInfo /ip:192.168.250.1\nThis command deletes all session settings of destination Controller.\nConfirm the settings to be deleted first, and enter \"Yes\".\n>Yes\nAll settings are deleted.\n000: Success\n<TLSSettingTool Folder>>\nb) When you cancel the command execution (if operation authority is not set)\n<TLSSettingTool Folder>>tlsconfig delAllSessionInfo /ip:192.168.250.1\nThis command deletes all session settings of destination Controller.\nConfirm the settings to be deleted first, and enter \"Yes\".\n>No\nOperation is canceled.\n000: Success\n<TLSSettingTool Folder>>\ngetSessionInfo\n• Format\ngetSessionInfo□/id□n□[/o□path_to_SessionInfo]□[/f]□ {/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can read TLS session information (TLS session name, client certificate file name, client private\nkey file name, and a description of the session) of the specified session ID from the CPU Unit and\ndisplay it.\nIf you specify the /o option, you can save the TLS session information and client certificate file in the\nspecified folder in the computer, instead of displaying them. However, the client private key files can-\nnot be saved.\nThe TLS session information is saved in “TLSSessionN.txt” text file (N is the specified session ID).\nThe client certificate file is saved with the file name specified when the TLS session information is\nset.\nThe files of TLS session information and client certificate are saved in the folder with the session ID\nname in the specified folder.\n• Restrictions\nNone\n• Option details\n• /id n\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-87\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\nn: Session ID\nSpecify the session ID of the TLS session information to be read.\nSpecify a value from 0 to 59 for an NX502 CPU Unit or an NX102 CPU Unit. For other models,\nspecify 0 to 29.\n• /o path_to_SessionInfo\npath_to_SessionInfo: Path to the folder to save the read TLS session information and client certifi-\ncate files\nIf this option is specified, TLS session information is not displayed.\nThe path of the folder can be either a relative path or an absolute path.\nCharacters and formats that can be used for the specified folder path conform to Windows specifi-\ncations.\n• The drive letter (\"D:\" or the like) can be used for the pathname.\n• You must specify the path to the storage in the computer. UNC (Universal Naming Convention)\ncannot be used.\nAn error occurs in the following cases:\n• The specified folder already has a folder with the same name as the session ID specified.\n• You do not have the access right to the specified folder.\nYou should be given the appropriate authority or an appropriate folder with the right to access\nshould be specified.\n• /f\nIf the folder specified with the /o option exists, files in the folder will be deleted, and then the files\nof TLS session information and client certificate will be saved.\nIf the /o option is not specified, specification for this option is ignored.\n• Execution results\nTLS session information of the specified session ID is output.\nIf the client private key and client certificate are not set, \"none\" is output.\n• Normal operation\nId = session ID\nPrivateKey=File name of the private key file\nCertificate=File name of the certificate file\nDescription= Description of the session\n(Blank line)\n• Abnormal operation\nThe following message is output.\n[error code]:[error message]\nThe [error code] is stored in the Windows environment variable ERRORLEVEL.\n• Execution examples\na) When you want to display TLS session information of session ID=0\n<TLSSettingTool Folder>>tlsconfig getSessionInfo /id 0 /ip:192.168.250.1\nId=0\nPrivateKey=private.key\nCertificate=client.crt\nDescription=\n000: Success\n<TLSSettingTool Folder>>\nA-88 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nb) When you want to save TLS session information of session ID=2 in C:\\Dir1\\Dir2 folder\n<TLSSettingTool Folder>>tlsconfig getSessionInfo /id 2 /o C:\\Dir1\\Dir2 /ip:192.168.250.1\n000: Success\n<TLSSettingTool Folder>>\nTLSSension2.txt and client.crt are saved in C:\\Dir1\\Dir2\\2 folder.\nThe contents of TLSSession2.txt are as follows.\nId=2\nPrivateKey=private.key\nCertificate=client.crt\nDescription=\ngetAllSessionInfo\n• Format\ngetAllSessionInfo□[/o□path_to_SessionInfo]□[/f]□ {/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can read TLS session information (TLS session name, client certificate file name, and client pri-\nvate key file name) of all session IDs from the CPU Unit and display it in order from the smallest\nsession ID number.\nIf session ID of 1, 3, 10 and 20 are registered in the TLS session information in the CPU Unit, the\nTLS session information is displayed in the order of 1, 3, 10 and 20.\nIf you specify the /o option, you can save the TLS session information and client certificate file in the\nspecified folder in the computer, instead of displaying them. However, the client private key files can-\nnot be saved.\nThe TLS session information is saved in “TLSSessionN.txt” text file (N is the specified session ID).\nThe client certificate file is saved with the file name specified when the TLS session information is\nset.\nThe files of TLS session information and client certificate are saved in the folder for each Session ID\nin the specified folder.\n• Restrictions\nNone\n• Option details\n• /o path_to_SessionInfo\npath_to_SessionInfo: Path to the folder to save the read TLS session information and client certifi-\ncate files\nTLS session information and client certificate files are stored in the folder with the folder name\nthat has the Session ID followed by the above path.\nIf this option is specified, TLS session information is not displayed.\nThe path of the folder can be either a relative path or an absolute path.\nCharacters and formats that can be used for the specified folder path conform to Windows specifi-\ncations.\n• The drive letter (\"D:\" or the like) can be used for the pathname.\n• You must specify the path to the storage in the computer. UNC (Universal Naming Convention)\ncannot be used.\nAn error occurs in the following cases:\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-89\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\n• The specified folder already has a folder with the same name as the session ID specified.\n• You do not have the access right to the specified folder.\nYou should be given the appropriate authority or an appropriate folder with the right to access\nshould be specified.\n• /f\nIf the folder specified with the /o option exists, files in the folder will be deleted, and then the files\nof TLS session information and client certificate will be saved.\n• Execution results\nIn normal operation, all of the registered TLS session information is output.\nCount=Serial number\nId = session ID\nPrivateKey=”File name of the private key file”\nCertificate=”File name of the certificate file”\nDescription=”Description of the session”\n(Blank line)\nCount=Serial number\nId = session ID\nPrivateKey=”File name of the private key file”\nCertificate=”File name of the certificate file”\nDescription=”Description of the session”\n(Blank line)\n:\n• Serial number\nOutputs the serial number of 1, 2, 3, and… in the order of the session to be output.\n• Session ID\nOutputs session ID (decimal).\n• File name of the private key file\nOutputs the file name set by the setSessionInfo command. The path is not included in file name.\nIf it is not set, “none” is output.\n• File name of the certificate file\nOutputs the file name set by the setSessionInfo command. The path is not included in file name.\nIf it is not set, “none” is output.\n• Execution examples\na) When you want to display TLS session information of all session IDs\nAn example when two sessions of session ID=0 and 1 are registered\n<TLSSettingTool Folder>>tlsconfig getAllSessionInfo /ip:192.168.250.1\nCount=1\nId=0\nPrivateKey=private0.key\nCertificate=client0.crt\nDescription=\nCount=2\nId=1\nPrivateKey=private1.key\nCertificate=client1.crt\nDescription=\n000: Success\n<TLSSettingTool Folder>>\nb) When you want to save TLS session information of all session IDs in C:\\Dir1\\Dir2 folder\nA-90 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\n<TLSSettingTool Folder>>tlsconfig getAllSessionInfo /o C:\\Dir1\\Dir2 /ip:192.168.250.1\n000: Success\n<TLSSettingTool Folder>>\nThe read TLS session information and client certificate files are saved in two separate folders:\nTLSSession0.txt and client0.crt are saved in C:\\Dir1\\Dir2\\0\\ folder and TLSSession1.txt and cli-\nent1.crt are saved in C:\\Dir1\\Dir2\\1\\ folder.\nThe image of the folder is as follows.\nC:\\Dir1\\Dir2\\\n0\\\nTLSSession0.txt\nclient0.crt\n1\\\nTLSSession1.txt\nclient1.crt\nThe contents of TLSSession0.txt are as follows.\nId=0\nPrivateKey=private0.key\nCertificate=client0.crt\nThe contents of TLSSession1.txt are as follows.\nId=1\nPrivateKey=private1.key\nCertificate=client1.crt\nsetLogLevel\n• Format\nsetLogLevel□{/enable|/disable}□{/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can set to enable or disable the secure socket communications log.\nEnable: Starts output of secure socket communications log.\nDisable: Stops output of secure socket communications log.\n• Restrictions\nThis command can be used only when the CPU Unit is in PROGRAM mode. An error occurs when it\nis used in RUN mode.\n• Option details\n/enable: Enables secure socket communications log\n/disable: Disables secure socket communications log\nSpecify either of enable or disable.\nSelecting neither or both of the two will result in an error.\n• Execution results\nNone\n• Execution examples\na) When you enable secure socket communications log\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-91\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\n<TLSSettingTool Folder>>tlsconfig setLogLevel /enable /ip:192.168.250.1\n000: Success\n<TLSSettingTool Folder>>\nb) When you disable secure socket communications log\n<TLSSettingTool Folder>>tlsconfig setLogLevel /disable /ip:192.168.250.1\n000: Success\n<TLSSettingTool Folder>>\ngetLogLevel\n• Format\ngetLogLevel□{/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can read the enable or disable status of secure socket communications log.\ndisable: Secure socket communications log is disabled\nenable: Secure socket communications log is enabled\n• Restrictions\nNone\n• Option details\nNone\n• Execution results\nNone\n• Execution examples\na) When the result of reading secure socket communications log status was enable\n<TLSSettingTool Folder>>tlsconfig getLogLevel /ip:192.168.250.1\nenable\n000: Success\nb) When the result of reading secure socket communications log status was disable\n<TLSSettingTool Folder>>tlsconfig getLogLevel /ip:192.168.250.1\ndisable\n000: Success\nclearAllSettings\n• Format\nclearAllSettings□{/usb|/ip:xxx.xxx.xxx.xxx}\n• Functions\nYou can initialize the secure socket setting.\n• This command clears all TLS session information.\n• This command disables secure socket communications log (stops output).\n• Restrictions\nThis command can be used only when the CPU Unit is in PROGRAM mode. An error occurs when it\nis used in RUN mode.\n• Option details\nNone\n• Execution results\nA-92 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nNone\n• Execution examples\nIn the examples below, what it displayed by the command is underlined.\na) To execute the command\n<TLSSettingTool Folder>>tlsconfig clearAllSettings /ip:192.168.250.1\nThis command clears all settings of destination Controller.\nConfirm the settings to be cleared first, and enter \"Yes\".\n>Yes\nAll settings are cleared.\n000: Success\n<TLSSettingTool Folder>>\nb) To cancel command execution\n<TLSSettingTool Folder>>tlsconfig clearAllSettings /ip:192.168.250.1\nThis command clears all settings of destination Controller.\nConfirm the settings to be cleared first, and enter \"Yes\".\n>No\nOperation is canceled.\n000: Success\n<TLSSettingTool Folder>>\nhelp\n• Format\nhelp\n• Functions\nYou can display the version information and how to use the commands.\n• Restrictions\nNone\n• Option details\nNone\n• Execution results\nNone\n• Execution examples\n<TLSSettingTool Folder>>tlsconfig help\nSecure Socket Configuration Tool\ntlsconfig.exe Version 1.00.00\nCopyright (c) OMRON Corporation 2021. All Rights Reserved.\nUsage: tlsconfig command [option1,option2....]\ncommand:\nsetSessionInfo /id n [/key KEY_FILE_NAME /cert CERT_FILE_NAME] /desc [DESCRIPTION] [/f]\n{/usb|/ip:IP_ADDRESS}\ndelSessionInfo /id n {/usb|/ip:IP_ADDRESS}\ndelAllSessionInfo {/usb|/ip:IP_ADDRESS}\ngetSessionInfo /id n [/o path_to_SessionInfo] [/f] {/usb|/ip:IP_ADDRESS}\ngetAllSessionInfo [/o path_to_SessionInfo] [/f] {/usb|/ip:IP_ADDRESS}\nsetLogLevel {/enable|/disable} {/usb|/ip:IP_ADDRESS}\ngetLogLevel {/usb|/ip:IP_ADDRESS}\nclearAllSettings {/usb|/ip:IP_ADDRESS}\nhelp\n<TLSSettingTool Folder>>\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-93\nA-11\nSecure\nSocket\nConfiguration\nCommands\nA\nA-11-5\nCommand\nSpecifications\nAppendices\nWhen Commands are Omitted\n• Format\nNone\n• Functions\nSame as the help command.\n• Restrictions\nNone\n• Option details\nNone\n• Execution results\nNone\n• Execution examples\nA-94 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nA-12 TCP/ UDP Port Numbers Used for the\nBuilt-in EtherNet/IP Port\nThe following table shows the applications that the built-in EtherNet/IP port of the NJ/NX-series CPU\nUnit uses TCP/UDP ports, port numbers, port types, protocols used, default port states, usages, and\nhow to change from open to close.\nTCP/UDP ports (servers) other than those shown below are not used.\nUDP TCP De-\nHow to change\nApplica- port port Port Protocol fault\nCPU Unit model Usage from open (de-\ntion num- num- type used port\nfault) to close\nber ber state\nFTP server All models --- 20 Sys- FTP Close Used when us- ---\ntem ing the FTP\nport server.\n--- 21 User Close ---\nport\nSSH/SFTP All models --- 22 Sys- SSH/SFTP Close For mainte- ---\ntem nance\nport\nDNS client All models 53 --- Sys- DNS Close Used when us- ---\ntem ing the DNS cli-\nport ent.\nBOOTP cli- All models 68 --- Sys- BOOTP Close Used when us- ---\nent tem ing the BOOTP\nport client.\nDHCP cli- All NX502 CPU Unit DHCP Used when us-\nent models ing the DHCP\nclient.\nHTTP serv- All models --- 80 Sys- HTTP Close Used for com- ---\ner tem munications\nport with the Sys-\nmac Studio.\nNTP client All models 123 --- User NTP Close Used when us- ---\nport ing the NTP cli-\nent.\nSNMP All models 161 --- User SNMP Close Used when us- ---\nport (SNMPv1, ing the SNMP\nSNMPv2C) agent.\nSNMP trap All models 162 --- User Close Used when us- ---\nport ing the SNMP\ntrap.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-95\nA-12\nTCP/\nUDP\nPort\nNumbers\nUsed\nfor\nthe\nBuilt-in\nEtherNet/IP\nPort\nA\nAppendices\nUDP TCP De-\nHow to change\nApplica- port port Port Protocol fault\nCPU Unit model Usage from open (de-\ntion num- num- type used port\nfault) to close\nber ber state\nHTTPS All models --- 443 Sys- HTTPS Open Used for com- Make one of the\nserver tem munications following set-\nport with the Sys- tings.\nmac Studio. • Use the\nPacket Filter.\n*1\n• Set the DIP\nswitch to\nenable\nconnections\nto the\nSysmac\nStudio and\nNA that are\nnot\nsupporting\nsecure\ncommunicati\non. *1*6\nEtherNet/IP All models 2222 --- Sys- CIP Open Used for the Set Built-in\ntag data tem EtherNet/IP tag EtherNet/IP\nlinks port data links. Port Settings -\nAll NJ-series models 2223 --- Sys- Open CIP Settings -\ntem CIP Message\nport Server to Do\nnot use on the\nSysmac Studio.\nA-96 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nUDP TCP De-\nHow to change\nApplica- port port Port Protocol fault\nCPU Unit model Usage from open (de-\ntion num- num- type used port\nfault) to close\nber ber state\nFINS/UDP • All NJ-series 9600 --- User FINS (OM- Open Used for the Set Built-in\nmodels port RON proto- FINS/UDP. EtherNet/IP\n• All NX1P2 CPU col) Port Settings -\nUnit models FINS Settings -\n• All NX102 CPU FINS/UDP to\nUnit models*2 Do not use on\nthe Sysmac\n• NX701-1£20*2\nStudio.\n• All NX502 CPU\nUnit models*2\nFINS/TCP • All NJ-series --- 9600 User Open Used for the Set Built-in\nmodels port FINS/TCP. EtherNet/IP\n• All NX102 CPU Port Settings -\nUnit models*2 FINS Settings -\nFINS/TCP to\n• NX701-1£20*2\nDo not use on\n• All NX502 CPU\nthe Sysmac\nUnit models*2\nStudio.\nSysmac All models 9600 --- Sys- Open Used for com- Use the Packet\nStudio tem munications Filter.*1\nport with the Sys-\nCPU Unit with a 2224 --- Sys- Close* mac Studio. ---\nUSB port tem\n4\n• All NJ-series port\nmodels\n• All NX701 CPU\nUnit models*3\nMainte- All models --- 9610 Sys- TCP (OM- Close For mainte- ---\nnance tem RON proto- nance\nport col)\nCIP mes- All models 44818 44818 Sys- CIP Open Used for the Set Built-in\nsages tem CIP messages. EtherNet/IP\nport Port Settings -\nCIP Settings -\nCIP Message\nServer to Do\nnot use on the\nSysmac Studio.\nOPC UA CPU Units that sup- --- 4840 User OPC UA Close Used when us- ---\nport OPC UA port ing the OPC\n• NJ501-1£00 UA.\n• All NX102 CPU\nUnit models*5\n• NX701-1£££*5\n• All NX502 CPU\nUnit models*5\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-97\nA-12\nTCP/\nUDP\nPort\nNumbers\nUsed\nfor\nthe\nBuilt-in\nEtherNet/IP\nPort\nA\nAppendices\nUDP TCP De-\nHow to change\nApplica- port port Port Protocol fault\nCPU Unit model Usage from open (de-\ntion num- num- type used port\nfault) to close\nber ber state\nTCP/UDP CPU Units that sup- 64000 64000 User TCP/UDP Close Used when us- ---\nmessage port TCP/UDP mes- port ing the\nservice sage service TCP/UDP mes-\n• All NX102 CPU sage service.\nUnit models\n• All NX502 CPU\nUnit models\nX Bus CPU Units that sup- 67 --- Sys- DHCP Close* Used for com- ---\nport X Bus Units tem munications\n7\n• All NX502 CPU port with the X Bus\nUnit models 520 --- Sys- RIP Close* Units.\ntem\n7\nport\n44819 --- Sys- CIP Close*\ntem\n7\nport\n--- 9910 Sys- TCP (OM- Close*\ntem RON proto-\n7\nport col)\nSECS/GE CPU Units that sup- --- 9700 Sys- TCP/UDP Open Used when us- Use the Packet\nM connec- port SECS/ GEM tem (OMRON ing the Filter.\ntion service • NJ501-1340 port protocol) SECS/GEM\n--- 5000 User SECS-II Close connection ---\nport service.\nDB con- CPU Units that sup- --- 9800 Sys- TCP (OM- *8 Used when us- Use the Packet\nnection port DB connection tem RON proto- ing the DB con- Filter.\nservice • NJ501-££20 port col) nection service.\n• NJ101-££20 --- 9801 Sys- Open\n• NX102-££20 tem\n• NX701-1£20 port\n• All NX502 CPU --- 9810 Sys- *8\nUnit models tem\nport\n--- 9811 Sys- Open\ntem\nport\nA-98 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nUDP TCP De-\nHow to change\nApplica- port port Port Protocol fault\nCPU Unit model Usage from open (de-\ntion num- num- type used port\nfault) to close\nber ber state\nRobot inte- CPU Units that sup- 1989 --- Sys- UDP (OM- Open Used for com- • Use the\ngrated port Robot Integrat- tem RON proto- munications Packet Filter.\ned Controller port col) with the ACE • To close the\n• NJ501-R£££ 1992 --- Sys- Open (including Appli- ports on the\ntem cation Manag- left at once,\nport er) or Sysmac remove the\nStudio. SD Memory\n1997 1997 Sys- TCP/UDP Open\nCard, exe-\ntem (OMRON\ncute clear all\nport protocol)\nmemory op- 65533 --- Sys- UDP (OM- Open\neration, then\ntem RON proto-\nrestart the\nport col)\nController.\n65534 --- Sys- Open\ntem\nport\n1990 --- Sys- Close\ntem\nport\n1993 --- Sys- Close\ntem\nport\n69 --- Sys- TFTP Close\ntem\nport\n--- 43234 Sys- TCP (OM- Close\ntem RON proto-\nport col)\n--- 48987 Sys- Close\ntem\nport\n*1. Closing the port may prevent communications with the Sysmac Studio. Refer to Troubleshooting When You Cannot Go\nOnline from the Sysmac Studio in the NJ/NX-series Troubleshooting Manual (Cat. No. W503) on how to make correc-\ntions.\n*2. This port number is supported only on Port 2. It cannot be used on Port 1.\n*3. Only if the CPU Unit with a USB port.\n*4. Always closed for the built-in EtherNet/IP port. Opened for the USB port only.\n*5. This port number is supported only on Port 1. It cannot be used on Port 2.\n*6. The NX502 CPU Units do not have this setting.\n*7. Always closed for the built-in EtherNet/IP port. Opened for the X Bus only.\n*8. Closed for the NX502 CPU Units. Opened for the CPU Units other than the NX502 CPU Units.\nPrecautions for Correct Use\nWhen using socket service instructions, specify the port number so that the port numbers used\ndo not overlap. If the port numbers used are duplicated, an error will occur during instruction\nexecution.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-99\nA-12\nTCP/\nUDP\nPort\nNumbers\nUsed\nfor\nthe\nBuilt-in\nEtherNet/IP\nPort\nA\nAppendices\nA-13 Version Information\nThis appendix shows the supported functions which have been changed or added through version up-\ngrades of the CPU Units.\n Additions and Changes to Functional Specifications\nThe following table lists additions and changes to the functional specifications, each with the corre-\nsponding CPU unit version and Sysmac Studio version.\nAddition/ Unit ver- Sysmac Studio\nFunction Reference\nChange sion version\nCIP routing Addition page 1-21 1.01 1.02\nPacket Filter (Simple) Addition page 4-10 1.30 1.23\nPacket Filter Addition/ page 4-8 *1 1.50\nChange\nSupport for mounting a CJ1W-EIP Ether- Addition page 1-6 1.01 1.02\nNet/IP Unit\nOffsets for struc- Optional Addition page A-58\nture members CJ Addition page A-58 1.02 1.03\nCIP objects Identity object Change page 7-49 1.01 ---\nNX Configuration ob- Addition page 7-53 1.30 ---\nject\nTCP/IP Interface ob- Change page 7-74 1.02 ---\nject\nTag data links Packet intervals (RPI) Change page 6-6 1.03 1.04\nPermissible communi- Change\ncations band\nCIP message com- CIPOpenWithData- Addition page 7-4 1.06 1.07\nmunications Size instruction\nClient function Addition*2 page 7-16 1.11 1.15\nSocket services Number of supported Change page 8-10 1.03 1.04\nsockets\nSktSetOption instruc- Addition page 8-13 1.12 1.16\ntion\nTCP/UDP message Addition page 8-33 1.30 1.23\nSecure socket serv- Addition page 8-36 *3 1.46\nices\nFTP client Addition page 11-1 1.08 1.09\nTroubleshooting Tag Data Link Con- Addition *4 1.04 1.05\nnection Timeout\nNumber of Tag Sets Addition *4 1.30 1.23\nfor Tag Data Links Ex-\nceeded\nConnection settings Addition page A-5 1.09 1.10\nTCP/IP settings Operation for an IP Addition page 4-2 *5\naddress conflict\nModbus TCP Master Function Addition page 9-1 1.30 1.23\nA-100 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nAppendices\nAddition/ Unit ver- Sysmac Studio\nFunction Reference\nChange sion version\nDHCP client Addition page 5-5 1.60 1.54\n*1. Refer to Packet Filter on page 4-8 for the CPU Unit models and unit versions that support the Packet\nFilter.\n*2. An extension structure is supported as the data type of variables to contain the request path (IOI).\n*3. Refer to 8-9 Secure Socket Services on page 8-36 for the CPU Unit models and unit versions that sup-\nport the secure socket services.\n*4. Refer to NJ/NX-series Troubleshooting Manual (Cat. No. W503).\n*5. This function can be used with the Sysmac Studio and CPU Units which support OPC UA. Refer to the\nNJ/NX-series CPU Unit OPC UA User’s Manual (Cat. No. W588) for information on the models and unit\nversions of the CPU Units that support OPC UA, and the corresponding Sysmac Studio versions.\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) A-101\nA-13\nVersion\nInformation\nA\nAppendices\nA-102 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nI\nIndex\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) I-1\nI\nIndex\nIndex\nNumerics _EIP1_DhcpErr (Port1 DHCP Server Error)...........3-14, 3-48\n_EIP1_EstbTargetSta (CIP Communications1 Normal Target\n_EIP_BootpErr (BOOTP Server Error)...................3-13, 3-47 Node Information)...............................................3-26, 3-58\n_EIP_CipErr (CIP Communications Error)...............3-7, 3-41 _EIP1_EtnCfgErr (Port1 Basic Ethernet Setting Error)...........\n_EIP_DhcpErr (DHCP Server Error)......................3-14, 3-48 ............................................................................3-11, 3-44\n_EIP_DNSCfgErr (DNS Setting Error)...................3-13, 3-47 _EIP1_EtnOnlineSta (Port1 Online).......................3-23, 3-55\n_EIP_DNSSrvErr (DNS Server Connection Error).3-20, 3-54 _EIP1_IdentityErr (CIP Communications1 Identity Error).......\n_EIP_ErrSta (EtherNet/IP Error)..............................3-3, 3-39 ............................................................................3-15, 3-49\n_EIP_EstbTargetSta (Normal Target Node Information)......... _EIP1_IPAdrCfgErr (Port1 IP Address Setting Error).............\n............................................................................3-26, 3-58 ............................................................................3-12, 3-45\n_EIP_EtnCfgErr (Basic Ethernet Setting Error)......3-11, 3-44 _EIP1_IPAdrDupErr (Port1 IP Address Duplication Error)......\n_EIP_EtnOnlineSta (Online)...................................3-23, 3-55 ............................................................................3-12, 3-46\n_EIP_IdentityErr (Identity Error).............................3-14, 3-49 _EIP1_LanHwErr (Port1 Communications Controller Error)...\n_EIP_IPAdrCfgErr (IP Address Setting Error).........3-11, 3-45 ............................................................................3-10, 3-44\n_EIP_IPAdrDupErr (IP Address Duplication Error).3-12, 3-46 _EIP1_MacAdrErr (Port1 MAC Address Error)......3-10, 3-43\n_EIP_IPRTblErr (IP Route Table Error)..................3-14, 3-48 _EIP1_MultiSwONErr (CIP Communications1 Multiple\n_EIP_LanHwErr (Communications Controller Error).............. Switches ON Error).............................................3-19, 3-54\n............................................................................3-10, 3-43 _EIP1_PortErr (Communications Port1 Error).........3-5, 3-40\n_EIP_MacAdrErr (MAC Address Error)....................3-9, 3-43 _EIP1_RegTargetSta (CIP Communications1 Registered\n_EIP_MultiSwONErr (Multiple Switches ON Error)3-19, 3-53 Target Node Information)....................................3-25, 3-57\n_EIP_NTPResult (NTP Operation Information)......3-33, 3-62 _EIP1_TagAdrErr (CIP Communications1 Tag Name Reso-\n_EIP_NTPResult.ExecNormal (NTP Operation Result)......... lution Error).........................................................3-18, 3-53\n............................................................................3-34, 3-63 _EIP1_TargetNodeErr (CIP Communications1 Target Node\n_EIP_NTPResult.ExecTime (NTP Last Operation Time)........ Error Information)................................................3-32, 3-62\n............................................................................3-34, 3-63 _EIP1_TargetPLCErr (CIP Communications1 Target PLC\n_EIP_NTPSrvErr (NTP Server Connection Error)..3-20, 3-54 Error Information)................................................3-29, 3-60\n_EIP_PortErr (Communications Port Error).............3-4, 3-40 _EIP1_TargetPLCModeSta (CIP Communications1 Target\n_EIP_RegTargetSta (Registered Target Node Information).... PLC Operating Mode).........................................3-28, 3-59\n............................................................................3-25, 3-57 _EIP1_TDLinkAllRunSta (CIP Communications1 All Tag Da-\n_EIP_TagAdrErr (Tag Name Resolution Error).......3-18, 3-52 ta Link Communications Status).........................3-24, 3-57\n_EIP_TargetNodeErr (Target Node Error Information)............ _EIP1_TDLinkCfgErr (CIP Communications1 Tag Data Link\n............................................................................3-31, 3-61 Setting Error)......................................................3-15, 3-50\n_EIP_TargetPLCErr (Target PLC Error Information)............... _EIP1_TDLinkErr (CIP Communications1 Tag Data Link\n...................................................................3-29, 3-60, 6-11 Communications Error).......................................3-17, 3-52\n_EIP_TargetPLCModeSta (Target PLC Operating Mode)...... _EIP1_TDLinkOpnErr (CIP Communications1 Tag Data Link\n...................................................................3-27, 3-59, 6-11 Connection Failed)..............................................3-16, 3-51\n_EIP_TcpAppCfgErr (TCP Application Setting Error)............. _EIP1_TDLinkRunSta (CIP Communications1 Tag Data Link\n............................................................................3-20, 3-54 Communications Status).....................................3-24, 3-56\n_EIP_TcpAppErr (TCP Application Communications Error)... _EIP1_TDLinkStartCmd (CIP Communications1 Tag Data\n..............................................................................3-9, 3-42 Link Communications Start Switch)...........3-36, 3-63, 6-73\n_EIP_TDLinkAllRunSta (All Tag Data Link Communications _EIP1_TDLinkStopCmd (CIP Communications1 Tag Data\nStatus)................................................................3-24, 3-56 Link Communications Stop Switch)...........3-37, 3-64, 6-73\n_EIP_TDLinkCfgErr (Tag Data Link Setting Error).3-15, 3-49 _EIP2_BootpErr (Port2 BOOTP Server Error).......3-13, 3-47\n_EIP_TDLinkErr (Tag Data Link Communications Error)........ _EIP2_CipErr (CIP Communications2 Error)...........3-9, 3-42\n............................................................................3-17, 3-51 _EIP2_DhcpErr (Port2 DHCP Server Error)...........3-14, 3-48\n_EIP_TDLinkOpnErr (Tag Data Link Connection Failed)........ _EIP2_EstbTargetSta (CIP Communications2 Normal Target\n............................................................................3-16, 3-50 Node Information)...............................................3-27, 3-59\n_EIP_TDLinkRunSta (Tag Data Link Communications Sta- _EIP2_EtnCfgErr (Port2 Basic Ethernet Setting Error)...........\ntus)......................................................................3-24, 3-56 ............................................................................3-11, 3-45\n_EIP_TDLinkStartCmd (Tag Data Link Communications _EIP2_EtnOnlineSta (Port2 Online).......................3-23, 3-55\nStart Switch)..............................................3-36, 3-63, 6-73 _EIP2_IdentityErr (CIP Communications2 Identity Error).......\n_EIP_TDLinkStopCmd (Tag Data Link Communications ............................................................................3-15, 3-49\nStop Switch)..............................................3-36, 3-64, 6-73 _EIP2_IPAdrCfgErr (Port2 IP Address Setting Error).............\n_EIP1_BootpErr (Port1 BOOTP Server Error).......3-13, 3-47 ............................................................................3-12, 3-46\n_EIP1_CipErr (CIP Communications1 Error)...........3-8, 3-42\nI-2 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nIndex\n_EIP2_IPAdrDupErr (Port2 IP Address Duplication Error)...... broadcasting......................................................................8-9\n............................................................................3-12, 3-46 built-in EtherNet/IP port specifications...............................1-9\n_EIP2_LanHwErr (Port2 Communications Controller Error)... bye.................................................................................10-16\n............................................................................3-10, 3-44\n_EIP2_MacAdrErr (Port2 MAC Address Error)......3-10, 3-43 C\n_EIP2_MultiSwONErr (CIP Communications2 Multiple\nSwitches ON Error).............................................3-20, 3-54 calculating the number of connections............................14-4\n_EIP2_PortErr (Communications Port2 Error).........3-6, 3-41 cd...................................................................................10-14\n_EIP2_RegTargetSta (CIP Communications2 Registered changing devices.............................................................6-81\nTarget Node Information)....................................3-26, 3-58 changing the RPI...........................................................14-11\n_EIP2_TagAdrErr (CIP Communications2 Tag Name Reso- changing Windows firewall settings................................A-46\nlution Error).........................................................3-19, 3-53 checking bandwidth usage for tag data links...................14-8\n_EIP2_TargetNodeErr (CIP Communications2 Target Node checking connections......................................................6-80\nError Information)................................................3-33, 3-62 checking the current IP address......................................5-11\n_EIP2_TargetPLCErr (CIP Communications2 Target PLC CIDR..................................................................................5-4\nError Information)................................................3-30, 3-61 CIP Communications.......................................................1-20\n_EIP2_TargetPLCModeSta (CIP Communications2 Target CIP Communications Error.......................................3-7, 3-41\nPLC Operating Mode).........................................3-28, 3-60 CIP communications instructions......................................7-4\n_EIP2_TDLinkAllRunSta (CIP Communications2 All Tag Da- CIP Communications1 All Tag Data Link Communications\nta Link Communications Status).........................3-25, 3-57 Status..................................................................3-24, 3-57\n_EIP2_TDLinkCfgErr (CIP Communications2 Tag Data Link CIP Communications1 Error.....................................3-8, 3-42\nSetting Error)......................................................3-15, 3-50 CIP Communications1 Identity Error......................3-15, 3-49\n_EIP2_TDLinkErr (CIP Communications2 Tag Data Link CIP Communications1 Multiple Switches ON Error................\nCommunications Error).......................................3-17, 3-52 ............................................................................3-19, 3-54\n_EIP2_TDLinkOpnErr (CIP Communications2 Tag Data Link CIP Communications1 Normal Target Node Information........\nConnection Failed)..............................................3-17, 3-51 ............................................................................3-26, 3-58\n_EIP2_TDLinkRunSta (CIP Communications2 Tag Data Link CIP Communications1 Registered Target Node Information..\nCommunications Status).....................................3-24, 3-56 ............................................................................3-25, 3-57\n_EIP2_TDLinkStartCmd (CIP Communications2 Tag Data CIP Communications1 Tag Data Link Communications Error\nLink Communications Start Switch)...........3-36, 3-64, 6-73 ............................................................................3-17, 3-52\n_EIP2_TDLinkStopCmd (CIP Communications2 Tag Data CIP Communications1 Tag Data Link Communications Start\nLink Communications Stop Switch)...........3-37, 3-64, 6-73 Switch........................................................3-36, 3-63, 6-73\nCIP Communications1 Tag Data Link Communications Sta-\nA tus.......................................................................3-24, 3-56\nCIP Communications1 Tag Data Link Communications Stop\naddress............................................................................4-17 Switch........................................................3-37, 3-64, 6-73\nadjusting device bandwidth usage.................................14-10 CIP Communications1 Tag Data Link Connection Failed.......\nadjusting packet interval (RPI) according to the task period... ............................................................................3-16, 3-51\n...................................................................................14-26 CIP Communications1 Tag Data Link Setting Error................\nadjusting the communications load.................................14-7 ............................................................................3-15, 3-50\nAll Tag Data Link Communications Status.............3-24, 3-56 CIP Communications1 Tag Name Resolution Error................\nappend...........................................................................10-14 ............................................................................3-18, 3-53\napplication example from a host computer....................10-20 CIP Communications1 Target Node Error Information...........\narray variables for inputting and outputting service data and ............................................................................3-32, 3-62\nresponse data..............................................................7-20 CIP Communications1 Target PLC Error Information.............\nAuto Connection Configuration........................................6-46 ............................................................................3-29, 3-60\nautomatic clock adjustment.............................................12-2 CIP Communications1 Target PLC Operating Mode..............\nprocedure.....................................................................12-4 ............................................................................3-28, 3-59\nrequired settings..........................................................12-4 CIP Communications2 All Tag Data Link Communications\nspecifications...............................................................12-2 Status..................................................................3-25, 3-57\nAutomatic Clock Adjustment............................................1-26 CIP Communications2 Error.....................................3-9, 3-42\nautomatically setting connections....................................6-45 CIP Communications2 Identity Error......................3-15, 3-49\nautomatically starting tag data links.................................6-72 CIP Communications2 Multiple Switches ON Error................\n............................................................................3-20, 3-54\nB CIP Communications2 Normal Target Node Information........\n............................................................................3-27, 3-59\nBasic Ethernet Setting Error...................................3-11, 3-44 CIP Communications2 Registered Target Node Information..\nbinary format..................................................................10-19 ............................................................................3-26, 3-58\nBOOTP client...................................................................1-24\nBOOTP Server Error..............................................3-13, 3-47\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) I-3\nI\nIndex\nCIP Communications2 Tag Data Link Communications Error default gateway.................................................................4-4\n............................................................................3-17, 3-52 delete.............................................................................10-16\nCIP Communications2 Tag Data Link Communications Start destination IP address.......................................................4-7\nSwitch........................................................3-36, 3-64, 6-73 destination mask IP address.............................................4-7\nCIP Communications2 Tag Data Link Communications Sta- detailed descriptions of MIB objects................................13-5\ntus.......................................................................3-24, 3-56 Device Connection Structure Tree...................................6-47\nCIP Communications2 Tag Data Link Communications Stop Device Monitor.................................................................15-3\nSwitch........................................................3-37, 3-64, 6-73 DHCP client.....................................................................1-25\nCIP Communications2 Tag Data Link Connection Failed....... DHCP Server Error.................................................3-14, 3-48\n............................................................................3-17, 3-51 dir...................................................................................10-13\nCIP Communications2 Tag Data Link Setting Error................ displaying device status...................................................6-83\n............................................................................3-15, 3-50 DNS...................................................................................4-5\nCIP Communications2 Tag Name Resolution Error................ DNS Server Connection Error................................3-20, 3-54\n............................................................................3-19, 3-53 DNS Setting Error...................................................3-13, 3-47\nCIP Communications2 Target Node Error Information........... domain names...................................................................4-6\n............................................................................3-33, 3-62\nCIP Communications2 Target PLC Error Information............. E\n............................................................................3-30, 3-61\nCIP Communications2 Target PLC Operating Mode.............. EDS file management.....................................................A-42\n............................................................................3-28, 3-60 effect of tag data link on task period..............................14-26\nCIP message communications service specifications.......7-3 Ethernet connectors........................................................2-13\nCIP message server........................................................4-21 Ethernet Information Tab Page......................................15-10\nCIP safety communications.............................................4-21 Ethernet Link Object........................................................7-77\nCIP Settings Display........................................................4-21 Ethernet switch..................................................................1-6\nCIPClose...........................................................................7-5 types..............................................................................2-3\nCIPOpen............................................................................7-5 Ethernet switches\nCIPOpenWithDataSize......................................................7-5 connection methods.....................................................2-11\nCIPRead............................................................................7-5 functions.........................................................................2-3\nCIPSend............................................................................7-5 installation precautions.................................................2-11\nCIPUCMMRead.................................................................7-4 selection precautions.....................................................2-4\nCIPUCMMSend.................................................................7-4 EtherNet/IP Error......................................................3-3, 3-39\nCIPUCMMWrite.................................................................7-4\nF\nCIPWrite............................................................................7-5\nclearing device parameters.............................................6-75\nFTP client........................................................................1-25\nclient function of CIP message communications ..............7-4\nFTP server..............................................................1-25, 4-14\nclose..............................................................................10-16\nFTP server application example......................................10-9\nCommunications Controller Error...........................3-10, 3-43\nFTP server application procedure...................................10-7\nCommunications Port Error......................................3-4, 3-40\nFTP server overview and specifications..........................10-2\nCommunications Port1 Error....................................3-5, 3-40\nFTP settings display........................................................4-14\nCommunications Port2 Error....................................3-6, 3-41\nfunction\ncommunity name....................................................4-18, 4-20\nfunctional comparison with other series........................A-3\nConnection I/O Type...............................................6-41, 6-43\nConnection Name...................................................6-42, 6-43\nG\nconnection settings\nediting all connections..................................................6-42\ngateway address...............................................................4-7\nediting individual connections......................................6-40\nGeneral Status.................................................................7-37\nRegister Device List.....................................................6-38\ngeneral status code.........................................................7-35\nconnection status codes and troubleshooting................15-11\nget..................................................................................10-15\nConnection Tab Page......................................................15-7\nglobal addresses..............................................................5-11\nConnection Type....................................................6-41, 6-43\nglobal broadcast................................................................8-9\nController Log Tab Page..................................................15-8\nController Object..............................................................7-83\nH\nController status..............................................................6-10\ncreating tags and tag sets...............................................6-25\nHost Name.........................................................................4-5\nhost names..........................................4-6, 4-15, 4-18 – 4-20\nD\nI\ndata processing time calculation example.....................14-25\ndata processing time overview......................................14-24\nIdentity Error...........................................................3-14, 3-49\nI-4 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nIndex\nIdentity Object..................................................................7-48 importing to Network Configurator...............................6-35\nindicator (LED).................................................................1-17 Normal Target Node Information............................3-26, 3-58\nindicators.........................................................................1-17 NTP Last Operation Time.......................................3-34, 3-63\ninput ON response time.................................................14-28 NTP Operation Information....................................3-33, 3-62\ninterval.............................................................................4-15 NTP Operation Result............................................3-34, 3-63\nIP Address.........................................................................4-3 NTP operation timing.......................................................4-15\nIP address allocation.........................................................5-2 NTP server clock information..........................................4-15\nIP address configuration....................................................5-2 NTP Server Connection Error................................3-20, 3-54\nIP Address Duplication Error..................................3-12, 3-46 NTP Settings Display.......................................................4-15\nIP Address Setting Error.........................................3-11, 3-45 NX Configuration Object..................................................7-53\nIP address setting method..........................................4-3, 4-4\nIP addresses..........................4-3, 4-4, 4-6, 4-15, 4-18 – 4-20 O\nIP Route Table Error...............................................3-14, 3-48\nIP router table setting example..........................................4-7 Online.....................................................................3-23, 3-55\nIP routing.........................................................................1-22 open...............................................................................10-11\nOriginator Variable...........................................................6-43\nK output ON response time...............................................14-29\noutput variable operation and timing......................7-34, 8-16\nKeep Alive.........................................................................4-6 overview of built-in EtherNet/IP port socket services......8-10\nKeep Alive monitoring time................................................4-6 overview of the CIP message communications service....7-3\nL P\nLinger option......................................................................4-7 Packet Filter.....................................................................1-23\nLINK settings..........................................................4-12, 4-13 Packet Filter (Simple)......................................................1-24\nLINK/ACT........................................................................1-18 packet interval (RPI)......................................................14-29\nLLDP................................................................................4-13 Packet Interval (RPI)................................................6-9, 6-42\nlocal broadcast..................................................................8-9 packet interval (RPI) accuracy.........................................14-5\nlocation............................................................................4-17 passwords ......................................................................4-14\nls....................................................................................10-12 PING Command..............................................................5-18\nport numbers........................................4-14, 4-15, 4-17, 4-19\nM Port Numbers for Socket Services....................................8-2\nPort1 Basic Ethernet Setting Error..........................3-11, 3-44\nMAC address........................................................1-13 – 1-17 Port1 BOOTP Server Error.....................................3-13, 3-47\nMAC Address Error..................................................3-9, 3-43 Port1 Communications Controller Error.................3-10, 3-44\nMask..................................................................................4-4 Port1 DHCP Server Error.......................................3-14, 3-48\nmaximum tag data link I/O response time.....................14-27 Port1 IP Address Duplication Error........................3-12, 3-46\nmdelete..........................................................................10-16 Port1 IP Address Setting Error...............................3-12, 3-45\nmdir................................................................................10-13 Port1 MAC Address Error.......................................3-10, 3-43\nmessage service transmission delay.............................14-30 Port1 Online...........................................................3-23, 3-55\nmget...............................................................................10-15 Port2 Basic Ethernet Setting Error..........................3-11, 3-45\nMIB groups......................................................................13-5 Port2 BOOTP Server Error.....................................3-13, 3-47\nMIB system diagram........................................................13-4 Port2 Communications Controller Error.................3-10, 3-44\nmkdir..............................................................................10-13 Port2 DHCP Server Error.......................................3-14, 3-48\nmls.................................................................................10-12 Port2 IP Address Duplication Error........................3-12, 3-46\nmput...............................................................................10-16 Port2 IP Address Setting Error...............................3-12, 3-46\nmulti-cast and unicast communications.............................6-9 Port2 MAC Address Error.......................................3-10, 3-43\nmulticast filtering................................................................2-3 Port2 Online...........................................................3-23, 3-55\nMultiple Switches ON Error....................................3-19, 3-53 precautions in using socket services...............................8-31\nprecautions when accessing external outputs................A-62\nN\npriority DNS server............................................................4-6\nprivate addresses.............................................................5-11\nNET ERR.........................................................................1-18\nprocedure to use socket services....................................8-14\nNET RUN.........................................................................1-18\nprocedure to use the SNMP agent................................13-28\nNetwork Configurator.........................................................1-7\nput..................................................................................10-15\nconnecting through CPU Unit’s USB port....................6-58\npwd................................................................................10-14\nconnecting through Ethernet........................................6-55\ndirect connections via Ethernet....................................6-60 Q\nnetwork transmission delay time...................................14-29\nnetwork variables...............................................................6-8 quit.................................................................................10-17\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) I-5\nI\nIndex\nR SNMP Trap Settings Display...........................................4-19\nSNMP traps...................................................1-29, 4-19, 13-3\nreading network configuration file....................................6-78 socket................................................................................8-2\nreceive data processing time.........................................14-29 socket service..................................................................1-26\nRecognition 1 settings.....................................................4-18 socket service communications\nRecognition 2 settings.....................................................4-18 data receive processing.................................................8-6\nrecognition method..........................................................4-18 fragmenting of send data...............................................8-4\nrecommended clamp core and attachment method........2-10 TCP communications.....................................................8-3\nRegistered Target Node Information......................3-25, 3-57 TCP communications procedures..................................8-4\nregistering devices...........................................................6-23 UDP communications....................................................8-3\nrelationship between task periods and packet intervals socket service instruction................................................8-13\n(RPIs).........................................................................14-26 specifying host names.....................................................1-28\nrename..........................................................................10-13 specifying method..................................................4-19, 4-20\nreponse code...................................................................7-35 starting and stopping tag data links.................................6-10\nRequested Packet Interval (RPI) and bandwidth usage starting and stopping tag data links for individual devices......\n(PPS)...........................................................................14-3 .....................................................................................6-74\nRequested Packet Interval (RPI) settings........................14-2 starting and stopping tag data links for the entire network.....\nrmdir..............................................................................10-14 .....................................................................................6-73\nroute path..........................................................................7-6 Status 1 Tab Page...........................................................15-3\nRPI...................................................................................6-43 Status 2 Tab Page...........................................................15-6\nstructure variables for input request paths......................7-17\nS subnet mask........................................................4-3, 4-4, 5-3\nSysmac Studio...................................................................1-7\nsample program system-defined variables...................................................3-2\nladder programming for tag data links.........................6-85\nsample programming T\nCIP message communications....................................7-22\nsocket service.....................................................8-18, 8-23 table of commands.........................................................10-11\nsaving network configuration file.....................................6-77 tag data link bandwidth usage and RPI...........................14-9\nSD Memory Card functions Tag Data Link Communications Error.....................3-17, 3-51\nfile types.....................................................................10-18 tag data link communications method.............................14-2\nformat of variable data ..............................................10-19 Tag Data Link Communications Start Switch3-36, 3-63, 6-73\ninitializing...................................................................10-19 Tag Data Link Communications Status..................3-24, 3-56\ntypes..........................................................................10-18 Tag Data Link Communications Stop Switch3-36, 3-64, 6-73\nsecondary DNS server......................................................4-6 Tag Data Link Connection Failed...........................3-16, 3-50\nsecure socket service......................................................1-27 tag data link parameters\nsend a recognition trap....................................................4-17 downloading.................................................................6-62\nsend data processing time.............................................14-28 Tag Data Link Setting Error....................................3-15, 3-49\nserver specifying method.................................................4-15 tag data links\nsetting and downloading tag data link parameters............6-8 data areas......................................................................6-3\nsetting IP addresses..........................................................5-5 data concurrency.........................................................6-14\nSettings required for the SNMP agent...........................13-28 functions and specifications...........................................6-6\nsettings required for the socket services.........................8-12 introduction....................................................................6-2\nSktClearBuf.....................................................................8-13 settings.........................................................................6-21\nSktClose..........................................................................8-13 tag data links with other models than NJ-series CPU Units\nSktGetTCPStatus............................................................8-13 .................................................................................6-91\nSktSetOption...................................................................8-13 Tag Data Links (Cyclic Communications)........................1-20\nSktTCPAccept..................................................................8-13 Tag Name Resolution Error....................................3-18, 3-52\nSktTCPConnect...............................................................8-13 tag sets..............................................................................6-3\nSktTCPRcv......................................................................8-13 Tag Status Tab Page.......................................................15-9\nSktTCPSend....................................................................8-13 tags....................................................................................6-3\nSktUDPCreate.................................................................8-13 Target Device...................................................................6-43\nSktUDPRcv......................................................................8-13 Target Node Error Information................................3-31, 3-61\nSktUDPSend...................................................................8-13 Target PLC Error Information.........................3-29, 3-60, 6-11\nSNMP agent...........................................................1-28, 13-2 Target PLC Operating Mode..........................3-27, 3-59, 6-11\nSNMP messages.............................................................13-3 Target Variable.................................................................6-43\nSNMP service..................................................................4-17 TCP Application Communications Error...................3-9, 3-42\nSNMP Settings Display...................................................4-17 TCP Application Setting Error................................3-20, 3-54\nSNMP specifications........................................................13-3 TCP/IP function.................................................................5-1\nI-6 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\nIndex\nTCP/IP Interface Object...................................................7-74\nTCP/IP Settings Display....................................................4-2\nTCP/UDP message service.............................................1-29\ntime..................................................................................4-15\ntimeout time.....................................................................4-16\nTimeout Value.........................................................6-42, 6-43\ntiming of data transmissions..........................................14-23\nTrap 1 settings.................................................................4-19\nTrap 2 settings.................................................................4-20\ntwisted-pair cable...............................................................1-6\nconnection methods.....................................................2-13\ninstallation precautions..................................................2-7\nother precautions for cable installation........................2-10\ntype................................................................................10-15\nU\nuploading tag data link parameters\nuploading all.................................................................6-66\nuploading from individual devices................................6-67\nUSB port..........................................................................1-17\nUse of duplicated IP address.............................................4-5\nuser................................................................................10-12\nusing CIP communications instructions.............................7-5\nV\nverifying device parameters.............................................6-70\nverifying tag data link parameters....................................6-68\nversion................................................................................22\nversions...........................................................................4-20\nNJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506) I-7\nI\nIndex\nI-8 NJ/NX-series CPU Unit Built-in EtherNet/IP Port User’s Manual (W506)\n\nOMRON Corporation Industrial Automation Company\nAuthorized Distributor:\nKyoto, JAPAN Contact : www.ia.omron.com\nRegional Headquarters\nOMRON EUROPE B.V. OMRON ELECTRONICS LLC\nWegalaan 67-69, 2132 JD Hoofddorp 2895 Greenspoint Parkway, Suite 200\nThe Netherlands Hoffman Estates, IL 60169 U.S.A.\nTel: (31) 2356-81-300 Fax: (31) 2356-81-388 Tel: (1) 847-843-7900 Fax: (1) 847-843-7787\nOMRON ASIA PACIFIC PTE. LTD. OMRON (CHINA) CO., LTD. ©OMRON Corporation 2011-2025 All Rights Reserved.\n438B Alexandra Road, #08-01/02 Alexandra Room 2211, Bank of China Tower, In the interest of product improvement,\nTechnopark, Singapore 119968 200 Yin Cheng Zhong Road, specifications are subject to change without notice.\nTel: (65) 6835-3011 Fax: (65) 6835-3011 PuDong New Area, Shanghai, 200120, China\nTel: (86) 21-6023-0333 Fax: (86) 21-5037-2388 Cat. No. W506-E1-37 0225"}