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
Randy, thanks for your reply.
I can't see how a little more than 1 axis is enough and I get very inconsistent results on my Pixhawk. Often no more than one of the white dots is completed. It seems like quite a few others are having the same issue so it would be great if Michael could lengthen out the time or a least give us the option to go back to the old method for comparison. I'll be interested in your test results, also if you have a CSG Neo 8 GPS unit could you test it. Unless I have a bad mag the calibration doesn't seem to work well with it and gives very large offsets (my big quad is grounded until I figure this out)
Hi Randy,
I took some flights after doing the compass calibration with the latest mission planner, when I ran the log analyzer the logs from the 3 fights all had a big fat FAIL next to compass. I can tell you with the auto-complete, I never get past 1-2 axis rotations.. I can't imagine it's enough..
I then re-did the compass calibration on my laptop which had a slightly older version of MP(1.3.10 i believe), where I did the compass dance until I had 800+ samples. 3 more flights today and no complaints when running the log analyzer.
I don't know if it's related, but I'm also getting an "IMU mismatch - fail (Mismatch: 1.52, WARN: 0.75, FAIL: 1.50)" now which I did not have before - yes I re-calibrated accel.
I read on this or the other 3.2 thread that the calibration is down to mission planner, which makes sense to me.
So you are saying even if I upgrade to AC3.2, I will still use the older style compass calibration till I upgrade to one of the latest Mission Planners.
Correct?
Hi,
I was flying today with my quad and had strange issue with RTL, as soon i switched into RTL the copter descent fast and landed (nothing broke but i cannot find the reason why this happend. (it is the second occurrence on this quad) tried afterwards few times but RTL was normal !!!)
could someone have a look at the attached log and tell me whats wrong ?
Thanks
Thomas
Thomas,
Logs??? Did you forget something??
upps.. file was too big and no error message :-(
2014-11-15 15-51-43.rar
nobody :-(
Thomas,
Sorry, I should have replied earlier. When I try to download your .rar file I get an access denied error. :(
Regards,
Nathaniel ~KD2DEY
ok, here the bin
2014-11-15 15-51-43.bin
-
47
-
48
-
49
-
50
-
51
of 373 Next