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 Mike,
There really shouldn't be any need to re-do the calibration from 3.1.5 to 3.2. No offense to Javier but as far as I know, there should be no changes to the pwm being output with each version.
I wonder if it's possible that it's tripping over an arming check. If you connect it to the mission planner and then arm it (without the battery connected) does it arm?
Yes, just checked again, it always arms via MP without LiPo, no warning messages.
I have since been able to get it to arm and fly twice (out of 50 tries) by some combination of holding down the safety switch for a period of time when and after connecting the LiPo. It does not seem to be deterministic, or I have not found the correct pattern. I can tell when it will work because of the beeps. No beeps, no work, 2 beeps, it flies!
When it flies it is amazing, hats off to the Dev's!
Hi Mike, i am just curious... when you fly do you first connect to the Mission Planner via telemetry? Simple because, i think if the copter doesn't arm there should be message in the Mission Planner showing why arm can not be done....ex: bad compass health, magfield, etc.
hi randy, nice to see you back on the blog. can u add some instructions on using external LEDs on pixhawk. i cover my pixhawk with depron canopy to avoid heating becasue of direct sunlight on pixhawk. (sun is very hot here 45 deg celsius) so external LEDs become a necessity on pixhawk.
Ravi,
I think the best thing to do is attach an external I2C led. It's on the wiki here. It's in the 3dr store here.
I've been away for a few days updating the wiki.
Sonar info: http://copter.ardupilot.com/wiki/common-rangefinder-landingpage/
EKF/Inav check info: http://copter.ardupilot.com/wiki/ekf-inav-failsafe/
dual GPS: http://copter.ardupilot.com/wiki/common-installing-3dr-ublox-gps-co...
Pixhawk LEDs and tones: http://copter.ardupilot.com/wiki/common-apm-board-leds/#PixhawkPX4_...
Spline waypoints: http://copter.ardupilot.com/wiki/mission-command-list/#Spline_Waypoint
FrSky telemetry & RFD900 radio: http://copter.ardupilot.com/wiki/common-telemetry-landingpage/
PosHold flight mode: http://copter.ardupilot.com/wiki/poshold-mode/
A few other places were updated as well. If anyone finds info that's not updated, please ping me, thanks!
Now that this is all done I'm back on pushing towards -rc5 which should hopefully be out before the weekend.
Nice work Randy
It would be nice to have last update date on each page (maybe also created date).
With this dates , editors and readers can see wish page that has old info and need a update.
Does anyone happen to use this frame with their APM? It's a very solid frame with the clean section isolated with 8 dampers with 4200 battery on the clean section.
http://flyingcinema.com/cinetank.html
I've tried the AutoTune but it stops after 5 or so tries on roll. Maybe AutoTune doesn't like the dampening?
If anyone is using this frame can they post their rate PIDs?
Also does it matter what your PIDs are set to prior to tuning? Is that a starting off point for the tuning? I noticed when I had the rate P set higher, it would be very twitchy but the AutoTune went on longer before canceling out.
-
187
-
188
-
189
-
190
-
191
of 262 Next