Craziefly P2P communication with peripheral MCUs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- arduino, linux
- Domain
- embedded-iot, networking
Research direction
No source file, test, or implementation entry point is named. Start by reviewing the linked micro-ROS P2P and brokerless P2P discussions alongside the Arduino RP2040 and Crazyflie setup; done would require a maintainer-confirmed, actionable implementation scope for MCU-to-MCU and ground-control communication.
Written by the indexing model from the issue text.
Description
Hi folks! I would appreciate some info regarding the current state of P2P communication between MCUs running micro-ROS nodes, and whether my (theoretical) setup would be achievable:
Setup (theoretical)
- Craziefly 2.1 with FreeRTOS connected over UART 1 & 2 to two separate Arduino rp2040 Connect dev boards with the micro-ROS Arduino library (as done here).
- Ideally the Craziefly would also be able to communicate with a "ground control" Linux computer (with the PA module).
The rp2040 boards would be running distinct neural networks and publishing the inference results as per my micro-ROS + Edge Impulse project.
The reason I'm skeptical this is possible is because as far as I understand my options are to either:
- Use a P2P Agent configuration as mentioned here but as they point out, this makes DDS access impossible
- Use the (more updated) brokerless P2P implementation as per this post, in which case I think an agent is not even existant!
Thanks in advance for any guidance :)
Avi
- Dominant language
- C
- Stars
- 98
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
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.
More from micro-ROS/freertos_apps
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
micro-ROS/freertos_apps#93 · 4 comments ·
All issues in micro-ROS/freertos_apps
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100