Developer

ArduCopter-3.2.1 Beta Testing

ArduCopter 3.2.1-rc2 (release candidate #2) has completed beta testing and has been released as the official version available through the mission planner and other ground stations.

Changes from AC3.2 are listed below and in the ReleaseNotes:
1) Enhancements:
    a) reduced twitch when passing Spline waypoints
    b) Faster disarm after landing in Auto, Land, RTL
    c) Pixhawk LED turns green before arming only after GPS HDOP falls below 2.3 (only in flight modes requiring GPS)
2) Safety Features:
    a) Add desired descent rate check to reduce chance of false-positive on landing check
    b) improved MPU6k health monitoring and re-configuration in case of in-flight failure
    c) Rally point distance check reduced to 300m (reduces chance of RTL to far away forgotten Rally point)
    d) auto-disarm if vehicle is landed for 15seconds even in Auto, Guided, RTL, Circle
    e) fence breach while vehicle is landed causes vehicle to disarm (previously did RTL)
3) Bug Fixes:
    a) Check flight mode even when arming from GCS (previously it was possible to arm in RTL mode if arming was initiated from GCS)
    b) Send vehicle target destination in RTL, Guided (allows GCS to show where vehicle is flying to in these modes)
    c) PosHold wind compensation fix
    d) prevent infinite loop with do-jump commands pointing at each other
    e) pixhawk memory corruption fix when connecting via USB
    f) vehicle stops at fence's alt limit in Loiter, AltHold, PosHold (as it did in AC3.1.5)
    g) protect against multiple arming messages from GCS causing gyro calibratoin failure

