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
Similar behavior in the attached log, between 15th and 16th min. in my case copter went into the "alt hold" and started drifting with the wind and would not respond to any stick movements, until I put into stab mode, only after that I regained control.
2014-08-01 02-16-55.7z
Hi all,
there seems to be an "error" in Mission Planner (1.3.7) re Log Analysis of 3.2rc4 logs. I get the following error message: "Unknown mode in TestPitchRollCoupling: POSHOLD" and "Bad input file". Maybe MP 1.3.7 only searches for "Hybrid".
Best regards,
Thorsten
I only have the log file, I'll run another test by varying the parameters. then we'll see how it goes.
meanwhile, thanks
Great work dev team.
After a few more flights on rc4 i'm seeing error 16-2 & 16-0. I calibrated compass after upgrading to rc4.
What is this? here are logs
Raph,
That's the EKF Check (which also checks inertial nav in case you're not using EKF). It seems like we've set the checks to be too strict. Can you set the BAROGLTCH_DIST to 500 and the EKFCHECK_THRESH to 0.8?
Hope this helps.
Just noticed that when loaded with rc4, calibration procedure returns different numbers every time I try and some values differ a by 20-30 points. In comparison, when loaded with 3.1.5 I get more or less the same values every time I do calibration. Tried 2 different mag/gps combos so far... (if it makes any difference I use telemetry module when doing my calibrations)
same here - I tried 4 times and all 4 were different. No adverse affects (yet) during flight, though.
I think this is where the 16-2 comes from.... magnetometer is not getting calibrated correctly.... either MP fault or the way rc4 handles/provides data from mag to MP during calibration. so when the new EKFCHECK function catches discrepancies it throws an error, in addition if the discrepancies are large enough copter looses direction control.
here is a log where it seems error 17-1 switched me to land. At the time I thought it was a radio failsafe. I was not flying with EKF enabled.
-
275
-
276
-
277
-
278
-
279
of 373 Next