Page History

...

Tag Agents define what tags will be picked up in the Ignition tag tree and pushed to the defined cloud service. Tag Agents are very similar to MQTT Transmission 'Transmitters' in terms of how they interact with the Ignition Tag Tree. The 'Tag Provider' and 'Tag Path' configuration options define where in the Ignition Tag Tree the Agent will look for tags. There are also configuration options for the Sparkplug Group, Edge Node, and Device ID.

The Agent scans or discovers folders based on the different combinations of potential Sparkplug Settings.

• If all three IDs are left blank the Agent will assume the following folder structures follow the Tag Path:
  • <groupFolder>/<edgeNodeFolder>/<deviceFolder>/<tags>
  • <groupFolder>/<edgeNodeFolder>/<tags>
    
• If only the Group ID is specified the Agent will assume the following folder structure follows the Tag Path:
  • <edgeNodeFolder>/<deviceFolder>/<tags>
  • <edgeNodeFolder>/<tags>
    
• If the Group ID and the Edge Node ID are specified the Agent will assume the following folder structure follows the Tag Path:
  
  • <deviceFolder>/<tags>
  • <tags>
• If the Group ID, Edge Node ID, and the Device ID are specified the Agent will assume the following folder structure follows the Tag Path:
  
  • <tags>

Consider the following Custom Transmitter configuration.

Now consider the following tag tree:

Image Removed

With this Tag Agent configuration and tag tree we end up with the following Sparkplug IDs.

...

Note because there was no Device ID specified in the Tag Agent configuration so the Device IDs get picked up from the tag tree.

Consider another example:

...