Chapter 5 Configure the Network Online
Before You Begin. Verify Communication Between the Computer and Devices. Create a New File for the Network. Go Online to Your Network. Configure Each Device. Upload the Configuration of a Device. Change and Download Device Configuration. Configure the Scanner. Upload the Current Scanner Configuration. Define the Scanner Properties. Build the Scan List. Set the Alignment Option. Manually Assign Each Device to a Memory Location. Download the Configuration to the Scanner. Upload and Save the Configuration File. Generate an RSNetWorx for DeviceNet Report. 76 77
Chapter 6 Automatically Configure a DeviceNet Network
How AutoScan Operates. 80 Determine If You Can Use AutoScan. 82 How AutoScan Affects Your Network. 83 Install the DeviceNet Node Commissioning Tool. 84 Connect Devices to the Network. 84 Install a Scanner or Network Interface Devices. 84 Install Other DeviceNet Devices. 86 Set the Node Address and Baud Rate with the DeviceNet Node Commissioning Tool. 87 Add the Scanner to the RSLogix 5000 Project. 89 Add the Scanner to the I/O Configuration Folder. 89 Define the Properties of the Scanner. 90 Enable AutoScan with RSLogix 5000 Software. 91 Initiate AutoScan via the User Program. 93 Implementing AutoScan. 93 Additional Considerations Regarding AutoScan. 97 Access Device Data. 99 Put the Scanner in Run Mode. 100 Additional Information About AutoScan. 101 Type of Connection that the Scanner Sets Up. 101 Allocating More Memory for Each Device. 101
Chapter 7 Control a Device
Before You Begin. RSNetWorx Report for the Network. Data Map for Each of Your Devices. Add the Scanner to the Controllers I/O Configuration. Conserve EtherNet/IP or ControlNet Network Bandwidth. Add the Scanner to the I/O Configuration Folder. Configure the Scanner. Determine the Address of DeviceNet Data. SoftLogix 5800 Controller. Determine If a Device Has Failed. Place the Scanner in Run Mode. When to Use a MSG Instruction. Determine the Parameter Number to Access. Determine the Configuration of the Parameter. Test the Parameter. Enter Message Logic. Define the Source or Destination Data. Enter and Configure the MSG Instruction. Set the Communication Path. 121
Chapter 8 Interlock and Share Inputs
Interlock. Choose a Master Controller. Determine How Much Data to Exchange. Enable Slave Mode for the Slave Scanner. Map the Slave Mode Data. Add the Slave to the Master Scanners Scan List. Map the Data of the Slave. Place Both Scanners In Run Mode. Share Inputs. Add the Input to the First Scanner. Add the Input to the Second Scanner. Map the Input Data in the Second Scanner. 129 130
Chapter 9 Communicate with a PanelView Choose Data Types. 131 Choose a Communication Method. 132 Standard Terminal
I/O Slave Communication. Explicit Server Communication. Explicit Client Communication. Plan and Configure I/O Slave Tags. Use a Word/Bit Format for Each Tag. For Integers, Skip Every Other Word. Configure an I/O Slave Tag. 135

Additional Resources

For more information on the products included in this publication, use the publications listed in this table.
Resource DeviceNet Modules Installation Instructions, publication DNET-IN001 DeviceNet Media Design Installation Guide, publication DNET-UM072 Logix5000 Controllers Common Procedures Programming Manual, publication 1756-PM001M Description Describes how to install and set up 1756-DNB, 1769-ADN, and 1769-SDN DeviceNet modules. Describes how to design, install, and troubleshoot a DeviceNet cable system. Links to a collection of programming manuals that describe how you can use procedures that are common to all Logix5000 controller projects.

Network Configuration

The following chapters describe how to set up a DeviceNet network: Chapter 2Connect a Computer to the DeviceNet Network Chapter 3Connect Devices to the Network Chapter 4Configure the Network Offline Chapter 5Configure the Network Online You are not required to complete all tasks in each chapter in the exact order presented to set up your DeviceNet application. For example, you can configure your network offline before you connect a computer to the network. However, there are some requirements related to the order in which you complete tasks. For example, you must complete the tasks in chapters 2 and 3 before you can configure the network online. The following table describes optional and required conditions to consider when determining the order in which you plan to complete tasks in your DeviceNet application.
Network Configuration Tasks
Task Connect a computer to the network Optional Conditions Can be completed before or after connecting devices to the network Can be completed before or after configuring the network offline Can be completed before or after connecting a computer to the network Can be completed before or after configuring the network offline Can be completed before or after connecting a computer to the network Can be completed before or after connecting devices to the network Can be completed before configuring the network online Can be completed without creating a network configuration file offline Required Conditions Must be completed before configuring the network online
Connect devices to the network
Must be completed before configuring the network online
Configure the network offline
Configure the network online
Computer must be connected to the network before configuring the network online Devices must be connected to the network before configuring the network online

Chapter

DeviceNet Overview
The Logix5000 family of controllers operates with many DeviceNet communication modules. This chapter describes each communication module and the preliminary tasks you must complete before your configure and program the DeviceNet network.
Topic Choose a Single Network or Subnets Choose a Scanner Bridge Across Networks Choose a Baud Rate for the Network Calculate Scanner Memory Requirements Assign an Address to Each Device Page 20 23

Disadvantages to Using Subnets
There are disadvantages to using subnets for your DeviceNet application: The overall cost to install the network is higher than using a single network. You must manage multiple networks. The Logix5000 controller is remote from the linking device. For example, with subnets in a 1768 CompactLogix application, a 1768-L45 controller is remote from the 1788-CN2DN linking device.

Choose a Scanner

The DeviceNet scanner connects a Logix5000 controller to the devices on a DeviceNet network. The following graphic shows how a scanner exchanges data between a controller and devices on the DeviceNet network.
Scanner Module The scanner sends the input data to the controller. Controller
The scanner collects input data from the devices on the network.
Input Memory DINT DINT DINT Controller Data
Device Output Memory DINT DINT The scanner collects output data from the controller.
The scanner sends the output data to the devices.
The following table describes how to choose a scanner.
If you are using Single network And 1768 or 1769 CompactLogix controller ControlLogix controller DriveLogix controller SoftLogix 5800 controller Subnets EtherNet/IP main network ControlNet main network Use this scanner CompactLogix 1769-SDN modules ControlLogix 1756-DNB modules 1788-DNBO DeviceNet daughtercard 1784-PCIDS card EtherNet/IP to DeviceNet Linking Device 1788-EN2DN ControlNet to DeviceNet Linking Device 1788-CN2DN

Bridge Across Networks

Logix5000 controllers can usually communicate with devices on other networks with no additional configuration or programming. A bridge connects two networks.
IMPORTANT You cannot bridge from a device on a DeviceNet network to a device on a ControlNet nor EtherNet/IP network. You can only bridge from devices on ControlNet or EtherNet/IP networks to devices on DeviceNet networks. Refer to table Bridging Across Networks on page 17 for more information.
The bridge is one of the following: A single device with communication ports for two different networks, such as a 1788-EN2DN linking device A separate communication device in the same chassis For example, the bridge device shown in the following graphic is connected to both EtherNet/IP and DeviceNet networks. Device 1 on an EtherNet/IP network can communicate with Device 2 on a DeviceNet network through the bridge.
EtherNet/IP Network Switch Device 1 Bridge DeviceNet Network

