MQTT

FactoryTalk® Optix™
is compliant with Message Queuing Telemetry Transport (MQTT) versions 5.0 and 3.1.1, with client supporting publisher/subscriber functionality.
MQTT is a lightweight network protocol that uses a publish-subscribe model for machine-to-machine and IoT communication. It supports efficient data exchange in networks with low bandwidth, high latency, or instability. It relies on a central broker to route messages based on topics.
MQTT 5.0 adds extended error handling, including reason codes and negative acknowledgments. MQTT 3.1.1 provides less detailed error reporting and can respond by ignoring a request or closing the connection.
For more information, see MQTT Version 5.0 (oasis-open.org) and MQTT Version 3.1.1 (oasis-open.org).

This section includes

  • MQTT overview
  • Default payload structure
  • Information on how to add and configure the following elements to develop your application logic:
    • Broker-Client Transport Layer Security (TLS) with and without client certificate
    • MQTT Azure Connector
    • MQTT Broker
    • MQTT Client, MQTT Publisher and MQTT Subscriber

Default payload structure

Structure of FactoryTalk Optix MQTT payload for folder with 2 numeric tags and 1 string tag:
{
  "Timestamp": "2024-01-16T14:31:31.5096725+01:00",
  "Records": [
    {
      "TagName": "ModbusTag1",
      "Value": 2
    },
    {
      "TagName": "ModbusTag2",
      "Value": 41
    },
    {
      "TagName": "ModbusTag3",
      "Value": “12”
    },
  ]
}
The default payload structure is fixed.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal