|
PaxiCF Features
PaxiCF offer classes with methods for access to all Xi specified methods and and additional methods that simplify the server access.
All methods are provided an a version for:
- synchronous server access.
This methods block the calling thread until the response is received from the server. In server calls from background threads this is fine. However, when used in a user interface thread then the application becomes unresponsive for the duration of the server call.
- asynchronous server access.
User interface threads should always use asynchronous server access. The application doesn't become unresponsive, even with slow server access.
PaxiCF handles the selection of the communication endpoints in a flexible way.
The application sets preference declarations and PaXiCF selects the best fitting endpoint available in the server:
- Endpoint Name
The endpoint with this name is used if it exists in the server configuration
- Security yes/no
Determines is a secure or non-secure endpoint is selected in case the server has endpoints configured with both kinds of bindings.
|
|
Classic OPC server access from .NET CF applications
DCOM based OPC server access is problematic from .NET Compact Framework applications.
The Express Interface is the solution - it uses WCF communication. Classic OPC servers are accessed through an Xi converter server. Such converters will be provided with classic OPC servers and are available from the OPC Foundation (for members) and from Advosol.
PaxiCF and XiTOCO offer a complete solution, using WCF communication instead of DCOM.
The XiTOCO converter server is installed on the same machine as the Classic OPC servers. The communication from the .NET Compact Framework application uses WCF, eliminating the need for DCOM support in .NET CF.
PaxiCF and XiTOCO are available as royalty free licenses, making the solution cost effective for low and high volume applications. |