Device 2

The following table describes how communication can bridge the networks.

Bridging Across Networks

A device on this network Can access a device on this network EtherNet/IP EtherNet/IP ControlNet DeviceNet RS-232 yes yes no yes ControlNet yes yes no yes(1) DeviceNet yes yes yes yes RS-232(2) yes yes no yes

Rockwell Automation Publication DNET-UM004B-EN-P - March 2011 41
Change a Device Node Address
You may need to assign a devices node address that is different from the number automatically assigned when the device is added to the configuration file. Complete the following steps to assign a device a specific node address. 1. Double-click the device. 2. Enter the node address for the device.

3. Click OK.

Configure Device Parameters
Complete the following steps to configure device parameters. 1. Double-click the device to display the configuration dialog box.
2. Click the appropriate tab. 3. Set a parameter to the desired new value. Typically, there are two methods to set a parameter: Choose a parameter from a pull-down menu Type a new value
4. Click Apply to apply the change and leave the configuration dialog box open. or Click OK to apply the change and close the configuration dialog box.

Configure the Scanner

A DeviceNet scanner manages input and output data for a controller. The scanner receives input data from I/O devices, organizes the information into scanner data tables, and sends the input data to the controller when the controller requests it. In addition, when the scanner receives output data from the controller, it sends the data to the I/O devices. A DeviceNet scanner is the only device that can be used as a master on a DeviceNet network. When there is only one scanner on a network, it is the master for that network by default. When there are multiple scanners on the same network, each device can have only one scanner designated as its master, which is the scanner that controls its outputs. You must configure the scanner to define how it communicates with other devices on the DeviceNet network. You must complete the following tasks to configure the scanner to communicate with the devices on the network: Build the Scan List Set the Alignment Option Manually Assign Each Device to a Memory Location
IMPORTANT Make sure you configure the scanner after you add all devices to the network. When you add a device to the network, it automatically appears in the list of available devices for the scanners scan list. If you build a scan list and then add another device to the network, it will not be included in the scan list until you repeat the steps in the next section.

b. If you want to place devices in sequential DINTs, as shown below, leave the box checked. When you check the box, the software automatically assigns a memory location for each device as you add it to the scan list.
If you get the following warning for a device, see Set the I/O Parameters of a Device on page 167.
Use the alignment option to map the I/O data so that it is aligned on a boundary, such as a byte, word, or double-word, or efficiently grouped without alignment in the input or output memory map. To map I/O data so it is grouped without alignment, click the Pack Align option.
Complete the following steps to select an alignment option. 1. Click the Input tab. 2. Click Options. 3. Click the desired data alignment. 4. Click OK.
In SoftLogix 5800 applications, the 1784-PCIDS scanner organizes its input and output memory in 16-bit words. For that scanner, click Word Align.
If you configured the software to automatically assign memory locations as devices are added, as described on page 70, skip this section.
Complete the following steps to manually assign each device to a memory location. 1. Click the Input tab. 2. Select the device.
3. In the Start DWord field, enter the element number to which you want to assign the data. This is the starting point for the data. Larger data sizes wrap to several elements. For example, to start the data in. Data[3], type 3 in the Start DWord box. 4. Click Automap. An entry for the device shows up in the input array.
5. Click the Output tab and repeat step 2 through step 4. 6. Click OK to complete scanner configuration. Sometimes, a specific input or output value may end up as the upper bytes of a DINT in the scanner.
Download the Configuration to the Scanner
IMPORTANT Make sure the scanner is in Idle mode. Complete one of the following tasks to put the scanner in Idle mode: Turn off the O.CommandRegister.Run bit of the scanner.
Place the controller in program/remote program mode. Complete the following steps to download configuration to the scanner. 1. Apply the changes. 2. When the Scanner Configuration Applet warning appears, click Yes to download the changes to the device. 3. Click OK.
Upload and Save the Configuration File
Once you finish configuring the devices on the network, upload the entire network and save the file. This stores the configuration of each device in an offline file. Complete the following steps to upload and save the configuration file. 1. From the File menu in RSNetWorx for DeviceNet software, choose Upload from Network. 2. When the warning appears, click Yes to upload the entire network. 3. Save the file.
An RSNetWorx for DeviceNet software report shows these items: Devices on the network Memory addresses of devices in the scanner Device configurations The report is a useful reference when you program your system. Complete the following steps to generate a report. 1. From the File menu in RSNetWorx for DeviceNet software, choose Generate Report.

Give this address To this device Scanner Your devices Computer interface to the network, such as a 1784-U2DN or 1788-PCIDS device Leave open. Out of the box, a DeviceNet communication module is preset for address 63. Leaving address 63 open lets you get a new device on the network without conflicting with another device.
Refer to Set the Node Address of a Device on page 30 for more information on how to use any of several options to set the node address. Refer to Set the Node Address and Baud Rate with the DeviceNet Node Commissioning Tool on page 87 for more information on how to use the DeviceNet node commissioning tool. 3. Set a baud rate for each device after you add it to the network. When setting baud rates, consider the following: Sensors and similar DeviceNet communication modules use autobaud to set their baud rate. They wait for another device to communicate. Then they set their baud rate to the same baud rate as the other device. If a device has a hardware mechanism to set its baud rate, set it to autobaud, if available. Otherwise, set the device to the baud rate of the network. After you change the address or baud rate of a device via a switch, cycle power to the device. If a device has no hardware mechanism to set its address or baud rate, Refer to Set the Node Address and Baud Rate with the DeviceNet Node Commissioning Tool on page 87. After you set the address of a device, check its network status indicator. Typically, a solid red indicator signifies an address conflict or problem with the baud rate.
Set the Node Address and Baud Rate with the DeviceNet Node Commissioning Tool
Complete the following steps to set a node address and baud rate with the DeviceNet node commissioning tool. 1. Start the node commissioning tool. 2. Click Browse.
3. Check I want to input the address for the device on the selected network. 4. Select the DeviceNet network. 5. Enter the current address for the device. Out of the box, a device uses address 63. 6. Click OK.
7. Enter the new address for the device. 8. Choose the baud rate for the device. 9. Click Apply.

As an option, you can allocate more memory for each device.
Consideration The bytes/node value defines the amount of memory for each address. Description AutoScan lets you specify how much input and output memory to give to each address on the network. For example, if you specify 2 DINTs (8 bytes) per address, the scanner sets aside 2 DINTs for each address. The actual data for the device fills the portion that it needs and the rest remains unused. DINT Device at Address 2 Device at Address 1 Input Memory Device at Address 0
The scanner sets-up communication with any The scanner automatically sets up communication with those devices that fit within the memory device that fits within the allocated memory size. allocated for each address. For example, if you allocate 2 DINTs (8 bytes) per address, the scanner sets up communication with any device that sends or receives 18 bytes of data. The scanner adds as many device as it can until it runs out of memory. If you give too much memory to each address, you may not have enough memory for all your devices. The scanner skips devices that are too large. If a device needs more memory than is allocated, the scanner skips it and does not set up communication with it. For example, if you specify 2 DINTs (8 bytes) per address but a device sends 9 bytes, the scanner does not add the device to the scan list.
Manually editing the scan list turns off AutoScan. If you use RSNetWorx for DeviceNet software to edit the configuration of the scanner, the scanner turns off AutoScan. Do not turn it back on or you will clear the configuration that you just entered. For example, if you use RSNetWorx for DeviceNet software to manually add a device to the scan list, the scanner turns off AutoScan. If turn on AutoScan again, the scanner clears it current configuration and starts over.

