Page History

...

• Azure Injector 8.1.10 or later is required
• Knowledge of Ignition and Module module installation process:   Cloud and MQTT Module Installation.
• An existing Microsoft Azure account

...

• Setting Name
  • This can be any string that makes sense that represents this connection.
• Enabled
  • Leave checked
• Scope ID
  • This is found in the Azure IoT Central application view under 'Administration → Device connection'. It is labeled 'ID scope'
• Password (Azure Enrollment Group Symmetric Key)
  • This is found in the Azure IoT Central application view under 'Administration → Device connection → 'SaS IoT Devices'. In the right pane are two keys. Either the primary or seconday secondary key can be used for the connection.
• Global Endpoint
  • Leave default
• Provisioned Device ID
  • Use the Device ID that was provisioned in step 1 of this tutorial (as part of provisioning the Azure IoT Central application)

...

In order to use this Tag Agent to push data to IoT Central, we need to create a Tag Tree in Ignition. Begin by opening Designer. Instructions on how to do this can be found here. Note that the link has provides a lot of information about Designer. For However, for the purposes of this tutorial we 're are only going to be creating a Tag Tree with memory tags in the Tag Browser. So, not all of the information there is pertinent to this tutorial.

Use Designer to create a tag tree as shown below with a single memory tag under the folder structure also shown.

...

Now click the Refresh boolean value to change it to trueTrue. This won't actually change the value of the tag but will tell Azure Injector to rescan the tag tree for any new tags that may have been added and to push them to Azure IoT Central. You may have to enable 'read/write' mode in Designer before this operation will be successful. Once the write is successful, you should see something similar to the following in Azure IoT Central's portal.

...

The first message shows the 'NBIRTH' message which is an indication that the Sparkplug Edge Node has come online. The second message is a Sparkplug DBIRTH message denoting that a Sparkplug Device has come online along with its 'metrics' or tags, their tag metadata, and values. In this case we only had a single tag so that is all that is included in the payload.

...