Introduction To DeviceNet

MET 382 1/14/2008
MET 382
S i ‘08
Spring
Introduction to
DeviceNet
Topics
z Introduction to DeviceNet
z DeviceNet Components
z DeviceNet Fundamentals
z Introduction to The 1756-DNB Scanner
z Configuring
g g the Scanner Module
z DeviceNet Overhead Rungs
Introduction to DeviceNet 1
MET 382 1/14/2008
Introduction
to DeviceNet
What is DeviceNet?
z DeviceNet is an example
p of a device-level local
area network (LAN).
z DeviceNet brings LAN technology down to the

lowest level of the manufacturing enterprise – the
shop floor.
z Just like a computer can function as a node on an

Ethernet network, a field device (such as a
photoelectric sensor) can function as a node on a
DeviceNet network. 4
MET 382 1/14/2008
Input Field Devices

z An input field device that provides on/off type
i f
information
ti (such
( h as a photo-eye)
h t ) can b
be purchased
h d
with a discrete (switched) output or a DeviceNet
output.
z An input field device that has a discrete (switched) output is
wired to a PLC discrete input module (24 volts DC or 120
volts
o s AC).
C)
z An input field device that has a DeviceNet output is wired to

a DeviceNet network.
z The DeviceNet capable input device transmits on/off data
as well as diagnostic information to the PLC. 5
Output Field Devices

z An output field device that is switched on and off
(
(such
h as a solenoid
l id valve)
l )b by a PLC program can
be:
z Wired to a discrete output module (24 volts DC or 120

volts AC),
OR
z Wired as a node on DeviceNet and then controlled by the

PLC over the network.
MET 382 1/14/2008
Example – Wiring input field devices

that have switched outputs
+24 VDC
Chassis
Input field devices

with switched outputs
Processor
module
(Controller)
Backplane
Discrete Input module (DC

inputs in this example)
7
Example – Wiring field devices that

have DeviceNet outputs
z DeviceNet capable field devices function as nodes on a
DeviceNet network. The processor communicates with each
field device through a device known as a scanner.
DeviceNet field devices
Device 0 Device 1
p
Backplane
Logix 5555 DeviceNet Network Cable
Controller Scanner
(1756-DNB)
Device 2 Device n
Chassis 8
MET 382 1/14/2008
DeviceNet Options when

Implementing a New System
z Today, a manufacturing company that implements a
PLC-based control system has essentially three
options with respect to DeviceNet:
z Option 1 – The company does not use DeviceNet!
z Option 2 – The company uses DeviceNet and ALL of the

field devices are DeviceNet capable.
z Option 3 – The company implements a hybrid system.

9
The ODVA
z DeviceNet is an open (non-proprietary) network.
z DeviceNet is supported by the Open DeviceNet

Vendors Association (ODVA).
z “The ODVA is an organization that manages

DeviceNet technology
gy and ppromotes the
worldwide adoption of DeviceNet in industrial
automation.”
z Check out: www.odva.org

10
MET 382 1/14/2008
Typical DeviceNet Nodes
Typical field devices that are placed on DeviceNet:
z Photoelectric sensors z Motor starters

z Proximity sensors z Motor drives
(inductive & capacitive) z Operator interfaces
z Mechanical limit switches (panel views, etc.)
z Pneumatic and hydraulic z PLCs
valves z PCs
z Electric Robots
z And much more…
11
DeviceNet Advantages
z Faster installation times
z Wiring is simpler (often reduced to quick
disconnect type connectors)
z Fewer connections compared to traditional

point-to-point wiring
z Nodes can be easily added, removed, and relocated

– even with power on!
12
MET 382 1/14/2008
DeviceNet Advantages (cont’d)
z Less expensive
p compared
p to traditional
point-to-point wiring
z The required number of conduit, junction boxes,
and terminal strips are reduced
z Labor costs are reduced since wiring is easier

and faster
13
z Most devices provide useful diagnostic information

which can make systems easier to troubleshoot and
minimize downtime
z DeviceNet devices can sometimes offer more

