Versions Compared

Old Version 7

changes.mady.by.user Dan Potter

Saved on

compared with

New Version 8

changes.mady.by.user Dan Potter

Saved on

Key

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

...

As you can see, the Sparkplug settings can be used to either hard-code these IDs, or leave them blank so that the Agent will scan and discover them based on the tag tree layout.

Default Tag Agent

In the original release of MQTT Transmission the Default Transmitter was the only mechanism that could be used to define which tags would be published over MQTT. When in use, it would look in the specified Tag Provider that is configured for a folder called 'Edge Nodes'. Each folder under the 'Edge Nodes' folder would be considered a Sparkplug 'Group ID'. Each folder under each 'Group ID' folder would be considered a 'Edge Node ID'. Finally, each folder under each 'Edge Node ID' folder would be considered a 'Device ID'.

Consider the following tag tree:

Image Removed

With the above tag tree while using MQTT Transmission's Default Transmitter we end up with the following Sparkplug Edge Nodes.

  • Edge Node with Group ID=G1 and Edge Node ID=E1 with one Device with Device ID=D1
  • Edge Node with Group ID=G2 and Edge Node ID=E1 with one Device with Device ID=D1
  • Edge Node with Group ID=G2 and Edge Node ID=E2 with two Devices with Device ID=D1 and Device ID=D2

Note each Edge Node also results in a single MQTT Client connection. So, the above configuration results in three Sparkplug MQTT clients publishing messages to an MQTT Server.

It is important to note that the Default Transmitter no longer exists in Ignition 8. This is because a Custom Transmitter can be defined to represent the Default TransmitterIgnition tag tree layout.

Additional Resources