Compact I/O

DeviceNet Scanner
Module
Catalog Number 1769-SDN

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://literature.rockwellautomation.com) describes some important
differences between solid state equipment and hard-wired electromechanical
devices. Because of this difference, and also because of the wide variety of
uses for solid state equipment, all persons responsible for applying this
equipment must satisfy themselves that each intended application of this
equipment is acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for
indirect or consequential damages resulting from the use or application of
this equipment.
The examples and diagrams in this manual are included solely for illustrative
purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume
responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to
use of information, circuits, equipment, or software 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.

Identifies information about practices or circumstances that can cause

WARNING
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

IMPORTANT
understanding of the product.
Identifies information about practices or circumstances that can lead
ATTENTION
to personal injury or death, property damage, or economic loss.
Attentions help you identify a hazard, avoid a hazard, and recognize
the consequence

SHOCK HAZARD Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that dangerous voltage may be present.

BURN HAZARD Labels may be on or inside the equipment, for example, a drive or
motor, to alert people that surfaces may be dangerous temperatures.

Allen-Bradley, Rockwell Automation, TechConnect, Compact I/O, CompactLogix, Logix5000, RSNetWorx, RSNetWorx for
DeviceNet, MicroLogix, POINT I/O, PowerFlex,RSLinx, RSLogix, RSLogix 500, RSLogix 5000, Series 9000, RediSTATION, DH+,
SLC, PanelView Plus, and PLC-5 are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.
 Summary of Changes

The information below summarizes the changes to this manual since

the last printing.

To help you find new and updated information in this release of the
manual, we have included change bars as shown to the right of this
paragraph.

Chapter 8 contains updated troubleshooting information.

Appendix B, CompactLogix Backup on the DeviceNet Network,

documents new features and additional or updated information about
existing features.

3 Publication 1769-UM009D-EN-P - August 2007

4 Summary of Changes

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Table of Contents
Preface Who Should Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . 9
About the CompactLogix System . . . . . . . . . . . . . . . . . . . . . . 9
Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Common Techniques Used in This Manual. . . . . . . . . . . . . . 10
Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 1
Overview What You Need to Know . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Identify Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
What Your Scanner Module Does . . . . . . . . . . . . . . . . . . . . 13
Communicating with Your Slave Devices . . . . . . . . . . . . . . . 14
1769-SDN Scanner Module Data Tables . . . . . . . . . . . . . . . . 15
Input Data Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Output Data Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
RSNetWorx Software as a Configuration Tool . . . . . . . . . . . . 16

Chapter 2
Quick Start for Experienced Users Required Tools and Equipment . . . . . . . . . . . . . . . . . . . . . . 19
What You Need to Do. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3
Installation and Wiring Compliance to European Union Directives . . . . . . . . . . . . . . 23
EMC Directive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Low Voltage Directive . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
General Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Hazardous Location Considerations . . . . . . . . . . . . . . . . 25
Preventing Electrostatic Discharge . . . . . . . . . . . . . . . . . 26
Removing Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Reducing Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Protecting the Circuit Board from Contamination. . . . . . . 27
System Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
System Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
System Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Minimum Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Panel Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
DIN Rail Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Replace the Scanner Module within a System . . . . . . . . . . . . 33
Field Wiring Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Grounding the Scanner Module . . . . . . . . . . . . . . . . . . . 34
DeviceNet Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Scanner Module Power-up . . . . . . . . . . . . . . . . . . . . . . . . . 35

5 Publication 1769-UM009D-EN-P - August 2007

6 Table of Contents

Chapter 4
Configure the DeviceNet Network Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Install the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Use RSLinx Software to Configure Your DeviceNet Driver. . . 38
Use RSNetWorx Software to Configure the 1769-SDN Scanlist 40
Set Up an Online Connection . . . . . . . . . . . . . . . . . . . . . 40
Set the Node Address. . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configure the I/O Devices . . . . . . . . . . . . . . . . . . . . . . . 46
General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Module Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Scanlist Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Input Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Auto Device Replacement (ADR) Tab . . . . . . . . . . . . . . . 56
Summary Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Download and Save Your Configuration . . . . . . . . . . . . . 60

Chapter 5
DeviceNet I/O Image SDN Input File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Status Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Scan Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Device Failure Array . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Autoverify Failure Array . . . . . . . . . . . . . . . . . . . . . . . . . 65
Slave Device Idle Array . . . . . . . . . . . . . . . . . . . . . . . . . 66
Active Node Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Scanner Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Reserved Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Device Status Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Module Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Input Data Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
SDN Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Output Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Module Command Array . . . . . . . . . . . . . . . . . . . . . . . . 70
Output Data Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 6
Using the 1769-SDN Scanner
Module with CompactLogix
Controllers

Publication 1769-UM009D-EN-P - August 2007

 Table of Contents 7

Chapter 7
Using the 1769-SDN Scanner MicroLogix 1500 Controllers . . . . . . . . . . . . . . . . . . . . . . . . 75
Module with MicroLogix RSLogix 500 Software I/O Configuration . . . . . . . . . . . . . . . 76
Controllers Start the Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
I/O Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . 78
Read I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 79
Installed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
1769-SDN Scanner Module Configuration . . . . . . . . . . . . 80
Changing the 1769-SDN Configuration . . . . . . . . . . . . . . 81
Backplane Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
PCCC Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Program Upload and Download . . . . . . . . . . . . . . . . . . . . . 83
Configuring a Local DeviceNet Message . . . . . . . . . . . . . . . . 85
Message Setup Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 85
MSG Instruction Error Codes . . . . . . . . . . . . . . . . . . . . . . . . 92

Chapter 8
Troubleshooting Diagnostic Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Error Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Appendix A
1769-SDN DeviceNet Class Codes
Appendix B
CompactLogix Backup on the Using This Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
DeviceNet Network How the Backup Works . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Backup System Requirements. . . . . . . . . . . . . . . . . . . . 101
Configure the Backup System . . . . . . . . . . . . . . . . . . . . . . 102
Develop the CompactLogix Backup Application . . . . . . . . . 104
Backup Heartbeat Configuration Rungs. . . . . . . . . . . . . 104
Reading Backup State Rung . . . . . . . . . . . . . . . . . . . . . 108
Reading Backup Status . . . . . . . . . . . . . . . . . . . . . . . . . 110
Using Indicators to Check Status . . . . . . . . . . . . . . . . . . . . 111
Module Status Indicator . . . . . . . . . . . . . . . . . . . . . . . . 111
Node Address and Status Display . . . . . . . . . . . . . . . . . 112
Development and Debugging Tips. . . . . . . . . . . . . . . . . . . 114
Glossary
Index

Publication 1769-UM009D-EN-P - August 2007

8 Table of Contents

Publication 1769-UM009D-EN-P - August 2007

 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.
• conventions used in this manual.
• Rockwell Automation support.

Who Should Use This Use this manual if you are responsible for designing, installing,
programming, or troubleshooting control systems that use
Manual Allen-Bradley programmable controllers.

You should have a basic understanding of electrical circuitry and

familiarity with relay logic. If you do not, obtain the proper training
before using this product.

About the CompactLogix This manual focuses on the 1769-SDN scanner module. For detailed
information about using the 1769-SDN scanner module with a
System CompactLogix system, refer to DeviceNet Modules in Logix5000
Control Systems User Manual, publication DNET-UM004.

This manual guides the development of a control system that uses a

Logix5000 controller and a DeviceNet network. Topics covered
include configuring, bridging, connecting, and controlling your
DeviceNet network.

Purpose of This Manual This manual is a reference guide for the Compact I/O 1769-SDN
DeviceNet scanner module. It describes the procedures you use to
install, program, and troubleshoot your scanner module. This manual:

• provides instructions on installing the scanner module.

• contains information about using the scanner module on the
DeviceNet network.
• provides tips on troubleshooting the scanner module.
• contains application examples to show how the scanner module
is used with various programmable controllers.

9 Publication 1769-UM009D-EN-P - August 2007

Preface 10

Common Techniques Used The following conventions are used throughout this manual:
in This Manual • Bulleted lists such as this one provide information, not
procedural steps.
• Numbered lists provide sequential steps or hierarchical
information.

Additional Resources The following documents contain additional information concerning

Rockwell Automation products. Contact your local A-B distributor for
information on ordering the publications. For electronic copies, go to
http://literature.rockwellautomation.com.

Resource Description
DeviceNet Modules in Logix5000 Control Configuring the CompactLogix controllers in the DeviceNet network and bridging information
Systems User Manual, publication
DNET-UM004
ControlNet Modules in Logix5000 Control Configuring the CompactLogix controllers in the ControlNet network and bridging information
Systems User Manual, publication
CNET-UM001
RSNetWorx for DeviceNet Getting Results RSNetWorx for DeviceNet software (catalog number 9357-DNETL3)
Guide, publication DNET-GR001
CompactLogix System User Manual, Planning, mounting, wiring, and troubleshooting your CompactLogix system
publication 1769-UM007
MicroLogix 1500 Programmable Controllers Planning, mounting, wiring, and troubleshooting your MicroLogix 1500 system
User Manual, publication 1764-UM001
Compact I/O Analog Modules User Manual, Installing, configuring, and using Compact I/O analog modules
publication 1769-UM002
DeviceNet Interface User Manual, How to install and use the DeviceNet Interface (catalog number 1761-NET-DNI)
publication 1761-UM005
DeviceNet Media Design and Installation DeviceNet network planning information
Guide, publication DNET-UM072
DF1 Protocol and Command Set Reference IDF1 open protocol
Manual, publication 1770-6.5.16
Industrial Automation Wiring and Grounding and wiring Allen-Bradley programmable controllers
Grounding Guidelines, publication 1770-4.1
National Electrical Code - Published by the Wire sizes and types for grounding electrical equipment
National Fire Protection Association of
Boston, MA.

Publication 1769-UM009D-EN-P - August 2007

 Chapter 1

Overview

This chapter provides an overview of communication between the

CompactLogix and MicroLogix 1500 programmable controllers and
DeviceNet devices via the 1769-SDN scanner module. The
configuration data tables and the RSNetWorx for DeviceNet dialogs
used to configure the data tables are also described.

The following table identifies what this chapter contains and where to
find specific information.

Topic Page
What You Need to Know 11
Identify Module Features 12
What Your Scanner Module Does 13
Communicating with Your Slave Devices 14
1769-SDN Scanner Module Data Tables 15
RSNetWorx Software as a Configuration 16
Tool

What You Need to Know Before configuring your scanner, you must understand these items:

• Data exchange between the programmable controller and

DeviceNet devices through the scanner

• User-configurable scanner module data tables

• Role of RSNetWorx software

These topics are covered briefly in this chapter and in more detail
throughout the rest of the manual.

11 Publication 1769-UM009D-EN-P - August 2007

12 Overview

Identify Module Features Use the following figure to identify the features of the scanner.

2A

1 3A

8B
8A 4
8B

5
9

7A

3B
2B
7B

Features

Item Description
1 Bus lever (with locking function)
2A Upper DIN rail latch
2B Lower DIN rail latch
3A Upper panel mounting tab
3B Lower panel mounting tab
4 Module and Network status LEDs
5 Address and Error numeric display
6 Grounding screw
7A DeviceNet mating male receptacle
7B Removable DeviceNet female connector
8A Movable bus connector with female pins
8B Bus connector with male pins
9 Nameplate label

Publication 1769-UM009D-EN-P - August 2007

 Overview 13

What Your Scanner Module In a typical configuration, the scanner module acts as an interface
between DeviceNet devices and the programmable controller.
Does

DeviceNet Network
PLC with RSNetWorx
for DeviceNet Software

CompactLogix controller with MicroLogix 1500 Controller with

1769 SDN Scanner Module 1769-SDN scanner

1784-PCD
Interface Card

1734 POINT I/O E3 Overload MicroLogix 1000 controller MicroLogix 1200 controller
Relay PowerFlex 40 Driv e with 1761-NE T-DNI with 1761-NE T-DNI
Enhanced DeviceNet
Communic ations Module
31535M

The scanner module communicates with DeviceNet devices over the

network to:
• Read inputs from slave devices
• Write outputs to slave devices
• Communicate with peer devices (messaging)
• Upload/download programs to a 1764-LRP based MicroLogix
1500 controller across a DeviceNet network

Publication 1769-UM009D-EN-P - August 2007

14 Overview

Communicating with Your The scanner module communicates with devices via strobe, poll,
change of state, or cyclic I/O messages. It uses these messages to
Slave Devices solicit data from or deliver data to each device. Data received from the
devices, input data, is organized by the scanner module and made
available to the controller. Data sent from your controller, output data,
is organized in the scanner module and sent on to your devices.

• A strobe message is a multicast transfer of data that is 64 bits in

length sent by the scanner module that initiates a response from
each strobed slave device.

The strobe devices respond with their data, which can be as

much as 8 bytes of information. As a slave device, the scanner
module does not support the strobe message.

• A poll message is a point-to-point transfer of data from 0...128

bytes sent by the scanner module to the slave device.

The poll message also initiates a response from each poll slave.
The slave device responds with its input data from 0...128 bytes.

• A change-of-state message is a transfer of data sent whenever a

data change occurs.

