MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). It is designed as an extremely lightweight publish/subscribe messaging transport that is ideal for connecting remote devices with a small code footprint and minimal network bandwidth.

The implementation of MQTT in EDM allows users to monitor the status of environmental tests (vibration, temperature, humidity) running in EDM VCS and measurements taken in EDM DSA. Users can even remotely run a test. This new messaging protocol will replace Socket Messages in EDM.

The following diagram explains the EDM MQTT Publish/Subscribe Architecture.

MQTT client:

The MQTT Client in EDM (publisher) publishes the test status and measurements to an MQTT broker.
A software (subscriber) written by a user subscribes to a topic from an MQTT broker to receive status and measurements or sends commands to an EDM MQTT client.

MQTT broker:

The MQTT Broker in EDM communicates to MQTT clients (both publisher and subscriber).
An MQTT Broker is hosted on the Internet by a third-party provider or on a LAN.

A built-in MQTT Client and MQTT Broker is provided in EDM VCS, EDM DSA, and EDM THV. The built-in MQTT Client also supports the SparkplugTM specification, which can be enabled/disabled.

Please refer to https://mqtt.org/ for MQTT technical content.

Please refer to https://sparkplug.eclipse.org/ for SparkplugTM specifications.

The MQTT Broker and MQTT Client windows can be accessed via Setup and under Extensions.