Cirrus Link Solutions

Sparkplug – MQTT Topic & Payload

 

sparkplug_logo_11-11-16_logotype-b-227_105 Cirrus Link provides open source software, tools and reference specification(Sparkplug) to facilitate clients to enable their applications, sensors, devices or gateways to seamlessly integrate data within MQTT Infrastructure.   It also is utilized in connecting with the Inductive Automation Ignition Platform utilizing the Cirrus Link MQTT modules.  The Sparkplug specification provides the necessary details for any MQTT enabled device to connect to MQTT servers and integrate with zero configuration into Ignition via the Cirrus Link MQTT Engine Module or other Sparkplug supported applications.

We have Tutorials for getting started supporting various languages including C, python and Java. The examples show how data can be published via MQTT from an emulated device running on a development machine.  In addition, it details how devices or projects can be controlled by writing to tags in Ignition.  It also details the caveats associated with establishing/ending an MQTT session and ensuring that the tag values in Ignition are valid.

The image below shows how with Sparkplug enabled devices and applications seamlessly connect to data to both IT and OT in real-time solutions with Igntion.

 

sparkplug-main-page-image

 

There are two payload formats for Sparkplug, A & B.  Payload A was the initial release and the Payload B supports a much richer data model within the MQTT infrastructures accommodating feedback from the user community.  Sparkplug Payload B provides additional support for:

  • Complex data types using templates
  • Datasets
  • Richer metrics with the ability to add property metadata for each metric
  • Metric alias support to maintain rich metric naming while keeping bandwidth usage to a minimum
  • Historical data
  • File data

To get Sparkplug specification with B format, please click here.  

For Sparkplug with A format, please click here.

A github site is available for examples using Sparkplug reference code is found here.

For the tutorials, support and latest documentation, please go here or go to the direct links to the implementations below.

For Payload B Format

For Payload A Format