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.
Thanks. But I think this menu option is only available in Arduino 1.0.3. I guess I'll have to downgrade.
Also this version is only available on Windows and Mac. I'm using Ubuntu Linux OS.
I need your help. APM2.6/3.1rc2/SimonK. The quad is flying great in Stabilzie, also Loiter is holding pos and altitude without toilet bowl. What I noticed in my videos though is that the motors seem to be very aggressive in Loiter mode, especially in windy conditions. Please have a look at the video and point me in the right direction of which parameters to tune. Loiter PID's, throttle rate or throttle accel?
hello Randy & Devteam,
Is there a way for the system to detect if it's downward velocity decreases rapidly?
On the Fence, I read the Wiki here
and watched the Youtube
But I did not 'see' where its mentioned if the fence is ignored in Auto or not, i.e. can I fly in Auto and it will ignore Fence. Also if so and I am in Auto and I was past the second fence(+20 meters outside first fence) and I changed to Stabilized would it land or better yet try to come back home first?
I also don't see RTL Altitude mentioned so not sure what that does.
Thanks guys, this is cool.
If enabled the fence isn't ignored. So even in Auto mode if it hits it, it'll switch to RTL and attempt to come back. It will come back at the RTL altitude even if that's been set to be higher than the fence's maximum altitude.
As you can see with the fence it can be a bit like the left hand not knowing what the right hand is doing but that's 'cuz it's a fairly simple implementation at this point.
One note of warning on the Fence, don't set it to be too small! I.e. keep it at least 50m radius.
Perfect, I just set the max Radius to 500m, I know it sounds far but I've always worried about changing to Auto and I have the wrong plan loaded and it tries to go 10 miles away, this would take care of it.
Maybe we can get an ignore if in Auto in the future, but its still a great new feature with or without it.
Nothing new. I had a lot of such surprises see below.
Command to descend produced a turn right.
Peaks with no command and jumps back.
Try to disable the Dataflash Logs. After this I had no more such "implemented" surprise. I assume the Processer is at its Limits and it is a Timing Problem. You can read a lot of such Troubles in the Forum.
Wow, maybe I should go back to 2.9x where I never had a problem. I just upgraded.
I don't really want to turn off all the data logs, since I often fly without telemetry. I have the default ones enabled. Can I slow down the smaple rate instead of turning them off? Maybe there are some I could do without.
Can you have a look at the attached log file please. My hex does not appear to respond to any of the stick movements apart throttle which works as expected. The hex hovers for a few yards and then flips. I appear to have no control of in pitch, roll or yaw?
Set up as follows:
DJR 550 frame
6 x 1000 kV motors
10 x 4.5 props
4S 2600 LiPo
I have attached log files - being new to this I am not sure which you need?
Hope you can help.
but I don't know how to install it :( I have conected trought i2c port but now I don't know to continue with the installation.
I tried to calibrate with live calibrate but I obtain the message: "log does not contain enough data" and if i try to do the compassmot: "compass not healthy"
Please can you help me?
Sorry for my english.
What instructions did you use to connect the APM I2C port to the compass?
The instructions in the Wiki are for connecting a 3DR stand alone compass to the APM I2C port: http://copter.ardupilot.com/wiki/common-external-magnetometer-for-i...
How did you determine what I2C connector wires went to the right pads on the new compass?
From the symptoms that you have described, it sounds like you did not get your new compass wired up correctly to the I2C cable.
TCIII ArduRover2 Developer