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 seems i'm getting closer to the issue, it seems to be very important to use the square spots 10x10 on the backside of the pixhawk for the foam. since i changed the position of the foam autotune seems to work properly.
The new PID now are pretty good, but did not test outside yet.
D 0.0105
I 0.190
P 0.190
STB 11.62
Hey Guys,
I just loaded ac 3.2 with mission planner 1.1.12 and it seems I have some issues. I almost had 3 flyaways today while in loiter. I just finished this big bird and have been having some ESC issues with it as well. I do not suspect the esc issues have much, if anything to do with the flyaways, but I thought I would include that as well. The vibration levels seem to be very good with the exception of a couple blips here and there coming from the gimbal. Which i suspect may have something to do with it.
I am using a 1200mm hex with avroto 3515's, 16*5.4 tmotor props, maytech opto 60a esc's(overkill i know) and 2 10000mah batteries. It flew very well with ac 3.15 would love an experts insight into my logs as to why I had these flyaways.
Hdop and sat counts are great throughout the flight.
Here is the log files
2014-11-15 15-44-17.zip
2014-11-15 15-43-11.tlog
Test: Compass = PASS - mag_field interference within limits (9.92%)
Max mag field length (559.10) > recommended (550.00)
A compass interference perhaps?
wouldnt compass interference only translate into yaw motion? it pitched over to 30 degrees and started flying away.
I think it is very possible for it to fly away if the mag. direction is way off. As Cala mentioned, it may think it is going north but going some other direction (ex. south if it is 180 degrees off).
That 30-degree pitch isn't odd if the copter is trying to reposition but going the opposite direction due to mag. interference...
Wait expert answers but if it is desoriented i suppose it probably fly away, It doesn't know where north is.
I can't seem to get compass calibration to work properly on either my APM 2.6 with a NEO 7 or my Pixhawk with a CSG NEO 8. I'm not sure if it's 3.2, Mission Planner or me. Both quads have calibrated without difficulty before loading 3.2 and doing the recent Mission Planner update. It says it is complete long before it did before and before I have a chance to complete all the axis. On the Pixhawk the offsets are - compass 1/ -104 -131 554, compass 2/ -25 25 6 so it is mainly compass 1 although the offsets for both are inconsistent. There is nothing different about the location where I am calibrating. Any ideas would be greatly appreciated.
I'm pulling hair out on this one. I've gone back to my APM and it didn't prematurely end the calibration this time. It let me continue and then tell it I was done. With the Pixhawk I have removed anything that could interfere, loaded plane to reset everything and then copter 3.15 and the compass calibration still said "done" on its own with only 1 1/2 axis done and the offsets are still similar to above. I reloaded 3.2 and still the same thing. Both compasses are sending data to Mission Planner but the calibration seems to end prematurely and leave huge and inconsistent offsets. I'm now reasonably sure it's not 3.2 so this is probably not the place for this but if anyone has any ideas please let me know and in the meantime I'll try to find a more appropriate forum.
Same thing here - pixhawk running the latest 3.2 and the calibration stops maybe 15-20 seconds in and gives me my offsets. What is concerning is that every time I do the compass calibration, the offsets are quite different. I am not getting any compass errors, and it does seem like the orientation on the map is OK.
Is this the new standard behavior for compass calibration? I thought it would run until I stopped it.
Thanks Ralph,
At least I'm not totally crazy. :) In my case the offsets do throw the actual directions off big time. It may have something to do with the mag in the CSG gps. I did have it working on earlier versions of Mission Planner. Sure wish someone in the know would address this.
-
45
-
46
-
47
-
48
-
49
of 373 Next