OPC Data Access

Source: Wikipedia, the free encyclopedia.
OPC Data Access (OPC DA)
International standardOPC DA specification
Developed by
Windows
Superseded byOPC Unified Architecture
Websitehttps://opcfoundation.org/about/opc-technologies/opc-classic/

The OPC Data Access Specification is the first of a group of

OPC Classic Specifications.[1]

OPC Data Access is a group of

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

  1. a value,
  2. the quality of the value, and
  3. a timestamp.

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

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

  1. ^ "Members".
  2. ^ "What is OPC?".
  3. .
  4. ^ "Classic".
  5. ^ "Members".
  6. ^ ".NET 4.0 (WCF) | OPC Foundation". opcfoundation.org. Archived from the original on 2014-07-03.
  7. ^ "Unified Architecture".

External links