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

        • Developer

          Hi Arterm,

          It looks like you are flying a tri and the front left motor is having trouble. You can see the copter is taking that motor (motor 2) to maximum and the copter is leaning forward and left (towards motor 2). This is further backed up by the rate logs.

          So as far as I can see everything is doing what we expect from a motor/esc problem on motor 2.

          I am glad the damage wasn't too bad!!!

          • Oh yes, leonardt, I've actually figured out that I was looking on the wrong log when wrote the first post, again, my bad.
  • I have a quick question, probably simple.

    I took my Iris out last evening and did an AutoTune, and it's flying really well. For about 1 minute after I launch, I'm getting the red/yellow flashing LED. It seems to fly fine during this period, with nothing unpredictable happening. If I land, it shows I have a solid GPS lock. So I'm curious about what that means.

    Thanks,

    Kelly

    • Do you have a log? That'll tell you what the warning is.

      • I'm able to extract the log, but I get this when I try to load it in APM Planner to look at it:

        Error preparing inserttable: insert or replace into 'GRAW' (idx,"TimeMS","WkMS","Week","numSV","sv","cpMes","prMes","doMes","mesQI","cno","lli") values (?,?,?,?,?,?,?,?,?,?,?,?); Error is: table GRAW has no column named cpMes Unable to execute statement

        • If you get corrupted logs over mavlink then pop out the SD card and read directly onto your computer

          • I'm getting this as well... 

            Error preparing inserttable: insert or replace into 'GRAW' (idx,"TimeMS","WkMS","Week","numSV","sv","cpMes","prMes","doMes","mesQI","cno","lli") values (?,?,?,?,?,?,?,?,?,?,?,?); Error is: table GRAW has no column named cpMes Unable to execute statement

  • So if you're getting EKF variance messages you're pretty much done with 3.3 until it's fixed?  Reason I'm asking and I know it's beta, but the autotune works so well!  After autotune in 3.3, none of my big units have ever flown this well.  Before I didn't even bother with autotune and they were flying like crack addict squirrels lol!  But all the muti's are used for mapping.  If I'm half an hour into a scan and I get dropped out of Auto mode that would be lame.  I presume that's what going to happen with the EKF variance problem?  Can I autotune in 3.3 and copy to back to 3.21?  Or are the gains weighted differently.  Anyhow, great job on the autotune!

    • Developer

      Hi Shaun,

      Thanks, I am glad you are enjoying autotune!! rc6 is a little better still.

      The big difference between 3.2 and 3.3 is the yaw controller. I have added filtering in there to handle the physics of copters properly.

      I can't really answer your EKF question but you should be able to apply your roll and pitch autotune results to 3.2. There are a couple of changes that may make them a little less than perfect but I am not sure.

      • Hi Leonard! 

        I again tuned yaw on OCTA with the 18x6.5 props. Twice tuned, both times were these:
        1. aggr_tune =0.09: stab yaw= 5.209 , rate yaw p= 2.0, i= 0.2, d=0.0
        2. aggr_tune =0.07 stab yaw= 5.44, rate same pid.

        I low aggr tune and stab yaw is upper.

        When released rc6?

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @Jetsonhacks: And I helped with the course! JetBot, JetBot, happy little JetBot! JetBot ... GO! Meet the Jetson Specialists Inspiring a…
7 hours ago
DIY Robocars via Twitter
RT @a1k0n: Designed RPi + camera mounts + new bumper for the new car. Fits great on the car first try, except my longest camera cable doesn…
7 hours ago
gotham liked gotham's profile
yesterday
DIY Robocars via Twitter
RT @RoboticMasters: Monaco GP Circuit in the Donkey Sim (coming soon). Including buildings, tunnel and all! https://github.com/robotics-masters/sim-donkeycar-f1/tree/f1-tracks @diyr…
Wednesday
DIY Robocars via Twitter
RT @breadcentric: Here are the details of #AWSDeepRacer finals: https://blog.deepracing.io/2020/12/01/aws-deepracer-league-finals-2020-round-1-schedule/ #awsreinvent2020 #AWSreInvent https://t.co/ovqsjp8V…
Wednesday
DIY Robocars via Twitter
RT @breadcentric: #AWSDeepRacer League #awsreinvent2020 Open race is on Dec 1st - Dec 31st in three categories, 15 DeepRacer Evo (with LIDA…
Wednesday
DIY Robocars via Twitter
RT @a1k0n: @SmallpixelCar @diyrobocars It's just something that's easy to track with chroma keying. I ended up using different colors on th…
Monday
DIY Robocars via Twitter
Monday
DIY Robocars via Twitter
RT @TinkerGen_: "The Tinkergen MARK ($199) is my new favorite starter robocar. It’s got everything — computer vision, deep learning, sensor…
Nov 23
DIY Robocars via Twitter
Nov 23
DIY Robocars via Twitter
RT @roboton_io: Join our FREE Sumo Competition 🤖🏆 👉 https://roboton.io/ranking/vsc2020 #sumo #robot #edtech #competition #games4ed https://t.co/WOx…
Nov 16
DIY Drones via Twitter
First impressions of Tinkergen MARK robocar https://ift.tt/36IeZHc
Nov 16
DIY Robocars via Twitter
Our review of the @TinkerGen_ MARK robocar, which is the best on the market right now https://diyrobocars.com/2020/11/15/first-impressions-of-tinkergen-mark-robocar/ https://t.co/ENIlU5SfZ2
Nov 15
DIY Robocars via Twitter
RT @Ingmar_Stapel: I have now explained the OpenBot project in great detail on my blog with 12 articles step by step. I hope you enjoy read…
Nov 15
DIY Robocars via Twitter
RT @DAVGtech: This is a must attend. Click the link, follow link to read the story, sign up. #chaos2020 #digitalconnection #digitalworld ht…
Nov 15
DIY Robocars via Twitter
RT @a1k0n: Got a new chassis for outdoor races (hobbyking Quantum Vandal) but I totally didn't expect that it might cause problems for my g…
Nov 11
More…