Control a Device

Use this chapter to develop the logic that examines and controls your devices.
Topic Before You Begin Determine the Address of DeviceNet Data Determine If a Device Has Failed Place the Scanner in Run Mode When to Use a MSG Instruction Determine the Parameter Number to Access Determine the Configuration of the Parameter Test the Parameter Enter Message Logic Page 117

AutoverifyFailureRegister

SINT[8]

DeviceIdleRegister

ActiveNodeRegister

StatusDisplay 11 ScannerAddress ScannerStatus ScrollingDeviceAddress

SINT[4] SINT SINT SINT

ScrollingDeviceStatus
32 DeviceStatus DeviceStatus SINT[32] SINT[64]
Complete the following steps to add the scanner to the I/O configuration file. 1. Right-click and choose New Module. 2. Select the type of scanner. 3. Click OK. 4. From the Major Revision pull-down menu, choose a major revision number for the scanner. 5. Click OK.
Complete the following steps to configure the scanner. 1. Type a name for the scanner. 2. Enter a node number. 3. Enter the slot number. 4. Enter the minor revision. 5. Enter the size of the input and output memory maps that the scanner will allocate for each device it detects on the network. Valid values range from 032 bytes per node. 6. If you need to make additional configuration changes, such as setting the requested packet interval (RPI), check Open Module Properties. 7. Click OK.
8. If the Module Properties dialog box appears, make additional configuration changes. You can change scanner configuration on the following tabs: General Connection RSNetWorx
Determine the Address of DeviceNet Data
When you add the scanner to the I/O configuration of the controller, RSLogix 5000 programming software automatically creates a set of tags for the input, output, and status data of the network.
Input Data from the Scanner Output Data for the Scanner Status Data from the Scanner
The scanner memory uses this format. slot type.Data [element].bit location which is this tag in the controller. :type.Data [element].bit = Optional Where Slot Location Is The slot number of the scanner If you have this scanner Local ControlLogix 1756-DNB Remote ControlLogix 1756-DNB CompactLogix 1769-SDN SoftLogix 5800 1784-PCIDS Linking Device 1788-EN2DN or 1788CN2DN Type If the data is Input from a device Output to a device The status of the network Element Bit Then location is Local:slot_number_of_scanner name_of_remote_bridge:slot_number_of_scanner Local:slot_number_of_scanner Local:slot_number_of_scanner The name of the linking device in the I/O configuration of the controller Then type is I O S

A specific DINT (DWord, 32-bit integer) within the array A specific bit within an integer
Complete the following steps to determine the tag name, or address, for DeviceNet data. 1. On the RSNetWorx report for the network, find the memory address for the input or output data of the device. 2. Find the corresponding tag in the controller-scoped tags of the controller. 3. Find the required data within the controller tag. Use the data map for the device as a reference.

Local:2:I.Data[0] 0 0

Data Map for Bulletin 160 AC drive
The SoftLogix 5800 scanner 1784-PCIDS organizes input and output memory in 16-bit words. It uses address format word.bit.
Where Word Bit Is INT (16-bit integer) with the memory of the scanner A specific bit within an integer
While you can use the input and output tags of the scanner directly in your logic, it is easier to use alias tags.
Determine If a Device Has Failed
If a DeviceNet communication device stops communicating, such as because of a device failure, the tag for the device stays at its last value. To make sure that your input data is valid, we recommend that you buffer the input data and examine the device failure register.
Indication that a device has failed. There is 1 bit for each address on the DeviceNet network. If a bit = 1, then the device at that address has failed. Addresses 0 to 7 Address 0 Address 1

Addresses 8 to 15

On every scan of the controller, execute logic similar to the following: If PhotoEye_RawData = 1 and PhotoEye_Failed = 0 then PhoteEye = 1 Otherwise PhoteEye = 0 Use the PhotoEye tag in the rest of your logic (not PhotoEye_RawData). Input Data from Device Failure Bit for Device Data for Your Logic
Place the Scanner in Run Mode
Complete the following steps to run the DeviceNet network. 1. Set the following bit of the output structure for the scanner.
If you want to Run the network Not run the network (idle mode) Fault the network Not fault the network Disable the network Enable the network Halt the scanner (ceases all operation) Unhalt the scanner Reset the scanner Resume operation after a reset Set this bit O.CommandRegister.Run O.CommandRegister.Run O.CommandRegister.Fault O.CommandRegister.Fault O.CommandRegister.DisableNetwork O.CommandRegister.DisableNetwork O.CommandRegister.HaltScanner O.CommandRegister.HaltScanner O.CommandRegister.Reset O.CommandRegister.Reset To 1 0

5. To read a parameter: Choose Get Attribute Single from the Service Type pull-down menu. Choose the tag to store the value from the Destination pull-down menu. Type the class, instance, and attribute for the parameter in hexadecimal format.
Set the Communication Path
The communication path specifies the route to the device. A communication path follows this format: scanner_name,2,device_address
Where scanner_name device_address Is The name of the scanner in the I/O Configuration folder of the controller. The address of the device on the DeviceNet network.

EXAMPLE

If the name of the scanner is MyScanner and the device is at address 3, the path is as follows: MyScanner,2,3
Complete the following steps to set the communication path. 1. Click the Communication tab. 2. Click the Browse button and select the scanner. 3. Type the rest of the path. 4. Click OK.
Typically, a CIP Generic MSG instruction requires no connection to transfer its data.
This type of message CIP data table read or write PLC2, PLC3, PLC5, or SLC (all types) Using this communication method CIP CIP CIP with Source ID DH+ CIP Generic Block-transfer read or write CIP N/A Uses a connection Yes No No Yes Your choice(1) Yes
(1) You can connect CIP generic messages, but for most applications we recommend you leave CIP Generic messages unconnected.
For more information on programming MSG instructions, see the Logix5000 Controller General Instructions Reference Manual, publication 1756-RM003.
Interlock and Share Inputs
The chapter describes how to interlock and share inputs over a DeviceNet network.
Topic Interlock Share Inputs Page 124 129

Interlocking

Controller Scanner A
Scanners (controllers) exchange data with each other.

Controller Scanner B

Sharing Inputs

DeviceNet Network Device

Input data goes to both scanners (controllers).

Chapter 8

