Allen-Bradley GuardLogix 5570 User Manual

Hide thumbs Also See for GuardLogix 5570:
Table of Contents

Advertisement

User Manual
Original Instructions
GuardLogix 5570 Controllers
Catalog Numbers 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT,
1756-L72EROMS, 1756-L73EROMS

Advertisement

Table of Contents
loading

Summary of Contents for Allen-Bradley GuardLogix 5570

  • Page 1 User Manual Original Instructions GuardLogix 5570 Controllers Catalog Numbers 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT, 1756-L72EROMS, 1756-L73EROMS...
  • Page 2 Important User Information Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.
  • Page 3: Table Of Contents

    Table of Contents Preface ............9 Summary of Changes .
  • Page 4 Table of Contents Chapter 3 Configure the Controller Create a Controller Project ........47 Electronic Keying .
  • Page 5 Table of Contents Address Safety I/O Data ........86 Safety I/O Modules Address Format .
  • Page 6 Table of Contents Chapter 7 Go Online with the Controller Connect the Controller to the Network......125 Connect Your EtherNet/IP Device and Computer .
  • Page 7 Table of Contents Appendix A Status Indicators Controllers Status Indicators ........151 Controller Status Display .
  • Page 8 Table of Contents Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 9: Preface

    Use this manual if you are responsible for the design, installation, programming, or troubleshooting of control systems with GuardLogix 5570 controllers. You must have a basic understanding of electrical circuitry and familiarity with relay logic.
  • Page 10: About Guardlogix Controllers

    Table 1 provides a brief overview Controllers of those differences. Table 1 - Differences between GuardLogix 5570 and GuardLogix 5560 Controllers Feature GuardLogix 5570 Controllers GuardLogix 5560 Controllers (1756-L71S, 1756-L72S, 1756-L72EROMS, (1756-L61S, 1756-L62S,...
  • Page 11: Terminology

    European Norm The official European standard. Energy Storage Module Used for clock support and backup for memory retention at powerdown on GuardLogix 5570 controllers. Get System Value An instruction that retrieves specified controller-status information and places it in a destination tag.
  • Page 12 Helps with how to estimate memory use and execution time of programmed logic, and Manual, publication 1756-RM087 how to select different programming options. http://www.rockwellautomation.com/literature. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative. Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 13: System Overview

    For SIL 3 and PLe safety system requirements, including functional validation test intervals, system reaction time, and PFD/PFH calculations, refer to the GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099. You must read, understand, and fulfill these requirements before you operate a GuardLogix SIL 3, PLe safety system.
  • Page 14: Safety Network Number

    Chapter 1 System Overview Safety Network Number The safety network number (SNN) must be a unique number that identifies safety subnets. Each safety subnet that the controller uses for safety communication must have a unique SNN. Each safety I/O device must also be configured with the SNN of the safety subnet.
  • Page 15: Hmi Devices

    System Overview Chapter 1 HMI Devices HMI devices can be used with GuardLogix controllers. HMI devices can access standard tags as with a standard controller. However, HMI devices cannot write to safety tags; safety tags are read-only for HMI devices. Controller Data-flow This illustration explains the standard and safety data-flow capabilities of the GuardLogix controller.
  • Page 16: Select System Hardware

    Chapter 1 System Overview Select System Hardware The GuardLogix system supports SIL 3 and PLe safety applications. The GuardLogix controller is composed of a primary controller and a safety partner that function together in a 1oo2 architecture. Table 4 lists catalog numbers for primary controllers and safety partners.
  • Page 17: Safety Partner

    System Overview Chapter 1 A three-position key switch on the front of the primary controller governs the controller operational modes. The following modes are available: • RUN • PROGram • REMote–this software-enabled mode can be Program, Run, or Test Figure 2 - Key Switch Positions Logix557x FORCE SD 1756-L7xS...
  • Page 18: Select Communication Networks

    Chapter 1 System Overview Select Communication The GuardLogix controller supports communication that lets it do the following: Networks • Distribute and control Safety I/O on DeviceNet or EtherNet/IP networks • Distribute and control remote Safety I/O on DeviceNet, EtherNet/IP, or ControlNet networks •...
  • Page 19: Programming Requirements

    System Overview Chapter 1 Programming Requirements Table 7 to identify the programming tool and the versions for use with your GuardLogix 5570 controllers. Table 7 - Software Versions Cat. No. Studio 5000® RSLogix 5000® RSLinx® Classic Environment Software Version Software Version...
  • Page 20 Chapter 1 System Overview Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 21: Install The Controller

    Chapter Install the Controller Topic Page Precautions Make Sure That You Have All of the Components Install a Chassis and Power Supply Install the Controller Into the Chassis Insert or Remove a Memory Card Make Communication Connections Update the Controller Choose the Operating Mode of the Controller Uninstall an Energy Storage Module (ESM) Install an Energy Storage Module (ESM)
  • Page 22 Chapter 2 Install the Controller Table 10 - Programmable Electronic Systems (PES) ATTENTION: Personnel responsible for the application of safety-related Programmable Electronic Systems (PES) shall be aware of the safety requirements in the application of the system and shall be trained in using the system.
  • Page 23 Install the Controller Chapter 2 Table 13 - North American Hazardous Location Approval The following information applies when operating this equipment in Informations sur l'utilisation de cet équipement en environnements hazardous locations. dangereux. Les produits marqués “CL I, DIV 2, GP A, B, C, D” ne conviennent qu'à Products marked “CL I, DIV 2, GP A, B, C, D”...
  • Page 24: European Hazardous Location Approval

    Chapter 2 Install the Controller European Hazardous Location Approval The following applies when the product bears the Ex Marking. This equipment is intended for use in potentially explosive atmospheres as defined by European Union Directive 94/9/EC and has been found to comply with the Essential Health and Safety Requirements relating to the design and construction of Category 3 equipment intended for use in Zone 2 potentially explosive atmospheres, given in Annex II to this Directive.
  • Page 25: Make Sure That You Have All Of The Components

    Install the Controller Chapter 2 Make Sure That You Have All Before you begin, check to make sure you have all of the components you need. of the Components IMPORTANT You must use a primary controller and a safety partner to achieve SIL 3/ PLe.
  • Page 26: Install A Chassis And Power Supply

    Chapter 2 Install the Controller Install a Chassis and Before you install a controller, you need to install a chassis and power supply. Power Supply 1. Install a ControlLogix® chassis according to the corresponding installation instructions. Cat. No. Available Slots Series Refer to These Installation Instructions 1756-A4...
  • Page 27: Install The Controller Into The Chassis

    Install the Controller Chapter 2 Install the Controller Into You can install or remove a controller while chassis power is on and the system is operating. the Chassis WARNING: When you insert or remove the module while backplane power is on, an electric arc can occur. This could cause an explosion in hazardous location installations.
  • Page 28: Insert Or Remove A Memory Card

    Chapter 2 Install the Controller 3. Align the circuit board with the top and bottom guides in the chassis. 4. Slide the controller into the chassis. The controller is fully installed when it is flush with the power supply or other installed modules and the top and bottom latches are engaged.
  • Page 29: Remove The Sd Card

    Install the Controller Chapter 2 Remove the SD Card Follow these steps to remove the SD card. IMPORTANT Verify that the SD card status indicator is off and that the card is not in use before removing it. 1. Turn the key switch to the PROG position. 2.
  • Page 30: Install The Sd Card

    Chapter 2 Install the Controller Install the SD Card Follow these steps to install the SD card. 1. Verify that the SD card is locked or unlocked according to your preference. Unlocked Locked 32005-M 2. Open the door for the SD card. Log ix 55x x RUN FORC E SD 3.
  • Page 31: Make Communication Connections

    Install the Controller Chapter 2 5. Close the SD card door. Log ix 55x x RUN FORC E SD 32006-M Make Communication The controller has a USB port that uses a Type B receptacle. The connection is USB 2.0-compatible and runs at 12 M. Connections To use the USB port of the controller, you must have RSLinx®...
  • Page 32 Chapter 2 Install the Controller To configure RSLinx software to use a USB port, you need to first set up a USB driver. To set up a USB driver, perform this procedure. 1. Connect your controller and workstation by using a USB cable. 2.
  • Page 33: Update The Controller

    Install the Controller Chapter 2 4. Click Finish to set up your USB driver. 5. To browse to your controller in RSLinx software, click RSWho In the RSLinx Workstation organizer, your controller appears under two different drivers, a virtual chassis and the USB port. You can use either driver to browse to your controller.
  • Page 34 Chapter 2 Install the Controller 3. Click Next to begin the upgrade process. 4. Select your controller and click Next. Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 35 Install the Controller Chapter 2 5. Expand the network driver to locate your controller. 6. Select the controller and click OK. 7. Select the desired firmware revision and click Next. Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 36 Chapter 2 Install the Controller TIP If you experience a Script File Error after selecting the firmware revision number (see the following example), there is likely an anomaly with your firmware files. To recover, perform the following: • Go to http://www.rockwellautomation.com/support/ and download the firmware revision you are trying to upgrade.
  • Page 37 Install the Controller Chapter 2 Before the firmware update begins, this dialog box appears. Take the required action for your application. In this example, the upgrade continues when you click OK. A progress dialog box indicates the progress of the firmware upgrade. WARNING: Let the firmware update to fully complete before cycling power or otherwise interrupting the upgrade.
  • Page 38: Using Autoflash To Update Firmware

    Chapter 2 Install the Controller Using AutoFlash to Update Firmware To upgrade your controller firmware with the AutoFlash feature, complete these steps. IMPORTANT If the SD card is locked and the Load Image option of the stored project is set to On Power Up, the controller firmware is not updated as a result of these steps.
  • Page 39 Install the Controller Chapter 2 5. Select the firmware revision to upgrade to and click Update. 6. On the Update Firmware dialog box, click Yes. 7. On the ControlFLASH dialog box, click OK. When the upgrade is complete, the Update Status dialog box indicates that the upgrade is complete.
  • Page 40: Choose The Operating Mode Of The Controller

    Chapter 2 Install the Controller WARNING: Let the firmware update to fully complete before cycling power or otherwise interrupting the upgrade. TIP If the ControlFLASH upgrade of the controller is interrupted, the controllers revert to boot firmware, that is firmware revision 1.xxx. When the upgrade is complete, click OK on the Who Active dialog box.
  • Page 41: Use The Key Switch To Change The Operation Mode

    Install the Controller Chapter 2 Use the Key Switch to Change the Operation Mode The key switch on the front of the controller can be used to change the controller to one of these modes: • Program (PROG) • Remote (REM) •...
  • Page 42: Uninstall An Energy Storage Module (Esm)

    Chapter 2 Install the Controller Figure 5 - Operation Mode via the Logix Designer Application TIP For this example, the controller key switch is set to Remote Mode. If your controller key switch is set to Run Mode or Program Mode, the menu options change.
  • Page 43 Install the Controller Chapter 2 Follow these steps to remove a 1756-ESMCAP(XT), 1756-ESMNSE(XT), or 1756-SPESMNSE(XT) module. WARNING: If your application requires the ESM to deplete its residual stored energy to 40 μJoule or less before you transport it into or out of the application, you must use the 1756-ESMNSE(XT) module for the primary controller and the 1756-SPESMNSE(XT) for the safety partner.
  • Page 44: Install An Energy Storage Module (Esm)

    Chapter 2 Install the Controller 2. Use your thumb to press down on the black release and pull the ESM away from the controller. Log ix 55x x Log ix 55x x RUN FORCE SD RUN FORC E SD Install an Energy Storage Table 15 lists the ESMs and the compatible GuardLogix®...
  • Page 45 Install the Controller Chapter 2 2. Slide the ESM into the chassis until it snaps into place. ATTENTION: To avoid potential damage to the product when inserting the ESM, align the ESM in the track and slide forward with minimal force until the ESM snaps into place.
  • Page 46 Chapter 2 Install the Controller Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 47: Create A Controller Project

    2. To expand the list of controller options, double-click GuardLogix® 5570 Safety Controller. 3. Choose a GuardLogix controller: • 1756-L71S GuardLogix 5570 Safety Controller • 1756-L72S GuardLogix 5570 Safety Controller • 1756-L73S GuardLogix 5570 Safety Controller 4.
  • Page 48 Chapter 3 Configure the Controller 7. Choose the controller firmware major revision. 8. Choose the chassis size. 9. Choose the slot number. The New Project dialog box displays the slot location of the safety partner based on the slot number entered for the primary controller. If you select a slot number for the primary controller that does not accommodate placement of the safety partner immediately to the right of the primary controller, you are prompted to re-enter a valid slot...
  • Page 49 Configure the Controller Chapter 3 The Logix Designer application creates a safety task and a safety program. A main ladder logic safety routine called MainRoutine is also created within the safety program. Figure 6 - Safety Task in the Controller Organizer A red bar under the icon distinguishes safety programs and routines from standard project components in the Controller Organizer.
  • Page 50: Electronic Keying

    Chapter 3 Configure the Controller TIP You can use the Controller Properties dialog box to change the controller from standard to safety, or safety to standard, by clicking the Change Controller button. However, standard and safety projects are substantially affected. Appendix Change Controller Type, for details on the ramifications of...
  • Page 51: Set Passwords For Safety-Locking And -Unlocking

    Configure the Controller Chapter 3 Carefully consider the implications of each keying option when selecting one. IMPORTANT Changing Electronic Keying parameters online interrupts connections to the device and any devices that are connected through the device. Connections from other controllers can also be broken. If an I/O connection to a device is interrupted, the result can be a loss of data.
  • Page 52: Protect The Safety Task Signature In Run Mode

    Chapter 3 Configure the Controller Protect the Safety Task You can prevent the safety task signature from being either generated or deleted while the controller is in Run or Remote Run mode, regardless of whether the Signature in Run Mode safety application is locked or unlocked.
  • Page 53: Handling I/O Device Replacement

    Configure the Controller Chapter 3 Handling I/O Device The Safety tab of the Controller Properties dialog box lets you define how the controller handles the replacement of an I/O device in the system. This option Replacement determines whether the controller sets the safety network number (SNN) of an I/O device that it is connected to and has configuration data for when a safety task signature exists.
  • Page 54: Enable Time Synchronization

    Chapter 3 Configure the Controller Enable Time Synchronization In a GuardLogix controller system, one device in the local chassis must be designated as the coordinated system time (CST) master. Time synchronization provides a standard mechanism to synchronize clocks across a network of distributed devices.
  • Page 55: Configure A Peer Safety Controller

    Configure the Controller Chapter 3 Configure a Peer Safety You can add a peer safety controller to the I/O configuration folder of your safety project to allow standard or safety tags to be consumed. To share safety Controller data between peer controllers, you produce and consume controller-scoped safety tags.
  • Page 56 Chapter 3 Configure the Controller Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 57: The Safety Network

    Chapter Communicate over Networks Topic Page The Safety Network EtherNet/IP Communication ControlNet Communication DeviceNet Communication The Safety Network The CIP Safety protocol is an end-node to end-node safety protocol that provides routing of CIP Safety messages to and from safety I/O devices through bridges, switches, and routers.
  • Page 58 Chapter 4 Communicate over Networks Figure 10 shows a CIP safety system with seven different subnets where each subnet has one unique SNN. Figure 10 - CIP Safety Example with More Than One SNN Router/ Switch Switch Firewall SmartGuard CIP Safety I/O SNN_1 SNN_3 SNN_5...
  • Page 59: Assign The Safety Network Number (Snn)

    Communicate over Networks Chapter 4 Manual Safety Network Number If the manual format is selected, the SNN is entered as values from 1…9999 decimal. Figure 12 - Manual Entry Assign the Safety Network Number (SNN) You can allow the Logix Designer application to automatically assign an SNN, or you can assign the SNN manually.
  • Page 60: Change The Safety Network Number (Snn)

    Chapter 4 Communicate over Networks Automatic Versus Manual For typical users, the automatic assignment of an SNN is sufficient. However, manual manipulation of the SNN is required if the following is true: • Safety consumed tags are used. • The project consumes safety input data from a module whose configuration is owned by some other device.
  • Page 61 Communicate over Networks Chapter 4 3. Click Time-based and then Generate. 4. Click OK. Change the Safety Network Number (SNN) of Safety I/O Devices on the CIP Safety Network This example uses an EtherNet/IP™ network. 1. Find the first EtherNet/IP communication module in the I/O Configuration tree.
  • Page 62 Chapter 4 Communicate over Networks 6. Highlight the Number and click Copy to copy the new SNN to the Windows Clipboard. 7. Click OK to close the Safety Network Number dialog box. 8. Click OK to close the Module Properties dialog box. 9.
  • Page 63 Communicate over Networks Chapter 4 11. Choose Time-based and click Paste to paste that EtherNet/IP network’s SNN into that device. 12. Click OK. 13. Repeat steps 9…11 for the remaining safety I/O devices under that EtherNet/IP communication module. 14. Repeat steps 2…11 for any remaining network communication modules under the I/O Configuration tree.
  • Page 64 Chapter 4 Communicate over Networks 2. Click Copy. 3. Click OK to close the dialog box. 4. Click the General tab on the Module Properties dialog box of the I/O device in the I/O Configuration tree of the consuming controller project.
  • Page 65: Ethernet/Ip Communication

    Communicate over Networks Chapter 4 EtherNet/IP Communication For EtherNet/IP network communication in a GuardLogix system, you have several modules to choose from. For CIP safety communication, including safety I/O device control, choose any of the modules shown in Table 17, except the 1756-EWEB module that does not support CIP safety communication.
  • Page 66: Ethernet/Ip Network

    Chapter 4 Communicate over Networks These products are available for EtherNet/IP networks. Table 18 - Product for EtherNet/IP Modules Product Is Used to Required Studio 5000® environment • Configure the controller project • Define EtherNet/IP communication BOOTP/DHCP utility Assign IP addresses to devices on an EtherNet/IP network RSNetWorx™...
  • Page 67: Ethernet/Ip Communication Examples

    Communicate over Networks Chapter 4 EtherNet/IP Communication Examples Figure 13 illustrates the following communication functions: • The controllers can produce and consume standard or safety tags between each other. • The controllers can initiate MSG instructions that send/receive standard data or configure devices. •...
  • Page 68 Chapter 4 Communicate over Networks In the Logix Designer application, version 24 and later, the controller supports both standard and safety via a single connection. Figure 14 - EtherNet/IP Communication with Standard and Safety Connection Example 1768 Compact GuardLogix Controller with Distributed I/O 1768-ENBT Module 1756-EN2T Module...
  • Page 69: Ethernet/Ip Connections For Safety I/O Devices

    Communicate over Networks Chapter 4 EtherNet/IP Connections for Safety I/O Devices Safety I/O devices on EtherNet/IP networks are added to the project under the EtherNet/IP communication module as described in Add Safety I/O Devices on page 75. When you add a safety I/O device, the Logix Designer application automatically creates controller-scoped safety data tags for that device.
  • Page 70: Controlnet Communication

    Chapter 4 Communicate over Networks 2. After you physically install an EtherNet/IP module and set its IP address, add the module to the Controller Organizer in your GuardLogix controller project. 3. Use the Logix Designer application to download the project. ControlNet Communication For ControlNet communication, choose a 1756-CNB or 1756-CNBR module for standard communication, or a 1756-CN2, 1756-CN2R, or 1756-...
  • Page 71: Producing And Consuming Data Via A Controlnet Network

    Communicate over Networks Chapter 4 The ControlNet communication modules provide the following: • Support for messaging, produced/consumed safety and standard tags, and distributed I/O • They support the use of coax and fiber repeaters for isolation and increased distance. Producing and Consuming Data via a ControlNet Network The GuardLogix controller supports the ability to produce (send) and consume (receive) tags over ControlNet networks.
  • Page 72: Controlnet Communication Example

    Chapter 4 Communicate over Networks ControlNet Communication Example This example illustrates the following: • GuardLogix controllers can produce and consume standard or safety tags between each other. • GuardLogix controllers can initiate MSG instructions that send/receive standard data or configure devices. •...
  • Page 73: Devicenet Communication

    Communicate over Networks Chapter 4 DeviceNet Communication To communicate and exchange data with safety I/O devices on DeviceNet networks, you need a 1756-DNB module in the local chassis. For information on how to install your 1756-DNB module, refer to the ControlLogix DeviceNet Scanner Module Installation Instructions, publication 1756-IN566.
  • Page 74: Standard Devicenet Connections

    Chapter 4 Communicate over Networks Figure 17 - DeviceNet Module in Controller in the I/O Configuration Tree Standard DeviceNet Connections If you use standard DeviceNet I/O with your GuardLogix controller, you need to allocate two connections for each 1756-DNB module. One connection is for module status and configuration.
  • Page 75: Add Safety I/O Devices

    Chapter Add, Configure, Monitor, and Replace CIP Safety I/O Devices Topic Page Add Safety I/O Devices Configure Safety I/O Devices Set the IP Address by Using Network Address Translation (NAT) Set the Safety Network Number (SNN) Use Unicast Connections on EtherNet/IP Networks Set the Connection Reaction Time Limit Understanding the Configuration Signature Reset Safety I/O Device Ownership...
  • Page 76: Configure Safety I/O Devices

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices • Configuration signature See page for information on when the configuration signature is set automatically and when you need to set it. • Reaction time limit See page for information on setting the reaction time limit. •...
  • Page 77 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 3. Click Create. 4. Type a name for the new device. 5. To modify the Module Definition settings, click Change (if required). 6. Enter the node address for DeviceNet networks, or the IP address for EtherNet/IP networks.
  • Page 78: Set The Ip Address By Using Network Address Translation

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Set the IP Address by Using NAT translates one IP address to another IP address via a NAT-configured router or switch. The router or switch translates the source and destination Network Address Translation addresses within data packets as traffic passes between subnets.
  • Page 79: Set The Safety Network Number (Snn)

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 5. Click OK. The controller uses the translated address but CIP Safety protocol requires the actual address of the device. The assignment of a time-based SNN is automatic when adding new safety Set the Safety Network I/O devices.
  • Page 80: Specify The Requested Packet Interval (Rpi)

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Specify the Requested Packet Interval (RPI) The RPI specifies the period that data updates over a connection. For example, an input module produces data at the RPI that you assign. For safety input connections, you can set the RPI on the Safety tab of the Module Properties dialog box.
  • Page 81: View The Maximum Observed Network Delay

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 View the Maximum Observed Network Delay When the GuardLogix controller receives a safety packet, the software records the maximum observed network delay. For safety inputs, the Maximum Observed Network Delay displays the round-trip delay from the input module to the controller and the acknowledge back to the input module.
  • Page 82: Parameters

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Set the Advanced Connection Reaction Time Limit Parameters Configure connection parameters like the timeout multiplier and network delay multiplier on the Advanced Connection Reaction Time Limit dialog box. Figure 21 - Advanced Configuration Timeout Multiplier The Timeout Multiplier determines the number of RPIs to wait for a packet before declaring a connection timeout.
  • Page 83 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Network Delay Multiplier The Network Delay Multiplier defines the message transport time that is enforced by the CIP Safety protocol. The Network Delay Multiplier specifies the round-trip delay from the producer to the consumer and the acknowledge back to the producer.
  • Page 84 [20 + 10]  50 = 60% Table 23 - Additional Resources Resource Description GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099 Guard I/O™ DeviceNet Safety Modules User Manual, Provides information on calculating reaction times.
  • Page 85: Understanding The Configuration Signature

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Understanding the Each safety device has a unique configuration signature that defines the module configuration. The configuration signature is composed of an ID Configuration Signature number, date, and time, and is used to verify a module’s configuration. Configuration via the Logix Designer Application When the I/O device is configured by using the Logix Designer application, the configuration signature is generated automatically.
  • Page 86: Reset Safety I/O Device Ownership

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Reset Safety I/O Device When the controller project is online, the Safety tab of the Module Properties dialog box displays the current configuration ownership. When the opened Ownership project owns the configuration, Local is displayed. When a second device owns the configuration, Remote is displayed, along with the safety network number (SNN), and node address or slot number of the configuration owner.
  • Page 87: Kinetix 5500, Kinetix 5700, And Powerflex 527 Drive

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Kinetix 5500, Kinetix 5700, and PowerFlex 527 Drive Address Format A Kinetix® 5500, Kinetix 5700, and PowerFlex® 527 drive address follows this example. EXAMPLE Drivename:Type.Member Table 25 - Drive Safety I/O Device Address Format Where Drivename The name of the Kinetix or PowerFlex drive...
  • Page 88: Monitor Safety I/O Device Status

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Monitor Safety I/O Device You can monitor safety I/O device status via Explicit Messaging or via the status indicators on the I/O modules. Refer to the Guard I/O manuals listed in Status Additional Resources on page 11 for information on I/O module...
  • Page 89: Reset A Module To Out-Of-Box Condition

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Reset a Module to Out-of-box If a Guard I/O module was used previously, clear the existing configuration before installing it on a safety network by resetting the module to its out-of-box Condition condition.
  • Page 90: Replace A Device By Using The Logix Designer Application

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Replace a Device by Using the You can use the Logix Designer application to replace a safety I/O device on an Ethernet network. To replace a Guard I/O module on a DeviceNet network, Logix Designer Application your choice depends on the type of module.
  • Page 91: Replacement With 'Configure Only When No Safety

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Replacement with ‘Configure Only When No Safety Signature Exists’ Enabled When a safety I/O device is replaced, the configuration is downloaded from the safety controller if the DeviceID of the new device matches the original. The DeviceID is a combination of the node/IP address and the Safety Network Number (SNN) and is updated whenever the SNN is set.
  • Page 92 Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Scenario 1 - Replacement Device Is Out-of-box and Safety Signature Exists 1. Remove the old I/O device and install the new device. 2. Right-click the replacement safety I/O device and choose Properties. 3.
  • Page 93 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Scenario 2 - Replacement Device SNN Is Different from Original and Safety Signature Exists 1. Remove the old I/O device and install the new device. 2. Right-click your safety I/O device and choose Properties. 3.
  • Page 94 Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices 8. Click Set. 9. Verify that the Network Status (NS) status indicator is alternating red/ green on the correct device before clicking Yes on the confirmation dialog box to set the SNN and accept the replacement device. 10.
  • Page 95 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Scenario 3 - Replacement Device SNN Is Different from Original and No Safety Signature Exists 1. Remove the old I/O device and install the new device. 2. Right-click your safety I/O device and choose Properties. 3.
  • Page 96: Replacement With 'Configure Always' Enabled

    Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Replacement with ‘Configure Always’ Enabled ATTENTION: Enable the ‘Configure Always’ feature only if the entire CIP Safety Control System is not being relied on to maintain SIL 3 behavior during the replacement and functional testing of a device.
  • Page 97: Replace A Point Guard I/O Module By Using Rsnetworx

    Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 Replace a POINT Guard I/O Follow these steps to replace a POINT Guard I/O module when the module and the controller are on a DeviceNet network. Module by Using RSNetWorx for DeviceNet Software 1.
  • Page 98 Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices 6. Verify that the (NS) network status indicator is flashing on the correct module and click OK to set the SNN on that device. RSNetWorx for DeviceNet software confirms that the SNN has been set.
  • Page 99 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Chapter 5 If the configuration downloaded to the module is not from the original DNT file, the configuration signature does not match the original. Even if you recreate the same parameters in a new DNT file, the time and date portions of the signature are different so the connection to the controller is not made.
  • Page 100 Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Devices Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 101: Develop Safety Applications

    For guidelines and requirements for developing and commissioning SIL 3 and PLe safety applications, refer to the GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099.
  • Page 102: The Safety Task

    Chapter 6 Develop Safety Applications The Safety Task When you create a safety controller project, the Studio 5000 Logix Designer® application automatically creates a safety task with a safety program and a main (safety) routine. Figure 24 - Safety Task in the Controller Organizer Within the safety task, you can use multiple safety programs, composed of multiple safety routines.
  • Page 103: Safety Task Execution

    However, all safety I/O connections are closed and then re- opened once the controller is in Run mode. The safety task period directly affects system reaction time. The GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099, provides detailed information on calculating system reaction time.
  • Page 104: Safety Routines

    Chapter 6 Develop Safety Applications Safety Routines Safety routines have all the attributes of standard routines, except that they exist only in a safety program. At this time, only ladder diagram is supported for safety routines. TIP A watermark feature visually distinguishes a safety routine from a standard routine.
  • Page 105: Tag Type

    Develop Safety Applications Chapter 6 To create a safety tag, open the New Tag dialog box by right-clicking Controller Tags or Program Tags and choose New Tag. Figure 26 - Creating a New Tag Tag Type Table 30 defines the four types of tags. Table 30 - Four Tag Types Tag Type Description...
  • Page 106: Data Type

    Chapter 6 Develop Safety Applications Data Type The data type defines the type of data that the tag stores, such as bit or integer. Data types can be combined to form structures. A structure provides a unique data type that matches a specific need. Within a structure, each individual data type is called a member.
  • Page 107: Scope

    Develop Safety Applications Chapter 6 Scope A tag’s scope determines where you can access the tag data. When you create a tag, you define it as a controller tag (global data) or a program tag for a specific safety or standard program (local data). Safety tags can be controller-scoped or safety program-scoped.
  • Page 108: Class

    Chapter 6 Develop Safety Applications Class Tags can be classified as standard or safety. Tags classified as safety tags must have a data type that is permitted for safety tags. When you create program-scoped tags, the class is automatically specified, depending upon whether the tag was created in a standard or safety program.
  • Page 109: Produced/Consumed Safety Tags

    Develop Safety Applications Chapter 6 Produced/Consumed Safety To transfer safety data between GuardLogix controllers, you use produced and consumed safety tags. Produced and consumed tags require connections. The Tags default connection type for produced and consumed tags is unicast. Table 34 - Produced and Consumed Connections Connection Description Produced A GuardLogix controller can produce (send) safety tags to other 1756 or 1768 GuardLogix...
  • Page 110 Chapter 6 Develop Safety Applications Follow these steps to copy and paste the SNN. 1. Add the producer controller to the consumer-controller I/O tree. TIP The same producing controller must not appear more than once in your controller I/O tree or a verification error occurs. Consumer Controller Producer Controller 2.
  • Page 111 Develop Safety Applications Chapter 6 4. Copy the producer-controller SNN. 5. In the consumer-controller project, right-click the producer controller and choose Module Properties. 6. Click to open the Safety Network Number dialog box. 7. Paste the producer controller’s SNN into the SNN field and click OK. The safety network numbers match.
  • Page 112: Produce A Safety Tag

    Chapter 6 Develop Safety Applications Produce a Safety Tag Follow this procedure to produce a safety tag. 1. In the producing controllers project, create a user-defined data type defining the structure of the data to be produced. Make sure that the first data member is of the CONNECTION_STATUS data type.
  • Page 113: Consume Safety Tag Data

    Develop Safety Applications Chapter 6 Consume Safety Tag Data Follow these steps to consume data produced by another controller. 1. In the consumer controller’s project, create a user-defined data type identical to the one created in the producer project. TIP The user-defined type can be copied from the producer project and pasted into the consumer project.
  • Page 114 Chapter 6 Develop Safety Applications 8. In the Requested Packet Interval (RPI) field, enter the RPI for the connection in 1 ms increments. The default is 20 ms. Consumer’s Project Producer’s Project The RPI specifies the period when data updates over a connection. The RPI of the consumed safety tag must match the safety task period of the producing safety project.
  • Page 115 Develop Safety Applications Chapter 6 9. If the Connection Reaction time limit is acceptable, click OK; or for more complex requirements, click Advanced to set the Advanced Connection Reaction Time Limit parameters. The Timeout Multiplier determines the number of RPIs to wait for a packet before declaring a connection timeout.
  • Page 116: Safety Tag Mapping

    You must not directly control a SIL 3/PLe safety output with standard tag data. Refer to the GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099, for more information.
  • Page 117: Create Tag Mapping Pairs

    Develop Safety Applications Chapter 6 Create Tag Mapping Pairs 1. Choose Map Safety Tags from the Logic menu to open the Safety Tag Mapping dialog box. 2. Add an existing tag to the Standard Tag Name or Safety Tag Name column by typing the tag name into the cell or choosing a tag from the pull-down menu.
  • Page 118: Monitor Tag Mapping Status

    Chapter 6 Develop Safety Applications Monitor Tag Mapping Status The leftmost column of the Safety Tag Mapping dialog box indicates the status of the mapped pair. Table 37 - Tag Mapping Status Icons Cell Contents Description Empty Tag mapping is valid. When offline, the X icon indicates that tag mapping is invalid.
  • Page 119 Develop Safety Applications Chapter 6 The following actions are not permitted in the safety portion of the application when the controller is safety-locked: • Online/offline programming or editing (including safety Add-On Instructions) • Forcing safety I/O • Changing the inhibit state of safety I/O or produced connections •...
  • Page 120: Generate A Safety Task Signature

    Chapter 6 Develop Safety Applications You can safety-lock and -unlock the controller from the Safety tab of the Controller Properties dialog box, or by choosing Tools>Safety>Safety Lock/ Unlock. Figure 27 - Safety-locking the Controller If you set a password for the safety-lock feature, you must type it in the Enter Password field.
  • Page 121 Develop Safety Applications Chapter 6 Click Generate to generate the safety task signature from the Safety tab of the Controller Properties dialog box. You can also choose Tools>Safety>Generate Signature. Figure 28 - Safety Tab If a previous signature exists, you are prompted to overwrite it. TIP Safety task signature creation and deletion is logged in the controller log.
  • Page 122: Programming Restrictions

    ATTENTION: If you delete the safety task signature, you must retest and revalidate your system to meet SIL 3/PLe. Refer to the GuardLogix 5570 and Compact GuardLogix 5370 Controller Systems Safety Reference Manual, publication 1756-RM099, for more information on SIL 3/PLe requirements.
  • Page 123 Develop Safety Applications Chapter 6 If even one of these conditions apply, you cannot do the following: • Create or modify safety objects, including safety programs, safety routines, safety tags, safety Add-On Instructions, and safety I/O devices. IMPORTANT The scan times of the safety task and safety programs can be reset when online.
  • Page 124 Chapter 6 Develop Safety Applications Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 125: Connect The Controller To The Network

    Chapter Go Online with the Controller Topic Page Connect the Controller to the Network Understanding the Factors that Affect Going Online Download Upload Go Online Connect the Controller to If you have not done so, connect the controller to the network. the Network Table 38 - Communication Connections For this type of...
  • Page 126: Connect Your Ethernet/Ip Device And Computer

    Chapter 7 Go Online with the Controller Connect Your EtherNet/IP Device and Computer WARNING: If you connect or disconnect the communication cable with power applied to this module or any device on the network, an electric arc can occur. This could cause an explosion in hazardous location installations. Be sure that power is removed or the area is nonhazardous before proceeding.
  • Page 127: Understanding The Factors That Affect Going Online

    Go Online with the Controller Chapter 7 Understanding the Factors The Studio 5000 Logix Designer® application determines whether you can go online with a target controller based on whether the offline project is new or that Affect Going Online whether changes occurred in the offline project. If the project is new, you must first download the project to the controller.
  • Page 128: And -Unlocked Status

    Chapter 7 Go Online with the Controller Safety Task Signature and Safety-locked and -unlocked Status The existence of a safety task signature and the safety-locked or -unlocked status of the controller affect both the upload and download processes. On Upload If the controller has a safety task signature, the safety task signature and the safety task lock status are uploaded with the project.
  • Page 129: Download

    Go Online with the Controller Chapter 7 Download Follow these steps to transfer your project from your computer to your controller. Controller Project Download 1. Turn the key switch of the controller to REM. 2. Open the controller project that you want to download. 3.
  • Page 130: Upload

    Chapter 7 Go Online with the Controller 5. Follow the directions in this table to complete the download based on the Logix Designer application’s response. If the software indicates Then Download to the controller. Choose Download. The project downloads to the controller and goes online. Unable to download to the controller.
  • Page 131 Go Online with the Controller Chapter 7 3. If the project file does not exist, choose File>Select>Yes. 4. If the project file exists, select it. If the project to controller match is enabled, the Logix Designer application checks whether the serial number of the open project and the serial number of the controller match.
  • Page 132: Go Online

    Chapter 7 Go Online with the Controller Go Online Follow these steps to go online to monitor a project that the controller is executing. Controller Online Project Project 1. Define the path to the controller. a. Click Who Active b. Select the controller. To expand a level, click the + sign.
  • Page 133 Go Online with the Controller Chapter 7 3. Follow the directions in the table below to connect to the controller. Table 40 - Connect to the Controller If the software indicates Then Unable to connect to controller. Mismatch between the Connect to the correct controller, select another project file, or choose the Update project serial number checkbox offline project and the controller serial number.
  • Page 134 Chapter 7 Go Online with the Controller Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 135: Use Memory Cards For Nonvolatile Memory

    Chapter Store and Load Projects Using Nonvolatile Memory Topic Page Use Memory Cards for Nonvolatile Memory Store a Safety Project Load a Safety Project Use Energy Storage Modules Estimate the ESM Support of the WallClockTime Manage Firmware with Firmware Supervisor GuardLogix®...
  • Page 136: Store A Safety Project

    Chapter 8 Store and Load Projects Using Nonvolatile Memory ATTENTION: Do not remove the memory card while the controller is reading from or writing to the card, as indicated by a flashing green OK status indicator. This could corrupt the data on the card or in the controller, as well as corrupt the latest firmware in the controller.
  • Page 137: Load A Safety Project

    Store and Load Projects Using Nonvolatile Memory Chapter 8 If a safety task signature exists when you store a project, the following occurs: • Safety tags are stored with the value they had when the signature was first created. • Standard tags are updated. •...
  • Page 138: Use Energy Storage Modules

    Chapter 8 Store and Load Projects Using Nonvolatile Memory Use Energy Storage Modules You can use the GuardLogix ESMs to execute either of the following tasks: • Provide power to the controller to save the program to the controller’s on-board non-volatile storage (NVS) memory after power is removed from the chassis or the controller is removed from a powered chassis.
  • Page 139: Clear The Program From On-Board Nvs Memory

    Store and Load Projects Using Nonvolatile Memory Chapter 8 Immediately after the controller is no longer powered, the OK status indicator transitions to solid red and remains that way long enough to save the program. Figure 31 - OK Status Indicator. Logix557x FORCE SD 2.
  • Page 140: Estimate The Esm Support Of The Wallclocktime

    Chapter 8 Store and Load Projects Using Nonvolatile Memory Estimate the ESM Support of The ESM provides support for the maintenance of the WallClockTime attribute of the controller when power is not applied. Use this table to estimate the WallClockTime the hold-up time of the ESM, based on the temperature of the controller and installed ESM.
  • Page 141: View Status Via The Online Bar

    Chapter Monitor Status and Handle Faults Topic Page View Status via the Online Bar Monitor the Connections Monitor the Status Flags Monitor the Safety Status Controller Faults Developing a Fault Routine Appendix Status Indicators for information on interpreting the controller’s status indicators and display messages. View Status via the Online The online bar displays project and controller information, including the controller’s status, force status, online edit status, and safety status.
  • Page 142: Monitor The Connections

    Chapter 9 Monitor Status and Handle Faults The Safety Status button itself indicates whether the controller is safety-locked or -unlocked, or faulted. It also displays an icon that shows the safety status. Table 44 - Safety Status Icon If the safety status is This icon is displayed Safety Task OK Safety Task Inoperable...
  • Page 143: Safety Connections

    Monitor Status and Handle Faults Chapter 9 Safety Connections For tags associated with produced or consumed safety data, you can monitor the status of safety connections by using the CONNECTION_STATUS member. For monitoring input and output connections, safety I/O tags have a connection status member called SafetyStatus.
  • Page 144: Monitor The Safety Status

    Chapter 9 Monitor Status and Handle Faults Monitor the Safety Status View controller safety status information on the safety status button on the online bar and on the Safety tab of the Controller Properties dialog box. Figure 34 - Safety Task Status These are the possible values for safety status: •...
  • Page 145: Controller Faults

    Monitor Status and Handle Faults Chapter 9 Controller Faults Faults in the GuardLogix system can be nonrecoverable controller faults, nonrecoverable safety faults in the safety application, or recoverable safety faults in the safety application. Nonrecoverable Controller Faults These occur when the controller’s internal diagnostics fail. If a nonrecoverable controller fault occurs, safety task execution stops and safety I/O devices are placed in the safe state.
  • Page 146: View Faults

    Chapter 9 Monitor Status and Handle Faults Recoverable faults let you edit the standard and safety application as required to correct the cause of the fault. However, if a safety task signature exists or the controller is safety-locked, you must first unlock the controller and delete the safety task signature before you can edit the safety application.
  • Page 147: Developing A Fault Routine

    Monitor Status and Handle Faults Chapter 9 Developing a Fault Routine If a fault condition occurs that is severe enough for the controller to shut down, the controller generates a major fault and stops the execution of logic. Some applications do not want all safety faults to shut down the entire system. In those situations, use a fault routine to clear a specific fault and let the standard control portion of your system continue to operate or configure some outputs to remain ON.
  • Page 148: Use Gsv/Ssv Instructions

    Chapter 9 Monitor Status and Handle Faults Use GSV/SSV Instructions Logix controllers store system data in objects rather than in status files. You can use the Get System Value (GSV) and Set System Value (SSV) instructions to retrieve and set controller data. The GSV instruction retrieves the specified information and places it in the specified destination.
  • Page 149: Rockwell Automation Publication 1756-Um022D-En-P - May

    Monitor Status and Handle Faults Chapter 9 Table 47 - GSV/SSV Accessibility (Continued) Accessible from Accessible from Safety the Safety Task Standard Tasks Attribute Name Data Type Attribute Description Object SafetyLocked SINT Indicates whether the controller is safety-locked or -unlocked. SafetyStatus Specifies the safety status as the following: •...
  • Page 150 Chapter 9 Monitor Status and Handle Faults Capture Fault Information The SafetyStatus and SafetyTaskFaultRecord attributes can capture information about non-recoverable faults. Use a GSV instruction in the controller fault handler to capture and store fault information. The GSV instruction can be used in a standard task in conjunction with a controller fault handler routine that clears the fault and lets the standard tasks continue executing.
  • Page 151: Controllers Status Indicators

    Appendix Status Indicators Topic Page Controllers Status Indicators Controller Status Display Controllers Status Indicators The status of the primary controller is displayed via four status indicators. Table 49 - Primary Controller Status Indicator Descriptions Indicator Status Description No user tasks running. Controller is in PROGram mode. Green Controller is in RUN mode.
  • Page 152: Controller Status Display

    Appendix A Status Indicators The safety partner has an OK status indicator. Table 50 - 1756-L7SP Status Indicator Indicator Status Description No power is applied. Green The safety partner is operating with no faults. Powering up or nonrecoverable controller fault. Controller Status Display The controller status display scrolls messages that provide information about the controller’s firmware revision, energy storage module (ESM) status, project...
  • Page 153: General Status Messages

    Status Indicators Appendix A General Status Messages The messages described in Table 52 are typically indicated upon powerup, powerdown, and while the controller is running. These messages indicate the status of the controller and the ESM. Table 52 - General Status Display Message Interpretation No message is indicated...
  • Page 154: Fault Messages

    Appendix A Status Indicators Fault Messages If the controller is faulted, these messages can be indicated on the status display. Table 53 - Fault Messages Message Interpretation Major Fault TXX:CXX message A major fault of Type XX and Code XX has been detected. For example, if the status display indicates Major Fault T04:C42 Invalid JMP Target, then a JMP instruction is programmed to jump to an invalid LBL instruction.
  • Page 155: Major Recoverable Fault Messages

    Status Indicators Appendix A Major Recoverable Fault Messages Major recoverable faults are indicated by Major Fault TXX:CXX message on the controller status display. Table 54 lists specific fault types, codes, and the associated messages as they are shown on the status display. For detailed descriptions and suggested recovery methods for major recoverable faults, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014.
  • Page 156 Appendix A Status Indicators Table 54 - Major Recoverable Fault Messages Type Code Message Type Code Message CST Reference Loss Detected ™ CIP Motion Initialization Fault CIP Motion Initialization Fault Mfg CIP Motion Axis Fault CIP Motion Axis Fault Mfg User-defined CIP Motion Fault CIP Module Fault...
  • Page 157: I/O Fault Codes

    Status Indicators Appendix A I/O Fault Codes I/O faults indicated by the controller are indicated on the status display in one of these formats: • I/O Fault Local:X #XXXX message • I/O Fault ModuleName #XXXX message • I/O Fault ModuleParent:X #XXXX message The first part of the format is used to indicate the location of the faulted module.
  • Page 158 Appendix A Status Indicators Code Message Code Message #0108 Invalid Connection Type #0801 Incompatible Multicast RPI #0109 Invalid Connection Size #0802 Invld Safety Conn Size #0110 Module Not Configured #0803 Invld Safety Conn Format #0111 RPI Out of Range #0804 Invld Time Correct Conn Format #0113 Out of Connections...
  • Page 159: Change From A Standard To A Safety Controller

    Appendix Change Controller Type Topic Page Change from a Standard to a Safety Controller Change from a Safety to a Standard Controller Change Safety Controller Types Because safety controllers have special requirements and do not support certain standard features, you must understand the behavior of the system when changing the controller type from standard to safety or from safety to standard in your controller project.
  • Page 160: Change From A Safety To A Standard Controller

    Appendix B Change Controller Type Change from a Safety to a Upon confirmation of a change from a safety controller project to a standard controller, some components are changed and others are deleted, as described Standard Controller below: • The safety partner is deleted from the I/O chassis. •...
  • Page 161: Change Safety Controller Types

    Compact GuardLogix controller. TIP A GuardLogix 5570 controller supports 100 safety programs in the safety task while a 1768 Compact GuardLogix controller supports 32. Floating-point instructions, such as FAL, FLL, FSC, SIZE, CMP, SWPB, and CPT are supported in GuardLogix 5570 controllers, but not in GuardLogix 5560 and 1768 Compact GuardLogix controllers.
  • Page 162 Appendix B Change Controller Type Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 163: Index

    Index Numerics 1756-Axx 26 base tags 105 1756-CN2 70 BAT indicator 141 1756-CN2R 70 battery 1756-CN2RXT 70 fault 141 1756-CNB 70 1756-CNBR 70 1756-DNB 73 changing controllers 160 1756-EN2F 65 chassis 17 1756-EN2T 65 catalog numbers 26 1756-EN2TR 65 CIP Safety 11 1756-EN2TRXT 65 CIP Safety I/O 1756-EN2TXT 65...
  • Page 164: Rockwell Automation Publication 1756-Um022D-En-P - May

    Index controller … change type 159 editing 121 configuration 47 electronic keying 50 extreme environment 10 electrostatic discharge 22 fault handler 147 feature differences 10 enclosure 21 installation 27 energy storage module 25 logging 1756-ESMCAP 25 safety lock, unlock 119 charging 27 safety task signature 121 definition 11...
  • Page 165 Index memory capacity 16 gateway 69 memory card 135 general status messages 153 installation 28 get system value (GSV) removal 28 accessibility 148 message definition 11 status display 153 using 148 messages go online 132 fault 154 factors 127 general status 153 Guard I/O module safety status 152 …...
  • Page 166 Index reset module 89 password ownership 86 set 51 reset module 89 valid characters 51 restrictions paste programming 122 safety network number 63 safety tag mapping 116 peer safety controller software 122 configuration 55 when safety signature exists 121 location 109 when safety-locked 119 sharing data 109 RIUP...
  • Page 167 Index safety tab 120 software configuration signature 85 ControlNet network 70 connection data 79 DeviceNet networks 73 generate safety task signature 121 restrictions 122 module replacement 90 USB 31 safety-lock 120 standard data in a safety routine 116 safety-lock controller 120 status unlock 120 …...
  • Page 168 Index user memory 16 UV radiation 22 verification errors changing controller type 161 view safety status 127 WallClockTime 138 energy storage module 140 object 45 watchdog time 102 See extreme environment. Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 169 Index Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 170 Index Notes: Rockwell Automation Publication 1756-UM022D-EN-P - May 2017...
  • Page 172 Rockwell Automation maintains current product environmental information on its website at http://www.rockwellautomation.com/rockwellautomation/about-us/sustainability-ethics/product-environmental-compliance.page. Allen-Bradley, Armor, ControlFLASH, ControlLogix, DriveLogix, FlexLogix, Guard I/O, GuardLogix, Integrated Architecture, Kinetix, Logix5000, PanelView, PhaseManager, PLC-5, POINT Guard I/O, PowerFlex, Rockwell Automation, Rockwell Software, RSLinx, RSLogix 5000, RSNetWorx, Studio 5000, and Studio 5000 Logix Designer are trademarks of Rockwell Automation, Inc.

Table of Contents