micro-ROS / micro-ROS/micro-ROS-Agent

No Topic Visible if running micro ros agent on Humble, but these are visible if the agent is running on Foxy

未关闭
#230 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
C++
星标
201
派生
111
平均合并
1 天 6 小时
30 天内合并 PR
10

描述

## 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.
![image](https://github.com/micro-ROS/micro-ROS-Agent/assets/33423340/d47b08e8-3fec-4cf0-bbcd-5f68dbd144b4)

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

![image](https://github.com/micro-ROS/micro-ROS-Agent/assets/33423340/b59fc517-f892-47bc-9f2e-1184b5d94e71)

#### 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 ![Screenshot from 2024-06-23 14-05-50](https://github.com/micro-ROS/micro-ROS-Agent/assets/33423340/45af52b9-8d62-42de-933a-3083f88823e7)

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

首先,在 ROS 2 Humble 上使用 micro-ROS Agent 重现该问题,并按照描述同时使用 serial 和 UDP,将其 -v6 输出与 Foxy Docker setup 进行比较。检查报告中 ROS_DOMAIN_ID 和 RMW_IMPLEMENTATION 的不同变体。当 agent 在 Humble 上运行时,可以发现 topics 和 nodes 并对其执行 echo,即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
cpp
领域
networking, robotics
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
28/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。