A user-configurable heartbeat rate allows devices to indicate

proper operation during intervals between data changes.

• A cyclic message is a transfer of data sent at a specific

user-configurable rate, such as every 50 ms.

IMPORTANT Throughout this document, input and output are defined from
the controller’s point of view. Output is data sent from the
controller to a device. Input is data collected by the controller
from a device.

In addition to I/O messaging, the scanner module also supports PCCC

and CIP explicit messaging, defined later in this manual.

Publication 1769-UM009D-EN-P - August 2007

 Overview 15

1769-SDN Scanner Module To manage the flow of data between your controller and network
devices, the scanner module uses input and output data images to
Data Tables transfer data, status, and command information between the scanner
module and the MicroLogix controller.

For information about the CompactLogix image structure, refer to the

DeviceNet Modules in Logix5000 Control Systems User Manual,
publication DNET-UM004.

Input Data Image

The input data image is transferred from the scanner module to the
controller across the Compact I/O bus.

Word Description Data Type

0…65 Status structure 66-word array
66…245 DeviceNet slave inputs 180-word array

Output Data Image

The output data image is transferred from the controller to the scanner
module across the Compact I/O bus.

Word Description Data Type

0 and 1 Module command array 2-word array
2…181 DeviceNet slave outputs 180-word array

Module Command Array Bit Assignments

Word Bit Operating Mode

0 0 1 = run, 0 = idle
1 1 = fault
2 1 = disable network
3 Reserved(1)
4 1 = reset
5…15 Reserved(1)
1 0 …15 Reserved(1)
(1)
Do not manipulate Reserved Bits. Doing so may interfere with future compatibility.

Publication 1769-UM009D-EN-P - August 2007

16 Overview

RSNetWorx Software as a RSNetWorx software is used to configure the scanner’s slave devices.
This software tool connects to the scanner module over the DeviceNet
Configuration Tool network via an RS-232 interface (1770-KFD module) or PC card
(1784-PCD or 1784-PCID).

We recommend RSNetworx for DeviceNet software, version 3.00 or

later.

If your RSNetWorx configuration software does not include the

required electronic data sheet (EDS) file, go to
http://www.ab.com/networks/eds.

Register the new EDS file by using the EDS wizard in RSNetWorx
software. Access the wizard from the Tools menu. This configuration
tool lets you to identify all of the DeviceNet devices and their
locations in your system.

The controller must be in Program mode, or the scanner module in

Idle mode (bit 0 of the Module Command Array = 0) for the scanner
module to accept the configuration information.

Publication 1769-UM009D-EN-P - August 2007

 Overview 17

RSNetWorx Configuration Dialog Map

The main RSNetWorx dialog.

To browse the network,

click Online
and select the driver.

To access the 1769-SDN scanner module,

double-click the 1769-SDN icon.

To access the scanlist, Move the device into

click on the Scanlist tab. the scanlist.
To download the scanlist, click
Download to Scanner.

To automatically map input To automatically map output

devices, click the Input tab devices, click the Output tab
and click the AutoMap and click the AutoMap button.
button.
To edit a device’s I/O parameters,
double-click the device in
the scanlist.

Publication 1769-UM009D-EN-P - August 2007

18 Overview

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Chapter 2

Quick Start for Experienced Users

This chapter helps you get started using the 1769-SDN scanner
module. Procedures are based on the assumption that you have an
understanding of Allen-Bradley controllers. You should understand
electronic process control and be able to interpret the ladder logic
instructions required to generate the electronic signals that control
your application. Because it is a start-up guide for experienced users,
this chapter does not contain detailed explanations about the
procedures listed.

This table identifies what this chapter contains and where to find
specific information.

Topic Page
Required Tools and Equipment 19
What You Need to Do 20

Required Tools and Have the following tools and equipment ready:
Equipment • Personal computer
• Programmable controller: CompactLogix or MicroLogix 1500
system
• 1770-KFD RS-232 DeviceNet adapter, or 1784-PCD or 1784-PCID
DeviceNet interface card
• For network communication: RSLinx software, version 2.30 or
later
• For DeviceNet network configuration:
RSNetWorx for DeviceNet software, version 3.00 or later
• For ladder logic programming:
RSLogix 500 software, version 5.00.10 or later, or
RSLogix 5000 software, version 8.02 or later
• 1769-SDN scanner module
• Mounting hardware
• Screwdriver

19 Publication 1769-UM009D-EN-P - August 2007

20 Quick Start for Experienced Users

What You Need to Do Follow these steps to get started using the 1769-SDN scanner module.

1. Verify planned system configuration.

a. Ensure system power supply has sufficient current.

Maximum Current Draw

Module 5V dc 24V dc
1769-SDN 440 mA 0 mA

The scanner module cannot be located more than four

modules away from the system power supply.

b. Verify that the DeviceNet network has adequate power.

DeviceNet Power Requirements

Module DeviceNet Power Requirements

1769-SDN N.E.C. Class 2

90 mA @ 11V dc, max.

110 mA @ 25V dc, max.

200 mA for 1.5 ms inrush

2. Remove power.

Remove power before removing or inserting this module. When

ATTENTION
you remove or insert a module with power applied, an electrical
arc may occur. An electrical arc can cause personal injury or
property damage by:
• sending an erroneous signal to your system’s field devices,
causing unintended machine motion.
• causing an explosion in a hazardous environment.
Electrical arcing causes excessive wear to contacts on both the
module and its mating connector and can lead to premature
failure.

3. Assemble and mount the I/O bank.

The scanner module can be attached to an adjacent controller,

power supply, or I/O module. The scanner module can be panel
or DIN-rail mounted. Modules can be assembled before or after
mounting.

Be sure to observe minimum spacing guidelines for adequate

ventilation.

Publication 1769-UM009D-EN-P - August 2007

 Quick Start for Experienced Users 21

4. Ground the scanner module and complete the DeviceNet

network wiring.

5. Apply power to the system.

6. Be sure that the programming software and equipment is ready.

7. Use RSLinx to configure drivers.

8. Use RSNetWorx software to configure the 1769-SDN scanner

module and the DeviceNet devices.

9. Use RSLogix software to create your project and ladder logic.

10. Start the system.

a. Apply power.
b. Download your program and put the controller into Run
mode.
c. status indicators turn on solid green.

11. Monitor the scanner module status to check if the scanner

module is operating correctly.

Module status is reported by the status indicators and numeric

display on the front of the scanner module. The information is
also stored in the scanner module’s input data file, so these bits
can be used in your control program to flag an error.

Publication 1769-UM009D-EN-P - August 2007

22 Quick Start for Experienced Users

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Chapter 3

Installation and Wiring

This chapter describes how to install and wire the 1769-SDN scanner
module. This table describes what this chapter contains and where to
find specific information.

Topic Page
Compliance to European Union Directives 23
Power Requirements 24
General Considerations 25
System Planning 27
System Assembly 29
System Mounting 30
Replace the Scanner Module within a 33
System
Field Wiring Connections 34
Scanner Module Power-up 35

Compliance to European This product is approved for installation within the European Union
and EEA regions. It has been designed and tested to meet the
Union Directives following directives.

EMC Directive

The module is tested to meet Council Directive 89/336/EEC

Electromagnetic Compatibility (EMC) and the following standards, in
whole or in part, documented in a technical construction file:

• EN 50081-2
EMC – Generic Emission Standard, Part 2 - Industrial
Environment

• EN 50082-2
EMC – Generic Immunity Standard, Part 2 - Industrial
Environment

This product is intended for use in an industrial environment.

23 Publication 1769-UM009D-EN-P - August 2007

24 Installation and Wiring

Low Voltage Directive

This product is tested to meet Council Directive 73/23/EEC Low

Voltage, by applying the safety requirements of EN 61131-2
Programmable Controllers, Part 2 – Equipment Requirements and
Tests.

For specific information required by EN61131-2, see the appropriate

sections in this publication, as well as the following Allen-Bradley
publications:

• Industrial Automation, Wiring and Grounding Guidelines,

publication 1770-4.1
• Automation Systems Catalog, publication B113

Power Requirements The scanner module receives power through the Compact I/O bus
interface from the +5V dc system power supply.

Maximum Current Drawn by the Module

Module 5V dc 24V dc
1769-SDN 440 mA 0 mA

The scanner module also draws power from the DeviceNet network.

DeviceNet Power Requirements

Module DeviceNet Power Requirements

1769-SDN N.E.C. Class 2

90 mA @ 11V dc, max.

110 mA @ 25V dc, max.

200 mA for 1.5 ms, inrush

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 25

General Considerations The Compact I/O system is suitable for use in an industrial
environment when installed in accordance with these instructions.
Specifically, this equipment is intended for use in clean, dry
environments (Pollution Degree 2(1)) and to circuits not exceeding
Over Voltage Category II(2) (IEC 60664-1).(3)

Hazardous Location Considerations

This equipment is suitable for use in Class I, Division 2, Groups A, B,

C, D or nonhazardous locations only. The following WARNING
statement applies to use in hazardous locations.

WARNING
EXPLOSION HAZARD
Substitution of components may impair suitability for
Class I, Division 2.
Do not replace components or disconnect equipment unless
power has been switched off or the area is known to be
nonhazardous.
Do not connect or disconnect components unless power has
been switched off or the area is known to be nonhazardous.
This product must be installed in an enclosure.
All wiring must comply with N.E.C. article 501-4(b).

(1)
Pollution Degree 2 is an environment where, normally, only nonconductive pollution occurs except that
occasionally a temporary conductivity caused by condensation shall be expected.
(2)
Over Voltage Category II is the load level section of the electrical distribution system. At this level, transient
voltages are controlled and do not exceed the impulse voltage capability of the product’s insulation.
(3)
Pollution Degree 2 and Over Voltage Category II are International Electrotechnical Commission (IEC)
designations.

Publication 1769-UM009D-EN-P - August 2007

26 Installation and Wiring

Preventing Electrostatic Discharge

Electrostatic discharge (ESD) can damage integrated circuits or

ATTENTION
semiconductors if you touch the bus connector pins. Follow these
guidelines when you handle the module:
• Touch a grounded object to discharge static potential.

• Wear an approved wrist-strap grounding device.

• Do not touch the bus connector or connector pins.

• Do not touch circuit components inside the module.

• Use a static-safe work station, if available.

• Keep the module in its static-shield box when it is not in use.

Removing Power

Remove power before removing or inserting this module. When you

ATTENTION
remove or insert a module with power applied, an electrical arc may
occur. An electrical arc can cause personal injury or property damage
by:
• sending an erroneous signal to your system’s field devices,
causing unintended machine motion.

• causing an explosion in a hazardous environment.

Electrical arcing causes excessive wear to contacts on both the

module and its mating connector and can lead to premature failure.

Reducing Noise

We recommend installing this module in an industrial enclosure to

reduce the effects of electrical interference. Group your modules to
minimize adverse effects from radiated electrical noise and heat.

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 27

Protecting the Circuit Board from Contamination

The printed circuit boards of the modules must be protected from dirt,
oil, moisture, and other airborne contaminants. To protect these
boards, we recommend installing the system in an enclosure suitable
for the environment. The interior of the enclosure should be kept
clean and the enclosure door should be kept closed whenever
possible.

System Planning Consider the following when planning your system:

• The scanner module can communicate with up to 63 DeviceNet

devices.
• The scanner, as a master, can own up to 63 slave I/O nodes.
• The scanner module can simultaneously be a master and a slave
owned by another DeviceNet master.
• A 1769-ECR right end cap or 1769-ECL left end cap is required to
terminate the end of the Compact I/O bus.
• Each bank of Compact I/O modules must have its own power
supply.

A MicroLogix 1500 controller acts as the power supply for

modules directly connected to it.

• A Compact I/O power supply, or MicroLogix 1500 base unit, has

limits on the amount of +5V dc and +24V dc current it can
supply to modules in its I/O bank.

These limits depend on the catalog number of the power

supply, for example, 1769-PA2. A bank of modules must not
exceed the current limits of the I/O bank power supply or
MicroLogix 1500 base unit.

Refer to the Compact 1769 Expansion I/O Power Supplies

Installation Instructions, publication 1769-IN028, or the
MicroLogix 1500 User Manual, publication 1764-UM001.

• The scanner module has a distance rating of four, therefore, the

scanner module must be within four modules of the I/O bank’s
power supply.
• Determine the DeviceNet communication rate, based on
standard DeviceNet considerations.
• Consider the number of words of I/O data the host controller
supports.

Publication 1769-UM009D-EN-P - August 2007

28 Installation and Wiring

For more information on planning your DeviceNet network, refer to

the DeviceNet Media Design Installation Guide, publication
DNET-UM072.

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 29

System Assembly The scanner module can be attached to an adjacent controller, power
supply, or I/O module. This procedure shows you how to assemble
the Compact I/O system.
A
D
E
C
B

G
B
F

1. Disconnect power.

2. Check that the bus lever of the scanner module (A) is in the
unlocked (fully right) position.

3. Use the upper and lower tongue-and-groove slots (B) to secure

the modules together.

4. Move the scanner module back along the tongue-and-groove

