OPC .Net client server toolkits for OPC DA, HDA, AE, XML-DA      Advanced
OPC
Solutions    
         OPC .Net client server toolkits for OPC DA, HDA, AE, XML-DA
Online Tools
- OPC Error Lookup
- ASP.NET Sample Clients
- XML DA Sample Servers
Sign In | My Account | Shopping Cart
Search  
   
* privacy and security Guaranteed  
.Net OPC Solutions - Client Components Login  

Client Components



Product Summary Version Info
EasyUA Client SDK

The EasyUA Client SDK provides a set of .NET classes the handle the UA server communication. Included are sample applications and utilities for configuration and testing.
OPC UA DA, HA, AC and UA Methods functionality is supported.

 
PaXi (OPC .NET)

The PaXi Client Base greatly simplifies the development of OPC .NET client applications. OPC .NET (Xi) servers, Classic OPC DA,AE,HDA servers and OPC UA servers can be accessed thru the same API.

 
OPCDA.NET

OPCDA.NET Client Development Component
OPC clients can be developed in .NET without the hassle of COM interoperability. The OPCDA.NET assembly provides .NET classes and methods for for all OPC DA V2/V3 defined functions. Additional helper classes, tools and many samples provide a highly efficient application development environment.

 
OPCDA.NET-UA

The OPCDA.NET-UA component extends the OPCDA.NET Client Component with an OPC UA wrapper.
The application can access OPC DA and OPC UA servers through the same API.

 
OPCHDA.NET

OPC HDA .NET Client Development Component
OPC historical data access clients can be developed in .NET without the hassle of COM interoperability. The OPCHDA.NET assembly provides classes and methods take advantage of the .NET features and make OPC HDA Server access real simple and also very efficient.

 
OPCHDA.NET-UA

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

 

 
OPCAE.NET

OPC A&E .NET Client Development Component
OPC A&E clients can be developed in .NET without the hassle of COM interoperability. The OPCAE.NET assembly provides classes and methods take advantage of the .NET features and make OPC AE Server access real simple and also very efficient.

 
OPCAE.NET-UA

The OPCAE.NET-UA component extends the OPCAE.NET Client Component with an OPC UA wrapper.
The application can access Classic OPC AE and OPC UA-AC servers through the same API.

 
XMLDA.NET

XML DA / OPC DA Client Development Component
XMLDA.NET is a .NET component that handles the access to OPC DA and XML DA servers. The application is coded as an XML DA web client, independent of the type of server to be accessed.

 

.Net Applications

ASP.NET Applications 

WCF Applications 

 OPC-DA V2/V3 Servers

yes

yes

yes

XML-DA Servers

yes

yes

yes

Powerful helper classes such as BrowseTree, ListBuilder and DataBind reduce the application code to a minimum. Complex data visualization applications can be implemented in a few lines of VB.Net or C# code.

 

 


Category Description

How to develop OPC Clients with .NET?

Developers have many options for the development of .NET OPC client applications. What's best depends on many factors and on personal preferences.
The basic choices are the API and the communication.

Type of
Application
Interface

 

OPC client applications increasingly have to access different types of OPC servers. This can be accomplished with wrappers, either embedded in the client or as external converter servers.
The chosen application interface and the servers that need to be accessed determine the needed wrappers.
OPC defined interfaces are:

Classic OPC

The classic OPC DA, HDA, AE specification define a C++ COM interface and a COM Automation interface. For .NET the OPC Foundation provided sample .Net wrapper code but didn't create a .NET API specification.
Vendors offer .Net client components with widely different APIs:
- Methods that mirror the OPC specified interface functions. The application can use all OPC specified features.
- Usage oriented method that make the server access simple.
- Embedded into an overall product concept.

XML DA

The OPC XML DA specification was created in 2003. It defines .NET2 web service SOAP messages for the functionality of OPC DA (Data Access). See OPC-DA / XML-DA Comparison for an overview and comparison of the two OPC specifications.
There are no corresponding web service specifications for OPC HDA and OPC AE.
The .NET web services WSDL tools create API methods from the specification.

OPC UA

OPC UA was started in 2003 with the ambitious goal of a multi-platform specification with the capability to model all kinds of systems.
The specification was partially released in 2009 and vendors offer UA products, mostly with only DA functionality.
The OPC UA specification defines communication records. The multi-platform capability requires UA specific communication stacks for each platform.
The communication stack implementation defines the application interface.

OPC .NET (Xi)

