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
Please take a look at this log as well and the fact that there is a GPS dip each time the crash happens while baro-alt stays normal raises question
2014-10-03 17-12-34.log
Please help me to fix one problem...
GoPro video shows some vertical jumps while moving forward at alt-hold and poshold modes. Please tell me that parameters should I tune to correct this ?
And now for something COMPLETELY different....Is Spline Way Point working properly in RC10? ... and now we return to our regularly schedule programming :P
Thor,
Yes, it works. The only thing I'd say is that it does have a small twitch as it passes through a spline waypoints if the WPNAV_SPEED is set to 10m/s or higher (actually I'm not sure of the exact speed where it appears).
Today i am going out to test some things on my RC10 Release, is Spline_Waypoint Now working properly? I am wanting to test DO_SET_ROI with Spline Waypoints around a tree as a target.
Also going to try out Follow ME in Droidplanner but disappointed in the changes in the software that it appears almost hidden in the Auto options.
Also for any N00BS out there like me, i discovered that you cant find follow me until you are armed. once armed and before you select Auto to get to Follow ME, be aware my motors spun up unexpectedly, even tho my MOT_SPIN ARM is set to 0. Luckily i had my props off for safety.
i am guessing Droid Planner assumes you are already in the air when you click Auto. i am glad i took my props off while i was looking into this, i was in my house at the time because the cursed florida weather has left me grounded for a couple weeks. I am only mentioning it here because this is the most popular thread on Beta Arducopter.
Hopefully this will be fully communicated out to all and no one has to discover this like i did. this could have been disastrous for the less experienced.
I don't think you have to be in auto to start FM. I didn't I was just in loiter. re- took off... maybe your throttle wasn't low when you hit uto
Auto only appeared when the quad was armed in the 2.7 RC2 version of Droid planner, i dont want to hijack this thread, i just wanted to make sure thsi was noted some where on a popular thread, if i made the mistake of any kind others will too :)
must press takeoff before follow me.
got it, it worked great today, so thank you!!
-
142
-
143
-
144
-
145
-
146
of 373 Next