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

        • thanks Randy for that, looking forward for the next release. By the way, would the new gimbal feature: "do-mount-control commands supported in missions" work if I use the traditional wiring for gimbal? or is it for gimbals which use Serial interface only?

          • Developer

            @Erwin,

            The mount-control mission commands should work for all gimbals.

            The next release candidate (AC3.3-rc2) will definitely, 100% be out in time for weekend testing.

            Txs for testing!

    • Hi Shad,

      This may have something to do with setting mnt_type in the settings.
      Mnt_type will need to be set these values:

      Mount Type (MNT__TYPE)

      Mount Type (None, Servo or MAVLink)

      VALUE MEANING
      0 None
      1 Servo
      2 MAVLink
      3 Alexmos Serial
      4 SToRM32

      Best Erik
      • Hi Eric,

        Thanks.  I looked at MNT_TYPE, but thought that the "3" that was set there was the proper value.  I'm not sure if the meanings changed in 3.3rc1 or what, but its working now when setting it to 1.

        Some of the other changes in 3.3rc1 are visibly better, thanks devs!

        • Hi Shad,

          Ok solved.., put your RC controlling channels in MNT_RC_IN_ROLL and MNT_RC_IN_TILT and your control from the transmitter is back...

          In the camera Gimbal Settings under Initial Setup I have the same RC Channels, and stabilize on.., which appear to work as well (stabilization I mean)
          Leave the input channels in this screen empty...

          MNT_TYPE = 1, MNT_DEFLT_MODE can be anything, depending on what the control should be during auto missions.

          Erik
        • Developer

          There seems to be some confusion because there is a new MNT_TYPE parameter in addition to the MNT_MODE parameter.  In your case the mode would be 3 but the type would be 1 

          • Developer

            MNT__ was a typo in the parameter description

            Fixed now

            https://github.com/diydrones/ardupilot/commit/85b0a18f610dc29c4cf96...

          • Hi Graig,
            I do find a Mount default operating mode (MNT__DEFLT_MODE)

            Mount default operating mode on startup and after control is returned from autopilot

            VALUE MEANING
            0 Retracted
            1 Neutral
            2 MavLink Targeting
            3 RC Targeting
            4 GPS Point
            Which I do have at 3 (RC Targeting)
            For the type I should make sense to put a 1 in there in case you work with Servo's like I do, but for the Alexmos serial it should be 3 correct ?

            Or do we have a MNT_Mode somewhere?

            Thanks !

            Erik
            • Developer

              Erik,

              The MNT_DEFLT_MODE is the mode that the mount will be in when it starts up and after a mission is completed that makes use of the mount.  So normally leaving that to "3" (RC Targeting) makes sense.

  • Okay, so its been a rough week for my birds.

    Just had a crash on 3.3rc1 with a y6b. I was doing some fast circles when all of a sudden it went out of control and crashed to the ground. Looking at the logs I think I cracked/broke a prop in flight as the vibrations rose quite a bit right before the crash.

    Here is the log.

    2015-04-24 09-55-37.log

    https://storage.ning.com/topology/rest/1.0/file/get/3701988370?profile=original
This reply was deleted.

Activity