Rockwell Automation 1753-DNSI User Manual

DeviceNet Safety Scanner for GuardPLC™ Controllers

Catalog Number 1753-DNSI

User Manual

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

WARNING

IMPORTANT

ATTENTION

SHOCK HAZARD

BURN HAZARD

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.

Identifies information that is critical for successful application and understanding of the product.

Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you:

• identify a hazard

• avoid a hazard

• recognize the consequence

Labels may be located on or inside the equipment (e.g., drive or motor) to alert people that dangerous voltage may be present.

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

Preface

Who Should Use this Manual. . . . . . . . . . . . . . . . . . . . . . . P-1

Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . P-1

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . P-2

Common Techniques Used in This Manual. . . . . . . . . . . . . P-2

Understanding Terminology . . . . . . . . . . . . . . . . . . . . . . . P-3

Chapter 1

Safety Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

DeviceNet Safety Scanner Communications . . . . . . . . . . . . 1-2

How the 1753-DNSI Communicates . . . . . . . . . . . . . . . 1-2

Understand Data Signals. . . . . . . . . . . . . . . . . . . . . . . . 1-3

How Data Tables Work . . . . . . . . . . . . . . . . . . . . . . . . 1-4

How to Distinguish Between Standard Data and Safety Data

in RSLogix Guard PLUS! . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Role of RSNetWorx for DeviceNet and RSLogix Guard PLUS! 1-5

DeviceNet Safety Scanner Features. . . . . . . . . . . . . . . . . . . 1-6

Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

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

Install the 1753-DNSI

Set Up Your DeviceNet Network

Chapter 2

General Safety Information . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . 2-2

Mount the Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

DIN Rail Mounting. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Panel Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Ground the Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Connect Power Source . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Make Communication Connections . . . . . . . . . . . . . . . . . . 2-5

DeviceNet Connections . . . . . . . . . . . . . . . . . . . . . . . . 2-6

High-speed Safety Protocol (HSP) Connections . . . . . . . 2-7

Chapter 3

Connect a Computer to the DeviceNet Network . . . . . . . . . 3-1

Configure a Driver for the Network . . . . . . . . . . . . . . . 3-1

Make Sure the Driver Works. . . . . . . . . . . . . . . . . . . . . 3-2

