-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CPU Board attached to the Bebop drone #19
Comments
Hi, |
Thank you for the prompt response. |
We do not plan to sell it since we are still in development phase. While the board can be already purchased, the integrated system will follow in the (hopefully) near future. |
Hi, thanks for your answer. |
The PULP board that runs dronet in Ultra-low power can already be purchased. Implementation of the algorithm that is highly non-trivial, but we are currently on it. We will soon share our findings and implementation. |
Hi Antonilo, Can you please share an explanation/description of how to connect the Up-board to the Bebop2? Thanks, Yoni |
I would argue that the easier way to do it is using ROS. This is however not the only one and for sure not the best one in term of performance. |
Thanks, but I meant how connect the Up-Board physically to the drone (power and communication)? Thanks again, Yoni |
We have an external battery to power the Up-Board and communication happens via WiFi and ROS. |
Hi Antonilo, Is there a big difference in the performance between running the algorithms on the UpBoard or on a laptop ? Thank you, Yoni. |
In the original dronet video, computation was done off-board in a laptop. In our last projects, all computation has been shifted to fully on-board: Deep Drone Racing, Beauty and the Beast. The minimum inference time required to give good behavior is generally 8-10Hz. |
Hi Antonio, |
Yes, we've re-implemented their algorithm as described in the paper. |
Ok, thank you. |
Hi Antonio, |
Hi,
Which CPU Board is recommended to attach to the Bebop drone for running the net?
If available, please share a link.
Thank you.
The text was updated successfully, but these errors were encountered: