Versions Compared

Old Version 5

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 Transmission provides a mechanism for publishing newly added tags to the tag tree for which a Transmitter publishes on. This must be done any time new tags are added to the tag tree or tags are moved within the tag tree. It must also be done any time properties of tags are modified.

Since MQTT Transmission only publishes tag updates on Value or Quality changes, this mechanism can also be useful in refreshing slow changing tag values so that downstream processes can confirm that the system is operating correctly.

This can be done manually or via a script.

...

Info

In performing this type of 'Global Refresh' using the '[MQTT Transmission]Transmission Control/Refresh' means that the entire all Transmitter 's tag treetag trees in Transmission will be rescanned. So, using this mechanism will also publish new BIRTH sequences for all Edge Nodes in MQTT Transmission. In this example both 'My Group/Edge Node 1' as well as 'My Group/Edge Node 2' would publish their BIRTH sequences. In addition, if tags had been added to both any Edge Nodes the changes would also be picked up for both all and published in their respective BIRTH messages.

...

Refreshing the Tag Tree for a Single Edge Node:


Info

This is only available in MQTT Transmission 4.0.9 and later.

Building off of the example from the previous section add another tag to 'Edge Node 1' called 'Tag 4' as shown below:

Image Added

Now expand the Transmission Info folder under the MQTT Transmission tag provider as shown below.

Image Added

Now that the Global Refresh Required boolean is true as is the 'Edge Node 1' Refresh Required is also true. This is because we added a tag under the 'Edge Node 1' Edge Node. As a result, 'Edge Node 2' doesn't actually need to be refreshed. So, at this point we can write a true to the '[MQTT Transmission]Transmission Info/Transmitters/Default Transmitter/Edge Nodes/My Group/Edge Node 1/Refresh Edge Node' tag. In doing so, only the tag tree associated with 'Edge Node 1' is rescanned. Also as a result, only the BIRTH sequence associated with 'Edge Node 1' will be published. After performing this refresh, the Global Refresh Required tag as well as the 'Edge Node 1' specific Refresh Required tag should go back to false denoting that everything is up to date. This is shown below.

Image Added

Finally, MQTT Engine should also now show 'Tag 4' in the tag tree.

Image Added

Info

In performing this type of 'Edge Node specific Refresh' using the '[MQTT Transmission]Transmission Info/Transmitters/TRANSMITTER_NAME/Edge Nodes/GROUP_ID/EDGE_NODE_ID/Refresh Edge Node' means that only the sub-tag tree associated with this specific Edge Node will be rescanned. So, using this mechanism will only publish a new BIRTH sequence for this one Edge Node. In this example only 'My Group/Edge Node 1' would publish it's BIRTH sequence. In addition, if tags had been added to any other Edge Node(s) the changes would not be picked up because the refresh scope is to this one single Edge Node.


Additional Resources