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
Hello Randy
is reset to armed yaw available in the next version?
for beginners this is a great help.
regards
Rainer
Rainer,
Ok, we've talked about it on the dev team and we're thinking about adding it back only for Loiter & PosHold modes but leaving it off for Stabilize and AltHold. The idea being that we should keep Stabilize and AltHold simple because they're fallbacks for the other flight modes. How do people feel about that approach?
(randy braces himself for the negative reaction)
All of the modes please. This for me is fallback in itself - to regain a sense of orientation if anything goes wrong in any mode.
Don't have much time to think about whether the mode I happen to be in at the moment is possibly enabled for the good old "show me your a...." switch :-)
Sam,
How about just enabling simple mode on a ch7/ch8 switch instead?
I'm using this trick and work great for me ;)
Point taken. Last time I looked I got the impression I would have to somehow select/declare all modes I would like to have simple mode active, so I used reset-to-armed-yaw - seemed less complicated then. I will re-visit GUI/docs and reorganize my setup - just that old habits die hard
Ok, thanks for the vote to have it in. which flight modes do you like to use it in? stabilize, althold, loiter, poshold?
On APM Planner v2.0.14 on the Standard Params page there is Channel 7 option(CH7_OPT) that I have set to EKF but when I go to Extended Tuning page, it says "do nothing". Full Parameter List shows it has value of 20 so I know it's getting set but probably APM Planner doesn't have the full list of options on the Extended Tuning page.
steve,
I think this is an APM planner issue. Any chance you could raise this in the APM Planner issues list?
Done! https://github.com/diydrones/apm_planner/issues/462
-
143
-
144
-
145
-
146
-
147
of 262 Next