Versions Compared

Old Version 11

changes.mady.by.user Wes Johnson

Saved on

compared with

New Version Current

changes.mady.by.user Gill Houghton

Saved on

Key

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

...

MQTT Recorder requires that a database be set up in Ignition.  That can be done as described in the 'Connect to a Database' section here.  Once a database is set up, MQTT Recorder can be configured.  Do so by opening the Ignition Gateway Web UI and browsing to the Configure tab at the top of the screen and then selecting 'MQTT Recorder → Settings'.

...

  • Alarm Scan Rate
    • Set to 0 to indicate that alarms are required.
  • 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 a positive number to launch the PeriodicHistoryPoller with specified poll rate.
  • 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.

Image RemovedImage 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:

  • Alarm Scan Rate
    • Set to 0 to indicate that alarms are required.
  • Event Scan Rate
    • Set to -1 to disable polling for Events.
  • Periodic History Scan Rate
    • Set to 0 to poll on notification form the 'Record Info' poller.
  •  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, Periodic History poller will be notified on any 'RecordInfo' change such as 'Last Record Sequence number Used', etc.

Image RemovedImage Added

If the 'Alarm Source' device configuration option is set to ALARM_LOG_RECORDS (Array 245), the scan rates can be set 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.

Image RemovedImage Added

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.

Image RemovedImage Added

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.  

MQTT Transmission is connected to the MQTT Server and as a result MQTT Engine is receiving tag change events.  In addition, because an EFM ABB Totalflow device has been created and configured with the same Sparkplug Group ID, Edge Node ID, and Device ID, history data will also be pushed to the MQTT server as Sparkplug RECORD objects.  When new history data is polled by the EFM ABB Totalflow driver, they will be published to the MQTT server, consumed by MQTT Engine, passed on to MQTT Recorder, and then inserted into the specified database.  Below is a view of some events records using a third party database viewing tool.

Additional Resources