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 in a 'motor out' case we should not try to control the yaw anymore but just let it spin its way back home. Perhaps even boost the spinning for some gyroscopic stability. That way we dont have to shut down a working motor.
i whole heartedly agree, some kind of protection should be in the immediate future.
This might be a great nonsense, but what if at firmware upload, a password was asked to handshake serial comms ? The password would be defined in the planner and the APM would be waiting for a password send from the planner to establish a successfull connection ? Just a thought.
Hi randy, it will be nice if user can reduce the copter speed when approaching home during RTL. I want it slow stop.
Hi Randy, here is the dropbox link with raw footage about AC3.1 ROI and CIRCLE function
Regarding my previous post about RTL, here is the internal log.
Thank you for your help, Mihai.
Not theoretical, and not hard. I believe that hacking MAVlink was demonstrated a year ago.
Rui, you can't transmit the password unencrypted, or somebody can easily catch it, and then use it. Encryption is the only way.
Encryption is basically using a password, but it can only be understood if you already know the password. So somebody listening in can't catch it (easily).
I was going to suggest encrypted comm, but I believe the process of decripting / encrypting all messages would be somehow slow depending on cipher length. However, there's nothing like trying it :)
I can't seem to load 3.1 rc7 to my X8.
First I updated to MP 1.2-88.
Did the upload as I usually do for my Iris. Connect cable, change port number and baud top right but don't connect.
Go to load firmware. It loads 3.01. I click "Beta Firmware". and 3.1 rc7 appears.
I click the X8. Syas "checking board version", and hangs for a good 5 minutes. After a while it will start to load Hex but hangs and then times out. My internet conection is good.
I tried loading the hex file from code.google, and then "load custom firmware". After a pause, it begins to load Hex, and then hangs about half way through.
I backed up to MO 1.2.86, but the same thing!
I have loaded 3.1 rc7 on my X8 using MP1.88 with no problem on 2 diff. APM 2.5 and APM 2.5.2 board (RCtimer clone). I have also loaded with MP1.87 and 86, no problem. I am using Windows 7.
Arducopter 3.1 CIRCLE around me
BLUE is MOT#3 and it looks lower than the rest before they all are shut off. I'm learning - what did I miss?