Allen-Bradley 1769-SDN User Manual

Reserved

Chapter 4, Configuring the DeviceNet Network

DO NOT manipulate Reserved Bits. Doing so may interfere with future compatibility.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

1-6 Overview

RSNetWorx Software as a

Configuration Tool

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

-PCID).

The recommended configuration software is RSNetworx for DeviceNet

(version 3.00 or higher).

TIP

If your RSNetWorx configuration software does not include the required EDS (Electronic Data Sheet) file, it is available via http://www.ab.com/networks/eds.

RSNetWorx. Access the wizard from the Tools pull-down menu.

This configuration tool allows you to identify all of the DeviceNet devices and their locations in your system.

TIP

The controller must be in the Program mode, or the scanner in the Idle mode (bit 0 of the Module

Command Array = 0), for the scanner to accept the configuration information.

The following configuration screen map shows the RSNetWorx screens used to configure the scanner.

For more detailed information, see:

•

•

Chapter 6, Using the 1769-SDN Scanner Module with

CompactLogix Controllers

•

Chapter 7, Using the 1769-SDN Scanner Module with MicroLogix

Controllers

Publication 1769-UM009B-EN-P - May 2002

The main RSNetWorx screen.

Overview 1-7

Figure 1.1 RSNetWorx Configuration Screen Map

To browse the network, click on the Online button and select the driver.

To access the 1769-SDN Scanner Module, double-click on the 1769-SDN icon.

To access the scanlist, click on the Scanlist tab.

Move the device into the scanlist.

To download the scanlist, click on the Download to Scanner button.

To edit a device’s I/O parameters, double-click on the device in the scanlist.

To automatically map input devices, select the Input tab and click on the AutoMap button.

To automatically map output devices, select the Output tab and click on the AutoMap button.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

1-8 Overview

Notes:

Publication 1769-UM009B-EN-P - May 2002

Chapter

Quick Start for Experienced Users

Before You Begin

Required Tools and

Equipment

This chapter can help you to get started using the 1769-SDN scanner module. We base the procedures here 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. It does, however, reference other chapters in this book where you can get more information about applying the procedures described in each step.

If you have any questions or are unfamiliar with the terms used or concepts presented in the procedural steps, always read the referenced chapters and other recommended documentation before trying to apply the information.

Have the following tools and equipment ready:

•

Personal Computer

•

Programmable Controller: CompactLogix or MicroLogix 1500

System

•

1770-KFD RS-232 DeviceNet Adapter, 1784-PCD or 1784-PCID

DeviceNet Interface Card

•

Communications Software: RSLinx, Version 2.30 or later

•

DeviceNet Configuration Software:

RSNetWorx for DeviceNet, Version 3.00 or later

•

Ladder Logic Programming Software:

RSLogix 500, Version 5.00.10 or later

RSLogix 5000, Version 8.02 or later

•

1769-SDN Scanner Module

•

Mounting Hardware

•

Screwdriver

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

2-2 Quick Start for Experienced Users

What You Need To Do

Verify planned system configuration.

EXAMPLE

limitations, see System Planning on page 3-5.

a. Ensure system power supply has sufficient current. The modules maximum current draw is shown below.

Table 2.1

Module

1769-SDN

5V dc

440 mA

24V dc

0 mA

TIP

The module cannot be located more than 4 modules away from the system power supply.

b. If you are not familiar with Compact I/O and DeviceNet

c. Verify that the DeviceNet network has adequate power.

Table 2.2

Module

1769-SDN

DeviceNet Power Requirements

N.E.C. Class 2

90 mA at 11V dc (maximum)

110 mA at 25V dc (maximum)

200 mA for 1.5 ms (inrush)

Publication 1769-UM009B-EN-P - May 2002

Quick Start for Experienced Users 2-3

Remove power.

EXAMPLE

ATTENTION

Remove power before removing or inserting this module. When 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 may lead to premature failure.

Assemble and mount the I/O bank.

EXAMPLE

Be sure to observe minimum spacing guidelines on page 3-7 for

The module can be attached to an adjacent controller, power supply, or I/O module. The module can be panel or DIN rail mounted. Modules can be assembled before or after mounting.

adequate ventilation.

Ground the module and complete DeviceNet wiring.

EXAMPLE

Apply power to the system.

EXAMPLE

Configuring the DeviceNet Network

Chapter 8

Troubleshooting

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

2-4 Quick Start for Experienced Users

Be sure programming software and equipment is ready.

EXAMPLE

Chapter 4

Use RSLinx to configure drivers.

EXAMPLE

Chapter 4

Configuring the DeviceNet Network

Use RSNetWorx to configure the 1769-SDN scanner module and the DeviceNet Devices.

EXAMPLE

Chapter 4

Configuring the DeviceNet Network

Chapter 5

DeviceNet I/O Image

Chapter 6

Using the 1769-SDN Scanner Module with CompactLogix

Controllers

Chapter 7

Using the 1769-SDN Scanner Module with MicroLogix Controllers

Use RSLogix to create your project and ladder logic.

EXAMPLE

Chapter 6

Using the 1769-SDN Scanner Module with CompactLogix

Controllers

Chapter 7

Using the 1769-SDN Scanner Module with MicroLogix Controllers

Publication 1769-UM009B-EN-P - May 2002

Quick Start for Experienced Users 2-5

Start system.

EXAMPLE

d. If the LEDs turn red or flash, see Table 8.1 Troubleshooting the LEDs and Numeric Display on page 8-2. If the condition

Chapter 8

Troubleshooting

a. Apply power.

b. Download your program and put the controller into Run mode.

c. During a normal start-up, the Module and Network LEDs turn on solid green.

persists, contact your local distributor or Rockwell

Automation for assistance.

Monitor the module status to check if the module is operating correctly.

EXAMPLE

Chapter 8

Troubleshooting

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

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

2-6 Quick Start for Experienced Users

Notes:

Publication 1769-UM009B-EN-P - May 2002

Chapter

Installation and Wiring

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

For information about

Compliance to European Union Directives

Power Requirements

General Considerations

System Planning

System Assembly

System Mounting

Replacing the Scanner Module within a System

Field Wiring Connections

Scanner Module Power-Up

See page

Compliance to European

Union Directives

This product is approved for installation within the European Union and EEA regions. It has been designed and tested to meet the 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.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-2 Installation and Wiring

Power Requirements

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 for

Noise Immunity , publication 1770-4.1

•

Automation Systems Catalog , publication B113

The module receives power through the Compact I/O bus interface from the +5V dc system power supply. The maximum current drawn by the module is shown in the table below.

Table 3.1

Module

1769-SDN

5V dc

440 mA

24V dc

0 mA

The module also draws power from the DeviceNet network. The power requirements are shown in the table below.

Table 3.2

Module

1769-SDN

DeviceNet Power Requirements

N.E.C. Class 2

90 mA at 11V dc (maximum)

110 mA at 25V dc (maximum)

200 mA for 1.5 ms (inrush)

Publication 1769-UM009B-EN-P - May 2002

General Considerations

Installation and Wiring 3-3

Compact I/O 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 non-hazardous 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 non-hazardous.

Do not connect or disconnect components unless power has been switched off or the area is known to be non-hazardous.

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 non-conductive 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)

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-4 Installation and Wiring

Prevent Electrostatic Discharge

ATTENTION

Electrostatic discharge can damage integrated circuits or 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.

•

If available, use a static-safe work station.

•

When it is not in use, keep the module in its static-shield box.

Remove Power

ATTENTION

• 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 may 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-UM009B-EN-P - May 2002

System Planning

Installation and Wiring 3-5

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.

Consider the following when planning your system:

•

The scanner can communicate with up to 63 DeviceNet devices.

•

The scanner, as a master, can own up to 63 slave I/O nodes.

•

