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)

Views: 305686

Reply to This

Replies to This Discussion

Update Mavlink bad packets:

unchecking ECC box on both modules did the job!! Now the wireless connection is outstanding!

thanks for the update! that is a bit disheartening though.. ECC is recommended in the documentation - correct?

https://code.google.com/p/ardupilot-mega/wiki/3DRadio?wl=en

yes it's recommended..

I also noticed a high frequency blinking of the red LED of Pixhawk telemetry. There was no connection established to PC. That means something sends a lot of data into space. I'm not sure if that happened with 3.1.5. but it didn't with APM.

There should only be heartbeat blinking..

Hi Christian, Thanks.  i really don't know because warning #2 says "if two spline waypoints are created one on top of the other". In my case, the waypoints are far from each other. Anyway, they might be related and hopefully fixed in rc3.

I also noticed faster connection of the copter to Andropilot(Android tablet) with ECC disabled.

I agree. Unfortunately my PixHawk won't work with anything earlier than 3.2. It freezes up with any copter versions of 3.1.x so I'm anxiously waiting for 3.2 to be released. Until then I'm stuck doing short test flights.

Is there any schedule or estimated date for 3.2 to be released? When is RC3 coming? :)

This is meant to be an encouragement, not a complaint! ;)

My PixHawk works fine with 3.1.5 as long as I don't use waypoints with 0 Lat and 0 Lon. I don't think your freezing is a 3.1.5 problem.

Raph, i tried today checking the ECC box but increasing the air speed to 128. it works! Log download is easy and also the wireless connection.

Willy thanks so much - i will be making this change soon. I'm always hesitant since i have to change the setting on a bunch of telem radios.

thx willy, so you doubled the speed which was halved by ECC.

So now its the only question, in which of the 2 cases the range is not badly decreased...

Will try flying with a) ECC untick,airspeed at 64 and b)enable ECC,airspeed at 128 then compare the range.

Reply to Discussion

RSS

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service