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
I couldnt dind any information on my problem so far, so Ill ask here in the post.
Unfortunatly, my compass2 offsets remain at 0/0/0 and the external compass parameter at 0...
Is there a way to test if the ext. compass is even working?
Thanks a lot and regards
andreas
@sixtimesseven,
I guess you're using a Px4 or Pixhawk? Sounds very much like the compass isn't working. The compass-external flag should automatically be set when it detects the external compass.
hi randy
thanks for your answer! cable was broken but not completely ripped apart, discovered by testing trough the leads... :-)
Would it be possible to merge this pull request in rc6?
https://github.com/diydrones/ardupilot/pull/1150
It is a very handy/simple gimbal for fpv.
I'm afraid we took the branch for AC3.2 after -rc5 went out. We're already 2 months overdue on this release and although it's a small change, we have to draw the line somewhere. For example just this week there have been 2 other small changes that people also asked to be included... it's endless.
The delay between AC3.2 and AC3.3 won't be anything like the delay between AC3.1 and AC3.2 though.
Sorry, we just need to get this version released and pushed out so all can enjoy it.
Hi Randy,
Do you have any idea when you will give public release on the AC3.2
Missionplanner 1.3.8 still gives me the AC 3.1.5 as public.
I totally understand and appreciate the follow-up. (I work in the software business, so I know how it goes.) Hopefully we can get this, or even something better/more configurable, in for 3.3.
Thanks!
The requests like yours are many, and if we continue to be evaluated and put them in the code we will never release a new version, hope you understand.
The important thing is groped to fix all the bugs that may be present, then release.
Hi Marco and Randy, Thank you for the great work you are doing! I don't think this is the place to clutter with requests/suggestions for AC3.3 so where is the best forum/site to do so??
Yes please. The SSG is a very nice, simple, easy to make gimbal and this is a pretty minor code change. Can we please get an indication of the likelihood it will get in?
The KK and OC boards support it. It would be very nice to have it in AC 3.2. I thought I'd read somewhere that the PR had already been accepted, but it looks like that isn't the case.
Thanks!