Chapter 11 Intro to DeviceNet

7/23/2019 Chapter 11 Intro to DeviceNet

http://slidepdf.com/reader/full/chapter-11-intro-to-devicenet 1/85

Chapter 11

Introduction to DeviceNet



DeviceNet Purpose

• Open network

• Link low-level devices to PLCs

– Sensors

– Pushbutton stations

– Distributed IO blocks

– Intelli!ent "otor started overloads

– #ariable $re%uenc& drives



DeviceNet Open Network

• Open network

• Network devices 'nodes( can be purchased

$ro" "an& di$$erent vendors

• Network "ana!ed b& Open DeviceNet

#endors )ssociation 'OD#)(

– OD#)*O+,



DeviceNet )dvanta!e

• Save wirin! costs

– +ather than run power wires separatel& to each

device – +ather than run si!nal wires $ro" each $ield device

separatel& back to PLC IO "odule connect devices

directl& to a network

– One cable with $our wires• .wo power wires

• .wo si!nal wires



/ield Devices 0ore Intelli!ent

• .raditional s&ste"s

– ) photo switch countin! pieces as the& pass

on a conve&er was wired directl& into an input"odule*

• Counter pro!ra""ed on ladder to track partscount

• Counter done bit tri!!ered output point tocontrol $ield action



DeviceNet )dvanta!e

• 0an& DeviceNet devices are intelli!ent*

• Photo switch has counters and ti"ers incorporated

into sensor*• PLC does not need to have ti"er or counter on

ladder*

• 2hen ti"er or counter is done the action is carried

out throu!h +SNet2or3 $or DeviceNet so$tware totri!!er $ield device across the network*



DeviceNet Co"ponents

• PLC with DeviceNet scanner

• +SNet2or3 so$tware $or DeviceNet

• .runk line• Drop lines

• Nodes

• 0ini"u" one power suppl&

• .wo 141-oh" 5-watt ter"ination resistors• 6p to 78 nodes



DeviceNet Network 93a"pleCable to open-st&le

connector on

network PLC scanner

:wikLink cable

.er"ination

resistor

+i!htSi!ht

photo sensor

Insulation

displace"ent

connector Co"pact;lock

IO "odule

)r"or;lock

"a3i"u"

8 IO points

Power

suppl&

.er"ination

resistor

Open-st&le connection

$or power suppl&

Pro3 switch

and cable Stack li!ht



Sa"ple o$ So"e DeviceNet 0edia Co"ponents

.hick round

drop line cable

:wikLink drop

line cable

:wikLink $lat trunk

line cable insulation

displace"ent connector

Device port

.-port

:wikLink $lat trunk

line cable

DeviceLink



DeviceNet Cablin!

• .hick round

• .hin round

• :wikLink cable

• Special-use cable

• Open-st&le connectors



.hick +ound Cable

• 6sed $or trunk line

• .-ports used to connect $ro" trunk line to

drop lines



.hin +ound Cable

• .&picall& used $or drop lines

• Can be used $or trunk in short networks with

low current re%uire"ents



:wikLink DeviceNet Connection

:wikLink $lat cable

Insulation displace"ent

connector



Insulation Displace"ent Connection

• /or non-wash down

• .&pical usa!e conve&or lines

• 0ount on inside rail o$conve&or

• No conduit needed

• 9as& installation o$ new

nodes• No "ini"u" spacin!



DevicePort

• Passive 8- or <-point taps

• Connected to trunk line b& drop line

• Previous slide showed an <-point DevicePort

• Nodes connected to DevicePort b& drop lines



.-port

• 6sed to connect drop line to trunk line

• Drop line connected to DevicePort and then

on to "ultiple nodes• Drop line connected directl& to node

• 0a3i"u" drop line len!th 4= $eet



DeviceLink

• )dapter to inter$ace non-DeviceNet devices

to network

• 4- or >-wire 48-# sensors• 0echanical li"it switches

• )n& non-DeviceNet device with rela&

contacts• One re%uired $or each non-DeviceNet node



)dditional 0edia

• +e$er to the DeviceNet 0edia catalo! $or a

co"plete listin! o$ available products*



0a3i"u" .runk Line Len!th '1 o$ 4(

• 0a3i"u" cable distance between an& two

nodes

• Not necessaril& actual len!th o$ backbone• 0a3i"u" len!th deter"ined b& cable t&pe

and baud rate



0a3i"u" .runk Line Len!th '4 o$ 4(



.runk Line Calculation One

Node nu"ber



93a"ple One

• Le$t ter"inatin! resistor to node 1 is 14 $eet*

• Drop line node 1 is 4 $eet*

• +i!ht ter"inatin! resistor to node 14 is also14 $eet*

• Node 14 drop line is 4 $eet*

• /ro" node 1 drop line to node 14 drop line is<== $eet*



.runk Line Calculation '1 o$ 4(

• /or this e3a"ple trunk line len!th is

"a3i"u" len!th o$ cable between

ter"inatin! resistors*



.runk Line Calculation '4 o$ 4(

• 14 ? <== ? 14 @ <48 $eet

• +e$er to table $or "a3i"u" baud rate o$

network*



0a3i"u" .runk Line Len!th

.runk line len!th is over <4= $eet so "a3i"u" baud rate $or this network is 14A :*



.runk Line Calculation .wo

Power Suppl&

1

4

>

8

A

7

B <

1=

11

14

1>

18

7 $t

4 $t

< $t

>== $t4= $t

14 $t

> $t

Node nu"bers



93a"ple .wo

• Le$t ter"inatin! resistor to node 1 drop line is 4= $eet*• Node 1 drop line is 7 $eet*• +i!ht ter"inatin! resistor to node 14 drop line is 4

$eet*• Node 14 drop line is < $eet*• .runk line $ro" node 14 drop to node 18 drop line is

> $eet*

• Node 18 drop line is 14 $eet*• Node 1 trunk line to node 18 is >== $eet*



.runk Line Calculation

• /or this e3a"ple trunk line len!th is

"a3i"u" len!th o$ cable between an& two

nodes or ter"inatin! resistors*• )ssu"e round thick trunk line*

• Look at network a!ain*



.runk Line Calculation .wo '1 o$ 4(

Power Suppl&

1

4

>

8

A

7

B <

1=

11

14

1>

18

7 $t

4 $t

< $t

>== $t4= $t

14 $t

> $t

/or this e3a"ple trunk line len!th is "a3i"u" len!th o$ cable between an&

two nodes or ter"inatin! resistors*



.runk Line Calculation .wo '4 o$ 4(

• .he lon!est cable distance is between the le$tter"inatin! resistor and node 18*

• /or this e3a"ple the distance betweenter"inatin! resistors would not be the correctcalculation*

• 4= ? >== ? 14 @ >>4 $eet

• +e$er to table $or "a3i"u" baud rate o$network*



0a3i"u" .runk Line Len!th '1 o$ >(

.runk line len!th is over >4< $eet so "a3i"u" baud rate

$or this network is either14A : or 4A= k*



0a3i"u" .runk Line Len!th '4 o$ >(

• .he rule is to !o back 4= $eet $ro" the

ter"ination resistors and see i$ there is a

drop line that is lon!er* – I$ a drop is lon!er then it "ust be included in

the trunk line calculation*

– +e"e"ber "a3i"u" drop line len!th is 4=

$eet*



15

8

43

7

20 feet

0a3i"u" .runk Line Len!th '> o$ >(

• .er"inatin! resistor

and node == is > $eet*

• Node == and node 1 is8 $eet*

• .runk line to node B is

1A $eet*

• 1A $oot drop is lon!erthan > ?8 $or trunk*



Cu"ulative Drop Line Len!th '1 o$ 4(

• Su" o$ all drop lines

• 0a3i"u" drop line len!th to an& one node

– 4= $eet

• Cu"ulative drop line len!th also deter"ines

network baud rate

Text fgure 11 30



Cu"ulative Drop Line Len!th '4 o$ 4(

Text fgure 11-30



.otal )ll Drop Line Len!ths '1 o$ 4(



.otal )ll Drop Line Len!ths '4 o$ 4(

• Cu"ulative len!th is 1>1 $eet*

• Nodes 1= 1> and 18 e3ceed the 4=-$oot

"a3i"u" drop to an& 1 node*• Shorten up cable*

• Cu"ulative drop line len!th is now 14B $eet*

• +e$er to the table $or "a3i"u" baud rate $ornetwork*



Cu"ulative Drop Line Len!th

Cu"ulative drop line len!th is 14B $eet*



Power Calculations

• )dd up total device current

• Deter"ine trunk line len!th

• Cable t&pe• ow "an& power supplies and where "ounted

• Look up tables $or power allowed on network

• /ull calculation "ethod available $or additional

accurac&



Co""on Proble"s

2ith DeviceNet Networks '1 o$ 4(

• I"proper installation

– .runk line len!th correctE

– Cu"ulative drop line len!th correctE – Power suppl& proper siFeE

– Overdrivin! network with too "uch in$or"ation $lowE

• +e$er to DeviceNet Cable S&ste" Plannin! and

Installation 0anual $ro" +ockwell )uto"ation 2ebsite*



Co""on Proble"s

2ith DeviceNet Networks '4 o$ 4(

• Network "odi$ication a$ter installation

– .runk line len!th recalculatedE

– Cu"ulative drop line len!th recalculatedE – Power suppl& recalculatedE

– Overdrivin! network with too "uch

in$or"ation $lowE



DeviceNet Inter$ace



DeviceNet open-st&le

cable connection point

Set baud rate

Set inter$ace

cards node

Status LEDs

/le3Lo!i3 PLC DeviceNet

Dau!hter Card



Co"pactLo!i3 DeviceNet Scanner

DeviceNet scanner

Open-st&le cable connection

Co"pactLo!i3 processor

Co"pactLo!i3 is a "e"ber o$ the ControlLo!i3 $a"il&*



ControlLo!i3 0odular Inter$ace

• ControlLo!i3 "odular

chassis inter$ace

"odule• 1BA7-DN;

• DeviceNet brid!e

"odule

In$or"ation

window

Status L9Ds

Open-st&le

network connection

1BA7-DN;



93a"ple o$ +ockwell )uto"ation

PLC DeviceNet Inter$ace 0odules• SLC A== DeviceNet scanner

– 1B8B-SDN

• PLC A DeviceNet scanner

– 1BB1-SDN



93a"ple o$ ,eneral 9lectric PLC

DeviceNet Inter$ace 0odules• Series =->= PLCs

– DeviceNet "aster "odule

– IC7>DN04==• #ersa0a3 PLC

– +e"ote IO DeviceNet network inter$ace

– IC4==D;1==1



Personal Co"puter

DeviceNet Inter$ace• Co"puter t&pe deter"ines inter$ace needed*

– Notebook uses PC0CI) such as a +ockwell

)uto"ation 1B<8-PCD* – Desktop or industrial co"puter would re%uire

a DeviceNet 1B<8-e3pansion card*

– Co"puter with serial port could use +ockwell

)uto"ation 1BB=-:/D inter$ace bo3*



1BB=-:/D Inter$aceDesktop or notebook

co"puter with serial port

1BB=-:/D Inter$ace cable

Open-st&le connector to

DeviceNet network

Inter$ace

cable plu!

:/D to serial port

inter$ace cable

SLC A== 1B8B-SDN



Open-st&le connector

to DeviceNet network

PC0CI) inter$ace

card 1B<8-PCD

SLC A== 1B8B-SDN

Notebook

personal co"puter

Inter$ace cables

1B<8-PCD Card



6se ControlLo!i3

PLC as a ;rid!e '1 o$ 4(

• 0ost popular inter$ace to PLC $or upload

download on-line editin! is 9thernet

• 9thernet inter$ace card in ControlLo!i3chassis'1BA7- 9N;.(

• ) 1BA7-DN; or DeviceNet brid!e "odule in

