Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
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 Une 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 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 ! Producteur/Consommateur Controller 2 Controller 1 AL L E N - B RAD L E Y HMI P a n e l Vi e w 5 5 0 7 8 9 4 5 6 1 2 3 . 0 < F1 F2 F3 F4 F5 F6 F7 F8 F9 F1 0 - <- - - - - - - - - - - - - - - - - ' ^ < > v #1 #2 Sensor • message #1 Drive1 Drive2 Drive3 – 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 Network Specifications Physical Media Network Power Maximum Devices •24vDC power to devices •Thick & Flat trunk rated to 8 amps 64 Nodes per Network •Thin wire rated at 3 amps AL LEN-BRADLEY (Shielded Twisted Pair) Communications and Power Thick - Trunk or drop Thin - Trunk or Drop Flat - Trunk only Trunk line Distance and Baud rate 100m Max. with Thin cable 500m @ 125Kbaud (thick) 250m @ 250Kbaud (thick) 100m @ 500Kbaud (thick) (longer with Repeaters) Pa n e lV ie w 5 5 0 7 8 9 4 5 6 1 2 . 0 < F1 F2 F3 F4 F5 F6 F7 F8 F9 F1 0 3 - < -----------------' ^ < > v Device Connections T-Taps Zero-drop (Maximum 6m each) Cumulative Drop-line Budget Terminating Resistors 120 Resistors at both network trunkline ends Messaging Services Producer/Consumer High-speed I/O Programming Configuration Diagnostics Drop-line wiring Single drop Daisy-chaining off drop Branching off drop 156m @ 125Kbaud 78m @ 250Kbaud 39m @ 500Kbaud (Maximum of 6m each) Caractéristiques Physiques • 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 • • • • 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 . Cablage Devicenet rouge blanc Fil nu bleu noir +24VDC ( V+ ) CAN-H Shield CAN-L +0VDC ( V- ) • 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. Topologie Trunk Distance Tap Termination Termination Trunk Noeud Noeud Noeud Longueur du Trunk Noeud max 20 feet Noeud “drop” en branche Noeud Zero Drop Noeud Noeud P/S Noeud Daisy Chain Noeud Drops Noeud Terminaison • 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 Terminologie • “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” Cable Budget - Thick Trunk Data Rates Trunk Distance 125 Kbaud 500m (1640 ft) 250 Kbaud 250m (820ft) 500 Kbaud 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 Data Rates Trunk Distance 125 Kbaud 100m (328 ft) 250 Kbaud 500 Kbaud 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 - Flat Trunk Data Rates Trunk Distance 125 Kbaud 420m (1378 ft) 250 Kbaud 200m (656 ft) 500 Kbaud 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 Types de connecteurs Mini Quick Disconnect 18mm “Terminal Strip” Style Connector Micro Quick Disconnect 12mm Cable Sealed T-Taps • Tee Tap – • Keyed left & right Field Installable trunk line connectors – • Trunk line segments – – screw type • Drop lines – – – mini or micro molded connectors up to 20ft mini, micro or pigtail at sensor molded minior micro connectors various lengths KwikLinkFlat Cable • Requirements – – – – – – Modulaire Faible cout Temps d’installation minime Format compact Compatible avec les media existants NEMA 6P & 13, IP 67 Multi-Port Sealed Media • DevicePort Multiport Tap – micro quick disconnects – various configurations • DeviceBox Multiport Tap – 2, 4, 8 (to Trunk) DeviceBox™ DevicePort™ Drop Drop Drop Trunk Trunk Typical Sealed-Style Taps Tee Taps Field Installable trunk line connectors -screw type -crimp type Trunk line segments -molded mini-connectors Drop lines - molded connectors - 0 to 6 m (20 ft.) - mini or micro at device Multiport Taps Open Style Taps Trunk • Dropline Zero length drop using 1787-Plug10R with probe cable support Open Style Device Open Style Device Sealed Control Enclosure Open Style Device Open Style Device Thick Cable Description • • • • • 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 DeviceNet Thick Cable Beldfoil Aluminum/Polyester Shield Vinyl Jacket .480” O.D. Blue & White Data Pair Datalene Insulation Polypropylene Fillers 18 AWG. Tinned and Stranded Copper Conductors 65% Coverage Stranded Drain Wire Tinned Copper Braid Shield Tinned Copper 18 AWG. Thick Cable Grey PVC Yellow CPE Belden 3082A 3083A AB number YR-29790 YR-39659 15 AWG. Tinned and Stranded Copper Conductors Red & Black DC Power Pair PVC/Nylon Insulation Thin Cable Description • • • • • 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 DeviceNet Thin Cable Beldfoil Aluminum/Polyester Shield Vinyl or CPE Jacket .270” O.D. Polypropylene Fillers Blue & White Data Pair Datalene Insulation Overall Mylar Tape 24 AWG. Tinned and Stranded Copper Conductors 65% Coverage Tinned Copper Braid Shield Thin Cable Grey PVC Yellow CPE Belden 3084A 3085A AB number YR-29832 YR-39660 Stranded Drain Wire Tinned Copper 22 AWG. 22 AWG. Tinned and Stranded Copper Conductors Red & Black DC Power Pair PVC/Nylon Insulation KwikLink 4-wire Flat Cable DeviceNet Flat Media DeviceNet Cable CAN_H Auxiliary Power Cable User User defined 1 defined 2 CAN_L 0 Vdc +24Vdc DeviceNet Power, 8 Amps Max. +24Vdc 0 Vdc Output Power, 8 Amps Max. Media Features • 600V, 8A rating • Physical key • Fits in 1” conduit • Works with existing devices • TPE / Santoprene jacket • Highly flexible Network Grounding • 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+ .. . Power Tap V- . . V+ 24 VDC Power Supply Single Supply Configuration up to 500 m up to 500 m up to 500 m N32 N1 power supply N33 N64 • 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 Two Supply Configuration ( Current Boost ) up to 500 m N1 Power Supply N32 N33 Power Supply N64 • 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) Topology for Power Along the Bus 24 V Power Supply Node Optional Second Supply 24 V Power Supply Node V+ Power Conductor V- Power Conductor CAN-H, CAN-L, Shield Node Node 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 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 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 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 ) 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. Replacement Original Device Node Recovery Configuration Recovery #55 #63 #55 Replacement Device #63 DeviceNet Products A-B DeviceNet Products DH485/DH+ DH+/ControlNet/Ethernet SLC-5/02, 5/03, 5/04 1747-SDN Scanner PLC-5/xx DeviceNet RIO DeviceLink I/O w/standard sensor 1771-SDN Scanner Physical Media 1770-KFD RS-232 PC I/F DeviceNet Config s/w DeviceNet Manager V3.04 1203 DeviceNet Interface Series 9000 Photoelectric 1794-ADN Adapter for Flex I/O Third Party Third Party ThirdDevices Party Devices Devices 800T RediSTATION AdaptaScan Bar Code Reader SMP3 SMP-3 Smart 1305, 1336 Drives Motor Protector, SMC Dialog Plus DeviceNet Products 1784-PCIDS Scanner Card SLC-5/02, 5/03, 5/04 871-TM Prox 18mm & 30mm 1761-NET-DNI PanelView 550, 900 DTAM Plus DTAM Micro ALL EN-BRADL EY P a n e lV ie w 5 5 0 PLC-5/xx 7 8 9 4 5 6 1 2 3 . 0 < F1 F2 F3 F4 F5 F6 F7 F8 F9 F1 0 ^ < 1771-SDN/B Scanner 1747-SDN/B Scanner - < -----------------' > v physical media A-B A LLE N -B R A D LE Y 1784-PCD PCMCIA I/F RSServer WIN DNet16 RSNetworx for DeviceNet SMC PLU S ArmorBlock I/O and Low Profile Armor Block I/O DeviceView IMC S-Class 1394 GMC Smart Motor Controller Dodge EZlink sensorized bearing 160 Smart Speed Controller 825 Smart Motor Manager FlexPak 3000 & GV3000 Drives 1770-KFD DETAILS 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-topoint connections to devices. 1770-KFD contains a built in terminating resistor for point to point use. 1784-PCD PCMCIA DeviceNet Interface Card 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 FlexI/O DETAILS 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 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 Flex I/O 1794-OB16 and Other Discrete Outputs Data Usage Consumes 1 word of output data word 0 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) 871TM SmartProx DETAILS 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. 871 TM Prox Data Descriptions Sensor Output – Set when target Detected. : Too Close Definition – Target is within 1.5mm of face. Latched on until another target detection 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 pass through user configured Too Far Min Margin point. The default value of the Too Far set point is -20% of the switch point, but can configured from 0% to -20%. The user may also setup this diagnostic as Static to Dynamic. In static mode the diagnostic is set whenever the target pass in the defined region, while in dynamic mode the diagnostic is latched 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 pass through user configured Always In Max Margin point. The default value of the Always In set point is +20% of the switch point, but can configured from 0% to +20%. This diagnostic 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 Preset time. Counter Output – Counter Preset value reached Analog Output – Analog value for relative distance (0 – 255) 871 TM Prox Data Details Consumes 1 bit of Strobe output data or 0 bytes of COS data Strobe bit clears timers and counters when set to a 1. Produces 2 byte of Strobe or COS data Byte 0 Bit 0 Sensor Output Bit 1 Diagnostic Bit 2 Coil Operational Byte 1 Bit 0 Bit 1 Bit 2 Bit 3 Too Close Bit 4 Too Far Bit 3 Bit 4 Analog Output Bit5 Always In Bit 6 Motion Detect Bit 7 Counter Output Bit5 Bit 6 Bit 7 CompactBlock I/O DETAILS 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 1791D2.1. CompactBlock I/O • CompactBlock I/O for the DeviceNet communication network is a compact, low-cost block I/O for use in a variety of distributed applications • Delivers ease of installation and expandability in a compact, 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 CompactBlock I/O Details Modules Base Input Base Output Base Combination Base input with expansion input Base output with expansion output Base input with expansion output Base output with expansion input Combination module with expansion input Combination module with expansion output I/O Points 16 Inputs 16 Outputs 8 Input/ 8 Output 32 Input 32 Output 16 Inputs/ 16 Outputs 16 Outputs/ 16 Outputs 24 Inputs/ 8 Outputs 24 outputs/ 8 Inputs Produce Consume ( Rx Size ) ( Tx Size ) 2 bytes 0 bytes 1 byte 5 bytes 1 byte 3 bytes 3 bytes 4 bytes 2 bytes 0 bytes 2 bytes 1 byte 0 bytes 4 bytes 2 bytes 2 bytes 1 bytes 3 bytes Notice that for every 8 inputs a byte of data is added to the Rx size and for every 8 outputs a byte 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 a status for the expansion module. Bit 7 = 1 means expansion module bad or missing, bit 7 = 0 means the expansion module is functioning correctly. 1761-NET-DNI DETAILS 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 1761-NET-DNI Fun Facts 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!! Bit 7 of LSB of Input Data Bit 7 of LSB of Output Data || Excellent User Manual available Pub. No. 1761-6.5 ( ) Ladder Programming over DeviceNet • 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. PLC-5 SLC-500 MicroLogi x Or PC running RSLogix 500 or RSLogix 5 with RSLinx V2.0 DF1 Channel Or