4 ms·
>The usual way to solve this, is a simplified onboard system. Crash prevention and the like. Probably an Arduino or ESP8266. My idea was have something like th
by rubber_duck 10y ago
>The usual way to solve this, is a simplified onboard system. Crash prevention and the like. Probably an Arduino or ESP8266.
My idea was have something like that hooked in to the bigger board via USB - the Android is creating flight plans and the micro controller is just managing the motors and following the plans it receives.
snapdragon 410 seems like it doesn't have OpenCL 2 (shared memory access ?)
- shakna 10y agoThe microcontroller may need more than naively doing as told, to reduce crash & burn. For the other board, I probably wouldn't use USB, but a serial or pin connection could be faster. Broadcom recently released the spec sheet for the Raspberry Pi's GPU, and people have been doing good work with that. Edit: Snapdragon 410 has official support only for OpenCL 1.1
- rubber_duck 10y ago>For the other board, I probably wouldn't use USB, but a serial or pin connection could be faster. I was just thinking USB since it's guaranteed to be there and should be simple to program on android if I chose to go down the "disassemble a phone for parts" route.