Developer

Copter-3.3 beta testing

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!

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • Hi,

    Great work, thank you! I have a problem but I am not really sure that it is down to the firmware (3.3 -rc1), it was flying well with 3.2.1 but I made a few changes; ESC (New X rotors), Foam, GPS (Ublox 7) at the same time as upgrading. I know the sensible thing is to revert and try again but it started to rain!

    The copter (TBS Disco with carbon arms PIXHAWK and 390KV motors), flies superbly in stabilise but when I switch to any other mode it goes nuts! Up,Down take your pick it does it and fast!!! ;-) Switch back to Stab and harmony is restored.

    Really appreciate some help with this - Cheers! 

    2015-04-16 19-24-23.log

    • Developer

      Mike,

      It looks like really high vibration when the throttle goes above 40% so I'm guess a mechanical issue.  In the graph below it's especially obvious at the beginning with the vibration maxing at +3G and -4G.

      3702560521?profile=original

      • That's great Randy thank you! I changed the foam under the FC - I think it's to firm. Will double check the props too, assumed they will be good as they are pre-balanced T-Motors. 

        Thanks again, looking forward to the final release of 3.3 - Cheers

  • Why do I get "EKF variance" immediately after arming (trying to arm in stabilize mode)? Led start to blink yellow-red. Even did not fly, just arming on the ground. Is it normal? Small log attached.

    2015-04-16 23-25-37 2.bin

    • Any ideas?

  • Re: b) increased accelerometer range from 8G to 16G to reduce chance of climb due to high vibrations (requires accel calibration)

    I have a 250 which had some serious altitude stability issues on 3.2.   Those problems seem to have disappeared after installing 3.3.

    Thanks!

    • Awesome!

      I also have a quad that was a disaster, and is much much better on 3.3.

      • I will have to try it on my 250 quad

        Thanks

  • Did three auto tunes so far, reduced the suggested atc_accel parameters and the other parameter suggested in this thread( can't remember the name right now, but the one that was 0.5 instead of 0.1) each auto tune, was way too unstable, machine would take off, and wobble violently. last auto tune with the accel parms lowered was the least wobbly. Turned down stab rates by 1/3 and they are now closer to previous settings I had that flew well,( except in stronger winds) 

    So far 3.3 seems more solid in position hold.

    Besides the auto tune problems, I can't get loiter and throttle pids to change. I change them, click write...and it reverts back.  

    • Developer

      Hi Nate892, 

      The next release candidate should fix your problem. Sorry about the hassle!!

This reply was deleted.

Activity