Robobot MQTT topics: Difference between revisions
No edit summary |
|||
| Line 23: | Line 23: | ||
* topic: robobot/# | * topic: robobot/# | ||
All used topics start with the keyword <code>robobot/<\code>. The <code>#<\code> is a wildcard that matches all sub-topics. | All used topics start with the keyword <code>robobot/ <\code>. The <code># <\code> is a wildcard that matches all sub-topics. | ||
* topic: robobot/drive/# | * topic: robobot/drive/# | ||
The sub-topic <code>robobot/drive/<\code> is used for all data messages sourced by the teensy_interface (data from the drive function). | The sub-topic <code>robobot/drive/ <\code> is used for all data messages sourced by the teensy_interface (data from the drive function). | ||
* | * | ||
Revision as of 08:43, 15 February 2025
Back to Robobot
MQTT
MQTT (Message Queuing Telemetry Transport) is a lightweight protocol that transports messages between processes and networks.
The used MQTT server is Mosquitto from https://mosquitto.org/
The interface library used in both the Teensy_interface and the MQTT_client is paho-mqtt: https://eclipse.dev/paho/files/paho.mqtt.python/html/index.html
Robobot
Robobot uses MQTT
The MQTT server connects the Teensy_interface with the behaviour part of the robot.
Data topics
Data messages mainly originate from the Teensy firmware, where data can be subscribed.
- topic: robobot/#
All used topics start with the keyword robobot/ <\code>. The # <\code> is a wildcard that matches all sub-topics.
- topic: robobot/drive/#
The sub-topic robobot/drive/ <\code> is used for all data messages sourced by the teensy_interface (data from the drive function).
