{"id":7377,"date":"2023-05-12T10:17:35","date_gmt":"2023-05-12T08:17:35","guid":{"rendered":"https:\/\/wp.delphin.de\/?post_type=glossar&#038;p=7377"},"modified":"2026-07-02T14:49:56","modified_gmt":"2026-07-02T12:49:56","slug":"opc-da","status":"publish","type":"glossar","link":"https:\/\/www.delphin.de\/en\/glossar\/opc-da\/","title":{"rendered":"OPC DA (OPC Data Access)"},"content":{"rendered":"<p class=\"wp-block-paragraph\"><strong>OPC DA (OPC Data Access)<\/strong> was the first OPC standard and, in 1996, laid the foundation for an entire family of vendor-neutral communication standards in automation and measurement technology. It was developed to transmit real-time data according to the <strong>Client-server model<\/strong> between devices, programmable logic controllers (PLCs), and human-machine interfaces (HMIs). Data is transmitted serially\u2014that is, sequentially in individual data packets\u2014with the OPC protocols handling the actual data transfer via <strong>TCP\/IP<\/strong> can be set up and integrated into virtually any existing Ethernet network.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The problem that OPC DA solves<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Before the introduction of OPC, exchanging data between devices from different manufacturers was a complex undertaking: Each product required its own driver-specific interface to communicate with other systems. For example, if you wanted to connect measuring devices, PLCs, and visualization software from different vendors, a custom driver was required for each individual combination\u2014a significant burden in terms of system integration, maintenance, and expansion. <strong>OPC DA replaces this driver-specific data exchange with a universal standard.<\/strong> For each device or PLC, only a single, standardized OPC driver needs to be configured, through which any OPC-compatible software can then access the data. This eliminates the need to implement a separate interface for each manufacturer and each system.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Significance for Measurement Technology<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In industrial measurement data acquisition and test bench automation in particular, components from a wide variety of manufacturers are often used together: sensors, measurement amplifiers, controllers, actuators, and higher-level control systems. OPC provides a common language that allows these systems to communicate with one another regardless of their respective manufacturers. For users in measurement technology, this means significantly simpler system integration: New devices can be connected via a standard OPC driver, rather than having to develop a custom solution for every new combination of devices.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">From OPC DA to OPC UA<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Although OPC DA was groundbreaking, it also had its limitations: The standard was based on Microsoft\u2019s COM\/DCOM technology and was therefore fundamentally tied to Windows systems; furthermore, it did not offer end-to-end security mechanisms for communication across enterprise and network boundaries. As a result, a further development was therefore <strong>OPC UA (OPC Unified Architecture)<\/strong> created. \u201eUA\u201c stands for \u201eUnified Architecture\u201c and refers to the current, platform-independent generation of the OPC standard. <a href=\"https:\/\/www.delphin.de\/wp-content\/uploads\/2023\/08\/Landingpage-OPC-UA.jpg\" data-type=\"attachment\" data-id=\"10784\">OPC UA<\/a> \u2014unlike OPC DA\u2014is no longer dependent on a specific operating system, transmits data in an encrypted and authenticated manner, and also combines the functions of earlier OPC variants such as Data Access (real-time data), Historical Data Access (HA; historical, archived measurement data), and alarms into a single, unified standard. OPC UA thus meets the requirements of modern, end-to-end networked architectures, as needed in the context of Industry 4.0 and the Industrial Internet of Things (IIoT)\u2014from the sensor and field level through PLCs and control systems all the way up to the cloud.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">OPC at Delphin \u2013 Practical Applications<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Delphin Technology<\/strong> consistently implements both standards in its product portfolio. The measurement technology software <strong>ProfiSignal<\/strong> has had an OPC client interface for many years, which allows third-party hardware from a wide variety of manufacturers to be integrated. In addition, both the central measurement data management software <strong>Delphin Data Center<\/strong> As well as the data loggers in the Expert, Loggito, and ProfiMessage series, they offer full OPC UA compatibility: as OPC UA clients, OPC UA servers, and OPC UA HA servers for the convenient transfer of historical measurement data. The high-performance measurement database developed by Delphin enables data transfer rates of up to 500,000 data points per second and supports up to 20,000 OPC UA nodes\u2014allowing even large raw data streams, such as those from vibration measurements, can be reliably transmitted via OPC UA.<\/p>","protected":false},"featured_media":0,"template":"","class_list":["post-7377","glossar","type-glossar","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.delphin.de\/en\/wp-json\/wp\/v2\/glossar\/7377","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.delphin.de\/en\/wp-json\/wp\/v2\/glossar"}],"about":[{"href":"https:\/\/www.delphin.de\/en\/wp-json\/wp\/v2\/types\/glossar"}],"wp:attachment":[{"href":"https:\/\/www.delphin.de\/en\/wp-json\/wp\/v2\/media?parent=7377"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}