正在加载...

OPC UA Client

参见购买信息了解更多详情
OPC UA Client 演示下载

产品概览

Kepware 的 OPC 隧道通讯方案包含 KEPServerEX 连接平台和 OPC UA Client 驱动。OPC UA 统一架构开放标准用于为 KEPServerEX 两个实例之间的设备通信提供理想隧道:一个实例用作隧道客户端,另一实例用作隧道服务器。OPC UA Client 驱动与 KEPServerEX 实施的 UA 服务器接口配对以安全可靠地传输数据。

OPC 隧道通讯

此隧道通讯方案使用客户端/服务器架构,可穿过防火墙,安全而又可靠地实现跨 Internet、WAN 或 LAN的 实时数据通讯。它不依赖于 Microsoft COM 和 DCOM 技术,因此可在设备、数据源和应用程序之间轻松进行远程通信。

资源

性能

  • 支持 OPC DA 1.0 和 2.05a 的 OPC 隧道通讯
  • 经由 VPN 通过防火墙在 Internet、WAN 或 LAN 在企业网络中工作
  • 为 OPC、原生接口和 DDE 提供远程访问
  • 支持介质级别冗余,包括能够配置次要隧道和触发条件
  • 可通过 RSA 标准进行数据加密
  • 可通过 x509 证书进行端点身份验证
  • 自动查找 OPC UA 服务器
  • 支持结构化数据以实现通信和存储优化
  • 支持 Nano 配置文件以允许通过 OPC UA 访问嵌入式设备生成的数据
  • 具有自动生成标签数据库的功能
  • 能够设置 OPC UA 服务器优先级
  • 支持轮询或例外报告(数据更改时)
  • 对每个连接提供端点管理
  • 能够将第三方服务器数据与所有 KEPServerEX 驱动集成
  • 提供“保持活动”和“监视器”功能以确保可靠连接

协议

  • OPC Unified Architecture (UA)

可用语言

  • Simplified Chinese
  • 德语
  • 日语
  • 英语

应用程序支持

  • DDE Format CF_Text and AdvancedDDE
  • NIO Interface for iFIX
  • 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

发行说明

6.3.273.0

2017/9/27

  • 解决了以下问题:在 OPC 客户端驱动程序中连续写入相同值可能导致标签质量差。
  • 修复了以下问题:使用 NULL PolicyId 设置 AnonymousIdentityToken 的客户端被拒绝,其状态为 Status_BadIdentityTokenInvalid。
  • 通道数上限从 128 增加到了 256。

6.2.460.0

2017/7/6

  • 增加了中文支持。

6.2

2017/6/8

  • Localized custom dialog boxes for German and Japanese cultures.

6.1.601.0

2017/4/4

  • Enhanced the UA Client tag browser to import the components of complex variables. During import, the driver automatically imports components of complex variables when their data type derives from a supported built-in type or enumeration.
  • Enhanced browsing to allow importing all items as default data type.
  • Escaped spaces in OPC UA URLs caused issues for certain servers when connecting with security. Upgrading from KEPServerEX V6.0 to V6.1 requires re-issuing certificates to fix. Upgrading from V5.X to V6.1 re-issues the certificate automatically.
  • Resolved an issue where the driver did not re-subscribe to subscriptions that had timed out.
  • Resolved issue where the server could crash, resulting in "Invalid or missing user information" error messages until the server was re-installed or repaired. The issue could occur if there were multiple OPC UA Client driver channels attempting to connect simultaneously.
  • Transport layer disconnects are detected by the session watchdog, the timeout of which is now configurable. Enhanced reconnect logic to attempt to re-use sessions, subscriptions, and republish any missed data after a transport-layer disconnect.
  • Added support for UA Nano, Micro, and Micro Embedded UA Server profiles by eliminating the creation of monitored items for devices in 'Polled' mode. Devices in 'Polled' mode can now be configured to use registered or unregistered reads.

6.0.2107.0

2016/11/15

  • Added support for Asymmetric Key Size of up to 2048 bit.
  • Fixed an issue with connecting with a router using port forwarding.
  • Fixed a failure to connect to a server that doesn't support certificates or password security.
  • Fixed an issue with the user not being prompted to trust a certificate from the Channel Properties of the UA server when attempting to connect to an untrusted server.
  • Added notification for connected OPC DA clients when a write failed.
  • Fixed an issue with the MLR Switch on Failure not switching back to the primary OPC server correctly.
  • Added a property to control whether an explicit read occurs after a write.
  • Added German language support.
  • Added Japanese language support.

5.21.114.0

2017/3/20

  • Fixed an issue where consecutive writes of the same value could result in bad tag quality.
  • Added a property to control whether an explicit read occurs after a write.
  • Resolved an issue where the UA Client driver did not correctly resolve internal tags like _System tags.
  • Fixed an issue where the server could crash which would result in "Invalid or missing user information" error messages until the server was re-installed or repaired. The issue could occur if there were multiple OPC UA Client driver channels attempting to connect simultaneously.

5.21.112.0

2016/8/16

  • Fixed a buffer overflow that could result in a crash.
  • Fixed an issue where the driver could delete monitored items immediately after creating them.
  • Fixed an issue in Polled Mode where all items were set to “Bad” quality if a keep-alive or data change was not received within the watchdog timeout. These only apply to Exception Mode and are not required for Polled Mode.

5.20.396.0

2016/5/3

  • Added support for 64-bit data types (LLong, QWord).
  • Fixed a race condition that could result in a runtime crash in limited scenarios.
  • Improved driver to prompt the user to trust a connection to the UA server when creating an initial connection using security if the certificate is not yet trusted.

