1756-ENBT 1756-EN2F 1756-EN2T 1756-EN2TR 1756-EN2TXT 1768-ENBT 1769-L23E-QB1B - Datasheet Archive

 

Systems Catalog Numbers 1756-ENBT, 1756-EN2F, 1756-EN2T, 1756-EN2TR, 1756-EN2TXT, 1768-ENBT, 1769-L23E-QB1B, 1769-L23E-QBFC1B,

 

EtherNet/IP Modules in Logix5000 Control Systems Catalog Numbers 1756-ENBT 1756-ENBT, 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, 1756-EN2TXT 1756-EN2TXT, 1768-ENBT 1768-ENBT, 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B, 1769L32E 1769L32E, 1769-L35E 1769-L35E, 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, 1783-ETAP2F 1783-ETAP2F, 1794-AENT 1794-AENT, 20COMM-E 20COMM-E, 22-COMM-E 22-COMM-E, 1734-AENT 1734-AENT, 1734-AENTR 1734-AENTR User Manual Important User Information Solid state equipment has operational characteristics differing from those of electromechanical equipment. Safety Guidelines for the Application, Installation and Maintenance of Solid State Controls (publication SGI-1.1 available from your local Rockwell Automation sales office or online at http://www.rockwellautomation.com/literature/) describes some important differences between solid state equipment and hard-wired electromechanical devices. Because of this difference, and also because of the wide variety of uses for solid state equipment, all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable. In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment. The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams. No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual. Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited. Throughout this manual, when necessary, we use notes to make you aware of safety considerations. WARNING IMPORTANT ATTENTION SHOCK HAZARD BURN HAZARD Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss. Identifies information that is critical for successful application and understanding of the product. Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present. Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures. Allen-Bradley, ArmorPOINT, CompactLogix, ControlLogix, DriveLogix, FLEX I/O, FlexLogix, Guard I/O, Logix5000, POINT I/O, Rockwell Automation, RSLinx, RSLogix 5000, Stratix 6000, Stratix 8000, and TechConnect are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies. Summary of Changes Introduction This release of this document contains new and updated information. To find new and updated information, look for change bars, as shown next to this paragraph. Updated Information The document contains these changes. Topic Page Description of 1783-ETAP1F 1783-ETAP1F and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Fiber Taps to the EtherNet/IP Overview chapter 13 Updated Rockwell Automation Products with Embedded Switch Technology section 58 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Tap Status Indicators 187 Additional less significant changes have been made throughout the document. Change bars mark all changes. 3Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 3 Summary of Changes Notes: 4 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Table of Contents Preface Purpose of This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Who Should Use This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Chapter 1 EtherNet/IP Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1756-ENBT 1756-ENBT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, and 1756-EN2TXT 1756-EN2TXT Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 1768-ENBT 1768-ENBT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B Packaged Controllers . . . . 17 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 1769-L32E 1769-L32E and 1769-L35E 1769-L35E Controllers . . . . . . . . . . . . . . . . . . . . . . . . 18 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Taps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1788-ENBT 1788-ENBT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1794-AENT 1794-AENT Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1734-AENT 1734-AENT and 1734-AENTR 1734-AENTR Adapters . . . . . . . . . . . . . . . . . . . . . . 20 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1738-AENT 1738-AENT and 1738-AENTR 1738-AENTR Adapters . . . . . . . . . . . . . . . . . . . . . . 21 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 20-COMM-E 20-COMM-E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22-COMM-E 22-COMM-E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 EtherNet/IP Communication Modules in a Control System . . . . . . . 23 Installing Communication Modules or Other Devices on the EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Safety I/O in EtherNet/IP Control Systems . . . . . . . . . . . . . . . . . . . . 24 I/O Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Guard I/O Catalog Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 CIP Safety in EtherNet/IP Safety Architectures . . . . . . . . . . . . . . 26 Bridge Across Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 EtherNet/IP Network Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Chapter 2 Configure a Workstation to Operate on an EtherNet/IP Network 5Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Configure the Ethernet Communication Driver in RSLinx Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 5 Table of Contents Chapter 3 Configure Stratix Switches Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Select a Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Switch Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Determine Network Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Set the IP Network Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Assign Network Parameters via the BOOTP/DHCP Utility . . . . . . . 45 Other Methods to Assign Network Parameters . . . . . . . . . . . . . . . . . . 47 Configure the Module with RSLinx Software . . . . . . . . . . . . . . . . 48 Configure Your Module with RSLogix 5000 Software . . . . . . . . . 50 Use DHCP Software to Set the IP Address . . . . . . . . . . . . . . . . . . 51 Duplicate IP Address Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Detection of Duplicate IP Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 IP Address Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 DNS Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Use EtherNet/IP Modules in a Logix5000 Controller Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Chapter 5 Configure a Supervisor on a Device-level Ring Network 6 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Rockwell Automation Products with Embedded Switch Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Features Common to Products with Embedded Switch Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Supervisor Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Ring Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Construct the Physical Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Configure Supervisor Nodes on a DLR Network . . . . . . . . . . . . . . . . 64 Configure a Ring Supervisor in RSLogix 5000 Programming Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Enable Ring Supervisor in RSLogix 5000 Programming Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Configure and Enable a Ring Supervisor in RSLinx Classic Communication Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Complete the Physical Connections of the Network . . . . . . . . . . . . . . 74 Verify Supervisor Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Troubleshoot DLR Network Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Table of Contents Chapter 6 Control I/O Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Add Distributed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Add a Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Select a Communication Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Choosing a Direct or Rack-optimized Connection . . . . . . . . . . . . 83 Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Select a Remote Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Set the Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . 88 Access Distributed I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Chapter 7 Interlocking and Data Transfer Between Controllers Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Logix5000 Controller Combinations . . . . . . . . . . . . . . . . . . . . . . . 94 Tag Guidelines for Produced or Consumed Data . . . . . . . . . . . . . . . . 95 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 Connections for Produced and Consumed Tags . . . . . . . . . . . . . . . . . 96 Produce a Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Configure the Produced Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Consume Data Produced by Another Controller. . . . . . . . . . . . . . . . 100 Add the Producer Controller to the Consumer's I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Create the Consumed Tag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Guidelines for Message (MSG) Instructions. . . . . . . . . . . . . . . . . . . . 105 Connections for Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Cache Message Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Enter Message Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Add the EtherNet/IP Module to the Local Controller's I/O Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Enter a Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Configure a MSG Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Communicate with PLC-5 or SLC Processors . . . . . . . . . . . . . . . . . . 115 Converting between INTs and DINTs . . . . . . . . . . . . . . . . . . . . 115 Mapping Tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Receive MSGs from PLC-5 or SLC 500 Processors . . . . . . . . . . 118 7 Table of Contents Chapter 8 Send Email Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 EtherNet/IP Module as an Email Client . . . . . . . . . . . . . . . . . . . . . . 119 Send Email Via a Controller-initiated Message Instruction . . . . . . . . 121 Create String Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Enter the Ladder Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Configure the MSG Instruction That Identifies the Mail Relay Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Configure the MSG Instruction That Contains the Email Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Enter Email Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Possible Email Status Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Chapter 9 Communicate with PanelView Terminals Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Logix5000 Controller Combinations . . . . . . . . . . . . . . . . . . . . . . 132 Connections to PanelView Terminals . . . . . . . . . . . . . . . . . . . . . . . . . 132 Add a PanelView Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Organize Controller Data for a PanelView Terminal. . . . . . . . . . . . . 136 Connections to RSView Applications . . . . . . . . . . . . . . . . . . . . . . . . . 136 Chapter 10 Monitor Diagnostics Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Diagnostic Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Network Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Explicit Message Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 Ethernet Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Chapter 11 Troubleshoot an EtherNet/IP Module 8 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Access Web Browser Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147 Diagnostic Overview Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Message Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 I/O Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Ethernet Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Switch Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 Internet Group Multicast Protocol . . . . . . . . . . . . . . . . . . . . . . . . 157 Virtual Local Area Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Table of Contents Chapter 12 USB Serial Communication Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Set Up the Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161 Configure a Module Via the USB Port . . . . . . . . . . . . . . . . . . . . . . . . 162 Set Up a USB Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Flash Upgrade Firmware through a USB Port . . . . . . . . . . . . . . . . . . 165 Appendix A Status Indicators Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 1756-ENBT 1756-ENBT EtherNet/IP Module Status Indicators. . . . . . . . . . . . . 169 1756-EN2F 1756-EN2F EtherNet/IP Module Status Indicators . . . . . . . . . . . . . 171 1756-EN2T 1756-EN2T EtherNet/IP Module Status Indicators . . . . . . . . . . . . . 173 1756-EN2TR 1756-EN2TR EtherNet/IP Module Status Indicators. . . . . . . . . . . . 175 1756-EN2TXT 1756-EN2TXT ControlLogix-XT EtherNet/IP Bridge Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 1769-L23E-QB1B 1769-L23E-QB1B and 1769-L23E-QBFC1B 1769-L23E-QBFC1B Controllers Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 I/O Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 1769-L32E 1769-L32E and 1769-L35E 1769-L35E Controllers Status Indicators . . . . . . . . . 183 1768-ENBT 1768-ENBT Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . 185 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Tap Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . 187 1788-ENBT 1788-ENBT EtherNet/IP Daughtercard Status Indicators. . . . . . . . 189 1734-AENT 1734-AENT and 1734-AENTR 1734-AENTR EtherNet/IP POINT I/O Adapter Status Indicators . . . . . . . . . . . . . . . . . . . . . . . 192 1738-AENTR 1738-AENTR ArmorPOINT I/O 2-port EtherNet/IP Adapter Status Indicators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 1794-AENT 1794-AENT EtherNet/IP FLEX I/O Adapter Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 20-COMM-E 20-COMM-E Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . 201 22-COMM-E 22-COMM-E Module Status Indicators . . . . . . . . . . . . . . . . . . . . . . . 205 Appendix B Fiber Cable and LC Connector Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Appendix C EtherNet/IP Network Connections Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 CIP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 TCP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 Multicast Address Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 9 Table of Contents Appendix D EtherNet/IP Network Overview Index 10 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Ethernet Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 Use of the Common Industrial Protocol (CIP) . . . . . . . . . . . . . . 218 Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Subnet Mask. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Manual Configuration on an Ethernet Switch . . . . . . . . . . . . . . . . . . 222 Change Ports on an Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . 222 Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Preface Purpose of This Manual This manual describes how you can use EtherNet/IP modules with your Logix5000 controller and communicate with various devices on the Ethernet network. Who Should Use This Publication You should use this manual if you program applications that use Ethernet with one of these Logix5000 controllers: · CompactLogix controller · ControlLogix controller · FlexLogix controller You should also understand: · networking concepts. · RSLogix 5000 programming software. · RSLinx Classic programming software. 11Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 11 Preface Notes: 12 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Chapter 1 EtherNet/IP Overview Introduction The Logix5000 family of controllers offers several EtherNet/IP communication modules. Topic 1756-ENBT 1756-ENBT Module 15 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, and 1756-EN2TXT 1756-EN2TXT Modules 15 1768-ENBT 1768-ENBT Module 17 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B Packaged Controllers 17 1769-L32E 1769-L32E and 1769-L35E 1769-L35E Controllers 18 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Taps 18 1788-ENBT 1788-ENBT Module 19 1794-AENT 1794-AENT Adapter 20 1734-AENT 1734-AENT and 1734-AENTR 1734-AENTR Adapters 20 1738-AENT 1738-AENT and 1738-AENTR 1738-AENTR Adapters 21 20-COMM-E 20-COMM-E Module 21 22-COMM-E 22-COMM-E Module 22 EtherNet/IP Communication Modules in a Control System 23 Safety I/O in EtherNet/IP Control Systems 24 Bridge Across Networks 27 EtherNet/IP Network Specifications 13Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Page 30 13 Chapter 1 EtherNet/IP Overview Select a module based on the EtherNet/IP functions the application requires. EtherNet/IP Module Functions and Applications Module Works With a Controller to Interfaces With Originate Communication Distributed I/O Modules (Scanner/Bridge) (Adapter) or End Node 1734-AENT 1734-AENT X 1738-AENT 1738-AENT, 1734-AENTR 1734-AENTR X 1756-ENBT 1756-ENBT X X 1756-EN2F 1756-EN2F X X 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, 1756-EN2TXT 1756-EN2TXT X X 1768-ENBT 1768-ENBT X 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B X 1769-L32E 1769-L32E, 1769-L35E 1769-L35E X 1788-ENBT 1788-ENBT X 1794-AENT 1794-AENT X 2x-COMM-E X The EtherNet/IP communication modules: · support messaging, produced/consumed tags, and distributed I/O. · encapsulate messages within standard TCP/UDP/IP protocol. · share a common application layer with ControlNet and DeviceNet network protocols. · interface via RJ45, category 5, unshielded, twisted-pair cable, except for the 1756-EN2F 1756-EN2F fiber cable, which has a fiber connector. · support half/full duplex 10 Mbps or 100 Mbps operation. · require no network scheduling. · require no routing tables. 14 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview 1756-ENBT 1756-ENBT Module Chapter 1 The 1756-ENBT 1756-ENBT module operates either as an interface for a ControlLogix controller to communicate with other devices over an EtherNet/IP network or as an adapter for 1756 I/O modules on an EtherNet/IP network. This module supports: · control of I/O. · communication via produced/consumed tags and MSG instructions. · communication with HMI. · configuration and programming, such as uploading and downloading. · an adapter for 1756 I/O modules. · a web server to provide diagnostic and status information. Additional Resources Resource Description 1756-ENBT 1756-ENBT ControlLogix EtherNet/IP Bridge Module Installation Instructions, publication 1756-IN019 1756-IN019 Details how to install the module and provides technical specifications. 1756-ENBT 1756-ENBT ControlLogix Redundancy System Revision 15 User Manual, publication 1756-UM523 1756-UM523 Details how to use and maintain a ControlLogix redundancy system. 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, and 1756-EN2TXT 1756-EN2TXT Modules 1756-EN2T 1756-EN2T The following modules perform the same functions as the 1756-ENBT 1756-ENBT module but with twice the capacity for demanding applications. · · · · 1756-EN2F 1756-EN2F ControlLogix EtherNet/IP fiber module 1756-EN2T 1756-EN2T ControlLogix EtherNet/IP bridge module 1756-EN2TR 1756-EN2TR ControlLogix EtherNet/IP 2-port module 1756-EN2TXT 1756-EN2TXT ControlLogix-XT EtherNet/IP module All modules support: · · · · · · control of I/O. communication via produced/consumed tags and MSG instructions. communication with HMI. configuration and programming, such as uploading and downloading. an adapter for 1756 I/O modules. USB serial communication, enabling a laptop or workstation to access and program a Logix5000 controller. For more information, see the chapter USB Port Connection. · a web server to provide diagnostic and status information. · rotary switches for quick IP address configuration. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 15 Chapter 1 EtherNet/IP Overview The 1756-EN2F 1756-EN2F module only supports an LC fiber connector to support additional applications. For more information on LC fiber connectors, see Fiber Cable and LC Connector on page 209. The 1756-EN2TR 1756-EN2TR module only supports connection of a ControlLogix system to a linear or device level ring (DLR) network. The 1756-EN2TXT 1756-EN2TXT module only supports use of the module in extreme temperatures. The module is capable of operating in temperatures from 70 158 -25. ° C (-13. ° F). Additional Resources Resource Description 1756-EN2T 1756-EN2T ControlLogix EtherNet/IP Bridge Module Installation Instructions, publication 1756-IN603 1756-IN603 Details how to install the module and provides technical specifications. 1756-EN2TR 1756-EN2TR ControlLogix EtherNet/IP 2-port Module Installation Instructions , publication 1756-IN612 1756-IN612 Details how to install the module and provides technical specifications. 1756-EN2F 1756-EN2F ControlLogix EtherNet/IP Fiber Module Installation Instructions, publication 1756-IN606 1756-IN606 Details how to install the fiber module and provides technical specifications. 1756-EN2TXT 1756-EN2TXT ControlLogix-XT EtherNet/IP Bridge Module Installation Instructions, publication 1756-IN635 1756-IN635 Details how to install the fiber module and provides technical specifications. 16 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview 1768-ENBT 1768-ENBT Module Chapter 1 The 1768-ENBT 1768-ENBT module is an interface that enables a 1768-L43 1768-L43 or 1768-L45 1768-L45 CompactLogix controller to communicate with devices over an EtherNet/IP network. The module supports: · · · · · control of I/O. communication via produced/consumed tags and MSG instructions. communication with HMI. configuration and programming, such as uploading and downloading. a web server to provide diagnostic and status information. Additional Resources Resource Description 1768-ENBT 1768-ENBT CompactLogix EtherNet/IP Communication Module Installation Instructions, publication 1768-IN002 1768-IN002 Details how to install the module and provides technical specifications. 1768 CompactLogix Controllers User Manual, publication 1768-UM001 1768-UM001 Details how to program and maintain the controller. 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B Packaged Controllers 1769-L23E-QB1B 1769-L23E-QB1B The 1769-L23E-QB1B 1769-L23E-QB1B and 1769-L23E-QBFC1B 1769-L23E-QBFC1B CompactLogix packaged controllers have an integrated EtherNet/IP port. Through this port, the controller supports: · · · · · control of I/O. communication via produced/consumed tags and MSG instructions. communication with HMI. configuration and programming, such as uploading and downloading. a web server to provide diagnostic and status information. Additional Resources Resource Description 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B CompactLogix Packaged Controller Installation Instructions, publication 1769-IN082 1769-IN082 Details how to install the controller and provides technical specifications. 1769-L23E-QB1B 1769-L23E-QB1B, 1769-L23E-QBFC1B 1769-L23E-QBFC1B CompactLogix Packaged Controller Quick Start and User Manual, publication IASIMP-QS010 IASIMP-QS010 Details how to program and maintain controllers. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 17 Chapter 1 EtherNet/IP Overview 1769-L32E 1769-L32E and 1769-L35E 1769-L35E Controllers The 1769-L32E 1769-L32E and 1769-L35E 1769-L35E CompactLogix controllers have an integrated EtherNet/IP port. Through this port, the controller supports: · · · · · control of I/O. communication via produced/consumed tags and MSG instructions. communication with HMI. configuration and programming, such as uploading and downloading. a web server to provide diagnostic and status information. Additional Resources Resource Description 1769-L32E 1769-L32E and 1769-L35E 1769-L35E CompactLogix Controller Installation Instructions, publication 1769-IN020 1769-IN020 Details how to install the controller and provides technical specifications. 1769-L32E 1769-L32E and 1769-L35E 1769-L35E CompactLogix System User Manual, publication 1769-UM011 1769-UM011 Details how to program and maintain controllers. 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP Taps 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F and 1783-ETAP2F 1783-ETAP2F taps allow devices that do not support embedded switch technology to connect to linear and DLR networks. Each tap supports: · a device port on the front of the tap to connect to other devices. · two network ports to connect the tap to linear and DLR networks. · the functionality to divide an Ethernet network into segments and direct network traffic more efficiently than using repeating hubs. · the functionality to connect one of the tap ports to a single device segments the network so you can dedicate bandwidth to that device. · multiple simultaneous communication between devices on different ports. 18 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview Chapter 1 The network ports used to connect to linear or DLR networks are different for each tap. The following table describes the types of taps used with each tap: Cat. No. Network Ports Description 1783-ETAP 1783-ETAP 2 copper Two copper network ports connect the tap to copper linear or DLR networks. 1783-ETAP1F 1783-ETAP1F 1 copper One copper network port connects the tap to a copper linear or DLR network, and one fiber-optic network port connects the tap to a fiber-optic linear or DLR network. 1 fiber This tap is commonly used to connect a copper section with a fiber-optic section of the same network. 1783-ETAP2F 1783-ETAP2F 2 fiber Two fiber-optic network ports connect the tap to a fiber-optic linear or DLR network. Additional Resources Resource Description Three-Port EtherNet Tap Installation Instructions, publication 1783-IN007 1783-IN007 Details how to install the tap and provides technical specifications. EtherNet/IP Fiber Tap Installation Instructions, publication 1783-IN008 1783-IN008 Details how to install the tap and provides technical specifications. EtherNet/IP Ring Topology Application Manual, publication ENET-AP005 ENET-AP005 Details how to use the tap in a ring topology. 1788-ENBT 1788-ENBT Module The 1788-ENBT 1788-ENBT module operates as an interface for a FlexLogix and DriveLogix controller to communicate with other devices over an EtherNet/IP network. This module supports: · control of I/O. · communication via produced/consumed tags and MSG instructions. · communication with HMI. · configuration and programming, such as uploading and downloading. · a web server to provide diagnostic and status information. Additional Resources Resource Description 1788-ENBT 1788-ENBT EtherNet/IP Daughtercard Installation Instructions, publication 1788-IN054 1788-IN054 Details how to install the daughtercard and provides technical specifications. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 19 Chapter 1 EtherNet/IP Overview 1794-AENT 1794-AENT Adapter The 1794-AENT 1794-AENT adapter operates as an adapter for FLEX I/O modules on an EtherNet/IP network. This module supports: · control of I/O. · module configuration. · a web server to provide diagnostic and status information. Additional Resources Resource Description 1794-AENT 1794-AENT FLEX I/O EtherNet/IP Adapter Module Installation Instructions, publication 1794-IN082 1794-IN082 Details how to install the adapter and provides technical specifications. 1734-AENT 1734-AENT and 1734-AENTR 1734-AENTR Adapters The 1734-AENT 1734-AENT and 1794-AENTR 1794-AENTR adapters operate as adapters for POINT I/O modules on an EtherNet/IP network. These adapters support: · control of I/O. · module configuration. · linear and device level ring (DLR) topologies on the 1734-AENTR 1734-AENTR adapter only. Additional Resources Resource Description 1734-AENT 1734-AENT POINT I/O Ethernet Adapter Installation Instructions, publication 1734-IN590 1734-IN590 Details how to install the adapter and provides technical specifications. 1734-AENT 1734-AENT POINT I/O Ethernet Adapter User Manual, publication 1734-UM011 1734-UM011 Details how to configure and maintain an installed adapter. 20 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview 1738-AENT 1738-AENT and 1738-AENTR 1738-AENTR Adapters EtherNet I/P The 1738-AENT 1738-AENT and 1738-AENTR 1738-AENTR adapters operate as adapters for ArmorPOINT I/O modules on an EtherNet/IP network. These adapters support: 1738-AENT 1738-AENT · control of I/O. · module configuration. · linear and device level ring (DLR) topologies on the 1738-AENTR 1738-AENTR adapter only. x100 0 2 8 6 I P 4 A x10 0 2 6 x1 D D 2 8 R E S S 4 0 8 6 PWR 4 Chapter 1 Adapter Status Network Activity Network Status PointBus Status System Power Adapter Power TM conformance tested Additional Resources Resource Description ArmorPOINT 2-Port EtherNet/IP Adapter Installation Instructions, publication 1738-IN028 1738-IN028 Details how to install the adapters and provide technical specifications. POINT I/O 2-Port Ethernet Adapter User Manual, publication 1734-UM014 1734-UM014 Details how to configure and maintain an installed adapter. 20-COMM-E 20-COMM-E Module The 20-COMM-E 20-COMM-E module operates as an adapter and provides an internal EtherNet/IP connection for PowerFlex 70, 700, 700S and 700H drives, and other DPI-based host devices. This module supports: · · · · configuration. collection of data. peer-to-peer capability. a web server to provide diagnostic and status information. Additional Resources Resource Description 20-COMM-E 20-COMM-E PowerFlex EtherNet/IP Adapter User Manual, publication 20COMM-UM010 20COMM-UM010 Details how to program and maintain the adapter. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 21 Chapter 1 EtherNet/IP Overview 22-COMM-E 22-COMM-E Module The 22-COMM-E 22-COMM-E module operates as an adapter and provides an internal EtherNet/IP connection for PowerFlex 40 AC drives. This module supports: · · · · user configuration of a module via a process display window. e-mail notification of faults. monitoring of a diagnostics and event queue. direct launching of Drive Explorer or Drive Executive on a workstation to connect online over Ethernet. · multi-drive support of up to five PowerFlex 4 and 40 AC drives to connect to a single node on an EtherNet/IP network, ultimately reducing hardware costs. Additional Resources Resource Description 22-COMM-E 22-COMM-E PowerFlex EtherNet/IP Adapter User Manual, publication 22COMM-UM004 22COMM-UM004 Details how to program and maintain the adapter. 22 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview EtherNet/IP Communication Modules in a Control System Chapter 1 These diagrams show how EtherNet/IP modules can fit into a control system. EtherNet/IP Network Overview 1769-L23Ex Distributed I/O 1756-ENBT 1756-ENBT 1756 I/O modules 1769-L3xE 1768-L4x 1768-ENBT 1768-ENBT Switch PowerFlex drive 1794-AENT 1794-AENT 1794 I/O modules 1734-AENT 1734-AENT 1734 I/O modules Workstation 1783-ETAP 1783-ETAP Workstation 1783-ETAP 1783-ETAP 1783-ETAP 1783-ETAP PanelView terminal 1783-ETAP 1783-ETAP PowerFlex drive 1756-ENBT 1756-ENBT 1756 I/O modules 1734-AENTR 1734-AENTR 1734 I/O modules 1738-AENTR 1738-AENTR 1738 I/O modules In this example: · the controllers can produce and consume tags with each other. · the controllers can initiate MSG instructions that send/receive data or configure devices. · the workstation can upload/download projects to the controllers. · the workstation can configure devices on the EtherNet/IP network. These diagrams show how EtherNet/IP modules can fit into a control system. IMPORTANT Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 For more information on how some EtherNet/IP modules and tapscan be used in a linear or DLR network, see Configure a Supervisor on a Device-level Ring Network on page 57. 23 Chapter 1 EtherNet/IP Overview Installing Communication Modules or Other Devices on the EtherNet/IP Network In addition to using the installation instructions for each Rockwell Automation EtherNet/IP device you install in your control system, you should also consult the EtherNet/IP Media Planning and Installation Manual available from ODVA, the organization that supports network technologies built on the Common Industrial Protocol (CIP). You can obtain EtherNet/IP Media Planning and Installation Manual at the ODVA website, that is, http://www.odva.org. Safety I/O in EtherNet/IP Control Systems Rockwell Automation offers the Guard I/O product line that implements the EtherNet/IP safety protocol. This section provides an overview of the modules use in a safety system. For more information on using Guard I/O modules, see Guard I/O EtherNet/IP Safety Modules user manual, publication 1791ES-UM001 1791ES-UM001. I/O Module Overview The Guard I/O modules implement the CIP-safety protocol extensions over EtherNet/IP networks and provide various features for a safety system. Use the modules to construct a safety-control network system that meets the requirements up to Safety Integrity Level 3 (SIL 3) as defined in IEC 61508, Functional Safety of Electrical, Electronic, and Programmable Electronic Safety-related Systems, and the requirements for Safety Category 4 of the EN 954-1 standard, Safety of machinery - Safety related parts of control systems. Remote I/O communication for safety I/O data are performed through safety connections supporting CIP safety over an EtherNet/IP network, and data processing is performed in the safety controller. The status and fault diagnostics of the I/O modules are monitored by a safety controller through a safety connection using a new or existing EtherNet/IP network. 24 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview Chapter 1 The following is a list of features common to Guard I/O modules: · CIP-safety and EtherNet/IP protocol conformance · Safety inputs ­ Safety devices, such as emergency stop push buttons, gate switches, and safety light curtains, can be connected. ­ Dual-channel mode evaluates consistency between two input signals (channels), which allows use of the module for Safety Category 3 and 4. ­ The time of a logical discrepancy between two channels can be monitored using a discrepancy time setting. ­ An external wiring short-circuit check is possible when inputs are wired in combination with test outputs. ­ Independently adjustable on and off delay is available per channel. · Test outputs ­ Separate test outputs are provided for short circuit detection of a safety input (or inputs). ­ Power (24V) can be supplied to devices, such as safety sensors. ­ Test outputs can be configured as standard outputs. ­ All Guard I/O modules have numerous test outputs, of which some can be used for broken wire detection of a muting lamp. · Safety outputs ­ Dual-channel mode evaluates consistency between two output signals (channels). ­ Safety outputs can be pulse tested to detect field wiring shorts to 24V DC and 0V DC. · I/O status data - In addition to I/O data, the module includes status data for monitoring I/O circuits. · Removable I/O connectors - I/O connectors support mechanical keying. Guard I/O Catalog Numbers See the table for a listing of the types of Guard I/O modules. Types of Guard I/O Modules Catalog Number 1791ES-IB16 1791ES-IB16 1791ES-IB8XOBV4 1791ES-IB8XOBV4 (1) Description Safety input module Safety I/O module with solid state outputs Enclosure Type Rating Safety Inputs Meets IP20 16 8 Test Outputs(1) Safety Outputs 16 8 4 bipolar pairs Solid State Broken wires can be detected on the muting outputs. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 25 Chapter 1 EtherNet/IP Overview CIP Safety in EtherNet/IP Safety Architectures Use Guard I/O modules in EtherNet/IP safety architectures as shown in the figure. The Guard I/O family is a set of I/O modules that when connected to an EtherNet/IP safety network are suitable for applications up to SIL3, as defined in the IEC 61508 standard, and Safety Category 4, as defined in the EN 954-1 standard. Safety Interlocking and Control via CIP Safety RSLogix Software RSView Software Ethernet ControlNet DeviceNet DeviceNet DeviceNet EtherNet/IP ControlNet DeviceNet Standard Communication Safety Communication Safety controllers control the safety outputs. Safety or standard controllers can control the standard outputs. For more information on using Guard I/O modules, see Guard I/O EtherNet/IP Safety Modules user manual, publication 1791ES-UM001 1791ES-UM001. 26 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview Bridge Across Networks Chapter 1 Some EtherNet/IP modules support the ability to bridge or route communication through devices, depending on the capabilities of the platform and communication devices. IMPORTANT The update time of local I/O modules may increase when bridging messages. EtherNet/IP modules do not support the transfer of data to and from I/O modules across two or more segments of any network. You have a bridge when you have a connection between communication devices on two networks. For example, this bridge device has both EtherNet/IP and DeviceNet connections, enabling Device 1 on the EtherNet/IP network to communicate with Device 2 on a DeviceNet network through the bridge. Bridge Device Device 1 EtherNet/IP Switch Bridge DeviceNet Device 2 CIP Message Bridging CIP messages that originateon this network Can bridge to this network EtherNet/IP ControlNet DeviceNet RS-232 RS-232 Serial EtherNet/IP Yes Yes Yes Yes ControlNet Yes Yes Yes Yes RS-232 RS-232 Yes Yes Yes Yes Here, a workstation configures a drive on a DeviceNet network and bridges EtherNet/IP networks to reach the drive. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 27 Chapter 1 EtherNet/IP Overview Drive Configuration and Programming PanelView Station EtherNet/IP Switch Bridge DeviceNet Drive The bridge can be an EtherNet/IP-to-DeviceNet bridging device or a Logix5000 system with an EtherNet/IP communication module and a DeviceNet communication module. The bridge can be a: · ControlLogix chassis with a 1756-ENBT 1756-ENBT, 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, 1756-EN2TXT 1756-EN2TXT, and 1756-DNB 1756-DNB module. The controller is not required. · 1769-L23E-QB1B 1769-L23E-QB1B, 1756-L23E-QBFC1B 1756-L23E-QBFC1B, 1769-L32E 1769-L32E, 1769-L35E 1769-L35E CompactLogix controller with 1769-SDN 1769-SDN module. · 1768-L43 1768-L43 or 1768-L45 1768-L45 CompactLogix controller with 1768-ENBT 1768-ENBT and 1769-SDN 1769-SDN modules. · 1788-EN2DN 1788-EN2DN linking device. Status data can also be transferred from a DeviceNet network through the Logix5000 controller to a RSView32 operator interface. For a CompactLogix or FlexLogix controller, map the data into the DeviceNet I/O image and then use RSLinx OPC software from the workstation to the Logix5000 controller over the EtherNet/IP network. This avoids using the limited bridging resources of the CompactLogix or FlexLogix controller. You cannot bridge EtherNet/IP I/O across networks. I/O modules must be configured in either a local chassis or a remote chassis. You cannot go through a gateway chassis to control I/O even though, in some circumstances, RSLogix 5000 programming software accepts such a configuration in the I/O Configuration folder. 28 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview Chapter 1 DeviceNet Bridge Linking to an EtherNet/IP Network 1 2 3 4 5 Item 1 EtherNet/IP network 2 EtherNet/IP bridge in ControlLogix system 3 DeviceNet bridge in same ControlLogix system 4 DeviceNet network 5 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Description Distributed DeviceNet devices 29 Chapter 1 EtherNet/IP Overview EtherNet/IP Network Specifications These are the EtherNet/IP network connection specifications. EtherNet/IP Network Specifications Catalog Number Connections TCP CIP 1734-AENT 1734-AENT, 1734-AENTR 1734-AENTR 32 20 1738-AENT 1738-AENT, 1738-AENTR 1738-AENTR 32 1756-ENBT 1756-ENBT CIP Unconnected Messages (backplane + Ethernet) Packet Rates (packets/ second)(1) I/O HMI/MSG 32 5000 900 20 32 5000 64 128(2) 64 + 64 1756-EN2F 1756-EN2F 128 256(2) 1756-EN2T 1756-EN2T, 1756-ENT2TR 1756-ENT2TR, 1756-EN2TXT 1756-EN2TXT 128 1756-EWEB 1756-EWEB 1768-ENBT 1768-ENBT(3) SNMP Support (password required) Media Support Twisted Pair Fiber No Yes No 900 No Yes No 5000 900 Yes Yes No 128 + 128 10,000 3200 Yes No Yes 256(2) 128 + 128 10,000 3200 Yes Yes No 64 128(2) 128 + 128 N/A 900 Yes Yes No 32 64(2) 32 + 32 5000 960 Yes Yes No 64 128 1768-EWEB 1768-EWEB 64 128(2) 128 + 128 N/A 960 Yes Yes No 1769-L23Ex 8 32(2) 32 + 32 2000 380 Yes Yes No 1769-L3xE 64 32(2) 32 + 32 4000 760 Yes Yes No 1783-ETAP 1783-ETAP 64 N/A N/A N/A 900 No Yes No 1783-ETAP1F 1783-ETAP1F, 1756-ETAP2F 1756-ETAP2F 64 N/A N/A N/A 900 No Yes Yes 1794-AENT 1794-AENT 64 64 N/A 9500 N/A Yes Yes No 2x-COMM-E 30 16 16 400 50 No Yes No (1) Total packet rate = I/O Produced Tag, max + HMI/MSG, max. Packet rates will vary depending on packet size. For more detailed specifications, see the EDS file for a specific catalog number. (2) CIP connections for these devices can be used for all explicit or all implicit applications. Example: A 1756-ENBT 1756-ENBT has a total of 64 CIP connections and can be used for any combination of connections. (3) The number of TCP and CIP connections supported by the 1768-ENBT 1768-ENBT module depends on the firmware revision you are using. If you are using firmware revision 1.x, the module supports 32 TCP connections and 64 CIP connections. If you are using firmware revision 2.x or later, the module supports 64 TCP connections and 128 CIP connections. 30 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 EtherNet/IP Overview Chapter 1 EtherNet/IP Network Specifications Catalog Number Produced/Consumed Tags Number of Multicast Tags, Max Unicast Available(1) 1734-AENT 1734-AENT, 1734-AENTR 1734-AENTR N/A RSLogix 5000 programming software, version 18 Socket Services Speed Duplex (Half/Full) Duplicate IP Detection (starting revision) No 10/100 Revision 2.x 1734-AENT 1734-AENT Revision 3.x 1734-AENTR 1734-AENTR 1738-AENT 1738-AENT, 1738-AENTR 1738-AENTR N/A RSLogix 5000 programming software, version 18 No 10/100 Revision 2.x 1738-AENT 1738-AENT Revision 3.x 1738-AENTR 1738-AENTR 1756-ENBT 1756-ENBT 32(2) RSLogix 5000 programming software, version 16 No 10/100 Revision 3.3 1756-EN2F 1756-EN2F 32(2) RSLogix 5000 programming software, version 16 No 10/100 Revision 1.x 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, 1756-EN2TXT 1756-EN2TXT 32(2) RSLogix 5000 programming software, version 16 1756-EN2T 1756-EN2T No 10/100 Revision 1.x RSLogix 5000 programming software, version 17.01 1756-EN2TR 1756-EN2TR 1756-EWEB 1756-EWEB N/A N/A Yes 10/100 Revision 2.2 1768-ENBT 1768-ENBT 32(2) RSLogix 5000 programming software, version 16 No 10/100 Revision 1.x 1768-EWEB 1768-EWEB N/A N/A Yes 10/100 Revision 1.x 1769-L23Ex 32(2) RSLogix 5000 programming software, version 17 No 10/100 Revision 16 1769-L3xE 32(2) RSLogix 5000 programming software, version 16 No 10/100 Revision 15 1783-ETAP 1783-ETAP N/A N/A No 10/100 Revision 1.x 1783-ETAP1F 1783-ETAP1F, 1783-ETAP2F 1783-ETAP2F N/A N/A No 10/100 Revision 2.x 1794-AENT 1794-AENT N/A N/A No 10/100 Revision 3.x 2x-COMM-E N/A N/A No 10/100 Revision 1.1 (1) These are the maximum number of I/O CIP connections. (2) Each controller can send a maximum of 32 produced tags to one single consuming controller. If these same tags are sent to multiple consumers, the maximum number is 31. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 31 Chapter 1 EtherNet/IP Overview IMPORTANT Non-CIP communication requires 1756-EWEB 1756-EWEB, 1768-EWEB 1768-EWEB or MicroLogix 1400 embedded web server sockets. For more information on the 1756-EWEB 1756-EWEB or 1768-EWEB 1768-EWEB modules, see the EtherNet/IP Web Server User Manual, publication ENET-UM527 ENET-UM527. For more information on the enhanced MicroLogix 1400 controllers, see the MicroLogix 1400 Embedded Web Server User Manual, publication 1766-UM002 1766-UM002 32 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Chapter 2 Configure a Workstation to Operate on an EtherNet/IP Network Introduction This chapter describes how to configure a workstation to operate on an EtherNet/IP network. You need to load an Ethernet communication driver for all Rockwell Software applications to communicate with devices on an EtherNet/IP network. A workstation needs this driver to: · upload and download controller projects over the EtherNet/IP network via RSLogix 5000 programming software. · configure EtherNet/IP network parameters for devices on the network via RSNetWorx for EtherNet/IP software. · collect controller data for PanelView terminals and RSView applications. You can choose from any of three Ethernet drives: · AB_ETHIP · AB_ETH · TCP We recommend that you use the AB_ETHIP driver. Before loading a communication driver, make sure: · the Ethernet communication card is already installed in the workstation. · the IP address and other network parameters are correctly configured for the workstation. · the workstation is properly connected to the EtherNet/IP network. See the documentation for the appropriate Ethernet communication module for information on installing and configuring the module. 33Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 33 Chapter 2 Configure a Workstation to Operate on an EtherNet/IP Network Configure the Ethernet Communication Driver in RSLinx Software To configure the Ethernet communication driver, perform this procedure. 1. In RSLinx software, from the Communications pull-down menu, choose Configure Drivers. The Configure Drivers dialog box appears. 2. From Available Driver Types pull-down menu, choose EtherNet/IP Driver or Ethernet devices and click Add New. The Add New RSLinx Driver dialog box appears. 3. Type a name for the new driver and click OK. 34 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Workstation to Operate on an EtherNet/IP Network Chapter 2 The Configure driver dialog box appears. 4. Select Browse Local Subnet. 5. Click Apply. 6. Click OK. This new driver is now available. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 35 Chapter 2 Configure a Workstation to Operate on an EtherNet/IP Network Notes: 36 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Chapter 3 Configure Stratix Switches Introduction This chapter describes how you can use a Stratix switch. Topic Page Set Up the Hardware 38 Select a Switch 37 Switch Features 38 Additional Resources 39 Stratix switches provide a rugged, easy-to-use, secure switching infrastructure for harsh environments. You can connect these switches to network devices such as servers, routers, and other switches. In industrial environments, you can connect any Ethernet-enabled industrial communication devices including programmable log controllers (PLC's), human-machine interfaces (HMI's), drives, sensors, and I/O. Select a Switch Select the switch depending on the application and environment. If your application Select · Integrates enterprise and manufacturing Stratix 8000 modular, managed switch environments · Requires I/O and Produced/Consumed communication · Requires diagnostics data · Requires security options · Integrates plant floor devices Stratix 6000 fixed, managed switch · Requires I/O and Produced/Consumed communication · Require diagnostics data · Requires security options · Requires easy set-up and direct relacement of switches Stratix 2000 unmanaged switch · Meets IP20 or IP67 standards 37Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 37 Chapter 3 Configure Stratix Switches Set Up the Hardware In this example, multiple Ethernet-enabled devices are connected via a Stratix switch. EtherNet/IP-enabled Devices Connected Via a Stratix Switch 3 4 1 2 5 Device 1 HMI device 2 Drive 3 Stratix switch 4 Logix chassis 5 Switch Features Description Distributed I/O The features available vary according to the switch you select. Stratix Features Switch Stratix 8000 Configuration Features · IT-friendly configuration tool ­ Cisco Command Line Interface, Cisco Network Assistant, Device Manager · Express setup ­ quick start-up feature Monitoring Features · RSLogix 5000 pre-defined tags allow easy access for HMI development · Sample face plates available for View applications Security Features · Supports all security features available in the Cisco Catalyst line of switches including: - 802.1x industry standard authentication · "Smartport" ­ easy switch port optimization feature · Web enabled configuration using embedded web pages - ACL (Access Control List) · AOP configuration stored as part of project in RSLogix 5000 38 - MAC ID device authentication Maintenance Features · Removable CompactFlash card holds OS and configuration of the switch which can be easily transferred to a new one · Standard DHCP Option 82 support enables fixed IP address assignment to switch ports - Port control Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure Stratix Switches Chapter 3 Stratix Features Switch Stratix 6000 Configuration Features Monitoring Features · Real-time diagnostics available in embedded web pages · Default IP address allows quick start up · Web enabled configuration using embedded web pages · AOP configuration stored as part of project in RSLogix 5000 · RSLogix 5000 pre-defined tags allow easy access for HMI development - Traffic level monitor w/ alarms · Sample face plates available for View applications Stratix 2000 No parameters to configure No diagnostics are for unmanaged switches available in unmanaged switches Additional Resources Security Features · Supports all security features available in the Cisco Catalyst line of switches including: - Port control - MAC ID device authentication - Switch access username/password authentication No security features available in unmanaged switches Maintenance Features · Parameter settings held in Logix project and are automatically downloaded after switch replacement (IP address must be set prior to download) · DHCP per port ensures connected devices are assigned the right addresses after replacement Direct replacement - no set-up or configuration required These documents contain additional information concerning related Rockwell Automation products. Resource Stratix 8000 and 8300 Ethernet Managed Switches Installation Instructions, publication 1783-IN005 1783-IN005 Describes how to install and configure the switch. Stratix 6000 Ethernet Managed Switches Installation Instructions, publication 1783-IN004 1783-IN004 Describes how to install and configure the switch. Stratix 2000 Ethernet Unmanaged Switch Installation Instructions, publication 1783-IN001 1783-IN001 Describes how to install and configure the switch. Stratix 8000 Ethernet Managed Switches Hardware User Manual, publication 1783-UM002 1783-UM002 Provides detailed information on installing and using your switches. Stratix 8000 and 8300 Ethernet Managed Switches Sofware user Manual, publication 1783-UM003 1783-UM003 Provides detailed information on configuring and managing your switches. Stratix 6000 Ethernet Managed Switch User Manual, publication 1783-UM001 1783-UM001 Provides detailed information on configuring and managing your switches. Device Manager online help (provided with the switch) Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Description Provides context-sensitive information on configuring and using the switch, including system messages. 39 Chapter 3 Configure Stratix Switches Notes: 40 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network Introduction This chapter describes how to configure an EtherNet/IP communication module to operate on an EtherNet/IP network. Topic Page Determine Network Parameters 41 Set the IP Network Address 43 Assign Network Parameters via the BOOTP/DHCP Utility 45 Other Methods to Assign Network Parameters 47 Duplicate IP Address Detection 51 IP Address Swapping 53 DNS Addressing 54 Use EtherNet/IP Modules in a Logix5000 Controller Application 55 When you first install a Rockwell Automation EtherNet/IP module, the module is BOOTP/DHCP enabled. Determine Network Parameters To operate an EtherNet/IP network, you must define these parameters. EtherNet/IP Network Parameters EtherNet/IP Network Parameter Description IP address The IP address uniquely identifies the module. The IP address is in the form xxx.xxx.xxx.xxx where each xxx is a number from 0. . .255. However, there are some reserved values that you cannot use as the first octet in the address. For example, you cannot use: · 001.xxx.xxx.xxx · 127.xxx.xxx.xxx · 223 to 255.xxx.xxx.xxx Subnet mask Subnet addressing is an extension of the IP address scheme that allows a site to use a single network ID for multiple physical networks. Routing outside of the site continues by dividing the IP address into a net ID and a host ID via the class. Inside a site, the subnet mask is used to redivide the IP address into a custom network ID portion and host ID portion. This field is set to 0.0.0.0 by default. If you change the subnet mask of an already-configured module, you must cycle power to the module for the change to take effect. 41Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 41 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network EtherNet/IP Network Parameters EtherNet/IP Network Parameter Description Gateway A gateway connects individual physical networks into a system of networks. When a node needs to communicate with a node on another network, a gateway transfers the data between the two networks. This field is set to 0.0.0.0 by default. If you use DNS addressing, or reference the module via host name in MSG instructions, define these parameters. EtherNet/IP Network Parameters for DNS Addressing EtherNet/IP Network Parameter Description Host name A host name is part of a text address that identifies the host for a module. The full text address of a module is host_name.domain_name. Domain name A domain name is part of a text address that identifies the domain in which the module resides. The full text address of a module is host_name.domain_name. The domain name has a 48-character limit. If you specify a DNS server, you must enter a domain name. Also, if you send email from the module, some mail relay servers require a domain name during the initial handshake of the SMTP session. Primary DNS server address Secondary DNS server address This identifies any DNS servers used in the network. You must have a DNS server configured if you specified a domain name or a host name in the module's configuration. The DNS server converts the domain name or host name to an IP address that can be used by the network. For more information on DNS addressing, see page 54. Check with your Ethernet network administrator to determine if you need to specify these parameters. 42 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Set the IP Network Address Chapter 4 EtherNet/IP modules ship with the IP address configuration switches set to 999 and DHCP enabled. You can set the network Internet Protocol (IP) address by: · using the switches available on some modules. IMPORTANT The switches on 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F and 1783-ETAP2F 1783-ETAP2F taps are used somewhat differently than other EtherNet/IP modules. For more information on how to use switches on the taps, see either of the following: · EtherNet/IP Tap Installation Instructions, pubication 1783-IN007 1783-IN007 · EtherNet/IP Fiber Tap Installation Instructions, publication 1783-IN008 1783-IN008 · using a Bootstrap Protocol (BOOTP)/Dynamic Host Configuration Protocol (DHCP) server, such as the Rockwell Automation BOOTP-DHCP server utility. · using RSLinx software or RSLogix 5000 programming software. IMPORTANT The adapter reads the configuration switches only when you cycle power to determine if the switches are set to a valid number. Valid settings range from 001.255, with some exceptions. There are some reserved values that you cannot use as the first octet in the address. For example, you cannot use: · 001.xxx.xxx.xxx · 127.xxx.xxx.xxx · 223 to 255.xxx.xxx.xxx To restore the factory default settings on the module, set the switches to 888. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 43 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network The graphic below shows how your module's IP address is set. Module power-up No No Is DHCP or BOOTP enabled? Adapter uses IP address stored in nonvolatile memory Module IP address between 001-254? Yes Yes Module requests address from DHCP/BOOTP server Module using a valid IP address1 1 - If necessary, you can set the module switches to 888 to restore the IP address to the factory default value of 999. In this case, cycle power to the module after restoring the factory default settings and begin the flowchart process again. For more detailed information, see the table below. IP Network Address Configuration Switch Settings If the Switches are set to a valid number Then · The adapter's IP address will be 192.168.1.xxx (where xxx represents the number set on the switches). · The adapter's subnet mask will be 255.255.255.0, with the gateway address set to 0.0.0.0. · The adapter will not have a host name assigned, or use any Domain Name System when using the thumbwheel settings. Switches are set to an invalid number · The module checks to see if DHCP or BOOTP is enabled. If either is, the module requests an IP address from a DHCP/BOOTP server. The DHCP/BOOTP server will also assign other Transport Control Protocol (TCP) parameters. · If you have used software to preconfigure an IP address, and DHCP or BOOTP is disabled, the module will use the configured IP address. DHCP is not enabled · The adapter will use the IP address and any otherTCP configurable parameters stored in nonvolatile memory. Important: The factory default switch setting is 999, and DHCP is enabled. 44 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Assign Network Parameters via the BOOTP/DHCP Utility Chapter 4 By default, the EtherNet/IP module is BOOTP enabled. The BOOTP/DHCP utility is a standalone program that is located in the: · BOOTP-DHCP Server folder accessed from the Start menu. · Tools directory on the RSLogix 5000 installation CD. IMPORTANT Before you start the BOOTP/DHCP utility, make sure you have the hardware (MAC) address of the module. The hardware address is on a sticker on the side of the EtherNet/IP module. The hardware address in a format similar to: 00-0b-db-14-55-35. This utility recognizes BOOTP-enabled devices and provides an interface to configure a static IP address for each device. To assign network parameters via the BOOTP/DHCP utility, perform this procedure. 1. Start the BOOTP/DHCP software. 2. Select Tool Network Settings. 3. If appropriate for the network, enter the subnet mask, gateway address, primary/secondary server addresses, and domain name. 4. Click OK. The Request History panel displays the hardware addresses of modules issuing BOOTP requests. 5. Double-click the hardware (MAC) address of the module to be configured. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 45 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network The hardware address is on a sticker on the side of the EtherNet/IP module. The format of the hardware address resembles 00-0b-db-14-55-35. The New Entry window appears with the module's Ethernet Address (MAC). 6. Enter the IP address, host name, and a module description. 7. Click OK. 8. To permanently assign this configuration to the module, highlight the module and click the Disable BOOTP/DHCP button. When power is recycled, the module uses the assigned configuration and does not issue a BOOTP request. If you do not select the Disable BOOTP/DHCP button, on a power cycle, the host controller clears the current IP configuration and will again begin sending BOOTP requests. 46 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Other Methods to Assign Network Parameters Chapter 4 There are other methods to assign network parameters. Assignment of Network Parameters If Use this method for assigning network parameter RSLinx software · A BOOTP server is not available Page 48 · The EtherNet/IP module is connected to another NetLinx network The RSLogix 5000 project is online with the controller that RSLogix 5000 programming software communicates to or through the EtherNet/IP module 50 DHCP is enabled (not BOOTP) for the EtherNet/IP module DHCP software 51 You need to cycle power to your device for some reason Thumbwheel switches 43 These factors might affect your choice of method: · Network isolation from or integration into the plant/enterprise network · Network size For large networks, even isolated networks, it might be more convenient and safer to use a BOOTP/DHCP server rather than RSLogix 5000 or RSLinx software. The BOOTP/DHCP server also limits the possibility of assigning duplicate IP addresses. · Company policies and procedures dealing with plant floor network installation and maintenance · Level of involvement by IT personnel in plant floor network installation and maintenance · Type of training offered to control engineers and maintenance personnel If you use the Rockwell Automation BOOTP or DHCP server in an uplinked subnet where an enterprise DHCP server exists, a module may get an address from the enterprise server before the Rockwell Automation utility even sees the module. You might have to disconnect from the uplink to set the address and configure the module to retain its static address before reconnecting to the uplink. This is not a problem if you have node names configured in the module and leave DHCP enabled. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 47 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network Configure the Module with RSLinx Software To use RSLinx software to configure the EtherNet/IP module, perform this procedure. 1. Make sure the module is installed and started. 2. In RSLinx software, from the Communications pull-down menu, choose RSWho. The RSWho dialog box appears. 3. Navigate in RSWho to the Ethernet network. 4. Right-click the EtherNet/IP module and select Module Configuration. The Module Configuration dialog box appears. 48 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Chapter 4 5. Click the Port Configuration tab. 6. For Network Configuration Type, select Static to permanently assign this configuration to the port. IMPORTANT If you select Dynamic, on a power cycle, the controller clears the current IP configuration and resumes sending BOOTP requests. a. b. c. d. In the IP Address field, type the IP address. In the Network Mask field, type the network mask address. In the Gateway Address field, type the gateway address. In the Primary Name Server field, type the name of the primary server. e. In the Secondary Name Server field, type the name of the secondary server. f. In the Domain Name field, type the domain name. g. In the Host Name field, type the host name. 7. Configure the port settings. To Then Use the default port speed and duplex settings Leave checked the Auto-negotiate port speed and duplex check box. Important: The default port speed is 100, and the default duplex setting is Full. Manually configure your port's speed and duplex settings. a.Uncheck the Auto-negotiate port speed and duplex check box. b. From the Current Port Speed pull-down menu, select a port speed. c. From the Current Duplex pull-down menu, choose Half Duplex. 8. Click OK. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 49 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network Configure Your Module with RSLogix 5000 Software To use RSLogix 5000 programming software to configure the EtherNet/IP module, perform this procedure. 1. Make sure the module is installed, started and connected to the controller via a serial, or other network, connection. 2. In the Controller Organizer of RSLogix 5000 programming software, right-click the EtherNet/IP module and choose Properties. The Module Properties dialog box appears. The example screen below shows the Module Properties dialog box for the 1756-ENBT 1756-ENBT module. 3. Click the Port Configuration tab. 4. In the IP Address field, type the IP address. a. In the other fields, type the other network parameters, if needed. IMPORTANT The fields that appear vary from one EtherNet/IP module to another. 5. Click Apply. 6. Click OK. 50 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Chapter 4 Use DHCP Software to Set the IP Address Dynamic Host Configuration Protocol (DHCP) software automatically assigns IP addresses to client stations logging onto a TCP/IP network. DHCP is based on BOOTP and maintains some backward compatibility. The main difference is that BOOTP allows for manual configuration (static), while DHCP allows for both static and dynamic allocation of network addresses and configurations to newly attached modules. Be cautious when using DHCP software to configure a module. A BOOTP client, such as the EtherNet/IP modules, can boot from a DHCP server only if the DHCP server is specifically written to also handle BOOTP queries. This is specific to the DHCP software package used. Consult your system administrator to see if a DHCP package supports BOOTP commands and manual IP allocation. ATTENTION The EtherNet/IP module must be assigned a fixed network address. The IP address of this module must not be dynamically provided. Failure to observe this precaution may result in unintended machine motion or loss of process control. Duplicate IP Address Detection Some EtherNet/IP modules (and their future revisions) support duplicate IP address detection. Cat. No. 1734-AENT 1734-AENT, 1734-AENTR 1734-AENTR 2.1 and later 1738-AENT 1738-AENT, 1738-AENTR 1738-AENTR 3.002 and later 1756-ENBT 1756-ENBT 3.2 and later 1756-EN2F 1756-EN2F 1.x and later 1756-EN2T 1756-EN2T 1.x and later 1756-EN2TR 1756-EN2TR 1.x and later 1756-EN2TRXT 1756-EN2TRXT 1.x and later 1768-ENBT 1768-ENBT 1.x and later 1769-L2x 17.01 and later 1769-L32E 1769-L32E and 1769-L35E 1769-L35E 15.01 and later 1783-ETAP 1783-ETAP 1.x and later 1783-ETAP1F 1783-ETAP1F, 1783-ETAP2F 1783-ETAP2F Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Firmware Revision 2.x and later 51 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network Cat. No. Firmware Revision 1788-ENBT 1788-ENBT 2.1 and later 1794-AENT 1794-AENT Series A - 3.x and later Series B - 4.1 and later 2x-COMM-E 1.1 and later When you change the IP address or connect one of these modules to an EtherNet/IP network, the module checks to make sure that the IP address assigned to this module does not match the address of any other network device. If the module determines that another device on the network with a matching IP address, the EtherNet/IP port of the module goes into conflict mode, where the module's: · OK status indicator blinks red. · Network (NET) status indicator is solid red. · front display indicates the conflict (1756-ENBT 1756-ENBT, 1756-EN2F 1756-EN2F, 1756-EN2T 1756-EN2T, 1756-EN2TR 1756-EN2TR, and 1756-EN2TXT 1756-EN2TXT). The display scrolls:OK Duplicate IP For example: OK 10.88.60.196 Duplicate IP - 00:00:BC:02:34:B4 To resolve this conflict, use the instructions in this chapter to change the IP address of the module. Then cycle power to the module or reset the modules, such as disconnecting and then reconnecting the EtherNet/IP cable cable. Two modules could possibly detect a conflict simultaneously. If this occurs, perform this procedure. 1. Remove the module with the incorrect IP address or correct its conflict. 2. Cycle power to the second module or disconnect its EtherNet/IP cable 3. Reconnect the cable. 52 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Chapter 4 Detection of Duplicate IP Addresses Devices in conflict over an IP address behave differently depending on whether connections have been established to either of the modules and whether both modules support duplicate IP address detection. Device Conflict Over Duplicate IP Addresses If Then Both modules support duplicate IP address detection The first started module uses and retains its IP address. Both modules support duplicate IP address detection and are started at roughly the same time They surrender the IP address and enter conflict mode One module supports duplicate IP address detection and a second module does not The second module generally keeps its IP address, regardless of which module first obtains the IP address. The other module will detect a conflict, give up the IP address and enter conflict mode. The module that supports duplicate IP address detection will detect the conflict and give up the IP address. IP Address Swapping This EtherNet/IP modules supports IP address swapping in ControlLogix redundancy systems: · 1756-ENBT 1756-ENBT, firmware revision 3.1 and later · 1756-EN2T 1756-EN2T, firmware revision 2.003 and later · 1756-EN2TR 1756-EN2TR, firmware revision 2.x and later · 1756-EN2TXT 1756-EN2TXT, firmware revision 2.1 and later During a switchover in ControlLogix redundancy systems, these module swaps its IP address with its partner modules in the other redundant chassis. For more information about IP address swapping, see the ControlLogix Redundancy User Manual, publication 1756-UM523 1756-UM523. When using publication 1756-UM23 1756-UM23, be aware that neither the 1756-EN2TR 1756-EN2TR module nor the 1756-EN2TXT 1756-EN2TXT module supports redundancy. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 53 Chapter 4 Configure an EtherNet/IP Module to Operate on the Network DNS Addressing To further qualify a module's address, use DNS addressing to specify a host name for a module, which also includes specifying a domain name and DNS servers. DNS addressing makes it possible to set up similar network structures and IP address sequences under different domains. DNS addressing is only necessary if you refer to the module by host name, such as in path descriptions in MSG instructions. To use DNS addressing, perform this procedure. 1. Assign a host name to the module. A network administrator should be able to assign a host name. Valid host names should be IEC-1131-3 IEC-1131-3 compliant. 2. Configure the module's parameters. 3. In addition to the IP address, subnet mask, and gateway address, configure a host name for the module, domain name, and primary/secondary DNS server addresses. In the DNS server, the host name must match the IP address of the module. IMPORTANT Make sure the DNS enable bit is set. If you configure your module using RSLinx software, version 2.41, the enable bit is cleared and DNS addressing will not work. If you configure your module using the Port Configuration tab in RSLogix 5000 programming software, the enable bit is set, so DNS addressing should work. 54 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure an EtherNet/IP Module to Operate on the Network Chapter 4 4. In RSLogix 5000 programming software, add the module to the I/O configuration tree. See Add a Moduleon page 79. IMPORTANT IMPORTANT Use EtherNet/IP Modules in a Logix5000 Controller Application If a child module resides in the same domain as its parent module, just enter the host name. If the child module's domain differs from that of its parent module, enter the host name and the domain name (host.domain) You can also use DNS addressing in a module profile in the I/O controller tree or in a message path. If the destination module's domain name differs from that of the source module, use a fully-qualified DNS name (hostname.domainname). For example, to send a message from ENBT1.location1.companyA to ENTB1.location2.companyA, the host names match, but the domains differ. Without the entry of a fully qualified DNS name, the module adds the default domain name to the specified host name. After installing an EtherNet/IP module and setting its IP address, add the module to the Controller Organizer in an RSLogix 5000 project. This addition establishes I/O control. You must download that project to the host controller before operation can begin. When the controller begins operation, it establishes a connection with the EtherNet/IP module. The module's configuration determines its behavior. For more information on configuring and placing a workstation (for developing an RSLogix 5000 project) on an EtherNet/IP network, see Configure a Workstation to Operate on an EtherNet/IP Network on page 33. For information on controlling I/O, see Control I/O on page 77. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 55 Chapter 4 56 Configure an EtherNet/IP Module to Operate on the Network Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Chapter 5 Configure a Supervisor on a Device-level Ring Network Introduction A Device-level Ring (DLR) network is a single-fault tolerant ring network intended for the interconnection of automation devices. Topic Page Rockwell Automation Products with Embedded Switch Technology 58 Construct the Physical Network 63 Configure Supervisor Nodes on a DLR Network 64 Complete the Physical Connections of the Network 74 Verify Supervisor Configuration 75 Troubleshoot DLR Network Issues 75 The ring topology provides: · · · · media redundancy. fast network fault detection and reconfiguration. the resiliency of a single-fault tolerant network. easy implementation without any additional hardware requirements. IMPORTANT This section describes how to configure a ring supervisor on a DLR network. This section does not fully describe a DLR network itself. See the EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005 ENET-AP005, for information on: · a DLR overview. · how to fully configure a DLR network. · how to monitor a DLR network. · how to troubleshoot a DLR network. 57Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 57 Chapter 5 Configure a Supervisor on a Device-level Ring Network Rockwell Automation Products with Embedded Switch Technology The current Rockwell Automation products that you can use to construct a DLR or linear network include: · 1756-EN2TR 1756-EN2TR ControlLogix EtherNet/IP 2-port module - Allows ControlLogix controllers, I/O modules and communication modules to connect to the DLR or linear network. · 1783 EtherNet/IP taps - Allow devices that do not support embedded switch technology to connect to a linear or a DLR network. Each tap uses a device port on the front of the tap to connect to devices that do not support the embedded switch technology to connect to linear or DLR networks. The taps have two network ports to connect to linear or DLR networks. The network ports used to connect to linear or DLR networks are different for each type of tap. The following table describes the types of taps used with each tap: Cat. No. Network Ports Description 1783-ETAP 1783-ETAP 2 copper Two copper network ports connect the tap to copper linear or DLR networks. 1783-ETAP1F 1783-ETAP1F 1 copper One copper network port connects the tap to a copper linear or DLR network, and one fiber-optic network port connects the tap to a fiber-optic linear or DLR network. 1 fiber This tap is commonly used to connect a copper section with a fiber-optic section of the same network. 1783-ETAP2F 1783-ETAP2F 2 fiber Two fiber-optic network ports connect the tap to a fiber-optic linear or DLR network. The primary advantages of using fiber-optic networks is the availability of increased distances between network nodes and greater noise immunity on the network. · 1734-AENTR 1734-AENTR, POINT I/O 2-port Ethernet adapter - Allows POINT I/O modules to connect to the DLR or linear network. · 1738-AENTR 1738-AENTR, ArmorPOINT 2-port Ethernet adapter - Allows ArmorPOINT I/O modules to connect to the DLR or linear network. 58 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 · Any 1732E 1732E ArmorBlock I/O EtherNet/IP modules with a catalog number ending in R, including: ­ 1732E-IB16M12R 1732E-IB16M12R ­ 1732E-OB16M12R 1732E-OB16M12R ­ 1732E-16CFGM12R 1732E-16CFGM12R ­ 1732E-IB16M12DR 1732E-IB16M12DR ­ 1732E-OB16M12DR 1732E-OB16M12DR ­ 1732E-8X8M12DR 1732E-8X8M12DR ­ 1732E-IB16M12SOEDR 1732E-IB16M12SOEDR Features Common to Products with Embedded Switch Technology The products described on page 58 have certain features in common. · Each product supports the management of network traffic to ensure timely delivery of critical data, that is, QoS and IGMP protocols are supported. · Each product is designed according to the open ODVA specification for EtherNet/IP. Because of this design, third-party products may be designed, according the ODVA specification, to operate on a DLR or linear network. To see the ODVA specification, go to: http://www.odva.org/ · For DLR networks, ring recovery time is less than 3ms for a 50-node ring. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 59 Chapter 5 Configure a Supervisor on a Device-level Ring Network · Each product supports a 1588 transparent clock for CIP motion and CIP Sync applications. CIP Sync technology can be used in Logix control systems to synchronize clocks across a system operating on the EtherNet/IP network. This technology supports highly distributed applications that require such functions as timestamping, sequence of events recording, distributed motion control, and increased control coordination. For example, with CIP Sync technology, a single ControlLogix controller can establish a master time and then, using ControlLogix Ethernet modules, propogate that time to all necessary devices on the network. For more information on how to use CIP Synch technology, see the Integrated Architecture and CIP Sync Configuration Application Solution, publication IA-AP003 IA-AP003. · Each of the products described on page 58 has 2 ports to connect to a linear or DLR network in a single subnet. You cannot use these ports as two Network Interface Cards (NICs) connected to two different subnets. 60 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 Example Device-level Ring Topology 1783-ETAP 1783-ETAP 1756-EN2TR 1756-EN2TR 1783-ETAP 1783-ETAP 1783-ETAP 1783-ETAP 1756-EN2TR 1756-EN2TR 1734-AENTR 1734-AENTR 1738-AENTR 1738-AENTR Supervisor Node A DLR network requires at least one node to be configured as ring supervisor. Currently, two Rockwell Automation products support the ring supervisor functionality. · 1756-EN2TR 1756-EN2TR, ControlLogix EtherNet/IP 2-port module · 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F EtherNet/IP taps IMPORTANT Out of the box, the supervisor-capable devices have their supervisor function disabled so they are ready to participate in either a linear/star network topology, or as a ring node on an existing DLR network. In a DLR network, you must configure at least one of the supervisor-capable devices as the ring supervisor before physically connecting the ring. If not, the DLR network will not work. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 61 Chapter 5 Configure a Supervisor on a Device-level Ring Network Active Ring Supervisor When multiple nodes are enabled as supervisor, the node with the numerically highest precedence value becomes the active ring supervisor; the other nodes automatically become back-up supervisors. The ring supervisor provides two main functions: · Manage traffic on the DLR network · Collect diagnostic information for the network Back-up Supervisor Node At any point in time, there will only be one active supervisor on a DLR network. However, we recommend that you can configure at least one other supervisor-capable node to act as back-up supervisor nodes. During normal operation, a back-up supervisor behaves like a ring node. If the active supervisor node faults, the back-up supervisor with the next numerically highest precedence becomes the active supervisor. If multiple supervisors are configured with the same precedence value (the factory default value for all supervisor-capable devices is 0), the node with the numerically highest MAC address becomes the active supervisor. IMPORTANT While a back-up supervisor is not required on a DLR network, we recommend that you configure at least one ring supervisors for your ring network. We recommend that you: · configure at least one back-up supervisor. · configure your desired active ring supervisor with a numerically higher precedence value as compared to the back-up supervisors. · keep track of your network's supervisor-precedence values for all supervisor-enabled nodes. For more information about how to configure a supervisor, see Configure Supervisor Nodes on a DLR Network on page 64. 62 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 Ring Node A ring node is any node that operates on the network to process data that is transmitted over the network or to pass on the data to the next node on the network. When a fault occurs on the DLR network, these reconfigure themselves and relearn the network topology. Additionally, ring nodes can report fault locations to the active ring supervisor. Construct the Physical Network The first thing you must do to create a new DLR network is physically connect all necessary devices to the network. However, you should leave at least one connection unmade, that is, temporarily omit the physical connection between two nodes on the ring, as the factory default settings of DLR devices are set to operate in linear/star mode or as ring nodes on existing DLR networks. The figure below shows an example of a new DLR network with one physical connection left open. Example Device-level Ring Topology with One Connection Left Unmade Last physical connection is not made. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 63 Chapter 5 Configure a Supervisor on a Device-level Ring Network Configure Supervisor Nodes on a DLR Network After you have installed all devices on the DLR network, you must configure the supervisor node. Ring nodes do not require any configuration. Before you can complete a DLR network, that is, configure all devices on the network and make all physical connections, you must configure and enable a ring supervisor in: · RSLogix 5000 programming software or · RSLinx Classic communication software This section shows how to use RSLogix 5000 programming software, beginning on page 65, and RSLinx Classic communication software, beginning on page 71, to configure and enable a ring supervisor. When using either software, the 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F taps have additional configuration parameters. IMPORTANT In addition to using the software listed above to configure and enable a ring supervisor, you can use the DIP switches on your tap to automatically configure the tap to be a ring supervisor. For more information on how to use the DIP switches on your EtherNet/IP tap, see the EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005 ENET-AP005. 64 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 Configure a Ring Supervisor in RSLogix 5000 Programming Software To configure the 1756-EN2TR 1756-EN2TR module or the 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F or 1783-ETAP2F 1783-ETAP2F taps as a ring supervisor, use the device's Add-on Profile (AOP) in RSLogix 5000 programming software, version 17.01. To download AOP's, go to: IMPORTANT Depending on the firmware revision of your product, you must use a specific AOP version. Cat. No. Firmware Revision Required Add-on Profile Revision 1756-EN2TR 1756-EN2TR 2.1(1) 1.x or later 3.x or later 2.x or later 1.1(2) 1.x or later 2.x or later 2.x or later 2.x or later 2.x or later 1783-ETAP 1783-ETAP 1783-ETAP1F 1783-ETAP1F 1783-ETAP2F 1783-ETAP2F (1) You can use the ControlFLASH Firmware Upgrade software to upgrade a 1756-EN2TR 1756-EN2TR module from firmware revision 2.1 to 3.x or later. (2) You can use the ControlFLASH Firmware Upgrade software to upgrade a 1783-ETAP 1783-ETAP tap from firmware revision 1.1 to 2.x or later. To download new firmware, go to: If you upgrade the firmware revision on your module or tap, you must use the required AOP revision listed above for that revision. For example, if you upgrade your 1756-EN2TR 1756-EN2TR module to firmware revision 3.x or later, you must use AOP revision 2.x or later in your RSLogix 5000 programming software. Additionally, if you upgrade the firmware revision on your module or tap, you must also use the required RSLinx communication software for that firmware revision. For more information on which RSLinx communication software version is required for each firmware revision, see page 71. For both the 1756-EN2TR 1756-EN2TR module and 1783-ETAP 1783-ETAP tap, make sure that the Major Revision configured on the General tab of the device's RSLogix 5000 programming software configuration matches the major revision of the physical module. If the device configuration on the General tab does not match the physical module, the programming software alerts you to this mismatch when you attempt to configure the Internet Protocol, Port Configuration and Network tabs for that device. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 65 Chapter 5 Configure a Supervisor on a Device-level Ring Network To configure the ring supervisor in RSLogix 5000 programming software, follow these steps. IMPORTANT The steps to configure a ring supervisor via software are basically the same for the 1756-EN2TR 1756-EN2TR module and the 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F taps. This example shows how to configure the 1756-EN2TR 1756-EN2TR module. You need to configure only the 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, and 1783-ETAP2F 1783-ETAP2F taps in your I/O Configuration if you plan to enable the tap as a ring supervisor. If you do not plan to use the tap as a ring supervisor, we recommend that you do not add it to your I/O Configuration. Additionally, if you want to configure a 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, or 1783-ETAP2F 1783-ETAP2F tap as a supervisor via software or with its DIP switchs, you must first assign it an IP address. The tap does not require an IP address if it is used as a ring node or has its supervisor function enabled by DIP switch For more information on how to use a tap's switch to configure it as a ring supervisor, see the EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005 ENET-AP005. 1. Add the module to your project. a. Right-click 1756 Backplane and choose New Module. a 66 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 b. Select the module. c. Click OK. b c 2. Complete configuration information for the module in your RSLogix 5000 project. The graphic below shows the I/O configuration for an example DLR network. 3. Download to your Logix controller. 4. Go online with the controller and leave it in Program mode. Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 67 Chapter 5 Configure a Supervisor on a Device-level Ring Network Enable Ring Supervisor in RSLogix 5000 Programming Software To enable a ring supervisor, you must use an AOP in RSLogix 5000 programming software, version 17.01. After you have added your 1756-EN2TR 1756-EN2TR module or 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, or 1783-ETAP2F 1783-ETAP2F tap to your RSLogix 5000 project, you must enable the ring supervisor. IMPORTANT If you are using RSLogix 5000 programming software to configure your ring supervisor and monitor diagnostics of your DLR network, you must be online with your controller. To enable the 1756-EN2TR 1756-EN2TR module or 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, or 1783-ETAP2F 1783-ETAP2F tap as a ring supervisor, follow these steps. IMPORTANT The steps to enable a ring supervisor are basically the same for both the 1756-EN2TR 1756-EN2TR module and the 1783-ETAP 1783-ETAP, 1783-ETAP1F 1783-ETAP1F, or 1783-ETAP2F 1783-ETAP2F tap. This example shows how to do it for the 1756-EN2TR 1756-EN2TR module. 1. With your project online with the controller, double-click a supervisor-capable device in the I/O configuration tree. Double-click the module. 68 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 2. Click the Network tab to enable Supervisor Mode. Click here to enable Supervisor Mode. Configuration takes affect immediately; you do not need to click Apply or OK. 3. Click the Advanced button to configure supervisor-related parameters, as shown in the screen shot below. For the Supervisor Precedence parameter, you must click Set after entering a value. 4. Click Set. IMPORTANT Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 For Beacon Interval, Beacon Timeout and Ring Protocol VLAN ID, we recommend that you only use the default values. 69 Chapter 5 Configure a Supervisor on a Device-level Ring Network Functionality Description Default Setting Supervisor Precedence You must configure a supervisor precedence number for each device configured as a ring supervisor. The highest possible supervisor precedence value is 255. 0 When multiple nodes are enabled as supervisor, the node with the highest precedence value is assigned as the active ring supervisor; the other nodes automatically become back-up supervisors. We recommend that you: · configure back-up supervisor nodes. · set your desired Active Ring Supervisor with a relatively high supervisor-precedence value compared to the back-up nodes. · keep track of your network's supervisor-precedence values. If multiple supervisors are configured with the same precedence value (the factory default value for all supervisor-capable devices is 0), the node with the numerically highest MAC address becomes the active supervisor. Beacon Interval Frequency of the active ring supervisor transmitting a beacon frame through both of its Ethernet ports. This parameter is user configurable for any time between 200µS and 100mS. 400 µS Beacon Timeout The beacon timeout is amount of time nodes wait before timing out the reception of beacon frames and taking appropriate action. Supervisors support a range from 400µS to 500mS. 1960 µS Ring Protocol VLAN ID Reserved for future use. 0 70 Publication ENET-UM001I-EN-P ENET-UM001I-EN-P - January 2010 Configure a Supervisor on a Device-level Ring Network Chapter 5 Configure and Enable a Ring Supervisor in RSLinx Classic Communication Software You can configure and enable a ring supervisor for your DLR network through RSLinx Classic communication software. Depending on the firmware revision of your product, you must use specific versions of RSLinx communication software. IMPORTANT Cat. No. Firmware Revision Required RSLinx Commmunication Software Version 1756-EN2TR 1756-EN2TR 2.1(1) 2.55 or later 3.x or later 2.56 or later 1.1(2) 2.55 or later 2.x or later 2.56 or later 2.x or later 2.56 or later 1783-ETAP 1783-ETAP 1783-ETAP1F 1783-ETAP1F 1783-ETAP2F 1783-ETAP2F (1) You can use the ControlFLASH Firmware Upgrade soft