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
Just got my new 3DR pixhawk and temp quad set up. This time I used a Futaba receiver and set up throttle fail safe [ should have done this before]. Setting up the pixhawk was easy as usual. But the new thing for me was the throttle failsafe. I was astonished to see no jump, twice, drop in altitude, or anything when I shut of my TX!!! Absolutely incredibly smooth. It just slowly rolled over and proceeded to go back to home [ 3 meters away in my back yard ] then it lanced itself and disarmed. WOW NICE!!! It was a fresh install of beta so guess that's rc10. Unless EKF is on by default it wasn't on. Very impressed with pos hold again. Alt hold worked great too. Stabilize seemed fine. I was using the stock 3DR ublox which I've not a had any surprises with I think I might just keep using it instead of the M8.
Richard,
Great, thanks for the feedback. We spent some time on AC3.2 getting rid of twitches in various places so perhaps that's what's helped. There are still some (i.e. spline when waypoint speed is set high) but there are fewer at least.
I had a great time running 3.2 on my Trad heli again today. I got Follow me to work (nice). I also got POS Hold to work(I don't like it as much as loiter). I'm posting a video of a Spline flight path. I think I need to stretch my plans out a little. I think the heli gets a little wound up on the tight turns. But it's so much better than no splines.
I'll never go back to 3.1.
http://youtu.be/RQHwxTbaKe8
Great work. Seems very violent on the accel stops. What Freq. are you running on the video. It seems to have a lot of interference.
Looking good. I too and haveing great luck with 3.2. Have you tried using the Kalman Filter?
Joe
Fellow Traditional Heli Guy...
This machine was originally configured for speed. 90mph is the fastest I've recorded. I'm tuning it down to be a gentler machine. But, still, I like it's aggressive nature.
She'll behave if I tune it down,slow it down, and give her some room to maneuver.
I'm using a 5.8g tx. It's really the rx that has a problem. I'm getting a bad picture at 30 ft sometimes.
EKF? not yet. I'm wondering how it will work.
Thanks for posting the video. I have a 500 size Heli begging for an APM transplant :)
BTW, was with that APM or Pixhawk ?
Martin
Pixhawk. It's really nice for this settup.
Ray, thanks for testing out the TradHeli especially cuz we have less users on that frame type!
Telemetry is logging twice, not all the time , do we need that much logging
Sort on RAD
2014-08-30 08-25-31.bin
Richard,
Thanks for the report. It seems the RADIO dataflash log message is written whenever the vehicle answers a request from the ground station for the status (MAVLINK_MSG_ID_RADIO or MAVLINK_MSG_ID_RADIO_STATUS). That's a bit inconsistent with how we write all other dataflash messages so I'm not overly happy with that but putting that aside, it means in the short-term it's likely caused by the ground station asking for both messages. I guess you're using the Mission Planner?
-
106
-
107
-
108
-
109
-
110
of 262 Next