OPC DA .Net Client Development Component |
|
Online Reference Manual
|
OPCDA.NET is a .NET component for the development of OPC DA client applications with C# or VB.NET. It provides classes, controls and tools for the efficient development of high quality .NET (C# or VB) OPC DA client applications. OPCDA.NET is the only .Net wrapper that supports 32-bit and 64-bit operation on Windows XP, Vista and Windows-7 systems. The .Net wrapper assembly and the utilities are provided in a version for .Net Framework 4, 2 and 1.1. Many samples applications are provided with projects for Visual Studio 2010, 2008, 2005 and 2003.
OPCDA.NET has a multi-layered class structure. The user can choose the interface layer according the application requirements and the personal preferences.
- The server access Controls reduce application coding to a minimum. These invisible controls are configured in the Visual Studio Designer and handle the OPC server access with extensive error checking.
- The QuickUse classes provide simple to use methods for data binding, item browsing and synchronous/asynchronous item read/write access. Minimal OPC knowledge is required.
- OPC DA V3 server access methods. All OPC DA V3 defined (mandatory and optional) functions can be accessed through methods that handle all data type conversion to/from .Net data types.
- OPC DA V2.05 server access methods. All OPC DA V2.05 defined (mandatory and optional) functions can be accessed through methods that handle all data type conversion to/from .Net data types.
|
|
|
|
|
The Professional Edition offers features that improve the application quality without increasing the development effort.
- The DAServer/DAGroup Controls are configured in the Visual Studio Designer and handle the OPC server access and callbacks.
- The Background Server Access classes handle all server access in background threads and prevent the application from becoming unresponsive due to long DCOM communications timeouts or long server processing times due e.g. to slow device access.
- The ItemList Builder/Loader makes coding cleaner, simpler, quicker and better maintainable.
- The convenient OPC DA V3 Browse and GetProperties methods can be used with OPC DA V2 servers.
- The OPCDA.NET-UA option can be added to the project to enable the application to access OPC DA and OPC UA servers through the same API.
See more details in the Feature Comparison.
Download the evaluation version for hands-on tests or study the feature details in the Online Reference Manual
|
|
Access to UA Servers OPCDA.NET with the OPCDA.NET-UA option enables clients to access OPC DA and OPC UA servers through the same API. No external converters are required. DCOM is completely eliminated.
|
OPC Server Access Controls
The OCP Server Access controls are easy to use and handle the OPC server access efficiently and with extensive error checking. The controls are invisible, doing the background work. To add OPC server access to a Windows Form or Service application, drag the controls from the Visual Studio Toolbox to the application design pane and configure the properties. The configuration is supported by dialogs. Servers and items can be browsed and selected. All OPC server access is asynchronous. Requests from the application are queued and success/error is reported in the completion handler, simplifying the application error handling. |
DAServer Control |
Connects to one OPC server and periodically checks the server connection. |
DAGroup Control |
Handles Read, Write and DataChange callbacks for any number of items. Items can be assigned to a control or to a method to eliminate application callback handling. Application coding is reduced to handling special cases. |
|
QuickUse Classes Browse functions display the items directly in a TreeView control. Items can be read or written with a single, very simple method call using either synchronous or asynchronous access. For asynchronously accessed items the QuickUse class maintains a data buffer and handles the data change callbacks. The user can read the current value from the buffer or request a notification. OPCDA.NET V4 added support for data binding subscriptions that refresh the item values directly in Windows controls and user classes, no user callback handlers are required.
Large View
Read more about DataBinding Subscriptions.....
|
Private Sub btnConnect_Click(ByVal sender As System.Object, _
ByVal e As System.EventArgs) Handles btnConnect.Click
ListView1.Items.Clear()
ListView1.Items.Add("")
ListView1.Items.Add("")
Try
tbStatus.Text = "Connected"
OpcBind= New OpcDataBind(Me, cbOPCServers.Text)
OpcBind.Subscribe("SimulatedData.Signal", CheckBox1)
OpcBind.Subscribe("SimulatedData.Ramp", ProgressBar1)
OpcBind.Subscribe("Dynamic.Analog Types.Double[]", _
ListView1.Items(1).SubItems, 0)
Catch ex As OPCException
tbStatus.Text = ex.Message
End Try
End Sub
Private Sub btnDisconnect_Click(ByVal sender As System.Object, _
ByVal e As System.EventArgs) Handles btnDisconnect.Click
OpcBind.Disconnect()
tbStatus.Text = "Disconnected"
End Sub
|
OPC DA Methods This interface layer provides access to all OPC DA server functions including functions such as item properties and server management. User with some OPC experience will find this layer easy to use, all data is passed in .Net data types. The project creation wizards create functional sample code with the features selected in the wizard dialog. The OPCDA.NET Professional Edition does emulate some OPC DA V3 methods for OPC DA V2 servers.
Documentation and Support Extensive documentation is provided as a Help2 Visual Studio plug-in that offers context sensitive help. Phone/email support is free and questions are answered with short response times.
OPCDA.NET overview:
|
the OPC DA V2/V3 functions are provided as methods with easy to use .NET interface. |
|
.NET 1.1 - 4.5 versions provided that work on Windows XP and newer systems including Windows Vista in 32-bit and 64-bit mode. |
|
the Visual Studio 2003/2005/2008/2010/2012 project wizards create VB or C# application projects with a functional client that connects to an OPC server and browses the items. |
|
the Visual Studio 2005/2008/2010/2012 class wizards add an OPC server access class to an existing project. |
|
Visual Studio 2005/2008/2010/2012 code snippets speed the client coding. |
|
Many sample applications in VB and C# source code illustrate the server access |
|
the OPC DA V2 and OPC V3 test clients can be used to check the server behavior |
|
the OPC DA V2/V3 simulation test server can be used as a reference |
|
the extensive reference documentation plugs into Visual Studio 2005, 2008 2010, 2012. Context sensitive help displays the needed information without long searches. |
|
extra classes are provided for typical tasks like browsing servers or items. These methods return the result in Windows control compatible lists that can be directly displayed. |
|
classes for background server access prevent applications becoming unresponsive. |
|
ItemListBuilder tool and ItemListLoader class for clients that use a pre-defined set of items. |
|
OpcSecurityAnalyzer tool helps resolve DCOM settings issues. |
|
the .NET interface is wrapped directly to the custom interface with custom marshalers, offerering top performance |
OPCDA.NET is a top performance .Net wrapper that marshals .Net calls directly to the OPC custom interface, without an ActiveX or OPC Automation layer. All OPC DA V2/V3 defined functions are supported. Additional classes for browsing and item access simplify the the client development considerably.
Wizard The project generation wizard generates the OPC server access code according the user selections. The generated code is fully functional, easy to understand and an excellent starting point for any OPC client application.
Browse Support OPCDA.NET provides excellent browse support, making the interactive selection of items real simple. With one method call the server can be browsed into an in-memory TreeNode structure or directly into a TreeView control.
The BrowseShowTree class shows branches and items in a single TreeView control. Only single nodes can be selected in a TreeView control. |
The BrowseShowTreeList class shows the branches in a TreeView control and the items of the selected branch in a ListView control. Multiple items can be selected in the ListView control. |
|
|
Browsing a single branch is also made simple. The convenient OPC DA V3 Browse and GetProperties methods can be used with OPC DA V3 and V2 servers.
Background Server Access Each OPC server access can possibly take seconds or even minutes due to either long DCOM communications timeouts or due to long server processing times that may be caused e.g. by slow device access. The OPCDA.NET background server access classes handle all server access in background threads and prevent the application becoming unresponsive during the server access. The application quality can be greatly enhanced without additional develoment effort. The application becomes also highly robust, all server access is time limit checked and the server connection is monitored even without the application making a server access. View the C# sample code to see how short and simple a high quality OPC DA client application can be. Visual Studio 2005 code snippets are provided for all methods.
ItemListBuilder / ItemListLoader Some client applications access a single OPC server and a pre-defined set of items. OPCDA.NET also provides excellent support for such applications. Instead of coding the item names into the application the OPCItemDef array required in Group.AddItems() can be created from an XML file by the ItemListLoader helper class. The XML item definition file is created interactively with the ItemListBuilder utility. The XML File can optionally be embedded in the client EXE file. A separate XML file makes the application easy to modify. An embedded XML file prevents changes without recompilation.
|
Large View |
Large View
|
|
Visual Studio integrated Help Comprehensive help documentation integrates into Visual Studio offering context sensitive help. A utility is provided to view the Help2 documentation outside of Visual Studio.
|
|
|
Large View |
|
Error Lookup Utility The OPC error codes and OPC related Windows error codes are explained. The utility also explains OPC quality codes.
|
|
OPC DA V2 Test Client Easy to use test client that uses OPCDA.NET for the server access. The server access can be tested with the same .Net wrapper as used in the OPCDA.NET based application. |
Large View |
|
|
OPC DA V3 Test Client Test client that uses OPCDA.NET for the server access. Most OPC DA3 features can be interactively tested. |
Large View |
|
Sample Applications Many sample applications are provided for C# and VB.NET, complete with Visual Studio 2003 projects. The projects are tested to convert and compile with Visual Studio 8 (2005). The samples show how the many OPCDA.NET features can be used and the samples can be used as the starting point for user applications.
Browse |
Shows how the OPC server can be browsed and items displayed and selected. The high-level BrowseTree classes are used. |
BrowseV3 |
Shows how the OPC DA V3 Browse method can be used to browse the items in a branch and reading all item properties. Only the Professional Edition supports these Browse methods for OPC DA V2 servers. |
BrowseLowLevel |
Shows how the OPC server can be browsed using the OPC DA V2 defined Browse support functions. This application can also be used to find eventual non-compliances in the server browse interface. |
Background Server Access |
Shows the usage of the Professional Edition background server access classes. All server access is handled in background threads to ensure that the application never freezes, even with the OPC access hanging in a DCOM timout due to communication failure. |
DataBind |
Shows how the DataBind class can be used to display OPC item values in different types of Windows controls without the user having to code callback handlers. |
Item Lists |
OPC calls are made with item lists that are loaded from an XML file. The XML ItemList definition file was created with the ItemListBuilder utility. This feature is available only in the OPCDA.NET Professional Edition. |
Properties |
This sample client shows how the OPC server can be browsed and items properties queried and read. |
Read |
This client uses the RefreshGroup class to asynchronously read the values of two items. Server and item names are hard coded into the program. |
Update |
This sample client uses the OPCDA.NET QuickUse RefreshGroup class to periodically update one item through data change callbacks. |
Windows Service |
This sample shows how a Windows service can access OPC servers. The values of three items are transferred to other items in the same server. Multiple OPC servers can be accessed by creating multiple OpcServer objects. |
Sample Client |
Simple test client application with browse, read, write, subscribe features. |
Many additional sample Windows applications can be created with the project wizards. The features added to the code can be selected in a dialog. With only the code for the selected features the created application are easy to understand and extend to meet the user requirements.
OPCDA.NET Features Include |
|
VB .NET and C# Wizards for Visual Studio 2005, 2008 2010 and 2012 |
|
Wrapper DLL versions for .NET Framework 1.1, 2.0/3.0/3.5 and 4.0/4.5 |
|
Full source code available |
|
Visual Basic .NET sample clients |
|
VC# .NET sample clients |
|
All kinds of applications including Windows Services |
|
OPC V2/V3 simulation test server |
|
Visual Studio 2005/2008/2010/2012 integrated, context sensitive help |
|
Site license with one time license fee, no royalties. |
|
Updates/Support subscription included for 90 days. |
|
Can be combined with OPCAE.NET for Alarms&Events handling |
|
Can be combined with OPCHDA.NET for Historical Data Access |
System Requirements |
|
Windows 7, 8.x,10 or Windows Server 2008,2012,2016 ,NET 4.x 32 or 64 bit |
|
Visual Studio 2010,2012,2013,2015,2017 C# or Visual Basic |
|
Evaluation Download
Download the free Evaluation Version by clicking 'Add to Cart' below. This is a full featured version including the sample client source code. However it has to be restarted after 30 minutes run-time.
Top ranked at PerfectDownloads.com |
Top ranked at Download25.com |
Editor's pick at Top4Download.com |
|
Download the evaluation version for hands-on tests or study the feature details in the Online Reference Manual
Alternate Approaches OPCDA.NET is strutured according the OPC DA interface specification. OPC DA servers can also be accessed thru components with a different application interface.
XML-DA application interface XMLDA.NET offers an alternate approach for developing .Net based OPC DA clients. If performance is not paramount then the more complex XMLDA.NET wrapper may be used and the client can be developed as an XML-DA client. XMLDA.NET is a fully compatible replacement for the XML-DA .Net web services proxy stub and wraps XML-DA client calls to OPC DA V2 server calls. The client is developed as an XML-DA web service application and is ready to be used with XML-DA servers. OPCDA.NET based clients can access XML-DA servers thru the XDAGW-CS gateway. The OPCDA.NET and XMLDA.NET products offer flexible solutions with performance characteristics. OPCDA.NET is optimized for OPC DA server access and XMLDA.NET is optimized for XML-DA servers. There are fundamental differences between OPC-DA and XML-DA that make it impossible for one client design to have high performance access to both kind of servers. |
|
OPC .NET (Xi) application interface The PaXi client base implements the OPC .NET (Xi) specified interface. OPC .NET combines the functionality of the classic OPC DA, AE and HDA in to single, WCF (Windows Communication Foundation) based interface. PaXi based applications can access Xi servers thru WCF comunication and classic OPC DA, AE, HDA server thru DCOM communinication, without external converter servers.
OPCDA.NET based clients can access Xi servers with WCF communication thru the DAEToXi converter server. Performance is similar but with PaXi no external converter servers need to be installed, configured and maintained. Some rarely used OPC DA features are not accessible thru the OPC .NET (Xi) interface.
|
|
|