The scanner can simultaneously be a master and be 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 must have its own power supply (a

MicroLogix 1500 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 (e.g. 1769-PA2) of the supply. 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-5.14 or the MicroLogix

1500 User Manual , publication 1764-UM001A-EN-P.

•

The scanner has a distance rating of four, therefore the scanner must be within four modules of the I/O bank’s power supply.

•

Determine the DeviceNet baud rate based on standard

DeviceNet considerations.

•

Consider the number of words of I/O data the host controller supports.

For more information on planning your DeviceNet network, refer to the DeviceNet Cable System Planning and Installation Manual , publication DN-6.7.2.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-6 Installation and Wiring

System Assembly

The module can be attached to an adjacent controller, power supply, or I/O module. For mounting instructions, see “Panel Mounting” on

page 3-8, or “DIN Rail Mounting” on page 3-10. To work with a

system that is already mounted, see “Replacing a Single Module within

a System” on page 3-10.

The following procedure shows you how to assemble the Compact

I/O system.

Disconnect power.

Check that the bus lever of the module (A) is in the unlocked

(fully right) position.

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

Move the module back along the tongue-and-groove slots until the bus connectors (C) line up with each other.

Use your fingers or a small screw driver to push the bus lever back slightly to clear the positioning tab (D).

Move the module’s bus lever fully to the left (E) until it clicks.

Ensure it is locked firmly in place.

ATTENTION

When attaching I/O modules, it is very important that the bus connectors are securely locked together to ensure proper electrical connection.

Attach an end cap terminator (F) to the last module in the system by using the tongue-and-groove slots as before.

Publication 1769-UM009B-EN-P - May 2002

Installation and Wiring 3-7

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.

System Mounting

ATTENTION

During panel or DIN rail mounting of all devices, be sure that all debris (metal chips, wire strands, etc.) is kept 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, adjacent equipment, etc. Allow 50 mm (2 in.) of space on all sides for adequate ventilation, as shown below:

Top

Side

Host Controller

Side

Bottom

Allow at least 110 mm (4.33 in.) of enclosure depth to accommodate the module and the DeviceNet connector.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-8 Installation and Wiring

Mounting Hole

Dimension

Panel Mounting

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

Panel Mounting Using the Dimensional Drawing

NOTE: All dimensions are in mm (inches). Hole spacing tolerance: ±0.4 mm (0.016 in.).

Compact I/O with CompactLogix Controller and Power Supply

50 mm

(1.97 in)

40 mm

(1.58 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

70 mm

(2.76 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

28.5 mm

(1.12 in)

DIN Rail

Center Line

14.7 mm

(0.58 in)

Publication 1769-UM009B-EN-P - May 2002

Mounting Hole

Dimension

Installation and Wiring 3-9

Compact I/O with MicroLogix 1500 Base Unit and Processor

168 mm

(6.62 in)

147 mm

(5.79 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

28.5 mm

(1.12 in)

DIN Rail

Center Line

13.5 mm

(0.53 in)

14.7 mm

(0.58 in)

Panel Mounting Procedure Using Modules as a Template

The following procedure allows you to 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:

On a clean work surface, assemble no more than three modules.

Using the assembled modules as a template, carefully mark the center of all module-mounting holes on the panel.

Return the assembled modules to the clean work surface, including any previously mounted modules.

Drill and tap the mounting holes for the recommended M4 or #8 screw.

Place the modules back on the panel, and check for proper hole alignment.

Attach the modules to the panel using the mounting screws.

TIP

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.

Repeat steps 1 to 6 for any remaining modules.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-10 Installation and Wiring

DIN Rail Mounting

The module can be mounted using the following DIN rails:

35 x 7.5 mm (EN 50 022 - 35 x 7.5) or 35 x 15 mm (EN 50 022 - 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.

Table 3.3

Dimension Height

118 mm (4.65 in.)

59 mm (2.325 in.)

Replacing the Scanner

Module within a System

The scanner can be replaced while the system is mounted to a panel

(or DIN rail) once power is removed.

Remove power. See important note on page 3-4.

Remove the DeviceNet cable from the scanner by removing the

DeviceNet connector.

Remove the upper and lower mounting screws from the scanner

(or open the DIN latches using a flat-blade screwdriver).

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

Gently slide the disconnected scanner module forward.

Publication 1769-UM009B-EN-P - May 2002

Installation and Wiring 3-11

If you feel excessive resistance, make sure that you disconnected the scanner from the bus and that you removed both mounting screws (or opened the DIN latches).

TIP

It may be necessary to rock the scanner slightly from front to back to remove it, or, in a panel-mounted system, to loosen the screws of adjacent modules.

Before installing the replacement scanner, be sure that the bus lever on the right-side adjacent module is in the unlocked (fully right) position.

Slide the replacement scanner into the open slot.

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

10.

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

11.

Replace the DeviceNet cable on the scanner by attaching the connector to the scanner.

12.

Restore scanner configuration using RSNetWorx for DeviceNet.

IMPORTANT

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

Field Wiring Connections

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 must be connected to a suitable ground source when operating in electrically noisy environments. Use a

#14 AWG wire to make this connection.

Refer to Industrial Automation Wiring and Grounding Guidelines ,

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

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

3-12 Installation and Wiring

DeviceNet Wiring

DeviceNet

Connector

Grounding Screw

Use #14 AWG wire to connect to panel ground.

Table 3.4

Connect

(1)

Red Wire

White Wire

Bare Wire

Blue Wire

Black Wire

V+

CAN High

Shield

CAN Low

V-

Connect the DeviceNet cable to the removable connector as shown.

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

Screw the removable connector to the scanner case with the upper and lower mounting screws. Screw torque is 0.6 to 0.7

Nm (5 to 6 in-lbs).

IMPORTANT

If the 1769-SDN is the first or last device connected to the DeviceNet network trunkline, be sure to add a termination resistor (120

Ω

≥

¼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 is ready to communicate.

The default scanner settings are:

• baud rate = 125K

• node address = 63

Use your configuration software to change the baud rate and node address.

What’s Next?

The next step is to configure the scanner and perform I/O data mapping through RSNetWorx.

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network

Chapter

This chapter describes how to configure the DeviceNet network using

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

For information about

Software Versions

Installing the Software

Using RSLinx to Configure Your DeviceNet Driver

Using RSNetWorx to Configure the 1769-SDN’s Scanlist

See page

4-1

retry limit. See additional information under Edit I/O Parameters on page 4-17.

Software Versions

The following table lists the software and revision level required to operate with the 1769-SDN scanner module.

Table 4.1 Compatible Software

Function

Communications

Program

RSLinx

Revision

2.30 or higher

DeviceNet Configuration RSNetWorx for DeviceNet 3.00 or higher

Ladder Logic Programming Software RSLogix 500 5.00.10 or higher

RSLogix 5000 8.02 or higher

TIP

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

TIP

If your RSNetWorx configuration software does not include the required EDS (Electronic Data Sheet) file, it is available via http://www.ab.com/networks/eds.

RSNetWorx. Access the wizard from the Tools pull-down menu.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-2 Configuring the DeviceNet Network

Installing the Software

Install RSLinx and RSNetWorx.

For both of these software packages:

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.

From the Windows Start menu, select Run .

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

Follow the prompts that appear on the screen as you install the software.

After software installation is complete, you will use RSLinx to configure your DeviceNet driver and RSNetWorx to configure the network.

Using RSLinx to Configure

Your DeviceNet Driver

Start RSLinx. The RSLinx main window will open.

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-3

From the Communications menu, select Configure Drivers as shown above. The following window will appear.

Select DeviceNet Drivers from the above pull-down list and click on Add/New . You will see the following choices.

TIP

Your driver setup will depend on your particular system setup

(COM port, baud rate, node address). Choose the appropriate settings for your system. We used the settings shown at right.

Select your driver.

The Driver Configuration window will appear.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-4 Configuring the DeviceNet Network

Configure the driver using the example above as a guide and click on OK . The software will take a few seconds to configure the driver. When it is done the following prompt will appear:

Click on OK to use the default driver name.

Minimize RSLinx.

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

Using RSNetWorx to

Configure the 1769-SDN’s

Scanlist

This manual assumes a certain level of familiarity with RSNetWorx. For detailed information on RSNetWorx for DeviceNet, please refer to your software’s documentation.

Setting Up an Online Connection

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

DeviceNet network using the 1770-KFD driver.

Start RSNetWorx. The following screen will open.

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-5

From the File menu, select New .

If you have ControlNet configured on your system you may see the following window. Otherwise, proceed to step 4.

Highlight DeviceNet Configuration and click on OK .

Click on the Online button on the toolbar.

A list of the available networks will appear. (Your list may appear different from that shown below, depending upon the drivers you have configured on your system.)

Select your DeviceNet driver and click on OK .

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

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-6 Configuring the DeviceNet Network

Click on OK to upload the devices and go online.

RSNetWorx will begin browsing for network devices. When the software is done browsing, your network is displayed on your screen.

TIP

RSNetWorx 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 which was online later goes offline, there will be no “live” indication in

RSNetWorx. You must manually perform a browse to detect the missing node.

To manually perform the browse, press the button.

If RSNetWorx fails to find a device, check the physical connection to the device. If the physical connection is intact, verify that the device’s baud rate is the same as the DeviceNet driver’s.

TIP

If your RSNetWorx configuration software does not include the required EDS (Electronic Data Sheet) file, it is available via http://www.ab.com/networks/eds.

RSNetWorx. Access the wizard from the Tools pull-down menu.

Publication 1769-UM009B-EN-P - May 2002

TIP

Configuring the DeviceNet Network 4-7

Setting the 1769-SDN Node Address

Once the network browse is complete, the node addresses appear to the right of their icons. If you need to change a module’s node address, use the following procedure.

TIP

You can use this procedure to change the node address of other devices on the network (e.g., a

Photoeye). You can also change the network data rate (baud rate) of some devices. Depending upon the device, power may need to be cycled for baud rate changes to take effect.

The controller must be in the Program mode, or the scanner in the Idle mode (bit 0 of the Module

Command Array = 0), for the scanner to accept the configuration information.

Perform the following steps:

From the Tools menu select Node Commissioning . You will see the Node Commissioning window.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-8 Configuring the DeviceNet Network

Click on the Browse button.

You will see the Device Selection window.

Select the DeviceNet network.

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

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-9

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

You will see the Node Commissioning window with the current settings for your scanner. Your window will look similar to the next one shown in this procedure.

The default scanner settings are:

• baud rate = 125K

• node address = 63

In the New Device Settings: Node Address box, enter the new node address.

Click on Apply and Exit the window.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-10 Configuring the DeviceNet Network

Configuring the I/O Devices

The information in this section will focus on the scanner’s configuration and parameters that you can change using RSNetWorx.

The following screen shows how a DeviceNet network is shown within RSNetWorx. As you can see, node one is a 1769-SDN scanner.

To view or modify the scanner’s parameters, double-click on the scanner.

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-11

General Tab

The following screen shows the properties dialog that RSNetWorx displays for the 1769-SDN scanner module.

Available items are accessed through a series of tabs located across the top of the screen. The General tab is the default tab and provides information relative to the module.

TIP

If you ever need product support, you will need to provide the Revision number when you contact

Rockwell Automation Technical Support.

(phone 440-646-5800)

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-12 Configuring the DeviceNet Network

Module Tab

Interscan Delay

This parameter defines the delay time the scanner uses between scans of the DeviceNet network. If you have slave devices configured for

Polled behavior in the 1769-SDN’s scanlist, Interscan Delay (ISD) defines the amount of time the scanner 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-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-13

Each waveform shows polling frequency for the given Foreground to

Background Poll Ratio

Where:

= x foreground slave devices

= 1st background slave device

= 2nd background slave device

= 3rd background slave device

= 4th background slave device

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.

Figure 4.1 Foreground/Background Polling Behavior

Poll Ratio = 1

Poll Ratio = 2

Poll Ratio = 4

Module Defaults

Clicking the Module Defaults button sets Interscan Delay and

Foreground to Background Poll Ratio to the following values, which are:

•

Interscan Delay: 10 msec

•

Foreground to Background Poll Ratio: 1

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-14 Configuring the DeviceNet Network

Slave Mode

Clicking on the Slave Mode button opens the following screen:

TIP

Enable slave mode only if you want to use this scanner as a slave.

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

Table 4.2 Slave Mode Settings

Connection Format

Strobed

Polled

Change of State / Cyclic

Description

Not supported by the 1769-SDN scanner module.

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.

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-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-15

Advanced Module Settings

Clicking on the Advanced button opens the following screen:

Expected Packet Rate (EPR)

When the scanner 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 within 4 times the

EPR value, the slave device drops the connection. If the scanner does not receive a packet from the slave within 4 times the EPR value, it drops the connection and periodically attempts to open a new connection.

When a connection is dropped, status bits in the scanner identify that the slave is not online. Slave behavior when a connection is dropped is a function of the slave device. If the slave is an I/O device, the 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 milliseconds.

IMPORTANT

Changing the EPR number should be done carefully because it effects how long it takes the scanner to detect a missing device.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-16 Configuring the DeviceNet Network

Transmit Retries

Transmit Retries specifies the number of times the scanner attempts to retransmit a change of state or cyclic message that has not been acknowledged by the slave device.

The connection is not necessarily dropped as a result of reaching the

Scanlist Tab

The Scanlist defines which devices on the DeviceNet network are owned by the scanner.

Publication 1769-UM009B-EN-P - May 2002

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 on the same network, or they may have dual functionality. An example of a dual function device is the

1761-NET-DNI. The DNI can be used as slave I/O, or as a communications interface for PLC’s or other DF1 full-duplex devices.

Configuring the DeviceNet Network 4-17

Scanlist

These devices have been assigned to be slave I/O to this scanner. A slave device on DeviceNet can only be owned by 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 ensure that a particular slave device always matches the intended device when the scanner initiates a connection to it. When one of the devices in the Scanlist section is highlighted, these boxes may be checked to indicate to what extent the key parameters must match the actual device on the network. A match of just Device Type can be selected or the additional parameters of Vendor Id, Product Code, Major Revision, and Minor

Revision may be incrementally added. For the Major and Minor

Revision keys, “or higher” may be selected to indicate that an exact match of the revision is required or some higher revision value.

Should the scanner detect a mismatch with any of the key parameters checked, an AutoVerify failure will occur for that slave device and the scanner will not continue the connection allocation process.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-18 Configuring the DeviceNet Network

Input Tab

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

Publication 1769-UM009B-EN-P - May 2002

In this example we have 4 input devices that are mapped into the scanner’s input image. The graphical window at the top shows each device’s node number, catalog number, type of connection that is used between the scanner and the slave device (strobed, polled, cyclic or change of state), the amount of data that will be exchanged (in bytes), and the word within the controller’s input image where the data will appear.

Advanced

Clicking on the Advanced button opens the following screen:

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

(segmented) into separate input image areas. This capability allows you to 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.

Configuring the DeviceNet Network 4-19

Output Tab

The output tab screen allows you to define how data from the scanner is mapped to the outputs of the slave devices.

In this example we have 4 output devices that are mapped into the scanner’s output image. The graphical window at the top shows each devices node number, catalog number, type of connection that is used between the scanner and the slave device (strobed, polled, cyclic or change of state), the amount of data that will be exchanged (in bytes), and the word within the controller’s output image.

Advanced

Clicking on the Advanced button opens the following screen:

The scanner allows you to select up to 4 separate starting addresses from anywhere in the module’s output image, and map that data into the slave device.

This is simply an ease-of-use feature. For maximum performance, do not segment a slave device’s data.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-20 Configuring the DeviceNet Network

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 baud rate and node address as the device being replaced.

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 scanners 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 on-line due to a revision-keying mismatch.

The 1769-SDN scanner 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 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 device’s such as drives. Use the full electronic key, including revision. To enable electronic key revision checking, you must be using a 1769-SDN scanner and RSNetWorx for DeviceNet.

Important Considerations

Keep the following in mind when using the ADR feature with

RSNetWorx for DeviceNet:

•

ADR is intended for use in single-master environments.

•

The CR and AAR features can only be used with devices that are in the scanlist of the scanner.

•

The AAR feature can only be enabled for a device if the CR feature is also enabled.

Publication 1769-UM009B-EN-P - May 2002

Configuring the DeviceNet Network 4-21

•

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

Configure ADR Parameters

On the ADR property page, you can configure the ADR parameters for the 1769-SDN scanner. Using the controls on this property page, you can select ADR parameters and enable/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.

On the ADR property page, select the device you want to configure to use ADR.

Click Load Device Config .

This will load the configuration of each device selected into the scanner 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.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-22 Configuring the DeviceNet Network

Click the box next to Configuration Recovery.

Notice the ADR space (in bytes) is displayed for the module you are updating.

Click the box next to Auto-Address Recovery if desired.

The Enable Auto-Address Recovery box needs to be checked in order for AAR to work.

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.

Publication 1769-UM009B-EN-P - May 2002

When finished, click Download to Scanner .

Click Apply or OK .

Configuring the DeviceNet Network 4-23

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

Click on the Scanlist tab and then on the Download to

Scanner button.

You will see this window:

Select All Records .

Click on the Download button to download the configuration to the scanner.

Click on the OK button to complete the DeviceNet scanner configuration.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

4-24 Configuring the DeviceNet Network

From the File menu select Save As .

6. Save the configuration to a DeviceNet file.

7. Close RSNetWorx.

Publication 1769-UM009B-EN-P - May 2002

SDN Input File

Chapter

DeviceNet I/O Image

This chapter describes the input and output data structure.

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

For information about

SDN Input File

Status Structure

Module Status Register

See page

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.

Table 5.1 Input Image

Name

Status Structure

Input Data Image

Size

66-words (fixed)

180-word array (configurable)

Word Offset

0 to 65

66 to 245

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

5-2 DeviceNet I/O Image

Status Structure

The first area of the input image is the Status Structure and is

illustrated in Table 5.2. The status words are described in more detail

in the following sections

Table 5.2 Status Structure

Description

Scan Counter

Device Failure Array

Autoverify Failure Array

Slave Device Idle Array

Active Node Array

Reserved

(1)

Scanner Status

Reserved Array

information shown in Table 5.7.

Device Status Array

Module Status Register

Words

0 and 1

2 to 5

6 to 9

10 to 13

14 to 17

18 and 19

20 and 21

22 to 31

32 to 63

64 and 65

Data Type

2 words

64-bit array

4-byte array

20-byte array

64-byte array

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-UM009B-EN-P - May 2002

DeviceNet I/O Image 5-3

Device Failure Array

These 64 bits provide status information for use in your control program. For each slave device owned by the scanner the user 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).

Table 5.3 Slave Device Status Information

Input Word

(1)

(2)

(3)

(4)

Bit 0 to Bit 15

Node 0 to Node 15

Node 16 to Node 31

Node 32 to Node 47

Node 48 to Node 63

Description

Bit ON (1) = Slave node faulted

Bit OFF (0) = Slave node not faulted

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

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

5-4 DeviceNet I/O Image

Table 5.4 Slave Device Configuration Comparison to Scanner Configuration

Input Word

(1)

(2)

(3)

(4)

Bit 0 to Bit 15

Node 0 to Node 15

Node 16 to Node 31

Node 32 to Node 47

Node 48 to Node 63

Description

Bit ON (1) = Slave node mismatch

Bit OFF (0) = Slave node match

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

Table 5.5 Slave Device Status

Input Word

(1)

(2)

(3)

(4)

Bit 0 to Bit 15

Node 0 to Node 15

Node 16 to Node 31

Node 32 to Node 47

Node 48 to Node 63

Description

Bit ON (1) = idle

Bit OFF (0) = non-idle

(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-UM009B-EN-P - May 2002

DeviceNet I/O Image 5-5

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.

Table 5.6 Slave Node Status

Input Word Bit 0 to Bit 15

(1) Node 0 to Node 15

Node 16 to Node 31

(2)

(3) Node 32 to Node 47

(4) Node 48 to Node 63

Description

Bit ON (1) = Active node

Bit OFF (0) = Inactive node

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

The Scanner Device Status is a 4-byte array which contains the

Table 5.7 Scanner Device Status

Input Word

Bit

Description

(1)

0 to 7 (lower byte) Scanner Address in BCD

8 to 15 (upper byte) Scanner Status in BCD

0 to 7 (lower byte) Slave Device Address in BCD

8 to 15 (upper byte) Slave Device Status in BCD

(1)

Status codes are defined in Table 8.2 on page 8-3.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

5-6 DeviceNet I/O Image

Reserved Array

Table 5.8 Reserved Array

Input Word

22 to 31

Description

(1)

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 the following table. Each byte indicates the status code of the scanner’s master and the slave devices.

Table 5.9 Device Status

Input Word

...

Bit

Description

(1)

0 to 7 (lower byte) Node 0 DeviceNet Status

8 to 15 (upper byte) Node 1 DeviceNet Status

0 to 7 (lower byte) Node 2 DeviceNet Status

8 to 15 (upper byte) Node 3 DeviceNet Status

...

0 to 7 (lower byte) Node 62 DeviceNet Status

8 to 15 (upper byte) Node 63 DeviceNet Status

(1)

Status codes are defined in Table 8.2 on page 8-3.

Publication 1769-UM009B-EN-P - May 2002

DeviceNet I/O Image 5-7

Module Status Register

The scanner supports a 32-bit Module Status Register as shown below:

Table 5.10 Scanner Module Status Register

Input Word

Bit

Description

Run

Fault

Network Disable

Operation

Bit ON (1) = scanning I/O

Bit OFF (0) = halted

Bit ON (1) = faulted

Bit OFF (0) = not faulted

Bit ON (1) = disabled

Bit OFF (0) = not disabled

Bit ON (1) = failure

Bit OFF (0) = no failure

Device Failure

Autoverify Failure

Communication Failure

Duplicate Node Failure

DeviceNet Power Detect

8 to 15

0 to 15

Reserved

(1)

Reserved

Bit ON (1) = power

Bit OFF (0) = no power n/a 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:

Table 5.11 Input Data Image

Word Offset

66 to 245

Description

DeviceNet Slave input and/or master output data

The Input Data Image is mapped using RSNetWorx for DeviceNet configuration software.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

5-8 DeviceNet I/O Image

SDN Output File

Output Array

The scanner supports up to 182 output words. This array is broken up into two distinct data segments.

Table 5.12 Output Array

Name

Module Command Array

Output Data Image

Size

2 words

180-word array

Word Offset

0 and 1

2 to 181

Module Command Array

The module command array is the primary control interface between your control program and the module.

Table 5.13 Module Command Array

Output

Word

Bit

Description Behavior

5 to 15

16 to 31

Run

Fault

This bit controls when the module scans its mapped slave devices. When set (1), the scanner 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).

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.

Disable Network When set, the scanner is functionally removed from the network.

Reserved

Reset

n/a

Restarts access to the DeviceNet network.

n/a

Reserved

(1)

Reserved

Configuring The DeviceNet System using RSNetWorx

n/a

(1)

DO NOT manipulate Reserved Bits. Doing so may interfere with future compatibility.

Publication 1769-UM009B-EN-P - May 2002

Output Data Image

DeviceNet I/O Image 5-9

The Output Data Image can be up to a 180 word array. The controllers output data will be delivered across DeviceNet 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).

Table 5.14 Output Data Image

Output Word

2 to 181

Description

DeviceNet Slave output and/or master input data

Slave mapping is done using RSNetWorx.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

5-10 DeviceNet I/O Image

Notes:

Publication 1769-UM009B-EN-P - May 2002

System Diagram

Chapter

Using the 1769-SDN Scanner Module with

CompactLogix Controllers

This chapter contains an example where the 1769-SDN scanner module is used with a 1769-L30 controller and a 1769-ADN adapter module.

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

For information about

System Diagram

Purpose

Scope

Creating a Project for the 1769-L30 CompactLogix Controller

See page

6-1

6-2

6-10

The following system diagram shows the example DeviceNet network.

Figure 6.1 1769-SDN DeviceNet Scanner System with a 1769-ADN Adapter

Notebook Computer with:

•

RSLogix 5000, Version 8.02 or higher

•

RSNetWorx, Version 3.00 or higher

•

RSLinx, Version 2.30 or higher

• 1784-PCID DeviceNet Interface card (or a 1770-KFD and a comm. Port)

DeviceNet

DIAG

DeviceNet

Power Supply

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Purpose

This example shows how to provide DeviceNet connectivity for

Distributed I/O for CompactLogix controllers.

Scope

This example describes:

• using RSNetWorx for DeviceNet to assign node addresses to the

1769-SDN and the 1769-ADN and map the adapter’s image into the scanner

• creating a CompactLogix project including the necessary configuration for the 1769-SDN DeviceNet scanner module

• controlling outputs and reading inputs with the distributed I/O via DeviceNet

Configuring The DeviceNet

System using RSNetWorx

The following procedures describe how to assign the node addresses and map the adapter’s image to the scanner.

Configuring the 1769-ADN Adapter

Connect the 1769-SDN scanner, 1769-ADN adapter, and the computer together on a DeviceNet network as shown in the

System Diagram.

Start RSNetWorx. The following screen appears:

Publication 1769-UM009B-EN-P - May 2002

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

Click the Network pull-down menu and select Online (or click the Online icon). The RSLinx communication driver screen appears.

Choose the “1784-PCD-1, DeviceNet” driver, or if you are using a

1770-KFD, choose its driver. In this example, it is assumed that one of these drivers has been previously configured in RSLinx.

The software then prompts you to either upload or download.

Choose upload .

RSNetWorx then browses your network for valid devices. The online screen should look like the following, where the

1784-PCID card (computer) is node 6, the 1769-ADN is node 15, and the 1769-SDN is node 32 for this example.

See Node Commissioning on page 4-7 if you need to add

devices to the DeviceNet network.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Right click on the 1769-ADN and choose Properties . The following screen appears:

Publication 1769-UM009B-EN-P - May 2002

Click on the I/O Bank 1 Configuration tab, then choose upload when prompted. The actual 1769-ADN I/O layout appears. From this screen you can configure the I/O modules in the 1769-ADN system by simply clicking on the slot number box associated with each I/O module.

For this example, only the two analog modules need to be configured. The graphical user interface makes configuring these modules very straight forward. Refer to the Compact I/O Analog

Modules User Manual , publication 1769-UM002A-EN-P for additional information concerning the analog modules.

TIP

Only analog and specialty modules are configurable. Discrete I/O modules, power supplies, and end caps are not configurable.

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

When the I/O modules are configured, click on the Summary tab. Note the number of bytes of input and output data. This will be used later when adding the adapter to the 1769-SDN’s scanlist.

Click Apply , then OK to save the configuration and download it to the adapter.

TIP

Configuration changes made to the adapter or any of its I/O modules with RSNetWorx will not be saved or downloaded to the adapter once the adapter is configured in a scanner’s scanlist.

To make configuration changes, the controller must be placed into the Program mode and the adapter must be temporarily removed from the scanner’s scanlist.

Setting Up the 1769-SDN Scanlist

Next, add the adapter to the scanner’s scanlist.

Right click on the 1769-SDN and choose Properties . The following screen appears:

Click the Scanlist tab, then click Upload when prompted. The area on the left is called “Available Devices” and the area on the right is called “Scanlist”. The 1769-ADN adapter should be on the left. Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Click on the adapter , then click on the single arrow pointing to the right. This moves the adapter from Available Devices to the scanner’s scanlist.

Then, click on the Edit I/O Parameters button and the following screen appears:

Verify that the Rx Size and Tx Size are correct. The Tx

(Transmit) and Rx (Receive) sizes correspond to the total number of output and input bytes noted from the adapter’s

summary page (step 7 on page 6-5).

In this example, the scanner transmits 6 bytes to the adapter

(output data) and receives 28 bytes from the adapter (input data). Click OK when finished with this screen.

Publication 1769-UM009B-EN-P - May 2002

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

Click on the Input tab. The following screen appears:

The first 66 words (0 to 65) are read-only. Refer to page 5-2 in

this manual for information concerning these status words. For this example, 28 bytes or 14 words of input data will be mapped by the scanner to the 1769-L30 controller’s input tag, beginning with word 66. The 1769-ADN adapter also adds 2 words of status information to the input data. Therefore, the actual input data from the I/O modules in the 1769-ADN adapter’s system begins at word 68.

Click Apply , then OK .

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Click on the Output tab. The following screen appears:

Publication 1769-UM009B-EN-P - May 2002

The first 2 words (0 and 1) are read-only from the scanner’s point of view, but are control words for the controller. Bit 0 of output word 0 is used for control. It is the scanner’s Run bit.

When set (1), it places the scanner into Run mode. When the scanner’s Run bit is a 0, the scanner is in Idle mode even if the controller is in Run mode.

The output data begins with word 2. This is where the actual output data goes for the output modules in the 1769-ADN adapter’s system.

TIP

The input and output data being exchanged by the scanner and adapter is packed data. This means that there is no special structure to it that makes it obvious which I/O module it is associated with.

To establish which data is from which module, you must list the number of input and output words each module has. Then, based on its position in the I/O bank, you can determine where any module’s data is in the controller’s

I/O tags.

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

For example, there are 28 bytes of input data and 6 bytes of output data for this example. The I/O modules in the adapter’s system are:

Table 6.1 1769-ADN I/O Bank Input and Output Data Size

Module

ADN Status Information

(added by the 1769-ADN)

1769-IA16

1769-OB16

1769-IF4

1769-OF2

Total Words

Total Bytes

Input

2 words

1 word

6 words

4 words

14 words

28 bytes

Output

0 words

1 word

0 words

2 words

3 words

6 bytes

The total is 14 input words or 28 input bytes. The first two input words are adapter status, leaving 12 words (24 bytes) for data. In this example, words 66 and 67 are the two words of status in the controller input tag for the scanner. The actual input data is then mapped to the controller’s input data tag at the following word locations:

Table 6.2 Input Data Tag

Location

Words 66 and 67

Word 68

Word 69

Words 70 to 75

Words 76 to 79

Description

1769-ADN Status Information

1769-IA16 module’s input word

1769-OB16 module’s input data (output data echo)

1769-IF4 module’s input data

1769-OF2 module’s input data

The output data can be determined in a similar manner. This data begins with word 2 of the output tag in the controller for the scanner as follows:

Table 6.3 Output Data Tag

Location

Word 0 and 1

Word 2

Words 3 and 4

Description

See Module Command Array on page 5-8.

1769-OB16 module’s output word

1769-OF2 module’s output words

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Creating a Project for the

1769-L30 CompactLogix

Controller

Now create a 1769-L30 Project using RSLogix 5000. In this project you will configure the local I/O modules, including the scanner, and view the I/O tags created for scanner. Then you will create a simple ladder program to test our communications with the distributed I/O.

Double-click the RSLogix 5000 icon on your Desktop to start the software. The following screen appears:

Click on the File pull down menu and select New , or click the New icon. In the New Controller screen that appears, select the 1769-L30

CompactLogix5330 controller for the Type, then enter a name for this project. Click OK and the following screen appears:

Publication 1769-UM009B-EN-P - May 2002

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

The first thing to do is to configure the local I/O. The area on the left side of the screen is called the controller organizer. This is where you access controller properties, tasks, tags and configure I/O.

Right click on the last entry in the controller organizer called

CompactBus Local and choose New Module . The following screen appears:

From this screen you can choose, by catalog number, the two discrete

I/O modules in the local system. Select the 1769-IQ16 first, by single clicking on it and then click OK . The next screen that appears needs a name for the module. All other entries should be left at their default values, except keying which may be changed to one of the other two choices if desired. Compatible Module is the default. Click Finish , then repeat this procedure for the 1769-OV16.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

The scanner does not yet have a profile so you must use the Generic

Profile to configure it. After you right click on the CompactBus Local and choose New Module , click on the Generic 1769 Module , then click OK . The following screen appears:

Publication 1769-UM009B-EN-P - May 2002

From the Generic Profile screen, enter a name for the scanner and choose Data – INT for the Comm Format. Then enter the following for the number of input , output and configuration words:

Table 6.4 Comm Format Data

Data

Input

Output

Config

Assembly Instance

101

100

102

Size

TIP

To learn how the Input and Output sizes are

calculated, see Calculating Maximum I/O Sizes for the 1769-SDN Scanner Module on page 6-15.

Once all values are entered, click Finish . The I/O modules should now all appear below the CompactBus Local in the controller organizer.

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

All tags for I/O modules are automatically created when the profiles for these modules are configured. Double click on Controller Tags in the controller organizer to view these tags. Each I/O module slot has

Input, Output and Configuration tags created, if they apply. These

Local I/O tags are structured as follows:

Table 6.5 Local I/O Tag Structure

Tag

Local:s:I

Local:s:O

Local:s:C

Definition s is the slot number

I represents Input Data

O represents Output Data

C represents Configuration Data

Each of these tags can be further expanded by clicking the plus sign to the left of its entry. For example, click the [+] to the left of Local:3:I and the following tags appear:

Local:3:I.Fault

Local:3:I.Data

The Fault tag is a DINT, so clicking its plus sign only reveals its 32 bits. This is status information concerning the module’s connection to the CompactLogix controller. Clicking the plus sign to the left of the

Data tag reveals the 80 input words created when this value was entered into the Generic profile for the scanner. For this example, the input addresses for the scanner are broken down as follows:

Table 6.6 1769-SDN Input Addresses

Tag

Local:3:I.Data[0] through Local:3:I.Data[65]

Local:3:I.Data[66] through Local:3:I.Data[67]

Local:3:I.Data[68]

Local:3:I.Data[69]

Local:3:I.Data[70] through Local:3:I.Data[75]

Local:3:I.Data[76] through Local:3:I.Data[79]

Definition

Read Only Status

1769-ADN Status Information

Input Data from 1769-IA16

Input (output echo) Data from 1769-OB16

Input Data from 1769-IF4

Input Data from 1769-OF2

The Output tag created for the scanner is as follows:

Local:3:O

Click the [+] to its left to reveal Local:3:O.Data.

Click the [+] to its left and the 5 words of output data created when you created the Generic profile for the scanner will be displayed. This output data is broken down as follows for this example:

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Table 6.7 1769-SDN Output Addresses

Tag

Local:3:O.Data[0] through Local:3:O.Data[1]

Local:3:O.Data[2]

Local:3:O.Data[3] through Local:3:O.Data[4]

Definition

Control to 1769-SDN

(1)

Output data for 1769-OB16

Output data for 1769-OF2

(1)

Bit 0 of output word 0 is the Run mode bit for the scanner. With the controller in Run mode, set this bit to a 1 to place the scanner into the Run mode. With the controller in Run and this bit a 0, the scanner will be in Idle

mode and will not scan I/O. The Module Command Array is described in more detail on page 5-8.

Now that you have created a Project, configured the I/O and determined the location in the I/O tags where all input and output data resides, you can write the application program. The program for this example consists of a single rung that is used to place the scanner into the RUN mode.

To place the scanner in the Run mode when the CompactLogix controller is in the Run mode, either set “SDN_RUN” to a 1, or remove it from the program. When “SDN_RUN” is removed, the scanner’s Run bit is always in Run when the controller is in Run.

The rung appears as shown below:

Publication 1769-UM009B-EN-P - May 2002

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

You may add your own logic to the program and wire some I/O to test the I/O in the 1769-ADN adapter, or you may simply turn on outputs in the scanner’s output tags in the controller to verify that they physically turn on at the output card. In addition, you may wire an analog output to an analog input to verify the operation of the network and the analog modules. Be sure the analog modules are properly configured for such operation.

When your program is written, verify and save it, then download it to your controller to run and test your system.

Calculating Maximum I/O

Sizes for the 1769-SDN

Scanner Module

The calculations in this section apply to all Series A CompactLogix controllers, firmware revision 10 and earlier.

The amount of I/O a CompactLogix version 8 controller can exchange with Compact I/O modules is 256 16-bit words. In addition to the I/O words, the following items must be accounted for in the calculations:

•

4 words must be allotted for end cap checking

•

30 words must be allowed for system overhead requirements

TIP

If any module in a CompactLogix system requires more than 30 words for its configuration file, then that length should be used for the system overhead value.

There are two types of I/O modules in a CompactLogix system:

•

Modules with only input data

•

Modules with both input and output data

Modules with only input data are typically discrete input modules like the 1769-IQ16 and 1769-IA16. Discrete output modules, analog modules, and specialty modules contain both input and output images.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

Calculating I/O Usage for the I/O Modules

The formulas below are used to calculate the amount of I/O used by each type of I/O module. The amount of I/O used by each module will then be subtracted from the total amount of I/O supported by the

CompactLogix controller. If we calculate the amount of I/O used by each I/O module in the CompactLogix system, except for the scanner, then what remains is the maximum amount of I/O the scanner can support in that particular system.

Formula for Modules with Only Input Data

The formula is:

6 words + the number of input words rounded to the next even number

Formula for Modules with Input and Output Data

The formula is:

8 words + the number of input words rounded to the next even number + the number of output words rounded to the next even number

Example Calculations

These examples show how to determine the amount of data that will be left for the scanner module.

Example 1:

The 1769-IQ16 module contains only input data, so its total I/O count is:

6 words + 2 words = 8 total words of I/O

Since this module has only one input word, we must round up to 2.

Example 2:

The 1769-OV16 module contains one input and one output word, so its total I/O count is:

8 words + 2 words + 2 words = 12 total I/O words

Publication 1769-UM009B-EN-P - May 2002

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

To determine how much I/O remains for the scanner module we must subtract the I/O used by the other I/O modules in the system, along with the system overhead and end cap detection from the total I/O supported by the CompactLogix controllers (256 words) as follows:

Table 6.8 I/O Data used by the 1769-IQ16 and 1769-OV16 Modules

I/O Words

256

-30

-4

-8

-12

202

Description total I/O words supported by CompactLogix controllers system overhead end cap detection

1769-IQ16 total I/O

1769-OV16 total I/O remaining I/O words

Calculating Remaining I/O Usage for the Scanner Modules

Now we must calculate the number of actual I/O left in the system for the scanner. The 1769-SDN scanner is the type of module with both input and output words.

The amount of I/O words left for the scanner is then calculated as follows:

8 words + N words = 202, where N = total number of input and output words for the for the scanner

N = 202 – 8 = 194 words

This means that in the Generic Profile for the 1769-SDN scanner module, up to a total of 194 words can be used, in any even number mix, with one limitation:

66 words are needed in the input image for Status information from the scanner and 2 words are needed in the output image for the Module Command Array.

This leaves 194 – 68 = 126 words left for actual I/O.

These 66 input words and 2 output words do need to be included in the total input and output words entered into the generic profile for the scanner.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

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

For this example, a total of 14 input words are needed to map the I/O in the 1769-ADN system back to the CompactLogix controller via the

1769-SDN. This must then be added to the 66 status words to calculate the number of input words to enter into the Generic Profile for the

scanner, as shown in Table 6.4. Also, we must add the 3 output words

to the 2 Module Command Array words and include this in the

Generic Profile for the scanner as well.

As shown in Table 6.4 on page 6-12, the total number of input words

for the Generic profile for this example is 80 and the total number of output words for the generic Profile for this example is 5.

The total I/O words used by the scanner for this example is then:

8 words + 80 words + 6 words = 94.

This is obviously less than the 194 words of unused I/O remaining after the 1769-IQ16 and 1769-OV16 modules’ I/O totals were subtracted from the CompactLogix controller’s I/O capacity. This application will not exceed the amount of I/O the CompactLogix controller can access.

Publication 1769-UM009B-EN-P - May 2002

Chapter

Using the 1769-SDN Scanner Module with

MicroLogix Controllers

MicroLogix 1500

Controllers

This chapter contains an example where the 1769-SDN scanner module is used with a MicroLogix 1500 controller. The following table describes what this chapter contains and where to find specific information.

For information about

MicroLogix 1500 Controllers

RSLogix 500 I/O Configuration

Backplane Messaging

Program Upload/Download

Configuring a Local DeviceNet Message

See page

The MicroLogix 1500 programmable controller has two different processors that are compatible with the 1769-SDN scanner module.

The 1764-LSP and 1764-LRP processors can use the scanner as a

DeviceNet master and own DeviceNet slave devices. This allows either processor to communicate with intelligent devices like drives, scales, starters and many others, or use DeviceNet to expand the processors I/O capabilities/capacity.

The 1764-LRP processor allows messaging functionality over

DeviceNet, 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. This is discussed in

greater detail in Configuring a Local DeviceNet Message on page 7-11.

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

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-2 Using the 1769-SDN Scanner Module with MicroLogix Controllers

RSLogix 500 I/O

Configuration

One of the advanced features of RSLogix 500 is the ability to have the programming software establish a communications 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 will illustrate how to read which I/O modules are attached to the controller, and manually configure them. We will then configure the scanner. An example network is shown below:

DeviceNet Network

PC with RSNetWorx for DeviceNet software

MicroLogix 1500 Controller I/O

Bank with 1769-SDN Module

1770-KFD PC

Communication

Module

DANGER

Series 9000

Photoeye

RediSTATION

1305 Drive Connected via 1203-GU6

Enhanced DeviceNet Communications Module

DANGER

MicroLogix 1000 Controller

Connected via 1761-NET-DNI

MicroLogix 1200 Controller

Connected via 1761-NET-DNI

Publication 1769-UM009B-EN-P - May 2002

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-3

Starting the Project

Open RSLogix 500.

Select File.

3. New.

Choose MicroLogix 1500 LRP series C.

The screen capture below should match what you see on your computer.

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

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

Configuration.

Double click I/O Configuration .

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-4 Using the 1769-SDN Scanner Module with MicroLogix Controllers

I/O Configuration Screen

The I/O configuration screen shows each of the controllers 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 through 16 are for

Compact I/O expansion modules (referred to as local I/O, because they are physically attached to the controller). Slots 9 through 16 are only available using a Series C processor with a Series B base unit

(1)

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

TIP

To manually configure the controller I/O, simply drag the appropriate modules from the available list

(right window), to the appropriate slot on the left.

Note, you cannot have open slots, modules must be contiguous from 1 to 16.

Publication 1769-UM009B-EN-P - May 2002

(1)

Series B base units will be available late in 2001. Contact your local Allen-Bradley distributor for availability.

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-5

Read I/O Configuration

The next screen that appears is a communications dialog that allows you to select a communication path using RSLinx to the MicroLogix controller.

If you have previously connected to a controller, the communications driver that you used before will be the active driver. This dialog screen 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, select Read I/O Config .

Installed I/O

RSLogix 500 then 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 discrete input module in slot 2.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-6 Using the 1769-SDN Scanner Module with MicroLogix Controllers

1769-SDN Scanner Module Configuration

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

To configure the scanner in this example, double-click on 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 to 65) are required by the scanner 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).

See Configuring the I/O Devices section on page 4-10 and Chapter 5,

DeviceNet I/O Image, for more information related to mapping

DeviceNet Slave devices into the 1769-SDN’s scanlist.

Output Words

This is the number of output words the controller assigns to the module. The first 2 words (0 and 1) are required by the scanner 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 outputs = 182).

See Configuring the I/O Devices section on page 4-10 and Chapter 5,

DeviceNet I/O Image, for more information related to mapping

DeviceNet Slave devices.

Publication 1769-UM009B-EN-P - May 2002

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-7

Changing the 1769-SDN Configuration

Changing (adding or removing) the amount of data the controller has assigned to the scanner is done in the expansion module configuration screen. From within RSLogix 500, 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.

TIP

Reducing the number of words for either inputs or outputs will require a change in the 1769-SDN’s scanlist, which is done using RSNetWorx.

See page 4-16.

IMPORTANT

It is recommended that you NOT reduce the number of words assigned to a 1769-SDN’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. Simply add the number of additional words that are needed in the module (using the above example), and change the scanlist using

RSNetWorx.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-8 Using the 1769-SDN Scanner Module with MicroLogix Controllers

The configuration screen for the scanner is shown below.

Backplane Messaging

Ignore Configuration Error

Checking (enabling) this box instructs the module to ignore I/O size mismatches. If this is checked and the input/output scanlist configured by RSNetWorx (DeviceNet side of the 1769-SDN) does

NOT match the amount of I/O data assigned by the controller (0 to

180 words), the module will not generate an error.

If this box is not checked, the number of data words on the controller side must match the number of words configured by RSNetWorx. 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. (phone 440-646-5800)

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 DeviceNet. 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-UM009B-EN-P - May 2002

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-9

PCCC Messaging

PCCC stands for “Programmable Controller Communications

Commands”. PCCC provides point to point and master/slave communications 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 communications between

Allen-Bradley controllers. PCCC messaging allows program upload/download to occur over DeviceNet, and allows users to message across DeviceNet, just like they did using DH-485 or DH+.

There are a number of devices that support PCCC messaging over

DeviceNet, including the 1761-NET-DNI (DNI), 1203-GU6 interface, and RSLinx. If the DeviceNet network has DNI’s, either device can initiate a PCCC message.

CIP Messaging

See CIP Generic on page 7-14.

Program Upload/Download

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

IMPORTANT

DeviceNet networks can operate at 125K, 250K or

500K baud. Depending on network size and communication activity, performing program upload and/or download operations while the network is controlling an application may impact control system performance. It is up to the user to know and understand how upload/download will impact their operations.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-10 Using the 1769-SDN Scanner Module with MicroLogix Controllers

To perform program upload/download using RSLogix 500, select

Comms . From the drop-down menu, select System Comms .

System Comms will generate an RSLinx screen 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/download can be performed with the devices at nodes 5, 6, 7 and 32. Node 32 is a 1769-SDN. Simply highlight the

1769-SDN and then click on either the upload or download button on the right side of the screen.

Publication 1769-UM009B-EN-P - May 2002

Configuring a Local

DeviceNet Message

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-11

This section describes how to configure a local message using the scanner and a MicroLogix 1500 1764-LRP processor.

Message Setup Screen

Rung 0 shows a standard RSLogix 500 message (MSG) instruction preceded by conditional logic.

Access the message setup screen by double-clicking Setup

Screen .

The RSLogix 500 Message Setup Screen appears. This screen is used to setup or monitor message parameters for “This

Controller”, “Target Device”, and “Control Bits”. Descriptions of each of these sections follow.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-12 Using the 1769-SDN Scanner Module with MicroLogix Controllers

“This Controller” Parameters

Channel

The 1764-LRP 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 also supports backplane communications through the

Expansion Communication Port (ECP) as illustrated below.

When ECP is chosen, you are able to select which slot position (1 to

16) the scanner resides in. The 1764-LRP processor can support up to two 1769-SDN scanner modules with full messaging functionality.

Publication 1769-UM009B-EN-P - May 2002

TIP

You can use multiple 1769-SDN scanner modules in a MicroLogix 1500 system, but you can only message through the first two. Any other 1769-SDN scanner can only be used for I/O scanning.

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-13

Communication Command

The 1764-LRP processor supports the six standard types of communications 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’s, other MicroLogix 1500 controllers using 1769-SDN scanner modules, etc.). You can initiate reads, writes, program upload/download and online monitoring across DeviceNet. This is functionally identical to DH-485 and DH+ networking.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-14 Using the 1769-SDN Scanner Module with MicroLogix Controllers

