Home

1769-UM009C-EN-P, Compact I/O 1769

1. E gt g N T lis e o a Center Line F TU A 13 5 mm 14 7 mm 0 53 in 0 58 in Publication 1769 UMO09C EN P May 2005 Installation and Wiring 3 9 Panel Mounting Procedure Using Modules as a Template The following procedure allows you to 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 to 6 for any remaining modules DIN Rail Mounting The module can be mounted using the following DIN rails 35 x 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 op
2. Keep the following in mind when using the ADR feature with RSNetWorx for DeviceNet e ADR is intended for use in single master environments e The CR and AAR features can only be used with devices that are in the scanlist of the scanner e The AAR feature can only be enabled for a device if the CR feature is also enabled e 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 will notify you of devices that have no writable parameters e The AAR feature will not work for devices that do not support changing the node address over the network Publication 1769 UMQ09C EN P May 2005 4 22 Configure the DeviceNet Network Publication 1769 UMO09C EN P May 2005 Configure ADR Parameters On the ADR property page you can configure the ADR parameters for the 1769 SDN scanner Using the controls on this property page 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 property page select the device you want to configure to use ADR 1769 SDN Scanner Module 1 Upload from scanner Downoad fo Scanner Sm 04 17910 8 06 1769 AD E 08 1761 NE in Lonhguraton Recovery 2 Click L
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 3 Screw the removable connector to the scanner case with the upper and lower mounting screws Screw torque is 0 6 to 0 7 Nm 5 to 6 in lbs IMPORTANT If the 1769 SDN is the first or last device connected to the DeviceNet network trunkline be sure to add a termination resistor 120 Q 1 2 14W resistor Allen Bradley part number 1485A C2 across the Blue CAN Low and White CAN High wites Publication 1769 UMQ09C EN P May 2005 3 12 Installation and Wiring Scanner Module Power Up When power is applied via the Compact I O bus the scanner module goes Publication 1769 UMO09C EN P May 2005 through a self test sequence Upon successful completion of the self test the scanner is ready to communicate The default scanner settings are e Baud rate 125K e Node address 63 Use your configuration software to change the baud rate and node address Software Versions Chapter 4 Configure the DeviceNet Network This chapter describes how to configure the DeviceNet network using RSLinx and RSNetWorx for DeviceNet software The following table describes what this chapter contains and where to find specific information For Information About See Page software Versions 4 1 Install the Software 4 2 Use RSLinx to Configure Your DeviceNet
4. Dimension Drawites 5 14 62526 6 eeu ihe execs daa a eet een ak A 3 Appendix B Who Should Use this Manual About CompactLogix Preface Read this preface to familiarize yourself with the rest of the manual It provides information concerning e Who should use this manual e The purpose of this manual e Related documentation e Conventions used in this manual e Rockwell Automation support Use this manual if you are responsible for designing installing programming or troubleshooting control systems that use Allen Bradley 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 This manual focuses on the 1769 SDN module For detailed information about using the 1769 SDN module with a CompactLogix system refer to the following publication e DeviceNet Modules in a Logix5000 Control Systems User Manual publication DNET UM004 This manual guides the development of a control system that uses a Logix5000 controller and a DeviceNet network Topics covered include configuring bridging connecting and controlling your DeviceNet network Publication 1769 UMQ09C EN P May 2005 Preface 2 Purpose of this Manual This manual is a reference guide for Compact I O 1769 SDN DeviceNet scanner module It describes the procedures you use to install program and troubleshoot your module This manua
5. Publication 1769 UMOQ09C EN P May 2005 Module Tab 1769 SDN Scanner Module 2 x General Module Scanlizt Input Output ADA Summary Interscan Delay meee Upload from Scanner T Ratio f Zi Download to Scanner Module Default Slave Mode Advanced 1769 50 Platform CompactLogis s Slot fi Cancel Apply Help Interscan Delay This parameter defines the delay time the scanner uses between scans of the DeviceNet network If you have slave devices configured for Polled behavior in the 1769 SDN s scanlist Interscan Delay ISD defines the amount of time the scanner 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 messages 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 Configure the DeviceNet Network 4 13 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 scannert s input section Figure 4 1 Foreground Background Polling Behavior
6. Rung 3 0 MG11 1 CIF Generic Write Assembly Write Output Point Read Output Point Read Input Point Read Parameter Write Parameter Read Analog Input Write Analog Output Generic Get Attribute Single Generic Set Attribute Single Generic Get Member Generic Set Member Message Timeout Message timeout is specified in seconds If the target does not 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 larget Type You can select either Module or Network Device If you need to message to a device on DeviceNet 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 only be edited when the module is in Idle Mode Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 17 Local Node address This is the target device s DeviceNet node number Service DeviceNet 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 Read 4 sembl If you need to use a service that is not available select one of the Generic services The Generic service allows you to enter specific s
7. ele 1784 PCD g Interface Card 0000 0000 1734 POINT 1 0 E3 Overload MicroLogix 1000 controller MicroLogix 1200 controller Relay PowerFlex 40 Drive with 1761 NE T DNI with 1761 NE T DNI Enhanced DeviceNet Communic ations Module 31535M The scanner communicates with DeviceNet devices over the network to e Read inputs from slave devices e Write outputs to slave devices e Communicate with peer devices messaging e Upload download programs to a 1764 LRP based MicroLogix 1500 controller across a DeviceNet network Publication 1769 UMQ09C EN P May 2005 1 4 Overview Communicating with Your Slave Devices Publication 1769 UMO09C EN P May 2005 The scanner 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 received from the devices input data is organized by the scanner and made available to the controller Data sent from your controller output data is organized in the scanner and sent on to your devices e A strobe message is a multicast transfer of data which is 64 bits in length sent by the scanner 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 does not support the strobe message e A poll message is a point to point transfer of d
8. 11 Scanner Module Power Upee et sosro tiaa a ces re 3 12 Chapter 4 SONWALE V ClSIONS morran Joe S eerie oc Sas ee we ex 4 1 lasalle Solna Ea a a ra ees ne AEE SOD A 4 2 Use RSLinx to Configure Your DeviceNet Driver 4 2 Use RSNetWorx to Configure the 1769 SDN s Scanlist 4 4 Chapter 5 SDN Input Filewcccecs reoite ter eeu cognates senna E 5 1 SATUS o CC PU Cee a ea E uh cues A dt Boh DG dad au We See ees 5 2 DON Output Piles state veienagier tenet at deen ee eames hod 5 8 Output Data nace soit fase eis eS Sess OEE E g ea Wada ta ected 5 9 Chapter 6 Publication 1769 UMQ09C EN P May 2005 Table of Contents ii Using the 1769 SDN Scanner Module with MicroLogix Controllers Troubleshooting Specifications 1769 SDN DeviceNet Class Codes Publication 1769 UM009C EN P May 2005 Chapter 7 Mictoboom 1500 Controllers lt eeror e a EO E eis 7 1 RSLogix 500 I O ConteuranOn sq s56oo a dienes et awlin eta eaweeks T2 Backplane Messab iNO oa runar EE ESRO EIEEE 7 8 Program Upload Download 4 4 040 hn tes whee ae eu ear ses one es 7 9 Configuring a Local DeviceNet Message 000 7 11 MSG Instruction Error Codes 0 00 ce ees 7 18 Chapter 8 Diagnostic MACOS 2 05 2 5 ase ace Ee he toke Geka OR Bas 8 1 PO OC ee cig cotta haa a oo PE O a eitdatne ke E 8 3 Appendix A General SPeCINCANONS s 3 onsen tomes stan eeeewen ees tutes A 1 Electrical and DeviceNet Specifications 000 A 2
9. 2 663 0600 Fax 32 2 663 0640 Asia Pacific Rockwell Automation 27 F Citicorp Centre 18 Whitfield Road Causeway Bay Hong Kong Tel 852 2887 4788 Fax 852 2508 1846 Headquarters for Dodge and Reliance Electric Products Americas Rockwell Automation 6040 Ponders Court Greenville SC 29615 4617 USA Tel 1 864 297 4800 Fax 1 864 281 2433 Europe Rockwell Automation Br hlstra e 22 D 74834 Elztal Dallau Germany Tel 49 6261 9410 Fax 49 6261 17741 Asia Pacific Rockwell Automation 55 Newton Road 11 01 02 Revenue House Singapore 307987 Tel 65 351 6723 Fax 65 355 1733 Publication 1769 UMO09C EN P May 2005 Supersedes Publication 1769 UMO09B EN P May 2002 Copyright 2005 Rockwell Automation Inc All rights reserved Printed in the U S A
10. Network DeviceNet Port is Disabled 91 Bus Off Bus off condition detected on integral DeviceNet port 92 No DeviceNet Power No network power detected on DeviceNet port 95 FLASH Update Flash Update In Progress 98 Firmware Corrupted Firmware is corrupted 99 Hard Fault Publication 1769 UM009C EN P May 2005 Recommended Action None This code clears itself once the module properly initializes all slave devices on the network Configure the slave device for a smaller data size Check the device configuration and slave node status Try the ADR download again If it still fails try clearing the ADR flash by downloading an empty ADR configuration to the scanner and then try the ADR configuration again Check for the DISABLE being set in the Module Command Array See page 5 8 Check the DeviceNet connections and physical media integrity Check system for failed slave devices or other possible sources of network interference Check the Baud Rate Provide network power Make sure the module drop cable is providing the proper power to the DeviceNet port None DO NOT disconnect the module from the network while a FLASH update is in progress 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 Cycle Power Reflash module firmware Contact Rockwell Automation Technical Support General Spec
11. The following table describes the Error Codes indicated by the 7 segment numeric display Description Controller has Failed Duplicate Node Address Check The node address selected is already in The slave device Vendor ID key parameter does not match the slave s configuration in the module s scanlist 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 No direct network traffic for the scanner detected 10 seconds elapsed and no DeviceNet input being screened by the module has been received The data being received from the slave device does not match the configuration in the scanlist Slave device in scanlist does not exist The module has failed to transmit a message Module is in IDLE mode The Scanner has stopped producing and consuming I O data This condition does not affect the scanner s system or messaging modes Error detected in sequence of fragmented 0 messages from device Recommended Action Change the module s or conflicting device s network address node number to an available one Reconfigure the scanlist table and remove any illegal data Inspect the module s slave devices and verify the DeviceNet connections Make sure that the device at the flashing node address matches the desired electronic key vendor product code product type Verify the scanlist is correc
12. adequate 11 to 25V dc If the module is supposed to be controlling DeviceNet slaves configure the module s scanlist Monitor the status display or the module s status field to determine which slave device Is offline Reset module Change module s node address or change conflicting device s node address If failure continues replace module 7 Segment Node Address Indicates diagnostic information about the status of the module Numeric and Status Display Display e When the numeric display is showing 0 to 63 it is indicating the scanners DeviceNet node address Publication 1769 UMO09C EN P May 2005 e When it shows 70 to 99 it indicates an Error Code for the displayed node address e When it flashes alternating numbers one is the Error Code 70 to 99 and the other is the Node Number 0 to 63 that has generated the error Error Codes Table 8 2 Device Status Code decimal 70 15 76 71 78 19 80 81 02 83 Duplicate Node use Illegal Scanlist Data Illegal data in scanlist Slave Timeout One of the module s slave devices has stopped communicating Electronic Key Mismatch No Messages Received No Message For Scanner Slave Data Size Mismatch No Such Device Transmit Failure In Idle Mode Scanner Faulted Fragmentation Error Slave Init Error Slave device is returning error responses when the module attempts to communicate with It Troubleshooting 8 3
13. cycle power for baud rate changes to take effect The controller must be in the Program mode or the scanner in the Idle mode bit 0 of the Module Command Array 0 for the scanner to accept the configuration information 1 From the Tools menu select Node Commissioning Node Commissioning Publication 1769 UMO09C EN P May 2005 4 8 Configure the DeviceNet Network 2 Click on the Browse button Device Selection 1747 S0N Scanner Module 1761 NET ONI Seres B DeviceNet 1761 MET DHI Seres E DeviceNet 1761 NET DN Device Net Interface 7 pg aed len Workstation a0 1747 SDN 5 E 05 1761 HET D H 07 1761 NET D m 62 Workstation 6 2 AB OF1 1 OFT 3 Select the DeviceNet network The devices on the network will appear in the right panel of the window Publication 1769 UMO09C EN P May 2005 Configure the DeviceNet Network 4 9 4 Select the device you are commissioning in the right panel and click on OK You will see the Node Commissioning window with the current settings for your scanner Your window will look similar to the next one shown in this procedure The default scanner settings are e Baud rate 125K e Node address 63 Node Commissioning 5 In the New Device Settings Node Address box enter the new node address 6 Click on Apply and Exit the window Publication 1769 UMO09C EN P May 2005 4 10 Configure the DeviceNet Network Publication 1769 UMO09
14. following table identifies what this chapter contains and where to find specific information For Information About See Page Required Tools and Equipment 2 1 What You Need To Do 2 2 Have the following tools and equipment ready e Personal computer e Programmable controller CompactLogix or MicroLogix 1500 system e 1770 KFD RS 232 DeviceNet adapter or 1784 PCD or 1784 PCID DeviceNet interface card e Communications software RSLinx version 2 30 or later e DeviceNet configuration software RSNetWorx for DeviceNet version 3 00 or later e Ladder logic programming software RSLogix 500 version 5 00 10 or later RSLogix 5000 version 8 02 or later e 1769 SDN scanner module e Mounting hardware e Screwdriver Publication 1769 UMQ09C EN P May 2005 2 2 Quick Start for Experienced Users What You Need To Do 1 Verify planned system configuration a Ensure system power supply has sufficient current Table 2 1 Maximum Current Draw 1769 SDN 440 mA 0 mA The module cannot be located more than 4 modules away from the system power supply b Verify that the DeviceNet network has adequate power Table 2 2 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 ATTENTION Remove power before removing or inserting this module When you remove or insert a module with power applied an e
15. means Not Active a bit value of 1 means Active Table 5 6 Slave Node Status Input Word BitO to Bit 15 1411 168 Node 32 Node 47 17 Node 48 Node 63 1 2 3 4 Bit 0 corresponds to Node 0 Bit 1 corresponds to Node 1 Bit 0 corresponds to Node 16 Bit 1 corresponds to Node 17 Bit 0 corresponds to Node 32 Bit 1 corresponds to Node 33 Bit 0 corresponds to Node 48 Bit 1 corresponds to Node 49 Scanner Status The Scanner Device Status is a 4 byte array Table 5 7 Scanner Device Status Description Node 0 Node 15 Bit ON 1 Active node 15 2 Node 16 Node 31 Bit OFF 0 Inactive node Bit 15 corresponds to Node 15 Bit 15 corresponds to Node 31 Bit 15 corresponds to Node 47 Bit 15 corresponds to Node 63 Input Word Bit Description 20 0 7 lower byte Scanner Address in BCD 15 upper byte Scanner Status in BCD 21 8 0 7 lower byte Slave Device Address in BCD 8 15 upper byte Slave Device Status in BCD Publication 1769 UM009C EN P May 2005 5 6 DeviceNet I 0 Image Publication 1769 UMO09C EN P May 2005 Reserved Array Table 5 8 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 the following table Each byte indicates the status code of the s
16. module within the first 24 hours of installation please review the information that s contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running United States 1 440 646 3223 Monday Friday 8am 5pm EST Outside United Please contact your local Rockwell Automation representative for any States technical support issues New Product Satisfaction Return Rockwell tests all of our products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning and needs to be returned United States Contact your distributor You must provide a Customer Support case number see phone number above to obtain one to your distributor in order to complete the return process Outside United Please contact your local Rockwell Automation representative for States return procedure www rockwellautomation com Corporate Headquarters Rockwell Automation 777 East Wisconsin Avenue Suite 1400 Milwaukee WI 53202 5302 USA Tel 1 414 212 5200 Fax 1 414 212 5201 Headquarters for Allen Bradley Products Rockwell Software Products and Global Manufacturing Solutions Americas Rockwell Automation 1201 South Second Street Milwaukee WI 53204 2496 USA Tel 1 414 382 2000 Fax 1 414 382 4444 Europe Rockwell Automation SA NV Vorstlaan Boulevard du Souverain 36 BP 3A B 1170 Brussels Belgium Tel 32
17. programmable controllers Wire sizes and types for grounding electrical equipment Publication 1769 UMO09C EN P May 2005 Read this Document Publication Number DeviceNet Modules in Logix5000 Control DNET UM004 systems User Manual ControlNet Communication Modules in CNET UMO001 Logix5000 Control Systems User Manual RSNetWorx for DeviceNet Technical Data 9398 DNETTD CompactLogix System User Manual 1769 UM007 MicroLogix 1500 Programmable Controllers 1764 UM001 User Manual Compact I O Analog Modules User Manual 1769 UM002 DeviceNet Interface user Manual 1 761 6 5 DeviceNet Media Design Installation Guide DN UM072 DF1 Protocol and Command Set Reference 1770 6 5 16 Manual Allen Bradley Programmable Controller 1770 4 1 Grounding and Wiring Guidelines National Electrical Code Published by the National Fire Protection Association of Boston MA Chapter 1 Overview This chapter provides an overview of communication between the CompactLogix and MicroLogix 1500 programmable controllers and DeviceNet devices via the 1769 SDN scanner module The configuration data tables and the RSNetWorx for DeviceNet screens and windows used to configure the data tables are also described The following table identifies what this chapter contains and where to find specific information For Information About See Page What You Need to Know 1 1 Identify Module Features 1 2 What Your Scanner Does 1 3 Communicating with
18. software After software installation is complete you will use RSLinx to configure your DeviceNet driver and RSNetWorx to configure the network Use RSLinx to Configure 1 Start RSLinx Ws Rockwell Software RSLinx Your DeviceNet Driver aes Rn Station DDE OPC Window Help Configure Shortcuts Configure Client Applications Configure CIP Options Configure Gateway Driver Diagnostics CIP Diagnostics Gateway Diagnostics Configure communication hardware f 06728799 04 20PM 5 Publication 1769 UMO09C EN P May 2005 Configure the DeviceNet Network 4 3 2 From the Communications menu select Configure Drivers as shown above Configure Drivers RS 232 DF1 devices Ethernet devices 1784 KT C x for ControlNet devices 1784 KT KT D APKTX 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 ar DF1 Slave Driver atatup s Virtual Backplane SoftLogix58 Stat 1 Z F0 KFD SDNPT drivers GF FLAL 1784 PCMK for DH DH 485 devices SoftLogix5 driver Remote Devices via Link Gatewa 3 Select DeviceNet Drivers from the above pull down list and click on Add New DeviceNet Driver Selection RSLinx DeviceNet 3 Allen Bradley 1770 KFD Allen Bradley 1771 SDNPT Allen Bradley 1747 SDNPT Allen Bradley 1784 PCIDS 4 Select your driver Allen Bradle
19. technical support 4 11 tools required for installation 2 1 troubleshooting 8 1 diagnostic indicators 8 1 typical network configuration 1 3 7 2 W what you need to know 1 1 wiring 3 1 Publication 1769 UM009C EN P May 2005 2 Index Notes Publication 1769 UMO09C EN P May 2005 How Are We Doing ANB Your comments on our technical publications will help us serve you better in the future Thank you for taking the time to provide us feedback wy You can complete this form and mail or fax it back to us or email us at RADocumentComments ra rockwell com Pub Title Type Compact 0 1769 SDN DeviceNet Scanner Module Cat No 1769 SDN Pub No 1769 UMOO9C EN P Pub Date May 2005 Part No Please complete the sections below Where applicable rank the feature 1 needs improvement 2 satisfactory and 3 outstanding Overall Usefulness 1 2 3 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 APES example guideline other explanation definition Technical Accuracy 1 2 3 Can we be more accurate all provided information Clarity 1 E 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
20. with intelligent devices like drives scales starters and many others or use DeviceNet to expand the processors I O capabilities capacity The 1764 LRP processor allows messaging functionality over DeviceNet 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 To determine if an application can be supported configuration tools are available from http www ab com micrologix 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 Publication 1769 UMQ09C EN P May 2005 7 2 Using the 1769 SDN Scanner Module with MicroLogix Controllers RSLogix 500 1 0 One of the advanced features of RSLogix 500 is the ability to have the Con figu ration programming software establish a communications connection with the 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 will illustrate how to read which I O modules are attached to the controller and manually configure them We will then configure the scanner An
21. 15 Data Table Address Receive 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 Expansion Comms Port CIF Generic Size in Bytes Receive and Send Since all data transmitted on DeviceNet 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 than 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 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 screen shown below N7 0 will recetve 2 bytes 1 word of data Exnarision Comms Fort CIP Generic fal 5 Network Device JF Publication 1769 UMO09C EN P May 2005 7 16 Using the 1769 SDN Scanner Module with MicroLogix Controllers Publication 1769 UMO09C EN P May 2005 Target Device MSG
22. 4 2 Driver Use RSNetWorx to Configure the 4 4 1769 SDN s Scanlist The following table lists the software and revision level required to operate with the 1769 SDN scanner module Table 4 1 Compatible Software Function Program Revision Communications RSLinx 2 30 or later DeviceNet Configuration RSNetWorx for DeviceNet 3 00 or later Ladder Logic Programming Software RSLogix 500 5 00 10 or later RSLogix 5000 8 02 or later You will also need one of the following interfaces to use your computer to communicate with the DeviceNet network e 1770 KFD RS 232 DeviceNet adapter e 1784 PCD or 1784 PCID DeviceNet interface card 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 using the EDS Wizard in RSNetWorx Access the wizard from the Tools pull down menu Publication 1769 UMQ09C EN P May 2005 4 2 Configure the DeviceNet Network Install the Softwa re Install RSLinx and RSNetWorx 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 select Run 3 Browse for the Setup program on the CD ROM and open it 4 Follow the prompts that appear on the screen as you install the
23. 9C EN P May 2005 Input Tab The input tab screen allows 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 Ga 04 1791D BB8P COS 06 1769 ADN Co COS E 08 1761 NET DN COS In this example we have 4 input devices that are mapped into the scannet s input image The graphical window at the top of the dialog box shows each device s e Node number e Catalog number e Type of connection that is used between the scanner and the slave device strobed polled cyclic or change of state e The amount of data that will be exchanged in bytes e The word within the controller s input image where the data will appear Configure the DeviceNet Network 4 19 Advanced The scanner allows each node s slave data to be broken up segmented into separate input image areas This capability allows you to 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 Publication 1769 UMO09C EN P May 2005 4 20 Configure the DeviceNet Network Publication 1769 UMO09C EN P May 2005 Output Tab The output tab screen allows you to define how data from the scanner is mapped to the outputs of the slave devices 1769
24. C EN P May 2005 Configure the 1 0 Devices The information in this section will focus on the scanner s configuration and parameters that you can change using RSNetWorx The following screen shows how a DeviceNet network is shown within RSNetWorx As you can see node one is a 1769 SDN scanner To view or modify the scanner s parameters double click on the scanner E SLX 69SDN PED DNT RSNet orx for DeviceNet Aje E 2 Ste 1769 SON 17900 2686 17910 3B8P 1769 ADN A 1761 NET ON PCB P447 Scanner 8 Univ Inve 8 Sink In 8 Device Net E E DeviceNet EH Category MPD Ac Drive H CJ Barcode Scanner H FJ Communication Adapter H FJ DPI to DeviceNet Hf DeviceNet to SCANport H A Dodge EZLINK H FJ General Purpose Discrete lO H TJ Generic Device H Human Machine Interface A Inductive Proximity Switch A Limit Switch Hl F Motor Protector Configure the DeviceNet Network 4 11 General Tab The following screen shows the properties dialog that RSNetWorx displays for the 1769 SDN scanner module t 1769 SDN Scanner Module 1 Available items are accessed through a series of tabs located across the top of the screen 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 Suppott Publication 1769 UMO09C EN P May 2005 4 12 Configure the DeviceNet Network
25. Consider the following when planning your system The scanner can communicate with up to 63 DeviceNet devices The scanner as a master can own up to 63 slave I O nodes The scanner can simultaneously be a master and be 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 must have its own power supply A MicroLogix 1500 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 e g 1769 PA2 of the supply 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 UMO001 The scanner has a distance rating of four therefore the scanner must be within four modules of the I O bank s power supply Determine the DeviceNet baud rate based on standard DeviceNet considerations Consider 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 DN UM072 Publication 1769 UMQ09C E
26. Each waveform shows polling frequency Fy By By B3 By Fy By By B3 B4 Fy By By B3 By Fy B By B3 By for the given Foreground to Background Poll Ratio Poll Ratio 1 Fy By By Fy B3 B4 Fy B4 B2 Fy B3 B4 Where l Poll Ratio 2 Fy x foreground slave devices B4 1st background slave device Fy By Fy By Fy B3 Fy By By 2nd background slave device Poll Ratio 4 B3 3rd background slave device B4 4th background slave device Module Defaults Clicking the Module Defaults button sets Interscan Delay and Foreground to Background Poll Ratio to the following values e Interscan Delay 10 ms e Foreground to Background Poll Ratio 1 Publication 1769 UMQ09C EN P May 2005 4 14 Configure the DeviceNet Network Slave Mode Enable slave mode only if you want to use this scanner as a slave Clicking on the Slave Mode button opens the following screen This parameter enables the slave functionality of the scanner and allows you to set the I O behavior with the amount of data to be exchanged The slave mode settings are described in the following table Table 4 2 Slave Mode Settings Connection Format Description strobed 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 scanner s slave I O Maximum size is 128 bytes Change of State Cyclic Values entered into Rx a
27. LAE gms gel oie rf it Be i Allen Bradley d h en Compact 1 0 1769 SDN DeviceNet Scanner Module 1769 SDN User Manual o a a a a SS SS SS m es iE Rockwell 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 ab com manuals gi 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 The examples and diagrams in this manual are included solely for illustrative urposes Because of the many variables and requirements associated with go 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 circuits equipment or software described in this manual considerations Identifies information about practices or circumstances that can cause a
28. Move the device into the scanlist To download the scanlist click on 1769 SDN Scanner Module 1 ink In 8 Source O E g 14 1761 NET DNI Devic 1769 SDN Scanner Module 1 the Download to Scanner button 02 1790D 8BV8B 8 Univ E 04 1791D 888P 8 Sink 1 06 1769 ADN Compact l El g 08 1761 NET DNI Devic Download Scanlist to Scanner a Ge 04 1791D 8B8F 8 Sink l i 06 1769 ADN Compact I a g 08 1761 NET DNI Devic To automatically map input devices select the Input tab and click on the AutoMap button To automatically map output devices select the Output tab and click on the AutoMap button Twe sie Map eo as 8BV8B Polled 1 66 0 70 DN COS 8 3 0 Publication 1769 UMO09C EN P May 2005 1 8 Overview Notes Publication 1769 UMO09C EN P May 2005 Required Tools and Equipment Chapter 2 Quick Start for Experienced Users This chapter helps you get started using the 1769 SDN scanner module Procedures are based on the assumption that you have an understanding of Allen Bradley 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 The
29. N P May 2005 3 6 Installation and Wiring System Assembly Publication 1769 UMO09C EN P May 2005 The module can be attached to an adjacent controller power supply or I O module The following procedure shows you how to assemble the Compact I O system 1 2 Disconnect power Check that the bus lever of the module A is in the unlocked fully right position Use the upper and lower tongue and groove slots B to secure the modules together Move the module back along the tongue and groove slots until the bus connectors C line up with each other Use your fingers or a small screw driver to push the bus lever back slightly to clear the positioning tab D Move the module s bus lever fully to the left E until it clicks Ensure it is locked firmly in place Pani When attaching I O modules it is very important that the bus connectors are securely locked together to ensure proper electrical connection Attach an end cap terminator F to the last module in the system by using the tongue and groove slots as before Lock the end cap bus terminator G IMPORTANT A 1769 ECR or 1769 ECL right or left end cap must be used to terminate the end of the serial communication bus Installation and Wiring 3 7 System Mounting During panel or DIN rail mounting of all devices be sure that all debris metal chips wire strands etc is kept from falling i
30. Phone ____No there is no need to 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 Fax 440 646 3525 Email RADocumentComments ra rockwell com Publication ClG CO521C EN P May 2003 PN 957782 91 PLEASE FASTEN HERE DO NOT STAPLE Other Comments PLEASE FOLD HERE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS MAIL PERMIT NO 18235 CLEVELAND OH POSTAGE WILL BE PAID BY THE ADDRESSEE An P Eime DOGE WE Rockwell Automation 1 ALLEN BRADLEY DR MAYFIELD HEIGHTS OH 44124 9705 PLEASE REMOVE Rockwell Automati on Rockwell Automation provides technical information on the web to assist you in using our 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 with a hardware
31. SDN Scanner Module 1 2x General Module Scanlist Input Output ADR Summary Type Size Map Autoan 02 1790D 8BV8B Polled 1 2 0 tim 04 1791D 8B8P COS 1 3 0 ies Advanced pe H 06 1769 4DN Co COS 2 40 a 08 1761 NET DN COS 8 5 0 Options 2 Memory Discrete StatWord J0 4 Bits 15 0 15 14 13 12 11 10 38 7 615 4 3 2 1 0 1 o Read Only Read Only CE Po 04 1791 8 BBP 8 Sink In 08 1761 NET DNI Device Net Interface 08 1761 NET DNI Device Net Interface NA 17AI NFT DNI Device Net Interface z 5 081761 NET DNI Device Net Interface Ta 8 Cancel Apply Help In this example we have 4 output devices that are mapped into the scanner s output image The graphical window at the top of the dialog box shows each devices e Node number e Catalog number e Type of connection that is used between the scanner and the slave device strobed polled cyclic or change of state e The amount of data that will be exchanged in bytes e The word 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 identical slave device con
32. Your Slave Devices 1 4 1769 SDN Module Data Tables 1 5 ore software as a Configuration 1 6 00 What You Need to Know Before configuring your scanner you must understand the e Data exchange between the programmable controller and DeviceNet devices through the scanner e User configurable scanner data tables e Role of RSNetWorx software These topics are covered briefly in this chapter and in more detail throughout the rest of the manual Publication 1769 UMQ09C EN P May 2005 1 2 Overview Identify Module Features Use the following figure to identify the features of the scanner Table 1 1 Features Item Description 1 Bus lever with locking function 2A Upper DIN rail latch 2B Lower DIN rail latch 3A Upper panel mounting tab 3B Lower panel mounting tab 4 Module and Network status LEDs 5 Address and Error numeric display 6 Grounding screw 7A DeviceNet mating male receptacle 7B Removable DeviceNet female connector 8A Movable bus connector with female pins 8B Bus connector with male pins 9 Nameplate label Publication 1769 UM009C EN P May 2005 Overview 1 3 What Your Scanner Does In a typical configuration the scanner acts as an interface between DeviceNet devices and the programmable controller DeviceNet Network PLC with RSNetWorx for DeviceNet Software _ CompactLogix controller with MicroLogix 1500 Controller with 1769 SDN Scanner Module 1769 SDN scanner
33. aging allows program upload download to occur over DeviceNet and allows users to message across DeviceNet just like they did using DH 485 or DH There are a number of devices that support PCCC messaging over DeviceNet including the 1761 NET DNI DND 1203 GU6 interface and RSLinx If the DeviceNet network has DNI s either device can initiate a PCCC message Before performing a program upload 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 IMPORTANT DeviceNet networks can operate at 125 K 250 K or 500 K baud Depending on network size and communication activity performing program upload and or download operations while the network is controlling an application may impact control system performance It is up to the uset to know and understand how upload download will impact their operations Publication 1769 UMQ09C EN P May 2005 7 10 Using the 1769 SDN Scanner Module with MicroLogix Controllers To perform program upload download using RSLogix 500 select Comms From the drop down menu select System Comms RSLogix 500 SDN MASTER System Comms tid ma AIL wu JL B a Pl User ABit A SDN MASTER RSS MAIN_PROG aes hee B3 0 H Hep P EES E E j 5 Controller i foose i Controller F aistoarani fev T Processor Status 53 0 1 ae D Function Files 10 C
34. are 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 PC Abbreviation for an IBM compatible personal computer 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 non volatile storage for a node in the scanlist Rx An abbreviation for receive Scanlist The list of devices nodes with which the scanner is configured to exchange I O data Scanner The function of the 1769 SDN module to support the exchange of I O with slave modules Slave Mode The 1769 SDN module is in slave mode when it is placed in another DeviceNet mastet 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 messag
35. arget Device and Control Bits Descriptions of each of these sections follow Publication 1769 UMQ09C EN P May 2005 7 12 Using the 1769 SDN Scanner Module with MicroLogix Controllers This Controller Parameters Channel The 1764 LRP 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 also supports backplane communications through the Expansion Communication Port ECP as illustrated below MSG Rung 3 0 MG11 1 0 Integral 7 0 Integral Read 1 Integral O When ECP is chosen you are able to select which slot position 1 to 16 the scanner resides in The 1764 LRP processor can support up to two 1769 SDN scanner modules with full messaging functionality MSL Rung 3 0 MG11 1 S0OCFU Read 1 You can use multiple 1769 SDN scanner modules in a MicroLogix 1500 system but you can only message through the first two Any other 1769 SDN scanner can only be used for I O scanning Publication 1769 UM009C EN P May 2005 Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 13 Communication Command MSG Rung 3 0 MG11 1 FOOCPU Read 7 FOOCPU Read The 1764 LRP processor supports the six standard types of communications commands same as all other MicroLogix 1200 and 1500 controllers and CIP Generic When any of these six standard commands are cho
36. ata from 0 to 128 bytes sent by the scanner 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 to 128 bytes e A change of state message is a transfer of data sent whenever a data change occurs A uset configurable heartbeat rate allows devices to indicate proper operation during intervals between data changes e A cyclic message is a transfer of data sent at a specific user configurable rate such as every 50 ms IMPORTANT Throughout this document input and output are defined from the controller s 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 also supports PCCC and CIP explicit messaging defined later in this manual 1769 SDN Module Data Tables Overview 1 5 To manage the flow of data between your controller and network devices the scanner uses input and output data images to transfer data status and command information between the scanner and the MicroLogix controller For information about the CompactLogix image structure refer to the DeviceNet Modules in a Logix5000 Control System User Manual publication DNET UM004 Input Data Image The input data image is transferred from the scanner module to the controller across the Compact I O bus Table 1 2 Input Data Word Description Data Type 0 65 Statu
37. ation Input Word Bit 0 Bit 15 Description 2 1 Node 0 Node 15 Bit ON 1 Slave node faulted 312 Node 16 Node 31 Bit OFF 0 Slave node not faulted Als Node 32 Node 47 5 4 Node 48 Node 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 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 between the slave and the scanner Publication 1769 UMQ09C EN P May 2005 5 4 DeviceNet 1 0 Image Publication 1769 UM009C EN P May 2005 Table 5 4 Slave Device Configuration Comparison to Scanner Configuration Input Word Bit 0 to Bit 15 Description gl Node 0 Node 15 Bit ON 1 Slave node mismatch 72 Node 16 Node 31 Bit OFF 0 Slave node match 3 Node 32 Node 47 4 Node 48 Node 63 p BitO corresponds to Node 0 Bit 1 corresponds to N
38. c Se Rockwell Automa 0 0 0p BB E E E EE Rockwell Autome bl Graph Master Sle lt High Publication 1769 UMO09C EN P May 2005 Configure the DeviceNet Network 4 5 2 From the File menu select New If you have ControlNet configured on your system you may see the following window Otherwise proceed to step 4 Hew File Configuration Types Description Control et Configuration Control et Files c E DeviceNet Configuration DeviceNet Files drt 3 Highlight DeviceNet Configuration and click on OK 4 Click on the Online button zs on the toolbar A list of the available networks will appear Your list may appear different from that shown below depending upon the drivers you have configured on your system Hew File Configuration Types Description Control et Configuration Control et Files 4c EB DeviceNet Configuration DeviceNet Files dnt Cancel 5 Select your DeviceNet driver and click on OK You will be prompted to upload or download devices before going online DeviceNet Configuration Services AN Tou must ether upload or download devices before viewing their online configuration For more information press F1 Publication 1769 UMQ09C EN P May 2005 4 6 Configure the DeviceNet Network Publication 1769 UMO09C EN P May 2005 6 Click on OK to upload th
39. canner Power Supply Power Supply Bay bong Power Supply RSLogix 500 then 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 UM009C EN P May 2005 7 6 Using the 1769 SDN Scanner Module with MicroLogix Controllers Publication 1769 UMO09C EN P May 2005 1769 SDN Scanner Module Configuration To configure a specific module simply double click on the module To configure the scanner in this example double click on the module in slot 1 Input Words This is the number of input words the controller assigns to the module The first 66 words 0 to 65 are required by the scanner 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 2 words 0 and 1 are required by the scanner 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 outputs 199 Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 7 Changing the 1769 SDN Configuration Module 1 1769 SDWN DeviceNetScanner Changing adding or
40. cannet s master and the slave devices Table 5 9 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 DeviceNet I O Image 5 7 Module Status Register The scanner supports a 32 bit Module Status Register Table 5 10 Scanner Module Status ee Speed ER Gestion Operon 64 Bit ON 1 scanning 1 0 Bit OFF 0 halted Bit ON 1 faulted Bit OFF 0 not faulted Network Disable Bit ON 1 disabled Bit OFF 0 not disabled o oeme far on a ify Fall SOFE ro failure Communication Failure Duplicate Node Failure DeviceNet Power Detect Bit ON 1 power Bit OFF 0 no power 8to15 Reserved n a 65 Reserved n a 1 DO NOT manipulate Reserved Bits Doing so may interfere with future compatibility Input Data Image The Input Data Image can be up to a 180 word array as shown below Table 5 11 Input Data Image Word Offset Description 66 245 DeviceNet Slave input and or master output data The Input Data Image is mapped using RSNetWorx for DeviceNet configuration software Publication 1769 UM009C EN P May 2005 5 8 DeviceNet I 0 Image SDN Output File Output Array The scanner supports up to 182 output wor
41. change of state Table 5 14 Output Data Image Output Word Description Doll DeviceNet Slave output and or master input data Slave mapping is done using RSNetWorx Publication 1769 UMQ09C EN P May 2005 5 10 DeviceNet I 0 Image Notes Publication 1769 UMO09C EN P May 2005 Chapter 6 Using the 1769 SDN Scanner Module with CompactLogix Controllers For information on using the 1769 SDN scanner module with CompactLogix controllers refer to the DeviceNet Modules in Logix5000 Control Systems User Manual publication DNET UM004 Publication 1769 UMQ09C EN P May 2005 6 2 Using the 1769 SDN Scanner Module with CompactLogix Controllers Notes Publication 1769 UMO09C EN P May 2005 MicroLogix 1500 Controllers Chapter Using the 1769 SDN Scanner Module with MicroLogix Controllers This chapter contains an example where the 1769 SDN scanner module is used with a MicroLogix 1500 controller The following table describes what this chapter contains and where to find specific information For Information About SeePage Backplane Messaging 7 8 Program Upload Download 0000 79 Configuring a Local DeviceNet Message 7 11 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 as a DeviceNet master and own DeviceNet slave devices This allows either processor to communicate
42. ck on the Scanlist tab and then on the Download to Scanner button You will see this window Download Scanlist to Scanner o MU Selected Stanlist pears Sze 2 Select All Records 3 Click on the Download button to download the configuration to the scanner 4 Click on the OK button to complete the DeviceNet scanner configuration Publication 1769 UMO09C EN P May 2005 Configure the DeviceNet Network 4 25 5 From the File menu select Save As news e 1769 S0N T DeviceNet 5 NewS canner T SLX BISON Ped 1769 5DN DeviceNet Files dnt 7 6 Save the configuration to a DeviceNet file 7 Close RSNetWorx Publication 1769 UMQ09C EN P May 2005 4 26 Configure the DeviceNet Network Notes Publication 1769 UMO09C EN P May 2005 SDN Input File Chapter 5 DeviceNet 0 Image This chapter describes the input and output data structure The following table describes what this chapter contains and where to find specific information For Information About See Page SDN Input File 5 1 Status Structure 5 2 Module Status Register 5 7 Input Data Image D 7 SDN Output File 5 8 Output Data Image 5 9 The 1769 SDN scanner module s input image is configurable up to 246 words The input image is broken up into two primary components the status area and the input data area Table 5 1 Input Image Name Word Offset Status Structure 66 words fixed 0 65 Input Da
43. dentical slave device configured at the same baud rate and Node Address as the device being replaced The programmable controller for example CompactLogix or MicroLogix 1500 Cyclic Dual Mode 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 only sent at a user configurable rate The scanner module is in dual mode when it serves as a master to one ot more slaves and as a slave to another master simultaneously EDS Electronic Data Sheet 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 Heartbeat 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 I O An abbreviation for input and output Input Data Data produced by a DeviceNet device and collected by the scanner module for the host platform to read Publication 1769 UMQ09C EN P May 2005 Glossary 2 This term Means MAC ID The network address of a DeviceNet node Also referred to as node address Multicast Used when describing a strobe message Network The DeviceNet network or the RSNetWorx for DeviceNet softw
44. ds This array is broken up into two distinct data segments Table 5 12 Output Array Name Sie Word Offset Module Command Array 0 and 1 Output Data Image 180 word array 2 181 Module Command Array The module command array is the primary control interface between your control program and the module Table 5 13 Module Command Array Output Description Behavior Word 0 Run This bit controls when the module scans Its mapped slave devices When set 1 the scanner will process 1 0 data as defined by its scanlist To actually scan the network the Fault and Disable Network command bits must be clear 0 1 Fault When set the scanner s 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 Disable Network When set the scanner is functionally removed from the network Reserved n a Restarts access to the DeviceNet network Reserved n a DONOT manipulate Reserved Bits Doing so may interfere with future compatibility Publication 1769 UMO09C EN P May 2005 Output Data Image DeviceNet I O Image 5 9 The Output Data Image can be up to a 180 word array The controllers output data will be delivered across DeviceNet to the destination slave devices The scannet s scanlist configuration will determine how this data is actually sent to the slave device polled cyclic or
45. e 1769 SDN Scanner Module with MicroLogix Controllers Publication 1769 UMO09C EN P May 2005 1 0 Configuration Screen 1 0 Configuration High Speed Counter 8 Input lsolated 120 WAC PowerSupply 16 Input 79 132 YAC Analog 4 Channel Input Module Analog 4 Chan inp Chan Out 12 Input 159 265 VAC 0 Bul 764 Micrologix 1500 LAP Series C 16 Input 1030 YOC 1769 IGESO0W4 6 lnput 24 WDC 4 Output RLY 6 Channel ATO Module 6 Channel Thermocouple Module 8 Output 120 240 VAC 16 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 screen shows each of the controllers 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 through 16 are for Compact I O expansion modules referred to as local I O because they are physically attached to the controller Slots 9 through 16 are only available using a Series C processor with a Series B base unit To have RSLogix 500 read the controller s local I O and configure the slots automatically select the Read I O Config button To manually configure the controller I O simply drag the appropriate modules from the available list right window to the appropriate slot on the left Note you cannot have open slo
46. e devices and go online RSNetWorx will begin browsing for network devices When the software is done browsing your network is displayed on your screen 1769 S50N 17WS00 8BV88 17910 888P 17689 ADNYA 1761 NET ON PCB P44 Scanner 3 Univ Ini 8 Sink Int Device Met RSNetWorx 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 which was online later goes offline there will be no live indication in RSNetWorx You must manually perform a browse to detect the missing node To manually perform the browse press the ca button If RSNetWorx fails to find a device check the physical connection to the device If the physical connection is intact verify that the device s baud rate is the same as the DeviceNet drivetr s 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 using the EDS Wizard in RSNetWorx Access the wizard from the Tools pull down menu Configure the DeviceNet Network 4 7 Set the 1769 SDN 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 e g a photoeye You can also change the network data rate baud rate of some devices Depending upon the device you may need to
47. e that contains one bit for each device on the network Tx An abbreviation for transmit Publication 1769 UMO09C EN P May 2005 B before you begin 1 1 2 1 C change of state message 1 4 common techniques used in this manual P2 configuring DeviceNet I O devices 4 10 4 24 4 25 scanlist configuration 4 4 setting up an online connection 4 4 4 6 software installation 4 2 using RSLinx 4 2 4 4 using RSNetworx 4 44 25 current draw 2 2 cyclic message 1 4 D data tables 1 5 DeviceNet driver adding 4 2 4 4 DIN rail mounting 3 9 E EMC Directive 3 1 equipment required for installation 2 1 European Union Directives 3 1 explicit messaging 1 4 7 8 G grounding 3 11 input data definition 1 4 installation 3 1 getting started 2 1 grounding 3 11 heat and noise considerations 3 4 manuals related P 2 module command array 5 8 mounting 3 7 Index 0 operating modes 1 5 5 8 output data definition 1 4 P panel mounting 3 7 3 9 poll message 1 4 power requirements 3 2 publications related P 2 related publications P 2 RSLinx configuring DeviceNet 4 2 4 4 installation 4 2 RSNetWorx technical data publication P 2 RSNetWorx for DeviceNet configuration screen map 1 7 configuring DeviceNet 4 4 4 25 installation 4 2 S scanlist configuration 4 10 scanner module functions 1 3 software installation 4 2 software versions 4 1 spacing 3 7 start up instructions 2 1 strobe message 1 4 7
48. en and lock into place DIN rail mounting dimensions are shown below Height 118 mm 4 65 in 59 mm 2 325 in Publication 1769 UMQ09C EN P May 2005 3 10 Installation and Wiring Replacing the Scanner Module within a System Publication 1769 UMO09C EN P May 2005 The scanner 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 by removing the DeviceNet connector Remove the upper and lower mounting screws from the scanner or open the DIN latches using a flat blade screwdriver On the scanner to be replaced and the right side adjacent module or end cap if the scanner is the last module in the bank move the bus levers to the right unlock to disconnect the scanner from the adjacent modules Gently slide the disconnected scanner module forward If you feel excessive resistance make sure that you disconnected the scanner from the bus and that you removed both mounting screws or opened the DIN latches It may be necessary to rock the scanner 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 into the open slot Connect the scan
49. ervice code parameters Information on what services a target device supports is usually provided in the device s documentation MSG Rung 3 0 MG11 1 CIF Generic pai 5 Read Assembly write Assembly Write Output Point Read Output Point Read Input Point Read Parameter Write Parameter Read Analog Input Write Analog Output Generic Get Attribute Single Generic Set Attribute Single Generic Get Member Generic Set Member Publication 1769 UMO09C EN P May 2005 7 18 Using the 1769 SDN Scanner Module with MicroLogix Controllers MSG Instruction Error Codes When the processor detects an error during the transfer of Expansion I O Communication Module message data the processor sets the ER bit and writes an error code at MG file subelement 18 that you can monitor from your programming software Table 7 1 1769 SDN Module Error Code Error Code EOH Description Expansion I O Communication Module Error The processor also writes general status information related to this error at the high byte of MG file subelement 22 that can be monitored from your program Table 7 2 Error Status Information General Status 01H 02H 04H 07H 08H 09H OBH OCH OEH 10H 11H 13H 14H 15H 16H 19H 20H 28H Publication 1769 UMO09C EN P May 2005 Description Illegal or unsupported service parameter Resource unavailable Segment type error in IOI Connection lost Service not supported Invalid attribute
50. et Publication 1769 UMQ09C EN P May 2005 B 2 1769 SDN DeviceNet Class Codes Notes Publication 1769 UMO09C EN P May 2005 Glossary This term Means Auto Addtess Auto Address Recovery AAR allows a slave device to be Recovery AAR 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 Scanners 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 on line due to a revision keying mismatch Auto Device Replace ment ADR Bridge The Auto Device Replacement feature automates the replacement of a failed slave device on a DeviceNet network by configuring the new device to the prior level of operation This includes Configuration Recovery CR and Auto Address Recovery AAR The scanner module s support of explicit message transfer Change of State 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 occurs or at the predefined heartbeat interval Configuration Recovery CR Controller Configuration Recovery CR allows a slave device to be removed from the network and replaced with an i
51. example network is shown below DeviceNet Network PC with RSNetWorx for DeviceNet Software MicroLogix 1500 Controller 1 0 Bank with 1769 SDN Module f i f Bi mal oea Toy a Elst x HA l HE eee 1770 KFD PC ALE Communication a u Pias Module wa lo VU Ure LFY f 10 Io qi Series 9000 Photoeye Lt MicroLogix 1000 Controller MicroLogix 1200 Controller RediSTATION Connected via 1761 NET DNI Connected via 1761 NET DNI O oo S 1305 Drive Connected via 1203 GU6 Enhanced DeviceNet Communications Module Publication 1769 UMO09C EN P May 2005 Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 3 Starting the Project 1 Open RSLogix 500 2 Select File 3 New 4 Choose MicroLogix 1500 LRP series C The screen capture below should match what you see on your computer RSLogix 500 TEMP jt Bloom a ae IVA SE jay user Abit A M Es RELAD 2 MAIN_PROG E E Project Bia Help Bi Controller i Controller Properties T Processor Status T Function Files 6 0 Data Files In this example the name for this application is TEMP In the TEMP window you see everything associated with the application Within the Controller folder you will see I O Configuration 5 Double click I O Configuration Publication 1769 UM009C EN P May 2005 7 4 Using th
52. figured at the same baud rate and node address as the device being replaced Configure the DeviceNet Network 4 21 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 is not in the scanners 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 on line due to a revision keying mismatch The 1769 SDN scanner 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 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 device s such as drives Use the full electronic key including revision To enable electronic key revision checking you must be using a 1769 SDN scanner and RSNetWorx for DeviceNet Important Considerations
53. ifications Specifications Appendix A This appendix contains the product specifications for the 1769 SDN DeviceNet Scanner Module For Information About See Page General Specifications A 1 Electrical and DeviceNet Specifications A 2 Dimension Drawings A 3 Compact 1 0 with CompactLogix Controller A 3 and Power Supply Compact 0 with MicroLogix 1500 Base A 4 Unit and Processor Specification Module Dimensions Approximate Shipping Weight with carton Storage Temperature Operating Temperature Operating Humidity Operating Altitude Vibration Operating Shock Operating Shock Nonoperating Agency Certification Hazardous Environment Class Value 118 mm height x 87 mm depth x 35 mm width height including mounting tabs is 138 mm 4 65 in height x 3 43 in depth x 1 38 in width height including mounting tabs is 5 43 in 280 g 0 61 Ibs 40 C 85 C 40 F 185 F 0 C 60 C 32 F 140 F 5 95 non condensing 2000 m 6561 ft Operating 10 500 Hz 5 g 0 030 in maximum peak to peak 30 g panel mounted 20 g DIN rail mounted 40 g panel mounted 30 g DIN rail mounted e C UL certified under CSA C22 2 No 142 e UL 508 listed e CE and C Tick compliant for all applicable directives e ODVA DeviceNet conformance tested Class Division 2 Hazardous Location Groups A B C D UL 1604 C UL under CSA 22 2 No 213 Radiated and Conducted Emi
54. 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 output memory location 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 ensure that a particular slave device always matches the intended device when the scanner 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 the 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 the Major and Minor Revision keys or higher may be selected to indicate that an exact match of the revision is required or some higher revision value Should the scanner detect a mismatch with any of the key parameters checked an AutoVerify failure will occur for that slave device and the scanner will not continue the connection allocation process Publication 1769 UMQ09C EN P May 2005 4 18 Configure the DeviceNet Network Publication 1769 UMO0
55. l e provides instructions on installing the module contains information about using the module on DeviceNet e provides tips on troubleshooting the module contains application examples to show how the module is used with various programmable controllers Common Techniques Used The following conventions are used throughout this manual in this Manual e Bulleted lists such as this one provide information not procedural steps e Numbered lists provide sequential steps or hierarchical information e CAPITALIZED BOLD type is used for emphasis Re ated Documentati on The following documents contain additional information concerning Rockwell Automation products Contact your local A B distributor for information on ordering the publications For electronic copies go to http www ab com literature For Information On Configuring the CompactLogix controllers in DeviceNet and bridging information Configuring the CompactLogix controllers in ControlNet and bridging information RSNetWorx for DeviceNet catalog number 9357 DNETL3 Planning mounting wiring and troubleshooting your CompactLogix system Planning mounting wiring and troubleshooting your MicroLogix 1500 system Installing configuring and using Compact 0 analog modules How to install and use the DeviceNet Interface catalog number 1761 NET DNI DeviceNet network planning information IDF1 open protocol Grounding and wiring Allen Bradley
56. l 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 If available use a static safe work station e When it is not in use keep the module in its static shield box Remove 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 by gt t 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 may 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 System Planning Installation and Wiring 3 5 Protecting the Circuit Board from Contamination The printed circuit boards of the modules must be protected from dirt oil moisture and other airborne contaminants To protect these boards we recommend installing the system in an enclosure suitable for the environment The interior of the enclosure should be kept clean and the enclosure door should be kept closed whenever possible
57. lectrical arc may occur An electrical arc can cause personal injury or property damage 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 may lead to premature failure 3 Assemble and mount the I O bank The module can be attached to an adjacent controller power supply or I O module The 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 4 Ground the module and complete DeviceNet wiring Publication 1769 UMO09C EN P May 2005 10 11 Quick Start for Experienced Users 2 3 Apply power to the system Be sure programming software and equipment is ready Use RSLinx to configure drivers Use RSNetWorx to configure the 1769 SDN scanner module and the DeviceNet devices Use RSLogix 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 During a normal start up the Module and Network LEDs turn on solid green Monitor the module status to check if the module is operating correctly Module status is reported by the LEDs and numeric display on the front of the module The information is also stored in the module s in
58. n Module No power applied to module Apply power Flashing No Bus Master MicroLogix or Green CompactLogix controller present 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 No action required Flashing Red Recoverable Fault Memory has been Complete flash update or start a new update erased or is being programmed solid Red Unrecoverable fault Network No module power no network power or communications are not occurring between the module and the DeviceNet network This may be an acceptable condition Flashing Device is operational There are no Green connections established with any of the network devices solid Green Normal operation Scanlist is configured No action required Module is not in Idle mode Flashing Red One or more of the devices that the scanner is communicating with Is in a timed out state solid Red Critical network failure Duplicate DeviceNet node address detected Verify module connectors are properly seated If they are verity that bus terminator end cap is installed Cycle power If still faulted replace the module Verify module has power Check that the DeviceNet cable is securely connected and the DeviceNet network is powered Verify that network power is
59. n 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 Identifies information about practices or circumstances ATTENTION that can lead to personal injury or death property damage or economic loss Attentions help you e identify a hazard e avoid a hazard recognize the consequence STIR a VZV Labels may be located on or inside the drive to alert people that dangerous voltage may be present BURN HAZARD Labels may be located on or inside the drive to alert people that surfaces may be dangerous temperatures Summary of Changes The information below summarizes the changes to this manual since the last printing To help you find new and updated information in this release of the manual we have included change bars as shown to the right of this paragraph The table below lists the sections that document new features and additional or updated information about existing features For this information See Updated related publications listing P 2 Reference to using the 1769 SDN with CompactLogix 6 1 controllers Publication 1769 UMQ09C EN P May 2005 summary of Changes 2 Notes Publication 1769 UMO09C EN P May 2005 Preface Overview Quick Start for Experienced Users Installation and Wiring C
60. nd Tx parameters define how much data will be exchanged over the change of state or cyclic connection that owns the scanner s slave 0 Maximum size is 128 bytes Publication 1769 UMO09C EN P May 2005 Configure the DeviceNet Network 4 15 Advanced Module Settings Clicking on the Advanced button opens the following screen Advanced Module Settings Expected Packet Rate EPR When the scanner 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 within 4 times the EPR value the slave device drops the connection If the scanner does not receive a packet from the slave within 4 times the EPR value it drops the connection and periodically attempts to open a new connection When a connection is dropped status bits in the scanner 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 IMPORTANT Changing the EPR number should be done carefully because it effects how long it takes the scanner to detect a missing device Transmit Retries Transmit Retries specifies the number of times the scanner attempts to retran
61. ner and modules together by locking fully left the bus levers on the replacement scanner and the right side adjacent module or end cap Replace the mounting screws or snap the scanner onto the DIN rail Replace the DeviceNet cable on the scanner by attaching the connector to the scanner Restore scanner configuration using RSNetWorx for DeviceNet IMPORTANT Be sure that the new module has the same node address and baud rate as the module that was replaced Field Wiring Connections Ground the Scanner Module Installation and Wiring 3 11 This product is intended to be mounted to a well grounded mounting surface such as a metal panel Additional grounding connections from the scannet s mounting tabs or DIN rail if used are not required unless the mounting surface cannot be grounded ATTENTION The grounding screw on the front of the scanner must be connected to a suitable ground source when operating in electrically noisy environments Use a 14 AWG wite to make this connection Refer to Industrial Automation Wiring and Grounding Guidelines Allen Bradley publication 1770 4 1 for additional information DeviceNet Wiring V co a DeviceNet Connector Grounding Screw Use 14 AWG wire to connect to panel ground A Table 3 4 Connect Red Wire White Wire Bare Wire Blue Wire Black Wire qaaae AANAAS aaa Va Vag y S r V CAN High shield CAN Low V
62. nto the module Debris that falls into the module could cause damage at power up Minimum Spacing Maintain spacing from enclosure walls wireways adjacent equipment etc 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 in of enclosure depth to accommodate the module and the DeviceNet connector Panel Mounting Mount the module to a panel using two screws per module Use M4 or 8 panhead screws Mounting screws are required on every module Publication 1769 UMQ09C EN P May 2005 3 8 Installation and Wiring Panel Mounting Using the Dimensional Drawing All dimensions are in millimeters inches Hole spacing tolerance 0 4 mm 0 016 in Compact 1 0 with L35E CompactLogix Controller and Power Supply 67 5mm 70mm 2 681in 2 7610 15mm 52 5mm 2 06in CRIN C 10s COREE M AB CAS C wy Allen Bradley Logix L35E 132mm 5 20in 118mm 4 65in CHANNEL 1 CHANNEL 0 y AU UA 35MM _ 35mm m 1 38in 1 38in AU UA i 52 5mm he 35mm whe 35mm on ae 2 0711 1 38in 1 381in Compact I 0 with MicroLogix 1500 Base Unit and Processor Mounting Hole Dimension 6 62 in 28 5 mm 147 mm 112 in 5 79 in 93 2 D ts
63. oad Device Config This will load the configuration of each device selected into the scanner configuration software If you are online but did not upload the network the configuration retrieved for the devices may not be what is actually used online Configure the DeviceNet Network 4 23 3 Click the box next to Configuration Recovery 1769 SDN Scanner Module 1 Ge 04 1791D BB8P Notice the ADR space in pees C o bytes is displayed for the 0S 1761 MET D module you are updating 4 Click the box next to Auto Address Recovery if desired The Enable Auto Address Recovery box 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 are enabled while Config indicates that only Configuration Recovery is enabled 1769 SDN Scanner Module 1 a j2 17900 668 Both 04 1791D 8B8P Config ADH Both ETS 1761 MET D Config 6 When finished click Download to Scanner 7 Click Apply or OK Publication 1769 UM009C EN P May 2005 4 24 Configure the DeviceNet Network Summary Tab The summary tab provides a condensed picture of the scanner s configuration which nodes are mapped if they are active and receive and transmit information 1769 S5DN Scanner Module 1 Yez 06 1769 4 ves E 08 1761 Yes Download and Save Your Configuration 1 Cli
64. ode 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 or that the slave is not present in the scanlist A bit value of 1 represents idle mode where the slave node is present in the scanlist Table 5 5 Slave Device Status Input Word Bit 0 to Bit 15 Description 10 Node 0 Node 15 Bit ON 1 idle 44 2 Node 16 Node 31 Bit OFF 0 non idle 413 Node 32 Node 47 1314 Node 48 Node 63 Sk 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 Active Node Array DeviceNet I O Image 5 5 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
65. onfiguration be Channel Configuration oi Program Files b sYS0 LR SYS1 System Comms will generate an RSLinx screen similar to the example below Communications Workstation SL 527 as Lins Gateways Ethernet Ege 1770 KFD 1 DeviceNet f 00 1747 SDN Scanner Module ff 62 Workstation SLX 527 as 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 download can be performed with the devices at nodes 5 6 7 and 32 Node 32 is a 1769 SDN Simply highlight the 1769 SDN and then click on either the upload or download button on the right side of the screen Publication 1769 UMO09C EN P May 2005 Configuring a Local DeviceNet Message Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 11 This section describes how to configure a local message using the scanner and a MicroLogix 1500 1764 LRP processor Message Setup Screen SLAD 3 MSG File e 0000 e Read Write Message MSG Fi MG11 1 Setup Screen MSG Rung 3 0 MG11 1 O integral 500CPU Read n Rung 0 shows a standard RSLogix 500 message MSG instruction preceded by conditional logic Access the message setup screen by double clicking the Setup Screen The RSLogix 500 Message Setup Screen appears This screen is used to setup or monitor message parameters for This Controller T
66. onfigure the DeviceNet Network DeviceNet l 0 Image Using the 1769 SDN Scanner Module with CompactLogix Controllers Table of Contents Who Should Use this Manual 0 000 0c eee eee P 1 ADO COMPACT LOOR gyra riaa a Son aa dai P 1 Purposeor iis Manual redete iein er ea TEE EEEE P 2 Common Techniques Used in this Manual P 2 Related Doctimentauon lt ss44 3 6 058466 b oosh 056558446 bh P 2 Chapter 1 What You Need to IKnOw seceta 8 de ein ay oere n chee eae ek 2 1 1 Identity Modale Features icy p85 oa a or Re ded ore Eamon iN bee 1 2 What Vout ocanner Does ann erie bake net ee ee eae ace 1 3 Communicating with Your Slave Devices 006 1 4 1769 SDN Module Data Tables soc cc ccc ce bein ev eee bee wba 1 5 RSNetWorx Software as a Configuration Tool 0 1 6 Chapter 2 Required Tools and Equipment t5 4 04 00 ind oaeariandie 24 eke eed 2 1 Wat Y OU Need To DOreror ipri erd aE a haha Shee Bw Se og 22 Chapter 3 Compliance to European Union Directives 006 3 1 Power KeEquITeMents t44s1G655d aGneatn oe teens E E see 3 2 General Considerations 4 224 se cube Path eas hes Chee ESE aa 3 3 Dy Ste Mi IAN MING ts hii handles bw Saad tae erie Pak Gt Ad ee 3 5 SEAS a ee ee ee a ee eee 3 6 SVSteM MOUM 6 o s todas Yat o act AE Re a oe EES eel oe 3 7 Replacing the Scanner Module within a System 3 10 Field Witine Connections s owas ipand bu a tees OS uea 4b tee 3
67. ower Requirements Publication 1769 UMO09C EN P May 2005 Low Voltage Directive This product is tested to meet Council Directive 73 23 EEC Low Voltage by applying the safety requirements of EN 61131 2 Programmable Controllers Part 2 Equipment Requirements and Tests For specific information required by EN61131 2 see the appropriate sections in this publication as well as the following Allen Bradley publications e Industrial Automation Wiring and Grounding Guidelines for Noise Immunity publication 1770 4 1 e Automation Systems Catalog publication B113 The module receives power through the Compact I O bus interface from the 5V dc system power supply Table 3 1 Maximum Current Drawn by the Module 1769 SDN 440 mA 0 mA The module also draws power from the DeviceNet network Table 3 2 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 Installation and Wiring 3 3 General Considerations Compact I O 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 29 and to circuits not exceeding Over Voltage Category u IEC 60664 1 Hazardous Location Considerations This equipment is suitable for use in Class I Division 2 Groups A B C D or non hazardo
68. put data file so these bits can be used in your control program to flag an error Publication 1769 UMQ09C EN P May 2005 2 4 Quick Start for Experienced Users Notes Publication 1769 UMO09C EN P May 2005 Compliance to European Union Directives Chapter 3 Installation and Wiring This chapter describes how to install and wire the 1769 SDN scanner module The following table describes what this chapter contains and where to find specific information For Information About See Page Compliance to European Union Directives 3 1 Power Requirements 3 2 General Considerations 3 3 system Planning 3 5 system Assembly 3 6 system Mounting 3 7 Replacing the Scanner Module within a 3 10 System Field Wiring Connections 3 11 Scanner Module Power Up 3 12 This product is approved for installation within the European Union and EEA regions It has been designed and tested to meet the following directives EMC Directive The module is tested to meet Council Directive 89 336 EEC Electromagnetic Compatibility EMC and the following standards in whole or in part documented in a technical construction file e EN 50081 2 EMC Generic Emission Standard Part 2 Industrial Environment e EN 50082 2 EMC Generic Immunity Standard Part 2 Industrial Environment This product is intended for use in an industrial environment Publication 1769 UMQ09C EN P May 2005 3 2 Installation and Wiring P
69. removing the amount of data the controller has assigned to the scanner is done in the expansion module configuration screen From within RSLogix 500 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 s scanlist which is done using RSNetWorx IMPORTANT It is recommended that you NOT reduce the number of words assigned to a 1769 SDN s scanlist once a system is operational Changing the number 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 Simply add the number of additional words that are needed in the module using the above example and change the scanlist using RSNetWorx Publication 1769 UMQ09C EN P May 2005 7 8 Using the 1769 SDN Scanner Module with MicroLogix Controllers Backplane Messaging Publication 1769 UMO09C EN P May 2005 The configuration screen for the scanner is shown below Module 1 1769 SDWN DeviceNetScanner Ignore Configuration Error Checking enabling this box instructs the module to ignore I O size mismatches If this is checked and the input output scanlist configured by RSNetWorx DeviceNet side of the 1769 SDN doe
70. s NOT match the amount of I O data assigned by the controller 0 to 180 words the module will not generate an error If this box is not checked the number of data words on the controller side must match the number of words configured by RSNetWorx The default condition is unchecked report an error on mismatch Series Major Rev Minor Rev You will need this information if you contact Rockwell Automation Technical Suppott 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 DeviceNet 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 Program Upload Download Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 9 PCCC Messaging PCCC stands for Programmable Controller Communications Commands PCCC provides point to point and master slave communications 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 communications between Allen Bradley controllers PCCC mess
71. s structure 66 word array 66 245 DeviceNet slave inputs 180 word array Output Data Image The output data image is transferred from the controller to the scanner module across the Compact I O bus Table 1 3 Output Image Word Description Data Type 0 and 1 Module command array 2 word array Zalo DeviceNet slave outputs 180 word array Table 1 4 Module Command Array Bit Assignments Word 0 Operating Mode 1 run 0 idle 1 fault 1 disable network Reserved 1 reset OIl AI Wy N O1 Reserved 1 on a on Reserved 0 DO NOT manipulate Reserved Bits Doing so may interfere with future compatibility Publication 1769 UM009C EN P May 2005 1 6 Overview RSNetWorx Software as a Configuration Tool Publication 1769 UMO09C EN P May 2005 RSNetWorx is used to configure the scanner s slave devices This software tool connects to the scanner over the DeviceNet network via an RS 232 interface 1770 KED module or PC Card 1784 PCD or PCID The recommended configuration software is RSNetworx for DeviceNet version 3 00 or higher 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 using the EDS Wizard in RSNetWorx Access the wizard from the Tools pull down menu This configuration tool allows you to identify all of the DeviceNet devices and their locations in
72. sen you can initiate standard messages to destination devices connected to DeviceNet products that support PCCC messaging including MicroLogix and SLC controllers using 1761 NET DNIPs other MicroLogix 1500 controllers using 1769 SDN scanner modules etc You can initiate reads writes program upload download and online monitoring across DeviceNet This is functionally identical to DH 485 and DH networking Publication 1769 UMQ09C EN P May 2005 7 14 Using the 1769 SDN Scanner Module with MicroLogix Controllers Publication 1769 UMO09C EN P May 2005 CIP Generic CIP stands for 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 DeviceNet 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 1G11 1 Expansion Comms Part CIP Generic Using the 1769 SDN Scanner Module with MicroLogix Controllers 7
73. smit 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 Publication 1769 UMQ09C EN P May 2005 4 16 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 40M Compact l S202 17900 0606 8 Univ Ga 4 7 7910 G68P 8 Sink I Veo Product bode Major Revision PFT Dl cit Aigner 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 on the same network or they may have dual functionality An example of a dual function device is the 1761 NET DNI The DNI can be used as slave I O or as a communications interface for PLC s or other DF1 full duplex devices Publication 1769 UMO09C EN P May 2005 Automap Options Data Alignment Bote Align Bivord Align Configure the DeviceNet Network 4 17 Scanlist These devices have been assigned to be slave I O to this scanner A slave device on DeviceNet can only be owned by 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
74. ssions EN50081 2 Class A Publication 1769 UMQ09C EN P May 2005 A 2 Specifications Electrical and DeviceNet Specifications Publication 1769 UM009C EN P May 2005 Specification Electrical EMC ESD Immunity IEC61000 4 2 Radiated Immunity IEC61000 4 3 Fast Transient Burst IEC61000 4 4 Surge Immunity IEC61000 4 5 Conducted Immunity IEC61000 4 6 Value The module has passed testing at the following levels e 4kV contact 8 kV air 4 kV indirect e 10 V m 80 1000 MHz 80 amplitude modulation 900 Mhz keyed carrier e 2 kV 5 kHz e 2 kV galvanic gun e 10V 0 15 80 MHz 2 0 For operation above 2000 meters consult the factory 2 Conducted Immunity frequency range may be 150 kHz to 30 MHz if the Radiated Immunity frequency range is 30 MHz to 1000 MHz Specification Bus Current Draw Max DeviceNet Power Requirements Heat Dissipation Max Baud Rates Maximum Cable Length DeviceNet Cable Power Supply Distance Rating DeviceNet to Compact Bus Isolation Vendor I D code Product Type Code Product Code Value 440 mA 5V dc 2 2 W N E C Class 2 90 mA 11V dc max 110 mA 25V dc max 200 mA for 1 5 ms inrush 3 8 W assumes typical DeviceNet network traffic 125 K bits s default 250 K bits s 500 K bits s 500 m 125 K baud 100 m 500 K baud Allen Bradley catalog number 1485C P1 Cxxx 4 The module may not be more than 4 modules away from the power suppl
75. ta Image 180 word array configurable 66 245 Publication 1769 UMQ09C EN P May 2005 5 2 DeviceNet 0 Image Status Structure Publication 1769 UMO09C EN P May 2005 The first area of the input image is the Status Structure The status words are described in more detail in the following sections Table 5 2 Status Structure Description Words Data Type scan Counter 2 words Device Failure Array 64 bit array Autoverify Failure Array ee 64 bit array Slave Device Idle Array tOta 64 bit array Active Node Array 14 17 64 bit array Reserved 4 byte array scanner Status 4 byte array Reserved Array 20 byte array Device Status Array 64 byte array Module Status Register 2 words DONOT 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 DeviceNet I O Image 5 3 Device Failure Array These 64 bits provide status information for use in your control program For each slave device owned by the scanner the user 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 Table 5 3 Slave Device Status Inform
76. tly configured to scan slave devices Verify DeviceNet network connections None There are other active devices on the network initiating messages but none of the messages are for the module Either reconfigure the slave device or change the module s scanlist to match the slave device Either add the device to the DeviceNet network or delete the device s entry in the scanlist Make sure that the module is connected to a valid network Check for disconnected cables Put the controller into RUN mode and enable the RUN bit in the Module Command Array see page 5 8 Check the FAULT value in the Module Command Array See page 5 8 Check scanlist table entry for slave device to make sure that input and output data lengths are correct Check slave device configuration Check slave device s configuration Reboot Slave device Publication 1769 UMQ09C EN P May 2005 8 4 Troubleshooting Table 8 2 Device Status Code Description decimal 84 Not Yet Initialized Module has not completed its initial attempt to establish communications with its slaves 85 Receive Buffer Overflow Data size returned is larger than expected 86 Device Went Idle Device is producing idle state 89 Auto Device Slave device responded with an error to the Replacement ADR Error initialization data sent to it by the scanner or the configuration table in the scanner s flash memory is not valid for a slave node 90 Disabled
77. ts modules must be contiguous from 1 to 16 Series B base units will be available late in 2001 Contact your local Allen Bradley distributor for availability Using the 1769 SDN Scanner Module with MicroLogix Controllers 7 5 Read 1 0 Configuration Read 10 Configration from Online Processor ABDI F AB_DF1 1 Node 1d local The next screen that appears is a communications dialog that allows you to select a communication path using RSLinx to the MicroLogix controller If you have previously connected to a controller the communications driver that you used before will be the active driver This dialog screen 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 select Read I O Config Installed 1 0 I 00 Configuration High Speed Counter 8 Input Isolated 120 VAC 1769 1416 16 Input 79 132 VAC 1769 IF4 Analog 4 Channel Input Module 1769 1F4X0F2 Analog 4 Chan Inp 2 Chan Out 1769 1M12 12 Input 159 265 VAC 0 Bul 1764 Micrologix 1500 LAP Series C 1769 1016 16 Input 10 30 YDC 1 1769 SDN DeviceNetScanner 1769 IQEXOW4 6 Input 24 YDC 4 Output RLY 2 1769 1016 16 Input 10 30 DC 6 Channel RTD Module 6 Channel Thermocouple Module 8 Output 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 Output Isolated Relay DeviceNetS
78. us locations only The following WARNING statement applies to use in hazardous locations EXPLOSION HAZARD Substitution of components may impair suitability for Class I Division 2 Do not replace components or disconnect equipment unless power has been switched off or the area is known to be non hazardous Do not connect or disconnect components unless power has been switched off or the area is known to be non hazardous This 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 non conductive pollution occurs except that occasionally a temporary conductivity caused by condensation shall be expected 2 Over Voltage Category II 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 designations Pollution Degree 2 and Over Voltage Category Il are International Electrotechnical Commission IEC Publication 1769 UMQ09C EN P May 2005 3 4 Installation and Wiring Publication 1769 UMO09C EN P May 2005 Prevent Electrostatic Discharge ATTENTION Electrostatic discharge can damage integrated circuits or semiconductors if you touch the bus connector pins AN Follow these guidelines when you handle the module e Touch a grounded object to discharge static potentia
79. value Already in requested mode state Object state conflict Attribute not setable Device state conflict Reply data too large Not enough data Attribute not supported Too much data Object does not exist Store operation failure Invalid parameter Invalid member ID Chapter 8 Troubleshooting The 1769 SDN scanner module is provided with LED diagnostic indicators on its front panel The diagnostics provided by these indicators are described in this chapter For Information About See Page Diagnostic Indicators 8 1 Error Codes 8 3 Diagnostic Indicators The first step in troubleshooting is to observe the 1769 SDN scanner module s LEDs and 7 segment numeric displays The indicators function as follows e The bicolor green red Module Status LED indicates whether the scanner has power and is functioning properly e The bicolor green tred Network Status LED provides information about the DeviceNet channel communication link e The numeric display shows Node Address and Status Display information Status information precedes the node addtess Publication 1769 UMQ09C EN P May 2005 8 2 Troubleshooting The following table summarizes the meanings of the LEDs and numeric codes Module LED Network LED Node Address and Status Display Table 8 1 Troubleshooting the LEDs and Numeric Display i MODULE NETWORK DeviceNet ADDRESS ERROR Indicator Color Status Indicates Recommended Actio
80. y Verified by one of the following dielectric tests 500V ac for 1 minute or 707V dc for 1 minute 30V dc working voltage IEC Class 2 reinforced insulation 1 12 105 Specifications A 3 Dimension Drawings Compact I 0 with CompactLogix Controller and Power Supply NOTE All dimensions are in mm inches Hole spacing tolerance 0 4 mm 0 016 in Compact 1 0 with CompactLogix Controller and Power Supply 28 5 mm MAR ee Mounting Hole Dimension 5 19 in 4 83 in 147 4 mm 5 81 in 132 mm 122 6 mm DIN Rail Center Line 14 7 mm 0 58 in Publication 1769 UM009C EN P May 2005 A 4 Specifications Compact 1 0 with MicroLogix 1500 Base Unit and Processor NOTE All dimensions are in mm inches Hole spacing tolerance 0 4 mm 0 016 in Compact I 0 with MicroLogix 1500 Base Unit and Processor Mounting Hole ee Dimension 6 62 in 1 38 in 28 5 mm 147 mm 35 mm 1 12 in 5 79 in i z LS lt lt y F DIN Rail 7 Center Line 13 5 mm 14 7 mm 0 53 in 0 58 in Publication 1769 UMO09C EN P May 2005 132 mm 5 19 in Appendix B 1769 SDN DeviceNet Class Codes This appendix contains the most commonly used class codes for the 1769 SDN DeviceNet Scanner Module They are shown in the following tables Table B 1 DeviceNet Object The set also causes a reset Table B 2 Identity Object Product Code Get Serial Number Get Product Name G
81. y 1770 KFD Driver Configuration Eanigue Maert i me Hemari Your driver setup will depend on your particular system setup COM port baud rate node address Choose the appropriate settings for your system Publication 1769 UM009C EN P May 2005 4 4 Configure the DeviceNet Network 5 Configure the driver using the example above as a guide and click on OK The software will take a few seconds to configure the driver Add New ASLins Driver Choose a name for the new driver 15 characters masimum Cancel li FFO KFD 1 6 Click on OK to use the default driver name 7 Minimize RSLinx You will use the driver you just configured to browse and configure the network with RSNetWorx Use RSNetWo rx to This manual assumes a certain level of familiarity with RSNetWorx For Co nfigure the 1769 SDN s detailed information on RSNetWorx for DeviceNet please refer to your S canlist software s documentation 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 L DeviceNet RSNetWorx for DeviceNet Eie Edit View Network Device Tools Help jals aal Sew a aE Elk lA 8 Hardware xj DeviceNet e Category AC Drive Barcode Scanne Dodge EZLINK General Purpose Generic Device Human Machine Inductive Proxim Limit Switch Photoelectri
82. your system The controller must be in Program mode or the scanner in Idle mode bit 0 of the Module Command Array 0 for the scanner to accept the configuration information Overview 1 7 The main RSNetWorx screen 1790D 8BV8B MED DeviceNet 8 Univ Inf Sre 4 Barcode Scanner E Communication Adapter C DPI to DeviceNet C DeviceNet to SCANport C Dodge EZLINK O General Purpose Discrete 1 0 O Generic Device O Human Machine Interface O Inductive Proximity Switch C Limit Switch O Motor Protector C Photoelectric Sensor p epee e 1769 ADN A G 1761 NET DNI FJ Smart MCC Series B O Specialty 1 0 P onas AO Rockwell Automation Allen Bradley D Rockwell Automation Dodge ae ae a ag Rockwell Automation Electro Craft Motion Cq Rockwell Automation Reliance Electric Rockwell Automation Sprecher Schuh 2 S S o aaa DeviceNet Int 1791D 8B8P 8 Sink In a Source Out 3 1761 NET DNI Device Net Interface 7 Figure 1 1 RSNetWorx Configuration Screen Map 1769 SDN Scanner Module 5 To browse the network click on the Online button and select the driver 770 KFD 1 DeviceNe OER DF1 PCB P447 To access the 1769 SDN scanner module double click on the 1769 SDN icon To edit a device s 1 0 parameters double click on the device in the scanlist Edit I O Parameters 04 1791D 8B8P 8 Si wv To access the scanlist click on the Scanlist tab

1769-UM009C-EN-P, Compact I/O 1769

Contents

Download Pdf Manuals

Related Search

Related Contents