Versions Compared

Old Version 10

changes.mady.by.user Ilya Binshtok

Saved on

compared with

New Version 11

changes.mady.by.user Ilya Binshtok

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

As en example, let's configure the driver to poll for Event records and disable Alarms and History. This can be done in two ways:

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 Alarms are not needed 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. PERIODIC_HISTORY or ALARM_LOG_RECORDS).
    • If it is set to 0 and the 'Alarm Source' is set to the 'PERIODICALARM_HISTORYLOG_RECORDS' and the 'Record Info Scan Rate' is set to -1, the 'Alarm Scan Rate' , alarms will be obtained from Periodic History recordscan be set to 0. With this setup, the AlarmPoller will not run on it own nor will it poll on notifications from the RecordInfoPoller. 
  • Event Scan rate
    • Needs Set to be set to a positive number number to launch the EventPoller with specified poll rate.
  • Periodic History Scan Rate
    •  Set to -1 Polling to disable polling for Periodic History records is disabled.
    • If 0 Periodic History is enabled, but only on notification from the 'Record Info' poller. And since the 'Record Info Scan Rate' is set to -1, there will be no polling for Periodic History.
     Daily
    • 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
    • 1 Polling for Periodic History is disabled
    • Set to -1 to disable polling for Daily History records.
    • If 0 Periodic History is enabled, but only on notification from the 'Record Info ' poller. And since the 'Record Info Scan Rate' is set to -1, there will be no polling for Periodic History., 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
    • -1 Polling Totalflow registers for any changes of Alarms, Events, and History arrays and notification respective pollers is disabledSet 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 -1 Polling to disable polling for Alarms is disabled.
  • Event Scan rate rate 
    •  0 Scan on notification form the  'Record Info' poller.
  • Periodic History Scan Rate
    • Set to -1 Polling to disable polling for Periodic History records is disabled.
     Daily
  • Daily History Scan Rate
    • Set to -1 Polling to disable polling for Daily History records is disabled.
  • Record Info Scan Rate
    • Needs Set to be set to a positive number to poll Totalflow registers for any changes of Alarms, Events, and History arrays and notify Event Poller that there are new entries in Array 252 (EVENT_RECORD)launch the RecordInfoPoller with specified poll rate. With this setup, EventPoller 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 Events at the rate specified in the EFM ABB Totalflow device configuration.  

...