Versions Compared

Old Version 32

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 33

changes.mady.by.user Gill Houghton

Saved on

Key

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

...

The Edge side client can publish historic data either in-order (synchronously) or asynchronously.


Notetip

If you are using MQTT Transmission as the Edge side client, under the MQTT Transmission Settings for your transmitter, navigate to the History Settings to disable the In-Order History configuration parameter. Enabling the In-Order History for MQTT Transmission is unnecessary and will result in a waste of resources.  

...

  • In-order history from the Edge Node
    • Historical data will be stored for the reference tag
    • If history is enabled on MQTT Engine tags, historical data will be stored the MQTT Engine tag
  • Asynchronous history from the Edge Node
    • Historical data will be stored for the reference tag
    • Even if history is enabled on MQTT Engine tags, historical data will not be stored the MQTT Engine tag. New values will only be stored in the historical database if it is a non-historical value.


Notetip

If you are using MQTT Transmission as the Edge side client, under the MQTT Transmission Settings for your transmitter, navigate to the History Settings to select or deselect the In-Order History configuration parameter.

As shown below, when the MQTT Transmission client comes back online and flushes history, it will flush the oldest historical events first (in order) before sending live Tag changes events to Engine. 

...