Interlock
To set up an interlock between two controllers over a DeviceNet network, complete the following tasks: Choose a Master Controller Determine How Much Data to Exchange Enable Slave Mode for the Slave Scanner Map the Slave Mode Data Add the Slave to the Master Scanners Scan List Map the Data of the Slave Place Both Scanners In Run Mode
Choose a Master Controller
To interlock, choose a controller to serve as the master. The other controller becomes a slave to the master. This defines the relationship between the controllers. The scanners of each controller still scan and control their own devices, if desired.
Controller Scanner A Master
Controller Scanner B Slave
Determine How Much Data to Exchange
Before you configure the scanners for the interlock, determine how much data you want to exchange between the controllers.

Configure the Scanner to Update I/O Slave Tags
Complete the following tasks to access I/O slave tags and map the data to the input and output maps of the scanner: Add the Terminal to the Scan List Edit I/O Parameters Map Input and Output Data
Add the Terminal to the Scan List
Complete the following steps to add the terminal to the scanlist. 1. Click the Scanlist tab. 2. Clear Automap on Add. 3. Add the terminal to the scanlist. 4. Click OK.

Edit I/O Parameters

Complete the following steps to edit I/O parameters. 1. Select the terminals. 2. Click Edit I/O Parameters. 3. Enter the input and output sizes in bytes. Make sure each number is two times the number you entered in the communication set-up of the terminal (1 word = 2 bytes). 4. Click OK.
Map Input and Output Data
Complete the following steps to map input and output data. 1. Click the Input tab. 2. Select the terminal. 3. Enter the starting element for the data in the input array. 4. Set the alignment option (typically DWord align). 5. Click AutoMap. An entry for the device shows up in the input array. 6. Click the Output tab and repeat steps 2 through 5.
Address I/O Slave Tags in the RSLogix 5000 Programming Software Project
You must get the following information to find the data for an I/O slave tag in your RSLogix 5000 programming software project: RSNetWorx for DeviceNet report for the network Address for the tag in the PanelView terminal Complete the following steps to get the information described previously. 1. On the report for the network, find the memory address for the PanelView terminal. 2. Find the corresponding tag in the controller-scoped tags of the controller. 3. Find the data within the controller tag. Use the tag address as a reference.

Local:2:I.Data[10] 0 0

Tag addresses in the PanelView terminal.

I:0 I:0

DeviceNet tags use the format described below.
Scanner Memory Format slot:type.Data[element].bit Where Location Is Location of the scanner in the system If you have this scanner ControlLogix 1756-DNB Then location is In a local chassis remote chassis Location is Local:slot_number_of_scanner adapter:slot_number_of_scanner where: adapter is the name of the EtherNet/IP or ControlNet module in the remote chassis. Tag in Controller location:type.Data[element].bit

CompactLogix 1769-SDN SoftLogix 5800 1784-PCIDS EtherNet/IP to DeviceNet Linking Device (1788-EN2DN) ControlNet to DeviceNet Linking Device (1788-CN2DN) Type Type of data: Where Input from a device Output to a device Status of the network Element Bit
Local:slot_number_of_scanner
The name of the scanner in the I/O configuration of the controller

Is I O S

The SoftLogix 5800 scanner 1784-PCIDS organizes input and output memory in 16-bit words. It uses the following address format. word.bit
Plan and Configure Explicit Server Tags
Explicit server tags are similar to I/O tags except that the controller initiates the communication with the terminal. Explicit server tags do not show up on the input and output maps of the scanner.
Assign Assembly Instances
A PanelView terminal gives you 14 assembly instances (316) for explicit server tags. Assembly Instance bits 16 bits Write Tag Tag address = I:0 If a bit-level tag, then tag address = I:0/bit # (015)
Each instance give you 64 words for either input or output data.

16 bits Read Tag

Assembly Instance 4
Read Tag Tag address = O:0 If a bit-level tag, then tag address = O:0/bit # (015)

16 bits Write Tag

Assembly Instance 16
16 bits 16 bits Use an assembly instance for either input (write) or output (read) tags, but not both.
Determine how you will use each assembly instance.
Instance Number Input (Write) or Output (Read) input output Instance Number Input (Write) or Output (Read)
Logix5000 controllers use 32-bit integers (DINTs). Complete the following steps to lay out your PanelView tags in a method that makes programming easier. 1. For bit-level tags, set aside an even number of words. 2. For each integer, set aside 2 words. Start each integer on an even word. This method lets each integer map to its own element in the scanner/controller.
Word Address of an integer value. Do not address this word. Leave it unused. Address of an integer value. Do not address this word. Leave it unused.
Configure an Explicit Server Tag
Complete the following steps to configure an Explicit-Server tag. 1. Type a descriptive name for the tag. 2. Choose the data type for the tag. 3. Let the controller initiate the update. 4. Choose the assembly instance for the tag. 5. Assign an address for the tag within the assembly instance. Write tag = I:word/bit Read tag = O:word/bit

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

Documentation Feedback

Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A., Kar Plaza Merkezi E Blok Kat:erenky, stanbul, Tel: +90 (216) 5698400
Publication DNET-UM004B-EN-P - March 2011 192
Supersedes Publication DNET-UM004A-EN-P - March 2004 Copyright 2011 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Add the Driver

1. Start RSLinx software.
2. Click the Configure Driver button.
3. Add the driver: For this network: Select this driver: RS-232 ControlNet EtherNet/IP DeviceNet RS-232 DF1 Devices driver that matches your card. Ethernet devices DeviceNet Drivers
4. Configure the driver. descriptive name for the network (driver) configuration (see pages 3-4 to 3-5 for help with specific drivers)

RS-232 DF1 Devices

Important: Make sure no other driver is configured for the COM port to which you connect the serial cable. 1. Choose the following: COM port that you are using. Logix 5550/CompactLogix.
Auto-Configure 5. Wait for the auto-configuration to finish.

Ethernet Devices

Enter the IP address of the controller or communication module.

1784-PCC

Use the address that the software picks. Or assign a specific address: A. Clear this check box. B. Enter the address that you to use.

1784-PCD

1. Use the default address of 62, if it is unused. 2. Select the baud rate for the network. 3. OK.

1770-KFD

Important: Make sure no other driver is configured for the COM port to which you connect the serial cable.
1. Select the COM port to which you connected the 1770-KFD device.
2. Use the default address of 62, if it is unused. 3. Select the baud rate for the network. 4. OK.
Make Sure the Driver Works
1. Check that the driver is running. 2. Close the dialog box. 3. Open the RSWho window.
4. Double-click the driver to see the network.
Automatically Configure a DeviceNet Network

How To Use This Chapter

Before you use this chapter: Connect your computer to the system. See chapter 4.
This chapter provides a quick method for configuring a DeviceNet network. It uses the AutoScan feature to establish communication between the controller and your devices with minimal steps. To use the AutoScan feature to configure your network:
Step: Determine If You Can Use AutoScan Review How AutoScan Effects Your Network Install the Node Commissioning Tool Connect Each Device to the Network Add the Scanner to the RSLogix 5000 Project Turn On AutoScan Access Device Data Put the Scanner in Run Mode Additional Information About AutoScan Page: 4-1 4-2 4-2 4-3 4-6 4-7 4-9 4-11 4-12

Upload and Save the Network File
1. Network Upload from Network. 2. Yes, upload the entire network.
Once you configure the devices on your network, upload the entire network and save the file. This stores the configuration of each device in your offline file.

