micro-ROS / micro-ROS/micro_ros_espidf_component
Is it feasible to select interfaces (UART/UDP) dynamically at runtime during the initialization phase?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 419
- Forks
- 124
- Avg merge
- 21h 35m
- Merged PRs (30d)
- 3
Description
- 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100