Page History

...

It is generally used at the Edge of an OT infrastructure and is capable of .

• 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 to maintain system state 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 is ideal for lightweight IT deployments where minimal data points are required by Enterprise consuming clients.

It is generally used on the IT side of an OT/IT infrastructure

• 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
• Data can be published as QoS0, QoS1 or QoS2
• Is capable of publishing a single data message for each tag change event
  • The topic is the Ignition tag path starting at the Tag Path defined in the transmitter
  • The payload is a JSON formatted payload containing only the tag name, dataType, value, timestamp and qualityCode
• Is capable of publishing a single properties message for each tag on a client connection
  • The topic is the Ignition tag path starting at the Tag Path defined in the transmitter extended by .props
  • The payload is a JSON formatted payload containing Ignition non default or custom property values 
• 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

...