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
Got the same result without Mission Planner
I use Mission Planner 1.3.10 Build 1.1.5369.11976
Esteban,
It's definitely vibration levels. Jonathan Challinger has recently added a new automated test of IMU variations between the two accelerometers on the Pixhawk and it seems quite good at catching the problems. It claims a 1.13 m/s/s difference between the two IMUs.
today I try again rc10 with strong wind, just impressed, first time that I can fly with this conditions in stabilize mode for the moment., Land is working well again.
Has PosHold been renamed to Position between RC9 and RC 10 ? I had been using flight mode 16 "Pos Hold" and now it seems to no longer exist ??
Sam,
Any chance you've re-installed the mission planner from the .msi? if "yes" then you've got an old version of the mission planner. I think on the "Help" screen in MP there's a "check for updates" button that should hopefully get it up to a more recent version.
Quite funny, it was actually the "Check for updates" button that messed up my installation of MP 1.3.10
Updated to 1.3.10.1 (Beta) and all is good again ;-)
Dan,
There seems to be a problem with the GPS messages (or the processing of the GPS messages). Below are two pics one that shows good GPS message timing (Column C shows the timing and all messages are 200ms apart = 0.2 seconds = 5hz).
In your log however the timing on the messages is not increasing properly at all. Which GPS are you using and is there anything else unusual about the GPS's connection to the APM?
Thomas,
I've made some fixes (here and here) which should ensure there's no "I-term build-up" before take-off. This will go out with -rc11. I'm almost confident that the next release candidate will be the last one.
Adolfo,
Thanks for testing it out. I haven't completed my analysis but part of the problem is a bad tune and/or a bad center of gravity on the frame. Is there a camera on the front perhaps that makes the vehicle nose heavy?
-
107
-
108
-
109
-
110
-
111
of 262 Next