Warning #1: Compass calibration and reducing interference is far more important than with 2.9.1b
Warning #2: GPS glitches can cause sudden and aggressive position changes while in loiter mode. You may wish to reduce the Loiter PID P to 0.5 (from 1.0) to reduce aggressiveness (see image below of where this gain can be found in mission planner).
Warning #3: optical flow is not supported but will be back in the next release (AC-3.0.2 or AC-3.1.0).
Warning #4: loiter turns does not maintain altitude. This bug will be fixed in AC-3.0.2.
Warning #5: This release has only been lightly tested on Traditional Helicopters.
Improvements over 2.9.1b include:
WPNAV_SPEED, WPNAV_SPEED_UP, WPNAV_SPEED_DN, WPNAV_ACCEL allows configuring speeds and acceleration during missions
How to upgrade:
1. Make sure you are using Mission Planner 1.2.59 or newer (get it here)
2. Click on the MissionPlanner's Hardware, Install Firmware screen. The version numbers should appear as "ArduCopter-3.0.1", then click the appropriate frame icon and it should upgrade as per usual.
3. Reduce the Loiter and Alt Hold PIDs if you have modified them from the defaults. The modified PID values for the 3DR frame can be seen in the image below.
Note: Nav parameters have been combined with Loiter so do not be concerned if you can't find them.
5. Try out the new version in stabilize mode first, then alt-hold, then loiter and finally RTL and Auto.
Numerous How-To videos are available:
Special Thanks to Marco, DaveC and the large number of testers on the pre-release thread who put their copters at risk during the extended testing period. Some of their videos can be found here, here, here, here, here and here. Thanks also to MichaelO for the MP changes required for this release.
All feedback welcome. Please put your questions, comments (good and bad!) below.
I have a small problem tuning 3.0.1 to perfection on a particular machine.
It's a foldable quad, inspired by Steadidrones' QU4D, with front arms in "hero mode" 150 deg. apart, and set up in MP as a "V"-frame. The trouble is yaw and yaw-authority related. It holds alt and position extremely well, flies straight lines both front-back and left-right beautifully, but anytime I apply yaw it ill-behaves.
Yaw in loiter woud yeld circling in increasing diameter up until 3-4 meters where it would settle and keep circling. Releasing rudder stick will have the quad snap back to center and holding nicely. In RTL, if WP_YAW_BEHAVIOUR is either 0 or 2 it will fly straight back without a moments hesitation keeping whatever heading it had. With 1, it will first do a large circle arc, which looks and feels unsettling :) then come home straight. And in high-speed Stabilize flight, applying yaw will have the motors sound like Rate-D is too high... a 2-4 Hz police siren.
Unfortunately, no logs. My beat-up APM 2.0 reports "dataflash not inserted" so I'll try parameter adjust from your wild guesses.
Really nice Ivan, thanks for your feedback!
OK i did the Scary compassmot testing on my desk and found out the office is very very dusty lol. First run i got 366% so i moved the apm on top of the top plate and did it again and got 26% Going ot tidy up the wires some and do a test flight to see if it helped. Worries me with the apm not really being protected in any way..
Got it thanks...
For some reason, I thought MSI is something different than the Mission Planner:)
That's where I got confused. All is good now...
ok got in a flight. It does better and the rlt is pretty good. Landed within 20' of launch. loiter is still iffy. Sometimes it does well and other times it wanders and starts going towards the ground. Ideas?
I have a small problem , I wanted to set a new firmware on a new AMP2.5 Board .. So I did connect it to MP unmounted to frame and with no wires attached just the bare board with USB to laptop ..connected to laptop fine and booted up ..then I went to CLI ..and did a RESET ..it asked to confirm with a Y ..and I did confirm to reset ..then it asked to reboot the board ..So I unplugged it and plugged it in back in to reboot .. That's when my trouble started, it is now not being picked up by the laptop and MP does not "see" it .. After boot it has green power light on and Red led blinks slowly .. What have I done wrong and how can I get the MP and laptop to Recognize the board ? Have I bricked it? Do I need to re-flash a boot-loader to the ATMega chip ??
Is there a full list of all default parameter (some where). Would like to compare my settings with the default ones -Without overwriting my own settings.
Attached are the default params for a quad with AC3.0.1. You should be able to use the "compare params" button on the MP's Config/Tuning > Full Parameter List screen.
Actually there shouldn't be any need to reload the firmware after doing the cli, "setup", "reset", "Y" procedure. What that does is reset all the parameters in eeprom to their default values but it does not touch the flight controller software which is held in the AVR2560's flash (not to be confused with where the logs are which is the "dataflash").
Doing the reset should also not affect the small avr32u2 chip which is responsible for the usb connection with your computer. So from there I agree with Richard that you should check the USB, cable, reboot the laptop or try another computer.