Page History

...

During the prerequisite tutorial a set of tags were created to publish to Azure IoT Hub. At this point, we will create some new tags that will be will be routed to the container based on the previous configuration. Because we created a message route that filtered on a Sparkplug Group ID of 'Routed Group' we should create a structure that includes this in the tag tree. So, expanding on the tag tree created previously, add a new Sparkplug Group, Edge Node, and Device folder structure with a single boolean tag along side the original structure created in the quickstart as shown below. Note for the message route in Azure to work properly, the Group ID MUST be 'Routed Group' as shown below.

Step 5: Publish Data to Azure IoT Hub

After creating this tag structure with the 'Routed Group', browse to the Azure Injector tag provider and write a 'true' to the Azure I

...

'Azure Injector Control/Refresh' tag shown below. This will cause Azure Injector to rescan the tag tree and publish messages to IoT Hub.

Image Added

Now that Azure Injector has scanned the tag tree, generate some tag change events by manually changing the following two tags. Make sure as you change these values you wait a couple of seconds between each change. This will ensure that a series of MQTT messages will be published to Azure IoT Hub.

[default]Edge Nodes/Routed Group/Routed Edge Node/Routed Device/Boolean Tag

[default]Edge Nodes/Tutorial Group/Tutorial Edge Node/Tutorial Device/Boolean001

At this point, Azure should route the 'Routed Group' messages to the storage container but ignore the 'Tutorial Group' messages. This can be verified in the next step of this tutorial.

Step 6: View the Data in the Azure Storage Container

...