Versions Compared

Old Version 9

changes.mady.by.user Wes Johnson

Saved on

compared with

New Version 10

changes.mady.by.user Wes Johnson

Saved on

Key

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

...

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 Edge Nodes the changes would not be picked up because the refresh scope is to this one single Edge Node.