No Topic Visible if running micro ros agent on Humble, but these are visible if the agent is running on Foxy
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 28/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- networking, robotics
Research direction
Start by reproducing the issue with the micro-ROS Agent on ROS 2 Humble and compare its -v6 output with the Foxy Docker setup, using both serial and UDP as described. Check the ROS_DOMAIN_ID and RMW_IMPLEMENTATION variations from the report. Done means topics and nodes are discoverable and can be echoed when the agent runs on Humble.
Written by the indexing model from the issue text.
Description
No Topic Visible if running micro ros agent on Humble, but these are visible if the agent is running on Foxy
- Hardware description: Linux and ESP32
- RTOS: -
- Installation type: micro_ros_setup
- Version or commit hash: Humble
Steps to reproduce the issue
I have followed the tutorial from the links below:
https://micro.ros.org/docs/tutorials/core/first_application_linux/
https://micro.ros.org/docs/tutorials/core/teensy_with_arduino/
The issue is, if I run the micro ros agent on ROS Humble (both serial or udp), I don't see any topics and nodes related. But in -v6 I am able to see the data is publishing.
The thing is, I am able to subscribe it through node. But I am not able to see the topic list in the terminal.
I have tried unset ROS_DOMAIN_ID, set the same ROS_DOMAIN_ID, set the same RMW_IMPLEMENTATION, unset the RMW_IMPLEMENTATION. But nothing works.
Then I tried to use foxy to run micro ros agent (using docker ros-foxy), I am able to see the topic list on Humble. And I also able to echo it. as you can see the picture below
Expected behavior
I should be able to see the topic list, while the micro ros agent runs in the Humble.
Actual behavior
Unable to see the topic list, while the micro ros aget runs in the Humble.
Additional information
This is my env, even if I didn't set the same ROS_DOMAIN_ID, and didn't set the RMW_IMPLEMENTATION, if I run the agent on Foxy, it still work and detected on Humble
- Dominant language
- C++
- Stars
- 201
- Forks
- 111
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 10
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from micro-ROS/micro-ROS-Agent
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
micro-ROS/micro-ROS-Agent#270 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
micro-ROS/micro-ROS-Agent#269 ·
-
Release to apt Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
micro-ROS/micro-ROS-Agent#267 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
micro-ROS/micro-ROS-Agent#266 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
micro-ROS/micro-ROS-Agent#265 · 1 comment ·
All issues in micro-ROS/micro-ROS-Agent
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·