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
Randy,
Ok I've changed all instances of "relay.on()" and "relay.off()" to "relay.on(0)" and "relay.off(0)" in my UserCode file and it's compiling, but sadly it's coming in too big now at 278kb. Are there any other features I can choose to disable apart from the ones listed in APM_Config.h?
Disabling the sonar only dropped it by 4kb - I need another 16kb to get it under 258kb. Someone else mentioned something about disabling unused flight modes perhaps; is that possible? PS: Can you point me towards the mailing list perhaps? Thanks
Andre,
The dev list is drones-discuss@googlegroups.com.
And excuse me if I'm asking dumb questions but do I just send my concerns or questions to that address or how does it work?
Andre,
Yes, just send the issue to that email list. Your first post gets moderated so it won't appear immediately. Then I'm sure someone will answer. I can't guarantee the answer will be helpful but you'll likely get a response! The email list is completely open so all posts and replies can be seen publicly. I have it delivered to my email box but i think there's a web page to view replies as well.
Thanks, will draft
Andre,
It's a real challenge to get it to fit on the APM1. I've turned off sonar for the APM1 for -rc12. Best of luck. By the way, this discussion should probably move to the drones-discuss email list because it's really more of a dev question.
I add some custom code in order to use the relay to control my LEDs as a voltage indicator - hence I need to manually compile through Arduino each time...
I wish 3DR would do that! That's one thing a DJi Phantom has that makes great sense. Just from the lights UNDER the quad you can know the battery life and if you have a decent gps count.
I could upload AC3.2rc11 on my APM1.0 by Mission Planner.
The result is;
1) Mediatek GPS is not recogized
2) Altitude becomes crazy, climbs up more than 50,000m high:-(
It looks like GPS becomes crazy.
Unfortunately, I have removed compass for APM2.0.
-
138
-
139
-
140
-
141
-
142
of 373 Next