Download Print this page

Omron sysmac NX Series User Manual

Safety control unit / communucation control unit

Hide thumbs Also See for sysmac NX Series:

User manual (306 pages)

,

Owner's manual (570 pages)

,

Hardware user manual (218 pages)

page of 986

/ 986
Bookmarks

Advertisement

Quick Links

Download this manual

Safety Network Controller

NX-series

Safety Control Unit/

Communication Control Unit

User's Manual

NX-SL5£££

NX-SI££££

NX-SO££££

NX-CSG£££

Safety Control Unit

Communication Control Unit

Z395-E1-13

Advertisement

Need help?

Need help?

Do you have a question about the sysmac NX Series and is the answer not in the manual?

Questions and answers

Summary of Contents for Omron sysmac NX Series

Page 1 Safety Network Controller NX-series Safety Control Unit/ Communication Control Unit User's Manual NX-SL5£££ NX-SI££££ NX-SO££££ NX-CSG£££ Safety Control Unit Communication Control Unit Z395-E1-13...
Page 2 • Every precaution has been taken in the preparation of this manual. Nevertheless, OMRON as- sumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained in this publication.
Page 3 Introduction Introduction Thank you for purchasing an NX-series Safety Control Unit / Communication Control Unit. This manual contains information that is necessary to use the NX-series Safety Control Unit / Commu- nication Control Unit. Please read this manual and make sure you understand the functionality and performance of the Unit before you attempt to use it in a control system.
Page 4 Introduction NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 5 Sections in this Manual Sections in this Manual Calculating Safety Overview Reaction Times System Configuration and Communications Load Configuration Devices Specifications of Safety Unit Restore Configuration Units Designing the Power Backup Functions of the Supply System Communication Control Unit Installation and Wiring Safety Data Logging Safety Network Troubleshooting...
Page 6 CONTENTS CONTENTS Introduction ......................1 Intended Audience............................1 Applicable Products ............................1 Sections in this Manual ................... 3 Relevant Manuals....................13 Manual Structure....................15 Page Structure...............................15 Special Information ............................16 Precaution on Terminology ..........................16 Terms and Conditions Agreement................ 17 Warranty, Limitations of Liability ........................17 Application Considerations ..........................18 Disclaimers ..............................18 Statement of security responsibilities for assumed use cases and against threats........19...
Page 7 CONTENTS 1-2-2 Detailed Procedures........................1-8 Section 2 System Configuration and Configuration Devices Basic Configuration.......................2-2 2-1-1 CPU Rack Configuration ......................2-2 2-1-2 EtherNet/IP Field Network Configuration ..................2-3 2-1-3 Configuration Units........................2-3 Connecting the Support Software..................2-5 Network Configuration between Controllers...............2-6 Section 3 Specifications of Configuration Units Communication Control Unit ....................3-2 3-1-1 Models and Specifications ......................3-2...
Page 8 CONTENTS 4-3-3 Designing the I/O Power Supply from External Sources............4-18 4-3-4 Restrictions on Inrush Current for ON/OFF Operation ..............4-19 Selecting External Power Supplies and Protective Devices..........4-20 4-4-1 Selecting the Unit Power Supply ....................4-20 4-4-2 Selecting the I/O Power Supplies....................4-22 4-4-3 Selecting Protective Devices.....................4-23 Section 5 Installation and Wiring...
Page 9 CONTENTS Section 7 Settings Configuration and Setup Procedures ..................7-2 Part Names and Functions of the Sysmac Studio Window ..........7-3 CPU Rack Configuration and Setup..................7-5 7-3-1 Procedures for Creating the CPU Rack Configuration ..............7-5 7-3-2 Setting and Viewing the NX Unit Settings ...................7-6 7-3-3 Setting Up the FSoE Communications..................7-7 EtherNet/IP Network Configuration and Setup ..............7-9...
Page 10 CONTENTS 8-2-8 Restrictions on Variable Names and Other Safety Program-related Names......8-17 Constants (Literals) ......................8-20 8-3-1 Constants ..........................8-20 8-3-2 Types of Constants ........................8-20 Programming Languages....................8-22 8-4-1 Programming Languages ......................8-22 8-4-2 FBD Language ..........................8-22 Programming Operations....................8-27 8-5-1 Programming Layer on the Sysmac Studio................8-27 8-5-2 Registering POUs ........................8-28 8-5-3...
Page 11 CONTENTS 9-6-5 Controlling BOOL Variables, Changing Present Values, and Using Forced Refreshing ...9-26 9-6-6 Cross References ........................9-34 Online Functional Test ......................9-37 9-7-1 Online Functional Test Settings....................9-37 9-7-2 Online Functional Test Execution Procedure ................9-41 Search FB Where Safety Output Is OFF ................9-47 9-8-1 Procedure for Operating Search FB Where Safety Output Is OFF ...........9-47 9-8-2...
Page 12 CONTENTS 11-1-3 Relationship between the Number of Packets Used per Second and Packet Intervals.... 11-5 11-1-4 Adjusting the Device Bandwidth Usage ..................11-5 Section 12 Safety Unit Restore 12-1 Safety Unit Restore......................12-2 12-1-1 Generate Safety Unit Restore File Function ................12-2 12-1-2 Safety Unit Restore Function ....................12-3 12-1-3...
Page 13 CONTENTS Section 15 Troubleshooting 15-1 Operation after an Error ......................15-2 15-1-1 Overview of Communication Control Unit Status ..............15-2 15-1-2 Fatal Errors ..........................15-4 15-1-3 Non-fatal Errors in the Communication Control Unit ..............15-6 15-1-4 Checking for Non-fatal Errors ....................15-15 15-1-5 Resetting Non-fatal Errors ......................15-17 15-1-6 Errors Related to the EtherNet/IP Function Module ..............15-19 15-1-7...
Page 14 CONTENTS A-4-3 Safety Laser Scanners ......................A-36 A-4-4 Safety Door Switches with Magnetic Locks and Key Selector Switches........A-39 A-4-5 Enable Switches........................A-43 A-4-6 Two-hand Switches ........................A-47 A-4-7 D40A Non-contact Door Switches.................... A-50 A-4-8 D40Z Non-contact Door Switches .................... A-53 A-4-9 Safety Mats and Safety Light Curtains ..................
Page 15 Relevant Manuals Relevant Manuals The following table provides the relevant manuals for this product. Read all of the manuals that are relevant to your system configuration and application before you use the product. Most operations on this product are performed from the Sysmac Studio Automation Software. For de- tails on the Sysmac Studio, refer to the Sysmac Studio Version 1 Operation Manual (Cat.
Page 16 Relevant Manuals Purpose of use NX-SL5£££ Safety CPU Unit NX-SL3£££ Safety CPU Unit NX-SI££££ and NX-SO££££ Safety I/O Units NX-CSG£££ Communication Control Unit NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 17 Manual Structure Manual Structure Page Structure The following page structure is used in this manual. Level 1 heading 4 Installation and Wiring Level 2 heading Mounting Units Level 3 heading Level 2 heading Gives the current Level 3 heading headings. 4-3-1 Connecting Controller Components The Units that make up an NJ-series Controller can be connected simply by pressing the Units together...
Page 18 Manual Structure Special Information Special information in this manual is classified as follows: Precautions for Safe Use Precautions on what to do and what not to do to ensure safe usage of the product. Precautions for Correct Use Precautions on what to do and what not to do to ensure proper operation and performance. Additional Information Additional information to read as required.
Page 19 Omron’s exclusive warranty is that the Products will be free from defects in materials and work- manship for a period of twelve months from the date of sale by Omron (or such other period ex- pressed in writing by Omron). Omron disclaims all other warranties, express or implied.
Page 20 (v) protecting Omron Products from unau- thorized access. Further, in no event shall liability of Omron Companies exceed the individual price of the Product on which liability is asserted. Application Considerations...
Page 21 Terms and Conditions Agreement Performance Data Data presented in Omron Company websites, catalogs and other materials is provided as a guide for the user in determining suitability and does not constitute a warranty. It may represent the result of Omron’s test conditions, and the user must correlate it to actual application requirements. Actual per- formance is subject to the Omron’s Warranty and Limitations of Liability.
Page 22 Safety Precautions Safety Precautions Definition of Precautionary Information The following notation is used in this manual to provide precautions required to ensure safe usage of the NX-series Safety Control Unit / Communication Control Unit. The safety precautions that are pro- vided are extremely important to safety.
Page 23 Safety Precautions Warnings Serious injury may possibly occur due to loss of required safety functions. When building the system, observe the following warnings to ensure the integrity of the safety-related components. WARNING Setting Up a Risk Assessment System The process of selecting these products should include the development and execu- tion of a risk assessment system early in the design development stage to help identify potential dangers in your equipment and optimize safety product selection.
Page 24 Safety Precautions Installing Safety Products Qualified engineers must develop your safety-related system and install safety prod- ucts in devices and equipment. Prior to machine commissioning verify through testing that the safety products works as expected. Related International Standards: • ISO 12100 General Principles for Design - Risk Assessment and Risk Reduction •...
Page 25 Safety Precautions Confirm that the calculated reaction times meet the required specifications for all safety chains. Serious injury may possibly occur due to loss of required safety functions. All safety devices and components that are connected to an NX-series Safety Control Unit must be selected and used to meet the required level of safety and the relevant safety category.
Page 26 Safety Precautions Testing Operation Before you start the system, perform user testing to make sure that all safety devices operate correctly. The safety signature is validated upon completion of the user testing. Serious injury may possibly occur due to loss of required safety functions. After you perform safety validation, check items for safety validation printed out to con- firm Safety Control Units are correctly configured.
Page 27 Safety Precautions Voltage and Current Inputs Make sure that the voltages and currents that are input to the Units and slaves are within the specified ranges. Inputting voltages or currents that are outside of the specified ranges may cause acci- dents or fire.
Page 28 Safety Precautions If there is interference in remote I/O communications or if a major fault level error oc- curs, output status will depend on the products that are used. Confirm the operation that will occur when there is interference in communications or a major fault level error, and implement safety measures.
Page 29 Safety Precautions Data input and output protection Validate backups and ranges to cope with unintentional modification of input/output da- ta to control systems and equipment. • Checking the scope of data • Checking validity of backups and preparing data for restore in case of falsification and abnormalities •...
Page 30 Safety Precautions Cautions Caution Application Do not touch any Unit when power is being supplied or immediately after the power supply is turned OFF. Doing so may result in burn injury. Wiring Be sure that all terminal screws and cable connector screws are tightened to the tor- que specified in the relevant manuals.
Page 31 Precautions for Safe Use Precautions for Safe Use Transporting • Do not attempt to disassemble, repair, or modify any Units. Doing so may result in malfunction or fire. • Do not drop any Unit or subject it to abnormal vibration or shock. Doing so may result in Unit mal- function or burning.
Page 32 Precautions for Safe Use Restricted region (shaded portion) • The End Cover has a metal portion and is heavier than it looks. Be careful not to drop it when han- dling. Installation • Always connect to a ground of 100 Ω or less when installing the Units. Wiring •...
Page 33 Precautions for Safe Use • When you insert a flat-blade screwdriver into a release hole on the screwless clamping terminal block, press the screwdriver down with a force of 30 N or less. Applying excessive force may dam- age the terminal block. •...
Page 34 Precautions for Safe Use Debugging • With forced refreshing, the values of variables are overwritten with specified values and then the safety programs are executed. If forced refreshing is used for variables that give the results of pro- gram processing, the variables will first take the specified values, but they will then be overwritten by the safety program.
Page 35 Precautions for Safe Use If you need to prevent equipment from restarting when safety process data communications recover automatically, implement suitable restart conditions in the user program. • If you change the fail-soft operation setting, the output status when the error occurs may also change.
Page 36 If an error occurs in tag data link communications, this product continues refreshing variables with the last values that it receives. b) If an error occurs in tag data link communications, the Omron EtherNet/IP Originator automati- cally restores the communications after resolving the cause of the error.
Page 37 Precautions for Safe Use Restoring Data • You cannot back up, restore, or compare some or all of the settings for certain slaves and Units. Also, you cannot back up, restore, or compare data for disabled slaves or Units. After you restore data, sufficiently confirm that operation is correct before you start actual operation.
Page 38 Precautions for Correct Use Precautions for Correct Use Storage and Installation • Follow the instructions in this manual to correctly perform installation and wiring. • Do not operate or store the Units in the following locations. Doing so may result in burning, in opera- tion stopping, or in malfunction.
Page 39 Precautions for Correct Use DIN Track mounting hooks on all of the NX Units at the same time. If you unlock the DIN Track mounting hooks on all of the NX Units at the same time, all of the Units may come off. Wiring •...
Page 40 Safety CPU Unit. Take caution not to lose the password. If you want to reset the con- figured password, contact your OMRON representative. • For safety data logging, make sure to use the settings file generated from the same project file as the logging target.
Page 41 If there is a corrupted file in the SD Memory Card, the file is automatically deleted by the restoration function when the power supply is turned ON. • If you use an OMRON SD Memory Card, the end of the life of the SD Memory Card can be detected in the following ways.
Page 42 NRAG7 (CSA C22.2 No.61010-1, CSA C22.2 No.61010-2-201, and CSA C22.2 No.213) FSPC (IEC 61508 and ISO 13849) The FSoE protocol was certified for applications in which OMRON FSoE devices are connected to each other. For compatibility with FSoE devices other than OMRON FSoE devices, the customer must validate FSoE communications.
Page 43 Concepts l EMC Directives OMRON devices that comply with EU Directives also conform to the related EMC standards so that they can be more easily built into other devices or the overall machine. The actual products have been checked for conformity to EMC standards.*1 Whether the products conform to the standards in the system used by the customer, however, must be checked by the customer.
Page 44 NX-series product must also comply with the standards, consult with your OMRON representative. Application conditions are defined according to the installation location. Application may not be possible for some installation locations.
Page 45 Regulations and Standards This product meets the electromagnetic compatibility requirements for business use. There is a risk of radio interference when this product is used in home. Usage Conditions for KC Certification Take the same measures as those described in Conformance to EU Directives on page 40. In addi- tion, attach a clamp core to the port side of the EtherNet/IP cable.
Page 46 Lot number and serial num- Gives the lot number and the serial number of the Unit. DDMYY: Lot number, £: Used by OMRON, SSSS: Serial number “M” gives the month (1 to 9: January to September, X: October, Y: November,...
Page 47 Shows the unit version of the Unit. Lot number Gives the lot number of the Unit. DDMYY£: Lot number, £: Used by OMRON. “M” gives the month (1 to 9: January to September, X: October, Y: November, Z: December) The following information is provided in the notched area on the Unit.
Page 48 Lot number and unit ver- Gives the lot number and unit version of the Unit. • sion DDMYY£: Lot number, £: Used by OMRON. “M” gives the month (1 to 9: January to September, X: October, Y: Novem- ber, Z: December) •...
Page 49 Unit Versions To use the NX-CSG£££ Communication Control Unit and the NX-SL5£££ Safety CPU Unit, Sys- mac Studio version 1.24 or higher is required. Refer to A-19 Version Information on page A-112 for the relationship between the unit versions of the Units and the Sysmac Studio versions, and for the functions that are supported by each unit version.
Page 50 Related Manuals Related Manuals The followings are the manuals related. Use these manuals for reference. Manual name Cat. No. Model numbers Application Description NX-series Z395 NX-SL5£££ Learning how to use Describes the hardware, setup methods, Safety Control Unit / Commu- NX-SI££££...
Page 51 Terminology Terminology Term Description standard The generic term for devices, functions, and data that are used for general control purposes as opposed to those that are used for safety measures. safety function A function that is executed by the safety control system to achieve a safe state for a machine hazard.
Page 52 Terminology Term Description Safety I/O Unit An I/O Unit that is used for safety controls. This is a type of NX Unit. safety input device An input device that is designed with special safety measures for use in safety controls. The generic term for safety input devices, such as emergency stop pushbutton switches and safety switches.
Page 53 Terminology Term Description after safety validation A status indicates that safety validation has been performed on the safety application data from the Sysmac Studio because it has been determined that the safety controls meet the required specifications of the safety system. CPU Rack A Rack to which a CPU Unit or Communication Control Unit is mounted.
Page 54 Terminology Term Description Node ID An ID assigned to each of devices on a network so that the devices with the same Safety Network Number (SNN) can be uniquely identified for CIP Safety communications. The Safety CPU Unit is the only CIP Safety device on the NX bus, and the Node ID is always 1.
Page 55 Revision History Revision History A manual revision code appears as a suffix to the catalog number on the front and back covers of the manual. Cat. No. Z395-E1-13 Revision code Revision Date Revised content code April 2018 Original production • July 2018 Made changes accompanying the upgrade to NX-SL5700 unit version 1.3.
Page 56 Revision History NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 57 Overview This section describes the overview of Safety Network Controller. Overview of the Safety Network Controller ..........1-2 1-1-1 Features ......................1-2 1-1-2 Introduction to the System Configurations ............1-4 Procedure ....................... 1-7 1-2-1 Overall Procedure ................... 1-7 1-2-2 Detailed Procedures..................1-8 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 58 1 Overview Overview of the Safety Network Con- troller 1-1-1 Features The NX-series Safety Network Controller is a safety controller lined up as part of Sysmac devices. By combining the NX-series Safety Control Unit with the NX-series Communication Control Unit, it can be utilized as a safety controller which has the CIP Safety on EtherNet/IP Communications functions.
Page 59 I/O Units can be connected. You can exchange data easily between Safety CPU Units and these Units. Excellent Connectability with OMRON Safety I/O Devices You can directly connect OMRON’s wide lineup of Safety I/O Devices to Safety I/O Units without using any special units. Support for the IEC 61131-3 Programming Environment...
Page 60 1 Overview 1-1-2 Introduction to the System Configurations Safety Network Controller supports the following system configurations. Basic Configurations The Safety Network Controller basic configurations include CPU Rack configuration, EtherNet/IP field network configuration, and the Support Software. • CPU Rack Configuration NX-SL5£££...
Page 61 1 Overview Support Software CPU Rack Configuration EtherNet/IP Field Network Configuration Communication Safety CPU Unit Control Unit NX-SL5 NX-CSG Built-in EtherNet/IP port 1 Standard Controller EtherNet/IP Built-in EtherNet/IP port 2A NX Units Built-in EtherNet/IP port 2B CPU Rack EtherNet/IP Safety I/O terminal Network Configuration between Controllers The Safety Network Controller can perform CIP Safety on EtherNet/IP communications with other Safety Network Controllers on the same network when the built-in EtherNet/IP port on the Communi-...
Page 62 1 Overview Sysmac Studio EtherNet/IP Communication Safety CPU Unit Safety CPU Unit Communication Control Unit NX-SL5 Control Unit NX-SL5 NX-CSG NX-CSG Standard Controller EtherNet/IP EtherNet/IP Safety I/O terminal Safety I/O terminal NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 63 1 Overview Procedure 1-2-1 Overall Procedure Use the following procedure to build a safety control system. Step 1. System Design Step 1-1 Determining Safety Measures by Performing Risk Assessment Step 1-2 Selecting Safety Devices Step 1-3 Selecting Network Devices Step 1-4 Designing the Interface between Standard Controls and Safety Controls Step 1-5 Designing the Interface between Safety Controls Step 1-6 Designing Device Security Step 2.
Page 64 1 Overview 1-2-2 Detailed Procedures Step 1. System Design Procedure Description Reference • Step 1-1 Determining Identify potential danger factors and perform Safety Measures by Per- risk assessment. • forming Risk Assessment Study and decide on measures to reduce risks. Step 1-2 Selecting Safety Select the safety devices for inputs, logic, and Section 2 System Configura-...
Page 65 1 Overview Step 2. Software Design Procedure Description Reference Step 2-1 Designing I/O De- Design the configuration of the I/O devices and 6-3 Safety I/O Function on vice and Processing I/O Units. page 6-16 • Safety I/O devices • Standard I/O devices •...
Page 66 1 Overview Step 3. Calculating and Verifying Safety Response Performance Procedure Description Reference Step 3-1 Calculating Safe- Calculate safety task period, EPI and FSoE Section 10 Calculating Safety ty Communications Per- WDT, and verify the bandwidth usage. Reaction Times on page 10-1 formance Section 11 Communications Load on page 11-1...
Page 67 1 Overview Procedure Description Reference Step 4-6 Exposing Varia- Specify variables to be exposed to the standard 7-8 Exposing Variables to bles to Standard Control- controllers. Standard Controllers on page lers 7-49 Step 4-7 Programming Variable Registration: 8-5 Programming Operations •...
Page 68 1 Overview Step 6. Checking Operation Procedure Description Reference Step 6-1 Transferring Data Place the Sysmac Studio online with the Com- 9-2 Transferring the Configura- to the Controller munication Control Unit and transfer the config- tion Information on page 9-6 uration information from a computer to the Con- 9-3 Operating Modes of the troller.
Page 69 1 Overview Step 7. Operation, Maintenance, and Inspection Procedure Description Reference Step 7-1 Operation Restart the Safety CPU Unit. 9-11 Performing Safety Valida- If the Safety CPU Unit has a validated user pro- tion and Operation on page gram, the Safety CPU Unit will automatically 9-57 start in RUN mode.
Page 70 1 Overview 1-14 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 71 System Configuration and Config- uration Devices This section describes how to configure the Safety Network Controller system, and provides information on configuration devices in the system. Basic Configuration ..................2-2 2-1-1 CPU Rack Configuration ................. 2-2 2-1-2 EtherNet/IP Field Network Configuration ............2-3 2-1-3 Configuration Units..................
Page 72 2 System Configuration and Configuration Devices Basic Configuration The configuration that includes the Safety CPU Unit, the Communication Control Unit, as well as the Units of which input and output are directly controlled by the Safety CPU Unit and the Communication Control Unit, is called the Basic Configuration.
Page 73 2 System Configuration and Configuration Devices 2-1-2 EtherNet/IP Field Network Configuration The EtherNet/IP field network configuration consists of Communication Control Unit, Safety CPU Unit, an End Cover, a device that supports CIP Safety on EtherNet/IP, and a standard controller. The Safety Network Controller performs communications with devices that support CIP Safety on EtherNet/IP and standard controllers by connecting the built-in EtherNet/IP port of the Communication Control Unit to the EtherNet/IP network.
Page 74 2 System Configuration and Configuration Devices l SD Memory Card When you insert an SD Memory Card into the Communication Control Unit, various data can be saved, backed up, restored and compared using the SD Memory Card. Refer to 3-6 SD Memory Cards on page 3-60 for the models and specifications of individual SD Memory Card.
Page 75 2 System Configuration and Configuration Devices Connecting the Support Software The Safety Network Controller and the Support Software can be connected each other via the built-in EtherNet/IP port of the Communication Control Unit. Refer to 3-7-2 Connection on page 3-62 for in- formation on the connection between Safety Network Controller and the Support Software.
Page 76 2 System Configuration and Configuration Devices Network Configuration between Con- trollers The network configuration between Controllers consists of multiple Safety Network Controllers. You can configure network between Controllers when you connect the built-in EtherNet/IP ports of Com- munication Control Unit to the EtherNet/IP network. This network provides CIP Safety on EtherNet/IP communications between multiple network controllers.
Page 77 Specifications of Configuration Units This section provides the specifications of the configuration units. Communication Control Unit ................ 3-2 3-1-1 Models and Specifications................3-2 3-1-2 Built-in EtherNet/IP Port Specifications ............3-7 3-1-3 Part Names and Functions................3-10 3-1-4 Terminal Blocks ..................... 3-12 3-1-5 Indicators.......................
Page 78 3 Specifications of Configuration Units Communication Control Unit This section describes the models and specifications of the Communication Control Unit as well as the names and functions of the parts. 3-1-1 Models and Specifications This section describes the specifications of the Communication Control Unit. Models and Outline of Specifications The models and outline of specifications of the Communication Control Unit are given below.
Page 79 3 Specifications of Configuration Units General Specifications This section provides the general specifications of the Communication Control Unit. Item Specification Enclosure Mounted in a panel (open type) Grounding method Ground to 100 Ω or less Operating environment Ambient operating tem- 0 to 55°C perature Ambient operating humid-...
Page 80 3 Specifications of Configuration Units Individual Specifications This section provides the individual specifications of Communication Control Unit. l NX-CSG320 Unit name Communication Control Unit Model NX-CSG320 Indicators [RUN] indicator, [ERROR] indicator, [BUSY] indicator, [SD PWR] indicator, [SD BUSY] indicator, [NS] indicator x 2, [L/A] indicator, [L/A 2A] indicator, [L/A 2B] indicator, [TS] indicator, [UNIT PWR] indicator, [I/O PWR] indicator [TS] indicator, [UNIT PWR] indicator,...
Page 81 3 Specifications of Configuration Units Unit power Power sup- 24 VDC (20.4 to 28.8 VDC) supply ply voltage Unit power 5.95 W consump- tion Inrush cur- For cold start at room temperature: 10 A max./0.1 ms max. rent 2.5 A max./150 ms max. Current ca- pacity of power sup-...
Page 82 3 Specifications of Configuration Units The inrush current may vary depending on the operating condition and other conditions. Therefore, select fuses, breakers, and external power supply devices that have enough margin in characteristic and capacity, considering the condition under which the devices are used. Especially when you turn the power ON/OFF through a switch inserted to the external DC power supply, cy- cling power ON-OFF-ON within one second will cause the inrush current of approx.
Page 83 3 Specifications of Configuration Units 3-1-2 Built-in EtherNet/IP Port Specifications The following table shows the specifications of the built-in EtherNet/IP port of the Communication Con- trol Unit. Specification Item NX-CSG£££ Communications protocol TCP/IP or UDP/IP Sysmac Studio connection, tag data links, CIP message communications, Supported services FTP server, automatic clock adjustment (NTP client), SNMP (agent), DNS (client), BOOTP (client), TCP/UDP message service...
Page 84 3 Specifications of Configuration Units Specification Item NX-CSG£££ Number of con- 32/Logical ports nections (total of 64 with two logical ports) 1 to 10,000 ms in 1-ms increments Packet interval Packet intervals can be set independently for each connection. (Data is re- (refresh cycle) freshed over the network at preset intervals and does not depend on the number of nodes.)
Page 85 3 Specifications of Configuration Units If more than 40 tag sets are registered in total, the Tag Data Link, Too Many Tag Sets Registered (840E0000 hex) event will occur. Because the built-in EtherNet/IP port is equipped with an IGMP client (version 2), unnecessary multicast packets can be filtered out by an Ethernet switch that supports IGMP Snooping.
Page 86 3 Specifications of Configuration Units 3-1-3 Part Names and Functions This section provides the part names and functions of Communication Control Unit. (A) (B) (P) (O) Letter Name Function SD Memory Card con- Connects the SD Memory Card to the Communication Control Unit. nector SD Memory Card pow- Turns OFF the power supply so that you can remove the SD Memory Card.
Page 87 3 Specifications of Configuration Units Letter Name Function IP Address Switch 2 Used for setting an IP address for the built-in EtherNet/IP port (PORT2A and (x16, x1) PORT2B). Use the rotary switches and specify a two-digit hexadecimal num- ber. Refer to 7-4-1 Setting IP Addresses on page 7-9. IP Address Switch 1 Used for setting an IP address for the built-in EtherNet/IP port (PORT1).
Page 88 3 Specifications of Configuration Units 3-1-4 Terminal Blocks The terminal blocks on the Communication Control Unit are removable screwless clamping terminal blocks that allow you to easily connect and remove the wiring. Use the NX-TBC082 for the Communication Control Unit. Connect the Unit power supply, I/O power supply, and ground wire to the screwless clamping terminal block.
Page 89 3 Specifications of Configuration Units Applicable Terminal Blocks for Each Model Current capacity of power supply terminals and applicable terminal blocks for each model of Commu- nication Control Unit are shown in the following table. Current capacity of power sup- Terminal block ply terminal for the Unit Unit model...
Page 90 3 Specifications of Configuration Units 3-1-5 Indicators This section describes the indicators of Communication Control Unit. Note that the appearance of the indicators is different for the Unit with the lot number representing the date on or before March 19, 2019, from that representing the date on or after March 20, 2019. This manual shows the indicators for lot numbers representing the date on or after March 20, 2019.
Page 91 3 Specifications of Configuration Units Precautions for Safe Use • Never turn OFF the power supply to the Communication Control Unit when the BUSY indica- tor is flashing. While the BUSY indicator is flashing, a backup of the setting values into the built-in non-volatile memory is in progress.
Page 92 3 Specifications of Configuration Units l BUSY Indicator The BUSY indicator shows the status of access to the built-in non-volatile memory of Communica- tion Control Unit. The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 93 3 Specifications of Configuration Units Built-in EtherNet/IP Status Indicators (PORT1) These indicators show the operation status of the built-in EtherNet/IP port (PORT1) of the Communi- cation Control Unit. The meaning of the indicators is shown below. l NS Indicator The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 94 3 Specifications of Configuration Units Built-in EtherNet/IP Status Indicators (PORT2) These indicators show the operation status of the built-in EtherNet/IP port (PORT2) of the Communi- cation Control Unit. The meaning of the indicators is shown below. l NS Indicator The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 95 3 Specifications of Configuration Units NX Bus Status Indicators These indicators show the communications status of Communication Control Unit and NX Units. The meaning of the indicators is shown below. l TS Indicator The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 96 3 Specifications of Configuration Units Power Status Indicators These indicators show the power supply status of Communication Control Unit. The meaning of the indicators is shown below. l UNIT PWR Indicator The UNIT PWR indicator displays the status of the Unit power supply. The following table lists the possible states for this indicator and what they mean.
Page 97 Lot number and serial Shows the lot number and the serial number of the this Unit. number DDMYY: Lot number, £: For use by OMRON, SSSS: Serial number For M, 1: January to 9: September, X: October, Y: November, Z: Decem- ber.
Page 98 3 Specifications of Configuration Units Safety CPU Unit This section describes the models and specifications of the Safety CPU Units as well as the names and functions of the parts. 3-2-1 Models and Specifications The Safety CPU Unit specifications are described below. Models The following table specifies the list of Safety CPU Unit models.
Page 99 3 Specifications of Configuration Units Individual Specifications This section provides the individual specifications of the Safety CPU Unit. l Datasheet Items for Safety CPU Unit The following table gives the meaning of the datasheet items for the Safety CPU Unit. Item Description Maximum number of safety...
Page 100 3 Specifications of Configuration Units l NX-SL5500 Item Specification Maximum number of safety I/O 1,024 points points Program capacity 2,048 KB Number of safety I/O connections Number of CIP Safety originator connections Number of CIP Safety target con- nections Number of originators that can be connected with a multi-cast con- nection CIP Safety maximum data size per...
Page 101 3 Specifications of Configuration Units Item Specification Installation orientation and re- Installation orientation: Upright installation Restriction: None. strictions The cable length for the Units (Communication Control Unit and the Power Supply Unit for NX Units) that supply power to the corresponding Unit must be up to 20 m. Only NX102 CPU Units and Communication Control Units can be connected.
Page 102 3 Specifications of Configuration Units Item Specification Hardware switch settings [SERVICE] switch, [SETTING] switch Dimensions (mm) 30 × 100 × 71 (W × H × D) I/O power supply method Not supplied. Current capacity of I/O power No I/O power supply terminals supply terminals 3.35 W NX UnitPower consumption...
Page 103 3 Specifications of Configuration Units Let- Name Function Marker attachment loca- The locations where markers are attached. The markers made by OMRON tions are installed for the factory setting. Commercially available markers can also be installed. Refer to 5-2-7 Attaching Markers on page 5-20.
Page 104 3 Specifications of Configuration Units Letter Name Function Indicators Show the current operating status and communications status of the Safety CPU Unit. Safety CPU Unit Operation Status Indicators Indicators to show the operation status of the Safety CPU Unit are located in the center of the front side of the Safety CPU Unit.
Page 105 3 Specifications of Configuration Units Color Status Meaning • Not lit There is no Unit power supply • The Unit is restarting • Waiting for initialization to start l NS Indicator The NS indicator shows the CIP Safety communications status of the Safety CPU Unit. The following table lists the possible states for this indicator and what they mean.
Page 106 3 Specifications of Configuration Units Color Status Meaning Not lit No errors in the running program or settings l RUN Indicator The RUN indicator shows the execution status of the programs for the Safety CPU Unit. The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 107 3 Specifications of Configuration Units Item Meaning At normal operation It shows the lowest one byte of the safety signature for the safety pro- gram that is operating. If the safety signature is not confirmed, “—“ is dis- played. While a CIP Safety originator connection is being established, the indica- tor flashes.
Page 108 3-3-1 Models and Specifications The Safety Input Unit specifications are described below. Models The following table specifies the list of Safety Input Unit models. Number Number OMRON Number of Rated of safety of test Internal I/O Special I/O refresh-...
Page 109 Rated input voltage This is the rated input voltage of the Unit. OMRON Special Safety Input De- This tells whether the Unit supports the connection of OMRON Special vices Safety Input Devices (D40A Non-contact Door Switches, E3FS Single Beam Safety Sensors, etc.).
Page 110 Number of test output points 2 points Internal I/O common PNP (sinking inputs) Rated input voltage 24 VDC (20.4 to 28.8 VDC) OMRON Special Safety Input De- Can be connected. vices Number of safety slave connec- tions I/O refreshing method...
Page 111 3 Specifications of Configuration Units Item Specification Indicators [TS] indicator, [FS] indicator, [IN] indicator, [IN ERR] indicator [IN] indicator [IN ERR] indicator Safety input current 4.5 mA typical Safety input ON voltage 11 VDC min. Safety input OFF voltage/OFF 5 VDC max./1 mA max. current Test output type Sourcing outputs (PNP)
Page 112 Number of test output points 2 points Internal I/O common PNP (sinking inputs) Rated input voltage 24 VDC (20.4 to 28.8 VDC) OMRON Special Safety Input De- Cannot be connected. vices Number of safety slave connec- tions I/O refreshing method...
Page 113 3 Specifications of Configuration Units Item Specification Safety input OFF voltage/OFF 5 VDC max./1 mA max. current Test output type Sourcing outputs (PNP) Test output rated current 50 mA max. Test output ON residual voltage 1.2 V max. (IOV and all output terminals) Test output leakage current 0.1 mA max.
Page 114 This section provides the names and functions of the parts of the Safety Input Unit. Letter Name Function Marker attachment loca- The locations where markers are attached. The markers made by OMRON tion are installed for the factory setting. Commercially available markers can also be installed. Refer to 5-2-7 Attaching Markers on page 5-20.
Page 115 3 Specifications of Configuration Units Terminal Blocks There are two models of screwless clamping terminal blocks: NX-TB£££2 and NX-TB£££1. The following models of Terminal Blocks can be mounted to Safety Input Units. NX-TB£££2 16-terminal type 8-terminal type NX-TB£££1 8-terminal type 16-terminal type 3-39 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 116 3 Specifications of Configuration Units Letter Name Function Terminal number The terminal numbers are given by column letters A and B, and row numbers 1 to 8. indications The combination of the "column" and "row" gives the terminal numbers from A1 to A8 and B1 to B8.
Page 117 3 Specifications of Configuration Units WARNING Do not use the status of the indicators on the NX-series Safety Control Units for safety operations. This will compromise the safety functions of the Unit and may cause serious injury in the event of an accident. The appearance of the indicators is different depending on whether the lot number of the Unit repre- sents the date of or before September 19, 2018, or the date of or after September 20, 2018.
Page 118 3 Specifications of Configuration Units IN ERR IN ERR l TS Indicator The TS indicator shows the current status of the Safety Input Unit and its communications status with the Communication Control Unit. The following table lists the possible states for this indicator and what they mean. Color Status Meaning...
Page 119 3 Specifications of Configuration Units Color Status Meaning Not lit Power is not being supplied or a fatal fault has occurred. l IN Indicator The IN indicator shows the signal input status of the safety input terminal. The following table lists the possible states for this indicator and what they mean. The table shows an example of safety input terminal Si01.
Page 120 3 Specifications of Configuration Units Additional Information If the lot number of the Unit represents the date of or before September 19, 2018, the indicators have square-shaped light emitters. For details on the differences in appearance of the indica- tors, refer to Differences in Appearance of the Indicators on page 3-44. Color Status Meaning...
Page 121 3 Specifications of Configuration Units Safety Output Unit This section describes the models and specifications of the Safety Output Units as well as the names and functions of the parts. 3-4-1 Models and Specifications The Safety Output Unit specifications are described below. Models The following table specifies the list of the Safety Output Unit models.
Page 122 3 Specifications of Configuration Units Item Specification Operating environment Ambient operating temper- 0 to 55°C ature Ambient operating humidi- 10% to 95% (with no condensation or icing) Atmosphere Must be free from corrosive gases. Ambient storage tempera- −25 to 70°C (with no condensation or icing) ture Altitude 2,000 m max.
Page 123 3 Specifications of Configuration Units Item Specification Safety output rated current This is the maximum load current for safety outputs on the Unit. The inrush current of the external connection load must be lower than this value. Safety output ON residual voltage This is the residual voltage when a safety output on the Unit is ON.
Page 124 3 Specifications of Configuration Units Item Specification External con- Screwless clamping terminal block (8 terminals) nection termi- nals Indicators [TS] indicator, [FS] indicator, [OUT] indicator, [OUT ERR] indicator [OUT] indicator [OUT ERR] indicator Safety output 1.2 V max. (between IOV and all output terminals) ON residual voltage Safety output...
Page 125 3 Specifications of Configuration Units Item Specification Terminal con- So0 to So1: Safety output terminals nection dia- IOG: I/O power supply 0 V gram Safety Output Unit NX-SOH200 Refer to 6-3-2 Safety Output Function on page 6-38 for details. 3-49 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 126 3 Specifications of Configuration Units Item Specification Installation Installation orientation: orientation • Connected to a CPU Unit or a Communication Control Unit and restric- Possible in the upright installation orientation. tions • Connected to a Communications Coupler Unit Six possible orientations. Restriction: For upright installation, the ambient temperature is restricted as shown below ac- cording to the total Unit load current.
Page 127 3 Specifications of Configuration Units Item Specification I/O refreshing method Free-Run refreshing External connection ter- Screwless clamping terminal block (8 terminals) minals Indicators [TS] indicator, [FS] indicator, [OUT] indicator, [OUT ERR] indicator [OUT] indicator [OUT ERR] indicator Safety output ON residual 1.2 V max.
Page 128 3 Specifications of Configuration Units Item Specification Terminal connection dia- So0 to So3: Safety output terminals gram IOG: I/O power supply 0 V Safety Output Unit NX-SOD400 Refer to 6-3-2 Safety Output Function on page 6-38 for details. Installation orientation Installation orientation: and restrictions •...
Page 129 3 Specifications of Configuration Units Letter Name Function Marker attachment loca- The locations where markers are attached. The markers made by OMRON tion are installed for the factory setting. Commercially available markers can also be installed. Refer to 5-2-7 Attaching Markers on page 5-20.
Page 130 3 Specifications of Configuration Units 8-terminal type Letter Name Function Terminal number The terminal numbers are given by column letters A and B, and row numbers 1 to 8. indications The combination of the "column" and "row" gives the terminal numbers from A1 to A8 and B1 to B8.
Page 131 3 Specifications of Configuration Units Terminal block Unit model number Model Number of terminals Ground terminal mark Current capacity NX-SOH200 NX-TBA081 8 Not provided NX-TBA082 10 A NX-SOD400 NX-TBA081 8 Not provided NX-TBA082 10 A Precautions for Correct Use You can mount either NX-TB£££1 or NX-TB£££2 Terminal Blocks to the Units that the cur- rent capacity specification of the terminals is 4 A or less.
Page 132 3 Specifications of Configuration Units Letter Name Function Indicators Show the current operating status and communications status of the Safety I/O Units. Safety Output Unit Operation Status Indicators There are the indicators to show the operation status of Safety Output Unit in the center of the front side of the Safety Output Unit.
Page 133 3 Specifications of Configuration Units The following table lists the possible states for this indicator and what they mean. Color Status Meaning Green The FSoE connections are established and there are no er- rors in any Safety I/O Units functions. Flashing (at 1-s intervals) The FSoE connections are being established.
Page 134 3 Specifications of Configuration Units Additional Information If the lot number of the Unit represents the date of or before September 19, 2018, the indicators have square-shaped light emitters. For details on the differences in appearance of the indica- tors, refer to Differences in Appearance of the Indicators on page 3-44. Color Status Meaning...
Page 135 3 Specifications of Configuration Units End Cover This section describes the model and specifications of the end cover. 3-5-1 Models and Specifications The specifications of the End Cover are described below. Item Specification Model NX-END02 Dimensions (mm) 6 × 100 × 71 (W × H × D) Weight 82 g 3-59...
Page 136 3 Specifications of Configuration Units SD Memory Cards This section describes the models, specifications, and application of the SD Memory Cards. 3-6-1 Models and Specifications Refer to Specification of Supported SD Memory Cards, Folders, and Files in the NX-series Communication Control Unit Built-in Function User's Manual (Cat. No. Z396) for details. 3-6-2 Purpose You can use the SD Memory Card for the following applications.
Page 137 3 Specifications of Configuration Units Support Software The Support Software is a software package that provides an integrated development environment to design, program, debug, and maintain NX-series Satefy Network Controllers. Refer to A-19 Version In- formation on page A-112 for combinations of the available Support Software and its versions. This section describes the models and connecting methods of the Sysmac Studio.
Page 138 3 Specifications of Configuration Units 3-7-2 Connection You can connect online the Sysmac Studio to the Communication Control Unit in the following ways. Refer to 7-4-1 Setting IP Addresses on page 7-9 for details. Configuration l Connection with EtherNet/IP • •...
Page 139 This section gives the PFH (PFH ) values of the NX-series Safety CPU Unit and the Safety I/O Units. Precautions for Correct Use Go to the following URL for the most recent PFH values: http://www.ia.omron.com/support/ sistemalibrary/index.html Additional Information The NX-series Safety Control Unit is a Type B subsystem that is defined by IEC 61508 with HFT = 1 and SFF >...
Page 140 3 Specifications of Configuration Units 3-64 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 141 Designing the Power Supply Sys- This section describes how to design the power supply system for the NX-series NX- CSG320 Communication Control Unit. Power Supply System..................4-2 4-1-1 NX Unit Power Supply and I/O Power Supply..........4-2 4-1-2 NX-series Power Supply-related Units ............4-3 Designing the NX Unit Power Supply System ..........
Page 142 4 Designing the Power Supply System Power Supply System The power supply system for the CPU Rack of the NX-series NX-CSG320 Communication Control Unit consists of two power supply lines: one for NX Unit power and the other for I/O power. Therefore, you need to prepare two separate external power supplies for them.
Page 143 4 Designing the Power Supply System I/O Power Supply I/O power is supplied to the I/O circuits of each NX Unit on the CPU Rack of the NX-CSG320 Commu- nication Control Unit, as well as to external devices connected to the NX Units. Some NX Units receive I/O power through the NX bus, and others receive from external devices.
Page 144 For the specifications of NX-series power supply-related Units, refer to the NX-series System Units User’s Manual (Cat. No. W523). For information on the latest lineup of the NX-series power supply- related Units, refer to the relevant catalogs or OMRON websites, or ask your OMRON representative. Additional NX Unit Power Supply Unit...
Page 145 4 Designing the Power Supply System The total power consumption The total power consumption from the NX Unit power supply is from the NX Unit power within the NX Unit power supply supply is within the NX Unit capacity of the Communication power supply capacity.
Page 146 4 Designing the Power Supply System from the existing one. The I/O power is supplied to NX Units No.2 and No.3 via the inserted Addi- tional I/O Power Supply Unit. More than one Additional I/O Power Supply Unit can be connected to the CPU Rack. If adequate I/O power is not provided for all the NX Units on the right side of the Additional I/O Power Supply Unit, add another Additional I/O Power Supply Unit to an appropriate place.
Page 147 4 Designing the Power Supply System I/O power supply voltage I/O power supply voltage 24 VDC 12 VDC Cover Additional NX-series NX Unit NX Unit NX Unit NX Unit Communication I/O Power Supply Control Unit Unit Internal Internal Circuits power supply NX Unit power supply circuit...
Page 148 4 Designing the Power Supply System Cover NX-series I/O power I/O power NX Unit NX Unit NX Unit supply supply Communication connection connection Control Unit unit unit Internal Internal Circuits power supply NX Unit power supply circuit NX bus connector I/O power supply I/O power Unit...
Page 149 4 Designing the Power Supply System Designing the NX Unit Power Supply System This section describes how to design the NX Unit power supply to the CPU Rack of the NX-series NX- CSG320 Communication Control Unit. 4-2-1 Procedure for Designing the NX Unit Power Supply System The total power consumption from the NX Unit power supply must not exceed the NX Unit power sup- ply capacity of the Unit that supplies the NX Unit power.
Page 150 4 Designing the Power Supply System l NX Unit Power Supply Capacity and Restrictions The internal power supply circuits of the Communication Control Unit or Additional NX Unit Power Supply Unit supply the NX Unit power to the NX Units. The NX Unit power supply capacity does not include the NX Unit power consumption of the Addi- tional NX Unit Power Supply Units.
Page 151 4 Designing the Power Supply System Additional Information Excess or insufficiency in the NX Unit power supply capacity can be easily checked when the Unit configuration is created on the CPU and Expansion Racks Tab Page on the Sysmac Stu- dio.
Page 152 4 Designing the Power Supply System Designing the I/O Power Supply Sys- This section describes how to design the I/O power supply to the NX Units connected to the NX-series NX-CSG320 Communication Control Unit. 4-3-1 I/O Power Supply Method There are the following three methods to supply the I/O power supply to the NX Units depending on the type and model of the NX Units.
Page 153 4 Designing the Power Supply System 4-3-2 Designing the I/O Power Supply from the NX Bus Procedure for Designing the I/O Power Supply Make sure that the following design conditions are met when you design the I/O power supply from the NX bus.
Page 154 4 Designing the Power Supply System 32 units max. a. The total current consumption from I/O power a. The total current consumption from I/O power supply is less than the maximum I/O power supply is less than the maximum I/O power supply current (NX Units for “Supplied from supply current (NX Units for “Supplied from external source”...
Page 155 4 Designing the Power Supply System Calculating the Total Current Consumption from the I/O Power Sup- The total current consumption from the I/O power supply from the NX bus is the total of the following current consumptions. • The current consumption from the I/O power supply that is required for the Communication Control Unit, for the Additional I/O Power Supply Unit, and for the NX Units that are connected to them •...
Page 156 4 Designing the Power Supply System I/O power is supplied to the NX-SID800 and NX-SOD400 from the NX bus. a. Unit Specifications Current consumption from I/O power Model Input current supply NX-CSG320 10 mA NX-SL5700 0 mA NX-SID800 20 mA 6 mA/point NX-SOD400 60 mA...
Page 157 4 Designing the Power Supply System Calculating the Voltage Drop in the I/O Power Supply Voltage drop occurs in the Communication Control Units and NX Units due to the contact resistance at the points where Units are connected to each other. Design the I/O power supply system to maintain the voltage specifications of the NX Unit I/O circuits and connected external devices even if the volt- age of the I/O power supply drops.
Page 158 4 Designing the Power Supply System In actual calculations, add the current consumption from the I/O power supply that is given in the NX-series Data Reference Manual (Cat. No. W525). l Outline Find the I/O power supply voltage of the NX Unit that is the farthest from the Communication Con- trol Unit.
Page 159 4 Designing the Power Supply System 4-3-4 Restrictions on Inrush Current for ON/OFF Operation This section describes the restrictions on inrush current from the I/O power supply that occurs when connected external devices turn ON and OFF. Inrush Current Restrictions If inrush current to the I/O power supply occurs when a connected external device turns ON or OFF, do not allow the effective value of the I/O power supply current to exceed the following rated values when the inrush current is added to the current consumption from the I/O power supply.
Page 160 • Has double or reinforced insulation between the input and output. • Has an output voltage of 24 VDC (20.4 to 28.8 VDC). Recommended Power Supplies: S8VK-S Series (manufactured by OMRON) Calculating the Required Power Supply Capacity of the Unit Power...
Page 161 4 Designing the Power Supply System l Blocks A block consists of the Unit that supplies the NX Unit power and the range of Units to which that Unit supplies the NX Unit power. Communication Control Unit Block Additional NX Unit Power Supply Unit block NX Unit connected to the NX Unit connected to additional NX Communication Control Unit...
Page 162 *1. Use an output voltage that is appropriate for the I/O circuits of the NX Units and the connected external devi- ces. Recommended Power Supplies: S8VK-S Series (manufactured by OMRON) Calculating the Required Power Supply Capacity of the I/O Power...
Page 163 4 Designing the Power Supply System 4-4-3 Selecting Protective Devices This section describes how to select protective devices (e.g., breakers and fuses) to protect against short circuits and overcurrents in external circuits. Overcurrent is the current that flows when an excessive load is connected and one of the following ratings is exceeded.
Page 164 4 Designing the Power Supply System Current Breaking/fusing time 56 A 1.5 s max. 70 A 0.8 s max. The following values apply when the current capacity of power supply terminal is 4 A. Current Breaking/fusing time 1 min max. 12 A 15 s max.
Page 165 4 Designing the Power Supply System Block to which the Communication Control Unit supplies Block to which the Additional NX Unit Power the Unit power supply Supply Unit supplies the Unit power supply Block to which the Communication Block to which the Additional Control Unit supplies the I/O power I/O Power Supply Unit supply...
Page 166 4 Designing the Power Supply System Block to which the Communication Control Unit supplies Block to which the Additional NX Unit Power Supply Unit supplies the Unit power supply the Unit power supply Block to which the Communication Block to which the Additional Control Unit supplies the I/O power I/O Power Supply Unit supply...
Page 167 Installation and Wiring This section describes how to install and wire the NX-series NX-CSG320 Communica- tion Control Unit as well as details on installation locations. Processing at Power ON ................5-2 5-1-1 Power ON Operation ..................5-2 5-1-2 Operation When Resetting the Controller from the Sysmac Studio ....5-2 Mounting Units ....................
Page 168 5 Installation and Wiring Processing at Power ON WARNING • Do not disassemble any of the Units. Particularly the Units contain parts with high voltages when power is ON or immediately after power is turned OFF. Electrical shock may occur. There are also sharp internal parts that may cause injury. 5-1-1 Power ON Operation Precautions for Safe Use...
Page 169 5 Installation and Wiring • Check the status of output loads. • Make sure that SD Memory Card access is not in progress. NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 170 5 Installation and Wiring Mounting Units This section describes how to mount Units to the NX-series Controller. Precautions for Safe Use Always turn OFF the power supply to the Controller before attempting any of the following. • Mounting or removing NX Units or Communication Control Units •...
Page 171 5 Installation and Wiring 5-2-1 Installation in a Control Panel Installation in Cabinets or Control Panels When the NX-series Controller is being installed in a cabinet or control panel, be sure to provide prop- er ambient conditions as well as access for operation and maintenance. l Temperature Control The ambient operating temperature of the NX-series must be within the range of 0 to 55°C.
Page 172 5 Installation and Wiring l Controller Orientation • Each Rack must be mounted in the following position to provide proper cooling. This position is called an upright position. • Do not install a Rack in any of the following positions. Place DIN Track downward Place DIN Track upward DIN Tracks...
Page 173 5 Installation and Wiring Installation Method in Control Panels An NX-series Controller must be mounted inside a control panel on DIN Track. • Consider the width of wiring ducts, wiring, ventilation, and Unit replacement when determining the space between the CPU Rack and other devices. Additional Information A Controller must be mounted on DIN Track.
Page 174 5 Installation and Wiring l Routing Wiring Ducts Install the wiring ducts at least 20 mm away from the tops of the Rack and any other objects (e.g., ceiling, wiring ducts, structural supports, devices, etc.) to provide enough space for air circulation and replacement of Units.
Page 175 Preparations for Installation We recommend using the following products to install the Unit on a DIN Track. Name Model Manufacturer Remarks • 35-mm DIN Track PFP-50N OMRON Corporation Length: 50 cm • Material: Aluminum • Surface treatment: Insulated • PFP-100N OMRON Corporation Length: 100 cm •...
Page 176 5 Installation and Wiring ± 0.15 ± ± 0.15 15 (5) 1,000 (500) *1. PFP-50N dimensions are given in parentheses. NS 35/ 7,5 PERF R0.8 R0.8 NS 35/ 15 PERF 15° R1.25 R1.25 l End Plate PFP-M (Two) CLIPFIX 35 (Two) 5-10 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 177 5 Installation and Wiring 5-2-3 Installing the Communication Control Unit This section describes how to install the Communication Control Unit. Precautions for Safe Use • Do not apply labels or tape to the Unit. When the Units are installed or removed, adhesive or scraps may here to the pins in the NX bus connector, which may result in malfunctions.
Page 178 5 Installation and Wiring Install the DIN Track. • Using a PFP-50N/100N DIN Track Use one M4 screw for each three holes in the DIN Track. There must be a screw for each inter- val of 105 mm or less. The screw tightening torque is 1.2 N·m. DIN Track Use one screw for each three holes.
Page 179 5 Installation and Wiring Communication Control Unit DIN Track mounting hook Press hard DIN Tracks Additional Information It is not normally necessary to unlock the DIN Track mounting hook when you mount the unit. However, if you mount the unit on a DIN Track that is not one of the recommended DIN Tracks, the DIN Track mounting hook may not lock properly.
Page 180 5 Installation and Wiring Precautions for Safe Use • Always turn OFF the power supply before mounting the Units. If the power supply is not OFF, the Unit may result in malfunction or may be damaged. • Do not apply labels or tape to the Unit. When the Unit is installed or removed, adhesive or scraps may adhere to the pins in the NX bus connector, which may result in malfunctions.
Page 181 5 Installation and Wiring l Mounting an NX Unit to the Communication Control Unit Mount the NX Unit to the Communication Control Unit after removing the End Cover. From the front of the Communication Control Unit, engage the Unit hookup guides on the NX Unit with the Unit hookup guides on the Communication Control Unit.
Page 182 5 Installation and Wiring l Mounting NX Units to Each Other Use the following procedure to mount NX Units to each other. From the front of the previously mounted NX Unit, engage the Unit hookup guides on a new Unit with the Unit hookup guides on the previously mounted NX Unit. Unit hookup guides Unit hookup guides Slide the NX Unit on the hookup guides.
Page 183 5 Installation and Wiring 5-2-5 Mounting the End Cover Always mount the End Cover (NX-END02) provided with the product to the end of the CPU Rack. Precautions for Safe Use The End Cover has a metal portion and is heavier than it looks. Be careful not to drop it when handling.
Page 184 After you mount the Unit on the DIN Track, always secure it with End Plates at both sides. If you do not secure it, the Unit may be damaged or malfunction. l Using PFP-M (OMRON) To mount an End Plate, 1) hook the bottom of it on the bottom of the DIN Track and 2) rotate the End Plate to hook the top of it on the top of the DIN Track.
Page 185 5 Installation and Wiring Flat-blade screwdriver 5-19 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 186 Attaching Markers Markers can be attached to NX Units and their terminal blocks to identify them. The plastic markers made by OMRON are installed for the factory setting. The ID information can be written on them. Commercially available markers can also be installed.
Page 187 • The service life may be extremely short if a non-OMRON SD Memory Card is used. Also, operation may be affected due to deterioration in writing performance. • If you use an OMRON SD Memory Card, the end of the life of the SD Memory Card can be detected in the following ways.
Page 188 5 Installation and Wiring Installing the SD Memory Card Place your finger on the upper side panel of the memory card cover located in the middle of the Communication Control Unit and open it to the left. Insert the SD Memory Card with the label facing to the right. Insert the SD Memory Card with the label facing the right side of the Communication Control Unit.
Page 189 5 Installation and Wiring Close the Memory Card cover. 5-23 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 190 5 Installation and Wiring Removing the SD Memory Card Press the SD Memory Card power supply switch. SD Memory Card power supply switch Press the SD Memory Card after you confirm that the SD BUSY indicator (lit while SD Memory Card access is in progress) and SD PWR indicator (lit while SD Memory Card power is sup- plied) are no longer lit.
Page 191 5 Installation and Wiring Pull out the SD Memory Card. Close the Memory Card cover. 5-25 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 192 5 Installation and Wiring 5-2-9 Removal of the Communication Control Unit This section describes how to remove the Communication Control Unit. Precautions for Correct Use When you remove a Unit, be careful not to touch or bump the pins in the NX bus connector. Unlock the DIN Track mounting hook.
Page 193 5 Installation and Wiring 5-2-10 Removing NX Units Precautions for Safe Use Always turn OFF the Unit power supply and I/O power supply before you remove the NX Unit. Use a flat-blade screwdriver to pull up the DIN Track mounting hook on the Unit to remove. Flat-blade screwdriver DIN Track mounting hook Put your fingers on the protrusions for removing multiple NX Units including the Unit to be re-...
Page 194 5 Installation and Wiring 5-2-11 Assembled Appearance and Dimensions Installation Dimensions End Plate End Cover Communication End Plate Control Unit DIN Track center line DIN Tracks 72+(C)+(C) Unit: mm • Unit width Model Unit width [mm] NX-CSG£££ 72 • DIN Track dimension DIN Track model Dimension from the back of the Unit to the back of the DIN DIN Track dimension...
Page 195 5 Installation and Wiring End Plate model End Plate dimension PFP-M 10 mm CLIPFIX 35 9.5 mm 5-29 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 196 5 Installation and Wiring l Calculation Example of CPU Rack Configuration Width Communication Safety CPU Unit Control Unit Safety Input Unit Safety Output Unit End Cover The widths of the Units in the example CPU Rack configuration and the total configuration width are given below.
Page 197 5 Installation and Wiring Installation Height The installation height of the CPU Rack depends on the model of DIN Track and on the models of NX Units that are mounted. Also, additional space is required for the cables that are connected to the Unit. Allow sufficient depth in the control panel and allow extra space when you mount the CPU Rack.
Page 198 5 Installation and Wiring Wiring WARNING • Make sure that the voltages and currents that are input to the slaves and Units are within the specified ranges. Inputting voltages or currents that are outside of the specified ranges may cause accidents or fire.
Page 199 5 Installation and Wiring 5-3-1 Wiring the Power Supply This section describes the wiring of the power supply to the power supply terminals on the Communi- cation Control Unit. Through-wiring for unwired terminals Unit power supply (24 VDC) I/O power supply (5 to 24 VDC) Ground to 100 Ω...
Page 200 5 Installation and Wiring You can use the unwired terminals for through-wiring to an Additional NX Unit Power Supply Unit or to the Unit power supply terminals on another Communication Control Unit. When you supply the Unit power through the unwired terminals, be careful not to exceed 4 A, the current capacity of power supply terminals.
Page 201 5 Installation and Wiring 5-3-5 Grounding This section describes how to ground the CPU Rack. Units with Ground Terminals and Type of Ground Terminals Functional grounding Communication Control Unit, NX Unit l Units with Ground Terminals • Communication Control Unit •...
Page 202 5 Installation and Wiring Side of the Unit Ground terminal DIN Track contact plate Connected inside the Unit. 5-36 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 203 5 Installation and Wiring Grounding the CPU Rack This section describes how to ground the ground terminals on the CPU Rack. The functional ground terminals that are provided on some Units and the DIN Track are grounded. • Using a dedicated ground wire, ground the ground terminals and DIN Track with a ground resist- ance of 100 Ω...
Page 204 If the ground wire for a Unit with a ground terminal is shared with power equipment, noise will adverse- ly affect the Units. You can use OMRON NX-AUX01 DIN Track Insulation Spacers with PFP-50N or PFP-100N DIN Tracks to isolate the CPU Rack from the control panel.
Page 205 Ethernet switch as IGMP snooping or GMRP. Specific nodes are nodes equipped with an IGMP client, and have made transfer requests to the Ethernet switch. (OMRON built-in EtherNet/IP ports are equipped with an IGMP client.) Without 5-39...
Page 206 5 Installation and Wiring this function, multicast packets are transferred to all nodes in the network, just like broadcast packets, which increases the traffic in the network. Settings must be made in the Ethernet switch to enable this function. There must be enough mul- ticast filters for the network.
Page 207 5 Installation and Wiring • Executing CIP Safety I/O communications or Tag Data Links, and Message Communications We recommend an L2 Ethernet switch with multicast filtering and L4 QoS. If you set CIP Safety I/O communications or the tag data links to higher-priority transmission, it is possible to prevent problems such as transmission delays due to message communications traf- fic and packet losses resulting from buffer overflow.
Page 208 5 Installation and Wiring • Do not lay the twisted-pair cable in locations subject to excessive dirt, dust, oil mist or other con- taminants. Connecting the Shield to Connector Hoods: Between an EtherNet/IP Port and an Ethernet Switch Connect the shield to connector hoods as described below. •...
Page 209 5 Installation and Wiring Additional Information Noise immunity may be reduced and device damage may occur due to ground loops, which can occur due to improper shield connections and grounding methods. When using a baud rate of 100 Mbps or less, it may be possible to alleviate this problem by connecting only the Ethernet switch side as described in (2), rather than connecting both ends as described in (1).
Page 210 5 Installation and Wiring • Always use a dedicated power supply for the Ethernet switch. Do not use the same power supply for other equipment, such as an I/O power supply, motor power supply, or control power supply. • Before installation, check the Ethernet switch's environmental resistance specifications, and use an Ethernet switch that is appropriate for the ambient conditions.
Page 211 5 Installation and Wiring • Electrical specifications: Conforming to IEEE 802.3 standards. • Connector structure: RJ45 8-pin Modular Connector (conforming to ISO 8877) • For information on connecting shield wire to connector hoods, refer to Precautions When Laying Twisted-pair Cable on page 5-41. 10BASE-T and 100BASE-TX: Connector Signal name...
Page 212 5 Installation and Wiring 5-3-7 Wiring to the Screwless Clamping Terminal Blocks This section describes how to connect wires to the screwless clamping terminal blocks, the installation and removing methods, and functions for preventing incorrect attachment. You can connect ferrules that are attached to the twisted wires to the screwless clamping terminal block.
Page 213 5 Installation and Wiring The applicable ferrules, wires, and crimping tools are given in the following table. Applicable Termi- Manufac- Ferrule wire Crimping tool nal type turer model (AWG)) All ter- Phoenix AI0,34-8 0.34 (#22) Phoenix Contact (Applicable wire sizes are given in minals Contact parentheses.)
Page 214 5 Installation and Wiring Wire type Terminals Conductor Twisted wires Solid wire Wire size length (strip- Classifica- Current Unplat- Unplat- ping length) Plated Plated tion capacity All termi- 2 A max. Possible Possible Possible Possible 8 to 10 mm 0.08 to 1.5 mm nals except Greater Not pos-...
Page 215 5 Installation and Wiring Wire type Terminals Twisted wires Solid wire Ferrule Classifica- Current ca- Plated Unplated Plated Unplated tion pacity All terminals 2 A max. except Greater than Not possible Not possible ground termi- 2 A and 4 A nals or less Ground termi-...
Page 216 5 Installation and Wiring Secure wires within the range of 30 mm from the screwless clamping terminal block. 30 mm Connecting and Removing Wires This section describes how to connect and remove wires. l Terminal Block Parts and Names Release hole Terminal hole 5-50 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 217 5 Installation and Wiring l Required Tools Use a flat-blade screwdriver to connect and remove wires. Use the following flat-blade screwdriver. Side view Front view 8° to 12° 2.5-mm dia. 0.4 mm 2.5 mm Recommended screwdriver Model Manufacturer SZF 0-0,4X2,5 Phoenix Contact l Connecting Ferrules Insert the ferrule straight into the terminal hole.
Page 218 5 Installation and Wiring Release hole Flat-blade screwdriver 10° to 15° Leave the flat-blade screwdriver pressed into the release hole and insert the twisted wire or the solid wire into the terminal hole. Insert the stripped portion of the wire all the way into the terminal hole to prevent shorting. Twisted wire or Solid wire Remove the flat-blade screwdriver from the release hole.
Page 219 5 Installation and Wiring Precautions for Safe Use • Do not press the flat-blade screwdriver straight into the release holes on a screwless clamp- ing terminal block. Doing so may damage the terminal block. • When you insert a flat-blade screwdriver into a release hole on a screwless clamping terminal block, press it down with a force of 30N or less.
Page 220 5 Installation and Wiring Wire Remove the flat-blade screwdriver from the release hole. Precautions for Safe Use • Do not press the flat-blade screwdriver straight into the release holes on a screwless clamp- ing terminal block. Doing so may damage the terminal block. •...
Page 221 5 Installation and Wiring Press the lock lever on the terminal block and pull out the top of the terminal block to remove it. Lock lever Terminal block Attaching a Terminal Block Mount the terminal block hook that is applicable to each Unit model on the guide at the bottom of the NX Unit, lift up the terminal block, and press in on the top of the terminal block until you hear it engage.
Page 222 5 Installation and Wiring Preventing Incorrect Attachment of Terminal Blocks In order to prevent unintentionally installing the wrong terminal block, you can limit the combination of a Unit and a terminal block. Insert three Coding Pins (NX-AUX02) into three of the six incorrect attachment prevention holes on the Unit and on the terminal block.
Page 223 1 through 6 in the figure below. As shown in the following table, there are 20 unique pin patterns that you can use. Terminal block Unit Holes used by Holes used by OMRON OMRON Holes for incorrect Holes for incorrect attachment prevention attachment prevention...
Page 224 • The holes not designated by the numbers 1 through 6 in the above figure are used by OM- RON. If you insert any Coding Pins into the holes reserved for use by OMRON, you will not be able to mount the terminal block to the Unit.
Page 225 5 Installation and Wiring Unit Checking Wiring You can check the wiring from the Watch Tab Page on the Sysmac Studio. For Input Units, you can turn ON and OFF an input from the external device that is connected to the Unit you need to check and monitor the results.
Page 226 5 Installation and Wiring Control Panel Installation To ensure system reliability and safety, the system must be designed and configured according to the installation environment (temperature, humidity, vibration, shock, corrosive gases, overcurrent, noise, etc.). 5-4-1 Temperature Panels have been reduced in size due to space-saving and miniaturization in devices and systems, and the temperature inside the panel may be at least 10 to 15°C higher than outside the panel.
Page 227 5 Installation and Wiring l Forced Ventilation (by Fan at Top of Panel) Controller Controller Air filter Forced Ventilation Method l Forced Air Circulation (by Fan in Closed Panel) Controller Controller Forced Air Circulation l Room Cooling (Cooling the Entire Room Where the Control Panel Is Lo- cated) Cooler Control panel...
Page 228 5 Installation and Wiring 5-4-2 Humidity Rapid temperature changes can cause condensation to occur, resulting in malfunctioning due to short- circuiting. When there is a possibility of this occurring, take measures against condensation, such as leaving the Controller power ON at night or installing a heater in the control panel to keep it warmer. Control panel Moisture absorber...
Page 229 5 Installation and Wiring 5-4-5 Electrical Environment When installing or wiring devices, make sure that there will be no danger to people and that noise will not interfere with electrical signals. Controller Installation Location Install separately the Controller from high-voltage (600 V or higher) and power devices to ensure safe operation and maintenance.
Page 230 5 Installation and Wiring Controller DC I/O AC I/O device device Terminal block Example of Arrangement in Panel Wire Layout for the Power Supply System Observe the following points when wiring the power supply system. • Separate the Controller power supply from the I/O device power supply and install a noise filter near the Controller power supply feed section.
Page 231 5 Installation and Wiring Surge suppressor Input Inductive Inductive Diode Unit, Inductive Diode load load Built-in load Input Output Output Unit Unit Connect a diode in a DC circuit. Connect a surge Connect a diode suppressor in an AC circuit. in a DC circuit.
Page 232 5 Installation and Wiring • Communications lines and power lines • DC signals and AC signals • High-frequency devices (such as Inverters) and signal lines (communications) l Wiring Observe the following points when wiring power supply and signal cables. • When routing signal cables with differing characteristics through the same duct, always keep them separated.
Page 233 5 Installation and Wiring • Noise induction may occur if the Controller is installed in a panel that includes high-voltage devi- ces. Wire and install them as far apart as possible. (Refer to Controller Installation Location on page 5-63.) • Either install the Controller a minimum of 200 mm away from high-voltage lines or power lines, or place the high-voltage lines or power lines in metal tubing and completely ground the metal tub- ing to 100 Ω...
Page 234 5 Installation and Wiring Additional Information • In countries or regions where earthing methods are regulated, you must comply with the reg- ulations. Refer to the applicable local and national ordinances of the place where you install the system, or other international laws and regulations. •...
Page 235 5 Installation and Wiring Connect the ground lines of the device that is connected with a communications cable and oth- er devices as a bundle to a single earth electrode. Be sure that the earth electrode is separated by a minimum of 10 m from any other earth electrode of a device that could be a noise source. NX-series Communication Control Unit A device that could be Control panel...
Page 236 5 Installation and Wiring NX-series Communication Control Unit Control Other A device that could be panel devices NX-AUX01 a noise source Precautions for Grounding l General Precautions • To prevent electrical shock, do not connect devices to ground poles (or steel frames) with non- equalized potential to which multiple devices are connected.
Page 237 5 Installation and Wiring l Controller Ground Terminals The Controller has the following ground terminal. Grounding Symbol Connection type Functional Ground this terminal when power supply noise causes malfunc- Grounding tioning. When the functional ground terminal is correctly grounded, it is generally effective in suppressing power supply common noise.
Page 238 5 Installation and Wiring 5-72 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 239 Safety Network Controller Opera- tion This section provides information that is necessary to use the Safety Network Control- ler, including how the Safety Network Controller works. Overview of the Safety Network Controller Operation ....... 6-2 6-1-1 Introduction to FSoE Communications............6-2 6-1-2 Introduction to Communications between NX Units ........
Page 240 6 Safety Network Controller Operation Overview of the Safety Network Con- troller Operation This section describes an overview of the Safety CPU Unit operation. A Safety CPU Unit executes safety programs and performs I/O refreshing to achieve safety controls. The Safety CPU Unit accesses the data for I/O refreshing through variables and executes the safety programs.
Page 241 6 Safety Network Controller Operation Communication Safety CPU Unit Safety Input Unit Safety Output Digital Input Digital Output Control Unit Unit Unit Unit M: FSoE Master S: FSoE Slave 6-1-2 Introduction to Communications between NX Units In communications between NX units, data is cyclically exchanged between the Safety CPU Unit and the standard I/O Unit.
Page 242 6 Safety Network Controller Operation Communication Communication Safety CPU Safety CPU Control Unit Control Unit Unit Unit Communication Safety CPU Control Unit Unit CIP Safety device O: CIP Safety Originator T: CIP Safety Target 6-1-4 Introduction to Tag Data Links Tag Data Links Tag data links enable cyclic tag data exchanges on an EtherNet/IP network between Controllers or be- tween Controllers and other devices.
Page 243 6 Safety Network Controller Operation Communication Control Unit CJ-series CPU Unit EtherNet/IP Units Inputs Output Connection Tag set name: ABC Tag set name: OUT1 Var_In_a Var-Out1(DM0) I/O refreshing Var_In_a Var-Out1 Input tag Output tag Var_In_b Var-Out2(DM100) I/O refreshing Var_In_b Var-Out2 Var_In_c Var-Out3(DM200) Var_In_c...
Page 244 6 Safety Network Controller Operation l Example In the following example, input tags "a" to "g" at the originator are a tag set named SP1_IN and output tags "I" and "ii" are a tag set named SP1_OUT. A connection is set between these two tag sets.
Page 245 6 Safety Network Controller Operation Communication Control Unit CJ-series CPU Unit I/O memory area Tag set SP1_IN Tag set SP1_OUT (tag a) (tag c) Connection Variable a Variable c Tags Tag set SP2_IN Tag set SP2_OUT (tag d) (tag b) Connection Variable b Variable d...
Page 246 6 Safety Network Controller Operation Connection Setting Parameters The connection settings have the following setting parameters. • Setting the Requested Packet Interval (RPI) The RPI (Requested Packet Interval) is the I/O data refresh cycle on the Ethernet line when tag data links are established.
Page 247 6 Safety Network Controller Operation Thereafter, you can start and stop tag data links for the entire network or individual devices from the Network Configurator. Starting and stopping tag data links for individual devices must be performed for the originator. Controller Status You can include the Controller status as a member of a tag set in the data sent and received.
Page 248 6 Safety Network Controller Operation For the CIP Safety originator connections, you can establish a unidirectional input or output com- munication with a CIP Safety target per connection. Two connections are used to establish bidir- ectional input and output communications. •...
Page 249 6 Safety Network Controller Operation l Calculating the Number of Routable CIP Safety Connections for the Com- munication Control Unit You must specify the total number (m+n) of targets that establish connections as an originator (m) and originators that establish connections as a target (n), which must be set within the maximum number of routable CIP Safety connections for the Communication Control Unit.
Page 250 6 Safety Network Controller Operation Number of targets that Number of originators Total (m establish connections as that establish connec- an originator (m) tions as a target (n) Communication Control Unit (A) 2 Communication Control Unit (B) 6 Communication Control Unit (C) 2 Two multi-cast connections are included in this number.
Page 251 6 Safety Network Controller Operation O : originator Node1 T : target multicast multicast Node2 Node3 6-13 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 252 6 Safety Network Controller Operation I/O System This section describes how the Safety CPU Unit processes I/O with external devices such as Safety I/O Units. When the Safety CPU Unit exchanges signals with Safety I/O Units and other external devices, it does so through logical interfaces that are called "I/O ports".
Page 253 6 Safety Network Controller Operation The names of safety data type variables have the word SAFE appended to a standard data type name such as SAFEBOOL. Refer to 8-2-5 Data Type on page 8-14 for details on the safety data types. Standard Data Type Variables These variables represent data that is not related to safety controls.
Page 254 Semiconductor Output for Dual Channel Equivalent • Semiconductor Output for Dual Channel Complementary The following OMRON Special Safety Input Devices can be connected directly without a special con- troller. (This applies only to the NX-SIH400.) 6-16 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 255 6 Safety Network Controller Operation Type Examples OMRON Single-beam Safety Sensors E3ZS and E3FS * Conforms to Type 2 and PLc. OMRON Non-contact Door Switches D40Z * Conforms to PLe and Safety Category 4. D40A * Conforms to PLd and Safety Category 3.
Page 256 6 Safety Network Controller Operation NX-SI Example of Sysmac Studio Settings: • Dual-channel Input When I/O Short Detection between Lines Is Not Required NX-SI Example of Sysmac Studio Settings: 6-18 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 257 6 Safety Network Controller Operation • Dual-channel Input When I/O Short Detection between Lines Is Required NX-SI Example of Sysmac Studio Settings: 6-19 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 258 6 Safety Network Controller Operation Precautions for Correct Use • Configure dual-channel inputs with safety input terminals on the same Unit. It is not always possible to detect short circuits between safety input terminals on different Units. • The total length of cable connected to one test output must be as follows: NX-SIH400 and NX-SID800: 400 m max.
Page 259 30 µs max. Check the specifications of the connected device for the maximum cable length. l E3ZS/E3FS Single-beam Safety Sensors An OMRON E3ZS/E3FS Single-beam Safety Sensor is connected as shown in the following figure. Single-beam Safety Sensors 24 VDC The unit that supplies the I/O...
Page 260 6 Safety Network Controller Operation Example of Sysmac Studio Settings: 6-22 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 261 6 Safety Network Controller Operation Precautions for Correct Use • The maximum number of connections per Unit is as follows: NX-SIH400: 4 • You can branch the connections to up to four Single-beam Safety Sensors for each test out- put. Single Beam Single Beam Single Beam...
Page 262 6 Safety Network Controller Operation l D40A/D40Z Non-contact Door Switches The non-contact door switch output (black line) from the OMRON D40A or D40Z Non-contact Door Switch is input to a safety input terminal. This is a one-line signal. When connecting it, branch it as shown at Si0 and Si1 in the following figure.
Page 263 • The D40Z Non-contact Door Switch can be used in a Safety Category 4 or lower or a PLe or lower application. l UM/UMA Safety Mats OMRON UM/UMA Safety Mats are connected as shown in the following figure. n pcs (n=12 max.) NX-SIH400...
Page 264 • The UM/UMA Safety Mats can be used in a Safety Category 3 or lower or a PLd or lower application. They cannot be used in a Safety Category 4 or PLe application. l SGE Safety Edges OMRON SGE Safety Edges are connected as shown in the following figure. 6-26 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 265 6 Safety Network Controller Operation NX-SIH400 n Units (n = 5 max.) Blue Blue Blue Blue Safety edge Brown Brown Brown Brown n + 1 Example of Sysmac Studio Settings: 6-27 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 266 6 Safety Network Controller Operation Precautions for Correct Use • The maximum number of connections per Unit is as follows: NX-SIH400: 5 (5 connected in series × 1 series) • A Safety Edge requires two test output terminals when it is used. If a Safety Edge is connect- ed to the NX-SIH400 Unit, you cannot connect any additional safety input devices that require test output terminals.
Page 267 6 Safety Network Controller Operation Safety Input Unit Safety CPU Unit Safety Output Unit Safety output Safety input Safety I/O Safety I/O Safety program function function communications execution communications Safety input data Safety output data Self-diagnosis Without test pulse Mechanical contacts Test Pulse Evaluation Single-beam safety sensors A pulse is output at a specific...
Page 268 An OMRON D40A/D40Z Non-contact Door Switch is connected. Test signals for the D40A Door Switch or D40Z will be output. Safety Mat/Safe- An OMRON UM/UMA Safety Mat or SGE Safety Edge (4-wire) is connected. A test signal ty Edge for Safety Mat/Safety Edge diagnosis is output. Dual Channel Evaluation Safety input terminals can be used as dual channels (one pair).
Page 269 6 Safety Network Controller Operation Safety CPU Unit Safety Input Unit Test Pulse Evaluation Safety input data Dual channel Safety program evaluation execution Safety process data Test Pulse Evaluation communications The following parameters are also used. • Single/Dual • Discrepancy Time l Single/Dual Set the evaluation method to use with the safety input terminals.
Page 270 6 Safety Network Controller Operation Input signals on the safe- Safety input data ty input terminals Single/Dual Meaning of status Si (n) Si (n+1) Si (n) Si (n+1) Dual Channel Equivalent 0 Inactive (OFF) Discrepant status Discrepant status Active (ON) Dual Channel Comple- Discrepant status mentary...
Page 271 6 Safety Network Controller Operation Safety input terminals Error Cause of error detected removed Safety input data I/O indicator (yellow) I/O indicator (red) *1. This is the time that the error status (control data, status data, and indicator status) is held (1 s min.). •...
Page 272 6 Safety Network Controller Operation Safety input terminal 0 Safety input terminal 1 Safety input data 0 before dual evaluation Safety input data 1 before dual evaluation Discrepancy time Safety input data 0 I/O indicator (yellow) 0 I/O indicator (yellow) 1 I/O indicator (red) 0 I/O indicator (red) 1 *1.
Page 273 6 Safety Network Controller Operation Setting Error detection Contact Short with posi- circuits Single/Dual Test pulse Disconnection Ground fault tive side of in input power line wiring Dual Channel Without Test Pulse Not detecta- Not detectable. Detectable Not de- Equivalent when input tecta- ble.
Page 274 6 Safety Network Controller Operation Input Filters The input filter helps prevent malfunctions that are sometimes caused by chattering or noise from the external device that is connected to a safety input terminal. You can filter out chattering and noise from the external device for the widths that are set with the ON delay time and OFF delay time.
Page 275 6 Safety Network Controller Operation Safety input terminals OFF Error Internal timer Counter cleared. Counter cleared. OFF delay Safety input data I/O indicator (yellow) I/O indicator (red) *1. This is the time that the error status (control data, status data, and indicator status) is held (1 s min.). l Operation with Both an ON Delay and OFF Delay You can filter out ON pulses for the width that is set with the ON delay time and filter out OFF puls- es for the width that is set with the OFF delay time.
Page 276 6 Safety Network Controller Operation I/O Power Supply Monitoring I/O power supply monitoring monitors the voltage range of the I/O power supply. If a voltage that is less than the specified range is detected, all safety inputs for the Unit are turned OFF.
Page 277 6 Safety Network Controller Operation NX-CSG Current when IOG line is broken I/O power supply (24 VDC) Disconnected NX-SO Load Use the wiring that is shown in the following figure to prevent a floating condition for the IOG of the Safety Output Unit even if the IOG line is broken.
Page 278 6 Safety Network Controller Operation NX-SO ≤100m ≤100m ≤100m ≤100m NX-SI Example of Sysmac Studio Settings: Precautions for Correct Use • The line length from the safety output terminals to the output devices (L1, L2, L3, and L4) is 100 m max. for each line. •...
Page 279 6 Safety Network Controller Operation NX-SO NX-SO Types of Safety Output Functions The types of safety output functions that are performed by the Safety Output Unit is shown below. The safety output functions diagnose the outputs to the safety output terminals and the external device wiring based on the safety output data from the safety program.
Page 280 6 Safety Network Controller Operation Test Pulse Evaluation The test pulse evaluation outputs a test pulse with a specific period on the 24-VDC power line from a safety output terminal to detect errors in wiring to the externally connected device. This evaluation is achieved through the Test Pulse Diagnosis parameter.
Page 281 6 Safety Network Controller Operation Setting Description Dual Channel Equiv- The pair of safety output terminals are used as dual channel outputs. The output is ON alent if the paired safety output terminals are both normal. l Relationship between the Single/Dual Setting and Safety Output Data The safety output data that is used in the safety program is output to the safety output terminals according to the Single/Dual parameter as shown below.
Page 282 6 Safety Network Controller Operation Safety output data Safety output command value Safety output terminals Error Cause detected removed. I/O indicator (yellow) I/O indicator (red) *1. This is the time that the error status (control data, status data, and indicator status) is held (1 s min.). •...
Page 283 6 Safety Network Controller Operation Safety output data Safety output command value Safety output terminal 0 Error Cause of error detected removed Safety output terminal 1 I/O indicator (yellow) 0 I/O indicator (yellow) 1 I/O indicator (red) 0 I/O indicator (red) 1 Flashing *1.
Page 284 6 Safety Network Controller Operation Safety Output Terminal Short Detection The safety output terminal short detection prevents the internal circuits of the safety output terminals from being destroyed if an overcurrent flows due to a ground fault or other cause. If an overcurrent is detected, the safety output terminal is turned OFF.
Page 285 Settings Configuration and Setup Procedures............7-2 Part Names and Functions of the Sysmac Studio Window......7-3 CPU Rack Configuration and Setup ............. 7-5 7-3-1 Procedures for Creating the CPU Rack Configuration ........7-5 7-3-2 Setting and Viewing the NX Unit Settings ............7-6 7-3-3 Setting Up the FSoE Communications............
Page 286 7 Settings Configuration and Setup Procedures This section describes the procedures for using the Sysmac Studio to configure and set up the Safety Network Controller. Make the settings in the following order. CPU Rack Configurations and Setup EtherNet/IP Network Configurations and Setup I/O Terminals Setup Assigning Variables to I/O Ports Exposing Variables to Standard Controllers...
Page 287 7 Settings Part Names and Functions of the Sys- mac Studio Window This section gives the names of the parts of the Sysmac Studio Window. Controller Selection Box Use this box to select the Safety CPU Unit or the Communication Control Unit. The tab page will change between the Safety CPU Unit Setup and Programming View and the Communication Control Unit Setup and Programming View.
Page 288 7 Settings Letter Name Function Output Tab The Output Tab Page shows the results of building. Page Watch Tab The Watch Tab Page shows the monitor results of the online Safety CPU Unit, the Page Communication Control Unit, or the Simulator. Build Tab Page The Build Tab Page shows the results of program checks and building.
Page 289 7 Settings CPU Rack Configuration and Setup This section describes the configuration and setting procedures for a CPU Rack for the Safety Net- work Controller. You configure and set up a CPU Rack of the Communication Control Unit on the CPU and Expansion Racks Tab Page of the Communication Control Unit.
Page 290 7 Settings Additional Information • Only one Safety CPU Unit can be placed on the Communication Control Unit. If you add more than one Safety CPU Units, the " ! " icons are displayed under all of the Safety CPU Units, and it will cause an error during the synchronization and download process.
Page 291 7 Settings Data Name Description Initial value range Power con- This is the power consumption of the NX Unit from the NX Depends on the sumption (W) pos- bus. model of the sibl This setting applies to Units other than an Additional NX Unit.
Page 292 7 Settings Item Description Active (Enable/ The communications setting for FSoE communications is displayed. Disable) sibl Selected: Enabled This setting assigns the Safety I/O Unit to the Safety CPU Unit as a communications node, and displays the I/O ports for that Unit in the I/O Map. Not selected: Disabled This setting does not assign the Safety I/O Unit to the Safety CPU Unit as a commu- nications node, and does not display the I/O ports for that Unit in the I/O Map.
Page 293 7 Settings EtherNet/IP Network Configuration and Setup 7-4-1 Setting IP Addresses IP Addresses l IP Address Configuration IP addresses are made up of 32 bits of binary data that specify the network number (net ID) and host number (host ID). The network number identifies the network, and the host number identifies the node (or host) on the network.
Page 294 7 Settings l Subnet Mask Operation and management of a network can become very difficult if too many nodes are connect- ed on a single network. In such a case it can be helpful to configure the system so that a single network is divided up into several subnetworks.
Page 295 7 Settings As shown in the above tables, node 1 and node 2 have the same network address, which means these nodes belong to the same network. l CIDR CIDR, or classless interdomain routing, is used to assign IP addresses that do not use classes. IP addresses that use classes are separated into blocks according to network IDs and host IDs, resulting in inefficient usage of IP address space.
Page 296 7 Settings You can also select Obtain from BOOTP Server for the IP address setting method in TCP/IP Settings of the Built-in EtherNet/IP Port Settings on the Sysmac Studio and then set the IP ad- dress switch on the Communication Control Unit to 00. •...
Page 297 7 Settings TCP/IP Settings IP Ad- dress Fix at the IP address ob- Obtain from BOOTP Switch Fixed setting tained from BOOTP serv- server. Settings 01 to FE The ports will have the following IP address- The IP Address Switch Settings Error is triggered and the communications are disabled.
Page 298 7 Settings Connect the Sysmac Studio online to the Communication Control Unit. Additional Information The first time you establish an online connection to the Communication Control Unit with Win- dows Firewall enabled after you installed Sysmac Studio, a dialog box may be displayed to con- firm the connection.
Page 299 7 Settings Additional Information • The TCP/IP Settings Display is not updated even after the IP address is normally obtained from the BOOTP server. To check the IP address that was obtained from the BOOTP server, upload the project from the Communication Control Unit and check the Controller Status Pane.
Page 300 7 Settings Precautions for Correct Use If there is more than one node with the same IP address in the EtherNet/IP network, the built-in EtherNet/IP port will connect to the node that is detected first. Note that an IP Address Duplication Error will not be detected in this case. Online Connection Procedure Connect the Communication Control Unit and the computer that runs Sysmac Studio via Ethernet, and then perform the following procedure.
Page 301 7 Settings l Checking the Current IP Address The current IP address can be confirmed in the Controller Status Pane of the Sysmac Studio, whether it is manually set or obtained from the BOOTP server. • • Basic Controller Status Pane Controller Status Pane with Details Additional Information •...
Page 302 7 Settings Additional Information The following network variable names are not allowed. • Variable names that contain only single-byte numerals from 0000 to 6143 • Variable names with the following single-byte letters (uppercase or lowercase) followed by single-byte numerals a) H (H000 to H511) b) W (W000 to W511) c) D (D00000 to D32767) d) E0_ to E18_ (E0_00000...E0_32767 to E18_00000...E18_32767)
Page 303 7 Settings a) Right-click anywhere in the Input Tab Page of the Built-in EtherNet/IP Connection Set- tings Tab Page and select Create New Tag Set from the menu. b) Enter a tag set name for the list in the Input Tab Page. c) Right-click anywhere in the Input Tab Page and select Create New Tag from the menu.
Page 304 7 Settings Name Setting Items Instance ID Displays the Instance ID. • Auto • IN...{min}...IN...{max} {min} represents the minimum number of Produced Assembly ID recorded in the EDS files for the relevant devices. {max} represents the maximum number of Produced Assembly ID recorded in the EDS files for the relevant devices.
Page 305 7 Settings CIP Safety Communication Settings 7-5-1 Safety Network Number Settings for the NX Bus Use the following procedure to set the Safety Network Number (SNN) for the NX bus. In the Multiview Explorer, select the target Safety CPU Unit in the Controller Selection Box. Select Configurations and Setup –...
Page 306 7 Settings Additional Information You can also enter the Safety Network Number (SNN) directly in the Safety Network Number Settings Tab Page. 7-5-2 Originator Connection Settings To use the Safety CPU Unit as an originator device for CIP Safety, the CIP Safety communications need to be set.
Page 307 7 Settings Item Description EtherNet/IP Port 2 Settings of CIP Safety connections via the built-in EtherNet/IP port 2 are listed. Safety Network Number: Specifies the SNN for the EtherNet/IP net- work for which the port 2 is connected Connection list: Connections grouped together by each target device are listed.
Page 308 7 Settings Select a target device in the connection list and right-click on it. Click the Edit Menu. The target device settings pane is displayed. Change the displayed settings according to the actual target device settings. The settings depend on a type of the target device as shown in the following table. Target device type Setting Items Safety CPU Unit...
Page 309 7 Settings Item Description I/O Assembly I/O assemblies of the target device for which a safety connection can be opened are listed. Connection Type For input connection (receiving from the target device), select ei- ther Point to Point Connection or Multicast Connection. Open Type Select a type for connection opening.
Page 310 7 Settings Select a target device in the connection list and right-click on it. Click the Create New Connection Menu. The Connection Assignment Dialog Box is displayed. Specify the connection parameters and click the OK Button. A new connection is added to the connection list. Batch Connection Settings l EPI Batch Setting The function of EPI Batch Setting can change the EPI of the CIP Safety connections at once.
Page 311 7 Settings Click the Batch connection settings button to select EPI Batch Setting. The EPI Batch Setting window is displayed. Output Expected Packet Input Expected Packet Interval(EPI) Interval(EPI) Item Description Input Expected Packet Interval Enter an EPI value for the CIP Safety input connections. (EPI) Output Expected Packet Interval Enter an EPI value for the CIP Safety output connections.
Page 312 7 Settings Click the Batch connection settings button to select Open Type Batch Setting. The Open Type Batch Setting window is displayed. The Open Type Batch Setting window consists of the items shown in the following table. Item Description Target Device Selec- Select target devices that change the open types or those that obtain and tion Check Box change the signature codes.
Page 313 7 Settings Confirm the changed contents and click the OK button. The set open types and safety signatures (SCCRC and SCTS) of the target devices will be re- flected in the project file. Additional Information Change the open type to Type2a and then press the Get the signature (SCID) from the target device button to obtain safety signatures from the target devices.
Page 314 7 Settings The I/O Assembly Settings (Target) Tab Page is displayed. The I/O Assembly Settings (Target) Tab Page consists of the items shown in the following ta- ble. Item Description Active/Inactive Use this box to enable or disable each I/O Assembly. When you ena- ble the assembly, a port is added to the I/O Map.
Page 315 Connecting Target Devices of Other Manufacturers To configure the CIP Safety communication settings for target devices manufactured by other compa- nies, you need to create or install the EDS file for non-OMRON target devices. Creating an EDS File This function can create an EDS file to set CIP Safety connections with a CIP Safety target device.
Page 316 7 Settings Click the New EDS file button. The New EDS file window is displayed. Specify the information of the target device. Item Description I/O Assembly Select the I/O assembly supported by the target device. Input and Output: Select Input and Output when the target device supports the input and output connections.
Page 317 7 Settings Item Description Vendor ID Specify the vendor ID of the target device. Used for the connection settings with the target device. Vendor Name Specify the vendor name of the target device. Used for display on the Sysmac Studio. Product Type Specify the product type of the target device.
Page 318 7 Settings The created EDS file is registered in the EDS Library for CIP Safety screen. After the registra- tion is completed, the EDSFileCRC will be displayed in the dialog. Exporting the EDS File You can reuse the created EDS file on other computers by exporting it. 7-34 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 319 7 Settings The procedure to export the EDS file is described below. Right-click on the Connection Settings (Originator) screen and select the menu EDS Library for CIP Safety. The EDS Library for CIP Safety screen is displayed. Click the Export button. The export window is displayed.
Page 320 7 Settings Right-click on the Connection Settings (Originator) screen and select the menu EDS Library for CIP Safety. The EDS Library for CIP Safety screen is displayed. Click the Install button and select the EDS file for the target device you will add. Then, click the Open button.
Page 321 7 Settings The non-OMRON target device is added to the EDS Library for CIP Safety. Click the Close button to close the EDS Library for CIP Safety screen. The device registered to the EDS Library for CIP Safety is displayed in the list of connectable target devices in the Tool- box on the Connection Settings (Originator) screen.
Page 322 7 Settings Setting the Input and Output Func- tions This section describes setting procedures of the input and output functions for NX Units. 7-6-1 Safety I/O Functions You set the safety input functions and safety output functions of the Safety I/O Units when you assign input devices and output devices to the Safety I/O Units with the Sysmac Studio.
Page 323 7 Settings Letter Name Function Parameter Set- This pane is used to make settings for the input and output devices that are tings Pane set for the Safety I/O Units. You can arrange the devices, set diagnosis func- tions, change icons, etc. Refer to A-9 Icon list for Safety Slave Unit Parameters on page A-83 for de- tails on changing icons.
Page 324 7 Settings When you complete the settings, the following is displayed. Change the settings and enter comments. Refer to 6-3-1 Safety Input Function on page 6-16 and 6-3-2 Safety Output Function on page 6-38 for the I/O devices that you can connect and the settings for each I/O device. 7-40 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 325 7 Settings Precautions for Correct Use If you select an input device that cannot be set for a Safety Input Unit, an error will occur and the frame around the input device will be displayed in red. Additional Information The I/O terminal comments on the Parameters Tab Page are linked to the device variable com- ments and the global variable comments.
Page 326 7 Settings Assigning Variables to I/O Ports 7-7-1 Registering Device Variables Device variables are used to access data in devices (slaves and Units). This data is accessed through a port that acts as an interface to an external device. This logical port is called an "I/O Port".
Page 327 7 Settings If you choose the Create Device Variable command, the device variables are automatically named with the device name and port name. The device variables that you enter or automati- cally create are registered in the global variable table. l Selecting from the Registered Variables If the variables that are used in the program are registered before you finalize on the Controller configuration and the external devices to connect, you can select and assign variables to the I/O...
Page 328 7 Settings In the Variable and Variable Comment columns, set any variable name and variable com- ment. After you edit data with a spreadsheet application, save the data in the CSV format (UTF-8). From the main menu, select Tools - I/O Map - Import or Import (Include variable comment). Import imports only the Variable column of the CSV file.
Page 329 7 Settings I/O Ports for Safety I/O Units That Are Displayed in the I/O Map of the Safety CPU Unit The I/O ports for Safety I/O Units that are displayed in the I/O Map of the Safety CPU Unit are descri- bed in this section.
Page 330 7 Settings Port Data type Name Description fault Safety Con- SAFE- Safety Connec- This flag indicates when a safety connection is nection Status BOOL tion Status active. Use it for an input to the Activate termi- nal on a safety FB or for safety connection/ disconnection applications.
Page 331 7 Settings Port Data type Name Description fault So03 Output SAFE- So03 Output Gives the status of safety output terminal So03. Value BOOL Value 0: OFF, 1: ON 7-7-2 Settings of Communications between NX Units Communications between NX Units are used for standard process data communications between a Safety CPU Unit and standard I/O Units.
Page 332 7 Settings The I/O data of the standard I/O Units will be allocated to the exposed variables of Safety CPU Unit. Precautions for Correct Use The I/O ports of the NX Unit that is set for communications between NX Units are not available to be registered as device variables of the Communication Control Unit.
Page 333 7 Settings Exposing Variables to Standard Con- trollers This section describes how to control and monitor the Safety CPU Unit from a standard controller through tag data links. 7-8-1 Exposing Global Variables To ensure that global variables in the Safety CPU Unit are not accidentally used by a program of the standard controller, they are not assigned to the standard controller at the time of their setting.
Page 334 7 Settings 7-8-2 Setting Exposed Variables This section describes how to expose Safety CPU Unit variables to the Communication Control Unit. Exposed Safety CPU Unit variables (exposed variables) appear in the I/O Map of the Communication Control Unit. Use one of the following methods to set exposed variables. •...
Page 335 7 Settings The variable that you entered is registered in the exposed variable table and in the global vari- able table. Setting the Expose Column for Global Variables Register global variables with standard data types. Refer to 8-5-3 Registering Variables on page 8-38 for details on registering variables. Select the Expose Column for global variables, and then select Input or Output.
Page 336 7 Settings Refer to 8-5-3 Registering Variables on page 8-38 for details on registering variables. Right-click one or more global variables and select Copy from the menu. The selected global variables are copied. Press the Shift Key or Ctrl Key to select more than one global variable. Right-click in the Exposed Variables Tab Page and select Paste from the menu.
Page 337 7 Settings To change the I/O setting for an exposed variable, right-click the exposed variable and select Move To Output or Move To Input from the menu. Press the Shift Key or Ctrl Key to select more than one exposed variable. Selecting Global Variables on the Exposed Variables Tab Page Use the following procedure to select registered global variables on the Exposed Variables Tab Page and set them as exposed variables.
Page 338 7 Settings Enter the name of the variable to expose (the global variable that was registered in step 1) to the Communication Control Unit. You can also enter the first letter of the global variable in the Name Box to display a list of can- didates, and then double-click the desired variable.
Page 339 7 Settings Refer to A-6 Safety CPU Unit Status on page A-69 for details on the items in the Safety CPU Unit status. 7-8-4 I/O Ports of Safety I/O Units The tag data links allow you to view the port values of Safety I/O Units from the standard controller. The port values can be referenced by assigning variables to the I/O ports that are displayed on the I/O Map of the Communication Control Unit.
Page 340 7 Settings Exporting/Importing Settings Data This section describes how to reuse the settings data for the entire CPU Rack in the Sysmac Studio or the safety application data in the Safety CPU Unit. You can export and import the data for the entire CPU Rack or the safety application data in the Safety CPU Unit as a single file.
Page 341 7 Settings Right-click the Communication Control Unit and select Export All NX Unit Settings from the menu. The Export All NX Unit Settings Dialog Box is displayed. Enter a file name, and then click the Save Button. A configuration file for all the NX Units with an .nsfp extension is saved. 7-57 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 342 7 Settings To import a file, right-click the Communication Control Unit in the CPU and Expansion Racks Tab Page, and select Import All NX Unit Settings from the menu. All NX Units including Safety CPU Unit to be imported will be added to the CPU and Expansion Racks Tab Page.
Page 343 7 Settings Right-click the Safety CPU Unit to export and select Export NX Unit Settings from the menu. The Export NX Unit Settings Dialog Box is displayed. Enter a file name, and then click the Save Button. An NX Unit configuration file with an .nsf extension is saved. 7-59 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 344 7 Settings To import a file, select the Unit to the left of the point where you wish to add the slave on the CPU and Expansion Racks Tab Page, and then right-click and select Import Slave Settings and Insert New Slave from the menu. The Safety CPU Unit to import is added to the CPU and Expansion Racks Tab Page.
Page 345 7 Settings 7-10 Offline Comparison This section describes the function for comparing the safety application data between the currently opened project and another project file. This function can be used for managing changes in safety application data. In addition, target data can be reflected in the current project if the data supports detailed comparison.
Page 346 7 Settings Item Description Target Data As data to compare, you can select Configurations and Setup or Programming. By default, Programming is selected. Refer to 7-10-4 Target Data of Offline Comparison on page 7-65 for details of target data. Select the target project, Safety CPU Unit to be compared, and target data, and then click the Execute Button.
Page 347 7 Settings The contents of this window are as follows. Letter Name Description Current Project Displays the source project in a tree format. Target Project Displays the target project in a tree format. Detailed Com- Displays the detailed comparison window for data that has any differences in the parison Button comparison results AND that supports detailed comparison.
Page 348 7 Settings Safety Programs The contents of this window are as follows. Letter Name Description Zoom in/out Button Zooms in/out on the program comparison window. Program Comparison Displays the source and target programs. Window Program Comparison Displays differences against each program network. Click the Reference but- Results List ton to display differences on the program comparison window.
Page 349 7 Settings Variable Table The contents of this window are as follows. Letter Name Description Zoom in/out and Jumping Used to zoom in/out on the variable table comparison window and to jump to Differences Button to differences. Variable Table Compari- Displays the results of variable table comparison between the source and son Window target projects.
Page 350 7 Settings Detailed Com- Displayed name Target data parison • Configurations and Setup Whether FSoE communications settings are Not applicable Communications enabled or disabled Safety • Whether FSoE Watchdog Timer is set to au- Safety I/O to setting or not •...
Page 351 7 Settings Detailed Com- Displayed name Target data parison • Configurations and Setup I/O assembly settings for a CIP Safety I/O Not applicable Communications assembly Safety EtherNet/IP Safety Connection Settings Connection Settings (Originator) I/O Assembly Settings (Target) I/O Map • Configurations and Setup Assignment settings for standard I/O and ex- Not applicable...
Page 352 7 Settings 7-68 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 353 Programming This section describes variables, instructions, and other elements that are used to cre- ate safety programs. It also describes the programming operations that are used on the Sysmac Studio. POUs (Program Organization Units) ............8-3 8-1-1 POU......................... 8-3 8-1-2 Overview of the Three Types of POUs............
Page 354 8 Programming 8-6-1 Generation Algorithms for Automatic Programming........8-87 8-6-2 Automatic Programming Settings..............8-90 8-6-3 Automatic Programming Execution Procedure ..........8-93 Monitoring Memory Usage for Communication Control Unit ....8-97 Monitoring Memory Usage for Safety Control Unit........8-98 Offline Debugging ..................8-100 8-9-1 Offline Safety Program Debugging..............
Page 355 8 Programming POUs (Program Organization Units) The safety program that runs on an NX-series Safety CPU Unit is made from a combination of POUs (program organization units). This section describes the configuration and specifications of POUs. Refer to 8-5 Programming Operations on page 8-27 for the procedures to create POUs on the Sys- mac Studio.
Page 356 8 Programming Function Blocks (FBs) l Executing Function Blocks and Execution Conditions • You can call function blocks from programs or other function blocks to execute them. • Function blocks are always executed. • To execute a function block for only specific conditions, pass a TRUE value to the Activate input variable of that function block.
Page 357 8 Programming POU type Programs Function blocks Functions Item Execution condition Always executed. Always executed. Always executed. Specify the execution condition with an input variable. The hierarchical relationships between programs, functions, and function blocks are shown in the fol- lowing figure. Task Program 1 Program 2...
Page 358 8 Programming l Order of Execution You can set the order of execution of all programs in a safety task. You set this order in the Program Assignment Settings Display of the Task Settings Tab Page on the Safety CPU Unit Setup and Programming View on the Sysmac Studio. Refer to 8-5 Pro- gramming Operations on page 8-27 for programming operations.
Page 359 8 Programming Settings of a function block instance in a program Instance name Function block name Local Variable Table Output parameters Input parameters Input variable Output variable Internal variables Algorithm Programming in the FBD language Any instructions and user-defined function blocks can be used Created in the function definitions l Function Block Name or Instruction Name This is the name of the user-defined function block or the instruction.
Page 360 8 Programming Variable Designations for Function Blocks Instance name Value is Value is Function block definition name or assigned assigned instruction name Input Internal Output Input parameters Output parameters variable variables variable The specifications for variables in function blocks are given below. Variables Specification Number...
Page 361 8 Programming l Function Block Instance When you place an instance of a function block definition in a program or another function block, the function block definition is treated as a part of that program or function block. Function block definitions that are called from a program or another function block are called "instances".
Page 362 8 Programming Accessing Variables in a Function Block from Outside the Function Block You can access the input and output variables of a function block from outside the function block. Vari- ables are written as follows: InstanceName.VariableName Example: To Access Output Variable B of Function Block Instance FB1_Instance FB1_Instance.B FB1_Instance FB1_Instance.B...
Page 363 Functions do not have instance names. 8-1-7 Instructions Instructions are the smallest unit of the processing elements that are provided by OMRON for use in POU algorithms. There are FB instructions and FUN instructions. Programs and user-defined function blocks consist of a combination of these instructions.
Page 364 8 Programming Variables In the Safety CPU Unit, variables are used to exchange I/O information with external devices, to per- form data calculations, and to perform other processes. This section describes variable designations in detail. 8-2-1 Variables Variables store I/O data for exchange with external devices or temporary data that is used for internal POU processing.
Page 365 8 Programming Local Variables A local variable can be read and written only inside the POU (program or function block) in which it is defined. “Local variables” is the generic term for internal variables, input variables, output variables, and exter- nal variables.
Page 366 8 Programming Attribute Description Specification Default Initial Value Specify a value for the variable for This setting is re- FALSE for BOOL and one of the following situations: quired. SAFEBOOL variables, • When the power supply is turned and 0 for numeric vari- ables.
Page 367 8 Programming Type Definition Duration A data type that represents a time duration (days, hours, minutes, seconds, and milliseconds). Safety Data Types and Standard Data Types The Safety Control Unit classifies data types into the following two types to distinguish between safety data and standard data.
Page 368 8 Programming If you use the SAFEWORD, TIME, or SAFETIME data type for a global variable, you must set a constant. Bit String Data Format This section describes the data format for bit string data. "Bit 0" is the least significant bit of a bit string variable. Bit values are expressed as 1 or 0.
Page 369 8 Programming The values of variables with a Constant attribute cannot be written from instructions after the initial val- ue is set. If there is an instruction in a POU that attempts to write a value to a variable with the Con- stant attribute, an error will occur when the program is built.
Page 370 8 Programming Character Restrictions Multi- byte charac- Case Char- Maximum size Safety program- Applicable characters served sensi- acter (not including related name words com- tivity code NULL) patibili- Variable names Usable characters Refer to 127 bytes ASCII • (including POU in- Reserv sup- case...
Page 371 8 Programming • Local variable names and global variable names 8-19 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 372 8 Programming Constants (Literals) This section describes constants. 8-3-1 Constants The value of a variable changes depending on the data that is assigned to that variable. The value of a constant never changes. Unlike variables, constants are not stored in memory. You can use constants in the algorithm of a POU without the need to declare them.
Page 373 8 Programming Bit Strings l Bit String Data Notation Example Example • {da- word#16#0064 Data type: BYTE or WORD • ta_type}#{base Base: 2, 8, 10, or 16 }#{numeric_val- The normalizing processing omits the base of 10 and converts val- ues entered as base of 8 to decimal numbers. {da- word#100 This is interpreted as decimal data.
Page 374 8 Programming Programming Languages This section describes the programming languages in detail. Refer to 8-5 Programming Operations on page 8-27 to learn how to enter the programming languag- es on the Sysmac Studio. 8-4-1 Programming Languages The languages used to express the algorithms in a POU (program or function block) are called the programming languages.
Page 375 8 Programming Jump instruction Instructions or user-defined function blocks Networks Input parameters Exception RETURN Return instruction Jump label Exception: Output parameters The networks shown above include a Jump instruction that changes the top-to-bottom flow of execu- tion between networks, a label that shows the network to jump to, and a Return instruction. Refer to Execution Order of Safety Programs Written in the FBD Language on page 8-23 and Execu- tion Control on page 8-24 later in this manual, and also to the NX-series Safety Control Unit Instructions Reference Manual (Cat.
Page 376 8 Programming Block1 Block4 Block2 Block3 However, if there is a Return instruction in the middle of a program and the execution condition is met, the POU is ended and a return is made to the source of the call. No processes after Return instruction are executed.
Page 377 8 Programming Connecting Instructions or User-defined Function Blocks l Correct Connection Configurations Parameters and commands, or user-defined function blocks can be connected with a connecting line. Var1 Var2 The connecting line can connect two instructions or two user-defined function blocks. Multiple instructions or user-defined function blocks can be connected to a single instruction or user-defined function block.
Page 378 8 Programming Var1 Var1 8-26 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 379 8 Programming Programming Operations This section describes the procedures on the Sysmac Studio that you use to create safety programs for the Safety CPU Unit. 8-5-1 Programming Layer on the Sysmac Studio You use the Programming Layer with the Controller set to the Safety CPU Unit on the Sysmac Studio as shown below to create safety programs for the Safety CPU Unit.
Page 380 8 Programming Programming Header Description FunctionBlock0 A list of user-defined function blocks is displayed. There are no function blocks when you create a new project. FunctionBlock1 Double-click a function block to display it in the FBD editor and begin editing. You can change the name, delete, copy, paste, and cut function blocks.
Page 381 8 Programming The variable table and FBD editor are displayed in the Edit Pane. From here you can edit pro- grams. Refer to 8-5-3 Registering Variables on page 8-38 for information on how to register varia- bles, and 8-5-4 FBD Programming on page 8-46 for information on programming in the FBD editor.
Page 382 8 Programming The following table describes the items in the Property Dialog Box. Item Editing Description Name Possible This is the name that is currently set for the POU. Not possible This is the CRC data of the POU. You can also check the CRC data on the Change Tracking Tab Page. Version Possible This is the version information for the POU.
Page 383 8 Programming Enter a file name, and then click the Save Button. A program file with an .spg extension is saved. Precautions for Correct Use • Do not delete the program CRC data that is displayed after the program is exported. It is used to check the data when importing the program.
Page 384 8 Programming When you select the files to import, you can press theShiftKey orCtrlKey to select more than one file. Select the .spg file to import, and then click theOpenButton. When external variables are used in the program to import, the following dialog box is dis- played.
Page 385 8 Programming Check the CRC data, and click theOKButton. The program is imported and added to the project. Precautions for Correct Use After a function block is imported, the safety program in the project will be in an unvalidated state. Always execute safety validation again. Additional Information You can check the CRC data on theChange TrackingTab Page or Properties Dialog Box.
Page 386 8 Programming Precautions for Correct Use • Do not delete the function block CRC data that is displayed after the function block is export- ed. It is used for data confirmation when the function block is imported. You can check the CRC data on the Change Tracking Tab Page or Properties Dialog Box. •...
Page 387 8 Programming When a function block help file is imported, the following Import Dialog Box is displayed. If you select a help file (.pdf extension) with the same name as the imported function block, the specified file is copied to the save location for the user-defined help file. A dialog box to check the CRC data is displayed.
Page 388 Prepare a help file with the same name as the function block (extension .pdf). Save the help file in the specified folder. The default folder is C:\OMRON\Data\Lib\Safety. l Changing the Save Location for Help Files You can change the folder in which help files are saved.
Page 389 8 Programming For 64-bit OS: C:\Program Files (x86)\OMRON\Sysmac Studio\Sample\IEC 61131-10 XML\Safety • Sysmac Studio (64 bit) C:\Program Files\OMRON\Sysmac Studio\Sample\IEC 61131-10 XML\Safety The procedure to import the IEC 61131-10 XML files is as follows. Select IEC 61131-10 XML - Import from the Tools Menu.
Page 390 8 Programming Click the Execute Button. The data is imported and the global variables and POUs in the XML file are added to the project. If the project already has any global variable or POU with the same name, data is imported as you configured in the import options.
Page 391 8 Programming Field Description Restrictions Name Enter a name to use to identify the variable. Only single-byte alphanu- meric characters are al- lowed. Multi-byte characters, such as those used for Japa- nese, are not allowed. The maximum size is 127 bytes.
Page 392 8 Programming Enter values for each item, and then press the Enter Key. The variable is registered. Always set the variable name and the data type. Additional Information If there are no registered variables at all, the message Empty. Click here to add Item is dis- played.
Page 393 8 Programming Change the value or the settings, and then press the Enter key. The change is applied to the variable. • Entry candidates you can select are displayed as follows: Entry candidates are displayed in the Name, Data Type, and Initial Value cells. Entry candidates that match the characters in the entered text string are displayed as you edit the text string.
Page 394 8 Programming Precautions for Correct Use If you enter any invalid characters or out of range values, the cell is highlighted in pink. An error will occur when the program is built. A red icon "!" is displayed in the Multiview Explorer. The error message is displayed when the mouse cursor is moved over the cell where the error exists or over the exclamation icon.
Page 395 8 Programming The local variable table for the program or the local variable table for the function block is dis- played in the Edit Pane. • The local variable table for programs is shown below. • The local variable table for function blocks is shown below. Field Description Restrictions...
Page 396 8 Programming Additional Information The operating procedures for local variables are the same as the procedures used for global variables. Refer to 8-5-3 Registering Variables on page 8-38. Deleting Unused Variables You can delete unused variables in the Safety CPU Unit programs all at once. Select Delete Unused Variables from the Edit menu.
Page 397 8 Programming Select the checkbox(es) of the variable(s) to delete and click the OK Button. The following confirmation dialog is displayed. Check the contents and click the Yes Button. The unused variables are deleted. The window displays the number of deleted entries. Precautions for Correct Use •...
Page 398 8 Programming 8-5-4 FBD Programming With the Safety CPU Unit, you use the FBD language to express algorithms that are inside the POUs (programs and function blocks). You add and connect functions and function blocks in the FBD editor to build algorithms inside POUs (programs and function blocks). This section describes how to use the FBD editor.
Page 399 8 Programming Zooming In and Zooming Out of the FBD Editor Use the icons that are displayed in the toolbar to zoom in or zoom out of the FBD editor. Inserting FBD Networks There are three ways to insert an FBD network. l Method 1 Right-click the FBD network and select Insert Network Above from the menu.
Page 400 8 Programming l Method 2 Select the FBD network and press the Delete Key. The selected FBD network is deleted and the focus moves to the next network. Editing Comments for FBD Networks Use the following procedure to edit the comment for an FBD network. •...
Page 401 8 Programming Method Operation Method 1 Drag a FUN or FB from the Toolbox to an I/O terminal on the FUN or FB in the FBD editor, or to a new network where the words Start Here are displayed. Method 2 Right-click the FBD network, select Insert Function Block from the menu, and specify FUN or FB. Precautions for Correct Use Not all of the FUNs and FBs that you can use are displayed in the Toolbox.
Page 402 8 Programming Click in the FB name text box and press the Ctrl + Space Keys to display a list of the FUNs and FBs that you can enter. Select a FUN or FB from the list. Additional Information You can click the Input Assistance Button ( ) to the right of the FB name text box to display the Input Assistant Dialog Box.
Page 403 8 Programming If you drop the SF_Antivalent FB on the network where the words Start here are displayed, the FB is inserted in the new network. If you drop the SF_Antivalent FB on an input terminal, the FB is inserted before the input termi- nal.
Page 404 8 Programming Method Operation Method 1 Right-click the FUN or FB on the FBD network and select Delete from the menu. Method 2 Select the FUN or FB on the FBD network and press the Delete Key. Replacing a FB or FUN You can replace a FUN or FB with a different instruction without changing the input and output param- eters.
Page 405 8 Programming Adding Input Parameters to AND, OR, ADD, MUL, and MUX You can add input parameters to the AND, OR, ADD, MUL, and MUX instructions. Use one of the fol- lowing procedures. Method Operation Method 1 Drag Input from General in the Toolbox to the Append Input area in the instruction in the FBD edi- tor.
Page 406 8 Programming Changing the Output Terminals of a FUN or FB Use the following procedure to change the output terminals of a FUN or FB. Right-click an output terminal on a FUN or FB on the FBD network and select Set Output Connection from the menu.
Page 407 8 Programming • After the unused parameters of the FUN or FB are deleted, the network is as shown below. Updating the Input Parameters and Output Parameters of a FUN or Use the following procedure to display the input parameters and output parameters of a FUN or FB. Right-click a FUN or FB on the FBD network and select Update from the menu.
Page 408 8 Programming Editing Function Block Instance Variables Use one of the following methods to edit existing function block instance variables. If you specify a variable name that does not exist in the local variable table, that variable will be regis- tered as a local variable.
Page 409 8 Programming If you enter the variable name directly, a list of variable names that you can select from is displayed when you enter the first letter of the variable name. Use the Up and Down Keys to select the varia- ble name from the list, and then press the Enter Key.
Page 410 8 Programming Select the Select the internal or global variable Check Box and click the OK Button. If you select the above option, the following dialog box is displayed when a variable is registered automatically from the Safety FBD Editor. If you click the Internal variable Button, the variable is registered as an internal variable in the lo- cal variable table.
Page 411 8 Programming Drop point Position where function block is added “Start here” on the net- Input parameters and output parameters are added to the new network. work Input terminal The output parameter is inserted on a branch that is created before the input ter- minal.
Page 412 8 Programming Deleting Output Parameters Use the following procedure to delete output parameters. Right-click the Output parameters on the FBD network and select Delete from the menu. The selected output parameter is deleted. You cannot select multiple variables. Editing Output Parameters Use one of the following procedures to edit output parameters.
Page 413 8 Programming Method Operation Method 1 Right-click the Jump label and select Delete from the menu. Method 2 Select the Jump label and press the Delete Key. Editing Jump Labels Use the following procedure to edit jump labels. Select a jump label on the network and edit it. •...
Page 414 8 Programming Deleting Jump Instructions Use one of the following procedures to delete a Jump instruction. Method Operation Method 1 Right-click the Jump Instruction select Delete from the menu. Method 2 Select the Jump Instruction and press the Delete Key. The selected Jump instruction is deleted.
Page 415 8 Programming Method Operation Method 2 Select the Return instruction and press the Delete Key. The selected Return instruction is deleted. Viewing the Locations of Variable Definitions You can view where variables are defined. Use the following procedure. Right-click the variable and click Browse − Go To Definition from the menu. The focus moves to the location where the variable is defined (local variable).
Page 416 8 Programming Menu command Description Next Variable The display will jump to the next location where the selected variable is used. Previous Variable The display will jump to the previous location where the selected variable is used. Next Input The display will jump to the next location where the selected variable is used as a program input.
Page 417 8 Programming Method Description Method 1 Right-click on the FBD editor, and then select Network Comment List from the menu. Method 2 On the FBD editor, press the L Key. The list of network comment that are set in the current POU is displayed. Select a network comment to jump to the location where the selected network comment is set.
Page 418 8 Programming Color Selection for the FBD Editor You can change the display color of global variables that are displayed in the FBD editor. Select Option from the Tools menu. The Option Dialog Box is displayed. Select the Safety tab and click the button displayed at Color Selection. The Color Settings Dialog Box is displayed.
Page 419 8 Programming Select any color and click the OK button. In the Option Dialog Box, click the OK button. The color selection settings are applied. 8-5-5 Program Pattern Copy Program Pattern Copy is a function that allows you to easily replicate the FBD program having the same program pattern (logic part).
Page 420 8 Programming Right-click a row and select Program Pattern Copy from the menu. Or, press the Ctrl+Shift +V Keys. The following setting window is displayed. Set the copy counts, variable name generation rules, variable name to be changed, and offset value.
Page 421 8 Programming Item Description Variable Select a generation rule for the variable name. The rules you can select are as follows: • name gener- Add an offset value to the first number of the variable name. ation rules This rule generates another variable name by adding the offset value to the first num- ber contained in the variable name.
Page 422 8 Programming File Format for Customized Setting The file format for the customized setting is shown below. Since the setting file contains the CRC of the selected FBD network, use the CSV file saved with Output to template file. Name Description Remarks Source Variable Name...
Page 423 8 Programming In the Multiview Explorer, select Programming – POUs – Programs. Then, select a program you want to convert into a function block. Right-click the program and select Generate Function Block from the menu. The following message appears and the converted function block is added under Function Blocks, which is located below Programming –...
Page 424 8 Programming A check is performed on the programs and variables during this process. If there are any errors, the build is not performed and the errors are displayed in the Build Tab Page. Executing the Build Process Use one of the following procedures to execute the build process. Method Operation Method 1 Select Build Controller from the Project Menu.
Page 425 8 Programming Item Example Description Number of warn- Displays the total number of warnings. ings Error or warning Displays the errors or warnings in the number order in which they were found. Description Displays a description of the error or warning.
Page 426 8 Programming Selected item Scope of Searching and Replacing All items (text strings) Variable names, variable comments, FBD network comments, jump labels, and Jump instructions. Variable Variable names Instruction Function block instance names Search and Replace Pane Use one of the following procedures to display the Search and Replace Pane in place of the Toolbox.
Page 427 8 Programming Setting Items The setting items in the Search and Replace Pane are explained below. Setting Items Description • Search what Enter a search string. • You can select from previous search strings in the list. • Replace with Enter the string to replace the search string with.
Page 428 8 Programming l Wildcards Charac- Meaning Description Example Zero or more char- Searches for a text string that con- “new*” matches “newfile.txt”. acters tains a variable text string. Any single character Searches for a text string with a var- “A?C” matches “ABC”, “AdC”, and iable character.
Page 429 8 Programming Program Assignments The program assignment settings are used to assign the programs to the safety task and set the pro- gram execution order. The programs that are assigned to the task are executed in the specified order. Double-click Task Settings under Configurations and Setup in the Multiview Explorer. Click the Program Assignment Settings Button ( ) in Safety Task Settings Tab Page in the Edit Pane.
Page 430 8 Programming Set the task period for the safety task. Set the safety task period to a value that is within 100 ms of the minimum safety task period. 8-5-10 Variable Comment Switching Function The variable comment switching function is designed to switch the variable comment displayed in the safety program or on the variable table to another comment.
Page 431 8 Programming Editing a Variable Comment File Edit comments for variables in the exported CSV file. Open the CSV file on a spreadsheet application. Name Description Remarks Unique ID automatically assigned to a variable. Do not change this item. Table Type The type of the variable table is displayed.
Page 432 8 Programming The File Selection Dialog Box is displayed. Select an CSV file to import, and then click the Open Button. The Confirmation Dialog Box for the import is displayed. When you click the OK Button, the import function executes and replaces the comments in the project with the comments in the CSV file.
Page 433 8 Programming • Method 2: How to start the Edit Variable Comments Window from the variable table Select any variable in the variable table, and right-click the variable and select Edit Variable Comments. • Method 3: How to start the Edit Variable Comments Window from the FBD editor Select any variable in the FBD editor, and right-click the variable and select Edit Variable Comments.
Page 434 8 Programming The display contents of the Edit Variable Comments Window are as follows. Item Description Remarks POU Name This is the name of POUs (programs and function blocks) in which varia- (Cannot be bles are defined. The variables defined in the global variable table are dis- edited.) played as Global Variables.
Page 435 8 Programming Precautions for Correct Use • Project data, for which Comment 2 to Comment 4 are set by the Edit Variable Comments function, cannot be imported by using the Sysmac Studio Ver.1.28 and earlier. • If the content of Comment 1 was modified by the Edit Variable Comments function, the safe- ty validation status becomes unvalidated.
Page 436 8 Programming The project containing the imported variable comment file cannot be opened on Sysmac Studio Ver.1.28 and earlier because the switching variable comment function is not supported. When you de- lete variable comments in Comment 2 through Comment 4 in the following procedure, the project can be opened on Sysmac Studio Ver.1.28 and earlier.
Page 437 8 Programming Precautions for Correct Use Since the settings for Comment 2 and the subsequent comments are not included in the safety application data, they are not transferred to the Safety CPU Unit. Additional Information The settings for Comment 2 and the subsequent comments are downloaded when the safety application data is transferred, such as during the execution of validation check or transfer by synchronization.
Page 438 8 Programming Precautions for Correct Use If you use Sysmac Studio Ver.1.28 and earlier to upload safety application data from the con- troller and the Safety CPU Unit containing a downloaded variable comment file for the Safety CPU Unit, the data for Comment 2 and the subsequent comments are not restored because Ver.1.28 and earlier does not support the variable comment switching function.
Page 439 8 Programming Automatic Programming This section describes "automatic programming", which generates safety programs based on required specifications for the safety system using the Sysmac Studio. WARNING Programs generated by the automatic programming do not guarantee functional safe- ty. Before you perform validation test of the safety programs, complete debugging of the safety programs.
Page 440 8 Programming The following table shows values set to input variables of the function block. Input variable name Setting value Activate TRUE S_StartReset FALSE S_AutoReset Value specified for the reset type Manual: FALSE Auto: TRUE Reset Variable generated in the reset signal generation step MonitoringTime t#300ms Any other input variables Variable automatically generated based on the following naming rule:...
Page 441 8 Programming EMO_NC_S1_Out Contactor_KM1_KM2_In & LaserScanner_S3_Out l Output Signal Generation At this step, an SF_EDM function block is generated based on the Use EDM settings defined for Output Settings on the Automatic Programming Settings Tab Page. The internal variable, which is automatically generated at the generation of logical operation circuit, is used as an input signal for the SF_EDM function block.
Page 442 8 Programming 8-6-2 Automatic Programming Settings To execute the automatic programming, you need to specify the following items on the Automatic Pro- gramming Settings Tab Page. • Reset signal • Input signal • Output signal • Expected value of the output signal corresponding to the input signal You can open the Automatic Programming Settings Tab Page in either of the following procedures: •...
Page 443 8 Programming Let- Name Function Operation The operation panel is used to make settings for and execute the automatic programming. Panel Generate Button Generates a program using the automatic programming. Register Variables Button Registers the variables that are used for the automatic programming.
Page 444 8 Programming Let- Name Function Input Set- Specify a variable for the input signal used for automatic programming. tings In addition to the variable name, you need to specify a reset type and a linked safety func- tion block for the input signal. Variable Specify a variable name used as input signal for the pro- gram.
Page 445 8 Programming AGV stops also when the safety laser scanner detects someone or an object approaching to the safe- ty zone. At that time, enter the following variables of the safety laser scanner on the Automatic Programming Setting Tab Page. •...
Page 446 8 Programming The Automatic Programming Settings Tab Page is displayed. Set Basic Settings, Input Settings, Output Settings, and Expected Value Settings. On the operation panel of the Automatic Programming Settings Tab Page, click the Generate Button. Once a program is generated, the following dialog is displayed. Click the OK Button.
Page 447 8 Programming Program Generated through Automatic Programming Based on the example settings provided in 8-6-2 Automatic Programming Settings on page 8-90, the following program will be generated. 8-95 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 448 8 Programming OC_ResetSignal_0 OC_ResetSignal Reset_S2 Reset ResetSignal_Out Reset_S2_Out t#350ms ResetPulseWidth Emergency Stop Pushbutton S1 SF_EmergencyStop_0 SF_EmergencyStop TRUE Activate Ready EMO_NC_S1_Out EMO_NC_S1 S_EStopIn S_EStopOut FALSE S_StartReset Error FALSE S-AutoReset DiagCode Reset_S2_Out Reset Safety Laser Scanner S3 SF_ESPE_0 SF_ESPE TRUE Activate Ready LaserScanner_S3_Out LaserScanner_S3 S_ESPE_In...
Page 449 8 Programming Monitoring Memory Usage for Com- munication Control Unit This monitor shows the estimated memory usage for variables you are editing in Sysmac Studio. If the size of variables exceeds the memory size, transferring the variables to the Communication Control Unit generates an error in the Communication Control Unit.
Page 450 8 Programming Monitoring Memory Usage for Safety Control Unit You can display the memory usage of the safety control system and the safety network usage includ- ing the I/O data size. Precautions for Correct Use Check the memory usage when there are no building errors. If there is a building error, the memory usage is not displayed correctly.
Page 451 8 Programming Item Display content Related parameters • Program Displays the memory usage of Number of the connected Safety I/O Units • Memory the safety program. Number of CIP Safety connections, number of target I/O As- semblies • Number of functions blocks and functions in the safety pro- gram •...
Page 452 8 Programming Offline Debugging Offline debugging allows you to debug a program when you are not connected online to a Safety CPU Unit. You can debug on a Simulator to check control program logic before transferring the project to the Safety CPU Unit.
Page 453 8 Programming The Safety Simulation Pane is displayed below the Toolbox Pane on the right of the window. Click the Run Button in the Safety Simulation Pane. Or, select Run from the Simulation Menu. The following Connect to safety device Dialog Box is displayed. Note 1.
Page 454 8 Programming Click the OK Button. The following transfer confirmation dialog box is displayed. Click the Yes Button. The following device confirmation dialog box is displayed. Click the OK Button. Note You do not need to enter anything in the Password Box. After the Simulator is started and connected, the Online Indicator in status monitor is lit green.
Page 455 8 Programming Pausing Use the following procedure to pause a simulation. The values of variables are retained. Program execution stops at the start of the program. 8-9-2 Monitoring You can monitor the present values of variables in the FBD editor or Watch Tab Page to debug the safety programs.
Page 456 8 Programming Select the type of variables. The selected type of variables is displayed. The following types of variables can be selected: global variables, programs, and function blocks. Change the initial values of the variables. 8-9-6 Feedback Settings You can set input status that is linked to changes in output status, such as feedback inputs for safety relays.
Page 457 8 Programming Supported variable Item Description types Invert This check box is used to invert the input value. If you select this check box, the input value is inverted. Press the Insert Key in the feedback setting table, or right-click in the feedback setting table and select Create New from the menu.
Page 458 8 Programming The following Simple Automatic Test Tab Page is displayed. The setting areas of the Simple Automatic Test are configured as described in the following table. Item Name Function Simple The operation panel is used to make settings for and execute the Simple Automatic Test. You Auto- can perform the following operations.
Page 459 8 Programming Item Name Function Import Button Imports the settings for a Simple Automatic Test from a CSV file. If you import the settings, the current settings are overwrit- ten. Export Button Exports the current settings for the Simple Automatic Test to a CSV file.
Page 460 8 Programming M1 stops when safety door 1 (S3, S4) is opened. M2 stops when safety door 2 (S5, S6) is opened. Both M1 and M2 stop when the emergency stop pushbutton S1 is pressed. The settings for the Simple Automatic Test are derived from the following points. •...
Page 461 8 Programming Select Simulation - Simple Automatic Test from the menu. The Simple Automatic Test Tab Page is displayed. Set the Test Condition, Input Settings, Output Settings, and Expected Value Settings. Click the Run Button on the control panel on the Simple Automatic Test Tab Page. A precaution is displayed to ensure proper execution of the Simple Automatic Test.
Page 462 8 Programming You can check the progress of the Simple Automatic Test in the following dialog box. The Simulator stops when the test is completed. Click the OK Button. The Simple Automatic Test Result Window is displayed when the test is completed. If the re- sults show that the test has failed, correct the safety program or check the test settings.
Page 463 8 Programming Precautions for Correct Use The Simple Automatic Test is provided as a simple means to check the output signal results for the input signals. It may not be able to determine correct test results for complicated conditions or special cases. If necessary, check the program logic manually. Additional Information The actual test operations that are performed for the Simple Automatic Test are given in A-15 Execution Scenarios for the Simple Automatic Test on page A-105.
Page 464 8 Programming 8-112 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 465 Checking Operation and Actual Operation This section describes the procedures to perform before you can operate the Safety Network Controller. It describes the operating modes of the Safety CPU Unit, checking operation in DEBUG mode, and the procedures to perform safety validation. Procedures before Operation and Transferring the Required Data ..
Page 466 9 Checking Operation and Actual Operation 9-10 Security Settings ..................9-52 9-10-1 Setting the Safety Password ................. 9-52 9-10-2 Data Protection....................9-53 9-11 Performing Safety Validation and Operation ..........9-57 9-11-1 Performing Safety Validation ................. 9-57 9-11-2 Changing to RUN Mode ................9-59 9-11-3 Changing to PROGRAM Mode ..............
Page 467 9 Checking Operation and Actual Operation Procedures before Operation and Transferring the Required Data 9-1-1 Commissioning Procedure After you write the safety programs, use the following procedure to start operating the Safety Network Controller. Place the Sysmac Studio online with the Communication Control Unit. Transfer the configuration information to the Communication Control Unit and Safety CPU Unit.
Page 468 9 Checking Operation and Actual Operation Communication Safety CPU Unit Control Unit Setup and Safety CPU Unit Setup and Programming View Setting Tab Page Programming View Steps 1 and 2 Step 3 Steps 4 and 5 Step 6 Step 7 Checking operation Transferring the CPU and Changing to DEBUG mode...
Page 469 9 Checking Operation and Actual Operation Transfer method Transfer des- Safety Network Controller Settings tination When connected to Communication Control Unit Safety applica- Unvalidated safe- The safety application data is transferred automatical- Safety CPU tion data ty application da- ly when you change to DEBUG mode from the Safety Unit CPU Unit Setup and Programming View.
Page 470 9 Checking Operation and Actual Operation Transferring the Configuration Infor- mation This section describes how to start communications and transfer configuration information from the Sysmac Studio to the Communication Control Unit and the NX-series Safety CPU Unit. 9-2-1 Overview By transferring the CPU and Expansion Racks configuration information to the Communication Control Unit and Safety CPU Unit, you can connect the Sysmac Studio and Safety CPU Unit online and per- form debugging.
Page 471 9 Checking Operation and Actual Operation To go online with the Safety CPU Unit, use the following procedures. Select the Communication Control Unit from the Controller Selection Box in the Multiview Ex- plorer of Sysmac Studio, and open the Communication Control Unit Setup and Programming View.
Page 472 9 Checking Operation and Actual Operation Operating Modes of the Safety CPU Unit This section describes the operating modes of the Safety CPU Unit, state changes, and the functions that can be executed in each mode. 9-3-1 Startup Operating Mode and Changing the Operating Mode The operating mode of the Safety CPU Unit changes to PROGRAM mode or RUN mode after the power is turned ON, depending on whether the safety programs are validated, as shown in the follow- ing figure.
Page 473 9 Checking Operation and Actual Operation *2. When the operating mode changes from PROGRAM mode to DEBUG mode, the safety application data in the non-volatile memory of the Safety CPU Unit is deleted. *3. The Safety CPU Unit automatically enters PROGRAM mode if 30 seconds elapses after the connection to the Sysmac Studio is disconnected due to a damaged cable or any other reason.
Page 474 9 Checking Operation and Actual Operation Safety Out- Standard Safety Input Standard Input Status (Safe- Output (Ex- Operating mode (FSoE/CIP (Exposed Vari- ty CPU Sta- (FSoE/CIP posed Varia- Safety) able) tus) Safety) ble) Initializing Not received Not received Cleared Cleared Cleared PROGRAM mode Not received...
Page 475 9 Checking Operation and Actual Operation Relationship between Establishing Safety Communications and Ex- ecution of the Safety Programs The Safety CPU Unit starts execution of the safety programs at the same time the safety process data communications are established. The input data that is refreshed from the Safety Input Units is used for processing. 9-3-3 Executable Functions in Each Mode of the Safety CPU Unit The following table shows the executable functions in each mode of the Safety CPU Unit.
Page 476 9 Checking Operation and Actual Operation PRO- DEBUG mode RESTORE Initializing GRAM RUN mode Function mode STOPPED mode Monitoring for trouble- Not possi- Possible Possible Possible Possible Possible shooting Changing the safety pass- Not possi- Possible Not possi- Not possi- Possible Not possi- word...
Page 477 9 Checking Operation and Actual Operation Changing to DEBUG Mode This section describes how to place the Safety CPU Unit into DEBUG mode. When you change to DE- BUG mode, the safety application data is transferred to the Safety CPU Unit. WARNING Before you use the Sysmac Studio to change the operating mode of the Safety CPU Unit to DEBUG Mode, make sure that it is safe to do so at the destination for the safe-...
Page 478 9 Checking Operation and Actual Operation On the Safety CPU Unit Setup and Programming View, perform one of the following opera- tions. • Select Mode – DEBUG Mode from the Controller Menu. • Press the Ctrl + 2 Keys. • Click the DEBUG Mode Button on the toolbar. The following mode confirmation dialog box is displayed.
Page 479 9 Checking Operation and Actual Operation When you use the DEBUG mode for the first time, or when the safety password is not speci- fied, leave the Password field blank and click the OK Button. When a safety password is specified, enter the security password and click the OK Button. Refer to 9-10 Security Settings on page 9-52 for the procedure to set a safety password.
Page 480 9 Checking Operation and Actual Operation Checking External Device Wiring This section describes the functions that you use on the Sysmac Studio to check the wiring of external devices connected to the Safety I/O Units. You can obtain information on the Safety I/O Units to which external devices are connected and con- firm that the external devices are correctly wired by placing the Sysmac Studio online with the Safety CPU Unit and changing to DEBUG mode.
Page 481 9 Checking Operation and Actual Operation Description of the Monitor Tab Page • NX Unit Displays Monitor Display Description function Enabled The Safety I/O Unit is present in the actual configuration, and has its communications established. This shows that there is no error at the safety I/O terminals of the Safety I/O Unit.
Page 482 9 Checking Operation and Actual Operation Monitor Display Description function Disabled The Safety I/O Unit is present in the actual configuration, and has its safety process data communications disabled. This Safety I/O Unit is not subject to monitoring. Disabled The Safety I/O Unit is present in the actual configuration, and its safety process data communications are not estab- lished.
Page 483 9 Checking Operation and Actual Operation • Safety I/O Terminal Displays Click the Icon below the safety input I/O terminals to display the legend for the safety I/O termi- nal. 9-5-3 Troubleshooting Safety I/O Terminals This section describes troubleshooting errors that may occur at a safety I/O terminal because of incor- rect external device wiring or incorrect safety I/O settings.
Page 484 9 Checking Operation and Actual Operation For details on the safety I/O terminal errors, refer to 15-3-4 Safety I/O Unit Error on page 15-210. 9-5-4 Clear All Memory Operation for Safety I/O Units If an attempt to establish safety process data communications fails due to an illegal FSoE Slave Ad- dress, you must execute a Clear All Memory operation for the Safety I/O Units.
Page 485 9 Checking Operation and Actual Operation Right-click the Safety I/O Unit and select Clear All Memory from the menu. Click the Execute Button on the Clear All Memory Tab Page for the NX Unit. 9-21 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 486 9 Checking Operation and Actual Operation Functions for Checking Operation This section describes the functions that you use on the Sysmac Studio to check the operation on the Safety CPU Unit. You can check and adjust the operation of safety programs through an online connection between the Sysmac Studio and the Safety CPU Unit.
Page 487 9 Checking Operation and Actual Operation Starting and Stopping the Safety Programs Use the following procedure to change the Safety CPU Unit to DEBUG mode (RUN) or DEBUG mode (STOPPED). With the Safety CPU Unit in DEBUG mode, perform one of the following operations. •...
Page 488 9 Checking Operation and Actual Operation • The value of the variable is displayed in the frame on the right side of the variable name. “FALSE” is displayed with a black background, and “TRUE” is displayed with a blue background. Numeric values are displayed as decimal numbers.
Page 489 9 Checking Operation and Actual Operation You can right-click an column and use the displayed menu to display or hide the following items: Com- ment, Data type, AT, and Display format. YES: Editable, NO: Not editable Item Description Editing Device name The device name is displayed.
Page 490 9 Checking Operation and Actual Operation Deleting Variable Names from the Watch Tab Page Right-click the variable name to delete in the Watch Tab Page and select Delete from the menu. Or, press the Delete Key to delete the variable name directly. The variable name and the row it was displayed on are deleted.
Page 491 9 Checking Operation and Actual Operation Each double-click toggles the temporary value. Select Write Values from the Controller Menu. The temporary value is removed and reflected as the present value. Example: The present value of variable a is set to TRUE. Set to TRUE.
Page 492 9 Checking Operation and Actual Operation Select the Prepare a new value for the next write or force operation Option and enter the new value. Example: This example changes the value to 100. The present value is displayed. Enter the desired value here. Click the OK Button.
Page 493 9 Checking Operation and Actual Operation Additional Information You can replace more than one present value in a single operation. To do this, set multiple present values with temporary values, and then select Write Values from the Controller Menu. l Changing Present Values on a Watch Tab Page Use the following procedure to change present values from the Watch Tab Page.
Page 494 9 Checking Operation and Actual Operation Forced Refreshing Forced refreshing allows you to refresh external inputs and outputs with user-specified values from the Sysmac Studio to debug the system. You execute this in the FBD editor or Watch Tab Page. Forced refreshing is executed for the specified variables.
Page 495 9 Checking Operation and Actual Operation A temporary value appears in <> on the right side of the present value. This indicates that the temporary value is available for forced refreshing. Temporary value is displayed Each click toggles the temporary value. Select Force Values from the Controller Menu.
Page 496 9 Checking Operation and Actual Operation Click the OK Button. The Prepare Value Dialog Box closes and the value changes to a temporary value. A temporary value appears in <> on the right side of the present value. Temporary value is displayed To cancel the temporary value, click the present value of the variable again.
Page 497 9 Checking Operation and Actual Operation The letter F in dark red is displayed Additional Information You can use forced refreshing for up to 256 variables at the same time. l Procedure to Cancel All Forced Refreshing from the FBD Editor Use the following procedure to batch-clear forced refreshing.
Page 498 9 Checking Operation and Actual Operation To clear forced refreshing without changing the present values, select the Release the force, without modifying the value Option, and then click the OK Button. <UnforceRestore> is displayed Select Force Values from the Controller Menu. The forced refreshing is cleared individually.
Page 499 9 Checking Operation and Actual Operation Item Description (a) Lock Button Click this button to lock the display of the referenced element and cross refer- ence list. Click the button again to release the lock. (b) Reference Tar- The referenced element that is currently selected is displayed. Or, you can direct- get field ly enter a variable name or variable member name as the reference target in this field.
Page 500 9 Checking Operation and Actual Operation Areas for Cross Reference The following table shows the areas where the usage locations of referenced element are detected. The following areas are displayed in the cross reference list if the referenced element is used in the areas.
Page 501 9 Checking Operation and Actual Operation Online Functional Test This section explains how to perform Online Functional Test to check operation of safety functions of the safety system using the Sysmac Studio. Connect the Sysmac Studio and the Safety CPU Unit online, and operate the Safety Input Units and the reset switch to confirm that the output device is op- erating normally, and then output the test result.
Page 502 9 Checking Operation and Actual Operation The configuration of the Online Functional Test setting tab page is as follows: Let- Name Function Operation panel The operation panel is used to make settings for and execute the online functional test. Run Button Starts an online functional test.
Page 503 9 Checking Operation and Actual Operation Let- Name Function Export – CSV File Output Exports the current online functional test set- tings to a CSV file. Export – Export to Auto- Exports the current online functional test set- matic Programming tings to the automatic programming settings.
Page 504 9 Checking Operation and Actual Operation Let- Name Function Expected Value Settings Displays the matrix of the variables specified in the input setting and output setting. Sets the values subject to test and the expected value of the output variables for each input variable. The expected values that you can set for output variables have the following meanings: •...
Page 505 9 Checking Operation and Actual Operation 9-7-2 Online Functional Test Execution Procedure Use the following procedure to execute the Online Functional Test. Place the Sysmac Studio online with the Safety CPU Unit. Place the Safety CPU Unit in DEBUG mode. Refer to 9-4 Changing to DEBUG Mode on page 9-13 for a detailed procedure.
Page 506 9 Checking Operation and Actual Operation Check the precautions for executing the Online Functional Test and select Yes. Operate the device as instructed on the screen. When you complete the preparations for start- ing a test, select OK. Operate the device as instructed on the screen. Execute a shutoff test. The operating instructions for the device to be tested will appear.
Page 507 9 Checking Operation and Actual Operation Operate the device as instructed on the screen. Execute a restore test. The operating instructions for the device to be tested will appear. Operate the device as in- structed on the screen and specify TRUE for the variable assigned to the input device. Make sure that the device was restored normally.
Page 508 9 Checking Operation and Actual Operation • Reset Type: Auto The Controller checks if the variables assigned to all the output devices are set to TRUE when detecting that the specified variables are set to TRUE. The test result appears in the dialog shown below.
Page 509 9 Checking Operation and Actual Operation Check the operation of function reset. It is displayed only for Manual Reset. The Controller checks if the variables assigned to all the output devices are set to TRUE when detecting that the variable assigned to the reset switch changed from FALSE to TRUE, and then FALSE again.
Page 510 9 Checking Operation and Actual Operation Export or print the test results if a CSV file if needed. Precautions for Correct Use The Online Functional Test allows you to perform basic operation check by executing manual reset or auto reset. The test result may not be accurate for complex conditions or special cases. Perform advanced operation check separately if needed.
Page 511 9 Checking Operation and Actual Operation Search FB Where Safety Output Is This section describes the function for searching for a function block instance that causes safety out- put to be turned off in the safety program currently being executed by using Sysmac Studio. Using this function, you can identify a function block instance where output has been turned off after an input signal had been disrupted or an error had occurred, without analyzing a safety program.
Page 512 9 Checking Operation and Actual Operation Letter Name Function Search re- This section lists function block instances where safety output is turned off in the safety sults program currently being executed. POU Name Displays the name of the POU where relevant function block in- stance is being executed.
Page 513 9 Checking Operation and Actual Operation Letter Name Description Safety Function block Displays search settings for safety function blocks. search settings table Search settings are predefined for available safety function blocks by de- fault. Active/Inactive Select the check box to include the function block as a search target, or clear the selection of the check box to exclude it.
Page 514 9 Checking Operation and Actual Operation 9-50 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 515 9 Checking Operation and Actual Operation Node Name This section describes the node name setting for the Safety CPU Unit. l Node Name Application The node name is a unique name that you assign to each Safety CPU Unit within the project. This helps you recognize the correct Safety CPU Unit when you begin online operations.
Page 516 • If you lose the password set to the Safety CPU Unit, you will no longer be able to make changes to the Safety CPU Unit. Take caution not to lose the password. If the password is lost and needs to be reset, contact your OMRON representative. l Characters Allowed for Passwords The following characters can be used for the password.
Page 517 9 Checking Operation and Actual Operation Item Description Number of Characters 32 characters max. Applicable Characters Single-byte alphanumeric characters (case sensitive) l Setting a New Safety Password Go online with the Safety CPU Unit and then select Security − Set Safety Password from the Controller Menu on the Safety CPU Unit Setup and Programming View.
Page 518 9 Checking Operation and Actual Operation l Data That Can Be Protected The following table lists the data that you can protect from being displayed and changed. Display pro- Change pro- hibition hibition Target data Dis- Chan Dis- Chan play play Program Program names...
Page 519 9 Checking Operation and Actual Operation Precautions for Correct Use • You will not be able to temporarily release protection or remove the protection setting if you forget the password. Protection settings are also transferred for synchronization operations. If you forget the passwords for protected data that was transferred to the Controller, you will no longer be able to display or change the protected data.
Page 520 9 Checking Operation and Actual Operation Select the data for which to release protection, and then select Security − Set/Release Data Protection from the Controller Menu. Or right-click the data for which to release protection, and select Security − Set/Release Data Protection from the menu. The Temporary Release of Data Protection Dialog Box is displayed.
Page 521 9 Checking Operation and Actual Operation 9-11 Performing Safety Validation and Op- eration This section describes the procedure for safety validation testing. Safety validation testing is used to confirm that all safety functions and all Safety Control Units meet the required specifications of the safety system.
Page 522 9 Checking Operation and Actual Operation Connect the Sysmac Studio online with the Safety CPU Unit, place the Safety CPU Unit in DE- BUG mode, and select Safety Validation from the Controller Menu. The following confirmation dialog is displayed. Click the Yes button. After the validated safety programs are saved to non-volatile memory in theSafety CPU Unit, the following dialog is displayed to indicate the process was completed, and then the Safety CPU Unit enters the state shown below.
Page 523 9 Checking Operation and Actual Operation The following window is displayed. The contents of each item are described in the following table. Item Description Last Modified (UTC) The time on the computer on which safety validation has been performed. Last Modified Signature Displays the signature code (four-digit hexadecimal number) of the validated safety program.
Page 524 9 Checking Operation and Actual Operation Check the node name, and click the Yes Button. A Mode Change Confirmation Dialog Box is displayed. Click the OK Button to change the Safety CPU Unit to RUN mode. 9-11-3 Changing to PROGRAM Mode If you need to change the safety programs, or if you need to change the operating mode of the Safety CPU Unit from RUN mode to DEBUG mode, you must first change to PROGRAM mode.
Page 525 9 Checking Operation and Actual Operation The following dialog box is displayed. Click the OK Button. 9-61 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 526 9 Checking Operation and Actual Operation 9-12 Starting and Stopping the Safety Ap- plication Monitoring This section describes how to start and stop the monitoring function for variables and the Safety I/O Unit by using Sysmac Studio. This function can be executed only when the Safety CPU Unit is in the RUN mode.
Page 527 9 Checking Operation and Actual Operation To Stop Monitoring: • On the menu bar, selectController-Stop Monitoring. • Click theStop MonitoringButton on the toolbar. 9-12-2 Changing the Monitoring Options for the Safety Application You can select whether you will start the safety application monitoring when Sysmac Studio is con- nected online.
Page 528 9 Checking Operation and Actual Operation 9-13 Uploading Configuration Information and Safety Application Data This section describes how to transfer the configuration information and safety programs from the Safety Control Units to the computer with the Sysmac Studio. 9-13-1 Outline You can transfer the settings of the Safety Control Units and the safety programs from the Safety Con- trol Units to the computer.
Page 529 9 Checking Operation and Actual Operation Set the communications path to the Communication Control Unit. Select Online from the Controller Menu. Or, click the Go Online Button ( ) in the toolbar. Select Synchronization from the Controller Menu. In the Synchronization Window, clear the selections of the following check boxes. •...
Page 530 9 Checking Operation and Actual Operation 9-14 Transferring Safety Application Data This section describes how to transfer safety application data that was validated in the procedure specified in the preceding section 9-11 Performing Safety Validation and Operation on page 9-57 to another Safety CPU Unit.
Page 531 9 Checking Operation and Actual Operation Select Synchronization from the Controller Menu. In the Synchronization Window, clear the selections of the following check boxes. • Do not transfer the following. (All the items are not to be synchronized.) • NX Unit application data on the CPU Rack Click the Transfer to Controller Button.
Page 532 9 Checking Operation and Actual Operation 9-15 Monitoring Controller Status This section describes how to display the status of Safety CPU Unit that is connected to Safety CPU Unit online or the status when the Simulator is connected. Controller Status Monitor Control status monitoring is used to display the status of the connected Safety CPU Unit or Simulator in the Controller Status Pane.
Page 533 9 Checking Operation and Actual Operation Information Displayed information and indicator colors Communications Status Displays the communications status between the Safety CPU Unit and Sys- mac Studio or displays the Simulator startup status. • Normal communications: Lit green • Communications error: Flashing red Error Status Displays the error status of the Safety CPU Unit or Simulator.
Page 534 9 Checking Operation and Actual Operation 9-16 Restarting and Clearing All Memory 9-16-1 Restarting Restarting allows you to restart the CPU Rack that includes the Safety CPU Unit and Safety I/O Units without cycling the unit power supply to the Communication Control Unit. Precautions for Safe Use If the safety application data in the Safety CPU Unit is validated, be careful when you execute the Restart operation because the Safety CPU Unit will automatically start in RUN mode.
Page 535 9 Checking Operation and Actual Operation Precautions for Correct Use • The memory in the Safety CPU Unit is not cleared even when you perform the Clear All Memory operation for controllers. To clear the memory of the Safety CPU Unit, use the Clear All Memory operation for NX Units.
Page 536 9 Checking Operation and Actual Operation Click the Execute Button. The Clear All Memory Confirmation Dialog Box is displayed. Click the Yes Button. The Authentication Dialog Box is displayed. Enter the password, and click the OK Button. If a password is not set, leave the box empty and click the OK Button.
Page 537 9 Checking Operation and Actual Operation Click the OK Button. After memory is cleared, the Memory All Cleared Dialog Box is displayed. l Clear All Memory Operation for Controllers Go online, and select Controller – Clear All Memory from the Communication Control Unit Setup and Programming View.
Page 538 9 Checking Operation and Actual Operation 9-74 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 539 Calculating Safety Reaction Times This section describes how to calculate safety reaction times for Safety Control Units. 10-1 Safety Reaction Time ................... 10-2 10-1-1 Calculating the Safety Reaction Time ............10-2 10-1-2 Verifying Safety Reaction Times..............10-4 10-2 Safety Task....................10-5 10-2-1 Safety Task....................
Page 540 10 Calculating Safety Reaction Times 10-1 Safety Reaction Time This section describes the safety reaction time (i.e., the safety response performance) of Safety Con- trol Units. The safety reaction time is the maximum time required to turn OFF an output in consideration of possi- ble failures and breakdowns over safety chains .
Page 541 This is the response time that is required for a safety sensor or switch, such as a light cur- sensor/ tain, to turn OFF. The value is defined for each sensor or switch. switch re- Use the following values when an OMRON Special Safety Input Device is connected to a sponse Safety Input Unit. time...
Page 542 10 Calculating Safety Reaction Times Precautions for Correct Use • If the safety task period changes due to changes in the safety program or other reasons, re- calculate the safety reaction times. • To calculate the safety reaction times, add the "delaying influences from the input filter delay settings", the "safety program function block delay settings", and the "safety program loopback connections".
Page 543 10 Calculating Safety Reaction Times 10-2 Safety Task This section describes the safety task of the Safety CPU Unit. The safety task period of the Safety CPU Unit affects the safety reaction times. 10-2-1 Safety Task The safety task is used to assign an execution condition to a series of processes, such as for data exchange with the Safety I/O Units and the CIP Safety target device, as well as for safety program execution.
Page 544 10 Calculating Safety Reaction Times Precautions for Correct Use If you change any of the following values, the minimum safety task period will change. Check the minimum safety task period again. • Safety program execution time (This time depends on the sizes of the programs and the func- tion blocks that are used.) •...
Page 545 10 Calculating Safety Reaction Times 10-3 FSoE Watchdog Timer This section describes the FSoE watchdog timers. 10-3-1 FSoE Watchdog Timers An FSoE watchdog timer is used for timeouts in safety process data between the Safety CPU Unit and Safety I/O Units. The FSoE watchdog timers affect the safety reaction times.
Page 546 10 Calculating Safety Reaction Times Double-click the cell in the FSoE watchdog timer Column for the Unit to change and set the desired FSoE watchdog timer value. 10-8 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 547 10 Calculating Safety Reaction Times 10-4 EPI (Data Packet Interval) EPI stands for Expected Packet Interval and refers to the transmission interval of safety data packets in the CIP Safety communications. The EPI affects the safety reaction time. If you specify a smaller EPI, it shortens the network reaction time and the safety reaction time, but it increases the communications load on the EtherNet/IP communications port.
Page 548 10 Calculating Safety Reaction Times 10-10 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 549 Communications Load This section describes how to adjust communications load in order to realize high- speed and stable communications. 11-1 Adjusting the Communications Load............11-2 11-1-1 Checking Bandwidth Usage for Tag Data Links ..........11-3 11-1-2 Checking the Device Bandwidth Usage of the CIP Safety Routing....11-4 11-1-3 Relationship between the Number of Packets Used per Second and Packet Intervals....................11-5...
Page 550 11 Communications Load 11-1 Adjusting the Communications Load In an Ethernet network using an Ethernet switch, the network bandwidth is not shared by all of the no- des, and independent transmission paths are established between individual nodes through the Ether- net switch.
Page 551 11 Communications Load Particularly when using an Ethernet switch that does not support multi-cast filtering, the settings must be made considering that multi-cast packets will be sent even to nodes without connection settings. Additional Information If the connection type is set to Multi-cast connection in the connection settings of the CIP Safety or the tag data links, multi-cast packets are used.
Page 552 11 Communications Load Item Description Usage of Capacity (without The ratio of the device's packet usage to the maximum number of packets per Multicast filter) second. Number of packets used per second / Number of maximum packets per second The values outside parentheses are for when multi-cast filtering is used. The values inside parentheses are for when multi-cast filtering is not used.
Page 553 11 Communications Load Item Meaning Displays the number of packets used for each CIP Safety connection per sec- ond and the total sum of used packets Mbit/s Displays the network bandwidth used for each CIP Safety connection. 11-1-3 Relationship between the Number of Packets Used per Second and Packet Intervals The usage rate to the maximum number of packets per second can be adjusted by modifying the set- tings for the packet interval (PRI) for the tag data link or the packet interval (EPI) for the CIP safety...
Page 554 11 Communications Load Ethernet Switches without Multicast Filtering • Does the total number of packets transmitted to the built-in EtherNet/IP port per second exceed the maximum number of packets allowed per second? If it exceeds the maximum number, check and modify the connection settings, including RPI and EPI values.
Page 555 Safety Unit Restore This section describes the procedures to execute the Safety Unit Restore. 12-1 Safety Unit Restore ..................12-2 12-1-1 Generate Safety Unit Restore File Function..........12-2 12-1-2 Safety Unit Restore Function ................ 12-3 12-1-3 Specifications of a Safety Unit Restore File ..........12-5 12-1 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 556 12 Safety Unit Restore 12-1 Safety Unit Restore The safety unit restore is a function designed to transfer safety programs and settings to Safety CPU Unit via an SD Memory Card. You can use the Safety Unit Restore in the following instances. Item Application Program and setting changes...
Page 557 12 Safety Unit Restore Startup the Sysmac Studio. Open a project which contains the validated safety application da- From the Controller selection in the Multiview Explorer, select Safety CPU Unit, then select Tools – Generate Safety Unit Restore File from the menu. The Generate Safety Unit Restore File Dialog Box is displayed.
Page 558 12 Safety Unit Restore Precautions for Correct Use To execute the Safety Unit Restore, you need to execute the restore function for the Communi- cation Control Unit as well. In addition, you need to generate a safety backup file and a backup file of the Communication Control Unit from a same project or from a same physical unit from which a project is transferred.
Page 559 12 Safety Unit Restore Processing stage Procedure and Display Wait for Completion Com- The safety signature for the settings information transferred to the Safety CPU mand Unit is repeatedly shown as a four-digit hexadecimal number in the seven-seg- ment indicators of the Safety CPU Unit. (Example: Supposing the safety signature is 0xABCD) Check the safety signature.
Page 560 12 Safety Unit Restore l File Name File File name Safety Unit Restore File SLSystem.dat 12-6 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 561 Backup Functions of the Commu- nication Control Unit This section describes the backup functions for the settings in an NX-series Communi- cation Control Unit. There are different types of backup functions that handle different data or different storage locations. First an overall description of the backup functions is provided followed by descriptions of the individual functions.
Page 562 13 Backup Functions of the Communication Control Unit 13-1 The Backup Functions The following three functions are supported for data backup for an Communication Control Unit. Note that these functions are not designed to back up the Safety Control Unit settings. Refer to Sec- tion 12 Safety Unit Restore on page 12-1 for details on the restore operations of the Safety Control Unit.
Page 563 13 Backup Functions of the Communication Control Unit This section describes the procedure for performing a backup, restore or compare operation of the SD Memory Card using Communication Control Unit front-panel switch. Backup Procedure l Preparations Insert the SD Memory Card into the Communication Control Unit. Set pins 1 to 4 on the DIP switch on the Communication Control Unit as follows: 1: OFF, 2: OFF, 3: ON, and 4: OFF.
Page 564 13 Backup Functions of the Communication Control Unit l Ending the Restoration Procedure Press the SD Memory Card power supply switch to turn OFF the SD PWR indicator. Turn OFF the power supply to the Communication Control Unit. l Starting Normal Operation Remove the SD Memory Card.
Page 565 13 Backup Functions of the Communication Control Unit Data group Data items Data and settings *1*2 Unit Configuration and Unit Setup I/O Map Controller Setup (Operation Settings and Built-in EtherNet/IP Port Set- tings) Tag Data Link Tables Controller name Operation authority verification Built-in clock (time zone setting) Data (global variables) IP address of the built-in...
Page 566 13 Backup Functions of the Communication Control Unit Operating method Communi- cation Con- Function name Description Reference Sysmac trol Unit Studio Front-panel DIP Switch SD Memory Backing up The Communication Control Available Availa- 13-2-1 Backup (Controller Card Back- data Unit data is saved in a back- to SD Memory Card) on up file on the SD Memory page 13-10...
Page 567 13 Backup Functions of the Communication Control Unit Operating meth- Com- muni- cation Con- Function name Description Reference trol Sysmac Unit Studio Front- panel Switc Sysmac Studio Backing The Communication Control Available 13-4-1 Backup (Controller to Controller up data Unit data is saved in a backup Computer) on page 13-16 backups file on the computer.
Page 568 13 Backup Functions of the Communication Control Unit Data group Data and Settings IP address Present val- Units and Type of backup function ues of varia- slaves set- of built-in bles tings EtherNet/IP *1*2 port Sysmac Studio Controller Backing up data backups Restoring data Verifying data...
Page 569 13 Backup Functions of the Communication Control Unit Computer Communication Control Unit NX Unit Communication Control Unit NX Unit Applicable range of the SD Memory Card backup, EtherNet/IP slaves and Sysmac Studio Controller backup functions 13-9 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 570 13 Backup Functions of the Communication Control Unit 13-2 SD Memory Card Backups You can use SD Memory Cards to back up, restore, and verify the Communication Control Unit data. SD Memory Card Communication Control Unit Backing up data Restoring data Data to be backed up Verifying data...
Page 571 13 Backup Functions of the Communication Control Unit Processing Contents • This backup operation processes all data groups. • When you back up data, the backup file, restore command file, and automatic transfer command file are created in the specified directory on the SD Memory Card. •...
Page 572 13 Backup Functions of the Communication Control Unit 13-2-2 Restore (SD Memory Card to Controller) You can transfer the data in a backup file on the SD Memory Card in the Communication Control Unit to the Communication Control Unit. You can perform this operation using the Communication Control Unit front-panel DIP switch. The transfer starts when the power supply is turned ON with the Communication Control Unit front- panel DIP switch.
Page 573 13 Backup Functions of the Communication Control Unit Procedure l Backing Up Data with the Communication Control Unit Front-panel DIP Switch Processing stage Procedure Start command Turn ON the power supply to the Communication Control Unit with the DIP switch 1 to 4 set as follows: 1: OFF, 2: OFF, 3: ON, and 4: ON.
Page 574 13 Backup Functions of the Communication Control Unit Procedure l Backing Up Data with the Communication Control Unit Front-panel DIP Switch Processing stage Procedure Start command The verification operation starts when the SD Memory Card power supply switch is pressed for 3 seconds with the DIP switch pins set as follows: 1: OFF, 2: OFF, 3: OFF, and 4: OFF.
Page 575 13 Backup Functions of the Communication Control Unit 13-3 Disabling Backups to SD Memory Cards You can disable the backup function from writing data to the SD Memory Card This function will help you protect user assets. The function to disable backups to SD memory cards applies to the following two backup actions: •...
Page 576 13 Backup Functions of the Communication Control Unit 13-4 Sysmac Studio Controller Backups You can use the Sysmac Studio to back up, restore, and verify the Communication Control Unit data from a computer. Sysmac Studio Communication Control Unit Backing up data Restoring data Data to be backed up...
Page 577 13 Backup Functions of the Communication Control Unit Data group Backing up condition Event logs CPU Unitmust be selected. Units and slaves settings NX Units on the CPU Rack must be selected. Values of the IP address switch ofCommunication Control Unitare not included for the data backup func- tion.
Page 578 13 Backup Functions of the Communication Control Unit Data group Restoring condition Units and slaves settings The NX Units on the CPU Rack must be selected. Values of the IP address switch of Communication Control Unit are not backed up. Please set them manual- ly as required.
Page 579 13 Backup Functions of the Communication Control Unit Data group Verification condition Units and slaves settings NX Units on the CPU Rackmust be selected. Values of the IP address switch ofCommunication Control Unitare not included for the data backup function. Set these values manually as required.
Page 580 13 Backup Functions of the Communication Control Unit 13-5 Importing and Exporting Sysmac Stu- dio Backup File Data You can create or read from a backup file in the specified directory on the computer from the Sysmac Studio project without using the Communication Control Unit. This following data is processed: Data group User program and settings...
Page 581 13 Backup Functions of the Communication Control Unit 13-6 Backup Functions when NX Units are Connected For NX Units on the Communication Control Unit, you can use the SD Memory Card backup functions and the Sysmac Studio Controller backup functions. This section provides information on the data that is backed up, backup support according to the Com- munication Control Unit status, and restore conditions when NX Units are connected to the Communi- cation Control Unit.
Page 582 13 Backup Functions of the Communication Control Unit 13-6-3 Conditions for Restoring NX Unit Data on the Communication Control Unit The following conditions must be met before you restore the backup data to the NX Units on the Com- munication Control Unit. •...
Page 583 13 Backup Functions of the Communication Control Unit 13-7 Backup-related Files This section describes the specifications of the backup-related files. 13-7-1 Types of Backup-related Files There are four types of files that are related to backup functions: backup files, restore command files, automatic transfer command files, and verification results files.
Page 584 13 Backup Functions of the Communication Control Unit File Creation Timing and Created Directories Function Procedure Creation timing Created directory SD Memory Card Communication Control Unit When backup is Root directory on the SD Mem- backups Front-panel DIP Switch executed ory Card SD Memory Card Window in When backup is...
Page 585 13 Backup Functions of the Communication Control Unit File contents (defaults when the file is created) Description ; --- User Program and Configuration. --- Not used in Communication Control ; Always select "yes". Unit. UserProgram=yes ; --- IP Address of Built-in EtherNet/IP Port Settings. --- IP address of built-in EtherNet/IP port ;...
Page 586 13 Backup Functions of the Communication Control Unit How to Check the Verification Results The verification results files contain the results of comparing the Communication Control Unit data and the data in a backup file on the SD Memory Card in the Communication Control Unit for each data group.
Page 587 13 Backup Functions of the Communication Control Unit You can check the verification results in the portion that gives the verification results for the NX Units. Result=Matched indicates a data group for which no differences were found. Result=Not matched indi- cates a data group for which differences were found.
Page 588 13 Backup Functions of the Communication Control Unit 13-8 Compatibility between Backup-relat- ed Files The files may not be compatible if you back up and restore data under different conditions. The files may not be compatible in these three cases: •...
Page 589 13 Backup Functions of the Communication Control Unit 13-9 Functions that cannot be Executed during Backup Functions The following functions cannot be executed at the same time as any of the backup functions. Do not execute any backup function while the Communication Control Unit is executing any of these func- tions.
Page 590 13 Backup Functions of the Communication Control Unit 13-30 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 591 Safety Data Logging This section describes the Safety Data Logging function. 14-1 Outline of the Safety Data Logging Function ..........14-2 14-2 Creating a Safety Data Logging Settings File with the Sysmac Studio ......................14-4 14-3 Safety Data Logging Operation Procedure..........14-6 14-4 Checking the Logging Status..............
Page 592 14 Safety Data Logging 14-1 Outline of the Safety Data Logging Function The safety data logging is a function that records exposed variables and device variables used in the safety program of the Safety CPU Unit in a chronological order. The function logs the specified varia- bles in the volatile memory and saves the log data into the SD Memory Card before and after the trig- ger condition is met.
Page 593 14 Safety Data Logging l Start Trigger When the following condition is met in the logging standby state, the start trigger is activated and the unit enters into the logging in-progress state. • The service switch is pressed for operation after all the safety master connections were estab- lished.
Page 594 14 Safety Data Logging 14-2 Creating a Safety Data Logging Set- tings File with the Sysmac Studio The Sysmac Studio allows you to create a safety data logging settings file. Safety validation must be completed for the safety application data. Refer to 9-11 Performing Safety Validation and Operation on page 9-57 for details on the safety validation of safety application data.
Page 595 14 Safety Data Logging Item Description Logging Settings ID An ID number is specified to associate a logging settings file with relevant log files as its logging result. This ID number is used as part of their file names so that the safety data logging settings file and the corresponding log files can be identified.
Page 596 14 Safety Data Logging 14-3 Safety Data Logging Operation Proce- dure Use the following procedure to execute the safety data logging function: Find the SD Memory Card that contains the safety data logging settings file in the specified folder. Insert the SD Memory Card into the SD Card Slot of the Communication Control Unit to which the Safety CPU Unit is connected.
Page 597 14 Safety Data Logging 14-4 Checking the Logging Status You can verify the logging status in the following methods: • Checking the seven-segment indicator of the Safety CPU Unit. • Checking with system-defined variables 14-4-1 Checking the Seven-segment Indicator The logging status is displayed with the right and left dots of the seven-segment indicator of the Safety CPU Unit as shown below.
Page 598 14 Safety Data Logging Variable Meaning Function Data Type Member name .IsStart Safety Data Logging Busy The value becomes 1 (ON) BOOL Flag when starting the safety data logging, and 0 (OFF) when stopping the safety data logging. .IsComplete Safety Data Logging Com- The value becomes 1 (ON) BOOL pleted Flag...
Page 599 14 Safety Data Logging 14-5 Log File Specifications Log files are stored in the SD Memory Card. A log file is saved as a comma-delimited text file with a csv extension. Log file specifications are described below. Item Specifications SFLog_<N>_<ID>_<SIGNATURE>_<Date of output>_<Time of output>.csv *1 *2 Log file name File location...
Page 600 14 Safety Data Logging Logging completion condition: VarX changes to FALSE Logging target: Var1(SAFEBOOL), Var2(SAFEBOOL), Var3(WORD) Reason for logging stopped: The trigger condition is met. (VarX changes to FALSE.) The condition was met when No2205 was read in the sampling. "index","time","condition","Var1:SAFEBOOL","Var2:SAFEBOOL","Var3:WORD"...
Page 601 Troubleshooting This section describes the event codes that are recorded when errors occur, and how to check and troubleshoot errors. 15-1 Operation after an Error ................15-2 15-1-1 Overview of Communication Control Unit Status .......... 15-2 15-1-2 Fatal Errors ....................15-4 15-1-3 Non-fatal Errors in the Communication Control Unit ........
Page 602 15 Troubleshooting 15-1 Operation after an Error This section describes the error status of the Communication Control Unit and the Safety Control Unit, and the operation that occurs after an error is detected. Refer to 15-2 Error Troubleshooting Methods on page 15-23 for details on corrections for specific er- rors.
Page 603 15 Troubleshooting The following table shows the status of front-panel indicators and the ability to communicate with the Sysmac Studio or with an HMI during startup, during normal operation, and when errors occur. (¡: Lit / l: Not lit / 8: Flashing) Communication Control Unit Communications Communication Control Unit operating status...
Page 604 15 Troubleshooting Types of Errors There are two main types of errors (events) depending on whether the Communication Control Unit can manage them or not. l Fatal Errors in the Communication Control Unit These errors are not detected by the event management function of the NX-series because the Communication Control Unit stops operation.
Page 605 15 Troubleshooting The RUN indicator will flash at 2-second intervals while the Communication Control Unit is starting, but if it flashes for 30 seconds or longer, then this error occurs. 15-5 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 606 15 Troubleshooting Checking for Fatal Errors in the Communication Control Unit You can identify fatal errors in the Communication Control Unit based on the status of the UNIT PWR, RUN and ERROR indicators, as well as by the ability to connect communications to the Sysmac Stu- dio.
Page 607 15 Troubleshooting Details on Controller Events (Errors and Information) l Controller Event Times The time of occurrence is recorded when an event occurs. The time of occurrence for an event is displayed on the Sysmac Studio or HMI. l Sources of Controller Events The Event source information indicates the location where an event occurred.
Page 608 15 Troubleshooting l Levels of Controller Events (Errors and Information) The following table classifies the levels of Controller events according to the effect that the errors have on control. All events in impact levels as errors are collectively called Controller errors. All other events that are not classified into errors but mean information are called Controller informa- tion.
Page 609 15 Troubleshooting Click the Event Level Settings Button. A list of the events for which you can change the event level is displayed. Change the levels of the required events in the Event Level column. Precautions for Correct Use If you change an event level on the Sysmac Studio and download the event level setting to the Controller when the event already exists on the Controller, the event will be reset when the download is started.
Page 610 15 Troubleshooting l Operation for Each Level The operation that is performed when an error occurs depends on the error level of the Controller event. Level of event Controller in- Controller errors Item formation Major fault Partial fault Minor fault Observation Information level...
Page 611 15 Troubleshooting Level of event Controller in- Controller errors Item formation Major fault Partial fault Minor fault Observation Information level level level • Outputs from NX Refer to I/O Depends on Depends on Depends on Errors in NX Units Operation for Bus Func- the user pro- the user pro-...
Page 612 15 Troubleshooting l Operation in the Function Module Where an Error Event Occurred Level of current event Function module Major fault level Partial fault level Minor fault level Observation PLC Function Operation continues. Module NX Bus Function I/O refreshing for Operation contin- Operation contin- Module...
Page 613 15 Troubleshooting l I/O Operation for Major Fault Level Controller Errors The following table gives the operation of the Communication Control Unit and the I/O devices. Unit Communication Control Unit operation Unit or slave operation NX Unit mounted to the Com- Input refreshing stops.
Page 614 15 Troubleshooting l Event Code Events that occur in a Controller have an event code. When an event occurs, the Sysmac Studio or HMI will display the event code. The event codes are 8-digit hexadecimal values. The first digit of a Controller event represents its category. These categories are listed in the table below.
Page 615 15 Troubleshooting 15-1-4 Checking for Non-fatal Errors Checking Methods Use the following methods to check for non-fatal errors in the Communication Control Unit. Checking method What you can check Checking the indicators You can use the indicators to confirm the Controller error level and the error status of the EtherNet/IP Function Module.
Page 616 15 Troubleshooting l Log of Past Errors Open the Sysmac Studio’s Controller Event Log Tab Page to check the times, levels, sources, source details, event names, event codes, details, attached information 1 to 4, actions, and corrections for previous errors. Refer to the Sysmac Studio Version 1 Operation Manual (Cat.
Page 617 15 Troubleshooting 15-1-5 Resetting Non-fatal Errors Unless you reset an error, the Controller will retain the error status until you turn OFF the power supply to the Controller or reset the Controller. To reset a Controller error, it is necessary to eliminate the cause of the error. The same error will occur again if you reset the error, but do not eliminate the cause of the error.
Page 618 15 Troubleshooting Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for details on clearing errors from the Sysmac Studio. 15-18 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 619 15 Troubleshooting 15-1-6 Errors Related to the EtherNet/IP Function Module This section describes the errors that are related to the EtherNet/IP Function Module. Classification There are the following sources of errors in the EtherNet/IP Master Function Module. Classification Description Communications If an error is detected for EtherNet/IP communications port 1, the corresponding bit in the port 1 errors Communications Port1 Error status variable shows the error.
Page 620 15 Troubleshooting Event Source and Level The following table gives sources and levels of the events that can occur in the EtherNet/IP Function Module. Source Level Communications port CIP communications TCP application Major fault None None None EtherNet/IP Processing Er- None None Partial fault...
Page 621 • Checking with the CIP Safety Monitor Function of Device status • Sysmac Studio Connection status • Parameter monitor value • Event logs (for OMRON CIP Safety target devices only) 15-21 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 622 By establishing online connection between Sysmac Studio and a Safety CPU Unit, you can check the device status, connection status, and parameter monitor values. With OMRON CIP Safety target devices, you can also checked the event logs. • Device status The device status can be checked.
Page 623 15 Troubleshooting 15-2 Error Troubleshooting Methods This section describes troubleshooting methods for specific errors. 15-2-1 Troubleshooting Flowcharts This section provides basic error identification and troubleshooting flowcharts. Use them when an er- ror occurs in the NX-series Controller. Checking to See if the Communication Control Unit Is Operating When an error occurs in the Communication Control Unit, use the following flowchart to determine whether the error is a "fatal error"...
Page 624 15 Troubleshooting Troubleshooting Flowchart for Non-fatal Errors For a non-fatal error, use the Sysmac Studio or an HMI to troubleshoot the error with the following flowchart. You can use the indicators to check the following. • Level • Whether the error is in the EtherNet/IP port •...
Page 625 15 Troubleshooting l System Initialization Error Cause Correction A conductive object has gotten inside. If there is conductive material nearby, blow out the Communica- tion Control Unit with air. Noise If the error did not result from the above causes, cycle the power to the Controller and see if that resets the error.
Page 626 15 Troubleshooting The Sysmac Studio automatically collects the Controller’s error information, and opens the Troubleshooting Dialog Box. l Checking Current Errors with the Sysmac Studio You can click the Controller Errors Tab in the Troubleshooting Dialog Box to read information on current errors in the Controller.
Page 627 15 Troubleshooting Displayed Item Description Level This is the event level of the error. Source and Source Details This is the physical location and functional location of the error. Event Name Error name Event Code This is the code of the error. You can click the column headings in the Controller error list, such as the Level or Source, to reor- der the table rows according to that heading.
Page 628 15 Troubleshooting l Resetting Errors with the Sysmac Studio You can use the Sysmac Studio to reset errors that occur in a Controller. Before you attempt to reset a Controller error, isolate and remove the cause of the error. The Troubleshooting Dialog Box displays the cause, source, and corrections for the error. You can select any of the items from the error list to display the following information about that error.
Page 629 15 Troubleshooting To eliminate the cause of the error, first select the item to perform from the Action and Correction list. When you select the appropriate step in the Action and Correction list, either the Jump to Error or Error Help Button is enabled, depending on the contents. In some cases, neither button will oper- ate.
Page 630 15 Troubleshooting For details on synchronization, refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504). If you have enabled the verification of operation authority, it is necessary to confirm your authority before you can reset Controller errors. The Operator, Maintainer, Designer, and Administrator have the authority to reset errors.
Page 631 15 Troubleshooting Checking for Errors with System-defined Variables The system-defined variables include an Error Status variable, which shows the error status in a hier- archical structure. The system determines the error status of each level by logically ORing the error status information of the next lower level.
Page 632 15 Troubleshooting Troubleshooting Incorrect Settings and Faulty Communications Path l Direct Connection with EtherNet/IP Port Sysmac Studio cannot connect to Communication Control Unit. Is power supplied to the Controller? Turn ON the power supply to the Controller. Can the Sysmac Studio go online with Communication Control Unit? Insert the cable connectors at the personal...
Page 633 15 Troubleshooting Is the same IP address set Set the IP address for the personal for more than one node computer. Use the default IP address for (computer or Controller) in the Controller, or set the IP address. the same domain? Can the Sysmac Studio go online with Communication Control Unit?
Page 634 15 Troubleshooting l Ethernet Hub Connection Sysmac Studio cannot connect to Communication Control Unit. Is power supplied to the Controller? Turn ON the power supply to the Controller. Can the Sysmac Studio go online with Communication Control Unit? Insert the cable connectors at the personal computer, Ethernet switches, Is the Ethernet cable and the Controller until they lock into...
Page 635 15 Troubleshooting Set the IP address for the personal computer. Use the default IP address for Is the same IP address the Controller or connect the Sysmac set for more than one Studio to the Controller with a direct node (computer or Ethernet connection and set the required Controller) in the same domain?
Page 636 [L3] An error has occurred in the Cycle the power supply. If the software. error reoccurs, contact your OMRON representative. NX Bus I/O Communications Refer to NX Bus I/O Commu- Stopped nications Stopped ( page 15-185). NX Unit I/O Communications...
Page 637 15 Troubleshooting Sev- TS In- NS In- FS In- P ERR In- seg- dica- dica- dica- Cause Corrective action dicator ment Indi- cator [d6] -- CIP Safety Originator Con- Refer to CIP Safety Origina- > [iP] nection Not Established Error tor Connection Not Establish- -->...
Page 638 15 Troubleshooting Sev- TS In- NS In- FS In- P ERR In- seg- dica- dica- dica- Cause Corrective action dicator ment Indi- cator The safety connections are Wait until processing is com- not established (including pleted. when they are currently being 1-sec- established).
Page 639 15 Troubleshooting Sev- TS In- NS In- FS In- P ERR In- seg- dica- dica- dica- Cause Corrective action dicator ment Indi- cator SF_ESPE Error Refer to SF_ESPE Error ( page 15-188). 1-second interval SF_GuardLocking Error Refer to SF_GuardLocking Error ( page 15-189). 1-second interval SF_GuardMonitoring Error...
Page 640 15 Troubleshooting Sev- TS In- NS In- FS In- P ERR In- seg- dica- dica- dica- Cause Corrective action dicator ment Indi- cator SF_TwoHandControlTypeIII Refer to SF_TwoHandCon- Error trolTypeIII Error ( page 15-194). 1-second interval NX Message Communica- Refer to NX Message Com- tions Error munications Error ( page 15-201).
Page 641 15 Troubleshooting TS Indicator FS Indicator Cause Corrective action Safety Process Data Communica- Refer to Safety Process Data Com- tions Not Established, Incorrect munications Not Established, Incor- FSoE Slave Address Error rect FSoE Slave Address Error 1-second inter- ( page 15-218). Safety Process Data Communica- Refer to Safety Process Data Com- tions Not Established, Incorrect...
Page 642 15 Troubleshooting TS Indicator FS Indicator Cause Corrective action Initializing Status is normal. Wait until process- ing is completed. 2-second inter- System Error Refer to System Error ( page 15-216). NX Bus I/O Communications Stop- Refer to NX Bus I/O Communica- tions Stopped ( page 15-223).
Page 643 Safety CPU Unit, as well as the parameter monitor values. If you are using an OMRON CIP Safety target device, the event logs can also be checked. Part Names and Functions of the CIP Safety Monitor This section describes the names and functions of the components on the CIP Safety Monitor.
Page 644 15 Troubleshooting Select Tools - CIP Safety Monitor. Or, click the CIP Safety Monitor Button ( ) in the tool- bar. If the information of the CIP Safety target device matches between the Safety CPU Unit and Sysmac Studio, CIP Safety Target List displays CIP Safety target devices that are registered in the Safety CPU Unit as shown below.
Page 645 15 Troubleshooting In the CIP Safety Target List, the display of the connection status error icon is refreshed. If an error is present in the connection, an error icon is displayed. Icon Description A connection between the target device cannot be established. No target device is found.
Page 646 15 Troubleshooting In the CIP Safety Target List, the display of the remote target status error icon is refreshed. If an error is present in the device status of the CIP Safety target devices, an error icon is dis- played. Icon Description An error is present in the device status.
Page 647 Checking the Event Logs You can check event logs of the OMRON CIP Safety target devices. Go to CIP Safety Target List and select an OMRON CIP Safety target device that you want to check the event logs. Click the Event Log Button.
Page 648 15 Troubleshooting 15-3 Error Descriptions and Corrections This section lists all of the errors (events) that can occur. 15-3-1 Interpreting Tables Within each source, errors (events) are given by functional classifications. Also, events that are not errors are given. l Interpreting Description of Events When Using the Communication Con- trol Unit On the Sysmac Studio, the descriptions of events that are common to the Communication Control Unit and NJ/NX-series Controllers are displayed as the descriptions of NJ/NX-series Controller.
Page 649 15 Troubleshooting Item Description Event code The event code of the error in the NX-series Controller is given. The codes are given in eight hexadecimal digits. A version in parentheses in the Event code column is the unit version of a Communication Control Unit where an event with the relevant event code occurs.
Page 650 15 Troubleshooting Interpreting Error Descriptions The items that are used to describe individual errors (events) are described in the following copy of an error table. Event name Gives the name of the error. Event code Gives the code of the error. Meaning Gives a short description of the error.
Page 651 15 Troubleshooting 15-3-2 Communication Control Unit Error The section provides tables of the errors (events) that can occur in the Communication Control Unit. They are divided into the following functional classifications for each function module. Function module Functional classification PLC Function Module Self-diagnosis Controller operation NX Bus Function Module...
Page 652 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 10020000 hex Non-volatile A file that must be in page The Controller power supply Memory Da- non-volatile memory was turned OFF while the 15-78 ta Corrupted is missing or corrupt- BUSY indicator was lit.
Page 653 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 40030000 hex PLC System A fatal error was de- page An error occurred in the soft- Processing tected in the PLC ware. ¡ 15-84 Error Function Module. • 40040000 hex PLC System A fatal error was de-...
Page 654 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 10060000 hex SD Memory A file that must be in page The Controller power supply Card Data the SD Memory Card was turned OFF while the SD 15-90 Corrupted is missing or corrupt- BUSY indicator was lit.
Page 655 15 Troubleshooting l Errors Related to Controller Operation Level Event code Event name Meaning Assumed cause Reference • 10200000 hex User Pro- The user program or page The user program or Controller gram/ Controller Configura- 15-93 Configurations and Setup are Controller tions and Setup were not correct because the power...
Page 656 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 10230000 hex Event Log Saving the event log page A low battery voltage prevent- Save Error failed. ed retention of memory during 15-97 a power interruption. (NJ/NX- series) •...
Page 657 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 102A0000 hex Backup The backup operation page The capacity of the SD Memo- Failed ended in an error. ry Card is insufficient. 15-100 • It was not possible to save the data that was specified for backup.
Page 658 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 102B0000 hex Restore Op- An error was detect- page An SD Memory Card is not in- eration ed in pre-execution serted. 15-102 • Failed to checks for a restore The SD Memory Card type is Start operation.
Page 659 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • The robot version of the CPU Unit to which to restore the files is older than the robot ver- sion of the backup files on the SD Memory Card. Check the followings for specifi- cation with system-defined varia- bles.
Page 660 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 102C0000 hex Restore Op- The restore operation page It was not possible to read the eration ended in an error. data to restore. 15-105 • Failed The SD Memory Card was re- moved during a restore opera- tion.
Page 661 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 10640000 hex Safety Data Saving the log file for page The SD Memory Card was re- Log File safety data logging moved after the start of log- 15-108 Save Failed failed.
Page 662 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 90020000 hex Time Zone The time zone was page The time zone was changed. ¡ Changed changed. 15-112 • 90050000 hex User Pro- The user program page The user program and the gram/ and the Controller Controller configurations and...
Page 663 15 Troubleshooting NX Bus Function Module Error Table l Errors Related to the NX Bus Level Event code Event name Meaning Assumed cause Reference • 04100000 hex NX Bus An error occurred in An I/O communications error page Controller the NX bus. ¡...
Page 664 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 35910000 hex Unregistered There is a mounted page There is a mounted Unit that NX Unit NX Unit that does not does not exist in the Unit con- 15-125 Mounted exist in the Unit con-...
Page 665 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 85500000 hex NX Bus A communications er- page The NX bus connector contact Communica- ror that prevents nor- is faulty due to vibration or 15-129 tions Error mal NX bus commu- shock.
Page 666 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 10620000 hex NX Unit Saving or reading the page Data in the NX Unit event log Event Log NX Unit event log area are invalid. 15-133 Save Error failed.
Page 667 15 Troubleshooting EtherNet/IP Function Module Error Table l Errors Related to the Built-in EtherNet/IP Port on Communication Control Unit Level Event code Event name Meaning Assumed cause Reference • 14220000 hex EtherNet/IP A fatal error was de- page Hardware has failed. Processing tected in the Ether- 15-135...
Page 668 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 34250000 hex NTP Client An error was detect- page Setting error • Setting Error ed in the NTP client 15-141 Power was interrupted when a settings. ¡ download was in progress for the NTP client settings.
Page 669 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 50010000 hex Controller In- The amount of data page The amount of data for the sufficient for the EtherCAT EtherCAT slave configuration, 15-147 Memory slave configuration, network-published information, Warning network-published in- or other data exceeds the val-...
Page 670 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 840A0000 hex IP Address The same IP address page The IP address of the built-in Duplication is used more than EtherNet/IP port is also used 15-152 ¡ Error once.
Page 671 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 84060000 hex Link OFF An Ethernet link OFF page An Ethernet cable is broken, Detected was detected. disconnected, or loose. 15-158 • The Ethernet switch’s power supply is turned OFF. •...
Page 672 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 94040000 hex Tag Data Tag data links were page Tag data links were started by Link started by the Net- the Network Configurator, Sys- 15-161 Started work Configurator, mac Studio, or manipulation of Sysmac Studio, or a system-defined variable.
Page 673 15 Troubleshooting PLC Function Module Error Descriptions l Errors for Self Diagnosis Event name DIP Switch Setting Error Event code 00090000 hex Meaning An error was detected in the DIP switch setting. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes...
Page 674 15 Troubleshooting Event name Internal Bus Check Error Event code 000D0000 hex Meaning A fatal error was detected on the internal bus. Source PLC Function Module Source details None Detection tim- Continuously Error attributes Level Major fault Recovery Cycle the power Log category System supply.
Page 675 15 Troubleshooting Event name Non-volatile Memory Life Exceeded Event code 000E0000 hex Meaning The specified number of deletions for non-volatile memory was exceeded. Or, the number of bad blocks in memory exceeded the specified value. Source PLC Function Module Source details None Detection tim- At power ON, at...
Page 676 15 Troubleshooting Event name Main Memory Check Error Event code 00130000 hex Meaning An error was detected in the memory check of the main memory in the CPU Unit. Source PLC Function Module Source details None Detection tim- Continuously Error attributes Level Major fault Recovery...
Page 677 15 Troubleshooting Event name Non-volatile Memory Restored or Formatted Event code 10010000 hex Meaning An error was detected in the non-volatile memory check and file system recovery or formatting was executed. Previous files may have been deleted. Source PLC Function Module Source details None Detection tim-...
Page 678 15 Troubleshooting Event name Non-volatile Memory Data Corrupted Event code 10020000 hex Meaning A file that must be in non-volatile memory is missing or corrupted. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level Major fault...
Page 679 15 Troubleshooting Event name Main Memory Check Error Event code 10080000 hex Meaning An error was detected in the memory check of the main memory in the CPU Unit. Source PLC Function Module Source details None Detection tim- Continuously Error attributes Level Major fault Recovery...
Page 680 15 Troubleshooting Event name Non-volatile Memory Data Corrupted Event code 100B0000 hex Meaning A file that must be in non-volatile memory is missing or corrupted. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level Major fault...
Page 681 15 Troubleshooting Event name Event Level Setting Error Event code 100C0000 hex Meaning The settings in the event level setting file are not correct. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level Major fault Recovery...
Page 682 15 Troubleshooting Event name Present Values of Retained Variables Restoration Er- Event code 100F0000 hex Meaning An error occurred in the software and the present values of retained variables could not be restored at startup. The values were initialized. Source PLC Function Module Source details None...
Page 683 15 Troubleshooting Event name Present Values of Retained Variables Not Saved Event code 10100000 hex Meaning A forced shutdown is performed or an error occurred in the software and the present values of retained varia- bles could not be saved during power-OFF processing. Source PLC Function Module Source details...
Page 684 Name fined variables None Cause and cor- Assumed cause Correction Prevention rection An error occurred in the software. Contact your OMRON representa- None tive. Attached infor- None mation Precautions/ None Remarks For details, refer to I/O Operation for Major Fault Level Controller Errors on page 15-13.
Page 685 Name fined variables None Cause and cor- Assumed cause Correction Prevention rection An error occurred in the software. Contact your OMRON representa- None tive. Attached infor- None mation Precautions/ None Remarks For details, refer to I/O Operation for Major Fault Level Controller Errors on page 15-13.
Page 686 15 Troubleshooting Event name Real-Time Clock Stopped Event code 00070000 hex Meaning The oscillation of the real-time clock stopped. The real-time clock is set to an illegal time. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level...
Page 687 15 Troubleshooting Event name SD Memory Card Invalid Type Event code 000F0000 hex Meaning The current SD Memory Card is not supported. Source PLC Function Module Source details None Detection tim- At power ON, at Controller reset, or when SD Memory Card is inserted Error attributes...
Page 688 Prevention rection The file format of the SD Memory Make sure that the correct SD Use an OMRON SD Memory Card. Card inserted in the CPU Unit is Memory Card is inserted in the Do not format the SD Memory not FAT16 or FAT32.
Page 689 15 Troubleshooting Event name SD Memory Card Restored or Formatted Event code 10040000 hex Meaning An error was detected during the file system check and the file system was restored. Files may have been de- leted. Source PLC Function Module Source details None Detection tim-...
Page 690 15 Troubleshooting Event name SD Memory Card Data Corrupted Event code 10060000 hex Meaning A file that must be in the SD Memory Card is missing or corrupted. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level...
Page 691 15 Troubleshooting Event name SD Memory Card Access Power OFF Error Event code 10070000 hex Meaning The power supply to the Controller was interrupted during access to the SD Memory Card. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes...
Page 692 15 Troubleshooting Event name Incorrect SD Memory Card Removal Event code 10310000 hex Meaning SD Memory Card removal processing failed. Source PLC Function Module Source details None Detection tim- At SD Memory Card removal Error attributes Level Observation Recovery Log category System Effects User program...
Page 693 15 Troubleshooting l Errors Related to Controller Operation Event name User Program/Controller Configurations and Setup Event code 10200000 hex Transfer Error Meaning The user program or Controller Configurations and Setup were not transferred correctly. Source PLC Function Module Source details None or I/O bus Detection tim- At power ON or...
Page 694 15 Troubleshooting Event name Illegal User Program/Controller Configurations and Event code 10250000 hex Setup Meaning The upper limit of the usable memory was exceeded or the user program or Controller Configurations and Set- up is corrupted. Source PLC Function Module Source details None Detection tim-...
Page 695 None Cause and cor- Assumed cause Correction Prevention rection An error occurred in the software. Contact your OMRON representa- None tive. Attached infor- Attached information 1: System information mation Attached information 2: System information Attached information 3: System information...
Page 696 None Cause and cor- Assumed cause Correction Prevention rection An error occurred in the software. Contact your OMRON representa- None tive. Attached infor- Attached information 1: System information mation Attached information 2: System information Attached information 3: System information...
Page 697 15 Troubleshooting Event name Event Log Save Error Event code 10230000 hex Meaning Saving the event log failed. Source PLC Function Module Source details None Detection tim- At power ON, or Controller reset Error attributes Level Observation Recovery Log category System Effects User program...
Page 698 15 Troubleshooting Event name Backup Failed to Start Event code 10290000 hex Meaning An error was detected in pre-execution checks for a backup operation. Source PLC Function Module Source details None Detection tim- When backup is specified by the user Error attributes Level Observation...
Page 699 15 Troubleshooting Attached infor- Attached information 1: Operation type • mation 0101 hex: Controller to SD Memory Card for switch operation on front of CPU Unit • 0102 hex: Controller to SD Memory Card for system variable operation • 0103 hex: Controller to SD Memory Card for Sysmac Studio operation •...
Page 700 15 Troubleshooting Event name Backup Failed Event code 102A0000 hex Meaning The backup operation ended in an error. Source PLC Function Module Source details None Detection tim- During backup operation Error attributes Level Observation Recovery Log category System Effects User program Continues.
Page 701 15 Troubleshooting Attached infor- Attached information 1: Operation type • mation 0101 hex: Controller to SD Memory Card for switch operation on front of CPU Unit • 0102 hex: Controller to SD Memory Card for system variable operation • 0103 hex: Controller to SD Memory Card for Sysmac Studio operation •...
Page 702 15 Troubleshooting Event name Restore Operation Failed to Start Event code 102B0000 hex Meaning An error was detected in pre-execution checks for a restore operation. Source PLC Function Module Source details None Detection tim- When restoring data is specified by the user Error attributes Level Observation...
Page 703 15 Troubleshooting Synchronization, online editing, or Wait for the synchronization, online Do not attempt to perform a restore the Clear All Memory operation is editing, or the Clear All Memory operation during a synchronization, in progress. operation to end and then perform online editing, or the Clear All the restore operation again.
Page 704 15 Troubleshooting The SD Memory Card is write pro- Remove write protection from the Make sure that the SD Memory tected. SD Memory Card. Card is not write protected. The capacity of the SD Memory Replace the SD Memory Card for Use an SD Memory Card that has Card is insufficient.
Page 705 15 Troubleshooting Event name Restore Operation Failed Event code 102C0000 hex Meaning The restore operation ended in an error. Source PLC Function Module Source details None Detection tim- During restore operation Error attributes Level Observation Recovery Log category System Effects User program Operation Not affected.
Page 706 15 Troubleshooting Precautions/ None Remarks Event name Online Edits Transfer Failure Event code 103F0000 hex Description Transferring the online edits failed. Source PLC Function Module Source details None Detection tim- When online ed- its are transfer- Error attributes Level Observation Recovery Log category System...
Page 707 15 Troubleshooting Event name Safety Data Logging Failed to Start Event code 10630000 hex Description Starting the safety data logging failed. Source PLC Function Module Source details None Detection tim- When safety da- ta logging is started Error attributes Level Observation Recovery Log category...
Page 708 15 Troubleshooting Event name Safety Data Log File Save Failed Event code 10640000 hex Description Saving the log file for safety data logging failed. Source PLC Function Module Source details None Detection tim- When safety da- ta logging file is saved Error attributes Level...
Page 709 15 Troubleshooting Event name Safe Mode Event code 40170000 hex Meaning The Controller started in Safe Mode. Source PLC Function Module Source details None Detection tim- At power ON or Controller reset Error attributes Level Observation Recovery Log category System Effects User program Stops.
Page 710 15 Troubleshooting Event name Safety Data Logging Aborted Event code 90470000 hex Description The execution of safety data logging was aborted. Source PLC Function Module Source details None Detection tim- During the exe- cution of safety data logging Error attributes Level Observation Recovery...
Page 711 15 Troubleshooting Event name PLC System Information Event code 40150000 hex Meaning This event provides internal information from the PLC Function Module. Source PLC Function Module Source details None Detection tim- Continuously Error attributes Level Information Recovery Log category System Effects User program Continues.
Page 712 15 Troubleshooting Event name Clock Changed Event code 90010000 hex Meaning The clock time was changed. Source PLC Function Module Source details None Detection tim- Commands from user Error attributes Level Information Recovery Log category Access Effects User program Continues. Operation Not affected.
Page 713 15 Troubleshooting Event name User Program/Controller Configurations and Setup Event code 90050000 hex Downloaded Meaning The user program and the Controller configurations and setup were downloaded. Source PLC Function Module Source details None Detection tim- During user pro- gram/Controller configurations and setup download Error attributes...
Page 714 15 Troubleshooting Event name Event Log Cleared Event code 900C0000 hex Meaning The event log was cleared. Source PLC Function Module Source details None Detection tim- Commands from user Error attributes Level Information Recovery Log category Access Effects User program Continues.
Page 715 15 Troubleshooting Event name Power Interrupted Event code 90120000 hex Meaning The power supply was interrupted. Source PLC Function Module Source details None Detection tim- At power inter- ruption Error attributes Level Information Recovery Log category System Effects User program Stops.
Page 716 15 Troubleshooting Event name Backup Started Event code 901A0000 hex Meaning A backup operation was started. Source PLC Function Module Source details None Detection tim- At start of back- up operation Error attributes Level Information Recovery Log category System Effects User program Continues.
Page 717 15 Troubleshooting Event name Restore Operation Started Event code 901C0000 hex Meaning A restore operation started. Source PLC Function Module Source details None Detection tim- At start of re- store operation Error attributes Level Information Recovery Log category System Effects User program Operation Not affected.
Page 718 15 Troubleshooting Event name Safety Data Logging Started Event code 90460000 hex Description Safety data logging was started. Source PLC Function Module Source details None Detection tim- When safety da- ta logging is started Error attributes Level Information Recovery Log category System Effects User program...
Page 719 15 Troubleshooting NX Bus Function Module Error Descriptions l Errors Related to the NX Bus Event name NX Bus Controller Error Event code 04100000 hex Meaning An error occurred in the NX bus. Source NX Bus Function Module Source details Master Detection tim- At CPU Unit...
Page 720 15 Troubleshooting Event name NX Bus Hardware Error Event code 04110000 hex Meaning A hardware error was detected in the NX Bus Function Module. Source NX Bus Function Module Source details Master Detection tim- Continuously Error attributes Level Partial fault Recovery Cycle the power Log category...
Page 721 15 Troubleshooting Event name Failed to Read NX Unit Operation Settings Event code 10610000 hex Meaning Reading the NX Unit operation settings failed. Cycle the power supply to the CPU Unit to restore the previous normally-saved settings. Source NX Bus Function Module Source details Master Detection tim-...
Page 722 15 Troubleshooting Event name Number of Mountable NX Units Exceeded Event code 24D00000 hex Meaning The number of mounted NX Units exceeds the specified value for the CPU Unit. Source NX Bus Function Module Source details Master Detection tim- At CPU Unit power ON, at Controller reset, or at NX bus re-...
Page 723 15 Troubleshooting Event name Total I/O Data Size in NX Units Excessive Event code 24D20000 hex Meaning The total size of I/O data in the mounted NX Units exceeds the maximum specified value for the CPU Unit. Source NX Bus Function Module Source details Master Detection tim-...
Page 724 15 Troubleshooting Event name NX Unit Version Not Matched Event code 35900000 hex Meaning There is a mounted NX Unit with a unit version earlier than that in the Unit configuration information registered in the CPU Unit. Source NX Bus Function Module Source details Master Detection tim-...
Page 725 15 Troubleshooting Event name Unregistered NX Unit Mounted Event code 35910000 hex Meaning There is a mounted NX Unit that does not exist in the Unit configuration information registered in the CPU Unit. If there are more than one NX Unit relevant to this event, only the NX Unit that is nearest to the CPU Unit is registered with the event.
Page 726 15 Troubleshooting Event name NX Unit Serial Number Mismatch Event code 35930000 hex Meaning There is a mounted NX Unit with a serial number different from that in the Unit configuration information regis- tered in the CPU Unit. Source NX Bus Function Module Source details Master Detection tim-...
Page 727 None Cause and cor- Assumed cause Correction Prevention rection An error occurred in the software. Contact your OMRON representa- None tive. Attached infor- Attached information 1: System information mation Attached information 2: System information Attached information 3: System information...
Page 728 15 Troubleshooting Event name Registered NX Unit Not Mounted Event code 35920000 hex Meaning There is no mounted NX Unit that exists in the Unit configuration information registered in the CPU Unit. If there are more than one NX Unit relevant to this event, only the NX Unit that is nearest to the CPU Unit is registered with the event.
Page 729 15 Troubleshooting Event name NX Bus Communications Error Event code 85500000 hex Meaning A communications error that prevents normal NX bus communications was detected. If there are more than one NX Unit relevant to this event, only the NX Unit that is nearest to the CPU Unit is registered with the event.
Page 730 15 Troubleshooting Event name NX Unit Initialization Error Event code 85520000 hex Meaning Initializing an NX Unit failed. Source NX Bus Function Module Source details Master Detection tim- At CPU Unit power ON, at Controller reset, at NX bus re- start, or at error reset Error attributes...
Page 731 15 Troubleshooting Event name NX Unit Startup Error Event code 85530000 hex Meaning Starting an NX Unit failed. Source NX Bus Function Module Source details Master Detection tim- At CPU Unit power ON, at Controller reset, at NX bus re- start, or at error reset Error attributes...
Page 732 15 Troubleshooting Event name NX Unit Restore Operation Failed Event code 103D0000 hex Meaning The restore operation for an NX Unit ended in an error. Source NX Bus Function Module Source details Master Detection tim- During restore operation Error attributes Level Observation Recovery...
Page 733 15 Troubleshooting Event name NX Unit Event Log Save Error Event code 10620000 hex Meaning Saving or reading the NX Unit event log failed. Continuing to operate with this error may result in no event log saved at CPU Unit power OFF although it has no effect on the control function.
Page 734 15 Troubleshooting Event name NX Bus Restart Executed Event code 95800000 hex Meaning An NX bus restart was executed. Source NX Bus Function Module Source details Master Detection tim- At NX bus re- start or at NX Unit restart Error attributes Level Information Recovery...
Page 735 15 Troubleshooting EtherNet/IP Function Module Error Descriptions l Built-in EtherNet/IP Port on CPU Unit Event name EtherNet/IP Processing Error Event code 14220000 hex Meaning A fatal error was detected in the EtherNet/IP Function Module. Source EtherNet/IP Function Module Source details Communica- Detection tim- Continuously...
Page 736 15 Troubleshooting Event name Identity Error Event code 14210000 hex Meaning The CIP identity information in non-volatile memory was not read correctly. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- At power ON or Controller reset Error attributes Level Minor fault Recovery...
Page 737 15 Troubleshooting Event name IP Address Switch Settings Error Event code 28040000 hex Meaning An error was detected in the IP address switch settings. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON, tions port 1 or 2 Controller reset, or at user oper- ation...
Page 738 15 Troubleshooting Event name Tag Data Link Setting Error Event code 34200000 hex Meaning An error was detected in the communications settings for tag data links. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- At power ON or Controller reset Error attributes Level...
Page 739 15 Troubleshooting Event name IP Rout Table Setting Error Event code 34230000 hex Meaning An IP routing setting error was detected. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON or tions port Controller reset Error attributes Level Minor fault Recovery...
Page 740 15 Troubleshooting Event name FTP Server Setting Error Event code 34240000 hex Meaning An error was detected in the FTP server settings. Source EtherNet/IP Function Module Source details Detection tim- At power ON or Controller reset Error attributes Level Minor fault Recovery Automatic re- Log category...
Page 741 15 Troubleshooting Event name NTP Client Setting Error Event code 34250000 hex Meaning An error was detected in the NTP client settings. Source EtherNet/IP Function Module Source details Detection tim- At power ON or Controller reset Error attributes Level Minor fault Recovery Automatic re- Log category...
Page 742 15 Troubleshooting Event name SNMP Setting Error Event code 34260000 hex Meaning An error was detected in the SNMP agent/trap settings. Source EtherNet/IP Function Module Source details SNMP Detection tim- At power ON or Controller reset Error attributes Level Minor fault Recovery Automatic re- Log category...
Page 743 15 Troubleshooting Event name Tag Name Resolution Error Event code 34270000 hex Meaning Resolution of a tag used in a tag data link failed. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- At power ON, at Controller reset, when variables are changed from the Sys-...
Page 744 15 Troubleshooting Event name Basic Ethernet Setting Error Event code 34280000 hex Meaning An error was detected in the Ethernet settings. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON or tions port 1 or 2 Controller reset Error attributes Level Minor fault...
Page 745 15 Troubleshooting Event name IP Address Setting Error Event code 34290000 hex Meaning An error was detected in the IP address settings. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON or tions port 1 or 2 Controller reset Error attributes Level...
Page 746 15 Troubleshooting Event name DNS Setting Error Event code 342A0000 hex Meaning An error was detected in the DNS settings or Hosts settings. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON or tions port Controller reset Error attributes Level Minor fault...
Page 747 15 Troubleshooting Event name Controller Insufficient Memory Warning Event code 50010000 hex Meaning The amount of data for the EtherCAT slave configuration, network-published information, or other data ex- ceeds the value that is specified for the CPU Unit. You may not be able to perform online editing or other oper- ations.
Page 748 15 Troubleshooting Event name NTP Server Connection Error Event code 84040000 hex Meaning Connection with the NTP server failed. Source EtherNet/IP Function Module Source details Detection tim- At NTP opera- tion Error attributes Level Minor fault Recovery Automatic re- Log category System covery (after downloading the...
Page 749 15 Troubleshooting Event name Tag Data Link Connection Failed Event code 84070000 hex Meaning Establishing a tag data link connection failed. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- When establish- ing tag data link connection Error attributes Level Minor fault Recovery...
Page 750 15 Troubleshooting Event name Tag Data Link Timeout Event code 84080000 hex Meaning A timeout occurred in a tag data link. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- Continuously af- ter starting tag data link com- munications Error attributes Level...
Page 751 15 Troubleshooting Event name Tag Data Link Connection Timeout Event code 84090000 hex Meaning A timeout occurred while trying to establish a tag data link connection. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- When establish- ing tag data link connection Error attributes Level...
Page 752 15 Troubleshooting Event name IP Address Duplication Error Event code 840A0000 hex Meaning The same IP address is used more than once. Source EtherNet/IP Function Module Source details Communica- Detection tim- After link is es- tions port 1 or 2 tablished Error attributes Level...
Page 753 15 Troubleshooting Event name BOOTP Server Connection Error Event code 840B0000 hex Meaning Connection with the BOOTP server failed. Source EtherNet/IP Function Module Source details Communica- Detection tim- At BOOTP oper- tions port 1 or 2 ation Error attributes Level Minor fault Recovery Automatic re-...
Page 754 15 Troubleshooting Event name Allowed Communications Bandwidth per Unit Exceed- Event code 840C0000 hex Meaning The total bandwidth for the connections that are set or established exceeded the allowed communications bandwidth of tag data links and CIP Safety communications per Unit for all of the built-in EtherNet/IP ports. Source EtherNet/IP Function Module Source details...
Page 755 15 Troubleshooting Event name IP Address Switch Change during Operation Error Event code 840D0000 hex Meaning The IP address switch setting was changed during the operation. Source EtherNet/IP Function Module Source details Communica- Detection tim- When IP ad- tions port, com- dress switch munications port setting is...
Page 756 15 Troubleshooting Event name Number of Tag Sets for Tag Data Links Exceeded Event code 840E0000 hex Meaning The total number of tag sets for tag data links for all ports of the built-in Ethernet/IP port exceeds the upper limit. Source EtherNet/IP Function Module Source details...
Page 757 15 Troubleshooting Event name Access Detected Outside Range of Variable Event code 54E00000Hex Meaning Accessing a value that is out of range was detected for a tag variable that is used in a tag data link. Source EtherNet/IP Function Module Source details Communica- Detection tim-...
Page 758 15 Troubleshooting Event name Link OFF Detected Event code 84060000 hex Meaning An Ethernet link OFF was detected. Source EtherNet/IP Function Module Source details Communica- Detection tim- Continuously tions port, com- munications port 1, or communi- cations port 2 Error attributes Level Observation Recovery...
Page 759 15 Troubleshooting Event name TLS Log Saving Failed Event code 940F0000 hexBuilt-in EtherNet/IP Port on CPU Unit on page 15-135 Meaning Failed to save the TLS log to the SD Memory Card. Source EtherNet/IP Function Module Source details Communica- Detection tim- When TLS log- tions port ging is enabled...
Page 760 15 Troubleshooting Event name Tag Data Link Download Finished Event code 94020000 hex Meaning Changing the tag data link settings finished. Source EtherNet/IP Function Module Source details CIP /CIP1 /CIP2 Detection tim- At user opera- tion Error attributes Level Information Recovery Log category Access...
Page 761 15 Troubleshooting Event name Tag Data Link Started Event code 94040000 hex Meaning Tag data links were started by the Network Configurator, Sysmac Studio, or manipulation of a system-defined variable. Or, the data link table was downloaded from the Network Configurator or Sysmac Studio again. Source EtherNet/IP Function Module Source details...
Page 762 15 Troubleshooting Event name Restarting Ethernet Port Event code 94060000 hex Meaning The built-in EtherNet/IP port was restarted. Source EtherNet/IP Function Module Source details Communica- Detection tim- At user opera- tions port, com- tion munications port 1, or communi- cations port 2 Error attributes Level Information...
Page 763 15 Troubleshooting Event name IP Address Fixed Event code 94080000 hex Meaning The correct IP address has been determined and Ethernet communications can start. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON or tions port, com- Controller reset munications port 1, or communi-...
Page 764 15 Troubleshooting Event name FTP Server Started Event code 940A0000Hex Meaning The FTP agent started normally. Source EtherNet/IP Function Module Source details Detection tim- At power ON or Controller reset Error attributes Level Information Recovery Log category System Effects User program Continues.
Page 765 15 Troubleshooting Event name TLS Log Started/Stopped Event code 940E0000 hexBuilt-in EtherNet/IP Port on CPU Unit on page 15-135 Meaning TLS logging has started or stopped. Source EtherNet/IP Function Module Source details Communica- Detection tim- At power ON, tions port Controller reset, or when settings are changed...
Page 766 15 Troubleshooting l Other Troubles and Corrections Problem Correction • At startup, some of the receive If the user program uses receive data, make sure that the All Tag Data data is FALSE when it should Link Communications Status in communications status 1 or the Con- be TRUE.
Page 767 15 Troubleshooting l Communications Errors Level Event code Event name Meaning Assumed cause Reference • 35200001 hex FSoE Mas- FSoE communica- The FSoE communications ¡ page ter Connec- tions were not estab- 15-177 settings are not correct, the tion Not Es- lished with the FSoE FSoE slave is not in the cor- tablished Er-...
Page 768 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference 80200000 hex NX Unit I/O An I/O communica- NX Bus of the CPU Unit ¡ page • Communica- tions error occurred An error occurred in the CPU 15-178 tions Error with the NX unit.
Page 769 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 80300001 hex FSoE Mas- A communication ¡ page A setting is not correct. The ter Connec- timeout occurred in setting of the safety task peri- 15-180 tion Timeout FSoE communica- od is too short.
Page 770 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 80330000 hex CIP Safety The target node does ¡ page The communications cable is Target Does not exist. disconnected or broken. 15-183 • Not Exist The target node entered a state where it could not accept the connection.
Page 771 15 Troubleshooting l Operation Continuation Error Related to Program Execution Function Level Event code Event name Meaning Assumed cause Reference 74A00000 hex SF_Antiva- An error was detect- Refer to information on the diag- ¡ page lent Error ed in execution of a nostic code that is given for at- 15-186 safety function block.
Page 772 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference 74A80000 hex SF_Mode- An error was detect- Refer to information on the diag- ¡ page Selector Er- ed in execution of a nostic code that is given for at- 15-190 safety function block.
Page 773 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference 74B00000 hex SF_Two- An error was detect- Refer to information on the diag- ¡ page HandCon- ed in execution of a nostic code that is given for at- 15-194 trolTypeIII safety function block.
Page 774 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 24AA0000 hex Incorrect The DIP switch set- ¡ page The DIP switch setting was DIP Switch ting is not correct. changed to an incorrect value. 15-200 Setting l Restore Function Errors Level Event code Event name...
Page 775 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 352A0000 hex Safety Unit A safety password ¡ page The restore operation for a Restore Op- mismatch was detect- Safety Unit was performed on 15-209 eration ed during pre-execu- an incorrect unit.
Page 776 15 Troubleshooting l User Access Log Level Event code Event name Meaning Assumed cause Reference • 90400000 hex Event Log The event log was The event log was cleared by ¡ page Cleared cleared. 15-203 the user. • 90430000 hex Memory All The Unit settings ¡...
Page 777 15 Troubleshooting l Communications Errors Event name FSoE Master Connection Not Established Error Event code 35200001 hex Meaning FSoE communications were not established with the FSoE slave. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 778 15 Troubleshooting Event name NX Unit I/O Communications Error Event code 80200000 hex Meaning An I/O communications error occurred in an NX Unit. Source Depends on where the Support Source details NX Unit Detection tim- Continuously Software is connected and the system configuration.
Page 779 15 Troubleshooting Cause and [Communications Coupler Unit] correction An error occurred in the commu- Check the error in the communi- Try the solutions specified in Pre- nications coupler unit, which pre- cations coupler unit and try the vention for the error in the com- vents the NX bus communica- solutions specified in Correction.
Page 780 15 Troubleshooting Event name FSoE Master Connection Timeout Event code 80300001 hex Meaning A communication timeout occurred in FSoE communications with the FSoE slave. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 781 15 Troubleshooting Event name CIP Safety Originator Connection Not Established Event code 80310000 hex Error Meaning CIP safety originator connection was not established. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 782 15 Troubleshooting Event name CIP Safety Originator Connection Timeout Event code 80320000 hex Meaning A timeout occurred in CIP safety originator connection. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 783 15 Troubleshooting Event name CIP Safety Target Does Not Exist Event code 80330000 hex Meaning The target node does not exist. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 784 15 Troubleshooting Event name CIP Safety Target Connection Timeout Event code 80340000 hex Meaning A timeout occurred in the CIP Safety Target connection. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (STOP- tem configuration.
Page 785 15 Troubleshooting Event name NX Bus I/O Communications Stopped Event code 84F00000 hex Meaning An error occurred in I/O communications between the NX bus master and an NX Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- Continuously Studio is connected and the sys- tem configuration.
Page 786 15 Troubleshooting l Operation Continuation Error Related to Program Execution Function Event name SF_Antivalent Error Event code 74A00000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys-...
Page 787 15 Troubleshooting Event name SF_EmergencyStop Error Event code 74A20000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 788 15 Troubleshooting Event name SF_Equivalent Error Event code 74A40000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 789 15 Troubleshooting Event name SF_GuardLocking Error Event code 74A60000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 790 15 Troubleshooting Event name SF_ModeSelector Error Event code 74A80000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 791 15 Troubleshooting Event name SF_MutingPar_2Sensor Error Event code 74AA0000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 792 15 Troubleshooting Event name SF_OutControl Error Event code 74AC0000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 793 15 Troubleshooting Event name SF_TestableSafetySensor Error Event code 74AE0000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 794 15 Troubleshooting Event name SF_TwoHandControlTypeIII Error Event code 74B00000 hex Meaning An error was detected in execution of a safety function block. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 795 15 Troubleshooting l Operation Stop Error Related to Program Execution Event name Division by Zero Event code 55000000 hex Meaning Division by zero was detected. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 796 15 Troubleshooting Event name Cast Error Event code 55010000 hex Meaning A casting error was detected. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration. RUN mode Error attrib- Level...
Page 797 15 Troubleshooting Event name MUX Error Event code 55020000 hex Meaning An MUX instruction error was detected. Source Depends on where the Sysmac Source details NX Unit Detection tim- In DEBUG Studio is connected and the sys- mode (RUN) or tem configuration.
Page 798 15 Troubleshooting l Setting Errors Event name NX Bus Communications Settings Read Error Event code 10500000 hex Meaning There is an error in the NX bus communications settings that are saved in non-volatile memory. Source Depends on where the Sysmac Source details NX Unit Detection tim- At power ON or...
Page 799 15 Troubleshooting Event name NX Bus Communications Settings and Safety Ap- Event code 10520000 hex plication Data Mismatch Meaning There is an error in the safety application data that is saved in non-volatile memory. Source Depends on where the Sysmac Source details NX Unit Detection tim- When applica-...
Page 800 15 Troubleshooting Event name Non-volatile Memory Access Error Event code 10530000 hex Meaning Reading/writing non-volatile memory failed. Source Depends on where the Sysmac Source details NX Unit Detection tim- When power is Studio is connected and the sys- turned ON to tem configuration.
Page 801 15 Troubleshooting l Other Errors Event name NX Message Communications Error Event code 80220000 hex Meaning An error was detected in message communications for an NX Unit and the message frame was discard- Source Depends on where the Sysmac Source details NX Unit Detection tim- During NX Studio is connected and the sys-...
Page 802 15 Troubleshooting Event name Sysmac Studio Communications Connection Time- Event code 951E0000 hex Meaning A communications timeout occurred between the Sysmac Studio and the Safety CPU Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When applica- Studio is connected and the sys- tem configuration.
Page 803 15 Troubleshooting l User Access Log Event name Event Log Cleared Event code 90400000 hex Meaning The event log was cleared. Source Depends on where the Sysmac Source details NX Unit Detection tim- When com- Studio is connected and the sys- manded from tem configuration.
Page 804 15 Troubleshooting l Errors Related to Restore Function Event name Safety Unit Restore Operation Failed to Start (SD Event code 35250000 hex Memory Card Access Failed) Meaning Access to the SD Memory Card failed when you start the restore operation for a Safety Unit. Source Depends on where the Sysmac Source details NX Unit...
Page 805 15 Troubleshooting Event name Safety Unit Restore Operation Failed to Start Event code 35260000 hex (Safety Unit Restore File Read Failure) Meaning Reading the Safety Unit Restore File failed. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety Studio is connected and the sys- Unit restoring...
Page 806 15 Troubleshooting Event name Safety Unit Restore Operation Failed to Start Event code 35270000 hex (Model Mismatch) Meaning A model mismatch was detected during pre-execution checks for a restore operation for a Safety Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety...
Page 807 15 Troubleshooting Event name Safety Unit Restore Operation Failed to Start (Ver- Event code 35280000 hex sion Mismatch) Meaning A version mismatch was detected during pre-execution checks for a restore operation for a Safety Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety...
Page 808 15 Troubleshooting Event name Safety Unit Restore Operation Failed to Start Event code 35290000 hex (Node Name Mismatch) Meaning A node name mismatch was detected during pre-execution checks for a restore operation for a Safety Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety...
Page 809 15 Troubleshooting Event name Safety Unit Restore Operation Failed to Start Event code 352A0000 hex (Safety Password Mismatch) Meaning A safety password mismatch was detected during pre-execution checks for a restore operation for a Safety Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety...
Page 810 15 Troubleshooting Event name Safety Unit Restore Operation Failed Event code 352B0000 hex Meaning The restore operation for a Safety Unit ended in an error. Source Depends on where the Sysmac Source details NX Unit Detection tim- When Safety Studio is connected and the sys- Unit restoring tem configuration.
Page 811 15 Troubleshooting l Communications Errors Level Event code Event name Meaning Assumed cause Reference • 35210000 hex Safety Proc- Safety process data The model or safety I/O termi- ¡ page ess Data communications was 15-217 nal settings are not correct. Communica- not established with tions Not Es-...
Page 812 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference 80200000 hex NX Unit I/O An I/O communica- NX Bus of the CPU Unit ¡ page • Communica- tions error occurred in An error occurred in the CPU 15-220 tions Error an NX Unit.
Page 813 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 80300000 hex Safety Proc- A communications ¡ page A setting is not correct. The ess Data timeout occurred in setting of the safety task peri- 15-222 Communica- safety process data od is too short.
Page 814 15 Troubleshooting Level Event code Event name Meaning Assumed cause Reference • 65220000 hex External Test An error was detect- ¡ page The positive power supply wire Signal Fail- ed in test pulse evalu- is in contact with the input sig- 15-229 ure at Safety ation of the safety in-...
Page 815 15 Troubleshooting l Other Errors Level Event code Event name Meaning Assumed cause Reference • 80220000 hex NX Message An error was detect- The message communications ¡ page Communica- ed in message com- 15-235 load is high. • tions Error munications for an The communications cable is NX Unit and the mes-...
Page 816 15 Troubleshooting l System Error Event name System Error Event code 05200000 hex Meaning A hardware error was detected during self-diagnosis of the hardware. Source Depends on where the Sysmac Source details NX Unit Detection tim- Continuously Studio is connected and the sys- tem configuration.
Page 817 15 Troubleshooting l Communications Errors Event name Safety Process Data Communications Not Estab- Event code 35210000 hex lished - Incorrect Unit Parameter Error Meaning Safety process data communications was not established with the Safety CPU Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When safety...
Page 818 15 Troubleshooting Event name Safety Process Data Communications Not Estab- Event code 35230000 hex lished, Incorrect FSoE Slave Address Error Meaning Safety process data communications was not established with the Safety CPU Unit because of an incor- rect FSoE slave address. Source Depends on where the Sysmac Source details NX Unit...
Page 819 15 Troubleshooting Event name Safety Process Data Communications Not Estab- Event code 35240000 hex lished, Incorrect Frame Error Meaning Safety process data communications was not established with the Safety CPU Unit because an incorrect frame was received. Source Depends on where the Sysmac Source details NX Unit Detection tim- When safety...
Page 820 15 Troubleshooting Event name NX Unit I/O Communications Error Event code 80200000 hex Meaning An I/O communications error occurred in an NX Unit. Source Depends on where the Support Source details NX Unit Detection tim- Continuously Software is connected and the system configuration.
Page 821 15 Troubleshooting Cause and [Communications Coupler Unit] correction An error occurred in the commu- Check the error in the communi- Try the solutions specified in Pre- nications coupler unit, which pre- cations coupler unit and try the vention for the error in the com- vents the NX bus communica- solutions specified in Correction.
Page 822 15 Troubleshooting Event name Safety Process Data Communications Timeout Event code 80300000 hex Meaning A communications timeout occurred in safety process data communications with the Safety Control Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- When estab- Studio is connected and the sys- lishing or dur-...
Page 823 15 Troubleshooting Event name NX Bus I/O Communications Stopped Event code 84F10000 hex Meaning An error occurred in I/O communications between the NX Bus Master and an NX Unit. Source Depends on where the Sysmac Source details NX Unit Detection tim- Continuously Studio is connected and the sys- tem configuration.
Page 824 15 Troubleshooting l Safety I/O Errors Event name Internal Circuit Error at Safety Input Event code 05210000 hex Meaning A fault was detected in the internal circuit for the safety input terminal. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys-...
Page 825 15 Troubleshooting Event name Internal Circuit Error at Test Output Event code 05220000 hex Meaning A fault was detected in the internal circuit for the test output terminal. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 826 15 Troubleshooting Event name Internal Circuit Error at Safety Output Event code 05230000 hex Meaning A fault was detected in the internal circuit for the safety output terminal. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 827 15 Troubleshooting Event name I/O Power Supply Voltage Error Event code 65200000 hex Meaning An incorrect I/O power supply voltage was detected. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 828 15 Troubleshooting Event name Output Power Interrupt Circuit Error Event code 65210000 hex Meaning An error was detected by the output power interruption test. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 829 15 Troubleshooting Event name External Test Signal Failure at Safety Input Event code 65220000 hex Meaning An error was detected in test pulse evaluation of the safety input terminals. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 830 15 Troubleshooting Event name Discrepancy Error at Safety Input Event code 65230000 hex Meaning An error was detected in discrepancy evaluation of safety input terminals. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 831 15 Troubleshooting Event name Overload Detected at Test Output Event code 65240000 hex Meaning An overcurrent was detected at the test output terminal. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 832 15 Troubleshooting Event name Stuck-at-high Detected at Test Output Event Code 65250000 hex Meaning It was detected that the test output terminal is stuck ON. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 833 15 Troubleshooting Event name Short Circuit Detected at Safety Output Event code 65270000 hex Meaning A ground fault was detected on the safety output terminal. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 834 15 Troubleshooting Event name Stuck-at-high Detected at Safety Output Event Code 65280000 hex Meaning It was detected that the safety output terminal is stuck ON. Source Depends on where the Sysmac Source details NX Unit Detection tim- During refresh- Studio is connected and the sys- tem configuration.
Page 835 15 Troubleshooting l Other Errors Event name NX Message Communications Error Event code 80220000 hex Meaning An error was detected in message communications for an NX Unit and the message frame was discard- Source Depends on where the Sysmac Source details NX Unit Detection tim- During NX Studio is connected and the sys-...
Page 836 15 Troubleshooting l User Access Log Event name Event Log Cleared Event code 90400000 hex Meaning The event log was cleared. Source Depends on where the Sysmac Source details NX Unit Detection tim- When com- Studio is connected and the sys- manded from tem configuration.
Page 837 15 Troubleshooting 15-3-5 Other Troubles and Corrections Security Errors Problem Correction Forgot the Administrator password. You cannot access the Administrator's password. Al- ways record the Administrator password so that you do not forget it. Cannot release the operation lock with the Sys- Log in with verification authority that is equal to or mac Studio.
Page 838 15 Troubleshooting 15-4 Checking Status with the Network Configurator 15-4-1 The Network Configurator's Device Monitor Function Connect the Network Configurator online, select the device to be checked, right-click to display the pop-up menu, and select Monitor. The Monitor Device Dialog Box will be displayed. Additional Information If a communications error occurs during monitoring, the dialog box will continue to show the last information that was collected.
Page 839 15 Troubleshooting Classification Item TRUE status description Data Link Status Tag Data Link Error There were two or more errors in a connection as an originator. Invalid Parameter An error was found in the parameters for tag data links that are saved in non-volatile memory. All Tag Data Link Tag data links are communicating in all connections as the originator.
Page 840 15 Troubleshooting 15-240 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 841 15 Troubleshooting l Status 2 Tab Page This tab page displays information on nodes with tag data link originator settings. This information is in blue if the connection is normal, or red if an error occurred. Additional Information The target Controller status can be used when the Controller status is set to Included for all the target sets for both originator and target connections.
Page 842 15 Troubleshooting l Connection Tab Page • Target Node Status Information about the target node that acts as the originator is displayed. If all tag data link connections to the node are established and normal, this information is dis- played in blue. However, if any connection is broken it is displayed in red. However, this information is displayed in gray if the connection to the node is stopped.
Page 843 15 Troubleshooting l Controller Log Tab Page This tab page displays the Controller event log that is stored in the Communication Control Unit. The error history shows errors that have occurred. It can be saved in a file in the computer. 15-243 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 844 15 Troubleshooting l Tag Status Tab Page This tab page displays if the tag settings for each tag for tag data links are set so that data can be exchanged with the Communication Control Unit. The following status is displayed depending on the status that is set. Normally resolved: Normal data exchange is possible.
Page 845 15 Troubleshooting l Ethernet Information Tab Page This tab page displays the communications status at the communications driver level of the built-in Ethernet/IP port. The error counter information can be used to confirm whether communications problems have oc- curred. The tag data link information can be used to confirm characteristics such as the Bandwidth (pps). 15-245 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 846 15 Troubleshooting 15-4-2 Connection Status Codes and Troubleshooting This section explains how to identify and correct errors based on the tag data link's connection status. The connection status can be read using the Connection Tab Page of Monitor Device Window with the Network Configurator.
Page 847 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0106 Duplicate consumers: If the tag data Depends on If the tag data Attempted to open multiple connections link is stopped the target's link is stopped for single-consumer data.
Page 848 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0113 Error code generated by originator or re- Check the con- Check the con- Check the con- turned from target: nection set- nection set- nection settings Attempted to open more connections tings (number...
Page 849 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0117 Error code returned from target: Check whether Depends on Check the orig- The tag set specified in the connection's the originator the target's inator's con- target variables does not exist.
Page 850 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0204 Error code generated by originator: There was no response from the target. Check the The connection open process timed out. power supply and cable wiring of the devices in the communications path, including the target and switches.
Page 851 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0312 Error code returned from target: This error does Depends on Depends on There was a parameter error in the not occur. the target's the originator's frame used to open the connection.
Page 852 15 Troubleshooting Connection status Handling General Additional Source of error Configuration Configuration Configuration Status Status (hex) (hex) 0001 Error code generated by originator: The connection The meaning Depends on The connection operation is stopped. was stopped of this error the originator's because the code is defined specifications.
Page 853 Source of error Configuration Configuration Configuration Status Status (hex) (hex) OMRON error code 0810 Error code returned from target: This error may The meaning The meaning of New data could not be obtained from the occur if the of this error...
Page 854 15 Troubleshooting Additional Information The connection status has the same meaning as the Connection Manager's General and Addi- tional error response codes, as defined in the CIP specifications. The following table shows the likely causes of the errors and the troubleshooting methods for each connection status.
Page 855 15 Troubleshooting Connection sta- Gener- Description Cause Correction al sta- tended status (HEX) (HEX) 0117 Invalid connection point. The CIP Safety I/O assembly on the Check the connection settings of CIP Safety target device is not availa- the CIP Safety target device. ble.
Page 856 15 Troubleshooting Connection sta- Gener- Description Cause Correction al sta- tended status (HEX) (HEX) 080C SCID Mismatch. The Attempted to open a connection for an Check the CIP Safety connection SCID was non-zero and already configured CIP Safety target settings and the CIP Safety target did not match the value in device by selecting "Check Safety Sig- device settings.
Page 857 Inspection and Maintenance This section describes the procedures for cleaning, inspecting, and replacing Safety Network Controller. 16-1 Cleaning and Inspection................16-2 16-1-1 Cleaning ......................16-2 16-1-2 Periodic Inspections ..................16-2 16-2 Maintenance Procedures................16-5 16-2-1 Replacing the Communication Control Unit and the Safety CPU Unit ..16-5 16-2-2 Replacing Safety I/O Units ................
Page 858 16 Inspection and Maintenance 16-1 Cleaning and Inspection This section describes daily maintenance and the cleaning and inspection methods. 16-1-1 Cleaning Clean the Communication Control Units and Safety Control Units regularly as described below in order to keep them in optimal operating condition. •...
Page 859 16 Inspection and Maintenance Inspec- Inspection details Criteria Correction tion item Ambient Is the ambient operating 0 to 55°C Use a thermometer to check the environ- temperature within stand- temperature and ensure that the ment ards? ambient operating temperature re- mains within the allowed range of 0 to 55°C.
Page 860 16 Inspection and Maintenance Tools Required for Inspections l Required Tools • Phillips screwdriver • Flat-blade screwdriver • Voltage tester or digital voltmeter • Industrial alcohol and pure cotton cloth l Tools Required Occasionally • Oscilloscope • Thermometer and hygrometer 16-4 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 861 16 Inspection and Maintenance 16-2 Maintenance Procedures If the inspection reveals any problems that require you to replace a Communication Control Unit or a Safety Control Unit, observe the following precautions. • Never disassemble, repair, or modify a Unit. This will compromise the integrity of the safety function and is dangerous.
Page 862 16 Inspection and Maintenance l When Using the Sysmac Studio Sysmac Studio can be used only when the safety application contained in the project file is validat- If the safety application is not validated yet, refer to Section 9 Checking Operation and Actual Op- eration on page 9-1.
Page 863 16 Inspection and Maintenance • To ensure the safety of all workers, turn OFF the power supply to all hazard sources (i.e., actua- tors, etc.). l Replacement Procedure Record the relationship between the wiring and the terminal numbers before you remove the terminal block from the Safety I/O Units.
Page 864 16 Inspection and Maintenance 16-8 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 865 Appendices The appendices provide the general specifications, dimensions of the Units, applica- tion examples, and other information. General Specifications ................. A-3 Dimensions ....................A-4 A-2-1 Communication Control Unit ................A-4 A-2-2 Safety CPU Unit ....................A-5 A-2-3 Safety I/O Units ....................A-5 A-2-4 End Cover .......................
Page 866 Appendices A-8-2 Extended Status Codes................. A-80 Icon list for Safety Slave Unit Parameters ..........A-83 A-9-1 External Device Icons for Input Devices............A-83 A-9-2 Contact Icons for Input Devices ..............A-87 A-9-3 External Device Icons for Output Devices............. A-89 A-9-4 Contact Icons for Output Devices..............
Page 867 Appendices A-1 General Specifications Refer to General Specifications on page 3-3 for the general specifications of Communication Control Unit. Refer to General Specifications on page 3-22 for the general specifications of Safety CPU Unit. Refer to General Specifications on page 3-32 for the general specifications of Safety Input Unit. Refer to General Specifications on page 3-45 for the general specifications of Safety Output Unit.
Page 868 Appendices A-2 Dimensions Dimensions of the Units are shown as follows. The unit of dimension is millimeter. A-2-1 Communication Control Unit NX-CSG320 End Plate End Cover Communication End Plate Control Unit Center line of DIN Track DIN Track Unit: mm For dimensions with the communications cable connected, refer to 5-2-11 Assembled Appearance and Dimensions on page 5-28.
Page 869 Appendices A-2-2 Safety CPU Unit NX-SL5500/NX-SL5700 (2.1) (72.1) 32.1 Unit: mm A-2-3 Safety I/O Units NX-SID800/NX-SIH400/NX-SOD400/NX-SOH200 14.1 0.55 12.0 65.2 Unit: mm *1. The dimension is 1.35 mm for Units with lot numbers through December 2014. *2. The dimension from the attachment surface of the DIN Track to the front surface of the Safety I/O Unit. NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 870 Appendices A-2-4 End Cover NX-END02 65.2 Unit: [mm] *1. The dimension from the attachment surface of the DIN Track to the front surface of the end cover. A-2-5 SD Memory Card ± ± 0.15 ± Unit: [mm] NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 871 Appendices A-3 NX Objects A-3-1 Format of NX Object Descriptions In this manual, NX objects are described with the following format. Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- Index (hex) : This is the index of the NX object that is expressed as a four-digit hexadecimal number.
Page 872 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1000 NX Bus Identity Number of Entries USINT sup- port- Model ARRAY [0..11] OF sup- BYTE port- Device Type 00000A00 hex UDINT sup- port-...
Page 873 Appendices NX-SL5700: 00A05700 hex Bits 24 to 31: Integer part of the Unit version Bits 16 to 23: Fractional part of the Unit version Bits 0 to 15: Reserved (Example) For Ver.1.0, 0100££££ hex The unique serial number of the product is given. Bits 0 to 31: Serial number The date of manufacture is given for the "lot number".
Page 874 Appendices l Safety Signature Objects Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 5002 Safety Signature Number of Entries USINT sup- port- 0x0000000000 0x0000000000 ULINT Last Modified 000000 000000 to sup- 0xFFFFFFFFF port-...
Page 875 Appendices l Status Objects Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 5001 Status Number of Entries USINT sup- port- Safety CPU Status 0000 hex 0000 to 007F WORD sup- port- Normal Operating BOOL...
Page 876 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1000 NX Bus Identity Number of Entries USINT sup- port- Model NX-SID800 ARRAY [0..11] OF sup- BYTE port- Device Type 00000A01 hex UDINT sup- port-...
Page 877 Appendices (Example) For Ver.1.0, 0100££££ hex The unique serial number of the product is given. Bits 0 to 31: Serial number The date of manufacture is given for the "lot number". Bits 24 to 31: Day of manufacture Bits 16 to 23: Month of manufacture Bits 8 to 15: Year of manufacture Bits 0 to 7: Reserved The hardware version is given in order in the lowest elements of the array.
Page 878 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 6002 Standard Input Da- Number of Entries USINT sup- port- Standard Input 1st 0000 hex 0000 to FFFF WORD Sup- Word port- Standard Input 2nd 00 hex...
Page 879 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 7000 FSoE Master Frame Elements Number of Entries USINT sup- port- FSoE Master CMD 00 hex 00 to FF hex BYTE Sup- port- FSoE Master...
Page 880 Appendices Other Objects This section lists other objects. Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 5000 Device Safety Ad- dress Number of Entries USINT sup- port- Safety Address 0000 hex 0000 to FFFF UINT sup-...
Page 881 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1000 NX Bus Identity Number of Entries USINT sup- port- Model NX-SIH400 ARRAY [0..11] OF sup- BYTE port- Device Type 00000A02 hex UDINT sup- port-...
Page 882 Appendices (Example) For Ver.1.0, 0100££££ hex The unique serial number of the product is given. Bits 0 to 31: Serial number The date of manufacture is given for the "lot number". Bits 24 to 31: Day of manufacture Bits 16 to 23: Month of manufacture Bits 8 to 15: Year of manufacture Bits 0 to 7: Reserved The hardware version is given in order in the lowest elements of the array.
Page 883 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 6002 Standard Input Da- Number of Entries USINT sup- port- Standard Input 1st 00 hex BYTE Sup- 00 to FF hex Byte port- Standard Input 2nd...
Page 884 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 7001 Safety Output Data Number of Entries USINT sup- port- Safety Output 1st 00 hex 00 to FF hex BYTE Sup- Byte port- Data...
Page 885 Appendices A-3-5 NX-SOD400 Safety Output Unit Unit Information Objects These objects give the product information. Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1000 NX Bus Identity Number of Entries USINT sup- port-...
Page 886 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1001 Production Info Number of Entries USINT sup- port- Lot Number 00000000 to UDINT FFFFFFFF hex sup- port- Hardware Version ARRAY [0..19] OF sup- BYTE...
Page 887 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 6000 FSoE Slave Frame Elements Number of Entries USINT sup- port- FSoE Slave CMD 00 hex 00 to FF hex BYTE Sup- port- FSoE Slave...
Page 888 Appendices Bit 3: So03 Monitor Value Bit 4: Safety Connection Status Bit 5: Safety Output Terminal Status Bit 6: Unit Normal Status Bit 7: IO Power Supply Error Flag The details of the "Standard Input 2nd Byte" are as follows: Bit 0: So00 Status Bit 1: So01 Status Bit 2: So02 Status...
Page 889 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 7002 Standard Output Data Number of Entries USINT sup- port- Standard Output 00 hex 00 to FF hex BYTE Sup- 1st Byte port- Standard Output 00 hex...
Page 890 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 1000 NX Bus Identity Number of Entries USINT sup- port- Model NX-SOH200 ARRAY [0..11] OF sup- BYTE port- Device Type 00000A04 hex UDINT sup- port-...
Page 891 Appendices (Example) For Ver.1.0, 0100££££ hex The unique serial number of the product is given. Bits 0 to 31: Serial number The date of manufacture is given for the "lot number". Bits 24 to 31: Day of manufacture Bits 16 to 23: Month of manufacture Bits 8 to 15: Year of manufacture Bits 0 to 7: Reserved The hardware version is given in order in the lowest elements of the array.
Page 892 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 6002 Standard Input Da- Number of Entries USINT sup- port- Standard Input 1st 00 hex BYTE Sup- 00 to FF hex Byte port- Standard Input 2nd...
Page 893 Appendices Data Index Subindex allo- Object name Default value Data range Unit Data type (hex) (hex) cess cati- trib- 7001 Safety Output Data Number of Entries USINT sup- port- Safety Output 1st 00 hex 00 to FF hex BYTE Sup- Byte port- Data...
Page 894 Appendices A-4 Application Examples Refer to the NX-series Safety Control Unit Instructions Reference Manual (Cat. No. Z931) for details on the instructions that are used in each example. A-4-1 Emergency Stop Pushbutton Switches Application Overview Safety category/PL Safety device Stop category Reset Equivalent to 4/PLe Emergency stop pushbutton...
Page 895 Appendices Timing Chart E-STOP released Activate OFF→ON Reset ON (Rising Edge) Discrepancy Discrepancy error EDM error reset E-STOP pushed error reset Safety connection status (Unit 2 and Unit 3) Discrepancy time E-STOP S1 (Si0) E-STOP S1 (Si1) Reset S2 EDM feedback MAX_Feedback_Time (T EDM error Safety I/O Terminal &...
Page 896 Appendices l I/O Map Settings Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 897 Appendices Safety category/PL Safety device Stop category Reset Equivalent to 4/PLe Safety limit switches 1 and 2 Auto (Safety Door) Emergency stop pushbutton Manual M1 stops when safety door 1 (S3, S4) is opened. M2 stops when safety door 2 (S5, S6) is opened. Both M1 and M2 stop when the emergency stop pushbutton S1 is pressed.
Page 898 Appendices Unit 4 (NX-SIH400) Unit 5 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3, S5: Safety limit switches S4, S6: Limit switches (NO contacts) KM1, KM2, KM3, KM4: Contactors M1, M2: Motors Timing Chart Reset ON Safety door 1 opened E-STOP pushed E-STOP released Safety connection status...
Page 899 Appendices l Safety I/O Terminal Settings l I/O Map Settings A-35 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 900 Appendices Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 901 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) OSSD A (red) OSSD B (yellow) Safety laser scanner 24 VDC (white) GND (brown) Unit4 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3: Safety laser scanner KM1, KM2: Contactors M: Motor Timing Chart E-STOP pushed Reset ON...
Page 902 Appendices l Safety I/O Terminal Settings l I/O Map Settings A-38 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 903 Appendices Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 904 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) Unit 4 (NX-SIH400) Unit 5 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3: Key selector switch S4: Safety door switch with magnetic lock S5: Safety limit switch Open S6: Unlock request switch KM1, KM2: Contactors M: Motor A-40...
Page 905 Appendices Timing Chart Reset ON E-STOP pushed E-STOP released Safety connection status (Units 2 to 5) E-STOP S1 Mode Monitor Time Mode Monitor Time Reset S2 Key Selector Switch S3 (RUN) Maintenance Mode Key Selector Switch Door opened Door closed S3 (Maintenance) Door SW S4 31-32 Limit SW S5...
Page 906 Appendices l I/O Map Settings A-42 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 907 Appendices Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 908 Appendices Application Overview Safety category/PL Safety device Stop category Reset • Equivalent to 4/PLe Manual Emergency stop pushbutton • (Enable Switch) Safety limit switch • Key selector switch • Enable switch Motor M stops when safety doors S3 and S4 are opened or key Selector switch S5 is maintenance mode.
Page 909 S1: Emergency stop pushbutton S2: Reset switch S3: Safety limit switch S4: Limit switch (NO contacts) S5: Key selector switch S6: Enabling switch (When OMRON enabling switch A4E or A4EG is used) KM1, KM2: Contactors M: Motor Timing Chart E-STOP pushed...
Page 910 Appendices l Safety I/O Terminal Settings l I/O Map Settings A-46 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 911 Appendices Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 912 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) Unit 4 (NX-SOD400) S11, S12: Two-hand switches S2: Reset switch KM1, KM2: Contactors M: Motor Timing Chart Input timing of S11 and Reset SF_TwoHandControlTypeIII error S12 separated by more SF_TwoHandControlTypeIII error than 500 ms. Reset SF_TwoHandControlTypeIII error SF_TwoHandControlTypeIII error...
Page 913 Appendices Safety I/O Terminal & I/O Map Setting l Safety I/O Terminal Settings l I/O Map Settings Program A-49 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 914 Appendices Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 915 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) Black Yellow White Brown 24 VDC Blue Standard I/O (NX-ID Unit 4 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3: Non-contact door switch KM1, KM2: Contactors M: Motor Timing Chart E-STOP pushed Reset ON Door opened E-STOP released...
Page 916 Appendices l Safety I/O Terminal Settings l I/O Map Settings A-52 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 917 Appendices Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 918 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) Black Yellow White Gray Brown 24 VDC Blue Standard I/O (NX-ID OSSD1 (green) 24 VDC (brown) GND (blue) OSSD2 (white) Unit 4 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3: Safety light curtain S4: Non-contact door switch KM1, KM2: Contactors M: Motor...
Page 919 Appendices Timing Chart E-STOP pushed E-STOP released Reset ON Safety connection status (Units 2 to 4) E-STOP S1 Reset S2 SLC S3 Non-contact SW S4 KM1, KM2 EDM feedback MAX_Feedback_Time (T Safety I/O Terminal & I/O Map Setting l Safety I/O Terminal Settings A-55 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 920 Appendices l I/O Map Settings Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 921 Appendices Application Overview Safety category/PL Safety device Stop category Reset • Equivalent to 3/PLd Manual Emergency stop pushbutton • (Safety Mat) Safety light curtain • Safety mat Safety light curtain monitors apertural area of safeguarded space and safety mat monitors inside of safeguarded space.
Page 922 Appendices Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400) Blue White Black Brown White Blue Brown Black OSSD1 (green) 24 VDC (brown) GND (blue) OSSD2 (white) Unit 4 (NX-SOD400) S1: Emergency stop pushbutton S2: Reset switch S3: Safety light curtain S4: Safety mat KM1, KM2: Contactors M: Motor A-58...
Page 923 Appendices Timing Chart E-STOP pushed Reset ON E-STOP released SLC interrupted Safety connection status (Units 2 to 4) E-STOP S1 Reset S2 SLC S3 A human stays in a safeguarded space Safety mat S4 KM1, KM2 EDM feedback MAX_Feedback_Time (T Safety I/O Terminal &...
Page 924 Appendices l I/O Map Settings Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 925 Appendices A-4-10 Safety Edges Application Overview Safety category/PL Safety device Stop category Reset • Equivalent to 3/PLd Emergency stop pushbutton Manual (Safety Edge) • Safety edge (2-wire cable on both sides) Motor M stops when emergency stop pushbutton S1 is pressed or when edge sensor detects a con- tact with persons or objects.
Page 926 Appendices Timing Chart Safety edge detected E-STOP pushed E-STOP released Reset ON Safety connection status (Units 2 to 4) E-STOP S1 Reset S2 Safety edge S3 KM1, KM2 EDM feedback MAX_Feedback_Time (T Safety I/O Terminal & I/O Map Setting l Safety I/O Terminal Settings A-62 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 927 Appendices l I/O Map Settings Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 928 Appendices Application Overview Safety category/PL Safety device Stop category Reset • Equivalent to 2/PLc Manual Emergency stop pushbutton • (Single Beam Safety Sen- Single beam safety sensor sor) Motor M stops when emergency stop pushbutton S1 is pressed. Motor M stops when the light in the single beam safety sensor is interrupted. Wiring Unit 2 (NX-SIH400) Unit 3 (NX-SIH400)
Page 929 Appendices Timing Chart E-STOP pushed E-STOP released Single beam interrupted Reset ON Safety connection status (Units 2 to 4) E-STOP S1 Reset S2 Single Beam S3 KM1, KM2 EDM feedback MAX_Feedback_Time (T Safety I/O Terminal & I/O Map Setting l Safety I/O Terminal Settings A-65 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 930 Appendices l I/O Map Settings Program Precautions for Safe Use • Test the functionality every six months to detect welded contactor contacts. • The customer is responsible for attaining conformance of the entire system to standards. • To detect electrical and mechanical failures, use a combination of redundant semiconductor output contacts and redundant mechanical output devices.
Page 931 Appendices A-5 Change Tracking What is Change Tracking? Change Tracking is used to display and manage changes in the safety application data after the pin is created. Tracking information is property information in safety application data. The storage of the safety appli- cation data settings at a given point in time is referred to as "creating a pin".
Page 932 Appendices Objects tab Type Name Description Safety Application TASK Safety Task Programs Function Blocks Global Variables I/O Map and exposed variables Safety process data communications Devices tab Type Name Description SAFEPLC Safety CPU Unit SAFEDEV Safety I/O Unit XVARDEF Exposed variables Pin Operations This section describes the procedures to create and delete pins, and the jump function.
Page 933 Appendices A-6 Safety CPU Unit Status The Safety CPU Unit status gives the operating status of the Safety CPU Unit. When a Safety CPU Unit is placed on the NX bus of the Communication Control Unit, the status is displayed as an I/O port in the I/O Map of the Communication Control Unit.
Page 934 Appendices Data I/O port Description Conditions type D06 CIP Safety No error in entire This variable is TRUE when the following condition is BOOL Target Con- CIP Safety Target met. If the condition is not met, it is FALSE. nection connections Condition •...
Page 935 Appendices A-7 I/O Ports of Safety I/O Units The I/O ports of the Safety I/O Units are displayed on the I/O Map of the Communication Control Unit if you place the Safety I/O Units on the Communication Control Unit. The names of the I/O ports that correspond to the data in the I/O Map of the Safety CPU Unit are giv- en in the "Corresponding port name"...
Page 936 Appendices Corre- spond- Port Data type Name Description Default ing port name Si00 Status BOOL Si00 Status Gives the status of safety input termi- nal 00. 0: Error 1: No error Si01 Status BOOL Si01 Status Gives the status of safety input termi- nal 01.
Page 937 Appendices A-7-2 NX-SID800 Safety Input Unit Corre- spond- Port Data type Name Description Default ing port name Standard Input WORD Standard In- 0000 hex 1st Word put 1st Word Si00 Logical Val- BOOL Si00 Logical Gives the status of safety input termi- Same Value nal Si00.
Page 938 Appendices Corre- spond- Port Data type Name Description Default ing port name IO Power Supply BOOL IO Power This flag indicates the status of the I/O Error Flag Supply Error power supply voltage. Flag 0: The I/O power supply voltage is nor- mal.
Page 939 Appendices Corre- spond- Port Data type Name Description Default ing port name So00 Monitor BOOL So00 Monitor Gives the status of safety output termi- So00 Value Value nal So00. Output 0: OFF, 1: ON Value So01 Monitor BOOL So01 Monitor Gives the status of safety output termi- So01 Value...
Page 940 Appendices Corre- spond- Port Data type Name Description Default ing port name So00 Monitor BOOL So00 Monitor Gives the status of safety output termi- So00 Value Value nal So00. Output 0: OFF, 1: ON Value So01 Monitor BOOL So01 Monitor Gives the status of safety output termi- So01 Value...
Page 941 Appendices Corre- spond- Port Data type Name Description Default ing port name So03 Status BOOL So03 Status Gives the status of safety output termi- nal 03. 0: Error 1: No error A-77 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 942 Appendices A-8 CIP Response Codes This section provides information on the response codes that are defined in the CIP specifications. They are stored in the received data of CIP messages that are sent to the Communication Control Unit or Safety CPU Unit. In case of the CIP Safety or tag data link not established error, an extended code supplementing the event information may be registered.
Page 943 Appendices General Status Status Name Description of Status Code (hex) Object does not exist An object that does not exist was specified for the requested serv- ice. Service fragmentation se- The fragmentation sequence for this service is not currently active quence not in progress for this data.
Page 944 Appendices General Status Status Name Description of Status Code (hex) Unknown Modbus Error A CIP to Modbus translator received an unknown Modbus Exception Code. Attribute not gettable A request to read a non-readable attribute was received. Instance Not Deletable The requested object instance cannot be deleted. Service Not Supported for The object supports the service, but not for the designated applica- Specified Path...
Page 945 Appendices General Additional Status Status Explanation (hex) (hex) 011D T->O Production Trigger not supported 011E Direction not supported 011F Invalid originator to target Network Connection Fixvar 0120 Invalid target to originator Network Connection Fixvar 0121 Invalid originator to target Network Connection Priority 0122 Invalid target to originator Network Connection Priority 0123...
Page 946 Appendices General Additional Status Status Explanation (hex) (hex) 0317 Either the segment is not present or the encoded value in the network segment is invalid. 0318 Link address to self is invalid. 0319 Resources on secondary are unavailable. 031A Connection is already established. 031B Direct connection is already established.
Page 947 Appendices A-9 Icon list for Safety Slave Unit Parame- ters The icons that you can set or change for Safety Slave Unit parameters are listed in the following table. A-9-1 External Device Icons for Input Devices Category Device Settable external device icons Safety Switch Emergency stop switch for dual channel equivalent input...
Page 948 Appendices Category Device Settable external device icons Safety Switch Safety key selector switch for dual-channel equivalent input Safety key selector switch for dual-channel complementary input Safety key selector switch for single channel Enabling switch Safety Sensor Safety light curtain Safety laser scanner High-Coded Door Switch High-Coded Door Switch (Guard Lock Model)
Page 949 Appendices Category Device Settable external device icons Standard Input De- Reset switch with test pulse vice Reset switch without test pulse A-85 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 950 Appendices Category Device Settable external device icons Generic Device Mechanical Contact for Single Channel Mechanical Contact for Dual Channel Equivalent Mechanical Contact for Dual Channel Complementary Semiconductor Output for Single Chan- Semiconductor Output for Dual Channel Equivalent Semiconductor Output for Dual Channel Complementary A-86 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 951 Appendices A-9-2 Contact Icons for Input Devices Category Device Settable contact icons Safety Switch Emergency stop switch for dual-channel equivalent input Emergency stop switch for single channel Safety door switch for dual-channel equivalent input Safety door switch for dual-channel complementary input 1NC/1NO 1NO/1NC Safety door switch...
Page 952 Appendices Category Device Settable contact icons Safety Switch Safety key selector switch for single channel Enabling switch Safety Sensor Safety light curtain OSSD1/OSSD2 Safety laser scanner OSSD1/OSSD2 Specialty devices Non-contact Door Switch Single Beam Safety Sensor OSSD1 Safety Mat/Safety Edge SafetyMat/ SafetyEdge EDM Feedback...
Page 953 Appendices Category Device Settable contact icons Generic Device Mechanical Contact for Dual Channel Complementary 1NC/1NO 1NO/1NC Semiconductor Output for Single Chan- OSSD1 Semiconductor Output for Dual Channel Equivalent OSSD1/OSSD2 Semiconductor Output for Dual Channel Complementary A-9-3 External Device Icons for Output Devices Category Device Settable external device icons...
Page 954 Appendices A-9-4 Contact Icons for Output Devices Category Device Settable contact icons Relays with Forcibly Relays with Forcibly Guided Con- Guided Contacts tacts for Dual Channel Load Relays with Forcibly Guided Contactor Contacts Relays with Forcibly Guided Con- tacts for Single Channel Load Relays with Forcibly Guided Contactor...
Page 955 Appendices A-10 Printing This section describes how to print information related to Safety Control Units from the Sysmac Studio. Refer to the Sysmac Studio Version 1 Operation Manual (Cat. No. W504) for basic printing procedures for the Sysmac Studio. A-10-1 Selecting the Items to Print Use the following procedure to set up printing for a Safety Control Unit.
Page 956 Appendices l Wiring Diagrams The wiring diagrams that are set on the Parameters Tab Page are printed. l Program The programs are printed. A-92 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 957 Appendices A-11 List of Screwless Clamping Terminal Block Models This section explains how to read the screwless clamping terminal block model numbers and shows the model number table. A-11-1 Model Notation The screwless clamping terminal block models are assigned based on the following rules. NX-TB Product type TB: Terminal block...
Page 958 Appendices Note When you purchase a terminal block, purchase an NX-TB£££2. A-94 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 959 Appendices A-12 I/O Refreshing between NX Units A-12-1 I/O Refreshing from the Communication Control Unit to NX Units The Communication Control Unit cyclically performs I/O refreshing with the NX Units. The following two cycles affect operation of the I/O refreshing between the Communication Control Unit and the NX Units.
Page 960 Appendices Setting the I/O Refreshing Methods For the Communication Control Unit, no setting operation is required, and the method is determined according to the following table. NX Unit that support both Free-Run refreshing and NX Unit that support only Free-Run refreshing synchronous I/O refreshing Free-Run refreshing Synchronous I/O refreshing...
Page 961 Appendices Free-Run Refreshing With this I/O refreshing method, the refresh cycle of the NX bus and the I/O refresh cycles of the NX Units are asynchronous. NX Units read inputs and refresh outputs at the time of I/O refreshing. This method is used when it is not necessary to be aware of factors such as the I/O timing jitter and the concurrency of the timing to read inputs and refresh outputs between the NX Units.
Page 962 Appendices Inputs (a) I/O refreshing for NX Units (d) Interval of the timing to read inputs is not constant. I/O refreshing of the NX bus Input refreshing Output refreshing ON/OFF response time Timing to read inputs Digital Input Unit A ON/OFF response time Input filter time...
Page 963 Appendices Synchronous Input Refreshing With this I/O refreshing method, the timing to read inputs is synchronized on a fixed interval between more than one NX Unit connected to the Communication Control Unit. This method is used when the problem such as input timing jitter or offset of timing to read inputs be- tween more than one NX Unit happens.
Page 964 Appendices I/O refreshing synchronization (c) Interval of I/O refreshing is not constant The longest AD conversion time is within one cycle. (d) Interval of synchronization timing (b) The Communication Control Unit reads is constant the data that is read by the Unit at I/O Not constant refreshing.
Page 965 Appendices • The interval of I/O refreshing varies with the processing conditions of the Communication Control Unit. (Refer to (c) in the figure below.) The timing of refreshing outputs will be at a fixed interval. (Refer to (d) and (e) in the figure below.) •...
Page 966 Appendices Formula: Maximum input response time = Tnx-InProc x 2 + Tnx-Indelay + 3.75 ms + Safety task period The elements in the formulas are as follows: • Safety task period: Setting of the safety task period in the Safety CPU Unit •...
Page 967 Appendices A-13 Units That Support Communications between NX Units Refer to A-19 Version Information on page A-112. A-103 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 968 Appendices A-14 Checking the Signature Code on the Seven-segment Indicator Use the following procedure to display a signature code on the seven-segment indicator on the front panel of the Safety CPU Unit. Press the service switch on the front panel of the Safety CPU Unit. If you hold down the service switch, the display of the seven-segment indicator will change as shown below.
Page 969 Appendices A-15 Execution Scenarios for the Simple Automatic Test The operations given in the following table are executed in order for the Simple Automatic Test. Test phase Executed processes Confirmations Displayed errors Initialize Set all the registered input varia- Examine all the registered output <Error>...
Page 970 Appendices All registered input variables <1-1> Reset variable <1-2> <1-3> All registered output variables <1-4> 2. Shutoff Test Target input variable <2-1> Output variables expected to be 0 <2-2> Output variables expected to be 1 <2-3> 3. Restore Test (Reset Type: Auto) Target input variable <3-1>...
Page 971 Appendices Target input variable <4-1> Reset variable <4-2> <4-3> Output variables expected to be 0 <4-5> <4-4> Output variables expected to be 1 <4-5> A-107 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 972 Appendices A-16 Differences in Checking Operation between the Simulator and Safety CPU Unit This section describes the differences in the program debugging functions that you can perform on the Sysmac Studio between online debugging on a Safety CPU Unit and offline debugging with the Simu- lator.
Page 973 Appendices A-17 I/O Data Enable Flag for CIP Safety Connections You can use the I/O data enable flag for CIP Safety connections in the safety program. ON and OFF Conditions of the I/O Data Enable Flag for CIP Safety Connections You can use the I/O data enable flag for CIP Safety connections in the safety program.
Page 974 Appendices The target instance variable name can be verified on the I/O Assembly Settings (Target) screen. Use "InstanceVariableName.S_RunIdleFlag" in the program POU. Precautions for Correct Use The I/O data enable flag for CIP Safety connections (S_RunIdleFlag) is supported by the NX- SL5500/NX-SL5700 unit version 1.4 or higher.
Page 975 Appendices A-18 Safety: Update Configurations and Setup Transfer Data If a standard controller and a Safety CPU Unit are transferred by using different projects, the following error may occur. Event name Event Code NX Bus Communications Settings and Safety Application Data Mismatch 10520000 hex If you cannot resolve the above error after you implement the normal correction, use the following pro- cedure.
Page 976 Appendices A-19 Version Information This section describes the compatibility between unit versions of the Safety Control Units and the ver- sion of the Sysmac Studio, as well as the functions supported by the Sysmac Studio. A-19-1 Relationship between the Unit Versions and Sysmac Studio Ver- sions This section describes the possible combinations of versions of Safety Control Units, Communication Control Units, and Sysmac Studio.
Page 977 Appendices Digital I/O Units NX Unit Corresponding unit version/version Communication Control Model Unit version Unit Sysmac Studio NX-CSG£££ NX-ID3317 Version 1.0 Version 1.00 Version 1.24 NX-ID3343 Version 1.0 Version 1.00 Version 1.24 NX-ID3417 Version 1.0 Version 1.00 Version 1.24 NX-ID3443 Version 1.0 Version 1.00 Version 1.24...
Page 978 Appendices Supported data types BOOL BYTE WORD DINT Analog I/O Units NX Unit Corresponding unit version/version Communication Control Model Unit version Unit Sysmac Studio NX-CSG£££ NX-AD2203 Version 1.0 Version 1.00 Version 1.24 NX-AD2204 Version 1.0 Version 1.00 Version 1.24 NX-AD2208 Version 1.0 Version 1.00 Version 1.24...
Page 979 Appendices Supported data types WORD DINT Temperature Input Units NX Unit Corresponding unit version/version Communication Control Model Unit version Unit Sysmac Studio NX-CSG£££ NX-TS2101 Version 1.0 Version 1.00 Version 1.24 NX-TS2101 Version.1.1 Version 1.00 Version 1.24 NX-TS2102 Version.1.1 Version 1.00 Version 1.24 NX-TS2104 Version.1.1...
Page 980 Appendices NX Unit Corresponding unit version/version Communication Control Model Unit version Unit Sysmac Studio NX-CSG£££ NX-PC0010 Version 1.0 Version 1.00 Version 1.24 NX-PC0020 Version 1.0 Version 1.00 Version 1.24 NX-PC0030 Version 1.0 Version 1.00 Version 1.24 NX-TBX01 Version 1.0 Version 1.00 Version 1.24 Communications between NX Units are not supported.
Page 981 Index NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 982 Index Index Additional I/O Power Supply Unit........4-5 Earthing Methods............5-67 Additional NX Unit Power Supply Unit.......4-4 End Cover ..............3-11, 5-17 Adjusting the communications load......... 11-2 End Plate............5-9, 5-10, 5-18 Adjusting the device bandwidth usage......11-5 Equipotential bonding system........ 5-67, 5-68 angle for insertion...........5-51, 5-53 Error Status variable...........15-16, 15-31 Applicable Wire..............5-46...
Page 983 Index safety input functions............6-28 dual channel evaluation..........6-30 LED..................15-2 dual channel ...........6-30, 6-42 Level................15-50 single channel ..........6-30, 6-42 input filters..............6-36 levels................15-8 Log category..............15-50 test pulse..............6-29 Lot number..............44, 3-21 safety output functions.............6-41 dual channel evaluation..........6-42 test pulse evaluation............ 6-42 safety program..............8-3 MAC addresses............
Page 984 Index Verifying data..............13-2 Wiring Ducts..............5-7 Wiring Terminal..............5-46 Wiring the Unit Power Supply..........5-33 NX-series Safety Control Unit/Communication Control Unit User's Manual (Z395)
Page 986 Hoffman Estates, IL 60169 U.S.A. Tel: (31) 2356-81-300 Fax: (31) 2356-81-388 Tel: (1) 847-843-7900 Fax: (1) 847-843-7787 ©OMRON Corporation 2018-2022 All Rights Reserved. OMRON ASIA PACIFIC PTE. LTD. OMRON (CHINA) CO., LTD. In the interest of product improvement, 438B Alexandra Road, #08-01/02 Alexandra Room 2211, Bank of China Tower, specifications are subject to change without notice.

This manual is also suitable for:

Sysmac nx-sl5 series Sysmac nx-si series Sysmac nx-so series Sysmac nx-csg series