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
After flying rc2 for a while I finally gave up and went back to the old firmware. It has a large amount of bugs and needs lots of work. They need to take their time so don't push them.
.
Mike,
I fly 3.2RC2 on a custom 550 H Quad (pixhawk with EKF on) and a 550 hex (APM). I have flown mostly, hybrid, Auto, (including Auto with spline), Alt hold, and RTL.
I have had no issues and find that 3.2 flies better than any earlier code in both the APM and Pixhawk variants.
Specifically which bugs are you referring to?
Hi Mike,
Sorry to hear this! I am flying 3.2rc2 on a Y6 (pixhawk), a 450 sized quad(pixhawk), and a 250 size quad (APM26). They all fly amazingly - what issues are you having?
My only problem is the impossibility of downloading logs over mavlink from my APM..
Best,
Raph
I confirm this report in Mission Planner. I try and reinstall the MP in Windows 7 system and Hybrid mode is not there!
ATTENTION: MISSION PLANNER DEVELOPERS!
jay
Everyone is responsible for his actions... ;-)
Don't try beta versions on big machine until they are released in the final version.
has anyone tested it on APM1 boards? I'm going to load it and try it out on my old boards and see how it stacks up.
Hi, i´m using Arducopter libraries to make my own firmware to fly my copters, i dont know if its a bug only for the pixhawk, because i was using the optical flow sensor PX4Flow (via i2c ) in the APM and works with Arducopter 3.2 libraries, but now i have the pixhawk but i can´t make communication with the sensor, i used a logic analyzer to see the bus but in the pixhawk i only see the comunication with the compass, with apm i don't have problems.
Could be a problem only for the Pixhawk i2c libraries or the PX4 HAL in AC 3.2 ?.
Well this is certainly not good news for DRONE fliers, http://gizmodo.com/drones-are-now-banned-in-every-national-park-in-... Drones Are Now Banned in Every National Park In America
This is a similar story on ABC News which states they may be over reaching their authority sice now laws are in place to prevent Drones flying in parks http://abcnews.go.com/Politics/wireStory/govt-moves-ban-drones-400-...
-
222
-
223
-
224
-
225
-
226
of 262 Next