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

    • auto analysis has to be fixed in mission planner. It's something Mr Osborne and whoever else is working with him needs to address, but I'm sure, just like with Kev's Log Analyzer, with things being such a moving target right now we are going to have to wait until the final hits and then they can catch up :)

  • I tested AC 3.3 RC10. This is a very stable release.
    And I wanted to draw attention to the following:
    1. Upload the firmware to Pixhawk AC 3.3 RC10 will be better if the first from AC 3.3 RC 9 down to AC 3.2.1, and then up to the AC 3.3 RC10
    2. Then need to check all the major parameters.
     And they are need to be rewritten.
    2. I do not use the automatic tuning. Better to use the manual settings for test flights.
    3. Very important buttons 'Calibrate Level" It is advisable to use prior to each flight.
    4. I'd like to ask to make the possibility of setting on or off the Audio Indications in auto mode. I can set the switch, but it is better to do it programmatically.
    My first the test here:

    Stabilize mode :  https://www.youtube.com/watch?v=meYPmOkk6yM

    Auto mode :  https://www.youtube.com/watch?v=UXIEqR_i45k

    • 1. Upload the firmware to Pixhawk AC 3.3 RC10 will be better if the first from AC 3.3 RC 9 down to AC 3.2.1, and then up to the AC 3.3 RC10

      As one fellow reminded me lately, this will do the reset as well:

      If I manually go in and change the SYSID_SW_MREV from 120 to 0, push the write params button and then disconnect/reconnect the parameters are restored to their defaults

      Saves some time;-)

      • Thanks, I'll try it.

      • This reply was deleted.
  • Sorry if this is repetitive (artifact of using a single thread for all feedback regarding this release vs. something threaded like APM 3.3 Forum I wish we could migrate to):

    I have found mixed reports of being able to connect the RSSI port on a FrSky receiver such as X8R to the sbus port on a Pixhawk, then setting RSSI_PIN to 103 to get RSSI input. However, other reports suggest this must be connected elsewhere in order for it to work with OSD, and yet others suggest PWM RSSI input has been implemented but will only be merged "in a future release". Is 3.3 that future release? I tried it and got odd values in the 90% range seemingly regardless of where I put the radio, and even if the radio was off, so I suspect either it is not implemented.

    I have seen reports of others doing this without a filter to convert the PWM to analog, however, so I thought I would ask. Can RSSI out on FrSky receiver report PWM RSSI to Pixhawk, and can it be viewable both in Mission Planner and OSD? Thanks all.

    • I'm using it with  the  RSSI filter as per wiki. 

  • I have a question about Autotune.

    I just ran it again, this morning, just to prove this point. It was executed twice before, on a day with no wind, same conditions as today. files 1 and 2 were on same day, file 3 was done this morning.

    I specifically wonder why roll values deviate so much every time and it seems that file 3 is close to file 1 again in roll values.

    Here is a comparison between file 2 and 3, listed below. File 2 would be a PRE_TUNE one.

    Would it be possible to comment on what is actually means when autotune produces such deviation every time and how it would make sense to adjust those values manually?

    I cannot think of anything else better than to run this autotune like, 10 times on the same battery type so AUW would be exact same and motors fed same current and then get average value for each parameter and use it for a permanent tune, as I am out of ideas.

    Is there any way to improve accuracy of this process? What can be done? Would it help for a tuning logic if we had a set of parameters to identify type of motors and AUW of the vehicle? I am just lost of where this deviation of after-tune values gets from.

    Comparing files after-tune.param and PRE-TUNE.PARAM

    ***** after-tune.param
    ARMING_CHECK,127
    ATC_ACCEL_P_MAX,43890.22
    ATC_ACCEL_R_MAX,118759.8
    ATC_ACCEL_Y_MAX,19387.29
    ATC_RATE_FF_ENAB,1
    ***** PRE-TUNE.PARAM
    ARMING_CHECK,127
    ATC_ACCEL_P_MAX,50821.42
    ATC_ACCEL_R_MAX,70294.46
    ATC_ACCEL_Y_MAX,19701.48
    ATC_RATE_FF_ENAB,1
    *****

    ***** after-tune.param
    COMPASS_MOTCT,2
    COMPASS_OFS_X,-106.1927
    COMPASS_OFS_Y,-30.84122
    COMPASS_OFS_Z,24.71892
    COMPASS_OFS2_X,74
    ***** PRE-TUNE.PARAM
    COMPASS_MOTCT,2
    COMPASS_OFS_X,-111.8069
    COMPASS_OFS_Y,-32.53017
    COMPASS_OFS_Z,15.17129
    COMPASS_OFS2_X,74
    *****

    ***** after-tune.param
    GCS_PID_MASK,0
    GND_ABS_PRESS,101040.5
    GND_ALT_OFFSET,0
    GND_TEMP,28.81843
    GPS_AUTO_SWITCH,1
    ***** PRE-TUNE.PARAM
    GCS_PID_MASK,0
    GND_ABS_PRESS,101103.1
    GND_ALT_OFFSET,0
    GND_TEMP,24.19114
    GPS_AUTO_SWITCH,1
    *****

    ***** after-tune.param
    INS_ACCSCAL_Z,0.9895147
    INS_GYR2OFFS_X,-0.02705187
    INS_GYR2OFFS_Y,-0.1423247
    INS_GYR2OFFS_Z,-0.06322701
    INS_GYR3OFFS_X,0
    ***** PRE-TUNE.PARAM
    INS_ACCSCAL_Z,0.9895147
    INS_GYR2OFFS_X,-0.02742356
    INS_GYR2OFFS_Y,-0.1415454
    INS_GYR2OFFS_Z,-0.0474136
    INS_GYR3OFFS_X,0
    *****

    ***** after-tune.param
    INS_GYRO_FILTER,20
    INS_GYROFFS_X,0.004249442
    INS_GYROFFS_Y,0.01446475
    INS_GYROFFS_Z,0.00545186
    INS_PRODUCT_ID,5
    ***** PRE-TUNE.PARAM
    INS_GYRO_FILTER,20
    INS_GYROFFS_X,0.005726107
    INS_GYROFFS_Y,0.01684802
    INS_GYROFFS_Z,0.005123362
    INS_PRODUCT_ID,5
    *****

    ***** after-tune.param
    RALLY_TOTAL,0
    RATE_PIT_D,0.01500276
    RATE_PIT_FILT_HZ,20
    RATE_PIT_I,0.2504629
    RATE_PIT_IMAX,2000
    RATE_PIT_P,0.2504629
    RATE_RLL_D,0.004
    ***** PRE-TUNE.PARAM
    RALLY_TOTAL,0
    RATE_PIT_D,0.01324288
    RATE_PIT_FILT_HZ,20
    RATE_PIT_I,0.2561696
    RATE_PIT_IMAX,2000
    RATE_PIT_P,0.2561696
    RATE_RLL_D,0.004
    *****

    ***** after-tune.param
    RATE_RLL_FILT_HZ,20
    RATE_RLL_I,0.09393342
    RATE_RLL_IMAX,2000
    RATE_RLL_P,0.09393342
    RATE_YAW_D,0
    RATE_YAW_FILT_HZ,1.386948
    RATE_YAW_I,0.07207587
    RATE_YAW_IMAX,1000
    RATE_YAW_P,0.7207587
    RC_FEEL_RP,50
    ***** PRE-TUNE.PARAM
    RATE_RLL_FILT_HZ,20
    RATE_RLL_I,0.07115527
    RATE_RLL_IMAX,2000
    RATE_RLL_P,0.07115527
    RATE_YAW_D,0
    RATE_YAW_FILT_HZ,1.388439
    RATE_YAW_I,0.07012143
    RATE_YAW_IMAX,1000
    RATE_YAW_P,0.7012143
    RC_FEEL_RP,50
    *****

    ***** after-tune.param
    SR3_RC_CHAN,2
    STB_PIT_P,4.837482
    STB_RLL_P,9.45916
    STB_YAW_P,4.601859
    SUPER_SIMPLE,0
    ***** PRE-TUNE.PARAM
    SR3_RC_CHAN,2
    STB_PIT_P,4.477704
    STB_RLL_P,3.592907
    STB_YAW_P,4.450249
    SUPER_SIMPLE,0
    *****

    after-tune1.param

    after-tune2.param

    after-tune3.param

    https://storage.ning.com/topology/rest/1.0/file/get/3702088002?profile=original
    • Developer

      Hi Paul,

      There are two measures that tell you which is the better tune, STB_XXX and ATC_ACCEL_X_MAX. When comparing two tunes look at which one generated the highest values. That will be the better tune.

      Looking at the two tunes for roll above I can see the tune that gave you the PRE-TUNE.PARAM. I can't tell you why the roll didn't run well in the PRE-TUNE.PARAM but you don't get that sort of variation without some sort of variation in the frame, or external disturbance at the wrong time.

      The only thing I can suggest trying is increasing your filter frequencies to 40 and see if your results are more consistent. (INS_GYRO_FILTER, RATE_PIT_FILT_HZ, RATE_RLL_FILT_HZ)

      For future reference the parameters set by or interesting for a tune are:

      ATC_ACCEL_P_MAX,
      ATC_ACCEL_R_MAX,
      ATC_ACCEL_Y_MAX,

      INS_GYRO_FILTER,

      RATE_PIT_D,
      RATE_PIT_FILT_HZ,
      RATE_PIT_I,
      RATE_PIT_IMAX,
      RATE_PIT_P,
      RATE_RLL_D,
      RATE_RLL_FILT_HZ,
      RATE_RLL_I,
      RATE_RLL_IMAX,
      RATE_RLL_P,
      RATE_YAW_D,
      RATE_YAW_FILT_HZ,
      RATE_YAW_I,
      RATE_YAW_IMAX,
      RATE_YAW_P,
      RC_FEEL_RP,
      STB_PIT_P,
      STB_RLL_P,
      STB_YAW_P.

      • Leonard,

        I did switch to 40Hz filter and I got to say difference in numbers post-autotune is quite dramatic.

        What is noticeable good is a realistic accel_y_max that is set now to a value that does not make vehicle jump like crazy in stabilize, and I see STB_ numbers all jumped up considerably. I will try to fly more later on new settings to confirm, only had 20min before first work meeting of the day today. .

        Comparing files after-tune4.param and AFTER-TUNE3.PARAM
        ***** after-tune4.param
        #NOTE: 9/10/2015 8:44:07 AM Frame :
        ACCEL_Z_D,0
        ***** AFTER-TUNE3.PARAM
        #NOTE: 9/8/2015 8:56:26 AM Frame :
        ACCEL_Z_D,0
        *****

        ***** after-tune4.param
        ARMING_CHECK,127
        ATC_ACCEL_P_MAX,77163.51
        ATC_ACCEL_R_MAX,137382.1
        ATC_ACCEL_Y_MAX,17564.14
        ATC_RATE_FF_ENAB,1
        ***** AFTER-TUNE3.PARAM
        ARMING_CHECK,127
        ATC_ACCEL_P_MAX,43890.22
        ATC_ACCEL_R_MAX,118759.8
        ATC_ACCEL_Y_MAX,19387.29
        ATC_RATE_FF_ENAB,1
        *****

        ***** after-tune4.param
        INS_GYR3OFFS_Z,0
        INS_GYRO_FILTER,40
        INS_GYROFFS_X,0.005611462
        INS_GYROFFS_Y,0.01585633
        INS_GYROFFS_Z,0.005035242
        INS_PRODUCT_ID,5
        ***** AFTER-TUNE3.PARAM
        INS_GYR3OFFS_Z,0
        INS_GYRO_FILTER,20
        INS_GYROFFS_X,0.004249442
        INS_GYROFFS_Y,0.01446475
        INS_GYROFFS_Z,0.00545186
        INS_PRODUCT_ID,5
        *****

        ***** after-tune4.param
        RALLY_TOTAL,0
        RATE_PIT_D,0.02312991
        RATE_PIT_FILT_HZ,40
        RATE_PIT_I,0.3502205
        RATE_PIT_IMAX,2000
        RATE_PIT_P,0.3502205
        RATE_RLL_D,0.007088783
        RATE_RLL_FILT_HZ,40
        RATE_RLL_I,0.2204735
        RATE_RLL_IMAX,2000
        RATE_RLL_P,0.2204735
        RATE_YAW_D,0
        RATE_YAW_FILT_HZ,1.347162
        RATE_YAW_I,0.08630268
        RATE_YAW_IMAX,1000
        RATE_YAW_P,0.8630268
        RC_FEEL_RP,50
        ***** AFTER-TUNE3.PARAM
        RALLY_TOTAL,0
        RATE_PIT_D,0.01500276
        RATE_PIT_FILT_HZ,20
        RATE_PIT_I,0.2504629
        RATE_PIT_IMAX,2000
        RATE_PIT_P,0.2504629
        RATE_RLL_D,0.004
        RATE_RLL_FILT_HZ,20
        RATE_RLL_I,0.09393342
        RATE_RLL_IMAX,2000
        RATE_RLL_P,0.09393342
        RATE_YAW_D,0
        RATE_YAW_FILT_HZ,1.386948
        RATE_YAW_I,0.07207587
        RATE_YAW_IMAX,1000
        RATE_YAW_P,0.7207587
        RC_FEEL_RP,50
        *****

        ***** after-tune4.param
        SR3_RC_CHAN,2
        STB_PIT_P,18
        STB_RLL_P,14.56053
        STB_YAW_P,4.746737
        SUPER_SIMPLE,0
        ***** AFTER-TUNE3.PARAM
        SR3_RC_CHAN,2
        STB_PIT_P,4.837482
        STB_RLL_P,9.45916
        STB_YAW_P,4.601859
        SUPER_SIMPLE,0
        *****

This reply was deleted.

Activity

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