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

      • Randy could you at least take a look at this issue:

        https://github.com/diydrones/ardupilot/issues/2426

        Seems very serious. I'm sure there will be a lot of people using the Storm32 controller with 3.3 since there is native support for it to some extent, but it would be sad to have a lot of people with burned out gimbal motors or broken cameras from that bug :(

        • I also would appreciate a working SToRM32 controller with pixhawk via serial! 

  • Tarot 680 pro frame. 

    13x5.5 cf

    blheli damped light esc

    3.3 RC7 only pitch and roll autotune.

    I can ear motor vibrations from the resulting autotune and hexa is twitchy around middle stick, mostly on the roll. I reduced resulting values 15% afterwards. The high vibs seam to go away (D to high?? or P ??  ) but the middle stick movement gives twitchy result. 

    My main problem is around middle stick. The very beginning of stick input and the copter is not smooth. On higher angles it does look locked and stable, just not on the very beginning of stick input. Best I can describe is wobbles. Slow and little roll or pitch inputs and the hexa wobbles just a bit. 

    Any suggestions ? Lower autotune_aggr form 0.1 ? higher than 0.1 ? reduce all autotune values by 25 % ? Does anyone see anything wrong on my log ?

     -> Autotune Log  -/p>

    Thank you

    • Developer

      Hi Adolfo,

      Drop your RC_Feel to 25 and see if that fixes the problem. If it does put your pids back to the autotuned numbers and see how it feels.

      • Tomorrow I'll give it a try but the auto tune values made the motors vibrate. What should I do about that? Any aggr value I should try??
        • Developer

          Hi Adolfo,

          Sorry missed that. Yeh, try the RC Feel and if you want to try autotune again use aggr of 0.05. Your tune looked very nice so I think you can handle a finer tune. We set it to 0.1 so it will handle the higher vibration and flex a lot of frames use. But I personally use 0.05 on most of my frames.

          • Very glad I saw this post. I was getting very frustrated with my Hoverthings modified FPV-Pro. @ 0.1 I was getting very high numbers all around (Stab R - 13~ Stab P 16~), etc... it was a very angry bee in the air and fpv and gopro vid showed it, gave the effect of a video camera in a paint shaker at anything over hover speed. 0.05 dropped the values tremendously (Stab R - 5.35~ Stab P 5.38~), etc... etc... super smooth now even cruising in 20mph gusts. I may have to call in sick tomorrow to enjoy some fpv flying.

          • Can I autotune with RC feel already set to 25? If the end result still makes it vibrate should I take autotune values and make them 25% smaller?
            • Developer

              Hi Adolfo

              RC feel doesn't have any effect on Autotune. So there is no problems setting it before doing an autotune with aggr set to 0.05.

              If the end result still vibrate then you will need to manually adjust the tune by dropping the values until it goes away.

  • Leonard,
    could you please take a look on attached autotune file, seems the PID's are getting really high.
    The PID's were pretty high since first autotune, for STB pitch about 15-16.
    Recently for maintanance just optimized some things and replaced a motor. After re-run Autotune i'm getting STB Pitch on the max of 18.

    Can't add the file which seems to be to big 25mb, how can i upload ?

    Dropbox link

    https://www.dropbox.com/s/uuu9rnb3hgxylbo/2015-07-05%2021-24-42.zip...


    Do you think this is realistic ? I fired 1-2 lipos with it and its flying pretty good.

    Dropbox - Error
    Dropbox is a free service that lets you bring your photos, docs, and videos anywhere and share them easily. Never email yourself a file again!
This reply was deleted.

Activity

DIY Robocars via Twitter
RT @Heavy02011: #VirtualRaceLeague: @DIYRobocars Race #14 - #ParkingLotNerds join us January 15th for #AutonomousRacing #RoboRace ⁦@DAVGtec…
2 hours ago
DIY Robocars via Twitter
RT @chr1sa: And after that came our races, 50 in all. This battle between these two Russians was the best we've ever seen -- incredible fig…
2 hours ago
DIY Robocars via Twitter
RT @chr1sa: Before our @DIYRobocars virtual race this weekend, we had a presentation from the team that won the Indy Autonomous Challenge i…
2 hours ago
DIY Drones via Twitter
Dec 12, 2021
DIY Robocars via Twitter
Dec 12, 2021
DIY Robocars via Twitter
RT @chr1sa: Just a week to go before our next @DIYRobocars race at @circuitlaunch, complete with famous Brazilian BBQ. It's free, fun for k…
Dec 4, 2021
DIY Robocars via Twitter
How to use the new @donkey_car graphical UI to edit driving data for better training https://www.youtube.com/watch?v=J5-zHNeNebQ
Nov 28, 2021
DIY Robocars via Twitter
RT @SmallpixelCar: Wrote a program to find the light positions at @circuitlaunch. Here is the hypothesis of the light locations updating ba…
Nov 26, 2021
DIY Robocars via Twitter
RT @SmallpixelCar: Broke my @HokuyoUsa Lidar today. Luckily the non-cone localization, based on @a1k0n LightSLAM idea, works. It will help…
Nov 25, 2021
DIY Robocars via Twitter
@gclue_akira CC @NVIDIAEmbedded
Nov 23, 2021
DIY Robocars via Twitter
RT @luxonis: OAK-D PoE Autonomous Vehicle (Courtesy of zonyl in our Discord: https://discord.gg/EPsZHkg9Nx) https://t.co/PNDewvJdrb
Nov 23, 2021
DIY Robocars via Twitter
RT @f1tenth: It is getting dark and rainy on the F1TENTH racetrack in the @LGSVLSimulator. Testing out the new flood lights for the racetra…
Nov 23, 2021
DIY Robocars via Twitter
RT @JoeSpeeds: Live Now! Alex of @IndyAChallenge winning @TU_Muenchen team talking about their racing strategy and open source @OpenRobotic…
Nov 20, 2021
DIY Robocars via Twitter
RT @DAVGtech: Live NOW! Alexander Wischnewski of Indy Autonomous Challenge winning TUM team talking racing @diyrobocars @Heavy02011 @Ottawa…
Nov 20, 2021
DIY Robocars via Twitter
Incredible training performance with Donkeycar https://www.youtube.com/watch?v=9yy7ASttw04
Nov 9, 2021
DIY Robocars via Twitter
RT @JoeSpeeds: Sat Nov 6 Virtual DonkeyCar (and other cars, too) Race. So bring any car? @diyrobocars @IndyAChallenge https://t.co/nZQTff5…
Oct 31, 2021
More…