Home

1769-UM009 - Rockwell Automation

image

Contents

1. SERCOS Intertace secondary Scanner Module Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B Backup System Requirements The CompactLogix backup on DeviceNet solution requires that you use the following RSLogix 5000 programming software version 10 or later Two CompactLogix controllers firmware revision 10 x or later Two 1769 SDN scanner modules firmware revision 3 x or later Additional requirements are as follows When setting up the DeviceNet network you must set the primary and secondary 1769 SDN scanner modules to the same node address and resetve the next node address We recommend that you set the primary and secondary 1769 SDN scanner module node addresses to 0 and reserve node 1 However you can use any successive node numbers for example 30 and 31 e All I O and operator interfaces that required backup must be on the DeviceNet network The scanlists in the two DeviceNet scanner modules must be identical 131 Appendix B CompactLogix Backup on the DeviceNet Network Configure the Backup Follow these steps to configure a CompactLogix backup system on the System 1 132 DeviceNet network Some of these steps are described in greater detail in the rest
2. 1305 Drive Connected via 1203 GUO Enhanced DeviceNet Communication Module 104 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Start the Project Follow these steps to begin your project 1 Open RSLogix 500 software 2 Choose File 2New MicroLogix 1500 LRP series C This dialog should match what you see on your computer RSLogix 500 TEMP Ee IE a Noroc E mes User Abit A M ES SLAD 2 MAIN_PROG 3 3 Project H E Help Controller i Controller Properties e Processor Status j en Function Filez Ali IO Configuration Es Channel Configuration Egg Program Files Ei Data Files In this example the name for this application is TEMP In the TEMP dialog you see everything associated with the application Within the Controller folder you will see I O Configuration 3 Double click I O Configuration 105 Chapter 7 Use the 1769 SDN Scanner Module with MicroLogix Controllers 106 I O Configuration Screen 1 0 Configuration High Speed Counter B Input lsolated 120 WAC Powers uppi 16 Input 73 132 VAC Analog 4 Channel Input Module Analog 4 Chan Inp 2 Chan Out 12 Input 159 265 VAC 0 Bull 764 Micralagis 1500 LAP Series C 16 Input 1030 vD E 1769 10 640 w4 6 lnput 24 WDC 4 Output RLY 6 Channel ATO Module 6 Channel Thermocouple Module 8 Output 120 240 VAC 1
3. The Active Node array contains 64 bits of data that represents each slave node s status A slave node is considered active when it is present and enabled in the master s scanlist A bit value of 0 means Not Active a bit value of 1 means Active Slave Node Status Input Word Bit 15 Description 14 Node 0 15 Bit ON 1 Active node 152 Node 16 31 Bit OFF 0 2 Inactive node 1683 Node 32 47 170 Node 48 63 Bito corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Scanner Module Status The Scanner Device Status is a 4 byte array Scanner Device Status Input Word Bit o0 Description 20 scanner Address in BCD scanner Status in BCD 21 Slave Device Address in BCD Slave Device Status in BCD Publication 1769 UMQQ09E EN P August 2009 91 Chapter6 DeviceNet 0 Image Reserved Array Reserved Array Input Word Description 22 31 Always 0 0 Do not manipulate reserved bits Doing so may interfere with future compatibility Device Status Array The Device Status Array is a 64 byte array containing the information shown in this table Each byte indicates the status code of the scanner s ma
4. 60664 1 9 Hazardous Location Considerations This equipment is suitable for use in Class I Division 2 Groups A B C D or nonhazardous locations only The following WARNING statement applies to use in hazardous locations EXPLOSION HAZARD Substitution of components may impair suitability for Class Division 2 Do not replace components or disconnect equipment unless power has been switched off or the area is known to be nonhazardous Do not connect or disconnect components unless power has been switched off or the area is known to be nonhazardous his product must be installed in an enclosure All wiring must comply with N E C article 501 4 b Pollution Degree 2 is an environment where normally only nonconductive pollution occurs except that occasionally a temporary conductivity caused by condensation shall be expected 2 Over Voltage Category Il is the load level section of the electrical distribution system At this level transient voltages are controlled and do not exceed the impulse voltage capability of the product s insulation 3 Pollution Degree 2 and Over Voltage Category Il are International Electrotechnical Commission IEC designations Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Installation and Wiring Chapter 3 Preventing Electrostatic Discharge Electrostatic discharge ESD can damage integrated circuits or ATTENTION i semiconductors
5. Download Scanlist to Scanner 04 1791D 8B8P 8 Sink I 4 J 06 1769 40N Compact g 08 1761 NET DNI Devic B Ge 04 1791D 8B8F 8 Sink l DB 1769 ADN Compact E E 08 1761 NET DNI Devic Ai Selected Beans HEcods Click the Input tab and click the AutoMap button to automatically map input devices Click the Output tab and click the AutoMap button to automatically map output devices 1769 SDN Scanner Module 1 2 1790D 8BV8B Polled 1 4 1731D 8B8P COS 1 68 8 lie 6 1769ADN Co COS 36 73 j 1769 ADN Co 08 1761 NET DN COS 8 B 08 1761 NET DN Publication 1769 UMOO9E EN P August 2009 Chapter 2 Quick Start for Experienced Users Introduction This chapter helps you get started using the 1769 SDN scanner module Topic Page Required Tools and Equipment 19 What You Need to Do 20 Procedures are based on the assumption that you have an understanding of Rockwell Automation controllers You should understand electronic process control and be able to interpret the ladder logic instructions required to generate the electronic signals that control your application Because it is a start up guide for experienced users this chapter does not contain detailed explanations about the procedures listed Required Tools and Have the following tools and equipment ready Equipment Personal computer Programmable controller CompactLogix or Mi
6. Run Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Fault This bit displays whether the network is faulted Network is not faulted Network is faulted Disable Network This bit displays whether the network is disabled Network is not disabled Netwotk is disabled Device Failure This bit displays whether any device failures have occurred on the network No device failures exist 1 Device failure exists examine the status structure for causes Autoverify Failure This bit displays whether the scanner has failed to initialize any devices on the netwotk e The scanner has initialized all devices e The scanner has failed to initialize at least one device Comm Failure This bit displays whether a communication failure exists on the network No communication failures exist e 1 A communication failure exists Publication 1769 UMOO9E EN P August 2009 99 Chapter6 DeviceNet 0 Image CompactLogix Command Register 100 Dup Node Failure This bit displays whether a network failure exists because of a duplicate node address e 0 No failure exists Failure exists due to duplicate node address Dnet Power Detect This bit displays whether a DeviceNet power failure exists on the network 0 No Devicenet power failure exists on the network DeviceNet power failure exists The first atea of the CompactL
7. Run Mode Node Number 01 or 00 otatus 68 No backup scanner present or Undefined error or 00 Run mode 69 Backup scanner invalid CRC Primary or Secondary Node Number 01 or 00 Status Undefined error or 80 Idle mode 69 Backup scanner invalid CRC 142 Publication 1769 UMOO9E EN P August 2009 Lost Primary Scanner Module With Valid Backup Scanner Module Run Mode Node Number Status Primary or Secondary Idle Mode Node Number Status Primary or Secondary CRC Error Run Mode Node Number Status Primary or Secondary Idle Mode Node Number Status Primary or Secondary Lost Primary Scanner Module Without Valid Backup Scanner Module Run Mode Node Number Status Primary or Secondary Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B Undefined error 68 No backup scanner present or 00 Run mode E rim m eem Undefined error 68 No backup scanner present or 80 Idle mode Petia 00 or 01 00 or 01 68 No backup scanner present or 69 Backup scanner invalid CRC 00 Run mode P Primary s 00 or 01 00 or 01 68 No backup scanner present or 69 Backup scanner invalid CRC 80 Idle mode P Primary Undefined error Undefined error 143 Appendix B CompactLogix Backup on the DeviceNet Network When you implement the CompactLogix system backup on the DeviceNet evelopment an you imp pactLogix sy p Debugging Tips network we recommend that yo
8. e 35x 7 5 mm EN 50022 35 x 7 5 or 35 x 15 mm EN 50022 35 x 15 Before mounting the module on a DIN rail close the DIN rail latches Press the DIN rail mounting area of the module against the DIN rail The latches will momentarily open and lock into place DIN rail mounting dimensions are shown below DIN rail mounting dimensions Dimension Height A 118 mm 4 65 in B 59 mm 2 325 in Publication 1769 UMOO9E EN P August 2009 Replace the Scanner Module within a System Publication 1769 UMOO9E EN P August 2009 Installation and Wiring Chapter 3 The scanner module can be replaced while the system is mounted to a panel or DIN rail once power is removed 1 2 10 11 12 Remove power Remove the DeviceNet cable from the scanner module by removing the DeviceNet connector Remove the upper and lower mounting screws from the scanner module or open the DIN rail latches using a flat blade screwdriver On the scanner module to be replaced and the right side adjacent module or end cap if the scanner module is the last module in the bank move the bus levers to the right unlock to disconnect the scanner module from the adjacent modules Gently slide the disconnected scanner module forward If you feel excessive resistance make sure that you disconnected the scanner module from the bus and that you removed both mounting screws or opened the DIN latches It may be necessar
9. A bit value of 1 represents Idle mode where the slave node is present 1n the scanlist Slave Device Status Input Word Bit 15 Description 10 Node 0 15 Bit ON 1 Idle 11 Node 16 31 Bit OFF 0 Non idle 123 Node 32 47 134 Node 48 63 1 2 3 4 96 Bit 0 corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Active Node Register The Active Node array contains 64 bits of data that represents each slave node s status A slave node is considered active when it is present and enabled in the master s scanlist A bit value of 0 means Not Active a bit value of 1 means Active Slave Node Status Input Word Bit 15 Description 14 Node 0 15 Bit ON 1 Active node 152 Node 16 31 Bit OFF 0 2 Inactive node 1683 Node 32 47 170 Node 48 63 Bito corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 7 Bito corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 3 Bito corresponds to N
10. Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Autoverify Failure Register These four words allow the control program to monitor if a slave s Device Key and Size matches the Device Key and Size in the scanner A bit value of 0 OFF represents a configuration match a bit value of 1 ON represents a mismatch A value of 0 does not indicate that the slave has been brought online or is functional only that there is a configuration match N between the slave and the scanner 95 Chapter6 DeviceNet 0 Image Slave Device Configuration Comparison to Scanner Module Configuration Input Word Bit0 15 0 Description gl Bit ON 1 Slave node mismatch 7 Bit OFF 0 Slave node match 3 4 Bit 0 corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Device Idle Register The slave device idle array contains 64 bits of data Each bit indicates the state of a slave device A bit value of 0 represents a Non idle mode ot that the slave is not present in the scanlist
11. Status Active Node Register Status Status Display Status Scanner Address Status Scanner Status Status Scrolling Device Address Status Scrolling Device Status Status Device Status Scan Counter Data Type 2 words 64 bit array 64 bit array 64 bit array 64 bit array 8 bytes 1 byte 1 byte 1 byte 1 byte 64 bytes This 32 bit unsigned value is incremented each time the DeviceNet network is scanned The value will automatically roll over to zero and continue counting Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Device Failure Register These 64 bits provide status information for use in your control program For each slave device owned by the scanner you should monitor the respective bit within these four words If a slave device faults the bit that corresponds to that node address will be set 1 If a slave device is not faulted or returns from a faulted state to an operating state the corresponding bit for that node will be cleared 0 Slave Device Status Information Input Word Bit 15 0 Description 2n Node 0 15 Bit ON 1 Slave node faulted 32 Node 16 31 Bit OFF 0 Slave node not faulted 43 Node 32 47 54 Node 48 63 Bito corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31
12. jals ula Tele a el E El amp amp Hl av Hardware x DeviceNet amp Category AC Drive Barcode Scanne Communication DeviceNet to S Dodge EZLINK General Purpose Generic Device Human Machine Inductive Proximi Limit Switch Rockwell amp utoma F gt b Graph Master Sle lt High 64 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 2 From the File menu choose New If you have ControlNet configured on your system you may see this dialog Otherwise proceed to step 4 Hew File Configuration Types Description Control et Configuration L antralM et Files c ui DeviceNet Configuration DeviceNet Files drt 3 Select DeviceNet Configuration and click OK 4 Click the Online button zs on the toolbar A list of the available networks will appear Your list may be different from that shown below depending upon the drivers you have configured on your system Hew File Configuration Types Description Controldet Configuration Control et Files 4c E DeviceNet Configuration DeviceNet Files dnt Cancel 5 Select your DeviceNet driver and click OK You will be prompted to upload or download device
13. so these bits can be used in your control program to flag an error 21 Chapter 2 Notes 22 Quick Start for Experienced Users Publication 1769 UMOO9E EN P August 2009 Power Requirements Publication 1769 UMOO9E EN P August 2009 Chapter J Installation and Wiring This chapter describes how to install and wire the 1769 SDN scanner module This table describes what this chapter contains and where to find specific information Topic Page Power Requirements 23 General Considerations 24 System Planning 26 System Assembly 2 oystem Mounting 28 Replace the Scanner Module within a 31 system Field Wiring Connections 32 scanner Module Power up 33 The scanner module receives power through the Compact I O bus interface from the 5V DC system power supply Maximum Current Draw 1769 SDN 440 mA 0 mA The scanner module also draws power from the DeviceNet network DeviceNet Power Requirements Module DeviceNet Power Requirements 1769 SDN N E C Class 2 90 mA 11V DC max 110 mA 25V DC max 200 mA for 1 5 ms inrush 23 Chapter3 Installation and Wiring General Considerations 24 The Compact I O system is suitable for use in an industrial environment when installed in accordance with these instructions Specifically this equipment is intended for use in clean dry environments Pollution Degree 2 and to circuits not exceeding Over Voltage Category II IEC
14. 2 A T SMC Flex Standard 62 This DeviceNet HIM If the Network Who screen does not appear as expected then the 193 DNCT terminal may be set to autobaud enabled and is not able to determine a communication rate because no communication is occurring on the network at this time Follow these steps to disable the autobaud feature and set the baud rate On the 193 DNCT terminal keypad press lt ESC gt ES l Select the AutoBaud option and use Up Arrow gt to select Disable Press SEL E to advance to the BaudRate option the appropriate baud rate Press lt Enter gt E to complete the node commissioning function Press lt ESC gt E to exit setup 41 Chapter 4 42 Automatically Configure a DeviceNet Network Set the Node Address of a Device Via a DeviceNet Configuration Terminal Follow these steps to set the node address of a device on your DeviceNet network via the 193 DNCT terminal 1 Connect the 193 DNCT terminal to the network The following display should appear for 10 seconds that shows the unit setup and the baud rate and node number values it has determined DEVICE MET HIM baud Fixed Baud Rate Baud 125l amp 4 Auto bZ Actual Terminal Auto Autobaud Node Address Actual Baud Rate Address Fixed HMI MaclD Auto Auto Addressing After 10 seconds a Network Who screen similar to the example shown below should appear that displays all Nodes and associated devices on the
15. DeviceNet instructions on how to send an explicit message via the class instance editor in RSNetWorx for DeviceNet are not covered in this document 1 Set up the physical network Make sure all devices are addressed appropriately that is there are no address conflicts and are communicating at the same baud rate The diagram below shows an example system using the 1769 SDN scanner 23 s a 2l 00 Hill 01 E 03 You can commission the node addresses via hardware switches on the device s ot through the 193 DNCT terminal Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 2 Set up I O allocation size in the scanner TIP This step is optional The default AutoScan setting allocates a 4 byte entry in both the input and output memory maps in the scanner for each slave device detected on the network This default size is chosen to accommodate the default Logix native data size of 32 bits DINT If that is adequate for the application skip to step 3 For applications where the user would like to customize the I O allocation size the 4 byte allocation could be adjusted through an Explicit Message to the scanner using the SetAttributeSingle service The entry allocation could be configured for 1 t
16. again the scanner clears out the current configuration and starts over Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 Access Device Data When you add the scanner to the I O configuration of the controller RSLogix 5000 software automatically creates a set of tags for the input output and status data of the network Sion Controller MvPrajeck 1 En IINE Tags bes EI Controller Fault ander CI Power Up Handler amp Controller Tags MyProject_ifcontroller Scope MyProject_I controll Shaw Module 5n input data from the scanner ne ES Tag Mame hh H Lacal z l m H Lacal 2 0 H Lacal 2 5 i output data for the scanner status data from the scanner _ The tags for your DeviceNet data follow this format H Optional wher _ location location of the scanner in the system If you have the 1769 SDN scanner ina Then location is local chassis Local slot number of scanner remote chassis adapter slot number of scanner where adapter is the name of the EtherNet IP or ControlNet module in the remote chassis type type of data input from a device output to a device IO offset address address of the device on the DeviceNet network based on 4 bytes per node bit specific bit within the data of the device Publication 1769 UMOO9E EN P August 2009 57 Chapter4 Automatically Configure a DeviceNet Network While you ca
17. backup on the DeviceNet network 129 145 configuring the DeviceNet network I O devices 70 84 manually 61 85 scanlist configuration 64 setting up an online connection 64 66 software installation 62 using RSLinx software 62 64 using RsNetWorx for DeviceNet software 17 64 85 Publication 1769 UMOO9E EN P August 2009 Index connecting devices to the DeviceNet network 39 current draw 20 cyclic message 14 D data tables 15 DeviceNet adapter 1770 KFD 19 61 DeviceNet driver adding 62 64 DeviceNet l 0 image 87 102 1769 SDN input structure 87 1769 SDN output structure 102 command register 100 101 input data image 102 status register 98 100 status structure 88 98 DeviceNet interface card 1784 PCIDS 19 DeviceNet interface cards 1784 PCD 1784 PCID 61 DeviceNet network CompactLogix backup on the network 129 145 power requirements 20 23 DIN rail mounting 30 E electrical noice reducing 25 electrostatic discharge preventing 25 equipment required for installation 19 error codes 124 message instructions 120 explicit messaging 14 F features of the scanner 12 G glossary 147 150 grounding 32 H hazardous location considerations 24 151 Index 152 1 0 allocation configuring via a user program 48 in CompactLogix controller 37 in MicroLogix 1500 controller 37 maximum node number 54 implementing AutoScan 46 60 input data definition 14 installation 23 33 getting started 19 grounding 32 heat and
18. backup state of the DeviceNet scannet If the message reads this value 254 67 68 69 295 The backup state of the DeviceNet scanner module is Disabled Primary scanner Backup scanner Invalid primary node address for example the node address cannot be 62 or 63 Faulted backup scanner module CRC failure for example the scanlists in the scanners do not match Faulted backup scanner module backup node number failure for example the backup scanner module is not using a node number the primary node number 1 Backup scanner module pending primary detection Attempting primary access scanner in Backup Scanner mode No backup scanner module present Invalid backup scanner module CRC Attempting backup access 139 Appendix B CompactLogix Backup on the DeviceNet Network 140 Reading Backup Status You can read the backup status of the DeviceNet scanner module with a single rung of ladder logic The backup state is useful for debugging or more sophisticated backup schemes The message in this rung uses the SINT data type This figure shows the rung you can use to read the backup state OPTIONAL Constantly Read Backup Status Bits Bit 0 No Backup Scanner Detected Bit 1 Primary Scanner forcing IDLE Backup in RUN but Primary in IDLE Head Backup Status EM MSG B i Type CIP Generic Message Control Head Backup Status LI MOV Move Source Backup Status Dest Rung 6 Message Configuration an
19. check its network status indicator Typically a solid red indicator means an address conflict or problem with the baud rate Set the Baud Rate of a Device Via a DeviceNet Configuration Terminal Follow these steps to set the baud rate for your DeviceNet network via the DeviceNet Configuration Terminal catalog number 193 DNCT For the rest of the chapter the terminal is referred to as the 193 DNCT terminal 1 Connect the 193 DNCT terminal to the network The following display appears for 10 seconds which shows the unit setup and the baud rate and node number values it has determined DE IE ME I FIM Baud 125K Auto B2 Actual Terminal Node Address Actual Baud Rate Address Fixed HMI MaclD Auto Auto Addressing Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 With the BaudRate option selected use Up Arrow gt Automatically Configure a DeviceNet Network Chapter 4 The 193 DNCT terminal is shipped so that when it is placed on a DeviceNet network for the first time it automatically sets its baud rate to that of the traffic on the network The terminal uses Auto Addressing to assign itself an unused network node address After 10 seconds a Network Who screen similar to the example shown below should appear that displays all Nodes and associated devices on the network NETWORK WHO Node 43 0 DeviceNet Scanner 2 1732D 24Vdc 8 Conf 5 E1 Plus b E3 Plus 0 4
20. connected to DeviceNet products that support PCCC messaging including MicroLogix and SLC controllers using 1761 NET DNI interfaces and other MicroLogix 1500 controllers using 1769 SDN scanner modules You can initiate reads writes program upload download and online monitoring across DeviceNet This is functionally identical to DH 485 and DH networking 115 Chapter 7 116 Use the 1769 SDN Scanner Module with MicroLogix Controllers CIP Generic Control amp Information Protocol CIP is a newer and more versatile protocol than PCCC It is an open protocol that is supported by newer Allen Bradley controllers and third party products CIP messaging is the native messaging format for the DeviceNet network All DeviceNet devices are compliant with CIP messaging The MicroLogix 1500 1764 LRP processor series C has an enhanced message instruction that provides simple easy to use CIP messaging Selecting CIP Generic configures the message instruction to communicate with DeviceNet devices that do not support PCCC messaging When CIP Generic is chosen you will notice that a number of message parameters change and many new ones become available depending upon the service selected MSG Rung 3 0 G11 1 Expansion Comma Fort CIF Generic Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Publication 1769 UMOO9E EN P August 2009 Data Table Address rece
21. contact me Yes please call me Yes please email me at Yes please contact me via Return this form to Rockwell Automation Technical Communications 1 Allen Bradley Dr Mayfield Hts OH 44124 9705 Email RADocumentComments ra rockwell com Publication ClG CO0521D EN P July 2007 PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES PLEASE REMOVE Rockwell Automation Rockwell Automation provides technical information on the Web to assist you in using its products At http support rockwellautomation com you can find technical Support manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools For an additional level of technical phone support for installation configuration 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 within the first 24 hours of installation please review the information that s contained in this ma
22. does not affect the scanners system or messaging modes Check the FAULT value in the Module Command Array See page 16 B 02 Fragmentation Error Error detected in sequence of fragmented I O messages from device Check scanlist table entry for slave device to make sure that input and output data lengths are correct Check slave device configuration 03 olave Init Error Slave device is returning error responses when the module attempts to communicate with it Check slave device s configuration Reboot slave device 04 Not Yet Initialized Module has not completed its initial attempt to establish communication with its slaves 85 Receive Buffer Overflow Data size returned is larger than expected Configure the slave device for a smaller data size E 86 Device Went Idle Device is producing idle state Check the device configuration and slave node status 89 Auto Device Slave device responded with an error to the initialization data sent to it by the scanner or the Replacement ADR Error configuration table in the scanners flash memory is not valid for a slave node Try the ADR download again If it still fails try clearing the ADR flash by downloading an empty ADR configuration to the scanner module and then try the ADR configuration again 90 Disabled Network DeviceNet Port is disabled Check for the DISABLE being set in the Module Command Array See page 16 91 Bus Off Bus off condition detected on integral DeviceNet port Check
23. if you touch the bus connector pins Follow these guidelines when you handle the module e Touch a grounded object to discharge static potential e Wear an approved wrist strap grounding device e Do not touch the bus connector or connector pins e Do not touch circuit components inside the module e Use a static safe work station if available e Keep the module in its static shield box when it is not in use Removing Power ATTENTION Remove power before removing or Inserting this module When you remove or insert a module with power applied an electrical arc may occur An electrical arc can cause personal injury or property damage N by e sending an erroneous signal to your system s field devices causing unintended machine motion e causing an explosion in a hazardous environment Electrical arcing causes excessive wear to contacts on both the module and its mating connector and can lead to premature failure Reducing Noise We recommend installing this module in an industrial enclosure to reduce the effects of electrical interference Group your modules to minimize adverse effects from radiated electrical noise and heat 25 Chapter3 Installation and Wiring Protecting the Circuit Board from Contamination The printed circuit boards of the modules must be protected from dirt oil moisture and other airborne contaminants We recommend installing the system in an enclosure suitable for the environment to
24. micrologix to determine if an application can be supported In addition to electrical limitations data space limitations also exist The maximum size of the input and output images for each module in the system is 250 input and 250 output words of data 103 Chapter7 Use the 1769 SDN Scanner Module with MicroLogix Controllers RSLogix 500 Programming One of the advanced features of RSLogix 500 software is the ability to have the programming software establish a communication connection with the Softwa re I 0 Configuration controller and read which I O modules are attached to the controller This capability significantly reduces the effort involved in configuring a system This section illustrates how to determine which I O modules are attached to the controller and manually configure the modules We will then configure the scanner An example network is shown below DeviceNet Network Personal Computer Running RSNetWorx for DeviceNet Software MicroLogix 1500 Controller O Bank with 1769 SDN Scanner Module CN atta mal Ic a HEN MERE I r3 1770 KFD PC Communication lies d Module f MEN Series 9000 MicroLogix 1000 Controller MicroLogix 1200 Controller Photoeye RediSTATION Connected via 1761 NET DNI Connected via 1761 NET DNI inta Interface Interface
25. module from the DeviceNet network This controller will be the secondary controller Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 10 11 12 13 14 15 CompactLogix Backup on the DeviceNet Network Appendix B Connect the other CompactLogix controller with a 1769 SDN scanner module on the network Set the node address to 0 Apply power to the controller and scanner module Use RSNetWorx for DeviceNet software to download the same scanlist used in step 5 It may be necessary to browse the network again before downloading the scanlist This second browsing of the network allows RSNetWorx for DeviceNet software to establish communication to the new scanner module at the same node number as the previous scannet Use RSLogix 5000 programming software to download the user program to the second CompactLogix controller as you did in step 6 Typically you download the same uset program to the second CompactLogix controller as you did to the first However unlike the scanlists the user programs in the controllers do not have to be identical Put the controller into Run mode This controller is now ready to use and is the primary controller Reapply power to the secondary controller and or reconnect the secondary scanner module to the DeviceNet subnet This completes the backup process For more detailed information on some of the steps listed previously see the next sec
26. module with a single rung of ladder logic The backup state is useful for debugging or more sophisticated backup schemes The message in this rung uses the SINT data type This figure shows the rung you can use to read the backup state OPTIONAL Constantly Read Backup State 0 Disabled 1 Primary Scanner 2 Backup Scanner 3 Invalid Primary Node Address e g can t be 62 or 63 4 Faulted Backup Scanner CAC Failure e g Scan Lists don t match 5 Faulted Backup Scanner Backup Made Number Failure e g Backup not Primary 1 B Backup Scanner Pending Primary Detection 254 Attempting Primary Access 255 Attempting Backup Access Head Backup State EM MSG 5 Type CIP Generic Message Control Head Backup State Mos P MOM Move Source Backup State De Dest DUMMY De 138 Rung 5 Message Configuration and Communication tabs Message Configuration Read Backup State Get Attribute Single el Source Element SGUTGE SET Message Configuration Head Heartbeat LEGIT DTI Ge GTI VI EH GTI Dele OD hrk Bic SIGUTGE I Pa zi Epes Backup_State I E riri Je stia me C T pe ETTAN p S GUITGE LITT i Vestination T age rg Wietaly v Cache Gonnections Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B This table describes the possible values this message may return when reading the
27. of the appendix Install all I O and operator interfaces that you need to back up on the DeviceNet network We recommend that you reserve node addresses 0 and 1 for the two 1769 SDN scanner modules used with the CompactLogix controllers within a backup system If you do not use 0 and 1 make sure you reserve two consecutive numbers for the 1769 SDN scanner modules when you install I O and other devices on the DeviceNet network Connect a CompactLogix controller with a 1769 SDN scanner module to the DeviceNet network Set the scanner module node address to 0 or the lower of the two node addresses reserved for the CompactLogix controller backup system Apply power to the controller and the network Use RSNetWorx for DeviceNet software to download the network s scanlist to the 1769 SDN scanner module You can either use a scanlist from a new configuration or from a previously used configuration If the scanlist is a new configuration we recommend that you save it to a new project for later use Use RSLogix 5000 programming software to download the appropriate user program to the CompactLogix controller The program should contain the explicit messages that enable the backup feature for this controller and scanner module The messages are described in the Develop the CompactLogix Backup Application section beginning on page 134 Put the controller into Run mode Either disable power to the controller or disconnect the scanner
28. re initializes and in another 10 seconds the 193 DNCT terminal again displays the Network Who screen At this point the new node appears in the table 43 Chapter4 Automatically Configure a DeviceNet Network Add the Scanner to the RSLogix 5000 Project 44 Add the scanner to the I O configuration of the controller to access the data of your network Add the Scanner to the 1 0 Configuration Folder 1 Right click and choose New Module 1769 L35E Ethernet Port LocalENB a Ethernet a CompactBus Loga New Module N Description Status Offline Module Fault Cross Reference Ckrl E eate a module Properties Alt Enter 2 Choose the type of scanner 3 Click OK lll Select Module Module Description Analog Communications 1769 5DN A 1769 Scanner DeviceNet 71 769 5DN 6 1769 Scanner DeviceNet Digital Other Specialty Vendor Allen Bradley Allen Bradley Find Add Favorite By Category By Vendor Favorites cares Heb Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 4 Select the Major revision of the scanner 5 Click OK Select Major Revision Select major revision For new 1 753 5 DN B module being created Define the Properties of the Scanner 1 Name the scanner 2 Set the scanner Minor Revision 3 Choose the size of the input and output memory maps that the scann
29. status indicator provides information about the DeviceNet channel communication link The numeric display shows node address and status display information Status information precedes the node address Publication 1769 UMOO9E EN P August 2009 121 Chapter8 Troubleshooting This table summarizes the meanings of the status indicators and numeric codes Module Indicator F MODULE r3 Oa NETWORK um Network Indicator Destteet ADDRESS ERROR 8H Node Address and otatus Display Troubleshooting the Status Indicators and Numeric Display Indicator Color Status Description Module Off No power applied to module Apply power Fashing No bus master MicroLogix or CompactLogix controller present Green Verify module connectors are properly seated If they are cycle power to the controller If this does not correct the problem replace the controller If replacing the controller does not correct the problem replace the scanner solid Green Normal operation Flashing Red Recoverable Fault Memory has been erased or is being programmed Complete the flash update or start a new update e Bad firmware in module Replace firmware Solid Red Unrecoverable fault Verify module connectors are properly seated If they are verify that bus terminator end cap is installed Cycle power If still faulted replace the module 122 Publication 1769 UMOO9E EN P August 2009 Troubleshooting Chapter 8 Troubl
30. the 1769 SDN Scanner Module with MicroLogix Controllers Channel Parameter The 1764 LRP controller supports three different pathways for messaging Channels 0 and 1 are RS 232 ports and are functionally identical to MicroLogix 1200 and MicroLogix 1500 1764 LSP controllers The 1764 LRP controller also supports backplane communication through the Expansion Communication Port ECP as illustrated below MSG Rung 3 0 MG11 1 0 Integral Integral Read 1 Integral When ECP is chosen you are able to select which slot position 1 16 the scanner module resides in The 1764 LRP processor can support up to two 1769 SDN scanner modules with full messaging functionality MSG Rung 3 0 MG11 1 S0OCFU Read i You can use multiple 1769 SDN scanner modules in a MicroLogix 1500 system but you can message only through the first two Any other 1769 SDN scanner module can be used only for I O scanning 114 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Communication Command MSG Rung 3 0 G11 1 3 5DDCPL Read SOOLPL Head The 1764 LRP controller supports the six standard types of communication commands same as all other MicroLogix 1200 and 1500 controllers and CIP Generic When any of these six standard commands are chosen you can initiate standard messages to destination devices
31. transfer of data that is 64 bits in length sent by the scanner module that initiates a response from each strobed slave device The strobe devices respond with their data which can be as much as 8 bytes of information As a slave device the scanner module does not support the strobe message A poll message is a point to point transfer of data from 0 128 bytes sent by the scanner module to the slave device The poll message also initiates a response from each poll slave The slave device responds with its input data from 0 128 bytes A change of state message is a transfer of data sent whenever a data change occuts A user configurable heartbeat rate allows devices to indicate proper operation during intervals between data changes A cyclic message is a transfer of data sent at a specific user configurable rate such as every 50 ms MRITUB n oughout this document input and output are defined trom the controllers point of view Output is data sent from the controller to a device Input is data collected by the controller from a device In addition to I O messaging the scanner module also supports PCCC and CIP explicit messaging defined later in this manual Publication 1769 UMOO9E EN P August 2009 1769 SDN Scanner Module Data Tables Publication 1769 UMOO9E EN P August 2009 Overview Chapter 1 The scanner module uses input and output data images to transfer data status and command information between
32. use in your control program For each slave device owned by the scanner you should monitor the respective bit within these four words If a slave device faults the bit that corresponds to that node address will be set 1 If a slave device is not faulted or returns from a faulted state to an operating state the corresponding bit for that node will be cleared 0 Slave Device Status Information Input Word Bit 15 0 Description ol Bit ON 1 Slave node faulted 32 Bit OFF 0 Slave node not faulted Bito corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Autoverify Failure Array These four words allow the control program to monitor if a slave s Device Key and Size matches the Device Key and Size in the scanner A bit value of 0 OFF represents a configuration match a bit value of 1 ON represents a mismatch A value of 0 does not indicate that the slave has been brought online or is functional only that there is a configuration match N between the slave and the scanner 89 Chapter6 DeviceNet 0 Image Slave Device Configuration Comparison to Scanner Module Configuration Input Word Bit0 1
33. 09 Rockwell Automation Inc All rights reserved Printed in the U S A
34. 1769 SDN DeviceNet Scanner Module Catalog Numbers 1769 SDN User Manual Allen Bradley iks is Rockwell Allen Bradley Rockwell Software Automation Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls publication SGI 1 1 available from your local Rockwell Automation sales office or online at http www rockwellautomation com literature describes some important differences between solid state equipment and hard wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable In no event will Rockwell Automation Inc be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment he examples and diagrams in this manual are included solely for illustrative purposes Because of the many variables and requirements associated with any particular installation Rockwell Automation Inc cannot assume responsibility or liability for actual use based on the examples and diagrams No patent liability is assumed by Rockwell Automation Inc with respect to use of information
35. 26 T technical support 71 tools required for installation 19 troubleshooting 121 126 diagnostic indicators 121 error codes 124 status indicators 121 typical network configuration 13 104 W what you need to know 11 wiring 23 33 Publication 1769 UMOO9E EN P August 2009 How Are We Doing 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 You can complete this form and mail or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type 1769 SDN DeviceNet Scanner Module Cat No 1769 SDN Pub No 17 69 UMO009E EN P Pub Date August 2009 Part No Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 How can we make this publication more useful for you 2 3 Can we add more information to help you Completeness all necessary information procedure step illustration feature is provided example guideline other explanation definition Technical Accuracy 1 2 9 Can we be more accurate all provided information Clarity 1 Ze How can we make things clearer all provided information is easy to understand Other Comments You can add additional comments on the back of this form Your Name Your Title Function Would you like us to contact you regarding your comments Location Phone No there is no need to
36. 4 Eu tea edd be etd ees 130 Backup System Requirements su acid aep ce 3 eek UR D a 131 Contburedhe Backup Syste oue eae ees tani aa Sapte teres 132 Develop the CompactLogix Backup Application 134 Backup Heartbeat Configuration Rungs 4 134 Reading Backup State Rune 25 ccns 5 true eer Pon eer etd 138 Reading Backup Status dui puis d icdciea e kote tela teed ood alid 140 Using Indicatorsito Check Status ices dod esu Y Gade bei 141 Module Status Indicatot ss 65 vu t rtt d e UR Cer alae 141 Node Address and Status Display 0 0 0 0 eee ee eee 142 Development and Debugging Vipss x4 1 cteve dea e Svo RO en Cede 144 Publication 1769 UMOO9E EN P August 2009 About This Manual Who Should Use This Manual Publication 1769 UMOO9E EN P August 2009 Preface Read this preface to familiarize yourself with the rest of the manual This manual is a user manual for the Compact I O 1769 SDN DeviceNet scanner module It describes the procedures you use to install program and troubleshoot your scanner module This manual provides instructions on installing the scanner module contains information about using the scanner module on the DeviceNet netwotk provides tips on troubleshooting the scanner module contains application examples to show how the scanner module is used with various programmable controllers Minin nis manual focuses on the 1 69 SDN scanner module with a MicroLogix 1
37. 5 0 Description gl Bit ON 1 Slave node mismatch 7 Bit OFF 0 Slave node match 3 4 Bit 0 corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Slave Device Idle Array The slave device idle array contains 64 bits of data Each bit indicates the state of a slave device A bit value of 0 represents a Non idle mode ot that the slave is not present in the scanlist A bit value of 1 represents Idle mode where the slave node is present 1n the scanlist Slave Device Status Input Word Bit 15 Description 10 Node 0 15 Bit ON 1 Idle 11 Node 16 31 Bit OFF 0 Non idle 123 Node 32 47 134 Node 48 63 1 2 3 4 90 Bit 0 corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 15 corresponds to Node 15 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 15 corresponds to Node 31 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Active Node Array
38. 500 control system on the DeviceNet network Topics covered include using Autoscan configuring bridging connecting and controlling your DeviceNet network For information about using the 1769 SDN scanner module with a CompactLogix system refer to DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UMO04 Use this manual if you are responsible for designing installing programming ot troubleshooting control systems that use Rockwell Automation programmable controllers You should have a basic understanding of electrical circuitry and familiarity with relay logic If you do not obtain the proper training before using this product Preface Preface Co nve ntions in This Manual The following conventions are used throughout this manual Additional Resources Resource DeviceNet Modules in Logix5000 Control systems User Manual publication DNET UMO04 ControlNet Modules in Logix5000 Control oystems User Manual publication CNET UMO01 RSNetWorx for DeviceNet Getting Results Guide publication DNET GROO1 CompactLogix System User Manual publication 1769 UM007 MicroLogix 1500 Programmable Controllers User Manual publication 1 764 UM001 Compact O Analog Modules User Manual publication 1 769 UM002 DeviceNet Interface User Manual publication 1761 UM005 DeviceNet Media Design and Installation Guide publication DNET UM072 Industrial Automation Wiring and Grounding Guidelines publicatio
39. 6 Output 24 YOC Source 16 Output 24 VOC Source w Protectio Analog 2 Channel Output Module 16 Output 24 WDC Sink 8 Output Relay 8 Output Isolated Relay DeviceNet canner Power Supply Power Supply Ady Eonia Power Supply The I O configuration dialog shows each of the controller I O slots For the MicroLogix 1500 controller slot 0 contains the embedded I O that is part of the MicroLogix 1500 base unit Slots 1 16 are for Compact I O expansion modules referred to as local I O because they are physically attached to the controller Slots 9 16 are available using only a series C processor with a series B base unit Click Read I O Config to have RSLogix 500 software read the controller s local I O and configure the slots automatically Drag the appropriate modules from the available list right pane to the appropriate slot on the left to manually configure the controller I O Modules must be contiguous with no open slots from 1 16 Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Read 1 0 Configuration Read 10 Configration from Online Processor jap OF ges ml AB DFI1 1 Mode 1d local Next you see a communication dialog that lets you select a communication path by using RSLinx software to connect to the MicroLogix controller If you have previously connected to a controller the communication driver that you used before will be the active driv
40. 6 words 0 65 are required by the scanner module for status DeviceNet slave input data words start at slot word 66 You can have a maximum of 180 input words for DeviceNet slave devices maximum slot amount for 1769 SDN scanner module inputs 246 Output Words This is the number of output words the controller assigns to the module The first two words 0 and 1 are required by the scanner module for status DeviceNet slave output data words start at slot word 2 You can have a maximum of 180 output words for DeviceNet slave devices maximum slot amount for scanner module outputs 182 Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Changing the 1769 SDN Configuration Module 1 1768 5DN DeviceNetScanner You can change add or remove the amount of data the controller has assigned to the scanner module in the expansion module configuration dialog From within RSLogix 500 software I O configuration open the 1769 SDN scanner module and change the input or output words as needed Save the program and download to the controller Reducing the number of words for either inputs or outputs will require a change in the 1769 SDN scanner module s scanlist which is done using RSNetWorx for DeviceNet software IMPORTANT We recommend that you not reduce the number of words assigned to a 1 69 SDN scanner modules scanlist once a system is operational Changing the num
41. 769 SDN scanner clears all existing configuration Notice that the 1769 SDN module status indicator flashes red and back to green while the status display momentarily shows 72 When the AutoScanning is complete the status display blinks between 65 and the node address of the scanner On the AutoScan set up screen press either the Up Arrow a Of Down Arrow gt M Press SEL Ej twice and then press lt Enter gt to save your changes Press lt ESC gt ES three times to return to the Network Who scteen on the 193 DNCT terminal If all the devices on the network are properly mapped the scanner status display blinks back and forth between 80 and the node address of the scanner IMPORTANT With 193 DNCT terminal version 2 1 and higher the active nodes line on the Network Who screen should show a number that exactly matches how many slave devices are on the DeviceNet network If the number on the active nodes line doe not match the number of slave devices on the network the cause typically is one of the following e The consume O data size of a device is greater than the selected l O allocation size e he slave device is not on the network Put the controller into Run mode and verify that the scanner is in Run mode CommandRegister Run is 1 in the scanner control output word 0 The scanner status should display only the node address of the scanner If it is flashing other codes as well refer to Chapter 8 T
42. 9 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 The MicroLogix 1500 1764 LRP processor and the 1769 SDN scanner module also support backplane messaging This new level of functionality allows the processor to read get or write set data to other devices on the DeviceNet network This is also referred to as Explicit Messaging You can use two different types of messages to exchange information with the DeviceNet device The type of message used is determined by the destination device You can generate a PCCC message or a CIP message PCCC Messaging Programmable controller communications commands PCCC provides point to point and master slave communication between devices PCCC is an open protocol that is built into all Allen Bradley controllers and many other Allen Bradley and third party products PCCC messaging has been used for many years on DH 485 DH and Ethernet networks and for point to point communication between Allen Bradley controllers PCCC messaging lets you upload or download programs over the DeviceNet network and allows users to message across DeviceNet networks just like they did using DH 485 or DH networks There are a number of devices that support PCCC messaging over DeviceNet including the 1761 NET DNI DNI interface 1203 GU6 interface and RSLinx software If the DeviceNet network has DNI interfaces either device can initiate a PCCC message 111 Chapt
43. August 2009 Overview Chapter 1 Scanner Module Operation In a typical configuration the scanner module acts as an interface between DeviceNet devices and the programmable controller Device Network PLC with RSNetWorx for DeviceNet software CompactLogix controller with MicroLogix 1500 controller 1769 SDN scanner with 1769 SDN scanner Interface card 0000 0000 oo o eri 1734 POINT 1 0 E3 Overload PowerFlex 40 Drive MicroLogix 1000 Controller MicroLogix 1200 Controller Relay Enhanced DeviceNet with 1761 NET DNI with 1761 NET DNI Communications Module The scanner module communicates with DeviceNet devices over the network to Read inputs from slave devices Write outputs to slave devices Communicate with peer devices messaging Upload download programs to a 1764 LRP based MicroLogix 1500 controller across a DeviceNet network Publication 1769 UMOO9E EN P August 2009 13 Chapter 1 Overview Communication with Your Slave Devices 14 The scanner module communicates with devices via strobe poll change of state or cyclic I O messages It uses these messages to solicit data from or deliver data to each device Data recetved from the devices input data is organized by the scanner module and made available to the controller Data sent from your controller output data is organized in the scanner module and sent on to your devices A strobe message is a multicast
44. E la Lontiguraton L Peco ety Autoddress oS Ll Ti ETT 2 Click Load Device Config This will load the configuration of each device selected into the scanner module configuration software If you ate online but did not upload the netwotk the configuration retrieved for the devices may not be what is actually used online 82 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 3 Click the Configuration Recovery checkbox 17B59 5DH Scanner Module 1 cm 4 1731D BBSP Notice the ADR space in M us bytes is displayed for the 08 1751 MET D module you are updating 4 Click the Auto Address Recovery checkbox if desired The Enable Auto Address Recovety checkbox needs to be checked in order for AAR to work 5 Repeat steps 1 4 for each desired module Notice that Both indicates Configuration Recovery and Auto Address Recovery ate enabled while Config indicates that only Configuration Recovery is enabled 1 769 SDN Scanner Module 1 Upload from Scanner Tovro bo Scanner a j2 17900 8849 Both em 4 1731D 8BSFP Config SDHWE Both EJ 08 1761 NET D Config m Lonhguration D mmu Pet ET 6 When finished click Download to Scannet 7 Click Apply or OK Publication 1769 UMOO9E EN P August 2009 83 Chapter5 Manually Configure the DeviceNet Network Summary Tab The summary tab provides a condense
45. N P August 2009 129 Appendix B How the Backup Works 130 CompactLogix Backup on the DeviceNet Network The following figure shows an example backup system In the backup system the following occurs Primary Controller moa muu wt secondary Controller Both controllers scanners simultaneously receive all inputs Both controllers execute in parallel but are not synchronized Only the primary controllers send output data to the I O devices A virtual switch in the 1769 SDN scanner module is used to switch outputs between primary and secondary controllers After failure or forced switchover outputs are automatically switched by the 1769 SDN scanner module from the primary controller to secondary When the switch occurs the secondary controller becomes the primary controller The switchover occurs so quickly that the I O devices do not timeout these devices are unaware that redundant controllers scanners exist and are unaware of the switchover DeviceNet Network P Eo m f D M oO D 000 B pan O DU e LINE EO a Wu J Primary Scanner Module QD Allen Bradley j c o aL Allen Bradley aum iea oon
46. N7 0 will recetve 2 bytes 1 word of data General This Controller Control Bits Channel Slat Port Ignore if timed out TO D Communication Command CIP Generic r Data Table Address Receive Send Awaiting Execution Ew 0 Size in Bytes Receive E Send Error ERI n Irar Target Device Message done DM n Message Timeout Message Transmitting ST 0 Target Type Message Enabled EM n Local Node Addr dec D 117 Chapter7 Use the 1769 SDN Scanner Module with MicroLogix Controllers larget Device MSG Rung 3 0 MG11 1 iran LIP Generic Write Output Point Head Output Paint Head Input Paint Read Parameter Generic Get Attribute Single Generic Set Attribute Single Generic Get Member Generic Set Member Field Definition Message Message timeout Is specified in seconds If the target does not Timeout respond within this time period the message instruction will generate a specific error The amount of time that is acceptable should be based on application requirements and network capacity loading Target Type You can select either Module or Network Device If you need to message to a device on the DeviceNet network select Network Device If you need to message to a DeviceNet parameter on the scanner select Module This allows the control program access to module parameters Many of the module parameters are not editable and some can be edited only when the mod
47. Publication 1769 UMOO9E EN P August 2009 35 Chapter4 Automatically Configure a DeviceNet Network How AutoScan Operates 36 AutoScan is active when the feature is enabled and the scanner is in IDLE mode When active the scanner attempts to connect to each device not enabled in the scan list The scanner only checks for devices with node addresses between 0 and 61 inclusive The connections to these devices are made on a round robin basis When a device is found the scanner gets the Produced and Consumed data sizes from the slave devices s Connection Object instance s If the Produced data size is greater than the configured I O allocation size the device is added to the scanlist with a produced size set equal to the I O allocation size When this happens an I O connection is made with the device But it errors and error code 77 1s displayed on the 1769 SDN for the device s node number f the Consumed data size is greater than the configured I O allocation size then the node is rejected and not entered into the scan list However you can change the I O allocation size as described in Configure I O Allocation Size Via the User Program to accommodate the device with the largest Produced and Consumed data sizes in your scanlist For qualitying nodes the scanner enters the device into the scan list and attempts to allocate an I O connection using one of the following communication format choices in this particular o
48. Register 98 CompactLogix Command Register 100 Input Data Image 102 1769 SDN Output Structure 102 The 1769 SDN scanner module s input image is configurable up to 246 words The input image is broken into two primary components the status area and the input data area Input Image Word Offset Status Structure 66 words fixed 0 65 Input Data Image 180 word array configurable 66 245 Name 87 Chapter 6 MicroLogix 1500 Status DeviceNet I 0 Image The first area of the MicroLogix 1500 controller input image is the Status S tructure Structure The status words are described in more detail in the following sections Description Words 0 Data Type ocan counter adi 2 words Device failure array 64 bit array Autoverify failure array LO MEN 64 bit array Slave device idle array 64 bit array Active node array 64 bit array Reserved 4 byte array ocanner module status 4 byte array Reserved array 20 byte array Device status array 64 byte array Module status register 2 words Do not manipulate reserved bits Doing so may interfere with future compatibility Scan Counter This 32 bit unsigned value is incremented each time the DeviceNet network is scanned The value will automatically roll over to zero and continue counting 88 Publication 1769 UMO09E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Device Failure Array These 64 bits provide status information for
49. Scan requires 16 bytes x 32 512 bytes 128 DINT of I O space in both the scanner s input and output table Assuming it is a CompactLogix system the maximum scanner input data table size is 90 DINT and 90 DINT for output The required space exceeds what the 1769 SDN can support The user would need to adjust the I O allocation size or reduce the slave device count on the network to include all of the devices in the scanlist Devices outside of the scanner s allowable I O image space will be rejected and will not be included in the scanlist See Scanlist on page 54 for an accurate maximum node count by allocation size 53 Chapter 4 54 Automatically Configure a DeviceNet Network Scanlist Data Allocation bytes 1 2 3 4 D 6 8 d 10 Max Node 61 61 61 61 61 60 91 45 40 36 32 30 2 25 24 22 21 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 The AutoScan feature is automatically disabled in the scanner as soon as the scanner configuration is modified by RSNetWorx for DeviceNet software For example any manual changes to the scanlist using RSNetWorx for DeviceNet software disables the AutoScan feature in the scanner One new status code has been added to the Node Status list This code is presented in the Node Status Table Status Code Decimal Description of Status 65 AutoScan Active Scanner on
50. T DNI Series B DeviceNet Interface aes 7 1761 NET DNI ice Net Inter 0 61 NET DNI Device Net Interface m 3 22 1769 SDN Scanner Module Workstation JE 52 Workstation SLX 527 gs AB_DF1 1 DF1 In this example the DeviceNet interface is a 1770 KFD module Selecting the 1770 KFD driver will show the devices on the DeviceNet network In this example upload or download can be performed with the devices at nodes 5 6 7 and 32 Node 32 is a 1769 SDN module Simply highlight the 1769 SDN module and click either Upload or Download on the right side of the screen Publication 1769 UMOO9E EN P August 2009 Configure a Local DeviceNet Message Publication 1769 UMOO9E EN P August 2009 Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 This section describes how to configure a local message by using the scanner module and a MicroLogix 1500 1764 LRP processor Message Setup Dialog SLAD 3 MSG File e 0000 e Read Write Message k MSG File MG11 1 S Scree MSG Rung 3 0 MG11 1 e Read Rung 0 shows a standard RSLogix 500 message MSG instruction preceded by conditional logic Access the Message Setup dialog by double clicking the Setup Screen The RSLogix 500 Message Setup dialog appears This dialog 1s used to set up ot monitor message parameters for this controller target device and control bits Descriptions of each of these sections follow 113 Chapter7 Use
51. a ER aun adest des 64 Set the Node Address o2 oio die cb eedee dite PERI AE 67 Coon ure the T Deve esnia EE S Ne PER EUER OSnREMS 70 Quar MIR Io cada an Stee tk dav sb en de T TE eres oe Gh are 71 IN MONGOL Tih ETC PECTORI A a ates ee p DEAS ED EET RETENTO dentine aera atte bee ee 76 Input D3Dooey uia pee P E RE EA veta itt atc vaste d 78 Auto Device Replacement ADR PAb a sea 2o ith 4 dees 80 DURO TAD a eek dux doen t wae ten oe ridet dodi 84 Download and Save Your Configuration 005 84 Publication 1769 UMOQ9E EN P August 2009 Table of Contents Chapter 6 DeviceNet l 0 Image NiO cUi eee r erie pda ee LUI Sdu MM MM E CET 87 170959 DINSIBDUE DEEOCEUEE 3d s etu e dato de E d beds 87 MicroLogix 1500 Status Struchites coda E HERE PEE SURE DG RUE 88 SGA COU ekra ira oat ae ee a os Gi ag EA ICI S 88 Device Taute 2 uray 2o Lace ddraodecuo aue ORE VC RATER ees 89 INUtOVELIDy Fallute Aa ee baa ed RP HDD PPM ER Ed 89 blave Device Idle AAEFAVCC Y da ocho a aO ae Ed ao arb ERU aes Em qa 90 ACUve NOGdGJUCAV yi qu PWYESERWE NEN ENSE ENENE E T ieh 91 Scanner Module Status ds ci Sate wad weeds Soudan dau weet n 91 Reserved NIT AN Led io dobech sdb asa kd Ganache each Bee a 92 Dere oa S A pig Ex Ru a Gate tee d gene OE 92 Module Status Reo Ei osasse riai eean ed Rc etd b ed 93 CompactEoP PC Status SUCI ns teu disp to EEE EA gros 94 EEE RR E E EE E E E E EET 94 Device Panute Rector ords aioe od rE eee dy VES 95 A toverify Fal re Re
52. a Sos wht E Bad eee 35 FLOW AutoScan Operil e Sreser ce outil ed tai eee Lowes b eng 36 Determine If You Can Use AutoScan 0 eee 38 How AutoScan Effects Your Netwotk lesen 38 Connect Each Device to the Network leen 39 Set the Baud Rate of a Device Via a DeviceNet Contisuralion Vernal as s seu stat pre Eon a echt Rc A Yon os 40 Set the Node Address of a Device Via a DeviceNet Contisuradon Eennidal ues nd quie n iced UU d 6 3 depu ieu 42 Add the Scanner to the RSLogix 5000 Project 0 6 002 0046 44 Add the Scanner to the I O Configuration Folder 44 Define the Properties of the Scanner 4 4 ves Tu eset Sob Eq 45 Implement AO SCA Lee nett dq ook e ee eae ee coe 46 Initiate AutoScan Via the User Program 49 Initiate AutoScan via the 193 DNCT Terminal 51 Additional Considerations Regarding AutoScan liu 53 Type of Connection that the Scanner Sets Up 56 Decess DDevieec D dE ud see 09 9 Sean QE ced V we seio e 57 Put the Scanner in Run Mode dacs o cack FN UR pt 60 Chapter 5 roduc HOTU accosted Ads ote E Do ted OOS uut Peake She aes 61 SONWALE Ver ONS qud werden diea hehe ode Dis net o cde aule a 61 PIS PAE SOIL uou S Ens us tot ea age e uu Ee I 62 Use RSLinx Software to Configure Your DeviceNet Driver 62 Use RSNetWorx fot DeviceNet Software to Configure tbe TOSIN SCIS 11s o pa ect dovuta a Boe 64 Set Up an Online Connection es sec
53. apter 5 Advanced The scanner module allows each node s slave data to be broken up segmented into separate input image areas This capability lets you group data from multiple slave nodes into contiguous memory locations This is simply an ease of use feature For maximum performance do not segment a slave device s data 0 0 Discrete 66 0 lt not mapped gt lt not mapped gt lt not mapped gt Output Tab The output tab dialog lets you define how data from the scanner module is mapped to the outputs of the slave devices EE 1769 SDN Scanner Module 1 Ga 04 1781D 888P COS gt J 06 1769 ADN Co COS B 08 1761 NET DN COS 79 Chapter5 Manually Configure the DeviceNet Network In this example four output devices are mapped into the scanner s output image The dialog box shows each device s node number catalog numbet connection type used between the scanner module and the slave device strobed polled cyclic or change of state amount of data that will be exchanged in bytes wotd within the controller s output image Auto Device Replacement ADR Tab The Auto Device Replacement feature automates the replacement of a failed slave device on a DeviceNet network by returning it to the prior level of operation This includes Configuration Recovery CR and Auto addtess Recovery AAR CR allows a slave device to be removed from the network and replaced with an
54. ber of words may cause addressing problems on the controller side and mapping changes on the DeviceNet network Adding words to an existing system Is relatively easy to do because it doesn t affect existing addresses or mapping Add the number of additional words that are needed in the module using the above example and change the scanlist using RSNetWorx for DeviceNet software Publication 1769 UMOO9E EN P August 2009 109 Chapter 7 110 Use the 1769 SDN Scanner Module with MicroLogix Controllers The configuration dialog for the scanner module is shown below Module 1 1769 SDWN DeviceNetScanner Ignore Configuration Error Checking enabling the Ignore Configuration error checkbox instructs the module to ignore I O size mismatches If this is checked and the input output scanlist configured by RSNetWorx for DeviceNet software DeviceNet side of the 1769 SDN scanner module does not match the amount of I O data assigned by the controller 0 180 words the module will not generate an error If this checkbox is not checked the number of data words on the controller side must match the number of words configured by RSNetWorx for DeviceNet software The default condition is unchecked report an error on mismatch series Major Rev Minor Rev You will need this information 1f you contact Rockwell Automation Technical Support Publication 1769 UMOO9E EN P August 2009 Backplane Messaging Publication 176
55. cation 1769 UMOO9E EN P August 2009 27 Chapter3 Installation and Wiring System Mounting During panel or DIN rail mounting of all devices be sure that all debris metal chips wire strands is prevented from falling into the module Debris that falls into the module could cause damage at power up Minimum Spacing Maintain spacing from enclosure walls wireways and adjacent equipment Allow 50 mm 2 in of space on all sides for adequate ventilation as shown below Top Side Side Host Controller Compact 0 Compact 0 Compact 0 Compact 0 Compact 0 End Cap Bottom Allow at least 110 mm 4 33 1n of enclosure depth to accommodate the scanner module and the DeviceNet connector Panel Mounting Mount the scanner module to a panel using two screws per scanner module Use M4 or 8 panhead screws Mounting screws are required on every module 28 Publication 1769 UMOO9E EN P August 2009 Installation and Wiring Chapter 3 Panel Mounting Using the Dimensional Drawing All dimensions are in millimeters inches Hole spacing tolerance 0 4 mm 0 016 1n Compact I 0 System with L35E CompactLogix Controller and Power Supply 6 5 mm 2 68 in 70 0 mm 35 0 mm 15 mm a 2 76 in 1 38 in 0 59 in an A Logix L35E 132 mm 5 20 in n 118 mm 2 4 65 in Y Y PIA Lfd Hi Lfd L6 52 5 mm L L350 mm Somn 2 35 0 mm Som 7 207 in 11 38 in f 138in 138in 138i
56. ceNet software to register the new EDS file Access the wizard from the Tools menu Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 Set the Node Address Once the network browse is complete the node addresses appear to the right of their icons Use this procedure to change the node address of devices on the network such as a photoeye You can also change the network communication rate baud rate of some devices Depending upon the device you may need to cycle power for communication rate changes to take effect The controller must be in Program mode or the scanner module in Idle mode bit 0 of the Module Command Array 0 for the scanner module to accept the configuration information 1 From the Tools menu choose Node Commissioning E Hode Commissioning ru Bap EHI 67 Chapter 5 Manually Configure the DeviceNet Network 68 2 Click Browse Device Selection 1747 S0N Scanner Module 1761 NET DONI Seres B DeviceNet 1761 NET ONI Series B DeviceNet 1761 NET DONI Device Net Interface Workstation 3 Select the DeviceNet network The devices on the network will appear in the right panel of the dialog Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 4 Select the device you ate commissioning in the rig
57. ced m Consumers C Consumed 5 Alias For Lecat2 L D ata3 0 z Data Type ata ype POOL j SGT GqUITE 6 5 EM M Style Decimal 7 E Lacat 2l Select the address of the data pogale fortasse gu Click W to select a bit 7 Local 2 1 Data epee 8 S iori r2 n3 ra r8 16 17 r8 18 2021 22 23 24 26 26 27 28 29 30 3 Look in the Controller Scoped T age Program Scoped Tags controller scoped tags Publication 1769 UMOO9E EN P August 2009 59 Chapter4 Automatically Configure a DeviceNet Network Put the Scanner in Follow these steps to run the DeviceNet network Run Mode 1 Place the controller in Run Remote Run mode 2 Set the following bit of the output structure for the scannet If you want to run the network 0 CommandRegister Run not run the network idle mode Q Commandhegister Run 3 Check to see if the scanner is in Run mode by making sure an 80 status code does not appeat on the scanner s display 60 Publication 1769 UMOO9E EN P August 2009 Introduction Software Versions Publication 1769 UMOO9E EN P August 2009 Chapter 5 Manually Configure the DeviceNet Network This chapter describes how to configure the DeviceNet network using RSLinx and RSNetWorx for DeviceNet software This table describes what this chapter contains and where to find specific information Topic Page Software Versions 61 Install the Software 62 Us
58. circuits equipment or software described in this manual Reproduction of the contents of this manual in whole or in part without written permission of Rockwell Automation Inc is prohibited Throughout this manual when necessary we use notes to make you aware of safety considerations 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 IMPORTANT Identifies information that Is critical for successful application and understanding of the product ATTENTION Identifies information about practices or circumstances that can lead to personal injury or death property damage or economic loss Attentions help you identify a hazard avoid a hazard and recognize the consequence SHOCK HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that dangerous voltage may be present BURN HAZARD Labels may be on or inside the equipment for example a drive or motor to alert people that surfaces may reach dangerous temperatures o A AN A A Allen Bradley Compact I O CompactLogix MicroLogix POINT I O PowerFlex 40 Rockwell Automation RSLogix 500 RSLogix 5000 RSLinx RSNetWorx for DeviceNet and TechConnect are trademarks of Rockwell Automation Inc Trademarks not belonging to Rockwell Automation are property of their respective companies Sum
59. ckup on the DeviceNet Network Appendix B The 1769 SDN scanner module s status indicators provide useful information for example determining which scanner module is primary about backup scanner module status Module Status Indicator MODULE p gt NETWORK mm Network Status 9 DerfceNet Indicator a ADDRESS ERROR BH Node Address and otatus Display Module Status Indicator This table lists the indicators to monitor when checking backup status Module Status Indicator Behavior If this indicator Exhibits this behavior This condition exists Module status MS Flashing red e Recoverable Fault Memory has been erased or is being programmed e Bad firmware in module 141 Appendix B CompactLogix Backup on the DeviceNet Network Node Address and Status Display The seven segment numeric display shows the following information about the primary and secondary scanner modules in either Run or Idle modes TIP If error codes other than those shown in these tables appear in the display refer to Chapter 8 Troubleshooting for more information on error codes Primary Scanner Module With Valid Backup Scanner Module Run Mode Node Number LEEREN 01 or 00 otatus 67 Backup mode enabled or 00 Run mode Primary or Secondary S Secondary Node Number 00 01 or 00 Status 67 Backup mode enabled or 80 Idle mode Primary or Secondary S Secondary Primary Scanner Module Without Valid Backup Scanner Module
60. code for the displayed node address e When it flashes alternating numbers one is the error code 70 99 and the other is the node number 0 63 that has generated the error Publication 1769 UMO009E EN P August 2009 123 Chapter8 Troubleshooting Error Codes The following table describes the error codes indicated by the seven segment numeric display Device Status Code Description decimal 67 Backup Mode ocanner in Backup Scanner mode 68 No Backup Scanner No backup scanner module present Install and configure a backup scanner if needed 69 Backup Scanner Invalid The configuration of the primary and the secondary controller does not match Either one or both CRC of the configurations is incorrect Make sure that the same configuration is downloaded to both scanners 70 Duplicate Node Controller has Failed Duplicate Node Address Check The node address selected is already in use Change the module s or conflicting devices network address node number to an available one 71 Illegal Scanlist Data Illegal data in scanlist Reconfigure the scanlist table and remove any illegal data 72 Slave Timeout One of the module s slave devices has stopped communicating Inspect the module s slave devices and verify the DeviceNet connections 13 Electronic Key Mismatch The slave device Vendor ID key parameter does not match the slave s configuration in the module s scanlist Make sure that the device at the flashi
61. croLogix 1500 system e 1770 KFD RS 232 DeviceNet adapter or 1784 PCIDS 1784 UZDN DeviceNet interface card For network communication RSLinx software version 2 30 or later For DeviceNet network configuration RSNetWorx for DeviceNet software version 3 00 or later For ladder logic programming RSLogix 500 programming software version 5 00 10 or later or RSLogix 5000 programming software version 8 02 or later e 1769 SDN scanner module Mounting hardware e Screwdriver Publication 1769 UMQQ09E EN P August 2009 19 Chapter2 Quick Start for Experienced Users What You Need to Do Follow these steps to get started using the 1769 SDN scanner module 1 Verify planned system configuration a Ensure system power supply has sufficient current Maximum Current Draw Module 24V DC 1769 SDN 440 mA 0 mA The scanner module cannot be located more than fout modules away from the system power supply b Verify that the DeviceNet network has adequate powet DeviceNet Power Requirements Module DeviceNet Power Requirements 1769 SDN N E C Class 2 90 mA 11V DC max 110 mA 25V DC max 200 mA for 1 5 ms inrush 2 Remove power Remove power before removing or inserting this module When you remove or insert a module with power applied an electrical arc may occur An electrical arc can cause personal injury or property damage by e sending an erroneous signal to your system s field d
62. ct to the network as long as the device uses input data and output data sizes that fit in the New devices are automatically While the scanner is in idle mode AutoScan continues to establish communication with devices that scanners 0 allocation size The Automatic Device Recovery You have to use RSNetWorx for DeviceNet software to edit the configuration of the scanner to use the ADR option is not available Automatic Device Recovery ADR option of a DeviceNet scanner This turns off AutoScan Connect Fach Device to As P connect your devices to the DeviceNet network follow these the Network i 1 Assign an address to each device The following addresses are recommended but not required Give this address To this device 0 scanner 1 61 your devices 62 hand held configurator such as the DeviceNet Configuration Terminal catalog number 193 DNCT 63 Leave open Out of the box a DeviceNet device is preset for address 63 Leaving address 63 open lets you get a new device on the network without conflicting with another device 2 Connect the scanner and any network interface to the network By first connecting the scanner and or network interface device to the network you reduce the number of baud rate errors as you connect the rest of your devices e Scanners and network interface devices use a fixed baud rate e Sensors and similar DeviceNet devices use autobaud to set their baud rate They wait for another device to commu
63. d Communication tabs Message Configuration Read_Backup_Status x Message Configuration Head Heartbeat x Configuration Communication Tag Configuration Communication Tag Message Type Path DeviceNet DeviceNet dug Be Atre Single xl zource Fauan z Samoa ov EHI Source Length fo Bytes SGE x DA Chame Destination Link p SEICE e 57 n MD D Gade Nex Class S0 Hex Destination Backup Status i ole Hin Source links fp Destination Wade p etal JOUIGE Instance E Attibutefi 4 Hex mm Connected v Cache Connections e Enable lt 2 Enable Waiting Start Done Done Length 0 O Enable 12 Enable Waiting Start Done Done Lenath 2 Error Code Extended Error Code Timed Out Error Cor Extended Error Code Timed Out Error Path Error Path Error Text Error Text Cancel Help OK Cancel Help This table describes the possible values this message may return when reading the backup status of the DeviceNet scanner module If the message The backup state of the DeviceNet scanner module is reads this value 0 No backup scanner module detected 1 Primary scanner module forcing Idle backup in Run mode but primary in Idle mode 3 Primary scanner in Run mode detects backup scanner in Idle mode Publication 1769 UMOO9E EN P August 2009 Using Indicators to Check Status Publication 1769 UMOO9E EN P August 2009 CompactLogix Ba
64. d MicroLogix 1500 programmable controllers and DeviceNet devices via the 1769 SDN scanner module Topic Module Features Scanner Module Operation Communication with Your Slave Devices 1769 SDN Scanner Module Data Tables RSNetWorx for DeviceNet Software as a Configuration Tool The configuration data tables and the RSNetWorx for DeviceNet dialog boxes used to configure the data tables are also described in this chapter Before configuring your scanner you must understand these items Data exchange between the programmable controller and DeviceNet devices through the scanner User configurable scanner module data tables e Role of RSNetWorx for DeviceNet software These topics are covered briefly in this chapter and in more detail throughout the rest of the manual Publication 1769 UMOO9E EN P August 2009 11 Chapter 1 Overview Module Features 12 Use the following figure to identify the features of the scanner Module Features Item 1 2A 2B 3A 3B 4 9 6 7A 7B 8A 8B 9 Description Bus lever with locking function Upper DIN rail latch Lower DIN rail latch Upper panel mounting tab Lower panel mounting tab Module and Network status LEDs Address and Error numeric display Grounding screw DeviceNet mating male receptacle Removable DeviceNet female connector Movable bus connector with female pins Bus connector with male pins Nameplate label Publication 1769 UMOO9E EN P
65. d picture of the scannet s configuration which nodes are mapped if they are active and receive and transmit information 1769 SDN Scanner Module 1 Download and Save Your Configuration Follow these steps to download and save your configuration 1 Click the Scanlist tab and then Download to Scanner Download Scanlist to Scanner o e Selected Stanlet i EC VOIR 2 Click All Records 3 Click Download to download the configuration to the scanner 4 Click OK to complete the DeviceNet scanner module configuration 84 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 5 From the File menu choose Save As news de 1769 5DH DeviceNet Files drt 7 6 Save the configuration to a DeviceNet file 7 Close RSNetWorx for DeviceNet software Publication 1769 UMOO9E EN P August 2009 85 Chapter 5 Notes 86 Manually Configure the DeviceNet Network Publication 1769 UMOO9E EN P August 2009 Introduction 1769 SDN Input Structure Publication 1769 UMOO9E EN P August 2009 Chapter 6 DeviceNet l 0 Image This chapter describes the input and output data structure This table describes what this chapter contains and where to find specific information Topic Page 1769 SDN Input Structure 87 MicroLogix 1500 Status Structure 88 Module Status Register 93 CompactLogix Status Structure 94 CompactLogix Status
66. dy to communicate The default scanner module settings are Communication rate 125 Kbps Node addtess 63 Use your configuration software to change the communication rate and node address 33 Chapter 3 Notes 34 Installation and Wiring Publication 1769 UMOO9E EN P August 2009 Chapter 4 Automatically Configure a DeviceNet Network Introduction This chapter provides a quick method for configuring a DeviceNet network It uses the AutoScan feature to establish communication between the controller and your devices with minimal steps Topic Page Determine If You Can Use AutoScan 38 Review How AutoScan Effects Your Network 38 Connect Each Device to the Network 39 Add the Scanner to the RSLogix 5000 Project 44 Implement AutoScan 46 Additional Considerations Regarding AutoScan 53 Access Device Data 5 Put the Scanner in Run Mode 60 The DeviceNet AutoScan feature enables a scanner to automatically map a network of slave devices into its scanlist without the use of RSNetWorx for DeviceNet software This greatly improves the ease of setting up a DeviceNet netwotk especially networks comprised of simple devices When the feature is enabled a DeviceNet scanner continuously searches for devices on the network Once a qualifying slave device is found it is added to the scanner s scanlist and its I O data is mapped into a predefined location in the scanner s I O memory table based on the device s node address
67. e Enable Waiting D Start D Done Done Length 0 Error Code Extended Error Code Timed Out Error Path Error Text Cancel Apply Help Publication 1769 UMOO9E EN P August 2009 49 Chapter 4 Automatically Configure a DeviceNet Network 50 5 Set the path to your DeviceNet scannet Message Configuration InitiateAutoScan Configuration Communication Tag Path DeviceNet Scanner 0000000000000 DeviceNet Scanner EE Connected Enable Enable waiting D Start 3 Done Done Length 0 Error Co Extended Error Code Timed Out Error Path Error T ext OF Cancel Apply Help 6 Return the scanner to Run mode that is bit 0 in the scanner control output word 1 and the scanner status display should display the scanner node address The previous example is from RSLogix 5000 programming software refer to the appropriate user manuals to determine how to perform explicit messaging in other PLC platforms Publication 1769 UMOO9E EN P August 2009 D Allen Bradley eso seu a w Le EIU a e Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 Initiate AutoScan via the 193 DNCT Terminal Follow these steps to enable AutoScan using the 193 DNCT terminal version 2 1 or higher 10 11 Put your controller into Program mode and verify that the scanner is in Idle mode CommandRegist
68. e RSLinx Software to Configure Your 62 DeviceNet Driver Use RSNetWorx for DeviceNet Software to 64 Configure the 1769 SDN Scanlist This table lists the software and revision level required to operate with the 1769 SDN scanner module Function Software Version Communication 2 30 or later DeviceNet configuration 3 00 or later Ladder logic programming software 5 00 10 or later 0 02 or later You will also need one of the following interfaces to use your computer to communicate with the DeviceNet network 1770 KFD RS 232 DeviceNet adapter e 1784 PCD or 1784 PCID DeviceNet interface card If your RSNetWorx for DeviceNet software does not include the required Electronic Data Sheet EDS file go to http www ab com networks eds Register the new EDS file using the EDS Wizard in RSNetWorx for DeviceNet software Access the wizard from the Tools menu 61 Chapter5 Manually Configure the DeviceNet Network Install the Softwa re Follow these steps to install RSLinx and RSNetWorx for DeviceNet software 1 Insert the software CD ROM in the drive The CD ROM supports Windows Autorun If you have Autorun configured the installation will automatically start when you insert the CD ROM in your drive If you do not have Autorun configured perform steps 2 and 3 2 From the Windows Start menu choose Run 3 Browse for the Setup program on the CD ROM and open it 4 Follow the prompts that appear as you install the software A
69. eNetO CommandRegiste Aun Set Heartbeat DM MSG 3 i Type CIP Generic Message Control Head Heartbeat Verify No5 Po LJ If scanner successfully configured ar scanner already in RUN mode then set scanner ta RUN mode NOTE Since scanner resets after being configured there may be a delay END OF BACKUP INITIALIZATION DeviceNetO CommandRegiste Aun Read Heartbeat DM Qu DeviceNet D CommandRegister Hun 4 j Equal Source amp Current Heartbeat e Source B Config Heartbeat 16 DeviceNet 0 CommandRegister Hun Rung 3 Message Configuration and Communication tabs Message Configuration Head Heartbeat Verify CIP Generic DeviceNet i i SOUTCE EIEMent VIR AS Get Attribute Single E 2 LCA VO ECT FPN HT EA SGUTGE SET T S ples ee E Se Die Erina Destination ink EX teft 2 al 1 Current Heartbeat e 3 EP vin Source Linke zi Destination Node zi Meci SOUEEN v ISGIGHERLEGTITTEGUGITTS This completes the required portion of ladder logic to enable the CompactLogix backup on the DeviceNet network The following sections describe how to use additional ladder logic to read backup state and status Howevet these sections are not required to complete the backup solution Publication 1769 UMOO9E EN P August 2009 137 Appendix B CompactLogix Backup on the DeviceNet Network Reading Backup State Rung You can read the backup state of the DeviceNet scanner
70. eartbeat Rate Devices that are configured for change of state data will send data at this rate if no data change occurs Host Platform The computer on which the application software is run LO Input and output modules Input Data Data produced by a DeviceNet device and collected by the scanner module for the host platform to read MAC ID The network address of a DeviceNet node Also referred to as node address Multicast Used when describing a strobe message Glossary 149 Network The DeviceNet network or the RSNetWorx for DeviceNet software representation of the network Node Hardware that is assigned a single address on the network Also referred to as a device Offline When the host platform is not communicating on the network Online When the host platform is configured and enabled to communicate on the network Output Data Data produced by the host platform that is written to the scanner module s memory This data is sent by the scanner module to DeviceNet devices Point to Point Used when describing a poll message The message solicits a response from a single specified device on the network Polled A type of input output data communication A polled message solicits a response from a single specified device on the network a point to point transfer of data Record The node address and channel specific memory assigned in the scanner module s nonvolatile storage for a node in the scanlis
71. endix B CompactLogix Backup on the DeviceNet Network Introduction This appendix offers a solution to back up your CompactLogix controller on the DeviceNet network CompactLogix system backup on the DeviceNet network is a simple low cost back up system most effective when used in smaller applications that require fast switchovers from a primary to a secondary controller Topic Page How the Backup Works 130 Configure the Backup System 132 Develop the CompactLogix Backup 134 Application Using Indicators to Check Status 141 Development and Debugging Tips 144 This back up solution minimizes downtime in case of controller failure when the same program is used in both controllers mitigates the risk of changes adversely affecting the application use old proven program in one controller and new untested program in the other controller If the new untested program causes a problem a forced switchover can be made to the older proven program without downloading the program again The CompactLogix backup on the DeviceNet network solution takes advantage of Shared DeviceNet Mastership of Slave I O Devices technology Typically only a single DeviceNet master exists for any particular slave With Shared DeviceNet Mastership two masters can exist Heartbeat communication between primary and secondary controllers determines which scanner module is the master and which scanner module remains in Standby mode Publication 1769 UMOO9E E
72. er This dialog provides the ability to change the driver or perform a Who Active across a network to locate the specific MicroLogix controller If the driver and path are correct click Read I O Config Installed 1 0 I O Configuration High Speed Counter 8 Input Isolated 120 VAC 16 Input 79 132 VAC Analog 4 Channel Input Module Analog 4 Chan Inp 2 Chan Out 12 Input 159 265 VAC 0 Bul1764 Micrologix 1500 LAP Series C 16 Input 10 30 VDC 1 1769 SDN DeviceNetScanner 1769 IQ6X0W4 6 Input 24 VDC 4 Output RLY 2 17684016 16 Input 10 30 VDC 6 Channel RTD Module 6 Channel Thermocouple Module 8 Dutput 120 240 VAC 16 Output 24 VDC Source 16 Output 24 VDC Source w Protectio Analog 2 Channel Output Module 16 Output 24 VDC Sink 8 Output Relay 8 Dutput Isolated Relay DeviceNetScanner Power Supply Power Supply Power Supply RSLogix 500 software displays all of the I O modules that are attached to the MicroLogix controller In this example there is a 1769 SDN scanner module at slot 1 and a 16 point digital input module in slot 2 Publication 1769 UMOO9E EN P August 2009 107 Chapter 7 108 Use the 1769 SDN Scanner Module with MicroLogix Controllers 1769 SDN Scanner Module Configuration Double click the module to configure a specific module Double click the module in slot 1 to configure the scanner module in this example Input Words This is the number of input words the controller assigns to the module The first 6
73. er will allocate for each device it detects on the network Valid values range from 0 to 32 bytes per node 4 If you need to make additional configuration changes such as setting the Requested Packet Interval RPI leave the Open Module Properties box checked 5 Click OK Hew Module Type 1769 506 1769 Scanner DeviceNet Vendor Allen Bradley 1 dame ocal_ SDN Slat 1 Description Input Size 30 32 bit Output Size 30 32 bit 2 Eriet 1 Electronic Keping Compatible Keping 4 v Open Module Properties Cancel Help 6 When the Module Properties dialog appears that is if you left the Open Module Properties box checked make additional required configuration changes Publication 1769 UMQQ09E EN P August 2009 45 Chapter4 Automatically Configure a DeviceNet Network Implement AutoScan 46 Make sure that the appropriate version of DeviceNet scanner is used to implement this feature You must use the CompactLogix 1769 SDN DeviceNet scanner with firmware revision 4 1 or greater This section describes how to set up the feature and how it operates Notice that explicit messaging is used for some of the steps There are several ways that an explicit message can be sent on DeviceNet e A user ladder program External programming configuration devices such as the 193 DNCT terminal e RSNetWorx for DeviceNet software Since the purpose of the AutoScan feature is to eliminate the use of RSNetWorx for
74. er Run 0 and that all slave nodes are connected and communicating on the DeviceNet network Plug the 193 DNCT terminal into the DeviceNet network In the Network Who dialog press lt Up Arrow gt ES to navigate to and select the first line 0 1769 SDN DeviceNet Scanner Press lt Enter gt to go to the scanner s configuration dialog Press Down Artrow gt M to navigate to Scanner and press lt Enter gt A Press lt Down Arrow gt ad to navigate to AutoScan and press lt Enter gt E The AutoScan Setup dialog appears If AutoScan is selected and set to Enable press Up Arrow gt A to change the setting to Disable Press lt SEL gt Ed to scroll down to Save This disable the AutoScan feature Press SEL ed to scroll down to Mapping Type in the number of bytes that you want to automap to each DeviceNet node that is 1 32 The default is 4 bytes Press lt SEL gt Ed to scroll down to Save and press lt Enter gt E to commit yout byte size selections The AutoScan feature is now configured with the byte size entered in step 9 and step 10 For the 1769 SDN scanner to remap the network with this new setting the AutoScan feature must be re enabled 51 Chapter 4 52 Automatically Configure a DeviceNet Network 12 Change AutoScan setting to Enable and press SEL e to scroll down to Save When setting the AutoScan mode from Disable to Enable the 13 14 15 16 1
75. er7 Use the 1 69 SDN Scanner Module with MicroLogix Controllers Program Upload and Download 112 Before performing a program upload or download through the scanner be sure that the module is properly installed in the system and that a terminator is present at the end of the Compact I O expansion bus DeviceNet networks can operate at 125 Kbps 250 Kbps or 500 Kbps Depending on network size and communication activity performing program upload or download operations while the network Is controlling an application may impact control system performance It is up to you to know and understand how upload and download will impact operations Choose Comms System Comms to upload or download programs with RSLogix 500 software RSLogix 500 SDN MASTER b User ABit A SDN MASTER RSS MAIN_PROG B Project WIEST taut 30 EN Help WIEST IP TGGESSOTTYI ETTOTV 3 E gg Controller 0 i Controller Fo Histogram 0 0 Processor Status 0 5 Function Files Au IO Configuration ME HE Channel Configuration E gg Program Files 0B svso LE gysga T4 0 B3 0 eS ee DN 0001 System Comms will generate an RSLinx software dialog similar to the example below Communications E Workstation SLX 527 aa Lins Gateways Ethemet Ege 1770 KFD 1 DeviceNet f 00 1747 SDN Scanner Module 0 B 05 1761 NET DNI Series B DeviceNet Interface 07 1761 NET DNI Devi H 06 1761 NE
76. erved bits Doing so may interfere with future compatibility Input Data Image CompactLogix The input data image is transferred from the scanner module to the controller across the Compact I O bus 0 89 DeviceNet slave inputs 90 DINT array Output Data Image CompactLogix The output data image is transferred from the controller to the scanner module across the Compact I O bus 0 89 DeviceNet slave outputs 90 DINT array For additional information about the CompactLogix image structure refer to the DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 16 Publication 1769 UMOO9E EN P August 2009 RSNetWorx for DeviceNet Software as a Configuration Tool Publication 1769 UMOO9E EN P August 2009 Overview Chapter 1 RSNetWorx for DeviceNet software is used to configure the scanner s slave devices This software tool connects to the scanner module over the DeviceNet network via an RS 232 interface 1770 KFD module or PC card 1784 PCD or 1784 PCID We recommend RSNetworx for DeviceNet software version 3 00 or later If your RSNetWorx configuration software does not include the required electronic data sheet EDS file go to http www ab com networks eds Register the new EDS file by using the EDS wizard in RSNetWorx for DeviceNet software Access the wizard from the Tools menu This configuration tool lets you to identify all of the DeviceNet devices and their locations in your sys
77. es include those used to do network browsing and configuration upload download functions So if these network functions are sluggish on your system increase the ISD time Publication 1769 UMOO9E EN P August 2009 Each waveform shows polling frequency for the given Foreground to Background Poll Ratio Where Fy x foreground slave devices B 1st background slave device B 2nd background slave device B5 3rd background slave device B4 4th background slave device Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 Foreground to Background Poll Ratio Devices set for polled behavior can be polled on every I O scan foreground or they can be polled less frequently background Setting a device for foreground or background behavior is done when you configure each device in the scanner s input section Foreground Background Polling Behavior Fy B B B4 By F B B B B Fy By By B3 By Fy B B B4 By Poll Ratio 1 Fy By B2 Fy B3 B4 Fy By Bo Fy B3 By Poll Ratio 2 Fy Bi Fy B Fy Ba Fy By Poll Ratio 4 Module Defaults Clicking Module Defaults sets Interscan Delay and Foreground to Background Poll Ratio to the following values nterscan Delay 10 ms Foreground to Background Poll Ratio 1 Slave Mode Enable Slave mode only if you want to use this scanner module as a slave Clicking Enable Slave Mode ope
78. eshooting the Status Indicators and Numeric Display Indicator Color Status Description Network Off No module power no network power or communications are not occurring between the module and the DeviceNet network This may be an acceptable condition Verify module has power Check that the DeviceNet cable is securely connected and the DeviceNet network is powered Verify that network power is adequate 11 5V DC Flashing Device is operational There are no connections established with any of the network devices Green If the module is supposed to be controlling DeviceNet slaves configure the modules scanlist solid Green Normal operation Scanlist is configured Module is not in Idle mode Flashing Red One or more of the devices that the scanner module is communicating with is in a timed out state Monitor the status display or the module s status field to determine which slave device is offline solid Red Critical network failure Duplicate DeviceNet node address detected Reset module Change module s node address or change conflicting device s node address If failure continues replace module Seven Node Address Indicates diagnostic information about the status of the module segment and Status Numeric Display e When the numeric display is showing 0 63 it is indicating the scanner s DeviceNet node address Display e When it shows 67 69 it indicates backup status e When it shows 70 99 it indicates an error
79. evices causing unintended machine motion e causing an explosion in a hazardous environment Electrical arcing causes excessive wear to contacts on both the module and its mating connector and can lead to premature failure 20 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 10 11 Quick Start for Experienced Users Chapter 2 Assemble and mount the I O bank The scanner module can be attached to an adjacent controller power supply or I O module The scanner module can be panel or DIN rail mounted Modules can be assembled before or after mounting Be sure to observe minimum spacing guidelines for adequate ventilation Ground the scanner module and complete the DeviceNet network wiring Apply power to the system Be sure that the programming software and equipment is ready Use RSLinx to configure drivers Use RSNetWorx for DeviceNet software to configure the 1769 SDN scanner module and the DeviceNet devices Use RSLogix software to create your project and ladder logic Start the system a Apply power b Download your program and put the controller into Run mode c status indicators turn on solid green Monitor the scanner module status to check if the scanner module is Operating correctly Module status is reported by the status indicators and numeric display on the front of the scanner module The information is also stored in the scanner module s input data file
80. f Contents Use the 1769 SDN Scanner Module with MicroLogix Controllers Troubleshooting 1769 SDN DeviceNet Class Codes CompactLogix Backup on the DeviceNet Network Glossary Index Chapter 7 ROCCO ectetur Et Latt LM wh An M aed ede 103 Nactobosm 1500 Conttollets u c44 d pee t boe SC E ME eto ae tes 103 RSLogix 500 Programming Software I O Configuration 104 DISC IDe PTOISEES cbr eon ete d i Eae egisti aud ede diras 105 DOS oniouradof Screens cba mer quodsi div Kee EE 106 Read I O C ontiot AUDI odisea iiem eerte P pta werd 107 Installed s oa cx dom reaches a era ER ce RS er we 107 1769 SDN Scanner Module Configuration less 108 Changing the 1769 SDN Configuration lesser 109 Dackpiane NIGSSAP hos ove deci sucio Ceres ird bubo v dunes earls v ees 111 POCC AVIeSSADIHg vase pied eq e CP Cle He Og ent 111 Program Upload and Download zie xe EE RE bass 112 Configure a Local DeviceNet Message 0 000002 eee 113 Messaer e Dey 4 OO EE rr 113 MSG Instruction Error Codes cc ec cee eee ees 120 Chapter 8 EOC DOE OD excce ttd E Satie ds Bang a5 Sotelo UE oe aeRO 121 Status GICAL OL S suo o n x anoo reeddveris Sete eu Soter HAE ee eren 121 BAO Ea dic ote anise ESTNE EC TT TS tes aes ects ee eee 124 Appendix A MEO C DUC HON fee testes tos seo Nd Bild ds de Rud e Na se Bid tae alee 127 Appendix B roduc Onse eate see bbc E aede me Reuters du eb ales 129 Flow the Backup WO kienes 28 0
81. fter software installation is complete you will use RSLinx software to configure your DeviceNet driver and RSNetWorx for DeviceNet software to configure the network Use RSLinx Softwa re to Follow these steps to configure the DeviceNet driver Configure Your DeviceNet 1 Start RSLinx software D river Vy Rockwell Software RSLinx nee Station DDE OPC Window Help Configure Shortcuts Configure Client Applications Configure CIP Options Configure Gateway Driver Diagnostics CIP Diagnostics Gateway Diagnostics Configure communication hardware 06 28 99 04 20 PM Z 62 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 Publication 1769 UMOO9E EN P August 2009 2 From the Communications menu choose Configure Drivers Configure Drivers R5 232 DF1 devices Ethernet devices 1784 K TC for ControlNet devices 1784 K T KTAS D JJPK D For DH DH 485 devices DF1 Polling Master Driver 1784 PCC for ControlNet devices 1784 PCIC S for ControlNet devices 1747 PIC AIC device DF1 Slave Driver 5 5 SD SD2 for DH devices Virtual Backplane SoftLogix58sx DeviceNet Drivers 1764 PCD PCIDS 172 70 KFD SDNPT drivers PLC 5 DH Emulator driver SLC 500 DH485 Emulator driver 1784 PCMK for DH DH 485 devices SoftLogix5 driver Remote Devices via Link Gatewa 4 Select your driver De
82. gister oe caste Aaa tent qiero tob ayers Aton edd 95 Device Idle Reoite imsar ei rcd T o EEEE Uds 96 Active Node RECK eh s odo r a TP Ed v AAN 97 EAS ID 1S DIA VI dedii toca E e E a idee VD beeen ipe 97 Saner JXddfess eree ea seed P eve E Aa 97 SCA E o a e A e oa hres oto E S 97 Scrolling Device Addresh ao eres eu sx EE o Apte opa det s 97 Sctolline DEVICE Stal Uema a ici aoi och ohne oie edd dnd 98 Deve DEdLtiSus a une 89 P6 atheist qoae SUO Gees Wala PEU Dc ded 98 Compacthoo1x tatus INepISteE usu cine tte tapi oe ee aa Gees 98 UTD NEPOTES 98 TALE fe d s S ea eaaa BG a we ae eens A 99 IJisable INGISVOEIE shi arbe d qr be fetch odd o da Sra Re EE RE te 99 De VIC SUL Al esa oae ob Rennes Ge s den Eq EA LUI DE EE 99 JNOEDVOEIEY FAC i top scare o ms o pce tits bees 99 Comm Faure s om vedrai 4a SUE RR edetebcen Bj ached 7 dou 99 Dup Node Pallutess cctss tatoo bdo n SHORE REEE d GERE 100 Dict Power Dele6E s ue aee e B Tote E bb OI b e ated 100 Compact Loom Command Register eno er AS EE LORI E 100 og ase ss aetna Saeco Oak and a eg Ea eae tas 100 eA PEE RERO ttey chee sents clude Ge x day lees se aD S hele 101 Disable INeBUOEIe s sect o e oEh S eon bee eae tte re 101 Fal SC ADDS vastes ad E 4s sce SPEO EROR 101 loc o NECNON NERONI EE OEIL TNT LIEST 101 lapat ati Id SOL iet oec orn aia rodea R9 pL Sa bci Dea eed deed 102 1709 5 IN COUfDUE OTETI E aret cdcioedu quete ce dedi Wh Gare 102 Publication 1769 UMOO9E EN P August 2009 7 Table o
83. he actual device on the network A match of just Device Type can be selected or the additional parameters of Vendor ID Product Code Major Revision and Minor Revision may be incrementally added For Major and Minor Revisions you can select or higher to indicate that either an exact match or some higher revision value of the revision is required If the scanner module detects a mismatch with any of the key parameters checked an Auto Verify failure will occur for that slave device and the scanner module will not continue the connection allocation process Publication 1769 UMOO9E EN P August 2009 77 Chapter 5 78 Manually Configure the DeviceNet Network Input Tab The input tab dialog lets you to define how data from all of the scanner s slave devices are mapped into the input image of the controller 1769 SDN Scanner Module 1 S 04 1791D 8B8P COS ff 06 1769 ADN Co COS In this example four input devices are mapped into the scanner s input image The dialog shows each device s node number e catalog number e connection type used between the scanner module and the slave device strobed polled cyclic or change of state e amount of data that will be exchanged in bytes e word within the controller s input image where the data will appear Publication 1769 UMOOSE EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Ch
84. hover 1f desired If an operator interface is on the DeviceNet network it can work without knowledge of which controller is primary or secondary Online edits are not automatically performed on both primary and secondary controllers since no synchronization exists between primary and secondary controllers Once an online edit occurs on the primary controller the primary and secondary will have different programs CompactLogix system backup on the DeviceNet network is not hot backup Hot backup implies complete synchronization of program program variables and I O Also I O switchover is completely bumpless with hot backup 145 Appendix B CompactLogix Backup on the DeviceNet Network Notes 146 Publication 1769 UMOO9E EN P August 2009 Glossary Auto Address Recovery AAR Auto Addtess Recovery AAR allows a slave device to be removed from the network and replaced with another identical slave device that is residing on the network at node address 63 and not in the scan list The replacement device will have its node address automatically changed to that of the device being replaced Depending on the level of revision keying it may be possible for the node address of the replacement device to be changed but not brought online due to a revision keying mismatch Auto Device Replacement ADR The Auto Device Replacement feature automates the replacement of a failed slave device on a DeviceNet network by configuring the new dev
85. ht panel and click OK You will see the Node Commissioning dialog with the current settings for your scanner module The default scanner module settings are as follows Communication rate 125 Kbps Node address 63 LEM Node Commissioning 5 In the Node Address box enter the new node address 6 Click Apply and Exit the dialog 69 Chapter 5 70 Manually Configure the DeviceNet Network Configure the 1 0 Devices The information in this section will focus on the scanner module s configuration and parameters that you can change by using RSNetWorx for DeviceNet softwate This dialog shows how a DeviceNet network is shown within RSNetWorx for DeviceNet software As you can see node one is a 1769 SDN scannet Double click on the scanner module to view or modify the scanner s parameters i SLX 69SDN PED DNT RSNetWorx for DeviceNet 1769 SON 17900 2686 1791D 8B8P 1769 A0N A 1761 NET DM PCB P44 Scanner 8 Univ In 8 8 Sink In 8 Device Net B E DeviceNet D Category OB Ac Drive Cd Barcode Scanner J Communication Adapter A1 DPI to DeviceNet F DeviceNet to SCANport FJ Dodge EZLINK General Purpose Discrete O FJ Generic Device FJ Human Machine Interface Inductive Proximity Switch C Limit Switch 4 Motor Protector AF Photoelectric Sensor Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chap
86. ice to the prior level of operation This includes Configuration Recovery CR and Auto Address Recovery AAR Bridge The scanner module s support of explicit message transfer Change of State COS A type of I O data communication The scanner module can send and receive data with slave devices that have the change of state feature Data is sent whenever a data change occuts or at the predefined heartbeat interval Configuration Recovery CR Configuration Recovery CR allows a slave device to be removed from the network and replaced with an identical slave device configured at the same communication rate and Node Address as the device being replaced Controller The programmable controller for example CompactLogix or MicroLogix 1500 Cyclic A type of I O data communication The scanner module can send and receive data with slave devices that have the cyclic feature Data is sent at a user configurable rate Publication 1769 UMOO9E EN P August 2009 Glossary 148 Publication 1769 UMOO9E EN P August 2009 Dual Mode The scanner module is in Dual mode when it serves as a master to one or more slaves and as a slave to another master simultaneously Electronic Data Sheet EDS A vendor supplied template that specifies how information is displayed as well as what is an appropriate entry value Explicit Messaging A type of messaging used for lower priority tasks such as configuration and data monitoring H
87. identical slave device configured at the same communication rate and node address as the device being replaced 80 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 ADR allows a slave device to be removed from the network and replaced with another identical slave device that is residing on the network at node address 63 and is not in the scan list The replacement device will have its node address automatically changed to that of the device being replaced Depending on the level of revision keying it may be possible for the node address of the replacement device to be changed but not brought online due to a revision keying mismatch The 1769 SDN scanner module can handle any number of device failures simultaneously however the AAR feature will be disabled for devices that have the same electronic key The CR feature will remain active In this case you must use the Node Commissioning tool that ships with RSNetWorx for DeviceNet software to change the node s address If the electronic key of the replacement device differs only by revision the CR feature may not work Before replacing any device you should make sure that the configuration parameters of the replacement device are compatible with the existing device IMPORTANT This behavior may introduce a possible safety hazard for devices such as drives Use the full electronic key including rev
88. ision You must be using a 1769 SDN scanner module and RSNetWorx for DeviceNet software to enable electronic key revision checking Important Considerations Keep the following in mind when using the ADR feature with RSNetWorx for DeviceNet software ADR is intended for use in single master environments The CR and AAR features can be used only with devices that are in the scanlist of the scanner e The AAR feature can be enabled for a device only if the CR feature is also enabled The CR feature cannot be enabled for devices that have no writable parameters for example a device that is entirely configured using hardware switches RSNetWorx for DeviceNet software will notify you of devices that have no writable parameters The AAR feature will not work for devices that do not support changing the node address over the network 81 Chapter5 Manually Configure the DeviceNet Network Configure ADR Parameters On the ADR tab you can configure the ADR parameters for the 1769 SDN scanner module Using the controls on this tab you can select ADR parameters and enable or disable this functionality either globally or on a device specific basis Configure each device on the network If online make sure that the configuration is synchronized with the online devices 1 On the ADR tab select the device you want to configure to use ADR 1769 SDN Scanner Module 1 TS m 04 17910 8 DE 1769 40 E 08 1761 M
89. ive and send This value identifies the data file location within the 1764 LRP controller that will receive data from the DeviceNet device and or the starting data file location that will be sent to the destination DeviceNet device General This Controller Channel Slot Fort Communication Command Data Table Address Receive Send Size in Bytes Hecerve Send Target Device Message Timeout Target Type Local Node Addr dec o foctall a Service Service Lade hex Class hex dec Instance hex dec Attribute hex dec Size in Bytes receive and send Since all data transmitted on the DeviceNet network is byte based you must enter the number of bytes that will be received and sent You must make sure that enough memory is available in the destination device Word elements within 1764 LRP controllers contain 2 bytes each These include Bit and Integer data files Long word and Floating point elements contain 4 bytes each For receive the size in bytes entered must be greater than or equal to the number of bytes that the DeviceNet device will return DeviceNet devices return a fixed number of bytes depending on the class and service If more data is returned than expected the message will be in error and no data will be written If less data is returned than expected the data will be written and the remainder of the bytes will be filled with zeros In the example dialog shown below
90. le A Source Element SUITE LETT Current Heartbeat Jv Cache Connections Publication 1769 UMOO9E EN P August 2009 135 Appendix B CompactLogix Backup on the DeviceNet Network 136 DeviceNet 0 CommandH egister Aun This figure shows rung 2 and the message setup used on it The message in rung 2 uses the INT data type IF Scanner Configuration needs updating set the Heartbeat using MSG instruction to scanner Set Attrib Single ta Class 0890 Instance 0x01 Attrib 0x12 Head Heartbeat DN EQ Mat Equal Type CIP Generic Source amp Current Heartbeat Message Control Set Heartbeat N5 e Source B Config Heartbeat 16 Rung 2 Message Configuration and Communication tabs Message Configuration Set_Heartbeat CIP Generic Jesi Message Configuration Head Heartbeat DeviceNet LEGITITTTTDTIT GS GTI VI EC in TI E ME Se DIR enamel Destination ink STET cs TNNT p 5 LIP itr S GUITGE LITT Vestnauan T aes za ctal SUITE D v acne Eonnectons Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B This figure shows rungs 3 and 4 and the message setup used on it The message in rung 3 uses the INT data type IF new Heartbeat has been set verify Heartbeat Configuration by reading back from scanner to make sure configuration was accepted Get Attrib Single to Class 0 90 Instance O07 Attrib O12 Devic
91. le of a dual function device is the 1761 NET DNI module The DNI can be used as slave I O or as a communication interface for PLCs or other DF1 full duplex devices Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 Scanlist These devices have been assigned to be slave I O to this scanner A slave device on the DeviceNet network can be owned by only one master at a time Devices in the scanlist are configured using the input and output tabs Automap on Add Automap allows a slave s I O to be automatically mapped into the scannet s input or output image tables when the slave device is added to the scanlist do not check this box if you intend to map a slave device into a particular input or Automap Options Data Alignment Bote Align IAEA output memory location C pyra Align If you do select Automap you will be prompted to choose how the data should be aligned in the scanner Edit I O Parameters These parameters will vary depending upon the slave device Information on configurable parameters is usually provided in the device s documentation Electronic Key The electronic key is used to make sure that a particular slave device always matches the intended device when the scanner module initiates a connection to it When one of the devices in the Scanlist section is highlighted these boxes may be checked to indicate to what extent the key parameters must match t
92. ly status When the scanner is in Run mode with AutoScan enabled the scanner display alternates between 65 and the scanner node address When a scanner is transitioned from Run mode to Idle mode while AutoScan is enabled it only scans the network for nodes that are not already in the scanlist However while in Idle mode an AutoScan DISABLE to ENABLE transition causes the scanner to erase the existing scanlist and scan for all nodes on the network The AutoScan feature checks for the Quick Connect setting in each slave device and enables Quick Connect in the scanner if it is enabled in the slave devices 55 Chapter4 Automatically Configure a DeviceNet Network Consideration The scanner sets up communication with any device that fits within the allocated memory size The scanner skips devices that are too large Manually editing the scan list turns off Autoscan 56 Type of Connection that the Scanner Sets Up The type of update connection that the scanner sets up with each device depends on the device The scanner chooses the first connection type that the device supports in this order 1 change of state COS 2 polled 3 strobed 4 cyclic at 1000 ms The scanner tries to set up a change of state connection If the device doesn t support change of state then the scanner tries to set up a polled connection etc The type of connection that the scanner sets up may of be the default for the device As an o
93. mary of Changes The information below summarizes the changes to this manual since the last printing We have included change bars as shown to the right of this paragraph to help you find new and updated information in this release of the manual The table below lists the changes that have been made to this revision of the manual Topic Page Automatically Configure a Chapter 4 DeviceNet Network Updated information Index Publication 1769 UMOO9E EN P August 2009 3 summary of Changes 4 Publication 1769 UMOO9E EN P August 2009 Preface Overview Quick Start for Experienced Users Installation and Wiring Publication 1769 UMOO9E EN P August 2009 Table of Contents About This Manual l eee hh hn 9 Who Should Use This Manual een 9 Conventions in This Manual 2 eb E ERE PO LSEMERY SUEDE 10 Additonal ResOUE CES cs peces uU SOC mter beo ee det dete e d 10 Chapter 1 Introd HO ot oero os SOEs Co duni Lad dud ee eee eee eres 11 Module Featule sc eto eee actus Wa eh acc pA edet qoot 12 Scanner Module OperattOfiuss titania one edd 35 ARE GR RC ca 13 Communication with Your Slave Devices 0 000 000 cee 14 1769 SDN Scanner Module Data Tables lese 15 Input Data Image MicroLogix 1500 1 sv ERE 15 Output Data Image MicroLogix 1500 2 0 eee eee 15 Input Data Image CompactLogix 0 0 0 0 cece eee 16 Output Data Image CompactLogix 0 00 eee eee 16 RSNetWo
94. n Compact I 0 System with MicroLogix 1500 Base Unit and Processor l 35 mm 168 mm 6 62 in 1 38 in Mounting Hole 35 28 5 mm D l mm i MAS 147 mm 5 79 in 1 38 in 1 12 in N D R33 5 3 SN S o Je Slee E E 3 N e E E DIN Rail F R3 z 2 E x Center Line e D 13 5 mm 14 7 mm 0 53 in 0 58 in Publication 1769 UMO009E EN P August 2009 29 Chapter 3 30 Installation and Wiring Panel Mounting Procedure Using Modules as a Template This procedure lets you use the assembled modules as a template for drilling holes in the panel Due to module mounting hole tolerance it is important to follow these procedures 1 Ona clean work surface assemble no more than three modules 2 Using the assembled modules as a template carefully mark the center of all module mounting holes on the panel 3 Return the assembled modules to the clean work surface including any previously mounted modules 4 Drill and tap the mounting holes for the recommended M4 or 8 screw 5 Place the modules back on the panel and check for proper hole alignment 6 Attach the modules to the panel using the mounting screws If mounting more modules mount only the last one of this group and put the others aside This reduces remounting time during drilling and tapping of the next group 7 Repeat steps 1 6 for any remaining modules DIN Rail Mounting The module can be mounted using the following DIN rails
95. n 1770 4 1 Bulleted lists such as this one provide information not procedural steps Numbered lists provide sequential steps or hierarchical information The following documents contain additional information concerning Rockwell Automation products Contact your local Rockwell Automation distributor to order hard copy publications For electronic copies go to http literatute rockwellautomation com Description Describes configuring the CompactLogix controllers on the DeviceNet network Describes configuring the CompactLogix controllers on the ControlNet network Describes using RSNetWorx for DeviceNet software catalog number 9357 DNETL3 Describes planning mounting wiring and troubleshooting your CompactLogix system This manual focuses on the 1769 L20 and 1796 L30 CompactLogix controllers Planning mounting wiring and troubleshooting your MicroLogix 1500 system Installing configuring and using Compact I O analog modules How to install and use the DeviceNet Interface catalog number 1761 NET DNI DeviceNet network planning information Grounding and wiring Allen Bradley programmable controllers National Electrical Code Published by the Wire sizes and types for grounding electrical equipment National Fire Protection Association of Boston MA 10 Publication 1769 UMOO9E EN P August 2009 Chapter 1 Overview Introduction This chapter provides an overview of communication between the CompactLogix an
96. n use the input and output tags of the scanner directly in your logic it is a lot easier to use alias tags Conveyor OnCommand Convevor Start zLocal 2 0 D ata 4 0 alias tag a tag that represents another tag Both tags share the same data Conveyor Stop Conveyor OnCommand e When the data changes both tags change zLocal 2 D D ata 4 0 An alias tag provides a descriptive name for data such as DeviceNet input or output data As an option create tags that describe each device without pointing them to If the location of the data changes simply point the the actual addresses of the devices Later convert the tags to aliases for the alias tag lets to the new location without editing data of the devices your logic 1 Enter your logic 2 Type a descriptive tag name for the DeviceNet data 3 Right click the tag name and choose New nl x EM ETE are Ere 2 PEE PhotoEve HawD ata T Ct D u u 3 LLL Mew PhatoEve RawData e X jb Cut Instruction Ciro End Copy Instruction Cri c Paste ctrl 4 r 53HMainRoutine 7 58 Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 4 Select the Alias button 5 Select the tag that this alias tag represents 6 Select the scope for the alias tag 7 Choose OK Mame PhetoE ve HawD ata Description 1 Cancel w 4 Ld Tag Type C Bete FEE Help 4 Alles C Produ
97. ner is in IDLE mode and e the AutoScan feature is disabled 3 Execute an Explicit message to the scanner using the SetAttributeSingle setvice to enable AutoScan There are multiple ways to send an explicit message on DeviceNet including the following Initiate AutoScan Via the User Program Initiate AutoScan via the 193 DNCT Terminal 48 Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 Initiate AutoScan Via the User Program Follow these steps to initiate AutoScan using a MSG instruction 1 Verify that the scanner is in IDLE mode that is bit 0 in the scanner control output word 0 and that all slave nodes are connected to and communicating on the DeviceNet network 2 In the RSLogix 5000 programming software Tag Editor create new tags to initiate AutoScan via ladder programming as shown in the example below B Name e Alias For Base Tag Data Type Style Description Ins on Local1 l AB 1758 SDN 4 Ei Local1 0 4B 1769_SDh_3 _ Toagle DINT Decimal t Initiate amp utoScan MESSAGE 2 3 Create a MSG instruction that uses the new tags Message Configuration InitiateAutoScan Configuration Communication Tag Message Type CIP Generic Service Set Attribute Single Source Element AutoS canE nable Type Source Length 1 Bytes Service Code 10 Hex Class an Hex El Instance i Attribute 10 Hex TET D Enabl
98. network NETWORK WHO Node 43 0 x DgyiceMet t 5canner 1732D 24Vdc 8 Conf E1 Plus E3 Plus 0 4 2 A PowerFlex r00 VC 2 his DeviceNet HIM 5 b T SMC Flex Standard 8 2 6 2 Use Down Arrow gt Ev on the 193 DNCT terminal to scroll down through the list until the last entry for node 63 is highlighted which should read 63 No Product Name 4 Press lt Enter gt A to advance to the configuration screen 4 Use Down Arrow M to select the Tools option Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 5 10 Automatically Configure a DeviceNet Network Chapter 4 Press lt Enter gt and a screen appears with the N odeComm option highlighted Press lt Enter gt E and the Node Commissioning screen appears as shown below with the BaudRate option highlighted Node Commissio ning BaudRate 125K Address 63 Because you do not need to change the baud rate press lt SEL gt ed to advance to the Address option and highlight it Press the numbers on the key pad for the node number that you plan to use for the device that was just installed on the DeviceNet network and press lt Enter gt When the address is changed an Apply Changes messages appears on the screen Press lt SEL gt Ed to highlight the Apply Changes message Press Enter E to complete the node commissioning function After approximately two seconds the 193 DNCT terminal
99. ng node address matches the desired electronic key vendor product code product type 15 No Messages Received No network traffic received by the scanner 10 seconds have elapsed and no network traffic for the module or for any other device have been received by the module Verify the scanlist is correctly configured to scan slave devices Verify DeviceNet network connections 76 No Message For Scanner No direct network traffic for the scanner module detected 10 seconds elapsed and no DeviceNet input being screened by the module has been received 71 Slave Data Size The data being received from the slave device does not match the configuration in the scanlist Mismatch Either reconfigure the slave device or change the module s scanlist to match the slave device 78 No Such Device Slave device in scanlist does not exist Either add the device to the DeviceNet network or delete the device s entry in the scanlist 79 Transmit Failure The module has failed to transmit a message Make sure that the module is connected to a valid network Check for disconnected cables 124 Publication 1769 UMOO9E EN P August 2009 Troubleshooting Chapter 8 Device Status Code Description decimal 80 In Idle Mode Module ts in Idle mode Put the controller into RUN mode and enable the RUN bit in the Module Command Array See page 16 81 scanner Faulted The scanner module has stopped producing and consuming I O data This condition
100. nicate Then they set their baud rate to the same baud rate as the other device By first placing a scanner or network interface on the network the other devices have a baud rate against which to set their baud rate Initially leave the baud rate of the scanner and network interface at the default setting of 125K bits s If you want to change the baud rate wait until after you establish communication with all your devices at the default setting 125K See Set the Node Address of a Device Via a DeviceNet Configuration Terminal on page 42 to set the scanner s DeviceNet address Publication 1769 UMOO9E EN P August 2009 39 Chapter4 Automatically Configure a DeviceNet Network baud Fixed Baud Rate Auto Autobaud 40 3 Connect the rest of your devices to the network one at a time Out of the box a DeviceNet device is preset for address 63 Connect and set the devices one at a time to set the scannet s DeviceNet address Otherwise the address conflicts may prevent communication with them If a device has a switch to set its baud rate set the switch to autobaud if available Otherwise set the device to the baud rate of the network After you change the address or baud rate of a device via a switch cycle power to the device If a device has no switch or pushbutton for its address or baud rate see Set the Baud Rate of a Device Via a DeviceNet Configuration Terminal below After you set the address of a device
101. nments Use a 2 1 mm 14 AWG wire to make this connection For additional information on grounding the scanner module refer to Industrial Automation Wiring and Grounding Guidelines Allen Bradley publication 1770 4 1 DeviceNet Wiring DeviceNet Connector ADDRESS ERROR Connect To Red Wire V romney eer White Wire CAN High Use 2 1 mm 14 AWG Bare we shield wire to connect to Blue Wire CAN Low panel ground Black Wire V DeviceNet cable colors are shown on the wiring label on the front of the scanner Publication 1769 UMOO9E EN P August 2009 Installation and Wiring Chapter 3 1 Connect the DeviceNet cable to the removable connector as shown 2 Insert the removable female connector into the mating male connector on the DeviceNet scanner module 4 Screw the removable connector to the scanner module case with the upper and lower mounting screws to a torque of 0 6 0 7 Nm 5 6 in lbs IMPORTANT If the 1769 SDN scanner module is the first or last device connected to the DeviceNet network trunkline be sure to add a termination resistor 120 Q1 2 74W resistor Allen Bradley part number 1485A C2 across the Blue CAN Low and White CAN High wires Scanner Module Power up When power is applied via the Compact I O bus the scanner module goes Publication 1769 UMOO9E EN P August 2009 through a self test sequence Upon successful completion of the self test the scanner module is rea
102. noise considerations 25 required equipment 19 manually configuring the DeviceNet network 61 85 message instruction error codes 120 messaging backplane 111 configuring a local DeviceNet message 113 118 MicroLogix 1500 controllers 103 120 minimum spacing 28 module command array 16 module features 1 mounting 28 30 DIN rail mounting 30 panel 28 30 node address set via RSNetWorx for DeviceNet software 67 setting via a 193 DNCT terminal 42 43 0 operating modes 16 output data definition 14 P panel mounting 28 30 poll message 14 power requirements DeviceNet network 20 23 maximum current draw 20 23 preventing electrostatic discharge 25 publications related additional resources 10 reducing electrical noise 25 related publications 10 RSLinx software configuring the DeviceNet network 62 64 installation 62 minimum version 19 RSLogix 500 programming software 104 110 minimum version 19 RSLogix 5000 programming software 44 minimum version 19 RSNetWorx for DeviceNet software as a configuration tool 17 Auto Device Replacement 80 83 configuration screen map 18 configuring the DeviceNet network 64 85 installation 62 minimum version 19 S scanlist configuration 0 scanner configure automatically 35 60 module functions 13 replacement 31 software installation 62 software versions 19 61 spacing minimum 28 start up instructions 19 strobe message 14 system assembly 27 system mounting 28 30 system planning
103. ns this dialog 73 Chapter5 Manually Configure the DeviceNet Network This parameter enables the slave functionality of the scanner and lets you set the I O behavior with the amount of data to be exchanged The Slave mode settings are described in this table Slave Mode Settings Connection Format Description otrobed Not supported by the 1769 SDN scanner module Polled Values entered into Rx and Tx parameters define how much data will be exchanged over the polled connection that owns the scanners slave I O Maximum size is 128 bytes Change of State Cyclic Values entered into Rx and Tx parameters define how much data will be exchanged over the change of state or cyclic connection that owns the scanners slave 0 Maximum size is 128 bytes Advanced Module Settings Clicking Advanced opens this dialog Advanced Module Settings 74 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Manually Configure the DeviceNet Network Chapter 5 Expected Packet Rate EPR When the scanner module opens a polled or strobed I O connection it sets a maximum timeout expected packet rate with the device If the device does not receive a packet from the scanner module within four times the EPR value the slave device drops the connection If the scanner module does not receive a packet from the slave within four times the EPR value it drops the connection and periodically attempts to open a new c
104. ntroduction MicroLogix 1500 Controllers Publication 1769 UMOO9E EN P August 2009 Chapter Use the 1769 SDN Scanner Module with MicroLogix Controllers This chapter contains an example in which the 1769 SDN scanner module is used with a MicroLogix 1500 controller This table describes what this chapter contains and where to find specific information Topic Page MicroLogix 1500 Controllers 103 RSLogix 500 Programming Software 0 104 Configuration Backplane Messaging 111 Program Upload and Download 112 Configure a Local DeviceNet Message 113 The MicroLogix 1500 programmable controller has two different processors that are compatible with the 1769 SDN scanner module The 1764 LSP and 1764 LRP processors can use the scanner module as a DeviceNet master and own DeviceNet slave devices This allows either processor to communicate with intelligent devices like drives scales and starters or use the DeviceNet network to expand the processor s I O capacity The 1764 LRP processor allows messaging functionality over the DeviceNet network so non I O data may be exchanged Multiple 1769 SDN scanner modules may be used in a 1764 LRP system However only the first two scanners can be used for messaging The amount of power that modules draw from the processor or expansion power supply and the amount of data that the processor can support will determine how many can be used Configuration tools are available from http www ab com
105. nual You can also contact a special Customer Support number for initial help in getting your product up and running United States 1 440 646 3434 Monday Friday EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell Automation tests all of its 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 follow these procedures United States Contact your distributor You must provide a Customer Support case number call the phone number above to obtain one to your distributor to complete the return process Outside United Please contact your local Rockwell Automation representative for the States return procedure www rockwellautomation com 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 Souverain 36 1170 Brussels Belgium Tel 32 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation Level 14 Core F Cyberport 3 100 Cyberport Road Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Publication 1769 UMOO9E EN P August 2009 Supersedes Publication 1769 UMO009D EN P August 2007 Copyright 20
106. o 32 bytes per node One way to set the allocation size is described in section Configure I O Allocation Size Via the User Program The following table lists devices that most commonly use the AutoScan feature and their respective I O allocation sizes Device Bulletin Number Input Allocation Output Allocation ArmorStart Distributed 280D 281D 1 byte 1 byte Motor Controller 193 E Electronic 193 0 bytes 1 byte Overload Relays PowerFlex 40 22B 4 bytes 4 bytes Adjustable Frequency AC Drive 4 Chapter4 Automatically Configure a DeviceNet Network Configure I O Allocation Size Via the User Program Use the parameters shown in the MSG message setup screen below to adjust the I O allocation size Make sure that the message is sent to the appropriate DeviceNet Scanner Message Configuration SetlOAllocation Configuration Communication Tag This data tag should Message Type CIP Generic v be configured as an Siue Set Attribute Single Source Element SetlOAllocation SINT and should ype Source Length 1 Bytes contain the value of eines fo Hex Class 90 Hes E the desired per node fixed mapping size 1 32 Instance fi Attribute f11 Hex mm Q Enable Enable Waiting Start Q Done Done Length 0 Error Code Extended Error Code Timed Out Error Path Error T ext Cancel Apply Help IMPORTANT You can only change the 0 allocation size when e the scan
107. ode 32 Bit 1 corresponds to Node 33 Bit 15 corresponds to Node 47 Bito corresponds to Node 48 Bit 1 corresponds to Node 49 Bit 15 corresponds to Node 63 Status Display The Status Display is a 4 byte array of the 1769 SDN display Scanner Address The Scanner Address is the scannetr s DeviceNet node number Scanner Status The Scanner Status is the scanners DeviceNet status scrolling Device Address The Scrolling Device Address is the DeviceNet address and status of node with errors The data updates once per second scrolling through all nodes with errors 97 Chapter6 DeviceNet 0 Image CompactLogix Status Register 98 scrolling Device Status The Scrolling Device Status is the status of the node with errors The data updates once per second scrolling through all nodes with errors Device Status The Device Status is the status of each DeviceNet node indexed by node number into a 64 byte array The third area of the CompactLogix controller input image is the Status Register The status words are described in more detail in the following sections Description Data Type StatusRegister Run StatusRegister Fault StatusRegister DisableNetwork StatusRegister DeviceFailure StatusRegister Autoverify al StatusRegister CommFailure StatusRegister DupNodeFail StatusRegister DnetPowerDetect This bit displays whether the controller is in Idle or Run module e Idle e 1
108. ogix controller output image is the Command Register The status words are described in more detail in the following sections Description Data Type O CommandRegister Run O CommandRegister Fault O CommandRegister DisableNetwork bit O CommandRegister HaltScanner O CommandRegister Reset This bit changes the DeviceNet network between Idle and Run module e Idle e 1 Run Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Fault This bit forces the scanner into a faulted condition Network is not faulted Network is faulted Disable Network This bit disables the DeviceNet network Network is not disabled Netwotk is disabled Halt Scanner This bit halts the scanner Scanner is not halted e 1 Scanner is halted Reset This bit resets the scanner 0 The scanner has not been reset e The scanner has been reset Do not leave this bit 1 If you do not change the bit back to 0 the scanner continuously resets Publication 1769 UMQQ09E EN P August 2009 101 Chapter6 DeviceNet 0 Image Input Data Image The Input Data Image is described on page 15 for the MicroLogix 1500 controller and on page 16 for the CompactLogix controller 1769 SDN Outp ut Structure The Output Structure is described on page 15 for the MicroLogix 1500 controller and on page 16 for the CompactLogix controller 102 Publication 1769 UMOO9E EN P August 2009 I
109. onnection When a connection is dropped status bits in the scanner module identify that the slave is not online Slave behavior when a connection is dropped is a function of the slave device If the slave is an I O device the outputs will be cleared held at last state or set to a fault condition refer to the slave device s documentation for actual I O behavior when a connection is dropped The EPR default value is 75 ms Changing the EPR number should be done carefully because it effects how long it takes the scanner module to detect a missing device Iransmit Retries Transmit Retries specifies the number of times the scanner module attempts to retransmit a change of state or cyclic message that has not been acknowledged by the slave device The connection is not necessarily dropped as a result of reaching the retry limit 15 Chapter 5 76 Manually Configure the DeviceNet Network Scanlist Tab The Scanlist defines which devices on the DeviceNet network are owned by the scanner 1769 SDN Scanner Module 1 06 1769 4DN Compact I 2 1730D SBV8B 8 Univ BY Sa 04 1 731D 8BSP 8 Sink I Available Devices These are the devices on the network that have the ability to be slave I O devices Slave capable devices do not have to be used as slave I O by a scanner They may alternately be used as slave I O by another scanner module on the same network or they may have dual functionality An examp
110. ou configure the switchover time slower than the program scan and I O update the secondary lags behind the primary and eliminates this State variables such as counters or timers are not synchronized The user program must synchronize the primary and secondary controllers typically over an EtherNet IP or ControlNet network link between controllers If the outputs are dependent on a state variable the lack of synchronization can also cause a bumpy switchover e As with all backup and redundancy systems the I O must change at a slower rate than the switchover time If the inputs change faster than the switchover the change of state is lost Hither the user program or user action determine the primary controller In its simplest mode the first scanner module to turn on or become available on the DeviceNet network is the primary 144 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B Unlike some backup systems such as PLC 5 controller systems the primary controller still maintains control of the I O and switchover does not occur if the primary controller is set to Program Idle mode The secondary 1769 SDN scanner module also indicates that it is in Idle mode By default a switchover will not occur if the default fault routine or user fault routine is executed in the primary controller However the user fault routine can force a switc
111. protect these boards The interior of the enclosure should be kept clean and the enclosure door should be kept closed whenever possible System Planning Consider the following when planning your system The scanner module can communicate with up to 63 DeviceNet devices The scanner as a master can own up to 63 slave I O nodes The scanner module can simultaneously be a master and a slave owned by another DeviceNet master A 1769 ECR right end cap or 1769 ECL left end cap is required to terminate the end of the Compact I O bus Each bank of Compact I O modules must have its own power supply A MicroLogix 1500 controller acts as the power supply for modules directly connected to it A Compact I O power supply or MicroLogix 1500 base unit has limits on the amount of 5V DC and 24V DC current it can supply to modules in its I O bank These limits depend on the catalog number of the power supply for example 1769 PA2 A bank of modules must not exceed the current limits of the I O bank power supply or MicroLogix 1500 base unit Refer to the Compact 1769 Expansion I O Power Supplies Installation Instructions publication 1769 IN028 or the MicroLogix 1500 User Manual publication 1764 UM001 The scanner module has a distance rating of four therefore the scanner module must be within four modules of the I O bank s power supply Determine the DeviceNet communication rate based on standard DeviceNet considerations Consider
112. ption you can allocate more memory for each device Description The scanner automatically sets up communication with those devices that fit within the memory allocated for each address e For example if you allocate 2 DINTs 8 bytes per address the scanner sets up communication with any device that sends or receives 0 8 bytes of data e The scanner adds as many device as it can until it runs out of memory e f you give too much memory to each address you may not have enough memory for all your devices If a device needs more memory than is allocated the scanner skips it and does not set up communication with it IMPORTANT If the Produced data size is greater than the configured 1 0 allocation size the device is added to the scanlist with a produced size set equal to the 0 allocation size When this happens an 1 0 connection is made with the device But it errors and error code 77 is displayed on the 1769 SDN for the device s node number For example if you specify 2 DINTs 8 bytes per address but a device sends 9 bytes the scanner does not add the device to the scan list If you use RSNetWorx for DeviceNet software to edit the configuration of the scanner the scanner turns off AutoScan Do not turn it back on or you will clear the configuration that you just entered For example if you use RSNetWorx for DeviceNet software to manually add a device to the scan list the scanner turns off AutoScan If turn on AutoScan
113. r Code Error Code Description EOH Expansion I O Communication Module Error The processor also wtites general status information related to this error at the high byte of MG file sub element 22 that can be monitored from your program Error Status Information General Status Description 01H Illegal or unsupported service parameter 02H Resource unavailable 04H Segment type error in IOI 07H Connection lost 08H Service not supported 09H Invalid attribute value OBH Already in requested mode state OCH Object state conflict OEH Attribute not setable 10H Device state conflict 11H Reply data too large 13H Not enough data 14H Attribute not supported 15H Too much data 16H Object does not exist 19H otore operation failure 20H Invalid parameter 28H Invalid member ID 120 Publication 1769 UMOO9E EN P August 2009 Chapter 8 Troubleshooting Introduction The 1769 SDN scanner module s front panel status indicators aid in troubleshooting the module The diagnostics provided by these indicators are described in this chapter Topic Page Status Indicators 121 Error Codes 124 Status Indicators The first step in troubleshooting is to observe the 1769 SDN scanner module s status indicators and seven segment numeric displays The indicators function as follows The bi color green red Module status indicator shows whether the scanner module has power and is functioning properly The bi color green red Network
114. rder e Change Of State COS EPR 250ms poll EPR 75ms e Strobe EPR 75ms Cyclic EPR 500ms EXAMPLE If a photoeye was connected on a network that only supported strobed connections the scanner does a couple of things e First the scanner recognizes that a device exists for which memory was available for the node number with the configured allocation size on a network that was not currently mapped e Then the scanner would attempt to initiate both COS and polled connections first but the strobed connection would be selected as that is the only connection that the photoeye supported Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 The input and output data is mapped into the scanner s I O data table based on the device s node address and the configured fixed mapping size The DINT based formula is used with the CompactLogix controller for calculating the Input or Output data location is Input Output Offset Node Address x Allocation Size 4 EXAMPLE When using the default fixed mapping size of 4 bytes the input data for the devices shown in the example below is allocated in the 1769 SDN s input table as shown below Notice node 1 is located in the data map at DINT location 1 node 2 at DINT location 2 and so on Bits 31 0 EFELELEEELELEEEEELELELLL LLL LLT 01 Right 02 8027 Notice that in this example node 4 is unused However
115. roubleshooting for more information Publication 1769 UMOO9E EN P August 2009 Additional Considerations Regarding AutoScan Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 The factory default setting for AutoScan is disabled for all products Make sure that input or output data memory size in the scanner is large enough to accommodate the size required based on the number of nodes on the network and the AutoScan I O allocation size per node TIP IMPORTANT Nodes 0 61 inclusive are scanned and added to the scanlist if they are not already mapped and O space exists For maximum capacity for slave devices the scanner node address could be configured as node 62 node 63 could also be used but to avoid duplicate node address issues with a new device this Is not recommended According the ODVA DeviceNet Technical Overview the maximum number of nodes on a DeviceNet network is 64 However the normal useful number of slave nodes is 62 because e the DeviceNet scanner requires a node and we recommend that you leave node 63 unused for devices that are added to the network in the future If a network interface is used on the network and the above bullets are taken into consideration then the useful number of nodes becomes 61 If the I O allocation size per node is configured for 16 bytes and there are 32 slave devices on the network node addresses 1 32 Auto
116. rx for DeviceNet Software as a Configuration Tool 17 Chapter 2 IGttOQUCHOT zc siete a Dome YOR ets woe eee eee d egit 19 Required Took and EUPM oua tents deett heed bate e ib e edm a 19 What YOU Necd TODO 15 Lob e te tbe SE dde meis 20 Chapter 3 Power Requirements s odds ees ew au ous Soe eto Raid ear 23 General ConsidefatlOnS s cuz uai i eriin EO E a a 24 Hazardous Location Considerations 00 ce eee eee eee 24 Preventing Electrostatic Discharge s eoe dis o eA 6 dade p d 25 RK movon POWCE e inh adh ie Se dde tee tot dap dies diras dris 25 Reducing NODE 4 4 9 aui UP CIE HERE CPP A 25 Protecting the Circuit Board from Contamination 26 Dy Stemi aM iI cde io du bbc cred onte itr orbc aud dotate ones tts 26 Susterne s end IY erates tue wena oos taU dca D co pa RD OE Ad 27 STS MOUNN Cea a euius ree eae E eee E 28 Minimum SDACITID apasa op yn dU gd prar o eb Ped A oe dup on equa oo 28 Panel NOUO ons vod diat edi oue dt wade tetas osi OP dos 28 BIN BH MOUDUDBS vues ie da ar src aaa Va els die debout 30 Replace the Scanner Module within a System 31 Field Warine Cone eHdons ou a dos EAHUPRROd ed oa RE S o d x 32 Grounding the Scanner Module omine avowed xe 32 Scanner Module PoS CE UID cay sores eu Sates a tees LAE 33 5 Table of Contents Automatically Configure a DeviceNet Network Manually Configure the DeviceNet Network Chapter 4 MMO CNG HO hie erie tes ttn ta ote eee oh eat
117. s before going online DeviceNet Configuration Services AN ou must either upload or download devices before viewing their online configuration For more information press F1 Publication 1769 UMOO9E EN P August 2009 65 Chapter 5 66 Manually Configure the DeviceNet Network 6 Click OK to upload the devices and go online RSNetWorx for DeviceNet software begins browsing for network devices When the software is done browsing your network is displayed 1769 SDN lra D SB vSB 1781D SBSP 1768 ADN A 1761 NET ON PCB P44 Scanner 8 Uniw In 8 8 Sink In 8 Device Met RSNetWorx fot DeviceNet software performs a single pass browse when you go online or choose the browse feature The software will poll for devices one time and display the results If a node that was online later goes offline there will be no live indication in RSNetWorx for DeviceNet software You must manually perform a browse to detect the missing node Click the Ed button to manually perform the browse If RSNetWorx for DeviceNet software fails to find a device check the physical connection to the device If the physical connection is intact vetify that the device s communication rate 1s the same as the communication rate of the DeviceNet driver If your RSNetWorx for DeviceNet software does not include the required electronic data sheet EDS file go to http www ab com networks eds Use the EDS Wizard in RSNetWorx for Devi
118. ster and the slave devices Device Status Input Word Bit Description 32 0 7 lower byte Node 0 DeviceNet status 8 15 upper byte Node 1 DeviceNet status 33 0 7 lower byte Node 2 DeviceNet status 8 15 upper byte Node 3 DeviceNet status 63 0 7 lower byte Node 62 DeviceNet status 8 15 upper byte Node 63 DeviceNet status 92 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 DeviceNet 1 0 Image Chapter 6 Module Status Register The scanner module supports a 32 bit Module Status Register put Word Bit Description Operation 64 Run Bit ON 1 scanning l O Bit OFF 0 halted 1 Fault Bit ON 1 faulted Bit OFF 0 not faulted 2 Network disable Bit ON 1 disabled Bit OFF 0 not disabled Device failure Bit ON 1 failure Autoverify fail Bit OFF 0 no failure Communication failure Duplicate node failure DeviceNet power detect Bit ON 1 power Bit OFF 0 2 no power Do not manipulate reserved bits Doing so may interfere with future compatibility 93 Chapter 6 CompactLogix Status Structure 94 DeviceNet I 0 Image The second area of the CompactLogix controller input image is the Status Structure The status words are described in more detail in the following sections Description Status Scan Counter Status Device Failure Register Status Autoverify Failure Register Status Device Idle Register
119. t Publication 1769 UMOO9E EN P August 2009 Glossary 150 Publication 1769 UMOO9E EN P August 2009 Rx Abbreviation for receive Scanlist The list of devices nodes with which the scanner module is configured to exchange I O data Scanner The function of the 1769 SDN scanner module to support the exchange of I O with slave modules Slave Mode The 1769 SDN scanner module is in slave mode when it is placed in another DeviceNet master s scanlist as a slave device Strobed A type of I O data communication A strobed message solicits a response from each strobed device a multicast transfer It is a 64 bit message that contains one bit for each device on the network Tx Abbreviation for transmit Numerics 1770 KFD RS 232 DeviceNet adapter 19 61 193 DNCT terminal 40 initiating Autoscan 51 52 A accessing device data 5 59 additional resources 10 Auto Device Replacement in RSNetWorx for DeviceNet software 80 83 AutoScan additional considerations 53 56 firmware requirements 38 implementing 46 60 initiate via a 193 DNCT terminal 51 52 initiate via a user program 49 50 overview 38 when to use 38 backplane messaging 111 backup CompactLogix backup on the DeviceNet network 129 145 baud rate setting via a 193 DNCT terminal 40 41 before you begin 11 19 C change of state message 14 class codes 177 common techniques used in this manual 10 communication with your slave devices 14 CompactLogix
120. tem The controller must be in Program mode or the scanner module in Idle mode bit 0 of the Module Command Array 0 for the scanner module to accept the configuration information 17 Chapter 1 Overview The main RSNetWorx dialog 1790D 8BV8B 1791D 8B8P 8 8 UnivIn 8 Sre Sink In 8 Source Out 3 General Purpose Discrete 1 0 Generic Device Human Machine Interface Photoelectric Sensor Rockwell Automation miscellaneous s SCANport Adapter 1769 ADN A 3 1761 NET DNI 1761 NET DNI Series Device Net Smart MCC DeviceNet Int Interface 7 es oo Rockwell Automation Allen Bradley s Rockwell Automation Dodge E Rockwell Automation Electro Craft Motion Cq H A Rockwell Automation Reliance Electric op Rockwell Automation Sprecher Schuh RSNetWorx Configuration Dialog Map 1769 SDN Scanner Module 5 Click Online and select the driver to browse the network PCB P447 Double click the 1769 SDN icon to access the 1769 SDN scanner module Click on the Scanlist tab to Move the device into 1769 SDN Scanner Module 1 Double click the device in the scanlist to edit a devices 1 0 parameters Edit I O Parameters 04 1791D 8B8P 8 Sink In 8 Source f LJ dv o 18 B 14 1761 NET DNI Devic access the scanlist the scanlist Click Download to Scanner to lt 1769 SDN Scanner Module 1 Ix download the scanlist 02 1790D 8BV8B 8 Univ
121. ter 5 General Tab This dialog shows the properties that RSNetWorx for DeviceNet software displays for the 1769 SDN scanner module 1759 5DM Scanner Module 1 1753 5DM Scanner Module Available items ate accessed through a series of tabs located across the top of the dialog The General tab is the default tab and provides information relative to the module If you ever need product support you will need to provide the revision number when you contact Rockwell Automation Technical Support 71 Chapter 5 Manually Configure the DeviceNet Network 72 Module Tab 1769 SDN Scanner Module E 2 x General Module Scanlist Input Output ADA Summary Interscan Delay E eee Upload from Scanner EG Ratio Zi Download to Scanner Module D efaults Slave Made Advanced 1753 5DN Platform CompactLogis m Slot ES Cancel Apply Help Interscan Delay This parameter defines the delay time the scanner module uses between scans of the DeviceNet network If you have slave devices configured for polled behavior in the 1769 SDN scanner module scanlist Interscan Delay ISD defines the amount of time the scanner module waits between DeviceNet I O updates Increasing the ISD time causes a longer network scan which adversely affects overall input to output performance However the increase allows lower priority messages to get more network access These lower priority messag
122. the 1 0 memory slot remains allocated for it If you are using a MicroLogix 1900 controller with a 1769 SDN scanner you must use the following WORD based formula for calculating the Input or Output data location Input Output Offset Node Address x Allocation Size 2 Data Offset In this formula the Data Offset 66 for Input Offset and 2 for Output Offset The data offset value is used to account for scanners that have a fixed status field at the start of the input or output data for example the 1769 SDN scanner Publication 1769 UMQQ09E EN P August 2009 37 Chapter4 Automatically Configure a DeviceNet Network Dete rmine If You Can Make sure your network meets the following requirements to use this chapter Use AutoScan The scanner s I O allocation size is configured to accommodate the input and output data sizes of all devices on your DeviceNet network The default AutoScan setting allocates a 4 byte entry in both the input and output memory maps in the scanner for each slave device detected on the netwotk This default size is chosen to accommodate the default Logix native data size of 32 bits that is a DINT If you use a device that sends more than 4 bytes of input or output data for example an E3 Solid State Overload Relay catalog number 193 ECxx you must change the I O allocation size You are using the CompactLogix 1769 SDN DeviceNet scanner with firmware revision 4 1 or greater If your ne
123. the DeviceNet connections and physical media integrity Check system for failed slave devices or other possible sources of network interference Check the Baud Rate 92 No DeviceNet Power No network power detected on DeviceNet port Provide network power Make sure the module drop cable is providing the proper power to the DeviceNet port Publication 1769 UMOO9E EN P August 2009 125 Chapter8 Troubleshooting Device Status Code Description decimal 95 FLASH Update Flash Update In Progress IMPORTANT Do not disconnect the module from the network while a FLASH update is in progress 98 Firmware Corrupted Firmware is corrupted Reflash module firmware Do not power cycle the module Doing so may cause the module to become inoperable If the problem persists contact Rockwell Automation Technical Support 99 Hard Fault Cycle power Reflash module firmware Contact Rockwell Automation Technical Support 126 Publication 1769 UMOO9E EN P August 2009 Appendix A 1769 SDN DeviceNet Class Codes Introduction This appendix contains the most commonly used class codes for the 1769 SDN DeviceNet scanner module They are shown in the following tables DeviceNet Object The set also causes a reset Identity Object Product Code Get Serial Number Get Product Name Get Publication 1769 UMOO9E EN P August 2009 127 Appendix A 1769 SDN DeviceNet Class Codes Notes 128 Publication 1769 UMOO9E EN P August 2009 App
124. the number of words of I O data the host controller supports For more information on planning your DeviceNet network refer to the DeviceNet Media Design Installation Guide publication DNET UM072 26 Publication 1769 UMOO9E EN P August 2009 Installation and Wiring Chapter 3 System Assembly The scanner module can be attached to an adjacent controller power supply ot I O module This procedure shows you how to assemble the Compact I O system 1 Disconnect power 2 Check that the bus lever of the scanner module A is in the unlocked fully right position 3 Use the upper and lower tongue and groove slots B to secure the modules together 4 Move the scanner module back along the tongue and groove slots until the bus connectors C line up with each other 5 Use your fingers or a small screwdriver to push the bus lever back slightly to clear the positioning tab D 6 Move the scanner module s bus lever fully to the left E until it clicks Make sure it is locked firmly in place When attaching I O modules it is very important that the bus connectors are securely locked together for a proper electrical connection 7 Attach an end cap terminator F to the last module in the system by using the tongue and groove slots as before 8 Lock the end cap bus terminator C A 1769 ECR or 1769 ECL right or left end cap must be used to terminate the end of the serial communication bus Publi
125. the scanner module and the MicroLogix controller to manage the flow of data between your controller and network devices Input Data Image MicroLogix 1500 The input data image is transferred from the scanner module to the controller across the Compact I O bus Word Description Data Type 0 65 otatus structure 66 word array 66 245 DeviceNet slave inputs 180 word array See Chapter 6 for definitions of the Status structure Output Data Image MicroLogix 1500 The output data image is transferred from the controller to the scanner module across the Compact I O bus Word Description Data Type 0 and 1 Module command array 2 word array 2 181 DeviceNet slave outputs 180 word array 15 Chapter 1 Overview Module Command Array Bit Assignments Output Description Behavior Word 0 Run This bit controls when the module scans its mapped slave devices When set 1 the scanner module will process I O data as defined by its scanlist The Fault and Disable Network command bits must be clear 0 to scan the network 1 Fault When set the scanners 1 0 mode will be Halt messaging will still operate The fault bit is primarily used to artificially set the slave devices into a fault state due to some event or condition within the control program 2 Disable network When set the scanner module is mE removed from the network EN Reserved A 0 Ree 0 Restarts access to the DeviceNet network a Do not manipulate res
126. tion 133 Appendix B CompactLogix Backup on the DeviceNet Network Develop the CompactLogix Backup Application 134 The CompactLogix backup is enabled from an RSLogix 5000 programming software user program with a few simple ladder rungs The following rungs are used in the CompactLogix backup Backup Heartbeat Configuration Rungs required Reading Backup State Rung optional Reading Backup Status optional Backup Heartbeat Configuration Rungs The first and most critical step 1s to set the backup heartbeat constant in the DeviceNet scanner The heartbeat constant enables the backup feature and determines the switchover time 2 x heartbeat By default the heartbeat is zero this default value disables the Backup mode Your user program must set the heartbeat to a non zero value to enable backup The heartbeat occurs in multiples of 8 ms 8 16 24 We recommend a value of 16 48 ms for most applications The recommended heartbeat times result in switchover times of 32 96 ms These times do not include controller scan delays IMPORTANT If multiples of 8 are not used for the requested heartbeat then the DeviceNet scanner module uses the next higher supported heartbeat value that can be read from the scanner For example If you set the heartbeat to 10 the scanner module uses a 16 ms heartbeat Publication 1769 UMOO9E EN P August 2009 CompactLogix Backup on the DeviceNet Network Appendix B Se
127. tting the Heartbeat Constant You can set the heartbeat constant with five rungs of ladder logic This figure shows rungs 0 and 1 and the message setup used in rung 1 The message in rung 1 uses the INT data type START OF BACKUP INITIALIZATION THE FOLLOWING RUNGS ENABLE BACKUP 45 SOON AS PROCESSOR IS CHANGED TO RUN MODE DR IF SCANNER I5 MANUALLY CHANGED FROM RUN TO IDLE WITH PROCESSOR IN RUN MODE NOTE SCANNER IS IDLE WHEN CommandRegister Aun 0 Initialize heartbeat constant in milliseconds multiple of 8 15 255 Heartbeat is the heartbeat between redundant 1788 DMB s to detect Failure af the processor ar scanner Loss of two consecutive heartbeats causes a switchover DeviceNet 0 CommandRegister Hun Moy r Move Source Config Heartbeat 16 Dest Config Heartbeat 16 First read Heartbeat Configuration to see if Scanner already configured IF after powerup keep reading until scanner is available het Attrnib Single ta Class 30 Instance 0x07 Attrib 0x12 DeviceNet L CommandRegister Aun Head Heartbeat EM MSG 1 E il Type CIP Generic Message Control Head Heartbeat Mom Rung 1 Message Configuration and Communication tabs Message Configuration Head Heartbeat DeviceNet LEGITTITETUITERT GI HGITTE EHE TOR S p C DHe Chame El peman C LIP vai S GUITGE LUIK r Vesttation T GS SOUEEN Message Configuration Read_Heartbeat Get Attribute Sing
128. twork does not meet the requirements listed above then use Chapter 5 and Chapter 7 to configure your network and control your devices How AutoScan Effects As you use AutoScan keep the following in mind Your Network f Consideration Description Autoscan clears the current With AutoScan the scanner automatically sets up communication with the devices on your DeviceNet configuration network When you turn on the AutoScan option the scanner removes any previous configuration that was done to the scanner AutoScan allocates a fixed At its default setting AutoScan allocates 1 DINT of input memory and 1 DINT of output memory for memory size for each device each device on the DeviceNet network DINT Input Memory The actual data for the device 0 device at address 0 fills the portion that it needs and the rest remains unused 1 device at address 1 2 device at address 2 how much memory for each address For example if you specify 2 DINT Input Memory DINTs 8 bytes per address 0 device at address 0 the scanner sets aside 2 DINTs for each address oe O O 2 device at address 1 device fills the portion that it needs and the rest 4 device at address 2 The bytes node value defines AutoScan lets you specify how much input and output memory to give to each address on your network 38 Publication 1769 UMOO9E EN P August 2009 Automatically Configure a DeviceNet Network Chapter 4 Consideration Description available you conne
129. u consider the following development and debugging tips Develop and debug the entire application with only the primary controller and scanner module present When the application 1s totally verified then download the program and exact same scanlist to the secondary controller without the primary controller present Verity that the secondary is also functioning properly and then both primary and secondary can be added to the network at the same time No configuration parameters are entered from RSNetworx for DeviceNet software or RSLogix 5000 programming software to enable backup All configuration occurs in the user program The entire application except for a few ladder rungs can be developed without knowledge that the application will have a backup controller and scanner module Local I O still works when this solution is used but the local I O is not backed up e Switchover time depends on the user configurable heartbeat Typically switchover occurs after two heartbeats plus the time required to complete network polling The I O during switchover is not bumpless Since the programs and I O updates ate not synchronized it is possible for the secondary controller to be either slightly faster or slower than the primary For example if output changes during a switchover the fact that the primary and secondary controllers are not synchronized because the output to momentarily switch between an older and newer value If y
130. ule is in Idle mode Local Node This is the target device s DeviceNet node number Address 118 Publication 1769 UMOO9E EN P August 2009 Publication 1769 UMOO9E EN P August 2009 Field Service Use the 1769 SDN Scanner Module with MicroLogix Controllers Chapter 7 Definition The DeviceNet network uses services to provide specific messaging functions A number of standard services with their corresponding parameters have been preconfigured for ease of use 1 Network Device E Head 4ssembl If you need to use a service that is not available select one of the generic services The generic service lets you enter specific service code parameters Information on what services a target device supports is usually provided in the devices documentation MSG Rung 3 0 MU ERI CIP Generic Head Assembly Write Assembly Write Output Point Head Output Point Head Input Paint Head Parameter Write Parameter Head Analog Input Write Analog Output Generic Get Attribute Single Generic Set Attribute Single Generic Get Member Generic Set Member 119 Chapter7 Use the 1769 SDN Scanner Module with MicroLogix Controllers MSG Instruction When the processor detects an error during the transfer of Expansion I O Frror Codes Communication Module message data the processor sets the ER bit and writes an error code at MG file sub element 18 that you can monitor from your programming software 1769 SDN Module Erro
131. viceNet Driver Selection HS5Linx DeviceNet 3 SOFTWARE aiersieaey v7rsoner Allen Bradley 1747 SDNPT Allen Bradley 1784 PCIDS hr UTS may rita The software will take a few seconds to configure the driver Eaniagure Maier 3 From the Available Driver Types pull down menu choose Add New 5 Your driver setup will depend on your particular system setup COM port communication rate node address Choose the appropriate settings for your system Allen Bradley 1770 KFD Driver Configuration 63 Chapter5 Manually Configure the DeviceNet Network 6 Click OK Add New HSLinx Driver Choose a name for the new driver 15 characters maximum Cancel li FTO KFD 1 7 Click OK to use the default driver name 8 Minimize RSLinx software You will use the driver you just configured to browse and configure the network with RSNetWorx for DeviceNet software Use RSNetWo rx for This manual assumes a certain level of familiarity with RSNetWorx for DeviceNet Softwa re to DeviceNet software For detailed information on RSNetWorx for DeviceNet Configure th e 1769 SDN software refer to your software s documentation Scanlist Set Up an Online Connection Follow the procedure below to set up an online connection to the DeviceNet network using the 1770 KFD driver 1 Start RSNetWorx for DeviceNet software 2 DeviceNet RSNetWorx for DeviceNet BE Ed File Edit View Network Device Tools Help
132. y to rock the scanner module slightly from front to back to remove it or in a panel mounted system to loosen the screws of adjacent modules Before installing the replacement scanner be sure that the bus lever on the right side adjacent module is in the unlocked fully right position Slide the replacement scanner module into the open slot Connect the scanner module and modules together by locking fully left the bus levers on the replacement scanner module and the right side adjacent module or end cap Replace the mounting screws or snap the scanner module onto the DIN rail Replace the DeviceNet cable on the scanner module by attaching the connector to the scannet Restore the scanner module configuration using RSNetWorx for DeviceNet software IMPORTANT Be sure that the new module has the same node address and communication rate as the module that was replaced 31 Chapter3 Installation and Wiring Field Wiring Connections 32 Follow these procedures to wire the scanner module Grounding the Scanner Module This product is intended to be mounted to a well grounded mounting surface such as a metal panel Additional grounding connections from the scanner s mounting tabs or DIN rail if used are not required unless the mounting surface cannot be grounded The grounding screw on the front of the scanner module must be connected to a suitable ground source when operating in electrically noisy enviro

Download Pdf Manuals

image

Related Search

Related Contents

取扱説明書 ご使用前に必ず、ご確認ください  Antec DF-10  Mode d`emploi de l`appartement  取扱説明書の表示  Assistance technique pour un centre informatique de documentation  Aqua2Go GD86 high-pressure cleaner  Approved - KaVo Dental  K-BUS R RS485/ KNX Converter User manual  Istruzioni di servizio  Cables Direct 2TT-15  

Copyright © All rights reserved.
Failed to retrieve file