Here's what I hope is the final release.
As the new Manual gets formatted, you can view it at: http://code.google.com/p/ardupilot/wiki/ArduPilot25
Until the content is finally moved over the 2.4 manual is still a great resource.
Ardupilot_25_RC2.zip
Bonus - If you look check out the Waypoint_writer_25.pde file in the test suite, you can upload relative waypoints. This isn't supported in the config tool yet.
Jason
UPDATE -
A lot of people were having trouble with the GPS code and LEDs. I reworked the GPS parsers today to iron out some things. They were nothing that would interfere with flight, but I highly recommend using this new version. I've also added the ability to scale down your plane's roll based on airspeed. This should help planes that turn faster when they go slower. We may tweak this a bit in the future, so I'm looking for feedback on it. Note you can always turn it off in your header file with this line:
//6-4
#define AIRSPEED_TURN_P 1
see the header file for more instructions
Comments
The yellow stat doesn't flash but that's not critical i guess.
I'm only at the ground testing phase so it will be interesting to begin testing in the air!
Jason
If you don't have a computerized TX the only thing you can do is set the failsafe to low throttle stick and lowest throttle trim, then don't use low throttle trim again. This can pose problems with your speed controller. Some will want to spin the prop with throttle stick low and throttle trim middle.....
I still however, get no difference in the planes' behavior between POSITION_2 or POSITION_3.
With RTL the plane should turn and attempt to fly back to 'home' and in LOITER it should, as I understand it, go into a circle over whatever position it was currently in. All I get level stabilized flight until I have to bring the plane back, navigation is not functional so I'm not sure what's up?
Manual is controlled by the MUX. It's a separate chip. You can take over Manual control in Position 3 but I would not recommend it. You basically have to start controlling the MUX from the software and you defeat any safety measures the MUX provides. If the main processor crashes you'll loose control of your plane.
Just use position 1 for Manual. and positions 2 and 3 for your flight modes.
Jason
#define POSITION_1 MANUAL
#define POSITION_2 LOITER
#define POSITION_3 MANUAL
but don't get the system going back into MANUAL when I hit that third position
Thanks for your radio settings. I will add it to the manual.
Just in case there is confusion - AUTO flies waypoints and RTL is just return to launch.
On the serial output when the full 2.5RC is loaded I do get "##7| LOITER" & "##6| RTL" (or whatever I designate) indicated when I flip the switch so it does seem to work...
Would it help to know the millisecond values of that channel?
##0| MANUAL
##2| FLY BY WIRE
##1| STABILIZE
##2| FLY BY WIRE
##0| MANUAL
##2| FLY BY WIRE
##1| STABILIZE
##2| FLY BY WIRE
##0| MANUAL
##2| FLY BY WIRE
##1| STABILIZE
##2| FLY BY WIRE
##0| MANUAL
This sounds like your radio is not sending the correct signal to switch the hardware mux on the ardupilot board. Those three ranges are difficult to change without a hardware programmer.
What you need to do is to adjust your radio so the values are outputting correctly. Every radio is different, so could you document how you setup your radio and I'll add it to the Ardupilot Manual.
I've made a test application for you to debug your switch. I will add it to the test suite for Ardupilot as many people are asking this same question.
Ardupilot_25_control_switch_test.zip
-
6
-
7
-
8
-
9
-
10
of 14 Next