Consistent data formats
Use a standard topic structure and binary payload format so compatible applications can interpret device metrics.
MQTT SPARKPLUG B
Standardize equipment data and track device availability across industrial systems with EMQX and Sparkplug B.
Overview
Sparkplug B defines how industrial systems name, encode, and track data exchanged over MQTT.
Use a standard topic structure and binary payload format so compatible applications can interpret device metrics.
Use birth and death messages to track edge node and device availability, helping applications recognize stale data.
Publish changed metrics using report by exception to reduce repeated data transmission during an active session.
Architecture
Collect and encode equipment data with EMQX Neuron, then use EMQX to route Sparkplug messages and integrate the metrics applications need.
Schneider PLC EMQX Neuron
EMQX Enterprise
EMQX Node 1
EMQX Node 2
EMQX Node 3
EMQX Node N
Capabilities
Route industrial messages, process Sparkplug payloads, and connect downstream systems.
Distribute MQTT connections and message routing across a cluster as your industrial deployment grows.
Clustering guideUse a clustered broker deployment to reduce the impact of individual node failures.
Cluster architectureDecode Sparkplug B payloads with EMQX rules and route selected data to supported external systems.
Sparkplug payload guideUse TLS, client certificate authentication, and topic permissions to control access to industrial messages.
Security guideUse EMQX Neuron to collect data through supported industrial drivers and publish Sparkplug B messages.
Neuron Sparkplug setupRoute Sparkplug topics and use built-in payload encoding and decoding functions for application integration.
Sparkplug B functionsUSE CASES
Give industrial applications a common way to consume equipment data and track its availability.
Connect equipment data to SCADA and production applications for monitoring and operational analysis.
Explore manufacturingCollect telemetry from remote equipment and share state-aware data with monitoring applications.
Explore oil and gasConnect sensor and equipment data to applications that monitor water quality, flow, and distribution.
Read the use caseResources
FAQ
Sparkplug B is the binary payload format used by the Sparkplug specification for industrial MQTT systems. Sparkplug also defines topic naming and state management so compatible applications can interpret metrics and track availability.
EMQX routes MQTT messages, supports clustered deployment and access controls, and provides Sparkplug B encoding and decoding functions. Use rules and supported integrations to send decoded data to downstream systems.
Compatible participants follow the same topic, payload, and state conventions. This gives applications a common way to identify metrics and track availability across equipment from different vendors.
Edge nodes publish birth messages to establish their metrics and register a death message as the MQTT Last Will. Device birth and death messages track attached equipment. Host applications use these state messages to recognize unavailable or stale data.
Yes. An industrial gateway such as EMQX Neuron collects data using a supported driver and publishes Sparkplug B messages. Check driver and device compatibility when planning your deployment.
Sparkplug is used in manufacturing, oil and gas, water, energy, and other industrial settings where applications need standardized equipment metrics and state information.
Plan your industrial connectivity, Sparkplug data flows, and application integrations.