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'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..
Ah good deal Michael, glad that worked out the way you wanted. I put mine up to 80 :)
Just loaded RC5, it does not arm, no settings changed.. I know some people have raised this issue before on this forum. As this forum is almost 200+ pages long its rather tedious to find.
Can someone tell me how do I arm it now, red light keeps blinking (btw, this is my 100+ flight) :-P, so something must have changed in code :)
Jim.. when you say "the regular 3.1 release" do you mean 3.0.1? -rc5 is for 3.1 which isn't released beyond that release candidate yet, that's why I ask.
I've rolled back the changes and compiled successfully(RC5). I'm curious if any other libraries/functions are affected by reverting back to the original bus speed.
I plan on testing it today when I get off work. Doubt I'll fly with it. Just want to test if it solves my problem.
Ah, that was it.
Had to move the quad some few meters away to get it do the RTL.
Thanks Jim. Problem is solved :)
Good point Detlef. Especially if it's a tolerance issue. Though all boards meet a tolerance on initial production speed requirements, a few may be on the edge or just outside the boundary of the hard coded High Speed setting.
I did some more aggressive testing of 3.1rc5.
After autotuning (it flew great) I decided to start playing with flips. I read across Rob's post where IIRC he liked an ACRO_RP_P of 6.5, so I decided to try 7 (hehe, from 4.5). That was interesting; you get fast flips but IMHO it becomes difficult to finesse through gaps. I normally don't run expo on my tx. So I tried dialing it all the way up to 50% and I was still over correcting all the time. So I think I'm going to fall back to 4.5 to get used to shooting gaps with the rig, then I'll carefully dial up the flip rate & expo to get a better balance of precision and quickness.
I also got to play with Loiter, Acro, Alt, Stab, and RTL on an exceptionally windy day (25mph, with 38mph gusts). Loiter was excellent; watch the part where I loiter in front of myself. It tilted about aggressively in the swirling winds behind those trees, yet maintained a solid position. I think if I softened it up it would not look or sound so scary, but then it would probably drift in heavy winds. Early in the video I played with aggressive yaw in loiter, and as you can see the position was rock solid, and no toilet bowling even with my built in compass.
The RTL... my control rx just so happened to failsafe in that wind. I haven't tested RTL since the recent processing speed improvements. So I decided to let it do it's thing. It flew faster toward home than I'm used to probably due to the tail wind. I'm set for 30mph lateral max, but the trip home was short so it started slowing just after it broke 20mph. The ascent and descent performance with the latest code is phenominal! The descent was now so fast it scared the c**p out of me; it took a lot of faith for me to not take over control at that point. Fortunately it stopped on a dime right in front of me, but it may take some time for me to get used to the "daring auto descent" LOL. My 'max auto z' settings are +350 and -250, which my rig seems to be able to handle well; so I'm keeping it that way. I also like the newer feature where RTL yaws to launch heading before descent; I suck at transitioning from the monitor to LOS. ;)
Once again... cheers to the devs! :)