Moderator Comment by Hooks on June 14, 2009 at 3:26am

very very nice... ;-)

Comment by Tom in ON on June 14, 2009 at 4:49am

Thank you Chris. Excellent guide for those who started or will start this project. This will help others enter it with less difficulties. With further developments/expansion of the features/applications, this manual can be later updated by the community.

On my "wish list", it would be great to have a programming flow chart in plain English. This would allow for some of us newbies to understand the more intricate steps and also aid development.

For example:

1. read a value for a

2. read a value for b

3. if a = 0 then print the message ”Invalid value for a” goto line 5

4. if a = 0 then print the solution: ”The solution is x = −b/a.

5. stop.

Moderator Comment by Chris Anderson on June 14, 2009 at 5:05am

I should have noted that I hope the manual will eventually live as a wiki, which can be updated by the community. Explaining the code would be a big part of that. It's beyond the scope of a traditional manual.

Comment by D on June 14, 2009 at 5:46am

Chris, unless I missed it, where do you enter the desired airspeed to maintain?

Moderator Comment by Chris Anderson on June 14, 2009 at 6:42am

Hi David,

Great suggestions. I'll fix those asap. As for the FailSafe 1.6 code, this is only for people who have and AVR programmer and are able to modify code and compile it in C using AVRStudio. In short, it's for pros only and would only confuse people if I put it in the manual. We really don't want most people touching the MUX firmware.

Comment by Bryan Cuervo on June 14, 2009 at 10:28am

Chris,
This is excellent! Just what is needed to avoid having to navigate this ever growing/complex network for the essential set up info. I've made a major change to my EasyGlider, ordered the latest board and shield kit in anticipation of the official 2.2 release and I'm looking forward to continuing my test flights.

Developer Comment by John Arne Birkeland on June 14, 2009 at 11:04am

Looking good! What I would say is missing, is a layout of hardware functionality. A simple diagram drawing and description on how the different parts are working together like gps, i/o, servo, fail-safe (multiplexer, attiny), etc. It would make it easier to get the whole picture of how the system works, for someone new to the Ardupilot.

Moderator Comment by Chris Anderson on June 14, 2009 at 12:30pm

David,
There is no connection between failsafe1.6 and ArduPilot 2.2. Different chips and no interaction between them (by design!). Failsafe 1.6 is just for experts, and we really don't want beginners trying to mess around with AVR programmers and AVR Studio. We don't ship the board pre-;loaded with 1.6 because it needs to be tweaked for different radio systems--it would be a tech support nightmare. 1.5 is fine for most people.

Moderator Comment by Chris Anderson on June 14, 2009 at 12:32pm

D,

Target airspeed is line 4-6 in the ArduPilot.h file (see Appendix 2 of the manual)

Moderator Comment by Giles Barton-Owen on June 14, 2009 at 12:38pm

In the glossary you say IC2 rather than I2C or TWI, a small error but thats one I spotted. It's a good manual and I hope to see it grow into more than just for the Ardupilot (the Appendix 3 looks like the place for that).

Comment

• ‹ Previous
• 1
• 2
• Next ›
• Page