See purchasing information for more details
Download Free Demo

Product Overview

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

With the OPC XML-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.



  • Provides a single, reliable connection point to access data from multiple OPC XML-DA servers on local and remote machines
  • Enables optimized performance of OPC XML-DA 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 XML-DA server
  • Allows connectivity to multiple OPC XML-DA servers from clients that do not support multiple connections or handle multiple connections well
  • Allows connectivity to OPC XML-DA servers using different interfaces supported by clients, such as DDE, Wonderware SuiteLink, GE NIO, and so forth
  • Supports update by exception (Watchdog)
  • Can automatically import OPC XML-DA Server Items



Supported Devices

  • Any OPC XML-DA Server

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) Clients
  • SuiteLink and FastDDE for Wonderware

Release Notes



  • Fixed an issue where back-to-back writes of the same value to the same tag caused the tag quality to change to bad.



  • Disabled support for all versions of SSL/TLS older than v1.2. This change affects users referencing ‘HTTPS Security’ in the server endpoint URL.



  • Fixed an issue where the driver does not poll as expected from the update/poll rate.



  • Fixed an issue where the driver would not poll as expected according to the update/poll rate due to updating the last update/poll time after, rather than before, processing reads.



  • Revised the Update Mode logic to allow more than one simultaneous subscription and prevent orphaned items and subscriptions.



  • Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
  • Resolved an issue where the “KeepAlive” message was no longer sent under adverse network conditions.
  • 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.



  • Added support for 64-bit data types, including QWord, LLong, and arrays of these two types.



  • Fixed issues that were encountered when browsing for items on certain devices (such as SIMOTION controllers). Tags with the default data type can now be added and the data type will be determined on its first read.
  • Added the ability to use the Max Items per Read setting when using Exception mode.
  • Improved browsing speed when not using the leaf filter.


  • Fixed an issue where one tag with a bad address would cause all tags to have bad quality with certain XML-DA servers.
  • Added support for HTTP Authentication.
  • Added the item path to the tag address. The new syntax is <ItemPath><Delimiter><ItemName>. Tag import will read the item path; if it's not empty, it will build the tag address as displayed above. Users can specify the item path in Static Tags (which are manually created) in the same way. For a list of allowed item path delimiters, refer to the "Channel Setup" topic located in the help file.
  • Added the channel and device names to the "The item path <Channel>.<Device>.<ItemPath> is no longer available in the server address space" error message.
  • Added the item path (if it is not empty) to the "The item name <channel Name>.<Device Name>.<Item Path><delimiter><Item Name> is no longer available in the server address space" error message.


  • Fixed faulty browsing logic where the driver would continue attempting to browse after an error was encountered. This could result in the driver being stuck in a loop while browsing.
  • Corrected a failure to import tags from servers that do not return the item name in the GetProperties response.
  • Fixed a defect where if the target XML-DA server returned OPC quality for an item, the driver would set the tag quality to Good during a subscription poll refresh.


Initial release of a new driver used to connect to Third Party OPC XML-DA Servers.

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: