Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
Page History
...
- Ignition with Google Cloud Injector Module installed
- Review the Cirrus Link Module Installation documentation for installation details.
- Ignition Designer installed
- Review the Inductive Automation documentation for Launching Designer against the Ignition gateway
- An existing Microsoft Azure account with an active IoT Hub and a registered device.
- Documentation on creating an IoT Hub and registering an new device can be found here
...
Step 1: Configure the Azure Injector Module
Once you have Ignition and the Azure Injector Module installed and running we can setup the configuration to connect to the active IoT Hub.
| Tip |
|---|
| Review the Azure Injector Module configuration guide for more details on each tab |
Navigate to the Azure Injector Module configuration section from the left side bar in the Ignition Gateway. From the Azure IoT Hubs tab, click on the "Create new Azure IoT Hub Setting..." link to bring up the following configuration form:
Set the following parameters:
...
Click on "Create New Azure IoT Hub Setting" to finish creating the new configuration setting.
Now the Azure Injector module is connected to the IoT Hub, we have to determine if there are are changes needed to the Tag Agent tab to be able to push data.
If you already have Ignition tags defined, for example from the Ignition OPC UA Server, then depending on the depth of your tag tree you may need to configure the Sparkplug Settings.
| Tip |
|---|
| Review the Cloud Injector Tag Agents and Tag Trees document which describes how Cloud Injector Agent configurations interact with Ignition tag trees to push messages and tag change events to the cloud service. It explains how tags get identified to be pushed as well as what specific 'topics' will be included with the messages. It also goes over some example configurations to show how the system will behave in different scenarios. |
Once the Tag Agent is setup as needed, you can jump to Step 3: Publishing data.
If you do not have Ignition tags defined we will do that in the next step with a tag tree depth that requires no additional Sparkplug settings.
Step 2: Create tags to be published in Designer
When the Azure Injector module is installed in Ignition, an Edge Node folder is automatically created in the 'default' Ignition tag provider.
Create a tree structure under this folder as shown below with some memory tags - this folder structure creates the same hierarchy that is described in the Sparkplug B specification of Group ID, Edge ID, and Device ID.
| Tip |
|---|
| Refer to the Ignition Tag Browser and Creating Tags documentation for assistance in configuring Ignition tags |
| Anchor | ||||
|---|---|---|---|---|
|
When the Azure Injector module is installed in Ignition, an Azure Injector tag provider is automatically created. This folder will contain both information tags about the module's version and state, as well as control tags for refreshing the module and Tag Agents.
Make sure that the Ignition Designer has read/write communications turned on by selecting the Project/Comm Read/Write button highlighted in the image below.
| Tip |
|---|
| Review the Inductive Automation Designer documentation for additional assistance on setting the project communication mode |
...
Overview
Content Tools