Customers and co-workers often ask me about the purpose of industrial Ethernet – where it’s used, and especially about the benefits of the many different industrial Ethernet standards.
This new blog series is for designers who have decided to leverage industrial Ethernet in their system. I’ll talk about several common industrial Ethernet communication protocols. This should help you to better select the best standard for your application.
Industrial Ethernet is for factory automation and control, process automation, building automation and for many other industrial applications. One of the benefits of industrial Ethernet over standard Ethernet is the deterministic real-time data exchange and the isochronous cycle time of less than 1ms.
There are more than 20 industrial Ethernet protocols deployed as standards and used in industrial applications: these include EtherCAT, Sercos III, PROFINET, EtherNet/IP and Ethernet Powerlink. Why are there so many standards to choose from? Each manufacturer of industrial equipment seem to know the requirements for real-time data exchange over Ethernet a little bit better and has developed their own standard based on their knowledge about the historical serial fieldbus area.
You cannot implement most industrial Ethernet standards with a standard Ethernet media access control (MAC); they require a dedicated application-specific integrated circuit (ASIC) or field-programmable gate array (FPGA). This is because the Ethernet frame is received on the fly, also named as cut-through, which means that while the frame is getting received on the first Ethernet port, the frame is already getting processed and transmitted onto the second Ethernet port by a dedicated industrial Ethernet MAC hardware block. With the cut-through method a port-to-port delay of less than 1µs is achieved for an Ethernet frame.
On the other side standard Ethernet MAC uses the store and forward method. First the complete Ethernet frame must be received before secondly any processing or forwarding of the frame can be done by the Ethernet MAC. This adds jitter and delay to the frame and therefore it’s not a good choice for manufactures of industrial equipment.
The programmable real time unit-industrial communication subsystem (PRU-ICSS) provides great flexibility to support various industrial Ethernet protocols, but I’ll discuss that a bit more later.
Sercos has been around for 25 years in factory automation applications for mechanical engineering and construction. Sercos III is the third generation, established in 2003. This efficient and deterministic communication protocol merges the real-time data exchange of the Sercos interface with Ethernet. Sercos III technology integration was until now implemented in FPGAs.
One Sercos III master controls multiple Sercos III slave devices such as drives, sensors, and analog and digital I/O devices – this is shown in Figure 1. One master can control as many as 511 slaves.
Figure 1: Example Sercos III network ring topology
One key benefit of Sercos III is its support of a ring topology beside a line topology. If an Ethernet cable malfunctions the Sercos III network switches to a line topology, enabling the master to continue communicating with all of the slaves in the network. Once the Ethernet cable has been repaired, the master can switch the Sercos III network from a line topology to a ring topology.
The communication protocol is time-multiplexed, which is shown in Figure 2. Within one Sercos III communication cycle is a time slice dedicated to real-time Sercos III frames called real-time (RT) channel. In this time slice, the master and slave exchange process data, which is used within the programmable logic controller (PLC). In the second time slice, known as unified communication channel (UCC), all devices (master and slaves) in the network can exchange standard Internet protocol (IP) telegrams. UCC is used to exchange information of a Web server, update device software with trivial file transfer protocol (TFTP), or transfer Ethernet frames for any kind of IP-based applications.
Figure 2: Sercos III time multiplexed communication cycle
The use of an FPGA for Sercos III adds cost and board space. An alternative solution to remove that cost adder is to use PRU-ICSS, a peripheral available in many TI Sitara™ processors. For example, TI provides PRU-ICSS firmware for the AM335x processor, enabling a Sercos III slave device without the use of an external FPGA. You can evaluate the solution with the TMDSICE3359 evaluation board as seen in Figure 3.
Figure 3: TMDSICE3359 industrial communications development platform for Sercos III
I hope this blog post sheds some light into the functionality of Sercos III. If you want to know which industrial Ethernet standard is the best for your application then make sure to follow this blog series about industrial Ethernet and learn more about the other industrial Ethernet standards.
- Learn more about the EtherCAT Slave and Multi-Protocol Industrial Ethernet Reference Design
- Check out the Sercos III Slave For AM437x Communication Development Platform Reference Design.
- Read a blog post on industrial communication protocols.
- Take an inside look at industrial Ethernet protocols in this white paper.