Versions Compared

Old Version 49

changes.mady.by.user user-c32a8

Saved on

compared with

New Version Current

changes.mady.by.user Wes Johnson

Saved on

Key

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

...

Note

The Alarm Event Propagation implementation is limited as detailed below:

  • Prior to 4.0.30, the only alarm properties that are propagated are: Name, Priority and Notes.
  • Alarms over the GAN from an Engine gateway where alarms were forwarded over MQTT from Transmission is not currently supportedsupported from v4.0.31 and on as long as the Remote Tag Providers 'Alarm Mode' is set to 'Queried'. This feature requires Ignition 8.1.49+
  • Alarm pipelines and notifications exposed across MQTT along with alarm data is currently not supported
  • Alarm Status Table filtering to a Sparkplug Group/Edge and/or Device ID is not fully supported
    • In release 4.0.28 Sparkplug IDs were added to the source and display path of alarms at MQTT Engine to allow for Alarm Status Table filtering to Sparkplug IDs
    • From release 4.0.28 onward, MQTT Engine supports explicitly inserting alarm events into the Alarm Journal on arrival

...

  1. Stop the Ignition instances for both MQTT Transmission and MQTT Engine 

  2. Add a line similar to the following to the data/ignition.conf file on each Ignition instance replacing the 'XX' with the proper index per the wrapper.java.additional statements. 

    Code Block
    wrapper.java.additional.XX=--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED


    Warning
    Restart the Ignition instances


MQTT Transmission

  1. Ensure that Alarm Event Enable has been set under the Transmitter Alarm Settings configuration

  2. Ensure that a Disk Backed History Store has been configured and that the Transmitter has been configured under History Settings to use this history store. We recommend configuring a rolling buffer to manage a MQTT Transmission keep alive timeout scenario. 

...