User Manual GuardLogix 5570 Controllers Catalog Numbers 1756-L71S, 1756-L72S, 1756-L73S, 1756-L7SP, 1756-L73SXT, 1756-L7SPXT Studio 5000 Environment, version 21 or later
Important User Information Solid-state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid-state equipment and hard-wired electromechanical devices.
Table of Contents Preface About GuardLogix Controllers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Studio 5000 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Understanding Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Install an Energy Storage Module (ESM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Chapter 3 Configure the Controller Create a Controller Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Passwords for Safety-locking and -unlocking . . . . . . . . . . . . . . . . . . . . Protecting the Safety Task Signature in Run Mode . . . . . . . . . . . . . . . . . . Handling I/O Module Replacement . . . . . . . . . . . . . . . . . . . . . . . .
Table of Contents Monitor Safety I/O Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resetting a Module to Out-of-box Condition . . . . . . . . . . . . . . . . . . . . . . Replacing a Module by Using the Logix Designer Application . . . . . . . Replacement with ‘Configure Only When No Safety Signature Exists’ Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Replacement with ‘Configure Always’ Enabled. . . . . . . . . . . . .
Table of Contents Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Go Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Chapter 8 Store and Load Projects Using Nonvolatile Memory Using Memory Cards for Nonvolatile Memory . . . . . . . . . . . . . . . . . . . . Storing a Safety Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Topic Page About GuardLogix Controllers 7 Studio 5000 Environment 8 Understanding Terminology 9 Additional Resources 10 This manual is a guide for using GuardLogix® 5570 controllers in Studio 5000™ Logix Designer applications. It describes the GuardLogix-specific procedures you use to configure, operate, and troubleshoot your controller. Use this manual if you are responsible for designing, installing, programming, or troubleshooting control systems that use GuardLogix 5570 controllers.
Preface The extreme environment GuardLogix controller, catalog numbers 1756-L73SXT and 1756-L7SPXT, provides the same functionality as the 1756-L73S controller, but is designed to withstand temperatures of -25...70 °C (-13...158 °F). IMPORTANT Studio 5000 Environment Logix-XT system components are rated for extreme environmental conditions only when used properly with other Logix-XT system components.
Preface Understanding Terminology This table defines terms used in this manual. Table 2 - Terms and Definitions Abbreviation Full Term Definition 1oo2 One Out of Two Refers to the behavioral design of a multi-processor safety system. CIP Common Industrial Protocol A communication protocol designed for industrial automation applications. CIP Safety Common Industrial Protocol – Safety Certified SIL 3/PLe rated version of CIP.
Preface Additional Resources These documents contain additional information concerning related products from Rockwell Automation. Table 3 - Publications Related to GuardLogix Controllers and Systems Resource Description GuardLogix 5570 Controller Systems Safety Reference Manual, publication 1756-RM099 Contains detailed requirements for achieving and maintaining SIL 3/PLe with the GuardLogix 5570 controller system, using the Studio 5000 Logix Designer application.
Chapter 1 System Overview Topic Safety Application Requirements Page Safety Application Requirements 11 Distinguishing between Standard and Safety Components 12 Controller Data Flow Capabilities 13 Selecting System Hardware 14 Selecting Safety I/O Modules 15 Selecting Communication Networks 16 Programming Requirements 16 The GuardLogix 5570 controller system is certified for use in safety applications up to and including Safety Integrity Level (SIL) 3 and Performance Level (e) in which t
Chapter 1 System Overview Safety Task Signature The safety task signature consists of an ID number, date, and time that uniquely identifies the safety portion of a project. This includes safety logic, data, and configuration. The GuardLogix system uses the safety task signature to determine the project’s integrity and to let you verify that the correct project is downloaded to the target controller.
System Overview Controller Data Flow Capabilities Chapter 1 This illustration explains the standard and safety data-flow capabilities of the GuardLogix controller. Figure 1 - Data Flow Capabilities GuardLogix Controller Standard Safety Safety Task Standard Tasks Safety Programs Standard Programs Safety Routines Standard Routines Program Safety Data Program Data Controller Standard Tags Controller Safety Tags No.
Chapter 1 System Overview Selecting System Hardware The GuardLogix system supports SIL 3 and PLe safety applications. The GuardLogix controller is made up 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. The safety partner must be installed in the slot immediately to the right of the primary controller.
System Overview Chapter 1 Figure 2 - Keyswitch Positions Logix557x RUN FORCE SD OK REM PR OG RUN 1756-L7xS Safety Partner The safety partner is a coprocessor that provides an isolated second channel (redundancy) for safety-related functions in the system. The safety partner does not have a keyswitch or communication port. Its configuration and operation are controlled by the primary controller.
Chapter 1 System Overview The GuardLogix controller supports communication that lets it do the following: Selecting Communication 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 • Produce and consume safety tag data between 1756 and 1768 GuardLogix controllers across EtherNet/IP or ControlNet networks or within the same ControlLogix chassis • Distribute and control standard I/O
System Overview Chapter 1 Safety routines include safety instructions, which are a subset of the standard ladder logic instruction set, and safety application instructions. Programs scheduled under the safety task support only ladder logic.
Chapter 1 System Overview Notes: 18 Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Chapter 2 Install the Controller Topic Precautions Page Precautions 19 Make Sure That You Have All of the Components 22 Install a Chassis and Power Supply 22 Install the Controller into the Chassis 23 Insert or Remove a Memory Card 24 Make Communication Connections 27 Update the Controller 29 Choose the Operating Mode of the Controller 31 Uninstall an Energy Storage Module (ESM) 33 Install an Energy Storage Module (ESM) 34 Read and follow these precautions for use.
Chapter 2 Install the Controller 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. Removal and Insertion Under Power (RIUP) WARNING: When you insert or remove the module while backplane power is on, an electrical arc can occur. This could cause an explosion in hazardous location installations.
Install the Controller Chapter 2 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.
Chapter 2 Install the Controller Make Sure That You Have All of the Components Before you begin, check to make sure you have all of the components you will need. You must use a primary controller and a safety partner to achieve SIL 3/PLe. IMPORTANT These parts are included with the primary controller and safety partner. Cat. No.
Install the Controller Chapter 2 2. Install a ControlLogix power supply according to the corresponding installation instructions. Cat. No. Description 1756-PA72 1756-PB72 1756-PA75 1756-PB75 1756-PAXT 1756-PBXT Power supply, AC Power supply, DC Power supply, AC Power supply, DC XT power supply, AC XT power supply, DC Series Refer to These Installation Instructions C B 1756-IN005 B Extreme environment (XT) controllers require an XT power supply.
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. IMPORTANT You must install the safety partner in the slot immediately to the right of the primary controller. Follow steps 3 and 4 above to install the safety partner.
Install the Controller Chapter 2 Remove the SD Card If you want to remove the SD card, follow these steps. IMPORTANT Verify that the SD card status indicator is off and that the card is not in use before removing it. 1. Turn the keyswitch to the PROG position. 2. Open the door to access the SD card. Logix 55xx RUN FORCESD OK 32015-M 3. Press and release the SD card to eject it. Logix 55xx RUN FORCESD OK 32004-M 4. Remove the SD card and close the door.
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. Logix 55xx RUN FORCESD OK 3. Insert the SD card into the SD card slot. 4. Gently press the card until it clicks into place.
Install the Controller Chapter 2 5. Close the SD card door. Logix 55xx RUN FORCESD OK 32006-M Make Communication Connections The controller has a USB port that uses a Type B receptacle. The port is USB 2.0compatible and runs at 12 M. To use the USB port of the controller, you must have RSLinx software, version 2.59 or later, installed on your workstation. Use a USB cable to connect your workstation to the USB port.
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. On the Found New Hardware Wizard dialog box, click any of the Windows Update connection options and click Next. TIP If the software for the USB driver is not found and the installation is canceled, verify that you have installed RSLinx Classic software, version 2.
Install the Controller 5. To browse to your controller in RSLinx software, click RSWho Chapter 2 . 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. Virtual Chassis Driver USB Port Driver Update the Controller The controllers ship without firmware. Controller firmware is packaged with Studio 5000 environment.
Chapter 2 Install the Controller 6. Select the controller and click Next. 42900 7. Select the revision level to which you want to update the controller and click Next. 8. To start the update of the controller, click Finish and then click Yes. After the controller is updated, the status dialog box displays ‘Update complete’. IMPORTANT TIP Allow the firmware update to fully complete before cycling power or otherwise interrupting the upgrade.
Install the Controller Chapter 2 3. Click RSWho to specify the controller path. 4. Select your controller and click Update Firmware. 5. Select the firmware revision you want. 6. Click Update. 7. Click Yes. Allow the firmware update to complete without interruption. When the firmware upgrade is complete, the Who Active dialog box opens. You may complete other tasks in the Logix Designer application.
Chapter 2 Install the Controller Figure 4 - Controller Keyswitch Logix557x RUN FORCE SD OK REM PR OG RUN Use the Logix Designer Application to Change the Operation Mode Depending on the mode of the controller you specify by using the keyswitch, you can change the operation mode of the controller by using the Logix Designer application.
Install the Controller Uninstall an Energy Storage Module (ESM) Chapter 2 The controllers ship with an ESM installed. Controller Installed ESM Cat. No.
Chapter 2 Install the Controller 1. Remove the key from the keyswitch. The next step depends on which of the following conditions applies to your application: • If you are removing the ESM from a powered controller, go to step 2. • If you are removing the ESM from a controller that is not powered, either because the chassis power is turned off or the controller has been removed from a powered chassis, do not remove the ESM immediately.
Install the Controller Chapter 2 To install an ESM, complete these steps. Follow the same steps for the safety partner. 1. Align the tongue-and-groove slots of the ESM and controller. Logix 55xx RUN FORCESD OK 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. The ESM begins charging after installation.
Chapter 2 36 Install the Controller Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Chapter 3 Configure the Controller Topic Create a Controller Project Page Create a Controller Project 37 Set Passwords for Safety-locking and -unlocking 39 Handling I/O Module Replacement 41 Enable Time Synchronization 41 Configure a Peer Safety Controller 42 To configure and program your controller, use the Logix Designer application to create and manage a project for the controller. 1. Create a project in by clicking the New button on the main toolbar. 2.
Chapter 3 Configure the Controller 6. Enter the slot number of the controller. The New Controller 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 number. 7. Specify the folder in which to store the safety controller project. 8.
Configure the Controller Chapter 3 Figure 7 - Safety Network Number TIP You can use the Controller Properties dialog box to change the controller from standard to safety or vice versa by clicking Change Controller. However, standard and safety projects are substantially affected. See Appendix B, Change Controller Type, for details on the ramifications of changing controllers.
Chapter 3 Configure the Controller Follow these steps to set passwords. 1. Choose Tools > Safety > Change Password. 2. From the What Password pull-down menu, choose either Safety Lock or Safety Unlock. 3. Type the old password, if one exists. 4. Type and confirm the new password. 5. Click OK. Passwords may be from 1…40 characters in length and are not casesensitive. Letters, numerals, and the following symbols may be used: ‘ ~ ! @#$%^&*()_+,-={}|[]\:;?/.
Configure the Controller Chapter 3 The Safety tab of the Controller Properties dialog box lets you define how the controller handles the replacement of an I/O module in the system. This option determines whether the controller sets the safety network number (SNN) of an I/O module to which it has a connection and for which it has configuration data when a safety task signature(1) exists.
Chapter 3 Configure the Controller Figure 9 - Date/Time Tab For more information on Time Synchronization, refer to the Integrated Architecture™ and CIP Sync Configuration Application Solution, publication IA-AT003. Configure a Peer Safety Controller 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 data between peer controllers, you produce and consume controller-scoped safety tags.
Chapter 4 Communicate over Networks Topic The Safety Network Page The Safety Network 43 EtherNet/IP Communication 49 ControlNet Communication 53 DeviceNet Communication 55 Serial Communication 57 The CIP Safety protocol is an end-node to end-node safety protocol that allows routing of CIP Safety messages to and from CIP Safety devices through bridges, switches, and routers.
Chapter 4 Communicate over Networks Time-based Safety Network Number If the time-based format is selected, the SNN value that is generated represents the date and time at which the number was generated, according to the personal computer running the configuration software. Figure 10 - Time-based Format Manual Safety Network Number If the manual format is selected, the SNN represents entered values from 1…9999 decimal.
Communicate over Networks Chapter 4 Assigning the Safety Network Number (SNN) You can allow the Logix Designer application to automatically assign an SNN, or you can assign the SNN manually. Automatic Assignment When a new controller or module is created, a time-based SNN is automatically assigned. Subsequent new safety-module additions to the same CIP Safety network are assigned the same SNN defined within the lowest address on that CIP Safety network.
Chapter 4 Communicate over Networks Change the Safety Network Number (SNN) of the Controller 1. In the Controller Organizer, right-click the controller and choose Properties. 2. On the General tab of the Controller Properties dialog box, click the right of the safety network number to open the Safety Network Number dialog box. to 3. Click Time-based and then Generate. 4. Click OK.
Communicate over Networks Chapter 4 2. Expand the safety I/O modules available through the EtherNet/IP communication module. 3. Double-click the first safety I/O module to view the General tab. 4. Click to the right of the safety network number to open the Safety Network Number dialog box. 5. Choose Time-based and click Generate to generate a new SNN for that EtherNet/IP network. 6. Click OK. 7. Click Copy to copy the new SNN to the Windows Clipboard. 8.
Chapter 4 Communicate over Networks Copy and Paste a Safety Network Number (SNN) If the module’s configuration is owned by another controller, you may need to copy and paste the SNN from the configuration owner into the module in your I/O configuration tree. 1. In the software configuration tool of the module’s configuration owner, open the Safety Network Number dialog box for the module. 2. Click Copy. 3.
Communicate over Networks EtherNet/IP Communication Chapter 4 For EtherNet/IP network communication in a GuardLogix system, you have several modules to choose from. For CIP Safety communication, including safety I/O module control, choose any of the modules shown in Table 12, except the 1756-EWEB module, which does not support CIP Safety communication. Table 12 lists the modules and their primary features.
Chapter 4 Communicate over Networks These products are available for EtherNet/IP networks.
Communicate over Networks Chapter 4 EtherNet/IP Communication Example This example illustrates the following: • 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.(1) • The EtherNet/IP communication module is used as a bridge, letting the safety controller produce and consume standard and safety data. • The personal computer can upload/download projects to the controllers.
Chapter 4 Communicate over Networks Figure 13 - Adding EtherNet/IP Modules to the Project Standard EtherNet/IP Connections To use a standard EtherNet/IP module with the safety controller, add the module to the safety controller project and download the project to the GuardLogix controller. 1. To configure the module, define the IP address, subnet mask, and gateway. EtherNet/IP Parameter IP Address Subnet Mask Gateway Description The IP address uniquely identifies the module.
Communicate over Networks ControlNet Communication Chapter 4 For ControlNet communication, choose a 1756-CNB or 1756-CNBR module for standard communication, or a 1756-CN2, 1756-CN2R, or 1756-CN2RXT module for safety communication.
Chapter 4 Communicate over Networks Connections over the ControlNet Network The number of connections the controller uses is determined by how you configure the controller to communicate with other devices in the system. Connections are allocations of resources that provide more reliable communication between devices compared to unconnected messages. ControlNet connections can be scheduled or unscheduled.
Communicate over Networks Chapter 4 Figure 14 - ControlNet Communication Example PowerFlex 700S AC Drive with DriveLogix Software GuardLogix Controller with 1756-CN2 Module Compact GuardLogix Controller with 1768-CNB Module Distributed I/O Personal Computer/ Workstation 1756-DNB Module to DeviceNet Network with CIP Safety I/O 1756-CN2 Module (as an Adapter) with 1756 I/O Modules ControlNet GuardLogix Controller with 1756-DNB Module 1794-ACN15 Adapter with 1794 I/O Modules PanelView™ Terminal to Devi
Chapter 4 Communicate over Networks These products are used with the DeviceNet networks and 1756-DNB module. Table 17 - Product for Use with DeviceNet Networks Product Is used to Required Studio 5000 environment • Configure ControlLogix projects. • Define DeviceNet communication. Yes RSNetWorx for DeviceNet software • Configure DeviceNet devices. • Define the scan list for those devices. Yes RSLinx Classic or RSLinx Enterprise software • Configure communication devices. • Provide diagnostics.
Communicate over Networks Chapter 4 To use the 1756-DNB module to access standard data via the DeviceNet network, you must use RSNetWorx for DeviceNet software to do the following: • Create a configuration file for the network. • Configure each standard device on the network. • Configure the 1756-DNB. • Add the standard I/O devices to the 1756-DNB scan list.
Chapter 4 Communicate over Networks Notes: 58 Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Topic Page Adding CIP Safety I/O Modules 59 Configure CIP Safety I/O Modules 60 Setting the Safety Network Number (SNN) 61 Using Unicast Connections on EtherNet/IP Networks 61 Setting the Connection Reaction Time Limit 61 Understanding the Configuration Signature 65 Reset Safety I/O Module Ownership 66 Addressing Safety I/O Data 66 Monitor Safety I/O Module Status 67 Resetting a Module to Out-of-box Condition 69 Replacing
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O • IP address for EtherNet/IP networks To set the IP address, you can adjust the rotary switches on the module, use DHCP software, available from Rockwell Automation, or retrieve the default address from nonvolatile memory. • Safety network number (SNN) See page 61 for information on setting the SNN. • Configuration signature See page 65 for information on when the configuration signature is set automatically and when you need to set it.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 b. Type a name for the new module. c. Enter the node address or IP address of the module on its connecting network. Only unused node numbers are included in the pull-down menu. d. Modify the safety network number (SNN), if required, by clicking the button. See page 61 for details. e. Set module configuration parameters by using the Input Configuration, Test Output, and Output Configuration tabs.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O The Connection Reaction Time Limit is shown on the Safety tab of the Module Properties dialog box. Figure 16 - Connection Reaction Time Limit Specify the Requested Packet Interval (RPI) The RPI specifies the period at which 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.
Add, Configure, Monitor, and Replace CIP Safety I/O 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.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Timeout Multiplier The Timeout Multiplier determines the number of RPIs to wait for a packet before declaring a connection timeout. This translates into the number of messages that may be lost before a connection error is declared. For example, a Timeout Multiplier of 1 indicates that messages must be received during every RPI interval.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 Delay. This method can be used on an input or output connection. After the system has been run for an extended period of time through its worst-case loading conditions, record the Maximum Observed Network Delay.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Different Configuration Owner (listen only connection) When the I/O module configuration is owned by another controller, you need to copy the module configuration signature from its owner’s project and paste it into the Safety tab of the Module Properties dialog box. TIP Reset Safety I/O Module Ownership If the module is configured for inputs only, you can copy and paste the configuration signature.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 A CIP Safety I/O device address follows this format: Modulename:Type.Member Table 19 - CIP Safety I/O Module Address Format Where Is Modulename The name of the CIP Safety I/O module Type Type of data: Member Specific data from the I/O module Input: I Output: O Input-only Module: Modulename:I.RunMode Modulename:I.ConnectionFaulted Modulename:I.Input Members Output-only Module: Modulename:I.RunMode Modulename:I.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Table 21 - Status Indicator Operation Indicator Status Description Guard I/O DeviceNet Modules Module Status (MS) Network Status (NS) Input Points (INx) Output Points (Ox) Test Output Points (Tx) Off No power. Green, On Operating under normal conditions. Green, Flashing Device is idle. Red, Flashing A recoverable fault exists. Red, On An unrecoverable fault exists. Red/Green, Flashing Self-tests in progress.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 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. Resetting a Module to Outof-box Condition When the controller project is online, the Safety tab of the Module Properties dialog box displays the current configuration ownership. When the opened project owns the configuration, Local is displayed.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O If the entire routable CIP Safety control system is not being relied on to maintain SIL 3/PLe during the replacement and functional testing of a module, the Configure Always feature may be used. Go to Replacement with ‘Configure Always’ Enabled on page 74. Module replacement is configured on the Safety tab of the GuardLogix controller.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 Table 23 - Replacing a Module GuardLogix Safety Signature Exists Replacement Module Condition Action Required Yes No SNN (Out-of-box) See Scenario 1 - Replacement Module is Out-of-box and Safety Signature Exists on page 71. Yes No Different SNN from original safety task configuration See Scenario 2 - Replacement Module SNN is Different from Original and Safety Signature Exists on page 72.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O 5. Verify that the Network Status (NS) status indicator is alternating red/green on the correct module before clicking Yes on the confirmation dialog box to set the SNN and accept the replacement module. 6. Follow your company-prescribed procedures to functionally test the replaced I/O module and system and to authorize the system for use. Scenario 2 - Replacement Module SNN is Different from Original and Safety Signature Exists 1.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 7. Click to the right of the safety network number to open the Safety Network Number dialog box. 8. Click Set. 9. Verify that the Network Status (NS) status indicator is alternating red/green on the correct module before clicking Yes on the confirmation dialog box to set the SNN and accept the replacement module. 10.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Scenario 3 - Replacement Module SNN is Different from Original and No Safety Signature Exists 1. Remove the old I/O module and install the new module. 2. Right-click your POINT Guard I/O module and choose Properties. 3. Click the Safety tab. 4. Click Reset Ownership. 5. Click OK. 6. Follow your company-prescribed procedures to functionally test the replaced I/O module and system and to authorize the system for use.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 If the project is configured for ‘Configure Always’, follow the appropriate steps to replace a POINT Guard I/O module. 1. Remove the old I/O module and install the new module. a. If the module is in out-of-box condition, go to step 6. No action is needed for the GuardLogix controller to take ownership of the module. b. If an SNN mismatch error occurs, go to the next step to reset the module to out-of-box condition. 2.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O Replacing a POINT Guard I/O Module by Using RSNetWorx for DeviceNet Software Follow these steps to replace a POINT Guard I/O module when the module and the controller are on a DeviceNet network. 1. Replace the module and match the node number of the original module. 2. In RSNetWorx for DeviceNet software, open your project.
Add, Configure, Monitor, and Replace CIP Safety I/O Chapter 5 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 ben set. Once the download is completes successfully, the main project view displays this message: ‘The device at address xx has been downloaded. Any device-specific messages related to the download operation are displayed separately.
Chapter 5 Add, Configure, Monitor, and Replace CIP Safety I/O If you download this configuration to a temporary setup, place the module on the network and it automatically connects to the controller. If the configuration downloaded to the module was not from the original DNT file, the configuration signature will not match the original. Even if you recreate the same parameters in a new DNT file, the time and date portions of the signature will be different so the connection to the controller is not made.
Chapter 6 Develop Safety Applications Topic Page The Safety Task 80 Safety Programs 81 Safety Routines 82 Safety Tags 82 Produced/Consumed Safety Tags 86 Safety Tag Mapping 92 Safety Application Protection 95 Programming Restrictions 98 This chapter explains the components that make up a safety project and provides information on using features that help protect safety application integrity, such as the safety task signature and safety-locking.
Chapter 6 Develop Safety Applications The Safety Task When you create a safety controller project, the Logix Designer application automatically creates a safety task with a safety program and a main (safety) routine. Figure 22 - Safety Task in the Controller Organizer Within the safety task, you can use multiple safety programs, composed of multiple safety routines. The GuardLogix controller supports one safety task. The safety task cannot be deleted.
Develop Safety Applications Chapter 6 The safety task should be a high priority. You specify the safety task period (in ms) and the safety task watchdog (in ms). The safety task period is the period at which the safety task executes. The safety task watchdog is the maximum time allowed from the start of safety task execution to its completion. The safety task period is limited to a maximum of 500 ms and cannot be modified online.
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 Safety Tags A watermark feature visually distinguishes a safety routine from a standard routine. A tag is an area of a controller’s memory where data is stored. Tags are the basic mechanism for allocating memory, referencing data from logic, and monitoring data.
Develop Safety Applications Chapter 6 Figure 24 - Creating a New Tag Tag Type Table 24 defines the four types of tags: base, alias, produced, and consumed. Table 24 - Four Tag Types Tag Type Description Base These tags store values for use by logic within the project. Alias A tag that references another tag. An alias tag can refer to another alias tag or a base tag.
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. Like tags, members have a name and data type. You can create your own structures, as user-defined data types. Logix controllers contain predefined data types for use with specific instructions.
Develop Safety Applications Chapter 6 Controller-scoped Tags When safety tags are controller-scoped, all programs have access to the safety data. Tags must be controller-scoped if they are used in the following: • • • • More than one program in the project To produce or consume data To communicate with a PanelView/HMI terminal In safety tag mapping See Safety Tag Mapping on page 92 for more information. Controller-scoped safety tags can be read, but not written to, by standard routines.
Chapter 6 Develop Safety Applications Constant Value When you designate a tag as a constant value, it cannot be modified by logic in the controller, or by an external application such as an HMI. Constant value tags cannot be forced. The Logix Designer application can modify constant standard tags, and safety tags provided a safety task signature is not present. Safety tags cannot be modified if a safety task signature is present.
Develop Safety Applications Chapter 6 To properly configure produced and consumed safety tags to share data between peer safety controllers, you must properly configure the peer safety controllers, produce a safety tag, and consume a safety tag, as described below. Configure the Peer Safety Controllers’ Safety Network Numbers The peer safety controller is subject to the same configuration requirements as the local safety controller. The peer safety controller must also have a safety network number (SNN).
Chapter 6 Develop Safety Applications 3. Click to open the Safety Network Number dialog box. 4. Copy the producer controller’s SNN. 5. In the consumer controller’s project, right-click the producer controller and choose Module Properties. 6. Click 88 to open the Safety Network Number dialog box.
Develop Safety Applications Chapter 6 7. Paste the producer controller’s SNN into the SNN field and click OK. The safety network numbers match. Producer Controller Properties Dialog Box in Producer Project Module Properties Dialog Box in Consumer Project Paste the SNN here. Copy this SNN. 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.
Chapter 6 Develop Safety Applications 5. Click Advanced if you want to change the type of connection by unchecking ‘Allow Unicast Consumer Connections’. 6. Click OK. 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. 2.
Develop Safety Applications Chapter 6 4. Click Connection to open the Consumed Tag Connection dialog box. 5. Select the controller that produces the data. 6. Enter the name of the produced tag. 7. Click the Safety tab. 8. Enter the requested packet interval (RPI) for the connection in 1 ms increments. The default is 20 ms. Consumer’s Project Producer’s Project The RPI specifies the period at which data updates over a connection.
Chapter 6 Develop Safety Applications 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. The Network Delay Multiplier defines the message transport time that is enforced by the CIP Safety protocol.
Develop Safety Applications Chapter 6 Restrictions Safety tag mapping is subject to these restrictions: The safety tag and standard tag pair must be controller-scoped. The data types of the safety and standard tag pair must match. Alias tags are not allowed. Mapping must take place at the whole tag level. For example, myTimer.pre is not allowed if myTimer is a TIMER tag. • A mapping pair is one standard tag mapped to one safety tag.
Chapter 6 Develop Safety Applications 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. Click the arrow to display a filtered tag browser dialog box. If you are in the Standard Tag Name column, the browser shows only controller-scoped standard tags. If you are in the Safety Tag Name column, the browser shows controller-scoped safety tags. 3.
Develop Safety Applications Safety Application Protection Chapter 6 You can protect your application program from unauthorized changes by safetylocking the controller and by generating and recording the safety task signature. Safety-lock the Controller The GuardLogix controller can be Safety-locked to protect safety-related control components from modification.
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 25 - Safety-locking the Controller If you set a password for the safety-lock feature, you must type it in the Enter Password field. Otherwise, click Lock. You can also set or change the password from the Safety Lock dialog box. See page 39.
Develop Safety Applications Chapter 6 You can generate the safety task signature from the Safety tab of the Controller Properties dialog box by clicking Generate. You can also choose Tools>Safety>Generate Signature. Figure 26 - 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.
Chapter 6 Develop Safety Applications Delete the Safety Task Signature Click Delete to delete the safety task signature. The safety task signature cannot be deleted when the following is true: • The controller is safety-locked. • The controller is in Run mode with the keyswitch in RUN. • The controller is in Run or Remote Run mode with run mode protection enabled. ATTENTION: If you delete the safety task signature, you must retest and revalidate your system to meet SIL 3/PLe.
Chapter 7 Go Online with the Controller Topic Connecting the Controller to the Network Page Connecting the Controller to the Network 99 Understanding the Factors that Affect Going Online 101 Download 103 Upload 104 Go Online 106 If you have not done so, connect the controller to the network. Table 32 - Communication Connections For this type of connection Use See USB USB 2.
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 electrical 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. Connect your EtherNet/IP device and computer by using an Ethernet cable.
Go Online with the Controller Understanding the Factors that Affect Going Online Chapter 7 The Logix Designer application determines whether you can go online with a target controller based on whether the offline project is new or whether changes occurred in the offline project. If the project is new, you must first download the project to the controller. If changes occurred to the project, you are prompted to upload or download.
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.
Go Online with the Controller Download Chapter 7 Follow these steps to transfer your project from your computer to your controller. Project Controller Download 1. Turn the keyswitch of the controller to REM. 2. Open the controller project that you want to download. 3. Define the path to the controller. a. Click Who Active . b. Select the controller. To open a level, click the + sign. If a controller is already selected, make sure that it is the correct controller. 4. Click Download.
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. Mismatch between the offline project and the controller serial number. Selected controller may be the wrong controller.
Go Online with the Controller Chapter 7 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. If the controller serial numbers do not match, you can do one of the following: • Cancel the upload and connect to a matching controller. Then, start the upload procedure again.
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 Project Project Online 1. Define the path to the controller. a. Click Who Active . b. Select the controller. To expand a level, click the + sign. If a controller is already selected, make sure that it is the correct controller. 2. Click Go Online.
Go Online with the Controller Chapter 7 3. Follow the directions in the table below to connect to the controller. Table 34 - Connect to the Controller If the software indicates Then Unable to connect to controller. Mismatch between the offline project and the controller serial number. Selected controller may be the wrong controller.
Chapter 7 Go Online with the Controller Notes: 108 Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Chapter 8 Store and Load Projects Using Nonvolatile Memory Using Memory Cards for Nonvolatile Memory Topic Page Using Memory Cards for Nonvolatile Memory 109 Storing a Safety Project 110 Loading a Safety Project 111 Use Energy Storage Modules 111 Estimate the ESM Support of the WallClockTime 113 Manage Firmware with Firmware Supervisor 113 GuardLogix 5570 controllers support a memory card for nonvolatile memory. Nonvolatile memory lets you keep a copy of your project on the controller.
Chapter 8 Store and Load Projects Using Nonvolatile Memory If a memory card is installed, you can view the contents of the card on the Nonvolatile Memory tab of the Controller Properties dialog box. If a safety application is stored on the card, the safety-lock status and the safety task signature are shown. Figure 28 - Nonvolatile Memory Tab For detailed information on using nonvolatile memory, refer to the Logix5000 Controllers Nonvolatile Memory Programming Manual, publication 1756-PM017.
Store and Load Projects Using Nonvolatile Memory Chapter 8 You can only initiate a load from nonvolatile memory, if the following is true: • The controller type specified by the project stored in nonvolatile memory matches the controller type. • The major and minor revisions of the project in nonvolatile memory matches the major and minor revisions of the controller. • Your controller is not in Run mode.
Chapter 8 Store and Load Projects Using Nonvolatile Memory • Clear the program from the controller’s on-board NVS memory. For more information, see Clear the Program from On-board NVS Memory The following table describes the ESMs. Table 36 - Energy Storage Modules Cat. No. 1756-ESMCAP(XT) 1756-ESMNSE(XT) 1756-ESMNRM(XT) 1756-SPESMNSE(XT) 1756-SPESMNRM(XT) Description Capacitor-based ESM The controllers come with this ESM installed.
Store and Load Projects Using Nonvolatile Memory Chapter 8 2. Leave the ESM on the controller until the OK status indicator is off. 3. If necessary, remove the ESM from the controller after the OK status indicator transitions from solid red to off. Clear the Program from On-board NVS Memory If your application allows it, follow these steps to clear the program from the controller’s on-board NVS memory. 1. Remove the ESM from the controller. 2.
Chapter 8 Store and Load Projects Using Nonvolatile Memory Firmware Supervisor supports non-modular distributed I/O products that sit directly on the network without an adapter, including CIP Safety I/O modules on EtherNet/IP networks. CIP Safety I/O modules on DeviceNet networks and POINT Guard I/O modules are not yet supported. Follow these steps to enable Firmware Supervisor. 1. On the Controller Properties dialog box, click the Nonvolatile Memory tab. 2. Click Load/Store. 3.
Chapter 9 Monitor Status and Handle Faults Topic Page Viewing Status via the Online Bar 115 Monitoring Connections 116 Monitoring Safety Status 118 Controller Faults 118 Developing a Fault Routine 121 See Appendix A, Status Indicators for information on interpreting the controller’s status indicators and display messages.
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.
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. Both data types contain two bits: RunMode and ConnectionFaulted.
Chapter 9 Monitor Status and Handle Faults Monitoring 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 32 - Safety Task Status These are the possible values for safety status: • • • • • Safety partner is missing or unavailable. Safety partner hardware is incompatible with primary controller. Safety partner firmware is incompatible with the primary controller.
Monitor Status and Handle Faults Chapter 9 Nonrecoverable Controller Faults These occur when the controller’s internal diagnostics fail. If a nonrecoverable controller fault occurs, safety task execution stops and CIP Safety I/O modules are placed in the safe state. Recovery requires that you download the application program again. Nonrecoverable Safety Faults in the Safety Application If a nonrecoverable safety fault occurs in the safety application, safety logic and the safety protocol are terminated.
Chapter 9 Monitor Status and Handle Faults Viewing Faults The Recent Faults dialog box on the Major Faults tab of the Controller Properties dialog box contains two sub-tabs, one for standard faults and one for safety faults. The status display on the controller also shows fault codes with a brief status message, as described beginning on page 126. Fault Codes Table 40 shows the fault codes specific to GuardLogix controllers.
Monitor Status and Handle Faults Developing a Fault Routine Chapter 9 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. Depending on your application, you may not want all safety faults to shut down your entire system.
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. The SSV instruction changes the specified attribute with data from the source of the instruction.
Monitor Status and Handle Faults Chapter 9 Table 41 - GSV/SSV Accessibility Safety Object Attribute Name Data Type GSV SafetyLocked (2) SafetyStatus SINT Indicates whether the controller is safety-locked or -unlocked. INT Specifies the safety status as the following: • • • • • • Safety Controller AOI (Safety) (1) (2) (3) (4) Accessible from the Safety Task Attribute Description SafetySignatureExists SINT SafetySignatureID DINT GSV(4) ✓ SSV ✓ ✓ Safety task OK.
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.
Appendix A Status Indicators Controllers Status Indicators Topic Page Controllers Status Indicators 125 Controller Status Display 126 The status of the primary controller is displayed via four status indicators. Table 43 - Primary Controller Status Indicator Descriptions Indicator Status Description RUN Off No user tasks running. Controller is in PROGram mode. Green Controller is in RUN mode. Off No forces, standard or safety, are enabled on the controller.
Appendix A Status Indicators The safety partner has an OK status indicator. Table 44 - 1756-L7SP Status Indicator Controller Status Display Indicator Status Description OK Off No power is applied. Green The safety partner is operating with no faults. Red Powering up or nonrecoverable controller fault. The controller status display scrolls messages that provide information about the controller’s firmware revision, energy storage module (ESM) status, project status, and major faults.
Status Indicators Appendix A Table 46 - General Status Display Message Interpretation LOAD A project is being loaded from the SD card at controller powerup. You can also view the SD Indicator (see page 125) for additional status information. Allow the load to complete before removing the SD card, removing the ESM module, or disconnecting power. UPDT A firmware upgrade is being conducted from the SD card upon powerup. You can also view the SD Indicator (see page 125) for additional status information.
Appendix A Status Indicators Fault Messages If the controller is faulted, these messages may be indicated on the status display. Table 47 - Fault Messages(1) 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.
Status Indicators Appendix A Table 48 - Major Recoverable Fault Status Messages Type 1 1 1 1 3 3 3 3 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 6 7 Code 1 60 61 62 16 20 21 23 16 20 21 31 34 42 82 83 84 89 90 91 92 990 991 992 993 994 995 996 997 998 999 1 40 Message Run Mode Powerup Non-recoverable Non-recoverable – Diagnostics Saved Non-recoverable – Program Saved I/O Connection Failure Chassis Failure Connection Failure Unknown Instruction Invalid Array Subscript Control Structure LEN or POS < 0 I
Appendix A Status Indicators The latter part of the format, #XXXX message, can be used to diagnose the type of I/O fault and potential corrective actions. For details about each I/O fault code, see the Logix5000 Major, Minor, and I/O Fault Codes Programming Manual, publication 1756-PM014.
Status Indicators Appendix A I/O Fault Messages Continued Code #0807 #0808 #0809 #080A #080B #080C #080D #080E #080F #0814 #FD01 #FD02 #FD03 #FD04 #FD05 #FD06 #FD07 #FD08 #FD09 #FD0A #FD1F #FD20 #FD21 #FE01 #FE02 #FE03 #FE04 #FE05 #FE06 #FE07 Message Time Expectation Multiplier Timeout Multiplier Invld Max Consumer Number Invld CPCRC Time Correction Conn ID Invld Safety Cfg Signature Mismatch Safety Netwk Num Not Set OutOfBx Safety Netwk Number Mismatch Cfg Operation Not Allowed Data Type Mismatch Bad Ba
Appendix A Status Indicators Notes: 132 Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Appendix B Change Controller Type Topic Page Changing from a Standard to a Safety Controller 133 Changing from a Safety to a Standard Controller 134 Changing Safety Controller Types 134 Additional Resources 135 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.
Appendix B Change Controller Type • Standard controller features that are not supported by the safety controller, such as redundancy, are removed from the Controller Properties dialog box (if they existed). Changing from a Safety to a Standard Controller Upon confirmation of a change from a safety controller project to a standard controller, some components are changed and others are deleted, as described below: • The safety partner is deleted from the I/O chassis.
Change Controller Type Appendix B • The safety partner is created in slot x (primary slot + 1) when changing from a 1768 Compact GuardLogix to a GuardLogix 5570 controller. • When changing to a 1768 Compact GuardLogix controller, the safety partner is removed because it is internal to the Compact GuardLogix controller.. TIP A GuardLogix 5570 controller supports 100 safety programs in the safety task while a 1768 Compact GuardLogix controller supports 32.
Appendix B Change Controller Type Notes: 136 Rockwell Automation Publication 1756-UM022A-EN-P - November 2012
Index Numerics 1756-Axx 22 1756-CN2 53 1756-CN2R 53 1756-CN2RXT 53 1756-CNB 53 1756-CNBR 53 1756-DNB 55, 56, 99 1756-EN2F 49 1756-EN2T 49 1756-EN2TR 49 1756-EN2TXT 49 1756-EN3TR 49 1756-ENBT 49 1756-ESMCAP 22, 33, 34, 112, 113 1756-ESMCAPXT 22, 33, 34, 112, 113 1756-ESMNRM 22, 33, 34, 112, 113 1756-ESMNRMXT 22, 34, 112, 113 1756-ESMNSE 22, 33, 34, 112, 113 1756-ESMNSEXT 22, 34, 112, 113 1756-EWEB 49 1756-PA72 23 1756-PA75 23 1756-PAXT 23 1756-PB72 23 1756-PB75 23 1756-PBXT 23 1756-SPESMCAP 22, 33 1756-SPESM
Index controller change type 133-??, 133-135 configuration 37 extreme environment 8 fault handler 121 feature differences 7 installation 23 logging safety lock, unlock 95 safety task signature 97 match 101 mode 31 operating mode 31, 32 properties 38 serial number 101 serial number mismatch 104, 107 controller-scoped tags 85 ControlNet communication modules 16 configure driver 100 connections 54, 100 example 54 module 53, 99 overview 53 scheduled 54 software 53 unscheduled 54 coordinated system time 104, 12
Index G gateway 52 general status messages 126 get system value (GSV) accessibility 122 definition 9 using 122 go online 106 factors 101 Guard I/O module replacement 69-78 GuardLogix controllers differences 7 H hazardous location approval Europe 21 North America 20 HMI devices 12 hold-up time energy storage module 113 memory card 109, 111, 113 installation 24 removal 24 message status display 126 messages fault 128 general status 126 safety status 126 minor faults tab 120 mode operating 31 module Control
Index peer safety controller configuration 42 location 87 sharing data 87 SNN 87 Performance Level 9, 11 power supply catalog numbers 15, 23 primary controller description 14 hardware overview 14 modes 14 user memory 14 probability of failure on demand (PFD) definition 9 probability of failure per hour (PFH) definition 9 produce a tag 89 produce and consume tags 50, 53, 86 produced tag 83, 86 program fault routine 121 Program mode 31 programming 97 programming restrictions 98 program-scoped tags 85 project
Index safety tab 96, 97, 118 configuration signature 65 connection data 62 generate safety task signature 97 module replacement 70 safety-lock 96 safety-lock controller 96 unlock 96 view safety status 101, 118 safety tags controller-scoped 85 create 82 description 82 mapping 92-94 safety-program-scoped 85 valid data types 84 safety task 80 execution 81 priority 80 watchdog time 80 safety task period 62, 81, 86 safety task signature 86 copy 97 delete 98 description 12 effect on download 102 effect on upload
Index USB cable 27, 99 connection 27 driver 28 port 27 software required 27 type 27 user memory 14 UV radiation 21 V verification errors changing controller type 135 view safety status 101 W WallClockTime 112, 113 energy storage module 113 object 35 watchdog time 80 X XT See extreme environment.
Rockwell Automation Support Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support/, you can find technical manuals, a knowledge base of FAQs, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools.