CIP Generic

CIP stands for “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 DeviceNet. 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-UM009B-EN-P - May 2002

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-15

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 DeviceNet 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 than 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 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 screen shown below, N7:0 will receive 2 bytes (1 word) of data.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-16 Using the 1769-SDN Scanner Module with MicroLogix Controllers

Target Device

Publication 1769-UM009B-EN-P - May 2002

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 (see MSG Instruction Error Codes on page 7-18). 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 DeviceNet, 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. Some of the parameters are shown in Appendix B,

1769-SDN DeviceNet Class Codes.

TIP

Note, many module parameters are not editable, and some can only be edited when the module is in Idle

Mode.

Using the 1769-SDN Scanner Module with MicroLogix Controllers 7-17

Local Node address

This is the target device’s DeviceNet node number.

Service

DeviceNet 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 allows you to enter specific service code parameters. Information on what services a target device supports is usually provided in the device’s documentation.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

7-18 Using the 1769-SDN Scanner Module with MicroLogix Controllers

MSG Instruction Error

Codes

When the processor detects an error during the transfer of Expansion

I/O Communication Module message data, the processor sets the ER bit and writes an error code at MG file subelement #18 that you can monitor from your programming software.

Table 7.1 1769-SDN Module Error Code

Error Code

E0H

Description