3. Save the file.

Control a Device
Use this chapter to develop the logic that examines and controls your devices.
Step: Before You Use This Chapter Determine the Address of DeviceNet Data Program Your Logic With Alias Tags Determine If a Device Has Failed Place the Scanner in Run Mode When to Use a MSG Instruction Determine the Parameter Number to Access Determine the Configuration of the Parameter Test the Parameter Enter Message Logic Page: 7-2 7-7 7-10 7-11 7-12 7-13 7-13 7-14 7-15 7-16
Before You Use This Chapter
Before you use this chapter, get the following information:
RSNetWorx Report for Your Network
Data Map for Each of Your Devices
Add the Scanner to the I/O Configuration of the Controller
Step: If You Need to Conserve EtherNet/IP or ControlNet Network Bandwidth Add the Scanner to the I/O Configuration Folder Define the Properties of the Scanner See page: 7-3 7-5 7-6
If You Need to Conserve EtherNet/IP or ControlNet Network Bandwidth
The default configuration of the scanner gives you the maximum amount of input, output, and status data.
If the scanner communicates with the controller via an EtherNet/IP or ControlNet network and you need to conserve bandwidth over that network, consider reducing the input, output, or status sizes. Set the input and output sizes = the number of input and output DINTs in the scanner that actually store device data. If you are not going to use all the status information, set the status size to the minimum required. See Table 7.1 on page 7-4.

EXAMPLE

Set the status size for a scanner If you want to only use the ASCII representation of scanner status/display, then set the Status Size = 10. If you also want to read the status code of the scanner, set the Status Size = 11.
Table 7.1 Set the status size for a scanner If you want this information: count of I/O scans indication that a device has failed: There is 1 bit for each address on the DeviceNet network (0 -63). The position of a bit = address of a device. If a bit = 1, then the device at that address has failed. indication that the data size of a device does not match the amount of memory allocated for the device in the scanner: There is 1 bit for each address on the DeviceNet network (0 -63). The position of a bit = address of a device. If a bit = 1, then their is a mismatch with that address. indication that a device is idle: There is 1 bit for each address on the DeviceNet network (0 -63). The position of a bit = address of a device. If a bit = 1, then the device at that address is idle. indication that a device is online: There is 1 bit for each address on the DeviceNet network (0 -63). The position of a bit = address of a device. If a bit = 1, then the device at that address is online. ASCII representation of scanner status/display address of the scanner status code of scanner address with an error: scrolls through the addresses with errors ScrollingDeviceStatus member shows the status code status code of an address with an error: scrolls through addresses with errors ScrollingDeviceAddress member shows the address possible future expansion of the structure 5 DINTs status code of lower 32 devices 1 byte per device status code of all devices 1 byte per device 32 DeviceStatus DeviceStatus SINT[32] SINT[64] 11 Set the Status Which gives you: Size to (DINTs): Member: 10 ScanCounter DeviceFailureRegister

Data Type DINT SINT[8]

AutoverifyFailureRegister

SINT[8]

DeviceIdleRegister

ActiveNodeRegister

StatusDisplay ScannerAddress ScannerStatus ScrollingDeviceAddress

SINT[4] SINT SINT SINT

ScrollingDeviceStatus

CompactLogix scanner

ControlLogix, FlexLogix, and SoftLogix5800 scanners EtherNet/IP to DeviceNet linking device
ControlNet to DeviceNet linking device
1. Specify the general properties (name, slot, sizes, etc.).

2. Choose Next.

3. Choose Next.
4. Choose Browse and find the RSNetWorx configuration file for the network (.dnt file). The default path for the file is \Program Files\Rockwell Software\RSNetWorxII\Networks.

5. Choose Finish.

Determine the Address of DeviceNet Data
The scanner memory uses this format: slot type.Data [element].bit location Which is this tag in the controller :type.Data [element].bit
= Optional Where: slot location Is: slot number of the scanner If you have this scanner: local ControlLogix 1756-DNB remote ControlLogix 1756-DNB CompactLogix 1769-SDN SoftLogix5800 1784-PCIDS DriveLogix/FlexLogix 1788-DNBO Linking Device 1788-EN2DN or 1788-CN2DN type If the data is: input from a device output to a device status of the network element bit specific bit within an integer Then location is: Local:slot_number_of_scanner name_of_remote_bridge:slot_number_of_scanner Local:slot_number_of_scanner Local:slot_number_of_scanner name of the scanner in the I/O configuration of the controller name of the linking device in the I/O configuration of the controller Then type is: I O S
specific DINT (DWord, 32-bit integer) within the array
To determine the tag name (address) for DeviceNet data:
1. On the report for the network, find the memory address for the input or output data of the device.
2. Find the corresponding tag in the controller-scoped tags of the controller. 3. Find the required data within the controller tag. Use the data map for the device as a reference.

Local:2:I.Data[0] 0 0

data map for Bulletin 160 AC drive
The SoftLogix5800 scanner 1784-PCIDS organizes input and output memory in 16-bit words. It uses the following address format: word.bit
Where: word bit Is: INT (16-bit integer) with the memory of the scanner specific bit within an integer
Program Your Logic With Alias Tags
alias tag a tag that represents another tag Both tags share the same data. When the data changes, both tags change. An alias tag provides a descriptive name for data, such as DeviceNet input or output data.
As an option, create tags that describe each device without pointing them to the actual addresses of the devices. Later, convert the tags to aliases for the data of the devices.

In addition to the documentation for the device, the EDS file may also give you the required information:

parameter # class

instance attribute number of bytes

min. and max. values

Test the Parameter
A simple way to make sure that you have the correct configuration for a parameter (data size, values, etc.) is to use the Class Instance editor in RSNetWorx software.
1. In RSNetWorx software, go online to your DeviceNet network.
2. Right-click the device and choose Class Instance Editor.
3. Type the class, instance, and attribute for the parameter.
4. To change the parameter: a. Choose Set Single Attribute. b. Select the number of bytes. c. Type the new value in hexadecimal format.
5. To read the parameter, choose Get Single Attribute.

6. Choose Execute.

7. To change how output data is displayed, select the size and format.

Enter Message Logic

To access a parameter of a device (get or set the parameter), configure the MSG instruction as CIP Generic.
Change the current limit of the drive
To configure the MSG instruction:
Step: Define the Source or Destination Data Enter and Configure the MSG Instruction Set the Communication Path See page: 7-17 7-18 7-19
Define the Source or Destination Data
tag that controls the instruction Scope controller Data type MESSAGE The tag cannot be part of an array or a user-defined data type.
source or destination for the data that the instruction sets or gets Scope controller Data type In general, use the DINT data type, even when you set or get less than 4 bytes. Value Make sure the source value stays within the minimum and maximum values for the parameter that you are setting. number of bytes (only if setting a value)
In general: Use the DINT data type for the source or destination tag, even when you set or get less than 4 bytes. Make sure the source value stays within the minimum and maximum values for the parameter that you are setting. When setting a value, the CIP Generic MSG instruction takes only the specified number of bits from the source tag.

MySource_0

