Connectivity Drop with More Than 5 Devices in Micro-ROS Agent on Docker (Raspberry Pi 5)
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- cmake, cpp, docker
- 领域
- devops, embedded-iot, networking
调研方向
首先比较 src/micro_ros_setup/config/host/generic/client-host-colcon.meta、src/uros/rmw_microxrcedds/rmw_microxrcedds_c/CMakeLists.txt 和 workspace 的 /src/colcon.meta。在收集 agent 和 client 日志的同时,使用超过五个 ESP32 设备重现掉线问题。确定正确的配置路径,并且经过测试的设置能够支持预期的 client 数量而不发生连接掉线,即表示完成。
由索引模型根据 Issue 内容生成。
描述
Description:
I am running a micro-ROS agent in a Docker container using the prebuilt image (humble) on a Raspberry Pi 5. I have several ESP32 devices with micro-ROS (Humble). When I attempt to connect more than five devices to the agent, I experience connectivity dropouts, where some devices fail to stay connected. With 5 devices, they are successful in subscribing to topics.
I suspect this issue might be related to the configuration flags in the micro-ROS build, particularly those related to client and resource limits. I came across the following parameters:
RMW_UXRCE_MAX_CLIENTSRMW_UXRCE_MAX_SUBSCRIPTIONSRMW_UXRCE_MAX_SESSIONSRMW_UXRCE_MAX_NODESRMW_UXRCE_MAX_PUBLISHERSRMW_UXRCE_MAX_SERVICESRMW_UXRCE_MAX_WAIT_SETSRMW_UXRCE_MAX_GUARD_CONDITIONRMW_UXRCE_MAX_TOPICS
These parameters seem critical to configuring the agent, especially as I'm dealing with multiple devices where each subscribes to three topics. I suspect increasing the RMW_UXRCE_MAX_CLIENTS value might help, but I'm not entirely sure.
What I've Tried:
- I attempted to experiment by manually setting
RMW_UXRCE_MAX_CLIENTSto 1 (as a test), but it did not yield the expected results, as multiple clients could still connect. - I've tried searching through the documentation, including Vulcanexus for guidance, but I haven't been able to solve the issue.
Question:
In order to adjust these flags and rebuild the micro-ROS agent from source, do I need to modify the build configuration in the following file?
Or should the changes be made in this file instead?
I believe the latter might be where the flags should be set, but I'm uncertain. Has anyone else experienced similar connectivity issues when connecting more than five devices to a micro-ROS agent on Docker? If so, how did you resolve it?
(I've also noticed a colcon.meta file in the /src folder of my workspace, should the be used?)
Any guidance on where exactly to set the flags for a manual source installation would be greatly appreciated - Or even the correct approach to setting up an agent to allow for more than 20 clients!
Thanks in advance for your help!
System Details:
- Hardware: Raspberry Pi 5
- Docker Image: Prebuilt micro-ROS agent
- Micro-ROS Version: Humble on ESP32 devices
- Number of Devices: 5+ ESP32 devices
- Topics per Device: 3 Topics per device
Links to Documentation:
- Vulcanexus Documentation on Memory Management
- micro_ros_setup Repository
- rmw_microxrcedds Repository
Thank you!
- 主要语言
- C++
- 星标
- 201
- 派生
- 111
- 平均合并
- 1 天 6 小时
- 30 天内合并 PR
- 10
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
micro-ROS/micro-ROS-Agent 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
micro-ROS/micro-ROS-Agent#270 ·
-
难度 4/5 3-5 天 新手友好度 35/100
micro-ROS/micro-ROS-Agent#269 ·
-
Release to apt 未关闭
难度 5/5 一周以上 新手友好度 25/100
micro-ROS/micro-ROS-Agent#267 ·
-
难度 4/5 3-5 天 新手友好度 42/100
micro-ROS/micro-ROS-Agent#266 · 1 条评论 ·
-
难度 5/5 一周以上 新手友好度 20/100
micro-ROS/micro-ROS-Agent#265 · 1 条评论 ·
查看 micro-ROS/micro-ROS-Agent 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 90/100
AXERA-TECH/ax-llm#77 ·
-
难度 1/5 1 小时以内 新手友好度 90/100
games-on-whales/wolf#509 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
-
bug-unconfirmed
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 74/100
NVIDIA/cuda-samples#453 ·