slots until the bus connectors (C) line up with each other.

5. Use your fingers or a small screwdriver to push the bus lever

back slightly to clear the positioning tab (D).

6. Move the scanner module’s bus lever fully to the left (E) until it
clicks. Make sure it is locked firmly in place.

ATTENTION When attaching I/O modules, it is very important that the

bus connectors are securely locked together for a proper
electrical connection.

7. Attach an end cap terminator (F) to the last module in the

system by using the tongue-and-groove slots as before.

8. Lock the end cap bus terminator (G).

IMPORTANT A 1769-ECR or 1769-ECL right or left end cap must be

used to terminate the end of the serial communication
bus.

Publication 1769-UM009D-EN-P - August 2007

30 Installation and Wiring

System Mounting

ATTENTION During panel or DIN rail mounting of all devices, be sure that all
debris (metal chips, wire strands) is prevented from falling into
the module. Debris that falls into the module could cause
damage at power up.

Minimum Spacing

Maintain spacing from enclosure walls, wireways, and adjacent

equipment. Allow 50 mm (2 in.) of space on all sides for adequate
ventilation, as shown below.

Top

Compact I/O

Compact I/O

Compact I/O

Compact I/O

Compact I/O
Side Side

End Cap
Host Controller

Bottom

Allow at least 110 mm (4.33 in.) of enclosure depth to accommodate

the scanner module and the DeviceNet connector.

Panel Mounting

Mount the scanner module to a panel, using two screws per scanner
module. Use M4 or #8 panhead screws. Mounting screws are required
on every module.

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 31

Panel Mounting Using the Dimensional Drawing

All dimensions are in millimeters (inches). Hole spacing tolerance:

±0.4 mm (0.016 in.).

Compact I/O System with L35E CompactLogix Controller and Power

Supply
67.5mm 70mm 35mm
(2.68in) (2.76in) (1.38in)
15mm 52.5mm
(.59in) (2.06in)

132mm
(5.20in)
118mm
(4.65in)

52.5mm 35mm 35mm 35mm 35mm

(2.07in) (1.38in) (1.38in) (1.38in) (1.38in)

Compact I/O System with MicroLogix 1500 Base Unit and Processor

168 mm 35 mm
Mounting Hole (6.62 in.) (1.38 in.) 28.5 mm
Dimension (1.12 in.)
147 mm 35 mm
(5.79 in.) (1.38 in.)
(2.32 in.)
59 mm

147.4 mm (5.81 in.)

118 mm (4.65 in.)

132 mm (5.19 in.)

122.6 mm (4.83 in.)

(2.32 in.)
59 mm

DIN Rail
Center Line

13.5 mm 14.7 mm
(0.53 in.) (0.58 in.)

Publication 1769-UM009D-EN-P - August 2007

32 Installation and Wiring

Panel Mounting Procedure Using Modules as a Template

This procedure lets you use the assembled modules as a template for
drilling holes in the panel. Due to module mounting hole tolerance, it
is important to follow these procedures.
1. On a clean work surface, assemble no more than three modules.
2. Using the assembled modules as a template, carefully mark the
center of all module-mounting holes on the panel.
3. Return the assembled modules to the clean work surface,
including any previously mounted modules.
4. Drill and tap the mounting holes for the recommended M4 or #8
screw.
5. Place the modules back on the panel, and check for proper hole
alignment.
6. Attach the modules to the panel using the mounting screws.

If mounting more modules, mount only the last one of this

group and put the others aside. This reduces remounting time
during drilling and tapping of the next group.

7. Repeat steps 1...6 for any remaining modules.

DIN Rail Mounting

The module can be mounted using the following DIN rails:

35 x 7.5 mm (EN 50022 - 35 x 7.5) or 35 x 15 mm (EN 50022 - 35 x
15).

Before mounting the module on a DIN rail, close the DIN rail latches.
Press the DIN rail mounting area of the module against the DIN rail.
The latches will momentarily open and lock into place. DIN rail
mounting dimensions are shown below.

Dimension Height
A 118 mm (4.65 in.)
B 59 mm (2.325 in.)

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 33

Replace the Scanner The scanner module can be replaced while the system is mounted to
a panel (or DIN rail) once power is removed.
Module within a System
1. Remove power.

2. Remove the DeviceNet cable from the scanner module by

removing the DeviceNet connector.

3. Remove the upper and lower mounting screws from the scanner
module (or open the DIN rail latches using a flat-blade
screwdriver).

4. On the scanner module to be replaced and the right-side

adjacent module (or end cap if the scanner module is the last
module in the bank), move the bus levers to the right (unlock)
to disconnect the scanner module from the adjacent modules.

5. Gently slide the disconnected scanner module forward.

6. If you feel excessive resistance, make sure that you

disconnected the scanner module from the bus and that you
removed both mounting screws (or opened the DIN latches).

It may be necessary to rock the scanner module slightly from

front to back to remove it, or, in a panel-mounted system, to
loosen the screws of adjacent modules.

7. Before installing the replacement scanner, be sure that the bus

lever on the right-side adjacent module is in the unlocked (fully
right) position.

8. Slide the replacement scanner module into the open slot.

9. Connect the scanner module and modules together by locking

(fully left) the bus levers on the replacement scanner module
and the right-side adjacent module or end cap.

10. Replace the mounting screws (or snap the scanner module onto
the DIN rail).

11. Replace the DeviceNet cable on the scanner module by

attaching the connector to the scanner.

12. Restore the scanner module configuration using RSNetWorx for

DeviceNet software.

IMPORTANT Be sure that the new module has the same node address
and communication rate as the module that was
replaced.

Publication 1769-UM009D-EN-P - August 2007

34 Installation and Wiring

Field Wiring Connections Follow these procedures to wire the scanner module.

Grounding the Scanner Module

This product is intended to be mounted to a well-grounded mounting

surface, such as a metal panel. Additional grounding connections from
the scanner’s mounting tabs or DIN rail (if used), are not required
unless the mounting surface cannot be grounded.

ATTENTION The grounding screw on the front of the scanner module must
be connected to a suitable ground source when operating in
electrically noisy environments. Use a 2.1 mm2 (14 AWG) wire
to make this connection.

Refer to Industrial Automation Wiring and Grounding Guidelines,

Allen-Bradley publication 1770-4.1, for additional information.

DeviceNet Wiring

DeviceNet
Connector

Connect(1) To
Red Wire V+
Grounding Screw
White Wire CAN High
Bare Wire Shield
Use 2.1 mm2 (14 AWG
wire to connect to Blue Wire CAN Low
panel ground. Black Wire V-
(1)
DeviceNet cable colors are shown on the
wiring label on the front of the scanner

1. Connect the DeviceNet cable to the removable connector as

shown.
2. Insert the removable female connector into the mating male
connector on the DeviceNet scanner module.

Publication 1769-UM009D-EN-P - August 2007

 Installation and Wiring 35

3. Screw the removable connector to the scanner module case with

the upper and lower mounting screws to a torque of 0.6...0.7
Nm (5...6 in-lbs).

IMPORTANT If the 1769-SDN scanner module is the first or last device

connected to the DeviceNet network trunkline, be sure to add a
termination resistor (120 Ω 1% ≥ ¼W resistor, Allen-Bradley
part number 1485A-C2) across the Blue (CAN Low) and White
(CAN High) wires.

Scanner Module Power-up When power is applied via the Compact I/O bus, the scanner module
goes through a self test sequence. Upon successful completion of the
self test, the scanner module is ready to communicate.

The default scanner module settings are:

• Communication rate = 125 Kbps

• Node address = 63

Use your configuration software to change the communication rate

and node address.

Publication 1769-UM009D-EN-P - August 2007

36 Installation and Wiring

Publication 1769-UM009D-EN-P - August 2007

 Chapter 4

Configure the DeviceNet Network

This chapter describes how to configure the DeviceNet network using

RSLinx and RSNetWorx for DeviceNet software. This table describes
what this chapter contains and where to find specific information.

Topic Page
Software Versions 37
Install the Software 38
Use RSLinx Software to Configure Your 38
DeviceNet Driver
Use RSNetWorx Software to Configure the 40
1769-SDN Scanlist

Software Versions This table lists the software and revision level required to operate with
the 1769-SDN scanner module.

Function Software Version

Communication RSLinx 2.30 or later
DeviceNet configuration RSNetWorx for DeviceNet 3.00 or later
Ladder logic programming software RSLogix 500 5.00.10 or later
RSLogix 5000 8.02 or later

You will also need one of the following interfaces to use your
computer to communicate with the DeviceNet network:

• 1770-KFD RS-232 DeviceNet adapter

• 1784-PCD or 1784-PCID DeviceNet interface card

If your RSNetWorx configuration software does not include the

required Electronic Data Sheet (EDS) file, go to
http://www.ab.com/networks/eds.

Register the new EDS file using the EDS Wizard in RSNetWorx
software. Access the wizard from the Tools menu.

37 Publication 1769-UM009D-EN-P - August 2007

38 Configure the DeviceNet Network

Install the Software Follow these steps to install RSLinx and RSNetWorx software

1. Insert the software CD-ROM in the drive.

The CD-ROM supports Windows Autorun. If you have Autorun

configured, the installation will automatically start when you
insert the CD-ROM in your drive. If you do not have Autorun
configured, perform steps 2 and 3.

2. From the Windows Start menu, choose Run.

3. Browse for the Setup program on the CD-ROM and open it.

4. Follow the prompts that appear as you install the software.

After software installation is complete, you will use RSLinx software to

configure your DeviceNet driver and RSNetWorx software to configure
the network.

Use RSLinx Software to Follow these steps to configure the DeviceNet driver.
Configure Your DeviceNet 1. Start RSLinx software.
Driver

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 39

2. From the Communications menu, choose Configure Drivers.

3. From the Available Driver Types pull-down menu, choose

Add/New.

4. .Select your driver.

5. Your driver setup will depend on your particular system setup

(COM port, communication rate, node address). Choose the
appropriate settings for your system.

The software will take a few seconds to configure the driver.

Publication 1769-UM009D-EN-P - August 2007

40 Configure the DeviceNet Network

6. .Click OK.

7. Click OK to use the default driver name.

8. Minimize RSLinx software.

You will use the driver you just configured to browse and configure
the network with RSNetWorx software.

Use RSNetWorx Software This manual assumes a certain level of familiarity with RSNetWorx
to Configure the 1769-SDN software. For detailed information on RSNetWorx for DeviceNet
software, refer to your software’s documentation.
Scanlist
Set Up an Online Connection

Follow the procedure below to set up an online connection to the

DeviceNet network using the 1770-KFD driver.

1. Start RSNetWorx software.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 41

2. From the File menu, choose New.

If you have ControlNet configured on your system you may see
this dialog. Otherwise, proceed to step 4.

3. Select DeviceNet Configuration and click OK.

4. Click the Online button on the toolbar.

A list of the available networks will appear. Your list may be

different from that shown below, depending upon the drivers
you have configured on your system.

5. Select your DeviceNet driver and click OK.

You will be prompted to upload or download devices before
going online.

Publication 1769-UM009D-EN-P - August 2007

42 Configure the DeviceNet Network

6. Click OK to upload the devices and go online.

RSNetWorx software will begin browsing for network devices.

When the software is done browsing, your network is displayed.

RSNetWorx software performs a single pass browse when you

go online or choose the browse feature. The software will poll
for devices one time and display the results. If a node that was
online later goes offline, there will be no live indication in
RSNetWorx software. You must manually perform a browse to
detect the missing node.

To manually perform the browse, click the button.

If RSNetWorx software fails to find a device, check the physical

connection to the device. If the physical connection is intact,
verify that the device’s communication rate is the same as the
communication rate of the DeviceNet driver.

If your RSNetWorx software does not include the required

electronic data sheet (EDS) file, go to
http://www.ab.com/networks/eds.

Use the EDS Wizard in RSNetWorx software to register the new

EDS file. Access the wizard from the Tools menu.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 43

Set the Node Address

Once the network browse is complete, the node addresses appear to

the right of their icons.

Use this procedure to change the node address of devices on the

network (such as a photoeye). You can also change the network
communication rate (baud rate) of some devices. Depending upon the
device, you may need to cycle power for communication rate changes
to take effect.

The controller must be in Program mode, or the scanner module in

Idle mode (bit 0 of the Module Command Array = 0), for the scanner
module to accept the configuration information.

1. From the Tools menu, choose Node Commissioning.

Publication 1769-UM009D-EN-P - August 2007

44 Configure the DeviceNet Network

2. Click Browse.

3. Select the DeviceNet network.

The devices on the network will appear in the right panel of the
dialog.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 45

4. Select the device you are commissioning in the right panel and
click OK.

You will see the Node Commissioning dialog with the current
settings for your scanner module.

The default scanner module settings are as follows.

• Communication rate = 125 Kbps

• Node address = 63

5. In the Node Address box, enter the new node address.

6. Click Apply and Exit the dialog.

Publication 1769-UM009D-EN-P - August 2007

46 Configure the DeviceNet Network

Configure the I/O Devices

The information in this section will focus on the scanner module’s

configuration and parameters that you can change by using
RSNetWorx software.

This dialog shows how a DeviceNet network is shown within

RSNetWorx software. As you can see, node one is a 1769-SDN
scanner. To view or modify the scanner’s parameters, double-click on
the scanner module.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 47

General Tab

This dialog shows the properties that RSNetWorx software displays for
the 1769-SDN scanner module.

Available items are accessed through a series of tabs located across

the top of the dialog. The General tab is the default tab and provides
information relative to the module.

If you ever need product support, you will need to provide the
revision number when you contact Rockwell Automation Technical
Support.

Publication 1769-UM009D-EN-P - August 2007

48 Configure the DeviceNet Network

Module Tab

Interscan Delay

This parameter defines the delay time the scanner module uses
between scans of the DeviceNet network. If you have slave devices
configured for polled behavior in the 1769-SDN scanner module
scanlist, Interscan Delay (ISD) defines the amount of time the scanner
module waits between DeviceNet I/O updates.

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/download functions. So, if these
network functions are sluggish on your system, increase the ISD time.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 49

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 in the scanner’s input section.

Foreground/Background Polling Behavior

Each waveform shows polling frequency FX B1 B2 B3 B4 FX B1 B2 B3 B4 FX B1 B2 B3 B4 FX B1 B2 B3 B4
for the given Foreground to Background
Poll Ratio.
Poll Ratio = 1

FX B1 B2 FX B3 B4 FX B1 B2 FX B3 B4
Where:
Poll Ratio = 2
FX = x foreground slave devices.

B1 = 1st background slave device. FX B1 FX B2 FX B 3 FX B4

B2 = 2nd background slave device. Poll Ratio = 4

B3 = 3rd background slave device.

B4 = 4th background slave device.

Module Defaults

Clicking Module Defaults sets Interscan Delay and Foreground to

Background Poll Ratio to the following values:

• Interscan Delay: 10 ms
• Foreground to Background Poll Ratio: 1

Publication 1769-UM009D-EN-P - August 2007

50 Configure the DeviceNet Network

Slave Mode

Enable Slave mode only if you want to use this scanner module as a
slave. Clicking Enable Slave Mode opens this dialog.

This parameter enables the slave functionality of the scanner, and lets
you set the I/O behavior, with the amount of data to be exchanged.
The Slave mode settings are described in this table.

Slave Mode Settings

Connection Format Description

Strobed Not supported by the 1769-SDN scanner module.
Polled Values entered into Rx and Tx parameters define how
much data will be exchanged over the polled connection
that owns the scanner’s slave I/O. Maximum size is 128
bytes.
Change of State / Cyclic Values entered into Rx and Tx parameters define how
much data will be exchanged over the change of state or
cyclic connection that owns the scanner’s slave I/O.
Maximum size is 128 bytes.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 51

Advanced Module Settings

Clicking Advanced opens this dialog.

Expected Packet Rate (EPR)

When the scanner module opens a polled or strobed I/O connection,

it sets a maximum timeout (expected packet rate) with the device. If
the device does not receive a packet from the scanner module within
four times the EPR value, the slave device drops the connection. If the
scanner module does not receive a packet from the slave within four
times the EPR value, it drops the connection and periodically attempts
to open a new connection.

When a connection is dropped, status bits in the scanner module

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

The EPR default value is 75 ms.

IMPORTANT Changing the EPR number should be done carefully because it

effects how long it takes the scanner module to detect a
missing device.

Transmit Retries

Transmit Retries specifies the number of times the scanner module

attempts to retransmit a change of state or cyclic message that has not
been acknowledged by the slave device. The connection is not
necessarily dropped as a result of reaching the retry limit.

Publication 1769-UM009D-EN-P - August 2007

52 Configure the DeviceNet Network

Scanlist Tab

The Scanlist defines which devices on the DeviceNet network are

owned by the scanner.

Available Devices

These are the devices on the network that have the ability to be slave
I/O devices. 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 module on the same network, or they may have dual
functionality. An example of a dual function device is the
1761-NET-DNI module. The DNI can be used as slave I/O, or as a
communication interface for PLCs or other DF1 full-duplex devices.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 53

Scanlist

These devices have been assigned to be slave I/O to this scanner. A

slave device on the DeviceNet network can be owned by only one
master at a time. Devices in the scanlist are configured using the input
and output tabs.

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.

If you do select Automap, you will be prompted to choose how the

data should be aligned in the scanner.

Edit I/O Parameters

These parameters will vary depending upon the slave device.

Information on configurable parameters is usually provided in the
device’s documentation.

Electronic Key

The electronic key is used to make sure that a particular slave device
always matches the intended device when the scanner module
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, Product Code, Major Revision,
and Minor Revision may be incrementally added.

For Major and Minor Revisions, you can select or higher to indicate
that either an exact match, or some higher revision value of the
revision is required.

If the scanner module detects a mismatch with any of the key

parameters checked, an AutoVerify failure will occur for that slave
device and the scanner module will not continue the connection
allocation process.

Publication 1769-UM009D-EN-P - August 2007

54 Configure the DeviceNet Network

Input Tab

The input tab dialog lets you to define how data from all of the
scanner’s slave devices are mapped into the input image of the
controller.

In this example, four input devices are mapped into the scanner’s
input image. The dialog shows each device’s:

• node number.
• catalog number.
• type of connection that is used between the scanner module and
the slave device (strobed, polled, cyclic, or change of state).
• the amount of data that will be exchanged (in bytes).
• the word within the controller’s input image where the data will
appear.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 55

Advanced

The scanner module allows each node’s slave data to be broken up

(segmented) into separate input image areas. This capability lets you
group data from multiple slave nodes into contiguous memory
locations. This is simply an ease-of-use feature. For maximum
performance, do not segment a slave device’s data.

Output Tab

The output tab dialog lets you define how data from the scanner
module is mapped to the outputs of the slave devices.

Publication 1769-UM009D-EN-P - August 2007

56 Configure the DeviceNet Network

In this example, four output devices are mapped into the scanner’s
output image. The dialog box shows each device’s:

• node number.
• catalog number.
• type of connection that is used between the scanner module and
the slave device (strobed, polled, cyclic, or change of state).
• the amount of data that will be exchanged (in bytes).
• the word within the controller’s output image.

Auto Device Replacement (ADR) Tab

The Auto Device Replacement feature automates the replacement of a

failed slave device on a DeviceNet network by returning it to the prior
level of operation. This includes Configuration Recovery (CR) and
Auto-address Recovery (AAR).

CR allows a slave device to be removed from the network and

replaced with an identical slave device configured at the same
communication rate and node address as the device being replaced.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 57

AAR allows a slave device to be removed from the network and

replaced with another identical slave device that is residing on the
network at node address 63 and is not in the scan list. The
replacement device will have its node address automatically changed
to that of the device being replaced. Depending on the level of
revision keying, it may be possible for the node address of the
replacement device to be changed but not brought online due to a
revision-keying mismatch.

The 1769-SDN scanner module can handle any number of device

failures simultaneously, however, the AAR feature will be disabled for
devices that have the same electronic key. The CR feature will remain
active. In this case, you must use the Node Commissioning tool that
ships with RSNetWorx for DeviceNet software to change the node’s
address.

If the electronic key of the replacement device differs only by

revision, the CR feature may not work. Before replacing any device,
you should make sure that the configuration parameters of the
replacement device are compatible with the existing device.

IMPORTANT This behavior may introduce a possible safety hazard for

devices such as drives. Use the full electronic key, including
revision. To enable electronic key revision checking, you must
be using a 1769-SDN scanner module and RSNetWorx for
DeviceNet software.

Important Considerations

Keep the following in mind when using the ADR feature with
RSNetWorx for DeviceNet software:

• ADR is intended for use in single-master environments.

• The CR and AAR features can be used only with devices that are
in the scanlist of the scanner.
• The AAR feature can be enabled for a device only if the CR
feature is also enabled.
• The CR feature cannot be enabled for devices that have no
writable parameters (for example, a device that is entirely
configured using hardware switches).

RSNetWorx for DeviceNet software will notify you of devices

that have no writable parameters.

• The AAR feature will not work for devices that do not support
changing the node address over the network.

Publication 1769-UM009D-EN-P - August 2007

58 Configure the DeviceNet Network

Configure ADR Parameters

On the ADR tab, you can configure the ADR parameters for the
1769-SDN scanner module. Using the controls on this tab, you can
select ADR parameters and enable or disable this functionality either
globally or on a device-specific basis.

Configure each device on the network. If online, make sure that the
configuration is synchronized with the online devices.

1. On the ADR tab, select the device you want to configure to use
ADR.

2. Click Load Device Config.

This will load the configuration of each device selected into the
scanner module configuration software. If you are online, but
did not upload the network, the configuration retrieved for the
devices may not be what is actually used online.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 59

3. Click the Configuration Recovery checkbox.

Notice the ADR space (in

bytes) is displayed for the
module you are updating.

4. Click the Auto-Address Recovery checkbox if desired.

The Enable Auto-Address Recovery checkbox needs to be

checked in order for AAR to work.

5. Repeat steps 1...4 for each desired module.

Notice that Both indicates Configuration Recovery and

Auto-Address Recovery are enabled while Config indicates that
only Configuration Recovery is enabled.

6. When finished, click Download to Scanner.

7. Click Apply or OK.

Publication 1769-UM009D-EN-P - August 2007

60 Configure the DeviceNet Network

Summary Tab

The summary tab provides a condensed picture of the scanner’s

configuration: which nodes are mapped, if they are active, and receive
and transmit information.

Download and Save Your Configuration

Follow these steps to download and save your configuration.

1. Click the Scanlist tab and then Download to Scanner.

2. Click All Records.

3. Click Download to download the configuration to the scanner.

4. Click OK to complete the DeviceNet scanner module

configuration.

Publication 1769-UM009D-EN-P - August 2007

 Configure the DeviceNet Network 61

5. From the File menu, choose Save As.

6. Save the configuration to a DeviceNet file.

7. Close RSNetWorx software.

Publication 1769-UM009D-EN-P - August 2007

62 Configure the DeviceNet Network

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Chapter 5

DeviceNet I/O Image

This chapter describes the input and output data structure. This table
describes what this chapter contains and where to find specific
information.

Topic Page
SDN Input File 63
Status Structure 64
Module Status Register 69
Input Data Image 69
SDN Output File 70
Output Data Image 71

SDN Input File The 1769-SDN scanner module’s input image is configurable up to 246
words. The input image is broken up into two primary components,
the status area and the input data area.

Input Image

Name Size Word Offset

Status Structure 66-words (fixed) 0…65
Input Data Image 180-word array (configurable) 66…245

63 Publication 1769-UM009D-EN-P - August 2007

64 DeviceNet I/O Image

Status Structure The first area of the input image is the Status Structure. The status
words are described in more detail in the following sections.

Description Words Data Type

Scan counter 0 and 1 2 words
Device failure array 2…5 64-bit array
Autoverify failure array 6…9 64-bit array
Slave device idle array 10…13 64-bit array
Active node array 14…17 64-bit array
Reserved(1) 18…19 4-byte array
Scanner module status 20 and 21 4-byte array
Reserved array(1) 22…31 20-byte array
Device status array 32…63 64-byte array
Module status register 64 and 65 2 words
(1)
Do not manipulate reserved bits. Doing so may interfere with future compatibility.

Scan Counter

This 32-bit unsigned value is incremented each time the DeviceNet

network is scanned. The value will automatically roll over to zero and
continue counting.

Publication 1769-UM009D-EN-P - August 2007

 DeviceNet I/O Image 65

Device Failure Array

These 64 bits provide status information for use in your control

program. For each slave device owned by the scanner, you should
monitor the respective bit within these four words. If a slave device
faults, the bit that corresponds to that node address will be set (1). If a
slave device is not faulted or returns from a faulted state to an
operating state, the corresponding bit for that node will be cleared (0).

Slave Device Status Information

Input Word Bit 0...15 Description

2(1) Node 0…15 Bit ON (1) = Slave node faulted

3(2) Node 16…31 Bit OFF (0) = Slave node not faulted

4(3) Node 32…47

5(4) Node 48…63

(1)
Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15.
(2)
Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
(3)
Bit 0 corresponds to Node 32, Bit 1 corresponds to Node 33 … Bit 15 corresponds to Node 47.
(4)
Bit 0 corresponds to Node 48, Bit 1 corresponds to Node 49 … Bit 15 corresponds to Node 63.

Autoverify Failure Array

These four words allow the control program to monitor if a slave’s

Device Key and Size matches the Device Key and Size in the scanner.
A bit value of 0 (OFF) represents a configuration match, a bit value of
1 (ON) represents a mismatch.

ATTENTION A value of 0 does not indicate that the slave has been brought
online or is functional, only that there is a configuration match
between the slave and the scanner.

Publication 1769-UM009D-EN-P - August 2007

66 DeviceNet I/O Image

Slave Device Configuration Comparison to Scanner Module Configuration

Input Word Bit 0...15 Description

6 (1) Node 0…15 Bit ON (1) = Slave node mismatch

7(2) Node 16…31 Bit OFF (0) = Slave node match

8(3) Node 32…47

9(4) Node 48…63

(1)
Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15.
(2)
Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
(3)
Bit 0 corresponds to Node 32, Bit 1 corresponds to Node 33 … Bit 15 corresponds to Node 47.
(4)
Bit 0 corresponds to Node 48, Bit 1 corresponds to Node 49 … Bit 15 corresponds to Node 63.

Slave Device Idle Array

The slave device idle array contains 64 bits of data. Each bit indicates
the state of a slave device. A bit value of 0 represents a Non-idle mode
or that the slave is not present in the scanlist. A bit value of 1
represents Idle mode where the slave node is present in the scanlist.

Slave Device Status

Input Word Bit 0...15 Description

10(1) Node 0...15 Bit ON (1) = Idle

11(2) Node 16…31 Bit OFF (0) = Non-idle

12(3) Node 32…47

13(4) Node 48…63

(1)
Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15.
(2) Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
(3)
Bit 0 corresponds to Node 32, Bit 1 corresponds to Node 33 … Bit 15 corresponds to Node 47.
(4)
Bit 0 corresponds to Node 48, Bit 1 corresponds to Node 49 … Bit 15 corresponds to Node 63.

Publication 1769-UM009D-EN-P - August 2007

 DeviceNet I/O Image 67

Active Node Array

The Active Node array contains 64 bits of data that represents each
slave node’s status. A slave node is considered active when it is
present and enabled in the master’s scanlist. A bit value of 0 means
Not Active, a bit value of 1 means Active.

Slave Node Status

Input Word Bit 0...15 Description

14(1) Node 0…15 Bit ON (1) = Active node

15(2) Node 16…31 Bit OFF (0) = Inactive node

16(3) Node 32…47

17(4) Node 48…63

(1)
Bit 0 corresponds to Node 0, Bit 1 corresponds to Node 1 … Bit 15 corresponds to Node 15.
(2) Bit 0 corresponds to Node 16, Bit 1 corresponds to Node 17 … Bit 15 corresponds to Node 31.
(3)
Bit 0 corresponds to Node 32, Bit 1 corresponds to Node 33 … Bit 15 corresponds to Node 47.
(4)
Bit 0 corresponds to Node 48, Bit 1 corresponds to Node 49 … Bit 15 corresponds to Node 63.

Scanner Module Status

The Scanner Device Status is a 4-byte array.

Scanner Device Status

Input Word Bit Description

20 0…7 (lower byte) Scanner Address in BCD
8…15 (upper byte) Scanner Status in BCD
21 0…7 (lower byte) Slave Device Address in BCD
8…15 (upper byte) Slave Device Status in BCD

Publication 1769-UM009D-EN-P - August 2007

68 DeviceNet I/O Image

Reserved Array
Reserved Array

Input Word Description(1)

22…31 Always 0
(1)
Do not manipulate reserved bits. Doing so may interfere with future compatibility.

Device Status Array

The Device Status Array is a 64-byte array containing the information
shown in this table. Each byte indicates the status code of the
scanner’s master and the slave devices.

Device Status
Input Word Bit Description
32 0…7 (lower byte) Node 0 DeviceNet status
8…15 (upper byte) Node 1 DeviceNet status
33 0…7 (lower byte) Node 2 DeviceNet status
8…15 (upper byte) Node 3 DeviceNet status
... ... ...
63 0…7 (lower byte) Node 62 DeviceNet status
8…15 (upper byte) Node 63 DeviceNet status

Publication 1769-UM009D-EN-P - August 2007

 DeviceNet I/O Image 69

Module Status Register

The scanner module supports a 32-bit Module Status Register.

Input Word Bit Description Operation

64 0 Run Bit ON (1) = scanning I/O

Bit OFF (0) = halted

1 Fault Bit ON (1) = faulted

Bit OFF (0) = not faulted

2 Network disable Bit ON (1) = disabled

Bit OFF (0) = not disabled

3 Device failure Bit ON (1) = failure
4 Autoverify failure
Bit OFF (0) = no failure
5 Communication failure
6 Duplicate node failure
7 DeviceNet power detect Bit ON (1) = power

Bit OFF (0) = no power

8...15 Reserved(1) N/A
65 0...15 Reserved(1) N/A
(1)
Do not manipulate reserved bits. Doing so may interfere with future compatibility.

Input Data Image

The Input Data Image can be up to a 180-word array as shown
below:.

Word Offset Description

66…245 DeviceNet Slave input and/or master output data

The Input Data Image is mapped using RSNetWorx for DeviceNet

configuration software.

Publication 1769-UM009D-EN-P - August 2007

70 DeviceNet I/O Image

SDN Output File Output Array

The scanner module supports up to 182 output words. This array is

broken up into two distinct data segments.

Name Size Word Offset

Module Command Array 2 words 0 and 1
Output Data Image 180-word array 2…181

Module Command Array

The module command array is the primary control interface between

your control program and the module.

Output Bit Description Behavior

Word
0 0 Run This bit controls when the module scans its
mapped slave devices. When set (1), the
scanner module will process I/O data as
defined by its scanlist. To actually scan the
network the Fault and Disable Network
command bits must be clear (0).
1 Fault When set, the scanner’s I/O mode will be
Halt; messaging will still operate. The fault
bit is primarily used to artificially set the
slave devices into a fault state due to some
event or condition within the control
program.
2 Disable network When set, the scanner module is
functionally removed from the network.
3 Reserved(1) N/A
4 Reset Restarts access to the DeviceNet network.
5…15 Reserved(1) N/A
1 16…31 Reserved(1) N/A
(1) Do not manipulate reserved bits. Doing so may interfere with future compatibility.

Publication 1769-UM009D-EN-P - August 2007

 DeviceNet I/O Image 71

Output Data Image The Output Data Image can be up to a 180 word array. The
controllers output data will be delivered across the DeviceNet
network to the destination slave devices. The scanner’s scanlist
configuration will determine how this data is actually sent to the slave
device (polled, cyclic, or change of state).

Output Word Description

2…181 DeviceNet Slave output and/or master input data

Slave mapping is done using RSNetWorx software.

Publication 1769-UM009D-EN-P - August 2007

72 DeviceNet I/O Image

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Chapter 6

Using the 1769-SDN Scanner Module with

CompactLogix Controllers

For information on using the 1769-SDN scanner module with

CompactLogix controllers, refer to the DeviceNet Modules in
Logix5000 Control Systems User Manual, publication DNET-UM004.

73 Publication 1769-UM009D-EN-P - August 2007

74 Using the 1769-SDN Scanner Module with CompactLogix Controllers

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Chapter 7

Using the 1769-SDN Scanner Module with

MicroLogix Controllers

This chapter contains an example in which the 1769-SDN scanner

module is used with a MicroLogix 1500 controller. This table describes
what this chapter contains and where to find specific information.

Topic Page
MicroLogix 1500 Controllers 75
RSLogix 500 Software I/O Configuration 76
Backplane Messaging 82
Program Upload and Download 83
Configuring a Local DeviceNet Message 85

MicroLogix 1500 The MicroLogix 1500 programmable controller has two different
processors that are compatible with the 1769-SDN scanner module.
Controllers The 1764-LSP and 1764-LRP processors can use the scanner module as
a DeviceNet master and own DeviceNet slave devices. This allows
either processor to communicate with intelligent devices like drives,
scales, and starters, or use the DeviceNet network to expand the
processor’s I/O capacity.

The 1764-LRP processor allows messaging functionality over the

DeviceNet network, so non-I/O data may be exchanged. Multiple
1769-SDN scanner modules may be used in a 1764-LRP system.
However only the first two scanners can be used for messaging.

The amount of power that modules draw from the processor or

expansion power supply, and the amount of data that the processor
can support will determine how many can be used. To determine if an
application can be supported, configuration tools are available from
http://www.ab.com/micrologix.

In addition to electrical limitations, data space limitations also exist.

The maximum size of the input and output images for each module in
the system is 250 input and 250 output words of data.

75 Publication 1769-UM009D-EN-P - August 2007

76 Using the 1769-SDN Scanner Module with MicroLogix Controllers

RSLogix 500 Software I/O One of the advanced features of RSLogix 500 software is the ability to
have the programming software establish a communication
Configuration connection with the controller and read which I/O modules are
attached to the controller. This capability significantly reduces the
effort involved in configuring a system.

This section illustrates how to determine which I/O modules are

attached to the controller, and manually configure the modules. We
will then configure the scanner. An example network is shown below.

DeviceNet Network Personal Computer Running RSNetWorx

for DeviceNet Software

MicroLogix 1500 Controller I/O Bank

with 1769-SDN Scanner Module

1770-KFD PC
Communication
Module

DANGER
DANGER

Series 9000 MicroLogix 1000 Controller MicroLogix 1200 Controller

Photoeye Connected via 1761-NET-DNI Connected via 1761-NET-DNI
RediSTATION
Interface Interface Interface

1305 Drive Connected via 1203-GU6

Enhanced DeviceNet Communication Module

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 77

Start the Project

Follow these steps to begin your project.

1. Open RSLogix 500 software.

2. Choose File ⇒New ⇒MicroLogix 1500 LRP series C.

This dialog should match what you see on your computer.

In this example the name for this application is TEMP. In the

TEMP dialog, you see everything associated with the
application. Within the Controller folder you will see I/O
Configuration.

3. Double-click I/O Configuration.

Publication 1769-UM009D-EN-P - August 2007

78 Using the 1769-SDN Scanner Module with MicroLogix Controllers

I/O Configuration Screen

The I/O configuration dialog shows each of the controller I/O slots.
For the MicroLogix 1500 controller, slot 0 contains the embedded I/O
that is part of the MicroLogix 1500 base unit. Slots 1...16 are for
Compact I/O expansion modules (referred to as local I/O, because
they are physically attached to the controller). Slots 9...16 are available
using only a series C processor with a series B base unit.

To have RSLogix 500 software read the controller’s local I/O and
configure the slots automatically, click Read I/O Config.

To manually configure the controller I/O, drag the appropriate

modules from the available list (right pane), to the appropriate slot on
the left. Modules must be contiguous (with no open slots) from 1...16.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 79

Read I/O Configuration

Next you see a communication dialog that lets you select a

communication path by using RSLinx software to connect to the
MicroLogix controller.

If you have previously connected to a controller, the communication

driver that you used before will be the active driver. This dialog
provides the ability to change the driver or perform a Who Active
across a network to locate the specific MicroLogix controller.

If the driver and path are correct, click Read I/O Config.

Installed I/O

RSLogix 500 software displays all of the I/O modules that are attached
to the MicroLogix controller.

In this example, there is a 1769-SDN scanner module at slot 1, and a

16-point digital input module in slot 2.

Publication 1769-UM009D-EN-P - August 2007

80 Using the 1769-SDN Scanner Module with MicroLogix Controllers

1769-SDN Scanner Module Configuration

To configure a specific module, double-click the module. To configure

the scanner module in this example, double-click the module in slot 1.

Input Words

This is the number of input words the controller assigns to the

module. The first 66 words (0...65) are required by the scanner
module for status. DeviceNet slave input data words start at slot word
66. You can have a maximum of 180 input words for DeviceNet slave
devices (maximum slot amount for 1769-SDN scanner module inputs
= 246).

Output Words

This is the number of output words the controller assigns to the

module. The first two words (0 and 1) are required by the scanner
module for status. DeviceNet slave output data words start at slot
word 2. You can have a maximum of 180 output words for DeviceNet
slave devices (maximum slot amount for scanner module outputs =
182).

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 81

Changing the 1769-SDN Configuration

You can change (add or remove) the amount of data the controller
has assigned to the scanner module in the expansion module
configuration dialog. From within RSLogix 500 software, I/O
configuration, open the 1769-SDN scanner module and change the
input or output words as needed. Save the program and download to
the controller.

Reducing the number of words for either inputs or outputs will

require a change in the 1769-SDN scanner module’s scanlist, which is
done using RSNetWorx software.

IMPORTANT We recommend that you not reduce the number of words

assigned to a 1769-SDN scanner module’s scanlist once a
system is operational. Changing the number of words may
cause addressing problems on the controller side, and mapping
changes on the DeviceNet network.
Adding words to an existing system is relatively easy to do,
because it doesn’t affect existing addresses or mapping. Add
the number of additional words that are needed in the module
(using the above example), and change the scanlist using
RSNetWorx software.

Publication 1769-UM009D-EN-P - August 2007

82 Using the 1769-SDN Scanner Module with MicroLogix Controllers

The configuration dialog for the scanner module is shown below.

Ignore Configuration Error

Checking (enabling) the Ignore Configuration error checkbox instructs
the module to ignore I/O size mismatches. If this is checked and the
input/output scanlist configured by RSNetWorx software (DeviceNet
side of the 1769-SDN scanner module) does not match the amount of
I/O data assigned by the controller (0...180 words), the module will
not generate an error.

If this checkbox is not checked, the number of data words on the

controller side must match the number of words configured by
RSNetWorx software. The default condition is unchecked (report an
error on mismatch).

Series/Major Rev/Minor Rev

You will need this information if you contact Rockwell Automation

Technical Support.

Backplane Messaging The MicroLogix 1500 1764-LRP processor and the 1769-SDN scanner
module also support backplane messaging. This new level of
functionality allows the processor to read (get) or write (set) data to
other devices on the DeviceNet network. This is also referred to as
Explicit Messaging.

You can use two different types of messages to exchange information

with the DeviceNet device. The type of message used is determined
by the destination device. You can generate a PCCC message or a CIP
message.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 83

PCCC Messaging
Programmable controller communications commands (PCCC)
provides point to point and master/slave communication between
devices. PCCC is an open protocol that is built into all Allen-Bradley
controllers, and many other Allen-Bradley and third-party products.

PCCC messaging has been used for many years on DH-485, DH+, and
Ethernet networks, and for point-to-point communication between
Allen-Bradley controllers. PCCC messaging lets you upload or
download programs over the DeviceNet network, and allows users to
message across DeviceNet networks, just like they did using DH-485
or DH+ networks. There are a number of devices that support PCCC
messaging over DeviceNet, including the 1761-NET-DNI (DNI)
interface, 1203-GU6 interface, and RSLinx software. If the DeviceNet
network has DNI interfaces, either device can initiate a PCCC
message.

Program Upload and Before performing a program upload or download through the
scanner, be sure that the module is properly installed in the system,
Download and that a terminator is present at the end of the Compact I/O
expansion bus.

IMPORTANT DeviceNet networks can operate at 125 Kbps, 250 Kbps, or 500
Kbps. Depending on network size and communication activity,
performing program upload or download operations while the
network is controlling an application may impact control system
performance. It is up to you to know and understand how
upload and download will impact operations.

Publication 1769-UM009D-EN-P - August 2007

84 Using the 1769-SDN Scanner Module with MicroLogix Controllers

To upload or download programs with RSLogix 500 software, choose

Comms ⇒System Comms.

System Comms will generate an RSLinx software dialog similar to the

example below.

In this example, the DeviceNet interface is a 1770-KFD module.

Selecting the 1770-KFD driver will show the devices on the DeviceNet
network.
In this example, upload or download can be performed with the
devices at nodes 5, 6, 7, and 32. Node 32 is a 1769-SDN module.
Simply highlight the 1769-SDN module and click either Upload or
Download on the right side of the screen.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 85

Configuring a Local This section describes how to configure a local message by using the
scanner module and a MicroLogix 1500 1764-LRP processor.
DeviceNet Message

Message Setup Dialog

Rung 0 shows a standard RSLogix 500 message (MSG) instruction

preceded by conditional logic.

Access the Message Setup dialog by double-clicking the Setup Screen.

The RSLogix 500 Message Setup dialog appears. This dialog is used to
set up or monitor message parameters for this controller, target device,
and control bits. Descriptions of each of these sections follow.

Channel Parameter

The 1764-LRP controller supports three different pathways for

messaging. Channels 0 and 1 are RS-232 ports and are functionally
identical to MicroLogix 1200 and MicroLogix 1500 1764-LSP
controllers. The 1764-LRP controller also supports backplane

Publication 1769-UM009D-EN-P - August 2007

86 Using the 1769-SDN Scanner Module with MicroLogix Controllers

communication through the Expansion Communication Port (ECP) as

illustrated below.

When ECP is chosen, you are able to select which slot position (1...16)
the scanner module resides in. The 1764-LRP processor can support
up to two 1769-SDN scanner modules with full messaging
functionality.

You can use multiple 1769-SDN scanner modules in a MicroLogix

1500 system, but you can message only through the first two. Any
other 1769-SDN scanner module can be used only for I/O scanning.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 87

Communication Command

The 1764-LRP controller supports the six standard types of

communication commands (same as all other MicroLogix 1200 and
1500 controllers) and CIP Generic. When any of these six standard
commands are chosen, you can initiate standard messages to
destination devices connected to DeviceNet products that support
PCCC messaging (including MicroLogix and SLC controllers using
1761-NET-DNI interfaces, and other MicroLogix 1500 controllers using
1769-SDN scanner modules). You can initiate reads, writes, program
upload/download and online monitoring across DeviceNet. This is
functionally identical to DH-485 and DH+ networking.

Publication 1769-UM009D-EN-P - August 2007

88 Using the 1769-SDN Scanner Module with MicroLogix Controllers

CIP Generic

Control & Information Protocol (CIP) is a newer and more versatile

protocol than PCCC. It is an open protocol that is supported by newer
Allen-Bradley controllers and third-party products.

CIP messaging is the native messaging format for the DeviceNet

network. All DeviceNet devices are compliant with CIP messaging.
The MicroLogix 1500 1764-LRP processor (series C) has an enhanced
message instruction that provides simple, easy to use CIP messaging.

Selecting CIP Generic configures the message instruction to

communicate with DeviceNet devices that do not support PCCC
messaging. When CIP Generic is chosen, you will notice that a
number of message parameters change and many new ones become
available depending upon the service selected.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 89

Data Table Address (receive and send)

This value identifies the data file location within the 1764-LRP
controller that will receive data from the DeviceNet device, and/or the
starting data file location that will be sent to the destination DeviceNet
device.

Size in Bytes (receive and send)

Since all data transmitted on the DeviceNet network is byte based,

you must enter the number of bytes that will be received and sent.
You must make sure that enough memory is available in the
destination device. Word elements within 1764-LRP controllers contain
2 bytes each. These include Bit and Integer data files. Long word and
Floating point elements contain 4 bytes each.

For receive, the size in bytes entered must be greater than or equal to
the number of bytes that the DeviceNet device will return. DeviceNet
devices return a fixed number of bytes, depending on the class and
service. If more data is returned than expected, the message will be in
error and no data will be written. If less data is returned than
expected, the data will be written and the remainder of the bytes will
be filled with zeros.

In the example dialog shown below, N7:0 will receive 2 bytes (1

word) of data.

Publication 1769-UM009D-EN-P - August 2007

90 Using the 1769-SDN Scanner Module with MicroLogix Controllers

Target Device

Message Timeout

Message timeout is specified in seconds. If the target does not respond

within this time period, the message instruction will generate a
specific error. The amount of time that is acceptable should be based
on application requirements and network capacity/loading.

Target Type

You can select either Module or Network Device. If you need to

message to a device on the DeviceNet network, select Network
Device. If you need to message to a DeviceNet parameter on the
scanner, select Module. This allows the control program access to
module parameters. Many of the module parameters are not editable,
and some can be edited only when the module is in Idle mode.

Local Node Address

This is the target device’s DeviceNet node number.

Publication 1769-UM009D-EN-P - August 2007

 Using the 1769-SDN Scanner Module with MicroLogix Controllers 91

Service

The DeviceNet network uses services to provide specific messaging

functions. A number of standard services with their corresponding
parameters have been preconfigured for ease of use.

If you need to use a service that is not available, select one of the
generic services. The generic service lets you enter specific service
code parameters. Information on what services a target device
supports is usually provided in the device’s documentation.

Publication 1769-UM009D-EN-P - August 2007

92 Using the 1769-SDN Scanner Module with MicroLogix Controllers

MSG Instruction Error When the processor detects an error during the transfer of Expansion
I/O Communication Module message data, the processor sets the ER
Codes bit and writes an error code at MG file sub-element #18 that you can
monitor from your programming software.

1769-SDN Module Error Code

Error Code Description

E0H Expansion I/O Communication Module Error

The processor also writes general status information related to this

error at the high byte of MG file sub-element #22 that can be
monitored from your program.

Error Status Information

General Status Description

01H Illegal or unsupported service parameter
02H Resource unavailable
04H Segment type error in IOI
07H Connection lost
08H Service not supported
09H Invalid attribute value
0BH Already in requested mode/state
0CH Object state conflict
0EH Attribute not setable
10H Device state conflict
11H Reply data too large
13H Not enough data
14H Attribute not supported
15H Too much data
16H Object does not exist
19H Store operation failure
20H Invalid parameter
28H Invalid member ID

Publication 1769-UM009D-EN-P - August 2007

 Chapter 8

Troubleshooting

The 1769-SDN scanner module’s front panel status indicators aid in

troubleshooting the module. The diagnostics provided by these
indicators are described in this chapter.

Topic Page
Diagnostic Indicators 93
Error Codes 95

Diagnostic Indicators The first step in troubleshooting is to observe the 1769-SDN scanner
module’s status indicators and seven-segment numeric displays. The
indicators function as follows:

• The bicolor (green/red) Module status indicator shows whether

the scanner module has power and is functioning properly.
• The bicolor (green/red) Network status indicator provides
information about the DeviceNet channel communication link.
• The numeric display shows node address and status display
information.

Status information precedes the node address.

93 Publication 1769-UM009D-EN-P - August 2007

94 Troubleshooting

This table summarizes the meanings of the status indicators and

numeric codes.
Module Status
Indicator
Network Status
Indicator

Node Address and

Status Display
Troubleshooting the Status Indicators and Numeric Display

Indicator Color/Status Indicates Recommended Action

Module Off No power applied to module. Apply power.
Flashing No bus master (MicroLogix or Verify module connectors are properly seated. If they are, cycle
Green CompactLogix controller) present. power to the controller. If this does not correct the problem,
replace the controller. If replacing the controller does not
correct the problem, replace the scanner.
Solid Green Normal operation. No action required.
Flashing Red • Recoverable Fault - Memory has been • Complete flash update or start a new update.
erased or is being programmed.
• Bad firmware in module. • Replace firmware.
Solid Red Unrecoverable fault. Verify module connectors are properly seated. If they are, verify
that bus terminator/end cap is installed. Cycle power. If still
faulted, replace the module.
Network Off No module power, no network power, or Verify module has power. Check that the DeviceNet cable is
communications are not occurring securely connected and the DeviceNet network is powered.
between the module and the DeviceNet Verify that network power is adequate (11...5V dc).
network. (This may be an acceptable
condition.)
Flashing Device is operational. There are no If the module is supposed to be controlling DeviceNet slaves,
Green connections established with any of the configure the module’s scanlist.
network devices.
Solid Green Normal operation. Scanlist is configured. No action required.
Module is not in Idle mode.
Flashing Red One or more of the devices that the Monitor the status display, or the module’s status field to
scanner module is communicating with is determine which slave device is offline.
in a timed out state.
Solid Red Critical network failure. Duplicate Reset module. Change module’s node address or change
DeviceNet node address detected. conflicting device’s node address. If failure continues, replace
module.
Seven- Node Address Indicates diagnostic information about the status of the module.
segment and Status
Numeric Display • When the numeric display is showing 0...63, it is indicating the scanner’s DeviceNet node address.
Display • When it shows 67...69, it indicates backup status.
• When it shows 70...99, it indicates an error code for the displayed node address.
• When it flashes alternating numbers, one is the error code (70...99), and the other is the node number
(0...63) that has generated the error.

Publication 1769-UM009D-EN-P - August 2007

 Troubleshooting 95

Error Codes The following table describes the error codes indicated by the
seven-segment numeric display.

Device Status

Code Name Description Recommended Action

(decimal)
67 Backup Mode Scanner in Backup Scanner mode. None.
68 No Backup Scanner No backup scanner module present. Install and configure a backup scanner, if
needed.
69 Backup Scanner Invalid The configuration of the primary and the Be sure that the same configuration is
CRC secondary controller does not match. Either one downloaded to both scanners.
or both of the configurations is incorrect.
70 Duplicate Node Controller has Failed Duplicate Node Address Change the module’s or conflicting device’s
Check. The node address selected is already in network address (node number) to an
use. available one.
71 Illegal Scanlist Data Illegal data in scanlist. Reconfigure the scanlist table and remove
any illegal data.
72 Slave Timeout One of the module’s slave devices has stopped Inspect the module’s slave devices and verify
communicating. the DeviceNet connections.
73 Electronic Key Mismatch The slave device Vendor ID key parameter does Make sure that the device at the flashing
not match the slave’s configuration in the node address matches the desired electronic
module’s scanlist. key (vendor, product code, product type)
75 No Messages Received No network traffic received by the scanner. 10 Verify the scanlist is correctly configured to
seconds have elapsed and no network traffic for scan slave devices. Verify DeviceNet
the module or for any other device have been network connections.
received by the module.
76 No Message For Scanner No direct network traffic for the scanner module None. There are other active devices on the
detected. 10 seconds elapsed and no DeviceNet network, initiating messages, but none of
input being screened by the module has been the messages are for the module.
received.
77 Slave Data Size The data being received from the slave device Either reconfigure the slave device, or
Mismatch does not match the configuration in the scanlist. change the module’s scanlist to match the
slave device.
78 No Such Device Slave device in scanlist does not exist. Either add the device to the DeviceNet
network, or delete the device’s entry in the
scanlist.
79 Transmit Failure The module has failed to transmit a message. Make sure that the module is connected to a
valid network. Check for disconnected
cables.
80 In Idle Mode Module is in Idle mode. Put the controller into RUN mode and enable
the RUN bit in the Module Command Array.
See page 70.
81 Scanner Faulted The scanner module has stopped producing and Check the FAULT value in the Module
consuming I/O data. This condition does not Command Array. See page 70.
affect the scanner’s system or messaging modes.

Publication 1769-UM009D-EN-P - August 2007

96 Troubleshooting

Device Status

Code Name Description Recommended Action

(decimal)
82 Fragmentation Error Error detected in sequence of fragmented I/O Check scanlist table entry for slave device to
messages from device. make sure that input and output data lengths
are correct. Check slave device
configuration.
83 Slave Init Error Slave device is returning error responses when Check slave device’s configuration. Reboot
the module attempts to communicate with it. slave device.
84 Not Yet Initialized Module has not completed its initial attempt to None. This code clears itself once the
establish communication with its slaves. module properly initializes all slave devices
on the network.
85 Receive Buffer Overflow Data size returned is larger than expected. Configure the slave device for a smaller data
size.
86 Device Went Idle Device is producing idle state. Check the device configuration and slave
node status.
89 Auto Device Slave device responded with an error to the Try the ADR download again. If it still fails,
Replacement (ADR) Error initialization data sent to it by the scanner; or the try clearing the ADR flash by downloading an
configuration table in the scanner’s flash memory empty ADR configuration to the scanner
is not valid for a slave node. module and then try the ADR configuration
again.
90 Disabled Network DeviceNet Port is disabled. Check for the DISABLE being set in the
Module Command Array. See page 70.
91 Bus Off Bus off condition detected on integral DeviceNet Check the DeviceNet connections and
port. physical media integrity. Check system for
failed slave devices or other possible
sources of network interference. Check the
Baud Rate.
92 No DeviceNet Power No network power detected on DeviceNet port. Provide network power. Make sure the
module drop cable is providing the proper
power to the DeviceNet port.
95 FLASH Update Flash Update In Progress None. Do not disconnect the module from
the network while a FLASH update is in
progress.
98 Firmware Corrupted Firmware is corrupted. Reflash module firmware. Do not power
cycle the module. Doing so may cause the
module to become inoperable. If the problem
persists contact Rockwell Automation
Technical Support.
99 Hard Fault Cycle power. Reflash module firmware.
Contact Rockwell Automation Technical
Support.

Publication 1769-UM009D-EN-P - August 2007

 Appendix A

1769-SDN DeviceNet Class Codes

This appendix contains the most commonly used class codes for the
1769-SDN DeviceNet scanner module. They are shown in the
following tables.

DeviceNet Object

Name Class Instance Attribute Data Size Access

MAC ID 0x03 0x01 0x01 1 byte Get/Set(1)
Baud Rate 0x03 0x01 0x02 1 byte Get/Set
Bus Off Counter 0x03 0x01 0x04 1 byte Get
(1)
The set also causes a reset.

Identity Object

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
Status 0x01 0x01 0x05 2 bytes Get
Serial Number 0x01 0x01 0x06 4 bytes Get
Product Name 0x01 0x01 0x07 9 bytes Get

97 Publication 1769-UM009D-EN-P - August 2007

98 1769-SDN DeviceNet Class Codes

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Appendix B

CompactLogix Backup on the DeviceNet

Network

Using This Appendix This chapter offers a solution to back up your CompactLogix
controller on the DeviceNet network. CompactLogix system backup
on the DeviceNet network is a simple, low-cost, backup system most
effective when used in smaller applications that require fast
switchovers from a primary to a secondary controller.

Topic Page
How the Backup Works 100
Configure the Backup System 102
Develop the CompactLogix Backup 104
Application
Using Indicators to Check Status 111
Development and Debugging Tips 114

This backup solution will:

• minimize downtime in case of controller failure when the same

program is used in both controllers.

• mitigate the risk of changes adversely affecting the application

(use old, proven program in one controller and new, untested
program in the other controller). If the new untested program
causes a problem, a forced switchover can be made to the older
proven program without downloading the program again.

The CompactLogix backup on the DeviceNet network solution takes

advantage of Shared DeviceNet Mastership of Slave I/O Devices
technology. Typically, only a single DeviceNet master exists for any
particular slave. With Shared DeviceNet Mastership, two masters can
exist. Heartbeat communication between primary and secondary
controllers determines which scanner module is the master and which
scanner module remains in Standby mode.

99 Publication 1769-UM009D-EN-P - August 2007

100 CompactLogix Backup on the DeviceNet Network

How the Backup Works The following figure shows an example backup system. In the backup
system, the following occurs:

• Both controllers/scanners simultaneously receive all inputs.

• Both controllers execute in parallel but are not synchronized.

• Only the primary controllers send output data to the I/O

devices. A virtual switch in the 1769-SDN scanner module is
used to switch outputs between primary and secondary
controllers.

• After failure or forced switchover, outputs are automatically

switched by the 1769-SDN scanner module from the primary
controller to secondary. When the switch occurs, the secondary
controller becomes the primary controller.

The switchover occurs so quickly that the I/O devices do not

timeout; these devices are unaware that redundant
controllers/scanners exist and are unaware of the switchover.

DeviceNet Network

Primary Controller

Primary Scanner Module

Secondary Controller

Secondary Scanner Module

31722-M

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 101

Backup System Requirements

The CompactLogix backup on DeviceNet solution requires that you

use the following:

• RSLogix 5000 software, version 10 or later

• Two CompactLogix controllers, firmware revision 10.x or later
• Two 1769-SDN scanner modules, firmware revision 3.x or later

Additional requirements are as follows:

• When setting up the DeviceNet network, you must set the

primary and secondary 1769-SDN scanner modules to the same
node address and reserve the next node address.

We recommend that you set the primary and secondary

1769-SDN scanner module node addresses to 0 and reserve
node 1. However, you can use any successive node numbers
(for example, 30 and 31).

• All I/O and operator interfaces that required backup must be on

the DeviceNet network.

• The scanlists in the two DeviceNet scanner modules must be

identical.

Publication 1769-UM009D-EN-P - August 2007

102 CompactLogix Backup on the DeviceNet Network

Configure the Backup To configure a CompactLogix backup system on the DeviceNet

network, follow these steps. Some of these steps are described in
System greater detail in the rest of the appendix.

1. Install all I/O and operator interfaces that you need to back up
on the DeviceNet network.

We recommend that you reserve node addresses 0 and 1 for the

two 1769-SDN scanner modules used with the CompactLogix
controllers within a backup system. If you do not use 0 and 1,
make sure you reserve two consecutive numbers for the
1769-SDN scanner modules when you install I/O and other
devices on the DeviceNet network.

2. Connect a CompactLogix controller with a 1769-SDN scanner

module to the DeviceNet network.

3. Set the scanner module node address to 0 (or the lower of the
two node addresses reserved for the CompactLogix controller
backup system).

4. Apply power to the controller and the network.

5. Use RSNetWorx for DeviceNet software to download the

network’s scanlist to the 1769-SDN scanner module.

You can either use a scanlist from a new configuration or from a

previously-used configuration. If the scanlist is a new
configuration, we recommend that you save it to a new project
for later use.

6. Use RSLogix 5000 software to download the appropriate user

program to the CompactLogix controller.

The program should contain the explicit messages that enable

the backup feature for this controller and scanner module. The
messages are described in the Develop the CompactLogix
Backup Application section beginning on page 104.

7. Put the controller into Run mode.

8. Either disable power to the controller or disconnect the scanner

module from the DeviceNet network.

This controller will be the secondary controller.

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 103

9. Connect the other CompactLogix controller with a 1769-SDN

scanner module on the network.

10. Set the node address to 0.

11. Apply power to the controller and scanner module.

12. Use RSNetWorx for DeviceNet software to download the same

scanlist used in step 5.

It may be necessary to browse the network again before

downloading the scanlist. This second browsing of the network
allows RSNetWorx for DeviceNet software to establish
communication to the new scanner module at the same node
number as the previous scanner.

13. Use RSLogix 5000 software to download the user program to the
second CompactLogix controller as you did in step 6.

Typically, you download the same user program to the second

CompactLogix controller as you did to the first. However, unlike
the scanlists, the user programs in the controllers do not have to
be identical.

14. Put the controller into Run mode.

This controller is now ready to use and is the primary controller.

15. Reapply power to the secondary controller and/or reconnect the

secondary scanner module to the DeviceNet subnet.

This completes the backup process. For more detailed information on

some of the steps listed previously, see the next section.

Publication 1769-UM009D-EN-P - August 2007

104 CompactLogix Backup on the DeviceNet Network

Develop the CompactLogix The CompactLogix backup is enabled from an RSLogix 5000 software
user program with a few simple ladder rungs. The following rungs are
Backup Application used in the CompactLogix backup:

• Backup Heartbeat Configuration Rungs - required

• Reading Backup State Rung - optional
• Reading Backup Status - optional

Backup Heartbeat Configuration Rungs

The first, and most critical, step is to set the backup heartbeat constant
in the DeviceNet scanner. The heartbeat constant enables the backup
feature and determines the switchover time (2 x heartbeat).

By default, the heartbeat is zero; this default value disables the

Backup mode. Your user program must set the heartbeat to a
non-zero value to enable backup.

The heartbeat occurs in multiples of 8 ms (8, 16, 24). We recommend

a value of 16...48 ms for most applications. The recommended
heartbeat times result in switchover times of 32...96 ms. These times
do not include controller scan delays.

IMPORTANT If multiples of 8 are not used for the requested heartbeat, then
the DeviceNet scanner module uses the next higher supported
heartbeat value that can be read from the scanner. For example,
if you set the heartbeat to 10, the scanner module uses a 16 ms
heartbeat.

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 105

Setting the Heartbeat Constant

You can set the heartbeat constant with five rungs of ladder logic. This
figure shows rungs 0 and 1 and the message setup used in rung 1. The
message in rung 1 uses the INT data type.

Rung 1 Message Configuration and Communication tabs.

Publication 1769-UM009D-EN-P - August 2007

106 CompactLogix Backup on the DeviceNet Network

This figure shows rung 2 and the message setup used on it. The
message in rung 2 uses the INT data type.

Rung 2 Message Configuration and Communication tabs.

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 107

This figure shows rungs 3 and 4 and the message setup used on it.
The message in rung 3 uses the INT data type.

Rung 3 Message Configuration and Communication tabs.

This completes the required portion of ladder logic to enable the

CompactLogix backup on the DeviceNet network. The following
sections describe how to use additional ladder logic to read backup
state and status. However, these sections are not required to complete
the backup solution.

Publication 1769-UM009D-EN-P - August 2007

108 CompactLogix Backup on the DeviceNet Network

Reading Backup State Rung

You can read the backup state of the DeviceNet scanner module with
a single rung of ladder logic. The backup state is useful for debugging
or more sophisticated backup schemes. The message in this rung uses
the SINT data type.

This figure shows the rung you can use to read the backup state.

Rung 5 Message Configuration and Communication tabs.

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 109

This table describes the possible values this message may return when
reading the backup state of the DeviceNet scanner.

If the message reads The backup state of the DeviceNet scanner module is
this value
0 Disabled
1 Primary scanner
2 Backup scanner
3 Invalid primary node address (for example, the node address
cannot be 62 or 63)
4 Faulted backup scanner module - CRC failure (for example,
the scanlists in the scanners do not match)
5 Faulted backup scanner module - backup node number
failure (for example, the backup scanner module is not using
a node number = the primary node number + 1)
6 Backup scanner module pending primary detection
254 Attempting primary access
67 Scanner in Backup Scanner mode
68 No backup scanner module present
69 Invalid backup scanner module CRC
255 Attempting backup access

Publication 1769-UM009D-EN-P - August 2007

110 CompactLogix Backup on the DeviceNet Network

Reading Backup Status

You can read the backup status of the DeviceNet scanner module with
a single rung of ladder logic. The backup state is useful for debugging
or more sophisticated backup schemes. The message in this rung uses
the SINT data type.

This figure shows the rung you can use to read the backup state.

Rung 6 Message Configuration and Communication tabs.

This table describes the possible values this message may return when
reading the backup status of the DeviceNet scanner module.

If the message The backup state of the DeviceNet scanner module is

reads this value
0 No backup scanner module detected
1 Primary scanner module forcing Idle (backup in Run mode but
primary in Idle mode)
3 Primary scanner in Run mode detects backup scanner in Idle mode

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 111

Using Indicators to The 1769-SDN scanner module’s status indicators provide useful
information (for example, determining which scanner module is
Check Status primary) about backup scanner module status.
Module Status
Indicator
Network Status
Indicator

Node Address and

Status Display

Module Status Indicator

This table lists the indicators to monitor when checking backup status.

Module Status Indicator Behavior

If this indicator Exhibits this behavior This condition exists

Module status (MS) Flashing red • Recoverable Fault - Memory has
been erased or is being
programmed.
• Bad firmware in module.

Publication 1769-UM009D-EN-P - August 2007

112 CompactLogix Backup on the DeviceNet Network

Node Address and Status Display

The seven-segment numeric display shows the following information

about the primary and secondary scanner modules in either Run or
Idle modes.

If error codes other than those shown in these tables appear in the
TIP display, refer to Chapter 8, Troubleshooting, for more information on
error codes.

Primary Scanner Module With Valid Backup Scanner Module

Run Mode
Primary Secondary
Node Number 00 01 or 00
Status 00 (Run mode) 67 (Backup mode enabled) or 00 (Run mode)
Primary or Secondary P - (Primary) S - (Secondary)
Idle Mode
Primary Secondary
Node Number 00 01 or 00
Status 80 (Idle mode) 67 (Backup mode enabled) or 80 (Idle mode)
Primary or Secondary P - (Primary) S - (Secondary)

Primary Scanner Module Without Valid Backup Scanner Module

Run Mode
Primary Secondary
Node Number 00 or 01 01 or 00
Status 68 (No backup scanner present) or Undefined error or
00 (Run mode) 69 (Backup scanner invalid CRC)
Primary or Secondary P - (Primary) --
Idle Mode
Primary Secondary
Node Number 00 or 01 01 or 00
Status 68 (No backup scanner present) or Undefined error or
80 (Idle mode) 69 (Backup scanner invalid CRC)
Primary or Backup P - (Primary) --

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 113

Lost Primary Scanner Module With Valid Backup Scanner Module

Run Mode
Primary Secondary
Node Number 00 01 or 00
Status Undefined error 68 (No backup scanner present) or
00 (Run mode)
Primary or Secondary -- P - (Primary)
Idle Mode
Primary Secondary
Node Number 00 00 or 01
Status Undefined error 68 (No backup scanner present) or
80 (Idle mode)
Primary or Secondary -- P - (Primary)

CRC Error

Run Mode
Primary Secondary
Node Number 00 or 01 00 or 01
Status 68 (No backup scanner present) or 69 (Backup scanner invalid CRC)
00 (Run mode)
Primary or Secondary P - (Primary) --
Idle Mode
Primary Secondary
Node Number 00 or 01 00 or 01
Status 68 (No backup scanner present) or 69 (Backup scanner invalid CRC)
80 (Idle mode)
Primary or Secondary P - (Primary) --

Lost Primary Scanner Module Without Valid Backup Scanner Module

Run Mode
Primary Secondary
Node Number Undefined error Undefined error
Status -- --
Primary or Secondary -- --

Publication 1769-UM009D-EN-P - August 2007

114 CompactLogix Backup on the DeviceNet Network

Development and When you implement the CompactLogix system backup on the
DeviceNet network, we recommend that you consider the following
Debugging Tips development and debugging tips:

• Develop and debug the entire application with only the primary
controller and scanner module present. When the application is
totally verified, then download the program and exact same
scanlist to the secondary controller, without the primary
controller present. Verify that the secondary is also functioning
properly, and then both primary and secondary can be added to
the network at the same time.

• No configuration parameters are entered from RSNetworx for

DeviceNet software or RSLogix 5000 software to enable backup.
All configuration occurs in the user program. The entire
application (except for a few ladder rungs) can be developed
without knowledge that the application will have a backup
controller and scanner module.

• Local I/O still works when this solution is used, but the local I/O
is not backed up.

• Switchover time depends on the user configurable heartbeat.

Typically, switchover occurs after two heartbeats, plus the time
required to complete network polling.

• The I/O during switchover is not bumpless. Since the programs

and I/O updates are not synchronized, it is possible for the
secondary controller to be either slightly faster or slower than
the primary.

For example, if output changes during a switchover, the fact that

the primary and secondary controllers are unsynchronized can
cause the output to momentarily switch between an older and
newer value. If you configure the switchover time slower than
the program scan and I/O update, the secondary lags behind the
primary and eliminates this.

• State variables, such as counters or timers, are not synchronized.

The user program must synchronize the primary and secondary
controllers, typically over an EtherNet/IP or ControlNet network
link between controllers. If the outputs are dependent on a state
variable, the lack of synchronization can also cause a bumpy
switchover.

• As with all backup and redundancy systems, the I/O must

change at a slower rate than the switchover time. If the inputs
change faster than the switchover, the change of state is lost.

Publication 1769-UM009D-EN-P - August 2007

 CompactLogix Backup on the DeviceNet Network 115

• Either the user program or user action determine the primary

controller. In its simplest mode, the first scanner module to turn
on or become available on the DeviceNet network is the
primary.

• Unlike some backup systems (such as PLC-5 controller systems),

the primary controller still maintains control of the I/O, and
switchover does not occur if the primary controller is set to
Program/Idle mode. The secondary 1769-SDN scanner module
also indicates that it is in Idle mode.

• By default, a switchover will not occur if the default fault routine

or user fault routine is executed in the primary controller.
However, the user fault routine can force a switchover if desired.

• If an operator interface is on the DeviceNet network, it can work

without knowledge of which controller is primary or secondary.

• Online edits are not automatically performed on both primary

and secondary controllers, since no synchronization exists
between primary and secondary controllers. Once an online edit
occurs on the primary controller, the primary and secondary will
have different programs.

• CompactLogix system backup on the DeviceNet network is not

hot backup. Hot backup implies complete synchronization of
program, program variables, and I/O. Also, I/O switchover is
completely bumpless with hot backup.

Publication 1769-UM009D-EN-P - August 2007

116 CompactLogix Backup on the DeviceNet Network

Notes:

Publication 1769-UM009D-EN-P - August 2007

 Glossary

This Term Means

Auto-Address Auto-Address Recovery (AAR) allows a slave device to
Recovery (AAR) be removed from the network and replaced with another
identical slave device that is residing on the network at
node address 63 and not in the scan list. The
replacement device will have its node address
automatically changed to that of the device being
replaced. Depending on the level of revision keying, it
may be possible for the node address of the replacement
device to be changed but not brought online due to a
revision-keying mismatch.
Auto Device The Auto Device Replacement feature automates the
Replacement (ADR) replacement of a failed slave device on a DeviceNet
network by configuring the new device to the prior level
of operation. This includes Configuration Recovery (CR)
and Auto-Address Recovery (AAR).
Bridge The scanner module’s support of explicit message
transfer.
Change of State A type of I/O data communication. The scanner module
can send and receive data with slave devices that have
the change of state feature. Data is sent whenever a data
change occurs, or at the predefined heartbeat interval.
Configuration Configuration Recovery (CR) allows a slave device to be
Recovery (CR) removed from the network and replaced with an
identical slave device configured at the same
communication rate and Node Address as the device
being replaced.
Controller The programmable controller, for example
CompactLogix or MicroLogix 1500.
Cyclic A type of I/O data communication. The scanner module
can send and receive data with slave devices that have
the cyclic feature. Data is sent at a user-configurable rate.
Dual Mode The scanner module is in Dual mode when it serves as a
master to one or more slaves and as a slave to another
master simultaneously.
EDS Electronic Data Sheet. A vendor-supplied template that
specifies how information is displayed as well as what is
an appropriate entry (value).
Explicit Messaging A type of messaging used for lower priority tasks, such
as configuration and data monitoring.
Heartbeat Rate Devices that are configured for change of state data will
send data at this rate if no data change occurs.
Host Platform The computer on which the application software is run.

117 Publication 1769-UM009D-EN-P - August 2007

Glossary 118

This Term Means

I/O An abbreviation for input and output.
Input Data Data produced by a DeviceNet device and collected by
the scanner module for the host platform to read.
MAC ID The network address of a DeviceNet node. Also referred
to as node address.
Multicast Used when describing a strobe message.
Network The DeviceNet network or the RSNetWorx for DeviceNet
software representation of the network.
Node Hardware that is assigned a single address on the
network. Also referred to as a device.
Offline When the host platform is not communicating on the
network.
Online When the host platform is configured and enabled to
communicate on the network.
Output Data Data produced by the host platform that is written to the
scanner module’s memory. This data is sent by the
scanner module to DeviceNet devices.
Point-to-point Used when describing a poll message. The message
solicits a response from a single, specified device on the
network.
Polled A type of input/output-data communication. A polled
message solicits a response from a single, specified
device on the network (a point-to-point transfer of data).
Record The node address and channel-specific memory
assigned in the scanner module’s nonvolatile storage for
a node in the scanlist.
Rx An abbreviation for receive.
Scanlist The list of devices (nodes) with which the scanner
module is configured to exchange I/O data.
Scanner The function of the 1769-SDN scanner module to
support the exchange of I/O with slave modules.
Slave Mode The 1769-SDN scanner module is in slave mode when it
is placed in another DeviceNet master’s scanlist as a
slave device.
Strobed A type of I/O data communication. A strobed message
solicits a response from each strobed device (a multicast
transfer). It is a 64-bit message that contains one bit for
each device on the network.
Tx An abbreviation for transmit.

Publication 1769-UM009D-EN-P - August 2007

 Index

B input data definition 14

backup installation 23
CompactLogix backup on the DeviceNet getting started 19
network 99 grounding 34
before you begin 11, 19 heat and noise considerations 26

C M
change of state message 14 manuals, related 10
common techniques used in this manual module command array 70
10 mounting 30
configuring the DeviceNet network
I/O devices 46-60, 61 O
scanlist configuration 40 operating modes 15, 70
setting up an online connection 40-42 output data definition 14
software installation 38
using RSLinx software 38-40
using RSNetworx software 40-61 P
current draw 20 panel mounting 30-32
cyclic message 14 poll message 14
power requirements 24
D publications, related
data tables 15 additional resources 10
DeviceNet driver
adding 38-40 R
DeviceNet network related publications 10
CompactLogix backup on the network 99 RSLinx software
DIN rail mounting 32 configuring the DeviceNet network 38-40
installation 38
E RSNetWorx for DeviceNet software
EMC Directive 23 configuration screen map 17
configuring the DeviceNet network 40-61
equipment required for installation 19
installation 38
European Union Directives 23 RSNetWorx software
explicit messaging 14, 82 technical data publication 10

G S
grounding 34 scanlist configuration 46
scanner module functions 13
H software installation 38
http software versions 37
//www.ab.com/literature 10 spacing 30
start-up instructions 19
strobe message 14
I

Publication 1769-UM009D-EN-P - August 2007

120 Index

T W
technical support 47 what you need to know 11
tools required for installation 19 wiring 23
troubleshooting 93
diagnostic indicators 93
typical network configuration 13, 76

Publication 1769-UM009D-EN-P - August 2007

 How Are We Doing?
Your comments on our technical publications will help us serve you better in the future.
Thank you for taking the time to provide us feedback.

You can complete this form and mail (or fax) it back to us or email us at
[email protected]

Pub. Title/Type Compact I/O DeviceNet Scanner Module

Cat. No. 1769-SDN Pub. No. 1769-UM009D-EN-P Pub. Date August 2007 Part No. 953157-62

Please complete the sections below. Where applicable, rank the feature (1=needs improvement, 2=satisfactory, and 3=outstanding).
Overall Usefulness 1 2 3 How can we make this publication more useful for you?

1 2 3 Can we add more information to help you?

Completeness
(all necessary information procedure/step illustration feature
is provided)
example guideline other
explanation definition

Technical Accuracy 1 2 3 Can we be more accurate?

(all provided information
is correct) text illustration

Clarity 1 2 3 How can we make things clearer?

(all provided information is
easy to understand)

Other Comments You can add additional comments on the back of this form.

Your Name
Your Title/Function Would you like us to contact you regarding your comments?
Location/Phone ___No, there is no need to contact me
___Yes, please call me
___Yes, please email me at _______________________
___Yes, please contact me via _____________________
Return this form to: Rockwell Automation Technical Communications, 1 Allen-Bradley Dr., Mayfield Hts., OH 44124-9705
Fax: 440-646-3525 Email: [email protected]

Publication CIG-CO521C-EN-P- May 2003 PN953157-62957782-91

 PLEASE FASTEN HERE (DO NOT STAPLE)

Other Comments

PLEASE REMOVE
PLEASE FOLD HERE

NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 18235 CLEVELAND OH

POSTAGE WILL BE PAID BY THE ADDRESSEE

1 ALLEN-BRADLEY DR
MAYFIELD HEIGHTS OH 44124-9705
Rockwell Automation Rockwell Automation provides technical information on the Web to assist
you in using its products. At http://support.rockwellautomation.com, you can
Support find technical manuals, a knowledge base of FAQs, technical and application
notes, sample code and links to software service packs, and a MySupport
feature that you can customize to make the best use of these tools.

For an additional level of technical phone support for installation,

configuration, and troubleshooting, we offer TechConnect Support programs.
For more information, contact your local distributor or Rockwell Automation
representative, or visit http://support.rockwellautomation.com.

Installation Assistance

If you experience a problem with a hardware module within the first 24

hours of installation, please review the information that's contained in this
manual. You can also contact a special Customer Support number for initial
help in getting your module up and running.

United States 1.440.646.3223

Monday – Friday, 8am – 5pm EST
Outside 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, it may need to be returned.

United States Contact your distributor. You must provide a Customer Support case
number (see phone number above to obtain one) to your distributor in
order to complete the return process.
Outside United Please contact your local Rockwell Automation representative for
States return procedure.

Publication 1769-UM009D-EN-P - August 2007 128 PN 953157-62

Supersedes Publication 1769-UM009C-EN-P - May 2005 Copyright © 2007 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.