Expansion I/O Communication Module Error.

The processor also writes general status information related to this error at the high byte of MG file subelement #22 that can be monitored from your program.

Table 7.2 Error Status Information

11H

13H

14H

15H

16H

19H

20H

28H

08H

09H

0BH

0CH

0EH

10H

General Status Description

01H Illegal or Unsupported Service Parameter

02H

04H

07H

Resource Unavailable

Segment Type Error in IOI

Connection Lost

Service Not Supported

Invalid Attribute Value

Already in Requested Mode/State

Object State Conflict

Attribute Not Setable

Device State Conflict

Reply Data Too Large

Not Enough Data

Attribute Not Supported

Too Much Data

Object Does Not Exist

Store Operation Failure

Invalid Parameter

Invalid Member ID

Publication 1769-UM009B-EN-P - May 2002

Chapter

Troubleshooting

Diagnostic Indicators

The 1769-SDN scanner module is provided with LED diagnostic indicators on its front panel. The diagnostics provided by these indicators are described in this chapter.

For information about

Diagnostic Indicators

Error Codes

See page

8-1

8-3

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

•

The bicolor (green/red) Module Status LED indicates whether the scanner has power and is functioning properly.

•

The bicolor (green/red) Network Status LED provides information about the DeviceNet channel communication link.

