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

          Andreas,

          I've spent some time today trying to reproduce the fall-out-of-the-sky issue using FollowMe and the only way I could make it happen was if the GCS sent impossible lat or lon values to Copter.  I can't be completely sure this is the issue but I think it's likely.  The fixes in master are here and here and these will go out with -rc10 which will go out this weekend I think.  I actually found places in Rover, Plane and AntennaTracker where this could happen as well so we've fixed them too.

          Thanks again for the report.

          • Hi Randy,

            Thanks for the feedback. I can confirm, that my followme-box works now with RC9 with the correct coordinate frame SET_POSITION_TARGET_GLOBAL_INT.

            I have also done more flights with Tower in followme mode and it worked without problems. Now I was quicker in sending take off from Tower, so that I did not have to re-arm the copter a second time, which has caused the strange immediate take off (without any second take-off command in Tower) and the crash 30s later.

        • Hi Andreas,

          The Tower tlog files can be found on your device under /sdcard/Android/data/org.droidplanner.services.android/files/tlogs/org.droidplanner.android/

          -Fredy 

          Tower lead dev

          • Hi Fredia,

            Thanks for the info - I found the .tlog file from my crash with 3.3RC9 in combination with Tower in followme mode. I hope this brings more insight what happened.

            Andreas

    • Developer

      I've also some crash with the latest versione of "Tower", simply with a fast scroll of the parameters, annoying a lot... :)

      • Hi Marco, on which version of Tower and 3DR Services are you seeing the crashes while fast scrolling?

        • Developer

          The latest available yestarday on PlayStore (Asus Fonepad 7 with KitKat, APM:Plane 3.3.0).

          • Are you signed in for the beta releases?

            You can check the specific app version by going to the 'Settings' screen.

This reply was deleted.

Activity