ArduCopter 3.0 is ready for widespread use. To make the transition easier, this time we are asking people to voluntarily upgrade from 2.9.1b for the next month or so before we make 3.0 the default firmware downloaded by the mission planner. The new version can be found in the Mission Planner's Beta firmware's link, firmware.diydrones.com, GitHub and the new Downloads Area.
Warning #1: A bug was found in the FENCE in which if you lost GPS it could lean at extreme angles as it tried to maintain an invalid position. This is fixed in AC3.0.1-rc1.
Warning #2: This release has not been fully tested on Traditional Helicopters
Warning #3: GPS glitches can cause sudden and aggressive position changes while in loiter mode. You may wish to reduce the WPNAV_ACCEL to 100 and Loiter PID to 0.2 (from 1.0) to reduce aggressiveness.
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.
2. Click on the MissionPlanner's Firmware screen and click the "Beta Firmwares" link on the bottom right. The version numbers should update to "ArduCopter-3.0.1rc2", then click the appropriate frame icon and it should upgrade as per usual.
Note: Nav parameters have been combined with Loiter so do not be concerned if you can't find them.
4. If you purchased an APM prior to March of 2013, update your PPM encoder to the latest firmware.
5. Try out the new version in stabilize mode first, then alt-hold, then loiter and finally RTL and Auto.
Special Thanks to Marco, DaveC and the rest of the beta testers for putting 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.
Added by Craig:
Please watch Randy's videos on setting up and flying APM-Copter 3.0 before you go flying. They are excellent!
I'll do a few ground tests, and then also enable the NAV-log and see if I can determine which is which.
The most common problem with the auto functions not holding altitude properly happens when you switch into the auto mode when THR_MID has not been set properly.
In addition to the wiki Randy mentions we have a whole section in the new wiki http://dev.ardupilot.com/
Please join the drones-discuss google group and we can get you started.
Yes, it's starting now. Josh Potter flew it first. But there's a bug in the 3.0 code in trunk. There's a filter running on the Roll and Pitch Rate controllers that is much too slow, so basic stability is affected. It's not necessarily going to cause a crash, but it doesn't fly well.
I've fixed this on my 3.0 fork and test flew it myself, and it went quite well. I expected to have a problem due to vibrations on the 450, but it really wasn't bad at all. Loiter was pretty awesome.
Can you post a log file where you have the vehicle oscillating?
Have you tried putting the compass up on a stick yet? That's the #1 easy solution. That is DJI's solution, and it's perfectly valid for people who aren't interested in mucking about with this stuff.
If you aren't interested in working on your airframe, and don't want to put the mag up on a stick, then yeah, this system just isn't going to work out for you. We are not magicians. We can't make the magnetometer work when it's subject to interference.
Leonard, yes, using the same battery I think is a big deal.
Remember the problem I had at AVC with the compass? I had to really skew the declination to get it to fly straight. I was using borrowed batteries.
Back at home now, I'm using my regular batteries, and I just put the declination back to auto-declination, and it's perfect. I think the reason the mag was so bad at AVC was because of the different battery I had to use.
Here is the guide:
there is a repo somewhere for 3.0.x?
and anyone know how far is the fix for OptFlow and sonar?
The repository is located here