•

The numeric display shows Node Address and Status Display information. Status information precedes the node address.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

8-2 Troubleshooting

The following table summarizes the meanings of the LEDs and numeric codes.

Module LED

Network LED

Node Address and

Status Display

Table 8.1 Troubleshooting the LEDs and Numeric Display

Indicator

Module

Network

Color/Status

Off

Flashing

Green

Indicates

No power applied to module.

No Bus Master (MicroLogix or

CompactLogix controller) present.

Recommended Action

Apply power.

Verify module connectors are properly seated. If they are, cycle 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.

No action required.

Complete flash update or start a new update.

Solid Green Normal operation.

Flashing Red Recoverable Fault - Memory has been erased or is being programmed.

Solid Red Unrecoverable fault

Off

Flashing

Green

Solid Green

No module power, no network power, or communications are not occurring between the module and the DeviceNet network. (This may be an acceptable condition.)

Device is operational. There are no connections established with any of the network devices.

Normal operation. Scanlist is configured.

Module is not in Idle mode.

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.

Verify module has power. Check that the DeviceNet cable is securely connected and the DeviceNet network is powered.

Verify that network power is adequate (11 to 25V dc).

If the module is supposed to be controlling DeviceNet slaves, configure the module’s scanlist.

No action required.

7-Segment