Commission All Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Browse the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Safety Reset (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Set Passwords (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Set or Change a Password . . . . . . . . . . . . . . . . . . . . . . 3-5

1 Publication 1753-UM002A-EN-P - July 2005

Table of Contents 2

Manage the Safety Network Number

Configure DeviceNet Nodes and Connections

To set a password for a module: . . . . . . . . . . . . . . . . . 3-5

Forgotten Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Chapter 4

SNN Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Time-based SNN (Recommended) . . . . . . . . . . . . . . . . 4-1

Manual SNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Assignment of the SNN . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Automatic (Time-based) . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Set the SNN in All Safety Nodes. . . . . . . . . . . . . . . . . . . . . 4-3

SNN Mismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Safety Network Number Mismatch Dialog . . . . . . . . . . . 4-5

SNN and Node Address Changes . . . . . . . . . . . . . . . . . . . . 4-6

Chapter 5

Configuration Signature. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Configure DeviceNet Safety I/O Target Nodes . . . . . . . . . . 5-2

1791DS DeviceNet Safety I/O Module Parameters . . . . . 5-2

Configure the DeviceNet Safety Scanner’s Safety

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Configure DeviceNet Standard Slave I/O Nodes . . . . . . . . . 5-6

Configure the DeviceNet Safety Scanner’s Standard

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Standard Communication Properties . . . . . . . . . . . . . . . 5-6

Create a Scanlist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Configure Standard Inputs . . . . . . . . . . . . . . . . . . . . . . 5-10

Configure Standard Outputs . . . . . . . . . . . . . . . . . . . . . 5-11

Configure GuardPLC Controller Settings . . . . . . . . . . . . . . . 5-12

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

Chapter 6

Create or Open a GuardPLC Project . . . . . . . . . . . . . . . . . 6-1

Add High-Speed Safety Protocol to the GuardPLC Controller

Resource. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Review the GuardPLC Controller’s Communication Settings 6-5

Chapter 7

Scanner Signals File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Target Connections File. . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Automatically Update Signals. . . . . . . . . . . . . . . . . . . . . . . 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

Table of Contents 3

Chapter 8

Define Signals for Your GuardPLC Application . . . . . . . . . . 8-1

Define Signals for Safety Data. . . . . . . . . . . . . . . . . . . . 8-1

Configure HSP Connection. . . . . . . . . . . . . . . . . . . . . . 8-3

Create Application Program Logic . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Chapter 9

Start the Safety Device Verification Wizard . . . . . . . . . . . . . 9-1

Determine if Devices Can Be Verified . . . . . . . . . . . . . . . . 9-1

Select Devices to Verify. . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Review the Safety Device Verification Reports . . . . . . . . . . 9-5

Lock Safety Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

View the Safety Device Verification Wizard Summary . . . . . 9-7

Monitor Status

Specifications

Configure Peer-to-Peer DeviceNet Communications

Chapter 10

LED Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Alphanumeric Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

At Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

During Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

DeviceNet Connection Status Bit Behavior . . . . . . . . . . 10-9

DeviceNet Safety Connection Status . . . . . . . . . . . . . . 10-10

Standard DeviceNet Connection Status . . . . . . . . . . . . 10-11

DeviceNet Interface Status . . . . . . . . . . . . . . . . . . . . . 10-12

Appendix A

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Electrical/EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Certifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Appendix B

Plan Your Peer-to-Peer Communications . . . . . . . . . . . . . . B-2

Commission a Peer Scanner. . . . . . . . . . . . . . . . . . . . . . . . B-2

Add a Peer Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Define Target Connections for Standard and Safety Data. . . B-4

Create Required Signals . . . . . . . . . . . . . . . . . . . . . . . . B-5

Define Standard Target Connections . . . . . . . . . . . . . . . B-6

Define Safety Connections . . . . . . . . . . . . . . . . . . . . . . B-7

Configure Peer-to-Peer Connections. . . . . . . . . . . . . . . . . . B-8

Publication 1753-UM002A-EN-P - July 2005

Table of Contents 4

DeviceNet Class Codes

Calculate Safety Connection Bandwidth

Associate the Peer Safety Scanner and GuardPLC

Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8

Add the Peer Scanner to the Scanlist. . . . . . . . . . . . . . . B-9

Configure Safety Connections. . . . . . . . . . . . . . . . . . . B-10

Appendix C

DeviceNet Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Identity Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Safety Supervisor Object . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D

Single-cast Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

1 to 2 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

3 to 250 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Single-cast Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

1 to 2 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

3 to 250 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

Multicast Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

1 to 2 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2

3 to 250 Bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Glossary

Index

Publication 1753-UM002A-EN-P - July 2005

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 Manual

Purpose of 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:

• have a basic understanding of electrical circuitry

• are trained and experienced in the creation, operation, and

maintenance of safety systems.

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

1 Publication 1753-UM002A-EN-P - July 2005

2 Preface

Common Techniques Used in This Manual

The following conventions are used throughout this manual:

• Bulleted lists, such as this one, provide information, not procedural steps.

• Numbered lists provide sequential steps or hierarchical information.

Publication 1753-UM002A-EN-P - July 2005

Preface 3

Understanding Terminology

Acronym: Full Term: Definition:

1oo2 One Out of Two A safety architecture consisting of two channels connected in parallel, such

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

EDS Electronic Data Sheet A vendor-supplied template that specifies how device configuration

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

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 control, a controller-based system via

The following table defines acronyms used in this manual.

that either channel can perform the safety function.

receive data with slave devices whenever a data change occurs in the configured slave device.

information is displayed as well as what is an appropriate entry (value).

standard data between the GuardPLC controller and the DeviceNet Safety Scanner for GuardPLC Controllers.

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

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

• the roles of RSNetWorx for DeviceNet and RSLogix Guard PLUS! software in the safety system

• the features of the DeviceNet Safety Scanner

• the physical layout of your network

Safety Concept

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

The DeviceNet Safety Scanner and the GuardPLC system use the following mechanisms to support the integrity of the data they exchange:

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

• Configuration Signature – The combination of an ID number, date, and time that uniquely identifies a specific configuration for a safety device.

For SIL 3 and CAT 4 safety system requirements, including proof test 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.

1 Publication 1753-UM002A-EN-P - July 2005

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

DeviceNet Safety Scanner Communications

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:

• read inputs from a device

• write outputs to a device

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

Publication 1753-UM002A-EN-P - July 2005

Before You Begin 1-3

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

• whether the signal data is regarded as safety or standard data in the end device, and

• 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 Definition

Safety Safety Safety

Standard Safety Standard

Connection Type Permitted Use in Application

Standard Standard

IMPORTANT

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

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

Data the scanner reads from its target nodes. The data layout is defined by the target node’s configuration.

Data the scanner writes to its target nodes. The data layout is defined by the target node’s configuration.

Safety

Standard

Scanner is the target.

Scanner is the master.

Scanner is the slave.

Data that one other CIP Safety originator may write on the scanner’s target output connection point. The data signals to be written are selected in RSLogix Guard PLUS!.

Data the scanner reads from its standard DeviceNet slaves. The data layout is defined by the target node’s configuration.

Data that one other standard DeviceNet master can write on the scanner’s slave mode outputs. The data signals are selected in RSLogix Guard PLUS!.

Data that one or more other CIP Safety originators may read from the scanner’s target input connection point. The data signals to be read are selected in RSLogix Guard PLUS!.

Data the scanner writes to its standard DeviceNet slaves. The data layout is defined by the target node’s configuration.

Data that one or more other 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

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.

Publication 1753-UM002A-EN-P - July 2005

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

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

Role of RSNetWorx for DeviceNet and RSLogix Guard PLUS!

IMPORTANT

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

DeviceNet Software

1753-DNSI

L+L24V dc

GuardPLC Controller

(—)4(—)

L-L- L+ L+

24V DC

RS-485

PROFIBUS

ASCII/HSP

COMM1

COMM2

COMM3

GuardPLC Ethernet

10/100 BaseT

(—)4(—)

24 V DC

RUN

ERROR

PROG

FORCE

FAULT

OSL

123456

1234

1L-

L-DO 2

(2A)

5L-D1678

1LS+- LS+ LS+ LS+ LS+L-D1234

1920 2122 23 24

1314 1516 17 18

1920 2122 23 241314 1516 23 24 2526 2728 29 30 3132 3334 35 36 37 38 3940 41 42

789101112

78910

1112

5L- L-DO 6

(2A)

13 L-D1141516

9L-D1101112

3132 3334 35 36

2526 2728 29 30

PC with RSLogix Guard

PLUS! Software

1753-L28BBBM

20 DC Inputs 8 DC Outputs

17 L-D1181920

3738 3940 41 42

1770-KFD PC

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!, Program Management

Programming Application Logic

RSLogix Guard PLUS!, Hardware Management

4.0 or higher

6.x or higher

DeviceNet Safety Scanner Features

character display

LED Indicators

Publication 1753-UM002A-EN-P - July 2005

Hardware Overview

Front View Bottom View

HSP Port

DeviceNet Safety Port

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-cast 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:

• 125 Kbps (default)

• 250 Kbps

• 500 Kbps

Physical Layout of the DeviceNet Safety System

Planning your system helps ensure that you can:

• meet safety times

• use memory and bandwidth efficiently

• fulfill device-specific requirements

• 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:

• system safety time requirements

• communication requirements

• I/O size

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

Publication 1753-UM002A-EN-P - July 2005

DeviceNet Safety I/O Performance Factors

Safety nodes have priority on a DeviceNet network, but the performance of DeviceNet Safety I/O modules can be affected by the:

• baud rate of the network (Lower baud rates mean slower transmissions and slower responses.)

• packet size for the various connections (Bigger packets may result in fragmented messages and slower responses than single-packet messages, but use fewer resources.)

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

• RPI of the devices (Lower RPIs consume more bandwidth but lower system reaction time.)

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 Rate

125K bit/s 420 m (1378 ft) 500 m (1640 ft) 100 m (328 ft) 156 m (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)

IMPORTANT

flat cable thick cable thin cable

If you change the communication rate of your

Maximum Distance

Cumulative Drop Line Length

network, make sure that all devices change to the new communication rate. Mixed 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 pushbuttons on the device

software Some devices require a programming device to set its address

Some devices have switches or a pushbutton that sets the communication rate. Typically, the switch or pushbutton lets you 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.

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

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 0 If you have multiple scanners, give them

the lowest addresses in sequence.

any device on your network, except the scanner

RSNetWorx for DeviceNet workstation

no device 63 Leave address 63 open. This is where a

1 to 61 Gaps between addresses are allowed

and have no effect on system performance. Leaving gaps gives you more flexibility as you develop your system.

62 If you connect a computer directly to the

DeviceNet network, use address 62 for the computer or bridging/linking device.

non-commissioned node typically enters the network.

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.

Publication 1753-UM002A-EN-P - July 2005

General Safety Information

Install the 1753-DNSI

Chapter

ATTENTION

Safety Applications

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

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 enclosure. Also, see the appropriate sections in this publication, as well as the Allen-Bradley publication 1770-4.1 (Industrial Automation Wiring and Grounding Guidelines), for additional installation requirements pertaining to this equipment.

1 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

This equipment is sensitive to electrostatic discharge, which can cause internal damage and affect normal operation. Follow these guidelines when you handle this equipment:

• Touch a grounded object to discharge potential static.

• Wear an approved grounding wrist-strap.

• Do not touch connectors or pins on component

boards.

• Do not touch circuit components inside the equipment.

• If available, use a static-safe workstation.

• When not in use, store the equipment in

appropriate static-safe packaging.

Mount the Scanner

Publication 1753-UM002A-EN-P - July 2005

IMPORTANT

For effective cooling:

• Because of thermal considerations, mount the module horizontally only.

• Provide a gap of at least 100 mm (3.94 in.) above, below, and on each side of the module.

• Provide a gap of at least 51 mm (2.0 in.) from the front face of the module to the door of the enclosure.

• Select a location where air flows freely or use an additional fan.

• Do not mount the module over a heating device.

Install the 1753-DNSI 2-3

The module can be DIN rail or panel-mounted as described in the following sections.

ATTENTION

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

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

Ground the Scanner

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.

ATTENTION

Functionally ground the module through its DIN rail connection or through the mounting foot, if panel-mounted.

Grounding Stamping

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.

Publication 1753-UM002A-EN-P - July 2005

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

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). 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 main power source is the external power supply.

Make Communication Connections

ATTENTION

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 nodes. The HSP port lets you communicate with a single GuardPLC 1600 or 1800 controller via a 1753-CBLDN cable.

Do not connect or disconnect either communications cable with power applied to this module or any device on the network, because an electrical arc can occur. This could cause an explosion in hazardous location installations.

Publication 1753-UM002A-EN-P - July 2005

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

IMPORTANT

Wire the connector according to the following illustrations:

Connect To

Red Wire V+

White Wire CAN High

Bare Wire Shield

Blue Wire CAN Low

Black Wire V-

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

DeviceNet cable

5-position linear plug

10-position linear plug

D D D D D

Red

White

Bare

Blue

Black

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-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. The minimum bend radius of the 1753-CBLDN is:

• 30 mm (1.18 in.) when the cable is permanently restrained by the use of a wire tie, cable trough, or other means.

• 60 mm (2.36 in.) when unrestrained.

IMPORTANT

(—)4(—)

ASCII/HSP

COMM3

GuardPLC Ethernet

10/100 BaseT

L-L- L+ L+

24V DC

RS-485

PROFIBUS

COMM2

COMM1

(—)4(—)

123456

1234

1L-

24 V DC

RUN

ERROR

PROG

FORCE

FAULT

OSL

1LS+- LS+ LS+ LS+ LS+L-D1234

13 14 15 1617 18

789101112

L-DO 2

(2A)

11 12

78910

5L- L-DO 6

7 8

(2A)

5L-D1678

9L-D11011 12

19 20 21 2223 24

25 26 27 2829 30

19 20 21 2223 2413 14 15 1623 24 25 26 27 2829 30 31 32 33 3435 36 37 38 3940 4142

1753-CBLDN

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.

13 L-D11415 16

31 32 33 3435 36

1753-L28BBBM

20 DC Inputs 8 DC Outputs

17 L-D11819 20

37 38 39 4041 42

Publication 1753-UM002A-EN-P - July 2005

2-8 Install the 1753-DNSI

Publication 1753-UM002A-EN-P - July 2005

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

Connect a Computer to the DeviceNet Network

To access a network, either:

• connect directly to the network, or

• connect to a different network and browse to the desired

network via a linking device

TIP

Once you choose a network:

• Install the communication card, if required.

• Determine any network parameters for the computer, such as a

network address.

• Connect the computer to the network using the correct cable.

RSLinx provides online help for configuring drivers and using linking (bridge) devices.

Configure a Driver for the Network

1. Start RSLinx® software.

2. Click on the Configure Driver button.

1 Publication 1753-UM002A-EN-P - July 2005

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

Make Sure the Driver Works

1. Check the Configure Drivers dialog to make sure that the driver is running.

Commission All Nodes

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 allow the node address to be set using the Node Commissioning tool in RSNetWorx for DeviceNet.

Publication 1753-UM002A-EN-P - July 2005

Refer to the DeviceNet Safety I/O Modules User Manual, publication number 1791DS-UM001, for information on commissioning 1791DS I/O modules.

+ 102 hidden pages