You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

The Diagram below will step you through the process of installing and setting up an end to end solution to gather industrial Internet of things data and send to the cloud while also provide a superior OT solution using Inductive Automation - Ignition platform.  The minimum requirements for this end to end solutions are:

  1. Ignition Gateway platform
  2. MQTT Server - either MQTT Distributor running as a module on the Ignition Gateway or standalone Chariot Server
  3. Host Client - MQTT Engine running as a module on the Ignition Gateway
  4. Edge hardware - select appropriate edge hardware platform
  5. Edge Client - Ignition Edge
  6. Protocols - gather OT data from existing field equipment RTU's / PLC's using native protocols
  7. Cloud Injectors -  to transmit OT data to the cloud for big data analytics



Step 1. Installing Ignition Gateway

The unlimited platform for SCADA and so much more.

Ignition Gateway is the SCADA host platform, which performs all the traditional SCADA functions as well as allowing other MQTT Modules such as the MQTT Server and cloud Injector modules to be loaded.

Quick Start Guide

Step 2. Installing MQTT Server

Every MQTT solutions needs at least one MQTT Server for the MQTT Clients to connect to.  There can be Edge Clients typically data producers and Host Clients typically data consumers, however they are both clients connecting to the MQTT Server.  There are three options here depending on the size of the system:

  • MQTT Distributor - supports up to 50 clients connections and installs as a module on the Ignition Gateway.
  • MQTT Distributor Plus - supports up to 250 clients connections and installs as a module on the Ignition Gateway.
  • Chariot - supports unlimited clients connections and installs as a module on the Ignition Gateway.

Click here to download the MQTT Distributor module - note scroll almost to the bottom of the page for the Cirrus Link Modules.

Step 3. Installing MQTT Engine

MQTT Engine is a host client that allows Ignition to connect to MQTT Servers and receive MQTT Messages.  MQTT Engine support Sparkplug B which enables the auto discovery of devices and tags with the rich tag meta data.

Click here to download the MQTT Engine module - note scroll almost to the bottom of the page for the Cirrus Link Modules.

Click here for further details on MQTT Engine, including how to's and installation video's.

Step 4. Selecting Edge Hardware

Ignition Edge runs on most Edge Hardware platforms that support Java and have at least 1MB of free memory, this includes most Embedded edge hardware platforms or even a Raspberry Pi.

Click here for several hardware manufacturers that we have worked with and loaded Ignition Edge on.

Step 5. Installing Ignition Edge Client

Ignition Edge is a mini version of the Ignition Gateway, it has the same familiar UI and comes pre-configured with MQTT Transmission module, which is an MQTT Client that takes Ignition tags and transmits them to the MQTT Server. For easy PLC connections, Ignition Edge solutions come with unlimited tags and are equipped with OPC UA along with Modbus, TCP, and Siemens drivers, and the Allen-Bradley suite of drivers. Other drivers supported by Ignition, such as DNP3 and Modbus RTU, can be added onto Ignition Edge solutions for an additional cost.

Click here for more details on Ignition Edge MQTT.

Click here for instructions on installing Ignition Edge MQTT.

Step 6. Installing Ignition Edge Client

To quickly get connected to one of your devices, go to the Configure section of the Gateway webpage and scroll down to OPC-UA Server > Devices.  The Device page will appear showing all of your installed devices.  To add a new device, click on the on the blue link, Create new Device.  Scroll through the list of devices, and click the radio button next to the type of device connection that you are interested in:

Step 7. Cloud Injector Modules

The Cloud Injector Modules install on the primary Ignition Gateway and allow specified Ignition tags to be sent north bound to the cloud with a Cloud Injector originated connection, thus no inbound ports open.  Data is sent using the same efficient report by exception methodology to reduce data bandwidth and cloud injection costs.

All major cloud providers are supported:

AWS Injector

Azure Injector

Google Cloud Injector

IBM Cloud Injector





  • No labels