Ethernet Design Considerations

Reference Manual
Ethernet Design Considerations
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: 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. ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence. SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present. BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures. IMPORTANT Identifies information that is critical for successful application and understanding of the product.
Allen-Bradley, Rockwell Software, Rockwell Automation, ArmorBlock, CompactLogix, ControlLogix, FactoryTalk View, PanelView, RSLinx, RSLogix, Logix5000, Kinetix, FLEX, POINT I/O, PowerFlex, RSNetWorx, RSView, SoftLogix, Stratix 6000, Stratix 8000, Stratix 8300, ArmorPOINT, POINT Guard I/O, Guard I/O, GuardLogix, Integrated Architecture, ControlFLASH, and TechConnect are trademarks of Rockwell Automation, Inc. Trademarks not belonging to Rockwell Automation are property of their respective companies.
Summary of Changes
This manual contains new and updated information. Changes throughout this revision are marked by change bars, as shown to the right of this paragraph.
New and Updated Information
This table contains the changes made to this revision.

Topic Updated network information in table comparison Added default gateway addresses for devices with IP address switches Updated modules in architecture example for EtherNet/IP network Updated Network Address Translation (NAT) protocol section Added description of using nodes to determine the number of Ethernet devices that can communicate with CompactLogix 5370 controllers Updated EtherNet/IP specifications to include CompactLogix 5370 controllers Added CompactLogix 5370 controller example for estimating EtherNet/IP network capacity Updated explicit message bandwidth for CompactLogix 5370 controllers Added Index to manual Page 9 15 17 36 59 60 77 86 95
Rockwell Automation Publication ENET-RM002B-EN-P - April 2012
Summary of Changes
Notes:
Table of Contents
Preface
Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 1 EtherNet/IP Overview

