Skip to content

Commit

Permalink
Added documentation to comms bridge config file.
Browse files Browse the repository at this point in the history
  • Loading branch information
kbrowne15 committed Jan 16, 2024
1 parent a1e2a3a commit d2395e4
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions astrobee/config/communications/comms_bridge.config
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,21 @@ links = {
-- `from` to `to` direction), relay_backward (to be relayed only in the `to` to `from` direction),
-- and relay_both (to be relayed in both directions). Providing all three fields gives the user
-- full directional control while minimizing repetition and copy/paste errors.

-- Each topic entry can contain an input topic and an output topic. The
-- in topic is the topic being published on the robot sending the data and
-- must be specified. The optional out topic is the name of the topic a
-- user wants the data published on in the receiving robot. If the
-- out topic is not specified, the comms bridge will set it to be the name
-- of the robot sending the data combined with the in topic name. For
-- instance, if the from robot was Bumble and the to robot was Honey and
-- one of the in topics in the relay forward list was "mgt/ack", then it
-- would be published on Honey on topic "bumble/mgt/ack".
-- Please note that only one unique in topic can exist in the relay forward
-- and relay both lists and the relay backward and relay both lists. It is
-- fine to have the same in topic in the relay forward and relay backward
-- lists.

relay_forward = {
{in_topic = "honey/command", out_topic="command"},
},
Expand Down

0 comments on commit d2395e4

Please sign in to comment.