So my Iris+ experienced its second crash today and luckily it was not as volatile as the first.  All that is broken at first glance is the plastic gimbal mounts on the Tarot Gimbal. Those are not what I am concerned about.  This is my first drone that is this complex and I am really wanting to figure this thing out. I have been using it to actively search for my missing brother on Mt. Hood over the past month and I have yet to be able to recover him. I need this drone operational, its very important I get it working.  That said, I will start with an explanation of what happened during the last flight involving the crash.

It was its first flight of the day after the initial rebuild from the first crash.  After a quick ESC calibration I was able to get the Iris in the air. while in STD I flew forward a few feet then back at an altitude of approximately 4'. It was responding great and so i began to test the roll and began to move it to the right.  I managed to move it about 5'-6' to the right when suddenly the indicator light turned yellow.  The Iris quickly began to climb in altitude to about 20' and continued on its roll right trajectory right into the branches of a nearby tree.  It was completely unresponsive to any commands from me to stop it or change its path and it would not power down from throttle input even while bouncing around in the tree branches. In my haste to get it to power down I shut off the controller and it dropped. Still spooling up for a brief second once on the ground. Was a close call for a human hand reaching for the Drone but luckily there was no injury to anything but the Iris. 

This is the EXACT same behavior I had experienced from the first crash while using it for Search and Rescue for my brother Gerren.  After the first crash I had a friend of mine who has been building and doing drones for a few years take a look at it and do the repairs for me. He attempted to retrieve the flight dataflash logs but for some reason the data was corrupted for him. I believe I have been able to retrieve the data from the last flight as well, But like I said, I am very new to this Mission Planner and Flight data thing.

I have been going over many of the video tutorials on Youtube and previous threads on this site trying to glean an understanding of what I am looking at thus far.  So far I have been able to get MP to give me the "Log Analyzer" readings and from there I am currently feeling stumped (or just tired from staring at this computer for the last 6 hours at my attempt to figure this out, probably a combination of both honestly)  In my amateurish and beginner way of attempting to understand these crashes and fix the issue I will paste the logs from both crashes in this post. Any and all help is greatly appreciated, I really need to get back out there looking for my brother.

Crash on 1-3-15

Log File C:/Users/Logan/AppData/Local/Temp/tmp972D.tmp.log
Size (kb) 4713.3701171875
No of lines 64798
Duration 0:08:44
Vehicletype ArduCopter
Firmware Version V3.2
Firmware Hash c8e0f3e1
Hardware Type
Free Mem 0
Skipped Lines 0

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

Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FS_BATT FLT_MODE
Test: GPS = GOOD -
Test: IMU Mismatch = FAIL - Check vibration or accelerometer calibration. (Mismatch: 1.92, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = GOOD -
Test: Pitch/Roll = FAIL - Roll (-178.77, line 63374) > maximum lean angle (30.00)
Test: Thrust = FAIL - Avg climb rate 40.51 cm/s for throttle avg 720
Test: VCC = GOOD -

Crash on 12-18-2014

Log File C:/Users/Logan/AppData/Local/Temp/tmp1B8A.tmp.log
Size (kb) 384.9140625
No of lines 5679
Duration 0:00:00
Vehicletype ArduCopter
Firmware Version V3.2
Firmware Hash c8e0f3e1
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Autotune = UNKNOWN - No ATUN log data
Test: Balance/Twist = GOOD -
Test: Brownout = GOOD -
Test: Compass = GOOD - mag_field interference within limits (1.10%)

Test: Dupe Log Data = GOOD -
Test: Empty = FAIL - Empty log? Throttle never above 20%
Test: Event/Failsafe = GOOD -
Test: GPS = FAIL - Min satellites: 0, Max HDop: 99.99
Test: IMU Mismatch = GOOD - (Mismatch: 0.12, WARN: 0.75, FAIL: 1.50)
Test: Parameters = GOOD -
Test: PM = GOOD -
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = GOOD -

I am more than willing to dig out any more info necessary to figure this out as well as posting videos from the flights. (even though they make my gut wrench tight)

15.bin is crash on 1-3-15

12.bin is crash on 12-18-14

I could be going about this all wrong so I apologize for my ignorance, I will continue to try and educate myself on these matters while waiting for a response.

15.BIN

12.BIN

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

Join diydrones

Email me when people reply –

Replies

  • Update: so the Iris is once again operational and all systems are nominal at 100%. I was able to get some help from the guys over at ATI in Portland Oregon and after a couple hours of troubleshooting we where able to get it fixed. After resetting the pixhawk back to the OEM settings for the Iris and a couple of calibration settings for the GPS and RC, and some quick hardware re-arrangements we managed to get her In the air and flying correctly. Apparently their was some manual changes made during set up that greatly affected the Iris on top of the set up having been done for the wrong copter as well as having the GPS installed facing the wrong direction. Hence the incorrect heading direction on the MAVLink. We also could not retrieve the data from the first crash but believe it was the same malfunction caused by the incorrect values and set-up that caused the second crash. Thank you for the help getting my Iris up and running once more! This was one heck of a lesson for me and I learned way more than I thought I would.
  • This reply was deleted.
    • I think this might be the crash log from the first crash. bin 12 might be from when my tech turned it on in his shop. I would be greatly appreciated if someone would help take a look at it as well. If anyone has a link to a good tutorial on understanding these logs i am more than willing to dive in and learn.

      11.BIN

      • This reply was deleted.
        • Ok, well i beleive that the data from the first crash is more than likely gone somehow. I don't get how that could have happened but it apears that it did. I am now going to reset the Iris to the default settings and do both an accelerometer and compass calibration. I will then check the EKf parameters and be sure that the voltage on the low battery fail safe are set to the appropriate levels. I will update this thread with what happens for posterity in hopes that it might help others in experiencing my same issues. Hopefully this fixs my issues. Period. If not, well, it's been a real learning experience.........
This reply was deleted.

Activity