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
squilter suggested to check BRD_SAFETYENABLE. It is set to 1.
Upgrading to AC3.2 Is it possible to download logs using MAVlink on the APM planner ?
How ?
No, not from the APM. They removed the terminal window to save flash space.
The latest AC that have the terminal window was 3.1.5. After that no terminal window.
Nothing changed for Pixhawk since it has got plenty of flash memory.
I do that from my pixhawk not sure on a amp
yuvraj
Spoke too soon?? Major crash its wasted. All the $$ parts are okay though!!!! Fortunately it was just a quick wood made quad. I know I should be able to figure it out with drone share or the auto analysis on MP but I can't for the life of me get that to work not sure why. I had just turned around and was about to head home when it had a major twitch. After that it ignored my stick commands for the most part then it looked like it simply lost the ability to stay stable and fell 30-40 meters or so. I thought the battery went dead but A I had a RTL failsafe for that and B after looking at the log as far as I can tell that wasn't it. I think it was a mechanical failure but if anybody could take a look I'd sure love to know what happened.
153.BIN
According to your log you went into battery failsafe at 14850 (which is why your commands were ignored) then you got error messages from Baro, GPS, GPS failsafe, and radio. Looks like you ran out of battery capacity.
What did you look to graph to see the FS event?
oh I do see the RTL and I didn't do that. But how can you tell that from the log?
Richard,
I used Mission Planner. I opened up the flash log and then filtered the messages looking for ERR entries.
-
30
-
31
-
32
-
33
-
34
of 373 Next