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 Leonard,

        I hope you're referring to the first log I posted and not the second one.  I thought that one was good.  Let me know if I'm wrong!

        • Developer

          Hi Shaun,

          Yep, that is much better!!! Sorry I didn't see the rest of that thread and came in late.

    • Developer

      Shaun,

      Using the new VIBE message it looks like the vibes are a bit high including clipping.  I haven't looked super deeply into the logs to see if it's something else but this alone could explain the behaviour.3702587477?profile=original

      • So to any of those Pixhack users, the internal damping is not so good.  Here's the difference after adding a cheap Hobby King damper.  Looks good enough?  No clipping.  Z axis is below 30 now instead of around 100.

        HK.JPG

        2015-08-16 15-45-16.bin

        • Developer

          Yes, much better.  I hope the word gets out to Pixhack users and back to the manufacturer that the internal vibe dampening is not sufficient on many frames.  Maybe with the improved Vibe reporting in AC3.3 the manufacturer can do a better job on a future revision.

          • I'll give the group a heads up.  I had posted it was pretty good previously so I should let them know.  Retesting everything now.  My hex version of this frame isn't so good either (Pixhawk with 3DR foam), no clipping though.  I've got 5 more of those mounts and 4 more copters to test : )  Thanks again for your help.

        • 3702795466?profile=originalThat's all it took. $2 from Hobby King lol.  Thanks Randy!

      • So we don't use the pull down menu "vibration" anymore?  Doing that my vibes look good lol.  This looks really bad.  Over 80m/ss and clipping looks bad (don't really know what to look for in the clipping graph).  I presume clipping shouldn't keep escalating like that.  Wow, my missions are usually 30 to 40 min, I'm thinking I'll be running into some trouble.

    • Strange.  These two copters are almost identical.  Both running 3.3rc8, 5010 288kv motors, same props...  Only difference is the two extra motors on the X8 and the fact the X8 is using a pixhack and the Hex is using a pixhawk.  Both have more than sufficient power : )

      IMG_461442237.JPG

    • Have the same problem with my X8 (330kv motors, 16" propellers)

      84.BIN

This reply was deleted.

Activity

Jose Araujo liked Jose Araujo's profile
Aug 29
spencer harvey liked spencer harvey's profile
Jul 9
More…