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
From the pictures it looks like it's neo 7 have received it?
I doesn't received it. I still wait. The pictures shown a NEO 7M (I think) with 5883 (printed on it). But I think, the description is correctly and only other pictures used...
Thanks for the clues on the FS_THR_VALUE.
I'm using a FrSky Taranis adn X8R receiver. My RC3_MIN is 982
The default FS_THR_VALUE was 975.
I had to set the FS_THR_VALUE to be 971 to stop the 'check FS_THR_VALUE' warnings. Note that when I set it to be 10 below RC3_MIN (972) I Still received the warning.
If FS_THR_VALUE must be 11 or more below RC3_IN, perhaps part of the Radio Calibration Routine should automatically set this value or provide a warning if the values are out of a valid range?
Hi Randy, I have been flying with APM2.6 & AC3.2RC5, since it was released and did almost several hundered flights and had never any crash due to firmware ( I had crashes due to my mistakes). Do you still recommend me to upgrade to AC3.2RC7 ? In 99.9% of my flights, landing was only by the firmware and not myself. Was its only my luck that I had no crash due to firmware ?
Rana,
Great to hear things have been going well. Yes, the problem with the landing check in -rc5 could affect anyone so I'd recommend upgrading to -rc9. The number of changes has been slowing down in the later release candidates so it's hard to imagine that you'd be worse off with the later versions. The only thing you may not appreciate is the stricter landing check especially if you land in AltHold, Loiter or PosHold a lot.
Thanks for the clarity Randy !
Well I tried my hand at Droid Planner/Follow Me and my Yaw behavior didnt respond as it does when flying a mission (Turn toward next way point) any suggestions i am all ears
https://www.youtube.com/watch?v=fIZwR1gapMI
Hi Thor, was the follow-me working with Andropilot ? I tested recently the beta of Andropilot and it did not work at all.
no @Rana it was not working for Andropilot at all for me either
Were you in "Guided" mode ?
-
197
-
198
-
199
-
200
-
201
of 373 Next