The OPC Foundation adopted the Express Interface (Xi) specification as the OPC .NET API specification.
Xi was created by a number of OPC vendor companies as a .NET interface specification with the features of OPC DA, HDA, AE and is designed to make the implementation of wrappers simple and efficient.
OPC .NET (Xi) is based on the Microsoft Communication Foundation (WCF) and specifies a set of WCF contracts. The contracts define the server and client API.

Type of
Server
Communication

 

The interface specification defines the communication supported by the server.

(D)COM

 

The Classic OPC Specification defines a COM interface. OPC DA, HDA, AE servers are COM server and need to be accessed through (D)COM.
Microsoft still supports DCOM and for local server access COM is still a good and efficient solutions.
Remote server access is limited and the necessary DCOM configuration is tricky and the cause of most OPC difficulties.

.NET2 web services

The .NET2 web services (ASMX) eliminate the DCOM remote communication limitations and configuration issues. However, the communication is restricted to HTTP and the security options are limited. The .NET2 based XML DA is available since 2003 and is often used to remotely access OPC DA servers through an XML DA gateway server.

OPC UA

OPC UA communication is either TCP or HTTP. The security handling and the upper layer communication are UA specific to make it consistent on all platforms.
The OPC Foundation is working with member companies to make communication stacks and tools available to its members for different platforms, such as PLCs.

WCF

The Windows Communication Foundation (WCF) introduced with .NET3 extends the .NET2 web services with additional W3C standards and Microsoft specific features.
The communication can be configured for a wide range of communication and security options.

 

Products are available for many combinations of API and server communication.
Application designers should decide the used API based on:

  • communication (server types) that need to be supported (are converters available?).
  • communication that is mainly going to be used
  • the capability of available wrappers to support all needed features
  • the type of client application (GUI application, web client, Windows service, etc.)

 

Advosol offers the most complete set of client components, converter servers and server toolkits.

PaXi OPC .NET (Xi) Client Base
The PaXi Client Base implements the OPC .NET (Xi) specification and supports access to:
- OPC .NET server access thru WCF (Windows Communication Foundation) communication (replaces DCOM)
- Classic OPC DA, HDA, AE server thru DCOM communication
- OPC UA servers (DA, HA, AC functionality) thru the UA communication stack for .NET
The application can access any number of servers in any combination.

 

OPCDA.NET client component
The Classic OPC DA (Data Access) interface is implemented in .NET classes. All OPC DA V2.05 and 3.0 features are supported. In a layered class structure the upper level classes provide server access features with a minimal amount of code. OPCDA.NET can be combined with OPCHDA.NET and OPCAE.NET for HDA (Historical data access) and Alarm&Events.

  • UA Option
    UA servers can be accessed thru the same API as OPC DA servers. Existing OPCDA.NET based client applications can be upgraded to support UA without application code changes.
  • Xi Option
    OPC .NET (Xi) servers can be accessed thru the same API as OPC DA servers. Existing OPCDA.NET based client applications can be upgraded to support Xi without application code changes.

 

OPCAE.NET client component
The Classic OPC AE (Alarms&Events) interface is implemented in .NET classes. All OPC AE V1.1 features are supported. In a layered class structure the upper level classes provide server access features with a minimal amount of code. OPCAE.NET can be combined with OPCHDA.NET and OPCDA.NET for HDA (Historical data access) and DA (Data Access).

  • UA Option
    UA servers can be accessed thru the same API as OPC AE servers. Existing OPCAE.NET based client applications can be upgraded to support UA without application code changes.
  • Xi Option
    OPC .NET (Xi) servers can be accessed thru the same API as OPC AE servers. Existing OPCAE.NET based client applications can be upgraded to support Xi without application code changes.

 

OPCHDA.NET client component
The Classic OPC HDA (Historical Data Access) interface is implemented in .NET classes. All OPC HDA V1.2 features are supported. In a layered class structure the upper level classes provide server access features with a minimal amount of code. OPCHDA.NET can be combined with OPCDA.NET and OPCAE.NET for HDA (Historical data access) and Alarm&Events.

  • UA Option
    UA servers can be accessed thru the same API as OPC HDA servers. Existing OPCHDA.NET based client applications can be upgraded to support UA without application code changes.

 

XMLDA.NET client component
Thru the XML DA API the client application can access:
- XML DA servers with .NET2 or .NET3 (WCF basicHttp) communication
- OPC DA V2.05 and 3.0 servers
XMLDA.NET is especially well suited for .NET2 web client applications.
XMLDA.NET is often used in combination with XDAGW-SS server-side XML DA gateway. The client application can access local OPC DA servers directly or remote server thru the XML DA gateway.

 

home | contact us | return policy | privacy policy | security policy | Copyright © 2016 Advosol Inc. All Rights Reserved.