{"id":5326,"date":"2023-01-04T14:10:00","date_gmt":"2023-01-04T13:10:00","guid":{"rendered":"https:\/\/blog.microtronics.com\/?p=5326"},"modified":"2025-10-01T08:43:12","modified_gmt":"2025-10-01T06:43:12","slug":"opc-ua-uniform-access-to-machines-and-devices-on-the-internet-of-things","status":"publish","type":"post","link":"https:\/\/microtronics.com\/en\/blog-en\/opc-ua-uniform-access-to-machines-and-devices-on-the-internet-of-things\/","title":{"rendered":"OPC-UA – uniform access to machines and devices in the Internet of Things"},"content":{"rendered":"\n

What is OPC?<\/h2>\n\n

OPC is a collection of standards in the industrial environment and enables uniform access to a wide variety of machines, devices and other systems. With the implemented support for the OPC client, SCADA (Supervisory Control and Data Acquisition) system developers no longer have to support countless drivers for different devices and device manufacturers can make their products usable for users of all SCADA systems by adding an OPC server. OPC is particularly important in the context of Industry 4.0. The standard (IEC62541) is managed by the OPC Foundation<\/a>.<\/p>\n\n

What is OPC-UA?<\/h2>\n\n

OPC-UA is the current successor of OPC – today also referred to as OPC-Classic. The abbreviation “UA” stands for “Unified Architecture”. While OPC-Classic was dependent on basic Windows technologies, OPC-UA is based on TCP\/IP and can be used independently of the operating system. The following figure shows essential differences between OPC-Classic and OPC-UA.<\/p>\n\n

\"OPC<\/a><\/figure>\n\n

The fixation on Windows was a weakness of OPC-Classic and also limited the spread to other operating systems (e.g. Linux). Therefore, platform independence was one of the primary goals of OPC-UA. The changeover to TCP\/IP also has the advantage that communication can now be routed through common firewalls and thus more control of communication is possible. OPC-UA has also been further developed in the security area and offers various options for authentication and encryption.<\/p>\n\n

myDatanet OPC-UA Server<\/h2>\n\n

Due to the many advantages, an OPC-UA server was developed for the myDatanet platform. This can be activated optionally (even retrospectively). This allows Microtronics partners to easily forward the recorded and transmitted data fields to any SCADA system, thereby generating an even better solution for their customers.<\/p>\n\n

\"Overview<\/a><\/figure>\n\n

Implementation<\/h2>\n\n

OPC-UA-DA<\/h3>\n\n

The abbreviation \u201cDA\u201d stands for \u201cData Access\u201d and is the basic function expected from OPC. With “DA”, individual data fields and their value can be accessed. In the case of myDatanet OPC-UA, read access to last valid measured values as well as read and write access to configuration values can take place. The nature of the measuring point determines the data fields that can be retrieved without any additional configuration effort.<\/p>\n\n

OPC-UA-HDA<\/h3>\n\n

The abbreviation “HDA” stands for “Historical Data Access” and makes it possible to read out time series of data fields. Since historical data is available in myDatanet, myDatanet OPC-UA supports this function. In addition to the data field, the client can pass a time period and receives the existing data in return.<\/p>\n\n

Authentication<\/h2>\n\n

The authentication of the OPC-UA clients is linked to the myDatanet user administration. This fully integrates rights management and facilitates security management. The user used for authentication has the same rights as when logging in to the myDatanet UI (such as visible sites\/customers).<\/p>\n\n

Features of myDatanet OPC-UA<\/h2>\n\n