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
http://diydrones.com/forum/topics/how-to-test-for-continuity-on-a-s...
1 out 6, ok I can live with that. I didn't test the motors for continuity or anything, but now have taken a crash course in electric motor inspection after finding a second defective motor after installing it. The short didn't show up during the pre-install stage while calibrating the ESC's.
No complaints here, KDE responded immediately and took care of me. Those I've talked to that have the 515 say it is a beast of a motor and very efficient (better flight time than ecalc estimated). I'm looking forward to hopefully having the copter in the air this coming weekend.
Being in the inspection business, I never assume an essential part of a machine is good, and should be inspected. It's in my DNA :)
Trust, but verify.....
Hello everyone,
Randy you look at my log to give me an opinion on my drone, if you can find the log of the improvements to do on the setting.
Sounds good to me but a good analysis on the log I might reveal optimal values.
the frame is a Reptile 450 carbon frame and arms are in Nylon.
fc VRμBrain 5.1
Ublox M8 GPS with compass
4x Sunnysky X2212 980KV 180W
M-30A 30A ESC SimonK
3s battery 5200 mA / h
total weight 1.4 Kg
regards
2014-10-04 15-43-22.rar
Milan,
It looks like a mechanical failure rather than a software bug. The reason is that the desired roll/pitch vs actual roll/pitch are tracking well and then suddenly they diverge. This is the classic symptom of a mechanical failure. The frame didn't respond as it should, the controller certainly didn't ask for the vehicle to tumble (if it had, the desired roll and pitch would have gone crazy). My guess is it was a failure of the front-right motor, ESC or propeller because the vehicle rolls right (+ve roll) and pitches forward (-ve pitch).
The ThrIn going to zero looks unrelated as it happens after the crash.
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 :)
got it, it worked great today, so thank you!!
-
93
-
94
-
95
-
96
-
97
of 262 Next