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.
This is why I opted to put LED strips at the bottom of my quad arms when I first built it. When the quad is armed the LEDs are on and when the voltage drops to a certain level they start to flash. I prefer a visual light indication that the quad is armed compared to a visual prop spinning one...
I might as well chirp in too, I think props spinning as default is a good idea, people that are new to this, and are not expecting it need to get a little scared, this will get their attention without being dangerous. It will keep bystanders at bay too. Now maybe they will go back and read the warnings (or complain on the forum) Those of us who know about it will expect it or simply disable it. Having said that I disabled mine in favor of LED's and a buzzer, love the buzzer. Charles Lakins on here is selling this unit http://diydrones.com/forum/topics/apm-2-x-led-buzzer-modules?commen... which makes it super easy to install.
I've added a link to Charles's solution to the wiki as well.
I've got no problems with 3.1-rc5 and minimOSD. Flight mode and all other data display fine. Maybe its the minimOSD version you're using Steve. I'm using OSD extra 2.3 676... There are newer versions too.
Thanks for the feedback Jay!
I finally built an APM2-quad binary (here) which should show us more details of what's happening with the angle boost. It logs to the dataflash at 5hz or when the angle boost falls under -1000 using a modified PID message.
Could you load this up onto your problem copter (tell me if it's not an APM2 quad) using hte mission planner's Load Custom firmware link and give it a try, then download the dataflash log and post them here? Now, it may not actually be necessary to fly the copter...it's probably ok to fly it but if you can reproduce the problem on the bench, maybe with props off that'd be just as good. might need to wave it around, raise/lower the throttle.
When CLI is disabled (#define CLI_ENABLED DISABLED), it's impossible to download any logs. Is it possible, when CLI is disabled and LOGGING enabled, to have a minimum of CLI to allow log's downloading ?
Ok, good point and good idea. In the past we've talked about allow downloading of logs through mavlink which would also allow us to avoid the cli. Let me chat with Tridge about this part.
Yeah minimosd is working fine for me too with Rc5. Also using MinimOSD extra r621
Still works here with MinimOSD-Extra_Copter_Pre-release_2.4_r682.
OK I will try it today but since I have rc5 on there now, and the weather is nice, I'm going to fly a lot with that to see if the problem shows up. So far I've taken a handful of flights and haven't seen it at all.