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
-
ai_reviewed
難度 2/5 1-3 小時 新手友好度 68/100
ydb-platform/ydb#53869 · 3 則留言 ·
-
bug cert blocker needs triage
難度 2/5 1-3 小時 新手友好度 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
難度 2/5 1-3 小時 新手友好度 75/100
conan-io/conan-center-index#31035 ·
-
Bug
難度 2/5 1-3 小時 新手友好度 68/100
-
documentation
難度 1/5 1 小時以內 新手友好度 85/100
vllm-project/vllm-ascend#17329 ·