For what ever it's worth, I'm experimenting with converting the APM2 to a sensor suite that plugs into a higher level computer (such as a gumstix overo, beagleboard, laptop, desktop, etc.) My approach is to use the "library" portion of the ArduPlane code to simplify accessing and managing all the hardware sensors, but write my own setup() and loop() functions that (for the most part) just read the hardware sensors through the library API and write the output into a straightforward binary/checksummed packet format that my actual flight computer can parse.
I have some well developed autopilot code that runs on a a linux gumstix (or just about any other posix system) but I'm in need of some sensors to test with.
I realize there are any number of ways you can combine all the possible pieces together to get a solid autopilot, and there are any number of engineering decisions and choices that we face along the way, but for me I enjoy the bigger head room that a higher end linux computer offers, so this is the route I'm taking.
Yeah I have nothing wrong with the code. Its so good I have nothing to add. I dont just want to buy a uav and assemble it. I would like to make it a project and learning experience. Is it really that complex? I was just going to do it piece by piece. Like start with just fly by wire, then telemetry, then basic mission planner, then stabilization, then like a digital fence/border then waypoints, then complex mission planner. Something like that. Start basic then just add on. I will be using the current code as a huge reference. How long do you think this will take?
Replies
For what ever it's worth, I'm experimenting with converting the APM2 to a sensor suite that plugs into a higher level computer (such as a gumstix overo, beagleboard, laptop, desktop, etc.) My approach is to use the "library" portion of the ArduPlane code to simplify accessing and managing all the hardware sensors, but write my own setup() and loop() functions that (for the most part) just read the hardware sensors through the library API and write the output into a straightforward binary/checksummed packet format that my actual flight computer can parse.
I have some well developed autopilot code that runs on a a linux gumstix (or just about any other posix system) but I'm in need of some sensors to test with.
I realize there are any number of ways you can combine all the possible pieces together to get a solid autopilot, and there are any number of engineering decisions and choices that we face along the way, but for me I enjoy the bigger head room that a higher end linux computer offers, so this is the route I'm taking.
Yeah I have nothing wrong with the code. Its so good I have nothing to add. I dont just want to buy a uav and assemble it. I would like to make it a project and learning experience. Is it really that complex? I was just going to do it piece by piece. Like start with just fly by wire, then telemetry, then basic mission planner, then stabilization, then like a digital fence/border then waypoints, then complex mission planner. Something like that. Start basic then just add on. I will be using the current code as a huge reference. How long do you think this will take?