Today i started to write the theory+tutorial of Ardupilot and Ardupilot Shield. This is the first text. I will try to release more texts describing all the stuff involved in this little baby. My goal at the end is to join all the papers and make the mega manual, very well edited and revised for everybody.This is the first paper describing how the voltage divider in ardupilot works:Ardupilot_paper_preAlpha.doc[UPDATE] You can thrust in my word documents. No virus... ;-)[UPDATE] A better version well structured here (Thanks to Sarel P. Wagner )
Sarel wow looks great thanks! I will send you some stuff more often ;-)... Ok i will do raw papers and you better put it together, please. My class for writing technical papers is till the end of my career, but a that time i will become an expert if i fallow you!
We did try the Subversion repository at Google Code for a while, but to be honest we couldn't figure out how to make it work with Arduino code. Subversion is designed around Make files linking together lots of code files, but Arduino doesn't use the Make concept. Instead. it's built around folders. So we just went with zip files in
Google Code instead.
Do you know how to make Subversion work with Arduino?
Jordi,
This will be great!!! Not being a programmer, I've been trying to muddle through the code and figure out your logic for coding autonomous flight. The best I could do was change a variable, then go fly and see what the effect was. A very labor intensive and time consuming task. But, if I can understand what the defines like "trim" and “alt_pitch_trim” and “pitch_set_point” actually do in the code it will be easier to tune each particular aircraft.
Thanks for all the hard work!
It's great to see some documentation on the project. I think it might be difficult for you guys to decide what level the documentation should be made at. Lots of the ardupilot followers/users are very technically capable but now you have a product that's becoming easier to install/use I think you'll find lots of much less technically inclined users.
I'm a developer and hate writing documentation! One solution that I wondered might work for you guys would be to use trac or a similar ticketing system (I think you guys used to use Google Code for the Subversion repository) and link that in with the commits. At a developer level that would create handy code for you (and others to add to the project) and at the same time it's kind of self-documenting.
Keep up the fantastic work on this project. You and Chris have a lot to be proud of. I don't fly RC but am looking to buy myself an Easystar and learn to fly it (before playing with ardupilot) all because of this project! Sit back from it all every now and again and look at what you've produced, really amazing work. (OK it's sounds like I'm just kissing ass now!).
I hope some time I'll be able to contribute to the project.
Comments
Hi Jordi, hope you don't mind :) this is not an update to your content, that stayed the same.
It shouldn't be hard to get the two working together happily.
I'll have a look at how it behaves with the Arduino IDE tonight and drop you a private message with details.
James
We did try the Subversion repository at Google Code for a while, but to be honest we couldn't figure out how to make it work with Arduino code. Subversion is designed around Make files linking together lots of code files, but Arduino doesn't use the Make concept. Instead. it's built around folders. So we just went with zip files in
Google Code instead.
Do you know how to make Subversion work with Arduino?
This will be great!!! Not being a programmer, I've been trying to muddle through the code and figure out your logic for coding autonomous flight. The best I could do was change a variable, then go fly and see what the effect was. A very labor intensive and time consuming task. But, if I can understand what the defines like "trim" and “alt_pitch_trim” and “pitch_set_point” actually do in the code it will be easier to tune each particular aircraft.
Thanks for all the hard work!
It's great to see some documentation on the project. I think it might be difficult for you guys to decide what level the documentation should be made at. Lots of the ardupilot followers/users are very technically capable but now you have a product that's becoming easier to install/use I think you'll find lots of much less technically inclined users.
I'm a developer and hate writing documentation! One solution that I wondered might work for you guys would be to use trac or a similar ticketing system (I think you guys used to use Google Code for the Subversion repository) and link that in with the commits. At a developer level that would create handy code for you (and others to add to the project) and at the same time it's kind of self-documenting.
Keep up the fantastic work on this project. You and Chris have a lot to be proud of. I don't fly RC but am looking to buy myself an Easystar and learn to fly it (before playing with ardupilot) all because of this project! Sit back from it all every now and again and look at what you've produced, really amazing work. (OK it's sounds like I'm just kissing ass now!).
I hope some time I'll be able to contribute to the project.
James