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
Rainer das ist Thüringen :-)
Can anyone tell me why my heli isn't landing? I have a simple flight plan with Takeoff, a couple of splines and an RTL. The winds were gusting up to about 25kt and this was the first flight on 3.2rc12. I did the flight plan twice.
The first time it loitered at home for about a minute (should be 4 sec) before landing. The second time it loitered until I had to take the aircraft for batteries. I tried again later with the same results even in RTL mode.
When I looked at the NTUN. DPosX/Y are not recorded at line numbers 46K and 70k from reaching home to shutdown. CTUN DAlt has a steady alt.
Any clues?
5.BIN
Thanks. I've seen this problem too. I think it's a rounding problem. This issue usually shows itself on takeoff, though. It'll take off and climb to altitude and them stay there, unable to reach the impossibly small target, indefinitely.
It happened to me again, today; once out of the two flight plans I did. Can it be because of high winds? That when it shows.
Hello
The problem I had.
I deleted the SD card, and OK with RTL
Yeah, it seems to be working fine now.
Thanks, I'll try it.
Sorry, I haven't been answering too many reports or support questions in the past 3 days but I'll be back reviewing the build-up from tomorrow.
Please can you have look at my Question
-
110
-
111
-
112
-
113
-
114
of 373 Next