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
Cool! Thanks!
With RC10, my OSD will not display data unless I unplug it and plug it back with each flight. Is this related to RC10 or something else??
Pedals2Paddles,
I don't think this is related to -rc10 (or even AC3.2 vs AC3.1.5). It's more likely related to the SR0_ and SR1_ parameters. These are all zero by default meaning that GCS or MInimOSD must tell AC what update it wants for all the data streaming out of the telemetry link. Perhaps your MinimOSD is not waiting until the board has compeltely booted before making that request. A work-around would be to set the update rates manually using the mission planner. The parameters can be foudn in the Advanced and Full Parameter Lists.
Log from 3.2 rc12 on Tarot 650 quad with following specs:
APM 2.5 (no external mag)
SunnySky 4110S-25 340KV motors
HK Multistar 45amp ESC running SimonK firmware
Props - 16x5.5 CF
Battery: 6S 5000mAh Zi[ppy Lipo
Performed well; did not test any Auto or mission functions, just Stab, AltHld, PHold, and Land.
Would not let me upload log file as it is too large...
Link to video: http://youtu.be/Q7g8a6goDIg
can share minimosd firmware? small font
Jim, I really enjoyed it. Did you tune parameters through auto-tune or you used default parameters ?
Jim great to hear about your flight with RC12,Try to upload the telemetry log file or the flash log file. Don't worry about the size, it should be less than 10MB.
Added log file zipped...
2014-10-10 10-04-36.zip
-
122
-
123
-
124
-
125
-
126
of 373 Next