Solid state equipment has operational characteristics differing from those of
electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (Publication SGI-1.1
available from your local Rockwell Automation sales office or online at
http://www.ab.com/manuals/gi) describes some important differences
between solid state equipment and hard-wired electromechanical devices.
Because of this difference, and also because of the wide variety of uses for
solid state equipment, all persons responsible for applying this equipment
must satisfy themselves that each intended application of this equipment is
acceptable.
In no event will Rockwell Automation, Inc. be responsible or liable for
indirect or consequential damages resulting from the use or application of
this equipment.
The examples and diagrams in this manual are included solely for illustrative
purposes. Because of the many variables and requirements associated with
any particular installation, Rockwell Automation, Inc. cannot assume
responsibility or liability for actual use based on the examples and diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to
use of information, circuits, equipment, or software described in this manual.
Reproduction of the contents of this manual, in whole or in part, without
written permission of Rockwell Automation, Inc. is prohibited.
Throughout this manual we use notes to make you aware of safety
considerations.
WARNING
IMPORTANT
ATTENTION
SHOCK HAZARD
BURN HAZARD
Identifies information about practices or circumstances
that can cause an explosion in a hazardous environment,
which may lead to personal injury or death, property
damage, or economic loss.
Identifies information that is critical for successful
application and understanding of the product.
Identifies information about practices or circumstances
that can lead to personal injury or death, property
damage, or economic loss. Attentions help you:
• identify a hazard
• avoid a hazard
• recognize the consequence
Labels may be located on or inside the drive to alert
people that dangerous voltage may be present.
Labels may be located on or inside the drive to alert
people that surfaces may be dangerous temperatures.
Preface
About This Manual
To:See :
get started with a Logix5000 controllerDeviceNet Modules in Logix5000™ Control Systems, publication
Look up abbreviated information and procedures
regarding programming languages, instructions,
communications, and status
program a Logix5000 controller—detailed and
comprehensive information
program a specific Logix5000 programming
instruction
import or export a Logix5000 project or tags from or
to a text file
convert a PLC-5 or SLC 500 application to a
Logix5000 project
control devices over an EtherNet/IP networkEtherNet/IP Modules in Logix5000 Control Systems User
control devices over an ControlNet™ networkControlNet Modules in Logix5000 Control Systems User Manual,
You are
here
control devices over an DeviceNet™ networkDeviceNet Modules in Logix5000 Control Systems User Manual,
The manual is one of various Logix5000 manuals.
1756-QS001
Logix5000 Controllers System Reference, publication
1756-QR007
Logix5000 Controllers Common Procedures, publication
1756-PM001
• Logix5000 Controllers General Instructions Reference
Manual, publication 1756-RM003
• Logix5000 Controllers Process and Drives Instructions
Reference Manual, publication 1756-RM006
• Logix5000 Controllers Motion Instruction Set Reference
Logix5550 Controller Converting PLC-5 or SLC 500 Logic to
Logix5550 Logic Reference Manual, publication 1756-6.8.5
Manual, publication ENET-UM001
publication CNET-UM001
publication DNET-UM004
This manual guides the development of a control system that uses a
Logix5000™ controller and a DeviceNet™ network. A Logix5000
controller is any of the following:
• 1756 ControlLogix® controllers
• 1769 CompactLogix™ controllers
• 1789 SoftLogix5800™ controllers
• 1794 FlexLogix™ controllers
• PoweFlex®700S with DriveLogix™ controllers
1Publication DNET-UM004A-EN-P - March 2004
Preface 2
Who Should Use this
This manual is for those who program or maintain industrial
automation systems.
Manual
To use this manual, you must already have experience with:
• programmable controllers
• industrial automation systems
• personal computers and Windows® 95, Windows 98,
Windows NT®, or Windows 2000 operating system
Conventions in this Manual
Text that is:Identifies:For example:Means:
Italicthe actual name of an item that you
see on your screen or in an example
courierinformation that you must supply
based on your application (a
variable)
enclosed in brackets a keyboard keyPress [Enter].Press the Enter key.
As you use this manual, you will see some terms that are formatted
differently from the rest of the text:
Right-click User-Defined …Right-click on the item that is named
User-Defined.
Right-click
name_of_program …
You must identify the specific program in
your application. Typically, it is a name or
variable that you have defined.
ControlNet main networkControlNet to DeviceNet Linking Device 1788-CN2DN
Bridging Across Networks
Device 1
Logix5000™ devices can usually communicate with devices on other
networks with no additional configuration or programming.
• A bridge connects two different networks. The bridge is either:
– single device with communication ports for two different
networks
– separate communication devices in the same chassis
• For example, the bridge device shown below is connected to
both EtherNet/IP and DeviceNet networks. Device 1 on
EtherNet/IP can communicate with Device 2 on DeviceNet
through the bridge.
EtherNet/IP network
switch
bridge
DeviceNet network
Publication DNET-UM004A-EN-P - March 2004
Device 2
Before You Begin 1-7
Communication can bridge these networks:.
A device on this networkCan access a device on this network:
EtherNet/IPControlNet:DeviceNet:
EtherNet/IPyesyesyesyes
ControlNetyesyesyesyes
DeviceNetnonoyesno
RS-232yes
(1)
To use RSNetWorx software to configure and schedule a ControlNet network, we recommend that you either:
yes
(1)
yesyes
• connect to an EtherNet/IP network and bridge to the ControlNet network
• use a 1784-PCC interface device to connect directly to the ControlNet network
(2)
Typically, this is a point-to-point connection between a Logix5000 controller and another device, such as a PanelView™
Plus operator terminal.
RS-232
(2)
:
workstation
In this example, a workstation configures a drive on a DeviceNet
network. The workstation bridges EtherNet/IP to reach the drive.
EtherNet/IP network
switch
bridge
DeviceNet network
PWR
STS
PORT
MOD
Drive
NET A
NET B
Publication DNET-UM004A-EN-P - March 2004
1-8 Before You Begin
EtherNet/IP network
EtherNet/IP bridge in
1756 system
DeviceNet bridge in
same 1756 system
DeviceNet network
This example RSLinx window shows how the DeviceNet bridge links
to the EtherNet/IP network:
distributed DeviceNet
devices
Publication DNET-UM004A-EN-P - March 2004
Before You Begin 1-9
Choose a Baud Rate for the
The default baud rate for a DeviceNet network is 125K bits/s. This is
the easiest baud rate to use and is usually sufficient.
Network
The 2 most common methods to set the baud rate of a device are:
Method:Description:
autobaud featureAt power up, the device automatically sets its baud rate to the baud rate of the first device it hears on the network. It
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.
switches or
pushbutton on the
device
softwareSome devices require a programming device to set its address. For example, you can use your computer and the
Some devices have switches or a pushbutton that set the baud rate.
• The device reads the switch setting at power up.
• Typically, the switch lets you select either:
• autobaud
• fixed baud rate of 125K, 250K, or 500K
• If you change the switch setting, you have to cycle power to the device before the change to takes effect.
There are exceptions. For example, the 1756-DNB module has a pushbutton, which only lets you set the baud rate if
the module is unconnected from the network or network power is off. Once you change the baud rate, the module
automatically resets to the new baud rate.
DeviceNet Node Commissioning tool (software) to set the baud rate of a device. The Node Commissioning tool is
available:
• automatically when you install RSNetWorx for DeviceNet software
• as a separate application on the RSLogix 5000 software CD, revision 13.0 or later
Publication DNET-UM004A-EN-P - March 2004
1-10 Before You Begin
If You Want to Use a Higher 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 your network, make sure that all
devices change to the new baud rate. Mixed baud rates produce
communication errors.
To set the baud rate for the network:
length
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
does not have a switch to
enable autobaud
A. Set the switch to autobaud.
B. Connect the device to the network.
A. Connect the device to the network.
B. Use RSNetWorx software to enable
autobaud.
Publication DNET-UM004A-EN-P - March 2004
Before You Begin 1-11
Calculate Scanner Memory
Requirements
If a device sends input data, it uses
input memory in the scanner.
devicedevicedevice
If a device gets output data, it uses
output memory in the scanner.
A Logix5000 scanner has fixed sections of memory for the input and
output data of your network. Each device on your network requires
either some input or output memory of the scanner. Some devices
both send and receive data, so they need both input and output
memory.
The memory of a Logix5000 scanner is organized as an array
scanner
module
Input
Memory
DINT
DINT
DINT
Output
Memory
DINT
DINT
DINT
of DINTs (4-byte elements). A Logix5000 system is easier to
program if you give each device its own DINT or DINTs
within the scanner.
byte 3byte 2byte 1byte 0
DINT
DINT
DINT
Some memory may be left
empty (not used).
Device B
The data fills only the portion
of memory that it needs.
Device A
To make sure your network is within limits, calculate the amount of
input and output memory that the scanner needs. This information
will also be very useful when you configure the scanner.
Check the I/O Limits of the Scanner
Once you tally the input and output data for your network, make sure
it is within the limits of the scanner. If they exceed the limits, use
multiple scanners.
ScannerMaximum input data (DINTs)Maximum output data (DINTs)
1756-DNB124123
1769-SDN9090
1784-PCIDS124123
1788-CN2DN124123
1788-EN2DN124123
1788-DNBO124123
Publication DNET-UM004A-EN-P - March 2004
1-12 Before You Begin
If You Are Using a SoftLogix5800 Controller
The 1784-PCIDS scanner organizes its input and output memory in
16-bit increments. When you access the data in the controller, the data
is packed into 32-bit increments (DINTs).
Scanner Input Memory
16 bits
16 bits
16 bits
16 bits
16 bits
16 bits
Controller Input Data
Controller Output DataScanner Output Memory
A Logix5000 system is easier to program if you give each device its
own DINT or DINTs within the controller. To accomplish this with a
PCIDS scanner:
Publication DNET-UM004A-EN-P - March 2004
• Allocate memory in 4-byte increments.
• This may result in some 16-bit words being left unused.
Before You Begin 1-13
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 between 0 to
Device
Give this device:This address:Notes:
scanner0If you have multiple scanners, give them the lowest addresses is sequence (0, 1…).
any device on your network
except the scanner
computer interface to the
network
no device63Always leave address 63 open. Out of the box, most DeviceNet devices are preset for
1 to 61• Give the lower addresses to devices with 15 bytes or more of input or output
62If you connect a computer directly to the DeviceNet network, use address 62 for the
63. However, we recommend that you follow these guidelines:
data.
• Gaps between addresses are OK and have no effect on system performance. If
you are uncertain of the final lay-out of your system, leave gaps between
addresses. This gives you some flexibility as you develop your system.
computer.
• Many computer interface devices use this address as their default.
• Devices such as a 1770-KFD or 1784-PCD connect a computer directly to a
DeviceNet network.
address 63.
• Some devices have no switches or pushbutton to set the address. They require
software such as RSNetWorx for DeviceNet software to change the address. This
means that you must first place it on the network at its preset address of 63
before you can change the address.
• If another device is already using address 63, there will be an address conflict
and you won’t be able to communicate with the newly connected device.
• Leaving address 63 open makes it possible to configure a new device.
• The auto-address recovery feature also requires address 63 to be open.
Publication DNET-UM004A-EN-P - March 2004
1-14 Before You Begin
1. Give address 0 to the scanner.2. Give the lower addresses to devices with 15 bytes or more of input or
Here’s an example:
output data.
3. Gaps in addresses are OK.
DeviceAddressInput Size of
Device
(bytes)
Input Memory
in Scanner
(DINTs)
Output Size
of Device
scanner0n/an/an/an/a
PanelView terminal31283212832
<empty>22
I/O adapter w/ modules59352
<empty>22
drive74141
<empty>22
photoeye91100
computer interface62n/an/an/an/a
63
4. Give address 62 to the computer interface device.5. Leave address 63 open.
(bytes)
Output Memory
in Scanner
(DINTs)
Publication DNET-UM004A-EN-P - March 2004
Configure Your Network Offline
Chapter
2
How to Use This Chapter
To configure your DeviceNet network, you have the following
options:
If:Then configure your network:See:
Any of the following conditions apply:
• The network and devices are not yet installed.
• You do not have access to the network. (I.e., You are
off-site.)
• You prefer to do most of the configuration before you get
on-site with the network.
Both of the following conditions apply:
• The network and devices are already installed.
• You have access to the network. (I.e., You are on-site.)
offlineThis chapter
onlineChapter 6
Offline configuration lets you do most of the DeviceNet configuration
tasks before you connect to the network.
Off-Site
RSNetWorx for DeviceNet software
1. Configure parameters of each device.
2. Configure the scanner to communicate
On-Site
DeviceNet network
Scanner
Scan List
device 1
device 2
device3
…
1Publication DNET-UM004A-EN-P - March 2004
device 1
parameter 1
parameter 2
parameter 3
…
…
…
device 2
parameter 1
parameter 2
parameter 3
…
…
…
device 3
parameter 1
parameter 2
parameter 3
…
…
…
with the devices on your network.
2-2 Configure Your Network Offline
To configure a DeviceNet network while offline:
Step:Page:
❑ Before You Begin2-2
❑ Create a File for the Network2-3
❑ Draw Your Network2-4
❑ Configure Each Device2-5
❑ Configure the Scanner2-8
❑ Save the Network File2-15
❑ Generate an RSNetWorx Report2-16
❑ Download the Configuration to Network2-17
Before You Begin
DeviceAddressInput Size of
scanner0n/an/an/an/a
PanelView terminal31283212832
<empty>22
I/O adapter w/ modules59352
<empty>22
drive74141
<empty>22
photoeye91100
computer interface62n/an/an/an/a
Before you configure the network, make sure you have a list of the
devices that you are putting on your network and the address for each
of them.
For example:
63
Total
Device
(bytes)
Input Memory
in Scanner
(DINTs)
4341
Output Size
of Device
(bytes)
Output Memory
in Scanner
(DINTs)
Publication DNET-UM004A-EN-P - March 2004
Configure Your Network Offline 2-3
Create a File for the
Network
RSNetWorx software stores information about the configuration of
each device in a file on your computer.
Step:See page:
❑ Create a DeviceNet Configuration File2-3
❑ Give the File a Descriptive Name2-3
Create a DeviceNet Configuration File
1. Start RSNetWorx software.
2. Create a file.
3. Select DeviceNet Configuration.
4. Choose OK.
Save the file.
Give the File a Descriptive Name
Since the file stores the configuration of the network, give it a name
that identifies this specific DeviceNet network.
As you work in RSNetWorx software, periodically save your changes
to the file for the network.
Publication DNET-UM004A-EN-P - March 2004
2-4 Configure Your Network Offline
Draw Your Network
1. Browse the hardware list for the device.
2. If there is a [+] sign next to the device, click the [+] sign.
To configure a DeviceNet network, you use RSNetWorx software to
build a graphical picture of your network. To build a graphical picture
of your network, complete the following steps for each of your
devices:
graphical picture of your network
3. Double-click the major revision of the device.
For a device without a list of major revisions (no + or - sign), double-click the device.
Publication DNET-UM004A-EN-P - March 2004
If Your Device Is Not in the Hardware List…
If the hardware list does not show a device, then RSNetWorx requires
the EDS file for the device:
1. To see if an EDS file is available, go to
www.ab.com/networks/eds/
2. Use the EDS wizard of RSNetWorx software to register the file.
Loading...
+ 209 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.