5 quick questions about OPC UA FX

Dietmar Bruckner: FX stands for Field eXchange. This standard unifies the higher protocol layers as well as the semantics of the various control and field devices. The end result is a unified solution for all relevant automation applications – including motion control, safety and determinism.

Bruckner: Since OPC UA FX is entirely independent of the physical transport layer, it can be used alongside the various legacy protocols in hybrid networks. In that way, it connects the old world of communication with the new. That's really important when it comes to migration strategies towards OPC UA FX – whether starting a new project or upgrading an existing system. There's no need to quit your old solution cold turkey.

Bruckner: TSN is still the solution of choice for real-time applications with demanding speed requirements, but it's not mandatory. On the contrary, the OPC UA framework is built to enable the use of wireless technologies such as 5G or Wi-Fi 6 in the future.

Bruckner: The controller-to-controller specification is already available. Of particular importance to machine builders is that the OPC Foundation is also working together with PI on the vendor-independent solution for functional safety, OPC UA Safety. The FLC Safety working group has completed version 2.0 of the OPC UA Safety specification (OPC 10000-15), which supports OPC UA FX and Pub/Sub.

Bruckner: It's closer than you might think: OPC UA FX is already far more than just theory. In fact, a multi-vendor demonstration has already been presented where controllers from 17 well-known manufacturers were interconnected via Ethernet switches. The test setup showed that controller-to-controller communication is ready for the market – including automatic connection of devices from different manufacturers, known as connection management. So, if you ask me: That future is already here.