Warning #1: an issue has been found with Tower's Pause button which can cause the vehicle to fly to an old position if the vehicle has not sent a position update to Tower in some time.
Warning #2: Copter-3.3.2 fixes a bug found in Copter-3.3.1's desired climb rate initialisation which could lead to a sudden momentary drop when switching from Stabilize or Acro to AltHold, Loiter or PosHold.
Warning #3: Copter-3.3.2 fixes an issue found in Copter-3.3.1 which could lead to hard landings in RTL or AUTO if the WPNAV_SPEED_DN was set too high (i.e. >400 or 4m/s) and/or the WPNAV_ACCEL_Z was set too low (i.e. <100 or 1m/s/s).
Warning #4: a bug was found in Copter-3.3 which could cause a sudden crash if you abort a Take-off initiated from a ground station. Video description is here. The bug is fixed in Copter-3.3.1 so we recommend upgrading.
Note #1: AC3.3-rc8 corrected a long standing bug in the HDOP reporting. HDOP values will appear about 40% lower than previously but this does not actually mean the GPS position is better than before.
Note #2: if upgrading from AC3.2.1 the vehicle's accelerometer calibration needs to be done again.
Note #3: set SERIAL2_PROTOCOL to "3" and reboot the board to enable FrSky telemetry like in previous versions.
Note #4: the wiki will be updated over the next few weeks to explain how to use the new features
Copter-3.3.1 is available through the mission planner. The full list of changes vs AC3.2.1 can be see in the ReleaseNotes and below are the most recent changes since AC3.3.
Sadly this version (and all future versions) will not run on the APM2.x boards due to CPU speed, flash and RAM restrictions.
Changes from 3.3:
1) Bug fix to prevent potential crash if Follow-Me is used after an aborted takeoff
2) compiler upgraded to 4.9.3 (runs slightly faster than 4.7.2 which was used previously)
Changes from 3.3-rc11:
1) EKF recovers from pre-arm "Compass variance" failure if compasses are consistent
Changes from 3.3-rc10:
1) PreArm "Need 3D Fix" message replaced with detailed reason from EKF
Changes from 3.3-rc9
1) EKF improvements:
a) simpler optical flow takeoff check
2) Bug Fixes/Minor enhancements:
a) fix INS3_USE parameter eeprom location
b) fix SToRM32 serial protocol driver to work with recent versions
c) increase motor pwm->thrust conversion (aka MOT_THST_EXPO) to 0.65 (was 0.50)
d) Firmware version sent to GCS in AUTOPILOT_VERSION message
3) Safety:
a) pre-arm check of compass variance if arming in Loiter, PosHold, Guided
b) always check GPS before arming in Loiter (previously could be disabled if ARMING_CHECK=0)
c) sanity check locations received from GCS for follow-me, do-set-home, do-set-ROI
d) fix optical flow failsafe (was not always triggering LAND when optical flow failed)
e) failsafe RTL vs LAND decision based on hardcoded 5m from home check (previously used WPNAV_RADIUS parameter)
Thanks for your testing!
Replies
Also, here is some description: http://copter.ardupilot.com/wiki/configuration/ekf-inav-failsafe/
But, I did not fly, I just armed on ground and immediately I get error. This is weird.
Flashing red and yellow with rising tone: EKF or Inertial Nav failure - http://copter.ardupilot.com/wiki/common-autopilots/common-pixhawk-o...
This is ok, but WHY? Why I get error on startup?
Hello Randy!
Just kindly wanted to ask if you are developing some features for the epm from nicadrone? I just ordered one and I think it has a huge potential.
Thank you so much to all you developers who are working so hard, you truly amaze me everytime you release an update!
Have a nice day!
Autotune again
below the results of autotune - just R/P - with my Y6B with large props (15").
Stability / response is GREAT!
Especially fast descend, what was a really problem before, now works nearly perfect.
Great work!
2015-04-17 08-56-15.zip
I wonder if the Pixhawk 2(what is difference to Pix1?)Linux computers and gimbal control etc, from the Solo will also be available for DIY in a frame of our choice?
The spec's look very similar to the Pixhawk Firecape - I wonder if its an evolution of that?
https://erlerobotics.com/blog/product/pixhawk-fire-cape/
Maybe you can also add what was suggested by our fellow member here before, a 2 stage fail safe for the battery. Is it possible?
The scenario is when the low voltage is triggered, RTL will activate, however, if the UAV cannot make it home with its remaining battery, the second fail safe will activate which will cause the UAV to LAND.
Hopefully it can avoid causing damage to the UAV nor to anybody as it will not fall like a rockf from the sky since it will gradually land.
Thanks in advance!
It's on the to-do list here. Just a matter of a developer picking it up and implementing it but it's hard to make promises when that might happen.
Thanks. I'm happy with the thousands of features Arducopter has now. It just amazes me how much work you and the team have done. Huge congrats to you all. I hope that some day I get to buy you a beer or two or three...
Darrell,
Thanks for that.
Yes, the distance limited by remaining battery is a really great feature. I don't think it'll make AC3.3 but I'll go out on a ledge and say it'll very likely make AC3.4.