Network Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Common Industrial Protocol (CIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Gateway Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP Modules in a Control System . . . . . . . . . . . . . . . . . . . . . . . . . Bridge Across Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 12 13 13 15 16 17 18
Chapter 2 Ethernet Infrastructure Components Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hubs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Media Converters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Routers and Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Switches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unmanaged versus Managed Switches. . . . . . . . . . . . . . . . . . . . . . . . . . Autonegotiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full-duplex Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 23 23 24 24 25 26 27 27 28
Chapter 3 Ethernet Infrastructure Features

Transmission Packets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Default Setting in RSLogix 5000 Software . . . . . . . . . . . . . . . . . . . . . . Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multicast Address Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Resolution Protocol (ARP). . . . . . . . . . . . . . . . . . . . . . . . . . . . Domain Name System (DNS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Address Translation (NAT). . . . . . . . . . . . . . . . . . . . . . . . . . Virtual LANs and Segmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLAN Trunking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VLANs and Segmentation Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . Quality of Service (QoS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QoS Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resiliency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time Calculations in a Logix5000 System . . . . . . . . . . . . . . . . . . . . . . Resiliency Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Spanning Tree Protocol (STP) and Rapid STP (RSTP). . . . . . . . . . EtherChannel Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 31 32 33 33 33 34 36 37 39 39 40 40 41 41 41 42 43
Table of Contents
Flex Links Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Resilient Ethernet Protocol (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device-level Ring (DLR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Internet Group Management Protocol (IGMP) . . . . . . . . . . . . . . . . . . . . . Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Secure MAC Address (MAC ID) . . . . . . . . . . . . . . . . . . . . . Static Secure MAC Address (MAC ID) . . . . . . . . . . . . . . . . . . . . . . . . Security Violations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44 45 47 49 50 50 50 51 52
Chapter 4 EtherNet/IP Protocol

Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Connection Message Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Connection Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Nodes on an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP Network Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Packets Rate Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP Capacity Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade to Latest Firmware Revision . . . . . . . . . . . . . . . . . . . . . . . . . . Monitor Packet Sizes in Current Application . . . . . . . . . . . . . . . . . . . Requested Packet Interval (RPI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Implicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explicit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CIP Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Integrated Motion on an EtherNet/IP Network . . . . . . . . . . . . . . . . . . . . Connectivity to IT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 55 56 57 57 58 59 60 63 63 64 64 64 65 65 66 67 68 70 71
Chapter 5 Predict System Performance

System Prediction Goals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Part One: Determine If System Has Sufficient Bandwidth to Meet Application Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Part Two: Predict Maximum input or Output Times for CIP Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CompactLogix 5370 Controller Example . . . . . . . . . . . . . . . . . . . . . . . ControlLogix Controller Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identify and Count Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Calculate Packets/Second . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimate the Fastest RPI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimate Maximum Input or Output Times for CIP Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
74 75 76 77 77 78 79 80 82 83
Table of Contents
Example: Predict System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Determine If System Has Sufficient Bandwidth to Meet Application Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . Explicit Messaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP Module Serving as a Scanner . . . . . . . . . . . . . . . . . . . . . . EtherNet/IP Modules Functioning as Adapters . . . . . . . . . . . . . . . . . EtherNet/IP Modules 2 and 3 with Consumed Tags . . . . . . . . . . . . Recommendations to Achieve More Throughput in an Existing Control System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Estimate the Maximum Input or Output Times for CIP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Refine Estimates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
84 85 86 87 89 90 91 92 93
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Table of Contents
Notes:
Preface
Rockwell Automation follows a strategy of using open network technology for seamless, top-floor to shop-floor integration. These open networks speak a common language and share a universal set of communication services. As a result, information can be communicated seamlessly throughout the plant, from shop floor to top floor, and to and from the Internet for e-business applications. Each Rockwell Automation network is ideal for a wide range of applications, operates with devices manufactured by various vendors, and shares data with industry-standard information networks.
Comparison Function EtherNet/IP Network Plant management system tie-in (material handling); configuration, data collection, and control on a single high-speed network Mainframe computers Programmable controllers Robots HMI I/O Drives Process instruments ControlNet Network Supports transmission of time critical data between PLC processors and I/O devices Programmable controllers I/O chassis HMIs Personal computers Drives Robots DeviceNet Network Connects low-level devices directly to plant-floor controllerswithout interfacing them through I/O modules Sensors Motor starters Drives Personal computers Push buttons Low-end HMIs Bar code readers PLC processors Valve manifolds
Typical devices networked
Data repetition
Large packets, data sent regularly
Medium-size packets; data transmissions are deterministic and repeatable 99 nodes 5 Mbps Redundant applications Scheduled communication
Small packets; data sent as needed
Number of nodes, max Data transfer rate Typical use
No limit 10 Mbps, 100 Mbps, or 1 Gbps Plant-wide architecture High-speed applications
64 total nodes 500, 250, or 125 Kbps Supply power and connectivity to low-level devices
Preface
Additional Resources
Table 1 - ODVA Resources
Resource http://www.odva.org/ http://www.odva.org/default.aspx?tabid=54
These documents and websites contain additional information concerning related products from Rockwell Automation.
Description Accesses the Open DeviceNet Vendors Association (ODVA) website. Accesses the CIP Advantage website that offers the following: CIP features and benefits How to get started Describes the required media components and how to plan for, install, verify, troubleshoot, and certify an Ethernet network.
Ethernet Media Planning and Installation Manual, ODVA publication http://www.odva.org/Portals/0/Library/Publications_Numbered/ PUB00148R0_EtherNetIP_Media_Planning_and_Installation_Manual.pdf
Network Infrastructure for EtherNet/IP: Introduction and Considerations, ODVA publication Provides an overview of the technologies used in EtherNet/IP networks and provides guidelines for deploying infrastructure devices in EtherNet/IP networks. http://www.odva.org/Portals/0/Library/Publications_Numbered/ PUB00035R0_Infrastructure_Guide.pdf
Table 2 - Rockwell Automation Resources

Resource http://www.ab.com/networks/ http://www.rockwellautomation.com/services/networks/ http://www.rockwellautomation.com/services/security/ http://www.ab.com/networks/architectures.html EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005 EtherNet/IP QuickConnect Application Technique, publication ENET-AT001 EtherNet/IP Socket Interface Application Technique, publication ENET-AT002 EtherNet/IP Network Configuration User Manual, publication ENET-UM001 Description Accesses the networks and communication section of the Rockwell Automation website. Accesses Rockwell Automation network and security services websites. Links to the Education series webcasts for IT and controls professionals. Describes how to install, configure, and maintain linear and device-level Ring (DLR) networks using Rockwell Automation EtherNet/IP devices with embedded switch technology. Describes the EtherNet/IP QuickConnect technology, which enables EtherNet/IP devices to quickly power up and join an EtherNet/IP network. Describes the socket interface used to program MSG instructions to communicate between a Logix5000 controller via an EtherNet/IP module and Ethernet devices that do not support the EtherNet/IP application protocol. Describes how to configure and use EtherNet/IP communication modules with a Logix5000 controller and communicate with various devices on the Ethernet network.
Table 3 - Cisco and Rockwell Automation Alliance Resources

Resource http://www.ab.com/networks/architectures.html Converged Plantwide Ethernet (CPwE) Design and Implementation Guide, publication ENET-TD001 Description Links to the Rockwell Automation and Cisco Systems reference architecture website. Represents a collaborative development effort from Rockwell Automation and Cisco Systems. The design guide is built on, and adds to, design guidelines from the Cisco Ethernet-to-the-Factory (EttF) solution and the Rockwell Automation Integrated Architecture. The design guide focuses on the manufacturing industry.
You can view or download Rockwell Automation publications at http:/www.rockwellautomation.com/literature/. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative.
10
Chapter
EtherNet/IP Overview
The EtherNet/IP protocol is a multi-discipline, control and information platform for use in industrial environments and time-critical applications. The EtherNet/IP network uses standard Ethernet and TCP/IP technologies and an open, application-layer protocol called the Common Industrial Protocol (CIP). The open, application-layer protocol makes interoperability and interchangeability of industrial automation and control devices on the EtherNet/IP network a reality for automation and real-time, control applications.
Application CIP Control and Information Protocol EN50170 Control International and IF C 61158 Standard
Presentation
Session
Transport
UDP IP-Multicast
TCP
OPEN
Request for Comments IETF UDP/TCP/IP
Network
IP
Llink
Ethernet MAC IEEE 802.3 Ethernet Physical
Physical
Topic Network Protocols Configuration Requirements EtherNet/IP Modules in a Control System Bridge Across Networks
Page 12 13 17 18
The EtherNet/IP protocol follows these standards: IEEE 802.3 - standard Ethernet, Precision Time Protocol (IEEE-1588) IETF - Internet Engineering Task Force, standard Internet Protocol (IP) IEC - International Electrotechnical Commission ODVA - Common Industrial Protocol (CIP)
11
Chapter 1
Network Protocols
On the most basic level, Ethernet is a wire or cable that connects computers and peripheral modules so that they can communicate. The actual wire used for the network is referred to as the network medium. Beyond the physical medium, all Ethernet networks support protocols that provide data transfer and network management capability.
Description CIP applies a common application layer over an Ethernet network by encapsulating messages in TCP/UDP/IP. This common application layer is the Common Industrial Protocol (CIP), which provides interoperability and interchangeability of industrial automation and control modules on an Ethernet network. The EtherNet/IP network supports both real-time I/O (implicit messaging) and explicit messaging. TCP/IP is a transport-layer protocol (TCP) and a network-layer protocol (IP) commonly used in business environments for communication within networks and across internetworks. The EtherNet/IP communication modules use TCP/IP for explicit messaging, that is, messages in which time is not a critical factor, such as uploading or downloading programs. UDP is a much simpler transport protocol. It is connectionless and provides a simple means of sending datagrams between two modules. UDP is used by applications that implement their own handshaking between modules and only require minimal transport service. UDP is smaller, simpler, and faster than TCP and can operate in unicast, multicast, or broadcast mode. The EtherNet/IP communication modules use UDP/IP for real time I/O messaging.
Protocol CIP
Transmission Control Protocol/internet Protocol (TCP/IP) User Datagram Protocol/internet Protocol (UDP/IP)
Common Industrial Protocol (CIP)

The Common Industrial Protocol (CIP) is a message-based, application-layer protocol that implements a relative path to send a message from the producing module in a system to the consuming modules. CIP uses the producer/consumer networking model instead of a source/ destination (master/slave) model. The producer/consumer model reduces network traffic and increases speed of transmission. In traditional I/O systems, controllers poll input modules to obtain their input status. In the CIP system, digital input modules are not polled by a controller. Instead, they produce their data either upon a change of state (COS) or at a requested packet interval (RPI). The frequency of update depends upon the options chosen during configuration and where on the network the input module resides. The input module, therefore, is a producer of input data and the controller is a consumer of the data. The controller can also produce data for other controllers to consume. The produced and consumed data is accessible by multiple controllers over the Logix backplane and over the EtherNet/IP network. This data exchange conforms to the producer/consumer model.
12
Chapter 1
Configuration Requirements
All devices on Ethernet communicate by using the Ethernet address for the device. This address is sometimes referred to as the hardware address or Media Access Controller (MAC) address. The hardware address is a unique (in the world), six-byte address that is embedded in the circuitry of every device that sits on an Ethernet network. Every vendor of Ethernet products obtains their own unique address range. For a device to communicate on an Ethernet network, you must configure its IP address, gateway address, and subnet mask.
IP Address
The IP address identifies each node on the IP network or system of connected networks. Each TCP/IP node on a network must have a unique IP address. The IP address is 32 bits long and has a network ID part and a host ID part. Because networks vary in size, there are four types of networks.
Network Type Class A Class B Class C Class D For Large networks with many devices Medium-sized networks Small networks (fewer than 256 devices) Most common for private, industrial networks Multicast addresses
The network class determines how an IP address is formatted.

Class A Class B 0 0 0 1 0 8 network (7 bits) 8 network (14 bits) 8 0 8 0 1 network (21 bits) 16 24 multicast address (28 bits) 16 16 24 local address (24 bits) 24 local address (16 bits) 24 local address (8 bits) 31 31 31
Class C
0 1 1 0 1 1
16
31
Class D
13
Chapter 1
Each node on the same physical network must have an IP address of the same class and must have the same network ID. Each node on the same network must have a different local address (host ID), thus giving it a unique IP address. IP addresses are written as four-decimal integers (0...255) separated by periods where each integer gives the value of one byte of the IP address. For example, the 32-bit IP address: 10000010 00000000 00000000 00000001 is written as 130.0.0.1.
Class A B C D Leftmost Bits 0xxx 10xx 110x 1110 Start Address 0.0.0. 128.0.0.0 192.0.0.0 224.0.0.0 Finish Address 127.255.255.255 191.255.255.255 223.255.255.255 239.255.255.255
Public IP addresses are for computers and devices connected to the Internet. Devices on industrial networks are not connected to the Internet, but they communicate with each other over an EtherNet/IP network. These devices use private IP addresses that are not routed on the Internet. Private IP addresses typically start with 10, 172, or 192 as the first part of the address. Private IP addresses are typically connected to the Internet through a Network Address Translation (NAT) device. For more NAT information, see page 36.
14
Chapter 1
Gateway Address
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. The following figure shows gateway G connecting Network 1 with Network 2.
A
128.1.0.1
Network 1 G B
128.2.0.1
128.1.0.2
C
128.2.0.2
128.2.0.3
Network 2
When host B with IP address 128.2.0.1 communicates with host C, it knows from Cs IP address that C is on the same network. In an Ethernet environment, B can then resolve Cs IP address to a MAC address and communicate with C directly. When host B communicates with host A, it knows from As IP address that A is on another network because the network IDs differ. To send data to A, B must have the IP address of the gateway connecting the two networks. In this example, the gateways IP address on Network 2 is 128.2.0.3. The gateway has two IP addresses (128.1.0.2 and 128.2.0.3). Network 1 hosts must use the first IP address, and Network 2 hosts must use the second IP address. To be usable, a hosts gateway IP address must match its own net ID. Devices with IP address switches use the default gateway address of either 192.168.1.1 or 0.0.0.0. Check your product information to determine which gateway address applies for your device.
15
Chapter 1
Subnet Mask
Subnet addressing is an extension of the IP address scheme that enables a site to use a single net 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 IP class. Inside a site, the subnet mask is used to redivide the IP address into a custom net ID portion and host ID portion. A subnet mask determines which of the 32 bits in the IP address are part of the network ID and which are part of the unique node identification. This also determines the size of the network or subnetwork. Take Network 2 (a Class B network) in the previous example and add another physical network. Selecting this subnet mask would add two additional net ID bits allowing for four physical networks. 11111111 11111111 11111111 00000000 = 255.255.255.0 Two bits of the Class B host ID have been used to extend the net ID. Each unique combination of bits in the part of the host ID where subnet mask bits are 1 specifies a different physical network.
A
128.1.0.1 128.1.0.1
Network 1 G B
128.2.64.1 128.2.64.1
128.1.0.2 128.1.0.2
C
128.2.64.2 128.2.64.2
128.2.64.3 128.2.64.3
Network 2.1 G2 D
128.2.128.1 128.2.128.1
128.2.64.4
E
128.2.128.2 128.2.128.2
128.2.128.3 128.2.128.3
Network 2.2
A second network with Hosts D and E has been added. Gateway G2 connects Network 2.1 with Network 2.2. Hosts D and E will use Gateway G2 to communicate with hosts not on Network 2.2. Hosts B and C will use Gateway G to communicate with hosts not on Network 2.1. When B is communicating with D, G (the configured Gateway for B) will route the data from B to D through G2.
16
Chapter 1
EtherNet/IP Modules in a Control System
The following diagram shows how EtherNet/IP communication modules can fit into a control system.
1769-L18ERM-BB1B Control System 1769-L33ERM Control System 1756-EN2T 1756 I/O Modules 1794-AENT 1794 I/O Modules
Switch
PowerFlex Drive
1734-AENT 1734 I/O Modules
Kinetix 350 Drive with Motor
Workstation 1783-ETAP Workstation 1783-ETAP
PanelView Plus Terminal Connected Via a 1783-ETAP EtherNet/IP Tap
Kinetix 6500 Drives with Motors
1756-EN2TR 1756 I/O Modules
1734-AENTR POINT I/O Adapter with POINT I/O Modules
1794-AENTR FLEX I/O Adapter
In this example, the following actions can occur: Controllers produce and consume tags with each other. Controllers initiate MSG instructions that send/receive data or configure devices. Controllers control I/O and drives. Workstations can upload/download projects to the controllers. Workstations can configure devices on the EtherNet/IP network.
17
Chapter 1
Bridge Across Networks
Some EtherNet/IP communication modules support the ability to bridge or route communication through devices, depending on the capabilities of the platform and communication devices. You have a bridge when you have a connection between communication devices on two networks. For example, the 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. The bridge device can be an EtherNet/IP-to-DeviceNet bridging device or a Logix5000 system with an EtherNet/IP communication module and a DeviceNet communication module.
CIP messages that originate on this network
Can bridge to this network EtherNet/IP ControlNet Yes Yes Yes DeviceNet Yes Yes Yes RS-232 Serial Yes Yes Yes
EtherNet/IP ControlNet RS-232
Yes Yes Yes
In the following example graphic, a workstation configures a drive on a DeviceNet network and bridges EtherNet/IP networks to reach the drive.
PanelView Plus Terminal EtherNet/IP Switch Bridge DeviceNet
Drive
IMPORTANT
You can bridge between devices on different networks for messaging only. You cannot bridge from one network to another for I/O control or produced and consumed tags. This restriction applies regardless of whether the two networks are either of the following: Same type, for example, an EtherNet/IP network to EtherNet/IP network Different types, for example EtherNet/IP network to ControlNet network
18
Chapter
Ethernet Infrastructure Components
The topology and cable layout of the Ethernet network is part of the physical layer. Ethernet systems require various infrastructure components to connect individual network segments.
Topic Topologies Media Hubs Repeaters Media Converters Bridges Routers and Gateways Switches Page 19 22 23 23 24 24 25 26
Topologies
Ethernet networks are laid out in point-to-point configurations with one cable for each device. Ethernet networks have active infrastructures that rely on switches. You can design a network with individual switch devices and devices that have embedded switch technology.
Table 4 - Topologies with an Individual Switch

Topology Star Switch Description The traditional, most-common, EtherNet/IP network topology is a star, where end devices are connected and communicate with each other via a switch. In a star topology, nodes are typically grouped closely together. D Advantages Easy to design, configure, and implement Direct path between the infrastructure device and the end device Remove and add devices without affecting the rest of the network Increase port capacity on the switch to add more devices Centralization can ease troubleshooting, because the switch sees the activities of all of the connected devices Disadvantages Loss of network service in case of connection failure (no resiliency) Primarily the single point of failure of the centralized switch.
19
Chapter 2
Table 4 - Topologies with an Individual Switch

Topology Ring - switch based D D Description A ring network is a single-fault tolerant ring network intended for the interconnection of automation devices. Advantages Ability to survive a single point of failure or a device being powered down on the ring. Simplified cabling Ability to cover long distances with 100 m allowed between each copper segment Disadvantages Additional configuration complexity Longer convergence times Variable number of hops can make performance difficult to predict
Switch D D Switch D Linear - switch based Switch D D Switch D D Switch D D D Switch Switch D D
A linear network is a collection of devices that are daisy-chained together. A linear topology works best for a limited number of nodes. Advantages Easy to design, configure, and implement Least amount of cabling Minimal amount of cable needed Ability to cover long distances with 100 m allowed between each link Disadvantages Loss of network service in case of connection failure (no resiliency) Creates the potential for bottlenecks Variable number of hops can make performance difficult to predict Powering down a device or the failure of a device in the center of the network affects connectivity between any of the devices on either side Each link in the chain represents network delay
Redundant star Layer 3 Layer 3
A redundant star topology is essentially where every Layer 2 access switch has dual connections to a Layer 3 distribution switch. Devices are connected to the Layer 2 switches. Advantages Resiliency from multiple connection failures Faster convergence to connection loss Consistent number of hops provide predictable and consistent performance Fewer bottlenecks Disadvantages Additional wiring and ports required Additional configuration complexity
Layer 2 D D
Layer 2 D D
20
Chapter 2
The EtherNet/IP embedded switch technology offers alternative network topologies by embedding switches into the end devices themselves.
Table 5 - Topologies with Embedded Switch Technology
Topology Device-level ring (DLR) - embedded switch
D D D D D D D D
Description
Description
A DLR network is a single-fault tolerant ring network intended for the interconnection of automation devices. This topology is also implemented at the device level. No additional switches are required. Advantages Ability to survive a single point of failure or a device being powered down on the ring. Simplified cabling Ability to cover long distances with 100 m allowed between each copper segment Very fast network convergence Disadvantages Supervisor-node configuration required Additional configuration complexity Variable number of hops can make performance difficult to predict
Linear - embedded switch
A linear network is a collection of devices that are daisy-chained together. The EtherNet/IP embedded switch technology allows this topology to be implemented at the device level. No additional switches are required. A linear topology works best for a limited number of nodes. Advantages Easy to design, configure, and implement Least amount of cabling Minimal amount of cable needed Ability to cover long distances with 100 m allowed between each link Disadvantages Loss of network service in case of connection failure (no resiliency) Creates the potential for bottlenecks Variable number of hops can make performance difficult to predict Powering down a device or the failure of a device in the center of the network affects connectivity between any of the devices on either side Each link in the chain represents network delay
21
Chapter 2
Media
The actual wire used for the network is referred to as the physical media. Generally, shorter cable runs are less susceptible to EMI (electromagnetic interference) and RFI (radio-frequency interference) from electrical circuits, motors, and other machinery. Use this flowchart to select Ethernet media.
Do you have any of these: Long distances? High Magnetic fields? High noise?
Yes
Fiber Media Recommendations: Multi-mode for general purposes, cost less Single-node yields higher distance, but costs more
No
Do you have excess amounts of any of these: Radiated noise? Conducted noise? Metal conduit?
Yes
Copper STP (shielded twisted pair) Recommendations: Requires proper grounding Category 5e, 6, and 6a cables and connectors
No Copper UTP (unshielded twisted pair) Recommendations: Requires proper grounding Category 5e, 6, and 6a cables and comectors
For more information about the media options, see the Ethernet section of the Network Media Catalog, publication M116-CA552.
22
Chapter 2
Hubs
Hubs are multiport repeaters. They are based on older technology that has been largely replaced by network switches at layer 2, but that are still used as network diagnostic tools to analyze network traffic: A hub is at the center of a star topology. Hubs can be connected together using a variety of media as a backbone between hubs. A hub broadcasts everything it receives on any channel out all other channels.
Hub Personal computer
HMI
1738 ArmorPOINT I/O 1756 Controller PowerFlex 1734 POINT I/O
Repeaters
A repeater recreates the incoming signal and re-transmits it without noise or distortion that may have effected the signal as it was transmitted down the cable. Repeaters are generally only on older networks to increase the network length. More modern networks use fiber media or switches to increase network length.
Repeater
23
Chapter 2
Media Converters
Media converters let you mix fiber and copper (twisted-pair) cables in the same system. Use a switch to mix media: Physical layer devices offer no buffering or advanced diagnostic features. Physical layer devices are easily overrun by an EtherNet/IP system (no buffering = lost data). Layer 2 devices have buffering, QoS, and other management features.
Fiber Link
Bridges
A bridge is a device that isolates traffic between segments by selectively forwarding frames to their proper destination. It is transparent to the network and protocol independent. Similar to the repeater, the bridge isnt used much any more, but more advanced devices which perform the bridging function are commonly used.
Bridge Ethernet Ethernet
Bridge Ethernet Token Ring
Access Point Ethernet
Work Group Bridge Ethernet
24
Chapter 2
Routers and Gateways
Routers and gateways use the network portion of IP addresses to identify where networks are. They keep a routing table that tells the device which port a message should be transmitted out in order to get the message to the proper network. If the particular network is not directly attached to that device, it will forward the message to the next gateway or router in the path for further routing.
Routing Table Network 10.17.10.0 10.10.10.0 Port 1 2 Default Gateway 10.10.10.1 10.17.10.1
10.17.10.56 VLAN 17 Subnet 10.17.10.0 Subnet Mask 255.255.255.0 VLAN 10 Subnet 10.10.10.0 Subnet Mask 255.255.255.0
10.10.10.56
25
Chapter 2
Switches
Switches are key components that provide determinism and throughput required for control applications. Industrial-rated switches are recommended for connecting the computers and other devices to each other and to higher-level networks in the network reference architecture. Ethernet switches perform the following: Operate in full-duplex mode to eliminate collisions Include managed switch features for advanced network functionality
Figure 1 - Select an Ethernet Switch
For more information, see the Stratix Switch Reference Chart, publication ENET-QR001.
26
Chapter 2
Unmanaged versus Managed Switches

Unmanaged switches are relatively inexpensive and simple to set up, but they do not provide any management capabilities, security, or diagnostic information. Therefore, they are difficult to troubleshoot. As a general rule for using unmanaged switches, make sure your application: Does not contain I/O traffic or Has I/O control and the following is true: The network is not directly connected to the IT network All nodes on the network are Rockwell Automation devices There is no potential to overload a device with traffic Managed switches are typically more expensive than unmanaged switches and require some level of support for initial configuration and replacement. However, managed switches provide many advanced features that enable better network performance in your control system. Managed switches are able to manage multicast traffic, provide diagnostics data and security options, and other advanced features.
Advantages Managed switch Ability to manage multicast traffic Provide diagnostics data Provide security options Additional advanced features Disadvantages More expensive Requires some level of support and configuration to start up and replace No management capabilities No security No diagnostic information provided Difficult to troubleshoot
Unmanaged switch
Inexpensive Simple to set up 'No Config' replacement
Autonegotiation
Autonegotiation lets devices select the most optimal way to communicate without you having to configure the devices. However, if you connect a manuallyconfigured device to an autonegotiation device, there can be problems which result in a high rate of data transmission errors. All 100 Mbps devices are required to support autonegotiation, but most existing 10 Mbps devices do not. Select a switch that supports both speeds so you can connect to existing devices that support only the slower rate.
27
Chapter 2
Full-duplex Mode
Ethernet is based on Carrier Sense Multiple Access/Collision Detect (CSMA/ CD) technology. This technology places all nodes on a common circuit so they can all talk as needed. The nodes have to handle collisions (multiple devices talking at the same time) and monitor their own transmissions so that other nodes have transmission time. The data transmission mode you configure determines how devices transmit and receive data.
Transmission Mode Full-duplex Features Deterministic Transmit and receive at the same time Transmit on the transmit pair and receive on the receive pairs No collision detection, backoff, or retry Collision free Nondeterministic One station transmits and the others listen While transmitting, you do not receive, as no one else is transmitting If someone else transmits while you are transmitting, then a collision occurs Any Receive-while-Transmit condition is considered a collision
Half- duplex
Full-duplex mode eliminates collisions. Combined with the speed of the switches available today, you can eliminate the delays related to collisions or traffic in the switch. The end result is that the EtherNet/IP network becomes a highly deterministic network that works well for I/O control: If you are autonegotiating, make sure you are verifying the connection. If you are forcing speed and duplex on any given link, make sure you are forcing at both ends of the link. If you only force on one side of the link the autonegotiating side will always go to half duplex.
28
Chapter
Ethernet Infrastructure Features
When using the EtherNet/IP network for time-critical control, there are several features available in switches that are required or recommended.
Topic Transmission Packets Transmission Protocols Virtual LANs and Segmentation Quality of Service (QoS) Resiliency Internet Group Management Protocol (IGMP) Port Security Device Commissioning Page 30 33 37 40 41 49 50 52
29
Chapter 3
Transmission Packets
Packet Type Unicast Destination A single node
Data is transmitted over the EtherNet/IP network in packets. There are transmission methods for transporting data on the network.
Description Unicast connections are point-to-point transmissions between a source node and destination node on the network. A Frame is sent to a single destination.
Multicast
Multiple nodes simultaneously
Multicast connections deliver information from one sender to multiple receivers simultaneously. Copies of a single frame are passed to a selected subset of possible destinations.
Broadcast
All nodes
Broadcast connections transmit information to every device on the network. A frame is delivered to all hosts on the network.
Stratix 1756 Controller
Limit the amount of broadcast and multicast traffic on the supervisory control network: Eliminating unwanted traffic reduces the load on devices, switches, and the network. Eliminating unnecessary incoming broadcast traffic also minimizes network load.
30
Chapter 3
It is important to prevent network traffic from coming into the supervisory control (level 2) and manufacturing operations (level 3) network from other levels. Likewise, it is equally important to ensure that traffic on the control system network does not get propagated into the plant enterprise network
Default Setting in RSLogix 5000 Software

The support for unicast communication and the default settings in RSLogix 5000 programming software depend on the version of software. Later software versions include the unicast features of earlier versions.
Software Version 20 19 18 16 Unicast Support and Default Setting Safety I/O unicast support added Unicast default Safety produce/consume unicast support added Unicast default Standard I/O unicast support added Multicast default Standard produce/consume unicast support added Multicast default
For a compatibility chart of products see Knowledgebase Answer ID 66324 at http://www.rockwellautomation.com/knowledgebase/.
31
Chapter 3
Frames
Use multicast frames in these situations: Redundancy applications Communication with more than one destination (Multicast is more efficient than sending multiple, unicast streams to multiple nodes.) Video streaming
To Plant Network
Switch or Router
Layer 2 Switch
Layer 2 Switch
Controller (Consumer)
I/O (Producer)
You must use unicast communication if the transmission routes through a Layer 3 device. I/O devices generally produce at very fast rates (such as 10 ms), so it is easy to flood the network with multicast traffic and force each end device to spend time deciding whether to discard numerous multicast frames. If there are a lot of I/O devices, they can easily use up a significant part of a routers CPU time. You must consider control network traffic propagating onto the plant information network, as well as, plant information network traffic propagating onto the control network. Some best practices include the following: Minimize device load due to unwanted IP multicast traffic Minimize switch load due to unwanted IP multicast traffic Minimize network load due to unwanted incoming IP multicast or broadcast traffic Block IP multicast traffic generated within the EtherNet/IP subnet from propagating onto the plant network Implement standard network troubleshooting tools For more information, see Virtual LANs and Segmentation on page 37 and Internet Group Management Protocol (IGMP) on page 49.
32
Chapter 3
Multicast Address Limit

In multicast communication, EtherNet/IP interfaces support a maximum of 32 devices that transmit multicast. Example 1: An Ethernet adapter that produces data uses a unique multicast address for each I/O connection. Example 2: A Logix controller that produces tags uses a unique multicast address for each produced tag. The multicast address limit is independent of the connection limit for a device. Not all connections require a multicast address. And in the case of produced and consumed tags, one produced tag requires one multicast address but it also requires one connection for each consumer. If there are multiple consumers, the one multicast address would be using multiple connections.
Transmission Protocols
The Network layer (Layer 3) provides switching and routing that create logical paths, known as virtual circuits, for transmitting data from node to node. Routing and forwarding are functions of this layer, as well as addressing, and internetworking.
Address Resolution Protocol (ARP)

An ARP request is a broadcast message that asks who has this IP address?. The device that has that IP address responds and the requestor adds the IP address and hardware address pair to its ARP cache. The original device can now send the message. This protocol gives the network the ability to learn and adapt to changes.
1756 Controller Device needs to send a message to 130.151.3.4
1756 Controller
Who has the IP address 130.151.3.4 ? 1734 POINT I/O
I have IP address 130.151.3.4
130.151.3.4 PowerFlex
33
Chapter 3
If you replace a Rockwell Automation EtherNet/IP communication module with a new module, the new module will have a different MAC ID. The ARP cache entries in other devices are now invalid because the MAC ID corresponding to the module's IP address has changed. This could cause a delay in reestablishing communication with the replacement module. The delay varies depending on the module and the network configuration in use. When a Rockwell Automation EtherNet/IP device starts up, it issues a gratuitous ARP that causes other devices to update their ARP caches. This generally results in a quick recovery of communication with the replacement module (less than a minute). However, some switches will not forward the gratuitous ARP message onto the network, in particular, if the Spanning Tree Protocol is enabled on that port. We recommend that you disable the Spanning Tree Protocol on those ports to which EtherNet/IP communication modules are directly connected (but not on ports which are linked to other switches). In the worst case, if the gratuitous ARP is not seen, an originating device could wait as long as 10 minutes for the ARP cache entry to age out and be deleted.
Domain Name System (DNS)

DNS is a name resolution protocol that allows users to identify devices by names rather than IP addresses. In order for DNS to work, a DNS server is configured to hold a table of names and the associated IP addresses. When a device attempts to send a message to a device with an unknown name, it requests the IP address of the named device from the DNS server.
1756 Controller Controller needs to send a message to PowerFlex. DNS Server What is the IP address for PowerFlex? 1734 POINT I/O
130.151.3.4
PowerFlex
34
Chapter 3
The DNS server refers to its table and sends back an IP address for the requested name. Once the client device receives the IP address for a name, it stores it in its own table so it does not have to ask for the IP address every time. The device may still have to do an ARP request, since it must decode the IP address into a hardware address.
1756 Controller
DNS Server
I have IP address 130.151.3.4
1734 POINT I/O DNS Table Name Controller PowerFlex Point IP Address 130.151.3.5 130.151.3.4 130.151.3.5 130.151.3.5 PowerFlex
35
Chapter 3
Network Address Translation (NAT)

NAT is a translation protocol that lets a single device, commonly a router, act as an agent between the Internet (public network) and a private network. This facilitates communication between an entire group of computers using pre-set IP addresses on a private network by mapping each to a valid IP address for the public network. To use, you must set up the gateway address on the computers on the private network to the IP address of the NAT device. These are some examples: One-to-many (such as home networks with multiple nodes being mapped to a single public identity to get onto the Internet) conserves public IP addresses and offers some protection against attacks from the Internet. One-to-one has each node on the network translated to another identity on another network. This is used in manufacturing to integrate machinery onto a larger network without having to make addressing changes at the machine level.
End-user Workstation CompactLogix 5370 Controller PanelView Plus
Stratix 2000 NAT Device Kinetix 350
In the illustration, the NAT gateway address allows the (public) end-users workstation to communicate with the process control network even though the devices have separate IP addresses. IMPORTANT If you are not using IP address switches to assign network address information, you can use RSLinx and RSLogix 5000 software to set a gateway address. The software will not allow any address parameters to be changed when the switches are set to 1254. Products with IP address switches use a default gateway of either 192.168.1.1 or 0.0.0.0. See your product literature for which default gateway address applies for your device.
36
Chapter 3
Virtual LANs and Segmentation
A virtual LAN (VLAN) is a switched network segmented on a functional, application, or organizational basis, as opposed to a physical or geographical basis. Switches filter destination MAC addresses and forward VLAN frames only to ports that serve the VLAN to which the traffic belongs. A VLAN consists of several end systems, either hosts or network equipment (such as switches and routers), all of which are members of a single logical broadcast domain. A VLAN does not have physical proximity constraints for the broadcast domain. With VLANs, you can configure a switch to share two isolated networks without the traffic from one network burdening the other. IP multicast traffic from VLAN 1 will not reach VLAN 2. A VLAN blocks broadcast traffic and adds a measure of security between networks. A VLAN also gives you the ability to control access and security to a group of devices that is independent of physical location.
Controller 1 PC Controller 2
Switch
VLAN 1
VLAN 2
I/O
I/O
I/O I/O I/O
VLANs offer these features:.

Feature Broadcast control Description Just as switches isolate collision domains for attached hosts and forward only appropriate traffic out a particular port, VLANs refine this concept further and provide complete isolation between VLANs. A VLAN is a bridging domain, and all broadcast and multicast traffic is contained within it. High-security users can be grouped into a VLAN, possibly on the same physical segment, and no users outside of that VLAN can communicate with them. VLANs can also assist in securing plant-floor systems by limiting access of production floor personnel (such as a vendor or contractor) to certain functional areas of the production floor. The logical grouping of devices prevents traffic on one VLAN from burdening other network resources. Performance within the VLAN is also improved because the VLAN acts as a dedicated LAN. A device can be logically moved from one VLAN to another by configuring a port into the appropriate VLAN. The device does not have to be physically disconnected from one network and reconnected to another which can result in expensive, time-consuming recabling.
Security
Performance Network management
Segmentation is the process of outlining which endpoints need to be in the same LAN. Segmentation is a key consideration for a cell/area network. Segmentation is important to help manage the real-time communication properties of the network, and yet support the requirements as defined by the network traffic flows. Security is also an important consideration in making segmentation decisions.
Rockwell Automation Publication ENET-RM002B-EN-P - April 2012 37
Chapter 3
A security policy may call for limiting access of factory floor personnel (such as a vendor or contractor) to certain areas of the production floor (such as a functional area). Segmenting these areas into distinct VLANs greatly assists in the application of these types of security considerations.
VLAN 10
VLAN 102
VLAN 42
In fact, there are competing objectives. On one hand, all level 02 devices that need to communicate multicast I/O between each other must be in the same LAN. On the other hand, the smaller the VLAN, the easier it is to manage and maintain real-time communication. Real-time communication is harder to maintain as the number of switches, devices, and the amount of network traffic increase in a LAN. Typically control networks are segmented from business networks. You can also segment networks based on function, logical layout, and traffic types. Choose from these options to segment control.
Segmentation Option Physical isolation Description Physically isolate networks Each network is a separate subnet creating clusters of control No IT involvement A separate ControlLogix EtherNet/IP bridge module is dedicated to each subnet The chassis backplane provides isolation of Ethernet traffic Only CIP traffic can be shared between subnets No IT involvement
ControlLogix gateway
VLANs
Ports on a managed switch are assigned to a specific VLAN Data is only forwarded to ports within the same VLAN Maybe IT involvement
38
Chapter 3
VLAN Trunking
Trunking lets a VLAN span multiple switches.
VLAN 102 VLAN 42 VLAN 20 802.1 Q Trunk VLAN 102 VLAN 42 VLAN 20
VLANs and Segmentation Guidelines

Configure separate VLANs for different work cells or areas of your plant. Configure one VLAN for all data traffic relevant to one particular area/cell zone. Because 8090% of traffic is local to one cell, this is the optimal design. All devices with multicast connections must be on the same VLAN. Within a VLAN multicast and unicast traffic can be mixed depending on application requirements. The default communication type of unicast should be used for point-to-point communication to minimize device, network, and infrastructure loading: Design small cell/area zones, each with a dedicated VLAN and IP subnet. Restrict data flow out of the cell/area zone unless plantwide operations explicitly require it. Segment traffic types into VLANs and IP subnets to better manage the traffic and simplify security management. Within the cell/area zone: Use Layer 2 VLAN trunking between switches with similar traffic types When trunking, use 802.1Q, VTP in transparent mode Use Layer 3 distribution switches to route information between cell/area Zone VLANs and plantwide operations in the Industrial Zone. Enable IP directed Broadcast on Cell/Area zone VLANs with EtherNet/IP traffic for easy configuration and maintenance from control systems such as RSLinx software. Avoiding large layer 2 networks helps simplify network management. Select switches based on the VLAN features you need: Stratix 6000 switches support VLANs. Stratix 8000 and Stratix 8300 switches support VLANs and VLAN trunking, as well as Layer 3 switching (allows routing across VLANs and subnets).
39
Chapter 3
Quality of Service (QoS)
Quality of service determines how packets are marked, classified, and treated based on traffic type. Rockwell Automation EtherNet/IP devices prioritize traffic internally. Implementing QoS at the switch level adds another level of prioritization. QoS does not increase bandwidthQoS gives preferential treatment to some network traffic at the expense of others. Not all network traffic is created equal, nor should users treat it equally. To minimize application latency and jitter, control data should have priority within the Cell/Area Zone. Quality of Service (QoS) gives preferential treatment to some network traffic at the expense of others. Control data is more sensitive to latency and jitter than information data. To explain how QoS works, think about the last time you boarded a plane at the airport. As boarding time gets close everyone starts to crowd around the gate. It is impossible for everyone to go down the jetway to the plane at once, so the airline establishes a boarding procedure to avoid chaos. This can be compared to the use of QoS on an Ethernet network. The network could have motion traffic, voice traffic, and email traffic all being transmitted at the same time over the network. In the airline example, first class passengers board first, followed by families with small children, followed by frequent flyers, and followed by the coach cabin starting at the back of the plane. Similarly, QoS lets you set up priority queues in the managed switches on the network. In the automation example, equate motion traffic to the first class passengers and give it the highest priority for network usage. Voice traffic can go second (it also has low tolerance for delay) and email traffic has the lowest priority queue. This ensures the least amount of delay possible on the motion control.
Ingress Actions Egress Actions Queue/Schedule Classification Policing/Metering Marking Congestion Control
Distinguish traffic by examining Layer 2/3/4 labels and QoS fields. QoS changed depending on trust state at port.
Make sure conformance is to a specified rate.
DSCP-CoS or CoS DSCP mapping
4 queues/or with priority scheduling
QoS Guidelines
Manage the output queues based on application needs. Schedule precision and motion control packets in the highest priority queue. QoS gives preferential treatment to Industrial Automation and Control System Network traffic at the expense of other network traffic. QoS is integrated into the Stratix 8000 and Stratix 8300 switch configurations. Deploy QoS consistently throughout Industrial Automation and Control System Network.
40 Rockwell Automation Publication ENET-RM002B-EN-P - April 2012
Chapter 3
Resiliency
A resiliency protocol maintains parallel links for redundancy while avoiding loops. Network convergence time is a measure of how long it takes to detect a fault, find an alternate path, and recover from the fault: During the network convergence time, some portion of the traffic is dropped by the network because interconnectivity does not exist. Communication will drop if the convergence time is longer than the Logix connection timeout.
Time Calculations in a Logix5000 System

Network convergence must occur before the control system is impacted: Logix message instruction (MSG) time out (explicit, CIP Class 3) I/O connection timeout (implicit, CIP Class 1), 4 x RPI, 100 ms minimum Logix Producer/Consumer connection timeout (implicit, CIP Class 1), 4 x RPI, 100 ms minimum Safety I/O connection timeout (implicit, CIP Class 1), 4 x RPI (default)
Resiliency Protocols
Spanning Tree Protocol (STP), Rapid STP (RSTP), Multiple instance STP (MSTP) Stratix 8000 and Stratix 8300MSTP default Rapid Per VLAN Spanning Tree Plus (rPVST+); Cisco Technology Resilient Ethernet Protocol (REP); Cisco Technology EtherChannel Link Aggregation Control Protocol (LACP); IEEE Flex Links; Cisco Technology Device-level ring; topology option
Resiliency Protocol Mixed Vendor Ring Redundant Star Network Convergence > 250 ms Network Convergence > 70 ms Network Convergence > 1ms
STP RSTP MSTP PVST+ REP EtherChannel Flex Links DLR
X X X
X X X X X
X X X X X X X X X X X X
X X X X
41
Chapter 3
Spanning Tree Protocol (STP) and Rapid STP (RSTP)

Spanning Tree Protocol (STP) prevents loops on the network that occur when there is more than one open path active at once on the network. The convergence rate could take up to 50 seconds. Rapid Spanning Tree Protocol (RSTP) is designed for faster network convergence and eliminates the forwarding delay on point-to-point links by using explicit handshaking protocol. The convergence rate is significantly faster than STP: Only standard protocol for network resiliencyIEEE 802.1D Built into Stratix 8000 and Stratix 8300 switches Requires redundant star or ring topology Provides alternate path in case of failures, avoiding loops Unmanaged switches do not support STP or RSTP, or any other resiliency protocol
Distribution Switches Catalyst 3750 Switch Stack
Stratix 8000 Access Switches
F = Forwarding B= Blocking
42
Chapter 3
EtherChannel Protocol
The EtherChannel protocol combines multiple physical switch ports into one logical connection to increase bandwidth through load balancing, as well as physical connection redundancy. This protocol groups several physical Ethernet links to create one logical Ethernet link for the purpose of providing fault-tolerance and high-speed links between switches, routers, and servers. An EtherChannel can combine 28 active Fast Ethernet or Gigabit Ethernet ports: Link Aggregation Control Protocol (LACP) port aggregationIEEE 802.3ad Built into Stratix 8000 and Stratix 8300 switches Requires a redundant star topology Provides resiliency between connected switches if a connection is broken Fault-tolerance is a key aspect of EtherChannel. Should a link fail, the EtherChannel technology automatically redistributes traffic across the remaining links. This automatic recovery takes less than one second and is transparent to network applications and the end user. This makes it very resilient.
F = Forwarding
STP can be used with an EtherChannel. STP treats all the links as a single connection. Without the use of an EtherChannel, STP would effectively shutdown any redundant links between switches until one connection goes down. This is where an EtherChannel is most desirable, it allows full use of all available links between two devices.
43
Chapter 3
Flex Links Protocol

The Flex Links protocol provides link-level, physical redundancy in redundant star topologies. A pair of Layer 2 switchports ar configured to act as backup to each other: Built into Stratix 8000 and Stratix 8300 switches Requires redundant star topology Active/Standby Port Scheme Provides alternate path in case of failures, avoiding loops No bandwidth aggregation Recommend using equal speed ports Provides fast fail over for multicast traffic
A = Active S = Standby
44
Chapter 3
Resilient Ethernet Protocol (REP)

REP operates on chain of bridges called segments. A port is assigned to a unique segment. A segment can have up to two ports on a given bridge. REP is built in to Stratix 8000 and Stratix 8300 switches. REP supports closed and open rings in various topologies: Redundant networks can be built with REP segments Only ring resiliency protocol applicable to both Industrial and IT applications Ring recovery time is less than 70 ms for both unicast and multicast traffic in fiber implementations REP is a segment concept. A segment is a chain of bridges.
REP Segment REP Segment
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
Interfacef2 g1/2 Interface REP segment 10 rep segment 10
Interface g1/1 Interface f1 segment 10 repREP segment 10 Interface g1/2 Interface f2 segment 10 repREP segment 10
Interface g1/1 Interface f1 segment 10 repREP segment 10
When all links are operational, a unique port blocks the traffic on the segment. If any failure occurs within the segment, the blocked port goes forwarding.
Edge Port g1/2 Block Traffic Edge Port
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2 Link Failure
g1/1
g1/2
g1/2 Unblock
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
g1/1
g1/2
45
Chapter 3
Segments can be wrapped into a ring. Identification of edge ports requires additional configuration.
CC Blocking Blocking
YY AA XX C C Forwarding Forwarding Forwarding Forwarding B B
YY A A XX B B Link Failure Link Failure
46
Chapter 3
Device-level Ring (DLR)

The DLR protocol is a layer 2 protocol that provides link-level, physical redundancy that provides network convergence in the 13 ms range for simple automation device networks. The other resiliency protocols apply to infrastructure only (switches and routers). DLR provides resiliency directly to an end device directly (such as an I/O module, drive, or controller). Some control applications, such as safety and motion require network convergence times faster than what switch-oriented resiliency protocols can provide. Most control applications suffer connection timeouts with switchoriented resiliency protocols. A DLR network is a single-fault tolerant network. Network traffic is managed to ensure timely delivery of critical data.
ControlLogix Controller Forwarding Stratix 8000 IE Switch ETAP Announce Blocking Announce Beacon Active Ring Supervisor Beacon
POINT I/O Distributed I/O
ArmorPOINT I/O Distributed I/O
47
Chapter 3
Physical layer failure includes the following: All faults that are detectable at physical layer Physical layer failure detected by protocol-aware node Status message sent by ring node and received by ring supervisor
ControlLogix Controller Active Ring Supervisor ETAP Link Failure Link Status Link Status
Stratix 8000 IE Switch
POINT I/O Disrtributed I/O
Network convergence includes the following: After failure detection, ring supervisor unblocks blocked port Network configuration is now a linear topology Fault location is readily available via diagnostics
ControlLogix Controller Active Ring Supervisor
Stratix 8000 IE Switch
Forwarding
Forwarding
1783-ETAP
Link Failure
48
Chapter 3
Once ring is restored, the supervisor hears the beacon on both ports and transitions to normal ring mode by blocking one port.
ControlLogix Controller Stratix 8000 IE Switch
Forwarding
Beacon Announce ETAP
Active Ring Supervisor
Beacon Announce
Blocking
Internet Group Management Protocol (IGMP)
The IGMP is a communication protocol used to manage the membership of IP multicast groups. Much of EtherNet/IP implicit (I/O) messaging uses IP multicast to distribute I/O control data, which is consistent with the CIP produced/consumer model. Without IGMP, switches treat multicast packets the same as broadcast packets. That is, multicast packets are re-transmitted to all ports. The behavior of an unmanaged switch is to flood multicast packets to all ports within the same VLAN. This behavior is not typically desirable. To resolve this the following occurs: Querier functionality manages a table that lists the devices that are participating in multicast groups. Snooping functionality inspects packets from devices and only forwards multicast data to devices that request the data. IGMP snooping constrains the flooding of multicast traffic by dynamically configuring switch ports so that multicast traffic is forwarded only to ports associated with a particular IP multicast group. If you have a router (Layer 3 device) on the network, make it the querier. IGMP protocol has versions 1, 2, and 3. Rockwell Automation products support versions 1 or 2. IGMP protocol version 2 negotiates the active querier automatically and that task is assigned to the IGMP capable device with the lowest IP address on a given VLAN. Therefore, assign the first available IP address on a given VLAN to the router (Layer 3 device). If you do not have a router, the querier function should be placed on a centrally located IGMP capable device on the network by configuring it to the first available IP address on a given VLAN.
Rockwell Automation Publication ENET-RM002B-EN-P - April 2012 49
Chapter 3
Port Security
The switch has dynamic and static methods for limiting the MAC addresses (MAC IDs) that can access a given port.
Dynamic Secure MAC Address (MAC ID)

With Stratix 8000 and Stratix 8300 switches, the Smartport roles have a maximum number of MAC IDs that are allowed to use that port. For example, the Smartport role Automation Device sets up the port for a maximum of one MAC ID. The MAC ID is dynamic, meaning the switch learns the first source MAC ID to use the port. Attempts by any other MAC ID to access the port will be denied. If the link becomes inactive, the switch will dynamically relearn the MAC ID to be secured.
Smartport Role Automation Device Automation Device with QoS Desktop for Automation Switch for Automation Router I/P Phone + Desktop Access Point Port Mirroring None Number of MAC IDs, max 1 1 1 Not restricted Not restricted 3 Not restricted Not restricted Not restricted
Static Secure MAC Address (MAC ID)

With Stratix 6000, Stratix 8000, and Stratix 8300 switches, the other method of limiting MAC IDs is to statically configure a single MAC ID for a port. MAC IDs that are allowed to communicate on a given switch port become part of the saved configuration of the switch. This method provides strong security but requires reconfiguration whenever the device connected to the port is replaced, because the new device will have a different MAC ID from the old one. When you use RSLogix 5000 software to configure a Stratix 8000 and Stratix 8300 switch, you can use the static secure method. However, this method is not available with the Device Manager Web interface. For a Stratix 6000 switch the port security options are configured via the web browser or Logix5000 controller.
50
Chapter 3
Security Violations
In the event of a security violation with a Stratix 8000 or Stratix 8300 switch, one of these situations occurs: The maximum number of secure MAC addresses that have been configured for a port have been added to the address table, and a station whose MAC address is not in the address table attempts to access the interface. An address learned or configured on one secure interface is seen on another secure interface in the same VLAN. When a violation occurs, the port goes into the Restrict mode. In this mode, packets with unknown source addresses are dropped and you are notified that a security violation has occurred. An SNMP trap is sent, a syslog message is logged, and the violation counter increments. In the event of a security violation with a Stratix 6000 switch, the switch notifies the controller of the event (via an input bit) and the controller program decides how to proceed (such as shut that switch port down, send an alarm to the HMI, or shut the machine down). The switch does not make a decision on how to handle the security violation.
51
Chapter 3
Device Commissioning
There are multiple methods for assigning IP addresses. Switches on the product (such as thumbwheels, push buttons, or HIM modules) provide a static address that survive power cycles. Stratix switches support DHCP port allocation that is a hybrid solution for IP addressing as it allows for easy device replacement but is topology dependant.
Option Static
Description Devices hard-coded with an IP address Advantages: Simple to commission and replace Disadvantages: In large environments, can be burdensome to maintain Server assigns devices IP address Precursor to DHCP Advantages: Supported by every device Disadvantages: Requires technician to configure IP address/MAC address when a device is replaced Requires a PC for commissioning and replacement (unless there are switches to set the address offline) Adds complexity and point of failure Server assigns IP addresses from a pool (not recommended) Advantages: Efficient use of IP address range Can reduce administration work load Disadvantages: More complex to implement and adds a point of failure Devices get different IP addresses when they reboot Server assigns consistent IP addresses from a pool (not recommended) Advantages: Efficient use of IP address range Can reduce administration work load Disadvantages: More complex to implement and adds a point of failure Mixed environments may not work Automatically assign IP address per physical switch port Advantages: Efficient use of IP address range Eases maintenance and replacement in large environments Disadvantages: Requires some maintenance and upkeep on a per switch basis
Static via BOOTP configuration
DHCP
DHCP option 82
DHCP port-based allocation
52
Chapter
EtherNet/IP Protocol
The EtherNet/IP protocol is standard Ethernet and standard IP technologies with standard CIP technology at the application layer.
Topic Connections EtherNet/IP Network Specifications Packets Rate Capacity Requested Packet Interval (RPI) Messaging CIP Safety CIP Sync Integrated Motion on an EtherNet/IP Network Connectivity to IT Page 53 60 63 64 65 67 68 70 71
Connections
EtherNet/IP communication modules must consider connections and EtherNet nodes to communicate on the EtherNet/IP network. The number of supported nodes applies only to CompactLogix 5370 controllers; see page 59. A connection is a point-to-point communication mechanism used to transfer data between a transmitter and a receiver. Connections can be logical or physical. Two connection types--TCP connections and CIP connections--are layered over each other each time data is transferred. The TCP connection is the first connection established. It is used for all EtherNet/IP communication and is required for all CIP connection use. A single TCP connection supports multiple CIP connections and remains open. Established over TCP connections, EtherNet/IP CIP connections transfer data from an application running on one end-node (transmitter) to an application running on another end-node (receiver). CIP connections are configured to use explicit or implicit message types. The message types support connected and unconnected connection types. Typically, connected CIP messages are used to transfer data. Unconnected CIP are used but are only temporary.
53
Chapter 4
This graphic shows how connections are layered on each other when data is transferred over the EtherNet/IP network.
CIP Connection Types Your decisions when configuring your application determine the parameters of these connections. Connected Unconnected Connected
CIP Connection Message Types Explicit Implicit
You do not execute any tasks to establish these connections.
CIP Connection
TCP Connection
Remember these points when configuring your EtherNet/IP network application: All of the connections are used each time data is transferred on the EtherNet/IP network. You specify CIP connection message types and CIP connection types when configuring your application. For example, when a Logix5000 controller sends a MSG instruction to another Logix5000 controller, the transmitter sends the instruction to the receiver over a connection. That connection includes the following: a. A TCP connection is established. b. A CIP connection is layered on the TCP connection. c. An explicit or implicit CIP connection message is delivered via the CIP connection. d. If an explicit message type is used, it can be connected or unconnected. If an implicit message type is used, it is connected. Each EtherNet/IP communication module has TCP and CIP connection limits that you must account for when configuring your application. For more information on connection limits, see Table 8 on page 60. Refer to Nodes on an EtherNet/IP Network on page 59 for node count limitations for CompactLogix 5370 controllers.
54
Chapter 4
These example applications describe how connections are used. EXAMPLE I/O Connections A Logix5000 controller has five CIP I/O connections to modules in a remote chassis and all of these connections are through the same local 1756-EN2T module and the same remote 1756-EN2T module. The following connections exist: One TCP connection Five CIP connections
EXAMPLE
RSLinx OPC Test Client The following connections exist: One TCP connection Four CIP connections (four is the default)
Terminology
The terms in this table help you understand connections.
Table 6 - EtherNet/IP Connection Terminology
Term Producer and consumer Definition Producer/consumer refers to implicit connections. With implicit connections, messages are sent cyclically (every RPI). Example: Assume a ControlLogix controller is controlling a single rack of FLEX I/O using a rack connection. Both the ENBT module that is local to the controller and the FLEX AENT module are consumers and producers of data. The AENT consumes outputs and produces inputs. Client/server refers to explicit connections. A client creates a connection and initiates messages. A server provides a service or data. Clients can send messages continuously or intermittently. Example: A ControlLogix controller can send a MSG instruction to another controller.
Client and server
55
Chapter 4
Table 6 - EtherNet/IP Connection Terminology

Term Transports Definition Each connection has transports. A transport is a uni-directional entity with its own numeric identifier. An implicit connection has 2 transports. An explicit connection has 1 transport. Transports are important because they help you calculate the number of packets per second for each Ethernet interface. Example 1: I/O For an I/O connection to a rack of distributed I/O, a connection is configured in RSLogix 5000 software by adding the communication adapter and I/O modules in the I/O list. When the connection is created, output packets flow from the controller to the I/O rack. In addition, input packets flow from the I/O to the controller. Each direction of flow is a transport. In this example, two transports exist. One transport is from the controller to the adapter. The second transport is from the adapter to the controller. Example 2: Produced Tag For a multicast produced tag connection with two consumers, there is a connection to each consumer. Data from the producer is produced to the wire on one transport. Each of the consumers returns a heartbeat. A total of three transports exist in this example. One transport is from the tag producing controller to the wire media. The second transport is from one consumer to the tag producer. The third transport is from the second consumer. In the web servers, you can see references to Unconnected Message Manager (UCMM). This type of messaging is momentary and therefore can be ignored unless you are troubleshooting. Examples of where UCMM messages are used are: Update of module firmware Some functions in RSLinx software CIP Generic MSG instruction Opening any CIP connection (forward_open command)
UCMM
TCP Connections
TCP connections are used for all EtherNet/IP communication and are established before one device on the network transmits data to one or more devices on the network. EtherNet/IP communication modules use one TCP connection for each IP address to which the module is connected. TCP connections are automatically established before CIP connections are established because you can only establish CIP connections over a TCP connection. A single TCP connection supports multiple CIP connections. IMPORTANT EtherNet/IP communication modules also have web servers that use TCP connections for non-CIP traffic, such as HTTP. However, TCP connections used for non-CIP traffic do not count against the limits listed above.
56
Chapter 4
CIP Connections
CIP connections are automatically established over a TCP connection and transfer data from one device on the EtherNet/IP network to another. The following are examples of CIP connections: Logix5000 controller message transfer to Logix5000 controller I/O or produced tag Program upload RSLinx DDE/OPC client PanelView polling of a Logix5000 controller There are different CIP connections.
CIP Connection Bridged Description A bridged connection is a connection that passes through the EtherNet/IP communication module. The end point of the connection is a module other than the EtherNet/IP communication module. Example: An explicit connection from a controller through a 1756-EN2T module to another controller. An end-node connection is a connection whose end point is the EtherNet/IP communication module itself. Example: An explicit connection from RSLinx software to the EtherNet/IP communication module to set the module's IP address. A rack-optimized connections is an implicit message connection to a rack or assembly object in the EtherNet/IP communication module. Data from selected I/O modules is collected and produced on one connection (the rack-optimized connection) rather than on a separate direct connection for each module. This CIP connection is only available with digital I/O modules. An implicit message connection from a controller to an specific I/O module (as opposed to a rack-optimized connection). This CIP connection is available with analog and digital I/O modules.
End-node
Rack-optimized
Direct
IMPORTANT
CIP connections are further defined by these additional connection parameters: CIP Connection Message Types CIP Connection Types
CIP Connection Message Types

CIP connections use one of the following CIP connection message types: Implicit Explicit Implicit connections are time critical in nature. This includes I/O and produced/consumed tags. Implicit refers to information (such as source address, data type, or destination address) that is implied in the message but not contained in the message.
57
Chapter 4
Explicit connections are non-time critical and are request/reply in nature. Executing a MSG instruction or executing a program upload are examples of explicit connections. Explicit refers to basic information (such as source address, data type, or destination address) that is included in every message.
CIP Connection Types

CIP connection types determine how CIP connections transfer data on the network. The CIP connection types determine whether a connection is established between devices. If a connection is established between devices, the connection type determines if that connection remains open after data is transferred. There are two CIP connection types: Connected - Available with both implicit and explicit messages Unconnected - Available with only explicit messages This table describes how CIP connections are used with implicit and explicit messages.
CIP Connection Type Connected As Used with Implicit Messages The following events occur: 1. A connection is established between devices. 2. Data is transferred between devices. 3. The connection remains open for future data transmission. The following are examples of connected implicit messaging: I/O data transfer Produced/consumed tags between Logix5000 controllers Keep in mind the following points when using connected implicit messaging: Execution time is more efficient because the CIP connection between devices does not need to be reopened for each data transfer. EtherNet/IP communication modules support limited numbers of CIP connections. Because this connection remains open all the time, there is one fewer CIP connection available for other data transfer through the module. As Used with Explicit Messages The following events occur: 1. A connection is established between devices. 2. Data is transferred between devices. 3. The connection between the devices is closed. If data needs to be transferred again between these same two device, the connection must be reopened. The following are examples of connected explicit messaging: MSG instruction RSLinx Classic software setting the IP address for an EtherNet/IP communication module If you select a cached connection, the connection is not closed at the end of the transaction. Keep in mind the following points when using connected explicit messaging: Execution time is less efficient because the CIP connection between devices must be reopened for each data transfer. EtherNet/IP communication modules support limited numbers of CIP connections. Because this CIP connection is closed immediately after use, the CIP connection is immediately available for other data transfer through the module. In unconnected explicit messaging, no connection is established between devices. Data is sent in a packet that includes destination identifier information in the data structure but does not have a dedicated connection.
Unconnected
N/A
58
Chapter 4
Nodes on an EtherNet/IP Network

IMPORTANT This section applies only for CompactLogix 5370 controllers. For most applications, proceed to Table 8 on page 60 for network specifications.
CompactLogix 5370 controllers use the number of Ethernet nodes to stay within their capacity for the number of connections. These controllers have limits on the number of nodes they support in the I/O configuration section of your RSLogix 5000 software project. Any devices you add directly to the local Ethernet node in the I/O configuration are counted toward the controllers node limitation. The following are example devices that are added to the I/O configuration and must be counted: Remote communication adapters I/O modules directly connected to the EtherNet/IP network, for example the 1732E-IB16M12R ArmorBlock EtherNet/IP module Motion devices, such as drives You do not count Ethernet devices that exist on the EtherNet/IP network but are not added to the I/O configuration. These devices include the following: Computer HMI that are not added to the I/O configuration section, for example, PanelView Plus terminals MSG instructions that do not use an RPI and are not time-critical Devices like the CompactLogix 5370 controllers that communicate with by using a socket interface
Table 7 - CompactLogix 5370 Controller Ethernet Node Guidelines
Cat. No. 1769-L16ER-BB1B 1769-L18ER-BB1B 1769-L18ERM-BB1B 1769-L24ER-QB1B 1769-L24ER-QBFC1B 1769-L27ERM-QBFC1B 1769-L30ER 1769-L30ERM 1769-L30ER-NSE 1769-L33ER 1769-L33ERM 1769-L36ERM 32 48 16 8 Ethernet Nodes Supported 4
For more information, see the CompactLogix 5370 Controllers User Manual, publication 1769-UM021.
59
Chapter 4
EtherNet/IP Network Specifications

Table 8 - EtherNet/IP Network Specifications
Cat. No. Connections TCP 1734-AENT, 1734AENTR 1738-AENT, 1738AENTR 1756-ENBT 1756-EN2F 1756-EN2T, 1756EN2TR, 1756-EN2TXT, 1756-EN3TR 1756-EWEB 1768-ENBT 1769-L23Ex 1769-L3xE 1769-L16ER-BB1B 1769-L18ER-BB1B 1769-L18ERM-BB1B 1769-L24ER-QB1B 1769-L24ER-QBFC1B 1769-L27ERM-QBFC1B 1769-L30ER 1769-L30ERM 1769-L30ER-NSE 1769-L33ER 1769-L33ERM 1769-L36ERM 1783-ETAP 1783-ETAP1F, 1783ETAP2F 1794-AENT 2x-COMM-E 30 64 16 16 9500 400 N/A 50 Yes No 64 N/A N/A 48 N/A N/A 900 No 32 16 64 32(1) 64(2) 8 64 120 256 256 4 8 128(3) 64(3) 128 32(3) 2000 4000 6000 @ 500 bytes/packet 380 760 400 messages/s @ 20% comm. timeslice 32 + 32 64 128 128(3) 256(3) 64 + 64 128 + 128 IMPORTANT: Packet rates for ControlLogix EtherNet/IP communication modules depend on series and firmware revision. For more information, see Table 10 on page 62 N/A 5000 3200 Yes 32 CIP 20 CIP Unconnected Messages (backplane + Ethernet) 32 Ethernet Node Count, Max Packet Rate Capacity (packets/second)(4) I/O 5000 HMI and MSG 900 SNMP Support (password required) No
N/A
900 960
(1) The 1768-ENBT communication module supports 32 TCP connections when using firmware revision 1.x. (2) The 1768-ENBT communication module supports 64 TCP connections when using firmware revision 2.x or later. (3) CIP connections for this device can be used for all explicit or all implicit applications. For example, a 1756-ENBT module has a total of 128 CIP connections that can be used for any combination of connections. (4) Total packet rate capacity = 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.
60
Chapter 4
Table 9 - EtherNet/IP Network Specifications

Cat. No. Media Support Twisted Pair(1) 1734-AENT, 1734-AENTR 1738-AENT, 1738-AENTR 1756-ENBT 1756-EN2F 1756-EN2T, 1756-EN2TR, 1756-EN2TXT No Yes(2) Yes No 1756-EN2T - RSLogix 5000 software, version 16 1756-EN2TR - RSLogix 5000 software, version 17.01 1756-EN2TXT - RSLogix 5000 software, version 16 RSLogix 5000 software, version 18.00 N/A 32(3) N/A 32(3) N/A RSLogix 5000 software, version 16 N/A RSLogix 5000 software, version 17 RSLogix 5000 software, version 16 32 multicast Yes produced tags(3) 128 unicast produced tags Yes N/A No Yes No Yes No Revision 16 Revision 15 Revision 20.x N/A 32(3) RSLogix 5000 software, version 16 Yes See Table 10 on page 62 for details on these ControlLogix modules Yes(2) Fiber Produced/Consumed Tags Number of Multicast Tags, Max N/A Unicast Available Socket Integrated Services Motion on EtherNet/IP Axes No N/A Duplicate IP Detection (starting revision)
No
RSLogix 5000 software, version 18 or later
Revision 2.x - 1734-AENT Revision 3.x - 1734-AENTR Revision 2.x - 1738-AENT Revision 3.x - 1738-AENTR Revision 3.3 Revision 1.x
1756-EN3TR 1756-EWEB 1768-ENBT 1768-EWEB 1769-L23Ex 1769-L3xE 1769-L16ER-BB1B 1769-L18ER-BB1B 1769-L18ERM-BB1B 1769-L24ER-QB1B 1769-L24ER-QBFC1B 1769-L27ERM-QBFC1B 1769-L30ER 1769-L30ERM 1769-L30ER-NSE 1769-L33ER 1769-L33ERM 1769-L36ERM 1783-ETAP 1783-ETAP1F, 1783-ETAP2F 1794-AENT 2x-COMM-E Yes No N/A
Revision 3.x Revision 2.2 Revision 1.x
Up to 2 axes N/A
Up to 4 axes N/A Up to 4 axes N/A
Up to 8 axes Up to 16 axes N/A No N/A Revision 1.x Revision 2.x Revision 3.x Revision 1.1
(1) Most modules listed, with the exception of three fiber modules, support a speed duplex of 10/100. The 1756-EN2F, 1783-ETAP1F, and 1783-ETAP2F modules have a speed duplex of 100 only. (2) Module has two ports instead of one. With the second port, you can wire the module directly into a linear or device-level ring topology instead of connecting the network devices with an external managed switch. For more information on Embedded Switch Technology, see the EtherNet/IP Embedded Switch Technology Application Guide, publication ENET-AP005. (3) 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.
61
Chapter 4
This table lists additional specifications for some ControlLogix EtherNet/IP communication modules.
Table 10 - Additional ControlLogix EtherNet/IP Communication Module Specifications
Cat. No. Series Firmware Revision Any 2.x 3.6 or later B 1756-EN2T A 2.x or earlier 3.6 or later B 2.x 3.6 or later C 1756-ENT2TR A 2.x 3.6 or later B 1756-EN2TXT B 2.x 3.6 or later C 1756-EN3TR A 2.56 or later No 15.00 or later 18.00 or later
(1)
RSLogix 5000 Software Version 8.02 or later 15.00 or later 18.00 or later
(1)
RSLinx Software Version 2.30 or later 2.51 or later
Packet Rate Capacity (packets/ Support for second)(2) Extended Environment(4) I/O HMI/MSG 5000 10,000 25,000
(3)
Integrated Motion on EtherNet/IP Axes N/A N/A Up to 4 axes supported(5) Up to 8 axes supported(5)
1756-ENBT 1756-EN2F
Any A
900 3200
No
15.00 or later 18.00 or later(1) 15.00 or later 18.00 or later

(1)
10,000 25,000(3) 10,000 25,000(3)
N/A Up to 4 axes supported(5) N/A Up to 4 axes supported(5) Up to 8 axes supported(5)
17.01 or later 18.00 or later

(1)
2.55 or later 2.56 or later
10,000 25,000(3)
N/A Up to 4 axes supported(5) Up to 8 axes supported(5)
2.51 or later
10,000 25,000(3)
Yes
N/A Up to 4 axes supported(5) Up to 8 axes supported(5) Up to 255 axes supported(5)
(1) This version of RSLogix 5000 software is required to use CIP Sync technology, integrated motion on EtherNet/IP features, or Exact Match keying. (2) For more information on Packet Rate Capacity, see Packets Rate Capacity on page 63. (3) The packets rate capacity may change slightly depending on the specific firmware revision your EtherNet/IP communication module is using. For more information, see Packets Rate Capacity on page 63. (4) Module operates in a broad temperature spectrum, -2070 C (-4158 F), and meets ANSI/ISA-S71.04-1985 Class G1, G2 and G3, as well as cULus, Class 1 Div 2, C-Tick, CE, ATEX Zone 2 and SIL 2 requirements for increased protection against salts, corrosives, moisture/condensation, humidity, and fungal growth. (5) This value assumes the use of a 1756-L7x ControlLogix controller. If you are using a 1756-L6x ControlLogix controller, see ControlLogix Controllers User Manual, publication 1756-UM001.
62
Chapter 4
Packets Rate Capacity
Beginning with firmware revision 3.x for ControlLogix EtherNet/IP communication modules, packet rate capacity is increased. IMPORTANT Connection size impacts a modules increased packet rate capacity gained with firmware revision 3.x or later. Smaller connections are processed faster than larger connections. Larger connections can affect the increased packet rate capacity obtained with firmware revision 3.x or later. These example applications use larger connections: Applications using rack-optimized connections Applications using integrated motion on EtherNet/IP (only available with modules using firmware revision 3.x or later) Applications containing large produce/consume tag arrays Keep in mind that modules using firmware revision 3.x or later always have greater packet rate capacity than modules using firmware revision 2.x or earlier in the same application. Larger connections only impact how much greater the packet rate capacity is when using firmware revision 3.x or later.
EtherNet/IP Capacity Tool

The EtherNet/IP Capacity Tool is intended to help you in the initial layout of your EtherNet/IP network by calculating resources, for example, connections, packet rate capacity, used by a proposed network. Download the EtherNet/IP Capacity Tool at the Integrated Architecture Tools website. http://www.rockwellautomation.com/solutions/ integratedarchitecture/resources3.html#enetpredict IMPORTANT The EtherNet/IP Capacity Tool calculates a rough estimate of the packet rate capacity. Packet rate capacity varies depending on the specific conditions of each application. For a more detailed analysis of a proposed network, use RSNetWorx for EtherNet/IP software.
63
Chapter 4
Upgrade to Latest Firmware Revision

All ControlLogix EtherNet/IP communication modules must be upgraded to firmware revision 3.x or later to increase their packet rate capacity. You can upgrade your modules firmware regardless of series. Download the latest firmware revisions at the Rockwell Automation technical support website. http://support.rockwellautomation.com/ControlFlash/
Monitor Packet Sizes in Current Application

Some EtherNet/IP communication modules offer web pages that show module and application information. To view your modules information, type the modules IP address into your web browser. For more information on packet rate capacity on ControlLogix EtherNet/IP communication modules, see Article ID 66326, ControlLogix 1756-ENxxx V3.x performance increase FAQ, available from the Rockwell Automation Knowledgebase at http://www.rockwellautomation.com/support/americas/ index_en.html.
Requested Packet Interval (RPI)
The RPI is the update rate specified for a particular piece of data on the network. The RPI can be specified for an entire rack (using a rack-optimized connection) or for a particular module (using a direct connection). When adding a module to the I/O configuration of a controller, you must configure the RPI. This value specifies how often to produce the data for that module. For example, if you specify an RPI of 50 ms, every 50 ms the I/O module sends its data to the controller or that the controller sends its data to the I/O module. RPIs are used only for implicit connections, such as produced/consumed tags and I/O. For example, a local EtherNet/IP communication module does not require an RPI because it does not produce data for the system but acts only as a bridge to remote modules. Set the RPI only as fast as needed by the application. The CompactLogix 5370 controllers always attempt to scan an I/O module at the configured RPI rate. For guidelines on setting the RPI for the CompactLogix 5370 controllers, see the CompactLogix 5370 Controllers User Manual, publication 1769-UM021. The RPI also determines the number of packets per second that the module will produce on a connection. Each module has a limit on the total number of implicit packets per second. The total includes the sum of sent and received implicit packets. The packet rate capacity for implicit messages is for implicit only, and neither matches nor includes the explicit packet rate capacity.
64
Chapter 4
Messaging
The EtherNet/IP network supports both time-critical (implicit) and non timecritical (explicit) message transfer services of CIP. Exchange of time-critical messages is based on the producer/consumer model where a transmitting device produces data on the network and many receiving devices can consume this data simultaneously.
Implicit Messages
Implicit messages are time critical in nature. This includes I/O and produced/ consumed tags. Implicit refers to information (source address, data type, and destination address) which is implied in the message but not contained in the message. Examples of implicit applications include the following: Real-time I/O data Functional safety data Motion control data Implicit messages use the User Datagram Protocol (UDP) and can be unicast or multicast. Implicit messages transport data by using transport class 0/1 (Class 1): The data source/destination is an application object (Assembly object). There is no protocol in the message dataits all I/O data. Data transfer is more efficient because the meaning of the data is known ahead of time. Transfer is initiated on a time basis (cyclic trigger) or requested packet interval (RPI). Connection timing mechanism to alert application that the other side has stopped communicatingno heartbeat. Only connectedthere is no unconnected implicit messaging. An implicit message times out in: controller_multiplier x RPI. The multiplier is selected by the controller firmware so that the timeout is greater than or equal to 100 ms. The minimum multiplier is 4. These are examples: RPI = 2 ms; controller multiplier = 64. The timeout is 128 ms. RPI = 10 ms; controller multiplier = 16. The timeout is 160 ms.
65
Chapter 4
Explicit Messages
Explicit connections are non-time critical and are request/reply in nature. Executing a MSG instruction or executing a program upload are examples of explicit connections. Explicit refers to basic information (such as source address, data type, or destination address) that is included in every message. Each request is typically directed at a different data item. Examples of explicit applications include the following: HMI RSLinx connections Message (MSG) instructions Program upload/download Explicit messages use the Transmission Control Protocol (TCP). Explicit messages are used for point-to-point, client-server type transactions by using transport class 3 (Class 3): The Server side is bound to the Message Router object (has access to all internal resources) The Client side is bound to a client application object (has a need to generate requests to the Server) Uses an explicit messaging protocol in the data portion of the message packet Can be connected or unconnected
Device #1 Request Application Object Response Explicit Messaging Connection Explicit Messaging Connection Device #2 Request Response Application Object
An explicit message times out in 30 seconds. This is user-changeable in the Message (MSG) instruction structure.
66
Chapter 4
CIP Safety
CIP Safety is an extension to the application layer that provides a set of highly integrated safety services that leverage the underlying communication stacks of the standard CIP networks to transport data from a source to a destination. CIP Safety is certified to be compliant with the functional safety standard IEC 61508 up to safety integrity level (SIL) 3. The CIP Safety end-to-end protocol gives responsibility to ensuring safety to the end nodesrather than the bridges, routers, or intermediate nodes. CIP Safety cannot prevent communication errors from occurring, but if an error does occur in the transmission of data or in the intermediate router, the end device will detect the failure and take the appropriate action. Since the safety coding and not the underlying communication layers ensure the integrity of the data, the underlying communication layers can be interchanged and intermixed even across subnets. CIP Safety lets you mix standard and safety devices on the same open network.
Stratix
1791ES Guard I/O
1768 Compact GuardLogix
1783-ETAP Camera POINT Guard I/O POINT Guard I/O 1783ETAP Stratix 1738 ArmorPOINT I/O Stratix 1734 POINT I/O 1756 GuardLogix 1794 FLEX I/O 1768 CompactLogix PowerFlex 1783ETAP HMI
67
Chapter 4
CIP Sync
CIP Sync defines time synchronization services for CIP. Time synchronization on the EtherNet/IP network is a method to synchronize clocks across devices on the network. In a synchronized application, there is a single time master and multiple time slaves. For example, a ControlLogix controller can be configured to act as the time master and other ControlLogix modules, connected via EtherNet/IP communication modules, serve as the time slaves.
You can synchronize the clocks within the following applications: Multiple ControlLogix controllers ControlLogix redundancy systems Real world clocks Personal computer-based events
Time Master
Time Slave
Time Slave
Time Slave
68
Chapter 4
Typical time synchronized applications include the following: Input time stamping Events and alarms Sequence of Events recording First fault detection Time scheduled outputs Integrated motion on EtherNet/IP drive synchronization Distributed motion control CIP Sync a time synchronization extension to the application layer can help solve these application requirements. CIP Sync is based on the IEEE 1588 (IEC 61588) standardPrecision Clock Synchronization Protocol for Networked Measurement and Control Systems, commonly referred to as the Precision Time Protocol (PTP). The protocol provides a standard mechanism to distribute Coordinated Universal Time (UTC) across a standard Ethernet network of distributed devices. By time stamping in UTC events can easily be compared across time zones without having to be adjusted for the geography in which they were generated. CIP Sync lets users base control on true time synchronization rather than the more limited event synchronization model used historically. Using a 100 Mbps switched Ethernet system, advanced testing shows CIP Sync can deliver time synchronization accuracy of less than 500 ns between devices, meeting the requirements of some of the most demanding real-time applications.
69
Chapter 4
Integrated Motion on an EtherNet/IP Network
Integrated motion on an EtherNet/IP network sets the EtherNet/IP networking technology apart from the other industrial Ethernet networks. EtherNet/IP modules with integrated motion on the EtherNet/IP network combine the requirements of deterministic real-time motion control applications with standard unmodified Ethernet that provides full compliance with the Ethernet standards IEEE 802.3 and TCP/IP. This allows the use of standard Ethernet components and infrastructure without the use of special switches or gateways.
Stratix
1791ES Guard I/O
1768 Compact GuardLogix 1783-ETAP
Camera
POINT Guard I/O
1756 Controller 1783ETAP 1783ETAP
Stratix 1738 ArmorPOINT I/O Stratix PowerFlex
1734 POINT I/O 1756 Controller Kinetix
Kinetix
Integrated motion on the EtherNet/IP network accomplishes this by encompassing a set of application profiles designed to allow position, speed and torque loops to be set in the drive. With the addition of the CIP Sync technology multiple axes can be coordinated for precise, coordinated motion control applications. Integrated motion on the EtherNet/IP network uses time-stamped data along with its simple timing model to eliminate hard synchronization constraints between the drive and the controller. Real-time data values are adjusted at the end device at the time the data is applied; no need to hard schedule the network traffic. In addition, integrated motion on the EtherNet/IP network has the flexibility to handle different types of drives and time synchronization requirements. The same network connection can be used for both a high performance servo drive with precise synchronization requirements, and a low performance Volts/Hertz drive with no time synchronization capability.
70
Chapter 4
Connectivity to IT
While IT and controls engineers are often managed separately and given separate job performance goals, those goals are beginning to align because the availability of information is crucially important in both roles. Some companies are beginning to form hybrid groups and hire individuals with experience in both areas to form policies, guidelines, and procedures for design and maintenance of a common network architecture.
IT Network Protect intellectual property and company assets 1. Confidentiality 2. Integrity 3. Availability Converged network of data, voice, and video Strict network authentication and access policies Continues to operate Shut down access to detected threat As soon as possible During uptime Controls Network 24/7 operations High overall equipment effectiveness 1. Availability 2. Integrity 3. Confidentiality Converged network of data, control, information, safety, and motion Strict physical access Simple network device access Could stop operation Potentially keep operating with a detected threat Scheduled During downtime
Security Policies Focus Priorities
Types of data traffic Access control Implications of a device failure Threat protection Upgrades
Enterprise Business Systems
Level 4 Data Center
IT Network Industrial Network Level 3 - Site Operations FactoryTalk Application Servers FactoryTalk Services Platform Data Servers
DIO Stratix 8000 Layer 2 Switch HMI DIO Controller Filling Cell/Area Zone Levels 0-2 Ring Topology Device Level Ring Camera Controller Processing Cell/Area Zone Levels 0-2 Ring Topology Resilient Ethernet Protocol (REP)
HMI Controller
HMI
Drive
Drive DIO Material Handling Cell/Area Zone Levels 0-2 Bus/Star Topology
Drive
71
Chapter 4
Notes:
72
Chapter
Predict System Performance
This chapter describes how to predict the performance of your EtherNet/IP network-based control system and how to enhance that performance
Topic System Prediction Goals Performance Calculations Example: Predict System Performance Page 74 77 84
IMPORTANT
This chapter explains how to calculate system performance by using data from your system in specific equations. However, you can also use the EtherNet/IP Capacity Tool, an online tool, to predict system performance. The EtherNet/IP Capacity Tool and the IAB Tool are intended to help you in the initial layout of your EtherNet/IP network by calculating resources, for example, connections, packet rate capacity, used by a proposed network. Download the EtherNet/IP Capacity Tool at the Integrated Architecture Tools website: http://www.rockwellautomation.com/solutions/ integratedarchitecture/resources3.html#enetpredict. The EtherNet/IP Capacity Tool calculates a rough estimate of the packet rate capacity. Packet rate capacity varies depending on the specific conditions of each application. For a more detailed analysis of a proposed network, use RSNetWorx for EtherNet/IP software.
73
Chapter 5
System Prediction Goals
You allocate the bandwidth of your EtherNet/IP communication module between two types of messaging.
Messaging Type Explicit messaging Description Explicit messages are connections that do not use an RPI. Some examples of explicit messaging includes: MSG instructions HMI communication RSLogix 5000 software uploads and downloads Implicit messages are connections that use an RPI. Implicit messaging is used for I/O data exchanges, including: Rack-optimized connections(1) Direct connections Produced/consumed tags
Implicit messaging
(1) Available with digital I/O modules only.
The performance predictions have two major goals: Determine if the system as a whole has sufficient bandwidth and connections to meet application requirements. Estimate the maximum input or output times for rack-optimized connections, direct connections, and produced/consumed tags.
74
Chapter 5
Part One: Determine If System Has Sufficient Bandwidth to Meet Application Requirements
Part One
Start Step 1: Draw Your System
To determine if your system has sufficient bandwidth to fulfill the requirements of the application, complete the following steps. 1. Draw an overall sketch of your system that includes all of the following: Logix5000 controllers EtherNet/IP communication modules I/O modules All connections to the network Include a description of what the controllers are doing, for example, messaging using produced tags, and any known RPI requirements. 2. Identify and count each type of implicit connection for the system and each EtherNet/IP communication module. 3. Use the formulas provided later in this chapter to calculate the packet rate capacity loading on each EtherNet/IP communication module and the available bandwidth for any unspecified RPIs. 4. Based on the results of these calculations, decide if your system will work. 5. If necessary, modify your system by doing one or more of the following: For ControlLogix EtherNet/IP communication modules, upgrade to newer series and/or firmware revision. For example, the 1756-EN2T/A module, firmware revision 2.x or earlier module supports 10,000 pps. However, the 1756-EN2T/A module, firmware revision 3.6 or later module supports 25,000 pps. Increase some RPIs to allow other RPIs in the system to decrease. Change connection types, for example, direct to rack-optimized. Change I/O module configurations, such as filter times, trigger types. Add EtherNet/IP communication modules. Add Logix controllers. Verify that the network infrastructure can handle the system traffic. TIP We recommend your applications EtherNet/IP links are no more than 60% utilized and QoS is implemented. Typically, these conditions support most EtherNet/IP applications.
Step 2: Identify and Count Connections
Step 3: Calculate
No Step 5
Step 4 or 6: Does System Work?
Yes
Part Two
Step 7: Estimate Max Times
Go to Part Two Steps described on page 76.
Yes
Step 8: More Throughput Needed?
No
Done
Verify that the switches support full-duplex operation and IGMP snooping. Port-mirroring is also important for switch and system diagnostic functions. 6. If you have to make modifications, verify that the modified system will work by recounting the connections and recalculating the packet rate capacity loading.
75
Chapter 5
Part Two: Predict Maximum input or Output Times for CIP Connections
A CIP connection is an efficient communication path used for high performance. The following are basic types of CIP connections: Rack-optimized Data - input or output Produced tag A CIP connection is bi-directional. During every RPI, each end of a connection initiates a packet of information. A packet of information represents a connection. The type of data packet produced by each end of the connection depends on the connection type as described below.
Connection Type Rack-optimized Input data Output data Produced tag Scanner Output data Heartbeat Output data N/A Adapter Input data Input data Output data echo N/A Producer Controller N/A N/A N/A Tag data Consumer Controller N/A N/A N/A Heartbeat
To predict the maximum input (I/O to controller) or output (controller to I/O) times for CIP connections, complete the following steps. 1. Estimate the maximum time intervals for each CIP connection types used in the control system. 2. If necessary, modify your system to get more throughput by performing one or more of the adjustments described under step 5 on page 75. 3. If you have made modifications, verify that the modified system will work by re-counting the connections and re-calculating the packet rate capacity loading.
76
Chapter 5
Performance Calculations
Logix5000 controllers are similar by using packets/second and the number of connections for predicting system performance. However, CompactLogix 5370 controllers use the number of Ethernet nodes to stay within their capacity for the number of connections.
CompactLogix 5370 Controller Example

As shown in the illustration below, the 1769-L16ER-BB1B controller supports a maximum of four nodes. Therefore, any additional node, such as a 1734 Ethernet adapter, cannot be added to our example EtherNet/IP network. Use the supported node chart on page 59 and the EtherNet/IP Capacity Tool to simplify calculating system resources for your CompactLogix 5370 network.
1769-L164ER-BB1B 1756-EN2T 1756 I/O Modules
1794-AENTR FLEX I/O Adapter
Stratix Switch 1794-AENT 1794 I/O Modules PowerFlex Drive
1734-AENT 1734 I/O Modules
45908
The devices you add directly to the local Ethernet node in the I/O configuration section of your RSLogix 5000 software project are counted toward the 1769-L16ER-BB1B controllers node limitation.
77
Chapter 5
While you can use the EtherNet/IP node count to select a CompactLogix 5370 controller for your network requirements, most applications use three sets of calculations to determine performance: Identify and Count Connections Calculate Packets/Second Estimate Maximum Input or Output Times for CIP Connections
ControlLogix Controller Example

This example control system includes these connections: The 1756-L73 controller in the local chassis producing one tag that the 1756-L73 controller in the remote chassis consumes The produced/consumed tags between the local and remote 1756-L73 controllers use an RPI = 20 ms One rack-optimized connection between the local controller and the remote digital I/O modules at an RPI = 20 ms One direct connection to each remote analog I/O module at an RPI = 50 ms. IMPORTANT Each 1756-EN2T communication module in the example control system is series A, firmware revision 2.003. For 1756 communication modules, series level and firmware revision determine the maximum packet rate capacity. For more information, see Table 9 on page 61.
Figure 2 - Example ControlLogix System over an EtherNet/IP Network

Local ControlLogix Chassis Remote ControlLogix Chassis
1756-L73
1756-EN2T
1756-L73
1756-EN2T
2 Analog I/O Modules
3 Digital I/O Modules
You also can use the EtherNet/IP Capacity Tool described on page 63 to make performance predictions.
78 Rockwell Automation Publication ENET-RM002B-EN-P - April 2012
Chapter 5
Identify and Count Connections

Use your design to identify and count the total number of these connections for each EtherNet/IP communication module in your system. Performance prediction is done on a CIP connection basis. This table describes how to count connections for an EtherNet/IP communication module, regardless of whether it is in a local or remote chassis.
Connection Type Produced tag between controllers Consumed tag between controllers Rack-optimized connections Direct connections Count Calculation Method Number of consumers Number of tags consumed Number of chassis to which the controller is making a rack-optimized connection Number of devices to which the controller is making a direct connection, such as drives or I/O modules
IMPORTANT
The table above is used to calculate connections used by an EtherNet/IP communication module. To calculate connections used on a Logix5000 controller, see Logix5000 Controllers Produced and Consumed Tags Programming Manual, publication 1756-PM011.
Use this table to count the connections for the EtherNet/IP communication module in the example system shown on page 78.
Communication Module Local 1756-EN2T communication module Connection Type Produced tag between controllers Total 1 (Number of consumers) Rack-optimized connections to digital I/O modules Direct connections to analog I/O modules 1x1=1 (Number of chassis to which a rack-optimized connection is made x Number of rackoptimized connections made to the chassis) 2x1=2 (Number of remote analog modules to which a direction connection is made x Number of connections per remote analog module) 1 (Number of tags consumed) 1x1=1 (Number of chassis to which a rack-optimized connection is made x Number of rackoptimized connections made to the chassis) 2 x 1= 2 (Number of remote analog modules to which a direction connection is made x Number of connections per remote analog module)
Remote 1756-EN2T communication module
Consumed tag between controllers Rack-optimized connections to digital I/O modules Direct connections to analog I/O modules
Each 1756-EN2T communication module in the example system uses four connections.
79
Chapter 5
Calculate Packets/Second
All EtherNet/IP communication modules have a packet rate capacity, that is, maximum number of packets/second it can send. You must calculate the number of packets/second that each EtherNet/IP communication module in the control system is sending when predicting system performance. The number of packets/second an EtherNet/IP communication module sends in a control system depends on the number of each CIP connection type being sent and the RPI for that connection.
CIP Connection Type(1) Produced/consumed tags(2) Packets/Second Calculation Method At producer: (1 + number of connections)/RPI for each produced tag At consumer: 2/RPI for each consumed tag Rack-optimized connection Direct connection (2 x number of connections)/RPI (2 x number of connections)/RPI
(1) This method applies when application conditions are configured such that the heartbeat connection RPI equals the produced tag RPI. With RSLogix 5000 software, version 16 and later, the heartbeat RPI can be configured to a value different from the produced tag RPI. This option decreases the bandwidth utilization on resources, such as the EtherNet/IP communication module or controller. For more information see Knowledge For more information, see Rockwell Automation Knowledgebase article # 38535. You can access the Knowledgebase at http://www.rockwellautomation.com/knowledgebase/. (2) Producer and all consumers are in different chassis and operate at a uniform RPI.
For each EtherNet/IP communication module, the total is the sum of the above calculations. This total should not exceed the recommended 90% limit. We recommend you allocate bandwidth as follows: Reserve 10% of each EtherNet/IP communication modules packet rate capacity to allow for processing of explicit messages. IMPORTANT If you do not reserve at least 10% of each EtherNet/IP communication modules bandwidth, you might not be able to go online with RSLogix 5000 software or be able to access the EtherNet/IP communication modules embedded web server. To remedy this situation, remove the EtherNet/IP communication modules from one or more chassis to reduce the EtherNet/IP network traffic in the overloaded EtherNet/IP communication modules. Then go online with RSLogix 5000 software to reconfigure the RPIs to a less frequent (slower) rate.
The total for implicit messaging should not exceed 90% of capacity for each EtherNet/IP communication module.
80
Chapter 5
Use this table to count the total packets/second sent for each EtherNet/IP communication module in the example system shown on page 78.
Communication Module Local 1756-EN2T communication module Connection Type Produced tag between controllers Rack-optimized connections Direct connections Packets/Second (1 + 1)/20ms = 100 (2 x 1)/20ms = 100 (2 x 2)/50ms = 80 Module total packets/second = 280(1) Remote 1756-EN2T communication module Consumed tag between controllers Rack-optimized connections Direct connections 2/20ms = 100 (2 x 1)/20ms = 100 (2 x 2)/50ms = 80 Module total packets/second = 280(1)
(1) A 1756-EN2T/ A module, firmware revision 2.003 has a packet rate capacity = 10000 packets/second. When sending 280 packets/second, the module in the example system uses approximately 3% of its packet rate capacity, well below the recommended maximum of 90% of the modules packet rate capacity.
In addition to the configurable RPI parameter, you control system includes the Actual Packet Interval (API). The API is the actual time that requested data is delivered. The relationship between the RPI and API in your system depends on the controller initiating the communication. In general, these controller types calculate the API as follows: ControlLogix: API = RPI 1768 CompactLogix: API = RPI CompactLogix 5370 controllers, SoftLogix: API = RPI 1769-L23Ex, 1769-L3xE: API = 2n (where 2n is a value that is a power of 2, for example, 2, 4, or 8, that is equal to or faster than the RPI you configured) IMPORTANT In most cases, you can get data faster than the RPI you configured. This increased data transmission rate can increase the number of packets to be more than you expected based on the RPI. Therefore, the percentage of the EtherNet/IP communication modules packet rate capacity used may be slightly higher than expected.
81
Chapter 5
Estimate the Fastest RPI

The fastest RPI for an EtherNet/IP communication module is calculated with this formula: RPI(Fastest) = (2 x connections)/pps IMPORTANT It is not necessary to operate at the fastest RPI.
Example One
A 1756-EN2T module, firmware revision 3.6 or later, supports 25,000 pps. If there are only 40 connections that are all at the same RPI, the fastest RPI is the following: RPI(Fastest) = (2 x 40)/25,000 = 3.2 ms
Example Two
Assume there are 23 connections already running at an RPI of 2 ms on a 1756EN2T module, firmware revision 3.6 or later, that supports 25,000 pps. These connections are already using some of the communication packets: pps = (2 x 23)/0.002 = 23,000 pps The fastest RPI possible for a fourth connection is the following: RPI(Fastest) for 4th connection = (2 x 1)/(25,000-23,000) = 1 ms The same concept can be used for produced tags and consumed tags by replacing the (2 x connections) with (1 + connections) for produced tags or (2/RPI) for consumed tags.
82
Chapter 5
Estimate Maximum Input or Output Times for CIP Connections

System response is dependent on several factors. These are the dominant factors: RPI value Number of implicit CIP connections. To simplify, the response time of a connection can be approximated with only the RPI. The maximum input (I/O to controller) or output (controller to I/O) times for implicit CIP connections can be estimated as follows: Rack-optimized: 1 RPI Direct Connect: Digital = 1 RPI Analog (nonisolated) = 2 RTS (Real Time Sampling rate) Analog (isolated) = 1 RTS Produced/Consumed Tag = 1 RPI The above response times are estimates. For more accurate numbers, include system delays, as described in Refine Estimates on page 93.
83
Chapter 5
Example: Predict System Performance
This example ControlLogix system has the following components: IMPORTANT The information in the remainder of this section shows how to compute system performance by using ControlLogix controllers.
1756-L73 controller in chassis 1 that executes these tasks: Produces a tag that 1756-L73 controllers, in chassis 2 and 3 respectively, consume at an RPI = 20 ms Controls remote I/O in chassis 48 1756-L73 controllers in chassis 2 and 3 consuming a tag from the controller in chassis 1 Eight 1756-EN2T/A communication modules, firmware revision 2.003, one module in each chassis 15 digital I/O modules using rack-optimized connections at RPI = 20 ms, 3 modules in each chassis 48 Fifteen analog I/O modules, across five remote chassis, using direct connections at an RPI = 50 ms, three modules in each chassis 48 PanelView Plus terminal with a direct connection to an array of 40 tags at an RPI = 100 ms and an explicit connection to an array of 100 tags sent every 300 ms Workstation running FactoryTalk View SE software, requiring explicit messaging of an array of 1500 tags every 100 ms. This workstation also connects to the company Intranet
84
Chapter 5
Determine If System Has Sufficient Bandwidth to Meet Application Requirements

Based on the system requirements, the initial network diagram is shown below:
Chassis 1 1756-L73 Controller 1756-EN2T Module 1 One Produced Tag Workstation with RSView Chassis 2 1756-L73 Controller 1756-EN2T Module 2 One Consumed Tag Chassis 3 1756-L73 Controller 1756-EN2T Module 3 One Consumed Tag
To Company Intranet Switch
Chassis 4 1756-EN2T Module 4 Three Analog I/O Modules Three Digital I/O Modules
PanelView Plus Terminal
IMPORTANT: Each chassis with three analog and three digital I/O modules, that is, chassis 48, uses these connections: Three direct connections (one for each analog I/O module in the chassis) One rack connection (one for all digital I/O modules in the chassis)
85
Chapter 5
Explicit Messaging
The RSView and PanelView Plus messages are explicit messages. Reserve 10% of the bandwidth of the EtherNet/IP communication module for explicit messaging.
EtherNet/IP Interface 1756-ENBT 1756-EN2F 1756-EN2T 1756-EN2TR 1756-EN2TXT 1756-EN3TR Total Bandwidth 5000 pps The pps for these modules depends on the modules series and firmware revision. The modules support this pps: Series A, firmware revision 2.x or earlier = 10,000 pps Series A or later, firmware revision 3.6 or later= 25,000 pps For more information on the pps supported by these modules, see Table 8 on page 60. 5000 pps 2000 pps 4000 pps 6000 pps 10% Reserve for Explicit Messaging 500 pps One of the following: Series A, firmware revision 2.x or earlier = 1000 pps Series A or later, firmware revision 3.6 or later= 2500 pps
1768-ENBT 1769-L23Ex 1769-L32E 1769-L35E 1769-L30ER 1769-L30ERM 1769-L30ER-NSE 1769-L33ER 1769-L33ERM 1769-L36ERM 1769-L24ER-QB1B 1769-L24ER-QBFC1B 1769-L27ERM-QBFC1B 1769-L16ER-BB1B 1769-L18ER-BB1B 1769-L18ERM-BB1B 1788-ENBT 1734-AENT 1794-AENT
500 pps 200 pps 400 pps 600 pps
5000 pps 5000 pps 9500 pps
500 pps 500 pps 950 pps
Explicit messaging throughput is also dependent upon network availability and target availability. Therefore, reserving 10% of the total bandwidth does not guarantee throughput. Next determine if each EtherNet/IP communication module has enough bandwidth to handle the implicit messaging.
86
Chapter 5
EtherNet/IP Module Serving as a Scanner

EtherNet/IP module 1 functions as a scanner.
1756-EN2T Module 1
EtherNet/IP module 1, in the chassis with the main controller, must perform these tasks: Communicate with five remote I/O chassis. The EtherNet/IP module connects to the I/O modules in each chassis this way: One rack-optimized connection to digital I/O modules at an RPI = 20 ms Three direct connections to three analog I/O modules at an RPI = 50 ms Communicate with the PanelView Plus terminal via direct connections at an RPI = 100 ms Communicate with the two other controllers by using a produced tag at an RPI = 20 ms Perform explicit messaging
87
Chapter 5
Fill in the worksheet for this module as follows. EtherNet/IP Module ID: 1 Rack-optimized Connections 5 @ 20 ms (for digital I/O modules) = (2 x connections)/RPI = (2 x 5)/ 20 ms = Direct Connections 15 @ 50 ms (for analog I/O modules) = (2 x connections)/RPI = (2 x 15)/ 50 ms = Produced Tag Connections 2 @ 20 ms = (1 + connections)/RPI for each produced tag = (1 + 2)/ 20 ms = Consumed Tags 0 = 2/RPI for each consumed tag = Total Packets Per Second N/A 1250 150 600 500
The total of 1250 is well within the 1756-EN2T/A modules, firmware revision 2.003, remaining bandwidth of 9000 pps. The total of 22 CIP connections is well within the 1756-EN2T/ A modules, firmware revision 2.003, capacity of 256 CIP connections.
PanelView Plus/FactoryTalk View Connection Considerations

PanelView Plus terminals and workstation with FactoryTalk View software use RSLinx Enterprise software for communication with a Logix controller. RSLinx Enterprise software can open 25 CIP connections to a single Logix-based controller, based on the number of tags currently on scan. RSLinx Enterprise software opens up to four CIP connections for tag reads, based on the volume of tags requested. If a small number of tags are on scan at one time, for example, 80 DINT tags, only one CIP connection is opened. If a larger number of tags are currently on scan, for example, 320 DINT tags, four CIP connections are opened for reads. Only a single CIP connection is opened for all tag writes. For more information on determining the number of CIP connections required by a given application, see Rockwell Automation Knowledgebase article 39366. You can access the Knowledgebase at http://www.rockwellautomation.com/ knowledgebase/.
88
Chapter 5
EtherNet/IP Modules Functioning as Adapters

EtherNet/IP modules 48 function as adapters.
1756-EN2T Module 4
1756-EN2T Module 5
1756-EN2T Module 6
1756-EN2T Module 7
1756-EN2T Module 8
Each EtherNet/IP module functioning as an adapter in an I/O chassis, that is, 1756-EN2T EtherNet/IP communication modules 48 in the example on page 85, has these connections: One rack-optimized connection for digital I/O modules in its chassis. The digital I/O has a required RPI = 20 ms Three direct connections for analog I/O modules in its chassis. The analog I/O has a required RPI of 50 ms.
89
Chapter 5
For example, use the worksheet in Appendix A for each of the five EtherNet/IP modules as follows. EtherNet/IP Module ID: 4 - 8 Rack-optimized Connections 1 @ 20 ms = (2 x connections)/RPI = (2 x 1)/ 20 ms = Direct Connections 3 @ 50 ms = (2 x connections)/RPI = (2 x 3)/ 50 ms = Produced Tag Connections 0 = (1 + connections)/RPI for each produced tag = Consumed Tags 0 = 2/RPI for each consumed tag = Total Packets Per Second N/A 220 N/A 120 100
The total pps of 220 is well within the 1756-EN2T/A modules, firmware revision 2.003, remaining bandwidth of 9000 pps.
EtherNet/IP Modules 2 and 3 with Consumed Tags

EtherNet/IP modules 2 and 3 interface two consumer controllers to the network.
1756-EN2T Module 2 1756-EN2T Module 3
90
Chapter 5
Each of these controllers consumes one produced tag at an RPI = 20 ms. Either of these EtherNet/IP modules uses these connections. EtherNet/IP Module ID: 2 or 3 Produced Tag Connections 0 = (1 + connections)/RPI for each produced tag = Consumed Tags 1 tag @ 20 ms = 2/RPI for each consumed tag = 2/20 ms = Total Packets Per Second 100 100 N/A
The total of 100 pps is well within the 1756-EN2T/A modules, firmware revision 2.003, remaining bandwidth of 9000 pps.
Recommendations to Achieve More Throughput in an Existing Control System

Unlike the configuration of the last example control system, some control system configurations do not initially have enough bandwidth to achieve the desired throughput. If you determine your control system does not have the bandwidth to achieve the desired throughput, you need to modify your system. We recommend that you use one of these tasks described in step 5 on page 75, to increase system throughput.
91
Chapter 5
Estimate the Maximum Input or Output Times for CIP Connections

Calculate the worst-case, maximum input (I/O to controller) or output (controller to I/O) times for CIP connections in your system. For a Rack-optimized Connection, the maximum input or output time for a CIP connections is estimated as follows: TMAX (Rack-optimized) = RPI = 20 ms For the Direct Connect Analog Modules, assume non-isolated modules with the real-time sampling (RTS) rate equal to the RPI, that is, 50 ms. Therefore, the maximum input or output time is estimated as follows: TMAX (Analog Non-Isolated) = 2RTS = 2 x 50 ms = 100 ms Isolated modules have an RTS rate of 1RTS. For a Produced or Consumed Tag , the maximum input or output time is estimated as follows: TMAX (Produced/Consumed Tag) = 1RPI = 1 x 20 ms = 20 ms Assume that these times are acceptable for the example application. If you find that the times for your system are too slow, you can make adjustments to operate at faster RPIs. This may require selecting I/O modules that operate at faster data rates, adding more EtherNet/IP communication modules, and/or other changes as outlined in step 5 on page 75. No further modifications have been made, so the system is complete.
92
Chapter 5
Refine Estimates
To further increase the accuracy of these times, include considerations for system delays. For a Rack-optimized Connection, to the RPI, add these delays: TMAX (Rack-optimized) = input filter + RPI + transmission + switch + queue See the table for descriptions of delay types with a rack-optimized connection.
Type of Delay Input Filter Description Discrete input modules have filters. The default for a 1756 discrete I/O module is 1 ms. For The default for a FLEX discrete I/O module is 0.25 ms. input delay = 1 ms There are no filters for outputs, so there is no additional delay for outputs. Outputs are always sent using an RPI timer. The transmission delay is the interval of time that it takes a packet to be transmitted at a specific bit rate, for example, 100 Mbps. For example, in a 7-slot ControlLogix chassis, the size of the entire packet is approximately 122 bytes (including header, all protocols, all data, and CRC). At 100 Mbps, this packet takes approximately 10 microseconds. (0.01 ms) on the wire. transmission delay = 0.01 ms x (number of CIP connections) Switch latency is the delay between reception of the first bit and transmission of the first bit. This delay depends on the type of switch. It is typically 0.1 ms. switch delay = 0.1 ms Input data is sent from the remote rack (adapter), through a switch, through a communication module in the controller rack, and finally to a controller (scanner). If two or more input CIP connections are simultaneously ready to be transmitted, they must be transmitted sequentially. It takes 0.2 ms for a 1756-ENBT to process 1 implicit packet. Note that 0.2 ms is equal to the reciprocal of 5000 (pps). The total queue delay is 0.2ms times the number of CIP connections through the module. queue delay = 0.2 ms X (number of CIP connections)
Transmissions
Switch
Queue
For the Direct Connect Analog Modules, you add the same transmission, switch, and queue delays as for rack-optimized data: TMAX (Analog Non-Isolated)= 2RTS + transmission + switch + queue For a Produced or Consumed Tag , you add the same transmission, switch, and queue delays as for rack-optimized data: TMAX (Produced/Consumed Tag)= 1RPI + transmission + switch + queue
93
Chapter 5
Notes:
94
Index
A
address dynamic secure MAC 50 gateway 15 gateway default 15 resolution protocol (ARP) 33 static secure MAC 50 application bandwidth 75, 84 ARP definition 33 autonegotiation 27 connections 53 calculate CIP delays 93 calculate CIP times 92 CIP 57 direct 57 predict CIP times 76, 83 rack-optimized 57 TCP 56 connectivity 71 consumed tags 90 consumer 55 converters media 24 count connections 79 EtherNet/IP nodes 59
B
bandwidth 75, 84 determination 75 explicit message 86 bridge media 24 network communication 18 broadcast 30
D
default gateway address 15 definition CIP 12 delay times 93 determining bandwidth 75 device commissioning 52 -level ring definition 47 topology 21 direct connections 57 DLR definition 47 topology 21 DNS definition 34 domain name system (DNS) 34 dynamic secure MAC address 50
C
calculate packets per second 80 packets/second 80 system performance 77 capacity packet rate 63 tool 63 CIP connections 57 calculate delays 93 calculate times 92 maximum 76 predict times 76, 83 types 58 definition 12 safety 67 sync 68 client and server 55 commissioning device 52 communication module specifications 62 network bridge 18 components Ethernet infrastructure 19 switches 26 configuration requirements 13
E
equations 77 estimate RPI 82 times for CIP connections 83 EtherChannel protocol 43 Ethernet infrastructure 19 media 22 topologies 19
95
Index
EtherNet/IP network adapters 89 capacity tool 63 communication modules 17 definition 11 integrated motion 70 module features 60 node count 59 overview 11 protocol 53 scanners 87 specifications 60 example achieve more throughput 91 calculate times for CIP connections 92 consumed tags 90 delay times for CIP connections 93 determine bandwidth 85 RSLinx communication software bridging 18 system performance 84 explicit connections 58 messages 66 messaging 74, 86 messaging bandwidth 86
infrastructure Ethernet 19 features 29 integrated motion 70 internet group management protocol 49 IP address format 13 node 13 overview 13
L
linear -embedded switch topology 21 -switch topology 20
M
MAC ID 50 managed switches 27 mask subnet 16 media bridge 24 converters 24 Ethernet 22 hubs 23 repeaters 23 routers 25 switches 26 messages explicit 66, 74, 86 implicit 65, 74 types 57 mode full-duplex 28 half-duplex 28 motion integrated 70 multicast 30 address limit 33
F
firmware revision upgrade 64 flex links protocol 44 format IP address 13 frames 32 full-duplex mode 28
G
gateway 15 address 15 default address 15 guidelines 39 VLANs, segmentation 39
H
half-duplex mode 28 hubs multiport repeaters 23 NAT
N
definition 36 network address translation (NAT) 36 bridge 18 convergence 41 protocols 12 specifications 60 node count guidelines 59 EtherNet/IP network 59 IP addess 13
I
IGMP 49 implicit connections 57 messages 65 messaging 74
96
Index
O
overview EtherNet/IP network 11
S
safety CIP 67 security port 50 violations 51 segmentation 37 service quality 40 spanning tree protocol 42 specifications EtherNet/IP network 60 star topology 19 static secure MAC address 50 subnet mask 16 switches managed 27 media 26 unmanaged 27 sync CIP 68 system performance 73 achieve more throughput 91 calculate delays for CIP connections 93 calculate packets/second 80 calculate times for CIP connections 92 calculations 77 determine bandwidth 75 example 84 fastest RPI 82 predict times for CIP connections 76, 83
P
packets calculation 80 rate capacity 63 transmission 30 performance calculations 77 system 73 port security 50 produce and consume 55 tags number of multicast 61 producer 55 protocols network 12 transmission 33
Q
Qos 40 quality of service (Qos) 40
R
rack-optimized connections 57 rapid STP 42 redundant star topology 20 REP 45 repeaters media 23 requested packet interval 64 requirements configuration 13 reserve explicit messaging 86 resiliency 41 Ethernet protocol 45 protocols 41 ring-switch based topology 20 routers media 25 RPI calculation 82 RPI times 82 RSLinx communication software bridging 18
T
tags produced and consumed 61 TCP connections 56 terminology 55 throughput switches 26 topologies device-level ring 21 Ethernet 19 linear-embedded switch 21 linear-switch 20 redundant star 20 ring-switch based 20 star 19 transmission packets 30 protocols 33 transports 56 trunking VLAN 39
97
Index
U
UCMM 56 messages 56 unicast 30 default settings 31 unmanaged switches 27
V
violations security 51 virtual LAN 37 VLAN 38, 39 trunking 39
98
Rockwell Automation Support

Rockwell Automation provides technical information on the Web to assist you in using its products. At http://www.rockwellautomation.com/support, you can find technical manuals, technical and application notes, sample code and links to software service packs, and a MySupport feature that you can customize to make the best use of these tools. You can also visit our Knowledgebase at http://www.rockwellautomation.com/knowledgebase for FAQs, technical information, support chat and forums, software updates, and to sign up for product notification updates. For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer TechConnectSM support programs. For more information, contact your local distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/support/.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact Customer Support for initial help in getting your product up and running.
United States or Canada Outside United States or Canada 1.440.646.3434 Use the Worldwide Locator at http://www.rockwellautomation.com/support/americas/phone_en.html, or contact your local Rockwell Automation representative.
New Product Satisfaction Return

Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Outside United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your distributor to complete the return process. Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
Rockwell Otomasyon Ticaret A .., Kar Plaza Merkezi E Blok Kat:6 34752 erenky, stanbul, Tel: +90 (216) 5698400
Publication ENET-RM002B-EN-P - April 2012

Supersedes Publication ENET-RM002A-EN-P - July 2011 Copyright 2012 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.

Ethernet Design Considerations

Uploaded by

Copyright:

Available Formats

Ethernet Design Considerations

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ethernet Design Considerations

Uploaded by

Copyright:

Available Formats

What are some important differences between solid-state equipment and electromechanical devices?

What are some important differences between solid-state equipment and electromechanical devices?

What safety guidelines should be considered when applying solid-state equipment?

What safety guidelines should be considered when applying solid-state equipment?

Reference Manual

Ethernet Design Considerations

Important User Information

New and Updated Information

This table contains the changes made to this revision.

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Chapter 1 EtherNet/IP Overview

Chapter 2 Ethernet Infrastructure Components Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 3 Ethernet Infrastructure Features

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Chapter 4 EtherNet/IP Protocol

Chapter 5 Predict System Performance

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Typical devices networked

Large packets, data sent regularly

Small packets; data sent as needed

Number of nodes, max Data transfer rate Typical use

No limit 10 Mbps, 100 Mbps, or 1 Gbps Plant-wide architecture High-speed applications

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Table 2 - Rockwell Automation Resources

Table 3 - Cisco and Rockwell Automation Alliance Resources

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Request for Comments IETF UDP/TCP/IP

Ethernet MAC IEEE 802.3 Ethernet Physical

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Common Industrial Protocol (CIP)

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

The network class determines how an IP address is formatted.

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

EtherNet/IP Modules in a Control System

1734-AENT 1734 I/O Modules

Kinetix 350 Drive with Motor

Workstation 1783-ETAP Workstation 1783-ETAP

PanelView Plus Terminal Connected Via a 1783-ETAP EtherNet/IP Tap

Kinetix 6500 Drives with Motors

1756-EN2TR 1756 I/O Modules

1734-AENTR POINT I/O Adapter with POINT I/O Modules

1794-AENTR FLEX I/O Adapter

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Bridge Across Networks

CIP messages that originate on this network

EtherNet/IP ControlNet RS-232

Yes Yes Yes

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Ethernet Infrastructure Components

Table 4 - Topologies with an Individual Switch

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012

Ethernet Infrastructure Components

Table 4 - Topologies with an Individual Switch

Redundant star Layer 3 Layer 3

Rockwell Automation Publication ENET-RM002B-EN-P - April 2012