検索機能を使用して 500 を上回る Kepware の知識ベース記事の中から閲覧します。結果を絞り込むか、クエリーを下部の検索フィールドに入力します。

解決策が見つからなかった場合には、当社の PTC eSupport Portal で追加資料を確認することもできます。eSupport Portal へのログインを要求された場合、My Kepware の認証情報を使用できます。My 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/07

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