A few months earlier, mmormota and I have started to develop a combination of autopilot and OSD. We're made it for FPV purposes mainly, but you may have found it interesting because of the autopilot part. We've just accomplished our first flight tests in this week and the system didn't served it's temporary name: Crash 4 Sure :)
On the picture above you can see as it's going round on a small rectangle course. Here is the video: http://vimeo.com/15128879
Our main goals are:
- Simple installation, we hate the mess of wires.
- Keeping the part count and prices low.
- Make it modular for further expansions, but the basic unit must able to stabilize and bring back the plane safely.
Our unit is most likely a single chip design, based on an STM32 (ARM Cortex M3) controller witch performs all the tasks. This combination of the two systems is quite convenient. For example we can see clearly how the autopilot works, is the orientation correct, because it can display everything on screen real-time.
The sensing of orientation is IMU based, I'm currently using the Razor 6DOF IMU board from Sparkfun and mmormota is using ITG-3200 and BMA-180 breakouts for this task.
The autopilot have the following modes of operation:
-Manual mode
-Stabilized mode (exactly the same as ardupilot's "fly by wire")
-Waypoint mode
-Return to Home
We want to expand it's abilities with automatic takeoff and landing, but first we want to make the current software and features as safe as possible. We were using Raisonance's Ride7 and Rlink for he development, but run into the 32k code limit and have to transfer the project under Eclipse + GDB + OpenOCD + Rlink. Programming and debugging the target still didn't work very well, this environment is terribly complex and hard to configure everything right...
The entire code is in C, using floating point arithmetic everywhere. Now it takes about 10% CPU time to run everything what's related to the autopilot and the OSD consumes about 15% CPU time, so there is still plenty of possibility in the hardware. Ohh, and the core runs on 48MHz instead of the maximal 72MHz.
So this is the whole story in a nutshell, we're want to thank all of YOU who maintain this great community.
Special thanks to William Premerlani for the great papers !
Here are some photos of my equipment:
Comments
well done :)
beta tester here ready! :)
I really like the idea of autopilot+ODS in one system, any updates on the single board.
I would second the suggestion that you have sparkfun sell it. I know Chris was looking at options for an OSD to work with ardupilot that would be open source. If you make it open source you get the advantages of lots of people working for you for free in their spare time, it makes it easy to integrate in different applications, and you are not obliged to provide support. However, lots of people will pay for a plug-and-play solution and so you make money when you have a large installed base that open source gives you. This attracts the novices who are not programmers or electrical engineers and they are willing to pay (just ask Tim at ReadyMadeRC about this approach).
For exaple: http://www.rcgroups.com/forums/showthread.php?t=1290963
I think James is interested by the OSD part.
We're want to do it exactly the same way. FYI it's hex only AND locked, so you can't program an other controller with the provided hex file, only the ones which you buy from Remzibi. The point is, you can't made a Remzibi OSD form the given schematics and firmware.
If you could integrate it with APM
Integrate it with APM ?!
That doesn't make sense. C4S is all ready an IMU based autopilot, why do you want to connect it to APM?
If it'll be good enough, we would sell it.
If it won't be so good, competitive, if we don't have enough time or simply loosing interest, then we will publish everything.
So it's hard to say in this community, but it will remain a closed source project.
If anyone had a good idea, how to made it open source and earn some money with it at the same time, don't forget to post it!
-
1
-
2
of 2 Next