OPCDA.NET-Xi
OPCDA.NET-Xi |
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
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
Requirements
© Copyright 2000-2023 COGITO SOFTWARE CO.,LTD. All rights reserved