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
is this a Pixhawk only or will that be for APM 2.6 as well? that is good to hear!
It will be Pixhawk only, because 3.3 will not be published for APM.
DOH!!! thanks Rob!!
Not sure where i got this phobia of Channel 7 being bad, maybe a bad dream or something? but thanks for your response
Well, back 3-4 years ago, Ch8 was very very bad, as I believe it put the system into straight RC Pass-through. This was from the APM1 days, since it was originally designed as an airplane controller.
HA! thanks i knew i knew that from some where
I have a 650 quad with 12" props on 700kv motors that felt pretty smooth with stock settings. I ran the autotune on 3.2 and it became very very twitchy. I backed off RC feel and roll/pitch sensitivity but it still feels very twitchy. Any advice? Should I take RC feel lower? I can't lower roll/pitch anymore. Should I try autotune again?
I've included screenshots of my current pids and rc feel settings below.
Screen Shot 2015-01-21 at 2.27.03 PM.png
Screen Shot 2015-01-21 at 2.26.38 PM.png
My PID's were whatever the default settings are. I'd have to go searching to find them.
The copter feels twitchy in any mode, stabilize, alt hold, or position hold.
Considering that PIDS's are independand of radio used, here is a screen grab of my 3DR quad PIDS, after "Auto Tune"....
Really flies well :-)
Okay I give up. Pulling my hair out trying to figure out why my quad started toilet bowling and 'flying off' in all directions. I had it all dialed in flying nice but had a prop break in mid flight probably 20 meters up. Had a hard landing but nothing horrible. I get home and decide to upgrade to my shiny brand new taranis and X8R. I also upgraded to the last 3.2 but now I'm having problems. Should not have done so much at once now I'm not sure what the problem is. I simply cannot reliably get poshold to work well anymore it just seems twitchy and often just starts wandering off. It used to hold position within a couple meters easy. I re-did the calibration and compass calibration several times. I keep getting insane high reading on the internal compass.. I have no idea why. If somebody could look at this log and find any clues I'd really appreciate it. It is a 3Dr pixhawk. Ublox7 w/ compass. X8R receiver with Teensy.
279.BIN
-
4
-
5
-
6
-
7
-
8
of 262 Next