Numeric

Display

Flashing Red One or more of the devices that the scanner is communicating with is in a timed out state.

Solid Red

Node Address and Status

Display

Critical network failure. Duplicate

DeviceNet node address detected.

Monitor the status display, or the module’s status field to determine which slave device is offline.

Reset module. Change module’s node address or change conflicting device’s node address. If failure continues, replace module.

Indicates diagnostic information about the status of the module.

•

When the numeric display is showing 0 to 63, it is indicating the scanner’s DeviceNet node address.

•

When it shows 70 to 99, it indicates an Error Code for the displayed node address.

•

When it flashes alternating numbers, one is the Error Code (70 to 99), and the other is the Node

Number (0 to 63) that has generated the error.

See the list of Error Codes on page 8-3 for more information.

Publication 1769-UM009B-EN-P - May 2002

Troubleshooting 8-3

Error Codes

The following table describes the Error Codes indicated by the

7-segment numeric display.

Table 8.2 Device Status

Name Description Recommended Action Code

(decimal)

70 Duplicate Node

Illegal Scanlist Data

Controller has Failed Duplicate Node Address

Check. The node address selected is already in use.

Illegal data in scanlist.

Slave Timeout One of the module’s slave devices has stopped communicating.

Electronic Key Mismatch The slave device Vendor ID key parameter does not match the slave’s configuration in the module’s scanlist.

