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!

Views: 375199

Reply to This

Replies to This Discussion

dont switch so fast between modes.. make one decision ok i want this mode switch to it and stick with it for 10 seconds min.. then if you want to switch back go ahead but dont switch then switch to something else.. that might be your problem...

You say you didn't switch to Pos Hold? How are your Pwm values? Isn't that the problem

Things that I noticed: Your roll and des roll didn't track in that moment, idem Pitch, so I think that your controller didn't want to flip but, perhaps a mechanical failure did it, as James said, very fast switch modes, if you didn't do it check PWM mode values, and the third thing that I notice is that your vibs looks to high and some strange thing in clips but I'm not shure how to interpret them.

My 2 cents: check your motors/props (bearings, little shaft bolt, etc.)

As you discover the problem, you have to practice that pirouette, now you know that your copter can do it ;)

thanks but that's not the situation.

no i only use one single switch for three flight modes (2, 4 and 6 according to pwm values on my channel 5 switch)  so the switch is either high, low or middle and falls exactly on either 2,4 or 6 flight mode.  no overlap or use of other switches. I do have ch7 set up for auto tune but that is well separate from ch5 flight modes.

thanks Cala-  I actually went over the entire mechanics yeterday, tightened all frame points, motor mounts, prop nuts, etc, with typical blue locktight. then i wait at least 12hrs for the locktight to dry.

this morning before flight i went over the mechanics again, all 100% ship shape, and then post flight, all still 100% ship shape.  motors are new, balanced, lubed etc.

I have a good idea where my added vibration is coming from-  the RCTimer dome is attached to a deck, the deck holds the FC under the dome (hey isn't that a TV show? lol).  The deck is attached to the main frame via four rubber barrel mounts so it kind of floats. I think this lends itself to wind buffeting of the dome and it moving around independently of the frame with gusts. I'm going to revise how this assembly is attached and I'm pretty sure it will be a large improvement. when there is no wind gusts, there is not much of a vibe issue.

If you look at the length of the switching between modes, there is at least a minute or two between switching. I was testing drop in alt when going between poshold/althold/drift - and general drop in alt when rolling into the wind for sustained distances. I adjusted the throttle deadband for altitude hold modes and also my general throttle mid. 

Obviously there may be unexpected results if recklessly flipping modes back and forth within a second or two. Let's be realistic here guys :D

interesting - This is my first real long flight following the last auto tune session. however id say the auto tune results left it feeling more mushy than overly perky.  I'm actually going to roll back to the default values since they flew very well.

what was so weird (and cool), the flip was so spectacularly fast that it barely lost any altitude at all- i was only a few meters off the ground at the time.

I refer to this, looks des roll didn't flip, perhaps a motor jammed for a very little moment, I crashed my cuad with new chinesse motors, the little silly shaft bolt wasn't properly tight, the copter flip to one side and crash

 

I made a mistake during the release process yesterday and TradHeli has accidentally been upgrade to Copter-3.3.  The testing for TradHeli isn't complete so we will revert it to Copter-3.2.1 asap.  Any TradHeli users out there reading this should not upgrade to Copter-3.3.

Multicopter users should not be alarmed, this is a TradHeli specific warning.

Hi all Pos Hold vs Loiter fans,

Both use the same code when you are sitting there without touching the sticks. The difference happens when you start to move around.

Pos hold goes from Loiter on that axis to your stick angle and goes through a breaking procedure when you let go of the sticks.

Loiter has a almost perfectly smooth transition with no discontinuities. This lets you make very slow very precise changes in position. Loiter is also always controlling the position.

Most people won't notice the limitations because of the way they fly and their tendency to avoid the conditions that really let loiter shine. If I am landing in a bunch of trees with 40km/h winds gusting to 60km/h  in the presence of rotors and turbulence. There is only one mode to take the stress away.

Hi Randy,

THANK YOU for all the hard work !

I tried '3.3heli' yesterday, it didn't show any problems during 4 flights using Acro, Stabilize, AltHold and PosHold. I would change some defaults, like RATE_PIT_P=RATE_RLL_P * 3, RATE_PIT_D=RATE_RLL_D * 3, RATE_YAW_I = RATE_PIT_I and most important ACCEL_Z_P=0.5 never worked for me. Usually I use ACCEL_Z_P=0.3 to 0.4 therefore a default of ACCEL_Z_P=0.2 should be o.k.

Could you please add RATE_YAW_I and H_COLYAW to the TUNE options for channel 6. It would be nice to have reasonable heli limits in MP in the future as well.

Can you please tell me what version the '3.3 stable' really is ?

yeh i guess you could say it was an "in place roll". That spike in the graph is huge!

i was 20ft in front of the quad and it was at head level, so i had very good observation of the event. no motors stopped, one motor instantly sped up( "whoosh" sound) and the flip / roll resulted.  this was from starting at an althold hover, pushing a bit over half throttle, and rolling right 2/3rds stick into the wind. intention was to fly right into the wind and gain some altitude.

Reply to Discussion

RSS

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service