OPC UA Field eXchange, commonly referred to as OPC UA FX or UAFX, is an extension of the OPC UA communication standard. It has been developed for the specific communication requirements in the factory.
The benefits of OPC UA are starting to be established in the industry. OPC UA is a manufacturer-independent communication protocol that provides a standardized format to enable the exchange of information from the device level to higher levels. By implementing OPC UA, machine manufacturers and line builders make it easier for their customers to access and interpret the diverse information produced by machines.
OPC UA FX takes it a step further by introducing low-layer extensions that address communication requirements within machines and for synchronization between machines, regardless of the manufacturer. OPC UA FX, with its “semantic” based communication, will allow new ways to define the controls and interactions within the field level.
The objective of OPC UA combined with UAFX is to have a uniform data exchange and representation through all layers of production – from sensors on the shop floor to the cloud (IT-OT exchange).
The OPC Foundation’s Field Level Communications (FLC) initiative is currently defining the OPC UA FX specifications to ensure the smooth interoperability of devices from different manufacturers. OPC UA FX will provide dedicated communication mechanisms and data profiles to specify data exchange between various automation equipment.
OPC UA FX will also support real-time network access using Ethernet by incorporating Time-Sensitive Networking (TSN) mechanisms. This means that it will support both synchronized data exchange, ensuring that data arrives at its destination exactly when needed, and deterministic transfers, guaranteeing that data is delivered predictably. By incorporating TSN mechanisms, OPC UA FX is suitable for applications where precise synchronization and low latency are critical.
OPC UA is currently integrated into machines to interconnect with IT applications. The next natural step for OPC UA is to address the Machine-to-Machine communication (also called controller-to-controller), as most Ethernet and Fieldbuses do not cover this functionality in their standard. So, it’s likely that OPC UA FX will be adopted at the machine-to-machine level.
However, the picture becomes less clear when considering the control communication within the machine-to-device and device-to-device levels. Adoption at these levels hinges on factors such as cost, complexity, and the standardization of the information model.
But whatever happens, it's highly unlikely that OPC UA FX will replace existing fieldbus and industrial Ethernet protocols, which all find their niche applications based on their strength. Instead, it is much more likely that OPC UA FX, with its new UAFX capabilities, will address unmet needs, becoming another protocol that device manufacturers will need to support.
In the next article, we’ll go into more detail about how OPC UA FX will impact device manufacturers.
Joakim Wiberg, Head of Technology, Anybus. Joakim is also the Chief Technology Officer (CTO) of ODVA and a frequent lecturer on security and industrial communication.
Thierry Bieber is the Industry Manager at HMS Networks Market Unit in Central Europe. Thierry has over 20 years of technical and market experience in industrial communication and machine infrastructure applications, as well as participation with various standardization organizations like PROFINET International.
-(1)-(1)-(1)-(1).png?sfvrsn=8fb7dbd7_0)
Joakim Wiberg Thierry Bieber
Anybus have developed a ready-made communication interface that manufacturers can embed into their products to enable OPC UA connectivity.