5.19.467.0

2015/10/20

  • Enhanced Automatic Tag Generation for a device object while one or more clients are actively connected.
  • 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.
  • Resolved an issue where the posted error message was not representative of the actual cause of the error.
  • Resolved an issue that caused tag import to hang while loading large branches of tags.

5.18.673.0

2015/8/17

  • Upgraded OpenSSL (open source library) to version 1.0.2d to address security vulnerabilities pertaining to certificate validation.

5.18.662.0

2015/6/23

  • The driver no longer creates subscriptions and monitored items for inactive tags. This allows the driver to act in a cold redundancy mode when used with the Media Level Redundancy plug-in.
  • Increased time for UA clients to disconnect when shutting down to allow for proper shutdowns.
  • Changed the driver to request both the server and source timestamps from the UA server. The driver uses the source timestamp supplied by the UA server if it is available. If it is not available, the driver uses the UA server timestamp. If that is not available, the driver sets the timestamp to the current system time.
  • Fixed an issue to allow importing a tag branch containing a tag with an unsupported data type.

5.17.495.0

2015/2/24

  • Enhanced the driver to reconnect the UA session after encountering an invalid Session ID error.
  • The Device _Error flag is now set if the driver is unable to connect on the initial connection.

5.16.722.0

2014/10/21

  • Changed the driver to pass through source timestamp to tags instead of server timestamp. The timestamp will not be updated if the source timestamp is not provided.

5.15.588.0

2014/9/23

  • The driver now passes the source timestamp instead of the server timestamp to tags.

5.15.585.0

2014/7/22

  • Enhanced the driver to support Media Level Redundancy.
  • Modified the self-signed certificate to make the AppURI and SubjectAltName fields equal for OPC UA Compliance.

5.14.491.0

2014/2/18

  • Fixed a memory leak caused by unremoved items in a subscription. The leak occurred for Subscriptions using the "Poll" Update Mode.

5.13.191.0

2013/10/15

  • Resolved an issue where the driver failed to import tags if the data type returned by the target server was VT_EMPTY.

5.10.205

2012/11/13

  • Fixed an issue where the Default data type on a Static Tag using a dynamic address had Bad Quality.
  • Fixed an exception that would occur when invalidating tags while unloading the driver.

5.9.170

2012/6/26

  • Fixed an issue where tags containing the "GUID" Node ID type were not being validated correctly.
  • Fixed an issue in the Tag Import Browser where parent node tags would be imported even when only a child node was selected.

5.6.122.0

2011/7/25

  • Fixed the failure to decrypt persisted password information stored in projects that were created before 5.6.

5.5.94.0

2011/2/18

  • Added support for two-dimensional arrays.
  • Added support for Certificate Validation when importing or trusting certificates.

5.4.131.0

2010/10/28

  • Fixed an issue wherein the initial update was not passed on to client applications.
  • Improved the browse code to report a single failure instead of multiple failures per browse request.
  • Added support for the browseNext method, allowing clients to browse and import nodes from a server that limits the max returned nodes.
  • Fixed a deadband issue wherein we were not correctly passing in the client item handle for the item to which deadband was applied.
  • Removed the driver tag address limit of 1024.
  • Fixed duplicate browse entries when performing a full refresh through the context menu in the server browser.

5.3.118.0

2010/6/9

  • 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.
  • Fixed issue where the requested data type was not being honored when providing tag updates on monitored items.
  • Fixed a bug where the password was not cleared in the decryption logic if the password was empty. This caused the runtime and the configuration to get out of sync with channel passwords.
  • The performance of Auto Tag Generation has been enhanced.
  • Fixed an issue where we fail to connect to our own UA server if we are using a username/password and no security.
  • The client driver now places the server certificate in the rejected store if it fails to connect with security. In the configuration we also display a message box that allows the user to trust an untrusted endpoint.
  • Added synchronization and error checking for session read and write callbacks. It was possible to get an invalid subscription handle in the callback.
  • The driver now removes all items from the underlying server when the UA Client's device is configured as disabled.
  • Fixed an issue where the UA Client Driver returned an invalid read value when an item did not receive an update from the UA Server. We now continue to process the read request until we have a valid return value.

5.2.133.0

2010/2/18

  • New Driver

益处

  • 相比 DCOM,配置更为简单
  • 对防火墙友好
  • 强大的客户端接口与设备组合
  • 使用 256 位 AES 消息签名和加密提供安全可靠的数据传输
  • 多线程体系结构和非阻塞的异步消息传递提供出色性能、可扩展性和可靠性
  • 通过诊断工具轻松进行故障排除

什么是驱动?

KEPServerEX 不仅是 OPC 服务器,它还是一种适用于工业自动化和 IoT 的连接平台。只需下载 KEPServerEX,然后从包含 150 多种设备驱动、客户端驱动和高级插件的 Kepware 库中选择,以便适合您工业控制系统的独特通信要求。

驱动是一种软件组件,能够使 KEPServerEX 满足某个特定设备、系统或其他数据源的连接要求。此驱动处理 KEPServerEX 与数据源进行的所有专属通信;客户端接口处理通向监控或控制设备的应用程序的所有连接,包括支持的 OPC 连接、专属连接和开放式标准连接。

驱动可以单独或以套件形式获得授权许可。随着连接需求的发展,可以按需对其他驱动进行许可。

购买信息

OPC UA Client

KEPServerEX 的安全数据隧道通讯

获取步骤说明,了解如何在两个 KEPServerEX 实例之间配置安全、加密的数据隧道。

了解更多信息

© PTC Inc. 保留所有权利。