Help Reading Flight logs after a Crash

Hi all,

I am new the Pixhawk world but not to aviation.  I recently had a few incidents with my IRIS+ and am looking for some advice.  I had a roll over after landing on a bit of a hill with no damage.  I cleand up iris popped in a new battery and keept on flying and after some agressive flight I did a fast deceleration and at about 15 feet it did not respond to any inputs and leved itself and fell straight down no damage.  The second one is what really has me worried because it caused damage.  Everything was going great and another falling out of the sky. 


Any help analyzing the logs to understand what is going on with iris would be great.  Also suggestions to what calused the malfuntions and how to fix the issue. 

 

Thanks, in advance,

 

MsFirefighter662

15-03-15_15-37-28.bin

15-03-15_16-14-38.bin

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

Join diydrones

Email me when people reply –

Replies

  • Admin

    @MsFireFighter662

    An auto analysis of your first bin file revealed the following:

    Test: Autotune = UNKNOWN - No ATUN log data
    Test: Balance/Twist = GOOD -
    Test: Brownout = GOOD -
    Test: Compass = WARN - Moderate change in mag_field (27.35%)
    Max mag field length (557.00) > recommended (550.00)

    Test: Dupe Log Data = GOOD -
    Test: Empty = GOOD -
    Test: Event/Failsafe = FAIL - ERR found: CRASH
    Test: GPS = GOOD -
    Test: IMU Mismatch = FAIL - Check vibration or accelerometer calibration. (Mismatch: 18.32, WARN: 0.75, FAIL: 1.50)
    Test: Parameters = GOOD -
    Test: PM = GOOD -
    Test: Pitch/Roll = GOOD -
    Test: Thrust = GOOD -
    Test: VCC = GOOD -

    You appear to have had an IMU mismatch failure. 

    An auto analysis of your second bin file revealed the following:

    Test: Autotune = UNKNOWN - No ATUN log data
    Test: Balance/Twist = GOOD -
    Test: Brownout = GOOD -
    Test: Compass = WARN - Moderate change in mag_field (34.65%)
    Max mag field length (557.00) > recommended (550.00)

    Test: Dupe Log Data = GOOD -
    Test: Empty = GOOD -
    Test: Event/Failsafe = FAIL - ERR found: CRASH
    Test: GPS = GOOD -
    Test: IMU Mismatch = FAIL - Check vibration or accelerometer calibration. (Mismatch: 18.03, WARN: 0.75, FAIL: 1.50)
    Test: Parameters = GOOD -
    Test: PM = GOOD -
    Test: Pitch/Roll = FAIL - Roll (178.74, line 32882) > maximum lean angle (30.00)
    Test: Thrust = GOOD -
    Test: VCC = GOOD -

    You appear to have had an IMU mismatch failure again and your Roll exceeded the maximum lean angle. Also your compass is being affected by the quad's motors' magnetic fields.

    Regards,

    TCIII AVD

    • Thanks for the quick look over, I get that I can recalabrate the IMU problem but what can I do for the compas error from the motors?  Do you think that iris can be made airworthy again?

      • Admin

        @MsFireFighter662,

        I think that the IMU Mismatch might mean that the two onboard IMUs are not in agreement meaning one might be damaged.

        If your IRIS+ is still under warranty you should contact help@3drobotics.com and open a ticket and point them to this thread.

        Regards,

        TCIII Admin

        • I use the Mac version of mission planner and have not been able to find any of the tabs that can alow for anyalisis of the logs.  I guess there are Mac vs PC program differences.  I recalibrated the accelometers and the compas last night and plan on giving it a test flight today if WX holds out.  Is there a way to verity that the recalibration fixed the IMU issure? Anything elese I should do before the test flight?

           

          Thanks,

           

          MsFire

  • Admin

    @MsFireFighter662,

    The ArduCopter Wiki has a wealth of information: Link

    Regards,

    TCIII AVD

This reply was deleted.

Activity