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 picked up the same discrepancy and mentioned it here: http://diydrones.com/xn/detail/705844:Comment:1345279. Randy mentioned that he did recall an issue with the printing on some early boards and it looks like both yours and the one in the example image in the wiki show the y axis in the wrong direction. Given all the interest in external mags since the release of V3, I'm sure that it would save a lot of problems if the image was updated and a warning regarding the early boards posted.
Thanks a lot.
I was just demonstrating my friends at the flying field how my APM 2.5 fitted quad could do missions on its own as halfway through it decided to bank steeply and race away at full throttle! My heart skipped several beats there! Luckily, after two wide high speed turns I managed to get control back at a stable position from where I could safely bring it home.
Of course, to add to the drama, my GoPro recorded the flight in full detail. In it you can see that the quad is nicely following some waypoints as suddenly it banks and hits the throttle. What on earth (in the sky!) has happened there? I attached the log file and uploaded the movie to YouTube (the flyaway occurs just after the 1:00 mark; at around 2:00 I regain control by switching back to Stabilize):
anyone to help me ...???
is possible that the value in the Y-Gyro is precisely because of the accident, if not the cause .... the truth is that I was in a perfect hover, and hexa shot out forward, without any explanation I could download accelerator .... only after crossing an asphalt track, to prevent breakage was greater ... will have traveled about out of control about 20 meters tall ... and very little ... but with a lot of speed to later ... the truth is I'm new to this system, and I fail to distinguish that value attached log that might give me some clue of what happened ...
accel noise? your log does not have IMU info. Turn on and test your accel noise.
GPS Hdop is high also (sometimes > 2.6).
Marcelo: I'm newbie too but try to diagnose with this http://copter.ardupilot.com/wiki/common-diagnosing-problems-using-l... or perhaps this helps too http://copter.ardupilot.com/wiki/downloading-and-analyzing-data-log... , http://copter.ardupilot.com/wiki/downloading-and-analyzing-data-log... it's useful if you attach the dataflash logs too.
You must download your log : http://copter.ardupilot.com/wiki/common-diagnosing-problems-using-l...
turn on IMU log also to see your accel noise.
Also, change the Loiter PID P from 1 to 0,5 for reduce the aggressiveness.
thank you very much ...! This would be the log ...???
Finish with .log
This ...??? the problem is that I can not identify the specific log for the accident flight, I see that ends in 44, as he recorded the telemetry ... but the one in the EPROM of the board, to download it to my notebook, was recorded with today's date ...