...
- 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
- The topic is the identified Ignition tag path
- The payload contains only the tag name, dataType, value, timestamp and quality 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
- Is limited to publishing a single data message for each tag change event
{"serverDuration": 76, "requestCorrelationId": "3bb7872e878b780b"}