Home

1756-UM020C-EN-P, GuardLogix Controllers User Manual

Contents

1. Workstation Controller 1CD 1CD 2 RDX 2 RDX 3TXD 3TXD 4 DTR 4 DTR COMMON COMMON __ 6DSR 6DSR 7RTS 7RTS 8CTS 8CTS 9 9 You can also use a 1747 CP3 cable from the SLC product family but once the cable is connected you cannot close the controller door Connect Your EtherNet IP Device and Computer WARNING If you connect or disconnect the communications 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 Connect your EtherNet IP device and computer using Ethernet cable Ethernet Switch ns Standard Ethernet Cables with RJ45 Connector Crossover Ethernet Cable with dina RJ45 Connector Go Online with the Controller 87 Connect Your DeviceNet Scanner or ControlNet Communication Module and Your Computer To access either the DeviceNet network or the ControlNet network you can e connect directly to the network e connect to a serial or EtherNet IP network and browse bridge to the desired network This requires no additional programming Configure the Network RSLinx software handles communication between GuardLogix controllers and RSLogix 5000 software To communicate with the Driver controller configure RSLinx software for the required communication network Network Drivers For This Network Configure This Driver
2. You must first safety unlock the controller to allow the download to proceed Refer to the Controller safety unlocked portion of this table for download functionality IMPORTANT During a download to a controller that is safety unlocked the controller s status will be set to the safety locked or unlocked value of the offline project Publication 1756 UMO20C EN P December 2006 92 Go Online with the Controller Download GuardLogix Controller _ O0 o fom Download transfer a project from your computer to your controller so you can execute its logic je Project Download 1 Turn the keyswitch of the controller to REM 2 Open the RSLogix 5000 project that you want to download File Edit View Search Logic Communications Tools Bj New Ctrl N E Bp d pen Ctri o Close Ctrl S New Component gt Compact Page Setup Generate Report Print 1 Print Options _ 15D_safetycontroller ACD 2 mycontroller ACD Exit 3 Define the path to the controller a Click Who Active a 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 The software compares the following information in the offline project and the controller Controller serial number Gf project to controlle
3. 43 ControlNet Communications Additional Resources Resource Chapter 5 Develop Safety Applications Description Provides information on configuring produced and consumed safety tags EtherNet IP Modules in Logix5000 Control Systems User Manual publication ENET UMO001 Contains guidelines and specific details on interlocking and data transfer between controllers on the EtherNet IP network using the 1756 ENBT module EtherNet IP Web Server Module User Manual publication ENET UM527 1756 EWEB module Provides information on using the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 controllers Contains more information on how to produce and consume tags between Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 For ControlNet communications choose a 1756 CNB or 1756 CNBR Provides guidelines on optimizing a control application on an EtherNet IP network module for standard communications or a 1756 CN2 module for safety communications If your application controls standard I O modules requires an adapter for distributed 1 0 on ControlNet links communicates with other ControlNet devices messages shares standard data with other Logix5000 controllers produce consume bridges ControlNet links to route messages to devices on other networks Select 1756 CNB performs same functions as a 1756 CNB also
4. Series A Change Revision 13 Electronic Keying Exact Match Input Data Safety Input Status None Output Data Safety Data Format Integer Status Offline Cancel Apply Help 4 Click _ to the right of the safety network number to open the Safety Network Number dialog 5 Choose Time based and click Generate to generate a new SNN Jj for that DeviceNet network 6 Click OK 7 Click Copy to copy the new SNN to the Windows Clipboard 8 Open the General Tab of the Module Properties dialog of the next safety I O module under that 1756 DNB module 9 Click to the right of the safety network number to open the Safety Network Number dialog 10 Choose Time based and click Paste to paste that DeviceNet network s SNN into that device Publication 1756 UM020C EN P December 2006 38 Communicate Over Networks Publication 1756 UMO20C EN P December 2006 11 Click OK 12 Repeat Steps 8 9 and 10 for the remaining safety I O modules under that 1756 DNB module 13 Repeat Steps 2 through 10 for any remaining 1756 DNB modules under the I O Configuration tree Copy and Paste an Safety Network Number SNN If the module s configuration is owned by a different 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
5. 1 Define the path to the controller a Click Who Active eI 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 The software checks whether the offline project and controller serial numbers match if Project to Controller Match is selected e whether the offline project contains changes that are not in the controller project e whether the revisions of the offline project and controller firmware match whether the offline project or the controller are safety locked e whether the offline project or the controller have compatible safety signatures Publication 1756 UM020C EN P December 2006 96 Go Online with the Controller 3 Follow the directions in the table below to connect to the controller based on the software s response Connect to the Controller If the software indicates Unable to connect to controller Mismatch between the offline project and the controller serial number Selected controller may be the wrong controller Then Connect to the correct controller select a different project file or choose the Update project serial number checkbox and choose Go Online to connect to the controller and update the offline project serial number to match the controller Unable to connect to controller The revision of the offline project and the controller s firmware are not compat
6. Serial RS 232 DF1devices EtherNet IP EtherNet IP driver or Ethernet devices DeviceNet DeviceNet drivers ControlNet ControlNet drivers Configure a Serial Communications Driver 1 Start RSLinx software 2 From the Communications menu choose Configure Drivers 3 From the Available Driver Types list select the driver 4 Click Add New 5 Click OK to accept the default name for the driver 6 From the Comm Port pull down list select the serial port on the workstation to which the cable is connected 7 From the Device pull down menu choose Logix5550 Serial Port 8 Click Auto Configure Publication 1756 UM020C EN P December 2006 88 Go Online with the Controller E Understand the Factors that Affect Going Online Publication 1756 UMO20C EN P December 2006 9 Does the dialog display the following message Auto Configuration Successful If Then Yes Click OK No Go to Step 6 and verify that you selected the correct comm port 10 Click Close Configure an EtherNet IP DeviceNet or ControlNet Driver For information on configuring an EtherNet IP or DeviceNet driver refer to the appropriate publication e EtherNet IP Modules in Logix5000 Control Systems publication ENET UMO001 e DeviceNet Modules in Logix5000 Control Systems publication DNET UM004 e The ControlNet Modules in Logix5000 Control Systems User Manual publication CNET UM001 RSLogix 5000 software determines whether you can
7. The Connection Reaction Time Limit is the maximum age of safety packets on the associated connection For simple timing constraints an acceptable Connection Reaction Time Limit can be achieved by adjusting the RPI For more complex requirements set the Advanced Connection Reaction Time Limit parameters as described in step 9 The Max Network Delay is the maximum observed transport delay from the time the data was produced until the time the data was received When online you can reset the Max Network Delay by clicking Reset Max If the Connection Reaction time limit is acceptable click OK To set the Advanced Connection Reaction Time Limit parameters click Advanced Advanced Connection Reaction Time Limit Configuration Requested Packet Interval RPI 10 E ms 1 500 Timeout Multiplier 2240 4 Network Delay Multiplier 100 4 of RPI 10 600 Connection Reaction Time Limit 30 0 ms OK Cancel 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 The Network Delay Multiplier specifies the round trip delay from the producer to the consumer and back to the producer You can use the Network Delay Multiplier to increase or decrease the Connection Reaction Time Limit Develop Safety Applications 71 Additional Resources Resource
8. 5 Click OK Passwords may be from 1 to 40 characters in length and are not case sensitive Letters numerals and the following symbols may be used A amp _ I1 N 5 7 Configure the GuardLogix Controller 27 Handle 1 0 Module Replacement Select the CST Master The Safety tab of the Controller Properties dialog 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 signature P exists f Controller Properties SD safetycontroller j E z ni x General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced Fie Safety Memoy Safety Application Unlocked Safety Lock Unlock Safety Status Safety Signature ienerate e ID nan Date Lt When replacing Safety 1 0 Configure Only When No Safety Signature Exists C Configure Always Enable the Configure Always feature only if the entire routable CIP Safety Control System is not being relied on to maintain SIL 3 during the replacement and functional testing of a module See Replace a CIP Safety 1 0 Module on page 59 for more information One device in the local chassis must be designated as the coordinated system time CST master The CST master is
9. Catalog Number Available Slots Series Refer to These Installation Instructions 1756 M 4 1756 A7 7 1756 A10 10 B 1756 IN080 1756 A13 13 1756 A17 17 Publication 1756 UMO20C EN P December 2006 GuardLogix System Overview 19 Select Safety 1 0 Select Communication Networks Power Supply These ControlLogix power supplies are suitable for use in SIL 3 applications No extra configuration or wiring is required for SIL 3 operation of the power supplies Power Supply Catalog Numbers Catalog Description Series Refer to These Number Installation Instructions 1756 PA72 Power supply ac C 1756 PB72 Power supply dc 1756 PA75 Power supply ac B op NSS 1756 PB75 Power supply de 1758p 1 Power supply ac redundant ETSI 5 1756 IN573 1756 PB75R Power supply dc redundant 1 A1756 PSCA or 1756 PSCA2 redundant power supply chassis adapter is required for use with redundant power supplies Safety input and output devices can be connected to CIP Safety I O on DeviceNet networks allowing output devices to be controlled by the GuardLogix controller system via DeviceNet Safety communications For the most up to date information on available CIP Safety I O catalog numbers certified series and firmware revisions see http ab com certification safety The GuardLogix controller supports communication that lets it e distribute and control safety I O on DeviceNet net
10. 0 GuardLogix controller E a with 1756 ENBT module F 1756 ENBT module as an adapter wit 1756 1 0 modules 1756 DNB module for remote DeviceNet communication CompactLogix controles with integrated EtherNet IP port to standard or safety devices on DeviceNet network Lie 1794 AENT adapter with switch 1794l 0moduls 1734 AENT adapter with 1734 I O modules PowerFlex 700S AC drive with DriveLogix workstation EtherNet IP Modules in a GuardLogix System To use an EtherNet IP module with the GuardLogix controller you must configure the module s communication parameters add the module to the GuardLogix controller project and download the project to the GuardLogix controller Publication 1756 UMO20C EN P December 2006 42 Communicate Over Networks Publication 1756 UMO20C EN P December 2006 Configure the EtherNet IP Module To configure the module define the IP address subnet mask and gateway EtherNet IP Parameters EtherNet IP Description Parameter IP Address The IP address uniquely identifies the module The IP address is in the form xxx xxx xxx xxx where each xxx is a number between 0 and 255 The following reserved values cannot be used e 127 0 0 1 e 0 0 0 0 e 255 255 255 255 Subnet Mask Subnet addressing is an extension of the IP address
11. 3orfewer 16 months 16 months 16 months 51 55 C 123 131 F 3orfewer 11 months 11 months 11 months 56 60 C 132 140 F 3 or fewer 8 months 8 months 8 months EXAMPLE jai the following conditions the battery will last at least 2 years before the BAT LED indicator turns red e Max temperature 1 in below the chassis is 45 C 113 F e Power is cycled 3 times per day e The controller contains a 2 MB project Publication 1756 UM020C EN P December 2006 116 Maintain the Battery After BAT LED Indicator Turns On If the BAT LED indicator turns on when you apply power to the controller the battery life may be less than the Battery LED Indicator Worst Case Time table indicates Some of the battery life may have been used up while the controller was off and unable to turn on the BAT LED indicator Expect a minimum of 4 weeks of battery life after the BAT LED indicator turns on When to Replace the When the battery is about 9596 discharged the controller provides the following warnings Battery e The BAT LED indicator on the front of the controller turns on solid red e A minor fault occurs type 10 code 10 for the controller To prevent possible battery leakage even if the BAT LED indicator is off replace the battery according to the following schedule Battery Replacement Schedule If the temperature 2 54 cm 1 in below the chassis is 0 35 C 32 95
12. 4 23 ex urge tace qv o 90 Safety Signature and Safety locked unlocked Status 90 D wnload cela debe qo decer ento donde Uca dorado oboe ood 92 OAC oS a teh d ati o Id RA o 93 GONS afore Sep He tiun ta pha L A fash Gore I E beh Econ 95 Chapter 7 Tot OC USO lO esce Ark Aah eto ty howe dicio teh 97 Monitor Controller Status 4 2 4 ope ose cr te Do cS eod 97 Controller LED Indicators onana 97 Online DAE aod ques aee err vn rg 9 Bed i no haie y 99 Publication 1756 UMO20C EN P December 2006 8 Table of Contents Controller Specifications Maintain the Battery Change Controllers Publication 1756 UMO20C EN P December 2006 Monitor Connections erarinta eri Eaua PT EREE 100 DAV CONDECION S e en qo e eo Bee eG Paw goes e as 100 Safety Connections aue dob eo DW aie ok dad 100 Monitor Status Flags eoa eReXS foe Sheen eek DE OES ES 101 Monitor Safety BUXDUES e di hace Sede ho oe be RoE eS 101 GuardLogix Controller Faults 0 0 005 0000500505 102 Nonrecoverable Controller Faults 102 Nonrecoverable Safety Faults in the Safety Application 102 Recoverable Faults in the Safety Application 103 View Faults ua spacio e n RO OR THO INO RR EE 103 FAU COLES hainin ptr puna aere anaa a PEE 104 Develop a Fault Routine n nannaa aaa 105 Program Fault Routine book uy p deco Re 8 105 Controller Fault Wander sce dam esae ete d 105 Use GSV SSV Instructions iugis Rue p nt 106 Appendix
13. 5E 06 1 9E 10 Controller Specifications 111 Environmental Specifications Description Operating Temperature Value IEC 60068 2 1 Test Ad Operating Cold IEC 60068 2 2 Test Bd Operating Dry Heat IEC 60068 2 14 Test Nb Operating Thermal Shock e 0 60 C 32 140 F Storage Temperature IEC 60068 2 1 Test Ab Unpackaged Nonoperating Cold IEC 60068 2 2 Test Bb Unpackaged Nonoperating Dry Heat IEC 60068 2 14 Test Na Unpackaged Nonoperating Thermal Shock e 40 85 C 40 185 F Relative Humidity IEC 60068 2 30 Test Db Unpackaged Nonoperating Damp Heat 5 95 noncondensing Vibration IEC60068 2 6 Test Fc Operating 2 g 10 500 Hz Operating Shock IEC60068 2 27 Test Ea Unpackaged Shock 30 g Nonoperating Shock IEC60068 2 27 Test Ea Unpackaged Shock 50 g Emissions CISPR 11 Group 1 Class A ESD Immunity IEC 61000 4 2 e 6 kV contact discharges e 8 kV air discharges Radiated RF Immunity IEC 61000 4 3 e AM 10V m 80 1000 MHz 1 kHz e AM 10V m Q 1 2 GHz Q 1 kHz e PM 10V m Q 900 MHz 200 Hz EFT B Immunity IEC 61000 4 4 e 4 kV 2 5 kHz on power ports e 4 kV 2 5 kHz on communications ports Surge Transient Immunity IEC 61000 4 5 2 kV line earth CM on shielded ports Conducted RF Immunity IEC 61000 4 6 10V 150 kHz 80 MHz 1 kHz Enclosure Type Rating None open style
14. A T COGI e ORT us us oi ote dion ree ed oom te Sea do eo es 109 COTEIETCHIELOUHA S tas C Latte d AT p AC ROG E gr EATER 109 General Specie Pos x xw ed Pe Psp rU SAX ete Fuels 110 Safety Speciticdtlofis e vu saca Tug Menta que eon ager ey 110 Environmental Specifications llle 111 Environment and Enclosure Information 112 North American Hazardous Location Approval 113 Appendix B Introduction 2 neet tte a at stone YE ne cht atte Siok o a A 115 Estimate Baler Life 2 4o ur ques Ne OR e ed UR E 115 Before BAT LED Indicator Turns On i When to Replace the Battery a 4 44 4 2 fur Peor st e 116 Replace the Battery i vce EUER b A RESO 117 Store Replacement Batteries o n naaa 118 Additional Resources aaa 118 Appendix C Introduction ooo usn ke Bot ew ara ere Aai e Rt 119 From Standard to Safety cas sex 6 44 NE WR ESE RE OES Gud 119 From Safety to Standard so sce Ge peo eem 120 Index Preface Introduction Read this preface to familiarize yourself with the rest of the manual Topic Page Purpose of This Manual 9 Who Should Use This Manual 9 Additional Resources 10 Conventions 10 Understanding Terminology 11 Purpose of This Manual This manual is a guide for using GuardLogix controllers It describes the GuardLogix specific procedures you use to configure operate and troubleshoot your controller For detailed information on related topi
15. DISTRIBUTE PHASE INSTRUCTION IMPORTANT Scope This restriction includes user defined data types that contain predefined data types A tag s scope determines where you can access the tag data When you create a tag you define it as either a controller tag global data or a program tag for a specific safety or standard program local data Safety tags can be either controller scoped or safety program scoped Develop Safety Applications 71 Controller scoped Tags When tags are controller scoped all standard programs have access to the safety data Tags must be controller scoped if they are e used in more than one program in the project e used in a MSG instruction e used to produce or consume data e used to communicate with a PanelView terminal e used in safety tag mapping See Safety Tag Mapping on page 77 for more information Controller scoped safety tags can be read but not written to by standard routines IMPORTANT Controller scoped safety tags are readable by any standard routine but the safety tag s update rate is based on the execution of the safety task Tags associated with safety I O and produced or consumed safety data must be controller scoped safety tags For produced consumed safety tags you must create a user defined data type with the first member of the tag structure containing the status of the connection This member is a predefined data type called CONNECTION_STATUS Add
16. Isolation Voltage 30V Tested to withstand 500V for 60 s Programming Cable 1756 CP3 or 1747 CP3 serial cable category 3 Replacement Battery 1756 BA2 0 50 g lithium 1 See Industrial Automation Wiring and Grounding Guidelines publication 1770 4 1 Publication 1756 UM020C EN P December 2006 112 Controller Specifications Environment and Enclosure Information Publication 1756 UMO20C EN P December 2006 ATTENTION A Environment and Enclosure This equipment is intended for use in a Pollution Degree 2 industrial environment in overvoltage Category Il applications as defined in IEC publication 60664 1 at altitudes up to 2000 m 6562 ft without derating This equipment is considered Group 1 Class A industrial equipment according to IEC CISPR Publication 11 Without appropriate precautions there may be potential difficulties ensuring electromagnetic compatibility in other environments due to conducted as well as radiated disturbance This equipment is supplied as open type equipment It must be mounted within an enclosure that is suitably designed for those specific environmental conditions that will be present and appropriately designed to prevent personal injury resulting from accessibility to live parts The interior of the enclosure must be accessible only by the use of a tool Subsequent sections of this publication may contain additional information regarding specific enclosure type ratings
17. Manual publication 1791DS UM001 Provides information on using DeviceNet Safety I O Modules Logix5000 General Instruction Set Reference Manual publication 1756 RM003 Provides information on the Logix5000 Instruction Set Logix Common Procedures Programming Manual publication 1756 PM001 Provides information on programming Logix5000 controllers including managing project files organizing tags programming and testing routines and handling faults ControlLogix System User Manual publication 1756 UM001 Provides information on using ControlLogix in non safety applications DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 Provides information on using the 1756 DNB module in a Logix5000 control system EtherNet IP Modules in Logix5000 Control Systems User Manual publication ENET UMO01 Provides information on using the 1756 ENBT module in a Logix5000 control system ControlNet Modules in Logix5000 Control Systems User Manual publication CNET UMOO1 Provides information on using the 1756 CNB module in Logix5000 control systems Logix5000 Controllers Execution Time and Memory Use Reference Manual publication 1756 RM087 Provides information on estimating the execution time and memory use for instructions Logix Import Export Reference Manual publication 1756 RM084 Provides information on using RSLogix 5000 Import Export Utility If you would like a manua
18. Number dialog for the module Safety Network Number x Format Generate e 8 4 2004 8 36 16 195 AM C Manual 1756 Backplane Decimal Number 2E80_02EB_5143 Hex Copy Paste 2 Click Copy 3 Go to the General tab on the Module Properties dialog of the I O module in the I O Configuration tree of the consuming controller project This consuming controller is not the configuration owner 4 Click _ to the right of the safety network number to open the Safety Network Number dialog 5 Click Paste 6 Click OK Communicate Over Networks 39 EtherNet IP For EtherNet IP communications choose either a 1756 ENBT or JN 1756 EWEB module Communications If your application Select e controls 1 0 modules 1756 ENBT e requires an adapter for distributed I O on EtherNet IP links e communicates with other EtherNet IP devices messages e shares data with other Logix5000 controllers produce consume e bridges EtherNet IP links to route messages to devices on other networks e requires remote access via Internet browser to tags in a local 1756 EWEB ControlLogix controller communicates with other EtherNet IP devices messages bridges EtherNet IP links to route messages to devices on other networks does not support I O or produced consumed tags In addition to communication hardware for EtherNet IP networks these software products are available Software for EtherNet IP Modules
19. Over the EtherNet IP Network You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide more reliable communications between devices compared to unconnected messages message instructions All EtherNet IP connections are unscheduled An unscheduled connection is triggered by the requested packet interval RPD for I O control or the program such as a MSG instruction Unscheduled messaging lets you send and receive data when needed The 1756 EtherNet IP communication modules support 128 Common Industrial Protocol CIP connections over an EtherNet IP network EtherNet IP Communication Example In this example 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 the 1756 ENBT module can be used as a bridge letting the GuardLogix controller produce and consume standard and safety data to and from I O devices the personal computer can upload download projects to the controllers the personal computer can configure devices on the EtherNet IP network Communicate Over Networks 4 EtherNet IP Communication Example FlexLogix controller with 1788 ENBT module lt 77 Distibuted 1
20. Safety lock the Controller on page 79 e delete the safety signature if one exists See Delete the Safety Signature on page 82 Publication 1756 UM020C EN P December 2006 36 Communicate Over Networks Change the Safety Network Number SNN of the Controller 1 In the Controller Organizer right click the GuardLogix controller and choose Properties 2 On the General tab of the Controller Properties dialog click to the right of the safety network number to open the Safety Network Number dialog 55 Controller Properties SD safetycontroller Ctriex Ctrl C Ctriev Del Cross Reference Ctrl E kplane I Click OK Publication 1756 UMO20C EN P December 2006 Communicate Over Networks 37 Change the Safety Network Number SNN of Safety 1 0 Modules on the CIP Safety Network This example uses the DeviceNet network 1 Find the first DeviceNet Scanner 1756 DNB module in the I O Configuration tree 2 Expand the I O modules available through the 1756 DNB 3 Double click the first safety I O module to view the General tab General Connection Safety Module Info Input Configuration Test Output Output Configuration Type 1791DS IBEXOB8 4 8 Point 24VDC Sink Safety Input 8 Point 24 VDC Source Safety Output Vendor Allen Bradley Parent DNB_local Name In out Node 1 Be Spe Number poniamo rard zi DeviceNet 9999 r Module Definition
21. Verify that the safety network number SNN shown on the producer controller s Module Properties dialog in the consumer s safety project matches the SNN that is configured in the producer controller s project as shown on the producer controller s Controller Properties dialog Type 1756 L62S ControlLogix55625 Safety Controller Vendor Allen Bradley Name Description Publication 1756 UMO20C EN P December 2006 Producer Slot Safety Netwok 2EEE_0388_912D m Number 11 22 2004 11 20 27 437 AM TIP Producer Controller Properties in Producer Project a Minor Faults Date Time Advanced File Safety Memory l General Serial Port System Protocol l User Protocol Major Faults Vendor Allen Bradley Type 1756 L62S ControlLogix5562S Safety Controller Revision 14 31 Name produser o Description zi Chassis Type 1756410 10Slot ControlLogis Chassis v Slot Safety Network Number 2EEE_0388_912D T 11 22 2004 11 20 27 437 AM Cancel Apply Help An SNN can be copied and pasted using buttons on the Safety Network Number dialog Safety Network Number x Format Time based Generate 11 22 2004 11 20 27 437 AM C Manual 1756 Backplane Decimal Number 2EEE_03B8_912D Hex Copy Paste Cancel Help Develop Safety Applications 15 4 In the Controller Organizer right click the Controller Tags folder and choose Edit T
22. allocated Safety produced consumed connections are unscheduled Communicate Over Networks 45 The 1756 CNB and 1756 CNBR communication modules support 64 CIP connections over a ControlNet network The 1756 CN2 module supports 100 CIP connections over the ControlNet network However we recommend that you configure only 97 connections for each module to maintain optimal performance ControlNet Communication Example In this example e GuardLogix controllers can produce and consume standard or safety tags between each other e GuardLogix controllers can initiate MSG instructions that send receive standard data or configure devices e the 1756 CN2 module can be used as a bridge letting the GuardLogix controller produce and consume standard and safety data to and from I O devices e the personal computer can upload download projects to the controllers e the personal computer can configure devices on the ControlNet network and it can configure the network itself ControlNet Communication Example Personal Computer Workstation PowerFlex 700S AC Distributed 1 0 Drive with DriveLogix Rubr 1756 CN2 Module 1756 DNB Module with 1756 CN2 Module as an Adapter wit to DeviceNet Network 1756 1 0 Modules h CIP Safety 1 0 1 1 1 1 D D GuardLogix Controller a 1794 ACN15 Adapter with E S with 1794 1 0 Modu
23. communication with a device in the I O configuration of the controller does not occur for 100 ms the communication times out and the controller produces the following warnings e The I O LED indicator on the front of the controller flashes green e An alert symbol A shows over the I O configuration folder and over the device that has timed out e A module fault is produced which you can access through the Connections tab of the Module Properties dialog for the module the GSV instruction Safety 1 0 and produce consume connections cannot be configured to automatically fault the controller when a connection is lost Therefore you need to monitor for connection faults to be sure that the safety system maintains SIL 3 integrity See Safety Connections on page 100 Safety Connections For tags associated with produced or consumed safety data you can monitor the status of safety connections 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 The RunMode value indicates if consumed data is actively being updated by a device that is in the Run Mode 1 or Idle State 0 Idle state is indicated if the connection is closed the safety task is faulted or the remote controller or device is in Program mode or Test mode The ConnectionFaulted value indicat
24. devices or via message instructions from peer controllers RSLogix 5000 software can write safety tags when the controller is Safety unlocked does not have a safety signature and is operating without any safety faults The ControlLogix Systems User Manual publication 1756 UMO001 provides information on using ControlLogix devices in standard non safety applications HMI Devices HMI devices can be used with GuardLogix controllers HMI devices can access standard tags just as with any ControlLogix controller However HMI devices cannot write to safety tags safety tags are read only for HMI devices Publication 1756 UM020C EN P December 2006 16 GuardLogix System Overview GuardLogix Data Flow Capahilities Publication 1756 UMO20C EN P December 2006 This illlustration explains the standard and safety data flow capabilities of the GuardLogix controller Data Flow Capabilities GuardLogix Controller Standard 1 Standard tags and logic behave the same way they do in the ControlLogix platform 2 Standard tag data either program or controller scoped can be exchanged with external HMI devices personal computers and other controllers 3 GuardLogix controllers are integrated controllers with the ability to move map standard tag data into safety tags for use within the safety task ATTENTION This data must not be used to directly control a SIL 3 output 4 Controller scoped safety tags
25. from the Safety tab of the Controller Properties dialog by clicking Generate You can also choose Safety gt Generate Signature from the Tools menu f Controller Properties Manual i Bl xl General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced File Safety Memory Safety Application Unlocked Safety Lock Unlock Safety Status Safety Task OK Safety Signature Generate e ID 7C1DFEAO C Date 10 04 2004 8e Time 02 43 05 127 PM Delete P When replacing Safety 1 0 Con nly When No Safety Signature Exists Config OK Cancel Apply Help If a previous signature exists you will be prompted to overwrite it Publication 1756 UM020C EN P December 2006 82 Develop Safety Applications Software Restrictions Publication 1756 UM020C EN P December 2006 Copy the Safety Signature You can use the Copy button to create a record of the safety signature for use in safety project documentation comparison and validation When you click Copy the ID Date and Time components are copied to the Windows clipboard Delete the Safety Signature You can use the Delete button to delete the safety signature only when the controller is Safety unlocked The safety signature cannot be deleted when the controller is in Run mode with the keyswitch in RUN If you delete the safety signature you must retest and revalidate your system to meet SIL 3
26. scheme that allows a site to use a single network ID for multiple physical networks Routing outside of the site continues by dividing the IP address into a net ID and a host ID via the class Inside a site the subnet mask is used to redivide the IP address into a custom network ID portion and host ID portion This field is set to 0 0 0 0 by default If you change the subnet mask of an already configured module you must cycle power for the change to take effect Gateway A gateway connects individual physical networks into a system of networks When a node needs to communicate with a node on another network a gateway transfers the data between the two networks This field is set to 0 0 0 0 by default Add the Module to the Project After you physically install an EtherNet IP module and set its IP address you must add the module to the Controller Organizer in your GuardLogix controller project 73 Trends E 3 Data Types Cj User Defined El oa Strings El Cg Predefined H E Module Defined 5 6 I O Configuration ControlBus 1756 A10 fh 0 1756 L615 SD safetycontroller J 1 1756 LSP SD safetycontroller Partner H BJ 2 1756 DNB DNB local EB g 3 1756 ENBT A Ethernet Bridge Eig Ethernet 1756 ENBT 4 Ethernet Bridge Download the Project Use RSLogix 5000 software to download the project When the controller begins operation it establishes connections with the EtherNet IP modules Communicate Over Networks
27. that are required to comply with certain product safety certifications See NEMA Standards publication 250 and IEC publication 60529 as applicable for explanations of the degrees of protection provided by different types of enclosure Also see the appropriate sections in this publication as well as the Industrial Automation Wiring and Grounding Guidelines Allen Bradley publication 1770 4 1 for additional installation requirements pertaining to this equipment North American Hazardous Location Approval Controller Specifications 113 The following information applies when operating this equipment in hazardous locations Products marked CL I DIV 2 GP A B C D are suitable for use in Class I Division 2 Groups A B C D Hazardous Locations and nonhazardous locations only Each product is supplied with markings on the rating nameplate indicating the hazardous location temperature code When combining products within a system the most adverse temperature code lowest T number may be used to help determine the overall temperature code of the system Combinations of equipment in your system are subject to investigation by the local Authority Having Jurisdiction at the time of installation EXPLOSION HAZARD e Do not disconnect equipment unless power has been A removed or the area is known to be nonhazardous e Do not disconnect connections to this equipment unless power has been removed or the area is known to be nonhazard
28. the project you are prompted to update the firmware of the controller RSLogix 5000 software lets you update the firmware as part of the download sequence IMPORTANT To update the firmware of the controller first install a firmware upgrade kit An upgrade kit ships on a supplemental CD along with RSLogix 5000 software TIP Firmware upgrades can also be performed via the Tools gt ControlFlash menu in RSLogix 5000 software Publication 1756 UM020C EN P December 2006 90 Go Online with the Controller Publication 1756 UMO20C EN P December 2006 Safety Partner Status Faults Upload of program logic and going online is allowed regardless of safety status Safety status affects the download process only You can view the safety status via the Safety tab on the Controller Properties dialog Safety Status Safety Status Fault Condition Action Required Safety partner is missing or unavailable Install a compatible safety partner Safety partner hardware is incompatible with primary controller Install a compatible safety partner Safety partner firmware is incompatible with the primary controller Update the safety partner with the correct firmware revision The safety partner s firmware revision must be an exact match to the primary controller s Safety status OK None The software proceeds to check for the existence of a safety signature in the offline project See Safety Signature and Safety lock
29. to the next step 3 Remove the old battery Install a new 1756 BA2 battery a Insert the battery as shown b Connect the battery Red Black c Write the date you installed the battery on the battery label and attach the label to the inside of the controller door Install only a 1756 BA2 battery If you install a mt different battery you may DATE C damage the controller Publication 1756 UMO20C EN P December 2006 118 Maintain the Battery Store Replacement Batteries Additional Resources Publication 1756 UMO20C EN P December 2006 5 Is the BAT LED indicator on the front of the controller off If Then Yes Go to the next step No ES N 99 Check that the battery is correctly connected to the controller If the BAT LED indicator remains on install another 1756 BA2 battery If the BAT LED indicator remains on after installing the alternate battery in Step 2 contact your Rockwell Automation representative or local distributor 4 Dispose of the old battery in accordance with all local regulations ATTENTION Do not incinerate or dispose of lithium batteries in general trash collection They may explode or rupture A ATTENTION A Resource Guidelines for Handling Lithium Batteries publication AG 5 4 violently Follow all local regulations for disposal of these mate
30. 1 data type 70 overview 68 produced 69 produced consumed safety data 70 71 program scoped 71 safety I 0 70 71 scope 70 See also safety tags terminology used throughout manual 11 timeout multiplier 54 U UL 109 unscheduled 44 upload effect of controller match 89 effect of safety signature 90 effect of safety lock 90 process 93 user memory 17 Rockwell Automation Support www rockwellautomation com Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com 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 For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside Unite
31. 1DS UMO01 provides information on explicit messaging and I O module troubleshooting To replace a CIP Safety I O module on DeviceNet networks you must prepare the new module for installation and determine whether you need to use the Configure Always feature Prepare the 1 0 Module 1 Set the node address of the replacement module 2 Be sure that the replacement module is of the correct type and in out of box condition Publication 1756 UM020C EN P December 2006 60 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Publication 1756 UMO20C EN P December 2006 3 Return the module to the out of box condition if necessary by clicking Reset Ownership on the Safety tab of the Module Properties dialog imi Module Properties DNB local 1791DS IB8X0B8 A 1 1 E General Connection Safety Module Info Input Configuration Test Output Output Configuration 15 x Connection Requested Packet Connection Reaction Max Observed Type Interval RPI ms Time Limit ms Network Delay ms Safety Input 102 401 365 Reset Safety Output 10 3041 283 Reset Configuration Ownership Local Reset Ownership e Configuration Signature Status Running IMPORTANT You must clear any pre existing configuration from a safety device prior to installing it on a safety network If you are relying on a portion of the CIP Safety syste
32. 3 and CAT 4 safety system requirements including functional validation test intervals system reaction time and PFD PFH calculations refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 You must read understand and fulfill these requirements prior to operating a GuardLogix controller based SIL 3 or CAT 4 safety system GuardLogix based safety applications require the use of at least one safety network number SNN and a safety signature Both affect controller and I O configuration and network communications Publication 1756 UM020C EN P December 2006 14 GuardLogix System Overview Distinguish Between Standard and Safety Components Publication 1756 UMO20C EN P December 2006 Safety Network Number The safety network number SNN must be a unique number that identifies safety subnets Each safety subnet that the GuardLogix controller uses for safety communications must have a unique SNN Each CIP Safety device must also be configured with the safety subnet s SNN The SNN can be assigned automatically or manually For information on the safety network number see Manage the Safety Network Number SNN on page 33 of this manual Also refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 Safety Signature The safety signature consists of an ID number date and time that uniquely identifies the safety portion of a project This includes all sa
33. 4 Monitor Status and Handle Faults Fault Codes The Safety Faults table shows the major and minor fault codes specific to GuardLogix controllers The type and code correspond to the type and code displayed on the Major Faults tab Cor Minor Faults tab of the Controller Properties dialog and in the PROGRAM object MAJORFAULTRECORD or MINORFAULTRECORD attribute Safety Faults Type Code Cause Status Corrective Action Task watchdog expired User task has not Nonrecoverable Clear the fault completed in a specified period of time A program error caused an infinite loop the If a safety signature exists safety memory is program is too complex to execute as quickly re initialized via the safety signature and the as specified a higher priority task is keeping safety task will begin executing 01 this task from finishing or the safety partner has been removed If a safety signature does not exist you must download the program again to allow the safety task to run Reinsert the safety partner if it was removed 02 An error exists in a routine of the safety task Recoverable Correct the error in the user program logic 03 Safety partner is missing Nonrecoverable Install a compatible safety partner 04 Safety partner is unavailable Nonrecoverable Install a compatible safety partner 05 Safety partner hardware is incompatible Nonrecoverable Replace the existing safety partner with a Major compatible safety p
34. 93 Provides information on calculating reaction times DeviceNet Safety I O Users Manual publication 1791DS UM001 Each safety device has a unique configuration signature which identifies the module configuration to verify the integrity of configuration data during downloads connection establishment and module replacement The configuration signature is composed of an ID number a date and a time Configured via RSLogix 5000 Software When the I O module is configured using RSLogix 5000 software the configuration signature is generated automatically You can view and copy the configuration signature via the Safety tab on the Module Properties dialog Configuration Signature Hex Copy Different Configuration Owner Listen Only Connection When the I O module configuration is owned by a different 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 TIP If the module is configured for inputs only you can copy and paste the configuration signature If the module has safety outputs they are owned by the controller that owns the configuration and the configuration signature text box is unavailable Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 57 Reset Safety 1 0 Module Ownership Address Safety 1 0 Data When RSLogix 5000 software is online the Safety tab of the Module P
35. A Refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 for more information on SIL 3 requirements Restrictions limiting the availability of some menu items and features that is cut paste delete search and replace are imposed by the programming software to protect safety components from being modified whenever the controller is safety locked a safety signature exists safety faults are present safety status is partner missing partner unavailable hardware incompatible firmware incompatible Develop Safety Applications 83 If any of those conditions apply you may not create new safety objects including safety programs safety routines safety tags and safety I O modules modify existing safety objects including safety programs safety routines safety tags and safety I O modules IMPORTANT The scan times of the safety task and any safety programs can be reset when online edit safety routines modify safety tag values using the tag monitor apply forces to safety tags create new safety tag mappings modify or delete existing tag mappings modify or delete user defined data types that are utilized by safety tags modify the controller name description chassis type slot and safety network number modify or delete the safety signature when safety locked Publication 1756 UM020C EN P December 2006 84 Develop Safety A
36. AB Allen Bradley GuardLogix Controllers Catalog Numbers 1756 L61S 1756 L62S 1756 LSP User Manual LLLI EC CLE tat Rockwell Automation 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 literature rockwellautomation com describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment The examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information circuits equipment or software des
37. Communication timeout NS Red On Communication failure The device has detected an error that has prevented network communication Red Green Flashing Device is in Communication Faulted state or safety network number SNN is being set Off Safety input is OFF Yellow On Safety input is ON Input Points INx Red On An error has occurred in the input circuit Red Flashing When dual channel operation is selected an error has occurred in the input circuit Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 59 Replace a CIP Safety 1 0 Module LED Indicator Operation LED Color State Description Yellow Off Safety output is OFF Yellow On Safety output is ON Output Points Ox Red Flashing When dual channel operation is selected an error has occurred in the output circuit Red On An error has occurred in the output circuit LOCK Yellow On Device configuration is locked Yellow Flashing Device configuration is valid but device is not locked Yellow Off Invalid or no configuration data IN PWR Green On Input power normal Green Off No input power OUT PWR Green On Output power normal Green Off No output power or output power exceeds the upper lower limit of the power range Monitor Input and Output Status Data You can monitor Safety I O module status data via explicit messaging The DeviceNet Safety I O User Manual publication 179
38. Description pages 52 55 Provides more information on setting the RPI and understanding how the Max Network Delay Timeout Multiplier and Network Delay Multipliers affect the Connection Reaction Time Chapter 7 Provides information on the CONNECTION STATUS predefined data type Logix5000 Controllers Common Provides instructions for creating user defined data Procedures Programming Manual types publication 1756 PM001 Safety Tag Mapping Controller scoped standard tags cannot be accessed by a safety routine because the data is not high integrity To allow standard tag data to be used within the safety task s routines the GuardLogix controller provides a safety tag mapping feature that allows a standard tag value to be copied into the safety task s memory at the start of the safety task s execution Restrictions Safety tag mapping is subject to these restrictions e The safety tag and standard tag pair must be controller scoped e The data types of the safety and standard tag pair must match e 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 e One safety tag may be mapped to one standard tag e Tag mapping cannot be modified when the project is safety locked a safety signature exists the keyswitch is in RUN position a nonrecoverable safety fault exists an invalid partnership exists betw
39. F Replace the battery every No required replacement 36 40 C 96 104 F 3 years 41 45 C 105 113 F 2 years 46 50 C 114 122 F 16 months 51 55 C 123 131 F 11 months 56 60 C 132 140 F 8 months IMPORTANT Because the GuardLogix controller is a 1002 controller two processors we strongly recommend that both controller batteries be replaced at the same time Publication 1756 UMO20C EN P December 2006 Maintain the Battery 117 Replace the Battery Because the controller uses a lithium battery you must follow specific precautions when handling or disposing of a battery The controller uses a lithium battery which contains potentially dangerous chemicals Before handling or disposing of a battery review Guidelines for Handling Lithium Batteries publication AG 5 4 When you connect or disconnect the battery 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 L l IMPORTANT If you remove the battery and then lose power the project in the controller will be lost Follow this procedure to replace the battery 1 Turn on the chassis power 2 Does the existing battery show signs of leakage or damage If Then Yes Before handling the battery review Guidelines for Handling Lithium Batteries publication AG 5 4 No Go
40. MO20C EN P December 2006 go online process 95 H hazardous location approval North America 113 HMI devices 15 l IP address 42 K keyswitch 18 L LED indicators CIP Safety 1 0 58 GuardLogix controller 97 major faults tab 104 view controller faults 103 view safety status 90 minor faults tab 104 module properties dialog connection tab 57 safety tab 52 56 morphing See changing controllers network delay multiplier 54 new controller dialog 23 non recoverable safety faults re starting the safety task 103 0 online bar 99 ownership configuration 57 resetting 57 P password set 26 valid characters 26 peer safety controller configuration 29 SNN 29 power supplies catalog numbers 19 primary controller description 17 hardware overview 17 modes 18 user memory 17 probability of failure on demand PFD definition 11 values 110 probability of failure per hour PFH definition 11 values 110 produce and consume tags 40 44 produced tag description 69 72 program fault routine 105 program scoped tags 71 protecting the safety application 79 82 RSLogix Security 81 safety signature 81 safety lock 79 RAM capacity 17 reaction time limit CIP Safey 1 0 52 requested packet interval consumed tags 69 DeviceNet Safety 1 0 52 reset ownership 57 60 restrictions software 82 when safety signature exists 81 when safety locked 80 RPI see requested packet interval RSLogix 5000 description 20 restrict
41. Maximum Network Delay field on the Safety tab Since the CIP Safety time coordination is based on a message from the producer to the consumer and all calculations are done in a conservative manner the actual message delay will be less than the Maximum Network Delay In general the actual maximum message delay will be approximately one half the Maximum Network Delay observed Publication 1756 UM020C EN P December 2006 54 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Publication 1756 UMO20C EN P December 2006 Set the Advanced Connection Reaction Time Limit Parameters Advanced Connection Reaction Time Limit Configuration m Input Requested Packet Interval RPI Hj ms 1 500 Timeout Multiplier 2 a 1 4 Network Delay Multiplier 200 10 600 Connection Reaction Time Limit 40 1 ms Dutput Requested Packet Interval RPI 10 ms Safety Task Period Timeout Multiplier 2 a 1 4 Network Delay Multiplier 200 4 10 600 Connection Reaction Time Limit 30 1 ms Cancel Help 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 A Timeout Multiplier of 2 indicate
42. P You can use the Controller Properties dialog 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 C Change Controllers for details on the ramifications of changing controllers Additional Resources Resource Description task safety programs and safety routines Chapter 3 Communicate Over Networks Provides more information on managing the SNN Publication 1756 UM020C EN P December 2006 26 Configure the GuardLogix Controller Set Passwords for Safety locking and unlocking Publication 1756 UMO20C EN P December 2006 Safety locking the controller protects safety control components from modification Only safety components such as the safety task safety programs safety routines and safety tags are affected Standard components are unaffected You can safety lock or unlock the controller project either online or offline The safety lock and unlock feature uses two separate passwords Passwords are optional Follow these steps to set passwords 1 From the Tools gt Safety menu choose Change Password Change Passwords x What Password Old Password New Password Confirm New Password Cancel Help 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
43. Software Purpose RSLog Software ix 5000 Programming This software is required to configure the GuardLogix project and define EtherNet IP communications BOOTP DHCP Utility EtherNet IP network This utility comes with RSLogix 5000 software You can use this utility to assign IP addresses to devices on an RSNetWorx for EtherNet IP Software by IP addresses and or host names The EtherNet IP communication modules You can use this software to configure EtherNet IP devices e support messaging produced consumed tags HMI and distributed I O support CIP Safety communications encapsulate messages within standard TCP UDP IP protocol share a common application layer with ControlNet and DeviceNet networks interface via RJ45 category 5 unshielded twisted pair cable support half full duplex 10 Mbps or 100 Mbps operation support standard switches require no network scheduling require no routing tables Publication 1756 UM020C EN P December 2006 40 Communicate Over Networks Publication 1756 UMO20C EN P December 2006 Produce and Consume Data via the EtherNet IP Network The GuardLogix controller supports the ability to produce broadcast and consume receive system shared tags over the EtherNet IP network Produced and consumed tags each require connections The total number of tags that can be produced or consumed is limited by the number of available connections Connections
44. a Safety tags have all the attributes of standard tags with the addition of mechanisms certified to provide SIL 3 data integrity When you create a tag you assign the following properties e Name e Description optional Tag type e Data type e Scope e Class e Style Develop Safety Applications 69 Open the New Tag dialog by right clicking Controller Tags or Program Tags and choosing New Tag x Name OK Description a Cancel Help u Type Baes nnectior Alias For Data Type pro H Scope 5 SD safetycontroller Class Samdud v Style Dem F Configure on GF Tag Type There are four types of tags base alias produced and consumed 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 An alias tag can also refer to a component of another tag by referencing a member of a structure an array element or a bit within a tag or member IMPORTANT Aliasing between standard and safety tags is prohibited in safety applications Produced A tag that a controller makes available for use by other controllers A maximum of 15 controllers can simultaneously consume receive the data A produced tag sends its data to one or more consuming tags without using logic Produced tag data is sent at the RPI of the consuming tag Consum
45. able the safety task to run If no safety signature exists the safety task cannot run again until the entire application is downloaded again Recoverable Faults in the Safety Application When a recoverable fault occurs in the safety application the system may or may not halt the execution of the safety task depending upon whether or not the fault is handled by the Program Fault Handler in the safety application If a recoverable fault is cleared programmatically the safety task is allowed to continue without interruption If a recoverable fault in the safety application is not cleared programmatically a Type 14 Code 2 recoverable safety fault occurs The safety program execution is stopped and safety protocol connections are closed and reopened to reinitialize them Safety outputs are placed in the safe state and the producer of safety consumed tags commands the consumers to place them in a safe state as well Recoverable faults let you to edit the standard and safety application as required to correct the cause of the fault However if a safety signature exists or the controller is safety locked you must first unlock the controller and delete the safety signature before you can edit the safety application View Faults The Recent Faults dialog on the Major Faults tab of the Controller Properties dialog contains two sub tabs one for standard faults and one for safety faults Publication 1756 UMO20C EN P December 2006 10
46. afety I 0 modules support standard as well as safety data Module configuration defines what data is available You cannot add or delete a CIP Safety I O module on DeviceNet Set the Safety Network Number SNN Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 51 3 Specify the module properties New Module E x General Connection Safety Module Info Input Configuration Test Output Output Configuration Type 1791DS IBSXOB8 8 Point 24VDC Sink Safety Input 8 Point 24 VDC Source Safety Output Vendor Allen Bradley Parent DNB_local Name Node 1 bd Description x Safety 2 80 033C EFBA Network Number ASAE LISA E zi 8 4 2004 10 05 25 82 AM r Module Definition Series Revision Electronic Keying Input Data Input Status Output Data Data Format E 13 Exact Match Safety None Safety Integer Change Status Creating Cancel Help a Modify the Module Definition settings if required by clicking Change b Type a name for the new module c Enter the node address of the module on its connecting network Only unused node numbers are included in the pull down list d Modify the safety network number SNN if required by clicking the button See page 51 for details e Set module configuration parameters using the Input Configuration Test Output and Output Configuration tabs Refer to RSL
47. age those new features will be visible in the Controller Properties dialog TIP Peer safety controllers are not deleted even if they have no connections remaining As a result of the above changes to the system safety specific instructions or safety I O tags will not verify Instructions may still reference modules that have been deleted In addition consumed tags are deleted when the producing module is deleted Numerics 1747 CP3 cable 85 1756 Axx 18 1756 CP3 cable 85 1756 DNB connections 47 1756 PA72 19 1756 PA75 19 1756 PA75R 19 1756 PB72 19 1756 PB75 19 1756 PB75R 19 A address CIP Safety 1 0 module 57 advanced connection reaction time 54 alias tags 69 base tags 69 battery disposal 118 installation 117 replacement procedure 117 replacement schedule 116 storage 118 C CE 109 certifications 109 Change Controller button 25 changing controllers 119 120 chassis hardware overview 18 CIP Safety 1 0 adding 49 configuration signature 56 LED indicators 58 monitor system status 58 node address 49 replacing 59 63 reset ownership 57 status data 59 CIP Safety protocol definition 33 Index class 72 communication ControlNet 43 EtherNet IP 39 CompactFlash 17 configuration ownership identifying 57 resetting 57 configuration signature components 56 copy 56 definition 56 configure always checkbox 27 61 63 connect ControlNet 43 EtherNet IP 39 connection ControlNet 44 EtherNet IP 40 connection statu
48. ags 5 In the Controller Tags dialog right click the tag that will consume the data and choose Edit Tag Properties 6 In the Tag Properties dialog click Connection to open the Consumed Tag Connection dialog fo Tag Properties valC ini xl General Name mo Description Ig Type Consumed Alias For el Data Type mypcType o Scope i consumer Class Style 7 Configure the consumed tag connection properties on the Connection tab Consumed Tag Connection x Connection Safety Producer Producer Remote Data Tz Tag Name or Instance Number BPI 10 ms Jv Include Connection Status Cancel Help a Select the controller that produces the data b Enter the name of the produced tag c Enter the requested packet interval RPD for the connection in 1 ms increments The default is 20 ms The RPI specifies the period at which data updates over a connection The RPI of the consumed safety tag must match the safety task period of the producing safety project Publication 1756 UM020C EN P December 2006 76 Develop Safety Applications Publication 1756 UMO20C EN P December 2006 8 10 Choose the Safety tab to further refine the timing parameters x Connection Safety Requested Packet Interval RPI 1074 ms 1 500 Advanced Connection Reaction Time Limit 30 0 ms Max Network Delay 0 0 ms Reset Mar e Cancel Help
49. and one of which may be designated as the fault routine Safety programs may also define program scoped safety tags Safety programs cannot contain standard routines or standard tags Safety routines have all the attributes of standard routines except that they can exist only in a safety program At this time only relay ladder logic is supported for safety routines TIP RSLogix 5000 software uses a watermark feature to visually distinguish a safety routine from a standard routine f RSLogix 5000 SD_safetycontroller 1756 L615 SafetyProgram MainRoutine 4 sig x B File Edit View Search Logic Communications Tools Window Help lj x Bis S sale ol s eI Te vier eje Offline 0 F RUN wmm gd rah oe wd No Forces p F ok t E Notds 8 a Hfj 2e nel RO Oa No Edits a Eu d F yao Safety Unlocked 5 Bj p Favorites Bt X TimeriCounter X Input Output X Compare A J Controller 5D safetycontroller aA Controller Tags Controller Fault Handler Power Up Handler E E3 Tasks S A MainTask amp CR MainProgram E ESI SafetyTask E B SafetyProgram A Program Tags D MainRoutine Unscheduled Programs m Sj Motion Groups 4 gt MMainRoutine 4 Rung 0 of 1 app per Ca A tag is a text based name for 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 dat
50. are are online the safety locked status and safety signature of the controller match the controller s project The safety lock status and safety signature of the offline project are overwritten by the controller If you do not want the changes to the offline project to be permanent do not save the project file following the go online process Publication 1756 UMO20C EN P December 2006 Introduction Monitor Controller Status View LED Indicators Chapter Monitor Status and Handle Faults Topic Pae Monitor Controller Stats 9 Monitor Connections 100 Monitor Safety Status 101 GuardLogix Controller Faults 102 Develop a Fault Routine 105 codes Controller LED Indicators You can monitor status using the controller LED indicators and fault Primary controller and safety partner status is displayed by LED indicators LED Color Status Primary Controller Description Safety Partner Description RUN Off No user tasks running Controller is in PROGram Not applicable mode Green Controller is in RUN mode Not applicable SAFE Off Not applicable The user safety task or safety outputs are RUN disabled The controller is in the PROGram mode test mode or the safety task is faulted Green Not applicable The user safety task and safety outputs are enabled The safety application is executing at its periodic rate FORCE Off No forces standard or safety are enabled on the Not appl
51. artner 14 06 Safety partner firmware is incompatible Nonrecoverable Update the safety partner so that the firmware major and minor revision matches the primary controller 07 Safety task is inoperable Nonrecoverable Clear the fault If a safety signature exists safety memory is re initialized via the safety signature and the safety task will begin executing If a safety signature does not exist you must download the program again to allow the safety task to run 08 Coordinated system time CST not found Nonrecoverable Clear the fault Configure a device to be the CST master 09 Safety partner nonrecoverable controller fault Nonrecoverable Clear the fault and download the program If the problem persists replace the safety partner Minor 11 The Safety partner s battery is missing or Recoverable Install or replace the battery on the safety 10 requires replacement partner See Appendix B for information on replacing the battery The Logix5000 Controllers Common Procedures Programming Manual publication 1756 PMO001 contains descriptions of the fault codes common to all Logix controllers Publication 1756 UMO20C EN P December 2006 Monitor Status and Handle Faults 105 Develop 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 that is turning all outputs to their user configure
52. ata with Safety Integrity Level SIL 3 integrity The producing conroller uses two connections for each consumer one for safety data and one for time coordination Consumed GuardLogix controllers can consume safety tags from other GuardLogix controllers Each consumed tag or UDT consumes two connections one for safety data and one for time coordination Produced and consumed safety tags are subject to the following restrictions e Only controller scoped tags can be shared e Produced and consumed safety tags are limited to 128 bytes e Produced consumed tag pairs must be of the same user defined data type e The first member of that user defined data type must be the predefined CONNECTION STATUS data type The request packet interval RPD of the consumed safety tag must match the safety task period of the producing safety project Develop Safety Applications Produce a Safety Tag Follow this procedure to produce a safety tag 73 1 Open the GuardLogix controller project that contains the tag you 6 want to produce In the Controller Organizer right click the Controller Tags folder and choose Edit Tags In the Controller Tags dialog right click the tag you want to produce and choose Edit Tag Properties ontroller Tags producer controlle Scope B producer Show show au Name Alias For Base Tag Data Ty
53. ber checkbox and choosing Upload The software checks whether the open project matches the controller project a If the projects do not match you must select a matching file or cancel the upload process b If the projects match the software checks for changes in the offline open project The software checks for changes in the offline project a If there are no changes in the offline project you can go online without uploading Click Go Online b If there are changes in the open project that are not present in the controller you can choose to upload the project cancel the upload or select a different file If you choose Upload the standard and safety applications are uploaded If a safety signature exists it is also uploaded The Go Online with the Controller 95 safety lock status of the project reflects the original status of the online controller project TIP Prior to the upload if an offline safety signature exists or the offline project is safety locked but the controller is safety unlocked or has no safety signature the offline safety signature and safety locked state will be replaced by the online values safety unlocked with no safety signature If you do not want to make these changes permanent do not save the offline project following the upload Go Online GuardLogix Controller Online monitor a project that a controller is executing Project Project Online
54. can be read directly by standard logic 5 Safety tags can be read or written by safety logic 6 Safety tags can be exchanged between GuardLogix controllers over Ethernet or ControlNet networks 7 Safety tag data either program or controller scoped can be read by external devices such as HMI devices personal computers or other standard controllers IMPORTANT Me this data is read it is considered standard data not SIL 3 GuardLogix System Overview 17 Select GuardLogix System The GuardLogix controller is made up of a primary controller Hardware 1756 L6xS and a safety partner 1756 LSP which function together in a 1002 architecture The GuardLogix system supports SIL 3 and CAT 4 safety applications The safety partner must be installed in the slot immediately to the right of the primary controller The firmware major and minor revisions of the primary controller and safety partner must match exactly to establish the control partnership required for safety applications Primary Controller The primary controller catalog number 1756 L6xS is the processor that performs standard and safety functions and communicates with the safety partner for safety related functions in the GuardLogix control system Standard functions include e I O control Logic e Timing e Counting e Report generation e Communications e Arithmetic Computations e Data file manipulation The primary controller consists of a
55. central processor I O interface and memory Two catalog numbers are available Memory Capacity Catalog User Memory RAM Capacity Number Standard Tasks and Components Safety Task and Components 1756 L61S 2 MB 1 MB 1756 L628 4 MB 1 MB The GuardLogix controller does not support OS upgrades or user program storage and retrieval using CompactFlash However in version 16 of RSLogix 5000 software you will be able to view the contents of a CompactFlash card if one is installed in the primary controller Publication 1756 UM020C EN P December 2006 18 GuardLogix System Overview A three position keyswitch on the front of the primary controller governs the controller operational modes The following modes are available e RUN e PROGram e REMote this software enabled mode can be Program Run or Test Safety Partner The safety partner catalog number 1756 LSP is a coprocessor that provides redundancy for safety related functions in the system The safety partner does not have a keyswitch or RS 232 communications port Its configuration and operation are controlled by the primary controller The GuardLogix Controller Installation Instructions publication 1756 IN045 provides detailed information on installing the primary controller and safety partner Chassis The chassis provides physical connections between modules and the GuardLogix controller Chassis Catalog Numbers
56. ch DeviceNet network All safety devices on a DeviceNet subnet can have the same SNN e each chassis that contains one or more GuardLogix controllers TIP Multiple safety network numbers can be assigned to a CIP Safety subnet or a ControlBus chassis that contains more than one safety device However for simplicity we recommend that each CIP Safety subnet have one and only one unique SNN The SNN can be either software assigned time based or user assigned manual These two formats of the SNN are described in the following sections Publication 1756 UM020C EN P December 2006 34 Communicate Over Networks Publication 1756 UMO20C EN P December 2006 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 Safety Network Number x Eormat Generate ol 8 4 2004 8 36 16 195 AM C Manual 1756 Backplane Decimal Number 2E80_02EB_5143 Hex Copy Paste Cancel Help Manual Safety Network Number If the manual format is selected the SNN represents entered values from 1 through 9999 decimal Safety Network Number I x Eormat C Time based Generate DeviceNet 3333 Decimal Number 0001_0000_270F Hex Copy Paste Cancel Help Assign the Safety Network Number SNN You can allo
57. cribed in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations Identifies information about practices or circumstances that can cause an explosion in a hazardous environment which may lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence ATTENTION HA away Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present PDL vai Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may reach dangerous temperatures IPIE Rockwell Automation Allen Bradley TechConnect ControlLogix GuardLogix ControlFlash Logix Logix5000 RSLogix 5000 RSNetWrox for EtherNet RSNetWorx for DeviceNet RSNetWorx for ControlNet and RSLinx are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Summary of C
58. cs like programming your GuardLogix controller SIL 3 requirements or information on ControlLogix components see the list of Additional Resources on page 10 Who Should Use This Use this manual if you are responsible for designing installing Manual programming or troubleshooting control systems that use GuardLogix anua controllers You must have a basic understanding of electrical circuitry and familiarity with relay logic You must also be trained and experienced in the creation operation and maintenance of safety systems Publication 1756 UM020C EN P December 2006 10 Preface Additional Resources The table below provides a listing of publications that contain important information about GuardLogix controller systems Related Documentation Resource GuardLogix Controller Installation Instructions publication 1756 IN045 Description Provides information on installing the GuardLogix Controller GuardLogix Controllers Systems Safety Reference Manual publication 1756 RM093 Contains detailed requirements for achieving and maintaining SIL 3 with the GuardLogix Controller System GuardLogix Safety Application Instruction Set Reference Manual publication 1756 RM095 Provides information on the GuardLogix Safety Application Instruction Set DeviceNet Safety 1 0 Installation Instructions publication 1791DS IN001 Provides information on installing DeviceNet Safety 1 0 Modules DeviceNet Safety I O User
59. d states Depending on your application you may not want all safety faults to shut down your entire system In those situations you can 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 You must provide proof to your certifying agency that allowing a ATTENTION 1 i Mae portion of the system to continue to operate maintains safe operation The controller supports two levels for handling major faults Program Fault Routine e Controller Fault Handler Both routines can use the GSV and SSV instructions as described on page 106 Program Fault Routine Each program can have its own fault routine The controller executes the program s fault routine when an instruction fault occurs If the program s fault routine does not clear the fault or if a program fault routine does not exist the controller proceeds to execute the controller fault handler if one exists Controller Fault Handler The controller fault handler is an optional component that executes when the program fault routine could not clear the fault or does not exist You can create only one program for the controller fault handler After you create that program you must configure a routine as the main routine Publication 1756 UMO20C EN P December 2006 106 Monitor Status and Handle Faults Publication 1756 UMO20C EN P December 2006 The Lo
60. d Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 UMO020C EN P December 2006 Supersedes Publication 1756 UM020B EN P October 2005 Copyright 2006 Rockwell Automation Inc All rights reserved Printed in the U S A
61. d as shown above the online bar shows the controller s mode RUN and status OK The BAT LED indicator combines the status of both the primary controller and the safety partner If either or both have a battery fault the LED indicator illuminates The I O LED indicator combines the status of both standard and safety I O and behaves just like the LED indicator on the controller The I O with the most significant error status is displayed next to the LED indicator When the Safety Status button is selected as shown below the online bar displays the safety signature Offline f Safety Signature TTC No Forces E none 1 No Edits a Safety Unlocked 3 o 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 Safety Status Icon If the safety status is This icon is displayed Safety Task OK m Safety Task Inoperable A Partner Missing Partner Unavailable 3 Hardware Incompatible Firmware Incompatible Offline LS Icons are green when the controller is safety locked yellow when the controller is safety unlocked and red when the controller has a Safety fault When a safety signature exists the icon includes a small check mark Publication 1756 UM020C EN P December 2006 100 Monitor Status and Handle Faults Monitor Connections Publication 1756 UMO20C EN P December 2006 All Connections If
62. ed unlocked Status below Safety task inoperable Safety Signature and Safety locked unlocked Status On Upload If the controller contains a safety signature it is uploaded with the project The safety lock status of the uploaded project is set to that of the online project For example if the online project was safety unlocked it remains safety unlocked following the upload even if the offline project was locked prior to the upload Following an upload the safety signature also matches the status of the uploaded project If a safety signature existed in the offline project but there is no safety signature in the controller the offline safety signature is deleted during the upload On Download For safety projects the existence of a safety signature in the controller as well as the controller s safety lock status determines whether or not a download can proceed Following a successful download the controller s safety lock status is set to the original value of the offline project Go Online with the Controller 91 The combination of safety signature status and controller safety locked status affects the GuardLogix controller s download functionality The Effect of Safety lock and Safety Signature on Download Operation Safety lock Status Controller safety unlocked Safety Signature Status Safety signature in the offline project matches the safety signature in the controller Download Functionalit
63. ed A tag that receives the data of a produced tag The data type of the consumed tag must match the data type of the produced tag The requested packet interval RPI of the consumed tag determines the period at which the data updates Publication 1756 UMO20C EN P December 2006 70 Develop Safety Applications Publication 1756 UMO20C EN P December 2006 Data Type The data type defines the type of data that the tag stores such as bit integer floating point value or string Data types can be combined into a structure A structure is formatted to create 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 All Logix controllers contain predefined data types for use with specific instructions You can create safety tags of any valid data type Valid Data Types for Safety Tags BOOL FBD CONVERT REDUNDANT INPUT CAM PROFILE FBD COUNTER REDUNDANT OUTPUT CONNECTION STATUS FBD LOGICAL SERIAL PORT CONTROL CONTROL FBD MASK EQUAL SFC ACTION COUNTER FBD MASKED MOVE SFC STEP DINT FBD TIMER SFC STOP DIVERSE INPUT FIVE POS MODE SELECTOR SINT EMERGENCY STOP INT STRING ENABLE PENDANT LIGHT CURTAIN TIMER EXT ROUTINE CONTROL MOTION INSTRUCTION TWO HAND RUN STATION EXT ROUTINE PARAMETERS PHASE FBD BIT FIELD
64. edundancy rabled Help Name Poo Description a Chassis Type 1756 410 10 Slot ControlLogix Chassis X Slot o a Safety Partner Slot 1 Create In EARSLogix 5000 Projects Browse 3 Enter the major revision of firmware for the controller Publication 1756 UM020C EN P December 2006 24 Configure the GuardLogix Controller Publication 1756 UMO20C EN P December 2006 4 Type a name for the controller When you create a project the project name is the same as the name of the controller However you can rename either the project or the controller 5 Select the chassis size 6 Enter the slot number of the controller The New Controller dialog 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 will be prompted to re enter a valid slot number 7 Specify the folder in which to store the safety controller project 8 Click OK RSLogix 5000 software automatically creates a safety task and a safety program A main ladder logic safety routine called MainRoutine is also created within the safety program Controller SD safetycontroller amp Tasks E MainTask H E MainProgram yTask SafetyProgram A Program Tags Eh MainRoutine E Unscheduled Programs 3 Motion Gro
65. een the primary controller and safety partner When using standard data in a safety routine you are responsible for providing a reliable means of ensuring that the data is used in an appropriate manner Using standard data in a safety tag does not make it safety data You must not directly control a safety output with standard tag data Refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RMO93 for more information Publication 1756 UMO20C EN P December 2006 78 Develop Safety Applications Publication 1756 UMO20C EN P December 2006 Create Tag Mapping Pairs 1 Choose Map Safety Tags from the Logic menu to open the Safety Tag Mapping dialog E Standard Tag Name amp Safety Tag Name e Ej Help Delete Row e 2 Add an existing tag to either the Standard Tag Name or Safety Tag Name column by e typing the tag name into the cell e selecting a tag from the pull down list Clicking the pull down arrow to display a filtered tag browser dialog 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 x _ Standard TagName a Tag Name esi AB 1791D 4B 1791D Filter Show All 3 Add a new tag to either the Standard Tag Name or Safety Tag Name column by e right clicking in the empty cell and selecting New Tag e t
66. elop Safety Applications Publication 1756 UMO20C EN P December 2006 The following actions are not permitted in the safety portion of the application when the controller is safety locked Online offline programming or editing e Forcing safety I O e Changing the inhibit state of safety I O or producer controllers e Data manipulation except by safety routine logic e Generating or deleting the safety signature TIP The text of the online bar s safety status button indicates the safety lock status Offline f E RUN NoFoce p TOK 4 No Edits Ar E Safety Status Button Safety Unlocked 593 T The application tray also displays the following icons to indicate the safety controller s safety lock status e 0 controller safety locked E controller safety unlocked You can safety lock the controller project regardless of whether you are online or offline and regardless of whether you have the original source of the program However no safety forces or pending online safety edits may be present Safety locked or unlocked status cannot be changed when the keyswitch is in the RUN position You can Safety lock and unlock the controller from the Safety tab of the Controller Properties dialog or by choosing Safety gt Safety Lock Unlock from the Tools Safety menu Safety Lock E x Locking disables data editing logic editing and forcing in the safety application Lock safety application E
67. es whether the safety connection between the safety producer and the safety consumer is Valid 0 or Faulted 1 If ConnectionFaulted is set to Faulted 1 as a result of a loss of the physical connection the safety data is reset to zero Monitor Status and Handle Faults 101 Monitor Status Flags Monitor Safety Status The following table describes the combinations of the RunMode and ConnectionFaulted states Safety Connection Status RunMode ConnectionFaulted Status Status 1 Run 0 Valid Data is actively being controlled by the producing device The producing device is in Run mode Safety Connection Operation 0 Idle 0 Valid The connection is active and the producing device is in the Idle state The safety data is reset to zero 0 Idle 1 Faulted The safety connection is faulted The state of the producing device is unknown The safety data is reset to zero 1 Run 1 Faulted Invalid state If a module is inhibited the ConnectionFaulted bit is set to Faulted 1 and the RunMode bit is set to Idle 0 for each connection associated with the module As a result safety consumed data is reset to zero All Logix controllers including GuardLogix controllers support status keywords that you can use in your logic to monitor specific events For more information on how to use these keywords refer to the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 In additi
68. et Module Fault Code 162020 No safety task running in controller Status Faulted Cancel Help 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 When a nonrecoverable controller fault occurs safety task execution stops and CIP Safety I O on DeviceNet networks is placed in the safe state Recovery requires that you download of the application program again Nonrecoverable Safety Faults in the Safety Application When a nonrecoverable safety fault occurs in the safety application both safety logic and the safety protocol are terminated Safety task watchdog and control partnership faults fall into this category Monitor Status and Handle Faults 103 If the safety task encounters a nonrecoverable safety fault that is cleared programmatically in the Controller Fault Handler the standard application continues to execute Overriding the safety fault does not clear it If you override the safety fault it is your responsibility to prove that doing so maintains safe operation You must provide proof to your certifying agency that allowing a portion of the system to continue to operate maintains safe operation If a safety signature exists you only need to clear the fault to en
69. fety logic data and configuration The GuardLogix system uses the safety signature to determine the project s integrity and to let you verify that the correct project is downloaded to the target controller See Generate a Safety Signature on page 81 for more information Creating recording and verifying the safety signature is a mandatory part of the safety application development process Refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RMO093 for details Slots of a GuardLogix system chassis not used by the safety function may be populated with other ControlLogix modules that are certified to the Low Voltage and EMC Directives Refer to http ab com certification ce to find the CE certificate for the Programmable Control ControlLogix Product Family and determine which modules are certified GuardLogix System Overview 15 You must create and document a clear logical and visible distinction between the safety and standard portions of the application To aid in creating this distinction RSLogix 5000 programming software features safety identification icons to identify the safety task safety programs safety routines and safety components In addition the RSLogix 5000 software uses a safety class attribute that is visible whenever safety task safety program or safety routine properties are displayed The GuardLogix controller does not allow writes to safety tag data from external HMI
70. gix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 provides details on creating and testing a fault routine 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 get 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 When you enter a GSV or SSV instruction the programming software displays the valid object classes object names and attribute names for each instruction For standard tasks you can use the GSV instruction to get values for all the available attributes When using the SSV instruction the software displays only those attributes you are allowed to set For the safety task the GSV and SSV instructions are more restricted Note that SSV instructions in both safety and standard tasks cannot set bit 0 major fault on error in the the mode attribute of a safety I O module For safety objects the GSV SSV Accessibility table on page 107 shows which attributes you can get values for using the GSV instruction and which attributes you are allowed to set using the SSV instruction in both the Safety and standard tasks Use the GSV SSV instructions carefully Making changes to objects can cause unexpec
71. go online with a target controller based on whether the offline project is new or whether changes have occurred in the offline project If the project is new you must first download the project to the controller If changes have occurred to the existing project you will be prompted to upload or download If no changes have occurred you can go online to monitor the execution of the project A number of factors affect these processes including Project to Controller Match feature the safety status between the primary controller and safety partner the existence of a safety signature and the safety lock unlock status of the project and the controller Go Online with the Controller 89 Project to Controller Matching The Project to Controller Match feature affects the download upload and go online processes of all projects both standard and safety If the Project to Controller Match feature is enabled in the offline project RSLogix 5000 software compares the serial number of the controller in the offline project to that of the connected controller If they do not match you must either cancel the download upload connect to the correct controller or confirm that you are connected to the correct controller which will update the serial number in the project to match the target controller Firmware Revision Matching Firmware revision matching affects the download process If the revision of the controller does not match the revision of
72. gs you must create a user defined data type The first member of the tag structure must be a predefined data type called CONNECTION STATUS Controller Tags consumer controller E lal x v Sor Name id Fite Show All Force Mask f Style Scope g consumer Description E valC status m Bon C CONNECTION STATUS E valC data Decimal DIN e The requested packet interval RPD of the consumed safety tag must match the safety task period of the producing safety project Consumer s Project Producer s Project x zax Connection Safety General Configuration Program Schedule Monitor Requested Packet Interval RPI ms 1 500 Advanced Type Connection Reaction Time Period ms Limit 30 0 ms Priority fio Lower Number Yields Higher Priority Max Observed 0 ms Reset Max e Watchdog 10 000 ms Cancel Help Publication 1756 UMO20C EN P December 2006 Configure the GuardLogix Controller 31 Set the RPI via the Safety tab on the Consumed Tag Connection dialog To open this dialog right click the consumed tag and choose Edit TIP In RSLogix 5000 software version 16 the default Safety Task RPI was changed from 10 ms to 20 ms To view or edit the safety task period right click the producing safety task and choose Properties Then choose the Configuration tab Additional Resources Resource Desc
73. guration tree of the GuardLogix controller project CIP Safety I O modules on DeviceNet networks are added to the project under the 1756 DNB module as described in Chapter 4 Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks When you add a CIP Safety I O module RSLogix 5000 software automatically creates controller scoped safety data tags for that module Standard DeviceNet Connections Communicate Over Networks 47 Controller Organizer x Controller 5D safetycontroller Tasks H f MainTask A SafetyTask El o SafetyProgram G Unscheduled Programs m e Motion Groups Trends E Data Types E1 3 I O Configuration B S ControlBus 1756 A10 fh 0 1756 L615 SD safetycontroller g 1 1756 LSP SD safetycontroller Partner WELZ 1756 DNB DNB local EB am DeviceNet BJ 0 1756 DNB DNB local 8j 1 1791D5 IB8XOB8 A In out 5 Module Defined Tags A Locat2 l A Local 2 0 A Local 2 S If you use standard DeviceNet I O with your GuardLogix controller you will need to allocate two connections for each 1756 DNB module One connection is for module status and configuration The other connection is a rack optimized connection for the DeviceNet I O data To use the 1756 DNB module to access standard data via the DeviceNet network you must use RSNetWorx for DeviceNet software to e create a configuration file for the network e configure each standard device on the network e co
74. hanges The information below summarizes the changes to this manual since the last publication To help you find new and updated information in this release of the manual we have included change bars as shown to the right of this paragraph Topic Page Understanding GuardLogix controller s data flow capabilities 16 The controller does not support OS upgrades using CompactFlash 17 The safety task does not support Add on Instructions or Alarms and 20 Events The maximum RPI for safety connections has changed from 500 ms to 52 67 100 ms The list of illegal data types for safety programs has been replaced by 70 a list of valid data types The descriptions of safety produced and consumed connections has 72 been revised The explanation of the effect of the safety lock feature and the safety 91 signature on download operation has been revised UL NRGF certification 110 Probability of failure on demand PFD and probability of failure per 110 hour PFH values added to controller specifcations Publication 1756 UM020C EN P December 2006 4 Summary of Changes Publication 1756 UMO20C EN P December 2006 GuardLogix System Overview Configure the GuardLogix Controller Communicate Over Networks Table of Contents Preface TOLGOCI CHOR y des eb dte dr dei ote ote ed te se e o Se Bets 9 Purpose of This Manual aos x dy dcn RR OP TOR Re ORE Rs 9 Who should Use This Manuals usua tte a perte 9 Additio
75. he Match Project to Controller option on the Advanced tab of the Controller Properties dialog and enter your controller s eight digit hexidecimal serial number found on the controller label fo Controller Properties SD safetycontroller Configure the GuardLogix Controller 29 Configure a Peer Safety You can add a peer safety controller to the I O configuration folder of Controll your GuardLogix safety project to allow standard or safety tags to be ontroller consumed The peer GuardLogix safety controller is subject to the same configuration requirements as the local GuardLogix safety controller The peer safety controller must also have a safety network number SNN The SNN of the peer safety controller depends upon its placement in the system SNN and Controller Placement SNN Placed in the local chassis GuardLogix controllers located in a common chassis should have the same SNN Placed in a different chassis The controller must have a unique SNN To share safety data between peer controllers you produce and consume controller scoped safety tags Produced consumed safety tag pairs must be of the same data type To share data between peer safety controllers the following additional requirements must be met Peer Safety Controller Location e The SNN entered on the producer controller s Module Properties dialog in the consumer s safety project must match the SNN that is configured in the producer con
76. ible Choose one of the following options e Choose Update Firmware Choose the required revision and click Update Confirm your selection by clicking Yes IMPORTANT The online project will be deleted e To preserve the online project cancel the online process and install a version of RSLogix 5000 software that is compatible with the firmware revision of your controller You need to upload or download in order to go online using the open project Choose one of the following options e Upload to update the offline project e Download to update the controller project or e Select File to choose a different offline project Unable to connect in a manner that preserves safety signature Controller s firmware minor revision is not compatible with safety signature in offline project e To preserve the safety signature when the firmware minor revision is incompatible update the firmware revision in the controller to exactly match the offline project Then go online to the controller e To proceed with the download despite the safety signature incompatibility click Download The safety signature will be deleted IMPORTANT The safety system will require revalidation Unable to connect to controller Incompatible safety signature cannot be deleted while project is safety locked Cancel the online process You must safety unlock the offline project before attempting to go online When the controller and RSLogix 5000 softw
77. icable controller Amber Standard and or safety forces have been enabled Not applicable Amber Flashing One or more I O addresses standard and or safety have been forced to an on or off state but forces are not enabled Not applicable Publication 1756 UM020C EN P December 2006 98 Monitor Status and Handle Faults View LED Indicators LED Color Status Primary Controller Description Safety Partner Description BAT Off The battery is able to support memory The battery is able to support memory Red The battery is not able to support memory The battery is not able to support memory OK Off No power is applied No power is applied Green The controller is operating with no faults The safety partner is operating with no faults Red Flashing Nonrecoverable fault or recoverable fault not Not applicable handled in the fault handler All user tasks both standard and safety are stopped Red Powering up or nonrecoverable controller fault Powering up or nonrecoverable controller fault o Off No activity No 1 0 is configured Not applicable Green The controller is communicating to all configured Not applicable 1 0 devices both standard and safety Green Flashing One or more 1 0 devices is not responding Not applicable Red Flashing Controller is not communicating to any configured Not applicable 1 0 RS232 Off There is no activity Not applicable Green Data is being
78. igure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Introduction M f Topic Page Add CIP Safety 1 0 Modes o Ta Configure CIP Safety 1 0 Modules via RSLogix 5000 Software 50 Set the Safety Network Number SNN 51 Set the Connection Reaction Time Limit 52 Understand the Configuration Signature 56 Reset Safety I O Module Ownership 57 Address Safety 0 Data 57 Monitor Safety 1 0 Module Status 58 Replace a CIP Safety 1 0 Module 59 For more information on installation configuration and operation of CIP Safety I O on DeviceNet networks refer to the DeviceNet Safety I O User Manual publication 1791DS UMO001 Add CIP Safety 1 0 Modules When you add a module to the system you must define a specific configuration for the module including e Node address You cannot set the node address of an CIP Safety I O module on DeviceNet networks via RSLogix 5000 software Module node addresses are set via rotary switches on the modules For information on how to set the node address refer to the DeviceNet Safety I O User Manual publication 1791DS UMO01 e Safety network number SNN I See page 51 for information on setting the SNN e Configuration signature See page 56 for information on when the configuration signature is set automatically and when you need to set it Publication 1756 UM020C EN P December 2006 50 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Co
79. ilure per Hour The probability of a system to have a dangerous failure occur per hour RPI Requested Packet Interval When communicating over a network this is the expected rate in time for production of data SNN Safety Network Number A unique number that identifies a section of a safety network SSV Set System Value A ladder logic instruction that sets controller system data Standard Any object task tag program or component in your project that is not a safety related item that is standard controller refers generically to a ControlLogix controller Publication 1756 UM020C EN P December 2006 12 Preface Publication 1756 UMO20C EN P December 2006 Introduction Safety Application Requirements Chapter 1 GuardLogix System Overview Topic Page Safety Application Requirements 13 Distinguish Between Standard and Safety Components 14 GuardLogix Data Flow Capabilities 16 Select GuardLogix System Hardware 17 Select Safety 1 0 19 Select Communication Networks 19 Programming Requirements 20 The GuardLogix controller system is certified for use in safety applications up to and including Safety Integrity Level SIL 3 and Category CAT 4 in which the de energized state is the safe state Safety application requirements include evaluating probability of failure rates PFD and PFH system reaction time settings and functional verification tests that fulfill SIL 3 criteria For SIL
80. ion Provides a list of the Safety Application instructions and the subset of standard ladder logic instructions that are approved for safety applications Also contains more information on developing safety applications GuardLogix Safety Application Instruction Set Reference Manual publication 1756 RM095 Provides detailed information on the safety application instructions Logix5000 General Instruction Set Reference Manual publication 1756 RM003 Provides details on the standard Logix instructions Publication 1756 UM020C EN P December 2006 22 Guardlogix System Overview Publication 1756 UMO20C EN P December 2006 Chapter 2 Configure the GuardLogix Controller Introduction Topic Page CreateaNewContoller 239 Set Passwords for Safety locking and unlocking 26 Handle 1 0 Module Replacement 27 Select the CST Master 27 Configure Project to Controller Matching 28 Configure a Peer Safety Controller 29 Create a New Controller To configure and program a GuardLogix controller use RSLogix 5000 software to create and manage a project for the controller 1 Create a new project in RSLogix 5000 software by clicking the New button on the main toolbar 2 Select a GuardLogix controller from the Type pull down menu e 1756 L61S ControlLogix 5561S Controller e 1756 L62S ControlLogix 5562S Controller New Controller x Vendor Allen Bradley Revision 16 Y Cancel R
81. ions 82 RSLogix Security 81 S safe failure fraction SFF 110 safe state 13 Index 123 safety network number 33 assignment 33 automatic assignment 35 changing controller SNN 36 changing I O SNN 37 copy and paste 38 copying and pasting 38 description 14 formats 33 managing 33 manual 34 manual assignment 35 modification 35 time based 34 safety partner configuration 18 LED indicators 97 safety projects features not supported 20 safety signature copy 82 delete 82 description 14 effect on download 90 effect on upload 90 generate 81 restricted operations 81 viewing 99 safety status effect on download 90 viewing 90 99 safety tab generate safety signature 81 safety lock controller 80 view safety status 90 safety tag mapping dialog 78 79 safety tags controller scoped 71 description 68 invalid data types 70 mapping 77 79 safety program scoped 71 safety task execution 67 safety lock 79 effect on download 90 effect on upload 90 icon 80 safety unlock icon 80 scheduled 44 Publication 1756 UM020C EN P December 2006 124 Index serial communications 48 network driver 87 serial port configuration 48 connections 86 set system value SSV accessibility 107 SNN See safety network number software restrictions 82 specifications environmental 111 general 110 subnet mask 42 T tags alias 69 base 69 class 72 consumed 69 Publication 1756 UM020C EN P December 2006 controller scoped 7
82. is mode is typically used to program the controller through its serial port DF1 Master Control of polling and message transmission between the master and slave nodes The master slave network includes one controller configured as the master node and as many as 254 slave nodes Link slave nodes using modems or line drivers A master slave network can have node numbers from 0 254 Each node must have a unique node address Also at least 2 nodes must exist to define your link as a network 1 master and 1 slave station are the two nodes DF1 Slave Using a controller as a slave station in a master slave serial communication network When there are multiple slave stations on the network link slave stations using modems or line drivers to the master When you have a single slave station on the network you do not need a modem to connect the slave station to the master You can configure the control parameters for no handshaking You can connect 2 255 nodes to a single link In DF1 slave mode a controller uses DF1 half duplex protocol One node is designated as the master and it controls who has access to the link All the other nodes are slave stations and must wait for permission from the master before transmitting DH 485 Publication 1756 UMO20C EN P December 2006 Communicating with other DH 485 devices multi master token passing network allowing programming and peer to peer messaging Chapter Add Conf
83. ision of the safety partner is not compatible with the primary controller Update the firmware revision of the safety partner Choose Update Firmware Choose the required revision and click Update Confirm your selection by clicking Yes Unable to download to controller Incompatible safety signature cannot be deleted while the project is safety locked Cancel the download To download the project you must e safety unlock the offline project delete the safety signature and then download the project IMPORTANT The safety system will require revalidation Cannot download in a manner that preserves safety signature Controller s firmware minor revision is not compatible with safety signature in offline project e f the firmware minor revision is incompatible to preserve the safety signature update the firmware revision in the controller to exactly match the offline project Then download the offline project e To proceed with the download despite the safety signature incompatibility click Download The safety signature will be deleted IMPORTANT The safety system will require revalidation Unable to download to controller Controller is locked Controller and offline project safety signatures do not match Choose Unlock The Safety Unlock for Download dialog appears If the Delete Signature checkbox is selected and you choose Unlock you must confirm the deletion by selecting Yes Following a succe
84. it Safety Task Period x Timeout Multiplier Network Delay Multiplier 1 The Connection Reaction Time Limit is shown on the Safety tab of the Module Properties dialog General Connection Safety Module Info Input Configuration Test Output Output Configuration Connection Requested Packet Max Observed Connection Reaction e Type Interval RPI ms Time Limit ms Network Delay ms Safety Input i Reset Advanced Safety Output 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 The RPI is entered in 1 ms increments with a valid range of 1 through 100 ms and a default of 10 ms The Connection Reaction Time Limit is adjusted immediately when the RPI is changed via RSLogix 5000 software General Connection Safety Module Info Input Configuration Test Output Output Configuration Connection Requested Packet Connection Reaction Max Observed c Type Interval RPI ms Time Limit ms Network Delay ms Safety Input Advanced 10 Safety Output Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 53 For safety output connections the RPI is fixed at the GuardLogix safety task period If the corre
85. itional Resources Resource Description Safety Connections on page 100 Provides more information on the CONNECTION_STATUS member Logix5000 Controllers Common Procedures Provides instructions for creating Programming Manual publication user defined data types 1756 PM001 Program scoped Tags When tags are program scoped the data is isolated from the other programs Reuse of program scoped tag names is permitted between programs Safety program scoped safety tags can only be read by or written to via a safety routine scoped in the same safety program Publication 1756 UM020C EN P December 2006 72 Develop Safety Applications Produced Consumed Safety Tags Publication 1756 UMO20C EN P December 2006 Class Tags can be classified as either standard or safety Tags classified as safety tags must have a valid data type and must be either controller scoped or safety program scoped When you create program scoped tags the class is automatically specified depending upon whether the tag was created in a standard or safety program When you create controller scoped tags you must manually select the tag class To transfer safety data between GuardLogix controllers you use produced and consumed safety tags Produced and consumed tags require connections that must be configured Produced and Consumed Connections Tag Connection Description Produced A produced safety tag lets GuardLogix controllers share safety d
86. ject has a safety signature and the Configure Always feature is disabled follow the procedure below to replace a module 1 Remove the old I O module and install the new module 2 Restore power to the system if it was removed during replacement The controller will recognize the replacement module and annunciate an out of box error 3 Go online to the controller using RSLogix 5000 software to set the safety network number SNN 4 Go to the General tab of the Module Properties dialog for the replaced module Publication 1756 UM020C EN P December 2006 62 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks 5 Click to the right of the safety network number to open the Safety Network Number dialog General Connection Safety Module Info Input Configuration Test Output Output Configuration Type 1781D5 IBEXDB8 A 8 Point 24VDC Sink Safety Input 8 Point 24 VDC Source Safety Output Vendor Allen Bradley Parent DNB local Name In out Node 1 hd Description Safety ud ip Reines o001 0000 270F EA zl DeviceNet 9999 6 Click Set x Eormat 8 25 2004 9 19 02 574 AM C Manual DeviceNet Decimal Number 2E95_0312_7A2E Hex Copy Paste The Set Safety Network Number in Module confirmation dialog appears 7 Verify that the Network Status NS LED indicator is alternating red green on the correct module before clicking Yes to set the SNN and accept the
87. l you can e download a free electronic version from the Internet at http literature rockwellautomation com e purchase a printed manual by contacting your local Allen Bradley distributor or Rockwell Automation sales office Conventions These conventions are used throughout this manual e Bulleted lists such as this one provide information not procedural steps e Numbered lists provide sequential steps or hierarchical information Bold type is used for emphasis Publication 1756 UMO20C EN P December 2006 Preface 11 Understanding Terminology The following table defines terms used in this manual Terms and Definitions Abbreviation Full Term Definition 1002 One Out of Two Refers to the behavioral design of a multi processor safety system CIP Common Industrial Protocol A communications protocol designed for industrial automation applications DC Diagnostic Coverage The ratio of the detected failure rate to the total failure rate EN European Norm The official European Standard GSV Get System Value A ladder logic instruction that retrieves specified controller status information and places it in a destination tag PC Personal Computer Computer used to interface with and control a Logix based system via RSLogix 5000 programming software PFD Probability of Failure on Demand The average probability of a system to fail to perform its design function on demand PFH Probability of Fa
88. le e Hardware incompatible e Firmware incompatible SafetySignatureExists Indicates whether the safety signature is 4 4 present SafetyTaskFaultRecord Records safety task faults 4 1 From the standard task GSV accessibility of safety object attributes is the same as for standard object attributes Publication 1756 UM020C EN P December 2006 108 Monitor Status and Handle Faults Publication 1756 UMO20C EN P December 2006 Introduction Certifications Appendix A Controller Specifications This appendix contains specification information for GuardLogix controllers Topic Page Certifications 109 General Specifications 10 Environmental Specifications 111 Environment and Enclosure Information 12 North American Hazardous Location Approval 113 When marked the components have the following certifications For UL CE and C Tick see the Product Certification link at http ab com certification safety for Declarations of Conformity Certificates and other certification details Certification Description UL UL Listed Industrial Control Equipment CSA CSA Certified Process Control Equipment CSA CSA Certified Process Control Equipment for Class Division 2 Group A B C D Hazardous Locations FM FM Approved Equipment for use in Class Division 2 Group A B C D Hazardous Locations CE European Union 89 336 EEC EMC Directive compliant with e EN 61000 6 4 Indus
89. les 1756 DNB PanelView Terminal A module gt P EN 1734 ACNR Adapter with to DeviceNet Network PLC 5 40C Controller EN 1734 0 Modules _ with CIP Safety 1 0 Publication 1756 UM020C EN P December 2006 46 Communicate Over Networks DeviceNet Communications Publication 1756 UMO20C EN P December 2006 Additional Resources Resource ControlNet Modules in Logix5000 Control Systems User Manual publication CNET UMO01 Description Contains information on how to configure a ControlNet communication module control I O over the ControlNet network send a message over the ControlNet network produce consume a tag over the ControlNet network calculate controller connections over the ControlNet network Logix5000 Controllers Design Considerations Reference Manual publication 1756 RM094 Provides guidelines on optimizing a control application on a ControlNet network To communicate and exchange data with CIP Safety I O modules 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 The 1756 DNB module supports communication with DeviceNet Safety devices and standard DeviceNet devices You can use both types DeviceNet Safety Connections To access CIP Safety devices on DeviceNet networks add a 1756 DNB to the I O Confi
90. leted You cannot schedule standard programs or execute standard routines within the safety task Safety Task Period Specification The safety task is a periodic timed task You select the task priority and watchdog time via the Task Properties Safety Task dialog Open the dialog by right clicking the Safety Task and choosing Properties IBI General Configuration Program Schedule Monitor Type Period o ms Priority fi 0 a Lower Number Yields Higher Priority Watchdog fi 0 000 ms Cancel Apply Help The safety task should be the controller s top priority You specify both the safety task period in ms and the safety task watchdog Gin 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 Develop Safety Applications 67 The safety task period is limited to a maximum of 100 ms and cannot J be modified online Be sure that the safety task has enough time to finish before it is triggered again Safety task watchdog timeout a nonrecoverable safety fault in the GuardLogix controller occurs if the safety task is triggered while it is still executing from the previous trigger The safety task period and safety task watchdog affect the system reaction time The GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 provides detailed information on calc
91. llows Input Network Delay Multiplier x Input RPI Safety Task Period EXAMPLE Calculate the Approximate Output Network Delay Multiplier If Input RPI 10 ms Input Network Delay Multiplier 200 Safety Task Period 20 ms Then the Output Network Delay Multiplier equals 200 x 10 20 100 Method 2 Use the Maximum Observed Network Delay If the system is run for an extended period of time through its worst case loading conditions the Network Delay Multiplier can be set from the Maximum Observed Network 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 The Network Delay Multiplier can be approximated by the following equation Maximum Observed Network Delay Margin_Factor RPI EXAMPLE Calculate the Network Delay Multiplier from Maximum Observed Network Delay If RPI 50 ms Maximum Observed Network Delay 20 ms Margin_Factor 10 Then the Network Delay Multiplier equals 20 10 50 60 Publication 1756 UM020C EN P December 2006 56 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Understand the I Configuration Signature Publication 1756 UM020C EN P December 2006 Additional Resources Resource Description GuardLogix Controller Systems Safety Reference Manual publication T 1756 RM0
92. m to maintain SIL 3 behavior during module replacement and functional testing the Configure Always feature may not be used Follow the I O Replacement with Configure Always Disabled procedure on page 61 If the entire routable CIP Safety Control System is not being relied on to maintain SIL 3 during the replacement and functional testing of a module the Configure Always feature may be used Follow the I O Replacement With Configure Always Enabled procedure on page 63 Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 61 TIP The Configure Always option is located on the Safety tab of the Controller Properties dialog The default setting is Configure Only When No Safety Signature Exists f Controller Properties SD safetycontroller q Ioj x General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced Fie Safety Memory Safety Application Unlocked Safety Lock Unlock Safety Status Safety Signature ID none Date When replacing Safety 1 0 Configure Only When No Safety Signature Exists C Configure Always OK Cancel Apply Help 1 0 Replacement with Configure Always Disabled If other parts of the CIP Safety Control Systems are being relied upon to maintain SIL 3 behavior during the replacement and functional testing of a module be sure that the Configure Always feature is disabled If the pro
93. nFaulted Modulename 0 Output Members Combination Modulename l RunMode 1 0 Modulename l ConnectionFaulted Modulename l Input Members Modulename 0 Output Members Publication 1756 UM020C EN P December 2006 58 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks E Monitor Safety 1 0 Module Status Publication 1756 UMO20C EN P December 2006 Additional Resources Resource Chapter 7 Monitor Status and Handle Faults Description Contains information on monitoring safety tag data Logix5000 Controllers Common Procedures Programming Manual publication 1756 PMO001 Provides information on addressing standard O modules You can monitor system status via the LED indicators on the I O modules and via input and output status codes Monitor via LED Indicators LED indicators on the safety I O modules indicate system status LED Indicator Operation LED Module Status MS Color State Description 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 Off Device is not online or may not have power Green On Device is online connections are established Green Flashing Device is online no connections established Network Status Red Flashing
94. nal Resources naaa an Genet p deti v ni dt 10 Conventions io e eoe X wo o b S eh 10 Understanding Terminology wes eR REESE 11 Chapter 1 ntroduction seu Redit o a t Ser ls eon RE Sede es 13 Safety Application Requirements llle 15 Safety Network Number seva ya eke EPA See ESSA 14 Safety BIBCD ITO s ed ang Ee Fato Udo Bib Ro IE Rote e 14 Distinguish Between Standard and Safety Components 14 HMI DEViCeS ace rara ee tC RI UR ETE PO UN VA 15 GuardLogix Data Flow Capabilities 16 Select GuardLogix System Hardware 4 17 Primary Conttoller aat v Lx a e DL NR Deed E OR 17 Safety Partner yiri spea a ed CE EXE Spee Be 18 CRASSI S a re at USE a nee aa aa e qur dara 18 Power Supply zu ds Roe s peek Ay E RAS 19 Select Safety IO os oss aubepru cca da oe Lo os OCA rad ea RR 19 Select Communication Networks 0 0 00005 19 Programming Requirements sad qe eco SY e Bee ee d 20 Chapter 2 Introduction s ace e IX KR aea oot e ee Ad d 23 Create a New Controller 5 ete ts wee ESWRCREu PET 23 Set Passwords for Safety locking and unlocking 26 Handle I O Module Replacement sna 27 Select the GST ASIE teii toa ted So EXEC DA ERAN 27 Configure Project to Controller Matching 28 Configure a Peer Safety Controllers 4 sete Yd PS ed 29 Chapter 3 THUFGCIURS OTI 9 olan Vania E PRO eR p S a ar DEAD eg 33 The Safety Network ebria eh RE CN EE EUIS 33 Manage the Safe
95. nfigure CIP Safety 1 0 Modules via RSLogix 5000 Software Publication 1756 UMO20C EN P December 2006 e Reaction time limit See page 52 or refer to the DeviceNet Safety I O User Manual publication 1791DS UMO001 for information on setting the reaction time limit e Safety input output and test parameters Refer to the DeviceNet Safety I O User Manual publication 1791DS UMO001 and to RSLogix 5000 online help for more information on configuring these parameters You can configure CIP Safety I O modules on DeviceNet networks via the GuardLogix controller using RSLogix 5000 software TIP Refer to the DeviceNet Safety 1 0 User Manual publication 1791DS UMO01 for details To communicate with a CIP Safety I O module in your system you add the module to the 1756 DNB under the I O Configuration folder of the RSLogix 5000 project TIP networks while online 1 Right click the DeviceNet network and choose New Module E MainProgram ES SafetyTask El C8 SafetyProgram Unscheduled Programs 6 6 Motion Groups Ungrouped Axes Trends a Data Types Ci User Defined E Cp Strings E Ep Predefined H E Module Defined E1 3 I O Configuration ControlBus 1756 410 fa 0 1756 L615 SD safetycontroller g 1 1756 LSP SD safetycontroller Partner BJ 2 1756 DNB DNB_local E rj E P New Module pussze es K3 Paste Ctrl 2 Expand the Safety category and choose a CIP Safety I O module S
96. nfigure the 1756 DNB e add the standard I O devices to the 1756 DNB scan list When you add the 1756 DNB module to the I O Configuration of the controller RSLogix 5000 software automatically creates a set of standard tags for the input output and status data of the network Additional Resources Resource Chapter 4 Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks Description Provides more information on DeviceNet Safety I O and addressing Safety 1 0 data DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 Contains detailed information on configuring and using the 1756 DNB ina Logix5000 control system Publication 1756 UMO20C EN P December 2006 48 Communicate Over Networks Serial Communications To operate the GuardLogix controller on a serial network you need a workstation with a serial port e RSLinx software to configure the serial communication driver e RSLogix 5000 software to configure the serial port of the controller For the controller to communicate to a workstation or other device over the serial network you must 1 Configure the serial communication driver for the workstation 2 Configure the serial port of the controller Serial Communication Modes Use this mode DF1 Point to point For Communication between the controller and one other DF1 protocol compatible device This is the default System mode Th
97. nter Password l ieaz Set Password Cancel Help 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 See page 26 Develop Safety Applications 81 In addition to the safety lock feature described in this section the standard RSLogix Security measures are also applicable to GuardLogix controller applications Refer to the Logix5000 Controllers Common Procedures Programming Manual publication 1756 PM001 for information on RSLogix 5000 Security features Generate a Safety Signature Before verification testing you must generate the safety signature You can generate the safety signature only when the GuardLogix controller is online in Program mode safety unlocked and has no safety forces pending online safety edits or safety faults The safety status must equal Safety Task OK TIP You can view the safety status via the safety status button on the online bar see page 99 or on the Safety tab of the Controller Properties dialog as shown on page 81 When a safety signature exists the following actions are not permitted in the safety portion of the application Online offline programming or editing Forcing Safety I O e Changing the inhibit state of safety I O or producer controllers e Data manipulation except by safety routine logic You can generate the safety signature
98. odules in Logix5000 Control Systems User Manual publication CNET UMOO1 Provides information on using the 1756 CN2 module RSLogix 5000 software version 14 and version 16 and later is the programming tool for GuardLogix controller applications RSLogix 5000 version 15 does not support Safety Integrity Level SIL 3 Programs scheduled under the safety task support only ladder logic TIP In RSLogix 5000 software version 14 programs scheduled under the safety task as well as programs in standard tasks support only ladder logic The RSLogix 5000 software version 16 safety task does not support the following items but they are supported in version 16 standard tasks within a GuardLogix project e Function block diagrams FBD e Sequential function chart SFC routines e Structured text e Integrated motion e Event tasks e Equipment phase routines e Add on instructions e Alarms and events Safety projects do not support redundancy Safety routines include safety instructions which are a subset of the standard ladder logic instruction set and safety application instructions GuardLogix System Overview 21 Refer to Chapter 5 of this manual and the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 for information on developing safety applications Additional Resources Resource GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 Descript
99. ogix 5000 online help for more information on CIP Safety I O module configuration f Set the Connection Reaction Time Limit using the Safety tab See page 52 for details The assignment of a time based SNN is automatic when adding new Safety I O modules Subsequent safety module additions to the same DeviceNet network are assigned the same SNN as the node with the lowest node address on that DeviceNet network The CIP Safety I O module SNN is set in the module the first time that an out of box module is connected to the system and prior to the safety signature being applied to the controller project Publication 1756 UM020C EN P December 2006 52 Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Set the Connection Reaction Time Limit Publication 1756 UMO20C EN P December 2006 For most applications the automatic time based SNN is sufficient However there are cases in which manipulation of an SNN is required See Assign the Safety Network Number SNN on page 34 The Connection Reaction Time Limit is the maximum age of safety packets on the associated connection If the age of the data used by the consuming device exceeds the Connection Reaction Time Limit a connection fault occurs The Connection Reaction Time Limit is determined by the following equations Input Connection Reaction Time Limit Input RPI x Timeout Multiplier Network Delay Multiplier Output Connection Reaction Time Lim
100. on to viewing controller safety status information on the safety status button on the online bar you can also find controller safety status information on the Safety tab of the Controller Properties dialog f Controller Properties SD safetycontroller E nl x General Serial Port System Protocol User Protocol Major Faults Minor Faults Date Time Advanced Fie Safety Memoy Safety Application Locked Safety Lock Unlock Safety Status SafetyTask OK The possible values for safety status are e safety partner is missing or unavailable e safety partner hardware is incompatible with primary controller e safety partner firmware is incompatible with the primary controller e safety task inoperable e safety task OK With the exception of safety task OK the descriptions indicate that nonrecoverable safety faults exist Publication 1756 UM020C EN P December 2006 102 Monitor Status and Handle Faults GuardLogix Controller Faults Publication 1756 UMO20C EN P December 2006 See Safety Faults on page 104 for fault codes and corrective actions The status of the safety partner can be viewed on the Connections tab of its Module Properties dialog imi Module Properties Local 1 1756 LSP 14 1 General Connection Module Info Backplane Requested Packet Interval RPI 0 ms I Inhibit Module Major Fault Gn Controller If Connection Fails w Use Scheduled Connection over ContralN
101. oning SIL 3 and CAT 4 safety applications refer to the GuardLogix Controller Systems Safety Reference Manual publication 1756 RM093 The Safety Reference Manual addresses creating a detailed project specification writing documenting and testing the application generating the safety signature to identify and protect the project confirming the project by printing or displaying the uploaded project and manually comparing the configurations safety data and safety program logic verifying the project through test cases simulations functional verification tests and an independent safety review if required e locking the safety application Publication 1756 UM020C EN P December 2006 66 Develop Safety Applications i The Safety Task Publication 1756 UM020C EN P December 2006 When you create a new safety controller project RSLogix 5000 software automatically creates a safety task with a safety program and a main safety routine 3 Controller SD_safetycontroller Controller Tags Controller Fault Handler C3 Power Up Handler B E Tasks a MainTask L8 MainProgram B SafetyTask E 3 SafetyProgram A Program Tags En MainRoutine L Uu eduied ograms Motion Groups Ungrouped Axes Trends Within the safety task you can use multiple safety programs composed of multiple safety routines The GuardLogix controller supports a single safety task The safety task cannot be de
102. onnection Reaction Time Limit 52 Specify the Requested Packet Interval RPD 52 Understand the Maximum Observed Network Delay 53 Set the Advanced Connection Reaction Time Limit P rameterS uae abt vox A oT UH Dore RU Edd 54 Additional Resout6es curet gud Vx mx prp reda 56 Understand the Configuration Signature 56 Configured via RSLogix 5000 Software 56 Different Configuration Owner Listen Only Connection 56 Reset Safety I O Module Ownership 57 Address Safety I O Data dA pic d aec oed e o e qd 57 Monitor Safety I O Module Status n o naaa aaaea 58 Monitor via LED Indicators oaaae 58 Monitor Input and Output Status Data 59 Replace a CIP Safety I O Module su beo ea 59 Prepare the I O Module n on aee ee OA Yet 59 I O Replacement with Configure Always Disabled 61 I O Replacement With Configure Always Enabled 63 Chapter 5 nit Pot fU OE ee ios ard A e e a E EA E edo 65 The Safety Vasko vixero fave toate eee Shes Aes PERS RES 66 Safety Task Period Specification 4 4 io es 66 Safety Task ExeOcutfOtks 22a Voie ee ei ERO E debo 67 Safety Prota Ss a dks DLE YS PSOE PER SONS Fae 68 Safety RUNES pre rd ns ori Yen ose ARE RO ER ee 68 Go Online with the Controller Monitor Status and Handle Faults Table of Contents 7 Saf ty Tags dea ee oe ee S PACER Se Bh OUE CAE S OSTRE AER 68 i Mb CT 69 Data Types o ac de eoe C e ot teo ei
103. ontroller automatically checks for and accepts a replacement module that meets all of the following requirements e The controller has configuration data for a compatible module at that network address e The module is in out of box condition When a safety signature exists and the Configure Always feature is enabled follow the procedure below to replace an I O module 1 Remove the old I O module and install the new module The controller will recognize accept and configure the replacement module 2 Follow your company prescribed procedures to functionally test the replaced I O module and system and to authorize the system for use Publication 1756 UM020C EN P December 2006 64 X Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Publication 1756 UMO20C EN P December 2006 Chapter 5 Develop Safety Applications Introduction This chapter explains the components that make up a safety project including the safety task safety programs safety routines and safety tags It also provides information on using features that help protect safety application integrity such as the safety signature and safety locking Topic Page TheSafetyTask 6 Safety Programs 68 Safety Routines 68 Safety Tags 68 Produced Consumed Safety Tags 72 Safety Tag Mapping 77 Safety Application Protection 79 Software Restrictions 82 For guidelines and requirements for developing and commissi
104. ous Secure any external connections that mate to this equipment by using screws sliding latches threaded connectors or other means provided with this product e Substitution of components may impair suitability for Class Division 2 e f this product contains batteries they must be changed only in an area known to be nonhazardous Publication 1756 UM020C EN P December 2006 114 Controller Specifications Publication 1756 UMO20C EN P December 2006 Appendix B Maintain the Battery Introduction This chapter provides information on the 1756 BA2 battery Topic Page Estimate Battery Life 115 When to Replace the Battery 116 Replace the Battery 117 Store Replacement Batteries 118 Estimate Battery Life Battery life is dependent upon chassis temperature project size and how often you cycle power to the controller Battery life is not dependent upon whether or not the controller has power Before BAT LED Indicator Turns On Use the Battery LED Indicator Worst Case Time table to estimate the worst case time before the BAT LED indicator turns red Battery LED Indicator Worst Case Time Max Temperature 1 in Power Cycles Project Size Below Chassis per Day 1MB 2 MB 4MB 3 3 years 3 years 26 months 0 40 C 32 104 F y x 2 or fewer 3 years 3 years 3 years 3 2 years 2 years 2 years 41 45 C 105 113 F T Y 2 or fewer 2 years 2 years 2 years 46 50 C 114 122 F
105. pe b i valP z mypcType E valP status zn NET CONNECTION STATUS alP status RunMode New Tag which aliases valP BOOL alP status ConnectionFaulec Edit valP Properties Alt Enter BOOL valP data Edit mypcType Data Type DINT 2 Go to Cross Reference for valP Ctrl E Message Path Editor Go To Ctr G cu Ctrl X Copy Ctrl c gi Paste Ctr v Paste Pass Through Delete Del Options 4 X Monitor Tags A Edit Tags 4 In the Tag Properties dialog click Connection to open the Produced Tag Connection dialog Enter the number of controllers that will consume receive the data Tag Properties valP p General Name vaP ees S TV Include Connection Status ype Produced Connection Iv Send Data State Change Event To Consumers Data Type mpcT ype Hj Scope g producer Class Safety X w or Cancel Apply Help Click OK Destin z Connection E Max Consumers b Publication 1756 UM020C EN P December 2006 74 Develop Safety Applications Consume Safety Tag Data Follow these steps to consume data produced by another controller Producer Module Properties Dialog in Consumer Project imi Module Properties Local 8 1756 L62S 14 31 E General Connection Module Info Backplane 1 Open the GuardLogix project that will consume the data 2 Add the controller producing the data to the I O Configuration folder 3
106. pplications Publication 1756 UMO20C EN P December 2006 Chapter 6 Go Online with the Controller Introduction EM Topic Page Connect the Controller tothe Network 85 Configure the Network Driver 87 Understand the Factors that Affect Going Online 88 Download 92 Upload 93 Go Online 95 Connect the Controller to If you iE not already done so connect the controller to the the Network Neun Network Connections For This Network Connect the Controller via a Serial 1756 CP3 or 1747 CP3 cable EtherNet IP 1756 ENBT module in an open slot in the same chassis as the controller DeviceNet 1756 DNB module in an open slot in the same chassis as the controller ControlNet 1756 CN2 module in an open slot in the same chassis as the controller to bridge to safety 1 0 1756 CNB module in an open slot in the same chassis as the controller to bridge to standard 1 0 Publication 1756 UM020C EN P December 2006 86 Go Online with the Controller 1756 ENBT 1756 ENBT Publication 1756 UMO20C EN P December 2006 Connect the Controller via a Serial Network The 1756 CP3 cable attaches the serial port of the workstation directly to the controller TIP If you make your own cable e limit the length to 15 2 m 50 fb e wire the connectors as shown below e attach the shield to both connectors
107. r match is selected e Firmware major and minor revisions e Safety status between the primary controller and safety partner e Safety signature Gif one exists e Safety lock status Publication 1756 UMO20C EN P December 2006 Go Online with the Controller 93 5 Follow the directions in this table to complete the download based on the software s response If the software indicates Download to the controller Then Choose Download The project downloads to the controller and RSLogix 5000 software 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 Connect to the correct controller or verify that this is the correct controller If it is the correct controller select the Update project serial number checkbox to allow the download to proceed The project serial number will be modified to match the controller serial number Unable to download to the controller The major revision of the offline project and the controller s firmware are not compatible Choose Update Firmware Choose the required revision and click Update Confirm your selection by clicking Yes Unable to download to controller The safety partner is missing or unavailable Cancel the download process Install a compatible safety partner before attempting to download Unable to download to controller The firmware rev
108. received or transmitted Not applicable SAFETY Off Not applicable No partnership established Primary controller is TASK missing is not functioning properly or its firmware revision is incompatible with that of the safety partner Green Not applicable Safety controller status is OK The coordinated system time CST is synchronized and 1 0 connections are established Green Flashing Not applicable Safety controller status is OK The coordinated system time CST is not synchronized on either the primary controller or the safety partner Red Not applicable Partnership was lost and a new partnership has not been established primary controller is missing is not functioning properly or its firmware revision is incompatible with that of the safety partner Red Flashing Not applicable 1 1 0 includes produced consumed tags from other controllers Publication 1756 UMO20C EN P December 2006 Safety controller status is Inoperable Monitor Status and Handle Faults 99 Online Bar The online bar displays project and controller information including the controller s status force status online edit status and safety status as shown below Controller Status Button Offline f E RUN Force Status Button Wse No Forces p_ F OK E BAT Online Edit Button a NoEdis A i Safety Status Button gm Safety Unlocked 39 o When the Controller Status button is selecte
109. replacement module Set Safety Network Number in Module DANGER Setting Safety Network Number in module Network status indicator on module s front panel is alternating red and green to help validate module addressing If two or more controllers are attempting to configure module setting Safety Network Number will result in configuration ownership being granted to First controller that successfully configures module If two or more controllers are attempting to connect to outputs of module setting Safety Network Number will result in output ownership being granted to first controller that successfully connects to outputs Set Safety Network Number 8 Follow your company prescribed procedures to functionally test the replaced I O module and system and to authorize the system for use Publication 1756 UMO20C EN P December 2006 Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 63 1 0 Replacement With Configure Always Enabled 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 module Do not place any modules that are in the out of box condition on any CIP Safety network when the Configure Always feature is enabled except while following the module replacement procedure using Configure Always When the Configure Always feature is enabled in RSLogix 5000 software the c
110. rials You are legally responsible for hazards created during disposal of your battery A battery may leak potentially dangerous chemicals if stored improperly Store batteries in a cool dry environment We recommend 25 C 77 F with 40 60 relative humidity You may store batteries for up to 30 days at temperatures between 45 85 C 49 185 F such as during transportation To avoid possible leakage do not store batteries above 60 C 140 F for more than 30 days Description Provides more information on handling storing and disposing of lithium batteries Introduction From Standard to Safety Appendix C Change Controllers Topic Page From Standard to Safety 119 From Safety to Standard 120 Because safety controllers have special requirements and do not support certain standard features you must understand the behavior of the system when changing controllers from standard to safety or safety to standard Changing controller type affects e supported features physical configuration of the project that is the safety partner and safety I O e controller properties e project components such as tasks programs routines and tags In order to successfully change from a standard controller to a safety controller the chassis slot immediately to the right of the safety primary controller must be available for the safety partner Upon confirmation of a change from a standard controller to a safe
111. ription Chapter 5 Develop Safety Applications Contains more information on the safety task period and on configuring produced consumed tags Safety Connections on page 100 Provides more information on the CONNECTION STATUS data type Logix5000 Controllers Common Procedures Contains more information on producing Programming Manual publication and consuming tags and on creating 1756 PM001 user defined data types Publication 1756 UM020C EN P December 2006 32 Configure the GuardLogix Controller Publication 1756 UMO20C EN P December 2006 Chapter J Communicate Over Networks Introduction Topic Page The Safety Network 33 EtherNet IP Communications 39 ControlNet Communications 43 DeviceNet Communications 46 Serial Communications 48 The Safety Network 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 To maintain high integrity when routing through standard bridges switches or routers each end node within a routable CIP Safety Control System must have a unique reference This unique reference is a combination of a safety network number SNN and the node address of the network device Manage the Safety Network Number SNN The SNN assigned to safety devices on a network segment must be unique You must be sure that a unique SNN is assigned to e all safety devices on ea
112. rolNet Network You indirectly determine the number of connections the controller uses by configuring the controller to communicate with other devices in the system Connections are allocations of resources that provide more reliable communications between devices compared to unconnected messages ControlNet connections can be either scheduled or unscheduled Description A scheduled connection is unique to ControlNet communications A scheduled connection lets you send and receive data repeatedly at a predetermined interval which is the requested packet interval RPI For example a connection to an 1 0 module is a scheduled connection because you repeatedly receive data from the module at a specified interval Other scheduled connections include connections to e communication devices e produced consumed tags On a ControlNet network you must use RSNetWorx for ControlNet software to enable all scheduled connections and establish a network update time NUT Scheduling a connection reserves network bandwidth to specifically handle the connection Unscheduled Publication 1756 UMO20C EN P December 2006 An unscheduled connection is a message transfer between controllers that is triggered by the requested packet interval RPI or the program such as a MSG instruction Unscheduled messaging lets you send and receive data when needed Unscheduled connections use the remainder of network bandwidth after scheduled connections are
113. roperties dialog displays the current configuration ownership When the opened 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 Communication error is displayed if the module read fails When online you can reset the module to its out of box configuration by clicking Reset Ownership Reset Ownership e TIP You cannot reset ownership when there are pending edits to the module properties when a safety signature exists or when safety locked Configuration Ownership Local When you add a module to the I O configuration folder RSLogix 5000 software automatically creates controller scoped tags for the module I O information is presented as a set of tags Each tag uses a structure of data depending on the type and features of the I O module The name of a tag is based on its name in the system A CIP Safety I O device on a DeviceNet network follows this format Modulename Type Member CIP Safety 1 0 Module Address Format Where Is Modulename The name of the CIP Safety 1 0 module Type Type of data Input Module Output Module O Member Specific data from the I O module Input only Modulename l RunMode Module Modulename l ConnectionFaulted Modulename l Input Members Output only Modulename l RunMode Module Modulename l Connectio
114. s 101 consumed tag description 69 72 control and information protocol Definition 11 controller configuration 23 fault handler 105 match 89 controller properties dialog date time tab 28 general tab 25 major faults tab 90 103 104 safety tab 80 81 90 controller scoped tags 71 ControlNet connection use 44 example configuration 45 overview 43 scheduled 44 unscheduled 44 ControlNet module capabilities 44 coordinated system time 27 create a new project 23 CSA 109 CST See Coordinated System Time C Tick 109 Publication 1756 UM020C EN P December 2006 122 Index D Date Time tab 28 DeviceNet network configure driver 87 88 connections 47 87 DF1 48 DH 485 48 diagnostic coverage Definition 11 download effect of controller match 89 effect of firmware revision match 89 effect of safety signature 90 91 effect of safety status 90 effect of safety lock 90 91 process 92 93 E enclosure 112 environment 112 EtherNet IP connection use 40 example configuration 40 module capability 39 overview 39 EtherNet IP modules configuration parameters 42 EtherNet IP network configure driver 87 88 connections 86 parameters 42 European norm Definition 11 fault codes 104 non recoverable controller faults 102 non recoverable safety 102 recoverable fault 103 routines 105 107 firmware revision match 89 FM 109 G gateway 42 get system value GSV accessibility 107 definition 11 Publication 1756 U
115. s that 1 message may be lost as long as at least 1 message is received in 2 times the RPI 2 x RPD 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 You can use the Network Delay Multiplier to reduce or increase the Connection Reaction Time Limit in cases where the enforced message transport time is significantly less or more than the RPI For example adjusting the Network Delay Multiplier may be helpful when the RPI of an output connection is the same as a lengthy safety task period For cases where the input RPI or output RPI are relatively slow or fast as compared to the enforced message delay time the Network Delay Multiplier can be approximated using one of the two methods Add Configure Monitor and Replace CIP Safety I O on DeviceNet Networks 55 Method 1 Use the ratio between the input RPI and the safety task period Use this method only under the following conditions e if the path or delay is approximately equal to the output path or delay and e the input RPI has been configured so that the actual input message transport time is less than the input RPI and e the safety task period is slow relative to the Input RPI Under these conditions the Output Network Delay Multiplier can be approximated as fo
116. sponding Connection Time Reaction Limit is not satisfactory you can adjust the safety task period via the Safety Task Properties dialog See Safety Task Period Specification on page 66 for more information on the safety task period For simple timing constraints setting the RPI is usually sufficient For more complex requirements use the Advanced button to set the Connection Reaction Time Limit parameters as described on page 54 Understand the Maximum Observed Network Delay When the GuardLogix controller receives a safety packet the software records the maximum observed transport delay The Maximum Observed Network Delay specifies the round trip delay from the producer to the consumer and the acknowledge back to the producer This Maximum Observed Network Delay value is the result of capturing the age of the data upon the arrival of the message The Maximum Observed Network Delay is shown on the Safety tab of the Module Properties dialog When online you can reset the Maximum Observed Network Delay by clicking Reset General Connection Safety Module Info Input Configuration Test Output Output Configuration Max Observed Network Delay ms Connection Requested Packet Connection Reaction Interval RPI ms Time Limit ms Safety Input Safety Output IMPORTANT The actual Maximum Network Delay time from the producer to the consumer will always be less than the value displayed in the
117. ssful download the safety locked status and safety signature of the controller match the project that was downloaded Safety data is initialized to the values that existed when the safety signature was created Upload project Project M Upload transfer a project from a controller 4 d to your computer so you can monitor the E Upload GuardLogix Controller Publication 1756 UMO20C EN P December 2006 94 Go Online with the Controller Publication 1756 UMO20C EN P December 2006 Define the path to the controller a Click Who Active i 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 Click Upload If the project file does not already exist create the project file on your computer by choosing Select File then Select and Yes If the project file exists select it If the project to controller match is enabled RSLogix 5000 software 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 e Cancel the upload and connect to a matching controller Then start the upload procedure again e Select a new project to upload into or select a different project by choosing Select File Update the project serial number to match the controller by checking the Update Project Serial Num
118. supports redundant ControlNet media 1756 CNBR performs the same functions supported by the 1756 CNB module with higher performance supports CIP Safety communication 1756 CN2 In addition to communication hardware for ControlNet networks these software products are available Software for ControlNet Modules Software Purpose RSLogix 5000 Programming This software is required to configure the GuardLogix Software project and define ControlNet communications RSNetWorx for ControlNet This software is required to configure the ControlNet Software network define the network update time NUT and schedule the ControlNet network Publication 1756 UMO20C EN P December 2006 44 Communicate Over Networks ControlNet Connections Connection Type Scheduled unique to the ControlNet network The ControlNet communications modules e support messaging produced consumed safety and standard tags and distributed I O e support the use of coax and fiber repeaters for isolation and increased distance Produce and Consume Data via the ControlNet Network The GuardLogix controller supports the ability to produce broadcast and consume receive system shared tags over the ControlNet network Produced and consumed tags each require connections The total number of tags that can be produced or consumed is limited by the number of available connections in the GuardLogix controller Connections Over the Cont
119. te doses 70 SCODE 4A ped Xu PX P rA WEIOXG Qd X Pen eee EDL E 88 70 MU CONTRE KETTE RUNE E 72 Produeed Consumed Safety T3855 e iu su d aea dE Se soe 72 Produce a Safety Tag ounri acuto aiay EE E E h 73 Consume Safety Tag Data onana a aaa 74 Additional Resources s 2 uod 0e UE I mee Eo Re 77 Safety Tag Mapping ui pd eed E ER D Oe ERR ds 77 RESICHONS 4 ater us 9 uo p Bale e GA Wo x PY I Create Tag Mapping Pairs 444 nu aoe 6 04 60 boos 78 Monitor Tag Mapping Status 04 79 Safety Application Protection en dy OE ee OR ee 79 Satety lock the Controller re LE pene ERR ned 79 Generate a Safety Signature cs qu cte e d RC rd 81 Software Restrictions watt a doin ydo oss NP as bot 82 Chapter 6 Introduction vacas Corte eu PECES MOORE RR SEEN SUE Bees 85 Connect the Controller to the Network 85 Connect the Controller via a Serial Network 86 Connect Your EtherNet IP Device and Computer 86 Connect Your DeviceNet Scanner or ControlNet Communication Module and Your Computer 87 Configure the Network DAVer volg do ate RIES BYERS 87 Configure a Serial Communications Driver 87 Configure an EtherNet IP DeviceNet or ControlNet Diver orr ida oio taa eod to ce loe tee os e etd 88 Understand the Factors that Affect Going Online 88 Project to Controller Matching Soy eer bet 89 Firmware Revision Matching lll sss 89 Safety Partner 5tatus Eaulis 4
120. ted controller operation or injury to personnel Monitor Status and Handle Faults 107 GSV SSV Accessibility z XT Accessible from Accessible from Safety Object Attribute Name Attribute Description the Safety Task Standard Tasks GSV SSV esv SSV Instance Provides instance number of this task object V 4 Valid values are 0 31 Maximumlnterval The max time interval between successive V V executions of this task MaximumScanTime Max recorded execution time ms for this 4 4 task Minimumlnterval The min time interval between successive V 4 Safety Task executions of this task Priority Relative priority of this task as compared to V V other tasks Valid values are 0 15 Rate Period for the task in ms or timeout value 4 4 for the task in ms Watchdog Time limit in ms for execution of all 4 4 programs associated with this task Instance Provides the instance number of the program V 4 object Safety Program MajorFaultRecord Records major faults for this program V V V MaximumScanTime Max recorded execution time ms for this 4 4 program Safety Routine Instance Provides the instance number for this routine v y object Valid values are 0 65 535 SafetyLocked Indicates whether the controller is 4 safety locked or unlocked SafetyStatus Specifies the safety status as V e Safety task OK e Safety task inoperable Safety e Partner missing Controller e Partner unavailab
121. trial Emissions e EN 50082 2 Industrial Immunity e EN 61326 Meas Control Lab Industrial Requirements e EN 61000 6 2 Industrial Immunity C Tick Australian Radiocommunications Act compliant with AS NZS CISPR 11 Industrial Emissions TUV Functional Safety SIL 1 to 3 according to IEC 61508 Category 1 to 4 according to EN954 1 Publication 1756 UM020C EN P December 2006 110 Controller Specifications General Specifications Safety Specifications Publication 1756 UMO20C EN P December 2006 The following products are certified for UL NRGF Catalog Number Description 1756 L61S Primary controller with 2 MB memory 1756 L62S Primary controller with 4 MB memory 1756 LSP Safety partner For the current list of GuardLogix series and operating system revisions certified for UL NRGF see http ab com certification safety Catalog Number 1756 L61S 1756 L62S 1756 LSP Memory Standard Task 2 MB 4 MB N A Memory Safety Task 1 MB 1 MB 1 MB Backplane Current at 5V dc 1 20A 1 20A 1 20A Backplane Current at 24V dc 14 mA 14 mA 14 mA Power Dissipation 3 5 W 3 5 W 3 5 W Thermal Dissipation 11 9 BTU hr 11 9 BTU hr 11 9 BTU hr Weight 0 32 kg 11 3 0z 0 32 kg 11 3 oz 0 32 kg 11 3 oz Functional Probability of Probability of Safe Failure Verification Failure on Demand Failure per Hour Fraction SFF Test Interval PFD PFH 15 years 8 5E 06 1 9E 10 99 1 10 years 5
122. troller s project as shown on the producer controller s Controller Properties dialog Producer Controller Properties Dialog in Consumer Project Producer Controller Properties in Producer Project General Connection Module Info Backplane Minor Faults Date Time Advanced File Safety Memoy Type 1756 625 ControlLogixS5625 Safety Controller General Serial Port System Protocol l User Protocol l Major Faults Vendor Allen Bradley Vendor Allen Bradley rs Name Producer Slot s Type 1756 625 Control ogix5562S Safety Controller Change Controller aT Safety Network 5i Description reus EEE 03B8 912D Revision 1431 11 22 2004 11 20 27 437 AM Name producer Description Chassis Type 1756 A10 10 Slot ControlLoaix Chassis Slot Safety Network Mp 2EEE 03B8 312D E 11 22 2004 11 20 27 437 AM Cancel ply Help Publication 1756 UM020C EN P December 2006 30 Configure the GuardLogix Controller TIP An SNN can be copied and pasted using the buttons on the Safety Network Number dialog Open the respective Safety Network Number dialogs by clicking to the right of the SNN fields in the properties dialogs Safety Network Number 1 x Format Time based Generate 11 22 2004 11 20 27 437 AM C Manual 1756 Backplane Decimal Number 2EEE_03B8_912D Hex Copy Paste Cancel Hep For produced and consumed safety ta
123. ty controller safety components are created to meet the minimum requirements for a safety controller The safety task is created only if the maximum number of downloadable tasks has not been reached The safety task is initialized with its default values e Safety components are created that is safety task safety program and so forth e A time based safety network number SNN is generated for the local chassis e Any standard controller features such as redundancy which are not supported by the safety controller are removed from the Controller Properties dialog Publication 1756 UM020C EN P December 2006 120 Change Controllers From Safety to Standard Publication 1756 UMO20C EN P December 2006 Upon confirmation of a change from a safety controller to a standard controller some components are changed and others are deleted as described below e The safety partner 1756 LSP is deleted from the I O chassis e Safety I O modules and their tags are deleted The safety task programs and routines are changed to a standard task programs and routines e All safety tags except safety consume tags are changed to standard tags Safety consume tags are deleted e Safety tag mappings are deleted e The safety network number SNN is deleted e Safety lock and unlock passwords are deleted e If the standard controller supports features that were not available to the safety controller such as nonvolatile stor
124. ty Network Number SNN 33 Assign the Safety Network Number SNN aaa 34 Change the Safety Network Number SNN 35 EtherNet IP Communications llle 39 Produce and Consume Data via the EtherNet IP Network 40 Connections Over the EtherNet IP Network 40 EtherNet IP Communication Example 40 EtherNet IP Modules in a GuardLogix System 41 Publication 1756 UM020C EN P December 2006 6 Table of Contents Add Configure Monitor and Replace CIP Safety 1 0 on DeviceNet Networks Develop Safety Applications Publication 1756 UMO20C EN P December 2006 Additional Resources e094 Eek PR eS eee EES EX 43 ContralNet Communications ewes ie Toe dee Rd 43 Produce and Consume Data via the ControlNet Network 44 Connections Over the ControlNet Network 44 ControlNet Communication Example 45 Additional Resources scoop utes 46 DeviceNet Communications 0 00000 eee 46 DeviceNet Safety Connections 253 y ene perse 46 Standard DeviceNet Connections 47 Additional Resources iz yx ee ba eee abe eA Se A 47 Serial Communications o o ewe te RO EHI VE RE weak 48 Chapter 4 Introduction oer dodeoxE hi eh ooi Eod Roo Ere ath x Reha Des dod 49 Add CIP Safety I O Modules 4 io ser pein SEP 49 Configure CIP Safety I O Modules via RSLogix 5000 Software 50 Set the Safety Network Number SNN 0 00048 51 Set the C
125. ulating system reaction time Safety Task Execution The safety task executes in the same manner as a standard periodic task with the following exceptions e The safety task does not begin executing until the primary controller and safety partner have established their control partnership and the coordinated system time CST is synchronized However standard tasks begin executing as soon as the controller transitions to Run mode e Safety input tags and safety consumed tags are updated at the beginning of safety task execution e Safety input values are updated and then frozen at the start of each safety task execution e For standard tags that are mapped to safety tags the standard tag values are copied into safety memory at the start of safety task execution See page 77 for information on safety tag mapping e Safety produced tags are produced at the conclusion of safety task execution e Safety output tag values are sent to safety outputs at the conclusion of safety task execution Publication 1756 UM020C EN P December 2006 68 Develop Safety Applications Safety Programs Safety Routines Safety Tags Publication 1756 UMO20C EN P December 2006 Safety programs have all the attributes of standard programs except that they can only be scheduled in the safety task and can only contain safety components Safety programs can only contain safety routines one of which must be designated as the main routine
126. ups Ungrouped Axes Trends amp Data Types ER User Defined H E Strings E m Predefined H E Module Defined E1 3 I O Configuration ControlBus 1756 A10 fs 0 1756 L615 SD safetycontroller g 1 1756 LSP SD safetycontroller Partner Safety Fault A red bar under the folder icon distinguishes safety components from standard components in the RSLogix 5000 Controller Organizer Configure the GuardLogix Controller 25 When a new safety project is created RSLogix 5000 software also automatically creates a time based safety network number SNN This SNN defines the local chassis backplane as a safety subnet It can Jj be viewed and modified via the General tab on the Controller Properties dialog For most applications this automatic time based SNN is sufficient However there are cases in which you might want to enter a specific I SNN Safety Network Number f amp Controller Properties SD safetycontroller iof xj Minor Faults Date Time Advanced SFC Execution File Safety Memory General Serial Port System Protocol User Protocol Major Faults Vendor Allen Bradley Type 1756 L61S ControlLogix5561S Safety Controller Revision 16 1 Name SD_safeycontioley CS Description ig Chassis Type 1756410 10 Slot ControlLogix Chasss m Slot Safety Network Nunber IE 35 0434 A894 5 28 2006 2 35 59 898 PM Cancel Appl Help TI
127. usually a GuardLogix controller or another ControlLogix controller IMPORTANT Ifa CST master does not exist a nonrecoverable safety fault will occur when the controller is put into Run mode See GuardLogix Controller Faults on page 102 for more information on faults 1 The safety signature is a number used by the GuardLogix system to uniquely identify each project s logic data and configuration thereby protecting the system s safety integrity level SIL See Safety Signature on page 14 and Generate a Safety Signature on page 81 for more information Publication 1756 UMO20C EN P December 2006 28 Configure the GuardLogix Controller E Configure Project to Controller Matching Publication 1756 UMO20C EN P December 2006 You can set the controller as the CST master using the Date Time tab on the Controller Properties dialog Controller Properties SD safetycontroller T Adjust for Daviioht Saving 0000 e When online this tab also indicates whether the controller is synchronized with a CST master RSLogix 5000 software version 14 and later lets you link your project to a specific controller for the purposes of going online downloading and uploading If you enable this option each time you initiate one of these activities RSLogix 5000 software checks that the serial number configured in the project matches the serial number of the controller to which it is connected To enable this feature check t
128. w RSLogix 5000 software to automatically assign an SNN or you can assign the SNN manually Communicate Over Networks 35 Automatic Assignment When a new controller or module is created a time based SNN is automatically assigned via the configuration software Subsequent new safety module additions to the same CIP Safety network are assigned the same SNN defined within the lowest node address on that CIP Safety network Manual Assignment The manual option is intended for routable CIP Safety systems where the number of DeviceNet subnets and interconnecting networks is small and where users might like to manage and assign the SNN in a logical manner pertaining to their specific application See Change the Safety Network Number SNN on page 35 IMPORTANT If you assign an SNN manually take care to ensure that system expansion does not result in duplication of SNN and node address combinations Automatic Versus Manual For typical users the automatic assignment of an SNN is sufficient However manual manipulation of the SNN is required e if safety consumed tags are used e if the project will consume safety input data from a module whose configuration is owned by some other device e if a safety project is copied to a different hardware installation within the same routable CIP Safety system Change the Safety Network Number SNN Before changing the SNN you must e unlock the project if it is safety locked See
129. works The 1756 DNB DeviceNet module provides the interface between the GuardLogix controller and DeviceNet devices distribute and control remote safety I O on DeviceNet networks via Ethernet or ControlNet networks produce and consume safety tag data between GuardLogix controllers across an Ethernet IP or ControlNet network or within the same ControlLogix chassis 1756 ENBT modules provide a communication bridge between controllers on the EtherNet IP network 1756 CN2 modules provide a communication bridge between controllers on the ControlNet network access RSLogix 5000 programming software via a serial connection or an 1756 ENBT module or 1756 CNB module e support standard ControlNet communications Publication 1756 UM020C EN P December 2006 20 GuardLogix System Overview Programming Requirements Publication 1756 UMO20C EN P December 2006 Additional Resources Resource DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 Description Contains information on configuring a DeviceNet network communicating with devices over the DeviceNet network troubleshooting and optimizing network performance EtherNet IP Modules in Logix5000 Control Systems User Manual publication ENET UMO01 Contains information on configuring the 1756 ENBT module interlocking and data transfer between controllers on the EtherNet IP network managing connections and diagnostics ControlNet M
130. y The standard application is downloaded and the safety application is reinitialized via the safety signature Safety tags are reinitialized to the values they had when the safety signature was created The safety task is not downloaded Safety signatures do not match If the controller had a safety signature it is automatically deleted The entire project is downloaded If the offline project has a safety signature but the controller does not the entire project is downloaded to the controller Safety signature status is irrelevant Either e RSLogix 5000 software prompts you to flash the controller so that it matches the offline project Once the update is completed the entire project is downloaded Or e Upgrade the project to the controller version IMPORTANT This causes the safety signature to be deleted and the system will require revalidation Controller safety locked Safety signature in the offline project matches the safety signature in the controller If the offline project is safety locked the standard application is downloaded and the safety task is reinitialized If the offline project is not safety locked the download is blocked and you must first unlock the controller to allow the download to proceed i Firmware in the controller is different than in the offline project Safety signatures do not match or either the controller or the offline project does not have a safety signature
131. yping the tag name into the cell Right click in the cell and choose New tagname where tagname is the text you entered in the cell Develop Safety Applications 79 Monitor Tag Mapping Status The left most column of the Safety Tag Mapping dialog indicates the status of the mapped pair Tag Mapping Status Icons Cell Contents Description Empty Tag mapping is valid x When offline the X icon indicates that tag mapping is invalid You can move to another row or close the Safety Tag Mapping dialog When online an invalid tag map results in an error message explaining why the mapping is invalid You cannot move to a different row or close the Safety Tag Mapping dialog if a tag mapping error exists Indicates the row that currently has the focus E Represents the Create New Mapped Tag row z Represents a pending edit 1 Tag mapping is also checked during project verification Invalid tag mapping results in a project verification error For more information see the tag mapping restrictions on page 77 Safety Application Safety lock the Controller Protection The GuardLogix controller system can be Safety locked to protect safety related control components from modification The Safety lock feature applies only to safety components such as the safety task safety programs safety routines safety tags Safety I O or safety signature Publication 1756 UM020C EN P December 2006 80 Dev

Download Pdf Manuals

Related Search

Related Contents

Notice utilisateur  Gebrauchsanweisung  mini screen.ita.fm - Banner Engineering    10607 AE Env  Sonicare For Kids rechargeable sonic toothbrush  specifications-442  キット 取扱説明書 - スペシャルパーツ武川  

Copyright © All rights reserved. Failed to retrieve file