No Messages Received No network traffic received by the scanner. 10 seconds have elapsed and no network traffic for the module or for any other device have been received by the module.

No Message For Scanner No direct network traffic for the scanner detected. 10 seconds elapsed and no DeviceNet input being screened by the module has been received.

Slave Data Size

Mismatch

The data being received from the slave device does not match the configuration in the scanlist.

Change the module’s or conflicting device’s network address (node number) to an available one.

Reconfigure the scanlist table and remove any illegal data.

Inspect the module’s slave devices and verify the DeviceNet connections.

Make sure that the device at the flashing node address matches the desired electronic key (vendor, product code, product type)

Verify the scanlist is correctly configured to scan slave devices. Verify DeviceNet network connections.

None. There are other active devices on the network, initiating messages, but none of the messages are for the module.

No Such Device

Transmit Failure

In Idle Mode

Scanner Faulted

Slave device in scanlist does not exist.

The module has failed to transmit a message.

Module is in IDLE mode.

Either reconfigure the slave device, or change the module’s scanlist to match the slave device.

Either add the device to the DeviceNet network, or delete the device’s entry in the scanlist.

Make sure that the module is connected to a valid network. Check for disconnected cables.

Put the controller into RUN mode and enable the RUN bit in the Module Command Array.

See page 5-8.

Check the FAULT value in the Module

Command Array. See page 5-8.

Fragmentation Error

Slave Init Error

The Scanner has stopped producing and consuming I/O data. This condition does not affect the scanner’s system or messaging modes.

Error detected in sequence of fragmented I/O messages from device.

Check scanlist table entry for slave device to make sure that input and output data lengths are correct. Check slave device configuration.

Check slave device’s configuration. Reboot slave device.

Slave device is returning error responses when the module attempts to communicate with it.

Not Yet Initialized Module has not completed its initial attempt to None. This code clears itself once the establish communications with its slaves.

module properly initializes all slave devices on the network.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

8-4 Troubleshooting

Table 8.2 Device Status

Code

(decimal)

Name

Description Recommended Action

Receive Buffer Overflow

Device Went Idle

Auto Device

Replacement (ADR) Error

Data size returned is larger than expected.

Device is producing idle state.

Slave device responded with an error to the initialization data sent to it by the scanner; or the configuration table in the scanner’s flash memory is not valid for a slave node.

Configure the slave device for a smaller data size.

Check the device configuration and slave node status.

Try the ADR download again. If it still fails, try clearing the ADR flash by downloading an empty ADR configuration to the scanner and then try the ADR configuration again.

Disabled Network

Bus Off

No DeviceNet Power

FLASH Update

Firmware Corrupted

Hard Fault

DeviceNet Port is Disabled

Bus off condition detected on integral DeviceNet port.

Check for the DISABLE being set in the

Module Command Array. See page 5-8.

Check the DeviceNet connections and physical media integrity. Check system for failed slave devices or other possible sources of network interference. Check the

Baud Rate.

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.

Flash Update In Progress None. DO NOT disconnect the module from the network while a FLASH update is in progress.

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.

