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
Ok, thanks for the vote to have it in. which flight modes do you like to use it in? stabilize, althold, loiter, poshold?
On APM Planner v2.0.14 on the Standard Params page there is Channel 7 option(CH7_OPT) that I have set to EKF but when I go to Extended Tuning page, it says "do nothing". Full Parameter List shows it has value of 20 so I know it's getting set but probably APM Planner doesn't have the full list of options on the Extended Tuning page.
steve,
I think this is an APM planner issue. Any chance you could raise this in the APM Planner issues list?
Done! https://github.com/diydrones/apm_planner/issues/462
I just finished installing an external GPS/Mag and here it says http://copter.ardupilot.com/wiki/ac_compasssetupupadvanced/#Compass...
Compass_mot_x y and z should be less than 30%. The range for the parameter is -1000 - 1000 so would -300 - 300 be acceptable or has the range changed? I'm getting 2.8 - 1.7 and -2.2 for xyz. I don't have it installed on a pedestal yet so I'm surprised these values are so low or are they not?
Steve,
For compass mot, are you using throttle based or current based? I wouldn't recommend using the throttle approach. If you're doing current based then the final param values are "compass offsets per amp" so they tend to be very low. The best way to judge if the interference is acceptable is to look for that final "% interference" message that's displayed. If it's below 30% then the vehicle should be ok.
I'm using the APM power module so am assuming it's doing a compass_mot using current but is that a right assumption? I didn't see any way to choose current over throttle during the test. I didn't notice the final % at the end of the test. I just pressed start and after the test pressed OK and it gave me the readings. I will try again and look for the %.
Steve,
No necessarily correct. On the MP's Initial Setup >> Optional Hardware >> Battery monitor page you can enable the voltage and current monitoring. Once that's done the compassmot should use the current for the calibration. It'll actually print "CURRENT" in the little box in the MP just as the calibration starts.
Thanks Randy. I did have that selected and watch my current consumption on my OSD so it's working.
Been flying on 3.1.5 with no problems. Wanted to try follow me so I am trying 3.2 and cannot seem to get my quad in the air.
Should I need to recalibrate my escs? I have tried multiple times unsuccessfully. I can get pixhawk to arm but motors will not spin. Is the calibration procedure different from 3.1.5 because I cannot seem to get into the escs?
When I switch back to 3.1.5 it makes me recalibrate escs but it works from then on as it always had.
Using rctimer 30a escs
-
210
-
211
-
212
-
213
-
214
of 373 Next