Hello everyoneI have developed a hardware platform which I want to use to control a UAV, however I do not at this moment have the Software autopilot written. I was told that I could use ArduPilot and tailor it to fit my specific hardware. How difficult would this be? Anyone attempted and completed something like this? Is there a complete set of documentation on the software so that I can get started? Where can I get help with Q&A as I move along in the software development stages? tThanks in advance for your help.
You need to be a member of diydrones to add comments!
Thats why I designed the platform using an FPGA that way hooking up to the outside world should be pretty easy. I would love some help with the software part though anyone interesed? I could work it out to benefit anyone who would be willing to help.
My opinion might surprise you.
Due to the software complexity I estimate the total effort for autopilot to be 90% software and 10% hardware.
Because you made a hardware but never flown it, I estimate your hardware effort to be 50% complete (future adjustments, component change will be necessary).
As ArduPilot is actually a Development Platform (not a product with QA and pro user support), porting of such code directly to another hardware will take more time than writing a new one.
Hawing a different HW platform, what you can do is to learn from ArduPilot and Paparazzi then implement your own, maybe some code will be 'almost iodentical' at the end but copy-paste will simply introduce more bugs on your side you would ever imagine.
I think your project is unrealistic because you started the job BEFORE estimating the effort. The choice of HW platform directly dictates what you can borrow from the others.
Replies
Thats why I designed the platform using an FPGA that way hooking up to the outside world should be pretty easy. I would love some help with the software part though anyone interesed? I could work it out to benefit anyone who would be willing to help.
Due to the software complexity I estimate the total effort for autopilot to be 90% software and 10% hardware.
Because you made a hardware but never flown it, I estimate your hardware effort to be 50% complete (future adjustments, component change will be necessary).
As ArduPilot is actually a Development Platform (not a product with QA and pro user support), porting of such code directly to another hardware will take more time than writing a new one.
Hawing a different HW platform, what you can do is to learn from ArduPilot and Paparazzi then implement your own, maybe some code will be 'almost iodentical' at the end but copy-paste will simply introduce more bugs on your side you would ever imagine.
I think your project is unrealistic because you started the job BEFORE estimating the effort. The choice of HW platform directly dictates what you can borrow from the others.