Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ROS2 direct connection fails with Foxy
See original GitHub issueDescription I have ROS2 nodes running. Foxglove detects that they are there, but cannot see the topics they are publishing
- Version: 0.17.0
- OS: Ubuntu 20.04.3 (kernel: Linux 5.11.0-27-generic)
Steps To Reproduce
- Start foxglove.
- Start a ROS2 node. I used demo_nodes_py talker, but also tried
ros2 topic pub /test std_msgs/msgs/String)
Expected Behavior I should be able to see the topics in topic browser, raw messages panel, etc.
Actual Behavior Foxglove detects the ros2 nodes, which I can see in the dev tools (see screenshot) but I cannot observe the result in any Foxglove panels.
The nodes work over the ros2 webbridge, and the ros1 direct connection with ros1-ros2 node running.
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jtbandes I’ve tested on galactic, and it indeed works. We would prefer to use LTS versions of ROS, so foxy support would be ideal. Thank you so much for your help 😄
I’ve linked the relevant pull request to this ticket, the changes will go out in next week’s release. If you have any issues after that please feel free to reopen this ticket or file a new one.