Using an Phillips NXP LPC20148 ARM7 processor, a Nintendo Wii motion+, and some xbees I've made a really stable platform for quads. (mode details here) It is running FreeRTOS which makes it very expandable in the future. My old frame flew great with it, but I wanted something smaller. Enter my new carbon fiber mini-quad:
Here's the plug-and-play LPC flight controller. The motion+ is inside and wrapped in foam. The XBee plugs in to its' socket on the top. The ESCs plug in back.
Here's the remote. I can easily adjust the PID gains, and it sends them to the flight computer before taking off (there's no eeprom on the LPC). You should see the difference 0.05 on the pitch and roll I term makes in stability.
Not bad for an computer engineering undergrad in their spare time, with no class credit, and on the budget I get as a photojournalist for our paper, eh? This is remote v1.5, and remote v3.0 is in the works. Here's a sketch I drew a couple of weeks ago.
Everything's open source! I hate seeing people's cool project, wondering how it works, then getting the promise of OSS sometime in the future. I want to see how asap. Well here's how I did it: The remote code. The copter code.
Comments
About my site: Yep. I chose tonight to upgrade the CMS (zenphoto). Not a good choice, on afterthought. I'm on my svn server fixing things. That page is up and running now. Now I'm fixing the ajax image browsing.
ArduPilot? I'm sure one could. My plan for my remote v3.0 is to write code plugins for lots of flight softwares with a common protocol. One controller to rule them all: any digital project you want.
I like the remote, can you give us a little more info about it?
I see your remote code is an arduino sketch, so it's basically an arduino?
great work with acrylic