ControlLo!i3 chassis to co""unicate withDeviceNet



6se ControlLo!i3

PLC as a ;rid!e '1 o$ 4(

• 6se +SLin3 9thernet driver to !et to 9thernet

inter$ace "odule

• ;rid!e across ControlLo!i3 backplane toDeviceNet ;rid!e "odule '1BA7-DN;(

• Out DN; to DeviceNet network

• No separate DeviceNet inter$ace re%uired



+SNet2or3 So$tware

• +SNetwor3 $or DeviceNet so$tware

– Set up network

– 0ap data $lowin! on network – Pro!ra" "onitor or "odi$& device

para"eters



+SNet2or3 $or DeviceNet



+SNet2or3 #iew o$ DeviceNet

.er"inationresistor

.er"ination

resistor

Power suppl& not shown in +SNet2or3

.runk line

Drop line

Network scanner

Node address

Device or node

on network



DeviceNet Scan List

• +SNet2or3 so$tware

• Scan List is part o$ scanner properties*

• )n& device that is on the network that is to bescanned b& the PLC scanner "ust be in the ScanList*

• Network devices are not "apped until placed in theScan List b& pro!ra""er*

– )uto "appin!

– 0anual "appin!



)dd or re"ovesin!le device to

or $ro" Scan List

)uto "ap

devices when

add to scan list

Scan List tab

Scan List

9lectronic

ke&in!

ControlLo!i3

DN; scanner

properties screen

DeviceNet PLC Scanner Properties

)dd or re"ove

all devices to

or $ro" Scan List



)vailable Devices on Network

• 2hen !oin! on-line with a network scanner

like a 1BA7-DN; scanner will reco!niFe

devices currentl& present on network* – .hese devices or nodes will be listed in the

)vailable Devices view*

– .hese devices are not in the scan list at this

ti"e*



)uto 0ap Devices

2hen )dd to Scan List• Do &ou want the device's( to be auto-"apped

when added to the scan listE

• I$ )uto"ap is selected &ou have no control o$how devices are "apped*

• I$ &ou uncheck )uto"ap then devices can be

"anuall& "apped b& the pro!ra""er*



9lectronic :e&in!

• ow close does a replace"ent device haveto be to the ori!inal when replacedE

– Device t&pe – #endor

– Product code

– 0aGor revision

– 0inor revision• 0inor revision or hi!her



DeviceNet Data 0appin!

ControlLo!i3



ControlLo!i3 1BA7-DN; 0appin!

Scanner

properties

Input devices

in Scan List

Input tab

ControlLo!i3 processor

ta!s or addresses

where data is "apped*

Data "appin!$or each node

6nused processor

"e"or&* Can be

"anuall& "apped later*

Click here to

un"ap a device*




• ControlLo!i3 is a >4-bit PLC*

– )ll ta!s will be either >4 bits wide or aH

• 2ord called an inte!er 'IN.( which is17 bits

• ;&te called a short inte!er 'SIN.( which is < bits

• 0ini"u" "e"or& allocation $or an& DeviceNet

device is a SIN.*

• Node 7 is a bulletin 17= )llen-;radle& Drive* – Drive has two words o$ data*

• Drive status in$or"ation as sin!le bits

• Drive speed $eedback represented as = to >4B7B



>4 ;its

17 ;its

=B<1A17>1

ControlLo!i3 Input 0appin!

Node 7 Drive Input Status word

Node 7 Drives Speed /eedback word Node 8 Series ===

Photo 9lectric Sensor

"appin!

Node > Series ===

Photo 9lectric Sensor

"appin!

ControlLo!i3 .a!s



ControlLo!i3 Processor

Data 0appin! or .a!s'1 o$ 4(

• Node 7 is ;ulletin 17= the variable $re%uenc&

drive

– Status bits "apped as upper word o$LocalH1HI*Data4J*

– Drive Speed /eedback word is "apped as the

lower word o$ LocalH1HI*Data>J*



ControlLo!i3 Processor

Data 0appin! or .a!s '4 o$ 4(

• Node 8 is a Series === Photo Switch

"apped as the upper b&te o$ the lower word

at LocalH1*I*Data4J*• Node > is a Series === Photo Switch

"apped as the lower b&te o$ the lower word

at LocalH1*I*Data4J*




SLC A==




• SLC A== and PLC A are 17-bit co"puters*

– )ll data will either be a 17-bit word or one b&te*

•0ini"u" "e"or& allocation $or an& DeviceNetdevice is a b&te*

• Node 7 is a ;ulletin 17= )llen-;radle& Drive*

– Drive has two words o$ data*

• Drive Co""and in$or"ation as sin!le bits• Drive Speed Co""and represented as = to >4B7B



SLC A== Output Data 0appin!

1B8B-SDN

properties view

Output devices

in Scan List

SLC A== Output Status

.able where data isco"in! $ro"

Output "appin! tab

Click here to un"ap selected device

.wo words or <b&tes currentl&

"apped $or drive

at node 7



SLC A== Processor Data 0appin!

• Node 7 is ;ulletin 17= the variable $re%uenc&

drive

– Drive Co""and bits word is "apped asOH1*4*

– Drive Speed Co""and word is "apped as

OH1*>*



Node 4 Output 0appin!

• Node < is a +ockwell )uto"ation 1B4D

co"pact block output "odule*

– .his co"pact block has $our outputs*• Output data $ro" SLC A== "apped to lower

b&te o$ OH1*7*

• Currentl& upper b&te o$ OH1*7 is available $oranother device*



DeviceNet Nodes

,eneral Properties



• +i!ht click on device on +SNet2or3 screen*

• ,eneral Properties screen is displa&ed*

– Displa& IO data – Displa& "onitor or "odi$& devices

para"eters

– #iew electronic data sheet '9DS $ile(



Identi$ies this device

Current node address*

Node address can be

chan!ed here*

Para"eters

tab

Devices

identit&

9DS tab

Nu"bers used

to identi$& 9DS $ile

,eneral Properties



Device Para"eters

Para"eters

tab

Para"eter

nu"ber

Lock identi$ies

read-onl&

para"eters Click here to

"onitor para"eter

Icons $or uploadin!

or downloadin!to device

0onitor a sin!le

para"eter or all

Current value

o$ para"eter

Device



Para"eter 9ditin!

Select para"eter

to edit

Options drop-down bo3

Select



9lectronic Data Sheets

9DS /iles



9lectronic Data Sheets

• .&picall& re$erred to as 9DS $iles

– 9DS $iles contain in$or"ation re!ardin! the

personalit& o$ the device* – Correct 9DS $ile "ust reside in the device

be$ore it can be a workin! part o$ the network*

– 9DS $ile "ust be the sa"e $ir"ware level as

the device*



I$ 9DS /ile Is Not Current

• ,o to "anu$acturers 2eb site and download

correct $ile*

• ,o to OD#)*O+, site and download correct$ile*

• 9DS $ile nu"bers represented in e3*

• 6se 9DS 2iFard to update or re!ister thenetwork device*



9DS 2iFard

6pdatin! a network

Devices 9DS $ile is to

re!ister the $ile*

Click ne3t to continue*



+e!ister 9DS /ile

ow "an&$iles to re!ister

)$ter download

browse $or $ile

on &ou co"puter*

Click ne3t to

continue

re!istration*

9DS $ile na"e

represented

in e3



Deter"ine 9DS /ile Na"e

• )$ter downloadin! 9DS $ile the $ile na"e is

represented in e3*

– .o deter"ine 9DS $ile to use when re!isterin!$ileH

• 0ust know e3

• Construct $ile nu"ber $ro" +SNet2or3 !eneral

properties pa!e



1J @ ===1

Convert ,eneral Properties

Pa!e Device Identit& to e3

7J @ ===7

8>J @ ==4;

1*==8J @ =1==



Select Correct 9DS /ile



Select Correct 9DS /ile

Documents

Chapter 11 Intro to DeviceNet