59
Introduction Introduction à à

Introduction à

  • Upload
    yule

  • View
    22

  • Download
    0

Embed Size (px)

DESCRIPTION

Introduction à. Qu’est-ce que DeviceNet??. En terme de réseautique, il s’agit d’une structure qui présente des avantages indéniables sur la structure traditionnelle Source-Destination. Il s’agit du modèle Producteur-Consommateur. Exemple Source/Destination. - PowerPoint PPT Presentation

Citation preview

Page 1: Introduction à

IntroductionIntroductionàà

Page 2: Introduction à

En terme de réseautique, il s’agit d’une structure qui présente des avantages indéniables sur la structure traditionnelleSource-Destination. Il s’agit du modèleProducteur-Consommateur

Qu’est-ce queDeviceNet??

Page 3: Introduction à

Exemple Source/DestinationUne personne (“source”) dit a chaque

personne (“destinations”) dans une salle

l’heure du jour (data)• Les gens peuvent choisir d’ignorer l’information,

mais il y a du temps et des efforts de perdu.• Le temps s’écoule au fur et a mesure que la

“source” informe les “destinations”.• Le temps nécessaire pour informer tout le monde,

varie selon le nombre de personnes présentes

Page 4: Introduction à

Exemple Producteur/Consommateur

Une personne (“producteur”) dit a tout le monde (“consommateur”)en meme temps, l’heure du

jour (“data”) • Tout le monde recoit l’information

simultanément• Certaines personnes peuvent choisir de

“consommer” l’information. (ex. en ajustant leur montres)

• d’autres choisiront d’ignorer l’information• Tres efficace: cela prends le meme temps

si 10 ou 100 personnes sont présentes dans la salle !

Page 5: Introduction à

Producteur/Consommateur

• message #1– Position de référence du senseur vers Controller 1,

Controller 2, et HMI• message #2

– Commande de vitesse du Controller 1 est émis vers les Drives 1, 2, & 3, et HMI

• Moins efficace que le modele source/destination– requiet 7 messages vs. 2

Drive1Sensor

Drive3Drive2

#1#2

Controller 1Controller 2

ALLEN-BRADLEY

7 8 9

4 5 6

1 2 3

. 0 -

<-----------------'<--

F1

F6

F2

F7

F3

F8

F4

F9

F5

F10

PanelView 550

< >

^

v

HMI

Page 6: Introduction à

CumulativeDrop-line Budget156m @ 125Kbaud 78m @ 250Kbaud 39m @ 500Kbaud(Maximum of 6m each)

Trunk line Distanceand Baud rate100m Max. with Thin cable500m @ 125Kbaud (thick)250m @ 250Kbaud (thick)100m @ 500Kbaud (thick)(longer with Repeaters)

Maximum Devices64 Nodes per Network

Physical Media(Shielded Twisted Pair)Communications and PowerThick - Trunk or dropThin - Trunk or DropFlat - Trunk only

Drop-line wiringSingle dropDaisy-chaining off dropBranching off drop

ALLEN-BRADLEY

7 8 9

4 5 6

1 2 3

. 0 -

<-----------------'<--

F1

F6

F2

F7

F3

F8

F4

F9

F5

F10

PanelView 550

< >

^

v

Device ConnectionsT-TapsZero-drop(Maximum 6m each)

Terminating Resistors120 Resistors at bothnetwork trunkline ends

Network Power•24vDC power to devices•Thick & Flat trunk rated to 8 amps•Thin wire rated at 3 amps

Messaging ServicesProducer/ConsumerHigh-speed I/OProgrammingConfigurationDiagnostics

Network Specifications

Page 7: Introduction à

• Supporte jusqu’à 64 nœuds.• Un nœud peut etre enlevé “live” du réseau sans affecter la

bonne marche du réseau.• Protection contre les erreurs de cablage: il y a une protection

contre le cablage inversé a meme les équipements• Vitesse de transmission selectionnable: 125, 250, 500 K baud

– Pas requis de supporter toutes les vitesses– Perte de vitesse au profit de la distance

• Topologie “trunk-line”/”drop-line”– Branches permises sur les “drop”

