micro-ROS / micro-ROS/micro-ROS-Agent
Running uROS on the MCU without the Agent running on a PC
還沒有人認領這個 Issue。
- 主要語言
- C++
- 星號
- 201
- 分支
- 111
- 平均合併
- 1 天 6 小時
- 30 天內合併 PR
- 10
描述
Hey @pablogs9!
@CLansdaleBEC and I were talking about what it looks like for the MCU to run its respective nodes without the Agent running.
I could not quite recall if you had previously mentioned that it was a known limitation the MCU needed to communicate to the agent and then back down.
For instance:
Node A on MCU publishes message "Hello" -> Agent on PC -> Node B on MCU subscribes to topic and receives message "Hello"
Rather than
Node A publishes message -> Node B subscribes to topic and receives message.
I hope my question makes sense, but for our use case we are utilising the MCU as a safety critical system (meaning it handles some logic to ensure that in the fail case of it being unable to communicate with our PC, we publish commands to the rest of the MCU nodes so they can handle their respective parts).
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
該 issue 未指明任何檔案、測試或進入點。首先閱讀包含 24 則留言的討論以及 micro-ROS Agent 的架構,以確定是否支援不使用 Agent 的 MCU-to-MCU 通訊,還是需要新的設計。如果需要工作,則應以一項已記錄的決策和明確的實作範圍作為完成標準。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- cpp
- 領域
- distributed-systems, embedded-iot
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 25/100