使用搜索功能查看 Kepware 的信息库,其中包含 500 多篇知识库文章。缩小搜索结果范围,或在下面的搜索字段中输入您的查询。

或者,如果您无法找到解决方案,我们还有另一个资源:我们的 PTC eSupport Portal。 如果系统提示您登录 eSupport Portal,您可以使用“我的 Kepware”凭据。需要一个“我的 Kepware”帐户吗?在此处创建

搜索解决方案结果:
View All Solutions

Kepware Knowledge Base: Solution


Why Are Initial Updates Sometimes Slower in KEPServerEX V5 than in KEPServerEX V4?


Last Update: 2018/11/7

Problem:
When launching the OPC Quick Client or connecting another application to KEPServerEX V5 for the first time, KEPServerEX V5 sometimes updates the items slowly. This did not occur in KEPServerEX V4. This delay is noticeable on drivers like Weatherbug, DNP3, BACnet, and SNMP because the devices that support these protocols usually communicate slower than typical automation devices. This issue will also manifest itself if devices in the project are unresponsive and the server times out on them (especially when those devices are multi-dropped on a single connection).

Solution:
This delay is by design, and is the result of an OPC 3.0 Compliance setting that requires all items to be initialized before updates may be sent to the connected client. KEPServerEX V5 enables this setting by default, whereas KEPServerEX V4 disabled this setting by default. For more information, refer to the instructions below.

  1. To disable the setting in KEPServerEX V5, click File | Project Properties and open the OPC DA Compliance tab. Then, uncheck Return initial updates for items in a single callback.
  2. To enable this setting in KEPServerEX V4, click Tools | Options and open the OPC DA Compliance tab. Then, check Return initial updates for items in a single callback.
Related Products
KEPServerEX