I make a quadcopter, and before buying the pieces, I would like some advices because I'm a beginner in the subject.
So, it's based on the PL2Q printed by my 3D Printer.
But, the main idea is to remplace the gyro, telemetry, GPS, camera, accelerometer and the magnetometer with a smartphone (In this case, a HTC Wildfire) and put it on the camera place. It's connected with motors (and ESC) by a Arduino ADK board.
Here is the basic idea.
Bonus: With a phone, I can :
So, isn't this so cool? I could even start a kickstarter campaign and sell a UAV at 200$ without the phone but compatible with Android, iOS, Windows Phone,...
But for now I build one for me and my university
Thanks for reading
PS:Sorry for my poor english
I was thinking along the same lines. So, how have you gone so far?
Hey I worked on this solution for a plan...I didnt fly it but I did closed the cycle and connect it to Flight Gear Simulator to test it.
I use Android smart phone and IOIO to control servo.
pls check this project http://code.google.com/p/androiv-uav-over-android/
Android is not a real time operating system, it's not suitable for real time control.
You can use an APM or any other flight board(With it own's IMU, not the one on the android) to control the aircraft and have the android provide you with Telemetry, FPV and maybe use it's GPS but that's about it.
please tell me what you mine by that is not a real time os please explain ?
Realtime I/O means that the control signals happen in "Real" time. If the OS sets the control by tasking the operations it happens when the OS has the time to do it. That causes lag and the more operations the OS is doing the more lag there is.
Real time OS's send out control functions first and do other operations in the background. They give priority to control functions.
Android, OSX, Windows are not realtime. Linux does have some realtime kernels available. QNX is a realtime OS. POSIX is a realtime OS Ect...
So the real problem is that the not the OS but the number of processes that can be handled in one time?
Then limiting the number of processes will help this and more core in the processor will make it more real time. As well is knowing the number of processes and lead time the need for physical action within the program.
I think within a few years small android combination devices (basically phones, but maybe a bit smaller) will be able to have apps that do virtually ALL the flight control, GPS plus FPV and still pics/video. I can't see why it would head in other other direction, because the low cost of these devices made by the 100's of millions will have to edge out even the lowest cost dedicated hardware GPS stuff.
This is a view from the outside, but it is akin to al the things computers now do in software which previously required hardware or completely different devices.
With complete tablets selling for $150 (on sale) with GPS in them, how long before a sub-$100 3 inch screen phone/gps programmable do-dad which plugs into a receiver or other interface module and does most everything?
I say 5 years, but that's probably on the long end.
Edit -even if android is not "real time" now, additions to it plus outside interfaces for the stuff that has to be really quick could probably make up the difference. Some might depend on the use - but for photog and general flight (not flips, races, obstacle courses, etc.), would you need realtime for anything other than some of the motor balancing?
We'd need to know how slow it is....and why it could not be made quicker.
How are you going to connect the android to Arduino? I've only done it successfully via Bluetooth
We made flone, and it only cost around 70 euros: