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
Alexey,
No problem.
SIRF and NMEA are available by default on Pixhawk but we just couldn't fit it on the APM2 without dropping support for something else that seemed equally important.
So I won't be able to enable it by default for the next release. What I can do is sacrifice some other feature (like Sonar) and create a special binary for a limited number of frame types (like quad, tri, hexacopter and octacopter). I'd probably put those into the ardupilot.com/downloads area.
of course!
maximum 1-2% of APM users use sonar.
support of lots types GPS is more important!
Murdanny,
Can I ask what was the issue? In this log it appears the vehicle was in AltHold most of the time.
I see there were a number of EKF_CHECK warnings (warnings because the vehicle was in AltHold instead of a mode that required the horizontal position control). I'm unsure of the cause but I see very large discrepancies between DCM and EKF which is not a good sign. Also the ARMING_CHECK seems to have been disabled, which checks were causing it to refuse to arm?
One thing that I notice in the logs is the Rate Roll/Pitch P values are very high at 0.356. This may be leading to strange little twitches in the desired roll and pitch.
Murdanny,
Paul Riseborough had a look at the logs and he says that it was a combination of large gyro biases (probably caused by calibrating on a moving vehicle) which led to the EKF not believing that the compass was accurate. It then stopped using the compass completely and this led to a really bad heading estimate which caused the EKF check warnings.
We're wondering if perhaps the copter was being armed while on an steel deck of the boat? The EKF is a little different from DCM in that it records the inclination at startup and at arming. This means it can have problems if it's armed very near to large metal objects.
Murdanny,
So in the "23.bin" log the DCM and EKF stick together very well.
If the gyro calibration failure messages was appearing before the 3.bin flight then I strongly suspect that the boat was moving too much for it to calculate the gyro bias. This would make perfect sense. Instead of turning off all arming-checks, I'd recommend selecting "Skip INS". Better yet, leave them all on and just try and calibrate when the boat is more stable. Hopefully we will support boat takeoffs in AC3.3.
I'll also ask PaulR (EKF expert) to peek at your log.
i just update to RC12 from arducopter 3.1.5, but then on my mission planner, I cannot find the POSITION Hold mode, I reverted to 3.1.5 but still that flight mode is missing...I update again to arducopter 3.2rc 12 and still I cannot find the position hold/hybrid mode... can this be fixed? I fear that the sudden shift on the flight mode numbering could affect the succeeding flight modes.. and I often use hybrid or poshold.. hope you can help me with this. thanks!
Yes it seems that the issue is with the mission planner. I tried another laptop with misison planner and the PosHold mode is back.. thanks again!
Erwin,
It's less likely to be an arducopter firmware issue and more likely to be a mission planner issue. In particular your particular installation of mission planner does not have the latest parameters. Could you try Help >> Check For updates.
getting this strange tail dip , I see the spike that it registers however I cannot tell what is causing it. This craft I recently changed to the most recent RC12 and wondered if the behavior has been exhibited in a y6 prior
the log file is attached
39.BIN
I need a little help please understanding the Battery Failsafe, I have currently flown with 9.6 volts, reserve MAH 2600 for battery fail safe settings. i believe the mah setting is too high? but i only seem to be getting 10 minutes flight times where under 3.1.5, i got 18 minutes? the Battery is an 8000mah 3s Zippymax has power requirements changed for APM2.6 under RC12? as i understand it, Reserve MAH should be 20-30% which would be about 1600-2000 mah. 9.6 seems correct to leave each cell at 3.2 volts? or do i misunderstand something? thanks in advance
-
65
-
66
-
67
-
68
-
69
of 262 Next