control features compared to traditional/switched
d i
devices.
z For example, an inductive proximity sensor that has a
DeviceNet output can produce on/off data (indicating that
an object is present or absent) as well as analog data
(indicating how far away the object is). 14
MET 382 1/14/2008
z DeviceNet technology can be used with

either PLC or PC-based control systems.
15
Networking in Today’s
Manufacturing Enterprise
z Spanning the entire manufacturing

man fact ring enterprise,
enterprise local
area networks play a vital role in today’s automated
manufacturing environment.
z One network, however, does not do it all. Different

levels of the manufacturing enterprise have different
needs
d and d require
i diff
differentt ttypes off networks.
t k
z Many manufacturers are using DeviceNet to network

devices commonly found on the factory floor.
16
MET 382 1/14/2008
Networking The Manufacturing Enterprise -

Ethernet for Business, Research, and
General Office Applications
Example 1 – Typical
Connections to Ethernet 17

ControlNet at the Workcell Level
Example 2 – Typical Connections to ControlNet

18
MET 382 1/14/2008

DeviceNet on The Shop Floor
19
Example 3 – Typical Connections to DeviceNet
DeviceNet
Components
MET 382 1/14/2008
Introduction
z The devices commonly attached to a DeviceNet

network can generally be classified as follows:
z Scanners
z DC Power Supply
z Field Devices
z User Interface
21
DeviceNet Scanners
Scanners
z The scanner is usually a PLC module (when using

PLC control) or an adapter card in a personal
computer (when using PC control)
z There is usually one scanner on each DeviceNet

network
z Allen-Bradley Scanners: 1756-DNB (ControlLogix),

22
1771-SDN (PLC-5), 1747-SDN (SLC-500)
MET 382 1/14/2008
DeviceNet Scanners (Cont’d)
Scanners
z A “scan list” is generated and then downloaded to

the DeviceNet scanner.
z The scan list includes:

z A list of the active devices on the network
z How to communicate with each device (polled, strobed,

COS, or cyclic)
z How to map the DeviceNet I/O into the ControlLogix tag

23
database
Scanners
z The scanner is always in one of the following

modes:
z Idle mode
z In this mode the scanner does not communicate with the
devices on the network
z Run mode
z In the run mode the scanner communicates with the field
devices (nodes) on the DeviceNet and passes data to and from
the Logix5555 controller
24
MET 382 1/14/2008
Scanners
z On each dropline of the CIMT

conveyor system the DeviceNet
scanner module is located in slot 3.
The 1756-DNB
Th 1756 DNB
ControlLogix
Scanner Module
25
Basic Block Diagram:
DeviceNet field devices
Device 0 Device 1
Backplane
Logix 5555 DeviceNet

Controller Scanner
(1756-DNB)
Device 2 Device n
Chassis
n max = 63 26
MET 382 1/14/2008
DeviceNet Power Supply
24 volt DC
Power Supply
pp y
z The DeviceNet cable carries both data and power (24v

DC).
z Some devices are totally powered from the DeviceNet

cable.
bl
z Other devices (e.g., a panel view) require additional power

from a second 24 volt DC power supply
27
DeviceNet Field Devices
Field Devices
z Allen-Bradley DeviceNet field devices are classified

as follows:
z Single point devices
z Photoelectric sensors, proximity sensors, etc.
z I/O platforms
z Compact bl
C blockk I/O
I/O, A
Armor bl
block
k I/O
I/O, or Fl
Flex I/O
z Enables traditional/switched devices to be connected to
DeviceNet
z DeviceLink
z Enables traditional/switched devices to be connected to 28
DeviceNet
MET 382 1/14/2008
DeviceNet Field Devices
Field Devices
z Allen-Bradley DeviceNet field devices are classified

as follows (Continued):
z User Interface
z Configures a DeviceNet network
z Usually a computer running DeviceNet configuration software
z Motor drives
z Electronic operator interfaces (EOI)

z Examples include: PanelViews, message displays, etc. 29
DeviceNet Components - Field Devices

Æ Single Point Devices
Photoelectric
Sensor
871TM Inductive
Proximity Switch
These devices have true DeviceNet outputs

and will function as a node on DeviceNet 30
MET 382 1/14/2008

Æ I/O Platforms, Compact Block I/O
Switched field devices

are connected here
Incoming
DeviceNet cable
Compact Block I/O devices include a built-in network adapter,31

inputs/outputs, and a power supply in one small package

Æ I/O Platforms, Armor Block I/O
¾ Multiple traditional/switched ¾ Armor blocks

bl k are
field devices can be wired to an factory hardened units
Armor block. that can be mounted
directly on a conveyor or
¾ Each block supports multiple
machine – no enclosure is
inputs or outputs.
necessary.
¾ The entire block functions as
one node on DeviceNet.
¾ A wide variety of I/O
combinations (inputs/outputs,
AC/DC) are available. 32
MET 382 1/14/2008

Æ Armor Block I/O Example
These two mechanical limit switches are

connected to the Armor Block shown below
Armor block DeviceNet trunkline 33

Æ I/O Platforms, Flex I/O
¾ Flex I/O can be used to connect

traditional/switched field devices to
DeviceNet.
¾ Flex I/O can be used with multiple
networks. To use Flex I/O with DeviceNet
use the 1794-ADN Adapter.
¾ Flex I/O modules mount on a DIN Rail –
There is no chassis.
¾ One Flex I/O system supports up to 8
I/O modules.
¾ A wide variety of I/O is available. 34
MET 382 1/14/2008

Æ DeviceLink
A DeviceLink is used to connect
traditional/switched field devices to DeviceNet.
Typical field devices include:
¾ Photoelectric sensors
¾ Proximity sensors
¾ Mechanical limit switches
¾ and many more…
Traditional/switched devices have switched (discrete)
outputs (AC or DC) that are either fully on or fully
off. 35

Æ DeviceLink (Cont’d)
DeviceLink wire colors and definitions
This end connects This end is connected to

to DeviceNet the traditional/switched
field device
36
MET 382 1/14/2008
DeviceNet Components - User Interface
User Interface
¾ The user interface is usually a computer.

¾ The user interface is used for:
Node commissioning (assigning a device a node
number)
Monitoring or changing device parameters
Monitoring or changing the scanners scan list 37
DeviceNet Components - User

Interface (Cont’d)
User Interface
¾ The User Interface runs the DeviceNet configuration

software. The configuration software is used to setup a new
DeviceNet, troubleshoot problems associated with an existing
DeviceNet, or making changes to an existing DeviceNet.
¾ The user interface is typically assigned a high node number
(such as 62, where node numbers range from 0 to 63)
¾ DeviceNet configuration software example: Rockwell 38
Software’s RSNetworx for DeviceNet
MET 382 1/14/2008
DeviceNet Components - User

Interface (Cont’d)
User Interface
¾ Available Allen-Bradley PC Adapter Cards:

¾ 1784-PCID (desktop, PCI card)
¾ 1784-PCIDS (desktop, PCI card)
¾ The 1784-PCIDS allows the PC to function as a user interface or a
DeviceNet scanner if using PC-based control. This card is installed in
each dropline PC
¾ 1784-PCD (notebook, PCMCIA card)
¾ 1784-PCDS (notebook, PCMCIA card, same function as 1784-PCIDS) 39
DeviceNet
Fundamentals
MET 382 1/14/2008
DeviceNet Fundamentals
z Topics:
z Topology
z Assigning Node numbers
z Available Baud Rates
z DeviceNet Media
z I/O Message Types
41
DeviceNet Fundamentals -
Topology
z DeviceNet is based on a bus topology
(also called trunkline/dropline)
z A DeviceNet LAN has a main trunkline with

multiple droplines
42
MET 382 1/14/2008
Topology
43
Assigning Node Numbers
z Each device must have a unique node

number ranging from 0 to 63
z All devices “out of the box” default to node

