OPC Classic requires a Microsoft Windows OS to implement COM/DCOM server functionality. By using an SOA and web services, OPC UA is a platform-independent system that eliminates the previous dependency on a Windows OS. By using SOAP/XML over HTTP, OPC UA can deploy on a variety of embedded systems regardless of whether the system is a general-purpose OS, such as Windows, or a deterministic real-time OS.
Figure 1: OPC UA bypasses the need for a Windows-based component and can communicate directly with embedded OPC UA servers on PLCs.
Because of the benefits of OPC UA, National Instruments has chosen to integrate the creation of OPC UA clients and servers communication into two NI LabVIEW add-on modules. For Because of the benefits of OPC UA, National Instruments has chosen to integrate the creation of OPC UA clients and servers communication into LabVIEW through the LabVIEW OPC UA Toolkit. The LabVIEW OPC UA Toolkit is an API for the creation of OPC UA servers and clients for both Windows and Real-Time operating systems. This API includes support for the Data Access facet of the protocol as well as two additional facets: Historical Access (HA) and Alarms and Conditions (AC). The Historical Access facet allows the creation, retrieving, updating, and deleting of archived data and annotations. The Alarms and Conditions facet allows the definition, management, and acknowledgement of state driven notifications that require interaction with an operator or user such as infringement of safety limits, maintenance service, or confirmation of steps in a process.
>> Learn more about the LabVIEW OPC UA Toolkit