For example, if Source Length = 1 byte, then the CIP Generic MSG instruction sends the first byte of MySource_1.

To increase the efficiency of your logic, minimize the use of SINT or INT data types. Whenever possible, use the DINT data type for integers. A Logix5000 controller typically compares or manipulates values as 32-bit values (DINTs or REALs). The controller typically converts a SINT or INT value to a DINT or REAL value before it uses the value. If the destination is a SINT or INT tag, the controller typically converts the value back to a SINT or INT value. The conversion to or from SINTs or INTs occurs automatically with no extra programming. But it takes extra execution time and memory.
Enter and Configure the MSG Instruction
1. Enter the condition for the data transfer. 2. Enter the MSG instruction.

3. Select CIP Generic.

4. To change a parameter: a. Select Set Attribute Single. b. Select the tag that has the new value. c. Type the number of bytes d. Type the class, instance, and attribute for the parameter, in hex.
5. To read a parameter: a. Choose Get Attribute Single. b. Select the tag to store the value. c. Type the class, instance, and attribute for the parameter, in hex.
Set the Communication Path
The communication path specifies the route to the device. A communication path follows this format: scanner_name,2,device_address
Where: scanner_name device_address Is: Name of the scanner in the I/O Configuration folder of the controller. Address of the device on the DeviceNet network.
For example: If the name of the scanner is MyScanner and the device is at address 3, then the path is: MyScanner,2,3 To set the path:
1. Click the Communication tab. 2. Click the Browse button and select the scanner. 3. Type the rest of the path.
Typically, a CIP generic MSG instruction requires no connection to transfer its data.
This type of message: CIP data table read or write PLC2, PLC3, PLC5, or SLC (all types) Using this communication method: CIP CIP CIP with Source ID DH+ CIP generic block-transfer read or write
Uses a connection: yes no no yes your choice(1) yes

CIP na

You can connect CIP generic messages, but for most applications we recommend you leave CIP generic messages unconnected.
For more information on programming MSG instructions, see the Logix5000 Controller General Instructions Reference Manual, publication 1756-RM003.
Interlock and Share Inputs
The chapter describe how to interlock and share inputs over a DeviceNet network.

Interlocking

Controller scanner A
scanners (controllers) exchange data with each other

Controller scanner B

Sharing Inputs
input data goes to both scanners (controllers)

16 bits Scanner Output Map O.Data[0]
Read Tags in PanelView Assembly O:0 Instance O:16 bits 16 bits

O:bits

Explicit Server Communication
Explicit Server Controller executes a MSG instruction that gets or sets data in the PanelView terminal. 14 assembly instances are available for explicit - server transfers. Instance #s are 3 to 16. You define an instance as either input data (I) or output data (O) but not both. Each instance provides 64 words of either input or output data for the terminal. Write Tags in PanelView Assembly I:0 Instance I:16 bits 16 bits

MSG CIP Generic

Controller Tags Array_1[0]
16 bits Controller Tags Array_2[0]
Explicit Client Communication
Explicit Client PanelView terminal sets or gets data in another device on a tag-by-tag basis. PanelView Terminal Read Tag Read Tag Write Tag Device Parameter Parameter Parameter
Plan and Configure I/O Slave Tags
Like the other DeviceNet devices, I/O slave tags use space in the input and output maps of the scanner. The scanner gets/sets the data on each scan of the DeviceNet network. A PanelView terminal gives you 2 blocks of 16-bit words (assembly instances) for I/O slave tags:
Assembly instance 1 stores the data for write tags. It gives input data to the controller.

Input Data

I:0 I:1

16 bits 16 bits

Write Tag
Assembly instance 2 stores the data for read tags. It gets output data from the controller.

Output Data

O:0 O:1

Read Tag

You define the input and output sizes, up to 64 words.
To set up I/O slave tags:
Step: Use a Word/Bit Format for Each Tag For Integers, Skip Every Other Word Configure an I/O Slave Tag See page: 9-5 9-5 9-6
Use a Word/Bit Format for Each Tag
Each I/O slave tag requires a specific address in the corresponding assembly instance. A tag address follows this format:
Type :Word = Optional Where: Type Is: Type of tag If the tag is a: write tag (sends input data to the controller) read tag (gets output data from the controller) Word Bit Specific 16-bit word within the assembly Specific bit within Word (0 - 15) Then use: I O /Bit

1. For each of those devices, set their I/O parameters to polled with a poll rate = background. 2. For the scanner, set the poll ratio = 2. Increase the poll ratio if needed.
communication intermittently stops (status code 78) with a device that: sends or receives large amounts of data (e.g., PanelView operator terminal) and has the I/O parameters currently set to polled
Increase the interscan delay.
Factors that Effect Performance
The following example shows how different I/O or network parameters effect the performance of the network.

Scan Cycle Polled update

3 data at address 3 changes scanner gets the data

P3 Pr3 P4 Pr4 P5 Pr5

Px Scanner sends data to a polled device. Prx Polled device sends input data to scanner. x is the address of a device.
Interscan delay Scanner continues to get polled data from slower responders or larger devices. Communication with software such as RSLinx and RSNetWorx occurs (upload, download, browse, etc.)

Change of state (COS)

P4 Pr4 P5 C3 Pr5

P4 Pr4 P5 Pr5

Strobed update

Sr3 Sr4 Sr5 P1

S Scanner sends strobe request. Srx Strobed devices send input data to scanner. x is the address of a device.

Background poll

Shorter interscan delay
3 data at address 3 changes

scanner gets the data

I/O Parameters of Each Device
The type of connection (message) that you configure for a device determines when data transfers between the device and the scanner. Each device has a default connection type. This is a good starting point. Some devices may not offer all connection (message) types. The following table describes the different types of connections (messages) that you can configure for a device.
Connection (message) type: cyclic change of state (COS) Description: Data transfers at the period that you specify. The default range is 48 - 32,000 milliseconds. Both the scanner and the device sends data whenever the data changes. You also specify a heartbeat period for the connection. If the data does not change within the heartbeat period, the scanner and/or device sends their data at the end of the period. This lets both the scanner and device know that the other is still operational. strobed The scanner sends a single strobed request to solicit data from the strobed devices. The request is 64-bits long (1 bit for each node). In response to the request, each device that is configured for a strobed connection sends its data (up to 8 bytes). A point-to-point data transfer that occurs every I/O scan or as a ratio of the I/O scan (background). At the specified poll rate (every scan or background), the scanner sends data to a polled device (up to 255 bytes). The data is either output data for the device or a request for input data from the device. If the polled device gets a request for input data, it sends its input data (up to 255 bytes).

1. Start RSNetWorx software. 2. Open the file for the network, if necessary. 3. Go online.
4. Double-click the scanner. 5. Click the Module tab. 6. Upload the configuration from the scanner.
Set the Interscan Delay and Poll Ratio
Change these values only if needed.
1. Type or select the time for the interscan delay. 2. Type or select the poll ratio.
Set the I/O Parameters of a Device
1. Click the Scanlist tab 2. Select the device. 3. Choose Edit I/O Parameters.
4. Set the I/O parameters: For: Strobed Transfer Polled Transfer See page: 11-7 11-8
Change of State or Cyclic Transfer 11-7
Change of State or Cyclic Transfer
1. Check this box. 2. Choose Change of State or Cyclic. 3. Type or select the number of bytes that the device sends to the controller. 4. Type or select the number of bytes that the controller sends to the device. 5. For a cyclic update, type the period of the update. 6. Close the dialog box.

