ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
3

ros2 topic empty with fastdds discovery server

asked 2021-03-02 02:43:35 -0500

highmax1234 gravatar image

Hello, I followed this tutorial to set up a discovery server for ros2. The talker and listener examples all worked fine.

However, when it came to

ros2 topic list
and
ros2 node list
which were not part of the tutorial exactly, I did not find any nodes or topics. I exported the Server as follows in every terminal session:

export ROS_DISCOVERY_SERVER=127.0.0.1:11811

It seems like this is enough for talker and listener nodes to find each other, but not for ros2 command line tools. Also, rqt did not show any nodes or topics either. Command line tools and rqt work fine with standard discovery.

Is there anything else I need to do for ros2 topic list to show the /chatter topic?

edit retag flag offensive close merge delete

Comments

I have the same issue on the same computer and on a remote computer.

mechatronics3d gravatar image mechatronics3d  ( 2021-04-21 19:16:35 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
0

answered 2021-05-11 15:18:10 -0500

highmax1234 gravatar image

The corresponding issue mentions this question and can be followed under this link: https://discourse.ros.org/t/discovery...

To sum it up, there currently is a rather complicated XML-way to make CLI-Tools work on foxy, but the next patch should make it work without that workaround.

This outlook together with https://answers.ros.org/question/3730... should be enough to consider the topic done.

edit flag offensive delete link more

Comments

I encounter the same behavior as described in the original question in May 2022 on ROS2 Galactic. Has this issue been fixed only for ROS2 Foxy? I followed the solution outlined here, but the discovery server crashes upon startup.

Georg Bartels gravatar image Georg Bartels  ( 2022-05-23 12:25:59 -0500 )edit
0

answered 2021-03-16 08:02:46 -0500

volume_8091 gravatar image

I do not know exact mechanics of daemon caching data, but I sometimes see incomplete or even empty ros2 topic list, ros2 node list and ros2 param list.

Running with --no-daemon option or after ros2 daemon stop usually shows all data (topics, params, etc.)

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2021-03-02 02:43:35 -0500

Seen: 2,717 times

Last updated: May 11 '21