Thanks to Raph for the video.  This is actually a video from AC3.2 until we have one specific to AC3.2.1.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • The problem with log analysis is it looks at the hole log and doesn't know the difference between cause and effect.

     

    The GPS issue was way earlier in the flight and was corrected.  HDOP was high but not an issue.  The RTL was started which it flew south when you switched to Stabilize mode and gave it some gas and then cut the throttle where is looks like it skidded across the black top and came to rest in the trees.

    Can not determine from the logs why it went south instead of west to your position.  One cause is the compass is wrong.

     

    In the future I would start a new discussion instead of putting it here.  This does not have anything to do with 3.2.1 testing.

     

    • The RTL was started which it flew south

      that's weird... so at that moment it is started to flying away from me to the trees :(

       when you switched to Stabilize mode and gave it some gas

      I was in a panic :(

      In the future I would start a new discussion instead of putting it here. 

      When I was writing this post didn't notice that there is a forum. Sorry for that, forum is diffidently better place to discuss this. Post new topic http://diydrones.com/forum/topics/help-me-analyse-this-crash 

  • Hey,

    Today I crashed my quad and I'm trying to understand what's went wrong.

    I was testing return to launch (RTL) mode. So I was able to get GPS lock.
    When RTL mode was enabled pixhawk just flew away from me and crashed between trees. 

    I noticed interesting think from logs:

    Log File C:/Program Files/Mission Planner/logs/2015-03-13 19-13-19.log
    Size (kb) 645.455078125
    No of lines 9390
    Duration 6 days, 2:15:22
    Vehicletype ArduCopter
    Firmware Version V3.2.1
    Firmware Hash 36b405fb
    Hardware Type PX4
    Free Mem 52816
    Skipped Lines 1

    Test: Autotune = UNKNOWN - No ATUN log data
    Test: Balance/Twist = GOOD - 
    Test: Brownout = GOOD - 
    Test: Compass = FAIL - FAIL: Large compass offset params (X:-342.00, Y:-400.00, Z:-55.00)
    FAIL: Large compass offset in MAG data (X:-342.00, Y:-400.00, Z:-55.00)
    Large change in mag_field (140.55%)
    Max mag field length (766.31) > recommended (550.00)

    Test: Dupe Log Data = GOOD - 
    Test: Empty = GOOD - 
    Test: Event/Failsafe = FAIL - ERRs found: FLT_MODE GPS 
    Test: GPS = FAIL - Min satellites: 0, Max HDop: 2.09
    Test: IMU Mismatch = GOOD - (Mismatch: 0.37, WARN: 0.75, FAIL: 1.50)
    Test: Parameters = GOOD - 
    Test: PM = WARN - 3 slow loop lines found, max 9.38% on line 4002
    Test: Pitch/Roll = FAIL - Roll (86.81, line 8128) > maximum lean angle (45.00)
    Test: Thrust = GOOD - 
    Test: VCC = GOOD -

    It is saying like GPS failed but I clearly remember that pixhawk was showing solid green light.

    I will appreciate any help.

    crash.zip

    https://storage.ning.com/topology/rest/1.0/file/get/3691189007?profile=original
    • I didn't read the logs, but with the compass failure and 0 sats the PH had nothing to work with in RTL. Analysis reports GPS failure.

  • today i was having same issue as yesterday, please see attached log. EKF Error's and also Baro Error's.

    Finally crashed bad, what could be the reason ?

    2015-03-14 14-48-44.zip

    https://storage.ning.com/topology/rest/1.0/file/get/3701957781?profile=original
    • below the auto analysis

      Log File C:/Program Files (x86)/Mission Planner/logs/2015-03-14 14-48-44.log
      Size (kb) 2912.201171875
      No of lines 40263
      Duration 0:03:35
      Vehicletype ArduCopter
      Firmware Version V3.2.1
      Firmware Hash 36b405fb
      Hardware Type PX4
      Free Mem 50880
      Skipped Lines 2

      Test: Autotune = UNKNOWN - No ATUN log data
      Test: Balance/Twist = GOOD -
      Test: Brownout = GOOD -
      Test: Compass = GOOD - No MAG data, unable to test mag_field interference

      Test: Dupe Log Data = GOOD -
      Test: Empty = GOOD -
      Test: Event/Failsafe = FAIL - ERRs found: FS_BATT CRASH
      Test: GPS = GOOD -
      Test: IMU Mismatch = FAIL - Check vibration or accelerometer calibration. (Mismatch: 10.35, WARN: 0.75, FAIL: 1.50)
      Test: Parameters = GOOD -
      Test: PM = FAIL - 21 slow loop lines found, max 11.55% on line 7705
      Test: Pitch/Roll = FAIL - Roll (169.77, line 38747) > maximum lean angle (45.00)
      Test: Thrust = GOOD -
      Test: VCC = GOOD -

      • here are more informations i posted on the support forum, hope someone can use it.

        Hi,
        the vibration level on this copter is pretty good, the values shown by the auto analysis are coming from high dynamic flying. 10G = really fast and a lot of fun. :oops:

        The copter is very fast and flies high dynamic, speeds up to 60mph or 100km/h.
        I'm looking for the Baro and EKF errors included in the logs, what could be the reason for ?

        The flight ended abruptly while flying upside down, doing some acro figure. the copter suddenly was not accept any pilot inputs anymore and crashed stright upside down to the ground without to try to correct his position. In the logs there are simultaneous Baro and EKF errors.

  • Just put the release of 3.2.1 on my LEGO's...worked great...thanks guys...loads of fun.

  • Attached a log from todays flight with my 2015 Hexa speed acro, i must admit great job you guys have done.

    This thing flies awesome absolutly razor sharp control, completely new acro expirience.

    i know i have a battery issue, in the log we can clearly see as i'm getting throttle the battery goes into the knees and begs for mercy. I guess 20C is do low for the output this thing is producing.

    There is also another EKF error, could anybody help me out what to do ?

    before i was having also an Baro Error but seems this is solved by setting "GPSGLITCH_ACCEL" to 2200.

    Could it be something similiar for the EKF faliure ?

     

    2015-03-13 16-27-20.zip

This reply was deleted.

Activity