Strobed Transfer

1. Check this box. 2. Type or select the number of bytes that the device sends to the controller.

Polled Transfer

1. Check this box. 2. Type or select the number of bytes that the device sends to the controller. 3. Type or select the number of bytes that the controller sends to the device. 4. Choose whether to poll the device every scan or in the background. 5. Close the dialog box.
1. Apply the changes, 2. Yes, download.
After you make a change to your network, upload the entire network and save the file. This makes sure that the offline configuration file matches the network.
Troubleshoot a DeviceNet Network
A DeviceNet network gives you the following status information:
For this information: Front Display Status Tags in the Controller Status Codes See page: 12-1 12-13 12-16

Front Display

To interpret the display or status indicators of a device:
For this information: CompactLogix Scanner 1769-SDN ControlLogix Scanner 1756-DNB ControlNet to DeviceNet Linking Device 1788-CN2DN DriveLogix and FlexLogix Scanner 1788-DNBO EtherNet/IP to DeviceNet Linking Device 1788-EN2DN SoftLogix5800 Scanner 1784-PCIDS See page: 12-1 12-3 12-5 12-7 12-8 12-11
2 Character numeric display: Shows the status code and address of the device (status code first, then address). If a device has a problem, it shows the status code and address of the device (status code first, then address). To interpret the status codes, see Status Codes on page 12-16.

Module status indicator:

State: off flashing green Description: No power applied to module. No MicroLogix or CompactLogix controller is present. Recommended Action Apply power. 1. 2. 3. 4. None. Complete flash update or start a new update. 1. Make sure the device connectors are properly seated. 2. Make sure the bus terminator/end cap is installed. 3. Cycle power. 4. Replace the device. Make sure module connectors are properly seated. Cycle power to the controller. Replace the controller. Replace the device.

Module Status indicator

State off flashing green solid green solid red flashing red Description No power. The device is not configured and is in a standby state. Normal operation Device has an unrecoverable fault. Recoverable fault. DNet Data Rate or DNet Node Address switches are set in the PGM range. Recommended Action Turn on power to the device. Configure the device. None. 1. Cycle power to the device. 2. Replace the device Clear the fault. Change switch settings.
Linking Activity status indicator
State off flashing green flashing red and green Description No traffic Traffic present (flash rate reflects amount of traffic) Module is running boot code only (reduced functionality code only for FLASH upgrading)
ControlNet Network (CNet A, CNet B) status indicators If more than one state is present, the indicators always reflect the highest priority status present on the network. Note that these indicators do not reflect the status of the network access port (NAP).
State both steady off both steady red alternating red & green alternating red steady off flashing red & green flashing red flashing green steady green Priority 1 (highest) (lowest) How to View Cause View together Reset or no power Failed to link interface to ControlNet Self testing Bad node configuration (such as duplicate ControlNet network address) View Channel disabled or not supported independently Invalid link configuration Link fault or no frames received Temporary channel error or listen only Normal operation
Module status (MS) indicator
State: off solid green flashing green flashing red solid red flashing red-green Description: No power applied to device. Device is OK. Device either needs commissioning or is in the standby state. Recoverable fault. Device has an unrecoverable fault. Device is in self test. Recommended Action Turn on power to the controller. None. Make sure the device is correctly configured. Make sure the scan list of the device matches the configuration of the network. 1. Cycle power to the controller. 2. Replace the device None.

State flashing green solid green solid orange flashing red/green off Description Device is in idle mode Device is in run mode Device is powering up. A fault has been detected. There are no devices in the scan list. Recommended Action To control outputs, place the device in run mode. None. None. Clear the fault. If the device is supposed to communicate with other devices, add those devices to the scan list of this device.
DeviceNet (Network Status) indicator
State flashing green solid green flashing red solid red Description Device is OK but is not communicating with other devices on the network. Recommended Action If the device is supposed to communicate with other devices, add those devices to the scan list of this device.
The physical device has the following status lights: I/O status indicator

State: off green

Description: All inputs and outputs are inactive. One or more outputs are active and under control, and no outputs are faulted. One or more inputs are active and producing data, and no inputs are faulted.

flashing green

One or more outputs are idle and no outputs are active or faulted. One or more outputs are faulted, and may be in the fault state. One or more inputs are faulted, and may be in the fault state.

flashing red

solid red
One or more outputs are forced off (may be an unrecoverable fault). One or more inputs has an unrecoverable fault.
Module (MOD) status indicator
State: off solid green flashing green flashing red solid red flashing red-green Description: No power applied to device. Device is OK. Device either needs commissioning or is in the standby state. Recoverable fault. Device has an unrecoverable fault. Device is in self test. Recommended Action Turn on power to the controller. None. Make sure the device is correctly configured. Make sure the scan list of the device matches the configuration of the network. 1. Cycle power to the computer. 2. Replace the device None.
Network (NET) status indicator
In the SoftLogix chassis monitor, the SoftLogix5800 scanner give you the same status indicators as the ControlLogix 1756-DNB. To interpret this indicators, see ControlLogix Scanner 1756-DNB on page 12-3.
Status Tags in the Controller
Tags in the controller give you several levels of information about your DeviceNet network.
individual bits that show the general status and health of the scanner and network detailed information about each device on your network

The DeviceNet cable is not supplying power to the communication port. The firmware of the device is currently being updated. Communication port is in test mode.
Make sure the network has 24V dc power. Check the connection to the device. None. Do not disconnect the device while the update is in progress. You will lose any existing data in the devices memory. None.

Status code (decimal) 97

Description Controller has set the scanner to the halted mode.
Action 1. See if the following bit of the command register for the scanner is on: O.CommandRegister.HaltScanner 2. Cycle power to the scanner.
General firmware error. System failure.
Replace device. Replace device.
Automate the Replacement of a Failed Device
This chapter describes how to reduce the time it takes to replace a failed device:
For this information: How to Automate the Replacement of a Failed Device Set Up Automatic Device Recovery See page: 13-1 13-3
How to Automate the Replacement of a Failed Device
To reduce system downtime if a device fails, use the Automatic Device Recovery (ADR) option. With ADR, you do not have to use any software tools to get a replacement device configured and online.
Some devices do not support ADR.
With ADR, the scanner automatically configures a replacement part. If the address of the device is set via software, the scanner also sets the address of the replacement device.
You configure ADR on a device-by-device basis. Each device lets you set up the following components of ADR:
If you want to: automatically configure a replacement device that matches the electronic key of a failed device And: manually change the address of the replacement device Then select this ADR option for the device:
automatically set the address of the replacement device to address of the failed device (The device must let you change its address via software.)
manually configure a replacement device
If a DeviceNet network has more than one scanner, enable auto-address recovery for only one scanner. If more than one scanner is configured for auto-address recovery, there is no way to determine which scanner will recognize a newly-inserted device on the DeviceNet network.
Set Up Automatic Device Recovery
To set up ADR for a device:
Step: Choose an Electronic Key Level for a Device Update the Network Configuration File Define the Electronic Key Enable Auto-Address Recovery for the Scanner Set the ADR Settings for the Device Download the Changes to the Scanner Upload and Save the Network File See page: 13-3 13-4 13-5 13-6 13-6 13-7 13-7
Choose an Electronic Key Level for a Device
Use the electronic key options to define how closely a replacement device must match a failed device before the scanner applies ADR. The scanner only configures/addresses a device that meets the checked items in the electronic key of the failed device. If multiple devices with the same electronic key fail at the same time, the scanner disables auto-address recovery for those devices. This prevents the scanner from changing the address of the wrong device.

1734-IA2 Input Module

Message size: 1 Byte
7 Produces (scanner Rx) Consumes (scanner Tx) No consumed data ChCh0
Where: Ch0 = channel 0, Ch1 = channel 1; 0 = off, 1 = on
1734-IB2 Sink Input Module
7 Produces (scanner Rx) Consumes (scanner Tx)
Where: Ch0 = channel 0, Ch1 = channel 1; 0 = OFF 1 = ON

No consumed data

1734-IB4 Sink Input Module
Where: Ch0 = input channel 0 Ch1 = input channel 1 Ch2 = input channel 2 Ch3 = channel = OFF 1 = ON

3 Ch3 No consumed data

1734-IV2 Source Input Module
Where: Ch0 = input channel 0 data Ch1 = input channel 1 data
1734-IV4 Source Input Module
7 Produces (scanner Rx) Consumes (scanner Tx) Ch3 No consumed data 2 ChChCh0
Where: Ch0 = input channel 0 Ch1 = input channel 1 Ch2 = input channel 2 Ch3 = input channel 3

1734-OA2 Output Module

Where: 0 = Off, 1 = On
No produced data Not used Ch1 Ch0 Channel state
1734-OB2E Electronically Protected Output Module

7 Produces (scanner Rx)

Where: 0 = no error 1 = error

4 Not used

0 Ch0 Channel status

7 Consumes (scanner Tx)

Where: 0 = OFF 1 = ON

0 Ch0 Channel state

1734-OB2EP Protected Output Module
1734-OB4E Electronically Protected Output Module

Not used

Where: 0 = Off 1 = On

5 Not used

1734-OV2E Protected Sink Output Module
7 Produces (scanner Rx) Where:0 = no error 1 = error Not used ChCh0 Channel status
7 Consumes (scanner Tx) Where:0 = OFF 1 = ON Not used ChCh0 Channel state
1734-OV4E Protected Sink Output Module
7 Produces (scanner Rx) Where:0 = no error 1 = error Not used ChChChCh0 Channel status
7 Consumes (scanner Tx) Where:0 = OFF 1 = ON Not used 4 3
1734-OW2 Relay Sink/Source Output Module
1734-OX2 Relay Output Module
7 Consumes (scanner Tx) 4 Not used 1 ChCh0 Channel state
Where: 0 = NO contact OFF, NC contact ON1 = NO contact ON, NC contact OFF
1734-IE2C Analog Current Input Module

Message size: 6 Bytes

15 Produces (scanner Rx) 00
Input Channel 0 High Byte Input Channel 1 High Byte Status Byte for Channel 1 OR UR HHA LLA HA LA CM CF
Input Channel 0 Low Byte Input Channel 1 Low Byte Status Byte for Channel 0 OR UR HHA LLA HA LA CM CF No consumed data

network configuration 2-17 scanner configuration 6-16 driver 1770-KFD 3-5 1784-PCC 3-4 1784-PCD 3-5 configure 3-3 EtherNet/IP 3-4 RS-232 3-4
eds file interpret 7-14 error device state conflict 14-4, 15-13 error codes See status codes EtherNet/IP brigde options 1-6 configure driver 3-4 explicit client tags configure 9-19 explicit server tags access from controller 9-16 configure 9-15 plan 9-13
Flex I/O on DeviceNet 14-1 scanner memory requirements 14-2 foreground to background poll ratio 11-3
generate report 2-16, 6-17
I/O data define for device 11-6 map specific value A-1 I/O memory advanced mapping A-1 assign devices 2-14, 6-15 assign slave mode data 8-4 assign slave scanner 8-5 autoscan 4-12 data alignment 2-11, 6-12 estimate 1-11
estimate for Flex I/O 14-2 estimate for Point I/O 15-3 limits 1-11 I/O parameters configure 11-6 options 11-3 overview 11-3 select for device 11-1 interlock set up 8-1 use 8-1 interscan delay configure 11-6 examples 11-2 overview 11-4
network add devices to diagram 2-4 configuration file 2-3, 6-3 download configuration 2-17 go online 6-5 interscan delay 11-4 run 7-12 status information 12-13 tune 11-1 upload configuration 6-16 node See address node commissioning tool install 4-2 set address or baud rate 5-3
LEDs 1734 I/O module 15-14 1734-ADN 15-14 1734-ADNX 15-14 1734D 15-17 1734-PDN 15-13 1756-DNB 12-3 1769-SDN 12-1 1784-PCIDS 12-11 1788-CN2DN 12-5 1788-DNBO 12-7 1788-EN2DN 12-8 1794-ADN 14-5 logic detect failed device
online go 6-5 OPC access parameter 10-1
PanelView terminal add to scan list 9-9 address data 9-11 configure communication 9-7 configure explicit client tags 9-19 configure explicit server tags 9-15 configure I/O slave tags 9-4 explicit client overview 9-3 explicit server overview 9-3 plan explicit server tags 9-13 select communication method 9-2 send message 9-19 send message to 9-16 parameter determine class, instance, attribute numbers 7-14 path define for message 7-19 performance adjust 11-1 Point I/O on DeviceNet 15-2 scanner memory requirements 15-3 select adapter 15-2 PointBlock I/O as DeviceNet adapter 15-2 LEDs 15-17
map advanced mapping A-1 device to memory 2-14, 6-15 message configure 7-16 path 7-19 send from PanelView terminal 9-19 send to PanelView terminal 9-16 use 7-13 mode scanner 7-12 MSG instruction See message multicast input data set up 8-5 use 8-1
set address 15-6 poll change poll ratio 11-6 configure 11-8 overview 11-3 rate 11-3 ratio 11-3
report generate 2-16, 6-17 RS-232 bridge options 1-6 configure driver 3-4 RSView software access device 10-1
scan cycle examples 11-2 factors of performance 11-2 interscan delay 11-2, 11-4 scan list add shared input 8-6 add slave scanner 8-4 automap on add check box 2-12, 6-13 build 2-13, 6-14 build automatically 2-12, 6-13 I/O parameters 11-1, 11-3 overview 2-8, 6-9 set I/O parameters 11-6 scanner add PanelView terminal 9-9 add to project 7-5 adjust the status size 7-3 advanced mapping A-1 change interscan delay 11-6 change mode 7-12 change poll ratio 11-6 configure ADR 13-3 configure automatically 4-1 configure I/O parameters for device