Page History

...

• Set the following fields under 'Module Settings'.
  • IoT Edge Module Name: Ignition

  • Image URI: inductiveautomation/ignition:8.1.x where x is the latest stable release from the 8.1.x branch.

    Tip
    The latest version is updated and available here: https://hub.docker.com/r/inductiveautomation/ignition

    
    

  • Restart Policy: always
  • Desired Status: running
  • Image Pull Policy: On create
  • Startup Order: 200
• Leave the 'Environment Variables' blank

• Under 'Container Create Options' set the following JSON as the value. The 'Binds' field is required and there to preserve Ignition configuration across container deployments.

  Code Block
  { "HostConfig": { "Binds": [ "IgnitionData:/usr/local/bin/ignition/data" ], "PortBindings": { "8088/tcp": [ { "HostPort": "8088" } ], "8043/tcp": [ { "HostPort": "8043" } ], "8060/tcp": [ { "HostPort": "8060" } ] } } }

  
  

• Leave the 'Module Twin Settings' blank

...

At this point, Ignition is running as a Docker container in Azure Edge. You should be able to browse to http://[ip_address_of_azure_edge]:8088. Replace [ip_address_of_azure_edge] with the IP address of your Azure Edge system. You should see something similar to the following.

Follow the steps in the Installing and Upgrading Ignition documentation starting from Step 3. Ignition documentation and select either Ignition or Ignition Edge for this tutorial.

Step 3: Install and configure the Azure Injector Module

Follow the steps in the Module Installation guide to install the latest Azure Injector Module.

Now select 'Settings' under the Azure Injector section in the left navigation panel near the bottom. After doing so, you should see the following page.

Now select 'Azure IoT Edge HubsEdges' from the tabs near the top of the page. This will open the following page.

...

Now select the 'Settings' tab directly to the left of the 'Certificates' tab. Then click the 'Create new Azure IoT Edge Hub Setting...' link. This will open the following page.

...

If everything went well, you should also see 'Connected' under the Status column. Note it

...

Once the system is showing connected, tags can be created in Ignition Designer. Review the Inductive Automation documentation for Launching Designer against the Ignition gateway

When the Azure Injector modules 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 a 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.

Image Modified

Step 5: Publishing data

Using the Azure Command Line tools you previously installed on a development machine (from the prereqs here), run the following command

...

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. 

...

To refresh the default Tag Agent, open the folder "Azure Injector Control" and click on the Refresh Boolean. When this happens, the Tag Agent will scan the "Edge Nodes" folder and publish the Sparkplug BIRTH sequence to the Azure IoT Edge Hub.

...