Page History

...

Note there is a device with an attached PLC and two sets of registers.  Yours will look different based on the device you are using and how it is configured.  At this point, we can select the device (CLTEST002DIRECTOR in this case) and drag it into the Tag Browser under the 'default' Tag Provider.  This is shown below:

The first level of folders is very important in terms of layout and how the tags will be understood and represented by MQTT Transmission.  These are the rules:

...

Note the Tag Provider Name is the same Tag Provider we build out our Edge Nodes from in the Tag Browser earlier.  Now we can go back to Designer and force MQTT Transmission to update.  MQTT Transmission does not dynamically look for changes in the tag structure and update them.  This is because if If it did, you could end up with a lot of improperly structured data while the changes to the tag tree are being made.  So, the update must be forced via 'Refresh'.  This is a tag under the MQTT Transmission tag provider as shown below in the Tag Browser.

...

Once this is done, click 'Refresh' in the Tag Browser.  This will force MQTT Transmission to read the default Tag Browser tree, find 'Edge Nodes', and begin creating the components needed to send sending MQTT messages based on tag change events.  You can see this by clicking the refresh icon in the Tag Browser menu:

...