Today is...
Thursday, November 23, 2017
Welcome to Control.com, the global online
community of automation professionals.
Featured Video...
Featured Video
Wiring and programming your servos and I/O just got a lot easier...
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Visit our Post Archive
Kickstarter Campaign To Add MQTT Support To Ignition
Integrate Paho's Java MQTT client with Inductive Automation's Ignition Gateway via the Ignition SDK and APIs
3 out of 3 members thought this post was helpful...

Moderator's Note: We have never posted anything like this before and may not again depending of the feedback and comments we get.

Marrying I.o.T and SCADA

I've been writing code for many years and am now farming in Western Southland.

Have been caught by the I.o.T buzz and the promise of low cost telemetry; cpus; and open protocols like MQTT.

The Ignition Gateway represents the best of breed SCADA platform but has a surprising omission - no support for MQTT!

Having already integrated MQTT into the QGIS Open GIS platform, I figured let's do the same for the Ignition Gateway.

This project will create a .modl Ignition Module file to support any Paho compatible MQTT brokers.

Please see:

https://www.kickstarter.com/projects/1109584274/develop-an-mqtt-driver-for-the-ignition-gateway

Pledgers will get a copy of all code under the MIT license plus any updates and assistance to configure and use the driver within Ignition. They will receive our support and priority attention to any issues and/or feature improvements they wish to see.

Thank you

1 out of 1 members thought this post was helpful...

I've backed Andrew's development as I need to connect a Cellular IoT gateway to Ignition SCADA running in the cloud on MS Azure.

I had tried using an OPC-UA client but the work needed to get this to required level of functionally and stability was too much. MQTT is perfect for lite touch integration for IoT devices to Ignition.

What's more the OPC-UA standard is to support publish and Subscribe messaging but will use AMPQ as it's transport protocol. So even the standard makers realize that pub/sub is a good solution for certain devices and types of integration.

This project may be obviated as we have made an open source release of a dedicated nodejs solution. It is crude but generic and does not require Ignition.

See: https://github.com/nzfarmer1/mqtt2opcua