63
z New devices must be reassigned a different
node number
44
MET 382 1/14/2008
Available Baud Rates
z DeviceNet supports
pp the following
g baud rates:
z 125k bps (this is the default)
z 250k bps
z 500k bps
z M
Many d
devices
i supportt autobaud
t b d
z These devices automatically sense and then set
their data rate to the correct value when they are
connected into an existing network
45
Available Baud Rates (Cont’d)
z The baud rate and node numbers for Allen-
Bradley scanners are set as follows:
z ControlLogix – Use the pushbutton on the front of the 1756-
DNB module
z DeviceNet cable disconnected – The pushbutton is used
to set the baud rate
z DeviceNet cable connected – The pushbutton is used to

set node number
z PLC-5 – DIP switches on the scanner module
z SLC-500 – Software (RSLogix500)

46
MET 382 1/14/2008
DeviceNet Media
z There are three media types:
z Round – Thick
z Typically used for trunkline
z Round – Thin
z Typically used for drop lines
z Flat
47
DeviceNet Media, Quick

disconnect
Flat Cable connector
Interface
z KwikLinktm Flat Media
module
S t
System
z “50% savings in installation
costs”
z Modular connector system
z “V
“Vampire
i teeth”
t th” pierce
i cable
bl
Hinged tap
Flat cable 48
MET 382 1/14/2008
DeviceNet Media –
Comparing Different Media
Each dropline can span up to 20 feet (6 meters)
49
DeviceNet Media –
Wire Color Codes
z A DeviceNet cable carries both data and power
Data
Drain wire
connected
to shield
Ground
+24 VDC 50
MET 382 1/14/2008
DeviceNet Media –
Open Style Connector
Terminating
Resistor
51
DeviceNet Media –
Sealed Style Connectors
Trunkline (flat cable)
52
MET 382 1/14/2008
I/O Message Types
z Methods for gathering device data include:
z Polled
z Strobed
z Change-of-State (COS)
z Cyclic
The actual method used depends on your

specific application and which method(s)
are actually supported by the field device.
53
Introduction to The
1756-DNB Scanner
MET 382 1/14/2008
The 1756-DNB Scanner
z Topics:
z 1756-DNB Scanner – Wiring Details
z 1756-DNB Scanner – Using The Message

Display
z Scanner Error Codes
55
1756-DNB Scanner –
Wiring Details
The DeviceNet cable

connected to the
1756-DNB scanner
56
MET 382 1/14/2008
1756-DNB Scanner –
Using The Message Display
The scanners message g
display is located on the front
of the 1756-DNB module. It
displays:
LEDs show
¾ The scanners DeviceNet node important
address status
information
¾ The scanners current mode
(idle or run)
¾ Error Codes (if any)
{See next slide for error codes} Use this button to manually
set the scanners baud rate 57
and node address
Scanner Error Codes
58
MET 382 1/14/2008
Scanner Error Codes
59
Configuring The
Scanner Module
MET 382 1/14/2008
Configuring The Scanner

Module
z Basic Procedure:
z Add the 1756-DNB DeviceNet scanner module to
the I/O Configuration Folder of the CIMT 243
template program.
z Configure the scanner module as shown on the

following slides.
Continued on next slide …

61
Configuring the Scanner Module
Add the scanner module

(1756-DNB) to the I/O
Configuration folder
Configure the module

by selecting the desired
properties
Continued on next slide … 62
MET 382 1/14/2008
Configuring the Scanner Module
Note:
N t Use
U revision
i i 7.1
71
when configuring the
1756-DNB DeviceNet
scanner
63
Configuring the Scanner -

Configuration Results
The Results -- The General Tab …
64
Continued on next slide …
MET 382 1/14/2008

The Results -- The General Tab (cont’d) …
By default RSLogix5000 will allocate a maximum of 124 DINTs for

input data, 123 DINTs for output data, and 32 DINTs for status.
If memory is limited the input and output data sizes can be adjusted
for your application, otherwise use the maximum values as shown 65
above.

The Results -- The Connection Tab …
The Logix5555
g controller will
communicate with the 1756-DNB
scanner over the backplane at the
selected RPI rate.
66
MET 382 1/14/2008

