174
edits
User:Eb4890: Difference between revisions
From London Hackspace Wiki
no edit summary
No edit summary |
|||
| Line 23: | Line 23: | ||
===Android Robotics=== | ===Android Robotics=== | ||
See [http://www.cellbots.com/| cellbots] for current work. | See [http://www.cellbots.com/| cellbots] for other peoples current work. | ||
====Why==== | ====Why==== | ||
Android phones/tablets will get stupidly cheap in the future. They also have a bunch of sensors/wireless comms and the ability to connect to random micro-controller based usb devices. They also have GPUs to give a bunch of parallel processing power for a low price, | Android phones/tablets will get stupidly cheap in the future. They also have a bunch of sensors/wireless comms and the ability to connect to random micro-controller based usb devices. They also have GPUs to give a bunch of parallel processing power for a low price, although that can't be accessed nicely at the moment. | ||
They do compete somewhat with raspberry pis (raspberry pis being stripped down phones without the sensors/displays etc). I expect two ecosystems will emerge, with android phones and the OS being used for robots that need comms and lots of phone functionality, with micro controllers being used as for autonomic procedures and low latency apps. Raspberry PI and rooted phones with non-android roms will be used for situations where you need lots of processing power close to the metal. | They do compete somewhat with raspberry pis (raspberry pis being stripped down phones without the sensors/displays etc). I expect two ecosystems will emerge, with android phones and the OS being used for robots that need comms and lots of phone functionality, with micro controllers being used as for autonomic procedures and low latency apps. Raspberry PI and rooted phones with non-android roms will be used for situations where you need lots of processing power close to the metal. | ||
Probably the best positioning for the android phone is in a cheap/easy robot? Perhaps based upon a RC car. The phone/tablet would act as brains and eyes/ears and the RC car the locomotion. | |||
The camera would be used for depth mapping and object recognition. Use google apis for speech recognition? | |||
====Things to do==== | ====Things to do==== | ||
* Decide on a method taking advantage of multi-core and GPUs on android. This either means OpenCL, Render Script or hackily with openGL. OpenCL is more cross platform but Render Script is working on android today (at least for multicore) | * Decide on a method taking advantage of multi-core and GPUs on android. This either means OpenCL, Render Script or hackily with openGL. OpenCL is more cross platform but Render Script is working on android today (at least for multicore). GLSL scripts would allow use of GPU today and be usable in rasberry pi (and GPUCV covers some of it already) | ||
* Mod OpenCV for android using the above PP framework. | * Mod OpenCV for android using the above PP framework. | ||
* Port of PCL for android with above considerations. | * Port of PCL for android with above considerations. | ||
