.NET Client Development Toolkits

Member: Advosol Inc.

Product website: advosol.com/category/3

.NET based client development toolkits for all OPC specifications.
Advosol offers .NET based toolkits for the development of OPC client applications. Many of the toolkits support multiple OPC specifications to simplify the migration to the newer OPC specification that don't use DCOM.
Developers can choose the OPC specification for the application interface independently of the OPC server interface. E.g. the API can be the widely used and known Classic OPC DA for the access of OPC UA servers.

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. The EasyUA DLL contains a layered set of classes that make the UA server access very simple and on the other hand give the user full control over the server access by using the lower level classes.

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 AE (Alarms&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

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 AC servers can be accessed thru the same API as OPC AE servers. Existing OPCDA.NET based client applications can be upgraded to support UA 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 Alarms&Events.
UA Option
UA HA 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.

 


Back