ArduCopter 3.2.1-rc2 (release candidate #2) has completed beta testing and has been released as the official version available through the mission planner and other ground stations.
Changes from AC3.2 are listed below and in the ReleaseNotes:
a) reduced twitch when passing Spline waypoints
b) Faster disarm after landing in Auto, Land, RTL
c) Pixhawk LED turns green before arming only after GPS HDOP falls below 2.3 (only in flight modes requiring GPS)
2) Safety Features:
a) Add desired descent rate check to reduce chance of false-positive on landing check
b) improved MPU6k health monitoring and re-configuration in case of in-flight failure
c) Rally point distance check reduced to 300m (reduces chance of RTL to far away forgotten Rally point)
d) auto-disarm if vehicle is landed for 15seconds even in Auto, Guided, RTL, Circle
e) fence breach while vehicle is landed causes vehicle to disarm (previously did RTL)
3) Bug Fixes:
a) Check flight mode even when arming from GCS (previously it was possible to arm in RTL mode if arming was initiated from GCS)
b) Send vehicle target destination in RTL, Guided (allows GCS to show where vehicle is flying to in these modes)
c) PosHold wind compensation fix
d) prevent infinite loop with do-jump commands pointing at each other
e) pixhawk memory corruption fix when connecting via USB
f) vehicle stops at fence's alt limit in Loiter, AltHold, PosHold (as it did in AC3.1.5)
g) protect against multiple arming messages from GCS causing gyro calibratoin failure
Thanks to Raph for the video. This is actually a video from AC3.2 until we have one specific to AC3.2.1.
I am still seeing throttle/landing problems in 3.2.1.
First problem is it takes a really long time to determine that it's landed. I have broken countless props, trying to disarm when landed only to have the thing flip over because it thinks I am applying yaw. The most reliable thing I can do is switch to stabilize, throttle at zero and just wait for it to automatically disarm. To my mind yaw applied at zero throttle should have NO effect on the prop speed. It should only be looked at as a disarming action. Right now there is effectively no way to disarm at all while the copter thinks it hasn't landed (which is often). This seems worse with 3.2.1 than 3.2.
Second problem is that the min spin speed for the props only works on the first arming. When you land at zero throttle or rearm the props do not spin. This may be something to do with my Spektrum TX as I have noticed this also with my channel remapping patch.
I will probably raise bugs for these two unless someone can tell me they are expected.
I've been a bit absent for the last 2 weeks because Tridge and I were in SanFran attending the Embedded Linux Conference and meeting with 3DR people in the Berkley office.Back in Japan now and we've apparently resolved the altitude issue that were holding up AC3.3-rc1 so hopefully AC3.3-rc1 will be out by this weekend (I've said that before but this time it should really happen).
Sure... the old, I had to go to CA then to Japan excuse. Nice try Randy. lol Can't wait for 3.3 rc1. I'm sure you mentioned to everyone the imperative need to resolve 'boat calibration' issue.... :] yea yea I know it's not high on the list I get it. But hopefully it's on the radar though. LOTS of great follow me's in my boat and my kids on the jet skis. How cool is that!
Is AC3.3-rc1 only for Pixhawk? Regards.
Yes, only for Pixhawk and other fast CPU boards (Flymaple, PX4-v1, VRBrain, Linux, etc).
That's kinda cruel. I just bought APM 2.6 original hardware and now it's that I'm stuck with drifting height problem and incomplete EKF filter (which is in fact not working properly in this firmware, but it takes valuable ROM size, because lack of which development on APM stopped).
Maybe you can at least fix altitude things and make 3.2.2?
What should I do now? Send my APM to store and ask for moneyback because hardware is unusable for me? Man, that just destroys all positive image APM boards. :(
I think Rob Lefebvre can help look into the specific issues some users are having with AC3.2.1 on the thread opened for that issue. We went through months and months of testing including many APM2 users but if it turns out to be a firmware issue that can be fixed we can release a 3.2.2.
I've also sent a note to the 3DR guys responsible for the store and asked them to add a note that recommends people purchase the Pixhawk instead of the APM2.6.
Now I know why I broke 3 props of my quad at landing on battery failure.
I like the "old" way of landing/disarming better :-)
Randy,how its possible that some people with clone Pixhawk have preloaded 3.3 version already on them?!direct from china store not master trunk...
most likely they got it from the dev repo
Well, that's not good. AC3.3-dev has not gone through beta testing yet so no guarantees it will work well.
I attempted to autotune today.
The left-right part (the first half) was normal. During the forward-backward (second half) phase and in particular during the forward movement, I noticed that right after each oscillation the copter was adding a substantial amount of yaw towards the right. Wind wasn't strong enough to be a factor and was changing direction quite rapidly.
Is it supposed to do so? I've never seen it when I've done autotune in the past, but I've changed motors and propellers since (to very well balanced KDE motors and 15 inch props). It flies fine otherwise. Autotune terminated and I saved the new PIDs, which are ok (not perfect but definitely better than the defaults).