...
If the 'Alarm Source' device configuration option is set to PERIODIC_HISTORY_RECORDS, the scan rates can be set as shown below:
The first way is to set Periodic History scan rate as shown below:
...
- to indicate that alarms are required.
- Event Scan
...
...
- Set to -1 to disable polling for Events.
- If the 'Record Info Scan Rate' is set to -1, the 'Event Scan Rate' can be set to 0. With this setup, the EventPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller.
- Periodic History Scan Rate
...
- Set to a positive number to launch the PeriodicHistoryPoller with specified poll rate.
- Daily History Scan Rate
...
- to disable polling for Daily History records
...
- .
- If the 'Record Info Scan Rate' is set to -1, the 'Daily History Scan Rate' can be set to 0. With this setup, the DailyHistoryPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller.
- Record Info Scan Rate
...
- Set to -1 to disable the RecordInfoPoller so that there will be no notifications to Alarm, Events and History pollers on any 'RecordInfo' change such as 'Last Record Sequence number Used', etc.
Image Added
The second way is to set Record Info scan rate and obtain alarms from Periodic History records on notifications from the 'Record Info' poller as shown below:
...
- to indicate that alarms are required.
- Event Scan
...
...
- Set to -1 to disable polling for Events
...
- Periodic History Scan Rate
...
- Set to 0 to poll on notification form
...
- the 'Record Info' poller.
...
...
- to disable polling for Daily History records
...
...
- Set to a positive number to
...
- launch the RecordInfoPoller with specified poll rate. With this setup, Periodic History poller will be notified on any 'RecordInfo' change such as 'Last Record Sequence number Used', etc.
Image Added
If the 'Alarm Source' device configuration option is set to Alarm Log Records to ALARM_LOG_RECORDS (Array 245), the scan rates can be set in two ways:
The first way to do it is to configure scan rates as shown below:This can be done in two ways:
- Alarm Scan Rate
- Set to a positive number to launch the AlarmPoller with specified poll rate.
- Event Scan Rate
- Set to -1 to disable polling for Events.
- If the 'Record Info Scan Rate' is set to -1, the 'Event Scan Rate' can be set to 0. With this setup, the EventPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller.
- Periodic History Scan Rate
- Set to -1 to disable polling for Periodic History records.
- If the 'Record Info Scan Rate' is set to -1, the 'Periodic History Scan Rate' can be set to 0. With this setup, the PeriodicHistoryPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller.
- Daily History Scan Rate
- Set to -1 to disable polling for Daily History records.
- If the 'Record Info Scan Rate' is set to -1, the 'Daily History Scan Rate' can be set to 0. With this setup, the DailyHistoryPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller.
- Record Info Scan Rate
- Set to -1 to disable the RecordInfoPoller so that there will be no notifications to Alarm, Events and History pollers on any 'RecordInfo' change such as 'Last Record Sequence number Used', etc.
The second way to do it is to configure scan rates as shown below:
- Alarm Scan Rate
- Set to 0 to poll on notification form the 'Record Info' poller.
- Event Scan Rate
- Set to -1 to disable polling for Events.
- Periodic History Scan Rate
- Set to -1 to disable polling for Periodic History records.
- Daily History Scan Rate
- Set to -1 to disable polling for Daily History records.
- Record Info Scan Rate
- Set to a positive number to launch the RecordInfoPoller with specified poll rate. With this setup, the AlarmPoller will be notified on any 'RecordInfo' change such as 'Last Record Sequence number Used', etc.
At this point the EFM ABB Totalflow driver is configured and is polling for Alarms at the rate specified in the EFM ABB Totalflow device configuration.
...
