Used for reading/writing of real-time data with OPC DA 1.x, 2.x, and 3.x servers connected to control system devices such as PLC, DCS, etc. devices such as PLC, DCS, etc.
As supported by your OPC A&E server, access process alarms, operator actions, informational messages
In OPC UA, the functionality of classic OPC Data Access (DA) is called generic data. OPC Data Client supports full read/write subscribe capabilities and more.
OPC Data Client provides simple methods and event handlers provided to work with OPC UA servers that follow the Alarm & Condition Facet standards.
The OPC UA specifications provide for means for industry organizations and users to define complex data models where a node is no longer just a single value. A node might be a structure, also known as a User Defined Type (UDT) containing multiple values of differing data types.
OPC Data Client provides methods for reading, writing, and subscribing to complex data within an OPC UA Server. The Siemens S7-1500 PLC is an example of a device that has a built in OPC UA server that supports UDTs or structures.
Part 14 of the OPC Unified Architecture adds the ability to deliver data sets using message-oriented middleware. Starting with Version 2019.2 (5.56) and higher of the OPC Data Client toolkit, these features are supported in the Ultimate Edition product license.
With thanks to Matthis Damm of AscoLab from his OPC Day presentation for the infographic
OPC XML-DA was a predecessor to OPC UA that was widely adopted in applications where OPC XML-DA servers were placed into devices that were to be connected over radio networks and non-Windows environments. Wind turbines from Siemens and others are the most common device where OPC XML-DA servers are found.
Software Toolbox was a Charter Member of the OPC Foundation, joining back in 1996 when the standards were still being written, because we believed in what standards could do for industrial automation.
Throughout our history, we and our partners have remained committed to the process of OPC Interoperability Testing and OPC Compliance Testing. The OPC Data Client is regularly tested at the OPC Foundation's OPC Interoperability Workshops and has passed their independent lab testing process. These processes involve testing the toolkit and it's reference samples against many different OPC servers from other vendors, and working together with those suppliers to insure our products work well together.
Every application need is unique. If you were a carpenter, you would not use a hammer to insert a screw. We know development is no different, so OPC Data Client provides different development models for building your x86 and x64 applications.
Each model is complemented by our developer productivity features and extensive documentation and help.
We understand the job of being a developer and want to go beyond just providing a set of tools that reduces your need to know the details of the OPC specifications. The OPC Data Client delivers productivity in several areas
Don't reinvent the wheel, we have the tools. Browsing for OPC servers and items is common functionality you should not have to build yourself.
OPC Data Client includes ready-to-use, rich UI browsing dialogs that do not need to be placed on a form. They can be called from your code and used.
Browsing controls are intended to be placed on your UI form and adjust the visual appearance and behavior to integrate more closely with your applications.
Working with OPC UA brings new concepts designed to aid in working with multiple OPC UA server applications and managing the certificate based trust and security provided by the standard.
OPC Data Client provides several objects to help you avoid writing unnecessary code.
The Connectivity Explorer application allows you to connect to and browse the data hierarchy of OPC Data Access and OPC Unified Architecture servers and data nodes. You can subscribe to data changes, and view the results live. With the optional Excel Add-On you can setup Excel Real Time Data (RTD) links to data.
This optional feature can be added to any OPC Data Client License, allows you to drag/drop or copy/paste values from the OPC Data Client Connectivity Explorer into Excel.
Data transfers are done using the Excel Real Time Data (RTD) function. This feature works with OPC DA, OPC XML-DA, and OPC UA Generic Data.
Full details for all versions are provided in our knowledgebase. Below is a high level of currently supported platforms for your x86 or x64 development.
Linux and macOS
OPC Data Client is specifically designed with broad development language support in mind, allowing you to develop an OPC client in a wide range of languages.
Click for full development language details
COM development - including but not limited to:
Most OPC client development is done on Windows, using .NET Core, .NET Standard, or .NET Framework. Current supported platforms and .NET versions are detailed in our knowledgebase however here is a high level list.
We know that sometimes it helps to see someone showing you how to do things. We have a wide range of videos available for the OPC Data Client product from short
OPC Data Client documentation is all available online for review. Documentation includes coverage of how to get started, development models, method calls, extensive sample code, best practices, troubleshooting, and more.
With any development tool, there are many details that you may be interested in learning more about. In addition to our online documentation, these are some of the more common areas of interest.
For .NET Standard OPC UA, uses OPC Foundation's OPC UA .Net Standard Library 1.4.360.33
For .NET Framework OPC UA, uses OPC Foundation UA-.NET-Legacy libraries as of March 25, 2020
Development is possible for x86 or x64 applications, full details under "64-bit platforms" in the product documentation.
If you have a technical question you have not been able to find an answer to yet, please contact our support team and they will work to answer your question, even before you have purchased any licenses.
The demo is the full product. Once the OPC Data Client is connected to an OPC Server, it will run for 30 minutes at a time. The 30–minute timer will be disabled after 210 days from the initial version release.