Using Profinet to improve communication, networking
Profinet facilitates digital transformation with real-time/non-real-time channel separation, deterministic communication and coexistence with other protocols.
- Profinet enables digital transformation by allowing for the separation of Ethernet traffic into a real-time channel and a non-real-time channel, enabling devices to connect to an information model using OPC UA for non-real-time information exchange while Profinet handles real-time data exchange for factory operations.
- Profinet technology coexists with any other protocol on the wire, making it an ideal OT protocol for digital transformation that can meet requirements for determinism, redundancy, safety and security while supporting IT protocols for vertical integration.
There are many factors influencing the transformation of industrial networks. The end result of which is the transition from serial fieldbus technology to Industrial Ethernet-based networks where any device can be connected to any other device. However, it’s not just about connectivity, it’s equally important that we move from a “one bus, one protocol” mentality to a “one network, multiple protocols” philosophy. Having access to multiple protocols opens our minds and our networks to using the right protocols for the right tasks. In part two we look at why Profinet enables digital transformation in the context of this “one network, multiple protocols” philosophy.
Profinet works by separating Ethernet traffic into a real-time channel and a non real-time channel. To do this, Profinet uses a field in the Ethernet Frame called an EtherType and we use this Ethertype to distinguish between real-time frames and all other frames. Messages with the Profinet Ethertype go into the real-time channel and messages with any other Ethertype go into the non real-time channel. And this is how we can use the same standard unmodified Ethernet for Profinet for all other IT protocols.
The real-time channel provides real-time data exchange to keep the factory running, and the non real-time channel provides non real-time information exchange to get data from the factory floor to a higher level. Machines that speak Profinet do so through the real-time channel and these messages coexists with all other messages so information can pass from devices to machines to factories to the cloud and back.
Profinet and vertical integration
Profinet is needed to keep the factory operating, but users also need to get data in this operations part of the network to a higher level. So we need vertical integration. This is where OPC UA comes in, which demonstrates its power with information models.
Because the real power of OPC UA is its information models. They are self-describing, machine-readable, and semantically rich. So now a machine can connect to an information model and it doesn’t need to know a priori what it’s looking for or how the data is arranged, the information model itself tells it. Since we have Profinet for real-time data exchange on the factory floor and OPC UA for non real-time information exchange from the factory floor to the cloud, we have written companion specifications to map Profinet data to OPC UA information models.
Three ways to achieve vertical integration
The reason why you might want to do this mapping in a PLC is if there is some data dependency in the PLC application, or there is some other advantage in the PLC at the IO level. It may be that it doesn’t make sense to add an edge/gateway to the network. In any of these cases, however, users need to make sure the PLC performance isn’t disturbed by retrieving data from the OPC UA Server integrated in the PLC.
If you don’t want to touch the PLC or maybe it is max’ed out in terms of its capabilities, another option is to send data directly from a device to a higher level. Sending data directly from a device can also prevent a PLC or edge/gateway from being overloaded by a large number of devices on the network. There is so much interest in getting data out of devices that we are starting to see products in the market with both a Profinet interface in them and an OPC UA interface in them. This use case really highlights, more than anything else, the power of Profinet technology. Deterministic, real-time communication – Profinet handles all of that. Non real-time information exchange – OPC UA handles all of that.
The third use case for vertical integration is to use an edge gateway or edge computer. If you find yourself in a brownfield environment and you don’t want to touch the PLC, or there is a large amount of raw data on the network, an edge computer is a good choice because it doesn’t make sense to send all of this raw data directly to the cloud. It makes more sense to process this data at the edge – with an edge computer – and then send OPC UA information to the cloud. If you have just a little bit of data to get to the cloud, an edge gateway may be a better choice. This type of gateway reads Profinet data from the network, translates it to OPC UA, and then sends the OPC UA information out to the cloud.
The bottom line of Profinet’s usefulness
The journey towards digital transformation requires an OT protocol that can meet the requirements for determinism, redundancy, safety, and security while also supporting IT protocols for vertical integration.
– PI North America is a CFE Media and Technology content partner.
Do you have experience and expertise with the topics mentioned in this content? You should consider contributing to our CFE Media editorial team and getting the recognition you and your company deserve. Click here to start this process.