After months of testing, ArduCopter 3.2 (aka APM:Copter) is ready for widespread use and we invite all users to give it a try. In order to manage the support load at first it will be available only through the Mission Planner and APM Planner2's Beta Firmwares link. This link is visible from the regular "Install Firmware" page if you check the "Advanced View" on the Config/Tuning >> Planner page. On APM Planner2 the "Advanced View" it is under the File menu.
In about two weeks we plan to replace AC3.1.5 with AC3.2 as the default version dispensed by the ground stations.
The full list of changes can be found in the ReleaseNotes but here are the highlights:
Flight Mode Enhancements:
- PosHold flight mode: similar to Loiter but with direct response to pilot input during repositioning
- ACRO mode handling improvement EXPO (for faster rotations)
- Drift mode uses "throttle assist" (similar to AltHold)
- Smoother transitions between flight modes (i..e when entering Loiter or RTL from high speeds)
Mission Enhancements/Fixes:
- Spline waypoints
- Do_Jump, Conditional_Distance, Conditional_Delay fixed
- Do_Set_ROI persistent across waypoints
- Condition_Yaw accepts relative heading (i.e. current heading + 20)
- Reset horizontal position target when taking off in AUTO to avoid lean due to GPS position drift
- Rally points (Pixhawk only)
New Sensors/Devices:
- Lidar-Lite Range Finder, SF02, MaxBotix I2C sonar and Analog sonar (which was missing for Pixhawk)
- EPM Gripper
Safety Features:
- EKF/DCM check will switch to LAND mode if heading error > 60deg for 1 second
- Baro glitch detection
- Pre-arm check for Gyro calibration success
- Pre-arm check that internal & external sensors (gyros, accels and compass) are consistent (Pixhawk only)
- Parachute support (Pixhawk only)
- Feedback to Pilot when taking off in AltHold, Loiter, PosHold (i.e. motors spin up a little as throttle is raised)
- EKF (new attitude and position estimate system only used for reference in this release)
Bug Fixes:
- Pixhawk GPS driver buffer overflow that could lead to missed GPS messages
- Pixhawk I2C bug that could lead freeze up if I2C bus is noisy
Known issues/Warnings:
- Pixhawk users will need to recalibrate their compasses
- PosHold won't show up as option on FlightMode screen if you have an old version of mission planner. Please select Help > Check for Updates
- Landing detector is more strict meaning it may take longer to disarm after RTL, AUTO
- Set THR_MID parameter especially if you have a very powerful copter because "Feedback to Pilot" raises throttle to 1/2 of THR_MID
- Spline twitches slightly as it passes a waypoint especially if WPNAV_SPEED is set > 500.
- Dropped support for NMEA and SIRF GPS on APM boards (ran out of Flash space)
- Dropped ssupport for sonar for MultiCopters on APM1 and TradHeli on APM1 & APM2 (ran out of Flash space)
If you hit issues, please post them in the APM Forum and include a dataflash log file if possible.
Special thanks the Marco and the Beta Testing team from the AC3.2 beta testing thread who put their copters at risk in the pursuit of a smooth, safe release. Here are links to some of their videos: Marco's DJIs900, Holger's Water Tower, Josh's Acro, Ray's TradHeli2&FPV, Raph's Hawaii, PhillS's CommandYaw, Thor's Zombie Run&FollowMe, Phanivyas's Test, Rob's TradHeli, Christian's Test1&Test2, Balloon's Spline, JimJ's FPV, Ultrojo's ROI & Spline&FollowMe1&FollowMe2, Troy's Mission
Thanks also to the code contributors to this release including Tridge, Jonathan, Leonard, RobL, Paul Riseborough, MichaelO, Julien Dubois, David Dewey, Andrew Chapman, Emile, Allyson and many more. If you want to get involved check-out our dev wiki.
Comments
Possible Unwanted Surprise in Circle Mode:
This is really a Mission Planner matter but as other such are discussed here I'm posting it here:
Aircraft: Custom "Dead Cat" running Pixhawk 3.2-rc12.
I've been running the latest MP Beta until a couple of days ago when the update dialog box appeared on launch. I accepted the update (to 1.3.11 build 1.1.5426.22786).
I've been flying circle mode a lot, playing with different sizes and speeds at different camera settings to see what does and does not yield acceptably smooth panning video.
When I went into the main parameter list in the new MP my old value for circle radius, 500, was there. This was in centimeters in the previous version, so meaning the circle had a 10 meter diameter. I flew circles with that setting the day before the update and that's how big they were.
However, now next to this value in the updated MP is the word "meters".
If the radius value really was 500 meters, invoking Circle might have had the quad, even with my very slow relative speed setting of 7 degrees/sec, streaking off at high speed in what would look like a straight line to the pilot.
I really didn't care to try that as I have trees and terrain issues here, so set the radius to 3. And that's about the size in meters of the circle it then flew, which makes me think the 500 really was meters.
Maybe I'm missing something here but maybe be cautious if you've been using circle mode and have switched MP versions.
Its been removed from 3.2 -http://copter.ardupilot.com/wiki/ac2_positionmode/
At my Pixhawk Position dont work. Another user tested it on an APM and there it also dont works. GPS hdop 1,58.
Loiter works good, drift works great spline also great only Position makes trouble.
I have enjoyed about a dozen flights over the past 3 days and my experience with 3.2 has been wonderful. Position Hold mode is just fantastic. Thank you so much to all who had a hand in this latest release.
It has been blowing a gale though, so I have not been able to do an autotune yet. Even so, my APM powered IFly-4 is flying immaculately in high winds on standard parameters. I can't wait to try some more complex missions when conditions improve.
I am interested in learning more about the external outputs for LEDs and buzzer.
On 3.1.5 I ran the following Configuration:
A4: AUX LED - Front Left Arm LED (RED)
A5: Beeper - 5V Buzzer
A6: GPS - Front Right Arm LED (GREEN)
A7: Motor LED - Rear Right Arm LED (BLUE)
A8: Motor LED - Rear Left Arm LED (BLUE)
Configured based on this page.
Since Upgrading to 3.2 I have swapped things around to the following configuration based on advice for 3.2 users on this page:
A4: Motor LED - Rear Right Arm LED (BLUE)
A5: Beeper - 5V Buzzer
A6: GPS - Front Right Arm LED (GREEN)
A7: Arming LED - Front Left Arm LED (RED)
A8: ???Appears to be extra motor output??? - Rear Left Arm LED (BLUE)
Have I got that set up in the optimal way? Is A8 the same as A4, or should I control both rear (BLUE) LEDs from A4? Is there anywhere I can go to read more about how the LEDs report things like waypoints, failsafes, etc?
Hi,
thanks for the great work so far. I haven't found the right place for posting new feature requests, so I hope it's okay to post them here:
1) Adjustable BatLow buzzer alarm
Is quite handy and shouldn't be too difficult to implement ...
Unless I've missed something that's not implemented yet, although I think I've seen that in previous firmwares.
2) Native FrSky telemetry support (but I think that's planned for 3.3 anyway)
And one question: Is the gyro calibration only done on power up or also sometimes afterwards (i.e. during arming) ?
It's interesting because I want to start my small quad out of the hand and gyro calibration while arming wouldn't be good in that particular case.
Best regards,
lakeroe
I also made some testflights with 3.2.rc14. All worked very well, except for the mode position. I cant activate the mod position. hdop was well below2. Is it right, that this mod is deactivated in 3.2.-rc14?
I have not tried it with Vail of Hex but I have been throwing the X-250 frame around and it handles well at full throttle, hard turns in STAB, DRIFT and PODHLD. I am still getting my head around ACRO so I can't attest to how it goes flat out in ACRO mode.
I found that I could get the Stabilise Roll/Pitch P values a lot higher without oscillations when compared to earlier version. I am up at about 7.00 now when it used to be 3.5 to 4.0. I also seem to be able to get a wider range of PID's to work depending on how aggressive I want the setup to be. Even hard manual braking in gusty wind seemed OK. Hard cross wind turns were a bit hair raising at high speed but motors were smooth even when preventing the sudden urge to flip when caught by a gust in the middle of the turn.
I could probably increase the D terms for more short term correction but I have been finding that the low D term values work well for me at the moment.
I would love to know how it goes and if you still have the same issues. Good luck!
I believe others like the naze32 use a bit of code to reduce the PID loop above a certain throttle.
What size Mini? I have been flying a200size quad with 3.2 no problems.
All mine now on 3.2 looking forward to seeing how they run. Has any "mini quad" code made it in? Something to stop the oscillations that start at 70% throttle for example.