OPC DA Client

See purchasing information for more details
opc da client demo download

Product Overview

The OPC DA Client driver and KEPServerEX communications platform provide an easy and reliable way to connect disparate third-party OPC DA Servers to your client applications, including HMI, SCADA, Historian, MES, ERP, and countless custom applications.

With the OPC DA Client Driver and KEPServerEX, you can manage operations through a single server interface, so there is no need to learn the different nuances of other third-party servers.

This driver also enables Oracle MES and MOC users to bring Kepware OPC operations and all other third-party OPC operations into your business applications.

Resources

Performance

  • Provides a single, reliable connection point to access data from multiple OPC servers on local and remote machines
  • Enables optimized performance of OPC servers through OPC groupings that may be different than those required or allowed by your clients
  • Supports connection monitoring and reconnect behavior for each OPC server
  • Provides connectivity to remote OPC servers for clients that do not support DCOM
  • Allows connectivity to multiple OPC servers from clients that do not support multiple connections or handle multiple connections well
  • Allows connectivity to OPC servers using different interfaces that are supported by clients, such as DDE, Wonderware SuiteLink, GE NIO, and so forth
  • Supports update by exception (Watchdog)
  • Automatically import OPC Server Items

Protocols

  • OPC Data Access (DA)

Supported Devices

  • OPC DA Servers: 1.0 and 2.0

Available Languages

  • English

Application Support

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • OPC .NET Service (OPC .NET) Version 1.00
  • OPC Alarms and Events (OPC AE) Version 1.10
  • OPC Data Access (OPC DA) Versions 1.0a, 2.0, 2.05a, and 3.0
  • OPC Unified Architecture (OPC UA) Version 1.02
  • SuiteLink and FastDDE for Wonderware

Release Notes

6.3.273.0

9/27/2017

  • Improved performance when collapsing/expanding/importing items using the Browse Import Items dialog.
  • Fixed an issue where consecutive writes of the same value could result in bad tag quality.

6.2.429.0

6/8/2017

  • Fixed a crash issue when loading a project with an OPC DA Client using OPC DA 1.0.

6.0.2107.0

11/15/2016

  • Fixed issue where removing invalid items could result in a runtime failure.

5.21.114.0

3/20/2017

  • Enhanced the driver to support DA 3.0 browsing.
  • Resolved an issue where removing invalid items could result in a hang of the runtime.

5.21.112.0

8/16/2016

  • Refactored how the driver re-adds failed items. When items were continuously added and removed by the client where at least one of the items was invalid, it could lead to “Bad” quality of valid items and instability of the runtime.

5.20.396.0

5/3/2016

  • Enabled 64-bit data type support (LLong, QWord).
  • Added support for OPC Item Access Path using $ symbol for delimiters.
  • Enhanced the driver to allow OPC DA Read and Write methods (Asynchronous or Synchronous) based on the Update Mode of the OPC Group. Asynchronous Read and Write methods are the default and remain the optimal choice for most applications.

5.19.467.0

10/20/2015

  • Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
  • Resolved an issue that could cause tag reads using ReadMaxAge to always read from cache.
  • Resolved an issue that could cause the client to receive a newly written value, then a stale cached value, before receiving the new value again. 

5.16.722.0

10/21/2014

  • Enhanced the OPC DA Client Driver so that it will now attempt to re-add failed items.

5.15.588.0

9/23/2014

  • Fixed an issue where the server could crash if an In-Process Server (which is a server that is a .dll not an .exe) threw an unhandled exception.

5.15.585.0

7/22/2014

  • Fixed an issue where AddGroup() calls would fail when CoInitializeEx () was called after CoInitializeSecurity ().

5.11.250.0

3/5/2013

Resolved an issue where the driver would invalidate tags if the remote server did not provide a supported data type when the item was added to the server. The driver will now wait for the first update before invalidating unsupported data types.

5.10.205

11/13/2012

  • Previously, the driver would automatically filter out the data types that it could not resolve in a browser. It will now import these tags using the Default data type, and will also post a message to the Event Log.
  • Fixed an exception that would occur when invalidating tags while unloading the driver.
  • Fixed a reconnect issue where the shutdown sink flag was not cleared.
  • Fixed an issue where valid data change events were thrown away because the driver received data change events on items before they were fully added.

5.9.170

6/26/2012

Fixed an issue in the Tag Import Browser where parent node tags would be imported even when only a child node was selected.

5.7.84.0

10/24/2011

  • Changed the default update rate from 50 milliseconds to 1000 milliseconds.

5.6.122.0

7/25/2011

  • Improved initial update performance when there is a mix of good and non-good data items from the underlying servers.

5.5.94.0

2/18/2011

  • Added support for two-dimensional arrays.

5.4.131.0

10/28/2010

  • When adding groups, the time bias is now properly initialized to zero. At this moment, this setting is not user-configurable.
  • Fixed an issue wherein the initial update was not passed on to client applications.
  • Removed the limit that prevented the creation of nested groups with depth greater than 8.

5.3.118.0

6/9/2010

  • The driver now reports a value, quality, and timestamp for invalid tags (tags that can't be added to the remote server). Previously we would keep attempting to read the tags, expecting an initial update. In the case that the tag is invalid, we won't receive an update, and should report the tag is Bad: Out of Service.
  • Improved performance of ATG.
  • The driver now removes all items from the underlying server when the DA Client's device is configured as disabled.
  • Fixed issue where the driver returned an invalid read value when an item did not receive an update from the DA Server. We now continue to process the read request until we have a valid return value.

What Is a Driver?

KEPServerEX is more than an OPC server—it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.

A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices.

Drivers may be licensed individually or in suites. Additional drivers can be licensed on demand as connectivity needs evolve.

Purchasing Information

This product is available for purchase through the following suites:

Document Spotlight

Create a tunnel with KEPServerEX that uses OPC UA to establish a connection across remote OPC applications.

Learn More

© PTC Inc. All Rights Reserved.