What do Frisbees, duct tape, and crowbars have in common? Give up? None of them have changed an iota since the day they were created. And fifty years from now, they’ll likely be the same as they are today. You can’t say that about EtherNet/IP and its core technology CIP (Common Industrial Protocol). There is a lot going on in the EtherNet/IP world.
If you’re an integrator, distributor, control engineer, or other automation professional, EtherNet/IP and CIP are like old shoes to you. Been there – done that. You’re an expert.
UNTIL NOW.
Now there is so much activity going on that it would be fair to say that EtherNet/IP will change more in the next five years than it has since its inception. A good question to ask is “Why is there all this activity in a protocol that’s sort of old right now?” There are actually a whole host of reasons, but three are driving most of the work.
THE IT/OT CONVERGENCE – The first is a rather startling shift in thinking about how to architect control systems. For many years now, we’ve used a much more hierarchical model for automation systems. In the new thinking, that the model is being compressed. A LOT! In fact, it looks like the new model is for everything to be connected to everything in a single very fast, high bandwidth Ethernet ring network. A network architecture where anything can talk to anything: sensors, cell phones, motor drives, servers, HMIs, printers, your desktop, the chiller, the fire alarm, and entry systems.
SECURITY ISSUES – I can tell you that that if you think you haven’t been hacked, you’re wrong. If you think you won’t be hacked again, you’re wrong. If you think you can prevent the next hack, you’re wrong again. All we can really do is to stop the more unsophisticated attacks and the “people not knowing any better” type breaches.
NEED FOR MORE INFORMATION – The world is about information – more and more information. There is a loud demand for more and more data from our factory systems. One of the big issues for these legacy systems is wiring. We have to learn how to reuse the wiring we have in place, and that’s driving some of the work on EtherNet/IP.
These things are driving a lot of the work going on in EtherNet/IP. Here’s a summary of the five most important enhancements to EtherNet/IP that are going to affect you and your company in the next few years.
#1 – EtherNet/IP is Getting More Secure
What’s Going On: Soon you’ll be able to encrypt the messages between your controller (EtherNet/IP Scanner) and your end-devices (EtherNet/IP Adapter) devices.
Why: One of the threats to automation networks is employees and contractors (often not maliciously) plugging infected computers into switches carrying automation traffic and spreading that infection to controllers.
My Take: I am not enthusiastic about this effort. I believe that many, if not the majority, of manufacturers will continue to prefer cheaper and less secure devices in their manufacturing systems.
#2 – EtherNet/IP is Getting Faster, More Reliable, and More Deterministic
What’s Going On: EtherNet/IP is actively supporting TSN – the link layer backbone of the new world of IT/OT convergence. TSN (Time Sensitive Networking) is a collection of IEEE Ethernet standards that allow scheduled (I/O) and unscheduled (IT) traffic to use the same physical layer and same Ethernet segments.
Why: Manufacturers want more simplicity then they have today. They want a single network to support all their traffic – data and information. They want something that is robust, high performance, and capable of supporting all sorts of applications that aren’t even developed yet. They want more open computing platforms, hardware and software, that are future proof.
My Take: TSN is very interesting and an exciting set of standards. I expect that TSN technology will be in place in most industrial facilities in as little as five years.
#3 – EtherNet/IP is Adding All Sorts of New Features
What’s Going On: EtherNet/IP as you know it is getting more sophisticated. Here are a few of the new features either already available or in development:
LED Services - In applications where you have a number of EtherNet/IP devices – especially where the IP addresses are assigned using DHCP – it’s often hard to know which device is which. EtherNet/IP is adding new services that allow a Scanner to flash the LEDs of an Adapter device.
Cabling and Connectors - The EtherNet/IP physical layer SIGs are addressing the cabling issues associated with 1 GB Ethernet.
New Earthing and Bonding Document - The ODVA has released a very comprehensive Earthing and Bonding document with practical recommendations for deployment of Ethernet systems in the factory.
PoE and PoDL - Work is moving forward on making distributed EtherNet/IP without running power lines (Power over Ethernet / Power over Data Lines) possible.
Multiple EtherNet/IP Ports - Devices are now being developed with multiple Ethernet ports and multiple EtherNet/IP identities. The System SIG is working to determine how to address these kinds of devices.
Expanded Device Configuration Block - There has been frustration with the 400 byte limit for device configuration. That is being addressed.
Why: Ethernet technology is improving – speeds are increasing, new capabilities are being added (embedded switch technology), and EtherNet/IP is responding with mechanisms to address these enhancements.
My Take: I am looking forward to these improvements in the basic EtherNet/IP functionality.
#4 – EtherNet/IP is Integrating Low Level I/O Protocols
What’s Going On: EtherNet/IP isn’t the only game in town when it comes to moving I/O data. People use DeviceNet, Profibus DP, and IO-Link. The plan is for CIP message originators to be able to access I/O in a legacy network using Explicit and Implicit messaging as if that data was in a CIP device.
Why: There are really good reasons to do this. With vast experience and training, proven reliability, and confidence in these networks, manufacturers have stayed with these solutions. Deployment of these non-Ethernet networks continue to grow.
My Take: This work is important and necessary given the growth in these non-Ethernet networks. Manufacturers want the flexibility both to use the best solution for an application and to seamlessly integrate devices from multiple networks.
#5 – EtherNet/IP is Moving to Constrained Resource Devices
What’s Going On: Constrained devices are devices with minimal flash, RAM, and/or processing power, some of them implemented on very old cabling in places like refineries over the last 50 years. Work is going on in various EtherNet/IP SIGs to figure out how to EtherNet/IP-enable these kinds of devices.
Why: Some manufacturers are saying that they abhor having to support different networks, protocols, and media in the same facility.
My Take: The real issue here is being able to use the current wiring infrastructure and not rewire 30,000 odd devices in a refinery. I believe that a new, simpler Ethernet physical layer will be developed that can use that wiring.
#5 ½ – EtherNet/IP is Moving to the Cloud (and into the IoT world)
What’s Going On: EtherNet/IP is no exception to the current fascination with IoT and the cloud. Cloud objects are being developed by more than one of the EtherNet/IP SIGs.
Why: Everyone is talking about the cloud. Every device manufacturer is busy figuring out how to move data to the cloud.
My Take: I find all this work puzzling. Controllers will support cloud communications. I don’t see the point in having cloud communications from every single device on the network.
Summary
If you thought that EtherNet/IP was on its way to being Modbus, you’d be very wrong. Unlike Modbus, which hasn’t changed an iota in 40 years, EtherNet/IP is being reinvented.
EtherNet/IP is being reinvented for a highly distributed, high performance network architecture that can carry any kind of traffic and still provide the determinism that is needed in most applications. EtherNet/IP is being reinvented for the world of the Cloud. And EtherNet/IP is being reinvented for IoT.
That’s one of the reasons our company exists – to provide you with the information, technology, products and services that can help you navigate this time of upheaval in the industrial automation industry.
Note: This article is an abstraction from a paper that appears this month on automation.com.