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
Thanks, got it, works great, I attached that log from 3.2 rc1 download but I assume its the same.
2014-05-12 18-54-40.log
I've downloaded the logs using APMplanner and it works.
Is there a wiki about what EFK is and does and the ins and outs?
http://planner.ardupilot.com/wiki/common-apm-navigation-extended-ka...
There's a lot Peter. Kindly use your friendly google search to find out.
Ok I just did my test this morning and I was impress, but first things first I'd like to thank all the dev team who patches this all together. Excellent job!
Here's my assessment:
1. EKF rocks! there's a minimal descends when flying around. Same thing happen when you fly in ALTHold, Hybrid and Stabilized.
2. Battery failsafe trigger ahead of my battery lipo.
3. There's a twitch when shifting from inav to ekf and vice versa.
4. The twitch in RTL is now solved!
Test pattern:
1. Arm in stabilize
2. Take-off
3. Switch to Althold
4. Switch to Loiter
5. Switch to Hybrid
6. Back to stabilize but this time on EKF then repeat 3 - 5.
Quad details:
1. Flight controller Pixhawk with 3DR uBlox GPS with Compass
2. emax 2216 810 kv motor with 10 x 5.5 properller
3. 30amps esc
4. I tried different mAh lipo batteries. 2200, 2700 & 5000 all in 3s.
5. 450mm frame
I'll post the log later.
Hi Randy,
I noticed there's an EV = 28 in my log which was not define ardupilotwiki.
Jay,
In the wiki, it's written
"EV: an event number. The full list of possible events can be found in defines.h but the most common are:"
And in the define.h, you have the definition :
#define DATA_NOT_LANDED 28thanks Julien. I suggest this will be put in wiki.
here's my flight log #4
2014-05-13 05-01-38.zip
-
365
-
366
-
367
-
368
-
369
of 373 Next