Skip to content

Commit f4530a2

Browse files
lreiherbastilam
andauthored
apply suggestions from review after testing
Co-authored-by: Bastian Lampe <bastian.lampe@rwth-aachen.de>
1 parent 1327551 commit f4530a2

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
<a href="https://github.com/ika-rwth-aachen/mqtt_client"><img src="https://img.shields.io/github/stars/ika-rwth-aachen/mqtt_client?style=social"/></a>
99
</p>
1010

11-
The *mqtt_client* package provides a ROS nodelet that enables connected ROS-based devices or robots to exchange ROS messages via an MQTT broker using the [MQTT](http://mqtt.org) protocol. This works generically for arbitrary ROS message types.
11+
The *mqtt_client* package provides a ROS nodelet that enables connected ROS-based devices or robots to exchange ROS messages via an MQTT broker using the [MQTT](http://mqtt.org) protocol. This works generically for arbitrary ROS message types. The *mqtt_client* can also exchange primitive messages with MQTT clients running on devices not based on ROS.
1212

1313
- [Installation](#installation)
1414
- [Usage](#usage)
@@ -105,7 +105,7 @@ roslaunch mqtt_client standalone.launch
105105
[ INFO] [1665575657.462622065]: Connected to broker at 'tcp://localhost:1883'
106106
```
107107

108-
Note that the *mqtt_client* successfully connected to the broker and also echoed which ROS/MQTT topics are being bridged.
108+
Note that the *mqtt_client* successfully connected to the broker and also echoed which ROS/MQTT topics are being bridged. For testing the communication between *mqtt_client*, itself, and other MQTT clients, open five new terminals.
109109

110110
In order to test the communication among *mqtt_clients*, publish any ROS message on ROS topic `/ping/ros` and wait for a response on ROS topic `/pong/ros`.
111111

@@ -133,7 +133,7 @@ rostopic pub -r 1 /ping/primitive std_msgs/Int32 42
133133

134134
```bash
135135
# 5th terminal: publish primitive MQTT message to pingpong/primitive
136-
docker run --rm --network host eclipse-mosquitto mosquitto_pub -h localhost -t "pingpong/primitive" --repeat 10 --repeat-delay 1 -m 69
136+
docker run --rm --network host eclipse-mosquitto mosquitto_pub -h localhost -t "pingpong/primitive" --repeat 20 --repeat-delay 1 -m 69
137137
```
138138

139139
If everything works as expected, the second terminal should print a message at 1Hz, while the third terminal should print two different messages at 1Hz.

0 commit comments

Comments
 (0)