Ignition MQTT and Sparkplug B Integration
Key Takeaway
How to integrate MQTT and Sparkplug B with Ignition SCADA for IIoT data collection, edge-of-network architectures, and scalable industrial telemetry.
Quick Answer
MQTT Sparkplug B Ignition integration enables scalable IIoT data collection using a publish/subscribe architecture. Ignition's MQTT Engine module subscribes to an MQTT broker to receive data from edge devices, while MQTT Transmission publishes Ignition data to brokers for consumption by other systems. Sparkplug B adds a standardized topic namespace and auto-discovery that simplifies large-scale deployments.
Why MQTT for Industrial SCADA?
Traditional SCADA polling (OPC, Modbus) requires point-to-point connections that don't scale well beyond hundreds of devices. MQTT's publish/subscribe model decouples data producers from consumers, enabling architectures where thousands of edge devices publish to a central broker and Ignition by Inductive Automation subscribes to the topics it needs.
Sparkplug B Specification
Sparkplug B is an open specification built on MQTT that defines a topic namespace, payload encoding, birth/death certificates, and metric naming conventions for industrial applications. Key benefits include:
- Auto-discovery: Edge nodes publish birth certificates that automatically create tags in Ignition
- State management: Birth/death certificates provide connection status without polling
- Efficient encoding: Protobuf-based payloads reduce bandwidth compared to JSON or XML
- Store and forward: Edge devices buffer data during network outages and replay on reconnection
Ignition MQTT Modules
MQTT Engine subscribes to an MQTT broker and creates Ignition tags from incoming Sparkplug B messages. MQTT Transmission publishes Ignition tag data to an MQTT broker for consumption by other Ignition gateways or third-party systems. Together, these modules enable distributed Ignition architectures spanning multiple sites and network boundaries.
Architecture Patterns
Common MQTT architectures with Ignition include hub-and-spoke (single central broker), multi-broker with bridging, and edge-to-cloud pipelines. NFM's managed Ignition SCADA services include MQTT infrastructure monitoring and Sparkplug B integration support as part of our managed SCADA services retainer.
Broker Selection and Sizing
Popular MQTT brokers for Ignition deployments include Chariot (Cirrus Link), HiveMQ, and Eclipse Mosquitto. Broker selection depends on message volume, required high availability, and security requirements. NFM assists with broker sizing, TLS configuration, and cluster setup for production IIoT environments.
Frequently Asked Questions
Sparkplug B is an open MQTT specification that standardizes topic naming, payload encoding, and device state management for industrial applications. It enables auto-discovery of edge devices in Ignition without manual tag configuration, dramatically simplifying large-scale IIoT deployments.
MQTT and OPC-UA serve different roles. OPC-UA is ideal for direct device-to-gateway communication on plant-floor LANs. MQTT excels at wide-area, edge-to-cloud, and multi-site architectures. Many Ignition deployments use both — OPC-UA locally and MQTT for remote/distributed data.
Yes. MQTT Transmission supports store-and-forward, buffering data locally during network outages and replaying messages when connectivity resumes. This ensures no data loss in unreliable network environments common in remote industrial and oil & gas installations.