The Results -- The Module Info Tab …
This is status information

which can monitored when
you are online and in the
run mode.
d
67

The Results -- The Backplane Tab …

run mode.
68
MET 382 1/14/2008


run mode. 69


run mode.
70
MET 382 1/14/2008

The Results – I/O Controller Scoped Tags
Inputs
Outputs
St t
Status
71

The Results – Output Tags
When this bit is set to a 1 the scanner

is placed into the RUN mode. When
this bit is reset to a 0 the scanner is
placed into the IDLE mode. See
DeviceNet Overhead Rungs
Continued on next slide … 72
MET 382 1/14/2008

The Results – Output Tags (cont’d)
Thi iis an array off DINT
This DINTs corresponding
di tto
the scanners outputs. To understand this
array your must first understand how the
outputs are mapped into the scanner’s
scan list using RSNetworx for DeviceNet!
73

The Results – Input Tags
This is an arrayy of DINTs corresponding
p g to the
scanners inputs. To understand this array your
must first understand how the inputs are
mapped into the scanner’s scan list using
RSNetworx for DeviceNet!
74
MET 382 1/14/2008
DeviceNet
Overhead Rungs
DeviceNet Overhead Rungs

Every program
which controls
a dropline on
the CIMT
conveyor must
include the
following rungs!
76

Introduction To DeviceNet

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Introduction To DeviceNet

Încărcat de

Drepturi de autor:

Formate disponibile

MET 382 1/14/2008

z DeviceNet brings LAN technology down to the

z Just like a computer can function as a node on an

Input Field Devices

z An input field device that has a DeviceNet output is wired to

Output Field Devices

z Wired to a discrete output module (24 volts DC or 120

z Wired as a node on DeviceNet and then controlled by the

Example – Wiring input field devices

Input field devices

Discrete Input module (DC

Example – Wiring field devices that

DeviceNet field devices

DeviceNet Options when

z Option 1 – The company does not use DeviceNet!

z Option 2 – The company uses DeviceNet and ALL of the

z Option 3 – The company implements a hybrid system.

z DeviceNet is supported by the Open DeviceNet

z “The ODVA is an organization that manages

z Check out: www.odva.org

Typical DeviceNet Nodes

Typical field devices that are placed on DeviceNet:

z Photoelectric sensors z Motor starters

z Fewer connections compared to traditional

z Nodes can be easily added, removed, and relocated

DeviceNet Advantages (cont’d)

z Labor costs are reduced since wiring is easier

DeviceNet Advantages (cont’d)

z Most devices provide useful diagnostic information

z DeviceNet devices can sometimes offer more

DeviceNet Advantages (cont’d)

z DeviceNet technology can be used with

z Spanning the entire manufacturing

z One network, however, does not do it all. Different

z Many manufacturers are using DeviceNet to network

Networking The Manufacturing Enterprise -

Networking The Manufacturing Enterprise -

Example 2 – Typical Connections to ControlNet

Networking The Manufacturing Enterprise -

Example 3 – Typical Connections to DeviceNet

z The devices commonly attached to a DeviceNet

z The scanner is usually a PLC module (when using

z There is usually one scanner on each DeviceNet

z Allen-Bradley Scanners: 1756-DNB (ControlLogix),

DeviceNet Scanners (Cont’d)

z A “scan list” is generated and then downloaded to

z The scan list includes:

z How to communicate with each device (polled, strobed,

z How to map the DeviceNet I/O into the ControlLogix tag

DeviceNet Scanners (Cont’d)

z The scanner is always in one of the following

DeviceNet Scanners (Cont’d)

z On each dropline of the CIMT

DeviceNet Scanners (Cont’d)

Basic Block Diagram:

DeviceNet field devices

Logix 5555 DeviceNet

DeviceNet Power Supply

z The DeviceNet cable carries both data and power (24v

z Some devices are totally powered from the DeviceNet

z Other devices (e.g., a panel view) require additional power

DeviceNet Field Devices