Use the search feature to view Kepware's repository of more than 500 Knowledge Base articles. Narrow your results or type your query into the search field below.

Alternatively, if you are unable to find a solution, we have an additional resource - our PTC eSupport Portal . If you are prompted to log into the eSupport Portal, you can use your My Kepware credentials. Need a My Kepware account? Create one here .

Search Solution Results By:
View All Solutions

Kepware Knowledge Base: Solution

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

Last Update: 11/7/2018

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).

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