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:
1) Enhancements:
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.
Replies
I think you missed the point. He is saying with the throttle at 984 above and a failsafe of 975 he gets a failsafe warning message when he tries to arm the copter. He is in failsafe and needs to turn it off.
I got this when I remapped my RC channels. I see yours are not remapped but maybe has something to do with radio calibration.
Radio calibration with remapped channels is definitely fubared. I have a fix, but its taking me some time to test.
Any idea's? I can't believe I'm the only one with this issue. I'm basically grounded until I get it fixed.
In the code of 3.2.1 I see that of_loiter mode is implemented, but in the master branch not. Does this work and have someone tried it already ?
Dries,
I wouldn't recommend using OF_LOITER in AC3.2.1. I don't think it works very well and if it does it only works on an APM2.x with an old mouse-style sensor. it certainly won't work with Pixhawk and PX4Flow. AC3.3 will include support for the PX4Flow with Pixhawk but it's used in Loiter (and other modes) so no special OF_LOITER mode is required anymore.
Randy,
I uploaded PX3.3 on my pixhawk. Is it possible to test the PX4FLOW without GPS ? You said optical flow is used in normal loiter mode, but i cant arm in loiter mode without GPS (i dont want to use GPS). Can you help me a little further trying to get my hexa hold position with the PX4FLOW ?
Thanks in advance !!!
Randy,
Thank you very much ! Do you have any idea when AC3.3 will be available ? Or do you know if there is already some code available ?
Firmware.diydrones.com
Is it correct that i have to take the latest version ? http://firmware.diydrones.com/Copter/latest/PX4-hexa/ ?
And can I also find the source code somewhere ? Thank you already !
if that's what you want.. There are also older builds available as well as current stable and beta. You should notice that those are development builds and can have bugs.
Source is here https://github.com/diydrones/