DA Junction Control
The DA Junction control is a customized .NET control that enables Visual Basic .NET and C# programmers to easily develop OPC client applications that access any OPC DA servers. No detailed knowledge of OPC Data Access interfaces is required. The DA Junction will perform the connection handling procedure between your custom client application and the OPC server, as well as monitor and reconnect when necessary.
ClientAce DA Junction Features:
- The component completely covers the connection handling procedure for one or multiple OPC servers.
- Conversion of OPC data from different OPC Data Access interfaces into .NET data types.
Server Browser Control
The Server Browser control
provides functionality to browse OPC Data Access servers on local and remote machines. The Server URL is returned in an event to be used in the application for establishing connections and data acquisition.
Item Browser Control
The Item Browser control provides functionality to browse Tags/Items in an OPC Data Access server on local or remote machines. Items/Tags are selected and their information is returned to the application. The selections are used to request updated data from the server.
|
Channel Settings Control
The Channel Settings control provides functionality to view and make certain changes to the properties of a channel and devices within an OPC server provided by Kepware Technologies. The ability to write to System level tags must be enabled in the server.
Server State Control
The Server State control provides functionality to view the properties of a Kepware OPC Server project. The Properties include, the number of Clients connected to the server, total number of tags added by the clients and the total number of tags that are actively being polled.
ClientAce .NET API
The ClientAce .NET Application Programming Interface (API) provides users of languages such as C# and Visual Basic .NET with a simple, intuitive and optimized class library to quickly develop OPC client applications for accessing OPC servers.
ClientAce .NET API Features:
- A simple, intuitive .NET interface.
- The OPC Data Access interface has been simplified down to the major functions.
- No detailed knowledge of the different OPC Data Access interfaces is required.
- The API covers the different base technologies of OPC, for example, COM and DCOM.
- The API completely covers the connection handling to one OPC Server.
- The development of OPC Client applications with C# or Visual Basic .NET becomes very simple using ClientAce.
- Conversion of OPC data from different OPC Data Access interfaces into .NET data types.
- Fast and simple search for OPC COM Servers, both local and remote.
- High performance and optimized Client-Server communication by using kernel functionality implemented in C++.
Licensing:
- Design-time license per development seat
- Requires an initial 1-year service agreement
- First-year service agreement is mandatory
- Applications are subject to a 1-hour demo timeout (with reminder pop-ups)
- After purchase of a license, the application can be signed to avoid the timeout & pop-ups
- The signing utility is included with ClientAce
Free tools included with ClientAce install:
- Sample Server (rename of KEPServerEX)
- Simulation device driver
- VB.NET sample client applications
- OPC Quick Client
- 1-hour demo
Quick Links
|
| |
|
Microsoft Visual Studio Requirement
ClientAce is currently supported for Microsoft Visual Studio 2003, Visual Studio 2005 and Visual Studio 2008.
Note: Supported environments are C#, J#, and VB.Net. ASP.net is not supported by ClientAce at this time.
PC Hardware Requirements
Refer to Microsoft's .NET Framework hardware requirements for the version that will be used in the Visual Studio project:
- 100 MB available disk space
- Microsoft Visual Studio Requirments
When deploying the custom client applications created using ClientAce, the .NET Framework requirements depend on the version of Visual Studio that was used for development. For more information, refer to the appropriate section in Deploying Your Client Application.
|
PC Software Requirements
The following requirements must be met in order for the application to operate as designed:
- Microsoft Windows operating system requirements are the same for both ClientAce and the Microsoft Visual Studio development environment that is used to develop ClientAce applications. If the operating system's requirements for the version of Visual Studio being used does not list the operating system intended for use, then ClientAce is not supported for use on that operating system.
- UAC on Windows Vista and Windows 7
- To ensure that all components function correctly in the design environment, turn UAC off on machines being used to develop applications with ClientAce.
- UAC limits access to folders and files in the design environment, which will affect some objects in the design environment. UAC does not affect these objects in the Runtime environment.
|
| Additional Information and Resources:
|
Related Products:
|
|
|
