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
Thanks Randy. That's a lot different approach than what I think might be done. I was thinking maybe you could come up with an option for the board to remember the last known (good) settings for the gyros and go from there (kind of skipping the calibration for once). I always get confused as to why gyros (especially X and Y, it could be a different scenario for Z) have to be calibrated before each flight if the copter always rises from a level surface.
So I understand the Z gyro calibration as the copter's heading is different at each start up but it is almost always at level surface so why the need for X,Y gyro calibration each time?
Perhaps the answer may not be so straight forward...
Opps guess I missed that day / page thanks Doug!
Hi Randy,
I have just did test flight with AC3.2_RC14, AMP2.52 (Internal compass), Quad-X, F330. Supper stable loiter, perfect follow-me using Droidplanner 2. Attaching, telemetry & Flash logs.
This APM & Quad is different that the previous one on which there was yawing continuous.
Rest other functions are yet to be tested.
Arducopter 3.2_RC14, APM2.52, Quad-X, F330, Follow-me OK,Telemetry ...
Arducopter 3.2_RC14, APM2.52, Quad-X, F330, Follow-me OK, Flash Log...
F330 Quad-X frame with APM2.52, Arducopter 3.2_RC14.jpg
Hi Randy,
Troubles with rc14?
Prior to these hex flights with RC13 everything was working perfectly and without any changes other than loading RC14, I have experienced these issues..
#1 I am unable to activate Poshold in DP2, MP, nor AP2 while using flight modes per radio or Actions->set mode
#2 There has developed a oscillation in roll which is worse with throttle in Stab, Althold and loiter..
Thanks for the help..
2014-10-31 15-53-42.bin
2014-10-31 16-13-45.bin
Sandy,
The logs appear to be from AC3.1.5 flights so that's why PosHold wouldn't be available. Maybe you didn't push the "Beta Firmwares" link before uploading the firmware?
In any case, thanks for testing.
By the way, if anyone ever find that they need to do the parameter reset and it resolves problems I'd very much like to see the before and after log files (or at least the parameter files). I hear the reset thing resolves problems sometimes but it really shouldn't be necessary so I'd like to look into this.
Well nuts. I was having trouble with timeouts using a VM windows and MP and AP 2 with its crashes.. I maybe I went back to 3.1.5 momentarily to get something to load and never got back to 3.2 beta.. Anyway I shotgunned it with reset and succeeded in loading rc14. Now, all is well.. Thanks for looking and sorry for my confusion..
#2 fixed by defaulting params in parameter list", reloading 3.2rc14 and reloading latest auto tuned params.. I wish I had remembered to do reset before..
#1 Also, poshold is correctly announced with mode change..
Fixed my issue with selecting PosHold by downloading the latest beta of mission planner.
I've yet to test flight mine but I have also got the same issue regarding PosHold. If I set MP to any other flight mode from the drop down list in any of the 6 flight mode positions it's fine. No matter where I put PosHold (1-6) it refuses to go into PosHold and instead stays in the previous flight mode.
Can still see the channel pwm changing appropriately and works with any other flight mode just not PosHold.
I am, of course, assuming PosHold is available on APM 2.5 and not just a PixHawk option.
Hi,
today i have a flight with rc14 at my new Tarot 650. Stab work well, but loiter and Poshold have toilet bowling.
After update to rc14 i have done a compass and acel calibration and a compass mot.
Here is a small log from my last flight
Are there any other tarot 650 users here without problems?
Sven
tarot650_good_pid and ekf.param
2014-11-01 14-52-32.log.zip
-
71
-
72
-
73
-
74
-
75
of 373 Next