Internet of Things protocol can optimize cellular data transmission via MQTT’s publish-subscribe messaging system, transferring rationed data at critical times by way of a message broker
The two-way communication of MQTT enables the publisher to send data to the broker, which can then be pushed to the subscriber worry-free, rather than having the subscriber poll the publisher constantly. This protocol dramatically reduces data usage on a cell plan. The client can subscribe to tagged values from multiple SCADADroid®s, as well as publish to the SCADADroid® with any adjusted setpoints
What is MQTT?
Simply put, Message Queue Telemetry Transport (MQTT) is a wireless language spoken between machines. This “language” is referred to as machine to machine protocol, or “m2m” for short. What is special about this protocol is its ability to condense and queue bits of data rather than streaming them constantly, which minimizes the amount of data sent over wireless. It is particularly useful as an Internet of Things protocol, and SCADADroid® primarily uses it to minimize mobile wireless transmission of monitoring data
- Cloud-Based Broker service available for low monthly fees, or set up a third-party broker on the web browser configuration page
- MQTT's TCP middleware allows for MQTT integration with Modbus
- Several options exist for MQTT integration with simple Input/Output functions
- Configuration of Events allows for use of MQTT protocol in server reporting, and client publishing
- Last known values preservation guarantees the survival of critical data in the case of connection failure
- MQTT is encrypted via the message broker and does not need a VPN to operate securely
- Topic strings are legible subject-lines connecting server devices with selected clients via MQTT Broker
- Real values instead of percentages displayed through Modbus-driver tag upgrades
- App Interface programs for streamlined MQTT-smartphone monitoring
MQTT provides cloud-computing based messaging, much like Facebook Messenger App
MQTT handles information by having a client (a client being a device with the authority to both publish and subscribe) subscribe to a topic through the MQTT broker. At an event, the publisher (i.e. the SCADADroid®) sends a message to the cloud-based broker with a Topic included in the string. The broker will then push the message out to all the clients that have subscribed to that topic. This message can be sent to as many phones or computers that have subscribed to the desired topic, from the Broker as appropriately prioritized.