Versions Compared

Key

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

...

  • Block Node Commands
    • Whether or not to block outgoing commands from MQTT Engine to Edge Nodes. This is true by default and provides a security mechanism for preventing accidental outgoing commands from MQTT Engine.
  • Block Device Commands
    • Whether or not to block outgoing commands from MQTT Engine to Devices. This is true by default and provides a security mechanism for preventing accidental outgoing commands from MQTT Engine.
  • Include Security Context
    • Whether or not to include the Security Context in write command to be validated at the Edge Node. This is deselected by default.
    • Reference the Ignition MQTT Security Context HowTo for additional details on how to use this configuration.
  • Security Context Hashing Algorithm
    • Hashing algorithm to use when encrypting the Security Context. Options include SHA_1, SHA_224, SHA_256, SHA_384 and SHA_512
  • Change Password?
    • Checkbox to allow existing password to be changed 
  • Password
    • Password to be used when encrypting the Security Context

Anchor
GeneralAlarm
GeneralAlarm
General - Alarm Settings

Note

MQTT Engine 4.0.23 and newer support the acknowledgements of alarm events propagated from the Edge to MQTT Engine on the Central Gateway and inserted in the Ignition Alarm Journal 

Review the Alarm Event Propagation document for system configuration details including the changes needed to the data/ignition.conf file and MQTT Transmission

Image Added

  • Alarm Event Enable
    • When enabled and alarms are enabled on tags, MQTT Engine will receive the contents of the triggered alarms at the Edge and insert into the Ignition Alarm Journal on the server where MQTT Engine is installed

  • H2 Database Port
    • TCP Port to connect to H2 Database - applicable for disk-back history store only

Anchor
GeneralMiscellaneous
GeneralMiscellaneous
General - Miscellaneous

...