OPC Data Access
In today's world, OPC Data Access is a topic that has captured the attention of millions of people around the world. Whether due to its historical relevance, its impacts on society or its influence on popular culture, OPC Data Access has become a focal point for debate and reflection. In this article, we will explore the different facets of OPC Data Access and examine its importance in the current context. From its origin to its possible consequences, we will delve into an in-depth analysis of OPC Data Access and its role in the modern world.
 | This article needs additional citations for verification. (July 2016) |
| International standard | OPC DA specification |
|---|---|
| Developed by | OPC Foundation |
| Introduced | August 1996 |
| Industry | Operational technology and Information technology |
| Compatible hardware | Windows |
| Superseded by | OPC Unified Architecture |
| Website | https://opcfoundation.org/about/opc-technologies/opc-classic/ |
The OPC Data Access Specification is the first of a group of specifications known as the OPC Classic Specifications.[1]
OPC Data Access is a group of client–server standards that provides specifications for communicating real-time data from data acquisition devices such as PLCs to display and interface devices like Human–Machine Interfaces (HMI), SCADA systems[2] and also ERP/MES systems.[3] The specifications focus on the continuous communication of data.
The OPC Data Access specification is also known as OPC DA. OPC DA deals only with real-time data and not historical data (for historical data you need to use OPC Historical Data Access, or OPC HDA) or events (for Alarms and Events you need to use OPC Alarms and Events, or OPC AE). There are three attributes associated with OPC DA data. These are
The OPC DA specification states that these three attributes have to be returned to an OPC client making a request. Therefore, if the data source is not capable of providing a timestamp, for example, the OPC DA server must create a timestamp.
The OPC Classic specifications are based on the Microsoft COM technology[4] and define a C/C++ interface. A standard Automation wrapper interface is also defined for access from Visual Basic, Delphi and other automation-enabled languages.[5] Several vendors offer .NET toolkits to make the OPC interface accessible in .NET applications.
The newer OPC .NET (OPC Xi) specification is based on WCF (Windows Communication Foundation) and defines a .NET interface with the functionality of the OPC Classic specifications OPC DA, OPC HDA and OPC AE (Alarms&Events).[6]
The more recent OPC Unified Architecture allows the same functionality but offers platform independence and optionally complex information modelling capabilities.[7]
See also
References
- ^ "Members".
- ^ "What is OPC?".
- ^ Mahalik, Nitaigour P. (2013-03-09). Fieldbus Technology: Industrial Network Standards for Real-Time Distributed Control. Springer. ISBN 9783662072196.
- ^ "Classic".
- ^ "Members".
- ^ ".NET 4.0 (WCF) | OPC Foundation". opcfoundation.org. Archived from the original on 2014-07-03.
- ^ "Unified Architecture".