OPCDA.NET-Xi _Develop Controls_Develop Controls Versioning_COGITO SOFTWARE CO.,LTD English Website

OPCDA.NET-Xi

OPCDA.NET-Xi
OPC .NET (Xi) ExpressInterface Option for the OPCDA.NET Client Component.

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

OPCDA.NET based client applications can access OPC .NET (Xi) servers without having to be modified. The applications only need to be compiled with a reference to the OPCDA.NET component with the Xi option.

Depending on the name of the connected server, either the OPC DA DCOM server or the Xi Web Service is accessed.

For Xi server access DCOM is completely eliminated because the Xi handling is within the client process. There is no external DCOM to Xi wrapper involved.

Without additional application development effort the application can access DCOM OPC DA server and Xi (OPC .NET) web services.
Xi is specified with a structure and functionality similar to OPC DA, making the DA/Xi wrapping fast and reliable.

OPCDA.NET-Xi Advantages

The OPCDA.NET-Xi component enhances existing OPCDA.NET based OPC DA client applications with the capability to access OPC .NET (Xi) servers.
No code changes are required in the OPC DA application. Only the OPCDA.NET assembly references need to be changed to the assembly version with Xi (OPC .NET) support.
New client applications can be developed to support access to the widely installed classic OPC DA servers as well the new Xi (OPC.NET) servers.
For Xi server access DCOM usage is completely eliminated, unlike solutions with an external Xi wrapper server.

With the client application able to access OPC DA and OPC Xi server there is no need for external converters. This simplifies the installation, the configuration and the maintenance of the application. No converter (wrapper) 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 DA server access there is an efficient .NET wrapper that handles the DCOM interface. For Xi server access the .NET code performs the WCF communication without involving native code.

OPCDA.NET-Xi Limitations

The OPC .NET (Xi) server access is limited to the Data Access (DA) profile of the Xi server. The Historian (HDA) and Alarm&Event (AE) features of the Xi server cannot be accessed through the OPC DA client interface.
For application that require access to all features of the Xi server the PaXi client component needs to be used.

OPCDA.NET-Xi Feature Summary

.Net applications can access OPC DA and OPC .NET (Xi) servers through the same API
All OPCDA.NET classes can access DA and OPC .NET (Xi) servers
The server type is determined by the server name (ProgID or URL)
The automatic Xi configuration fits most applications
Specific Xi configuration settings can be defined in the application configuration file or in properties of the Xi classes
High performance for DA and OPC .NET (Xi) server access
Pure .NET code that runs in 32-bit or 64-bit for DA and Xi server access

Requirements

OPCDA.NET V9.0 or newer
.NET 3.5, or 4.0/4.5
Visual Studio 2005, 2008, 2010 or 2012