micro-ROS / micro-ROS/micro_ros_espidf_component
Is it feasible to select interfaces (UART/UDP) dynamically at runtime during the initialization phase?
还没有人认领这个 Issue。
- 主要语言
- C
- 星标
- 419
- 派生
- 124
- 平均合并
- 21 小时 35 分钟
- 30 天内合并 PR
- 3
描述
- Hardware description: ESP32-S3
- RTOS: FreeRTOS
- Installation type: micro_ros_espidf_component
- Version or commit hash: iron
Hi
I want to release a single binary file for different products and then select the communication interface through different configuration parameters (stored in Flash).
However, it seems that macro definitions like **RMW_UXRCE_TRANSPORT_UDP** or **RMW_UXRCE_TRANSPORT_CUSTOM** are used in many places, which are determined at compile time.
Can I treat UDP as a custom transport and then handle it by **rmw_uros_set_custom_transport**?
Thanks.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
Start by tracing the initialization path in the micro_ros_espidf_component and the uses of RMW_UXRCE_TRANSPORT_UDP and RMW_UXRCE_TRANSPORT_CUSTOM. Compare the runtime configuration goal with rmw_uros_set_custom_transport and the Flash-stored parameters. Done means establishing whether UART/UDP selection can be made at initialization time and identifying the compile-time constraints.
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- c
- 领域
- embedded-iot, networking
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 25/100