After months of testing AC3.1 is finally available in the Mission Planner and GitHub.
Warning #1: If the vehicle is left landed (but armed) while in AltHold or Loiter mode for more than a few seconds, the vehicle may suddenly jump into the air the moment the pilot raises the throttle above zero. The reason is the baro altitude may fall while the vehicle is sitting on the ground. In AC3.2 this bug is fixed because we reset the target before take-off.
Warning #2: Motors will spin (slowly) by default as soon as the copter is armed! You can switch this feature off by setting the MOT_SPIN_ARMED parameter to zero.
Warning #3: if you see "Bad Gyro" on the HUD then you may have a blown 3.3V regulator. See this thread for details.
Warning #4: if you use a sonar set the SONAR_GAIN parameter to 0.8 or lower
Warning #5: Trad Heli users should now connect their main rotor ESC to APM's RC8 output
Warning #6: Trad Heli BUG causes loss of collective control in ACRO mode if swash type set to flybarred (i.e. not flybarless). Will be fixed in AC3.2.
The major improvements over AC3.0.1 are (full list here):
1. Pixhawk support (Tridge & PX4 development team)
2. Autotune of Roll and Pitch gains (Leonard/Randy)
3. Drift mode (Jason)
4. Improved Acro (Rob/Leonard) and new Sport mode (Leonard)
5. Arming, Take-off, Land in Loiter or AltHold
6. TradHeli improvements (Rob) including:
a) support for direct drive tail rotors
b) smoother ramp-up of main rotor
c) reduced collective for better control in stabilize mode (STAB_COL_MIN, STAB_COL_MAX params)
7. Support for SingleCopter (Bill King)
8. Performance improvements resolve AltHold troubles for Hexa & Octacopters
9. Safety Improvements:
a) GPS Glitch detection (Randy)
b) Motors spin when armed (Jonathan Challinger)
c) crash detector shuts off motors if copter flipped for 2secs
d) batt failsafe option to RTL instead of LAND, gps failsafe option to trigger AltHold instead of Land
e) more pre-arm checks of inertial nav speed,
10. Bug fixes:
a) optical flow working again (although performance is still not great because not integrated with inertial navigation)
b) ROI working (use DO_SET_ROI command)
How to upgrade:
Click on the MissionPlanner's Initial Setup >> Install Firmware screen. The version numbers should appear as "ArduCopter-3.1", then click the appropriate frame icon and it should upgrade as per usual.
Special thanks to Marco and the many beta testers on the AC3.0.1 thread who put their copters at risk during the testing of this new version and uncovered many problems so that you don't have to! Here are some of their videos: loiter in wind, patio sonar, autotune, autotune2, roi, beach, acro, vrbrain, tricopter, train spotting, radio failsafe, the tree, double loiter
If you haven't seen it recently, please check out the ArduCopter wiki.
Feel free to post comments below and we're going to use the new APM Forum for support issues so please post your support requests there.
Replies
Hi, thanks to the team of developers, now we have 3.1.3!
I really did not experience any issues since ancient 3.0-rc5 and dozens of flighs but there is a flyway video below I simply can not share. Enjoy.
https://www.youtube.com/watch?v=l83T7ToRn1w
I wonder how DJI people felt when they watched that video...LOL...
Any official word yet on why were are getting the 0,0,0 compass calibration message only in 1.2.99 version of Mission Planner with firmware 3.1.3? Went back to 1.2.98 (or earlier) and get a proper compass calibration message.
Hi Andy ,
My APM 2.6 and UBlox Neo 6M GPS shows wrong heading , even after calibration. (North is ok , but East shows West..)
Is this related to latest version ? I did try the calibration and god 0,-1,0 results
Go to Mission Planner > Initial Setup > Mandatory Hardware > Compass > Orientation (assuming your at rotation none) hit Roll 180 and Yaw 180 combo. Should fix it.
If you already have roll 180 hit Rotation none yaw 180,
Then redo calibration
I owe you a beer mate :)
Can you recommend me which flight modes to configure for first timer ?
I went on Stabilize / Loiter / RTL. Should I have anything else also ?
Hi Eran,
Brandon is correct but 0,-1,0 are not realistic numbers and seem to be another example of the 1.2.99 mission planner weirdness.
I just did a full reset of my APM, did the compass calibration worked fine with 1.2.99 anyone know why some people are getting 0 0 0 ? Try re installing? Or use APM planner
I downgrade mp 1.2.94 and did calibration. Loiter perfect
Will it work to load saved parameters from 3.1.2 into 3.1.3? anything need to be changed or re-calibrated?