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)
Hi, Rich B
Now, I got the same issue "Initialising APM" with pixhawk, How did you solve it? can you help me?
I think the issue is that the board is not in a good state immediately after uploading the firmware. It's best (perhaps required) to power off/on the board after a firmware update.
I think your board is fine.
I thought EKF smoothing will be included in this release. :(
After upgrading to 3.2rc7, I'm not able to choose "Position Hold" flight mode in Mission Planner -> Flight Modes - no fm value on the combo box list. Full parameters page also does not show this flight mode in options column.
Missed PosHold after upgrading to rc7???
Strange... I checked - PosHold is in place.
After reinstallation of MP from *.msi package, I have "Hybrid" mode on the list. Should it not be "PosHold"?
Hybrid / PosHold - the same.
I know that, but I thought that changing naming convention from Hybrid to PosHold is permanent.
It's because the .msi package is not updated with each mission planner release. So when installing from the .msi you actually end up with an older version of mission planner. If the Help screen's "Check for Updates" button is pushed it should update to the latest and PosHold will reappear.