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
Hi devteam, I have this problem when trying "log analysis" it gives me this error message "Unknown mode in TestPitchRollCoupling: Hybrid"
Attached herewith said log.
2014-06-01 10-07-54.log
Ok well I don't have the logs then. Just the ones in the first post.
I'm using the latest stable but wondering if a change was made in the 3.2 beta regarding RTL sequence. Right now it turns and then rises. If you are flying at some speed away from home then that jerk can be pretty jarring when doing fpv. If it just rose first before turning that would give a softer warning.
Regarding RTL sequence, I think that should be selectable as a parameter or stay as it is - those of us who are not flying FPV need a clear sign that RTL has been invoked (either manually or automatically) and the rotation toward home serves that purpose well, while just a change in altitude (if any) is more ambiguous.
That might be a problem for uses that are not accustomed to orientation since it would face home and also might be some distance away if loss of signal caused the RTL. I think an altitude rise would be a clearer sign even if flying LOS because it wouldn't mess with the orientation right away and confuse the pilot. If you are flying LOS it can be difficult to see what way it's pointing.
Hi,
I have tested the 3.2 RC2 on my Tricopter and i have one issue.
When i arm and start the takeoff the tricopter wants to yaw around 45-90 degrees.I have never have this problem in the other old versions of Arducopter.
I can see that there been some changes in the yaw code. With Arducopter 3.1 i can move the servo when i have armed the copter with out throttle, but with 3.2 no servo movment when the throttle is down.
But when the copter is in the air everything work perfect.
2014-06-01 19-09-36.log
Thanks for your answer! And no, I am used to power my copter on the ground (which is for my usual test flights my small garden..not really level) For Betas, its an F450 a with battery on top, I don´t need to move it.
When I did these small "Hunt the warmup " tests, level was about correct, maybe 2° table tilt.
Unfortuately my flight logs exceed this forum max size . Here is one of my garden flights. (Hopefully one with EKF turned on)
http://www.file-upload.net/download-8987331/24.BIN.html
Here is a shorter flight I just did with shaking the copter a bit, standard start up , sadly bad HDOP at my shady place today. EKF turned on after start..
33.BIN
Hi Paul
I am usually not powering up within magnetic environment. I have to add: But since I use EKF with Ch 8 , my ACC/ Compass calibrations have been done without EKF.
Maybe its better to change this ??
Just noticed, that the effect is still visible (but only a very little bit. difference at 0.2-0.5°) after a few minutes. According to MP the quad lifts its back a little bit, when EKF is turned on. That explains the small movements in flight switching as well.
The last .bin file here http://www.file-upload.net/download-8986981/31.BIN.html
hope this is the right one.
I tried to attach the latest here as well
Thx
31.BIN
29.BIN
30.BIN
Hi Paul,
I did try this on my veranda with GPS 3-D Lock (warm start) and repeated it several times.
I did a HD video
https://www.youtube.com/watch?v=OmSb_gdmkWQ&feature=youtu.be
I am able to arm (which does not make a difference concerning the behavior), but am not sure where I should take the .bin file of. Directly of the sd card or via some MP command ?
It must be pretty short, because it disarms automatically after a few seconds. PH is rev. 2.4 Compass / ACC calibration has been repeated couple of times(for nothing) copter flies nice.
However, I wasn´t worried, because this effect settles down during my usual startup phase (Waiting anyways 3 minutes)
BR
PS: Just tried it with waiting with 15 seconds GPS 3D lock in advance (I did not do it in the video) Behavior is the same.
-
337
-
338
-
339
-
340
-
341
of 373 Next