Rockwell Automation AB Quality Allen-Bradley 1753-DNSI User Manual
  1. Manuals
  2. Brands
  3. Rockwell Automation Manuals
  4. Scanner
  5. AB Quality Allen-Bradley 1753-DNSI
  6. User manual
Rockwell Automation AB Quality Allen-Bradley 1753-DNSI User Manual

Rockwell Automation AB Quality Allen-Bradley 1753-DNSI User Manual

Devicenet safety scanner for guardplc controllers
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DeviceNet Safety
Scanner for
GuardPLC™
Controllers
Catalog Number 1753-DNSI
User Manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the AB Quality Allen-Bradley 1753-DNSI and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Rockwell Automation AB Quality Allen-Bradley 1753-DNSI

Summary of Contents for Rockwell Automation AB Quality Allen-Bradley 1753-DNSI

  • Page 1 DeviceNet Safety Scanner for GuardPLC™ Controllers Catalog Number 1753-DNSI User Manual...
  • Page 2 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.

  • Page 3: Table Of Contents

    Table of Contents Preface Who Should Use this Manual..... . . P-1 Purpose of This Manual......P-1 Related Documentation .
  • Page 4 Table of Contents To set a password for a module: ....3-5 Forgotten Passwords ......3-6 Chapter 4 Manage the Safety Network SNN Formats.
  • Page 5 Table of Contents Chapter 8 Develop Your GuardPLC Define Signals for Your GuardPLC Application ..8-1 Define Signals for Safety Data....8-1 Application Configure HSP Connection .
  • Page 6 Table of Contents Associate the Peer Safety Scanner and GuardPLC Controller ........B-8 Add the Peer Scanner to the Scanlist.

  • Page 7: Preface

    Preface Read this preface to familiarize yourself with the rest of the manual. It provides information concerning: • who should use this manual • the purpose of this manual • related documentation • common techniques used in this manual • terminology used in this manual Who Should Use this Use this manual if you are responsible for designing, installing, programming, or troubleshooting a safety control system that includes...

  • Page 8: Related Documentation

    • download a free electronic version from the internet at www.rockwellautomation.com/literature. • 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 •...

  • Page 9: Understanding Terminology

    Preface Understanding Terminology The following table defines acronyms used in this manual. Acronym: Full Term: Definition: 1oo2 One Out of Two A safety architecture consisting of two channels connected in parallel, such that either channel can perform the safety function. Controller Area Network The networking standard that defines the physical layer of DeviceNet.
  • Page 10 Preface Publication 1753-UM002A-EN-P - July 2005...

  • Page 11: Before You Begin

    Chapter 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: • the safety concept of the system • the data exchange between the GuardPLC controller and DeviceNet devices through the 1753-DNSI module •...

  • Page 12: Devicenet Safety Scanner Communications

    Before You Begin • 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.

  • Page 13: Understand Data Signals

    Before You Begin For safety data, the scanner 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.

  • Page 14: How Data Tables Work

    Before You Begin 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 Inputs Scanner Outputs Scanner is the...

  • Page 15: Role Of Rsnetworx For Devicenet And Rslogix Guard Plus

    Before You Begin 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.

  • Page 16: Devicenet Safety Scanner Features

    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. If you install RSLogix Guard PLUS! and RSNetWorx for DeviceNet on the same PC, you can take advantage of the ‘Automatically Update Signals’...

  • Page 17: Supported Connections

    Before You Begin 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.

  • Page 18: Physical Layout Of The Devicenet Safety System

    Before You Begin Communication Rate The safety scanner supports the following communication rates, but does not support autobaud: • 125 Kbps (default) • 250 Kbps • 500 Kbps Physical Layout of the Planning your system helps ensure that you can: DeviceNet Safety System •...

  • Page 19: Choose A Communication Rate For The Network

    Before You Begin 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.

  • Page 20: Assign An Address To Each Device

    1-10 Before You Begin Assign an 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 If you have multiple scanners, give them...

  • Page 21: Install The 1753-Dnsi

    Chapter Install the 1753-DNSI General Safety Information Safety Applications ATTENTION Personnel 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. Environment and Enclosure ATTENTION This equipment is intended for use in a Pollution...

  • Page 22: Preventing Electrostatic Discharge

    Install the 1753-DNSI Protective Debris Strip ATTENTION 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.

  • Page 23: Din Rail Mounting

    Install the 1753-DNSI The module can be DIN rail or panel-mounted as described in the following sections. Be careful of metal chips when drilling mounting ATTENTION holes for your module or other equipment within the enclosure or panel. Drilled fragments that fall into your module could cause damage.

  • Page 24: Panel Mounting

    Install the 1753-DNSI 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 the mounting template provided in the module’s installation instructions, publication number 1753-IN009. 2.

  • Page 25: Connect Power Source

    Install the 1753-DNSI guidelines, refer to the Industrial Automation Wiring and Grounding Guidelines, publication number 1770-4.1. Connect Power Source 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).

  • Page 26: Devicenet Connections

    Install the 1753-DNSI Front View Bottom View HSP Port 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. For detailed DeviceNet connection information, refer IMPORTANT to the DeviceNet Cable System Planning and Installation Manual, publication DN-6.7.2.

  • Page 27: High-Speed Safety Protocol (Hsp) Connections

    Install the 1753-DNSI 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-lb). High-speed Safety Protocol (HSP) Connections The module ships with the cable used to connect its HSP port to the GuardPLC controller’s COMM3 (ASCII/HSP) port.
  • Page 28 Install the 1753-DNSI Publication 1753-UM002A-EN-P - July 2005...

  • Page 29: Set Up Your Devicenet Network

    Chapter 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 2. Commission All Nodes 3. Browse the Network 4. Safety Reset (Optional) 5.

  • Page 30: Make Sure The Driver Works

    Set Up Your DeviceNet Network 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.

  • Page 31: Browse The Network

    Set Up Your DeviceNet Network To use the Node Commissioning tool: 1. Within RSNetWorx for DeviceNet, select Tools > Node Commissioning. 2. Click on the Browse button on the Node Commissioning dialog to select a device by browsing the network. 3.

  • Page 32: Safety Reset (Optional)

    Set Up Your DeviceNet Network Safety Reset (Optional) 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.

  • Page 33: Set Passwords (Optional)

    Set Up Your DeviceNet Network 3. Click on the Reset button. 4. If the device is Safety-Locked, you are prompted to first unlock the device. Once unlocked, the device cannot be relied ATTENTION upon to perform safety operations. You must test and verify the device’s operation and run the Safety Device Verification Wizard to Safety-Lock the device before operating the device in a safety application.

  • Page 34: Forgotten Passwords

    Set Up Your DeviceNet Network 3. Click on the Password… button. You can also access the Set Device Password dialog by either: • clicking on the module and choosing Set Password… from the Device menu, or • right-clicking on the module and selecting Set Password….
  • Page 35 3. Contact Rockwell Automation Technical Support and provide the device Serial Number and Security Code from the Reset Password dialog. 4. Enter the Vendor Password obtained from Rockwell Automation Technical Support on the Reset Device Password dialog and click OK.
  • Page 36 Set Up Your DeviceNet Network Publication 1753-UM002A-EN-P - July 2005...

  • Page 37: Chapter 4 Snn Formats

    Chapter Manage the Safety Network Number Safety Network Numbers 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.

  • Page 38: Manual Snn

    Manage the Safety Network Number Manual SNN In the manual format, the SNN represents entered values from 1 to 9999 decimal. You can use the Copy button on the Set Safety Network Number dialog to copy the SNN to the ®...

  • Page 39: Manual

    Manage the Safety Network Number 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. If you assign SNNs manually, take care to ensure that IMPORTANT system expansion does not result in duplication of...
  • Page 40 Manage the Safety Network Number If you need to set the SNN for a particular device, follow the steps below: 1. Click on the target device in the hardware graphic view and select Set Safety Network Number from the Device menu. 2.

  • Page 41: Snn Mismatch

    Manage the Safety Network Number 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 with the SNN. The hardware graphic view displays the ! symbol over the safety device icon.

  • Page 42: Snn And Node Address Changes

    Manage the Safety Network Number SNN and Node Address If you want to change the address of a safety device, the Safety Network Number must be uninitialized, or you must first reset the Changes Safety Network Number. To reset the SNN: 1.

  • Page 43: Configuration Signature

    Chapter 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 I/O Target Nodes 2. Configure the DeviceNet Safety Scanner’s Safety Connections 3. Configure DeviceNet Standard Slave I/O Nodes 4.

  • Page 44: Configure Devicenet Safety I/O Target Nodes

    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) device configuration file to the Configuration Signature in the online device.

  • Page 45: Configure The Devicenet Safety Scanner's Safety Connections

    Configure DeviceNet Nodes and 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. Other devices may have different configuration options.
  • Page 46 Configure DeviceNet Nodes and Connections The Add Safety Connection dialog allows you to configure a connection. 1. Select the desired connection by choosing the Connection Name. 2. Select a type of connection, either Multicast (input connections only) or Point-to-point (input or output connections). 3.
  • Page 47 Configure DeviceNet Nodes and Connections 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 constraints, setting the RPI is usually sufficient.

  • Page 48: Configure Devicenet Standard Slave I/O Nodes

    Configure DeviceNet Nodes and Connections Configure DeviceNet To configure your module, double-click on the module in the graphic view or right-click on the module and select Properties. Navigate Standard Slave I/O Nodes through the available tabs to review and modify the module’s configuration.
  • Page 49 Configure DeviceNet Nodes and Connections 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.

  • Page 50: Create A Scanlist

    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).
  • Page 51 Configure DeviceNet Nodes and Connections 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 configured to support a standard slave-mode interface will also appear in this list.

  • Page 52: Configure Standard Inputs

    5-10 Configure DeviceNet Nodes and Connections 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.

  • Page 53: Configure Standard Outputs

    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. 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...

  • Page 54: Configure Guardplc Controller Settings

    5-12 Configure DeviceNet Nodes and Connections Configure GuardPLC Use the GuardPLC tab to configure the scanner’s HSP connection parameters. Controller Settings 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.
  • Page 55 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...
  • Page 56 5-14 Configure DeviceNet Nodes and Connections Publication 1753-UM002A-EN-P - July 2005...

  • Page 57: Create Or Open A Guardplc Project

    Chapter 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 2.
  • Page 58 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. 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.

  • Page 59: Add High-Speed Safety Protocol To The Guardplc Controller

    Create a GuardPLC Project with High-Speed Safety Protocol Add High-Speed Safety To add High-Speed Safety Protocol (HSP) to your GuardPLC controller: Protocol to the GuardPLC Controller Resource 1. Right-click on the Protocols folder under your Resource and select New>HSP Protocol. 2.

  • Page 60: Resource

    Create a GuardPLC Project with High-Speed Safety Protocol Use the following guidelines when setting the Controller Receive Timeout and Controller Resend Timeout: • 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.

  • Page 61: Review The Guardplc Controller's Communication Settings

    Create a GuardPLC Project with High-Speed Safety Protocol Review the GuardPLC 1. Retrieve or confirm the communication settings by selecting Communication Settings from the Online menu. Controller’s Communication Settings a. If you know the current IP Address, SRS and Administrator password, you can fill in the IP Address and SRS and select Get.
  • Page 62 Create a GuardPLC Project with High-Speed Safety Protocol Publication 1753-UM002A-EN-P - July 2005...

  • Page 63: Scanner Signals File

    Chapter 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.

  • Page 64: Target Connections File

    Associate the Scanner and Controller and Download the DeviceNet Network Configuration 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.
  • Page 65 Associate the Scanner and Controller and Download the DeviceNet Network Configuration 4. Select your RSLogix Guard PLUS! project. a. If you have multiple RSLogix Guard PLUS! projects, use care to select the correct one. Only RSLogix Guard PLUS! projects that have at least one resource with HSP communications enabled can be selected.

  • Page 66: Manually Associate The Scanner And Controller

    Associate the Scanner and Controller and Download the DeviceNet Network Configuration Manually Associate the If you manually associate the scanner and controller, you must repeat this procedure whenever you make a change to the DeviceNet Scanner and Controller connections. To manage the association between the safety scanner and the GuardPLC controller manually: 1.

  • Page 67: Download The Devicenet Network Configuration

    Associate the Scanner and Controller and 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… b.
  • Page 68 Associate the Scanner and Controller and Download the DeviceNet Network Configuration 1. Go online by selecting the online button. 2. Browse to the DeviceNet network and click OK at the prompt. During each browse operation, RSNetWorx for DeviceNet reads the following attributes of each device. Safety Attribute Description SNN and Node Address...
  • Page 69 Associate the Scanner and Controller and Download the DeviceNet Network Configuration 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.
  • Page 70 Associate the Scanner and Controller and Download the DeviceNet Network Configuration Publication 1753-UM002A-EN-P - July 2005...

  • Page 71: Define Signals For Your Guardplc Application

    Chapter 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 2. Create Application Program Logic 3. Save and Compile Application Logic 4.
  • Page 72 Develop Your GuardPLC Application 2. Open the Signal Editor by selecting Editor from the Signals menu. 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.

  • Page 73: Configure Hsp Connection

    Develop Your GuardPLC Application Configure HSP Connection The safety scanner closes the HSP connection 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.

  • Page 74: Create Application Program Logic

    Develop Your GuardPLC Application Create Application Program Create application program logic using the signals you defined. Logic 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 Save and compile your application logic.
  • Page 75 Develop Your GuardPLC Application 4. Click the download icon and confirm the action by selecting Yes to the warning prompt. 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.
  • Page 76 Develop Your GuardPLC Application Publication 1753-UM002A-EN-P - July 2005...

  • Page 77: Start The Safety Device Verification Wizard

    Chapter Verify Your DeviceNet Safety Configuration Before running the Safety Device Verification Wizard, IMPORTANT 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 application prior to safety-locking your devices.
  • Page 78 Verify Your DeviceNet Safety Configuration appears listing those devices and their current status, including a device icon overlaid with a status icon. Status Description Icon 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.

  • Page 79: Select Devices To Verify

    Verify Your DeviceNet Safety Configuration 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’. 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.
  • Page 80 Verify Your DeviceNet Safety Configuration Click on Next to begin the upload and compare process. 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.

  • Page 81: Review The Safety Device Verification Reports

    Verify Your DeviceNet Safety Configuration Review the Safety Device The Review page displays safety devices with status of either ‘Verify FAILED’ or ‘Ready to be Safety Locked’. Verification Reports 1. Click on the Review hyperlink in the Report column to launch the device’s HTML report in your default browser.

  • Page 82: Lock Safety Devices

    Verify Your DeviceNet Safety Configuration Lock Safety Devices Before you lock your safety device configurations, IMPORTANT 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.
  • Page 83 Verify Your DeviceNet Safety Configuration View the Safety Device Before closing, the wizard displays a summary of all the safety devices that were Safety-Locked, the number of safety devices that still need Verification Wizard to be Safety-Locked, and lets you display the verified and Summary Safety-Locked state of all of the safety devices on the network.
  • Page 84 Verify Your DeviceNet Safety Configuration Publication 1753-UM002A-EN-P - July 2005...

  • Page 85: Chapter 10 Led Status Indicators

    Chapter Monitor Status To assist you in monitoring the status of devices on the DeviceNet Safety network, the DeviceNet Safety Scanner provides: • LED status indicators • an alphanumeric status display. You can also monitor the status of HSP, DeviceNet Safety and standard connections, and the DeviceNet interface via connection status bits and the corresponding GuardPLC application signals.

  • Page 86: Alphanumeric Display

    10-2 Monitor Status Color/State Description The module has not received any messages on the serial interface. Green, On The module is transmitting data over the serial communication interface. Green, Flashing The serial interface is ready for communication, but the Status controller is sending messages that do not match the safety scanner’s current configuration.
  • Page 87 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.
  • Page 88 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<:nnnn> Extended error code for safety connections, where: • ‘gg’ indicates the hexidecimal general status error code as listed in the Safety Connection General Status Error Codes table on page 10-5, and •...
  • Page 89 None. This code clears itself once the scanner attempts to initialize all the devices on the network. During runtime, the device is sending the wrong Contact Rockwell Automation support. See the back of this size of data. publication. • Check the configuration and status of the device.
  • Page 90 10-6 Monitor Status 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.
  • Page 91 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.
  • Page 92 10-8 Monitor Status General Extended Description Status Error Code Error Code (nnnn) (00gg) 0001 0x080D The target’s unique node identifier was not set. 0001 0x080E The target’s unique node identifier does not match. The message was likely routed to this node in error. 0001 0x080F The configuration operation was not allowed.

  • Page 93: Connection Status

    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.

  • Page 94: Devicenet Safety Connection Status

    10-10 Monitor Status HSP Connection State Signal The HSP connection status may be monitored via the HSP Protocol>Connect Signals>HSP Data>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.

  • Page 95: Standard Devicenet Connection Status

    Monitor Status 10-11 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 Connection Number 64 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 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 Connection...

  • Page 96: Devicenet Interface Status

    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!.
  • Page 97 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. Power Comm RESERVED Fail Fail Fail Publication 1753-UM002A-EN-P - July 2005...
  • Page 98 10-14 Monitor Status Publication 1753-UM002A-EN-P - July 2005...

  • Page 99: Appendix A General

    Appendix Specifications General Dimensions 90 mm x 110 mm x 87 mm (H x W x D) (3.5 in. x 4.33 in. x 3.43 in. Weight 400 kg (0.882 lb) DeviceNet Current 90 mA maximum @ 24V dc Load, Max. Power Consumption 10 W maximum (on external power connection) Response Overload...

  • Page 100: Electrical/Emc

    Specifications Electrical/EMC Emissions CISPR 11: Group 1, Class A ESD Immunity IEC 61000-4-2: • 6 kV contact discharges • 8 kV air discharges Radiated RF Immunity IEC 61000-4-3: • 10V/m with 1 kHz sine-wave 80% AM from 30 MHz to 2000 MHz •...

  • Page 101: Certifications

    Specifications Certifications When marked, the components have the following certifications. See the Product Certification link at www.ab.com for Declarations of Conformity, Certificates, and other certification details. Description Certification (when product is marked) c-UL-us UL Listed Industrial Control Equipment, certified for US and Canada UL Listed for Class I, Division 2 Group A,B,C,D Hazardous Locations, certified for US and Canada European Union 89/336/EEC EMC Directive, compliant with:...
  • Page 102 Specifications Publication 1753-UM002A-EN-P - July 2005...
  • Page 103 Appendix 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 safety originators on the DeviceNet network. Complete the procedures in this chapter before IMPORTANT making safety connections via the Safety Connections tab or standard connections via a...

  • Page 104: Plan Your Peer-To-Peer Communications

    Configure Peer-to-Peer DeviceNet Communications Plan Your Peer-to-Peer If your application requires peer-to-peer DeviceNet communications, you must: Communications • determine which RSLogix Guard PLUS! application signals each controller and scanner combination needs to make available to peer controllers, and • determine whether the chosen signals should be made available on standard or safety connections.

  • Page 105: Add A Peer Controller

    Configure Peer-to-Peer DeviceNet Communications 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 select New>Resource. 2. Name the resource. 3. In RSLogix Guard PLUS! Hardware Management, configure the resource properties by right-clicking on the resource and selecting Properties.

  • Page 106: Define Target Connections For Standard And Safety Data

    Configure Peer-to-Peer DeviceNet Communications 4. Add HSP protocol to the peer resource. 5. Configure HSP communications. Right-click on the peer HSP Protocol and select Properties. See page 6-3 for an explanation of the HSP communication parameters. 6. Review the peer controller’s communication settings. See page 6-5.

  • Page 107: Create Required Signals

    Configure Peer-to-Peer DeviceNet Communications 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 Signals menu.

  • Page 108: Define Standard Target Connections

    Configure Peer-to-Peer DeviceNet Communications 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>Standard Data. 2.

  • Page 109: Define Safety Connections

    Configure Peer-to-Peer DeviceNet Communications 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. 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.

  • Page 110: Configure Peer-To-Peer Connections

    Configure Peer-to-Peer DeviceNet Communications 3. RSLogix Guard PLUS! automatically generates a Target 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.

  • Page 111: Add The Peer Scanner To The Scanlist

    Configure Peer-to-Peer DeviceNet Communications 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. 2. Add the peer scanner to the scanlist by clicking on the > button. 3.

  • Page 112: Configure Safety Connections

    B-10 Configure Peer-to-Peer DeviceNet Communications Configure Safety Connections To configure a safety connection to the peer scanner: 1. On the Device Properties dialog, select the Safety Connections tab. 2. Right-click on the peer scanner and select Add Connections to display the available connections. 3.
  • Page 113 Configure Peer-to-Peer DeviceNet Communications B-11 For a description of the Safety Connection parameters, see pages 5-4 to 5-5. For peer-to-peer safety connections, you can only select ‘Do not check configuration signature’. Make non-peer-to-peer connections, following steps 2 and 4 in Chapter 5.
  • Page 114 B-12 Configure Peer-to-Peer DeviceNet Communications Publication 1753-UM002A-EN-P - July 2005...

  • Page 115: Appendix C Devicenet Object

    Appendix DeviceNet Class Codes This appendix contains the most commonly used class codes for the 1753-DNSI DeviceNet Safety Scanner for GuardPLC Controllers. DeviceNet Object Name Class Instance Attribute Data Size Access MAC ID 0x03 0x01 0x01 1 byte Get/Set Baud Rate 0x03 0x01 0x02...
  • Page 116 DeviceNet Class Codes Publication 1753-UM002A-EN-P - July 2005...

  • Page 117: Single-Cast Inputs

    Appendix 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, • RPI is in milliseconds • data sizes are in bytes •...

  • Page 118: Single-Cast Outputs

    Calculate Safety Connection Bandwidth Single-cast Outputs 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 + B x 8 + C) + (D x 115)] ÷...
  • Page 119 Calculate Safety Connection Bandwidth 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 = (B x 8 x bit_stuffing_factor) rounded to the nearest whole number %Bandwidth = 100 x...
  • Page 120 Calculate Safety Connection Bandwidth Publication 1753-UM002A-EN-P - July 2005...

  • Page 121: Glossary

    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.
  • Page 122 Glossary 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.
  • Page 123 Glossary 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 scanner ID is automatically generated by RSNetWorx for DeviceNet using the SNN and DeviceNet address of the scanner.
  • Page 124 Glossary Publication 1753-UM002A-EN-P - July 2005...
  • Page 125 Index Symbols DeviceNet Safety Scanner safety connections .ssf DeviceNet Safety Scanner standard See scanner signals file. connections .tcf DeviceNet Safety target nodes See target connections file. DeviceNet Standard slave nodes 5-12 GuardPLC controller connections Numerics HSP connnection safety parameters 1753-CBLDN signals 1770-KFD module 5-10...
  • Page 126 Index 1-4, 7-1, 7-2 10-3 data tables faulted, must issue safety reset data types features default module defaults button device status G#gg 10-4 10-1 monitoring grounding Safety Device Verification Wizard GuardPLC controller verification communication settings DeviceNet connections configuration DeviceNet network properties configuration GuardPLC project...
  • Page 127 Index 10-1 LED indicators parameters tab lock password See safety-lock. forgotten login screen protected operations 3-4, 3-6 reset set or change valid characters MAC address point-to-point reset poll messages 5-13 Max Scanner Response Time poll ratio 5-13 max scanner response time polled mean time between failures (MTBF) definition...
  • Page 128 Index features ground 10-4 S#ee hardware overview safety concept HSP connections safety configuration tab mounting safety connections power supply colorization reset safety connections tab scanner configuration signature safety data 5-12 scanner ID communication definition safety data, signal connections dialog 5-13 scanner receive timeout 1-5, 6-4, 7-1 scanner signals file...
  • Page 129 Index 10-3 N#xx 10-3 no network power unique node identifier 10-2 unknown device 10-4 S#ee icon status code update signals 10-4 descriptions 7-2–7-3 automatically 10-5 general status error codes upload and compare 10-4 safety connections Safety Device Verification Wizard 10-4 standard connections use data signals status codes...
  • Page 130 Index Publication 1753-UM002A-EN-P - July 2005...
  • Page 132 DeviceNet is a trademark of Open DeviceNet Vendor Association. All other trademarks are the property of their respective holders, and are hereby acknowledged. Publication 1753-UM002A-EN-P - July 2005 Copyright © 2005 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Table of Contents