• Permet des “drops” de longueur “zero”

Caractéristiques Physiques

Page 8: Introduction à

• Paires torsadées, faible perte, faible delais

• Utilisation de connecteurs scellés ou de type ouverts

• Supporte les équipements opto-isolés et non opto-isolés

• Alimentation séparée a meme le cable de communication

– Supporte les équipements auto-alimentés et alimentés externes

• Capacité haut courant (jusqu’à 8 amps)

• “Power taps” qui permettent le raccordement de plusieurs sources d’alimentation.

NOTE: ces “power taps”sont requis si l’alimentation se fait hors d’un cabinet de raccordement .

Caractéristiques Physiques

Page 9: Introduction à

• 5 Conducteurs, 1 paire pour le 24 Volts DC power, 1 paire pour la communication CAN, 1 Shield

• Courant Maximum en 24 Volts DC avec du cable “thick” et du cable plat, de 8 amp. Cependant, certaines regulations du code électrique, limite ce courant à 4 amp. Avec le cable “thick”.

• Courant maximum en 24 Volts DC avec du cable “thin” limité a 3 amp.

+24VDC ( V+ )

+0VDC ( V- )

CAN-H

CAN-L

ShieldFil nu

bleu

blancrouge

noir

Cablage Devicenet

Page 10: Introduction à

Zero Drop Drops“drop” en branche

Termination TerminationTap

Trunk

Daisy Chain max20 feet

Noeud Noeud

Noeud

Noeud

Noeud

Noeud

NoeudNoeud

Noeud

Noeud

Noeud

Trunk Distance

Longueur du Trunk

P/S

Topologie

Page 11: Introduction à

• Résistance de fin de ligne de 120 ou 121 Ohms, 1/4 Watt

• Elles DOIVENT etre placées à la fin de chaque extrémité du “trunk”, entre le fil blanc et le bleu .

• Existent en version scellée et ouverte

Terminaison

Page 12: Introduction à

• “Trunk” & “Drops”– Le “Trunk” constitue la “colonne vertebrale” du réseau . – Les “Drops” relient les équipements au “trunk”.

Longueur maximale: 20 pieds.

• Il existe 3 types de cables: Thick, Flat, et Thin– Thick & Flat supportent 8 amps .– Thin supporte 3 amps .– TOUT les types de cable peuvent servir de “Trunk”

Terminologie

Page 13: Introduction à

Data Rates 125 Kbaud 250 Kbaud 500 KbaudTrunk Distance 500m (1640 ft) 250m (820ft) 100m (328 ft)

Max. Drop Length 20 ft 20 ft 20 ft

Cumulative Drop 512 ft 256 ft 128 ft

Number of nodes 64 64 64

Cable Budget - Thick Trunk

Page 14: Introduction à

Data Rates 125 Kbaud 250 Kbaud 500 Kbaud

Trunk Distance 100m (328 ft) 100m (328 ft) 100m (328 ft)

Max. Drop Length 20 ft 20 ft 20 ft

Cumulative Drop 512 ft 256 ft 128 ft

Number of nodes 64 64 64

Cable Budget - Thin Trunk

Page 15: Introduction à

Data Rates 125 Kbaud 250 Kbaud 500 Kbaud

Trunk Distance 420m (1378 ft) 200m (656 ft) 75m (246 ft)

Max. Drop Length 20 ft 20 ft 20 ft

Cumulative Drop 512 ft 256 ft 128 ft

Number of nodes 64 64 64

Cable Budget - Flat Trunk

Page 16: Introduction à

Mini Quick Disconnect18mm

Micro Quick Disconnect12mm

“Terminal Strip”Style Connector

Cable

Types de connecteurs

Page 17: Introduction à

• Tee Tap– Keyed left & right

• Trunk line segments– molded minior micro connectors– various lengths

• Drop lines– mini or micro molded

connectors– up to 20ft– mini, micro or pigtail at

sensor

• Field Installable trunk line connectors

– screw type

Sealed T-Taps

Page 18: Introduction à

• Requirements– Modulaire

– Faible cout

– Temps d’installation minime

– Format compact

– Compatible avec les media existants

