1756-AT007-EN-P, Integrating DeviceNet into
Contents
1. Gere Dereka Device Fl Analog T IHCHARA Anak Fe Analog INC HAMA k Test Flex Analog IHCHANA WORDS Assunedio Chanrel 5 ai IHE HAMA Dw E IF IET DRET Bies IF WORDU HS WORDS IF nsleg INC HANA Anslog DRE T IHCHANA 1 Select an channel in the Est bes ot ight and precs the China bolton henna Block Select the channel containing thir channel Bock n the kt bow ard price Ohrid Block butten Show Parme Hanes Creel Hep 8 Select the appropriate Module Name from the drop down list to associate this input channel with the correct device 9 Click Assign Channel Block to complete the association Your screen should look similar to the above picture when you are finished You can chose any available channel to assign it does not need to be channel 5 10 Select the Input Data Location tab DMFTIF DASET INEHAN Block INCHAMBA 1 Parameters Project Discrete Dala Block Fins Configuration Parameters Main input Data Location Numeric Input Cong Assembly 7 Assembly Dllset Bir 24 Assn 244 Bad heres Cantic Bad Using the 1756 DNB and ProcessLogix to Communicate with Fl2. D ORD amp risdag 1 Charred Alar Select an channel fist at igh and press the Assign Chamel Block button above Urag Channel Block Select the channel contsning this channel block in the let and press Ihe Channel Bleck busan above See woe ua 15 Analog ONE T OUT CHAS 17 Dip Dig Dur Show Parameter Names Cancel Heb 3 Assign the block to the DNET DEVICE just as you did for the Input channel 4 Select the Output Data Location tab DAE TIPE T_T ON Block DET DUTCHAMRA Parameters Fro Dicis Da Block Pre Configuration Puare Output Data Location Humes the axe and size of the channel dats which is contained configurations are detected atte block Assambip Coe Et E Leng h Fal O Bod Cong Bed utut Status 5 Enter the correct information to match the Output Data Format table on the Module Configuration tab for your device Refer to the example on page 3 18 In our example this data matches the location of OEA that we called out on page 3 18 This data MUST match one of the entries in the Output Data Format table in the DNET_DEVICE block in order for the output channel to operate correctly 6 Select the
3. Dime Date Configustion Fersneters Moniving Block Preterences Mam Munere Contin Dizcoste Input Demie M cher Input Bed Opinn 18 OFF E ae ico Ra e IAE 4 In IG 8 3 10 111 13 14 i5 E Show Parameter Hames mcs Because we referenced the entire Input assembly in the Input Data Location tab we must set the byte and bit offsets here to point the input block to the correct space in the memory of the DNB We know that the input of the IB32 is offset 9 words 18 bytes from the beginning of the input assembly see example page 3 13 This setup enables each individual flag to be read through one pin on the block 3 After you have finished enabling channels and assigning appropriate offsets click OK to save changes and exit the form Output Channels 1 Select and set up a new DNET_OUTCHAN block just as you did for the OE4 however ONLY set up the Main tab 2 Select the Output Data Location tab D5ETIFDAET OLITCHAN Block DIET Dig Out Parameters Project Dwele Das Pine Configuration Parameters Main Output Dutput Config Sead lhe and sis of the channel data which is conlaned vahin th cdelecked aller
4. Empty Si a E From the Module Configuration tab each module can be configured channel config mode etc The two Generic Modules seen here are 1794 1 32 and a 1794 OB32 Even though RSNetworx does not recognize these modules we are able to use them via DeviceNet Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 13 9 Click the Summary tab to see the data mapping for each module 1794 008 flex 1 11 Adapter P 9 Module Sisus fond Eu Bot 1 1794 06478 4pl Analog ZE Deran Modia E Geren Modules PHF Isolated High Res dim AL 1F OFA isolated High Rez Apr a Engi Sii 7 Empty Sint C C 4e Ooh i Total inp Eres Total Bytes DA Total Input aede ELE Total Output onde 12 The Summary tab explains exactly where you need to point to in the DeviceNet interface modules memory to access each Flex I O module You now have sufficient data from RSNetworx to setup your DNET DEVICE block properly in ProcessLogix Publication 1756 AT007B EN P August 2003 3 14 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 Create a DNET DEVICE Now that you have a working DNET_IM module you need to create a DEVICE that will be associated with the new DNET IM 1 Go to the Library tab window 2 Lo
5. Change the name in the column on the right to the new Find Replace desired name or accept the default lt Back Cancel Help TIP To create a new DNET_IM you can use the menus instead of dragging the onto the CEE Select File gt New gt I O Modules gt DNETIF gt IM DeviceNet Interface Module Control Builder Project File Edit View Insert Tools Operate Options Window Help Slej Faje 4 1 2 12 Controllers Redundancy Module Open Tree Window Open Close WEE DNET DEVICE Generic DeviceNet Device S Interface Modules gt FBUSIF IM DeviceNet Interface Module Login to Server External Servers IO gt Page Setu Control Module rer i i gt Sequential Control Module pM unc UU RAO Export Wizard RAIL IO HAZ gt Import BASE Exit DNB ff DNET_DNB_2 1 1717 eg FLEX_23 Then assign it to the appropriate CEE 4 Click Finish 5 Expand the CEE 6 Expand the I O modules 7 Double click on the DNET_IM that was just created Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 3 5 You will see DeviceNet Interface Module MEN 8 Create a name 9 Enter the rack address of the 1756 DNB module that you want to communicate with The other fields are used for
6. Pe Preface 1 av Eta ated RR qr EN Vat Preface 3 Terms and Type Preface 3 Chapter 1 here Stes epe tie opp TTT E TTI 1 1 General Checklist to Configure 1756 DNB in ProcessLogix 1 1 1756 DNB DeviceNet Interface 122 Example Topology for Integrating DeviceNet into RAO od pire 1 3 DeviceNet Interface to a Non Redundant Controller 1 3 DeviceNet Interface to a Redundant Controller 1 4 System Performance Capacity and Topology Specifications 1 5 Chapter 2 Device Net rat qun quee ate area ded qoin iet 2 1 DONE LILI 2 act SE UC E 2 1 E uncHonmbloCck Seb situ ee SR ye OGLE B eae 22 Mc 2 2 DNE DEVICE a aiias dett EUN e Red 2 DNET INGHAN cae ck 252 DINE OI 2 3 Gontiourationm cs SSE 2 3 ATCP PE 2 3 DAET GDA 2 3 DeviceNet 2 3 DeviceNet Network Configuration 2 3 Chapter 3 Se 3 1 Getting Started in Control Builder 3 1 Creatine and Configuring the 3 2 Creating Modules bees an ae nie does 2
7. assigned 4 words of data Data Offset Double Words 0 Data Offset Bits 0 Length Bits 80 5 words 2 bytes per word 8 bits per byte 80 bits is actually 5 words of data the fifth word is not used in this example and included for so that all bits of data were accounted for appears as Generic Module This module appears next an offset of 80 bytes corresponds to 2 32 bit double words and 16 bits and is assigned 2 words of data Data Offset Double Words 2 Data Offset Bits 16 Length Bits 32 2 words 2 bytes per word 8 bits per byte This module has an offset of 112 80 plus 32 and will complete the output assembly with 5 words of data Data Offset Double Words 3 Data Offset Bits 16 Length Bits 80 5 words 2 bytes per word 8 bits per byte The entire output assembly 192 bits is accounted for and each output module has a separate space 14 15 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 19 Save this configuration by clicking OK once you have finished entering this data Download and activate the DNET DEVICE Once these steps are complete Input and Output channels may be configured to map to these locations Configure Input and Output Create anew CM Channels Go to the Project tab Click File gt New gt Control Module This new CM should appear in the Unassigned section of the Project tab Give it a unique name ours is cal
8. consideration when applying products such as those described in this publication Reproduction of the contents of this copyrighted publication in whole or part without written permission of Rockwell Automation is prohibited Throughout this publication notes may be used to make you aware of safety considerations The following annotations and their accompanying statements help you to identify a potential hazard avoid a potential hazard and recognize the consequences of a potential 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 about practices or circumstances ATTENTION P that can lead to personal injury or death property damage or economic loss IMPORTANT Identifies information that is critical for successful application and understanding of the product Allen Bradley is a trademark of Rockwell Automation Preface Introduction ProcessLogix R510 0 Function Block Set Architecture Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 Table of Contents lmpotant User Ta su ao atid ae ii Minimum Hardware Requirements for ProcessLogix R510 0 Preface 1 ProcessLogix Online User Documentation and Knowledoe xu a dau sists onthe dive eects Preface 1
9. A General Checklist to Configure a 1756 DNB in ProcessLogix v You must have Slot locations of 1756 DNBs that you plan on monitoring through ProcessLogix e Controller locations e Device Addresses Experience programming Function Blocks in Control Builder e Attend hands on training classes e Obtain help from a knowledgeable source Identified or installed the 1756 DNB 1756 DNB DeviceNet The 1756 DNB Interface Module e provides a communication bridge between ControlNet and DeviceNet utilizes the Rockwell 1756 form factor which is native to ProcessLogix can be located in either the ProcessLogix Controller Rack or I O Rack supports the three DeviceNet baud rates 500 KBps 250 KBps and 125KBps is configured from a PC running the RSNetWorx for DeviceNet configuration tool connected to either DeviceNet through a 1770 KFD Interface Module or ControlNet through a CNB input and output messages from to the various DeviceNet devices are bundled at the ControlNet level into 2 assemblies data objects which ate available for transport across ControlNet from to the 1757 PLX52 Controller e as configured with the DeviceNet network configuration all input data messages from DeviceNet input devices are packed into a 496 byte input assembly Input data is bound from input devices to the 1757 PLX52 Controller e as configured with the DeviceNet network configuration all output data messages to DeviceNet output devices are packe
10. Control Execution Environment IOC Input Output Channel IOM Input Output Module IOC FB Input Output Channel Function Block IOM FB Input Output Module Function Block Publication 1756 AT007B EN P August 2003 Preface 2 Table P 1 Terminology used in this Application Technique Term Definition DNET DeviceNet Interface Module specifically the 1756 DNB ODVA Open DeviceNet Vendor Association They provide comprehensive DeviceNet support and documentation contact www odva com You can also refer to www theautomationbookstore com to order or download Devicenet documentation from Rockwell such as the DeviceNet Planning and installation Guide DeviceNet Overviews and Selection Guides and well as a DeviceNet Starter Kit EDS Electronic Data Sheets 0115 that RSNetWorx requires to be able to identify the devices You can obtain these files in many ways Shipped with device through the manufacturers web site and for many are at www ab com Publication 1756 AT007B EN P August 2003 Conventions Preface Terms and Type Representations The following table summarizes the terms and type representation conventions used in this Guide Term Type Representation click click on click button name double click drag right click select F1 lt Ctrl gt lt C gt File gt New gt D setup exe lt Click left mouse button once Click Browse Assumes cursor 15 positioned on object or selection Click
11. Numeric Output Config tab Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 23 ONETIF ONET_OUTCHAN Block ONET_OUTCHANA Parameters Project E X Discrete Dats Black Fin Configuration Parameters Monkonng Parameters Black Preferences Main Dup Data Location Humenc uutCenh g Discrete Output Numeric Dats BETTE UNMSIGND WORD_SIGHED WORD SIGHED WOAD_SIGHED WORD_UNSIGND WORD SIGHED WORD SIGNED AWDRD SIGHED 8 0 0 0 0 0 0 o This tab is exactly the same for an INCHAN as it is for an OUTCHAN Byte Offsets are still relative to the data space selected in the Output Data Location tab In this example we are writing to the first channel of the 4 with pin 4 enabled 7 Select the desired number of numeric outputs for this block and set offsets accordingly if you are using discrete modules see the next example on page 3 23 8 Click OK to save changes and exit block parameters Set up communication with the 1794 1832 1794 0 32 pair Input channels 1 Select and set up a new DNET_INCHAN Main and Input Data Location tabs just as you did for the IES Publication 1756 AT007B EN P August 2003 3 24 Using the 1756 DNB and ProcessLogix to Communicate with Flex 0 2 Select the Discrete Input Config tab BET IF ET IPCHAN Block Digital In Parameters Project
12. controller rack of a redundant controller configuration However in non redundant applications the module can be deployed in either the controller rack or a downlink I O rack e The communication update interval between the DeviceNet Interface and the DNET_IM block is not configurable but is dependant upon the Base Execution Rate of the CEE in which the block is running Table 1 2 CEE Base Execution Rate Output Rate e Up to four 1756 DNB modules can reside in the local rack and or in remote rack This configuration has been tested and is currently supported e The DNET IM block supports communication to a maximum of 64 unique DeviceNet devices identified by a unique network address within the valid network address range of 0 63 e The DeviceNet Interface imposes the following constraints which may restrict the number of DeviceNet devices supported The sum of all input message sizes from all input devices cannot exceed 496 bytes The sum of all output message sizes from all output devices cannot exceed 492 bytes Regarding the existing system limit of 64 IOM connections per PLX and 24 IOM s per downlink CNB The IM block is the equivalent of 2 IOM s in this calculation The DNET DEVICE blocks that are associated with a given DNET IM block are not counted in these limits Only the associated DNET_IM block 15 counted e Supported DeviceNet baud rates 500 KBps 250 KBps and 125K Bps Publica
13. data assembly Rb A E 1 General Module Input arz ADR Surman 02 17 24 143 Dae 0 oUm w Memes T 0 H sum o ETT OND Mr mit 1 TET Flies Adag HE 173 amp ADH D From RSNetworx the data assemblies are assigned as one large chunk The memory space of each individual module is not delineated in the memory of the DNB The output assembly for the ADN has these characteristics Data Offset Double Words 0 Data Offset Bits 0 Length Bits 192 24bytes 8 bits per byte To see how the individual Flex I O modules are mapped you need to view the memory of the ADN Publication 1756 AT007B EN P August 2003 3 12 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 7 Double click on the ADN icon in the network display screen to see its configuration LTHAH flex 1 0 Adapter General Control Configuiation Summa 4 1794 ADM Flex 1 0 Adapter Address H Dee Belen Panay Vendor Flockwell Automation Alen Brede 1 Communication Adapter 12 Deck 170 1 Res 2100 1740648 4 1 Analog Output E Genere 52 Module Shad Empty Sint
14. device because you can read data from the DeviceNet interface module as many times as you want it does not interfere with the communication to and from the device IMPORTANT This screen may read Data Offset Words however this 15 a reference to a data size of 32 bits and is changed in R510 0 to read Data Offset Double Words Data Offset Double Words 0 Data Offset Bits 24 Length Bits 304 38 bytes 8 bits per byte Publication 1756 AT007B EN P August 2003 3 18 Using the 1756 DNB and ProcessLogix to Communicate with Flex 0 13 OE4 OB32 OF4I Publication 1756 AT007B EN P August 2003 For the output data assembly you need to separate the large chunk of data into module specific chunks You need to have one space for OEA data one space for the OB32 data and one space for the OF4 data This allows you to wtite to all three data spaces simultaneously with no overlap The scanlist information from RSNetworx tells us the size and location of the entire chunk of data Data Offset Double Words 0 Data Offset Bits 0 Length Bits 192 24 bytes 8 bits per byte Information from the 1794 ADN further defines the spaces of memory to create Refer to the Summary tab example in Step 9 on page 9 Based on the data shown here this configuration provides access to each Flex output module Following is the data provided in the example This module appears at the beginning of the output assembly and is
15. 3 DeviceNet Interface to a Redundant Controller Proc ess Logix Sapponded or PC Sener CorndtniNe RSHetillorcfor wa GHE Devic eH et Configuration Tool Sup enaa Mefwork Module CHE PLYS Red M od Med wor CHE 176 DHE Module De woe et Met work Device Vet Deuces Series Red STATION 1305 Drive anm Rack F hotoey The 1756 DNB is the DeviceNet Interface module e The PC with the RSNetWorx Configuration Tool is used to configure the DeviceNet Interface Module and the DeviceNet network e Ina redundant configuration the DeviceNet Interface resides in the I O chassis There are no Ethernet modules qualified for use with SRM s e Although only one DeviceNet Interface is shown a PLX controller can host multiple modules Refer to 1 5 5 232 S eral Link System Performance Capacity and Topology Specifications EN Root 20073 gai CEEFB75 33 Project 48 Monitoring Introduction 1 5 Following are the performance capacity and topology specifications applicable when implementing the DeviceNet Interface in a ProcessLogix system The information in this section is intended to supplement the ProcessLogix Installation and Upgrade Guide For more information about Integrating DeviceNet and ProcessLogix navigate in Knowledge Builder to CCL DeviceNet Interface The 1756 DNB 15 not a redundancy compliant device and therefore cannot be introduced into a
16. 42 Locate Mapping Data from 5 3 8 Create a DNET DEVICE m hy esee 3 14 Configure Input and Output 8 3 19 Crear a ae oet aE aT 3 19 Set up communication with the 1794 IE8 1794 OF4 pair 3 20 Input MANN eee 3 20 Ourpue Channel lt i toe atte sd 3 21 Publication 1756 AT007B EN P August 2003 Table of Contents 2 Set up communication with the 1794 IB32 1794 OB32 pair 3 23 Input 3 23 Chane eats wees 3 24 Set up communication with the 1794 IF41 1794 OF4I pair 3 25 Input 3 26 3 26 Chapter 4 Troubleshooting PAB toa NE E TE T ERR T T E E ET E EET 4 1 4 1 DNB Eror E 4 1 SO A Cate 4 1 RoNetwor for 4 1 Chanoine lard ware a stich a pes EE PE VEG 4 1 CODEC 4 1 Device is red but IM is green 4 1 Configuration mismatch error on download 4 1 Data not reflected in module or device 4 1 Backcover Rockwell Automation Support BC Installation aus io E e roe ead eee Cae RR
17. AT007B EN P August 2003 3 10 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 Publication 1756 AT007B EN P August 2003 Your screen should display a network similar to this one 3 Double click the 1756 DNB icon and select the Scanlist tab 6p T5b DAD A E A xl General Scenist input Op ADR Sunmar ewaisble Devices Span nz 1794 Deve 04 PsghiSight Standerd CEASE 9 Automan on Add Mode Actives Electamc Upload bom Scan 4 Device Type bo Scanner _ ic IR Haor Revision Parameters Fier A 1794 ADN Flex I O DeviceNet adapter is already in the Scanlist for 1756 DNB If it is not use the arrow buttons to assign it to your DeviceNet interface module 4 Click Apply if changes have been made to download these changes to the DNB module 5 Click on the Input tab to access the mapping data for the input assembly of the DNB 1 1 alal 16 aj Mene Data Start 0 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 11 The Input tab shows where the data is located in the DeviceNet interface modules memory The 1794 DNBs input assembly has these characteristics Data Offset Double Words 0 Data Offset Bits 24 Length Bits 304 38 bytes 8 bits per byte 6 Click the Output tab to view the output
18. Allen Bradley Integrating DeviceNet into ProcessLogix 1756 DNB 1757 Series ProcessLogix R510 0 and above Application Technique os MAS Rockwell Automation Se LLL Important User Information Because of the variety of uses for the products described in this publication those responsible for the application and use of these products must satisfy themselves that all necessary steps have been taken to assure that each application and use meets all performance and safety requirements including any applicable laws regulations codes and standards In no event will Rockwell Automation be responsible or liable for indirect or consequential damage resulting from the use or application of these products Any illustrations charts sample programs and layout examples shown in this publication are intended solely for purposes of example Since there are many variables and requirements associated with any particular installation Rockwell Automation does not assume responsibility or liability to include intellectual property liability for actual use based upon the examples shown in this publication Allen Bradley publication SGI 1 1 Safety Guidelines for the Application Installation and Maintenance of Solid State Control available from your local Rockwell Automation office describes some important differences between solid state equipment and electromechanical devices that should be taken into
19. BC New Product Satisfaction BC Publication 1756 AT007B EN P August 2003 Preface Minimum Hardwa re The DeviceNet Interface Library is only supported by ProcessLogix R510 0 Requirements for ProcessLogix R510 0 Server Software must be installed on a PC that is ProcessLogix R510 0 specifically qualified Use of any other PC variations will render the standard watranty and support agreement null and void ProcessLogix Online User Documentation Knowledge Builder ProcessLogix online user documentation is included with your ProcessLogix system in browser format through the Knowledge Builder Most of the documents may also be ordered individually through Rockwell Automation in print format visit us at www theautomationbookstore com Knowledge Builder provides the user with task based documentation within the Server and Client stations and may be accessed while using any of ProcessLogix s software programs Knowledge Builders internal links and search functions allow the user to access process relevant information and references References to Knowledge Builder throughout this document are illustrated as Navigate in Knowledge Builder to Ethernet Implementation Guide gt Configuration Setting Up Drivers and IP Addresses for more information Terminology Table P 1 Terminology used in this Application Technique Term Definition CNB ControlNet Interface Module ICP Integrated Control Platform
20. Download the CPM This procedure will create a representation of the 1756 DNB Module in the I O list for the CPM 1 Select the Library tab of x INCHANNEL LOGIC REGCTL SEM UCHIF UTILITY RAIL ID H amp 7 DNETIF PBLISIF RAIL ExCHANGE PULSEINPUT Bis Control Builder Library DNETIF Using the 1756 DNB and ProcessLogix to Communicate with Flexl O 3 3 2 Find and expand library Library 05 UTILITY RAIL ID HAZ DEVICE IM 21 Wh DNET_OUTCHAN RAIL 10 FBUSIF ECHANGE PULSEINPUT a i Project 45 Monitoring Library You see File Edit View Desert Took Operate Options Window Help elal E ERNST Project EE 20072 ceEFB S x Unassened Library an scu 9 Se UTILITY 10 DEVICE E m DMET_INCHAH ONET_OUTCHON PEUSIF 10 FBLISIE go EXCHANGE PRIMARY MGR Select the and drag it on to the CEE in the Tree Window Project Tab Publication 1756 AT007B EN P August 2003 3 4 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 You see Mame New Function Blacks o Sue IMT 17 IMT
21. Snapshot Selected and its 5 Sis snes Function Blocks 2 Selected CEETs TOM CMs Applicable Function Blacks 43 Project 5 Moni Activate Selected GEE S Stalls 19 Go to the I O section and verify that the DNET_IM is green 20 Double click on the selected DNET_IM Publication 1756 AT007B EN P August 2003 Using the 1756 DNB ProcessLogix to Communicate with Flex 1 0 3 7 DNET SLAVE 02 07 DNET SLAVE 02 08 51 02 09 3 Buletim 160 13 COMPAC_59 js COMPAC DNB 2 BASE nex 23 24 25 H FLEX_26 eH nex 27 nex 28 Publication 1756 AT007B EN P August 2003 3 8 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 21 Go to the Command Status tab and change the Command Register from Idle to Run Mode DNETIF DNET_IM Block DNB Parameters Monitoring inm zen kom Locate Mapping Data from RSNetworx RSNetworx for DeviceNet can indicate where all data is mapped 1 Go to RSNetworx for DeviceNet 2 Go Online by clicking this button EJ in toolbar Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 3 9 for DewiceNet Ede We Meteor Gerace Geegnostics Took Help CICA RI X Ha e ME xj Hardware Riot Sighi Standard Publication 1756
22. ain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1756 AT007B EN P August 2003 Supersedes Publication 1756 07 September 2002 PN 957824 87 Copyright 2003 Rockwell Automation Inc All rights reserved Printed in the U S A
23. and Other Comments You can add additional comments on the back of this form Your Name Location Phone Your Title Function Would you like us to contact you regarding your comments ___No there is no need to contact me A Yes please call me ___ Yes please email me at A Yes please contact me via Return this form to Allen Bradley Marketing Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Phone 440 646 3176 Fax 440 646 3525 Email RADocumentComments ra rockwell com Publication ICCG 5 21 January 2001 PN 955107 82 Other Comments PLEASE FASTEN HERE DO NOT STAPLE PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Allen Bradley RELIANCE ELECTRIC M ROCKWELL SOFTWARE e DODGE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Rockwell Automation Support www rockwellautomation com Rockwell Automation provides technical information on the web to assist you in using our products At http support rockwellautomation com you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuratio
24. are reading in the general ADN status word and the first 2 bytes of data from the IES Refer to page 3 13 for RSNetworx data 13 Select the desired number of numeric inputs for this block and set offsets accordingly if you are using discrete modules see the next example on page 3 23 14 Click OK to save changes and exit block parameters Output Channel 1 Drag and drop a DNET_OUTCHAN block from the Library tab 2 Double click on the block to display the block parameters form Publication 1756 AT007B EN P August 2003 3 22 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 DNETIF DMET Block Dig Qut Parameters Project Discrete Dara Block Fins Configuration Parameters Parameters Black Preferences Main upuDatalocain Numeric Output Config Decree Output Config Numeric Data Channel Block Configuration Channel Hane ET 7 Channel Block to 10 Mode amp xrigement Module Mame Te zi Ov Module Generic Device Channel Humber Channel Hame Anal INCHANA ORD Flex Analog WORDS 42 Flex Ankia MCHANA Assigned to Module Test 21 Di 2 Flax Dig DNET Digia ln Assigned ta Channel 17 IFl_Analog signed Analog wA DU 53023 WORDS IF Andog
25. black E Assembly CH zen Bi IMEEM Actemblp Lenght 7 Fed Gutput Ststu Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 25 3 Enter the correct information to match the Output Data Format table on the Module Configuration tab for your device Refer to the example on page 3 18 In our example this data matches the location of the OB32 described on page 3 18 This data MUST match one of the entries in the Output Data Format in the DNET_DEVICE block table in order for the block to operate correctly 4 Select the Discrete Output Config tab DETIF DMET OUTCHAN Block ONET_Dig_Out Parameters Project E Discrete Data Block Configuration Parameters Monkonng Parameters _ Black Preferences Main Qutput Data Location Numeric Config Discrete Conti Data OPEL Configuration Enable Bome EEE REBEE TAA SISTERS ICI ST ST e cn m 3s Show Names Cancel Helo Because we referenced a small chunk of the Output data assembly the information for the OB32 starts at the beginning of that chunk The byte and bit offsets only need to be set to point to places within the data space we have already referenced This setup enables each individual flag to be r
26. cate DNETIF and then DEVICE You see Conte Builder Library Edt View Fest Took Operate Options inde Help sie elles Sle tle el px 215 ET EET p o mu BULLT amp 3 19 ONET_COMPAC 55 00 ri DB 02 02 DMB 02 03 DNET DMB n H DMB ne 05 DWMB8 D 05 02 07 D amp B 02 09 Se 02 09 HS DNET DUTCHAN a RAIL 10 go EXCHANGE gH PULSEINPUT For Help press F1 Publication 1756 AT007B EN P August 2003 3 Select the DNET_DEVICE and drag it up to the CEE in the Project tab window 4 Click File gt New gt DNETIF gt DEVICE Using the 1756 DNB and ProcessLogix to Communicate with 1 0 3 15 5 Give yout DNET DEVICE a unique name Marie Mew Funchion Black s wILE Test J DNET_DEVICE 1069 Test 21 DV 2 Change the name in the colum on lhe right bo the new _ desired name or accapt the default ind Fieplace Cancel Halp 6 Click Finish to continue for this example the name of the device is Test 21 DV 2 7 Double click on the new icon for Test 21 DV 21in the project window Publication 1756 AT007B EN P August 2003 3 16 Using
27. d into a 492 byte output assembly Output data is bound from the 1757 PLX52 Controller to the output device Publication 1756 AT007B EN P August 2003 Example Topology for Integrating DeviceNet into ProcessLogix R510 0 Introduction 1 3 The DeviceNet Interface module can be supported in both Redundant and Non Redundant Controller topologies The following diagrams depict the intended ProcessLogix DeviceNet interface in these hardware topologies DeviceNet Interface to a Non Redundant Controller Supported PC with via RS Netlfllorefor DeuiceHet Proc es uni 25 232 Serial Lirk CHE 176 DHE Module FD Interes Module Supervisory Metwork Devic eet Network Device vet Devices Series 9000 RediSTATION 1305 Drive FLEX 16 Photoeye Rack The 1756 DNB is the DeviceNet Interface module e The PC with the RSNetWorx Configuration Tool is used to configure the DeviceNet Interface Module and the DeviceNet network e Although ControlNet is depicted for the supervisory network Ethernet supervisory networks are also possible e In a non redundant configuration the 1756 DNB may reside in the controller chassis or in the I O chassis e Although only one DeviceNet Interface is shown a PLX controller can host multiple modules Refer to 1 5 Publication 1756 AT007B EN P August 2003 1 4 Introduction Publication 1756 AT007B EN P August 200
28. e DNETIF library requires the purchase of one license for each interface module used DeviceNet Wizard The ProcessLogix DeviceNet Wizard takes the report file of the network created in RSNetworx and creates Device and IM blocks that can be imported into ControlBuilder Navigate in Knowledge Builder to ProcessLogix 510 gt Help gt DeviceNet Interface for detailed information DeviceNet Network Configuration The DeviceNet network is configured using the RSNetworks for DeviceNet configuration tool This tool including supporting documentation is putchased as a separate license Although this document includes some examples of DeviceNet configuration it does not attempt to duplicate the information provided in the RSNetworks for DeviceNet or any other DeviceNet documentation Publication 1756 AT007B EN P August 2003 2 4 ProcessLogix R510 0 Function Block Set Architecture Notes Publication 1756 AT007B EN P August 2003 Chapter 3 Using the 1756 DNB ProcessLogix to Communicate with Flex 1 0 Prerequisites The following checklist describes what is required of you before you begin integrating a DeviceNet device into your ProcessLogix R510 0 system Zee eee Getting Started in Control Builder 3 1 Creating and Configuring the CPM 2 2 Creating Module 252 IN Locate Mapping Data from RSNetworx 3 8 EN Create a DEVICE 3 14 Configure Input and Output Channels 3 19 Getting Started i
29. ead through one pin on the block 5 After you have finished enabling channels and assigning appropriate offsets click OK to save changes and exit the form Set up communication with the 1794 IF41 1794 OF4I pair 6 Follow the same procedure as described in the section Set up communication with the 1794 IE8 1794 OE4 pair on 3 20 Below example screens Publication 1756 AT007B EN P August 2003 3 26 Using the 1756 DNB and ProcessLogix to Communicate with 1 0 Input Channels DMETIF DMET INCHAN Block DNET_INCHANA_1 Parameters Project Discrete Data Configuiation Parameters Monitoring Parameters Black Preferences Main Input Dats Location Humane Inpul Discrete Input Config Husai Dala PY Configuration Descspior 24 chai SIGHED EYTE UNSIGHD BYTE UMSIGND BYTE UNSIGHD WORD SIGHED WORD SIGHED WORD SIGNED WORD SIGHED Pit ol re The IF4 is offset by 22 bytes 11 words 2 bytes per word Output Channels DETIEXWSET OLITICHAN Block Parameters Fro jer Dime Da Conhpurstion Parameters Sec the ond zize of the channel dais mhich is contened vati tarik aor delecied ai block miraion Assembly E Assembly Lenghe Ez Geri Bed Cutout Status DNETIEDNSET DUTCHAN Block DET Parame
30. ex 1 0 3 21 11 Enter the correct information to match the Input Data Format table on the Module Configuration tab for the DNET_DEVICE block Refer to Locate Mapping Data from RSNetworx on page 3 8 for the module configuration example IMPORTANT This data MUST match what is entered into the Input Data Format table in the DNET_DEVICE block or the input channel will not operate Use Steps 6 11 to configure the way that the Main and Input Data Location tabs for all input channels for this device the ADN adapter Use the Numeric Input Config tab or Discrete Input Config tab to indicate offsets for each individual module 12 Select the Numeric Input Config tab DE TIF TAET Block DET Parameters Project E 1 E Discrete Data Block Firs Congreso Paramelez Mondonng Pacsmeler _ Black Praleeericez Input D ata Locabon Humai Input Config Dice Input Config Numer Dain FY Configuration 4 L oo ee BYTE LASIGHE UN IGHO BYTE_Us IbHo BYTE LINSIGND W RD SIGNED WORD SIGNED WORD_SIGHED WORD SIGHED mm m SES TEES 1 3 0 D 0 0 The byte offset column indicates the location in the input data assembly that we are attempting to read This offset is relative to the Input Data Location that was specified in the Input Data Location tab In this example the input of the IES is the first module in the data assembly Therefore in this case we
31. led Flex Analog Assign it to the CPM to which your DNET IM blocks and DNET_DEVICE are assigned If your blocks are all unassigned you should do so at this time If necessary create a new CPM Click on the CM to drag and drop function blocks into it T Bulger Prajict SEE Fle Wie Inert Took Operate Options window Heb ee Desin ZEAE pu r Ted 22 IM 28 Tenas 23 fors Sieppertil Pars Stepper Sipe Paa Slippa Por Stepper Pars SiepperD udi bw Shere Unzisped ze cah 31 Publication 1756 AT007B EN P August 2003 3 20 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 Publication 1756 AT007B EN P August 2003 Set up communication with the 1794 1 8 1794 0 4 pair Input Channel 6 Drag and drop a INCHAN from the Library tab 7 Double click the block to display the block parameters form DET IPCHAN Block DET Digital In Parameters Project Discretes Data Block Pans Confgursbon Parameters Mondonng Parsmelerz Block hain Locsion Munere Contr kele Input Cordig hane Bleck Configuration Name O Eionn Chamel Glock bo Module Modus Hara z1 Dv 2
32. left mouse button twice in Double click the Station icon quick succession Assumes cursor Is positioned on object or selection Press and hold left mouse button Drag the PID function block while dragging cursor to new onto the Control Drawing screen location and then release the button Assumes cursor is positioned on object or selection to be moved Click right mouse button once Right click the AND function Assumes cursor is positioned on block object or selection click to highlight a menu item or select Configure list choice or click on a button Allen Bradley drivers from the list box Keys to be pressed are shown in Press F1 to view the online angle brackets Help Keys to be pressed together are Press lt Ctrl gt lt C gt to close the shown with a plus sign window Shows menu selection as menu Click File gt New to start new name followed by menu selection drawing Data to be keyed in at prompt or in Enter this path location an entry field gt D setup exe lt 3 Publication 1756 AT007B EN P August 2003 Preface 4 Notes Publication 1756 AT007B EN P August 2003 Chapter 1 introduction Pre requisites This document describes how to define configure and monitor a DeviceNet network using the DeviceNet Interface Library This Quick Start assumes that you have an understanding of basic Control Builder terminology control strategies as well as an understanding of DeviceNe
33. n Control 1 Open Control Builder Builder 2 In Control Builder have two tree windows open 33 Project Monitoring e Project e Monitoring Ce Control Builder Project sidl Le sis 21801 giake 11181 01 121 a 20073 FF 3 Unassigned 33 Project 34 Monitoring Libo B start 2 53 Efepevecter imsnetiwors nuns Gateway 2 control Builder Project Publication 1756 AT007B EN P August 2003 3 2 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 Creating and Configuring the CPM Creating a DNET_IM Module Publication 1756 AT007B EN P August 2003 3 Create a CPM ProcessLogix Controller representation if you don t already have one to use select File gt New gt Controllers gt 4 Configure the CPM enter the required information SYSTEM CPM Block CPM1911 Parameters Project Server History Server Displays 911 Network CONTROLNET Driver Name PCIC 1 Supervisor MAC Address ui n Supervisory Slot Number CPM Slot Number 01 m Command E Status Time Zone 0 fear Format Daylight Savings Time Weekday Format SUNDAY Enable Scheduled 10 Traffic This controller is redundant Secondary CPM Redundancy Capability OFF Synchronization State NOTINSY NC Show Parameter Names Cancel Help 5
34. n and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit http support rockwellautomation com Installation Assistance If you experience a problem with a hardware module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure Power Control and Information Solutions Headquarters Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Middle East Africa Rockwell Automation Vorstlaan Boulevard du Souver
35. remote rack locations DNETIF DNET_IM Block DNET_IM1719 Parameters Project EET b UNb In slot 4 Test4621 This is Test Case 4 6 2 1 DeviceNet Interface Module 10 Select the Interface Module tab You see DNETIF DNET_IM Block DNET_IM1719 Parameters Project 1756DNB H 6 11 Enter the information for the DeviceNet Address of the 1756 DNB 12 Click OK 13 Go to the Project tab window 14 Select the DNET_IM that you configured Publication 1756 AT007B EN P August 2003 3 6 Using the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 Download the DNET_IM to the processor by clicking Load xi Load Complete Test4621 You see the item loaded Load Dialog x Load List Current State State To Load Post Load State v 21 Mot Loaded INACTIVE ACTIVE hd 15 Click OK 16 Go to the Monitoring tab window 17 Select the CEE 18 Activate the CEE either by right clicking and selecting the following Monitoring Root 20073 DR zm Oh Compare Parameters op Configure Module Parameters rZ DH Load Load With Contents Gh Upload DP Upload with Contents OF X Update Project DR Update With Contents to Project Load Server Points gm Dh Delete Server Points Selected Item s Selected Themis and Selected Item s Hg Dh
36. t or output channel does not match the information in the corresponding DNET DEVICE block Data not reflected in module or device Check mapping in RSNetworx for DeviceNet to verify Inchan Outchan block is pointing to correct space in DNB memoty Publication 1756 AT007B EN P August 2003 4 2 Troubleshooting Notes Publication 1756 AT007B EN P August 2003 How Are We Doing AB Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback wy You can complete this form and mail it back to us visit us online at www ab com manuals or email us at RADocumentComments ra rockwell com Pub Title Type Integrating DeviceNet into ProcessLogix R510 0 Cat No 1756 DNB 1757 Series Pub No 1756 007 Pub Date August 2003 Part 957824 87 Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 Z 2 How we make this publication more useful for you C 2 3 Can we add more information to help you ompleteness all necessary information procedure step illustration feature is provided ee example guideline other explanation definition Technical Accuracy 1 2 3 Can we be more accurate all provided information 15 correct text illustration Clarity 1 Z 2 How can we make things clearer all provided information Is easy to underst
37. t terminology and configuration tools The following checklist describes what is required of you before you begin integrating a DeviceNet Device into your ProcessLogix R510 0 system General Checklist to Configure 1756 DNB Table 1 General Checklist to Configure 1756 DNB ProcessLogix ProcessLogix v You must have Purchased or upgraded to appropriate hardware to run ProcessLogix R510 0 ProcessLogix R510 0 with the DNET Interface Library installed e The DNET Library is integrated into ProcessLogix R510 0 e f you have purchased the ProcessLogix Hardware from Rockwell Automation this library has been installed on the Server shipped from the factory e f you are upgrading existing hardware or using your hardware configured to ProcessLogix R510 0 specifications then follow the installation instructions in the ProcessLogix R510 0 Installation and Upgrade Guide publication 1757 IN510A EN P A DeviceNet network wired properly and working All devices on the DeviceNet network assigned to the DeviceNet interface module and no errors are showing in the LED display A working knowledge or have access to the support of a person with working knowledge of Control Builder and RSNetWorx for DeviceNet RSNetWorx installed and running properly on your development machine RSNetWorx configuration information e Input mapping e Qutput mapping Publication 1756 AT007B EN P August 2003 1 2 Introduction Table 1
38. template a generic block that represents a DeviceNet device present on the DeviceNet network connected to the DeviceNet Interface Module DNET_INCHAN DNET_INCHAN is a generic input channel block template that represents individual input data read from the DeviceNet devices This block can be configured to create an interface to all DeviceNet devices Simply this function block receives input data from the 1756 DNB that has been sent from the DeviceNet device ProcessLogix R510 0 Function Block Set Architecture 2 3 DNET_OUTCHAN DNET_OUTCHAN is a generic output channel block template that represents individual output data to the DeviceNet devices This block can be configured to create an interface to all DeviceNet devices Simply this function block sends output data from ProcessLogix to the device through a 1756 DNB Configuration Tools Each of the affected hardware components in the ProcessLogix DeviceNet architecture require the use of specific configuration tools as listed in the table below Table 2 1 Configuration Tools Component Configuration Tool 1756 DNB Module RSNetworks for DeviceNet DeviceNet Devices RSNetworks for DeviceNet All ProcessLogix Blocks ProcessLogix Control Builder DeviceNet 1 0 Module Function Blocks DeviceNet Wizard optional 1 56 DNB Verify that your Rockwell 1756 DNB DeviceNet Interface Module is at firmware release 3 010 or later DNETIF Library Use of the DeviceNet Interface module with th
39. ters Project E Decrees Block Preferences Gutput Gata Location Humenc Config Output Config Dua FYTE UNSIGHO WORD SIGHED WORD SIGHED WORD SIGNED Dw ORD SIGNED WORD_SIGHED WORD SIGHED WORD SIGHED mn 0 E 0 This offset is set to 2 bytes because the first word of output to the OF41 is for filter settings Please refer to your device specific manual s for more information about write read locations within the data structure After you have configured the Input and Output Channels download and activate the new CMs Publication 1756 AT007B EN P August 2003 Hardware Software Chapter 4 Troubleshooting 1756 DNB DNB Error Codes Refer to the ControlLogix DeviceNet Interface Module User Manual 1756 6 5 19 RSNetworx for DeviceNet Changing Hardware When changing some device configuration information channel states etc Be sure that the device is not assigned to the DNB scanner list If the device is still assigned changes may not be saved Control Builder Device Is red but IM is green Make sure IM is in RUN mode Configuration mismatch error on download This error can be triggered by several configuration mistakes With DeviceNet this error could mean that the Data Offset DWORDS Data Offset BITS and Data Length BITS within an inpu
40. the 1756 DNB and ProcessLogix to Communicate with Flex 1 0 You see IDNETIF DNET_DE ICE Block Test_21_D _2 Parameters Project 8 Enter a Description 9 Select the Module Configuration tab Publication 1756 AT007B EN P August 2003 Using the 1756 DNB and ProcessLogix to Communicate with 0 3 17 You see a similar screen DNETIF DNET DEVICE Block Test 21 DV 2 Parameters Project E Module Configuration Server History Server Displays DeviceNet I F Module Name Test4621 Execution State NACTIVE Device Address 2 Device Status Alarming Enabled Input Data Format Eg Data Offset Data Offset Bits Data Lenath Bits 0 0 OOO OO OOOO m Ol O OI OI O Data Offset Bits Data Length Bits Show Parameter Names Cancel Help 10 Enter the DeviceNet I F Module Name as the name of the DNET IM that has this DeviceNet device Test 21 DV 2 in it s scanlist This example is DNET_IM module is Test 4621 11 Enter the DeviceNet Address of the 1794 ADN Refer to Locate Mapping Data from RSNetworx on page 3 8 12 Enter the Input Data Format refer back to page 3 11 where we recorded this data from RSNetworx In this example the correct information has been entered The input assembly does not need to be separated by
41. tion 1756 AT007B EN P August 2003 1 6 Introduction Notes Publication 1756 AT007B EN P August 2003 DeviceNet Library Chapter 2 ProcessLogix 510 0 Function Block Set Architecture The set of function blocks that comprise the ProcessLogix DeviceNet library are packaged as a Control Component Library CCL The CCL requires ProcessLogix R510 0 to run DNETIF Library All DeviceNet blocks amp contained in the DNETIF DeviceNet Interface library of the ProcessLogix database 27 10 IDCHANNEL LOGIC REGCTL SCM UCNIF UTILITY RAIL ID HAZ DNETIF PBLISIF RAIL 10 FEUSIF PULSEINPUT 33 Project Monitoring ti Library Publication 1756 AT007B EN P August 2003 2 2 ProcessLogix R510 0 Function Block Set Architecture Publication 1756 AT007B EN P August 2003 Function Block Set The DNETIF library comprises the following blocks library 1 NE E SEM UTILITY RAIL ID HAZ 7 DNET_DEVICE t Templates IM j INCHAM a Function Blocks 1 DNET_OUTCHAN PBLISIF RAIL 10 FBLSIF EXCHANGE PULSEINPUT 33 Project i2 Monitoring DNET_IM DNET IM is a template an block that represents a DeviceNet Interface module This template allows ProcessLogix to communicate monitor a DeviceNet device via the 1756 DNB such as any I O Flex or MicroLogix DNET_DEVICE DNET_DEVICE is a
Download Pdf Manuals
Related Search