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 #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)
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.
Fellow droners, i had been testing number of quad and hexa frames using AC3.1.3. the results are fantastic, they all fly superbly stable even in stabilize mode (No loiter). of course the credit goes to a superb code of AC3.1.3. a second reason for super performances is something an individual flyer has to do himself. that is balancing the props. whatever brand it is and irrespective of being nylon/carbon, must balance the props using a good quality magnetic type of balancer. use cyno glue on tip to add weight. scrub after drying using a knife if overweight. you would be surprised to see the difference in performance after balancing the props. i discovered this after two years of flying quads.
hi does anyone know the changes 3.1.4 introduces ? Can't find changelog anywhere .
@Marco yesterday you mentioned for me to Launch My Quad & check in Mission Planner for my Throttle rate while the aircraft maintained a stable Hover. I have searched fro that information and cant find it. is there a video for this, or a link describing it? i think its video worthy since it seems like the ideal way to ascertain that THR_MID number. if you cant make a video about i can, just looking for the steps to produce that information. thanks in advance
Prob best to look at the following site:
Basically you get throttle readings by plotting ThrOut from CTUN logs in mission planner & then average the value (by eye) that corresponds to your hovering period by checking the y axis and push that value into THR_MID. Better explained in the above link (sorry if this is not what you were looking for).
@Matt i appreciate the help but i am aware of that method, but Marco mentioned a seemingly more accurate way of getting THR_MID yesterday that i want to explore further, seeing as i am not being successful with the Logs. but thanks again!
If i'm updating firmware in APM do i have to do all the calibration again (ACC, gyro, compass, setup PID etc)?
i'm wondering the same thing .
Easy, takeoff and tries to keep in hovering perfectly your quad for more than 20 seconds (20 is better than 10) in "Stabilize" mode, lands and do a refresh parameter, go to "Full Parameter List", read the value of "TRIM_THROTTLE" and save it in "THR_MID", takeoff and see if it's ok.
HAHA i KNEW that TRIM_THROTTLE was good for something!!! thanks @Marco, thats very Helpful!!
Hi Sergos No you do not have to redo the set up again .. Unless its a major update that requires it.
Hi Thomas ..No you do not have to redo the set up again .. Unless its a major update that requires it.
AC-3.1.4-rc1 is now the official version available through the Mission Planner.
There are no changes for APM1 and APM2 users, but for PX4/Pixhawk users there are these bug fixes:
1. Bug Fix for Pixhawk/PX4 NuttX I2C memory corruption when errors are found on I2C bus
2. Fat system file corruption bug that could lead to corrupt log files