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 think we should leave it on spin when armed. The only addition I would suggest for 3.2 is that we disarm if the copter is upside down (past 90 degrees) in any Stabilized based mode (ie loiter and auto but not acro), for more than 1 second.
Working fine here also. rc5 and latest minimosd for copter.
I had a crash doing fpv the other day. I was just a few inches off the ground but must have bumped into something and it flipped. Luckily a friend was near by and grabbed. The props never stopped spinning even when it was upside down. If this state can be detected then maybe an auto disarm would help.
Also using RC5 now :) thanks for that devs.
I am wondering if its just me doing some wrong with the failsafe.
In mission planner when i turn off the transmitter it allways go to LAND mode instead of RTL i have set up.
I have enough sats 3d fix as far i can see.
Havent used it before this failsafe, just due to bad weather i gave it a try at home without props so it isnt moving around.
Maybe its a small bug or something?
Is your transmitter going to it's on failsafe and setting your mode switch to land? You would be able to tell by looking at your flight mode screen in config/tuning. Turn off the transmitter and see if it goes to that position. If it does then it's just a matter of setting your transmitters failsafe so it goes to your RTL mode. Also check that your throttle is going below the amount set for the failsafe.
...this is the reason I will never let the props spin on arm. Once crash detection is implemented then I will definitely do it, but for now I will not risk damage to the electronics if the quad crashes upside down a mile away (yes, I fpv a mile away regularly) with the props still trying to spin. I also thing that the motors should never spin with the USB port active (meaning it is plugged in to a computer) regardless of any other settings. I've been watching the passionate debate here and on the developers group on googlegroups and I think many, MANY fine points are being made - some are quite false but most are quite good! - and for me I just wont be happy setting it to spin-on-armed until its a bit safer. I think the intent of what it is trying to do though is very good, and I'll be using it once crash detection and USB-connection-detection are in place.
Completely agree. I have some nice plastic prop scratches on my PC monitor when I armed when connected to USB....
I've never ha
Sounds like a real developer headache since it doesn't seem to be the same level of sensitivity on each board. Wonder how many scratch the borderline at 8MHz once everyone tries 3.1.
How about a switch in MP that lets the user select between high and slow speed? That way the user is aware of the problem with his board.
I just upgraded to RC5 on one of my other quads (which is RTF from 3DR).
Just uploaded and compared with my previous params, lot of params seems to have changed, come in from the blue.
- E.g. Sonar gain from 2 to 0.2, STB_PITCH_IMAX from 0 to 800, etc.
- Lot of values have been truncated from 7 decimal points to 3 decimal float. Any reason for it?
Screenshot below. Can someone tell me why is this done?
knocked down ANGLE_MAX from 45º(4500) to 30º(3000) and wow so much better. At least for me this is so much smoother feeling. Thanks Josh Welsh for this tip!
I think this should be a good place for any noob to start when they are configuring their quad. Stabilize and althold are much more tolerable with the limit of tilt angle to 30º instead of 45º.
When you shut off your transmitter, was your multirotor sitting in the same place that it was when you armed it?
I don't know about RC5, but with the regular 3.1 release, I had to move my hex several meters away from the arming position in order to trigger RTL on transmitter loss..