Home

1753-UM002A-EN-P, DeviceNet Safety Scanner for

1. Bownload to Device Glass Instance Editor Re register Device 1738 AC 1738 AD 1738 AD Import Target Connections 1738 AD Export Scanner Signals 1738 4D 1738 4D 1738 AD Properties 1738 4 Export I O Details 2 Select Time based and click the Generate button or select Manual and fill in a Decimal number from 1 to 9999 Click OK Set Safety Network Number 00 1753 DNSI Desie Format Generate o 10 25 2004 9 59 01 7 41 AM Manual DeviceNet Decimal Number 2ED2_0337_15ED Hex Copy Paste ox Cae f Hep TIP You can use the copy and paste buttons on the Set Safety Network Number dialog to copy and paste SNNs between devices and to make a record of the SNN 3 Verify that the Network Status LED is rapidly alternating between red and green on the correct device and click OK Confirm Safety Network Number 00 1791DS IB4X0W4 4PE 4PE Sad The network status LED is flashing on the device address 00 in which the Safety Network Number will be set Click OK to set the Safety Network Number in the device Cancel Manage the Safety Network Number 4 5 SNN Mismatch RSNetWorx for DeviceNet compares the offline SNN to the online SNN during each browse operation one shot or continuous and during upload and download operations If the SNNs do not match RSNetWorx for DeviceNet indicates an error
2. character display LED Indicators DewiceNet Batali DeviceNet Safety Port Publication 1753 UM002A EN P July 2005 Before You Begin 1 7 The 1753 DNSI features two communication ports one for DeviceNet communications and one for High Speed Safety Protocol HSP communication with a GuardPLC controller The HSP port is a 1 Mbps full duplex RS 485 interface The safety scanner also features a 4 character dot matrix display which provides status and error codes Status LEDs on the safety scanner indicate module network and HSP connection status See Chapter 10 for more information Supported Connections The DeviceNet Safety port supports a maximum of 32 DeviceNet Safety input connections 32 DeviceNet Safety output connections and standard connections for up to 63 nodes The safety scanner does not support Quick Connect Auto Device Replacement or Autoscan Safety Connections The safety scanner supports single cast producing or consuming connections and multi cast consuming connections as a DeviceNet Safety originator Up to 32 producing and 32 consuming safety connections can be made These connections are used when the safety scanner is communicating to distributed safety I O modules The safety scanner also supports the use of two safety targets defined by RSLogix Guard PLUS and made available via the Target Connections File One target may be a single or multi c
3. list Input Points 02 03 8 Input Points 04 05 C Inout Points 06 07 t Indicates that this parameter is associated to a parameter above and or below the selected parameter in the parameter list Publication 1753 UM002A EN P July 2005 Configure DeviceNet Nodes and Connections 5 3 Configure the DeviceNet Safety Scanner s Safety Connections Standard Input and Output Parameters 1791DS modules support standard data as well as safety data Configure standard input and output parameters using the Parameters tab on the module properties page Y 1791DS IB12 12Pt Safety DC_Input 2 x General l Safety Safety Configuration Safety 1 0 Parameters 1 0 Data EDS File Select the parameter that you want to configure and initiate an action using the toolbar I Groups m M Jal z gt Monitor i e ID Parameter Current value 66 amp Test0OData OFF 67 TestoOStatus Ok 68 TestO0FaultAction Clear off 69 TestodAlarm No alarm 70 TestO1Data OFF Icon Description 71 Test0lStatus OK amp Indicates that this parameter is read 72 Test01FaultAction Clear off only TestO1Alarm No alarm Indicates that this parameter is a Test02Data OFF scaled value a z Testoz5taius Of e Indicates that this parameter is linked Test02FaultAction Clear off to another parameter in the parameter TestOZAlarm No alarm list Test03Data OFF t Indicates that this parameter is
4. GuardPLC Controller PLUS Software a baa C ao Communication Module DeviceNet RSNetWorx for DeviceNet exchanges signal information with RSLogix Guard PLUS the configuration and programming tool for the GuardPLC controller The Scanner Signals and Target Connections Publication 1753 UM002A EN P July 2005 1 6 Before You Begin Files enable RSNetWorx for DeviceNet and RSLogix Guard PLUS to share the same view of the individual signals available on all of the DeviceNet connections present in a specific DeviceNet Safety Scanner configuration TIP If you install RSLogix Guard PLUS and RSNetWorx for DeviceNet on the same PC you can take advantage of the Automatically Update Signals feature Otherwise you must manually import and export the Scanner Signals and Target Connections files See Chapter 7 Associate the Scanner and Controller and Download the DeviceNet Network Configuration for more information The following table lists the software and revision level required to operate with the 1753 DNSI scanner Function Software Revision Communications RSLinx 2 42 or higher DeviceNet Configuration RSNetWorx for DeviceNet 6 x or higher RSLogix Guard PLUS 4 0 or higher i o Program Management Programming Application Logic RSLogix Guard PLUS 6 x or higher Hardware Management DeviceNet Safety Scanner Hardware Overview Features Front View Bottom View HSP Port
5. Publication 1753 UM002A EN P July 2005 2 Preface Related Documentation The table below provides a listing of publications that contain important information about GuardPLC Controller systems For Read this document Publication Information on installing programming operating and GuardPLC Controller User Manual 1753 UM001 troubleshooting a GuardPLC Controller Detailed requirements for achieving and maintaining SIL 3 GuardPLC Controller Systems Safety Reference Manual 1753 RM002 applications with the GuardPLC Controller System Information on installing the DeviceNet Safety Scanner for DeviceNet Safety Scanner for GuardPLC Installation 1753 IN009 GuardPLC Controllers Instructions Information on installing DeviceNet Safety I O Modules DeviceNet Safety 1 0 Installation Instructions 1791DS INO01 Information on configuration and programming for DeviceNet Safety 1 0 Modules DeviceNet Safety 1 0 User Manual 1791DS UM001 If you would like a manual you can e download a free electronic version from the internet at www rockwellautomation com literature e purchase a printed manual by contacting your local Allen Bradley distributor or Rockwell Automation sales office Common Techniques Used The following conventions are used throughout this manual in This Manual e Bulleted lists such as this one provide information not procedural steps e Numbered lists provide sequential steps or
6. try_open The active endpoint is attempting to open the connection but the connection is not yet open 2 connected The connection is established and normal functions such as data transfer and time monitoring are occuring DeviceNet Safety Connection Status The Safety connection fault and idle status tables are only available as signals in the RSLogix Guard PLUS application Each table is presented as a collection of 66 bits contained within 3 DWORD device signals as shown in the following table The left column shows the signal names as they appear in RSLogix Guard PLUS Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 le f5 4 3 f2 j1 Jo ic amp Connection 32 31 30 129 128 127 126 125 24 123 22 21 120 19 118 17 hie las Jaa J13 t12 11 lio Ja fae 7 le Is la fa 2 fa Number N z Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 115 14 13 12 ola l8 7 le 5 f4 13 2 1 Jo is Connection le4 63 62 61 leo 59 58 57 56 55 54 53 52 51 50 49 Jas 47 lae las 44 a3 f42 fan fao 39 38 37 36 35 34 33 Number N v Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 115 14 13 12 oja l8 7 le 5 f4 13 2 1 Jo Connection RESERVED 66 65 Number N 3 Bit Position 31 30 29 28 127 26 25 24 123 22 21 20 19 18 17 16 15 14 13 12 111 10 19 Ja Iz le J5 J4 J3 i2 1
7. 5 Enter and confirm the new password 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 _ 1 2527 6 Click OK Forgotten Passwords If you forget the password you can reset it 1 On the Safety tab of the Device Properties dialog click on the Password button to open the Set Device Password dialog 2 Click on the Reset Password button Publication 1753 UM002A EN P July 2005 Set Up Your DeviceNet Network 3 7 3 Contact Rockwell Automation Technical Support and provide the device Serial Number and Security Code from the Reset Password dialog Reset Device Password 02 1753 DNSI DeviceNet Safety from the device Upon completing this operation it is A Resetting the device password will remove the password recommended that a new password be set in the device Device Details Serial Number FFFFFFFF Security Code ooo 0 To reset the device password contact the device vendor for your Vendor Password and enter it below m Cancel Hep 4 Enter the Vendor Password obtained from Rockwell Automation Technical Support on the Reset Device Password dialog and click OK Publication 1753 UM002A EN P July 2005 3 8 Set Up Your DeviceNet Network Publication 1753 UM002A EN P July 2005 SNN Formats Chapter 4 Manage the Safety Network Number Safety Network Number
8. guidelines refer to the Industrial Automation Wiring and Grounding Guidelines publication number 1770 4 1 Power for the module is provided via an external 24V dc power source as well as from the DeviceNet cable In North America you must use a power supply that is marked CLASS 2 per the requirements of NFPA National Electric Code or CSA 22 1 Canadian Electric Code Part 1 Outside of North America you must use a Safety Extra Low Voltage SELV or a Protected Extra Low Voltage PELV power supply to power this module A SELV supply cannot exceed 30V rms 42 4V peak or 60V dc under normal conditions and under single fault conditions A PELV supply has the same rating and is connected to protected earth Tighten power supply terminal screws to 0 5 to 0 6 Nm 4 4 to 5 3 in lb While some power is drawn from the DeviceNet network the Allen Bradley Gua PLE f D eNet Safety Scanne main power source is the external power supply 1753 DNSI device on the network because an electrical arc can occur This could cause an explosion in hazardous location installations ATTENTION Do not connect or disconnect either communications cable with power applied to this module or any The scanner has two communication ports The DeviceNet port is for communicating on DeviceNet allowing connections to up to 63 standard DeviceNet nodes and 32 DeviceNet Safety n
9. to Safety Lock the device before operating the device in a safety application 5 If you have set a password for the device enter the password when prompted Set Passwords Optional You can protect safety devices with a password to prevent changes to the configuration of the device by unauthorized personnel When a password is set the following operations require the password to be entered e download e Safety Reset e Safety Lock e Safety Unlock Set or Change a Password To set a password for a module 1 Double click on the module to open the Device Properties dialog 2 Select the Safety tab Publication 1753 UM002A EN P July 2005 3 6 Set Up Your DeviceNet Network 3 Click on the Password button 2x Input Output Summary GuardPLC General Safety Module Safety Connection Scanlist This safety device is not safety locked After you have configured Wes the device run the Safety Device Verification Wizard to set the i device to the safety locked state Safety Network Number 2F20_0435_5A94 1 11 2005 1 36 45 466 PM Configuration Signature ID 84715372 Copy Signature Date fi 1142005 Time fi 36 46 57 PM TIP You can also access the Set Device Password dialog by either e clicking on the module and choosing Set Password from the Device menu or e right clicking on the module and selecting Set Password 4 Enter the Old Password if one exists
10. Define Signals for Safety Datdis 15 42 o eg tee etek aes 8 1 Configure HSP Connection wswioy Reet S Fae aay 8 3 Create Application Program Logic 53 4 4 cuok sada eed a4 8 4 Save and Compile Application Logic 8 4 Download the Project to the Controller 8 4 Place the Controller in Stop Mode if necessary 8 4 Download the Project s2 5a kaos eee plaka 8 4 Chapter 9 Start the Safety Device Verification Wizard 9 1 Determine if Devices Can Be Verified 9 1 Select Devices OsV Cry lt 3 4 i ion ae Rtas eon ek tm 9 3 Review the Safety Device Verification Reports 9 5 Lock Safety Devices S amp oom swale 4 acd ah ew x Me Re bee aK 9 6 View the Safety Device Verification Wizard Summary 9 7 Chapter 10 LED Status Indicators Si Suet yak yess Geek eale eed 10 1 Alphanumeric Dis lay esa 9 oe 8S dis eh FE aoe gece dae b bodes 4 10 2 AU POW CE U DSen eein pie ea Gd cng see dei i a wes 10 2 During Operan ac sas at eee eae Bi Peed 10 2 Connection Status ren no 5 Fe rag eTA SSS STE PETES OS 10 9 DeviceNet Connection Status Bit Behavior 10 9 DeviceNet Safety Connection Status 10 10 Standard DeviceNet Connection Status 10 11 DeviceNet Interface Status o 4 scr age HAR ES aS 10 12 Appendix A GEHCPAL sac aha wish ul hog tlh ey at gas OUR a a Nay Aas ik nae ek A 1 Environmental sinse ae aia Pee Gon ha as RY ah Ble ta aes A 1 Ele
11. TestO3status associated to a parameter above and or below the selected parameter in the parameter list TIP Other devices may have different configuration options Consult the user manual for your device for more information Configure DeviceNet Safety communications by configuring the scanner s connections to safety targets On the Safety Connections tab right click on the I O module and select Add Connections to display all of the available connections EY 1753 DNSI DeviceNet Safety Scanner 2 x Input Output Summary GuardPLC General Safety Module Safety Connection Scanist Data APL CATL Config 1D Add Connection Auto Add Default Connections Configured Safety Connections 01 1791DS IB12 121 Select All Devices Ctrl 4 What s this Publication 1753 UM002A EN P July 2005 5 4 Configure DeviceNet Nodes and Connections Publication 1753 UM002A EN P July 2005 The Add Safety Connection dialog allows you to configure a connection 1 Target Device p 1791DS 1B12 12Pt Safety DC_Input Connection Name Details Connection Type Multicast hA Configuration Configuration signature must match x 7A68_A432 1 11 2005 1 37 19 566 PM Communication Parameters Requested Packet Interval RPI 10 a ms Connection Reaction Time Limit CRTL 60 0 ms Advanced Add Cancel Help en Select the desired connection by ch
12. 0 C to 60 C 32 F to 140 F Relative Humidity IEC 60068 2 30 Test Db Un packaged Non operating Damp Heat 5 to 95 noncondensing Vibration IEC60068 2 6 Test Fc Operating 2g at 10 to 500 Hz Operating Shock IEC60068 2 27 Test Ea Unpackaged Shock 30g Non operating Shock IEC60068 2 27 Test Ea Unpackaged Shock 50g Enclosure Type Rating none open style Publication 1753 UM002A EN P July 2005 A 2 Specifications Electrical EMC Publication 1753 UM002A EN P July 2005 Emissions CISPR 11 Group 1 Class A ESD Immunity IEC 61000 4 2 e 6 kV contact discharges e 8kV air discharges Radiated RF Immunity IEC 61000 4 3 e 10V m with 1 kHz sine wave 80 AM from 30 MHz to 2000 MHz e 10V m with 200 Hz 50 Pulse 100 AM at 900 MHz e 10V m with 200 MHz 50 Pulse 100 AM at 1890 MHz e 3V m with 1 KHZ sine wave 80 AM from 2000 MHz to 2700 MHz EFT B immunity IEC 61000 4 4 e 2 kV at 5 kHz on power ports e 2 kV at 5 kHz on communications ports Surge Transient Immunity IEC 61000 4 5 e 1 kV line line DM and 2 kV line earth CM on power ports RO e 2 kV line earth CM on communications ports Conducted RF Immunity IEC 61000 4 6 e 10Vrms with 1 kHz sine wave 80 AM from 150 kHz to 80 MHz Specifications A 3 Certifications When marked the components have the following certifications See the Produc
13. 1 assignment 4 2 4 3 automatic 4 2 automatic assignment 4 2 copy 4 2 definition G 2 formats 4 1 managing 4 1 manual 4 2 4 3 manual assignment 4 3 mismatch 4 5 mismatch dialog 4 5 reset 3 4 4 6 time based 4 1 safety network number error icon 9 2 safety reset 3 4 when faulted 10 3 safety lock devices during reset 3 5 icon 9 2 save and compile logic 8 4 scanlist 5 8 5 9 definition G 3 scanner DeviceNet connections 2 6 Publication 1753 UM002A EN P July 2005 features 1 7 ground 2 4 hardware overview 1 6 HSP connections 2 7 mounting 2 2 power supply 2 5 reset 4 6 scanner configuration signature 1 2 scanner ID 5 12 definition G 3 scanner receive timeout 5 13 scanner signals file 1 5 6 4 7 1 definition G 3 import 7 5 save 7 4 signal create 8 2 signal editor 8 2 signals connect 8 1 connect safety 8 2 define 8 1 8 2 export 7 4 import 7 5 safety data 8 1 SIL See safety integrity level software revision RSLogix Guard PLUS 1 6 RSNetWorx for DeviceNet 1 6 software revisions RSLinx 3 1 SRS See controller ID standard connection 1 7 standard connections colorization 1 4 standard data communication 1 2 statistics button 5 13 status A xx 10 2 bus off detected 10 3 display 10 2 duplicate node failure 10 2 E ee 10 4 extended error code 10 4 faulted must issue safety reset 10 3 G gg 10 4 IDLE 10 2 LEDs 10 1 monitoring 10 1 N xx 10 3 no network power 10 3 RUN 10 2 S ee 10 4 status code descrip
14. 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 o Address Re Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 114 13 12 11 10 19 8 7 6 5 4 3 12 0 if Node Z 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 Address Bit Position T 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 111 10 19 8 17 16 5 J4 3 12 0 i o TE Node amp 131 130 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 J10 19 8 I7 6 I5 l4 3 2 o Address x Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 J10 9 8 7 6 5 j4 3 2 0 i o a Node amp 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 138 137 36 135 34 133 132 Address DeviceNet Interface Status The DeviceNet Interface Status bits provide general status information for the scanner s DeviceNet Interface as described in the table below Status Bit Data Type Attribute Value Description Communications BOOL 0 Normal Failure 1 Bus Off condition is present DeviceNet Power BOOL 0 Normal Failure 1 No DeviceNet power Duplicate MAC BOOL 0 N
15. 51 mm 2 0 in from the front face of the module to the door of the enclosure e Select a location where air flows freely or use an additional fan e Do not mount the module over a heating device Publication 1753 UM002A EN P July 2005 Install the 1753 DNSI 2 3 The module can be DIN rail or panel mounted as described in the following sections Be careful of metal chips when drilling mounting holes for your module or other equipment within the enclosure or panel Drilled fragments that fall into your module could cause damage DIN Rail Mounting Mount the module to a EN50022 35x7 5 or EN50022 35x15 DIN rail by following the steps below 1 Close the DIN latches if they are open 2 Hook the top slot over the DIN rail 3 While pressing the module down against the top of the rail snap the bottom of the module into position TIP To remove the module from the DIN rail insert a flathead screwdriver into the gap between the housing and each latch and pull the latch downward When both DIN latches are open lift the module off of the rail The maximum extension of each DIN rail latch is 14 mm 0 55 in in the open position Publication 1753 UM002A EN P July 2005 2 4 Install the 1753 DNSI Ground the Scanner Publication 1753 UM002A EN P July 2005 Panel Mounting Mount the scanner directly to a panel using 4 screws The preferred screws are 8 M4 however 6 M3 5 may be used 1 Use
16. Delay This parameter defines the delay time the scanner uses between scans of the DeviceNet network If you have slave devices configured for Polled behavior in the scanner s scanlist Interscan Delay SD defines the amount of time the scanner waits between writing outputs to the polled devices Configure DeviceNet Nodes and Connections 5 7 Increasing the ISD time causes a longer network scan which adversely affects overall input to output performance However the increase allows lower priority messages to get more network access These lower priority messages include those used to do network browsing and configuration upload and download functions So if these network functions are sluggish on your system increasing the ISD time is one way to make more bandwidth available for lower priority messages In addition if the last node in your scan list produces a large amount of polled data you may want to increase the ISD time to ensure that the entire response is received before the next poll request is sent to that node Foreground to Background Poll Ratio Devices set for polled behavior can be polled on every I O scan foreground or they can be polled less frequently background Setting a device for foreground or background behavior is done when you configure each device on the Scanlist tab from the Edit I O Parameters dialog A ratio of 2 means that any nodes included on the background list are polled every other scan cycl
17. For example use a prefix of std_ for any signals that are standard and a prefix of safe_ for any signals that are safety related mE The red blue colorization is not a guarantee that a signal is a safety signal It only indicates which type of connection the signal was transferred over The classification of the end node must also be considered Any signal that appears in the blue standard Connect Signals window and is regarded as safety at the end device must be treated as standard in your application Any signal that appears in the red safety Connect Signals window and is regarded as standard at the end device must be treated as standard in your application In order for a signal to be regarded as a safety value in your application the end device configuration must treat it as safety and it must be transferred over a DeviceNet Safety connection RSNetWorx for DeviceNet version 6 x or higher is the configuration tool for the 1753 DNSI on the DeviceNet Safety network RSNetWorx for DeviceNet can connect to the safety scanner directly over the DeviceNet network via an RS 232 interface 1770 KFD module or PC card 1784 PCD or PCID or through another network using a bridge device A bridge can be either a single device with communication ports for two different networks or separate communication devices in the same chassis PC with RSNetWorx for 1753 DNSI Dene Ne Son Wale PC with RSLogix Guard
18. I O module in a system the Controller ID must be a unique number from 1 to 65 535 The default is 60000 Safety Lock The safety scanner and DeviceNet safety I O modules must be Safety Locked to prevent their configurations from being unintentionally modified Safety Lock all DeviceNet Safety devices by running the Safety Device Verification Wizard in RSNetWorx for DeviceNet before placing the safety application into service Password protection The configuration of the safety scanner can be protected by the use of an optional password If you set a password in a safety device the download Safety Reset Safety Lock and Safety Unlock operations will require a password The 1753 DNSI provides DeviceNet access for GuardPLC 1600 and GuardPLC 1800 controllers These GuardPLC controllers support communications via High Speed Safety Protocol HSP The 1753 DNSI reads and writes data from DeviceNet nodes and exchanges this aggregate data with the GuardPLC controller via HSP The 1753 DNSI scanner communicates with DeviceNet devices over the network to e read inputs from a device e write outputs to a device e monitor device status How the 1753 DNSI Communicates For standard data the safety scanner communicates with a device via strobe poll change of state and or cyclic messages It uses these messages to solicit data from or deliver data to each device in its scanilist Before You Begin 1 3 For safety data the scan
19. ID SRS of the controller If you do not know the SRS you need to connect the controller directly to your computer s Ethernet port and use the Communication Settings dialog to retrieve the SRS See step 1 on page 6 5 Publication 1753 UM002A EN P July 2005 Create a GuardPLC Project with High Speed Safety Protocol 6 3 Add High Speed Safety Protocol to the GuardPLC Controller Resource To add High Speed Safety Protocol CHSP to your GuardPLC controller 1 Right click on the Protocols folder under your Resource and select New gt HSP Protocol 2 Configure HSP communications Right click on HSP Protocol and select The Controller Receive Timeout is the amount of time that the controller waits to receive an HSP response from the scanner JzJRSLogix Guard PLUS Hardware Management Project Edit Signals Online Windows Help Eg DNSI project Configuration 60000 Resource L Prog Copy Paste Mi Modbus Master Delete M2 Modbus Slave Print PZ Profibus dp Slave ramming Properties Fae Profibus Master Se Send Receive over TCP SNTP Client SNTP Server Properties Configuration Resource Protocols HSP Protoc m x Type JESP Protocol Name JHSP Protocol ooo Controller Id ic Controller Receive Timeout ms fo ti Controller Resend Timeout ms poo Scanner Id E Scanner Receive Timeout ms cc HSP Signatur
20. OOFF 2111 Unable to read OOFF 2112 The shared routine is not editable OOFF 2113 The controller is in fault mode OOFF 2114 Run mode is inhibited Monitor Status 10 9 Connection Status You can monitor the HSP and DeviceNet Safety and standard connection status using the scanner s connection status bits and the related GuardPLC application signals as discussed in the following sections DeviceNet Connection Status Bit Behavior The following table describes the combined operation of the DeviceNet connection status bits Connection Idle Mode Safety Connection Operation Standard Connection Operation Fault 0 Valid 0 Run Data is actively being controlled by the producing device The producing device is in the Run mode 0 Valid 1 Idle The connection is active and the producing device is The connection is active and the producing node is in the Idle state The safety data sent to the in the Idle state The data sent to the controller for controller from this connection is reset to zero this connection is hold last state 1 Faulted 4 Idle The connection is faulted The state of the Not applicable producing device is unknown The safety data sent to the controller from this connection is reset to zero A safety connection status bit is set to Faulted any time the connection is not established or not operating error free 1 Faulted 0 Runl Not applicable The connection is faulted The
21. PLUS Hardware Management Project Edit Signals Online Windows Help ES DNS project A Configuration i BE 60000 Resource E Distibuted 1 0 Input Output l Pro BBO Guar gramming Ter amp Safety Data Signal Connections Configuration 60000 Resource Proc olx Delete Signal Define Data Help Safety Data Define Target Connections gt Standard Data Import Scanner Signals HSP Data Export Target Connections Validate New Copy Paste Delete Print Properties Publication 1753 UM002A EN P July 2005 8 2 Develop Your GuardPLC Application 2 Open the Signal Editor by selecting Editor from the Signals menu amp Signal Editor 3 Create a new signal by selecting New Signal or clicking in an empty signal Name field 4 With the Safety Data Signal Connections dialog visible and the Signal Editor dialog open drag your application signals to the desired device data signals BOOL BOOL BOOL BOOL ata BOOL ata BOOL a BOOL a BOOL BOOL BOOL BOOL BOOL amp Safety Data Signal Connections Con Pi m bs Delete Signal Define Data Help Input Output 01_1_Pt09D 01_1_Pti0Data Publication 1753 UM002A EN P July 2005 Develop Your GuardPLC Application 8 3 Configure HSP Connection The safety scanner closes the HSP connection
22. The HSP Signature is calculated based on the scanner s configured safety and standard connections and is passed to RSLogix Guard PLUS via the Scanner Signals File Implicit Messaging The type of messaging used for high priority I O control data e g change of state cyclic polled strobed or safety Node Hardware that is assigned a single address on the network also referred to as device or module Polled A type of standard I O data communication in which a polled message solicits a response from a single specified device on the network a point to point transfer of data Requested Packet Interval RPD When communicating over a network this is the maximum amount of time between subsequent production of input data Safety I O Safety I O has most of the attributes of Standard I O except it features mechanisms certified to SIL 3 to ensure data integrity and timeliness Safety Network Number SNN Uniquely identifies a network across all networks in the safety system The end user is responsible for assigning a unique number for each safety network or safety sub net within a system The Safety Network Number makes up part of the Unique Node Identifier UNID Glossary 3 Scanlist The list of devices nodes with which the scanner is configured to exchange I O data Scanner ID A read only value which uniquely identifies the scanner and is required to connect the GuardPLC controller to the scanner The s
23. and controller you must repeat this procedure whenever you make a change to the DeviceNet connections To manage the association between the safety scanner and the GuardPLC controller manually 1 On the GuardPLC tab of the Device Properties dialog verify that the Controller ID matches the GuardPLC controller to which you want the scanner associated 2 Click on the Export Scanner Signals button General Safety Module Safety Connection Scaniist Input Output Summary GuardPLC Controller ID feooo0 a Scanner ID 2F20_0435_5494_0000_0000 HSP Signature 7426_FE43 Scanner Receive Timeout 20 ms Max Scanner Response Time fig ms Statistics View Target Connection I Automatically Update Signals RSLogix Guard PLUS Project Folder l Export Scanner Signals D Import Target Connections ES 3 Save the Scanner Signals file The Scanner Signal file s extension is ssf Associate the Scanner and Controller and Download the DeviceNet Network Configuration 7 5 Download the DeviceNet Network Configuration 4 Import the Scanner Signals file into your GuardPLC project a In RSLogix Guard PLUS Hardware Management right click on the instance of the HSP protocol for your GuardPLC controller resource and select Import Scanner Signals JzJRSLogix Guard PLUS Hardware Management Project Edit Signals Online Windows Help ES DNS project I A Configuration BR 60000 Re
24. e RPI is in milliseconds e data sizes are in bytes e Baud_Rate is in bits per second The bit_stuffing_ factor is the percentage of bandwidth estimated to be used by bit stuffing We used 15 for our calculations 1 to 2 Bytes In the equation below A 1 Data_RPI 0 001 B Safety_Data_Size 6 C B x 8 x bit_stuffing_factor rounded to the nearest whole number D 1 Data_RPI x 100 0 001 Bandwidth 100 x A x 57 Bx 8 D x 115 Baud_Rate 3 to 250 Bytes In the equation below A 1 Data_RPI 0 001 B 2 x Safety_Data_Size 8 C B 8 rounded to the nearest whole number D 1 Data_RPI x 100 0 001 E Bx 8 x bit_stuffing_factor rounded to the nearest whole number Bandwidth 100 x CA x 57 x C Bx 8 E D x 115 Baud_Rate Publication 1753 UM002A EN P July 2005 D 2 Calculate Safety Connection Bandwidth Single cast Outputs Multicast Connections Publication 1753 UM002A EN P July 2005 1 to 2 Bytes In the equation below A 1 Data_RPI 0 001 B Safety_Data_Size 6 C B x 8 x bit_stuffing_factor rounded to the nearest whole number D 1 Data_RPI x 19 0 001 Bandwidth 100 x A x 57 Bx 8 C D x 115 Baud_Rate 3 to 250 Bytes In the equation below A 1 Data_RPI 0 001 B 2 x Safety_Data_Size 8 C B 8 rounded to the nearest whole number D 1 Data_RPI x 19 0 001 E Bx 8 x bit_stuffing fact
25. gt Cancel Help TIP If you click on Next without selecting a device to verify the wizard checks whether any devices were verified or are ready to be locked in this execution of the wizard If Then the wizard displays devices were verified the Review page listing those devices devices are ready tobe the Lock page listing those devices Safety Locked no devices were verified the Finish page no devices are ready to the Finish page be Safety Locked Verify Your DeviceNet Safety Configuration 9 5 Review the Safety Device Verification Reports The Review page displays safety devices with status of either Verify FAILED or Ready to be Safety Locked Safety Device erification Wizard x Review Safety Device Verification Reports 4 Click the Review link in the Report column to launch the safety verification report of the safety device To review the configuration of all devices click Review All a eview Verify FAILED Gm 02 1791DS 1B12 12Pt Safety DC_Input amp Review Ready to be Safety Locked sli 03 1791DS IBSX0B8 8Pt 8Pt Safety DC_Input amp Review Ready to be Safety Locked W 04 1791DS IB4X0 W4 4Pt 4Pt Safety DC_Input amp Review Ready to be Safety Locked Sa 05 1791DS IBSXOB8 8Pt 8Pt Safety DC_Input Review All It is recommended that you print the verification reports _ for your records Click Next to continue lt Back Cancel Help 1 Click o
26. hierarchical information Publication 1753 UM002A EN P July 2005 Preface 3 Understanding Terminology The following table defines acronyms used in this manual Acronym Full Term Definition 1002 One Out of Two A safety architecture consisting of two channels connected in parallel such that either channel can perform the safety function CAN Controller Area Network The networking standard that defines the physical layer of DeviceNet COS Change of State A type of I O data communication in which the interface module can send and receive data with slave devices whenever a data change occurs in the configured slave device EDS Electronic Data Sheet A vendor supplied template that specifies how device configuration information is displayed as well as what is an appropriate entry value EPR Expected Packet Rate The rate at which packets are expected to be received by a device HSP High Speed Safety Protocol A high speed high integrity protocol designed to transfer both safety and standard data between the GuardPLC controller and the DeviceNet Safety Scanner for GuardPLC Controllers MAC ID Media Access Identifier The network address of a DeviceNet node MTBF Mean Time Between Failures Average time between failure occurrences MTTR Mean Time to Restoration Average time needed to restore normal operation after a failure has occurred PC Personal Computer Computer used to interface with and co
27. whenever either an HSP error occurs or the safety scanner diagnostic reports an error Individual DeviceNet safety or standard connection errors do not cause the HSP connection to close In the case of a faulted DeviceNet connection any input data associated with that connection is forced to zero before being transmitted to the GuardPLC controller over HSP Your GuardPLC application logic can control the operation of the HSP connection by writing a value to the signal associated with the HSP Connection Control Word To connect a signal to the HSP Connection Control Word right click on your HSP protocol in the RSLogix Guard PLUS Hardware Management window and choose Connect Signals gt HSP Data Project Edit Signals Online Windows Help ES DNSI project A Configuration Safety Data WO Guar Define Target Connections gt Standard Data Programming Ter Import Scanner Signals Export Target Connections HSP Data amp Signal Connections Configuration 60000 Ren M Ex The following table describes the possible mode settings for the HSP connection Connection Mode Description Control Word Value 0x8000 Disabled HSP communication disabled 0 Autoconnect If communication is lost open it automatically in the next cycle 0x100 Toggle_Mode_0 If the connection is lost do not reopen it until Toggle_Mode_1 is written 0x10
28. wrong module 0001 0115 Device type is incorrect 0001 0116 Module revision is incorrect 0001 0118 The configuration format is invalid 0001 011A The application is out of connections 0001 0203 The connection has timed out 0001 0204 An unconnected message has timed out 0001 0205 Unconnected send parameter error occurred 0001 0206 The message is too large 0001 0301 There is no buffer memory 0001 0302 Bandwidth is not available 0001 0303 Dynamic I O resources are not sufficient 0001 0305 Signatures match 0001 0311 The port is not available 0001 0312 A link address is not available 0001 0x0315 Safety Connection Type name is invalid not equal to 0x50 0001 0317 The connection is not scheduled 0001 0x0801 The RPI is not compatible with previously established multicast connections All multi cast consumers must request the same RPI 0001 0x0802 Safety connection size is invalid 0001 0x0803 Safety connection format is invalid 0001 0x0805 Ping interval EPI multiplier was out of range 10 to 10000 0001 0x0806 Time Coordination Message Minimum Multiplier was out of range 10 to 10000 0001 0x0807 Time Expectation Multiplier was out of range 0 to 42969 0001 0x080A CPCRC value in Safety Open and calculated CPCRC value 0001 0x080B Time Correction Connection ID is invalid 0001 0x080C Configuration Signatures do not match The Configuration Signature was non zero and did not match the value in the targe
29. 1 Toggle_Mode_1 If the connection is lost do not reopen it until Toggle_Mode_0 is written Publication 1753 UM002A EN P July 2005 8 4 Develop Your GuardPLC Application Create Application Program Logic Save and Compile Application Logic Download the Project to the Controller Publication 1753 UM002A EN P July 2005 Create application program logic using the signals you defined Drag and drop the application signals which are now connected mapped to DeviceNet data signals into the appropriate application Type Instances and create your program logic Save and compile your application logic Compiling the application logic and controller hardware configuration results in a high integrity computation of the HSP signature Refer to the GuardPLC Controller Systems User Manual publication number 1753 UMO001 for details on creating saving and compiling program logic Place the Controller in Stop Mode if necessary Before you can download to the GuardPLC controller the controller must be in Stop mode In RSLogix Guard PLUS Hardware Management left click on the stop icon on the Control Panel and confirm the action by selecting Yes to the warning prompt Control Panel GPLC1600_1 PADT Resource Communication AS we i as Download the Project In RSLogix Guard PLUS Hardware Management 1 Right click on the controller resource 2 Select Online gt Control Panel 3 Fill in your user name a
30. 1784 PCD 1 5 1784 PCID 1 5 A A xx 10 2 add connections 5 3 add devices available devices list 5 9 advanced safety connection properties 5 5 associate 7 1 7 5 manually 7 4 7 5 automap 5 9 automatically update signals 7 2 7 3 available devices list 5 9 add devices 5 9 B baud rate reset 3 4 See communication rate bridge device 1 5 bus off detected 10 3 C change of state definition messages 1 2 CIP safety protocol definition G 1 COMM3 port 2 7 communication connections 2 5 communication rate 1 8 choose 1 9 set 1 9 compile logic 8 4 configuration DeviceNet Safety 1 0 target nodes 5 2 Index DeviceNet Safety Scanner safety connections 5 3 DeviceNet Safety Scanner standard connections 5 6 DeviceNet Safety target nodes 5 1 DeviceNet Standard slave nodes 5 6 GuardPLC controller connections 5 12 HSP connnection 8 3 safety parameters 5 2 signals 8 1 standard inputs 5 10 standard outputs 5 11 standard parameters 5 3 standard scanner inputs 5 10 verify 9 1 9 7 configuration owner reset 3 4 configuration signature 1 1 5 1 comparison 9 6 components 5 1 definition 5 1 G 1 mismatch 9 2 configure a driver 3 1 connect safety signals 8 2 connect signals 8 1 connection reaction time limit 5 4 and network delay multiplier 5 5 DeviceNet Safey 1 0 5 4 connections add 5 3 controller ID 5 12 7 4 and system ID 6 4 default 1 2 definition G 1 controller receive timeout set 6 3 controller resend timeout defin
31. 76 on page 10 4 NoTx The scanner has failed to transmit a message See Status code 79 on page 10 4 N xx Another device has a problem where xx is the node address of the device e For safety connections the status code S ee or extended error code G gg lt nnnn gt follows e For standard connections the status code E ee follows Publication 1753 UM002A EN P July 2005 10 4 Monitor Status Display Description S ee Status code for safety connections where ee is the decimal error code listed on page 10 4 G gg lt nnnn gt Extended error code for safety connections where e gg indicates the hexidecimal general status error code as listed in the Safety Connection General Status Error Codes table on page 10 5 and e nnnn indicates the hexidecimal extended error code as listed in the table Safety Connection Extended Error Codes on page 10 7 E ee Status code for standard connections where ee is the decimal error code listed in the Status Codes table on page 10 4 Status Codes Status Code Description Recommended Action ee 70 The address of the device is already in use by Change the address of the device to an unused address another device on the network 71 Illegal data in scan list Reconfigure the scan list and remove any illegal data 72 No communication with the device Inspect the device and verify connections 73 Device s identity information d
32. Controller s Communication cei aie f 7 Settings communication settings Te Address PES using MAC Address 00 e0 al Get Address PES using IP Address 0 0 0 0 System Rack a 0 Get Communication Settings IP ddress 0 0 0 0 Factory Settings Subnet Mask 0 0 0 0 gt Project Default Gateway aq o0 0 0 System Rack 0 0 Set via MAC Set via IP Cancel Help a If you know the current IP Address SRS and Administrator password you can fill in the IP Address and SRS and select Get This retrieves and confirms the communication settings If you want to modify the current settings see step 2 b If you do not know the current settings you must connect your GuardPLC controller directly to your computer s Ethernet port and fill in the last three digits of the controller s MAC Address The MAC Address is located on a label above the controller s lower Ethernet ports Select Get to retrieve the current settings TIP The MAC Address lookup function can fail if there is an Ethernet switch between the PC running RSLogix Guard PLUS and the GuardPLC controller 2 You can now enter the desired settings for the IP Address and SRS 3 To apply the new settings to the controller click on either the Set via IP or Set via MAC buttons depending on whether you use the IP Address or MAC Address in step 1 4 Click the gt Project button to send the settings to the pro
33. D Allen Bradley DeviceNet Safety Scanner for GuardPLC Controllers Catalog Number 1753 DNSI User Manual e ee oe ee ey m a eT 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 www ab com manuals gi 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
34. DeviceNet Safety I O Target Nodes 5 2 1791DS DeviceNet Safety I O Module Parameters 5 2 Configure the DeviceNet Safety Scanner s Safety GOTMIS COIS ay tee hd eS ce ee at Seat Ad NP 5 3 Configure DeviceNet Standard Slave I O Nodes 5 6 Configure the DeviceNet Safety Scanner s Standard MIS LIONS se rti ton E a s cock o a in ek Aeon thie Rot A 5 6 Standard Communication Properties 5 6 Create a Scanlist ice Gad pee OU ee dent ane he Sees 5 8 Configure Standard Inputs 0 bcd 0d wie dod dost wang Sa 5 10 Configure Standard Outputs vise a eae ee ie ea es 5 11 Configure GuardPLC Controller Settings 5 12 Chapter 6 Create or Open a GuardPLC Project 9 3 4 ee ed eG ead eae 6 1 Add High Speed Safety Protocol to the GuardPLC Controller RESOURCE 6s oi Sb Uae ee Fee e OS OEE SS PETERS 6 3 Review the GuardPLC Controller s Communication Settings 6 5 Chapter 7 Scanner Signals Fue sc soak Bt ES RAE Be 7 1 Target Connections Filey tbe he Bae ESE Oe ees 7 2 Automatically Update Signals onana bog ounguaed a bod 4 7 2 Manually Associate the Scanner and Controller 7 4 Download the DeviceNet Network Configuration 7 5 Develop Your GuardPLC Application Verify Your DeviceNet Safety Configuration Monitor Status Specifications Configure Peer to Peer DeviceNet Communications Table of Contents 3 Chapter 8 Define Signals for Your GuardPLC Application 8 1
35. Jo 8 amp Connection 132 31 130 29 28 27 26 25 24 23 22 21 J20 J19 lis 17 J16 15 lia 13 12 11 fio fa Je 7 le 5 la 3 fz fa Number N Publication 1753 UM002A EN P July 2005 Monitor Status 10 11 X Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 116 15 14 13 12 10 9 18 Z 16 5 J4 3 2 1 J0 a2 D Connection o 8 64 63 162 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 142 41 40 39 38 37 36 35 34 33 Number a Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 116 15 14 13 12 10 9 8 Z 16 5 J4 3 2 1 JO oe Ks D Connection kes S RESERVED 66 65 Number User application logic only needs to consider status bits associated with connections present in the scanner s configuration The list of configured connections can be obtained from the RSNetWorx for DeviceNet report feature by selecting File gt Generate Report Standard DeviceNet Connection Status The Faulted Node Table and Idle Node Table attributes of the Scanner Configuration Object class 0x90 contain standard DeviceNet connection status information as described in the following table Name Attribute Data Type Access Attribute Value Description 0 The device is not faulte
36. Net Safety Configuration Publication 1753 UM002A EN P July 2005 appears listing those devices and their current status including a device icon overlaid with a status icon Safety Device erification Wizard x Unable to verify the listed devices The following devices cannot be verified Mismatch Signature Mismatch Missing Unknown S 00 1791DS 1B12 12Pt Safety DC_Input 1 GA 01 1753 DNSI DeviceNet Safety Scanner ale 02 1791DS 4IBEXOB8 8Pt 8Pt Safety DC_Input DC_Output a 03 1753 DNSI DeviceNet Safety Scanner 1 Safety Network Number Error A 07 1791D5 1B12 12Pt Safety DC_Input You can either click Next to skip the devices and continue verifying other devices or click Cancel to return to ASNetworx to correct the states of the devices Click Next to continue lt Back Cancel Help Number Error invalid or does not match the Safety Network Number Status Icon Description Overlay Missing The device is part of the network configuration but was not found during the browse operation Mismatch The device identity in the network configuration does not match the identity of the online device Unknown The device is in the configuration but has not been 2 detected on the network yet Safety Network H The Safety Network Number in the device is either for the device in the RSNetWorx for DeviceNet configuration file Signature none The configuration signature in the device doe
37. Printed in the U S A
38. SNN is FFFF_FFFF_FFFF the Upload button is disabled Publication 1753 UM002A EN P July 2005 4 6 Manage the Safety Network Number SNN and Node Address Changes Publication 1753 UM002A EN P July 2005 If you want to change the address of a safety device the Safety Network Number must be uninitialized or you must first reset the Safety Network Number To reset the SNN 1 Select the device in the hardware graphic view 2 From the Device menu choose Reset Safety Device 3 Check the Safety Network Number checkbox on the Reset Safety Device dialog and click on Reset Only the attributes selected on the dialog are reset to their factory default settings The Safety Reset only affects the safety device the configuration in the RSNetWorx project is not lost See Safety Reset Optional on page 3 4 for more information on the Safety Reset function TIP After the safety reset the node address may be changed in RSNetWorx for DeviceNet by double clicking on the safety device s node address in the graphic view After changing the node address right click on the device and click Download to Device to restore the safety device s SNN and configuration Chapter 5 Configuration Signature Configure DeviceNet Nodes and Connections To configure standard safety and peer to peer connections follow the procedures listed below in order Procedure page 1 Configure DeviceNet Safety 1 0 TargetNodes 152 2 Con
39. Safety Safety Scanner DC Input DC Input DC oo 02 KH 4 gt bt Graph Spreadsheet iN Master Slave Configuration Diagnostics usa off During each browse operation RSNetWorx for DeviceNet reads the following attributes of each device Safety Attribute Description SNN and Node Address The node address and SNN stored in the Combination RSNetWorx for DeviceNet configuration file must match the node address and SNN of the online device If the SNNs do not match the device enters the SNN error state See page 4 5 for information on resolving an SNN mismatch error Configuration Signature RSNetWorx for DeviceNet compares the Configuration Signature in its configuration file with the Configuration Signature in the online device Safety Lock If the device is Safety Locked its configuration cannot be modified without first unlocking the device 3 Download your configuration to the network by selecting the device and choosing Download to Device from the Device menu or by right clicking on the device and selecting Download to Device Associate the Scanner and Controller and Download the DeviceNet Network Configuration 7 7 4 Confirm your intent to download by clicking Yes If a device is password protected RSNetWorx for DeviceNet prompts you to enter the password for each protected device If a device is Safety Locked you must first unlock the device and then download eaa of you Safety Unlock a devi
40. When you use the Automatically Update Signals option in RSNetWorx for DeviceNet that software automatically imports any updates when the scanner s property page is displayed You can also manually export the Target Connections file to a specific location at any time by right clicking on the HSP Protocol and selecting Export Target Connections Define Safety Connections To define safety target connections 1 Right click on the HSP Protocol instance of the peer resource and select Define Target Connections gt Safety Data JeJRSLogix Guard PLUS Hardware Management Project Edit Signals Online Windows Help Fg P2P project test oe A Configuration BK 100 peer Resource 9 Distributed 1 0 Protocols GET ypelnstance Q0 GuardPLC 1800 dte aE Safety Data bk 60000 Resource Import Scanner Signals Standard Data E Distributed 1 0 Export Target Connections Protocols validate Typelnstance B10 GuardPLC 1600 ey 7 Progamming Terminal Copy 2 Drag the Safety signals from the Signal Editor to the Safety Data Target Signal Connections dialog amp Signal Editor std_p2pslave a e ps safe_p2ptarget Publication 1753 UM002A EN P July 2005 B 8 Configure Peer to Peer DeviceNet Communications 3 RSLogix Guard PLUS automatically generates a Targ
41. afety originators on the DeviceNet network IMPORTANT Complete the procedures in this chapter before making safety connections via the Safety Connections tab or standard connections via a scanlist in RSNetWorx for DeviceNet steps 2 and 4 in Chapter 5 Use the slave mode for standard connections to allow standard devices such as standard PLCs ControlLogix CompactLogix SLC 500 and others or HMIs to exchange data with the GuardPLC controller Use the safety target interface for safety connections to allow multiple GuardPLC controllers to perform safety interlocking over DeviceNet To add peer to peer connections follow the procedures listed below in order Procedure page 1 Plan Your Peer to Peer Communications B 2 2 Set Up Your DeviceNet Network 3 1 3 Commission a Peer Scanner B 2 4 Create a GuardPLC Project with High Speed Safety Protocol 6 1 5 Add a Peer Controller B 3 6 Define Target Connections for Standard and Safety Data B 4 7 Configure Peer to Peer Connections B 8 8 Configure DeviceNet Nodes and Connections non peer to peer 5 1 9 Associate the Scanner and Controller and Download the 7 1 DeviceNet Network Configuration 10 Develop Your GuardPLC Application 8 1 11 Verify Your DeviceNet Safety Configuration 9 1 Publication 1753 UM002A EN P July 2005 B 2 Configure Peer to Peer DeviceNet Communications Plan Your Peer to Peer Communications Commission a Peer Scanner Public
42. arameters General Safety Module Safety Connection Scaniist Input Output Summary GuardPLC Controller ID 60000 Scanner ID 2F20_0435_5494_0000_0000 HSP Signature 7426_FE43 Scanner Receive Timeout 20 ms Max Scanner Response Time 19 a ms Statistics I Automatically Update Signals RSLogix Guard PLUS Project Folder l Export Scanner Signals Import Target Connections Controller ID The Controller ID SRS uniquely identifies a particular GuardPLC controller within a network of controllers Its use ensures that this configuration is applied to the correct controller Specify the Controller ID of your selected GuardPLC controller or this will automatically be provided when you associate the scanner and controller as described in Chapter 7 Scanner ID The scanner ID is a read only value which uniquely identifies the scanner and is required to connect the GuardPLC controller to the scanner The scanner ID is automatically generated by RSNetWorx for DeviceNet using the SNN and DeviceNet address of the scanner It is exported in the Scanner Signals file and is viewable in the associated RSLogix Guard PLUS project HSP Signature The HSP Signature is a read only value that is unique to each layout of the signals within the data exchanged between the GuardPLC controller and the 1753 DNSI The HSP Signature is calculated based on the scanner s configured safety and standard connections and a
43. ast producer the other may be a single cast consumer These connections allow the safety scanner to look like safety I O to another safety scanner on the network and can be used for interlocking of safety data between two GuardPLC systems Standard Connections The safety scanner supports the following standard DeviceNet connection types Standard Master Connections Standard Slave Connections Polled Polled Change of State COS Cyclic Bit Strobe Publication 1753 UM002A EN P July 2005 1 8 Before You Begin Communication Rate The safety scanner supports the following communication rates but does not support autobaud e 125 Kbps default e 250 Kbps e 500 Kbps Physical Layout of the Planning your system helps ensure that you can DeviceNet Safety System e meet safety times e use memory and bandwidth efficiently e fulfill device specific requirements e leave room for system expansion Before configuring your 1753 DNSI scanner you should be familiar with each of the DeviceNet devices on your network You should know each device s e system safety time requirements e communication requirements e T O size e frequency of message delivery You must also understand and define which data elements can be treated as safety and which as standard in your intended configuration DeviceNet Safety 1 0 Performance Factors Safety nodes have priority on a DeviceNet network but the performan
44. ata tables that are exchanged over the HSP connection See How Data Tables Work on page 1 4 for more information on how safety and standard data is organized in a GuardPLC system that uses the safety scanner The simplest way to associate the 1753 DNSI and the GuardPLC controller is to select Automatically Update Signals on the safety scanner s GuardPLC tab This option is only available when RSLogix Guard PLUS and RSNetWorx for DeviceNet are installed on the same computer 1 Open the Device Properties dialog by double clicking on the scanner you want to associate 2 Select the GuardPLC tab 3 Select the Automatically Update Signals option General Safety Module Safety Connection Scanlist l Input Output Summary GuardPLC Controller ID Scanner ID f2F20_0436_5494 0000_0000 HSP Signature ECSD_E75F Scanner Receive Timeout 20 ms Max Scanner Response Time 19 ms Statistic View Target Connections IV Automatically Update Signals RSLogix Guard PLUS Project Folder CAProgram Files RSLogix Guard PLUS SPROJECTSDNSI proje ft Target Connections Associate the Scanner and Controller and Download the DeviceNet Network Configuration 7 3 4 Select your RSLogix Guard PLUS project a If you have multiple RSLogix Guard PLUS projects use care to select the correct one Browse for Project Folder x Select the folder where the RSLogix Guard PLUS project file for the associated Guar
45. atalog number type of connection that is used between the scanner and the slave device strobed polled cyclic or change of state the amount of data that will be exchanged in bytes and the location of the data within the controller s scanner s standard input image Configure DeviceNet Nodes and Connections 5 11 Configure Standard Outputs The Output tab screen allows you to define how data from the scanner is mapped to the outputs of the slave devices Y 1753 DNSI DeviceNet Safety Scanner f axi General Safety Module Safety Connection Scanlist Input Output Summay GuardPLC AutoMap 1 04 1734 0A2B Polled 1 0 0 i Output Value 0 1 bit s Output Value 1 1 bit s uma lt Not Used gt 6 bits Advanced Memory Standard Output x Start Byte 0 a mA A A A E A e A A 04 17 3 2pt AC The graphical window at the top shows each devices node number catalog number type of connection that is used between the scanner and the slave device strobed polled cyclic or change of state the amount of data that will be exchanged in bytes and the location of the data within the controller s scanner s standard output image Publication 1753 UM002A EN P July 2005 5 12 Configure DeviceNet Nodes and Connections Configure GuardPLC Controller Settings Publication 1753 UM002A EN P July 2005 Use the GuardPLC tab to configure the scanner s HSP connection p
46. ation 1753 UM002A EN P July 2005 If your application requires peer to peer DeviceNet communications you must e determine which RSLogix Guard PLUS application signals each controller and scanner combination needs to make available to peer controllers and e determine whether the chosen signals should be made available on standard or safety connections Only the following data types are supported Type Size in Description bits BOOL 1 true or false on or off USINT 8 unsigned byte INT 16 signed word UINT 16 unsigned word DINT 32 signed double word UDINT 32 unsigned double word SINT 8 signed byte REAL 32 float IEC559 single precision format LREAL 64 double IEC559 double precision format BYTE 8 string of 8 bits WORD 16 string of 16 bits DWORD 32 string of 32 bits The next steps are to set up your DeviceNet Network as discussed in Chapter 3 1 Connect the scanner to the network following the installation instructions in Chapter 2 2 Commission the scanner following the instructions in Chapter 3 to set the node address baud rate SNN and password if desired The next step is to create a GuardPLC controller resource with HSP protocol as described in Chapter 6 Configure Peer to Peer DeviceNet Communications B 3 Add a Peer Controller To add a peer controller Resource to the project 1 In RSLogix Guard PLUS Project Management right click on Configuration and selec
47. canner ID is automatically generated by RSNetWorx for DeviceNet using the SNN and DeviceNet address of the scanner Scanner Signals File A file which defines the layout of the data passed via HSP including signals and the HSP Signature value SRS System Rack Slot See Controller ID Strobed A type of standard I O data communication in which a message solicits a response from each strobed device a multi cast transfer It is a 64 bit message that contains one bit for each slave device on the network Each slave node can return a maximum of 8 bytes in response to the master s strobe System Reaction Time The worst case time from a safety related event as input to the system or as a fault within the system until the time that the system is in the safety state System Reaction Time includes sensor and activator Reaction Times as well as the Controller Reaction Time Target Connections File A file used to pass target connection information for data the user wants to make available from the GuardPLC controller to another safety originator or standard master on the DeviceNet network Timeout Multiplier This value determines the number of messages that may be lost before declaring a connection error Publication 1753 UM002A EN P July 2005 Glossary 4 Publication 1753 UM002A EN P July 2005 Symbols ssf See scanner signals file tcf See target connections file Numerics 1753 CBLDN 2 7 1770 KFD module 1 5
48. ce you must run the Safety Device Verification Wizard to re verify and Safety Lock the device before operating the device in your safety system TIP If none of your devices are password protected or safety locked you can select Download to Network from the Network menu to download your configuration to the network However this process skips devices that are password protected or safety locked Publication 1753 UM002A EN P July 2005 7 8 Associate the Scanner and Controller and Download the DeviceNet Network Configuration Publication 1753 UM002A EN P July 2005 Chapter 8 Develop Your GuardPLC Application To define your application signals and use them in your program logic follow the procedures listed below in order Procedure page 1 Define Signals for Your GuardPLC Application 8 1 2 Create Application Program Logic 8 4 3 Save and Compile Application Logic 8 4 4 Download the Project to the Controller 8 4 Define Signals for Your Once the association between the scanner and controller is established you can configure signals which allow you to use the GuardPLC Application 4 RA safety or standard data in your GuardPLC application Review the guidelines for creating a distinction between safety and standard signals on page 1 4 Define Signals for Safety Data 1 In your RSLogix Guard PLUS project right click on the HSP icon and choose Connect Signals gt Safety Data ARSLogix Guard
49. ce of DeviceNet Safety I O modules can be affected by the e baud rate of the network Lower baud rates mean slower transmissions and slower responses e packet size for the various connections Bigger packets may result in fragmented messages and slower responses than single packet messages but use fewer resources e type and number of connections used Using point to point connections to make multiple connections to an input node uses more resources than a multicast connection e RPI of the devices Lower RPIs consume more bandwidth but lower system reaction time Publication 1753 UM002A EN P July 2005 Before You Begin 1 9 Choose a Communication Rate for the Network The default communication rate for a DeviceNet network is 125K bit s This is the easiest communication rate to use If you choose to use a different communication rate the length of the trunkline and type of cable determine which communication rates your application can support Communication Maximum Distance Cumulative Drop Rate flatcable thickcable thincable Line Length 125K bit s 420 m 1378 ft 500 m 1640 ft 100 m 328 ft 156m 512 ft 250K bit s 200 m 656 ft 250 m 820 ft 100 m 328 ft 78 m 256 ft 500K bit s 75 m 246 ft 100 m 328 ft 100 m 328 ft 39 m 128 ft meat f you change the communication rate of your network make sure that all devices change to the new communication rate Mix
50. ck configuration signature Make non peer to peer connections following steps 2 and 4 in Chapter 5 Then continue with the process described in Chapters 7 8 and 9 Publication 1753 UM002A EN P July 2005 B 12 Configure Peer to Peer DeviceNet Communications Publication 1753 UM002A EN P July 2005 DeviceNet Object Identity Object Safety Supervisor Object DeviceNet Class Codes Appendix C This appendix contains the most commonly used class codes for the 1753 DNSI DeviceNet Safety Scanner for GuardPLC Controllers Name Class Instance Attribute Data Size Access MAC ID 0x03 0x01 0x01 1 byte Get Set Baud Rate 0x03 0x01 0x02 1 byte Get Set SNN 0x03 0x01 0x0B 6 bytes Get Set Name Class instance Attribute Data Size Access Vendor ID 0x01 0x01 0x01 2 bytes Get Device Type 0x01 0x01 0x02 2 bytes Get Product Code 0x01 0x01 0x03 2 bytes Get Revision 0x01 0x01 0x04 2 bytes Get Serial Number 0x01 0x01 0x06 4 bytes Get Product Name 0x01 0x01 0x07 23 bytes Get Oltea imatami Adkine Mem sies Atces Publication 1753 UM002A EN P July 2005 C 2 DeviceNet Class Codes Publication 1753 UM002A EN P July 2005 Single cast Inputs Appendix D Calculate Safety Connection Bandwidth This appendix provides equations for calculating the amount of system bandwidth consumed by an individual safety input or output connection In the equations below
51. 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 ATTENTION e identify a hazard e avoid a hazard e recognize the consequence TAATA Labels may be located on or inside the equipment e g drive or motor to alert people that dangerous voltage may be present BURN HAZARD Labels may be located on or inside the equipment e g drive or motor to alert people that surfaces may be at dangerous temperatures Before You Begin Install the 1753 DNSI Set Up Your DeviceNet Network Table of Contents Preface Who Should Use this Manual 0005 P 1 Purpose of This Manual rs ios 2G A ae se aa eR eT P 1 Related Documentation 3 6 eee 4 ody tea ands 4m 9 we hem P 2 Common Techniques Used in This Manual P 2 Understanding Te
52. ctrical EMG ing Sha dna hay Ae be ORAS Ge el hue hae Pa bit A 2 CCE TTA CALI ONS ry acct e sicdh pied Bee as eee GE nie sind ae Ges A 3 Appendix B Plan Your Peer to Peer Communications B 2 Commission a Peer Scanner n a aaau B 2 Add a Peer Controller sch Po bd aaa B 3 Define Target Connections for Standard and Safety Data B 4 Create Required Sionals 4 g 60 hea a Pees ee eet eS B 5 Define Standard Target Connections B 6 Define Safety Connections 46 4 n dete Pa ed BES ey B 7 Configure Peer to Peer Connections 4 ns 64 ea ey B 8 Publication 1753 UM002A EN P July 2005 Table of Contents 4 DeviceNet Class Codes Calculate Safety Connection Bandwidth Publication 1753 UM002A EN P July 2005 Associate the Peer Safety Scanner and GuardPLC Controllers Page ate de Gene ath do ede on ule Wp eid ae atad tle Se sees Add the Peer Scanner to the Scanlist Configure Safety Connections 0 Appendix C DeviceNet Object igs iecsi ae eed 4 BP Re aa a ew deg RB es Identity COSCE ssh sss ety a seh ab gs Ae Gy had 6 at Yt Sah db jo tat gh he OBE Safety Supervisor Object ates en Hy Re eee RES Appendix D Single cast INOuUts 4 palinas w Chia aon e creche es Y hen a I tO 2 Byle Srm Bh eee vase Beets AMO Gee hehe e o et BLO 2 OMB VieS S sani a4 ae aaa Seas a erent ner Single cast Outputs 4 7 be5 no 5 pg baa eh ey Wags Gk g MEOR BYTES era n e Ak epee ote te aes A a
53. d See the extended error codes on pages 10 7 to 10 8 0002 Resources required for the requested services were unavailable 0003 Invalid value 0004 Internal Object Identifier syntax error See the extended error codes on pages 10 7 to 10 8 0005 Destination unknown class unsupported instance undefined or structure element undefined See the extended error codes on pages 10 7 to 10 8 0006 Packet space is insufficient 0007 Connection was lost 0008 Service is unsupported 0009 An error occurred in a data segment or an attribute value is invalid 000A Attribute list error occurred 000B This state already exists 000C Object state conflict occurred 000D This object already exists 000E Attribute is not settable Publication 1753 UM002A EN P July 2005 10 6 Monitor Status Publication 1753 UM002A EN P July 2005 General Description Status Error Code 00gg 000F Permission denied See the extended error codes on pages 10 7 to 10 8 0010 Device state conflict occurred 0011 Reply will not fit 0012 Fragmentation of a primitive value For example the service specified an operation that is going to fragment a primitive data value such as half a REAL data type 0013 Command data is insufficient 0014 Attribute is not supported 0015 Too much data
54. d or is not configured 1 The device is faulted Faulted Node 0x10 a Array of Get Table BOOL Idle Node 0x11 b Array of Get Table BOOL 0 The device is not in Idle mode or the device is not configured 1 The Device is in Idle mode 1 The bit offset in the table corresponds to the node number For example bit 0 corresponds to node 0 bit 15 corresponds to node 15 For nodes with more than one connection type enabled that is connections with both an input and output connection configured the status bit reflects the logical OR of the status for each configured connection User application program logic only needs to consider status bits associated with nodes that have one or more connections The status bits of nodes without any connections may be ignored The list of configured connections can be obtained from the RSNetWorx for DeviceNet report feature by selecting File gt Generate Report Publication 1753 UM002A EN P July 2005 10 12 Monitor Status Connection Status Signals Each standard status table is presented as a collection of 64 bits contained within 2 DWORD device signals as shown in the table below The left column shows the signal names as they appear in RSLogix Guard PLUS Bit Position 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 19 8 I7 6 5 4 3 12 0 E 5 EX ode E 31 30
55. dPLC controller has been saved Press F1 for Help 2 Plugins a 2 Sea J DNSI project L2P H example 1 L2P H example1 L2P C example1 L3P 2 FirstProject L2P H OPCtest L2P 2 Project1 L2P m Project2 L2P E G RSLogix Guard PLUS Demo gt 4 gt C e TIP Only RSLogix Guard PLUS projects that have at least one resource with HSP communications enabled can be selected b If you have multiple controller resources in your RSLogix Guard PLUS project RSNetWorx prompts you to select the correct resource Select GuardPLC to Associate 2 x Multiple GuardPLC s exist in the RSLogix Guard PLUS project folder Select the controller to associate to this device Controller ID 60000 Cancel 5 RSNetWorx for DeviceNet automatically updates the Controller ID and imports the Target Connections File from the associated RSLogix Guard PLUS project 6 Click OK to establish the association Whenever the safety scanner configuration changes RSNetWorx for DeviceNet automatically generates or updates the Scanner Signals file TIP If RSLogix Guard PLUS is open to the associated project then it automatically imports the Scanner Signals file Publication 1753 UM002A EN P July 2005 7 4 Associate the Scanner and Controller and Download the DeviceNet Network Configuration Manually Associate the Scanner and Controller Publication 1753 UM002A EN P July 2005 If you manually associate the scanner
56. e A ratio of 3 means they are polled on every third cycle etc Advanced Module Settings Clicking on the Advanced button lets you to set the Expected Packet Rate EPR and the Transmit Retries as described below Advanced Module Settings 2 x WARNING Modifying these settings may disrupt network A communication Do not modify unless instructed to do so by a technical support representative Expected Packet Rate E a Transmit Retries Cancel e Expected Packet Rate EPR When the scanner opens a polled or strobed I O connection it uses this value as a maximum timeout Expected Packet Rate with the device If the device does not receive a packet from the scanner within 4 times the EPR value the slave device drops the connection If the scanner does not receive a packet from the slave within 4 times the EPR value it drops the connection and periodically attempts to reopen the connection Publication 1753 UM002A EN P July 2005 5 8 Configure DeviceNet Nodes and Connections When a standard connection is dropped status bits in the scanner identify that the slave is not online Slave behavior when a connection is dropped is a function of the slave device If the slave is an I O device the standard outputs will be cleared held at last state or set to a fault condition refer to the slave device s documentation for actual I O behavior when a connection is dropped When an input connecti
57. e peroo ooo Import Scanner Signals Export Target Connections OK Cancel Apply Help before closing the HSP connection Controller Resend Timeout is the amount of time that the controller waits for the acknowledgement of a message before it resends it Publication 1753 UM002A EN P July 2005 6 4 Create a GuardPLC Project with High Speed Safety Protocol Use the following guidelines when setting the Controller Receive Timeout and Controller Resend Timeout e In environments where no HSP retries are required set the Controller Receive Timeout to the amount of time required for the controller to send the HSP request for the scanner to process the request and for the scanner to send a response back to the controller This value can be determined by observing the Response Time values displayed on the HSP protocol tab of the Resource Control Panel Set the Controller Receive Timeout to be greater than or equal to the maximum value reported plus a margin of safety 3 ms or 10 of the maximum value reported The Controller Resend Timeout should be set to zero e In electrically noisy environments configuring retries on the HSP link may be required Set the Controller Resend Timeout to be equal to or greater than the Max Response Time value reported on the HSP Protocol tab of the Resource Control Panel plus a margin of safety 3 ms or 10 of the maximum value reported To enable a single retry the Controll
58. ed communication rates produce communication errors Set the baud rate of the DeviceNet Safety Scanner using the Node Commissioning tool in RSNetWorx for DeviceNet See Commission All Nodes on page 3 2 The following table lists the most common methods for setting communication rates for other DeviceNet devices Method Description autobaud At power up the device automatically sets its communication rate to the baud rate of the first device it finds on the network The device remains set until it powers up again The network requires at least one device with a fixed communication rate so that the autobaud devices have something against which to set Typically scanners and network interfaces have a fixed communication rate switches or Some devices have switches or a pushbutton that sets the pushbuttons on the communication rate Typically the switch or pushbutton lets you device select either autobaud or a fixed communication rate 125K 250K or 500K bit s The device reads the switch setting at power up If you change the setting you must cycle power for the change to take effect software Some devices require a programming device to set its address and communication rate For example you can use the Node Commissioning tool in RSNetWorx for DeviceNet to set the communication rate of a device Publication 1753 UM002A EN P July 2005 1 10 Before You Begin Publication 1753 UM002A EN P July 2005 Assign a
59. efault only devices with the following status are shown e Verify FAILED e Ready to be verified e Verify not supported These states are described in the following table Status Description Verify FAILED The upload and compare operation indicated that the configuration in the device does not match the configuration in the RSNetWorx for DeviceNet configuration file Ready to be verified The device is not Safety Locked and can be selected for verification Verify not supported The device is not Safety Locked but the device does not support verification via the Safety Device Verification Wizard Consult your user documentation for information on how to verify this device Once the device has been verified it can be Safety Locked by the wizard Publication 1753 UM002A EN P July 2005 9 4 Verify Your DeviceNet Safety Configuration Publication 1753 UM002A EN P July 2005 Click on Next to begin the upload and compare process Safety Device Verification Wizard x Verify Safety Device Configuration 4 From the list select the safety devices you want to verify During the verification process the software will compare the configuration in the safety device to the software s configuration BESE eT evice Conngurations 2d S F 2 of 2 Address 01 1753 DNSI DeviceNet Safety Scanner M F m vy AEE EEL Eee Uploading Scanlist Address 6 Click Next to continue lt Back Next
60. er Receive Timeout must be 2 times the Controller Resend Timeout To enable 2 retries the Conroller Receive Timeout must be 3 times the Controller Resend Timeout e The controllers Communications Time Slice found on the Properties dialog of the controller Resource must be greater than the Controller Receive Timeout to enable proper HSP operation If other protocols are in use on the controller Resource then the Communications Time Slice should be increased to accommodate their use in conjunction with HSP The Maximum Communication Time Slice setting on the Device Properties page should be set to the Maximum Communication Time Slice observed on the Control Panel s Statistics tab plus a margin of safety 6 ms or 10 of the maximum value reported TIP The Controller Id Scanner Id and Scanner Receive Timeout values are shown here for reference These values are set following a successful Scanner Signals File Cssf import process For the import process to succeed the Controller Id must match the System ID SRS of the controller Resource Refer to the GuardPLC Controller Systems User manual publication 1753 UM001 for more information on configuring communications for GuardPLC controllers Publication 1753 UM002A EN P July 2005 Create a GuardPLC Project with High Speed Safety Protocol 6 5 Review the GuardPLC 1 Retrieve or confirm the communication settings by selecting Communication Settings from the Online menu
61. ese 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 United 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 and needs 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 GuardPLC RSLogix Guard PLUS and RSNetWorx are trademarks of Rockwell Automation Inc Microsoft and Windows are either registered trademarks or trademarks of M
62. et Connections file within its project folder When you use the Automatically Update Signals option in RSNetWorx for DeviceNet that software automatically imports any updates when the scanner s property page is displayed You can also manually export the Target Connections file to a specific location at any time by right clicking on the HSP Protocol and selecting Export Target Connections Project Edit Signals Online Windows Help ESP2P project test A Configuration bm 100 peer Resource i Distributed 1 0 Protocols bom HSF Protocol_1 ME Typelnstance Connect Signals gt H BIO GuardPLC 1800 Define Target Connections gt E Bi 60000 Resource Import Scanner Signals f G Distributed 1 0 Protocols 7 af Typelnstance WEEE i ER 10 GuardPLC 1600 New ll Programming Terminal Copy Configure Peer to Peer You must associate target scanners with their GuardPLC controller before you can configure the peer to peer standard and safety Connections connections Associate the Peer Safety Scanner and GuardPLC Controller Follow the procedure in Chapter 7 to associate the peer safety scanner to its GuardPLC controller and configure the peer scanner s GuardPLC connection View the application signals imported via the association by clicking on the View Target Connections button on the GuardPLC tab in RSNetWorx for DeviceNet The
63. et node s configuration configuration Standard Data that one other Data that one or more other Scanner is the slave standard DeviceNet master can write on the scanner s slave mode outputs The data signals are selected in RSLogix Guard PLUS standard DeviceNet master can read from the scanner s slave mode inputs The data signals are selected in RSLogix Guard PLUS Standard DeviceNet Explicit Messaging connections are limited to read only access to safety data ATTENTION A To maintain the safety integrity level SIL of your system you must ensure that safety data read by Explicit Messaging is used only as standard data in your application How to Distinguish Between Standard Data and Safety Data in RSLogix Guard PLUS In the HSP Signal Connection dialogs in RSLogix Guard PLUS signals that are transferred over safety connections are shown in white text on a red background Signals transferred over a standard connection are shown in blue text on a gray background Before You Begin 1 5 Role of RSNetWorx for DeviceNet and RSLogix Guard PLUS Since this colorization only applies to the Connect Signals dialogs available from the HSP protocol context menu we strongly recommend that when using both standard and safety signals in your application you use a naming convention to visually distinguish between standard and safety signals throughout the RSLogix Guard PLUS programming environment
64. ety Safety Standard Standard Standard Safety Standard Standard Standard Trotirtia Only safety signal data transmitted over safety connections may be used as safety data in safety application logic Publication 1753 UM002A EN P July 2005 1 4 Before You Begin Publication 1753 UM002A EN P July 2005 How Data Tables Work To exchange data the GuardPLC controller and the 1753 DNSI use two pairs of data tables one pair for safety input and output data and one pair for standard input and output data Connection Type Scanner is the originator Scanner Inputs Data the scanner reads from its target nodes The data layout is defined by the target node s configuration Scanner Outputs Data the scanner writes to its target nodes The data layout is defined by the target node s configuration Scanner is the Safety Data that one other CIP Data that one or more other target Safety originator may write CIP Safety originators may on the scanner s target read from the scanner s output connection point The target input connection data signals to be written point The data signals to be are selected in RSLogix read are selected in RSLogix Guard PLUS Guard PLUS Scanner is the Data the scanner reads from Data the scanner writes to master its standard DeviceNet its standard DeviceNet slaves The data layout is slaves The data layout is defined by the target node s defined by the targ
65. f any safety reset action Configuration Check this checkbox to reset the device s configuration owner Owner The next device that attempts to configure the device following the safety reset becomes the configuration owner Output Check this checkbox to reset any existing output connection Connection owners The next device that accesses an output connection Owner s point following the safety reset becomes the output connection owner Password Check this checkbox to reset the device password You must know the current device password to reset a password from the Reset Safety Device dialog Address Check this checkbox to reset the device s software configured node Address to 63 NOTE If the device s node Address has been set using DIP switches the reset operation has no effect on the node Address Baud Rate Check this checkbox to reset the device s baud rate to 125 kbps NOTE If the device s baud rate has been set using DIP switches the reset operation has no effect on the baud rate Safety Network Check this checkbox to reset the device s Safety Network Number Number Set Up Your DeviceNet Network 3 5 3 Click on the Reset button 4 If the device is Safety Locked you are prompted to first unlock the device ATTENTION Once unlocked the device cannot be relied upon to perform safety operations A You must test and verify the device s operation and run the Safety Device Verification Wizard
66. fety scanner only supports the polled connection on its slave mode interface 4 Specify the Poll Rate either Every Scan or Background Publication 1753 UM002A EN P July 2005 B 10 Configure Peer to Peer DeviceNet Communications Publication 1753 UM002A EN P July 2005 Configure Safety Connections To configure a safety connection to the peer scanner 1 On the Device Properties dialog select the Safety Connections tab LC 1753 DNSI DeviceNet Safety Scanner Input Output Summary GuardPLC General Safety Module Safety Connection Scanlist Configured Safety Connections s01 1791DS 1B12 12Pt E IN Safety 2Bytes 10ms 60 0 Signat 1 iA 02 1791DS IB4XOW4 2 Right click on the peer scanner and select Add Connections to display the available connections 3 Configure the safety connection zixl Target Device jo Peer 1753 DNSI DeviceNet Safety Sca IN Safety Target Input fix Details Connection Type Multicast z Configuration Do not check configuration signature x Connection Name Communication Parameters Requested Packet Interval RPI fio a ms Connection Reaction Time Limit CRTL jeno ms Advanced co e Configure Peer to Peer DeviceNet Communications B 11 For a description of the Safety Connection parameters see pages 5 4 to 5 5 TIP For peer to peer safety connections you can only select Do not che
67. figure the DeviceNet Safety Scanner s Safety Connections 5 3 3 Configure DeviceNet Standard Slave 1 0 Nodes 5 6 4 Configure the DeviceNet Safety Scanner s Standard Connections 5 6 5 Configure GuardPLC Controller Settings 5 12 Each safety device has a unique Configuration Signature which identifies its configuration to ensure 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 and is set automatically by RSNetWorx for DeviceNet when a configuration update is applied to the device The Configuration Signature is found on the Safety tab of the Device Properties dialog Parameters 1 0 Data EDS File General Safety Safety Configuration Safety 1 0 This safety device is not safety locked After you have configured the device run the Safety Device Verification Wizard to set the device to the safety locked state Safety Network Number 2F20_0436_SA9A Configuration Signature ID rabs_Aa32 Copy Signature Date fi 11 2005 Time fi 37 19 566 PM Publication 1753 UM002A EN P July 2005 5 2 Configure DeviceNet Nodes and Connections The Configuration Signature is read during each browse and whenever the Device Properties dialog is launched while the software is in Online mode RSNetWorx for DeviceNet compares the Configuration Signature in the software offline dev
68. g the correct cable Configure a Driver for the Network 1 Start RSLinx software 2 Click on the Configure Driver button Publication 1753 UM002A EN P July 2005 3 2 Set Up Your DeviceNet Network Commission All Nodes Publication 1753 UM002A EN P July 2005 3 Pull down the list of Available Driver Types and add the driver for your network For this network Select this driver RS 232 RS 232 DF1 Devices EtherNet IP Ethernet devices DeviceNet DeviceNet drivers 4 Configure the driver The settings you make are dependent upon the network you choose and whether you are using a communication card or interface module Make Sure the Driver Works 1 Check the Configure Drivers dialog to make sure that the driver is running 2 Close the dialog 3 Open the RSWho window 4 Double click on the driver to see the network Before you can use RSNetWorx for DeviceNet s Node Commissioning tool your computer and your DeviceNet devices must be connected to the DeviceNet network Use the Node Commissioning tool in RSNetWorx for DeviceNet to set the node address and or baud rate of the DeviceNet Safety Scanner and other DeviceNet devices Follow the guidelines on page 1 10 when selecting node addresses for your DeviceNet network TIP You can set the node address of a DeviceNet Safety I O module by setting the rotary switches to a value between 0 and 63 Or set the switches to a value between 64 and 99 to al
69. h the scanner connects as well as data areas allocated to RSLogix Guard PLUS application signals that are identified in the controllers Target Connections file tcf and made available to DeviceNet peers that connect to the scanner 1 Not all standard 1 0 devices may provide these detailed O assembly definitions Contact your device vendor for updated EDS files Standard devices that do not support these detailed I O assembly definitions may include an UNKNOWN data type Use the Define Data button on the Standard Data Signal Connections screen in RSLogix Guard PLUS to define these data types Publication 1753 UM002A EN P July 2005 7 2 Associate the Scanner and Controller and Download the DeviceNet Network Configuration Target Connections File Automatically Update Signals Publication 1753 UM002A EN P July 2005 The Scanner Signals File separates data transferred on safety connections from data transferred over standard connections Signals created in the RSLogix Guard PLUS Signal Editor can be assigned to scanner I O data signals allowing them to be used by the GuardPLC application logic RSLogix Guard PLUS generates the Target Connections File Ctcf to inform RSNetWorx for DeviceNet which application signals should be exposed on the scanner s DeviceNet slave mode or target interfaces As described in the Scanner Signals Files section RSNetWorx for DeviceNet chooses locations for these target signals within the d
70. he safety state and standard outputs to follow the behavior dictated by their configuration The Max Scanner Response Time should be set to a value that includes the maximum observed statistical scanner response time over several hours of operation plus a Margin of Safety equal to 3 ms or 10 of the maximum observed scanner response time When online you can view the Minimum Maximum and Average Observed Scanner Response Times by selecting the Statistics button Publication 1753 UM002A EN P July 2005 5 14 Configure DeviceNet Nodes and Connections Publication 1753 UM002A EN P July 2005 Create or Open a GuardPLC Project Chapter 6 Create a GuardPLC Project with High Speed Safety Protocol To configure the GuardPLC controller to communicate with the DeviceNet Safety Scanner for GuardPLC Controllers follow the procedures listed below in order Procedure page 1 Create or Open a GuardPLC Project 6 1 2 Add High Speed Safety Protocol to the GuardPLC Controller Resource 6 3 3 Review the GuardPLC Controller s Communication Settings 6 5 For detailed information on creating a GuardPLC controller project in RSLogix Guard PLUS refer to the GuardPLC Controller Systems User Manual publication number 1753 UMO001 TIP To optimize performance and minimize compilation time create and store your projects on a local drive 1 In RSLogix Guard PLUS either open an existing GuardPLC 1600 or GuardPLC 1800 controller projec
71. ice Controller ID SRS A value required to uniquely identify a particular GuardPLC controller within a network of controllers Refer to the GuardPLC Controller Systems User Manual publication number 1753 UMO001 Controller Receive Timeout The amount of time that the controller waits to receive an HSP response from the scanner before closing the HSP connection Controller Resend Timeout The amount of time that the controller waits for the acknowledgement of a message before it resends it Cyclic A type of standard I O data communication in which the interface module can send and receive data with slave devices that support the cyclic feature Data is only sent at the user specified rate Electronic Data Sheet EDS A vendor supplied template that RSNetWorx for DeviceNet uses to display the configuration parameters I O data profile and connection type support for a given DeviceNet or DeviceNet Safety module Explicit Messaging A type of messaging used for lower priority tasks such as configuration and status monitoring Publication 1753 UM002A EN P July 2005 Glossary 2 Publication 1753 UM002A EN P July 2005 Heartbeat Rate Devices that are configured for change of state data can also send a heartbeat signal to keep the connection active during periods when the data is not changing HSP Signature A read only value that represents the data exchanged between the GuardPLC controller and the 1753 DNSI
72. ice configuration file to the Configuration Signature in the online device If the Configuration Signatures do not match you are prompted to upload the online device configuration or download the software device configuration to resolve the mismatch Configure DeviceNet Safety 1791DS DeviceNet Safety 1 0 Module Parameters 1 0 Target Nodes To configure your module double click on the module in the graphic view or right click on the module and select Properties Safety Input Output and Test Parameters Safety parameters are configured using the Safety Configuration tab on the Module Properties page Parameters 1 0 Data EDS File General Safety Safety Configuration Safety 1 0 Select the parameter that you want to configure and initiate an action using the toolbar IV Groups R A m gt Monitor 3 Parameter Input Points 00 01 54 Input 00 01 Operation Type Single 5 Input 00 01 Operation Disc 0x10 ms Current Value 8 Input 00 Mode Not Used Icon Description 9 Input 00 Test Source None AAA TREE IT TPE CNS TO pP z Indicates that this parameter is read 6 Input 00 Off gt On Delay Time 0 ms only Input 00 On gt Off Delay Time Oms Indicates that this parameter is a 12 Input 01 Mode Not Used scaled value 13 Input 01 Test Source None 10 Input 01 OFf gt On Delay Time Oms P Indicates that this parameter is linked 11 Input 01 On gt Off Delay Time Oms to another parameter in the parameter
73. iceNet Verify that all your nodes are visible Save your project in RSNetWorx for DeviceNet Publication 1753 UM002A EN P July 2005 3 4 Set Up Your DeviceNet Network Safety Reset Optional Publication 1753 UM002A EN P July 2005 If you need to reset the safety device s attributes to the out of box default state you can do so via the Reset Safety Device dialog You can reset the attributes shown on the Reset Safety Device dialog by checking their associated checkbox Leaving an attribute checkbox blank preserves that attribute s setting during the safety reset operation Reset Safety Device 02 1753 DNSI DeviceNet Safety Scanner 2 xi A Resetting device attributes will cause the selected attribute s to return to their factory default settings Check the boxes below to select which attributes to reset in the device v Configuration Resetting the device will always reset its configuration I Address If resettable V Output Connection Owner s Baud Rate If resettable T Password I Safety Network Number Cancel Help 1 Open the Reset Safety Device dialog by clicking on the device in the RSNetWorx for DeviceNet graphic view and selecting Reset Safety Device from the Device menu 2 Check the attributes you want to reset Attribute Configuration Reset Behavior The configuration checkbox is always checked to indicate that the configuration of the device is erased as a result o
74. icrosoft Corporation in the United States and or other countries DeviceNet is a trademark of Open DeviceNet Vendor Association All other trademarks are the property of their respective holders and are hereby acknowledged Rockwell Automation 777 East Wisconsin Avenue Suite 1400 Milwaukee WI 53202 5302 USA Tel 1 414 212 5200 Fax 1 414 212 5201 Headquarters for Allen Bradley Products Rockwell Software Products and Global Manufacturing Solutions 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 SA NV 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 Headquarters for Dodge and Reliance Electric Products Americas Rockwell Automation 6040 Ponders Court Greenville SC 29615 4617 USA Tel 1 864 297 4800 Fax 1 864 281 2433 Europe Middle East Africa Rockwell Automation Herman Heinrich Gossen Strasse 3 50858 K ln Germany Tel 49 0 2234 379410 Fax 49 0 2234 3794164 Asia Pacific Rockwell Automation 55 Newton Road 11 01 02 Revenue House Singapore 307987 Tel 65 6356 9077 Fax 65 6356 9011 Publication 1753 UM002A EN P July 2005 Copyright 2005 Rockwell Automation Inc All rights reserved
75. ition G 1 set 6 3 6 4 cooling 2 2 cos See change of state create a GuardPLC project 6 1 create a scanlist 5 8 create a signal 8 2 create application program logic 8 4 cyclic definition G 1 messages 1 2 cyclic messages 1 3 Publication 1753 UM002A EN P July 2005 2 Index D data tables 1 4 7 1 7 2 data types B 2 default module defaults button 5 6 device status monitoring 10 1 Safety Device Verification Wizard 9 1 verification 9 3 DeviceNet connections 2 6 DeviceNet network configuration 3 1 configure a driver 3 1 connecting 3 1 DeviceNet Safety 1 0 configuration signature 5 1 set node address 3 2 DeviceNet Safety Scanner See scanner display status 10 2 download DeviceNet configuration 7 5 rats download project to controller 8 4 driver types 3 2 duplicate node failure 10 2 E E ee 10 4 edit I 0 parameters 5 9 EDS See electronic data sheet electronic data sheet definition electronic key 5 9 electrostatic discharge prevent 2 2 environment and enclosure 2 1 EPR See expected packet rate expected packet rate 5 7 default 5 8 explicit messaging 1 4 definition G 1 export scanner signals 7 4 extended error code 10 4 10 7 Publication 1753 UM002A EN P July 2005 F faulted must issue safety reset 10 3 features 1 7 G G gg 10 4 grounding 2 4 GuardPLC controller communication settings 6 5 configuration 6 1 properties 6 2 GuardPLC project create 6 1 GuardPLC tab associate a
76. ject Publication 1753 UM002A EN P July 2005 6 6 Create a GuardPLC Project with High Speed Safety Protocol Publication 1753 UM002A EN P July 2005 Chapter 7 Scanner Signals File Associate the Scanner and Controller and Download the DeviceNet Network Configuration To allow the scanner and the controller to communicate you can associate their configurations using the Automatically Update Signals feature or you can manually manage the association Both options are found on the GuardPLC tab of the Scanner Properties page in RSNetWorx for DeviceNet TIP We recommend using the Automatically Update Signals feature because it eliminates the need to manually import signals and export connections after every configuration change Once you ve made the association between the scanner and controller download the DeviceNet network configuration This chapter covers e the Scanner Signals File e the Target Connections File e the Automatically Update Signals procedure e the manual association procedure e downloading the DeviceNet network configuration The Scanner Signals File ssf contains standard and safety level input and output data RSNetWorx for DeviceNet creates a Scanner Signals File to define the layout of the data tables exchanged with the controller via HSP including detailed signal information and the HSP Signature The data table contents include the data areas allocated to the DeviceNet I O nodes to whic
77. lication prior to safety locking your devices Refer to the GuardPLC Controller Systems Safety Reference Manual publication number 1753 RM002 for information on verification testing for safety applications The Safety Device Verification Wizard accessed from RSNetWorx for DeviceNet guides you through the process of verifying the configuration of your safety devices and provides the means for Safety Locking those devices The verification process includes upload and comparison of the configuration stored in the device and the configuration stored in the RSNetWorx for DeviceNet configuration file The configuration is displayed in a report to facilitate visual verification and record keeping IMPORTANT Some devices may not support verification by the Safety Device Verification Wizard Consult the user documentation to determine the method required for verifying these devices To run the Safety Device Verification Wizard select Network gt Safety Device Verification Wizard The Welcome page which describes the verification process appears Click Next When the Safety Device Verification Wizard browses the network it checks the safety status of the devices on the network to determine if the devices can be verified If any devices are in a state that prevents the wizard from continuing the verification process the Unable to verify the listed devices page Publication 1753 UM002A EN P July 2005 9 2 Verify Your Device
78. low the node address to be set using the Node Commissioning tool in RSNetWorx for DeviceNet Refer to the DeviceNet Safety I O Modules User Manual publication number 1791DS UM001 for information on commissioning 1791DS I O modules Set Up Your DeviceNet Network 3 3 Browse the Network To use the Node Commissioning tool 1 Within RSNetWorx for DeviceNet select Tools gt Node Commissioning Click on the Browse button on the Node Commissioning dialog to select a device by browsing the network Select the DeviceNet network in the left panel Select the device you want to commission in the right panel and click OK If you want to change the baud rate of the device select the desired value Trotter hia The baud rate of the device will not update until the device is power cycled or reset On the Node Commissioning dialog type the new address for the device and click Apply A confirmation message tells you if the operation was successful eat T0 change the node address of a Safety device you must first reset the SNN to an uninitialized state by selecting the SNN and performing a Safety Reset as described on page 3 4 Browse the network by clicking on the online button a On the Browse for Network dialog select the DeviceNet network Wait for the Browse Network operation to complete As the network is browsed all of the devices on the network will show up in RSNetWorx for Dev
79. ls menu amp Signal Editor Tye Retain Constant Description Init Value 2 Click on the New Signal button to add new signal 3 Name the signal and configure its properties amp Signal Editor New Signal Delete Signal Help Tipe Retain Corstant_ Desorption ints std_p2pslave BOOL safe_p2ptarget BOOL 4 Leave the Signal Editor open For more information on using the Signal Editor refer to the GuardPLC Controller Systems User Manual publication 1753 UM001 Publication 1753 UM002A EN P July 2005 B 6 Configure Peer to Peer DeviceNet Communications Publication 1753 UM002A EN P July 2005 Define Standard Target Connections To define the signals that will be available to another standard master on the network 1 Right click on the HSP Protocol instance of the target resource and select Define Target Connections gt Standard Data JEJRSLogix Guard PLUS Hardware Management Project Edit Signals Online Windows Help Ts P2P project test l A Configuration X 100 peer Resource 95 Distributed 1 0 E3 Protocols JF Typelnstance n z 0 GuardPLC 1800 SoH MaRS ees Safety Data RK 60000 Resource Import Scanner Signals Standard Data E Distributed 1 0 Export Target Connections E Protocols Validate GE Ty
80. n Address to Each Device To communicate on the DeviceNet network each device requires its own address Follow the recommendations below when assigning addresses to the devices on your network Give this device This address Notes scanner 0 If you have multiple scanners give them the lowest addresses in sequence any device on your network 1 to 61 except the scanner Gaps between addresses are allowed and have no effect on system performance Leaving gaps gives you more flexibility as you develop your system RSNetWorx for DeviceNet 62 workstation If you connect a computer directly to the DeviceNet network use address 62 for the computer or bridging linking device Leave address 63 open This is where a non commissioned node typically enters the network no device 63 Standard DeviceNet assigns communication priority based on the device s node number The lower the node number the higher the device s communications priority This priority becomes important when multiple nodes are trying to communicate on the network at the same time DeviceNet Safety nodes have additional priority on the network regardless of node number DeviceNet Safety communications from devices with lower node numbers have priority over DeviceNet Safety communications from devices with higher node numbers Chapter 2 Install the 1753 DNSI General Safety Information ATTENTION A Safety Applications Pers
81. n the Review hyperlink in the Report column to launch the device s HTML report in your default browser 2 Click the Review All button to generate an HTML verification report for all of the devices listed If a device s status is Verify FAILED more information is provided in the verification failure report 3 Review and print the verification reports for your records Tate You must review the device configurations and record the configuration signatures prior to operating a safety application Publication 1753 UM002A EN P July 2005 9 6 Verify Your DeviceNet Safety Configuration Lock Safety Devices Publication 1753 UM002A EN P July 2005 IMPORTANT Before you lock your safety device configurations you must perform all of the verification steps required for your application 1 Choose which devices to Safety Lock by selecting the checkbox in the Lock column for each device that is ready to be Safety Locked Safety Device Yerification Wizard x Lock Safety Devices From the list below select the devices that you want to set to the safety locked state DC_Input M Lock Ready to be Safety Locked S 03 1791D5 IB8x0B8 8Pt 8Pt Safety DC_Input M Lock Ready to be Safety Locked S 02 1791DS IB12 12Pt Safety DC_Input I acknowledge that have reviewed the configurations of the safety devices as well as tested their operation EENEN Next Cancel Help 2 You mus
82. nd password on the login screen The default username is Administrator with no password Click OK TIP Enter Ctrl A to automatically fill in the default username and access type Develop Your GuardPLC Application 8 5 4 Click the download icon and confirm the action by selecting Yes to the warning prompt Control Panel GPLC 1600_1 TIP If this is the first time the application has been downloaded you may want to adjust the timing parameters artificially high and allow the project to run for several hours This lets you gather statistics on the system s operation before refining the timing parameters Set this parameter Using Controller Resend Timeout Controller Receive Timeout smn Tine Slice RSLogix Guard PLUS Hardware Management Watchdog Time Safety Time Scanner Receive Timeout Max Scanner Response Time RSNetWorx for DeviceNet Individual Safety Standard connection Timing parameters Publication 1753 UM002A EN P July 2005 8 6 Develop Your GuardPLC Application Publication 1753 UM002A EN P July 2005 Start the Safety Device Verification Wizard Determine if Devices Can Be Verified Chapter 9 Verify Your DeviceNet Safety Configuration IMPORTANT Before running the Safety Device Verification Wizard you should browse and upload your network and test the safety devices on your network to ensure that they are operating properly You must fully test your app
83. nded Action ee 82 Error detected in sequence of fragmented 1 0 e Check scan list device to make sure that its input and output messages from device data sizes are correct e Check the configuration of the device 83 Device returns error responses when the e Check the accuracy of the scan list scanner attempts to communicate with it e Check the configuration of the device The device may be in another scanner s scan list e Cycle power to the device 84 Scanner is initializing the DeviceNet network None This code clears itself once the scanner attempts to initialize all the devices on the network 85 During runtime the device is sending the wrong Contact Rockwell Automation support See the back of this size of data publication 86 Device is in idle state mode not producing e Check the configuration and status of the device data while the scanner is in run mode e f you set up an interlock between 2 scanners controllers make sure both scanners are in run mode 92 The DeviceNet cable is not supplying power to e Make sure the network has 24V de power the communication port e Check the connection to the device 95 The firmware of the device is currently being None Do not disconnect the device while the update is in progress updated You will lose any existing data in the device s memory Safety Connection General Status Error Codes General Status Error Code 00gg 0001 Description Connection failure occurre
84. ner communicates with safety devices via cyclic messages only You configure input and output connections in the DeviceNet safety scanner to transfer input and output data to and from DeviceNet safety I O modules and the GuardPLC controller The scanner can make data available to other DeviceNet scanners using Target connections When Target connections are enabled the safety scanner looks like a standard I O device that can be added to another scanner s scanlist or a safety target device allowing another safety scanner to connect to the safety data by adding a safety connection This allows for the transfer of data signals between two GuardPLC controllers for safety interlocking and distributed safety control Standard data signals can also be exchanged with PLCs HMIs or a ControlLogix system with a 1756 DNB scanner on the DeviceNet network For more information on Target connections see Appendix B Understand Data Signals In order to understand how to use data signals from the safety scanner in your GuardPLC application logic you must know e whether the signal data is regarded as safety or standard data in the end device and e whether the signal data was transferred over a safety connection or a standard connection The following table defines permitted uses of safety and standard signals based on connection and signal type End Device Signal Connection Type Permitted Use in Application Definition Safety Saf
85. nstraints setting the RPI is usually sufficient However for more complex requirements use the Advanced button to further adjust the timing values affecting the Connection Reaction Time Limit as described below 6 Set the Advanced Safety Connection Properties if required Advanced Safety Connection Properties 2 x WARNING A Modifying these settings may disrupt network communication Refer to the safety manual and or contact technical support before modify these values Requested Packet Interval RPI 10 a Timeout Multiplier 2 Network Delay Multiplier 200 Z of RPI Connection Reaction Time Limit CRTL 40 0 ms Request target device to allocate message IDs J Cancel Help e 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 indicates that 1 message may be lost as long as at least 1 message is received in 2 times the RPI 2 x RPD e Network Delay Multiplier The Network Delay Multiplier defines the message transport time that is enforced by the communications protocol The Network Delay Multiplier specifies the round trip delay from the producer to the consumer and back to the
86. ntation Flectronic Key The electronic key is used to ensure that a particular slave device always matches the intended device when the scanner initiates a connection to it When one of the devices in the Scanlist section is highlighted these boxes may be checked to indicate to what extent the key parameters must match the actual device on the network A match of just Device Type can be selected or the additional parameters of Vendor ID and Product Code may be incrementally added Publication 1753 UM002A EN P July 2005 5 10 Configure DeviceNet Nodes and Connections Publication 1753 UM002A EN P July 2005 Should the scanner detect a mismatch with any of the key parameters checked an Electronic Key failure status code 73 will occur for that slave device and the scanner will abort the connection establishment process Configure Standard Inputs The Input tab lets you define how standard data from all of the scanner s slave devices are mapped into the input image of the controller 5 x 1753 DNSI DeviceNet Safety Scanner 2 x General Safety Module Safety Connection Scanlist Input Output Summay GuadPLC 4 03 17344B2 C COS 1 i i Input Value 0 1 bit s Input Value 1 1 bit s uma lt Not Used gt 6 bit s Advanced Memory Standard Input 1 Start Byte 0 A S oe A The graphical window at the top shows each device s node number c
87. ntrol a controller based system via 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 Failure per Hour The probability of a system to have a dangerous failure occur per hour Rx Receive SNN Safety Network Number A unique number that identifies a safety network or safety sub net across all networks in the safety system Tx Transmit Publication 1753 UM002A EN P July 2005 4 Preface Publication 1753 UM002A EN P July 2005 Safety Concept Chapter 1 Before You Begin This chapter provides an overview of communication between the 1753 DNSI and the GuardPLC controller Before configuring your 1753 DNSI module you must understand e the safety concept of the system e the data exchange between the GuardPLC controller and DeviceNet devices through the 1753 DNSI module e the roles of RSNetWorx for DeviceNet and RSLogix Guard PLUS software in the safety system e the features of the DeviceNet Safety Scanner e the physical layout of your network The DeviceNet Safety Scanner for GuardPLC Controllers is certified for use in GuardPLC safety applications up to and including Safety Integrity Level SIL 3 according to IEC 61508 and Category CAT 4 according to EN 954 1 in which the de energized state is the safety state IMPORTANT For SIL 3 and CAT 4 safety system requirements including proof tes
88. ny target connections defined in RSLogix Guard PLUS It is passed to RSLogix Guard PLUS via the Scanner Signals File The HSP signature changes only when a modification occurs in the layout of the signals exchanged between the controller and scanner Configure DeviceNet Nodes and Connections 5 13 Scanner Receive Timeout The Scanner Receive Timeout is the amount of time in milliseconds that the scanner waits for a request from the GuardPLC controller before timing out the HSP connection If the scanner does not receive a message from the GuardPLC controller within this time all output connections are transitioned to the idle state causing the safety outputs to transition to the safety state and standard outputs to follow the behavior dictated by their configuration Set the Scanner Receive Timeout equal to the Watchdog Timeout specified on the Properties dialog of the controller resource in RSLogix Guard PLUS Hardware Management Refer to the GuardPLC Controller Systems User Manual publication number 1753 UMO001 for information on setting the Watchdog Time Max Scanner Response Time The Max Scanner Response Time is the maximum amount of time Gin milliseconds allotted for the scanner to process an HSP request from the controller and then format and send a proper response If the scanner cannot respond within this time frame then all output connections transition to the idle state causing the safety outputs to transition to t
89. odes The HSP port lets you communicate with a single GuardPLC 1600 or 1800 controller via a 1753 CBLDN cable Publication 1753 UM002A EN P July 2005 2 6 Install the 1753 DNSI Front View Bottom View HSP Port e Allen Bradley Guard PLE et De Safety S 1753 DNSI DewiceNet na Ha DeviceNet Safety Port DeviceNet Connections Wire the DeviceNet Connector Use an open style 5 or 10 position linear plug to connect to the DeviceNet network IMPORTANT Manes detailed DeviceNet connection information refer to the DeviceNet Cable System Planning and Installation Manual publication DN 6 7 2 Also refer to the Industrial Automation Wiring and Grounding Guidelines publication 1770 4 1 Wire the connector according to the following illustrations DeviceNet cablez Connect To Red Wire V White Wire CAN High Bare Wire Shield Blue Wire CAN Low Black Wire V 5 position 10 position linear plug linear plug Publication 1753 UM002A EN P July 2005 Install the 1753 DNSI 2 7 Connect to the DeviceNet Network Attach the connector to the module s DeviceNet port Tighten the screws on the connector to 0 6 to 0 7 Nm 5 to 6 in Ib High speed Safety Protocol HSP Connections The module ships with the cable used to connect its HSP port to the GuardPLC controller s COMM3 ASCH HSP port The minimum bend
90. oes not match e Make sure that the correct device is at this address electronic key in scanner e Make sure that the device matches the specified electronic key vendor product code product type 75 Either or both of the following Check that the device has e The device does not have a scan list e scan list e The device has not received l e properly wired connection to the network communication from any other device 76 No direct network traffic for scanner None The scanner hears other network communication but does not hear any directed to it 71 During initialization the data size expected by Check the device and the scan list for the correct input and output the device does not match the scan list entry size for the device 78 Device is not communicating or communication e Check that the device has a properly wired connection to the is intermittent network e Check that the device has power e f the device is polled make sure the interscan delay is long enough for the device to return its data 79 Scanner has failed to transmit a message e Make sure that your scanner is connected to a valid network e Check for disconnected cables 80 Scanner is in idle mode 1 Put controller in run mode 2 Make sure 1753 CBLDN is connected properly 3 Make sure the scanner and the controller have the same HSP signature Publication 1753 UM002A EN P July 2005 Monitor Status 10 5 Status Code Description Recomme
91. of HSP DeviceNet Safety and standard connections and the DeviceNet interface via connection status bits and the corresponding GuardPLC application signals LED Status Indicators The scanner has 3 LEDs which allow you to monitor module DeviceNet network and High Speed Protocol HSP status LED Module Status 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 or the device needs commissioning due to configuration or unique node identifier missing incomplete or incorrect Network Status Off Device is not online or may not have DeviceNet network power Green On Device is online one or more connections are established Green Flashing Device is online no connections established Red Flashing Communication timeout Red On Communication failure The device has detected an error which has prevented network communication Red Green Flashing The SNN is being set Publication 1753 UM002A EN P July 2005 10 2 Monitor Status Alphanumeric Display Display A XX LED Color State Description Off The module has not received any messages on the serial interface Green On The module is transmitting data over the serial ep communication in
92. omputer to the DeviceNet Network 3 1 Configure a Driver for the Network 3 1 Make Sure the Driver Works oa ee eae Oe ees 3 2 Commission All Nodes naana aaae 3 2 Browse the Network 2 00 0 aana a aaa 3 3 Safety Reset Opona cae veo bers eee eee iy es 3 4 Set Passwords Optional 4 dsleuss amp Pe eine ae Pees 3 5 Set or Change a Password soa ey heehee od Ba ety 3 5 Publication 1753 UM002A EN P July 2005 Table of Contents 2 Manage the Safety Network Number Configure DeviceNet Nodes and Connections Create a GuardPLC Project with High Speed Safety Protocol Associate the Scanner and Controller and Download the DeviceNet Network Configuration Publication 1753 UM002A EN P July 2005 To set a password for a module i 24 456725 0808045 3 5 Forgotten Passwords Pee bs a ee Gk oe od ORK CHS 3 6 Chapter 4 SNN Formats C1465 ee a BR EAS Ra ee a 4 1 Time based SNN Recommended 4 1 Manual SNN foe Goon et ed Fae boy Be bot ee eG Res 4 2 Assignment of THE SNIN fours aioe Gadus wed a aves te ek 4 2 Automatic Time based naana aaa aaa 4 2 Manual epeei ae eama n p a aa a 48 Gite eap ahnt 4 3 Set the SNN in All Safety Nodes onnaa anaana 4 3 SNN Mismatch 2 gases an vibes tee wee ee ees 4 5 Safety Network Number Mismatch Dialog 4 5 SNN and Node Address Changes 0005 4 6 Chapter 5 Configuration SIOMAtUTE Saco Skea eae tA A 5 1 Configure
93. on is dropped the scanner sets the corresponding data in the data tables sent to the GuardPLC controller via the HSP connection to the safety state 0 The EPR default value is 75 milliseconds meata Changing the EPR number should be done carefully because it effects how long it takes the scanner to detect a missing device e Transmit Retries Transmit Retries specifies the number of times the scanner attempts to retransmit a change of state or cyclic message that has not been acknowledged by the slave device before dropping the connection Create a Scanlist The scanlist defines the standard devices nodes with which the scanner is configured to exchange I O data Publication 1753 UM002A EN P July 2005 5 x 1753 DNSI DeviceNet Safety Scanner 2 x GuardPLC Scanlist Input Output Summary General Safety Module Safety Connection Scaniist i 03 17341B2 C 2pt DC In 04 1734 0A2 B 2pt AC Available Devices s 01 1791DS 1B12 12Pt Sa SA02 1791DS IB4xOW4 4 gt El I Node Active f Electronic Key IV Device Type IV Vendor Iv Br a Code Hi VISION To r higher IV Automap on Add Upload from Scanner Configure DeviceNet Nodes and Connections 5 9 Available Devices These are the devices on the network that have the ability to be standard slave I O devices The DeviceNet Safety Scanner as well as any other scanners that have been c
94. onfigured to support a standard slave mode interface will also appear in this list Slave capable devices do not have to be used as slave I O by a scanner They may alternately be used as slave I O by another scanner on the same network or they may have dual functionality Scanlist These devices have been assigned to be slave I O to this scanner The outputs of a slave device on DeviceNet can only be owned by one master at a time Data mappings for each device in the scanlist are configured using the input and output tabs Add an available device by selecting the device and clicking on the add arrow gt The double arrow gt gt adds all the available devices to the scanlist It is not necessary to enter safety nodes into the safety scanner s scan list All safety connections are configured on the Safety Connections tab You only need to put a safety device into the safety scanner s scanlist if you are communicating with that device via a standard connection and exchanging standard data with it Automap on Add Automap allows a slave s I O to be automatically mapped into the scanner s input or output image tables when the slave device is added to the scanlist DO NOT check this box if you intend to map a slave device into a particular input or output memory location Edit O Parameters These parameters will vary depending upon the slave device Information on configurable parameters is usually provided in the device s docume
95. onnel responsible for the application of safety related Programmable Electronic System PES shall be aware of the safety requirements in the application of the system and shall be trained in using the system ATTENTION A Environment and Enclosure This equipment is intended for use in a Pollution Degree 2 industrial environment in overvoltage Category II applications as defined in IEC publication 60664 1 at altitudes up to 2000 meters 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 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 enclo
96. oosing the Connection Name Select a type of connection either Multicast Gnput connections only or Point to point input or output connections Select Configuration signature must match This selection directs the scanner to ensure that the target safety device contains the correct configuration before opening the safety connection meat 1f you do not choose Configuration signature must match you are responsible for ensuring the safety integrity of your system by some other means Review the Connection Reaction Time Limit 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 Adjust the Connection Reaction Time Limit by changing the RPI or the Advanced Communication Properties as described in steps 5 and 6 Set the Requested Packet Interval RPD The RPI specifies the period at which data updates over a connection The RPI is entered in 1 millisecond increments and the scanner supports a valid range of 5 to 500 ms with a default Configure DeviceNet Nodes and Connections 5 5 of 10 ms Other target devices may have more limited RPI constraints Consult the documentation for each type of target device to determine its supported range and incremental values Modifying the RPI affects the Connection Reaction Time Limit For simple timing co
97. or rounded to the nearest whole number Bandwidth 100 x CA x 57 x Bx 8 E D x 115 Baud _Rate 1 to 2 Bytes In the equation below A 1 Data_RPI 0 001 B Safety_Data_Size 6 C B x 8 x bit_stuffing_factor rounded to the nearest whole number D 1 Data_RPI x 100 0 001 Bandwidth 100 x A x 657 Bx8 C 2x Dx 115 x Number_of_Consumers Baud_Rate Calculate Safety Connection Bandwidth D 3 3 to 250 Bytes In the equation below A 1 Data_RPI 0 001 B 2 x Safety_Data_Size 8 C B 8 rounded to the nearest whole number D 1 Data_RPI x 100 0 001 E Bx 8 x bit_stuffing_factor rounded to the nearest whole number Bandwidth 100 x CA x 57x O Bx 8 E 2x D x 115 x Number_of_Consumers Baud_Rate Publication 1753 UM002A EN P July 2005 D 4 Calculate Safety Connection Bandwidth Publication 1753 UM002A EN P July 2005 Glossary Change of State COS A type of standard I O communication in which the interface module can send and receive data with slave devices whenever a data change occurs in the configured slave device or controller Data is updated at the rate of the heartbeat CIP Safety Protocol A network communications method designed and certified for transport of data to assure SIL 3 requirements Configuration Signature The combination of an ID number date and time that uniquely identifies a specific configuration for a dev
98. ormal Failure 1 Duplicate MAC Failure Publication 1753 UM002A EN P July 2005 Monitor Status 10 13 Status Signals The one WORD _DNet_StatusTable GuardPLC signal indicates the status of the DeviceNet interface as show in the following table A al7fej s 4 si2i 1jol7fels j4 s 2 1 0 T x Dup z RESERVED Mac Power Comm S Fail Fail Fail Publication 1753 UM002A EN P July 2005 10 14 Monitor Status Publication 1753 UM002A EN P July 2005 General Environmental Appendix A Specifications Dimensions 90 mm x 110 mm x 87 mm HAWD 3 5 in x 4 33 in x 3 43 in Weight 400 kg 0 882 Ib DeviceNet Current 90 mA maximum 24V dc Load Max Power Consumption 10 W maximum on external power connection Response Overload shut down of the concerned output with cyclic reconnecting Isolation Voltage 30V continuous Tested to withstand 500V dc for 60 seconds HSP Cable 1753 CBLDN ships with safety scanner Wire Type Copper Wiring Category 2 on power and communication ports 1 Use this Conductor Category information for planning conductor routing Refer to Industrial Automation Wiring and Grounding Guidelines publication number 1770 4 1 2 Height does not include DI rail latches or mounting feet 3 Depth does not include communication cable Storage Temperature 40 C to 85 C 40 F to 185 F Operating Temperature
99. pelnstance B10 GuardPLC 1600 ay Z a Programming Terminal Copy 2 Drag the Standard signals from the Signal Editor to the Standard Data Target Signal Connections dialog amp Signal Editor il New HA Delete ea Help asme poo o n ea cale_pptaget TE amp Standard Data Target Signal Connections Conl Delete Signal Define Data l Help ie Connection ae The signal names in the Target Signal Connections dialog are named from the perspective of the peer controller that is connecting to this target Signals dropped into the Input Connection tab are read by the peer connecting controller Signals dropped into the Output Connection tab will be written by the peer connecting controller You may drop safety signals into the Standard Target Connection s Input tab so that they may be read by the peer but they may only be regarded as standard signals in the peer s application Do not drop safety signals into the Standard Target Connection s Output tab A signal may be dropped into only one of the four Target Connections tabs Safety Input Safety Output Standard Input or Standard Output If a signal appears in more than one Target Configure Peer to Peer DeviceNet Communications B 7 Connections tab RSNetWorx for DeviceNet will reject the Target Connections file when it is imported 3 RSLogix Guard PLUS automatically generates a Target Connections file within its project folder
100. power cable e Improper or no termination resistor e Improper grounding 5 Check for a device that is producing noise or inappropriate data on the network No Network The DeviceNet cable is not supplying power to the communication port Make sure the Power network has 24V dc power Check the connection to the scanner Faulted must issue Safety Reset The scanner encountered an internal critical fault 1 Issue a Safety Reset and download the configuration using RSNetWorx for DeviceNet 2 If the problem continues to occur the safety scanner may need to be replaced Contact your Rockwell Automation representative NVS Xfer Main The module is in the process of having its non volatile memory updated The new image for the main processor is currently being transferred to the module NVS Xfer Peer The module is in the process of having its non volatile memory updated The new image for the peer processor is currently being transferred to the module Main Save The new non volatile memory image for the main processor has been transferred and is now being saved to memory Peer Save The new non volatile memory image for the peer processor has been transferred and is now being saved to memory NoRx No direct traffic for the scanner has been detected This can be caused by not having a scanlist entered in the scanner or simply that the scanner has not received communication from any other device See status codes 75 and
101. present 001A Bridge request is too large 001B Bridge response is too large 001D Attribute list is invalid 001E Embedded service error occurred 001F Connection related failure occurred See the extended error codes on pages 10 7 to 10 8 0022 Invalid reply received 0025 Key segment error occurred 0026 Path size is invalid Either the size of the path was not large enough or too much data was included 0027 An unexpected attribute was encountered in the list 0028 DeviceNet error member ID is invalid 0029 DeviceNet error member is not settable 00D1 The module is not in the run state OOFB The message port is not supported OOFC The message data type is unsupported OOFD The message is uninitialized OOFE The message has timed out OOFF A general error occurred See the extended error codes on pages 10 7 to 10 8 Monitor Status 10 7 Safety Connection Extended Error Codes General Extended Description Status Error Code Error Code nnnn 00gg 0001 0100 The connection is in use 0001 0103 Transport is not supported 0001 0106 Ownership conflict occurred 0001 0107 The connection was not found 0001 0108 Connection type is invalid 0001 0109 Connection size is invalid 0001 0110 The module is not configured 0001 0111 Expected Packet Rate value is not supported 0001 0114 This is the
102. 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 Publication 1753 UM002A EN P July 2005 5 6 Configure DeviceNet Nodes and Connections Configure DeviceNet Standard Slave 1 0 Nodes Configure the DeviceNet Safety Scanner s Standard Connections Publication 1753 UM002A EN P July 2005 To configure your module double click on the module in the graphic view or right click on the module and select Properties Navigate through the available tabs to review and modify the module s configuration Refer to the user manual for the module for additional information on how to set up the module s configuration To configure the safety scanner for standard communications you set up a scanlist and define the memory locations for the standard data of each device Standard Communication Properties Configure the standard communication properties of the safety scanner on the Module tab of the Scanner Properties page You can use the Module Defaults button to return the safety scanner to the default settings which are shown below Y 1753 DNSI DeviceNet Safety Scanner l 21x Input Output Summary GuardPLC General Safety Module Safety Connection Scanilist Interscan Delay 10 msec Foreground to Background Poll Ratio fi Zi Advanced Interscan
103. r Bx 250 Bytes e ous ae be Rea oe a Ae ee Multicast Connections 6454080 aed Ho ONE Bd On BEN Tito 2 Bytes an en a a a eae ipa dar p auia F to 230 BES a was aoaea a ad Alt eee a Glossary Index Who Should Use this Manual Purpose of This Manual Preface Read this preface to familiarize yourself with the rest of the manual It provides information concerning e who should use this manual e the purpose of this manual e related documentation e common techniques used in this manual e terminology used in this manual Use this manual if you are responsible for designing installing programming or troubleshooting a safety control system that includes a GuardPLC controller communicating on a DeviceNet Safety network through a 1753 DNSI module We assume that you e have a basic understanding of electrical circuitry e are trained and experienced in the creation operation and maintenance of safety systems e know each of your device s I O parameters and requirements This manual only briefly describes the safety concept of the DeviceNet Safety Scanner for GuardPLC Controllers Its purpose is to provide information on installing operating and maintaining your 1753 DNSI in a GuardPLC controller system For detailed information on safety system requirements regarding the DeviceNet Safety Scanner for GuardPLC Controllers refer to the GuardPLC Controller Systems Safety Reference Manual publication number 1753 RM002
104. radius of the 1753 CBLDN is e 30 mm 1 18 in when the cable is permanently restrained by the use of a wire tie cable trough or other means e 60 mm 2 36 in when unrestrained 1753 CBLDN IMPORTANT The maximum length of the cable connection between the module and the GuardPLC controller is 0 75 m 2 46 ft To achieve a SIL 3 rating you must use the 1753 CBLDN cable which is shipped with the module Publication 1753 UM002A EN P July 2005 2 8 Install the 1753 DNSI Publication 1753 UM002A EN P July 2005 Connect a Computer to the DeviceNet Network Chapter 3 Set Up Your DeviceNet Network To set up devices on the DeviceNet network follow the procedures listed below in order Procedure page 1 Connect a Computer to the DeviceNet Network 3 2 2 Commission All Nodes 3 2 3 Browse the Network 3 3 4 Safety Reset Optional 3 4 5 Set Passwords Optional 3 5 To access a network either e connect directly to the network or e connect to a different network and browse to the desired network via a linking device TIP RSLinx provides online help for configuring drivers and using linking bridge devices Once you choose a network e Install the communication card if required e Determine any network parameters for the computer such as a network address e Connect the computer to the network usin
105. rminology 0 0 00005 P 3 Chapter 1 Safety Concept srai a OS Ora ae oh tS Pec ES OS 1 1 DeviceNet Safety Scanner Communications 1 2 How the 1753 DNSI Communicates 1 2 Understand Data Signals 4s 6G heed ere ROKG Eas 1 3 How Data Tables Work o a e sia at ace Peal aaa 1 4 How to Distinguish Between Standard Data and Safety Data in RSLogix Guard PLUS sania ctu eka we wee 1 4 Role of RSNetWorx for DeviceNet and RSLogix Guard PLUS 1 5 DeviceNet Safety Scanner Features 004 1 6 Hardware Overview 6 oh en bas ies HhS wee Es 1 6 Supported Connections 0 02 eu VAS ee a 1 7 Physical Layout of the DeviceNet Safety System 1 8 DeviceNet Safety I O Performance Factors 1 8 Choose a Communication Rate for the Network 1 9 Assign an Address to Each Device 1 10 Chapter 2 General Safety Information 694 fn ceo ee PK et ee eee Pee EG 2 1 Preventing Electrostatic Discharge 2 2 Mount the Scanner it unt 44 8 pel ah hp deb ak Betta pal eae 2 2 DIN Rail Mounting 5 Qh toe BO eG wb Re 2 3 Panel Mountings ognie oc So ct d ahs WS he abe ul Pee Guns 2 4 Ground the Scanner ts ccs tite Meo eats eR ee 2 4 Connect Power SOUTCE 1 5 5 Saale tose ha FS EG a 2 5 Make Communication Connections 2 5 DeviceNet Connections 2 ccakn sikh 1s RR 2 6 High speed Safety Protocol HSP Connections 2 7 Chapter 3 Connect a C
106. rotected operations 3 5 reset 3 4 3 6 set or change 3 5 valid characters 3 6 point to point 5 4 poll messages 1 2 poll ratio 5 7 polled definition G 2 power supply 2 5 probability of failure on demand PFD definition P 3 probability of failure per hour PFH definition P 3 protective debris strip 2 2 ready to be safety locked 9 5 ready to be verified 9 3 requested packet interval and connection reaction time limit 5 5 definition G 2 set 5 4 reset configuration owner 3 4 reset safety attributes 3 4 reset safety device 3 4 4 6 RPI See requested packet interval RSLinx 3 1 revision level 1 6 RSLogix Guard PLUS create a project 6 1 install 1 6 RSLogix Guard PLUS Hardware Management revision level 1 6 RSLogix Guard PLUS Program Management revision level 1 6 RSNetWorx for DeviceNet 1 5 install 1 6 node commissioning 3 2 revision level 1 6 RUN status 10 2 Publication 1753 UM002A EN P July 2005 4 Index S S ee 10 4 safety concept 1 1 safety configuration tab 5 2 safety connections 1 7 colorization 1 4 safety connections tab 5 3 safety data communication 1 3 safety data signal connections dialog 8 2 Safety Device Verification Wizard 3 5 definition 9 1 device status 9 1 reports 9 5 run 9 1 safety lock select devices 9 3 summary 9 7 upload and compare 9 4 Welcome page 9 1 safety 1 0 definition G 2 safety information 2 1 safety integrity level 1 4 2 7 safety network number 1 1 4
107. s assigned to each safety network or network sub net must be unique You must ensure that a unique Safety Network Number SNN is assigned to each DeviceNet network that contains safety nodes Each DeviceNet Safety device must be configured with an SNN The combination of SNN and DeviceNet node address provides a unique identifier for every safety node in a complex industrial network This unique identifier prevents data intended for a specific target node address on one DeviceNet subnet from being mis routed to a node with the same node address on a different DeviceNet subnet The Safety Network Number SNN can be either software assigned time based or user assigned manual These two formats of the SNN are described in the following sections Time based SNN Recommended In the time based format the SNN represents the date and time at which the number was generated according to the personal computer running RSNetWorx for DeviceNet Set Safety Network Number 00 1753 DNSI De x Format Generate E 10 25 2004 9 59 01 741 AM Manual DeviceNet Decimal Number 2ED2_0337_15 D Hex Copy Publication 1753 UM002A EN P July 2005 4 2 Manage the Safety Network Number Manual SNN In the manual format the SNN represents entered values from 1 to 9999 decimal Set Safety Network Number 00 1753 DNSID x Format C Time based Manual DeviceNet 9999 Decimal Number 0001_0000_270F He
108. s not Mismatch match the configuration signature in the RSNetWorx for DeviceNet configuration file Safety Locked The device is already locked To return to RSNetWorx for DeviceNet so that you can correct the status of the indicated devices close the Safety Device Verification Wizard by clicking on Cancel To skip the devices listed and continue the verification process for other safety devices on the network click Next Verify Your DeviceNet Safety Configuration 9 3 Select Devices to Verify Choose which devices to verify using the checkboxes in the Verify column of the Verify Safety Device Configuration dialog You can select only the devices whose status is Ready to be verified Safety Device erification Wizard xi Verify Safety Device Configuration From the list select the safety devices you want to verify During the verification 4 process the software will compare the configuration in the safety device to the software s configuration I Show all safety devices Ready to be verified W 00 1791DS IB4XO W4 4Pt 4Pt Safety DC_Input DC_Rel Ready to be verified 01 1753 DNSI DeviceNet Safety Scanner Verify not supported E 02 MSR241P Safety Relay Interface Owe Click Next to continue lt Back Cancel Heb If the Show all safety devices checkbox is checked the dialog lists all of the safety devices on the network and shows their current status If it is unchecked which is the d
109. select the device in the hardware graphic view and choose Set Safety Network Number from the Device menu i DeviceNet RSNetWorx for DeviceNet Eile Edit View Network Device Diagnostics Tools Help Pa B amp Upload from D wnload to Device Hardware C Communicati Glass Instance Editor t 1734 AD Re register Device 1 DRE ork Number H A Ri 1738 AD Import Target Connections 1738 AD Export Scanner Signals 1738 4D 1738 4D Export I O Details Properties omc a wo oO b oO maae Vhen you set the SNN the device is returned to its factory default configuration A time based SNN is automatically generated when the first new safety device is added to the network Subsequent additions to the network are assigned the same SNN as the lowest addressed safety device This automatic time based SNN is sufficient and recommended for most applications Publication 1753 UM002A EN P July 2005 4 4 Manage the Safety Network Number Publication 1753 UM002A EN P July 2005 If you need to set the SNN for a particular device follow the steps 1 Click on the target device in the hardware graphic view and select Set Safety Network Number from the Device menu DeviceNet RSNetWorx for DeviceNet Eile Edit View Network Device Diagnostics Tools Help A S W amp Ei Upload from Device Hardware
110. signals should match the definitions made in RSLogix Guard PLUS Publication 1753 UM002A EN P July 2005 Configure Peer to Peer DeviceNet Communications B 9 Add the Peer Scanner to the Scanlist To configure standard peer to peer communications 1 Open the DeviceNet Properties dialog for the DeviceNet Safety Scanner and select the Scanlist tab EY 1753 DNSI DeviceNet Safety Scanner ME Input Output Summary GuardPLC l General Safety Module Safety Connection Scanlist Available Devices Scaniist 753 DNSI Devi s01 1791DS IB12 12Pt Sa R02 1791DS IB4xXOW4 4 le kk IV Automap on Add IV Node Active Upload from Scanner setae aloe aU he IV Device Type IV Vendor Download to Scanner IV Product Code I Major Revision Edit 1 0 Parameters mirre ia ler rater Cancel Apply Help 2 Add the peer scanner to the scanlist by clicking on the gt button 3 Configure the I O parameters of the peer scanner by clicking on the Edit I O Parameters button O Parameters 03 Peer 1753 DNSI DeviceNet Safety Scanners Ed rT Change of State Cycli Input Size p 3 Bytes Change of State Cyclic Use Gutput Bit ia Input Size p Bytes Poed Outpusize 0 H Bytes Input Size fi Bytes Heartbeat Rate 250 msec Output Size jo Bytes e Poll Rate Ever Scan z Cancel Restore 0 Sizes The target sa
111. source i G Distributed 1 0 S59 Protocols nnect Si F Typelnstance oo pna BBO GuardPLC 160 Define Target Connections gt Programming Terminal Import Scanner Signals Export Target Connections Validate New gt Copy Paste Delete Print Properties b Browse to the correct ssf file and select Open Before you download you must go online to the DeviceNet network using RSNetWorx for DeviceNet Your computer and the devices you wish to communicate with must be connected to the DeviceNet network When you go online to a DeviceNet network RSNetWorx for DeviceNet browses the network one time and shows you the devices on the network It does not read upload or change download the parameters of any of the devices The graphics representation of the network created by the browse operation remains static It does not automatically update to show changes since the last browse unless the Continuous Browse option is selected Publication 1753 UM002A EN P July 2005 7 6 Associate the Scanner and Controller and Download the DeviceNet Network Configuration Publication 1753 UM002A EN P July 2005 1 Go online by selecting the online button Sa 2 Browse to the DeviceNet network and click OK at the prompt EES aama 1753 DNSI 1791DS IB12 1791D5 IB4X0V DeviceNet 12Pt Safety 4Pt 4Pt
112. st Print P Profibus dp Slave BIO Guar i PT Profibus Master ll Programming Terr___PYORerHes ks SE Send Receive over TCP SNTP Client SNTP Server 5 Configure HSP communications Right click on the peer HSP Protocol and select Properties Configuration peer Resource Protocols HSP Pr Type JHSP Protocol Name HSP Protocol_1 Controller Id jo Controller Receive Timeout ms fi 0 Controller Resend Timeout ms fo Scanner Id Scanner Receive Timeout ms j HSP Signature 16 0000_0000 Import Scanner Signals Export Target Connections OK Cancel Apply Help See page 6 3 for an explanation of the HSP communication parameters 6 Review the peer controllers communication settings See page 6 5 Define Target Connections To support peer to peer communication you must assign application for Standard and Safety signals to define target connections to which a peer scanner or other CIP Safety originator or standard master will connect Review the Data guidelines for creating a distinction between safety and standard signals on page 1 4 Publication 1753 UM002A EN P July 2005 Configure Peer to Peer DeviceNet Communications B 5 Create Required Signals Using RSLogix Guard PLUS Hardware Management create the signals that will be made available to peers on the DeviceNet Safety network via the Target Connections file 1 Open the Signal Editor by selecting Editor from the Signa
113. state of the 1 This value is meaningless when the Connection Fault bit is 1 Faulted producing device is unknown The data sent to the controller for this connection is reset to 0 At start up the standard fault bit defaults to 0 If the first attempt to connect to the slave device is not successful then the connection will be reported as faulted When one or more of the standard connections to the slave node timeout the corresponding fault bit is set When all of the connections to a slave node are in the established state the fault bit is set to 0 The fault bit for the slave mode interface is not used it is always 0 IMPORTANT The bits in the table above are only accurate if the HSP connection is established IMPORTANT As with any communications channel you must use the connection status bits in your application program logic to achieve a SIL 3 system Publication 1753 UM002A EN P July 2005 10 10 Monitor Status HSP Connection State Signal The HSP connection status may be monitored via the HSP Protocol gt Connect Signals gt HSP Data gt Connection State controller signal in RSLogix Guard PLUS Hardware Management Signal State of the Connection Connection State 0 closed The active end point is not attempting to open the connection
114. sure Also see the appropriate sections in this publication as well as the Allen Bradley publication 1770 4 1 Cndustrial Automation Wiring and Grounding Guidelines for additional installation requirements pertaining to this equipment Publication 1753 UM002A EN P July 2005 2 2 Install the 1753 DNSI ATTENTION Protective Debris Strip Do not remove the protective debris strip until after the module and all other equipment in the panel near the module is mounted and wiring is complete Once wiring is complete remove the protective debris strip Failure to remove the strip before operating can cause overheating Preventing Electrostatic Discharge ATTENTION Mount the Scanner This equipment is sensitive to electrostatic discharge which can cause internal damage and affect normal operation Follow these guidelines when you handle this equipment e Touch a grounded object to discharge potential Static e Wear an approved grounding wrist strap e Do not touch connectors or pins on component boards e Do not touch circuit components inside the equipment e If available use a static safe workstation e When not in use store the equipment in appropriate static safe packaging IMPORTANT For effective cooling e Because of thermal considerations mount the module horizontally only e Provide a gap of at least 100 mm 3 94 in above below and on each side of the module e Provide a gap of at least
115. t Publication 1753 UM002A EN P July 2005 10 8 Publication 1753 UM002A EN P July 2005 Monitor Status General Extended Description Status Error Code Error Code nnnn 00gg 0001 0x080D The target s unique node identifier was not set 0001 Ox080E The target s unique node identifier does not match The message was likely routed to this node in error 0001 Ox080F The configuration operation was not allowed 0004 0000 Extended status is out of memory 0005 0004 0001 Extended status is out of instances 0005 000F 0203 The connection has timed out OOFF 2001 One or more of the system address segments that a device must interpret to direct a message to its destination object is excessive OOFF 2002 A parameter value is bad OOFF 2018 Semaphore reject occurred OOFF 201B Size is too small OOFF 201C Size is invalid OOFF 2100 Privilege failure occurred OOFF 2102 Password is invalid OOFF 2103 No password was issued OOFF 2104 The address is out of range OOFF 2106 Data is in use OOFF 2107 Type is invalid and not supported OOFF 2108 The controller is in the upload and download mode OOFF 2109 An attempt was made to change the number of array dimensions OOFF 210A The symbol name is invalid OOFF 210B The symbol does not exist OOFF 210E The search failed OOFF 210F The task cannot start OOFF 2110 Unable to write
116. t Certification link at www ab com for Declarations of Conformity Certificates and other certification details Certification Description when product is marked UL Listed for Class Division 2 Group A B C D Hazardous Locations certified for US and Canada CE European Union 89 336 EEC EMC Directive compliant with e EN 61000 6 4 Industrial Emissions e EN 50082 2 Industrial Immunity e EN 61326 Meas Control Lab Industrial Requirements e EN 61000 6 2 Industrial Immunity e EN61131 2 Programmable Controllers Clause 8 Zone A B amp C 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 NFPA79 when used as described in the GuardPLC Controller Systems Safety Reference Manual publication 1753 RM002 ODVA ODVA conformance tested to DeviceNet Safety specifications 1 See the Product Certification link at www ab com for Declarations of Conformity Certificates and other certifications details Publication 1753 UM002A EN P July 2005 A 4 Specifications Publication 1753 UM002A EN P July 2005 Appendix B Configure Peer to Peer DeviceNet Communications This appendix provides instructions on how to set up peer to peer communications to share application signals between two GuardPLC controller 1753 DNSI scanner pairs or to other standard masters or s
117. t New gt Resource RSLogix Guard PLUS Project Management C Program Files RSLogix Gui Project Object Edit Window Tools Help Bl Resource if Type ge StandardLibs d Object Ctri N Rescan FS Global Variable Match Data Access Path Print Library Table of Contents Struct Folder FindjReplace F3 Link Pence Naka a 2 Name the resource 3 In RSLogix Guard PLUS Hardware Management configure the resource properties by right clicking on the resource and selecting Properties N Configuration peer Resource oO Type Gaci Name JpeerResorce t C S System ID SRS 100 Safety Time ms 100 Watchdog Time ms feo Main Enable Iv Autostart r Start Restart allowed Iv Loading allowed Iv Test Mode allowed E Online Test allowed in Forcing allowed r Stop on Force Timeout V max Com Time Slice ms fo Code Generation Version pooo g OK Cancel Apply Help Publication 1753 UM002A EN P July 2005 B 4 Configure Peer to Peer DeviceNet Communications 4 Add HSP protocol to the peer resource Project Edit Signals Online Windows Help FE P2P project test Configuration Bi 100 peer Resource Distributed 170 F Typelnst GB Guarc ASCII Protocol cy 80000 Riese ny Distribute z Protocols Paste Ma Modbus Master BBHSP Delete M2 Modbus Slave i GH Typeln
118. t check the acknowledgement box before the locking process can continue 3 Click Next 4 The wizard performs a final comparison of the configuration signature in each safety device to its configuration signature in RSNetWorx for DeviceNet before locking the device 5 If any of the selected devices are password protected you will be prompted to enter the password for that device Enter Device Password y x The device is password protected Enter the device password to continue locking the device Enter Password Skip Cancel Help If you want to skip the device and allow the locking process to continue for other devices click on Skip View the Safety Device Verification Wizard Summary Verify Your DeviceNet Safety Configuration 9 7 Before closing the wizard displays a summary of all the safety devices that were Safety Locked the number of safety devices that still need to be Safety Locked and lets you display the verified and Safety Locked state of all of the safety devices on the network Click on Finish to close the wizard Publication 1753 UM002A EN P July 2005 9 8 Verify Your DeviceNet Safety Configuration Publication 1753 UM002A EN P July 2005 Monitor Status Chapter 10 To assist you in monitoring the status of devices on the DeviceNet Safety network the DeviceNet Safety Scanner provides e LED status indicators e an alphanumeric status display You can also monitor the status
119. t intervals system reaction time and PFD PFH calculations refer to the GuardPLC Controller Systems Safety Reference Manual publication number 1753 RM002 You must read understand and fulfill these requirements prior to operating a GuardPLC controller based SIL 3 or CAT 4 safety system The DeviceNet Safety Scanner and the GuardPLC system use the following mechanisms to support the integrity of the data they exchange e Safety Network Number A unique number that identifies the Safety Network Each DeviceNet sub network that contains safety nodes must have one unique Safety Network Number e Configuration Signature The combination of an ID number date and time that uniquely identifies a specific configuration for a safety device Publication 1753 UM002A EN P July 2005 1 2 Before You Begin DeviceNet Safety Scanner Communications Publication 1753 UM002A EN P July 2005 e HSP High speed Safety Protocol Signature This is a read only value that represents the data exchanged between the GuardPLC controller and the safety scanner The HSP Signature is calculated based on the Scanner Configuration Signature and changes only when the data exchanged by the controller and the safety scanner changes The HSP Signature is sent to the controller configuration software and helps ensure the integrity of the data Controller ID SRS A unique identifier for every GuardPLC controller and GuardPLC Ethernet Distributed
120. t or create a new project by selecting Project gt New from the main menu If the project is new enter the name of the project in the Object Name field and click OK RSLogix Guard PLUS automatically creates a single resource in a new project TIP You can rename the controller Resource in the Project Management window by right clicking on the Resource and selecting Rename from the context menu Publication 1753 UM002A EN P July 2005 6 2 Create a GuardPLC Project with High Speed Safety Protocol If you are opening an existing project created in a prior version of RSLogix Guard PLUS the software automatically converts the project to the new version TIP Make a backup copy of your existing RSLogix Guard PLUS project before opening it in the latest version since the latest version automatically converts the existing project 2 In the Hardware Management dialog right click on the controller Resource and select Properties Configuration Resource sio Type Guaco Name Reswce System ID SRS joon C O NCNNNCC C Safety Time ms 100 Watchdog Time ms Main Enable Autostart Start Restart allowed Loading allowed Test Mode allowed Online Test allowed Forcing allowed Stop on Force Timeout Vv max Com Time Slice ms fi 0 Code Generation Version E 4 OK Cancel Apply Help 3 Specify the controller type GuardPLC 1600 or GuardPLC 1800 controllers only for HSP and enter the System
121. terface Status Green Flashing The serial interface is ready for communication but the controller is sending messages that do not match the safety scanner s current configuration Red Flashing The connection to the controller was lost after being established at least once since power up At Power Up When you apply power to the 1753 DNSI safety scanner check the scanner s alphanumeric display to determine if the module is operating properly It displays the following e firmware revision e MAC ID e DeviceNet communication rate During Operation Following power up the alphanumeric display on the safety scanner displays the following information Description xx is the MAC ID of the scanner A status string follows IDLE The scanner is in idle mode RUN The scanner is in run mode Duplicate Node Failure Publication 1753 UM002A EN P July 2005 The address of the scanner is already in use by another device on the network Change the address to an unused address Monitor Status 10 3 Display Description Bus Off A bus off condition communication problem exists Detected 1 Cycle power to the device or disconnect and reconnect the DeviceNet cable 2 Make sure all devices are at the same communication rate 3 Make sure a short circuit does not exist between the CAN line and a power or shield line 4 Check for any of the following sources of noise e Close proximity to a high voltage
122. the mounting template provided in the module s installation instructions publication number 1753 INO009 2 Space your module properly to allow for adequate cooling See page 2 2 3 Secure the template to the mounting surface 4 Drill holes through the template 5 Remove the mounting template 6 Secure the module to the panel using 4 screws This product is intended to be mounted to a well grounded mounting surface such as a metal panel Refer to the Industrial Automation Wiring and Grounding Guidelines publication 1770 4 1 for additional information This product is grounded through the DIN rail to chassis ground Use zinc plated yellow chromate steel DIN rail to assure proper grounding The use of other DIN rail materials e g aluminum plastic etc that can corrode oxidize or are poor conductors can result in improper or intermittent grounding Functionally ground the module through its DIN rail connection or through the mounting foot if panel mounted 0 sss O E D e Alen Bradiey Guors PLE t 73 045 You must always connect the power supply functional ground screw when connecting the power supply You must provide an acceptable grounding path for each device in your application For more information on proper grounding Install the 1753 DNSI 2 5 Connect Power Source Make Communication Connections
123. tions 10 4 general status error codes 10 5 safety connections 10 4 standard connections 10 4 status codes extended error code 10 7 strobe messages 1 2 strobed definition G 3 system ID SRS 6 2 system reaction time definition G 3 T target connections file 1 5 7 2 definition G 3 terminology used throughout manual P 3 timeout multiplier 5 5 definition G 3 timing parameters 8 5 transmit retries 5 7 5 8 Index U unique node identifier 4 1 unknown device icon 9 2 update signals automatically 7 2 7 3 upload and compare Safety Device Verification Wizard 9 4 use data signals 1 3 V verification failure report 9 5 verification reports Safety Device Verification Wizard 9 5 verify select devices 9 3 verify DeviceNet Safety configuration 9 1 9 7 verify FAILED 9 5 verify failed 9 3 verify not supported 9 3 view scanner response times 5 13 W Watchdog Timeout 5 13 welcome page 9 1 5 Publication 1753 UM002A EN P July 2005 6 Index Publication 1753 UM002A EN P July 2005 Rockwell Automation Support www rockwellautomation com Corporate Headquarters 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 th
124. utomatically 7 2 associate manually 7 4 configure HSP connection 5 12 H heartbeat rate definition G 2 high speed safety protocol 1 2 add to GuardPLC project 6 3 cable connections 2 7 configure communications 6 3 configure connections 8 3 signature 5 12 high speed safety protocol signature 1 2 definition G 2 HSP See high speed safety protocol HSP Connection Control Word 8 3 HSP connection control word 8 3 HSP signature See high speed safety protocol signature icon device status 9 2 IDLE status 10 2 implicit messaging definition G 2 import scanner signals 7 5 input tab 5 10 interscan delay 5 6 ISD See interscan delay L LED indicators 10 1 lock See safety lock login screen 8 4 MAC address 6 5 reset 3 4 Max Scanner Response Time 5 13 max scanner response time 5 13 mean time between failures MTBF definition P 3 mean time to restoration definition P 3 mismatch configuration signature 9 2 SNN 4 5 missing device icon 9 2 module tab 5 6 mount the scanner 2 2 DIN rail 2 3 panel 2 4 multicast connections 5 4 N xx 10 3 naming convention 1 5 network delay multiplier 5 5 network status LED flashing 4 4 no network power 10 3 node definition G 2 node address changes 4 6 DeviceNet Safety 1 0 3 2 select 1 10 node commissioning 3 2 3 3 node commissioning tool 3 2 0 online button 7 6 output connection owners reset 3 4 output tab 5 11 Index 3 P parameters tab 5 3 password 1 2 forgotten 3 6 p
125. with the SNN The hardware graphic view displays the symbol over the safety device icon You can resolve the SNN error from the Safety Network Number Mismatch dialog as described on page 4 5 When online RSNetWorx for DeviceNet also checks for an SNN mismatch whenever a safety device s Device Properties dialog is selected either from the Device gt Properties menu or by double clicking on the device If an SNN mismatch condition exists the Safety Network Number Mismatch dialog is displayed as described below Safety Network Number Mismatch Dialog This dialog displays the online device SNN and the offline software SNN You can choose to upload the device s SNN or download the offline SNN to resolve the mismatch Safety Network Number Mismatch 02 1753 DNSI DeviceNet S xj difference exists between the Safety Network Number of the device in the online configuration and the device in the offline configuration Device Safety Network Number Software Safety Network Number 0001_0000_03E8 12 9 2004 1 48 32 117 PM DeviceNet 1000 Do you want to upload the device s Safety Network Number to update the software s Safety Network Number or download the software s Safety Network Number to update the device Upload Download Cancel Help Downioed Conroe _ Heo TIP If the device s SNN has not been initialized the Device Safety Network Number field displays the default SNN FFFF_FFFF_FFFF When the device s
126. x Cancel Help TIP You can use the Copy button on the Set Safety Network Number dialog to copy the SNN to the Windows clipboard Assignment of the SNN SNNs can be generated automatically via RSNetWorx for DeviceNet or manually assigned by the user Automatically generated SNNs are sufficient and recommended for most applications Automatic Time based When a new safety device is added to the network configuration a default SNN is automatically assigned via the configuration software as follows e If at least one safety device already exists in the DeviceNet network configuration subsequent safety additions to that network configuration are assigned the same SNN as the lowest addressed safety device e If no other safety devices exist in the DeviceNet network configuration a time based SNN is automatically generated by RSNetWorx for DeviceNet Publication 1753 UM002A EN P July 2005 Manage the Safety Network Number 4 3 Set the SNN in All Safety Nodes Manual The manual option is intended for systems where the number of DeviceNet subnets and interconnecting networks is small and where you might like to manage and assign SNNs in a logical manner pertaining to their specific application IMPORTANT If you assign SNNs manually take care to ensure that system expansion does not result in duplication of SNN and Node Address combinations To set the SNN in a safety device via RSNetWorx for DeviceNet

1753-UM002A-EN-P, DeviceNet Safety Scanner for

Contents

Download Pdf Manuals

Related Search

Related Contents