What to know about industrial Ethernet versus office Ethernet
Ethernet is growing in popularity, particularly as more people work from home, but there are some important differences between industrial Ethernet and office Ethernet people need to be aware of.
There was a time when industrial field networks all had different hardware requirements. HART requires a unit capable of injecting and reading signals overlaid on an analog signal, RS232 requires two signal wires and a ground, and RS485 requires two pairs of differential signal wires. Machine builders and end users alike had to invest in cables, adapters, and training to service all the different networks. While these networks still exist, they’re losing popularity for new installations. Ethernet has overtaken all other standards, accounting for 52% of new installations according to HMS Industrial Networks’ 2018 annual study. There’s no sign this trend will slow down anytime soon.
This convergence is great because it means we don’t have to learn so many different standards or keep special cables around. We’ve already seen Ethernet in our homes and offices. We’re familiar with the blue cables, the clear plastic RJ-45 connectors and the routers in our basements. A lot of that familiarity can support our Ethernet use in industrial automation, but there are some important differences to be aware of. This article is based on “Industrial Ethernet Design Guide.”
We often hear network speed defined in terms of megabits per second (MB/s). In industrial applications, network hardware is most often rated for 100 MB/s, with 1000 MB/s gaining popularity. In the office, this is usually the important speed metric, but in an industrial control network, determinism is most important. When we’re controlling or monitoring real events at high speed, we have to communicate with devices in a consistent time frame. If a printer on an office network sees a 2-second delay in the middle of receiving a document, that’s no problem, but if a servo has to wait that long, it could be catastrophic. The most important design consideration here is keeping the automation network separate from the office network.
The industrial environment is electromagnetically noisy. There are large currents, often driven by switching power devices like variable frequency drives (VFDs) that are notorious for creating high frequency harmonics and electromagnetic interference (EMI) that can affect other devices. We’ve got a few options for reducing EMI’s effect on our network – segregation, twisting signal pairs, bonding and shielding. A good design includes all four. There’s a lot to know, but following a manufacturer’s recommendations will get you most of the way there. For example, VFD manuals always talk about grounding and bonding.
Industrial environments can be very harsh on components. Extreme temperatures, moving parts, reactive chemicals, and high voltages are all common. Each cable and device need to be rated for the environment or enclosed to protect it.
Network cables can be purchased to resist all sorts of harsh environments. All cables must have insulation rated for the highest voltage in the enclosure or wireway. That means, even though Ethernet is low voltage, it often still needs a 600V rated jacket. If the cable will be flexed during normal operation, get a flex-rated cable. If it’ll be routed through an exposed tray, NEC requires a tougher jacket to protect against mechanical damage (buy a tray-rated cable). For other mechanically challenging environments, there are crush-rated and abrasion-resistant cables. Finally, cables can be acquired with ratings for extreme temperatures, flame resistance, and oil/chemical resistance.
Industrial Ethernet protocols
When we plug in an Ethernet cable at the office, we can usually expect it to just work. We don’t need to know what’s going on inside the cable. However, in industry, not all Ethernet is compatible, so we have to know a little more about what’s going on.
A protocol is a language that devices use to communicate over an Ethernet cable. Often, protocols are used in layers, with a low-level protocol providing the foundation for a high-level protocol. Since industrial applications have different needs than building/office/home networks, protocols exist to specifically fit these needs, each with its own trade-offs. When an industrial protocol is defined “on top of” a widely used protocol (often TCP/IP), standard architectures and hardware can be used. When a protocol is defined at a low level (stacked on few other protocols), architecture and hardware options may be more limited. The other tradeoff between these two broad categories is performance. A low-level protocol will usually be more deterministic than a high-level protocol.
In practice, Ethernet protocol is usually dictated by programmable logic controller (PLC) choice. Each PLC manufacturer has a preference, and while some offer a few options, you’ll usually get the best results (easiest implementation, best support) if you stick with that manufacturer’s standard. Each of these manufacturers has played a key role in the standards organization that defines their favorite protocol.
Wide Ethernet adoption brings a lot of benefits to automation (and the people who build and maintain it!). We get to repurpose robust standards, tools and personal experience from the IT world. Adding a dusting of industrial intent turns these standards into a flexible, powerful, easy to use communication standard to power our automation. As always, knowing is half the battle. The small differences between office and industrial Ethernet can mean the difference between headaches and smooth sailing. Don’t let those little things get in the way. Keep learning, pay attention to the details, and live the good life with Ethernet.
Jon Breen, founder/owner, Breen Machine Automation Services, a CFE Media content partner. This article originally appeared on Breen Machine Automation Services’ blog. Edited by Chris Vavra, web content manager, Control Engineering, CFE Media and Technology, email@example.com.
Keywords: industrial Ethernet, Ethernet protocols
Industrial Ethernet and office Ethernet might seem similar, but there are key differences.
Key aspects to keep in mind include determinism, electromagnetic interference (EMI), noise immunity and environmental ratings.
For manufacturers, Ethernet protocols are often dictated by the kind of programmable logic controller (PLC) they use and the manufacturer’s preferred Ethernet protocol.
Which of these considerations is the biggest priority for you and which is the biggest challenge?