From da30ce60efecd45c6fa18d78e201373aa224103a Mon Sep 17 00:00:00 2001
From: Tommy Persson <tommy.persson@liu.se>
Date: Mon, 4 Apr 2022 14:27:40 +0200
Subject: [PATCH] Work on ROS2

---
 communication.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/communication.md b/communication.md
index 5321a6c..248be4a 100644
--- a/communication.md
+++ b/communication.md
@@ -57,9 +57,9 @@ When using an MQTT broker to communicate between ROS2 agents (and also
 between ROS1 and ROS2 agents) there are two programs running on the
 ROS2 agent:
 
-- **mqtt_to_ros**: This programs connect to the broker and push ut the ROS
-  messages it receives from the MQTT topics.
-- ros_to_mqtt: This program listen to ROS2 messages and push them on
+- **mqtt_to_ros**: This programs connect to the broker and decode the JSON encoded ROS
+  messages it receives from the MQTT topics and push them out on ROS topics.
+- **ros_to_mqtt**: This program listen to ROS2 messages and push them on
   the relevant MQTT topic as JSON strings. Note that ROS2 messages
   from mqtt_to_ros is filtered away (THIS MIGHT NOT BE POSSIBLE!!!).  Also this program can be
   configured to reduce the number of messages it sends by having a
@@ -75,7 +75,7 @@ The MQTT topic is built up in the following way:
 - channel
 - ext
 - ROS topic
-- receiver
+- receiver : ALL or namespace for unit/agent
 
 For example:
 
-- 
GitLab