– NEMA 6P & 13, IP 67

KwikLinkFlat Cable

Page 19: Introduction à

Drop

Trunk Trunk

DeviceBox™

DevicePort™

Drop

(to Trunk)

Drop

• DevicePort Multiport Tap– micro quick

disconnects

– various configurations

• DeviceBox Multiport Tap– 2, 4, 8

Multi-Port Sealed Media

Page 20: Introduction à

Multiport Taps

Tee Taps

Trunk line segments -molded mini-connectors

Drop lines - molded connectors - 0 to 6 m (20 ft.) - mini or micro at device

Field Installabletrunk lineconnectors -screw type -crimp type

Typical Sealed-Style Taps

Page 21: Introduction à

Trunk

Dropline• Zero length drop using 1787-Plug10R with probe cable support

Sealed Control Enclosure

OpenStyleDevice

OpenStyleDevice

OpenStyleDevice

OpenStyleDevice

Open Style Taps

Page 22: Introduction à

• Signal pair (#18), blue/white• Power pair (#15), black/red• Foil/braid shield with drain wire(#18)• PVC/nylon insulation on power pair• Industrial temperature range

– Storage: -40o C to +85oC– Operating: -20o C to +60o C @ 8A

• derate linearly to 0A at 80o C

• High flexure capability• Flame resistant, UL Oil Res. II• 0.480 inch diameter

Thick Cable Description

Page 23: Introduction à

Vinyl Jacket.480” O.D.

Beldfoil Aluminum/Polyester Shield

Polypropylene FillersBlue & White Data Pair

Datalene Insulation

18 AWG. Tinned and StrandedCopper Conductors

15 AWG.Tinned and StrandedCopper Conductors

Red & Black DC Power PairPVC/Nylon Insulation

Stranded Drain WireTinned Copper

18 AWG.

65% CoverageTinned Copper Braid Shield

Thick Cable Belden AB numberGrey PVC 3082A YR-29790Yellow CPE 3083A YR-39659

DeviceNet Thick Cable

Page 24: Introduction à

• Signal pair (#24), blue/white

• Power pair (#22), black/red

• Foil/braid shield with drain wire(#22)

• PVC/nylon insulation on power pair

• Industrial temperature range

– Storage: -40o C to +85oC

– Operating: -20o C to +70o C @ 1.5A

• derate linearly to 0A at 80o C

• High flexure capability

• Flame resistant, UL Oil Res. II

• 0.270 inch diameter

Thin Cable Description

Page 25: Introduction à

Vinyl or CPE Jacket.270” O.D.

Beldfoil Aluminum/Polyester Shield

Polypropylene FillersBlue & White Data Pair

Datalene Insulation

24 AWG. Tinned and StrandedCopper Conductors

22 AWG. Tinned and StrandedCopper Conductors

Red & Black DC Power PairPVC/Nylon Insulation

Stranded Drain WireTinned Copper

22 AWG.

65% CoverageTinned Copper Braid Shield

Overall Mylar Tape

Thin Cable Belden AB numberGrey PVC 3084A YR-29832Yellow CPE 3085A YR-39660

DeviceNet Thin Cable

Page 26: Introduction à

KwikLink4-wire Flat Cable

Page 27: Introduction à

DeviceNet Flat MediaDeviceNet Flat Media

•• 600V, 8A rating 600V, 8A rating

•• Physical key Physical key

•• Fits in 1” conduit Fits in 1” conduit

+24Vdc

DeviceNet Power, 8 Amps Max.

DeviceNet Cable

0 VdcCAN_H CAN_L

User defined 1

0 Vdc

User defined 2

Auxiliary Power Cable

Output Power, 8 Amps Max.

+24Vdc

•• Works with existing devices Works with existing devices

•• TPE / Santoprene jacket TPE / Santoprene jacket

•• Highly flexible Highly flexible

Media Features

Page 28: Introduction à

• V- ( Black Wire ) and Shield ( Bare Wire ) MUST be connected to a good earth ground at only one location on a DeviceNet System.

Signal

Signal

Shield

V-

V+

V- V+ 24 VDC Power Supply

.

..

..

Power Tap

Network Grounding

Page 29: Introduction à

powersupply

N33 N64N32 N1

up to 500 m

up to 500 m up to 500 m

• Characteristics and Advantages– Power supplies can be located anywhere on the network

• Must consider IR losses along cable– Greater current than most comparable networks

• Up to 8 amps (NEC limits to 4 amps)– Power supplies are standard, low cost models

Single Supply Configuration

Page 30: Introduction à

Two Supply Configuration( Current Boost )

PowerSupply

N33 N64N32N1

up to 500 m

PowerSupply

• Characteristics and Advantages

– Loads shared by supplies so same low cost supplies are used

– Substantially more current

• Still 8 amp limit on any branch of the trunk ( NEC limit of 4 Amps)

– Supplies can be located anywhere (consider IR losses)

Page 31: Introduction à

V+ Power Conductor

V- Power Conductor

24 V PowerSupply

Optional SecondSupply

Topology for Power Along the Bus

Node Node Node

24 V PowerSupply

Node

CAN-H, CAN-L, Shield

Page 32: Introduction à

Producer/Consumer Networks can support ALL three Connection

Relationships• One-to-One

• Multicast (One-to-Many)

• Broadcast (One-to-All)

• Mix and Match on the same network

Page 33: Introduction à

Producer/Consumer Networks can support ALL three Hierarchies

• Master/Slave

• Multimaster

• Peer-to-Peer

• Mix and Match on same network

• Explicit and Implicit Message types

Page 34: Introduction à

Producer/Consumer Networks can support ALL three I/O Data Exchange

Methods

• Polling

• Cyclic

• Change-of-State (COS)

• Mix and Match

• Master/Slave, Multimaster, Peer-to-Peer

• One-to-One, Multicast, or Broadcast

Page 35: Introduction à

Replacing Devices

• Set node address, data rate (or Autobaud)• Configure device parameters• Connect device to system• Slave devices must pass electronic “key”

– device type– manufacturer– part number

• NEW! Auto Device-Replace ( ADR )

Page 36: Introduction à

Auto Device Replace ( ADR )• RSNetworx for DeviceNet software must be used to configure ADR feature.

• ADR consists of two parts which are Node Recovery and Configuration Recovery. Node Recovery causes the node number of the replacement device to be automatically changed to the node number of the original device. This feature requires that the replacement device’s node number to modified over the DeviceNet network and its node number must be 63 to begin with.

• Configuration Recovery will cause the replacement devices configuration to be made identical to the original device. The replacement device must be able to have its configuration written over the DeviceNet network. Configuration Recovery files are stored in the master scanner that is communicating with the original device by RSNetworx.

• Electronic key of replacement device MUST match the original device exactly.

#55 #63

Replacement DeviceOriginal Device

#63

Replacement Device

#55

Replacement Device

Node Recovery

Configuration Recovery

Page 37: Introduction à

DeviceNet Products

Page 38: Introduction à

DeviceNet Config s/w

DH+/ControlNet/Ethernet

DeviceNet

1770-KFDRS-232PC I/F

DeviceNet Manager V3.04

1305, 1336 DrivesSMP-3 SmartMotor Protector,SMC Dialog Plus

Series 9000Photoelectric

800T RediSTATION

RIO

PLC-5/xx

AdaptaScan Bar Code Reader

1771-SDN Scanner

Third PartyDevices

Third PartyDevices

Third PartyDevices

A-B DeviceNet Products

1203DeviceNetInterface

1747-SDN Scanner

SLC-5/02,5/03, 5/04

DH485/DH+

A-B

A-B

Physical Media

SMP3

DeviceLink I/Ow/standard sensor

1794-ADNAdapter for Flex I/O

Page 39: Introduction à

DeviceNet Products

1784-PCDPCMCIA I/F

FlexPak 3000& GV3000 Drives825 Smart

Motor Manager

PLC-5/xx

1771-SDN/B Scanner

ArmorBlock I/O and LowProfile ArmorBlock I/O

1747-SDN/B Scanner

SLC-5/02,5/03, 5/04

DeviceView

FAULT

START

STALL

TEMP

LINE

ENERGY SAVER

STOPPING

STARTING

RUNNING

CONTROL VOLTAGE

3D3FRN

SMCPLUSTM

ALLEN-BRADLEYA-B

IMC S-Class1394 GMC

Smart MotorController

160 SmartSpeed Controller

physical media

DTAM PlusDTAM Micro

PanelView 550, 900ALLEN-BRADLEY

7 8 9

4 5 6

1 2 3

. 0 -

<-----------------'<--

F1

F6

F2

F7

F3

F8

F4

F9

F5

F10

PanelView 550

< >

^

v

RSNetworx forDeviceNet

RSServerWIN DNet16

Dodge EZlinksensorized bearing

1761-NET-DNI871-TM Prox

18mm & 30mm1784-PCIDSScanner Card

Page 40: Introduction à

1770-KFD DETAILS

Page 41: Introduction à

1770-KFD Fun Facts• The 1770-KFD is not a true RS232 to DeviceNet converter. The KFD is actually a

buffering interface between the two networks. The RS232 device connected to the KFD is actually running a DeviceNet driver to communicate through the KFD.

• 1770-KFD can NOT be put on-line unless at least one other node is also on the network. At least one other node must Ack the 1770-KFD Dup Mac Check.

• The RS232 led on the KFD must blink when there is correct RS232 communication to the KFD. If not, then there is some configuration conflict in the computer that keeps the COM port on the computer from being used for the KFD.

• 1770-KFD firmware is NVS Flash Tool upgradable.

• If the KFD is connected to a network that has a 24VDC power supply attached, the use of an AC adapter connected to the jack on the KFD is NOT necessary.

• An AC adapter, connected to the KFD, can source 60 ma of DC current for point-to-point connections to devices.

• 1770-KFD contains a built in terminating resistor for point

to point use.

Page 42: Introduction à

1784-PCD PCMCIA DeviceNet Interface Card

Page 43: Introduction à

DeviceNet PCMCIA Interface(1784-PCD or 1784-PCDS)

• PCMCIA card for PC connectivity to DeviceNet

• Use PC to configure devices, monitor data, or perform simple maintenance functions

• Type II compatible

• Autobaud capable

• Cabling scheme makes use of 1770-KFD cable options

• Operating system drivers for Windows 3.x, Windows 95/98 and NT

• Works with DeviceNet Manager and RSNetworx for DeviceNet software

Page 44: Introduction à

FlexI/O DETAILS

Page 45: Introduction à

1794-ADN FlexI/O Fun Facts• Node Number is set via pushwheels on the 1794-ADN adapter. • Baud rate is handled via autobaud automatically by the 1794-ADN.• Current firmware revision is V2.01 as of 3/25/97. This also handles Change of State and

Cyclic messaging.• Firmware is flash upgrade-able over the DeviceNet network using the NVS update tool on a

PC.• When fresh out of the box a 1794-ADN will actively read what modules are in its rack on

every powerup. It will use the default sizes shown in the following slides for each module contained in its rack to determine its Rx and Tx size. However, as soon as a specific configuration is stored to the 1794-ADN using the FlexI/O tool in RSNetworx or DeviceNet Manager, the 1794-ADN will lock in that configuration. The 1794-ADN will not automatically scan the rack anymore and will error if the rack configuration doesn’t match what it expects. The configuration is stored in the 1794-ADN and if the ADN goes bad. Someone will have to download the configuration to the replacement ADN before it will work the same as the original one. This complicates module replacement a lot. To clear out a configuration in an ADN and go back to “Fresh Out of the Box Mode” select the Clear Memory feature in the FlexI/O configuration tool in the RSNetworx or DeviceNet Manager. Note: Clear Memory will not operate if a network master is scanning the 1794-ADN at the same time. Disconnect the master from the network or disable scan list entry for the FlexI/O in the master before attempting a Clear Memory.

Page 46: Introduction à

1794-ADN FlexI/O Fun Facts ( Continued )

• Do NOT supply power to the 1794-ADN adapter from the network 24 VDC power, as tempting as it looks. The 1794-ADN and other FlexI/O modules draw a lot of power ( up to 400ma ) and you could run out of current quickly or get bitten by Common Mode Voltage at longer distances.

• 1794-ADN User Manual is Publication 1794-6.5.5. This manual shows how to configure the ADN and shows data sizes for most FlexI/O modules.

• Be careful when assembling the 1794 Terminal Bases to the 1794-ADN adapter, as the pins in the side of the ADN and Terminal Bases are fragile and bend over easily causing erratic operation in the FlexI/O rack. A good way to determine if a pin is bent over is to remove each module from the FlexI/O rack and note if the network led blinks red until the module is replaced. This is desirable behavior and if the led does not blink upon module removal, then a pin is bent over.

• Series B hardware is electrically identical to Series A except for a few cosmetic differences. Series B Phoenix connector has jack screws and there is a 3rd led to show power on the module.

• UCMM Capable Device

Page 47: Introduction à

Consumes 1 word of output data

16 bits of output (1 bit per output)

Produces 1 word of input data

word 0 Fuses blown (1 bit per output)(May not be applicable with all Modules)

Flex I/O 1794-OB16 and OtherDiscrete Outputs Data Usage

word 0

Page 48: Introduction à

871TM SmartProx DETAILS

Page 49: Introduction à

871 TM SmartProx Fun Facts• The Node Number is set via the Node Commissioning utility in the

RSNetworx, DeviceNet Manager and DeviceView hand held configurator.

• Baud rate set via autobaud which can be disabled if desired.

• Supports Change of State and Strobing message types in Series A. Will add Poll message type support in Series B.

• Comes in 18mm and 30mm sizes with micro connectors, mini connectors and cable connections to network.

• Features include counter capability, motion detect, analog output, On/Off delays and teach/learn mode.

Page 50: Introduction à

871 TM Prox Data DescriptionsSensor Output – Set when target Detected.

:Too Close Definition – Target is within 1.5mm of face. Latched on until another targetdetection is made that doesn’t enter 1.5mm of the face.Too Close Bit – Set when target Too Close

Too Far Definition – Target passes through sensor switch point, but does not passthrough user configured Too Far Min Margin point. The default value of the Too Far setpoint is -20% of the switch point, but can configured from 0% to -20%. The user mayalso setup this diagnostic as Static to Dynamic. In static mode the diagnostic is setwhenever the target pass in the defined region, while in dynamic mode the diagnostic islatched on.Too Far Bit – Set when target Too Far

Coil Operational – Set when an open in the coil is detected

Always In Definition– Target pass through sensor switch point, but does not passthrough user configured Always In Max Margin point. The default value of the AlwaysIn set point is +20% of the switch point, but can configured from 0% to +20%. Thisdiagnostic is latched on until target pass outside of the range.Always In Bit – Set when target Always In

Motion Detect Output – Set when the sensor output does not change within the Presettime.

Counter Output – Counter Preset value reached

Analog Output – Analog value for relative distance (0 – 255)

Page 51: Introduction à

871 TM Prox Data Details

Consumes 1 bit of Strobe output data or 0 bytes of COS data

Produces 2 byte of Strobe or COS data

Byte 0 Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit5 Bit 6 Bit 7SensorOutput

Diagnostic CoilOperational

TooClose

Too Far AlwaysIn

MotionDetect

CounterOutput

Byte 1 Bit 0 Bit 1 Bit 2 Bit 3 Bit 4 Bit5 Bit 6 Bit 7Analog Output

Strobe bit clears timers and counters when set to a 1.

Page 52: Introduction à

CompactBlock I/ODETAILS

Page 53: Introduction à

CompactBlock I/O Fun Facts• Node number is set via either Rotary Switches or Node Commissioning in the

RSNetworx or DeviceNet manager Software if switches are set for node 64 though 99. Baud rate is handled via autobaud automatically by the CompactBlock.

• Firmware is Flash upgradable over the network.

• Supports Polled, Change of State or Cyclic messaging.

• Outputs have electronic short circuit protection. Outputs can also be programmed to go to a 0, a 1 or hold last state on a fault.

• CompactBlock I/O can support up to 32 discrete points of I/O per node number. The stand alone base module can have 16 discrete 24VDC inputs, 16 Discrete 24VDC outputs or 8 discrete 24VDC inputs and 8 discrete outputs. The expansion module can have 16 discrete 24VDC inputsor 16 discrete 24VDC outputs and connects to the base module with a ribbon cable.

• CompactBlock I/O Installation Manual is Publication 1791D- 5.42. Product Profile document is Publication 1791D- 1.4. Product Data documentt is Publication 1791D- 2.1.

Page 54: Introduction à

CompactBlock I/O

• CompactBlock I/O for the DeviceNet communicationnetwork is a compact, low-cost block I/O for use in avariety of distributed applications

• Delivers ease of installation and expandability in acompact, flexible package

• 0-55°C temperature range, IEC IP20 rating

• Standards of compliance

– IEC1131 - 2

– NEMA Type 1+ inputs

– UL 508

– CUL Class I Division 2, Groups A-D

– CE marked

– ODVA conformance

Page 55: Introduction à

CompactBlock I/O DetailsModules I/O Points Produce Consume

( Rx Size ) ( Tx Size )

Base InputBase OutputBase CombinationBase input with expansion inputBase output with expansion outputBase input with expansion outputBase output with expansion inputCombination module with expansion inputCombination module with expansion output

16 Inputs16 Outputs8 Input/ 8 Output32 Input32 Output16 Inputs/ 16 Outputs16 Outputs/ 16 Outputs24 Inputs/ 8 Outputs24 outputs/ 8 Inputs

2 bytes0 bytes1 byte5 bytes1 byte3 bytes3 bytes4 bytes2 bytes

0 bytes2 bytes1 byte0 bytes4 bytes2 bytes2 bytes1 bytes3 bytes

Notice that for every 8 inputs a byte of data is added to the Rx size and for every 8 outputs abyte is added to the Tx size.

The only magic is that when an expansion module is used, it adds 1 extra byte to the Rx size and puts this byte as the last byte of the Input data. This extra byte has only bit 7 being used as astatus for the expansion module. Bit 7 = 1 means expansion module bad or missing, bit 7 = 0means the expansion module is functioning correctly.

Page 56: Introduction à

1761-NET-DNI DETAILS

Page 57: Introduction à

1761-NET-DNI• MicroLogix or SLC-500 Slave I/O to DNet Master

– 32 words of data

• Directly Message between other 1761-NET-DNI and other peer to peer capable modules.

– Standard MSG (read/write) instruction

• UCMM Capable Device

• Program/Monitor MicroLogix or SLC-500 over DeviceNet

– DH-485 Functionality

• Fast “local” control on DeviceNet

– True “distributed” control

• DF1 Full Duplex connection

– Any existing MicroLogix or SLC-500 controller

Page 58: Introduction à

1761-NET-DNI Fun Facts

| | ( )

Bit 7 of LSB of Input Data Bit 7 of LSB of Output Data

Baud Rate is determined via Autobaud and Node address is set via Node Commissioning.

To use RSLogix programming software running over DeviceNet to program a DF1 device connected to a DNI requires V2.0 or higher RSLinx software.

Transmit and Recieve Data sizes are set using the EDS file for the 1761-NET-DNI. Message types supported are COS and POLL.

When using the 1761-NET-DNI as a slave to another master, a ladder rung is neccessary to interface to the DNI heartbeat mechanism for proper operation. The least significant bytes of the the Transmit and Receive data are reserved for use by the 1761-NET-DNI!!

Excellent User Manual available Pub. No. 1761-6.5

Page 59: Introduction à

Ladder Programming overDeviceNet

• RSLogix 500 or RSLogix 5 software running on a PC uses the DeviceNet Driver in RSLinx to communicate to the node number of the 1761-NET-DNI. The DNI passes the programming commands over the DF1 channel to the MicroLogix, SLC-500 or PLC-5 processor. On-line edits, uploads, downloads, etc. can be done the same as if the PC running the RSLogix software were directly connected to the DF1 channel of the processor.

PC running RSLogix 500or RSLogix 5 withRSLinx V2.0

ALLEN-BRADLEY

DF1 Channel

Or Or

SLC-500 MicroLogix

PLC-5