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 would appreciate a second opinion from another experienced forum member. Running 3.2RC14 on a large quad controlled by an X2. Motors stopped mid flight while flying aggressively. Nick spotted some Gyro saturation in the EKF data, among other discrepancies. Not convinced of just a brownout.
Not necessarily looking for an in depth response, just additional opinions. Had the same thing happen on a 3DR Pixhawk controller two weeks ago on a very similar setup, and same firmware.
I have been using this stuff for quite some time now, and I can typically account for most failures. The cause of the failure may seem rather obvious for some of our Pro log readers out there, but I am not seeing any certainties.
10.BIN
Hi,
Have you made sure you have a stable 5.2 volts or higher going to the board ? I had a real hard time once trying to figure out why my copter would just "Fall" out the the sky ..after flying quite well before hand .. it turned out to be the power to the board was low.. once I replaced the 5v Bec all was working as it should, no more random dropping out of the blue ..I too, could not any evidence of a brown out , but the volts were just low enough to cause the controller to stall.
Running 3.2 and was doing a video range test. Ended up going to the end of radio range and when it went into failsafe the quad flipped but recovered. I cant find anything so I am asking for help.
Thanks for any help/ advise
2500% seems pretty odd. I'm sure we can't have more than 100% so it seems like some kind of reporting error.
The CPU utilisation of AC3.2 is a bit higher than AC3.1.5 as we've added new features but even with AC3.1.5 it was still running at very close to 100% when flying in loiter mode. I wouldn't worry about it too much unless you're seeing issues in flight.
@Damain
got this answer from Randy 5-6 weeks ago
http://diydrones.com/xn/detail/705844:Comment:1800261
The high peak in load starts when code get a gps fix or amount sat (or both)
i have no spare time to investigate it, to busy at work.
Hello Randy
Many thanks for the excellent work for 3.2
please tell me where can I download the version 3.1.5.
in the MP is only 3.1.4
@Rainer,
Aha, MP isn't showing AC3.1.5. I've ping'd a note to Michael to add it.
Please note that 3.2 has been released http://diydrones.com/profiles/blogs/arducopter-3-2-released
Sorry, isn't a good idea, when a firm become stable, to close beta post? so we write in only one post and is easier for developers to follow owr questions from only one post and not for two with include the same matter ? for me this forum is great, as you prefer, I learn a lot, this only a little idea to help with a drop in the ocean, thank's very much appreciate this forum.
This topics is a discussion to feedback with dev team our problems but the most important things are updated and resume in the instructions section, now instructions are well up to date. I enjoy follow the discussions and learn a lot, the only thing it looks little confuse for newers, I suppose, two topics of the same thing..
-
19
-
20
-
21
-
22
-
23
of 262 Next