 |
|
Xi Client Components
| Product |
Summary |
Version Info |
| 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. |
|
| PaxiCF |
The PaXiCF SDK greatly simplifies the development of Express Interface (Xi / OPC .NET 3.0) client applications for the .NET Compact Framework. |
|
| PaxiSL |
The PaxiSL Silverlight-4 component provides a set of classes for access to Express Interface (Xi / OPC .NET 3.0) servers. |
|
| OPCDA.NET-Xi |
The OPCDA.NET-Xi aad-on option extends the OPCDA.NET Client Component with an OPC .NET (Xi) ExpressInterface wrapper.
The application can access classic OPC DA and OPC .NET (Xi) servers through the same API. |
|
| OPCAE.NET-XI |
The OPCAE.NET-Xi add-on option extends the OPCAE.NET Client Component with an OPC .NET (Xi) ExpressInterface wrapper.
The application can access classic OPC AE and OPC .NET (Xi) servers through the same API. |
|
The Advosol Express Interface (Xi / OPC .NET 3.0) client components provide the base for interoperable Xi client applications.
|
PaXi Client Component for .NET 3.5 / 4
The Advosol PaXi client component greatly simplifies the development of native Xi client applications.
There are classes with convenient methods for asynchronous and synchronous server access. Asynchronous access enhances the quality of user interface applications because the application doesn't become unresponsive in possibly slow access to an Internet based Xi server.
PaXi offers Visual Studio toolbox components for basic server access handling. Instead of writing code the functionality can be selected in Visual Studio Designer editors.
|
|
|
Xi Option for OPCDA.NET
OPCDA.NET based client applications can access 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 server name specified in connect, either the OPC DA DCOM server the Xi Web Service is accessed.
For Xi server access DCOM is completely eliminated because the Xi handling is within the OPCDA.NET component. There is no external DCOM to Xi wrapper involved.
Without additional application development effort the application can access DCOM OPC DA server and Xi web services.
Xi is specified with a structure and functionality similar to OPC DA, making the DA/Xi wrapping fast and reliable.
|
 |
|
Xi Option for OPCAE.NET
OPCAE.NET based client applications can access Xi servers without having to be modified. The applications only need to be compiled with a reference to the OPCAE.NET component with the Xi option. Depending on the server name specified in connect, either the OPC AE DCOM server the Xi Web Service is accessed.
For Xi server access DCOM is completely eliminated because the Xi handling is within the OPCAE.NET component. There is no external DCOM to Xi wrapper involved.
Without additional application development effort the application can access DCOM OPC AE server and Xi web services.
Xi is specified with a structure and functionality similar to OPC AE, making the AE/Xi wrapping fast and reliable.
|
 |
|
PaxiCF Client Component for the Compact Framework
The Advosol PaxiCF client component greatly simplifies the development of OPC .NET client applications for WindowsCE or other .NET Compact Framework platforms.
The clients are .NET applications communicating with WCF. Classic OPC servers are accessed through an Xi converter server. Such converters will be provided with classic OPC servers and are available from Advosol or the OPC Foundation for OPC Foundation members.
|
|
|
PaxiSL Client Component for Silverlight
The Advosol PaxiSL client component greatly simplifies the development of OPC .NET client applications for Silverlight.
Classic OPC servers are accessed through an Xi converter server. Such converters will be provided with classic OPC servers and are available from Advosol or the OPC Foundation for OPC Foundation members.
|
|
|
|
|
