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
I had the same problem today, I install the beta Mplanner and solve it
I could be wrong, but updating mission planner "shouldn't" fix my situation. In my case the RC Transmitter is commanding the flight mode "POSITION" via CH 5 pwm, and the flight controller (HKPilot 2.7) is not responding to that command. The Mission Planner (or Droidplanner) is just the messenger, and it's just verifying that my mode change is being ignored. As a second try, i used a mavlink command (via Mission Planner /Actions) to change the flight controller its also being ignored. But all other flight modes change as expected. So i suspect this is a 3.2 RC 12 issue??
Ill try to reload the firmware and try to replicate what i did.
From what i know there is no "Position" mode anymore, it was replaced by PosHold. Position mode will be ignored totally in 3.2!
If you are on RC12 then you MUST use the Beta Mission Planner by clicking update beta in the help tab of mission planner.
At the top of your window it should say "Mission Planner 1.3.10 Build 1.1.5397.23504" or later.
The build number is important since there are multiple 1.3.10 versions, older one not having PosHold.
This is a Mission Planner issue, not APM :)
I upgraded Mission Planner, then relooked at the RC7 & 3.1.5 Quads, POSHOLD was returned. thanks for the help, i had previously used and seen POSHOLD in RC7 as well as RC 10, was suprised by it being missing on the RC7 FW. but its all good now
Thanks Johnex, That cleared things up with the flight modes- Im back to POSHOLD and POSITION is no longer available.
I am still unable to download logs in the CLI with Mission Planner 1.3.10.4 build 1.1.5399.10754. Can anyone else confirm this?
https://github.com/diydrones/ardupilot/blob/master/ArduCopter/Relea...
Did I miss something? I thought POSITION has changed to PosHold (with quite different behaviour) since 3.2.
Thanks i will get the Beta as well i guess Unless mission Planner gets upgraded sooner
+1
pixhawk only, apm on rc12 was ok
-
77
-
78
-
79
-
80
-
81
of 262 Next