...
The first way to do it is to configure scan rates as shown below:
- Alarm Scan Rate
- Set to -1 Polling to disable polling for Alarms is disabled0 If . If Alarms are not needed it is the best to set the 'Alarm Scan Rate' to -1. WIth this setup, alarm records are not going to be pushed to the rs_efm_meter_alarm database table regardless of the alarm source setting (i.e. If it is set to 0 and PERIODIC_HISTORY or ALARM_LOG_RECORDS).
- If the 'Alarm Source' is set to the 'PERIODICALARM_HISTORYLOG_RECORDS' , alarms will be obtained from Periodic History recordsand the 'Record Info Scan Rate' is set to -1, the 'Alarm Scan Rate' can be set to 0. With this setup, the AlarmPoller will not run on it own or on notification from the RecordInfoPoller.
- Event Scan rate
- Set to -1 Polling to disable polling for Events is disabled.
- If 0 Events are enabled, but only on notification from the 'Record Info ' poller. And since the 'Record Info Scan Rate' is set to -1, the 'Event Scan Rate' is can be set to -1, there will be no polling for events.0. With this setup, the EventPoller will not run on it own or on notification from the RecordInfoPoller.
- Periodic History Scan Rate
- Needs to be set Set to a positive number to launch the PeriodicHistoryPoller with specified poll rate
- Daily History Scan Rate
- Needs Set to be set to a positive number to launch the DailyHistoryPoller with specified poll rate
- Record Info Scan Rate
- -1 Polling Totalflow registers for any changes of Alarms, Events, and History arrays and notification respective pollers is disabled.Set to -1 to disable the RecordInfoPoller so that there will be no notifications to Alarm, Events or 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:
...
