Warning #1: PX4/Pixhawk users upgrading from AC3.1.5 (or earlier) may need to re-do their compass and accelerometer calibration because AC3.2 also uses the backup compass and accels. Pre-arm checks have been added to ensure this has been done.
Warning #2: on the APM2.x the logs must be downloaded using MAVlink instead of the terminal.
AC3.2-rc14 is now available for BetaTesters through the mission planner’s Beta Firmwares link. The full release notes can be found in ReleaseNotes.txt and changes from -rc13 can be seen below.
Feel free to raise issues found during testing on this discussion or in the new support section in the APM Forum.
It’s a big release with “the onion” restructure and a bunch of new features (including these 57 closed items) so we need to re-test almost everything including all flight modes, all mission commands and all the new features. Marco and I will be maintaining (and adding to) this testing list. Issues reported will first be checked by Jonathan, Marco and I and then confirmed bugs/issues will be put on the github issues list (and then hopefully fixed).
Thanks especially to the beta testers who put their copters at risk testing each release. Enjoy!
Changes from 3.2-rc13
1) Safety Features:
a) fail to arm if second gyro calibration fails (can be disabled with ARMING_CHECK)
2) Bug fixes:
a) DCM-check to require one continuous second of bad heading before triggering LAND
b) I2C bug that could lead to Pixhawk freezing up if I2C bus is noisy
c) reset DCM and EKF gyro bias estimates after gyro calibration (DCM heading could drift after takeoff due to sudden change in gyro values)
d) use primary GPS for LED status (instead of always using first GPS)
Replies
Hi Henri, Can you pls upload your latest successful flight tested telemetry log file of 800mm multirotor based on Arducopter 3.2_RC7, APM2.6 there ?
@Rana: Sorry I did upload the "founded .log" file and it is now on the droneshare.
Very nice soft and only 9:21 minutes but really enjoyable as no "undocumented features" showed up!
Cheers
Henri
Great Henri !
@Rana: Already erased, sorry. When everything goes well I tend to "clean" asap..
Henri, can u pls share your parameters file of 800mm quad with AC3.2RC7 & APM2.6
Maiden report:
AC3.2 rc7, hexacopter, pixhawk,gps neo7
1) no auto tune, default pid. awesome
2) tested, stab,althold,loiter,poshold, auto awesom
3) maybe gps glitch see video 0:40 .anyone can analyse it?
attached 2 flight log. video is flight log no 1and glitch during loiter, auto mode is flight log no 2, and also glitch during auto landing.
thanks for great project:
short video:
2014-09-06 12-15-58.log
2014-09-06 12-26-00.log
Ultrojo,
Thanks for the report. I had a look at the logs and the twitch doesn't appear to be caused by a GPS glitch (I think GPS glitches would normally last a lot longer by the way). It appears to be an uncommanded roll and pitch which means that the attitude controller didn't ask for the twitch which points towards a mechanical issue. I checked the RCOUT to see if any motors were very low at that time (motors going very low could temporarily stop is THR_MIN is too low) but they don't so I'm very unsure what the issue is except that I suspect the ESCs.
Thanks Randy for your comments.
maybe uncommanded roll or pitch due to my esc.
i used connecter for esc. not solder it. maybe that caused twitch.
I had a crash with rc6 today. I was flying in poshold and my quad just droped out of the sky like a brick. I have had about 10 really nice flights prior to this crash. How could I tell if this was the land detector bug? I am pretty new to reading logs so any direction would be greatly appreciated.
https://www.dropbox.com/s/9crrqtpn2eckz5z/2014-09-06%2015-00-20.log...
John,
Yes, I'm afraid your vehicle was the 4th victim of the "false positive on landing check issue" which has just been resolved in -rc7. I'm very sorry for your crash. Like Francis OBrien's logs I've looked at yours and confirmed that the two additional checks in -rc7 would have prevented the false positive.
-
216
-
217
-
218
-
219
-
220
of 373 Next