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
I had a hard landing yesterday after trying LAND mode for first time since AC3.3.1 , it went to land but it never slowed down the descent speed before touching down, literally slammed into the ground....I have my land speed set to 45cm/s.....
log attached, anyone that can help out? I have been able to replicate the issue and even sent land speed to 30cm/s and it doesnt seem to make any difference
2 log files attached...i think on the second one i aborted the landing by switching to stab
2015-11-05 11-45-25.bin
2015-11-05 11-48-05.bin
The copter does not slow to Land Speed until it believes it is 10m above Home Altitude. Your WPNAV_ACCEL_Z is set to 4.5 m/s. At this speed, it would hit the ground in 2.2 seconds. Your WPNAV_ACCEL_Z is set to 1.5 m/s/s. It would take 2.7 seconds to decelerate to 0.45m/s from 4.5 m/s. The copter did begin to slow and impacted the ground at about 2 m/s.
So it appears everything functioned as it was programmed to. I think the algorithm could be improved if it looked at the parameters to determine when it should begin to slow down, instead of using a 10m hard-coded setting.
Ooops, WPNAV_ACCEL_Z is set to 4.5m/s should be WPNAV_SPEED_DN = 4.5m/s
ok thanks yea I reduced WPNAV_SPEED_DN to 4.0m/s only and now it seems to be working ok, it slows down nicely at about 10meters and lands softly....thanks Rob
well I meant I should increase the accel_z and reduce the accel right?
thanks for looking into Rob!!...but it used to work just fine with these same parameters in 3.2.1, I dont recall crash landing like that....i do recall very well what you mention and it slowing down at 10m or so...but not now, at least visually, it doesnt seem to slow down at all...or doesnt try hard enough...
should I decrease the WPNAV parameters both?
Another problem is that it appears to have impacted the ground while it thought it was at 2m still. So obviously there was a height estimation error.
I would decreased the WPNAV_SPEED_DN, and increase the WPNAV_ACCEL_Z. If you used 250 and 250, you'd have 2.5 m/s and 2.5 m/s/s. At 2.5 m/s, you have 4 seconds from 10m to impact, but would only take 1 second to decelerate to zero.
You can balance those off however you like.
It is curious, when it passed 10m, it didn't even begin to try decelerating for 500 milliseconds (half a second). I wonder if that's due to a jerk limiter? By that point it was already at just 7.5m. So it had just 1.67 seconds to stop.
Hi
I got this result after autotune on a X8, flys OK but values out of range or?
After installing 3.3.1, I noticed a couple of PID values changed: RATE_RLL_IMAX & RATE_PIT_IMAX to 2000 from the earlier 1000 setting. Did the PID loops change such that what was 1000 on 3.2.1 needs to be 2000 to behave the same on 3.3.1?
-
93
-
94
-
95
-
96
-
97
of 558 Next