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 Randy - sorry to pile on but a major concern of mine is the full throttle bug with althold modes during take off. Has this issue been identified and eliminated (tested) ? I'd hate to be stuck in a tree again :D
Steve,
Based on your previous posts, it looks like you're a new user to arducopter. That's great of course but you should definitely stick with the nice and stable official firmware which is AC3.1.5.
The First Time setup wiki is here which might help you get started.
Alternatively if you have a dataflash log I can have a look at your flyaway issue.
3.2RC4, fly very well.
Thank you for development staff.
https://vimeo.com/103391672
That is smooth. I was going to wait for a final 3.2, but I'm finding it hard to resist flashing this.
Anyone been flying rc2, 3, or 4 with a Y6B and APM 2.6? How is it?
Is there a list of changes from the latest stable to the 3.2rc4?
Thanks Javier!
Tried to find more information about this: 9) Red Balloon Popper support (Randy, Leonard):
What is that?
Steve: That's a pretty sweet project for AVC where Randy hooked up a periphial computer (I believe a BeagleBoneBlack) with a camera that looked for the red ballons, and when it found them, steered ArduCopter toward it to pop it. Check this out: https://www.youtube.com/watch?v=yRmXwRqPesY
Need some help with this one please...
- Load 3.1.5 (no cal, no wizard, nothing but software load...). Apply LiPo power, all ESC's beep: beeep-beeep-beeep - beep-beep - followed by single ongoing beep, all motors wiggle. Arms and flies normally.
- Load 3.2-rc4 (no cal, no wizard, nothing but software load...). Apply LiPo power, 1 ESC beeps: beeep-beeep-beeep - beep-beep - followed by single ongoing beep, only that motors wiggles. Arms but only one motor turns. Disconnect / reconnect LiPo, 4 ESC do beeep-beeep-beeep (no double beep, no ongoing beep), but that's it... Arms but motors will not turn.
- Reload 3.1.5, all operations normal, flies perfectly with no cal/wizard, etc...
How can software loads affect the ESC in this manner?
Alas, I have done both many times, but thank you! I have calibrated the ESC, per both the "all at once" and the "individual" procedures prior to flying with 3.1.5, and they worked normally, and it flies perfectly. I did not think they need to be re-calibrated just because I load 3.2-rc3 or -rc4, so I then load 3.2-rc3 or -rc4 and they do not work. I then reload 3.1.5, without ESC re-calibration, and they work. If I re-calibrate ESC with 3.2-rc3 or -rc4 loaded, by either method, the calibration appears to work, but the strange motor behavior is still there when I connect LiPo and try to fly. I am fairly sure the ESC re-calibration worked when -rc3 or -rc4 were loaded because I can reload 3.1.5 without re-calibration after trying (and failing with) -rc3 or -rc4 and the ESC behave normally and it flies perfectly. The ESC simply do not work properly when -rc3 or rc4 are loaded.
-
186
-
187
-
188
-
189
-
190
of 262 Next