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

解決策が見つからなかった場合には、当社の PTC eSupport Portal で追加資料を確認することもできます。eSupport Portal へのログインを要求された場合、My Kepware の認証情報を使用できます。My Kepware アカウントが必要ですか? こちらで作成

各種検索方法:
View All Solutions

Kepware Knowledge Base: Solution


How Does an Absolute Trigger Work?


Last Update: 2018/11/07

An Absolute Trigger allows users to specify the day of the week and time of day that the trigger will be active. While in the triggered state, data can be logged via Static Interval or Data Change. Both Static Interval and Data Change logging starts when the trigger is active. For example, if a Static Interval is 1 minute, that minute will be calculated from the time that the trigger became active. As such, the first record would be logged 1 minute after starting. Data Changes are also determined from the start of the trigger activation. The following new trigger functions are available for Absolute Triggers:

  • Log once when trigger start condition is met: This function logs all the current values for the items in the Log Group once when the trigger starts. In KEPServerEX V5.5 and older versions of the server, this was referred to as a Start Snapshot.
  • Log once when trigger stop condition is met: This function logs all the current values for the items in the Log Group once when the trigger stops. In KEPServerEX V5.5 and older versions of the server, this was referred to as a Stop Snapshot.

Note: KEPServerEX V5.5 and older versions of the server require that the Static Interval or Data Change method be selected along with a snapshot condition. KEPServerEX V5.6 allows users to only select a snapshot condition (leaving the Static Interval and Data Change methods unchecked).

Related Products
DataLogger