Devicenet Network Configuration: User Manual
Devicenet Network Configuration: User Manual
Configuration
1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix,
1769 Compact GuardLogix, 1789 SoftLogix, Studio 5000
Logix Emulate
Publication DNET-UM004D-EN-P
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss.
Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.
IMPORTANT Identifies information that is critical for successful application and understanding of the product.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash
will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and
for Personal Protective Equipment (PPE).
Grammatical and editorial style changes are not included in this summary.
Global changes
This table identifies changes that apply to all information about a subject in
the manual and the reason for the change. For example, the addition of new
supported hardware, a software design change, or additional reference
material would result in changes to all of the topics that deal with that subject.
Subject Reason
Updated the Legal notices. Legal information changed.
Chapter 1
DeviceNet Overview Choose a Single Network or Subnets ....................................................... 15
Single Network ..................................................................................... 15
Advantages to Using a Single Network ........................................ 15
Disadvantages to Using a Single Network................................... 16
Subnets ................................................................................................. 16
Advantages to Using Subnets ....................................................... 16
Disadvantages to Using Subnets .................................................. 16
Choose a Scanner ....................................................................................... 16
Bridge Across Networks............................................................................. 17
Choose a Baud Rate for the Network ........................................................ 19
Assign an Address to Each Device............................................................ 20
Required Software...................................................................................... 21
Chapter 2
Connect a Computer to the Connection Options ..................................................................................23
DeviceNet Network Set Up the DeviceNet Driver .................................................................... 24
Obtain the Driver for the Interface Device ....................................... 24
Verify that the Driver Works .............................................................. 24
Chapter 3
Connect Devices to the Network Before You Begin....................................................................................... 27
Set the Node Address of a Device ............................................................ 27
Set Node Address via Hardware Mechanism ................................... 28
Set Node Address via Software .......................................................... 29
Set Node Address via DeviceNet Node Commissioning Tool ......... 30
Make Sure Your Devices Are on Your Network........................................32
Chapter 4
Configure the Network Offline Before You Begin........................................................................................ 33
Create a File for the Network .................................................................... 33
Create Your Network in RSNetWorx for DeviceNet Software ............... 34
Configure Each Device............................................................................... 35
Specify a Device Node Address ...........................................................36
Change a Device Node Address .................................................... 37
Chapter 5
Configure the Network Online Before You Begin........................................................................................ 51
Verify Communication Between the Computer and Devices ............... 52
Create a New File for the Network ............................................................ 53
Go Online to Your Network .......................................................................54
Configure Each Device...............................................................................56
Upload the Configuration of a Device ................................................56
Change and Download Device Configuration ...................................56
Configure the Scanner ............................................................................... 57
Upload the Current Scanner Configuration ..................................... 58
Define the Scanner Properties ............................................................59
Build the Scan List............................................................................... 60
Set the Alignment Option ................................................................... 62
SoftLogix 5800 Controller .............................................................63
Manually Assign Each Device to a Memory Location........................63
Download the Configuration to the Scanner.....................................65
Upload and Save the Configuration File...................................................65
Generate an RSNetWorx for DeviceNet Report ..................................... 66
Chapter 6
Automatically Configure a How AutoScan Operates .......................................................................... 69
DeviceNet Network Determine If You Can Use AutoScan ....................................................... 71
How AutoScan Affects Your Network ..................................................... 72
Install the DeviceNet Node Commissioning Tool ................................... 73
Connect Devices ......................................................................................... 73
Install a Scanner or Network Interface Devices ................................ 73
Install Other DeviceNet Devices .........................................................74
Set the Node Address and Baud Rate with the DeviceNet Node
Commissioning Tool............................................................................ 75
Add the Scanner to the RSLogix 5000 Project.......................................... 75
Add the Scanner to the I/O Configuration Folder ............................. 75
Chapter 7
Control a Device Before You Begin....................................................................................... 87
RSNetWorx Report for the Network ................................................. 88
Data Map for Each of Your Devices ................................................... 89
Add the Scanner to the Controller’s I/O Configuration ......................... 89
Conserve EtherNet/IP or ControlNet Network Bandwidth ............ 89
Add the Scanner to the I/O Configuration Folder ............................ 90
Configure the Scanner ......................................................................... 91
Determine the Address of DeviceNet Data ............................................. 92
SoftLogix 5800 Controller .................................................................. 94
Determine If a Device Has Failed .............................................................95
Place the Scanner in Run Mode................................................................ 96
When to Use an MSG Instruction ............................................................ 96
Determine the Parameter Number to Access ..........................................97
Determine the Configuration of the Parameter ......................................97
Test the Parameter .................................................................................... 98
Enter Message Logic ................................................................................. 99
Define the Source or Destination Data ............................................ 101
Enter and Configure the MSG Instruction ......................................102
Set the Communication Path ............................................................ 103
Chapter 8
Interlock and Share Inputs Interlock ................................................................................................... 105
Choose a Master Controller ............................................................... 106
Determine How Much Data to Exchange ........................................ 106
Enable Slave Mode for the Slave Scanner ........................................ 106
Map the Slave Mode Data .................................................................. 107
Chapter 9
Communicate with a PanelView Choose Data Types .................................................................................... 111
Standard Terminal Choose a Communication Method......................................................... 112
I/O Slave Communication ................................................................. 112
Explicit Server Communication ........................................................113
Explicit Client Communication .........................................................113
Plan and Configure I/O Slave Tags ..........................................................113
Use a Word/Bit Format for Each Tag ............................................... 114
For Integers, Skip Every Other Word ............................................... 115
Configure an I/O Slave Tag ............................................................... 115
Set Up the Terminal on Your Network ................................................... 116
Set the Protocol .................................................................................. 116
Set the Node Address and I/O Sizes ..................................................117
Configure the Scanner to Update I/O Slave Tags .................................. 118
Add the Terminal to the Scan List ..................................................... 118
Edit I/O Parameters ........................................................................... 119
Map Input and Output Data .............................................................120
Address I/O Slave Tags in the RSLogix 5000 Programming Software
Project .......................................................................................................120
SoftLogix 5800 Controller ................................................................. 122
Plan and Configure Explicit Server Tags ................................................ 122
Assign Assembly Instances................................................................ 123
For Integers, Skip Every Other Word ............................................... 124
Configure an Explicit Server Tag ...................................................... 124
Program the Controller to Get/Set Explicit Server Tags ....................... 125
Create an Array for the Assembly Instance ...................................... 125
Enter and Configure the MSG Instruction ...................................... 126
Set the Communication Path ............................................................ 127
Configure Explicit Client Tags ................................................................ 128
Determine the Parameter Number to Access .................................. 128
Determine the Configuration of the Parameter .............................. 129
Configure an Explicit Client Tag ...................................................... 129
Chapter 10
Communicate with a Before You Begin...................................................................................... 132
FactoryTalk View Project Create a Topic for the Device .................................................................. 132
Create a Node ........................................................................................... 133
Create a Tag for the Parameter ............................................................... 134
Chapter 11
Tune the Performance of a Factors that Affect Performance ............................................................. 137
DeviceNet Network I/O Parameters of Each Device ......................................................... 139
Background Poll ................................................................................. 139
Interscan Delay .................................................................................. 140
Change the Configuration of Your Network .......................................... 141
Upload the Current Configuration of the Scanner ......................... 141
Set the Interscan Delay and Poll Ratio ............................................. 142
Set the I/O Parameters of a Device ................................................... 143
Change of State or Cyclic Transfer ............................................. 143
Strobed Transfer .......................................................................... 144
Polled Transfer ............................................................................. 144
Download the Configuration to the Scanner................................... 145
Save the Configuration File ............................................................... 145
Chapter 12
Automate the Replacement of a Automatic Device Recovery..................................................................... 147
Failed Device Set Up Automatic Device Recovery ........................................................ 148
Choose an Electronic Key Level for a Device.................................... 148
Update Your Network Configuration File ........................................ 149
Define the Electronic Key .................................................................. 149
Enable Auto-Address Recovery for the Scanner .............................. 150
Set the ADR Settings for the Device ................................................. 151
Download the Changes to the Scanner ............................................ 151
Upload and Save the Configuration File .......................................... 152
Appendix A
Map the Memory Location with Give a Value Its Own Memory Location ................................................. 153
Advanced Mapping
You should use this manual if you program applications that use DeviceNet
with one of these Logix5000 controllers:
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.
Studio 5000 environment The Studio 5000 Automation Engineering & Design Environment® combines
engineering and design elements into a common environment. The first
element is the Studio 5000 Logix Designer® application. The Logix Designer
application is the rebranding of RSLogix 5000® software and will continue to
be the product to program Logix 5000™ controllers for discrete, process,
batch, motion, safety, and drive-based solutions.
Additional Resources For more information on the products included in this publication, use the
publications listed in this table.
Resource Description
DeviceNet Modules Installation Instructions, Describes how to install and set up 1756-DNB, 1769-
publication DNET-IN001 ADN, and 1769-SDN DeviceNet modules.
DeviceNet Media Design Installation Guide, Describes how to design, install, and troubleshoot a
publication DNET-UM072 DeviceNet cable system.
Logix5000 Controllers Common Procedures Links to a collection of programming manuals that
Programming Manual, publication 1756-PM001M describe how you can use procedures that are
common to all Logix5000 controller projects.
Legal Notices Rockwell Automation publishes legal notices, such as privacy policies, license
agreements, trademark disclosures, and other terms and conditions on the
Legal Notices page of the Rockwell Automation website.
A full list of all open source software used in this product and their
corresponding licenses can be found in the OPENSOURCE folder. The default
installed location of these licenses is C:\Program Files (x86)\Common
Files\Rockwell\Help\FactoryTalk Services Platform\Release
Notes\OPENSOURCE\index.htm.
DeviceNet Overview
Topic Page
Choose a Single Network or Subnets 14 on page 15
Choose a Scanner on page 16 16 on page 16
Bridge Across Networks on page 17 16 on page 17
Choose a Baud Rate for the Network on page 19 19 on page 19
Calculate Scanner Memory Requirements 20
Assign an Address to Each Device on page 20 23 on page 20
Single Network When you use a single network, you place all your devices on a single
DeviceNet network and connect the controller directly to the network via a
scanner. The following graphic shows a single network.
Advantages to Using a There are advantages to using a single network for your DeviceNet
application:
Single Network
• The overall cost to install the network is lower than using subnets.
• You need to manage only a single network.
• The Logix5000 controller is local to the DeviceNet scanner. For
example, with a single network in a ControlLogix application, the 1756-
L64 controller is in the same ControlLogix chassis as the 1756-DNB
scanner.
Disadvantages to Using a There are disadvantages to using a single network for your DeviceNet
application:
Single Network
• The network must use shorter distances from one end to another.
• The more devices on the network, the slower the overall performance
of the network.
• Your network may have more power supply requirements than can be
handled by one network
• A single network can contain only up to 64 nodes
Subnets A subnet configuration is a main network that is connected to distributed
subnets using a scanner, or linking device. In this option, you must install a
ControlNet network or EtherNet/IP network, also known as a backbone, that
connects to distributed subnets using a linking device.
For example, if you choose an EtherNet/IP network backbone, you must use
1788-EN2DN linking devices to connect the subnets.
Advantages to Using There are advantages to using subnets for your DeviceNet application:
Subnets • Typically, there are shorter runs on subnets, which allow a faster
communication rate for the DeviceNet network.
• With fewer devices on each subnet, the overall performance of the
network is faster.
• There are simpler power requirements.
Disadvantages to Using There are disadvantages to using subnets for your DeviceNet application:
Subnets • 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.
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 following table describes how communication can bridge the networks.
Bridging Across Networks
In this example, the RSLinx communication software window shows how the
DeviceNet bridge links to the EtherNet/IP network.
Choose a Baud Rate for the You must choose a baud rate for the DeviceNet network. There are three rates
available for the network:
Network
• 125 kbps—This is the default baud rate for a DeviceNet network. It is
the easiest baud rate to use and is usually sufficient.
• 250 kbps
• 500 kbps
The following table describes the most common methods to set a baud rate.
Method Description
Autobaud feature At powerup, the device automatically sets its baud rate to the baud rate of the first device it hears on the network. The baud rate
remains set until the device powers up again.
The network requires at least one device with a fixed baud rate so the autobaud devices have something against which to set.
Typically, scanners and network interfaces have a fixed baud rate.
The length of the trunkline and type of cable determines which baud rates you
can use.
If you change the baud rate of the network, make sure that all devices change
to the new baud rate. Mixed baud rates produce communication errors.
Complete the following steps to set the baud rate for the network.
1. Connect the network interface to the network and set its baud rate.
2. Connect the scanner to the network and set its baud rate.
3. For each device that has only fixed baud rates (no autobaud), set the
baud rate and connect it to the network.
4. Connect the remaining devices to the network and enable autobaud
for each of them.
If a device Then
has a switch to enable autobaud 1. Set the switch to autobaud.
2. Connect the device to the network.
does not have a switch to enable autobaud 1. Connect the device to the network.
2. Use RSNetWorx for DeviceNet software to enable autobaud.
Assign an Address to Each To communicate on the DeviceNet network, each device requires its own
address. In general, a device can use any address in the range of 0…63.
Device However, we recommend that you follow the guidelines in the following table.
Required Software You must use the correct software with the DeviceNet application.
This chapter shows how to connect a computer to the network. After you
physically connect a computer to the network, you must configure a driver in
RSLinx communication software to communicate over the network.
Topic Page
Connection Options on page 23 26 on page 23
Set Up the DeviceNet Driver on page 24 27 on page 24
After you connect a computer to the network and configure a driver in RSLinx
communication software, you can complete these tasks:
• Configure the devices on the network
• Configure network parameters
• Upload, download, monitor, and program projects for Logix5000
controllers
Some networks let you bridge to other networks in your system. This lets you
connect to one network and access devices or controllers on other networks.
Set Up the DeviceNet Driver The requirements for setting up the DeviceNet driver depend on your version
of RSLinx Classic software.
Obtain the Driver for the Follow these steps to download and install the device driver for the 1784-
U2DN interface device.
Interface Device
1. Visit http://www.rockwellautomation.com/knowledgebase/.
2. Open tech note ID 53280 and follow the instructions to install the
driver.
Verify that the Driver Works Complete the following steps to verify that the driver for the 1784-U2DN
interface device works.
This chapter describes how to connect a device to the network and set the
device’s address so it can communicate on the DeviceNet network.
Before You Begin Before you use this chapter, make sure that you can see all your devices on the
DeviceNet network. Complete the following steps to see your DeviceNet
network.
Set the Node Address of a You can use the following options to set the node address of DeviceNet
devices. However, not all options apply to every DeviceNet device.
Device
For example, you can use all three options with the 1756-DNB ControlLogix
DeviceNet scanner, but you can use only the second and third methods with
the 1769-SDN Compact I/O DeviceNet scanner.
For more information about setting the node address of DeviceNet devices,
refer to the Rockwell Automation Literature Library at:
http://www.rockwellautomation.com/literature/.
Set Node Address via Many DeviceNet devices have a hardware mechanism that you can use to set
the node address. If a device has a hardware mechanism to set the node
Hardware Mechanism address, use that mechanism.
The following table describes the two most common hardware mechanisms.
IMPORTANT As long as a device’s hardware mechanism sets the node address to 63 or lower, you
cannot change the node address with RSNetWorx for DeviceNet software or the
DeviceNet node commissioning tool.
Make sure each device’s node address set by a hardware mechanism matches the
node address used in your RSNetWorx for DeviceNet software network configuration
file, as described on page 40 on page 36.
However, if you set a device’s hardware mechanism to a number higher than 63, you
can use RSNetWorx for DeviceNet software or the DeviceNet node commissioning tool
to set the node address.
IMPORTANT You must cycle power to the module for node changes set through hardware to take
effect.
Set Node Address via You can set a device’s node address in RSNetWorx for DeviceNet software.
Software IMPORTANT Setting a device’s node address is only one task used when configuring a device with
RSNetWorx for DeviceNet software.
For complete information on how to configure all parameters with RSNetWorx for
DeviceNet software, including setting a device’s node address, refer to Chapter 4 on
page 37.
Complete the following steps to set a device’s node address in your network
configuration file. This example uses an AC drive.
IMPORTANT The node address assigned by RSNetWorx for DeviceNet software only takes effect if
the device does not have a hardware mechanism to set the node address or if the
device has its hardware mechanism set to a number higher than 63.
Set Node Address via You can use the DeviceNet node commissioning tool available in RSNetWorx
for DeviceNet software to set the node addresses of devices on the DeviceNet
DeviceNet Node network. Remember the following when you decide to use the DeviceNet
Commissioning Tool node commissioning tool.
• You can only use this tool with a DeviceNet network that is online.
• You should complete the tasks described in this section each time a
new device is added to the network.
• If you add more than one device to the online network before using the
DeviceNet node commissioning tool, you will experience duplicate
node address conflicts on the network because all new devices initially
use node address 63.
• Keep track of the node addresses you set with the DeviceNet node
commissioning tool and verify they match the device’s configuration
in the RSNetWorx for DeviceNet software configuration file.
Complete the following steps to use the DeviceNet node commissioning tool
to set a device’s node address. This example uses the 1769-SDN Compact I/O
DeviceNet Scanner module.
5. On the Device Selection dialog box, check the ‘I want to input the
address for the device on the selected network’ box.
6. Browse to the DeviceNet network.
7. Type the current address for the device. Out of the box, devices use
address 63.
9. When you return to the Node Commissioning dialog box, enter the
new address for the device.
10. Click Apply.
11. Look for confirmation.
12. If you need to use the DeviceNet node commissioning tool to set
another device’s node address, return to step on page 34 and repeat
the process.
Make Sure Your Devices Are Once you have assigned a node address to each device, make sure that the
on Your Network devices are communicating on the network. Complete these steps to make
sure your devices are on the network.
This chapter describes how to configure the network offline with RSNetWorx
for DeviceNet software.
Topic Page
Before You Begin on page 51 38 on page 51
Create a File for the Network on page 33 38 on page 33
Create Your Network in RSNetWorx for DeviceNet Software on page 34 39 on page 34
Configure Each Device on page 35 40 on page 35
Configure the Scanner on page 39 44 on page 39
Save the Configuration File on page 45 51 on page 45
Generate an RSNetWorx for DeviceNet Report on page 45 51 on page 45
Download Configuration to Your Network on page 49 55 on page 49
Before You Begin Before you configure the DeviceNet network, make sure you have a list of the
devices that you put on the DeviceNet network and, at minimum, the address
for each. The following table shows an example list of devices.
Device Address Input Size of Device Input Memory in Output Size of Device Output Memory in
(Bytes) Scanner (DINTs) (Bytes) Scanner (DINTs)
scanner 0 n/a n/a n/a n/a
PanelView terminal 3 128 32 128 32
<empty> 2 2
I/O adapter w/ modules 5 9 3 5 2
<empty> 2 2
drive 7 4 1 4 1
<empty> 2 2
photoeye 9 1 1 0 0
computer interface 62 n/a n/a n/a n/a
63
Total 43 41
Create a File for the Complete the following steps to create a DeviceNet configuration file.
4. Click OK.
5. Save the file.
Make sure you give the file a name that identifies this specific
DeviceNet network.
Create Your Network in Before you configure a DeviceNet communication module in RSNetWorx for
RSNetWorx for DeviceNet DeviceNet software, you must add it to the network configuration file.
Software The finished picture should match the collection of devices that are or will be
physically connected to the DeviceNet network. If the network configuration
file you create offline does not match the physical collection of devices on the
network, you may experience issues when you go online with your project.
Complete the following steps to add each device to network configuration file.
If the hardware list does not show a device, then RSNetWorx for DeviceNet
software requires the EDS file for the device.
To add an EDS file, follow these steps.
Configure Each Device After adding devices to the network configuration file, as described in
Create Your Network in RSNetWorx for DeviceNet Software on page 39 on
page 34, you configure parameters for each device to define the modules’
behavior.
• The node addresses that are automatically assigned as you add devices
to the configuration file do not take effect when the project is offline.
• For devices that do not have hardware mechanisms, the node number
assigned in the network configuration file takes effect when you
download the project to the DeviceNet network, as described on page
55 on page 49.
Change a Device Node You may need to assign a device’s node address that is different from the
Address number automatically assigned when the device is added to the configuration
file. Complete the following steps to assign a device a specific node address.
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 Complete the following steps to configure the scanner.
Set the Alignment Option Choose a data 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.
IMPORTANT The alignment option you choose applies to both the input and output maps.
SoftLogix 5800 Controller The SoftLogix 5800 scanner 1784-PCIDS organizes its input and output
memory in 16-bit words. For that scanner, click the Word Align option.
Manually Assign Each You can manually assign locations for device data.
Device to a Memory IMPORTANT If you configured the software to automatically assign memory locations as devices
are added, as described on page 45, skip this section.
Location 1. Click the Input tab.
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], enter 3 in the
Start DWord box.
4. Click Automap.
An entry for the device appears in the input array.
Save the Configuration File After you make a change to the network, upload the entire network and save
the file. This makes sure that the offline configuration file matches the
network.
Complete these steps to save the configuration file.
Go Online to Your Network When you go online, RSNetWorx for DeviceNet software browses the
network once and shows the devices currently on the network in the new
network configuration file.
Download Configuration to After you go online with the network configuration file you created while
offline, you can download the configuration to the network.
Your Network
IMPORTANT Before you download configuration to the network, make sure the scanner is in Idle
mode. To put the scanner in Idle mode, do one of the following:
• Place the controller in program/remote program mode.
• Turn off the …O.CommandRegister.Run bit of the scanner.
This chapter explains how to configure the network online with RSNetWorx
for DeviceNet software.
Topic Page
Before You Begin on page 51 58 on page 51
Verify Communication Between the Computer and Devices on page 52 58 on page 52
Create a New File for the Network on page 33 60 on page 33
Go Online to Your Network on page 47 60 on page 47
Configure Each Device on page 35 63 on page 35
Configure the Scanner on page 39 66 on page 39
Upload and Save the Configuration File on page 65 76 on page 65
Generate an RSNetWorx for DeviceNet Report on page 45 77 on page 45
Total 43 41
Verify Communication
Between the Computer and To configure your network online, your computer must be able to
communicate with each device on the DeviceNet network. Use RSLinx
Devices communication software to verify that you can communicate with all the
devices.
IMPORTANT If you cannot view the network, verify that your computer is connected to the
network. Refer to Chapter 2 on page 25 for more information on how to connect the
computer to the network.
If you can view the network but cannot see all the devices that should be on the
network, verify the devices are connected to the network. Refer to Chapter 3 on page
29 for more information on how to connect the devices to the network.
Go Online to Your Network When you go online, RSNetWorx for DeviceNet software browses the
network once and shows the devices currently on the network in the new
network configuration file.
Configure Each Device Once the devices on the DeviceNet network appear in the network
configuration file, complete these tasks to change the configuration for
a device:
Upload the Configuration of When you configure the network online, the devices on the network have
a Device parameters configured. Complete the following steps to upload configuration
from a device to the network configuration file.
Change and Download After you upload a device’s configuration to the network configuration file,
you can make changes to the configuration and download it.
Device Configuration
Complete the following steps to change and download new configuration
parameters.
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
You must configure the scanner to define how it communicates with other
devices on the DeviceNet network. When you are configuring the network
online, complete the following tasks to configure the scanner:
Upload the Current Scanner Complete the following steps to upload the current scanner configuration.
Define the Scanner Complete the following steps to change the scanner properties, if necessary.
Build the Scan List A scan list is a list of devices with which the scanner communicates. For each
device in the scanner’s scan list, the scanner sets aside input or output
memory for the data of the device.
Set the Alignment Option 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.
IMPORTANT The alignment option you choose applies to both the input and output maps.
SoftLogix 5800 Controller In SoftLogix 5800 applications, the 1784-PCIDS scanner organizes its input
and output memory in 16-bit words. For that scanner, click Word Align.
Manually Assign Each You can manually assign locations for device data.
Device to a Memory IMPORTANT If you configured the software to automatically assign memory locations as devices
are added, as described on page 70, skip this section.
Location Complete the following steps to manually assign each device to a memory
location.
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.
Download the Configuration Complete these steps to download the configuration to the scanner.
Upload and Save the Complete these steps to upload and save the configuration file.
Generate an RSNetWorx for An RSNetWorx for DeviceNet software report shows these items:
Topic Page
How AutoScan Operates on page 69 80 on page 69
Determine If You Can Use AutoScan on page 71 82 on page 71
How AutoScan Affects Your Network on page 72 83 on page 72
Install the DeviceNet Node Commissioning Tool on page 73 84 on page 73
Connect Devices to the Network on page 73 84 on page 73
Add the Scanner to the RSLogix 5000 Project on page 75 89 on page 75
Enable AutoScan with RSLogix 5000 Software on page 77 91 on page 77
Access Device Data on page 83 99 on page 83
Put the Scanner in Run Mode on page 84 100 on page 84
Additional Information About AutoScan on page 85 101 on page 85
How AutoScan Operates IMPORTANT AutoScan works only with 1756-DNB and 1769-SDN modules in Logix controller
applications.
AutoScan is active when the feature is enabled and the scanner is in Idle
mode. When active, the scanner attempts to connect to each device not
enabled in the scan list. The scanner only checks for devices with node
addresses between 0 and 61, inclusive. The connections to these devices are
made on a round-robin basis.
• If the produced data size is greater than the configured I/O allocation
size, the device is added to the scan list with a produced size set equal
to the I/O allocation size.
When this happens, an I/O connection is made with the device, but an error
occurs and error code #77 appears on the 1769-SDN for the device’s node
number.
• If the consumed data size is greater than the configured I/O allocation
size, then the node is rejected and not entered into the scan list.
However, you can change the I/O allocation size, as described in Configure
I/O Allocation Size Via the User Program on page 80, to accommodate the
device with the largest produced and consumed data sizes in your scan list.
For qualifying nodes, the scanner enters the device into the scan list and
attempts to allocate an I/O connection using one of the following
communication format choices in this particular order:
The input and output data is mapped into the scanner's I/O data table based
on the device's node address and the configured fixed mapping size. The
DINT-based formula that is used with the CompactLogix controller for
calculating the input or output data location is as follows:
Example
When using the default fixed mapping size of 4 bytes, the input data for the devices shown in the example below is allocated in the 1769-
SDN's input table as shown below. Notice node 1 is in the data map at DINT location 1, node 2 at DINT location 2, and so on.
Notice that, in this example, node 4 is unused. However, the I/O memory slot remains allocated for it.
IMPORTANT If you are using a MicroLogix 1500 controller with a 1769-SDN scanner, you must use
the following WORD-based formula for calculating the input or output data location:
Input (Output) Offset = ([(Node Address) x (Allocation Size)] / 2) + Data Offset
In this formula the Data Offset = 66 for Input Offset and 2 for Output Offset.
The data offset value is used to account for scanners that have a fixed status
field at the start of the input or output data, such as the 1769-SDN scanner.
• Your DeviceNet scanner must support the AutoScan feature. For more
information, refer to your firmware release notes.
• Your application uses RSLogix 5000 programming software, version 13
or later.
• The scanner’s I/O allocation size is configured to accommodate the
input and output data sizes of all devices on your DeviceNet network.
The default AutoScan setting allocates a 4-byte entry in both the input and
output memory maps in the scanner for each slave device detected on the
network. This default size is chosen to accommodate the default Logix native
data size of 32 bits, that is a DINT.
How AutoScan Affects Your As you use AutoScan, keep in mind the considerations described in the
following table.
Network
Consideration Description
AutoScan clears the current
With AutoScan, the scanner automatically sets up communication with the devices
configuration.
on your DeviceNet network. When you turn on the AutoScan option, the scanner
removes any previous configuration that was done to the scanner.
Install the DeviceNet Node Use the DeviceNet node commissioning tool to set a device’s node address
and baud rate when that device does not have a hardware mechanism to do
Commissioning Tool so.
You can skip this step if either of the following conditions apply:
• All your devices have hardware mechanisms to set a node address and
baud rate. In this case, you do not need the tool.
• You already have the tool installed.
Follow these steps to install the node commissioning tool.
1. On the RSLogix 5000 software CD, find the following folder where
language is the language of your software:
language\Tools\Node Commissioning Tool
For example, for software in English, open the ENU folder.
2. Follow the instructions in the readmefirst file.
Connect Devices When you use the AutoScan functionality, you should do the following:
• Install and configure the scanner and any network interface devices on
the network first.
• Install other devices on the network once the scanner and network
interface devices are on the network.
Install a Scanner or Complete the following steps to install a scanner or network interface device
Network Interface Devices on the DeviceNet network.
1. Connect the scanner and any network interface devices to the network.
2. Set a node address for the scanner and any network interface devices.
Out of the box, a DeviceNet device is preset for node address 63. To avoid
address conflicts, connect and configure the devices one at a time. Otherwise,
the address conflicts may prevent communication.
• If you set the baud rate on the scanner or network interface device
before you install other devices on the network, you reduce the
number of baud rate errors.
• Scanners and network interface devices use a fixed baud rate.
• 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.
• By first placing a scanner or network interface device on the
network, the other device has a network baud rate against which to
set its baud rate.
• Initially, leave the baud rate of the scanner and network interface at
the default setting of 125KBps. If you want to change the baud rate,
wait until after you establish communication with all your devices at
the default setting (125K).
• Refer to Set the Node Address and Baud Rate with the DeviceNet
Node Commissioning Tool on page 87 on page 75 for more
information.
Install Other DeviceNet Complete the following steps to install other devices on the DeviceNet
Devices network.
1. Connect the rest of your devices to the network one at a time.
2. Set a node address for each device after you add it to the network.
Out of the box, a DeviceNet device is preset for node address 63. To avoid
address conflicts, connect and configure the devices one at a time. Otherwise,
the address conflicts may prevent communication.
Add the Scanner to the To access the data of the network, add the scanner to the I/O configuration of
the controller.
RSLogix 5000 Project
Add the Scanner to the I/O Complete the following steps to add the scanner to the I/O configuration file.
Initiate AutoScan via the To enable AutoScan by using the MSG instruction, use the parameters shown
below and make sure that the message is sent to the appropriate DeviceNet
User Program scanner. The figure shown below is from RSLogix 5000 software. Refer to the
appropriate user manuals to determine how to perform explicit messaging in
other PLC platforms.
Implementing AutoScan To implement this feature, make sure that the appropriate version of
DeviceNet scanner is used. See page 97 on page 82 for the list of compatible
products supporting this feature.
This section describes how to set up the feature and how it operates. Notice
that explicit messaging is used for some of the steps. An explicit message can
be sent on a DeviceNet network in the following ways:
The diagram below shows an example system using the 1756-DNB scanner.
You can commission the node addresses via hardware switches on the devices
or through other DeviceNet configurators, such as the hand-held DeviceNet
Configuration Terminal. For more information on how to set up the
DeviceNet Configuration Terminal’s node address, see the DeviceNet
Configuration Terminal User Manual, publication 193-UM009A-EN-P.
1. Set up I/O allocation size in the scanner.
TIP This step is optional.
The default AutoScan setting allocates a 4-byte entry in both the input and
output memory maps in the scanner for each slave device detected on the
network. This default size is chosen to accommodate the default Logix native
data size of 32 bits (DINT). If that is adequate for the application, go to step 3.
For applications where you want to customize the I/O allocation size, the 4-
byte allocation can be adjusted through an explicit message to the scanner
Configure I/O Allocation Use the parameters shown in the Message Configuration dialog box below to
Size Via the User Program adjust the I/O allocation size. Make sure that the message is sent to the
appropriate DeviceNet scanner.
Configure I/O Allocation Via Rockwell Automation offers the hand-held DeviceNet Configuration
a DeviceView Configurator Terminal, catalog number 193-DNCT, to configure individual devices on a
DeviceNet network.
1. Enable AutoScan.
This is accomplished by executing an explicit message to the scanner by using
the SetAttributeSingle service. As mentioned before, there are multiple ways
to send an explicit message on DeviceNet, including the following:
Initiate AutoScan via the To enable AutoScan by using the MSG instruction, use the parameters shown
User Program below and make sure that the message is sent to the appropriate DeviceNet
scanner. The figure shown below is from RSLogix 5000 software. Refer to the
appropriate user manuals to determine how to perform explicit messaging in
other PLC platforms.
Initiate AutoScan via the To enable AutoScan by using a DeviceNet configurator, attach the device on
DeviceView Configurator the network and send an explicit message to the scanner using the
parameters below. Send a 1 to that attribute to enable the feature, and 0 to
disable.
Field Value
Service Code 10 Hex
Class 90 Hex
Instance 1
Attribute 11 Hex
Once the feature is enabled, the scanner scans the network to populate and
configure the scan list automatically.
Example
If the I/O allocation size per node is configured for 16 bytes and there are 32 slave
devices on the network (node addresses 1…32), AutoScan requires 16 bytes x 32 = 512
bytes (128 DINT) of I/O space in both the scanner's input and output table. Assuming it
is a ControlLogix system, the maximum scanner input data table size is 124 DINT and
123 DINT for output. The required space exceeds what the 1756-DNB can support. You
would need to adjust the I/O allocation size or reduce the slave device count on the
network to include all of the devices in the scan list.
Safety
ATTENTION: Devices outside of the scanner's allowable I/O image space will be rejected
and will not be included in the scan list.
One new status code has been added to the Node Status list. This code is
presented in the Node Status Table.
When the scanner is in Run mode with AutoScan enabled, the scanner display
alternates between 65 and the scanner node address.
The AutoScan feature enables AAR (Auto-Address Recovery) for each of the
configured slave devices.
The AutoScan feature checks for the Quick Connect setting in each slave
device and enables Quick Connect in the scanner if it is enabled in the slave
devices.
= Optional
Where Is
location
location of the scanner in the system
If you have this scanner In a Then location is
ControlLogix 1756-DNB local chassis Local:slot_number_of_scanner
bit
specific bit within the data of the
device
While you can use the input and output tags of the scanner directly in your
logic, it is a lot easier to use alias tags. Alias tags can be used whether you use
AutoScan or not to configure the scanner.
2. Set the following bit of the output structure for the scanner.
Additional Information The type of update (connection) that the scanner sets up with each device
depends on the device. The scanner chooses the first connection type that the
About AutoScan device supports in this order:
Allocating More Memory for The AutoScan feature is easiest to use if you leave it set to 1 DINT (4 bytes) of
input memory and output memory for each address.
Each Device
Number of bytes of
input memory and
output memory to
allocate in for each
address
Consideration
Description
The scanner sets-up communication with any device The scanner automatically sets up communication with those devices that fit within the memory allocated
that fits within the allocated memory size. 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 1…8 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.
Control a Device
Use this chapter to develop the logic that examines and controls your devices.
Topic Page
Before You Begin on page 27 104 on page 27
Determine the Address of DeviceNet Data on page 92 109 on page 92
Determine If a Device Has Failed on page 95 112 on page 95
Place the Scanner in Run Mode on page 96 113 on page 96
When to Use a MSG Instruction on page 96 113 on page 96
Determine the Parameter Number to Access on page 97 114 on page 97
Determine the Configuration of the Parameter on page 97 114 on page 97
Test the Parameter on page 98 116 on page 98
Enter Message Logic on page 99 117 on page 99
Before You Begin Before you use this chapter, make sure that you can see all your devices on the
DeviceNet network. Complete the following steps to see your DeviceNet
network.
1. Start RSLinx communication software.
2. Browse the network.
3. Expand a driver that lets you access the DeviceNet network.
4. Select the DeviceNet network.
Conserve EtherNet/IP or The default configuration of the scanner gives you the maximum amount of
input, output, and status data, as shown in the following graphic.
ControlNet Network
Bandwidth
• 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.
Example If you want to use only the ASCII representation of scanner status/display,
set the status size to 10.
If you also want to read the status code of the scanner, set the
status size to 11.
Add the Scanner to the I/O Complete the following steps to add the scanner to the I/O configuration file.
Configure the Scanner Complete the following steps to configure the scanner.
The scanner memory uses this format... which is this tag in the controller.
slot type .Data [element] .bit location :type .Data [element] .bit
= Optional
Where Is
Slot
The slot number of the scanner
CompactLogix 1769-SDN
Local:slot_number_of_scanner
Output to a device
O
Element
A specific DINT (DWord, 32-bit integer) within the array
Bit
A specific bit within an integer
Complete the following steps to determine the tag name, or address, for
DeviceNet data.
SoftLogix 5800 Controller The SoftLogix 5800 scanner 1784-PCIDS organizes input and output memory
in 16-bit words. It uses address format word.bit.
Word
INT (16-bit integer) with the memory of the
scanner
Bit
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.
2 Addresses 0 to 7
3 Address 0
4 Address 1
5 Addresses 8 to 15
Use the PhotoEye tag in the rest of your logic (not PhotoEye_RawData).
1. Set the following bit of the output structure for the scanner.
When to Use an MSG If you want to set or get a parameter based on conditions in your logic, use a
Instruction Message (MSG) instruction in ladder logic to access the parameter.
Determine the Parameter Use RSNetWorx for DeviceNet software to determine the parameter number
that you want to access. Some parameters are read-only and are shown with a
Number to Access lock symbol.
Determine the Find the information about the parameters listed in the following table to get
or set a parameter.
Configuration of the
Parameter
Item Value
Class # (hex)
Instance # (hex)
Attribute # (hex)
In addition to the documentation for the device, the EDS file may also give
you the required information.
You must complete the following tasks to configure the MSG instruction:
• Define the Source or Destination Data on page 101
• Enter and Configure the MSG Instruction on page 102
• Set the Communication Path on page 103
• Scope—Controller.
• Data type—MESSAGE.
The tag cannot be part of an array or a user-
defined data type.
• 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.
• 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.
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.
e. From the Source Element pull-down menu, choose the array that
has the data.
f. In the Source Length field, enter the number of bytes that you
have addressed in the PanelView instance (words x 2).
h. In the Instance field, type the assembly instance of the data in the
PanelView terminal. Convert it to hexadecimal format.
m. In the Instance field, type the assembly instance of the data in the
PanelView terminal. Convert it to hexadecimal format.
Set the Communication The communication path specifies the route to the PanelView terminal. A
Path communication path uses the following format:
scanner_name,2,device_address
The chapter describes how to interlock and share inputs over a DeviceNet
network.
Topic Page
Interlock on page 105 125 on page 105
Share Inputs on page 109 130 on page 109
Interlock
To set up an interlock between two controllers over a DeviceNet network,
complete the following tasks:
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.
Determine How Much Data Before you configure the scanners for the interlock, determine how much
data you want to exchange between the controllers.
to Exchange
Enable Slave Mode for the Complete the following steps to enable Slave mode.
Slave Scanner 1. In RSNetWorx for DeviceNet software, double-click the slave scanner
to open its properties.
2. Click the Module tab.
3. Click Slave Mode.
4. Check the Enable Slave Mode check box.
Map the Slave Mode Data Complete the following steps to map Slave mode data.
1. Map the Slave mode data to the input memory of the slave scanner.
This is the data that the scanner (controller) gets from the master.
Add the Slave to the Master Complete the following steps to add the slave to the master’s scan list.
Scanner’s Scan List 1. In RSNetWorx for DeviceNet software, double-click the master
scanner to open its properties.
2. Add the slave to the scan list.
Map the Data of the Slave Complete the following steps to map the data.
1. Map the slave scanner to the input memory of the master scanner. This
is the data that the scanner (controller) gets from the slave.
2. Repeat for the data that the master scanner (controller) sends to the
slave.
Place Both Scanners In Run To exchange data, place both scanners in Run mode. Refer to Place the
Scanner in Run Mode on page 113 on page 96 for more information on placing
Mode both scanners in Run mode.
Share Inputs To let multiple scanners (controllers) consume input data from the same
input device, complete the tasks in this section.
Add the Input to the First Establish communication between the input and one of the scanners. Use one
of the following sections to establish communication:
Scanner
• Configure the Network Offline on page 33 on page 37 on page 33
• Configure the Network Online on page 33 on page 57 on page 33
Add the Input to the Second Complete the following steps to add the input to the second scanner.
Scanner 1. In RSNetWorx for DeviceNet software, display the scan list for the
second scanner.
2. In the Available Devices list, right-click and choose Shared Inputs.
Topic Page
Choose Data Types on page 111 131 on page 111
Choose a Communication Method on page 112 132 on page 112
Plan and Configure I/O Slave Tags on page 113 134 on page 113
Set Up the Terminal on Your Network on page 116 136 on page 116
Configure the Scanner to Update I/O Slave Tags on page 118 138 on page 118
Address I/O Slave Tags in the RSLogix 5000 Programming Software Project on page 141 on page 120
120
Plan and Configure Explicit Server Tags on page 122 143 on page 122
Program the Controller to Get/Set Explicit Server Tags on page 125 146 on page 125
Configure Explicit Client Tags on page 128 150 on page 128
If the object on the PanelView screen reads or Then use this data type Which uses this many bits in the PanelView
writes terminal
Single bit Bit 1
Integer Unsigned integer 16
Data types, such as signed integer and float, also work with Logix5000
controllers. However, they require additional configuration and
programming.
Choose a Communication
Method You have three options to send data to and from a PanelView terminal.
Use the PanelView terminal to get or set a parameter Explicit client • Does not use the controller or scanner.
of a device on your DeviceNet network (not a • Lower priority on the network than I/O slave updates.
controller)
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…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.
Explicit Client
Communication
Explicit Client
PanelView terminal sets or gets data in another
device on a tag-by-tag basis.
Use a Word/Bit Format for Each I/O slave tag requires a specific address in the corresponding assembly
instance. A tag address uses the following format:
Each Tag
Type :Word /Bit
= Optional
Where
Is
Type
Type of tag
If the tag is a Then use
Write tag (sends input data to the controller) I
Read tag (gets output data from the controller) O
Word
Specific 16-bit word within the assembly
Bit
Specific bit within Word (0…15)
For Integers, Skip Every Logix5000 controllers use 32-bit integers (DINTs). Complete the following
steps to lay out your PanelView tags in a method that makes programming
Other Word easier.
Word
0 15 0
…
1 15 0
…
2 15 0
…
3 15 0
…
Configure an I/O Slave Tag Complete the following steps to configure an I/O slave tag.
Set the Protocol Complete the following steps to set the protocol.
Set the Node Address and Complete the following steps to set the node address and I/O sizes.
Add the Terminal to the Complete the following steps to add the terminal to the scanlist.
Scan List 1. Click the Scanlist tab.
2. Clear Automap on Add.
3. Add the terminal to the scanlist.
Edit I/O Parameters Complete the following steps to edit I/O parameters.
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 You must get the following information to find the data for an I/O slave tag in
your RSLogix 5000 programming software project:
the RSLogix 5000
• RSNetWorx for DeviceNet report for the network
Programming Software • Address for the tag in the PanelView terminal
Project 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.
Where
Is
Location
Location of the scanner in the system
If you have this scanner
Then location is
Bit
A specific bit within an integer
SoftLogix 5800 Controller The SoftLogix 5800 scanner 1784-PCIDS organizes input and output memory
in 16-bit words. It uses the following address format.
word.bit
Where
Is
Word
INT (16-bit integer) with the memory of the
scanner
Bit
A specific bit within an integer
Plan and Configure Explicit 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
Server Tags the input and output maps of the scanner.
Instance Number Input (Write) or Output (Read) Instance Number Input (Write) or Output (Read)
1 input 9
2 output 10
3 11
4 12
5 13
6 14
7 15
8 16
For Integers, Skip Every Logix5000 controllers use 32-bit integers (DINTs). Complete the following
steps to lay out your PanelView tags in a method that makes programming
Other Word 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
0 15 0
…
1 15 0
…
2 15 0
…
3 15 0
…
Configure an Explicit Server Complete the following steps to configure an Explicit-Server tag.
Program the Controller to Complete the following tasks to let the controller read or write data from or to
an Explicit-Server tag:
Get/Set Explicit Server
• Create an Array for the Assembly Instance on page 125
Tags • Enter and Configure the MSG Instruction on page 102
• Set the Communication Path on page 103
Create an Array for the For each assembly instance that you use for explicit server tags, create an
Assembly Instance array in the RSLogix 5000 project for the data.
Enter and Configure the Complete the following steps to enter and configure the MSG instruction.
MSG Instruction 1. Enter a condition for the data transfer, such as the DN bit of a timer.
2. Enter an MSG instruction.
p. From the Source Element pull-down menu, choose the array that
has the data.
q. In the Source Length field, enter the number of bytes that you
have addressed in the PanelView instance (words x 2).
r. In the Class field, type 4.
s. In the Instance field, type the assembly instance of the data in the
PanelView terminal. Convert it to hexadecimal format.
t. In the Attribute field, type 3.
x. In the Instance field, type the assembly instance of the data in the
PanelView terminal. Convert it to hexadecimal format.
Set the Communication The communication path specifies the route to the PanelView terminal. A
Path communication path uses the following format:
scanner_name,2,device_address
Where Is
scanner_name The name of the scanner in the I/O Configuration folder of the
controller.
device_address The address of the device on the DeviceNet network.
Configure Explicit Client Use an Explicit Client tag to let the PanelView terminal get or set a parameter
of another device on the DeviceNet network.
Tags
PanelView Terminal Device
Read Tag Parameter
Determine the Parameter Use RSNetWorx for DeviceNet software to determine the parameter number
Number to Access that you want to access. Some parameters are read-only and are shown with a
lock symbol.
Determine the Find the information about the parameters listed in the following table to get
or set a parameter.
Configuration of the
Parameter
Item Value
Class # (hex)
Instance # (hex)
Attribute # (hex)
Number of bytes (size)
Minimum value
Maximum value
Decimal places
Some devices assume a specific number of decimal places in a
value.
In addition to the documentation for the device, the EDS file may also give
you the required information.
Configure an Explicit Client Complete the following steps to configure an Explicit Client tag.
This chapter describes how use a FactoryTalk View project to get or set a
parameter of a DeviceNet communication module.
Topic Page
Before You Begin on page 27 155 on page 27
Create a Topic for the Device on page 132 156 on page 132
Create a Node on page 133 158 on page 133
Create a Tag for the Parameter on page 134 159 on page 134
Once you add a device to the scan list of a scanner, HMI software such as FactoryTalk View cannot write to (set) some parameters.
Once this device is in the scan list of the scanner, a FactoryTalk View project cannot set this parameter.
Create a Topic for the Use RSLinx communication software to create a topic for the DeviceNet
communication module that you want to access. Complete the following steps
Device to create a topic for the device.
Create a Node In the FactoryTalk View project, create a node for your RSLinx topics.
Complete the following steps to create a node.
Topic Page
Factors that Affect Performance on page 137 162 on page 137
Change the Configuration of Your Network on page 141 165 on page 141
As you configure and program the network, use the default settings whenever
possible. Once the network is running, determine if you need to improve
performance.
If Then
A specific device requires a faster update Change the I/O parameters of the device to change of state (COS).
An analog device does either of the following: Change the I/O parameters of the device to cyclic.
• Changes slower than the scan cycle
• Requires a repeatable update period, such as for PID calculations
Multiple devices are input only and I/O parameters are currently set to polled For each of those devices, change their I/O parameters to strobed.
with an input size less than or equal to 8 bytes
Two or more devices send or receive large amounts of data, such as the • For each of those devices, set their I/O parameters to polled with a poll rate
PanelView operator terminal = background.
• 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 Increase the interscan delay.
receives large amounts of data, such as the PanelView operator terminal, and
has the I/O parameters currently set to polled
Scan Cycle
Polled update
Interscan delay
Px—Scanner sends data to a polled device.
• Scanner continues to get polled data from slower responders or larger devices.
Prx—Polled device sends input data to Communication with software, such as RSLinx and RSNetWorx occurs, for uploading, downloading,
and browsing, for example.
scanner.
x is the address of a device.
Strobed update
Background poll
I/O Parameters of Each The type of connection (message) that you configure for a device determines
when data transfers between the device and the scanner. Consider the
Device following points when you configure the type of connection:
Background Poll The foreground to background poll ratio lets you adjust how often the scanner
polls certain devices for their data. In general, use the default values. Change
them only if you need to tune the performance of your system.
The following diagram shows the effect of a change to the poll ratio.
IMPORTANT When using a foreground to background poll ratio other than 1, the total network
time-out value of the EPR may need to be increased so the background devices do
not time out.
The expected packet rate (EPR) defaults to 75, which is then multiplied by 4 ms to get
a 300 ms timeout for a polled/strobed I/O connection.
Interscan Delay The interscan delay determines how long the scanner waits before it starts
another I/O scan. Follow these guidelines:
• In general, leave the interscan delay at its default value. Change it only
if you need to tune the performance of your system.
• Keep the interscan delay ≥ 5 ms. Otherwise, you may have trouble
accessing the network.
Upload the Current Complete these steps to upload the current configuration.
Configuration of the 1. Start RSNetWorx for DeviceNet software.
Scanner 2. If necessary, open the file for the network.
3. Go online.
4. Double-click the scanner.
5. Click the Module tab.
6. Click Upload from Scanner.
7. When prompted, upload the configuration from the scanner.
Set the Interscan Delay and Change the parameters shown below if needed.
Poll Ratio • For information on changing the Interscan Delay parameter, refer to
page 165 on page 140.
• For information on changing the Foreground to Background Poll Ratio
parameter, refer to page 164 on page 139.
Set the I/O Parameters of a Complete these steps to set the I/O parameters of a device.
Change of State or Cyclic Complete these steps to configure the I/O parameters for the Change of State
setting.
Transfer
1. Check Change of State/Cyclic checkbox.
2. Click the Change of State or Cyclic option.
3. Enter the number of bytes that the devices sends to the controller.
4. Enter the number of bytes that the controller sends to the device.
5. For a cyclic update, enter the period of the update.
6. Click OK.
Strobed Transfer Complete these steps to configure the I/O parameters for the Strobed
Transfer setting.
1. Check Strobed.
2. If the single bit being sent to the strobed device needs to be accessed by
the Logix controller, check Use Output Bit.
This lets you map the bit into the I/O data being transferred with the
controller.
3. Enter the number of bytes that the device sends to the controller.
4. Click OK.
Polled Transfer Complete these steps to configure the I/O parameters for the Polled setting.
1. Check Polled.
2. Enter the number of bytes that the device sends to the controller.
3. Enter 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. Click OK.
Download the Configuration Complete these steps to download the configuration to the scanner.
Save the Configuration File After you make a change to the network, upload the entire network and save
the file. This makes sure that the offline configuration file matches the
network.
This chapter describes how to reduce the time it takes to replace a failed
device.
Table 12.A
Topic Page
Automatic Device Recovery on page 147 173 on page 147
Set Up Automatic Device Recovery on page 148 175 on page 148
You configure ADR on a device-by-device basis. You can set up the following
ADR settings for each device.
If you want to And Then select this ADR option for the device
Manually change the address of the replacement
Automatically configure a
device
replacement device that matches
the electronic key of a failed device
Safety
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.
Use the electronic key options to define how closely a replacement device
must match a failed device before the scanner applies ADR. The scanner
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.
Update Your Network When you set up ADR for a device, RSNetWorx for DeviceNet software reads
the configuration for the device from the configuration file and stores it in
Configuration File the scanner. Before you set up ADR for a device, make sure the configuration
file is up-to-date.
1. Go online.
2. Configure the device.
3. Right-click and upload the entire network.
4. Save the network configuration.
Define the Electronic Key Complete the following steps to define the electronic key.
Set the ADR Settings for the Complete these steps to set the ADR settings for the device.
Download the Changes to Complete these steps to download changes to the scanner.
Upload and Save the Complete these steps to upload and save the configuration file.
To make your programming easier, re-map the value to its own tag within the
data array of the scanner. This lets you access the value without additional
programming.
Give a Value Its Own Complete these steps to give a value its own memory location in the input or
output memory of the scanner.
Memory Location
1. Select the device and click the Advanced button.
2. For the first map entry, specify the first bit of the data.
Literature Library Find installation instructions, manuals, brochures, and technical data publications. rok.auto/literature
Product Compatibility and Download Center Get help determining how products interact, check features and capabilities, and rok.auto/pcdc
(PCDC) find associated firmware.
Documentation feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at
rok.auto/docfeedback.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.
Allen-Bradley, expanding human possibility, Logix, Rockwell Automation, and Rockwell Software are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomayson Ticaret A.Ş. Kar Plaza İş Merkezi E Blok Kat:6 34752, İçerenkÖy, İstanbul, Tel: +90 (216) 5698400 EEE YÖnetmeliğine Uygundur