Cycle Power. Reflash module firmware.

Contact Rockwell Automation Technical

Support.

Publication 1769-UM009B-EN-P - May 2002

Appendix

Specifications

This appendix contains the product specifications for the 1769-SDN

DeviceNet Scanner Module.

For information about

General Specifications

Electrical and DeviceNet Specifications

Dimension Drawings

Compact I/O with CompactLogix Controller and Power Supply

Compact I/O with MicroLogix 1500 Base Unit and Processor

See page

A-1

A-2

A-3

General Specifications

Specification

Module Dimensions

Value

118 mm (height) x 87 mm (depth) x 35 mm (width) height including mounting tabs is 138 mm

4.65 in. (height) x 3.43 in (depth) x 1.38 in (width) height including mounting tabs is 5.43 in.

280g (0.61 lbs.) Approximate Shipping Weight

(with carton)

Storage Temperature

Operating Temperature

Operating Humidity

Operating Altitude

-40°C to +85°C (-40°F to +185°F)

0°C to +60°C (32°F to +140°F)

5% to 95% non-condensing

Vibration

2000 meters (6561 feet)

(1)

Operating: 10 to 500 Hz, 5G, 0.030 inches maximum peak-to-peak

Shock

Agency Certification

Operating: 30G panel mounted (20G DIN rail mounted)

Non-Operating: 40G panel mounted (30G DIN rail mounted)

•

C-UL certified (under CSA C22.2 No. 142)

•

UL 508 listed

•

CE and C-Tick compliant for all applicable directives

•

ODVA DeviceNet conformance tested

Hazardous Environment Class Class I, Division 2, Hazardous Location, Groups A, B, C,

D (UL 1604, C-UL under CSA C22.2 No. 213)

Radiated and Conducted Emissions EN50081-2 Class A

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

A-2 Specifications

Specification

Electrical /EMC:

ESD Immunity (IEC61000-4-2)

Radiated Immunity

(IEC61000-4-3)

Fast Transient Burst

(IEC61000-4-4)

Surge Immunity

(IEC61000-4-5)

Conducted Immunity

(IEC61000-4-6)

Value

The module has passed testing at the following levels:

•

4kV contact, 8kV air, 4kV indirect

•

10 V/m, 80 to 1000 MHz, 80% amplitude modulation, +900 MHz keyed carrier

•

2 kV, 5 kHz

•

2 kV galvanic gun

10V, 0.15 to 80 MHz

(2)

(1)

For operation above 2000 meters, consult the factory.

(2)

Conducted Immunity frequency range may be 150 kHz to 30 MHz if the Radiated Immunity frequency range is 30

MHz to 1000 MHz.

Electrical and DeviceNet

Specifications

Specification

Bus Current Draw (maximum)

Value

440 mA at 5V dc (2.2 Watts)

DeviceNet Power Requirements N.E.C. Class 2

90 mA at 11V dc (maximum)

110 mA at 25V dc (maximum)

200 mA for 1.5 ms (inrush)

Heat Dissipation (maximum)

Baud Rates

Maximum Cable Length

DeviceNet Cable

3.8 Watts (assumes typical DeviceNet network traffic)

125K bits/second (default)

250K bits/second

500K bits/second

500 meters at 125K baud

100 meters at 500K baud

Allen-Bradley catalog number 1485C-P1-Cxxx. Refer to publication DN-2.5 for more information.

Power Supply Distance Rating

DeviceNet to Compact Bus

Isolation

Vendor I.D. code

Product Type Code

Product Code

4 (The module may not be more than 4 modules away from the power supply).

Verified by one of the following dielectric tests: 500V ac for 1 minute or 707V dc for 1 minute.

30V dc working voltage (IEC Class 2 reinforced insulation)

105

Publication 1769-UM009B-EN-P - May 2002

Dimension Drawings

Mounting Hole

Dimension

Specifications A-3

Compact I/O with CompactLogix Controller and Power Supply

NOTE: All dimensions are in mm (inches). Hole spacing tolerance: ±0.4 mm (0.016 in.).

50 mm

(1.97 in)

40 mm

(1.58 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

70 mm

(2.76 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

28.5 mm

(1.12 in)

DIN Rail

Center Line

Mounting Hole

Dimension

14.7 mm

(0.58 in)

Compact I/O with MicroLogix 1500 Base Unit and Processor

NOTE: All dimensions are in mm (inches). Hole spacing tolerance: ±0.4 mm (0.016 in.).

168 mm

(6.62 in)

147 mm

(5.79 in)

35 mm

(1.38 in)

35 mm

(1.38 in)

28.5 mm

(1.12 in)

DIN Rail

Center Line

13.5 mm

(0.53 in)

14.7 mm

(0.58 in)

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

A-4 Specifications

Notes:

Publication 1769-UM009B-EN-P - May 2002

1769-SDN DeviceNet Class Codes

Appendix

This appendix contains the most commonly used class codes for the

1769-SDN DeviceNet Scanner Module. They are shown in the following tables.

Table 2.1 DeviceNet Object

Name

MAC ID

Baud Rate

Bus Off Counter

(1)

The set also causes a reset.

Class Instance Attribute Data Size Access

0x03 0x01 0x01 1 byte

Get/Set

(1)

0x03

0x01

0x02

0x04

1 byte

Get/Set

Get

Table 2.2 Identity Object

Name

Vendor ID

Device Type

Product Code

Revision

Status

Serial Number

Product Name

0x01

Class Instance Attribute Data Size Access

0x01 0x01 0x01 2 bytes Get

0x01

0x02

0x03

2 bytes

Get

0x01

0x04

0x05

0x06

0x07

2 bytes

4 bytes

9 bytes

Get

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

B-2 1769-SDN DeviceNet Class Codes

Notes:

Publication 1769-UM009B-EN-P - May 2002

Glossary

This term:

Auto-Address

Recovery (AAR)

Means:

Auto-Address Recovery (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 not in the Scanners 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 on-line due to a revision-keying mismatch.

Auto Device

Replacement (ADR)

The Auto Device Replacement feature automates the 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

Change of State

The scanner module’s support of explicit message transfer.

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

Recovery (CR)

Controller

Cyclic

Dual Mode

EDS

Configuration Recovery (CR) allows a slave device to be removed from the network and replaced with an identical slave device configured at the same Baud Rate and Node Address as the device being replaced.

The programmable controller, for example:

CompactLogix or MicroLogix 1500.

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 only sent at a user-configurable rate.

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.

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.

Allen-Bradley Drives

Publication 1769-UM009B-EN-P - May 2002

Glossary 2

This term:

I/O

Input Data

MAC ID

Multicast

Network

Node

Offline

Online

Output Data

Point-to-Point

Polled

Record

Scanlist

Scanner

Slave Mode

Strobed

Means:

An abbreviation for “input and output”.

Data produced by a DeviceNet device and collected by the scanner module for the host platform to read.

The network address of a DeviceNet node. Also referred to as node address .

Used when describing a strobe message.

The DeviceNet network or the RSNetWorx for DeviceNet software representation of the network.

Hardware that is assigned a single address on the network (also referred to as a “device”).

When the host platform is not communicating on the network.

When the host platform is configured and enabled to communicate on the network.

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.

Abbreviation for an IBM ® compatible personal-computer.

Used when describing a poll message. The message solicits a response from a single, specified device on the network.

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

The node address and channel-specific memory assigned in the scanner module’s non-volatile storage for a node in the scanlist.

An abbreviation for “receive”.

The list of devices (nodes) with which the scanner is configured to exchange I/O data.

The function of the 1769-SDN module to support the exchange of I/O with slave modules.

The 1769-SDN module is in slave mode when it is placed in another DeviceNet master’s scanlist as a slave device.

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.

An abbreviation for “transmit”.

Publication 1769-UM009B-EN-P - May 2002

Index

A

Allen-Bradley support

P-4

M

manuals, related

module command array

5-8

mounting

3-7

B

before you begin

1-1 ,

C

change of state message

common techniques used in this manual

P-3

configuring DeviceNet

I/O devices

4-10 –

4-23 ,

4-24

scanlist configuration

setting up an online connection

4-4 –

4-6

software installation

using RSLinx

using RSNetworx

current draw

cyclic message

D

data tables

1-5

DeviceNet driver adding

4-2 –

DIN rail mounting

3-10

O

operating modes

1-5 ,

5-8

output data definition

P

panel mounting

3-8

– 3-9

poll message

power requirements

3-2

publications, related

R

related publications

Rockwell Software contact information

P-4

RSLinx configuring DeviceNet

4-2 –

installation

RSNetWorx technical data publication

RSNetWorx for DeviceNet configuration screen map

1-7

configuring DeviceNet

4-4 –

4-24

installation

E

EMC Directive

3-1

equipment required for installation

European Union Directives

3-1

explicit messaging

1-4 ,

7-8

G

grounding

3-11

S

scanlist configuration

4-10

scanner module functions

1-3

software installation

software versions

4-1

spacing

3-7

start-up instructions

strobe message

I

input data definition

installation

getting started

grounding

heat and noise considerations

3-4

T

technical support

P-4 ,

4-11

tools required for installation