OPC .Net client server toolkits for OPC DA, HDA, AE, XML-DA      Advanced
         OPC .Net client server toolkits for OPC DA, HDA, AE, XML-DA
Online Tools
- OPC Error Lookup
* privacy and security Guaranteed  
OPCHDA.NET-UA  Buy or Evaluate

OPC UA Option for the OPCHDA.NET Client Component.

The OPCHDA.NET-UA component extends the OPCHDA.NET Client Component with an OPC UA (Unified Architecture) wrapper. The application can access OPC HDA and UA-HA servers through the same API.

OPCHDA.NET based client applications become OPC UA-HA clients without having to be modified. The applications only need to be compiled with a reference to the OPCHDA.NET component with the UA option.

Depending on the server ID ProgID or URL), the server is either accessed as an OPC HDA DCOM server or an OPC UA server.

For UA server access DCOM is completely eliminated because the UA converter is within the client process. There is no external DCOM to UA wrapper server involved. The client application acts as a native OPC UA-HA client.

Without additional application development effort the application can access DCOM OPC DA server and OPC UA-HA servers.



OPCHDA.NET-UA Advantages

  • The OPCHDA.NET-UA component enhances existing OPCHDA.NET based OPC Historian client applications with the capability to access OPC UA-HA servers.
    No code changes are required in the OPC HDA application. Only the OPCHDA.NET assembly references need to be changed to the assembly version with UA support and the OpcHDaNetUaOption.dll needs to be additionally referenced.
  • New client applications can be developed to support access to Classic OPC HDA servers as well as OPC UA servers.
    For UA server access DCOM usage is completely eliminated, unlike solutions with an external UA proxy server.

With the client application able to access OPC HDA and OPC UA-HA servers there is no need for external converters. This simplifies the installation, the configuration and the maintenance of the application. No converter (UA proxy) module needs to be installed, configured and maintained. There is one less component that may fail.

Top performance is achieved. The application communicates directly with the server. For OPC HDA server access there is an efficient .NET wrapper that handles the DCOM interface. For UA server access the .NET code performs the WCF based UA communication through the OPC UA communication stack.


OPCHDA.NET-UA Limitations

The UA server access is limited to the Historical Data (HA) profile of the UA server. The Data Access (DA) and Alarm&Conditionst (AC) features of the UA server cannot be accessed through the OPC HDA client interface. 
If also DA fuctionality is required then the OPCDA.NET / OPCDA.NET-UA products need to be used in combination with OPCHDA.NET /OPCHDA.NET-UA.
If also A&E fuctionality is required then the OPCAE.NET / OPCAE.NET-UA products need to be used in combination with OPCHDA.NET /OPCHDA.NET-UA.


OPCHDA.NET-UA Feature Summary

  • .Net applications can access OPC HDA and OPC UA servers through the same API
  • All OPCHDA.NET classes can access Classic OPC HDA and UA servers.
  • The server type is determined by the server name (ProgID or URL).
  • The UA configuration is defined in an additional configuration XML file.
  • UA specific configuration and testing tools are provided.
  • Detailed UA errors can be logged to file or the application can define a callback method for UA error/trace information.
  • High performance for HDA and UA server access.
  • Pure .NET code that runs in 32-bit or 64-bit for HDA and UA server access.
  • UA Methods handling



  • OPCHDA.NET Professional Edition V6.1 or newer
  • Windows 7, 8.x, 10 or Windows Server 2008, 2012, 2016    32 or 64bit
  • .NET Framework 4.x
  • Visual Studio 2010,2012,2013,2015 or 2017, C# or Visual Basic



Buy or Evaluate
home | contact us | return policy | privacy policy | security policy | Copyright © 2018 Advosol Inc. All Rights Reserved.