1 / 19

The Ten Commandments of Making EtherNet/IP Applications Successful

The Ten Commandments of Making EtherNet/IP Applications Successful. Event Date Presenter Title Email. EtherNet/IP – Quick Survey. Who has done the following… Used Ethernet for a computer network? Used Ethernet to plug into a controller? Used Ethernet for a control network?

rainer
Download Presentation

The Ten Commandments of Making EtherNet/IP Applications Successful

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. The Ten Commandments of Making EtherNet/IP Applications Successful Event Date Presenter Title Email

  2. EtherNet/IP – Quick Survey • Who has done the following… • Used Ethernet for a computer network? • Used Ethernet to plug into a controller? • Used Ethernet for a control network? • Used EtherNet/IP enabled devices for messaging or programming? • Used EtherNet/IP enabled devices to control I/O?

  3. Design Upgrade Install User Lifecycle Of a Network Maintain Configure Operate Startup Network User Lifecycle

  4. #1 - Understand the System Requirements • System Environment • Plant Floor I/O Control to IT Integration • Expandability • Security • Performance • How much data? How fast? • Infrastructure • Media, Switch, Router, Firewall, Remote Access, etc. The better you know the system’s requirements, the better chance you have for a successful installation

  5. # 2 - Learn the System Environment Critical Design Decision: • Integrated OR • CIP Connected More significant impact on design considerations OR • Isolated … with/from your corporate network You must choose how (and if) you want to connect your control system to your corporate network

  6. Enterprise Network Isolated – No Connection Between Control and Corporate Networks Enterprise Network • Design Impacts: • Choose your own IP addresses • Fewer performance considerations due to less traffic • Simpler security considerations Router Corporate Network Control Level TCP/IP Switch CIP

  7. Enterprise Network • IT and control networks separated by the CLX backplane • CIP messages route through the gateway • All other types of traffic are blocked (e.g. HTTP, FTP, etc.). CIP Connected – Only CIP Traffic Moves Between Networks Enterprise Network • Design Impacts: • Some IP address assignment coordinated with IT • Additional performance considerations • More security and access considerations Router Corporate Network Control Level ENBT ENBT TCP/IP Switch CIP

  8. Enterprise Network Integrated – All Devices Connected to the Same Infrastructure • Design Impacts: • High level of IP address assignment coordinated with IT • High level of performance considerations • High level of security and access considerations Router Corporate Network Control Level Switch Switch CIP Switch Switch TCP/IP CIP

  9. #3 - Make IT Aware • Impact of Controls traffic on the IT network • EtherNet/IP traffic type • I/O = “implicit” • Messaging = “explicit” • I/O traffic is multicast • Now that EtherNet/IP is “running” the plant floor, who owns the networks? • IT staff vs. Control staff • Maintenance, upgrade, troubleshoot • Assigning IP addresses IT needs to know that I/O traffic is multicast packets at high continuous rates

  10. #4 Segment Networks Properly • Why Segment Networks? • Simplify network management • Security • I/O traffic vs. HMI Messaging • Maximize backbone or Control network availability • Segmentation Tools • Physical segment : a switch • Logical segment: VLAN and IP Subnets Proper traffic segmentation can enhance system performance

  11. #5 - Never Use Hubs • Hubs vs. Switches vs. Router • Hubs (repeaters) • Allow collisions • Broadcast all traffic to all ports • Switches • Eliminate collisions (very important for controls!!) • Segment traffic within an IP subnet • Router • Segregates traffic into different IP subnets Always use switches and routers!!!

  12. #6 - Select the Switch with Proper Features • Choose a switch with industrial rating • Unmanaged Switches can be used Only When: • The features listed below are not needed • No potential to overload a device with traffic • Performance with multicast traffic on the network is acceptable • See white paper for more info: http://www.ab.com/networks/ethernet/get/UnmanagedSwitches_07252005.pdf • Recommended Managed Switch Features • Port mirroring – ability to duplicate the frames being transmitted from one port to another for troubleshooting • IGMP Snooping – constrains multicast traffic to ports associated with particular IP multicast group • Port diagnostics – allows troubleshooting and access to pertinent network stats • Web browser – allows web access to view configuration and diagnostics Unmanaged switches are less expensive and often simpler Click For More Features Ignoring the required switch features could potentially lead to problems

  13. #7 - Select and Install the Right Media • Copper • CAT 5e and 6 cables and connectors are recommended for industrial applications • UTP is generally recommended • STP is recommended for metal conduits and noisy environment • Ground one end ONLY!!!!!!! • Fiber • Fiber is good for noise immunity and long distance • Single mode (high performance, $$) • Multi-mode (general purpose) • Grounding and Noise • Same basic guidelines apply as other network installations • Refer to the EtherNet/IP Media and Installation Guide for more info (Pub #: ENET-IN001) Click For More Info Standard Ethernet rules and practices apply… but design carefully

  14. #8 - Understand End-device Capacities • The “bottlenecks” of a EtherNet/IP system are almost always in the end devices • Traffic usually consumes very little of the infrastructure bandwidth @ 100Mbps • Examples of Product Capacities: Not all end devices are created equally

  15. #9 - Be Aware of Potential Security Issues • Common Practices today: • Logically separate the IT / Corporate Network from the Control Network • Severely limit logical and physical access to the Control Network to those with a legitimate need (strict access policies) • Implement plant floor security processes, policies and procedures • Utilize your IT department’s standard security technology to enforce access policies • Consult with the experts (RA GSS Network Services) Deny access by default, permit by exception

  16. #10 - Don’t Hesitate to Get Help Time and money spent upfront will avoid heartache later!!

  17. Common Engineering Processes Design Design per specs & Basis for Validations Installation Validate installations against design & network specs Operation Validatesystem signal quality during operating conditions Documentation GSS Network Services Overview • Key Areas Addressed • Physical Media: Design, Installation • Application: Performance, Validation • Commercial: Project Cost, Acceptance • Networks Supported • Ethernet, EtherNet/IP, DeviceNet, ControlNet, DH+ • Coax, Fiber, Redundant Systems • FieldBus • Family of Services • Consulting & Design • Media Validation • Maintenance &Troubleshooting • Baseline Documentation • Training

  18. Reference Documents • Publications • ENET/IP Performance and Application Guide (Pub#: ENET-AP001) • ENET/IP Media Planning and Installation Guide (Pub#: ENET-IN001) • ENET/IP Modules in Logix5000 Control Systems User Manual (Pub#: ENET-UM001) • EtherNet/IP - Take the Next Step Website: • Check Tech Support Knowledge Base for additional information http://www.ab.com/networks/ethernet/next-step.html

  19. The Ten Commandments for EtherNet/IP • Understand the system requirements • Learn the system environment • Make I T aware • Segment networks properly • Never use Hubs • Select the switch with proper features • Select and install the right media • Understand end-device limitations • Be aware of potential security issues • Don’t hesitate to get help EtherNet/IP is not difficult, It’s just different!!!

More Related