Page History

...

The Sparkplug Transmitter creates a Sparkplug Client
After connection to the MQTT server, two way communication is available between the Sparkplug Host Application and the Sparkplug Client
Uses BIRTH and DEATH messages together with Primary Host ID to maintain system state awareness awareness
Data is always published as QoS0
The published messages can be consumed by any Sparkplug Host Application such as MQTT Engine.
- The topic uses the identified SPARKPLUG IDs for Group, Edge Node and Device
- The payload includes Metrics, Timestamps and Metadata encoded using Google’s Protocol Buffers (Protobuf)
Understands Ignition UDTs and can be configured to publish UDT definitions in BIRTH messages
Is capable of publishing thousands of tag change events in a single message

...

The UNS Transmitter creates an MQTT Client
After connection to the MQTT server, data can only be published from the MQTT Client to the MQTT Server
Uses LWT to maintain system state awareness
Data can be published as QoS0, QoS1 or QoS2
The published messages can be consumed by any MQTT Client
- A
Is capable of publishing a
- single data message is published for each tag change event
  - The topic is the identified Ignition tag path
  starting at the Tag Path defined in the transmitter
  - The payload
  is a JSON formatted payload containing
  - contains only the tag name, dataType, value, timestamp and
  qualityCode
Is capable of publishing a
- - quality formatted as JSON
- A single properties message is published for each tag on a client connection
  - The topic is
  the
  - the identified Ignition tag path
  starting at the Tag Path defined in the transmitter extended by .props
  - The payload
  is a JSON formatted payload containing
  - contains Ignition non default or custom property
  values
  - values formatted as JSON
Publishes the leaf tags of Ignition UDTs and the structure of the UDT (i.e. UDT name itself and folders in the UDT) become topic tokens

...

Versions Compared